rvtr/wiki
1
Fork 0
mirror of https://github.com/rvtr/wiki.git synced 2025-10-31 06:31:13 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

A few minor style changes

Browse Source 
- Two space tabs are a bit buggy sometimes with ordered lists
- Put a few more things in <code> backticks
- Trim trailing whitespace
This commit is contained in:
Pk11 2021-01-18 07:53:18 -06:00
parent 8cfc1533f2
commit fa897e4f13
1 changed files with 50 additions and 49 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

99
pages/_en-US/ds-index/hardmod.md
View File

@ -8,19 +8,20 @@ description: An explanation of all things DS modding
---
Hardmodding is when you physically solder the motherboard of the Nintendo DSi to an SD card adapter in order to be read on a computer. This is useful for restoring NAND backups, viewing NAND on your PC, etc...
### Nintendo DS
[![Original DS motherboard with touch-points labeled](/assets/images/ds-hardmod/mobo_pinout.png)](/assets/images/ds-hardmod/mobo_pinout.png)
### Nintendo DSi
To hardmod a Nintendo DSi / DSi XL (LL) you will need:
- [Pencil tipped soldering iron](https://www.amazon.com/dp/B01N4571Q6)
- [Very fine wire](https://www.amazon.com/dp/B01MXGNTA4), 28AWG or smaller, preferably 30AWG+
- SD to microSD adapter
- An SD card reader able to read eMMC chips running in single data-line mode. [Here's a known working one](https://www.amazon.com/dp/B006T9B6R2)
- [Win32DiskImager](https://sourceforge.net/projects/win32diskimager/) and [HxD](https://mh-nexus.de/en/downloads.php?product=HxD20) if on Windows
- A valid NAND backup of the DSi you are hardmodding
- To be comfortable soldering to pads that are as small as 0.5mm in diameter
- [Pencil tipped soldering iron](https://www.amazon.com/dp/B01N4571Q6)
- [Very fine wire](https://www.amazon.com/dp/B01MXGNTA4), 28AWG or smaller, preferably 30AWG+
- SD to microSD adapter
- An SD card reader able to read eMMC chips running in single data-line mode. [Here's a known working one](https://www.amazon.com/dp/B006T9B6R2)
- [Win32DiskImager](https://sourceforge.net/projects/win32diskimager/) and [HxD](https://mh-nexus.de/en/downloads.php?product=HxD20) if on Windows
- A valid NAND backup of the DSi you are hardmodding
- To be comfortable soldering to pads that are as small as 0.5mm in diameter
#### DSi side A pinouts
[![DSi side A pinouts](/assets/images/dsi-hardmod/side_a.jpg)](/assets/images/dsi-hardmod/side_a.jpg)
@ -30,16 +31,16 @@ To hardmod a Nintendo DSi / DSi XL (LL) you will need:
[![DSi XL side B pinouts](/assets/images/dsi-hardmod/dsi_xl_side_b.png)](/assets/images/dsi-hardmod/dsi_xl_side_b.png)
- You will need to solder the points on the motherboard to the microSD card adapter
- CMD to pin 2
- GND to pins 3 and 6
- CLK to pin 5
- DAT0 to pin 7
- CMD to pin 2
- GND to pins 3 and 6
- CLK to pin 5
- DAT0 to pin 7
#### Soldered microSD adapter example
[![microSD example](/assets/images/dsi-hardmod/sd.jpg)](/assets/images/dsi-hardmod/sd.jpg)
- Insert the microSD card adapter into your computer
- **WARNING** - Windows will ask you to format it: **DO NOT** format it - this might cause irrepairable damage
- **WARNING** - Windows will ask you to format it: **DO NOT** format it - this might cause irrepairable damage
#### Removing the no$gba footer
You will first need to remove the NOCASH footer from the backup you are flashing to the DSi. This can be done by running the hiyaCFW helper application found [here](https://github.com/mondul/HiyaCFW-Helper/releases/latest).
@ -50,19 +51,19 @@ You will first need to remove the NOCASH footer from the backup you are flashing
1. Click `Start` to create the NAND backup without the no$gba footer
- Once the script completes, there should be a file with a long name ending in `-no-footer.bin` in the folder where your terminal is open
- Use this file as the NAND image you flash onto the DSi
- Use this file as the NAND image you flash onto the DSi
#### Windows instructions (skip for macOS / Linux)
1. Open Win32DiskImager
1. Click the folder icon and browse to your desktop. In the text box, write NAND_0.bin. When selecting type, choose All types *.*
1. Click the folder icon and browse to your desktop. In the text box, write `NAND_0.bin`. When selecting type, choose `All types *.*`
1. Choose the device that is the DSi and click read
1. Once it is done, click the folder icon, change the name to NAND_1.bin and read again
1. Once it is done, click the folder icon, change the name to `NAND_1.bin` and read again
1. Open HxD and drag both files into the editor. Go to the top bar, click "Analysis", click "File compare" from the drop down menu, then click "Compare".
1. Choose to compare both files then click OK when done
- If it says "The chosen files are identical.", you are good to go to the next section
- If it doesn't say that, and both NANDs aren't around 240MB, dump NAND_1/NAND_0 again
- If it says "The chosen files are identical.", you are good to go to the next section
- If it doesn't say that, and both NANDs aren't around 240MB, dump NAND_1/NAND_0 again
1. Open Win32DiskImager, click the folder icon and choose your existing NAND backup you created before
1. Flash it with the `Write` button
1. Unplug the SD card adapter and attempt to turn on the DSi
@ -71,44 +72,44 @@ You will first need to remove the NOCASH footer from the backup you are flashing
1. Work out where the SD card is mounted
- Linux:
1. Unplug the SD card adapter
1. Run `lbslk` on a terminal
1. Plug in the SD card adapter
1. Run `lbslk` again
1. This time a new device should appear
- It may be called `/dev/sdb`, make sure you note down what it is called on *your* terminal
- Linux:
1. Unplug the SD card adapter
1. Run `lbslk` on a terminal
1. Plug in the SD card adapter
1. Run `lbslk` again
1. This time a new device should appear
- It may be called `/dev/sdb`, make sure you note down what it is called on *your* terminal
- macOS:
1. Unplug the SD card adapter
1. Run `df` on a terminal
1. Plug in the SD card adapter
1. Run `df` again
1. A new device should appear in the list
- It may be called `/dev/disk1s1`, make sure you note down what it is called on *your* terminal
- macOS:
1. Unplug the SD card adapter
1. Run `df` on a terminal
1. Plug in the SD card adapter
1. Run `df` again
1. A new device should appear in the list
- It may be called `/dev/disk1s1`, make sure you note down what it is called on *your* terminal
1. Dump the NAND
- Run the following command on a terminal:
- `cat {device-name} > nand0.bin`
- Replace {device-name} with the SD card mount location
- E.g `cat /dev/sdb > nand0.bin`
- Then run `cat {device-name} > nand1.bin`
- Run the following command on a terminal:
- `cat {device-name} > nand0.bin`
- Replace `{device-name}` with the SD card mount location
- E.g `cat /dev/sdb > nand0.bin`
- Then run `cat {device-name} > nand1.bin`
1. Compare NAND dumps
1. Run the following command:
- Linux : `md5sum nand0.bin nand1.bin`
- macOS : `md5 -r nand0.bin nand1.bin`
1. Check that the hash generated matches each other
1. If not, redump the NAND, adjusting the wiring if necessary
1. Keep on redumping the NAND until the hashes are identical
1. Run the following command:
- Linux: `md5sum nand0.bin nand1.bin`
- macOS: `md5 -r nand0.bin nand1.bin`
1. Check that the hash generated matches each other
1. If not, redump the NAND, adjusting the wiring if necessary
1. Keep on redumping the NAND until the hashes are identical
1. Flash NAND
1. Locate the NAND backup you created before on the console
1. Run the following command:
- `cat {existing-nand-backup} > {device-name}`
- Replace `{existing-nand-backup}` with the location and name of your old NAND backup
- Replace `{device-name}` with the mount point of the SD card
1. Locate the NAND backup you created before on the console
1. Run the following command:
- `cat {existing-nand-backup} > {device-name}`
- Replace `{existing-nand-backup}` with the location and name of your old NAND backup
- Replace `{device-name}` with the mount point of the SD card
At this point you may unplug the SD card adapter and attempt to turn on the DSi.
If all went well, the DSi should have booted to the state it was when the backup was created!