Nand Dump - Error 204 reading block 61

Bzaina

Full Member
Sep 27, 2011
26
0
Portugal
Hi.

Sorry for bother you guys but I'm having a problem while trying tu dumping the nand on my xbox.

When i try to dump it, i get this

"Error 204 reading block 61
Error 250 reading block 2DF8
Error 210 reading block 2DF9
Error 210 reading block 2DFA
Error 210 reading block 2DFB
Error 210 reading block 2DFC
Error 210 reading block 2DFD
Error 210 reading block 2DFE
Error 210 reading block 2DFF
3FFF"




Uploaded with ImageShack.us

Could anyone explain me how to solve this problem?

I have a nandx connected to my xbox by wire connection and i've already checked the connections... it seems ok.
 
Last edited:

Goldensavage

VIP Member
Jul 26, 2009
3,332
0
Essex, UK
It is not always soldering, but mostly. Check and re-check.

One thing i did notice. If you have your pc plugged into the same socket as many appliances, if one of the appliances switch on and off, like a fridge or freezer or something. It draws power from the pc. and with throw up errors. Had this while writing my nand.

I always turn everything else connected off now.

I had no bad reads/blocks on my 13604 nand. so my soldering is perfect. i know my falcon glitched perfect first time

i upgraded to 14699 before glitching to make life easier with the new dashboard, as i do with all 360's i process and low and behold I had one error on my 360 nand dump. same error 4 times. and i checked it in 360 flashtool.

It will bring up all actual bad blocks.

But in flashtool it didn't say any bad blocks were there. also that specific part was text.
so kept my orginal nand and my new multibuilder fresh retail nand ready just incase.

There are a few threads here on how to map bad blocks, just check them out.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
THIS is the ONLY process you need for checking your dump.

16MB consoles:

nandpro usb: -r16 nand.bin

256/512MB consoles:

nandpro usb: -r64 nand.bin

Open your nand.bin in 360 Flash Dump Tool. If you have no 'bad blocks' tab, you're good to go.
If you have bad blocks which are remapped, you are good to go.

If you have unmapped bad blocks, dump again.

Repeat until you either have no bad blocks or any bad blocks are remapped.
 

Bzaina

Full Member
Sep 27, 2011
26
0
Portugal
Any time i get errors like that its normally the soldering. I would go back over them and touch them up again or even pull them out and resolder them. That normally fixes it for me.
It is not always soldering, but mostly. Check and re-check.

One thing i did notice. If you have your pc plugged into the same socket as many appliances, if one of the appliances switch on and off, like a fridge or freezer or something. It draws power from the pc. and with throw up errors. Had this while writing my nand.

I always turn everything else connected off now.

I had no bad reads/blocks on my 13604 nand. so my soldering is perfect. i know my falcon glitched perfect first time

i upgraded to 14699 before glitching to make life easier with the new dashboard, as i do with all 360's i process and low and behold I had one error on my 360 nand dump. same error 4 times. and i checked it in 360 flashtool.

It will bring up all actual bad blocks.

But in flashtool it didn't say any bad blocks were there. also that specific part was text.
so kept my orginal nand and my new multibuilder fresh retail nand ready just incase.

There are a few threads here on how to map bad blocks, just check them out.
each time you dump this are you getting the errors in the same place every time?
THIS is the ONLY process you need for checking your dump.

16MB consoles:

nandpro usb: -r16 nand.bin

256/512MB consoles:

nandpro usb: -r64 nand.bin

Open your nand.bin in 360 Flash Dump Tool. If you have no 'bad blocks' tab, you're good to go.
If you have bad blocks which are remapped, you are good to go.

If you have unmapped bad blocks, dump again.

Repeat until you either have no bad blocks or any bad blocks are remapped.
Hi everyone and thank you for your time.

That errors were always on the same block and on the same type everytime i tried to dump the nand.


I've checked and resoldered all the wires and checked it again. But now my console don't even power on and jtag tool don't recognise it. The wires are well placed. Checked it over and over.

Don't know what to do anymore...


If it helps, here it goes...


http://img40.imageshack.us/img40/4067/14122011035.jpg
http://img824.imageshack.us/img824/4696/14122011036.jpg
http://img849.imageshack.us/img849/9664/14122011037.jpg
http://img641.imageshack.us/img641/6528/14122011038.jpg
http://img214.imageshack.us/img214/1192/14122011039.jpg
http://img12.imageshack.us/img12/7673/14122011040.jpg
http://img706.imageshack.us/img706/5089/14122011041.jpg
http://img11.imageshack.us/img11/909/14122011042.jpg
http://img33.imageshack.us/img33/6039/14122011043.jpg
 
Last edited:

Bzaina

Full Member
Sep 27, 2011
26
0
Portugal
So you've not flashed ANYTHING to your console in between it working and not?
NO, NOTHING. I read these posts, unsoldered (don't know how to say but i mean remove the wires) all the wires that connect to nandx, solder it all again and add that two wires (yellow and red one, that connect to the jtag thing that has a switch).

Didn't flash ANYTHING and didn't even save any nand.
 

Bzaina

Full Member
Sep 27, 2011
26
0
Portugal
You had the NAND dump from the screenshot, yes?

If it's no longer booting then you need to go over EVERYWHERE you've had a soldering iron.
I checked again all the connections and wires and they seem pretty well... no bridges found but the xbox is pretty much dead! It should power on even with the wires connected, right?

EDIT----


don't know what could i possibly done but i've just removed ALL the wires and the xbox didn't give any sign of life!


http://img824.imageshack.us/img824/4696/14122011036.jpg see this wire? It is "in" the board. I mean, when i pull it back or remove it, theres a hole in that location just like the other wires from the nandx. Could be this the probleam? I removed the wire already but nothing happens..
 
Last edited:

fersy

VIP Member
Dec 9, 2010
523
0
thats probably not strictly true this has happened me before and after shorting the nand it came back to life he may have corrupted something.

ps i know this is over a month old but somebody else might find this thread with the same problem
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
thats probably not strictly true this has happened me before and after shorting the nand it came back to life he may have corrupted something.

ps i know this is over a month old but somebody else might find this thread with the same problem
It's 100% true if the OP was telling the truth. He hadn't flashed anything to it, so there's no chance the SMC was corrupted (which is what the NAND shorting does - it puts the SPI into bad-flash mode).