Odd Retail Dash issue (RDoD)

[Menethoran]

OK, ran into a weird issue.
Had dash 16537 without Kinect/avatar files. Kept getting nagged about updating (connected to the network/internet)... So, I figured Id just go ahead and update to 16547 to stop the nagging and while I was at it, install the Kinect and Avatar items.
I looked for my Original NAND only to find out it had been on an external drive that took a crap on me and I lost the NAND when I tried to recover it (still had CPU key and KV file)... Anyway, I figured I would just use NAND Flasher 360 and read the nand from inside the xbox.. Went flawlessly (reported 1 bad sector at 0x0E8) copied the nand to my pc and used J-Runner to build the update.. J-Runner didnt give any errors...
So, I copied the update back to my USB stick, booted Xell and waited.. only to have it stick on "UDA0 Fat Format (Or something along those lines)" and not go any further like it normally would (as in, wouldnt update through Xell...)
Anyway, So i figured what the heck, ill just update through NAND Flasher 360... and again, worked without any flaw...

Booted into FS3 fine, and works perfectly there... but when I try to go into the Retail dash, The Xbox crashes with Error 71...

Any ideas on what would cause this and/or how to fix it?

So, anyway... tried doing some research... (Saw a post about possibly being LDVs)..
Anyway, booting XELL:

*nand init
*network init
*initializing lwip 1.4.0...
Reinit PHY...
Waiting for link...link up!
*requesting dhcp...success
*starting httpd server...success
*usb init
*initializing USB EHCI...
Initializing EHCI bus 0 at 0xea0030000
Initializing EHCI bus 1 at 0xea0050000
EHCI bus 1 port 4: low speed, releasing to OHCI
*Initializing USB OHCI...
USB bus 0 device 1: vendor 0000 product 0000 class 09: USB Hub
USB bus 1 device 1: vendor 0000 product 0000 class 09: USB Hub
USB: New device connected to bus 1 hub 1 port 4
USB bus 1 device 2: vendor 045E product 02A9 class FF: Xbox 360 Controller
*sata hdd init
ATAPI inquiry failed
no ata device connected.
*sata dvd init
ATAPI inquiry model: HL-DT-STDVD-ROM DL10N
SATA device at ea001200

Stops there and gives no further information...
It did this before the update but stopped after the SATA device at ea001200 comment and stopped at the UDA0 comment..

Any ideas?

 

[[email protected]]

disconnect hitachi drive and try again, you will see e-fuses then

 

[Menethoran]

Thanks Eugene... That did in fact get me past the lockup in Xell... But only has me more confused now because my fuseset 07 is 6 Fs... and the LDV of the update nand I wrote is also 6.. So, not much help there...

And sorry, the bad block was 0xb8

and in xell, it kicked back with these messages at the end of the flash (figured Id try a flash through Xell to see if it fixed the issue):
!SFCX: Bad Block found at 000000B8
block 0xb8 seems bad, status 0x00000250
Block Cannot be recovered (AKA it's really bad)
!SFCX: Bad block found at 000003FF
block 0x3ff seems bad, status 0x00000250

image written, shut down now!

 

[Menethoran]

Flashing the nand through Xell seemed to fix it...

 

[Martin C]

And sorry, the bad block was 0xb8

This is what's causing E71. You weren't dealing with it correctly.

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

NANDflasher 360 will remap bad blocks for you.

So if you remapped B8 to 3FF as part of the build process, when you write back, NANDFlasher will move the now EMPTY block of 3B8 to 3FF.

In future, if you need to write a NAND back using NANDFlasher and there are bad blocks, make sure you use the 'noremap' prior to building.

All you needed to do was use the J-Runner Update feature with dashlaunch installer. It literally does it all for you.