Xenon xbox with E71 - Help checking the Nand Filesystem

[warpjavier]

Hi,
I have an xbox 360 xenon that when I turn it on it start showing the X ball animation an suddenly goes to E71 error message.
I read that E71 is related to a corrupted nand filesystem so I would like to try to check it or rebuild it.
The weird thing is sometimes it boot to the dashboard and as soon as I try to start a game, E71 shows up. Sometimes doesnt even show the X ball animation.

I already dumped the nand on this console and unfortunately is not downgradable nor hackeable as it has the 8507 update applied and I also don't know the CPU key.

The big question is, Is there any way to check if the filesystem is corrupted or rebuild it not knowing the CPU key?

Could be hardware error related as the E71 error does not show up every time at the same place/time?

Thanks

[damox]

The big question is, Is there any way to check if the filesystem is corrupted or rebuild it not knowing the CPU key?

No.

[sandungas]

I did a brick with the same symptoms that you explain, but mine was e79
It was produced when installing a "xd card" socket (dual nand)

The 360 used to show the animation with the ball (included sound), but after this always an e79 (i cant remember but probably i saw an e71 too sometimes)
Rest of the times the console not even boot (black screen)



I fixed it writing an old nand dump... i cant assure that this errors means the same always, but mine was not a hardware damage, it was corruption of data inside the nand
I guess that the animation of the ball is inside the kernel... this means that all the "bootloader stages" are working, and the kernel is working too... the fail is after all this (probably the filesystem is loaded after the kernel)

[cory1492]

Is the bootloader animation not in a xex in the filesystem (bootanim.xex)? Getting to dash means the file system isn't really the issue, as well.

If you were tinkering around inside at all (ie: to get a flash dump) I'd check for loose bits of solder and other conductive material, especially around the NAND and the place where the NAND vias emerge on the backside. From the way E71 is showing up it sounds like a timeout issue waiting for data from the NAND, that the data is correct but isn't being read accurately in whatever number of retries software allows for - but the problem is intermittent. If you had soldered the NAND itself, I'd suggest reflow to ensure no cold joints which can easily cause such intermittent results.

You should also be able to get a NAND dump and at least try to verify the file system (raw extract works) is readable using flash tool with just 1BL key, even without CPU key. As to rebuilding the FS, I don't think there is a way without CPU key, but that may just be because all the current rebuild methods build everything in the NAND, not just the file system.

[warpjavier]

I didn't mess with the system's nand before E71 showed up, actually, is not my system, its a customer's.
Now, its showing RROD with 0022 secondary error, by the reading I've been doing in other threads, its still related to the nand/SB.
The nand dump I made looks good, I dumped the fs with nand tool and everything looks fine.
I think is a hardware problem like a resistor/capacitor dead or short between nand and SB.
I'll keep trying.

Thanks

[l_oliveira]

Try exploiting it (if it's pre 8xxx) and run emulators for some hardware testing.
If you manage to get it running linux and emulators you should be able to rebuild a 1888 nand image and udate it to 7371 again.

But then if you fix it that way it would be a great system for offline use.

I would not go online with it ... lol

[cory1492]

l_oliveira, it is already at 8507.

If possible reflow the SB chip, and still... inspect the entire board for stray bits of metal/any other conductive material inside the machine that doesn't belong (especially if its from a customer) - there is no end to the amazing things that wind up in consumer electronics without the awareness (real or embarrassment induced) of the owner. Spiders, lizards, roaches, and who knows what else that have ?minds? of their own have been found shorting out consoles in the past; can't find it but I'm pretty sure there is an interesting thread on it here.

[warpjavier]

Hi,
The dump I got from the NAND seems ok to me after comparing the files with another good dump I have.
Now, its showing 3 Red lights with 0022 secondary error. If I'm not mistaken, that also means corrupted nand.
I'm gonna dump the nand 2 more times and compare the dumps to see if I get different data every time.

If possible reflow the SB chip, and still...

I don't think the SB needs reflow as I can dump the nand.
I also inspected the mainboard very carefully with a magnifier and nothing weird found.

I was thinking that maybe the GPU needs reflos as is in charge of the RAM. Could be that when the system files from the NAND are copied to RAM they get corrupted somehow.

I'll keep you guys posted.

BTW, thanks for the answers.

PS. Is a Shame its been updated to 8505 as I cannot play more with it and at least extract the CPU key.

[marinho]

warpjavier ..

i had  same error here , i fix it
erasing my nand and write the dump again

[joeyddr]

I have a problem with the same error, 0022 and i check the nand with the infectus tool and it comes up with no bad pages either.... lemme know if you ever fix it.

[warpjavier]

I dumped the nand 4 times, and I get different dumps, I guess the nand is bad, od a componen between the nand and the SB is bad.

[krestean]

first, do you use xbr, and if so, did you move badblocks (if any) before flashing?

this is what worked for me :p

Dump the current nand, you will get errors..
you will need to flash these errors..

Fire up nandpro and extract the blocks that did error on the dump, from the flash image (the one you used to flash, the one that lead to e71) on pc

Then you flash those blocks to the nand, and hope for the best

[ReverseAffect]

krestean,
« Reply #10 on: November 19, 2009, 03:11:55 PM »
was the last reply here......hint 8507 dash no xbr...lol
and old post......

[Neptune]

Sorry to keep reviving old stuff..

@OP:

Sounds like your NAND developed some bad blocks post-update and it didn't . You should be able to manually remap those. I assume by now you figured something out though =/

[Gazcoigne]

the only way i have managed to fix E71 was on an exploitable console.

IMHO you will not be able to fix the issue as your box is not exploitable.

without CPU key you cannot rebuild a working NAND

either send to m$ and pay for them to fix it

or use it as spares and move on

[maximilian0017]

I dumped the nand 4 times, and I get different dumps, I guess the nand is bad, od a componen between the nand and the SB is bad.

Is it always the same blocks? (/4200hex), then i would make a load of dumps of that area and flash those block to the spare area using badblock mover by Redline99.
Maby erase the bad blocks original place to mark them bad?

[warpjavier]

The console is gone, I used the parts as spare.
As far as I know, a console with E71 and not having the CPU key, is not fixable.

Thanks anyway!

[ReverseAffect]

i guess this was a last min posting spot as some posted replys to your last reply of November 19, 2009...
and it's now feb....lol
i was having fun and watching peeps post for "i guess a jot down reason only" warpjavier .....so no don't close it yet...lol
s
after all it only takes 1 poster to update an old post...then most goto answer it because of it showing new in the section...
---cough----Mr. krestean ...lol

[maximilian0017]

i guess this was a last min posting spot as some posted replys to your last reply of November 19, 2009...
and it's now feb....lol

Other people who have the same problem can always use the SEARCH function to find it, so no total loss