N-archive/Guide_3DS
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Deprecate A9LH (Close #1388, Close #1387)

Browse source
This commit is contained in:
Plailect 2017-10-17 17:20:46 -04:00
parent 936860bbf3
commit 3d9fe52076
7 changed files with 13 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
_pages/en_US/ctrtransfer.txt
View file

@ -10,7 +10,7 @@ To use the [magnet](https://en.wikipedia.org/wiki/Magnet_URI_scheme) links on th
Note that if you have any payload files other than `GodMode9.firm` in the `/luma/payloads/` folder on your SD card, holding (Start) on boot will display a "chainloader menu" where you will have to use the D-Pad and the (A) button to select "GodMode9" for these instructions. Note that if you have any payload files other than `GodMode9.firm` in the `/luma/payloads/` folder on your SD card, holding (Start) on boot will display a "chainloader menu" where you will have to use the D-Pad and the (A) button to select "GodMode9" for these instructions.
You MUST have already installed Luma3DS and boot9strap or arm9loaderhax to use this. You MUST have already installed Luma3DS and boot9strap to use this.
{: .notice--danger} {: .notice--danger}
### What you need ### What you need

2
_pages/en_US/flashing-ntrboot-(3ds-multi-system).txt
View file

@ -10,7 +10,7 @@ Note that R4i Gold 3DS RTS flashcarts will not be able to be used for their stan
There are optional steps at the end of the ntrboot boot9strap installation instructions to remove the ntrboot exploit from your flashcart when you are done. There are optional steps at the end of the ntrboot boot9strap installation instructions to remove the ntrboot exploit from your flashcart when you are done.
This method requires temporary access to a second 3DS family device that is already running some kind of custom firmware (such as boot9strap or arm9loaderhax). It is compatible with the following flashcarts: This method requires temporary access to a second 3DS family device that is already running boot9strap. It is compatible with the following flashcarts:
+ [Acekard 2i](http://www.nds-card.com/ProShow.asp?ProID=160) + [Acekard 2i](http://www.nds-card.com/ProShow.asp?ProID=160)
+ [R4i Gold 3DS RTS](http://www.nds-card.com/ProShow.asp?ProID=149) + [R4i Gold 3DS RTS](http://www.nds-card.com/ProShow.asp?ProID=149)

4
_pages/en_US/installing-boot9strap-(dsiware).txt
View file

@ -10,9 +10,9 @@ There are two different methods of installing boot9strap using DSiWare on 11.6.0
One of these methods only works with four specific games that are no longer sold on the eShop, while the other works with quite a few games still sold on the eShop. One of these methods only works with four specific games that are no longer sold on the eShop, while the other works with quite a few games still sold on the eShop.
Both of these methods require two devices. One 3DS (or 2DS) must be running some kind of custom firmware (such as boot9strap or arm9loaderhax) and is referred to as the *source 3DS*, while the other 3DS (or 2DS) is on stock 11.6.0 and referred to as the *target 3DS*. Both of these methods require two devices. One 3DS (or 2DS) must be running boot9strap and is referred to as the *source 3DS*, while the other 3DS (or 2DS) is on stock 11.6.0 and referred to as the *target 3DS*.
Both of these methods will assume that the 3DS running custom firmware is using boot9strap or arm9loaderhax and has completed this guide. While it is possible to do these methods with some other kind of custom firmware, that is out of the scope of this guide. Both of these methods will assume that the 3DS running custom firmware is using boot9strap and has completed this guide. While it is possible to do these methods with some other kind of custom firmware, that is out of the scope of this guide.
Both of these methods use a combination of the "FIRM partitions known-plaintext" exploit detailed [here](https://www.3dbrew.org/wiki/3DS_System_Flaws), and an oversight that allows DSiWare titles to read and write to anywhere in encrypted NAND. Both of these methods use a combination of the "FIRM partitions known-plaintext" exploit detailed [here](https://www.3dbrew.org/wiki/3DS_System_Flaws), and an oversight that allows DSiWare titles to read and write to anywhere in encrypted NAND.

4
_pages/en_US/installing-boot9strap-(dsiware-game-injection).txt
View file

@ -16,7 +16,7 @@ If you do not use the correct `.firm` corresponding to the target 3DS, you will
### What you need ### What you need
* Two 3DS family devices * Two 3DS family devices
+ **The source 3DS**: the device running some kind of custom firmware (such as boot9strap or arm9loaderhax) *on the latest version* + **The source 3DS**: the device running boot9strap *on the latest version*
+ **The target 3DS**: the device on stock firmware *on 11.6.0* + **The target 3DS**: the device on stock firmware *on 11.6.0*
* Purchase (or already own) a compatible DSiWare game from the eShop on **the source 3DS** * Purchase (or already own) a compatible DSiWare game from the eShop on **the source 3DS**
+ A pirated copy of the game will **not** work + A pirated copy of the game will **not** work
@ -43,7 +43,7 @@ Use a [save manager](https://github.com/J-D-K/JKSM/releases/latest) to backup an
1. Power off **the source 3DS** 1. Power off **the source 3DS**
1. Insert **the source 3DS**'s SD card into your computer 1. Insert **the source 3DS**'s SD card into your computer
1. Copy `GodMode9.firm` (or `GodMode9.bin` for arm9loaderhax users) from the GodMode9 `.zip` to the `/luma/payloads` folder on **the source 3DS**'s SD card 1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads` folder on **the source 3DS**'s SD card
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of **the source 3DS**'s SD card 1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of **the source 3DS**'s SD card
1. Copy the `.app` and `savedata` folder from DSiWare injection `.zip` to the root of **the source 3DS**'s SD card 1. Copy the `.app` and `savedata` folder from DSiWare injection `.zip` to the root of **the source 3DS**'s SD card
1. Reinsert **the source 3DS**'s SD card 1. Reinsert **the source 3DS**'s SD card

4
_pages/en_US/installing-boot9strap-(dsiware-save-injection).txt
View file

@ -16,7 +16,7 @@ If you do not use the correct `.firm` corresponding to the target 3DS, you will
### What you need ### What you need
* Two 3DS family devices * Two 3DS family devices
+ **The source 3DS**: the device running some kind of custom firmware (such as boot9strap or arm9loaderhax) *on the latest version* + **The source 3DS**: the device running boot9strap *on the latest version*
+ **The target 3DS**: the device on stock firmware *on 11.6.0* + **The target 3DS**: the device on stock firmware *on 11.6.0*
* Already own one of the following exploitable DSiWare games (a pirated copy of the game will **not** work) on **the source 3DS** * Already own one of the following exploitable DSiWare games (a pirated copy of the game will **not** work) on **the source 3DS**
+ **Fieldrunners** + **Fieldrunners**
@ -40,7 +40,7 @@ If you do not use the correct `.firm` corresponding to the target 3DS, you will
Use a [save manager](https://github.com/J-D-K/JKSM/releases/latest) to backup any saves you care about on *the target 3DS* (it will be formatted!) Use a [save manager](https://github.com/J-D-K/JKSM/releases/latest) to backup any saves you care about on *the target 3DS* (it will be formatted!)
{: .notice--warning} {: .notice--warning}
1. Copy `GodMode9.firm` (or `GodMode9.bin` for arm9loaderhax users) from the GodMode9 `.zip` to the `/luma/payloads` folder on **the source 3DS**'s SD card 1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads` folder on **the source 3DS**'s SD card
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of **the source 3DS**'s SD card 1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of **the source 3DS**'s SD card
1. Copy the relevant `public.sav` from the `/dsiware/(8 Character ID)/` folder in the 3ds_dsiwarehax_installer `.zip` to the root of **the source 3DS**'s SD card 1. Copy the relevant `public.sav` from the `/dsiware/(8 Character ID)/` folder in the 3ds_dsiwarehax_installer `.zip` to the root of **the source 3DS**'s SD card
+ **Fieldrunners USA Region**: `4b464445` + **Fieldrunners USA Region**: `4b464445`

6
_pages/en_US/move-emunand.txt
View file

@ -8,7 +8,7 @@ This is an add-on section for moving the contents of a previous EmuNAND to your
Note that if you have any payload files other than `GodMode9.firm` in the `/luma/payloads/` folder on your SD card, holding (Start) on boot will display a "chainloader menu" where you will have to use the D-Pad and the (A) button to select "GodMode9" for these instructions. Note that if you have any payload files other than `GodMode9.firm` in the `/luma/payloads/` folder on your SD card, holding (Start) on boot will display a "chainloader menu" where you will have to use the D-Pad and the (A) button to select "GodMode9" for these instructions.
**You MUST have already installed Luma3DS and boot9strap or arm9loaderhax to use this.** You MUST have already installed Luma3DS and boot9strap to use this.
{: .notice--danger} {: .notice--danger}
### What you need ### What you need
@ -23,7 +23,7 @@ Note that if you have any payload files other than `GodMode9.firm` in the `/luma
1. Power off your device 1. Power off your device
1. Insert your SD card into your computer 1. Insert your SD card into your computer
1. Copy `GodMode9.firm` (or `GodMode9.bin` for arm9loaderhax users) from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card 1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card 1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card
1. Reinsert your SD card into your device 1. Reinsert your SD card into your device
@ -73,7 +73,7 @@ To identify a `<TitleID>.gbavc.sav` file's Title ID, you can get a listing of al
1. Navigate to `[E:] EMUNAND VIRTUAL` 1. Navigate to `[E:] EMUNAND VIRTUAL`
1. Press (A) on `nand.bin` to select it, then select "NAND image options...", then select "Restore SysNAND (safe)" 1. Press (A) on `nand.bin` to select it, then select "NAND image options...", then select "Restore SysNAND (safe)"
1. Press (A) to unlock SysNAND overwriting, then input the key combo given 1. Press (A) to unlock SysNAND overwriting, then input the key combo given
+ This will not overwrite your arm9loaderhax installation + This will not overwrite your boot9strap installation
1. Input the key combo given to unlock SysNAND (lvl1) writing 1. Input the key combo given to unlock SysNAND (lvl1) writing
+ This process will take some time + This process will take some time
1. Once it has completed, press (A) to continue 1. Once it has completed, press (A) to continue

4
_pages/en_US/region-changing.txt
View file

@ -22,7 +22,7 @@ Note that occasionally the eShop will inexplicably still not work for devices th
Region changing using CTRTransfer (which this method uses) seems to cause reboot patches to break. The cause for this is unknown, but Old 3DS users, for now, will be unable to play extended memory mode games (such as Monster Hunter, Super Smash Bros, and Pokémon Sun / Moon) until they format their devices. Region changing using CTRTransfer (which this method uses) seems to cause reboot patches to break. The cause for this is unknown, but Old 3DS users, for now, will be unable to play extended memory mode games (such as Monster Hunter, Super Smash Bros, and Pokémon Sun / Moon) until they format their devices.
You MUST have already installed Luma3DS and boot9strap or arm9loaderhax to use this. You MUST have already installed Luma3DS and boot9strap to use this.
{: .notice--danger} {: .notice--danger}
### What you need ### What you need
@ -47,7 +47,7 @@ You MUST have already installed Luma3DS and boot9strap or arm9loaderhax to use t
1. Power off your device 1. Power off your device
1. Insert your SD card into your computer 1. Insert your SD card into your computer
1. Create a folder named `cias` on the root of your SD card if it does not already exist 1. Create a folder named `cias` on the root of your SD card if it does not already exist
1. Copy `GodMode9.firm` (or `GodMode9.bin` for arm9loaderhax users) from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card 1. Copy `GodMode9.firm` from the GodMode9 `.zip` to the `/luma/payloads/` folder on your SD card
1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card 1. Copy the `gm9` folder from the GodMode9 `.zip` to the root of your SD card
1. Copy `ctrtransfer_ticket_copy.gm9` to the `/gm9/scripts/` folder on your SD card 1. Copy `ctrtransfer_ticket_copy.gm9` to the `/gm9/scripts/` folder on your SD card
1. Copy the 11.5.0 CTRTransfer image `.bin` from the CTRTransfer `.zip` to the `/gm9/` folder on your SD card 1. Copy the 11.5.0 CTRTransfer image `.bin` from the CTRTransfer `.zip` to the `/gm9/` folder on your SD card