Protect your investment :-p

If you own a XDK make sure you dump the flash chip... the jtag points are the same you just need to do it from the bottom. atleast if you ever bork it with a bad recovery or something just flash backup and your good to go. This will fix E74 if you push Y on recoveries as well as E79.

 

This I know. I tried to explain this to some hard headed people the other night but they all called me an idiot as usual >_> by chance does an xex exist to allow a dump of your nand without soldering? I would do this but I don't know the layout that well of the bottom board.

 

you can use the loader (the one by xorloser) and just ftp it, or the kingkong exploit with a 45XX kernle, but if u can solder, i would just jtag it + i think u need the cpu key anyway for the loader ftp method.

but yea, thats actualy a cool idea, and if u can get a full nand dump,you could try and reboot into it on a retail. and sondow u like trying to convert retail to dev, why not give it a try?

 

Erm you can just drag the contents out with Neighborhood but ftp won't do it you need to Transfer the .bin image. As for the kingkong that won't work with the newest kernel. Also really Copying one nand to another won't convert a retail this is for backing up your XeDK. I have my XeDK but no method to back it up without opening and as far as I know there is no daiagram for the underside jtag.

 

Go ahead and try recovering to the 45xx kernel on some newer kits and see what happens .

Fun stuff.

-Doom

 

What are you talking about, reading the NAND or the JTAG hack? Why would you wire up JTAG if you're only gonna dump the NAND? And why back it up at all, I thought the recoveries were for... recovering? Don't recovery discs overwrite the NAND (except, I'd guess, kv and config)? Please elaborate, I luckily didn't run into troubles that required a NAND backup so far.
Why would you need to solder to the bottom, aren't J1D2 and J2B1 through-holes on XeDKs like on retails, meaning the connection is available on top and bottom?
I don't think this should become standard procedure for XeDK owners since NANDPro/your wiring/your flashing hardware/flux or solder residue/bad luck can cause problems, the 3 dead 360s on my desk can tell a story about that (but luckily I got good dumps for all of them first, phew).
So, beware.

 

If some recover goes wrong, you can't recover again. XDK is broken then.

 

i said 45XX for kk exploit, and i didnt mean it in that way, i meant its not far fetched to believe its possible to reboot into a dev kernel whilst emulating the correct fuses, at least according to the freboot poeple. (if it sounds like im arguing im not so nothing personal, just dont want to be taken the wrong way )
weather or not thats a good idea can be debated...

But w/e thats not the topic.... if your just looking to back it up, downgrade to 45XX with the recovery im sure someone here will spare you. then just do the kk exploit just like you would on the retail.

oh and happy 2010 wooooooooooooooo
only 2 years left (kidding)

 

the FS is useless... i was doing some experimenting with my own kit (had everything backed up like cpukey nand etc etc) so i ran the recovery and pushed Y cause im curious like that lol and long behold it E74 on me. i soldered in jtag and reflashed it gave me E79 (since my dump was ECCless) using +W on nandpro. that gave me just enough to shadowboot the XDK recovery disc and recover sondow i got a way to dump via XDK but its eccless maybe u can fix the code and add ecc?

 

btw im not sure and DONT quote me on this but isnt the KK shader for debug internal?

 

I know a few people who can assist you in that fix, however I am a low end coder at best, My main talants are debugging providing solutions and modifying existing code but as for writing brand new code for something like that I don't think I would be much use but luckily I have a few friends whom are trustworthy whom wouldn't have a problem assisting you and they have dev's as well as I.

Also tyler man don't tell people to downgrade because then that will cause more problems then the solution we are looking for, doing so to my knowlege is a bunny hop and that is dangerous if you don't baby step and doing so in reverse on newer kits may kill them. I know it wasn't your intent but KK right now may soon get replaced with an executeable xell so I hope. Also yes those are through holes so it should work on bottom and top, not sure why it wouldn't, question is though, are we speaking of just a jtag or a LPT method and if so are the solder points different and will it still work despite the fuses being different and not to mention the factor of the new recovery ie 8x^ having latest kernel, isn't jtag patched? I would assume Jtag has been fixed with newer kernel just like retail, correct me if I am wrong.

 

umn you CAN use LPT with nandpro actually "nandpro lpt: -r64 orig.bin" the points ARE the same you just need to do it from the bottom due to sidecar headers

 

Sidecar headers in the way? I see. Also I was not debating rather or not Nandpro with LPT was the problem I was curious as to if JTAG was fixed on the latest recovery since it has the latest kernel and microsoft may be applying the same fix to devs as they are on retails. Can you confirm this is working on 8^ dev kernel?

 

do you mean as far as getting cpukey and whatnot from 9xxx kernel? because i personally have a xenon XDK so i got mine via 4xxx kernel and KK hack.

 

also to clear any confusion there maybe i didnt use any of the resistor points needed for retail systems

 

Can you confirm using JTAG+LPT on a XeDK with a 8498.0 flash with Read/Write capabilities to the XeDK NAND?

 

i really don't understand how bunny hopping is bad, ive gone from 4x to 9x on about 4 kits and never had a problem, i really think its just speculation

wait you said newer kits, yea you cant downgrade that low on newer hdmi kits, so your right.... but it works fine on xenons.

and the jtag i think was fixed in the 9x not the 8x but i could be wrong.

 

the jtag cable works fine on all units from xenon to jasper yeah of course xell itsself doesnt work. but reading and writing to the nand via jtag very much works i made a backup of my 4xxx image and 9xxx image. and since the XDK does not blow efuses you can flash any image (although be warned USE USB SPI! it took me like 3 and a half hours to dump and another to write)

 

I don't what your talking about xell but now that I know JTAG still works I will do this tomorrow to secure my XeDK incase of bad recovery thanks for the tip. Also would be helpful if you posted a pic of the bottom of the XeDK with a diagram attached.

Also tyler 8x is the flash 9x is XDK related we were speaking about the flash which is =/= to the retail version.

 

Guys, don't confuse JTAG hack with the SPI stuff for reading/writing the NAND.

They're two different things.

While I don't think the JTAG hack would function on a devkit at all (at least on the state it is to run on retails) it could be possible to make a devkit specific image for just obtaining the CPU key. But then since you can downgrade it, the KK exploit sounds fairer/easier to pull off.

Now about the SPI, since the devkit has the same southbridge as a retail, I see no reason for it to not work. Just rig it up and dump the damned flash !
Even the soldering points are the same.

:shrug: