Hacking Tried to update dashes on my JTAG, ended up with E71.

[Devante]

Hey guys,

I'll try to make this brief.

I have a JTAG Xenon on 13599.

I updated from 13599 to 17416.

During the avatar update step, it showed it was extracting files, then showed me the E71 error.
Any attempt to turn the 360 after resulted in E71.
I took my backup (dumped with NAND Flasher 360 v1.2.0) and used the installed Xell Reloaded to install my backup.

Well FSD loads fine as do games and the avatar editor, but if I try to go to the original 360 menu (NXE) or go into system settings via the mini-blades, it'll turn into an E71 error. This also happens with one game; The Walking Dead episode 1.

So now I don't know what to do.

I should also note that when I dumped my 13599 image, it showed I had 11 bad blocks. But I remember when I originally JTAG'ed the system and also when I updated my dashes a couple of times, I only had one bad block. Now it shows 11 (including the one I had way back when)!

Any advice would be appreciated!

I have my original stock NAND (old blades menu, 1 bad block) and the dump I got before updating today (13599, 11 bad blocks).

 

[C-Kronos]

1. With the console off, press and hold the sync up button (the small white one)
2. While holding the sync button press the power button to turn on the console
3. Continue to hold the sync button until the Console has booted up completely.
4. During the boot process the console should clear any failed updates, allowing you to use it normally.
   
   That may work, and the bad blocks are on your NAND itself, it doesn't matter if your original NAND dump only had 1 bad block, they can occur over time.

 

[godreborn]

my suggestion is to remap the bad blocks (jtag tool can do this by comparing ur nand to one downloaded from its repository).

 

[Devante]

1. With the console off, press and hold the sync up button (the small white one)
2. While holding the sync button press the power button to turn on the console
3. Continue to hold the sync button until the Console has booted up completely.
4. During the boot process the console should clear any failed updates, allowing you to use it normally.
   
   That may work, and the bad blocks are on your NAND itself, it doesn't matter if your original NAND dump only had 1 bad block, they can occur over time.

Thanks for the suggestion, but I tried that already. So does that mean eventually the entire NAND will go bad?

As for remapping the bad blocks, I'm downloading Coolshrimp JTAG Tool right now and will probably be able to figure it out, but if you have the time, mind typing a quick summary of steps?

 

[godreborn]

open ur nand with a program called degraded to determine the block and location numbers, open jtag tool and click remap bad blocks, input the block and location numbers and click unmap, input ur cpu key in the applicable box and create ur freeboot image, open the freeboot image in the remap section of jtag tool and hit remap. after doing that, open with the image with degraded to see if all bad blocks r fixed.h

oh, make sure u click the correct smc as well before creating the freeboot.

 

[Devante]

OK I fixed it.

Here's what I did.

Flashed my original JTAG NAND back using Flash360 (instead of Xell Reloaded).
- This got rid of E71 while going to NXE or system settings.

Redumped NAND using Flash360.
- Checked this NAND using Degraded.
- Degraded showed my original bad block as the only bad block, but it also showed 5 blocks that were remapped.

Unmapped ALL of the bad and redirected blocks using AutoGG.
- Remapped the single bad block.

Created 14719 image using J-Runner.
- Flashed it using Flash360 (ran from the Xbox 360 itself)

SUCCESS!

Not sure why it showed I had 11 bad blocks before, but now it shows my single bad block that I've always had and everything works fine.
I think what messed me up was using NAND Flasher to dump and Xell Reloaded to flash. Between them, I got all kinds of non-existent bad block issues.
It seems Flash360 handle dumping and flashing a lot better, and J-Runner is a cinch to use.

 

[DinohScene]

I also found that Flash360 is better then XeLL and other flashers (can't hardware flashers tho)

Maybe your NAND is slowly corrupting?
It's weird tho ;o

 

[godreborn]

I personally use nandflasher 360 instead of flash 360.

 

[DinohScene]

Nandflasher 360 isn't bad either.
It's more GUI then Flash360

 

[Devante]

Actually, NAND Flasher is what I used to backup my NAND on this update. It was the one that said I had 11 bad blocks when dumping when in actuality I only had 1.

 

[DinohScene]

What does your hardware flasher say?
Or did you dump it via LPT?

 

[godreborn]

Actually, NAND Flasher is what I used to backup my NAND on this update. It was the one that said I had 11 bad blocks when dumping when in actuality I only had 1.

not sure what could have happened. I originally used flash360 then jumped to nandflasher 360. never gotten a bad block from either. something must've messed up while it was dumping the nand if it gave u incorrect information.