DeviceID Exosphere Builder Switch: Difference between revisions

From GameBrew
(Created page with "{{Infobox Switch Homebrews |title=DeviceID Exosphere Builder |image=deviceidexospherebuilderswitch.png |description=Create a custom Exosphere binary to spoof the DeviceId |author=PabloZaiden |lastupdated=2021/02/28 |type=PC Utilities |version=0.18.1 |license=Mixed |download=https://dlhb.gamebrew.org/switchhomebrews/deviceidexospherebuilderswitch.7z |website=https://github.com/PabloZaiden/deviceid-exosphere-builder |source=https://github.com/PabloZaiden/deviceid-exosphere...")
 
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Infobox Switch Homebrews
{{Infobox Switch Homebrews
|title=DeviceID Exosphere Builder
|title=DeviceID Exosphere Builder
|image=deviceidexospherebuilderswitch.png
|image=deviceidexospherebuildernx.png
|description=Create a custom Exosphere binary to spoof the DeviceId
|description=Create a custom Exosphere binary to spoof the DeviceId.
|author=PabloZaiden
|author=PabloZaiden
|lastupdated=2021/02/28
|lastupdated=2021/02/28
Line 8: Line 8:
|version=0.18.1
|version=0.18.1
|license=Mixed
|license=Mixed
|download=https://dlhb.gamebrew.org/switchhomebrews/deviceidexospherebuilderswitch.7z
|download=https://dlhb.gamebrew.org/switchhomebrews/deviceidexospherebuildernx.7z
|website=https://github.com/PabloZaiden/deviceid-exosphere-builder
|website=https://github.com/PabloZaiden/deviceid-exosphere-builder
|source=https://github.com/PabloZaiden/deviceid-exosphere-builder
|source=https://github.com/PabloZaiden/deviceid-exosphere-builder
|donation=  
|donation=  
}}
}}
{{#seo:
Dockerized tool to build a custom Exosphere binary that spoofs the DeviceID.  
|title=Switch Homebrew PC Tools (PC Utilities) - GameBrew
|title_mode=append
|image=deviceidexospherebuilderswitch.png
|image_alt=DeviceID Exosphere Builder
}}
DeviceID Exosphere Builder, a tool that Dockerized to construct a personalized Exosphere binary capable of spoofing DeviceID. This tool can enable booting Horizon with Atmosphere on a Nintendo Switch that has PRODINFO/PRODINFOF partitions transplanted.
 
==How to transplant PRODINFO/PRODINFOF and recreate the other EMMC partitions from scratch==
=== WARNING ===
'''This procedure is only meant to be able to boot the console back into Horizon, after losing the contents of <code>PRODINFO</code>/<code>PRODINFOF</code> partitions. THIS IS NOT MEANT TO UNBAN YOUR CONSOLE. If you try doing that, the most likely outcome is that you will end up with another banned console. Avoid any kind of piracy from now on and DON'T USE the transplanted console online'''
 
