Xbox 360:Dumping your NAND and CPU Key: Difference between revisions
Jump to navigation
Jump to search
m (Removed the extra spaces) |
(Removed mediafire links) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category: | [[Category:Xbox 360]] | ||
This guide will walk you through dumping your console's NAND and obtaining it's CPU Key. These come in handy when updating your system software and | This guide will walk you through dumping your console's NAND and obtaining it's CPU Key. These come in handy when updating your system software and | ||
can also help you recover you from a possible brick. | can also help you recover you from a possible brick. | ||
The methods listed in this guide require a working modified console that can run homebrew programs. If you need to dump the NAND of a retail or bricked console, you need to follow the corresponding guides for a [[Xbox 360:4GB NAND|4 GB Corona/Waitsburg/Stingray NAND]] or [[Xbox 360:Standard NAND|all other NAND types]]. | |||
==Using XeLL== | ==Using XeLL== | ||
By default, if you boot XeLL with an ethernet cable is plugged in, it will either pull an IP from your router via DHCP or it will use the default IP of `192.168.1.99` if you are not connected to a router. You must unplug any wireless USB adapters if you have them plugged in, as it will halt the boot process. By entering the IP address shown toward the bottom of XeLL on a web browser, it should pull up a XeLL Reloaded web page. The following are displayed: | By default, if you boot XeLL with an ethernet cable is plugged in, it will either pull an IP from your router via DHCP or it will use the default IP of `192.168.1.99` if you are not connected to a router. You must unplug any wireless USB adapters if you have them plugged in, as it will halt the boot process. By entering the IP address shown toward the bottom of XeLL on a web browser, it should pull up a XeLL Reloaded web page. The following are displayed: | ||
| Line 17: | Line 19: | ||
==Using Simple 360 NAND Flasher 1.4b== | ==Using Simple 360 NAND Flasher 1.4b== | ||
# Download and launch [[File:Simple 360 NAND Flasher.7z]] ([https://github.com/Swizzy/XDK_Projects/tree/master/Simple%20360%20NAND%20Flasher source]) on your console. | |||
# Download and launch [ | |||
# Press X to dump NAND. If everything went fine, you should get message saying "NAND Dumped!". Press any button to exit. | # Press X to dump NAND. If everything went fine, you should get message saying "NAND Dumped!". Press any button to exit. | ||
# There should now be a file called "flashdmp.bin" in the Simple 360 NAND Flasher directory. Copy this file to your PC. | # There should now be a file called "flashdmp.bin" in the Simple 360 NAND Flasher directory. Copy this file to your PC. | ||
# Download and run [ | # Download and run [[:File:X360_NAND_Dump_Checker_GUI_v1.0.rar|X360 NAND Dump Checker]]. Press "check NAND" and select the flashdmp.bin file. If the NAND is fine, then you should see a message saying "NAND Verified as OK!". As long as the verification is OK, then bad blocks do not matter. If bad blocks are causing verification to fail, you should go back to step 1 and try to dump NAND again. | ||
# | # Your CPU key will be automatically saved into "cpukey.txt" file along with the NAND dump, which is "flashdmp.bin". | ||
# Store flashdmp.bin to a safe location, preferably outside of your PC (to a cloud, external media, etc). | |||
# | |||
Latest revision as of 21:04, 21 September 2024
This guide will walk you through dumping your console's NAND and obtaining it's CPU Key. These come in handy when updating your system software and can also help you recover you from a possible brick.
The methods listed in this guide require a working modified console that can run homebrew programs. If you need to dump the NAND of a retail or bricked console, you need to follow the corresponding guides for a 4 GB Corona/Waitsburg/Stingray NAND or all other NAND types.
Using XeLL
By default, if you boot XeLL with an ethernet cable is plugged in, it will either pull an IP from your router via DHCP or it will use the default IP of 192.168.1.99 if you are not connected to a router. You must unplug any wireless USB adapters if you have them plugged in, as it will halt the boot process. By entering the IP address shown toward the bottom of XeLL on a web browser, it should pull up a XeLL Reloaded web page. The following are displayed:
- CPU Key
- DVD Key
- Raw Flash (download): This will download a dump of your flash chip straight to the device you are using.
- Key Vault: This will download a decrypted keyvault file straight to the device you are using.
- Fuses: This will download a file listing the status of your CPU fuses straight to the device you are using.
- Startup Log: This will display a text file of all the events that have been printed to the screen since boot, some of which you can't normally see.
- Shutdown
- Reboot
A video demonstration of using XeLL to dump and flash a NAND can be found on MrMario2011's channel.
Using Simple 360 NAND Flasher 1.4b
- Download and launch File:Simple 360 NAND Flasher.7z (source) on your console.
- Press X to dump NAND. If everything went fine, you should get message saying "NAND Dumped!". Press any button to exit.
- There should now be a file called "flashdmp.bin" in the Simple 360 NAND Flasher directory. Copy this file to your PC.
- Download and run X360 NAND Dump Checker. Press "check NAND" and select the flashdmp.bin file. If the NAND is fine, then you should see a message saying "NAND Verified as OK!". As long as the verification is OK, then bad blocks do not matter. If bad blocks are causing verification to fail, you should go back to step 1 and try to dump NAND again.
- Your CPU key will be automatically saved into "cpukey.txt" file along with the NAND dump, which is "flashdmp.bin".
- Store flashdmp.bin to a safe location, preferably outside of your PC (to a cloud, external media, etc).