JTAG Trying to save my broken jtag

darthmaul1309

Senior Member
Jan 22, 2007
105
16
California
Well, Ive been trying to save my broken Jtag for a while now. I'm new to all this, so I'm stumped. I managed to dump my Nand which had several errors. I then attempted to write a downloaded and repaired Nand, but that also had errors. I dont know what to do now?? Do you think the machine is salvageable? I DON'T have my CPU keys and I DON'T have my original dump as I bought it pre-jtagged. Is there anything I can do to save this machine?? Oh, I am getting e79 error. Thanks in advance....
 
Last edited:

srt4fun

Senior Member
Sep 8, 2011
133
0
California
Are any of the bad blocks at 000, 001, or 3DE? If not, then it's very possible to recover it.

What program are you using to repair it?
 

darthmaul1309

Senior Member
Jan 22, 2007
105
16
California
I was using Jtag tool to try and recover bad blocks...ummm Im not sure which blocks were bad, but there were ALOT! Ill look for those blocks next time I dump it. IF those blocks are still good, what should be my next step?? Oh, and it might be savable even though I don't have the CPU keys????
 
Last edited:

srt4fun

Senior Member
Sep 8, 2011
133
0
California
Read your NAND 3 times and compare them. If they don't all match then it's most likely your wiring. What are you using to read/write your NAND?

If they all match, Repair your NAND dump with JTAG Tool, create new Freeboot with fixed image, remap bad blocks, flash.

Also, which SMC points is your box using? Very important when building your Freeboot image.

Edit: Like Keil423 said, you will need the dump you made when it first broke down.
 
Last edited:

darthmaul1309

Senior Member
Jan 22, 2007
105
16
California
does it not boot xell at all anymore? did you save the dump you did right after it broke down on you?
No it doesnt boot into Xell (I was in Xell when I did something wrong to get it in its current state) and no I don't have a dump of the nand right afer it died. Unfortunately this happened about a year ago and I just took it as a loss, but now I've gotten a little deeper into this hobby and thought I might be able to fix it...
 

darthmaul1309

Senior Member
Jan 22, 2007
105
16
California
Read your NAND 3 times and compare them. If they don't all match then it's most likely your wiring. What are you using to read/write your NAND?

If they all match, Repair your NAND dump with JTAG Tool, create new Freeboot with fixed image, remap bad blocks, flash.

Also, which SMC points is your box using? Very important when building your Freeboot image.
I am using Jtag tool to read/write my nand..didnt dump it three times though to compare. I did try the repair function of Jtag tool without success. BUT I didnt create new Freeboot with the fixed image, remap bad blocks and flash. Is the remapping of the blocks automate?? Umm..excuse my noobness, but I don't know what SMC points are..could you elaborate..thanks for all the help..

---------- Post added at 23:29 ---------- Previous post was at 23:25 ----------

I take it that you have no way to ge ahold of whoever you got it from to get the OG nand back aigh?
No..I tried that, no luck. I'm not tripping to much if it cant be saved..I have another 360 that I'm going to do the reset glitch hack on, but it would be a nice success story to bring this one back to life!
 

keil423

VIP Member
Apr 4, 2011
1,954
88
South Dakota, USA
www.epicconsole.com
Well Mrtin will correct me if I'm wrong but I do believe that without being able to retrieve you cpu key your kinda up the brown creek.

I guessing you wrote a donor nand to to without injecting your cpu key into it. this mean that you wrote over your nand with either no key at all or the wrong key in the donor nand. if this is the case then yeah you have a door stop.
 

darthmaul1309

Senior Member
Jan 22, 2007
105
16
California
Well Mrtin will correct me if I'm wrong but I do believe that without being able to retrieve you cpu key your kinda up the brown creek.

I guessing you wrote a donor nand to to without injecting your cpu key into it. this mean that you wrote over your nand with either no key at all or the wrong key in the donor nand. if this is the case then yeah you have a door stop.
Yep thats exactly what I did! If nothing else its been a good learing experience...this was the first time I soldered QSB's and stuff..I've learned a lot over the past few weeks here. So if it is indeed a door stop I can at least take some knowledge away from this..
 

srt4fun

Senior Member
Sep 8, 2011
133
0
California
Totally forgot you didn't have the key. :facepalm: So creating a freeboot image would be worthless...

You could try flashing Xell/Xellous to get the key... If it's a Xenon then the only option for the SMC points would be "Original"(default). For Zephyr, Falcon, and Jasper: the options are Original, AUD_CLAMP, and AUD_CLAMP & DVD_TRAY. It's basically how the JTAG hack is wired.
 

darthmaul1309

Senior Member
Jan 22, 2007
105
16
California
Flash that nand back to it and try to boot xell again by turning it on with the Eject button
Ill give that a try and report back later...thx for the help

---------- Post added at 08:06 ---------- Previous post was at 08:04 ----------

Totally forgot you didn't have the key. :facepalm: So creating a freeboot image would be worthless...

You could try flashing Xell/Xellous to get the key... If it's a Xenon then the only option for the SMC points would be "Original"(default). For Zephyr, Falcon, and Jasper: the options are Original, AUD_CLAMP, and AUD_CLAMP & DVD_TRAY. It's basically how the JTAG hack is wired.
Its a falcon..ill look into those SMC points...thanks for the help and suggestions...
 

J2G

VIP Member
May 13, 2010
3,737
0
90°N
www.esl-communications.com
No CPU key no Xell to boot into to get the key to make a new working NAND you need the CPU key off the guy you got it from if you can.
You did a number on it buddy which sounds like its a door stop now give it to someone that knows his sh*t on Jtags he won't charge you to tell you it's retrievable or tell you bin it


Sent from my iPhone 4s using
Tapatalk.