=== Requirements ===
* Windows
* A working console full EMMC backup (''Console A''), or that console running latest Hekate, connected to the PC
* A console with working hardware, but without a working EMMC backup (''Console B'')
* [https://github.com/eliboa/NxNandManager NxNandManager]
* [https://files.sshnuke.net/HacDiskMount1055.zip HackDiskMount]
* BIS keys for Console A and B
* Docker
* Latest [https://github.com/CTCaer/hekate/releases Hekate]
* Latest [https://github.com/Atmosphere-NX/Atmosphere/releases/ Atmosphere]
 
=== Steps ===
# Open the EMMC from ''Console A'' or its backup with NxNandManager, using ''Console A'' BIS keys.
# Write down the ''DeviceID'', without the initial <code>NX</code> and the <code>-0</code> (or whatever there is) at the end, skipping the first two digits. For instance, if it says: <code>NX1122334455667788-0</code>, the part you need to write down would be: <code>22334455667788</code>.
# Dump and decrypt <code>PRODINFO</code> and <code>PRODINFOF</code> partitions from ''Console A''.
# Close NxNandManager.
# Open the EMMC from ''Console B'' with NxNandManager, using ''Console B'' BIS keys. It may say that it has ''BAD CRYPTO''. This is expected on a nuked EMMC.
# Restore the decrypted <code>PRODINFO</code> and <code>PRODINFO</code> partitions from Console A into Console B.
# Close NxNandManager.
# Follow [https://switch.homebrew.guide/usingcfw/manualchoiupgrade.html this guide] to recreate the rest of the EMMC partitions, <code>BOOT0</code> and <code>BOOT1</code> on ''Console B'' using ''Console B'' BIS keys, '''UP TO AND INCLUDING, STEP 12. DO NOT ATTEMPT TO BOOT THE CONSOLE YET'''.
# On the <code>SYSTEM</code> partition, delete all the files/folders of the <code>save</code> folder '''except the one ending in <code>120</code>'''. Not doing this may end up in the console freezing during boot or Atmosphere showing an error while booting.
# Put the latest version of Hekate and Atmosphere on your SD card.
# Create the custom Exosphere binary to spoof the DeviceID.
# Boot the console using <code>fusee-primary.bin</code> or chainload it from Hekate.
 
== How to create the custom Exosphere binary with Docker ==
This tool requires a volume mounted to the <code>/output</code> directory of the container, and the <code>DEVICEID</code> environment variable, with the DeviceID to spoof.
 
Either build the docker image locally or use the prebuilt image from Dockerhub, replacing the <code>DEVICEID</code> value with your DeviceID (keep the <code>00</code> before your DeviceID. If the output from NxNandManager was <code>NX1122334455667788-0</code>, the value to use should be: <code>0x0022334455667788</code>. ):
 
(if you want to use a specific Atmosphere version, change the <code>latest</code> docker tag with the Atmosphere version number, like <code>0.14.4</code>)
 
<pre>mkdir -p ./output
docker pull pablozaiden/deviceid-exosphere-builder:latest
docker run -ti --rm -e DEVICEID=0x0022334455667788 -v &quot;$PWD&quot;/output:/output pablozaiden/deviceid-exosphere-builder:latest</pre>
 
After it finishes building, copy the <code>output/deviceid_exosphere.bin</code> file to the <code>Atmosphere</code> directory of your SD card, and add the following entries to <code>BCT.ini</code>:
 
<pre>[stage2]
exosphere = Atmosphere/deviceid_exosphere.bin</pre>
 
If booting via Hekate (without <code>fusee-primary.bin</code>), add this to the boot configuration to pick up the custom exosphere binary:
 
<pre>secmon=Atmosphere/deviceid_exosphere.bin</pre>
 
== How to create the custom Exosphere binary without Docker ==
To build the same Exosphere custom binary without using the Docker image, you have to do the following manual steps first (for more details, just follow what is being done in the Dockerfile):
 
<ul>
<li>Install DevKitPro</li>
<li>Install the required libraries to build Atmosphere</li>
<li>Clone Atmosphere into the commit/tag/branch you want</li>
<li>Copy the <code>deviceid.patch</code> file from this repo into the Atmosphere directory</li>
<li>Run the following command, to modify the DeviceId value in the patch and apply the patch (tested only on linux):
<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto">
 
<pre>export DEVICEID=0x0022334455667788
sed -i &quot;s/###DEVICEID###/$DEVICEID/g&quot; deviceid.patch
 
git am deviceid.patch</pre>
</div></li>
<li>Go to the <code>exosphere</code> directory, inside the repo</li>
<li>Build <code>exosphere</code>:
<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto">
 
<pre>make -j$(nproc) exosphere.bin</pre>


</div></li>
This can be used to boot Horizon with Atmosphere in a Nintendo Switch with transplanted <code>PRODINFO</code>/<code>PRODINFOF</code> partitions.
<li>Copy <code>exosphere.bin</code> to the <code>Atmosphere</code> directory in your SD card and follow the steps to configure it from the dockerized build.</li></ul>


== Considerations ==
Refer to the [https://github.com/PabloZaiden/deviceid-exosphere-builder/blob/master/README.md readme] for instructions.
* '''Important. Do not share your dumps and personalized builds.''' The <code>deviceid_exosphere.bin</code> is tied to a specific DeviceID and ''must not be shared''. The same applies for the <code>PRODINFO</code>/<code>PRODINFOF</code> dumps. You may end up with a banned console.
* Doing this will potentialy leave you with more than one console with the same MAC address. Trying to connect both of them at the same time, to the same wireless network may result in an unexpected behavior. To modify your MAC address, edit the decrypted PRODINFO and modify the 0x6 bytes starting at 0x210 and use the CRC16 method described [https://switchbrew.org/wiki/Calibration here] to properly fill the next 0x2 bytes.


==Changelog==  
==Changelog==  
'''(v.1.0)'''
'''0.18.1 2021/02/28'''
* First Release.
*Release compatible with Atmosphere 0.18.1.
'''0.17.0 2021/01/07'''
*Release compatible with Atmosphere 0.17.0.
'''0.16.2 2020/12/21'''
*Release compatible with Atmosphere 0.16.2.
'''0.15.0 2020/10/28'''
*Release compatible with Atmosphere 0.15.0.


== Acknowledgements ==
==Credits==
* '''shchmue''', '''Jan4V''' and '''SciresM''' for all the patience answering questions and all the info about this and the ''full nand transplant'' options.
Acknowledgements: shchmue, Jan4V and SciresM for all the patience answering questions and all the info about this and the full nand transplant options.


== External links ==
== External links ==
* Github - https://github.com/PabloZaiden/deviceid-exosphere-builder
* GitHub - https://github.com/PabloZaiden/deviceid-exosphere-builder
* Reddit - https://www.reddit.com/r/SwitchHaxing/comments/i3b8jw/deviceidexospherebuilder_transplant/

Latest revision as of 03:32, 13 June 2023

DeviceID Exosphere Builder
Deviceidexospherebuildernx.png
General
AuthorPabloZaiden
TypePC Utilities
Version0.18.1
LicenseMixed
Last Updated2021/02/28
Links
Download
Website
Source

Dockerized tool to build a custom Exosphere binary that spoofs the DeviceID.

This can be used to boot Horizon with Atmosphere in a Nintendo Switch with transplanted PRODINFO/PRODINFOF partitions.

Refer to the readme for instructions.

Changelog

0.18.1 2021/02/28

  • Release compatible with Atmosphere 0.18.1.

0.17.0 2021/01/07

  • Release compatible with Atmosphere 0.17.0.

0.16.2 2020/12/21

  • Release compatible with Atmosphere 0.16.2.

0.15.0 2020/10/28

  • Release compatible with Atmosphere 0.15.0.

Credits

Acknowledgements: shchmue, Jan4V and SciresM for all the patience answering questions and all the info about this and the full nand transplant options.

External links

Advertising: