Xbox 360:Dumping your NAND and CPU Key: Difference between revisions

From ConsoleMods Wiki
Jump to navigation Jump to search
m (Removed the extra spaces)
No edit summary
Line 16: Line 16:
A video demonstration of using XeLL to dump and flash a NAND can be found on [https://youtu.be/4iKCG6N1FzA?list=PL1CadovfabPskGb2Ur4kBGzD5s7DzQw5I MrMario2011's channel].
A video demonstration of using XeLL to dump and flash a NAND can be found on [https://youtu.be/4iKCG6N1FzA?list=PL1CadovfabPskGb2Ur4kBGzD5s7DzQw5I MrMario2011's channel].
==Using Simple 360 NAND Flasher 1.4b==
==Using Simple 360 NAND Flasher 1.4b==
===Dumping the NAND===


# Download and launch [https://www.mediafire.com/file/vu0vk5evpl662du/Simple_360_NAND_Flasher_v1.4b_BETA.rar/file Simple 360 NAND Flasher 1.4b] ([https://github.com/Swizzy/XDK_Projects/tree/master/Simple%20360%20NAND%20Flasher source]) on your console.
# Download and launch [https://www.mediafire.com/file/vu0vk5evpl662du/Simple_360_NAND_Flasher_v1.4b_BETA.rar/file Simple 360 NAND Flasher 1.4b] ([https://github.com/Swizzy/XDK_Projects/tree/master/Simple%20360%20NAND%20Flasher source]) on your console.
Line 24: Line 22:
# Download and run [https://www.mediafire.com/file/9n6o0mqbgm00htq/x360_NAND_Dump_Checker_GUI_v1.0.rar/file 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.
# Download and run [https://www.mediafire.com/file/9n6o0mqbgm00htq/x360_NAND_Dump_Checker_GUI_v1.0.rar/file 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.
# Store flashdmp.bin to a safe location, preferably outside of your PC (to a cloud, external media, etc). Keep a copy on hand if you wish to obtain your CPU key with the steps below.
# Store flashdmp.bin to a safe location, preferably outside of your PC (to a cloud, external media, etc). Keep a copy on hand if you wish to obtain your CPU key with the steps below.
# Simple 360 NAND Flasher 1.4b will automatically save your CPU key into "cpukey.txt" file along with the NAND.
# Your CPU key will be automatically saved into "cpukey.txt" file along with the NAND.
 
===Alternative method for obtaining the CPU Key===
# Download and launch the latest [https://www.mediafire.com/file/df63pfduf55p93a/xeBuild_GUI_2.099.rar/file xeBuild GUI] (v2.099 unofficial) on your PC.
# Click "Open" and for the "Source File", select your NAND backup (flashdmp.bin).
# If you know your Xbox 360's IP address type it into "IP to Xell" box and click "Get CPUKey/CFLDV from Network". The CPU Key should be displayed in its text box.
#* If you do not know your Xbox 360's IP, you can boot your Xbox 360 into XeLL (by pressing the eject button to start the console by default) and go to Tools → "Scan for Xell" and press "Start scanning for Xell". If your Xbox 360 is in same network, it will be detected and the CPU Key will be displayed in main window.
# Check "Keyvault Information" in bottom-right corner and verify that information given is OK. If something seems weird, you could always try again.
# xeBuild should have generated a "FUSE.txt" file to same directory containing your flashdmp.bin file. Store this file to a safe location, preferably outside of your PC (to a cloud, external media, etc).

Revision as of 10:27, 6 January 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.

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

  1. Download and launch Simple 360 NAND Flasher 1.4b (source) on your console.
  2. Press X to dump NAND. If everything went fine, you should get message saying "NAND Dumped!". Press any button to exit.
  3. There should now be a file called "flashdmp.bin" in the Simple 360 NAND Flasher directory. Copy this file to your PC.
  4. 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.
  5. Store flashdmp.bin to a safe location, preferably outside of your PC (to a cloud, external media, etc). Keep a copy on hand if you wish to obtain your CPU key with the steps below.
  6. Your CPU key will be automatically saved into "cpukey.txt" file along with the NAND.
Retrieved from "https://consolemods.org/wiki/index.php?title=Xbox_360:Dumping_your_NAND_and_CPU_Key&oldid=38440"