Xell works, but E74 when booting normally

Twinbird

Senior Member
Feb 9, 2010
124
18
Canada, ON
Hello,

I have a JTAGed Falcon Xbox 360. It is wired up using the original SMC points. When powering on with the eject button (or without the DVD drive) it boots into Xell, no problems. However, if I power it on normally with a DVD drive, I get E74 (1022). Would I need to reflash the NAND? What could be causing this?

Thanks!
 
You might also have a real E74 because XeLL does not go through the normal booting sequence as the Dashboard does. Therefore, when you try to boot normally, you get E74. But when you boot using the Eject button, XeLL boots!
 

Twinbird

Senior Member
Feb 9, 2010
124
18
Canada, ON
Thanks for the replies. I will flash it back with the original NAND and see how it goes.

I have reballed the GPU and HANA chip on this console. I have also reflowed the SB... I hope it's not a real E74 :mad:.

EDIT: Do I need to remove the JTAG wiring after flashing back the original NAND?

EDIT 2: I removed all the JTAG wiring and flashed back the original NAND... still the same problem.
I am now in the process of reballing the SB.
 
Last edited:
Its weird that the E74 didn't even go after reballing the GPU...
 
Last edited:

Twinbird

Senior Member
Feb 9, 2010
124
18
Canada, ON
I have reballed the GPU, the HANA and the SB (SB I reballed twice) and it's still giving me RRoD :( :(.
Right now I'm at E79 (1033) so it may still be a problem with the image I flashed to the NAND (I flashed back the original NAND image and removed the JTAG wiring so it should boot up normally).

Is there a way to confirm 100% you are flashing a good NAND to the console? Maybe I go something mixed up?

If I can't get this console working I'll find another Falcon console, and if it's not JTAGable I will just transfer the NAND and CPU over from this one. But if it's a problem with the image I flashed then the same thing will happen on the other system.
 

Twinbird

Senior Member
Feb 9, 2010
124
18
Canada, ON
I've been reballing for a while and I've never had any real issues. To me, the GPU reball was good. But I will look into reballing the GPU again.

Anyways, the original NAND image I flashed the console with was not the right one. I do not have an actual original dump of the NAND. Using my CPU key, is it possible to create an original flash image?
 
Last edited:

J2G

VIP Member
May 13, 2010
3,737
0
90°N
www.esl-communications.com
Don't get what your saying are you telling me you flashed the wrong one or you just took a piss in the dark lol.
Anyway if you don't have the original nand you are going to need to use a donor nand then open it in 360_Flash_Tool and patch the CPU Key.
You can get donor nands in Cools Jag Tool click Repair Bad Nand / Clean nand to download..
 

Twinbird

Senior Member
Feb 9, 2010
124
18
Canada, ON
The backup I had was created when the console was already JTAGed so it wasn't an original backup. That is why it was giving my E79 (1033) when I removed the JTAG wires.

I have downloaded a clean NAND using Jtag Tool. How do I inject my CPU key using 360 Flash Tool? It only gives me the option to import an encrypted KV.

I used the "Convert XBR To Original" option in Jtag Tool, I clicked "Convert" and created a NAND image (after opening up my freeBOOT backup and the original NAND I downloaded). Would this be an original NAND I can flash to the console? Or do I need to inject the CPU key into the clean Falcon NAND using 360 Flash Tool?
 

J2G

VIP Member
May 13, 2010
3,737
0
90°N
www.esl-communications.com
The backup I had was created when the console was already JTAGed so it wasn't an original backup. That is why it was giving my E79 (1033) when I removed the JTAG wires.
Your a very confusing man lol :rolleyes: what E79 you said it was E74 [1022] look if that nand you have is from the Jtag then fix it, use the repair nand in cools Jtag tool /Enter CPU Key/Click Repair Bad Nand /load the bad nand then load the clean nand you D/L / Make a save location for the Original new nand.....