Shadowbooting
No edit summary |
m (→RGLoader) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Development kernels have an undocumented, internal feature called "shadow booting" which allows them to enter an alternate boot chain during the boot process. By placing a specially crafted file titled 'xboxromw2d.bin' on the root of the system's hard disk, on bootup the system will start, read this file, then reboot again, finally completing the boot sequence having loaded from the bootloaders from the file on disk. Effectively, shadowbooting allows you to run a NAND image without actually flashing the NAND.<ref>https://free60.org/System-Software/Shadowboot/</ref> | Development kernels have an undocumented, internal feature called "shadow booting" which allows them to enter an alternate boot chain during the boot process. By placing a specially crafted file titled 'xboxromw2d.bin' (or `xboxromtw2d.bin` for a Test Kit) on the root of the system's hard disk, on bootup the system will start, read this file, then reboot again, finally completing the boot sequence having loaded from the bootloaders from the file on disk. Effectively, shadowbooting allows you to run a NAND image without actually flashing the NAND.<ref>https://free60.org/System-Software/Shadowboot/</ref> | ||
This is especially useful on a zero-fuse console, as you can flash XDKBuild to it, then shadowboot into other images. This preserves the fuses, while allowing you to use it as a devkit (with XDKBuild) or as a retail console (by shadowbooting into a retail kernel). Furthermore, there are no version restrictions placed on shadowbooted images, so you are free to shadowboot into any dashboard version. | This is especially useful on a zero-fuse console, as you can flash XDKBuild to it, then shadowboot into other images. This preserves the fuses, while allowing you to use it as a devkit (with XDKBuild) or as a retail console (by shadowbooting into a retail kernel). Furthermore, there are no version restrictions placed on shadowbooted images, so you are free to shadowboot into any dashboard version. | ||
{{Warning|Ensure that you have a transfer cable on hand in case the shadowboot file does not properly boot, as you will be unable to boot with the hard drive plugged in.}} | |||
== Pre-made Images == | == Pre-made Images == | ||
| Line 11: | Line 13: | ||
=== Development === | === Development === | ||
* [[:Media:Proto-xdk-shadowboot.zip|Proto for XDKs]] | ==== Proto ==== | ||
* [[:Media:Xdkbuild_proto_shadowboot-zerofuse.zip|Proto for zero-fuse consoles running XDKBuild]] | Images for booting Proto stealth server. Make sure to place Proto.xex and Proto.ini on HDD root as well as KV.bin (decrypted or encrypted KV works) and cpukey.txt (containing your CPU key). | ||
* [[:Media:Proto_UNOFFICIAL_Shadowboot_Collection-Byrom.zip|Proto for 16MB, Big Block, and XDKs]] - Created by Byrom | |||
* [[:Media:Proto-xdk-shadowboot.zip|Proto for XDKs]] - Created by Diamond and Byrom - This maybe should be deleted if it's already covered by the collection | |||
* [[:Media:Xdkbuild_proto_shadowboot-zerofuse.zip|Proto for zero-fuse consoles running XDKBuild]] - Created by Diamond and Byrom | |||
==== RGLoader ==== | |||
Images for booting RGLoader on a real devkit. Copy all contents to root of hard drive. | |||
* [[:Media:RGLoader_For_XDK_Shadowboot.rar|RGLoader for XDKs]] - Created by JustAnyone | |||
== Pre-made Images for Test Kits == | |||
None yet! | |||
== References == | == References == | ||
Latest revision as of 04:54, 31 March 2025
Development kernels have an undocumented, internal feature called "shadow booting" which allows them to enter an alternate boot chain during the boot process. By placing a specially crafted file titled 'xboxromw2d.bin' (or xboxromtw2d.bin for a Test Kit) on the root of the system's hard disk, on bootup the system will start, read this file, then reboot again, finally completing the boot sequence having loaded from the bootloaders from the file on disk. Effectively, shadowbooting allows you to run a NAND image without actually flashing the NAND.[1]
This is especially useful on a zero-fuse console, as you can flash XDKBuild to it, then shadowboot into other images. This preserves the fuses, while allowing you to use it as a devkit (with XDKBuild) or as a retail console (by shadowbooting into a retail kernel). Furthermore, there are no version restrictions placed on shadowbooted images, so you are free to shadowboot into any dashboard version.
 | Ensure that you have a transfer cable on hand in case the shadowboot file does not properly boot, as you will be unable to boot with the hard drive plugged in. |
Pre-made Images
Retail
None yet!
Development
Proto
Images for booting Proto stealth server. Make sure to place Proto.xex and Proto.ini on HDD root as well as KV.bin (decrypted or encrypted KV works) and cpukey.txt (containing your CPU key).
- Proto for 16MB, Big Block, and XDKs - Created by Byrom
- Proto for XDKs - Created by Diamond and Byrom - This maybe should be deleted if it's already covered by the collection
- Proto for zero-fuse consoles running XDKBuild - Created by Diamond and Byrom
RGLoader
Images for booting RGLoader on a real devkit. Copy all contents to root of hard drive.
- RGLoader for XDKs - Created by JustAnyone
Pre-made Images for Test Kits
None yet!