So a while ago I bricked my xdk, I have the nand backed up and so I opened the kit up. I modified the nandx wires to work with the xdk and was able to flash the nand and get it to work again. Unfortunately it only boots once out of 5 boots. I think this is because I flashed it as a big block jasper (I had to since the nand was 500mb and no other console has that big of a nand). So is there any way that I can flash it as a 1gb trinity slim xdk and not a big block jasper? Thanks!
As far as I know, that should have totally rendered the kit useless and not even able to be powered on, let alone give an RROD error. Any of us could have pulled a trinity nand for you.
Could flashing another XDK Trinity NAND over to the console help? Maybe trying to flash one over and then run an ISO recovery to attempt to wipe out everything.
It doesn't. If the nand is borked, it'll take some time to fix. I did this exact same thing like six or so years ago when all you could find in the wild were trinity stress kits, at like $600 plus at the time. I borked mine by dropping the recovery too low by accident (unmarked ISO recovery). It killed the kit. I flashed the nand with a Jasper one thinking it'd work. It did not. I wound up messing with JRunner and a Nand X connected to the stress cables, a Donor trinity xdk nand and prayer. A lot of fecking praying.
He has a backup of his nand but I can't help him without telling me how big his nand is? Could be 64MB or 512mb I need to know so I can tell you what to do step by step. @BlastsMods
If you don't already have J-Runner download, Download it then make sure your NAND-X, JR-Programmer or what ever your using shows up. 1> Click on Advanced at the top and then Custom NAND/CR Functions 2> Under Command Click Erase 3> Under Size click 512 4> Click RUN this will erase the NAND that you wrote as a Jasper NAND. (ONCE ITS DONE MOVE ON TO STEP 5) 5>Back Under Command change it from erase, and click write 6> Under filename click on the little box with three dots/periods (...) 7> Navigate to where your backup NAND is at click on it and it should open it 8> Click run it will then write the NAND once its done unplug everything from the PC 9> TEST THE XDK SHOULD BE WORKING AFTER STEP 8 @BlastsMods
Just finished doing it and it now just red rings when booting up, it powers on but no signal. Here's the output of J-runner: Version: 01 Flash Config: 0x00AA3020 Erasing Nand Error: 202 erasing block 78 Error: 202 erasing block 10D8 Error: 202 erasing block 2818 Error: 202 erasing block 30B8 Error: 202 erasing block 3E98 Error: 202 erasing block 7108 Done! in 0:30 min:sec Version: 01 Flash Config: 0x00AA3020 Writing Nand updflash.bin Error: 202 writing block 78 Error: 202 writing block 10D8 Error: 202 writing block 2818 Error: 202 writing block 30B8 Error: 202 writing block 3E98 Failed to write 0x6B12 block Error: 202 writing block 7108 Done! in 189:30 min:sec
Now that I think of it dude where the hell did you get 512mb the nand. Should show up on your computer as 64MB. Trinity's have the extra 4GB space on a chip has nothing to do with nand. Can you upload the nand or check it.
So I flashed it as a trinity (16mb) and it now boots fine, not too sure how that worked but I guess it works lmao
Oh, when I dumped the nand with flash360, it dumped 540mb. I uploaded my nand here: https://mega.nz/#!0w8zlKDa!hyyrmfS_WZasz9ZKCFHm_kR4jlEqWTIfaQ3BVLZr1r8