Nand Superhero?!

[showstopper]

Im looking for a nand superhero to help me please!!

OK so brief outline.
I tried to dump my nands but i kept getting error 250 in block 19 and the nands wouldnt compare. So i posted this thread - http://team-xecuter.com/forums/showthread.php?t=80382

I ran this script (nandpro nand1.bin: -e16 19 1) and compared the nands and they compared. So I created my .ecc file However I think I must of made a mistake somewhere as my console will not boot into retail or stock dash.

Now im worried that I actually dont have any good nand dumps and i have a paperweight shaped as an xbox.

Could someone please check these nands and tell me if i can rebuild a new nand image (Jasper 16mb) or if i have completely messed up.

Please leave snide comments about quadruple checking everything beforehand or sending to an expert. I know this already!

So in this zip - http://www.mediafire.com/?9bw599v7jhx6kwf are 2 folders:

Oldest - The nand dumps before i ran the script above
Newest - The nand dumps after the script.

 

[Martin C]

You can't rebuild anything until you have a CPU key.

Did you keep one of your NANDs before deleting block 19?

 

[showstopper]

OK so i found some more nands on my laptop - http://www.mediafire.com/?r5pe2ioapdva2tp

They are compare without differences so im hoping i should be ok.

 

[Martin C]

Your NANDs all look ok. What happens when you try and boot?

If you get 0022, how long does it take to appear?

Pics of your soldering is also helpful.

 

[Beejeex]

Did you write xell with the remapped block?
First you need to get xell booting before the next step...


Bee

 

[showstopper]

Your NANDs all look ok. What happens when you try and boot?

If you get 0022, how long does it take to appear?

Pics of your soldering is also helpful.

The nands in my 2nd post yeah?
I sent my console off to someone else as i knew i messed up. I gave him a cd with the nands in my 1st post and he says that it just does not boot into anything and all the nands are corrupt. I think he is right. I have found some more nands (2nd post and i think they are ok).

 

[Beejeex]

i don't see anything wrong with the nands except for the remapped block.

but Martin probably would know this better then me.

Bee

 

[Martin C]

I'm trying to understand why you were messing around with the bad blocks in your original NAND. The second set of dumps have had remaps done which has thrown it all out.

I know this because block 3ff still contains data, which is only possible if the block was remapped.

Where are you based and who did you send the console to?

 

[showstopper]

I'm trying to understand why you were messing around with the bad blocks in your original NAND. The second set of dumps have had remaps done which has thrown it all out.

I know this because block 3ff still contains data, which is only possible if the block was remapped.

Where are you based and who did you send the console to?

I think my housekeeping of the nands is all over the place. I think the nands in my original post are before i actually did anything. The nands in my second post and the ones after i ran the script.

The 2nd set of nands seem OK so i am hoping he can flash this and it should be good.

 

[WNYConsoles]

Try this ECC - http://wnyconsoleservices.com/showstopper.zip

 

[Martin C]

Did you read what I wrote? The second set of NANDs are wrong. Someone has messed around with them and they're misreporting. Block 19 was erased and 360 Flash Dump Tool isn't seeing it as a bad block.

I really wish people wouldn't mess with their original NAND!

---------- Post added at 21:06 ---------- Previous post was at 21:05 ----------

Try this ECC - http://wnyconsoleservices.com/showstopper.zip

And how is he going to get around the bad block without a remap?

 

[showstopper]

Did you read what I wrote? The second set of NANDs are wrong. Someone has messed around with them and they're misreporting. Block 19 was erased and 360 Flash Dump Tool isn't seeing it as a bad block.

I really wish people wouldn't mess with their original NAND!

---------- Post added at 21:06 ---------- Previous post was at 21:05 ----------



And how is he going to get around the bad block without a remap?

You can see im struggling here!!

OK so you are saying that the nands in my first post (oldest and newest) are actually OK? Cause nandpro3 says they dont compare.

The nands in my 2nd post (nand4.zip) do compare in nandpro3 but you are saying they are wrong?

 

[Martin C]

NANDs with bad blocks invariably dump bad data, inconsistently.

So we erase the bad block just to make sure the rest of the data checks out. Remember that the data which should be in 0x19 has been remapped to 0x3FF so as long as you get matching nands after this, you know that the rest is ok. This doesn't deter from the fact you have a bad block.

Erasing the block stops 360 Flash Dump Tool from reporting it. We don't want that as it throws a false positive (like what's happening in this case).

So:

http://www.2shared.com/file/kj6jznkw/showstopper.html

unrar.

flash the .ecc file to the console with +w16
then

nandpro usb: -w16 19ecc.bin 3ff 1
(block 19 from the ecc after it was written to a VNAND).

It should glitch.

 

[showstopper]

NANDs with bad blocks invariably dump bad data, inconsistently.

So we erase the bad block just to make sure the rest of the data checks out. Remember that the data which should be in 0x19 has been remapped to 0x3FF so as long as you get matching nands after this, you know that the rest is ok. This doesn't deter from the fact you have a bad block.

Erasing the block stops 360 Flash Dump Tool from reporting it. We don't want that as it throws a false positive (like what's happening in this case).

So:

http://www.2shared.com/file/kj6jznkw/showstopper.html

unrar.

flash the .ecc file to the console with +w16
then

nandpro usb: -w16 19ecc.bin 3ff 1
(block 19 from the ecc after it was written to a VNAND).

It should glitch.

Thank you for this Martin - i will report back and see how it goes.

 

[showstopper]

My mate tried this but he gets error 202 block 19.
Any ideas?

 

[Martin C]

As per my sticky:

2. Write the ecc file to your NAND as per normal. You'll get an error writing to one of the blocks. Don't worry about it for now.

Did you even read it?

It's a BAD BLOCK. You cannot read or write to it, hence BAD.

 

[showstopper]

As per my sticky:

2. Write the ecc file to your NAND as per normal. You'll get an error writing to one of the blocks. Don't worry about it for now.

Did you even read it?

It's a BAD BLOCK. You cannot read or write to it, hence BAD.

Sorry i thought with the files you posted that i wouldnt get that error.

 

[Martin C]

See, this is the problem with people not understanding due to other people posting up stuff like 'you can fix a bad block by mapping it back' etc etc.

You CANNOT fix a bad block. It's a hardware error. Read up on bad block management if you need to understand it more:

http://www.free60.org/NAND:Bad_Blocks

The fact you're seeing 202 confirms what I said from the start that the first batch of nands you uploaded were 100% fine as they showed correctly this was being remapped to 3FF.

Carry out the instructions I gave you and let me know what happens.

 

[nofeloniesyet]

martin is trying to explain to you that the memory chip that actually holds the nand image,has a bad sector if you will,much like a hd,and the data that needs to go there,cannot be written there because its bad,so that data gets remapped to a spot on the nand that is good,in the reserved for sh*t like this area,for lack of better words.

you will always get error whatever reading or writing that block on that console.

btw,if your installer has to be spoon fed this info...............and ill leave it at that.