Overview/Reality of the Method:
This method is not new, has been known and trusted since a long time. Basically, what we do is swap the KeyVault (or ‘KV’ in short. KV stores data like console certificates, per-box private keys, DVD keys, etc.) inside the NAND with the KV from an unbanned console. (While this is technically very different, you could somewhat compare it to swapping EEPROM data during the Xbox1 days.)
However there’s a Big ‘IF‘ in this method. You need the (unique) CPU key of your banned console – without it you can’t correctly write (or encrypt if you want) the new KV data in the NAND bin of your banned console.
How to get the CPU-key? Run XeLL it will give you that info. To run XeLL, you need to perform the JTAG hack (or the King Kong exploit, but that’s even more outdated) and if you got banned the last few weeks it means you updated to the latest dashboard/kernel (else you can’t get on LIVE). And that’s the problem. Microsoft patched the JTAG hack since kernel 849x (July 2009), so, no way to boot up XeLL (i.e. no realistic way for you to get the CPU-key atm) and thus no way to swap the KV data in your NAND image.
To add to the mess, there’s also added KV protection (hashing) on newer motherboards (Falcon+ ? and kernel 1888 won’t boot on those), but if you can’t even get your CPU-key it doesn’t matter much to do deeper into this problem.
The only way it would work is if you retrieved the CPU-key of your old banned 360 before you updated to anything over 849x. If you did that, you probably know about all of this and nothing written here is new.
Downgrading kernel is not an option either, older kernels won’t boot as both kernel and CB fuses were burned during the various updates MS performed, and you can’t bypass that without … your CPU-key. Or if you played on live in the last 3 months your out of luck. Also all the new wave 4 games have the update that will disable xell from working so your out of luck there as well.
Hope that explains the situation a bit, if all looks well, you can proceed with the method. (it’s not easy)
Before you Begin:
Make sure you have the following stuff handy with you:
- Your Xbox 360 (8955) live console & CPU key
- A 2nd Unbanned console
- NANDPro b + Flash cable
- Xell loader
- degraded
- 1888 fs
- Robinsod’s flashtool
Method:
Step 1. Use NANDPro and dump NAND from unbanned console. (Download)
Step 2. Flash Xell and use JTAG hack to obtain cpu key.
Step 3. Use flashtool to extract file system.
Step 4. Dump NAND from 8955 console.
Step 5. Use flashtool to patch nand dump with kv.bin from unbanned console.
Step 6. Save patched file (patched_kv.bin).
Step 7. Open degraded + 1888 fs.
Step 8. Create 1888 downgrader image (downgrader.bin) from your patched_kv.bin file.
Step 9. Flash downgrader.bin to 8955 console.
Step 10. Attach HDD + ethernet cable and boot console. Connect to live and update to 8955 dashboard.
Your console is now fully working and un-banned from LIVE. You will have to follow this procedure everytime you get banned.
The Fool proof way of doing this all is using Infectus method. This needs you to Buy a special Microchip, Costs around 45Euros.
For more Microsoft, Xbox 360, PS3, Gaming, Tech Guides and Tech News catch us on Twitter @taranfx
Note: A Newer, easier, fix is bing worked upon by 360Mods, We will publish that as son as it becomes available. So dont’ foregt to Subscribe us: Twitter updates, or RSS, join Facebook.