xboxscene.org forums

Xbox360 Forums => Xbox 360 Hacking Forums => General Technical Hacking Discussion => Topic started by: digipimp75 on March 22, 2011, 11:20:00 AM

Title: Jtag Points Db1f1/ft1u2 Lifted
Post by: digipimp75 on March 22, 2011, 11:20:00 AM
Hey all, ok here it is:

My friend gave me a Falcon box with an exploitable cb.   He tried to jtag it but lifted DB1F1/FT1U2 pads lol. I dumped the nand 5x, flashed xell, got cpu key, built fb image and flashed back.  For the jtag wiring I used boxddr aud_clamp wiring with resistors, and since those other pads were lifted I used the point under the southbridge.   All was well, and it booted to 12625 dash beautifully!   I booted it about 10-12 times, and it came up clean.. NO issues whatsoever. Note: This was my first attempt at a Falcon board, and have done quite a few Xenons (very easy smile.gif).  So I was pretty proud of myself.

Now it was time to add efuse protection.  I bridged UT61 and went to boot again.. E79.  CRAP!  Thinking something came loose, I checked all wiring.. seemed solid except for one loose one.  Redid all the points, nothing.  While screwing around trying to resolder the alt point under the southbridge, I lifted the frigging pad!!

So, are there ANY other options here?  Now we have 3 destroyed pads, and the thing that pisses me off the most is that it WAS WORKING, if only for a brief happy time.   I'd like to just start all over.. fresh transistors and resistors, since these look ragged now having been moved all around.  (At first they were professional looking).  

Should I just call it a wash, flash the orig nand back, update it to the newest dash and reflect on what could have been?  I heard of some folks scraping the trace next to one of these points and soldering the wire directly to it, but I'm not so sure about that.  If it's the only option though, I guess I'll try.    Any tips?  Sorry for the long post
Title: Jtag Points Db1f1/ft1u2 Lifted
Post by: digipimp75 on March 22, 2011, 06:50:00 PM
Thanks man, I'll give that a try.  I created the image based on aud_clamp wiring and, when it worked, it was soldered to the alt point under the southbridge.   So I should use a trace next to that pad?  or use db1f1?  or does it matter?  smile.gif   I imagine that as long as the aud_clamp wiring is used, this should work
Title: Jtag Points Db1f1/ft1u2 Lifted
Post by: digipimp75 on March 22, 2011, 10:22:00 PM
SUCCESS!!  smile.gif  Thanks dennisv9.    I did end up using the trace under the southbridge.  Scraped a little film away, cleaned it up with alcohol, tinned the trace and the wire, got a nice little connection and voila!  Booting like a champ again.  This actually wasn't as hard as I thought it would be.

For anybody out there who lifted pads on the points and thought the box was trashed, don't fret..  there's hope!  Don't throw in the towel just yet wink.gif
Title: Jtag Points Db1f1/ft1u2 Lifted
Post by: juggahax0r on March 22, 2011, 10:44:00 PM
QUOTE(digipimp75 @ Mar 23 2011, 12:22 AM) View Post

SUCCESS!!  smile.gif  Thanks dennisv9.    I did end up using the trace under the southbridge.  Scraped a little film away, cleaned it up with alcohol, tinned the trace and the wire, got a nice little connection and voila!  Booting like a champ again.  This actually wasn't as hard as I thought it would be.

For anybody out there who lifted pads on the points and thought the box was trashed, don't fret..  there's hope!  Don't throw in the towel just yet wink.gif


 Actually you can just use SMC_i/o tool to change the location of the points. The most common changes are moving Argon Data to Aud_Clamp and Db1F1/FTu21 (or whatever) too DVD_Tray Open. You can also swap those and do them the other way around. And with the newest version of the tool you can change it to any known  GPIO pin you can find or know of.

 But it sounds like you got it fixed none the less . But if you want a nice solid point and a fix for random e79 errors on HDMI go with the SMC io fix.
Title: Jtag Points Db1f1/ft1u2 Lifted
Post by: digipimp75 on March 23, 2011, 09:56:00 AM
Now ya tell me!  lol jk.  Thanks for the tip,  man.  Yeah I'd heard of that tool but never researched it's purpose.  I'll definitely keep that in mind should I ever run into this situation again.