JTAG Need some info E72

Status
Not open for further replies.

C43Mi57

VIP Member
Jan 22, 2011
293
0
Canada
Okay i just bought a falcon for 25 bucks was more intrested in the RF and case...anyways turned it on, its gives e72 error... opened it up looked like someone tried to reverse a jtag..

E72 Description
"This error is related to a loose pin or a not existent NAND chip, can also happen if you flashed it badly with an Infectus chip and/or the NAND is dead....
According to XBH: Error within Xam"

I do not have original nand..

Can anything be done?
willing to try anything not to concerned if this console lives or dies.
 

C43Mi57

VIP Member
Jan 22, 2011
293
0
Canada
so i took it out of the steel casing and looks like they used an alternate method. I can get Xellto boot by hitting the eject button.

used a few tutorials not sure if its okay but i redid a nand from another jtagged falcon changed the cpu key and dvd drive info tried to flash it with usb stick in xell no go.

the nand points look pretty beat up not sure if i will be able to connect my nand x to it... just waiting on nand x wires and stuff from xconsoles should be here tomorrow hopefully.

if anyone has any experience with this fell free to stop me if you read anything that may cause more headaches it would be very much appreciated...

i am new to this and would like to learn how to troubleshoot it, even if this means the death of the console.

I am starting to think it may of been a update gone wrong.
 

C43Mi57

VIP Member
Jan 22, 2011
293
0
Canada
So just a quick update... console has ALT SmC AUD_CLAMPS & DVD_TRAY .. i Managed to install pin headers yesterday.. NAND-X good to go... i dumped the XBR/freeboot nand.. and have a little more info now about the console... Still E72.. not sure what steps i should take.
 

C43Mi57

VIP Member
Jan 22, 2011
293
0
Canada
last update i got console up and running had used a donor nand and kv reflashed it with nand x everything is working fine..
 

C43Mi57

VIP Member
Jan 22, 2011
293
0
Canada
okay i hope this helps someone that has issues with a bad flash.

after i got it to boot i had issues, something to do with the KV i used.

i finally got console to run...basically what happened my first attempt with this console was, i wrote a freeboot image that had something going on with the KV would boot the console fine but no DVD drive information or anything in XELL...also KV error in Xell when booted into it.

So last night i spent about 3 hours trying to create a new nand to flash the console and in the process i had black screen, xmas lights, i think every possible error on a jtag.. i thought i was in over my head, I had about a thousand different programs d/l'd to....

This morning with my head cleared i was like this has to be just a bad flash and should be easier than i am making it.. so basically these are the things i used and the steps i took..

Things you need
Cpu Key
Donor retail nand
360 flash tool
Jtag tool
Hardware
Nand-x


Step1: Before i did anything i dumped the bad flash nand from the console using NAND-X with pin headers installed.

Step 2 :Extract KV from none booting jtag with 360 flash tool(the nand you just dumped)

Step 3 :Find a retail nand from the same console type

Step 4:Import your extracted KV (from Step 2) into the retail nand (from step 3)

Step 5:patch with OSIG and Key (whatever drive you want)

Step 6:create freeboot image from you new retail nand with jtag tool

Step 7: write to console with NAND_X

after 5 minutes of creating the image with 360 Flash Tool and then used jtag tool to create freeboot

It worked lol wtf
I figured i wasted enough time on it that someone else with the same issue shouldn't have to.
I spent alot of time looking for tutorials most of them were for consoles that booted (which mine didn't)

If you see anything that needs to be corrected or is just plain wrong feel free to leave your opinion i just posting it cause it worked for me and this is only my second JTAG console i have worked on. so yes i am a N00b to the whole JTAG thing.
 
Last edited:
Status
Not open for further replies.