Hacking Can’t enter open Decrypt9 from arm9loaderhax with AuReiNand

[gamecaptor]

I am following Plailect guide and I have hit a road block in Part 5, the step that is says to Enter Decrypt9. It says to power on the 3DS while holding L+R on boot. When I do this I get a black screen; nothing boots.

In its current state when I boot the 3DS it is powering me into sysNAND, NOT emuNAND as it says it should. Here are the specifics of my 3DS behavior:

Spoiler

Powering on 3DS without SD turns off immediately.

Powering on 3DS boots with SD and these AuReiNand settings boots into sysNAND
Enabled Updated SysNAND mode (A9LH-only)
Enabled Use pre-patched FIRMs
Enabled Force A9LH detection
Disabled Use 9.0 FIRM as default
Disabled Use second EmuNAND as default
Enabled Show current NAND in System Settings

Powering on 3DS boots with SD and these AuReiNand settings boots into emuNAND
Disabled Updated SysNAND mode (A9LH-only)
Enabled Use pre-patched FIRMs
Enabled Force A9LH detection
Disabled Use 9.0 FIRM as default
Disabled Use second EmuNAND as default
Enabled Show current NAND in System Settings

A few things of note that might help you help me
1. In Part 3 I used AuReiNand v3.14 instead of Cakes. There was a little bit of guess work on my part as to which files to put where, but it seemed to work so hurray me!
2. When I reached Step 17 of Part 3, where I reached the AuReiNand menu (it would be the equivalent of the same steps in Cakes) I didn’t select anything; I left everything disabled.
3. Since I started this AuReiNand v4.0.1 has been released, so Part 3 was done with v3.14 and Part 5 was done with 4.0.1 (I’m unsure if that plays into this or not)

Finally, here is the layout of my SD card currently:

Spoiler

SD:
| arm11.bin [from OTPHelper v20160330]
| arm9.bin [from OTPHelper v20160330]
| arm9loaderhax.bin [4.0.1]
| AuReiNand.dat [3.14]
| boot.3dsx [Home Brew Launcher v1.1]
| Decrypt9.log
| emuNAND_original.bin
| FBI_inject_with_banner.app
| hs.enc
| OTPHelper.log
| PlaiSys.log
| SafeA9LHInstaller.dat [v1.5.2]
| Slot0x05KeyY.bin
| slot0x11key96.bin
| slot0x25KeyX.bin
| sysNAND_original.bin
|
+---EmuNAND9 [v20160326]
| starter.bin
|
+---3ds
| +---AuReiNand [v4.0.1]
| | AuReiNand.3dsx
| | AuReiNand.smdh
| |
| +---EmuNAND9 [v20160326]
| | EmuNAND9.3dsx
| | EmuNAND9.smdh
| |
| +---PlaiSysUpdater [v04]
| | PlaiSysUpdater.3dsx
| | PlaiSysUpdater.smdh
| |
| +---TinyFormat [v1.0.0]
| | TinyFormat.3dsx
| | TinyFormat.smdh
| |
| +---OTPHelper [v20160330]
| | OTPHelper.3dsx
| | OTPHelper.smdh
| |
| +---Decrypt9WIP [20160309]
| | Decrypt9WIP.3dsx
| | Decrypt9WIP.smdh
| |
| +---FBI [v1.4.17]
| | FBI.3dsx
| | FBI.smdh
| |
| +---MiniPasta [v1]
| | MiniPasta.3dsx
| | MiniPasta.smdh
| |
| \---SafeA9LHInstaller [v1.5.2]
| SafeA9LHInstaller.3dsx
| SafeA9LHInstaller.smdh
|
+---aurei [from AuReiNand v4.0.1]
| | firmware.bin [from AuReiNAND Firmware_NTR_o3DS]
| | config.bin
| | patched_firmware_emu.bin
| | patched_firmware_em2.bin
| | patched_firmware_sys.bin
| |
| \---payloads
| b.bin [renamed Uncart.bin]
| default.bin [renamed Decrypt9WIP.bin]
| y.bin [renamed EmuNAND9.bin]
|
+---Nintendo 3DS
| +---84949d6d6854952a2581dadfda6f3de6
| | \---623d00d44730dad85344363400275048
| | +---dbs
| | | import.db
| | | title.db
| | |
| | +---extdata
| | | \---00000000
| | | +---0000008f
| | | | \---00000000
| | | | 00000001
| | | | 00000002
| | | | 00000003
| | | | 00000004
| | | | 00000005
| | | |
| | | +---00000219
| | | | \---00000000
| | | | 00000001
| | | | 00000002
| | | | 00000004
| | | | 00000005
| | | |
| | | +---000002cd
| | | | \---00000000
| | | | 00000001
| | | | 00000002
| | | | 00000003
| | | | 00000004
| | | | 00000005
| | | | 00000006
| | | | 00000007
| | | | 00000008
| | | | 00000009
| | | | 0000000a
| | | | 0000000b
| | | | 0000000c
| | | | 0000000d
| | | | 0000000e
| | | | 0000000f
| | | | 00000010
| | | | 00000011
| | | |
| | | \---00000210
| | | \---00000000
| | | 00000001
| | | 00000002
| | | 00000003
| | |
| | \---title
| | \---00040000
| | \---00269500
| | \---content
| | | 00000000.tmd
| | | 3dcc536a.app
| | |
| | \---cmd
| | 00000001.cmd
| |
| +---aa5b25854cbeded91a79f509f229fed0
| | \---623d00d44730dad85344363400275048
| | +---extdata
| | | \---00000000
| | | +---0000008f
| | | | \---00000000
| | | | 00000001
| | | | 00000002
| | | | 00000003
| | | | 00000004
| | | | 00000005
| | | |
| | | +---000002cd
| | | | \---00000000
| | | | 00000001
| | | | 00000002
| | | | 00000003
| | | | 00000004
| | | | 00000005
| | | | 00000006
| | | | 00000007
| | | | 00000008
| | | | 00000009
| | | | 0000000a
| | | | 0000000b
| | | | 0000000c
| | | | 0000000d
| | | |
| | | +---00000219
| | | | \---00000000
| | | | 00000001
| | | | 00000002
| | | |
| | | \---00000210
| | | \---00000000
| | | 00000001
| | | 00000002
| | | 00000003
| | |
| | +---title
| | | \---00040000
| | | \---00269500
| | | \---content
| | | | 00000000.tmd
| | | | 3dcc536a.app
| | | |
| | | \---cmd
| | | 00000001.cmd
| | |
| | \---dbs
| | import.db
| | title.db
| |
| +---Private
| | \---00020400
| | phtcache.bin
| |
| \---3300735ad9909303dc56fa9abf421af7
| \---623d00d44730dad85344363400275048
| +---extdata
| | \---00000000
| | +---000002cd
| | | \---00000000
| | | 00000001
| | | 00000002
| | | 00000003
| | | 00000004
| | | 00000005
| | | 00000006
| | | 00000007
| | | 00000008
| | | 00000009
| | | 0000000a
| | | 0000000b
| | | 0000000c
| | | 0000000d
| | |
| | +---0000008f
| | | \---00000000
| | | 00000001
| | | 00000002
| | | 00000003
| | | 00000004
| | | 00000005
| | |
| | +---00000219
| | | \---00000000
| | | 00000001
| | | 00000002
| | |
| | \---00000210
| | \---00000000
| | 00000001
| | 00000002
| | 00000003
| |
| +---title
| | \---00040000
| | \---00985700
| | \---content
| | | 00000000.tmd
| | | 331b2a86.app
| | |
| | \---cmd
| | 00000001.cmd
| |
| \---dbs
| import.db
| title.db
|
+---cia
| PlaiSysUpdater.cia [v04]
| TinyFormat.cia [v1.0.0]
| hblauncher_loader.cia [v1.1]
|
+---updates [2.1.0U Full]
| 0004001000021000.cia
| 0004001000021100.cia
| 0004001000021200.cia
| 0004001000021300.cia
| 0004001000021400.cia
| 0004001000021500.cia
| 0004001000021700.cia
| 0004001000021900.cia
| 0004001000021A00.cia
| 0004001000021B00.cia
| 0004001000021D00.cia
| 0004001000021E00.cia
| 0004001000021F00.cia
| 0004001000024000.cia
| 0004001B00010002.cia
| 0004003000008A02.cia
| 0004003000008A03.cia
| 0004003000008F02.cia
| 0004003000009002.cia
| 0004003000009202.cia
| 0004003000009302.cia
| 0004003000009402.cia
| 0004003000009602.cia
| 0004003000009702.cia
| 000400300000C502.cia
| 000400300000C503.cia
| 000400300000C802.cia
| 000400300000C803.cia
| 000400300000C902.cia
| 000400300000CB02.cia
| 000400300000CC02.cia
| 0004009B00010202.cia
| 0004009B00010402.cia
| 0004009B00010602.cia
| 0004009B00011402.cia
| 0004009B00011602.cia
| 0004009B00011D02.cia
| 0004009B00011E02.cia
| 0004009B00012302.cia
| 0004009B00013302.cia
| 0004009B00014002.cia
| 0004009B00014102.cia
| 0004009B00014202.cia
| 0004009B00014302.cia
| 0004009B00015302.cia
| 000400DB00010302.cia
| 000400DB00010502.cia
| 000400DB00016302.cia
| 000400DB00017302.cia
| 0004013000001502.cia
| 0004013000001503.cia
| 0004013000001602.cia
| 0004013000001702.cia
| 0004013000001703.cia
| 0004013000001802.cia
| 0004013000001803.cia
| 0004013000001A02.cia
| 0004013000001A03.cia
| 0004013000001B02.cia
| 0004013000001B03.cia
| 0004013000001C02.cia
| 0004013000001C03.cia
| 0004013000001D02.cia
| 0004013000001D03.cia
| 0004013000001E02.cia
| 0004013000001E03.cia
| 0004013000001F02.cia
| 0004013000001F03.cia
| 0004013000002002.cia
| 0004013000002102.cia
| 0004013000002103.cia
| 0004013000002202.cia
| 0004013000002203.cia
| 0004013000002302.cia
| 0004013000002303.cia
| 0004013000002402.cia
| 0004013000002403.cia
| 0004013000002602.cia
| 0004013000002702.cia
| 0004013000002703.cia
| 0004013000002802.cia
| 0004013000002902.cia
| 0004013000002903.cia
| 0004013000002A02.cia
| 0004013000002A03.cia
| 0004013000002B02.cia
| 0004013000002C02.cia
| 0004013000002C03.cia
| 0004013000002D02.cia
| 0004013000002D03.cia
| 0004013000002E02.cia
| 0004013000002E03.cia
| 0004013000002F02.cia
| 0004013000002F03.cia
| 0004013000003102.cia
| 0004013000003103.cia
| 0004013000003202.cia
| 0004013000003203.cia
| 0004013000003302.cia
| 0004013000003303.cia
| 0004013000003402.cia
| 0004013000003502.cia
| 0004013000003702.cia
| 0004013000008002.cia
| 0004013000008003.cia
| 0004013800000002.cia
| 0004013800000003.cia
| 0004013800000102.cia
| 0004800542383841.cia
| 00048005484E4441.cia
| 0004800F484E4841.cia
| 0004800F484E4C41.cia
|
\---a9lh
firm0.bin [from data_input]
firm1.bin [from data_input]
otp.bin
payload_stage1.bin [from payload_input]
payload_stage2.bin [from payload_input]
secret_sector.bin [from data_input]

Anyone give me a clue as to what is going on?

 

[SkyChotik]

No al9h folder in the root of sd?

You need the al9h folder with the .bin files to open by holding hardware buttons on boot.

https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax-&-AuReiNAND)#preparatory-work

Start there, says which files to copy for aurei, since I'm using cakes.

 

[gamecaptor]

Thanks for the reply SkyChotik.

I actually do have the aurei folder in the root of my SD. According to the instructions it says to place those files into the payloads folder (under the aurei folder) and rename them.
+---aurei [from AuReiNand v4.0.1]
| | firmware.bin [from AuReiNAND Firmware_NTR_o3DS]
| | config.bin
| | patched_firmware_emu.bin
| | patched_firmware_em2.bin
| | patched_firmware_sys.bin
| |
| \---payloads
| b.bin [renamed Uncart.bin]
| default.bin [renamed Decrypt9WIP.bin]
| y.bin [renamed EmuNAND9.bin]

 

[SkyChotik]

Wow, I really should have kept reading, I didn't realize how different booting aurei was from cakes.
Okay, I'm assuming your sysnand is 9.2? If so, I'd probably just recommend booting into that (holding R on power up) and using browserhax to boot cfw and launching decrypt9 from there.


Edit:

https://github.com/Plailect/Guide/wiki/Troubleshooting#ts_sys_a9lh

That should help also, if aurei isn't booting at all.

 

[gamecaptor]

Correct, sysNAND is 9.2, emuNAND is 10.7.

Turning on my 3DS boots me into sysNAND by default, not emuNAND. If I'm reading the instructions correctly it should be booting me into emuNAND?

But more dis-concerning is that the L+R is not booting into Decrypt9.

I went through the troubleshooting guide:
https://github.com/Plailect/Guide/wiki/Troubleshooting#ts_sys_a9lh

1. Ensure you have a working payload.
   1. Check for the existence of arm9loaderhax.bin in the root of your SD card. Verified
      
   2. If you are following the AuReiNand guide, check that
      1. /aurei/firmware.bin exist; and Verified
         
      2. /aurei/firmware.bin is the correct one for your console. Verified
2. Test booting Decrypt9
   1. On AuReiNAND, hold L + R on boot Fails
3. Try this test payload (mirror).
   1. Rename /arm9loaderhax.bin, if it exists, to something else.
   2. Place the arm9loaderhax.bin from the archive linked above in your SD root.
   3. Insert your SD card into your 3DS and power on.
   4. Press A. Your 3DS should power off; this means arm9loaderhax is working and something else is broken; your device is not bricked. Powers off by pressing A

So by going off that, something else is broken, I'm just not sure what.

 

[Just Passing By]

Correct, sysNAND is 9.2, emuNAND is 10.7.

Turning on my 3DS boots me into sysNAND by default, not emuNAND. If I'm reading the instructions correctly it should be booting me into emuNAND?

But more dis-concerning is that the L+R is not booting into Decrypt9.

I went through the troubleshooting guide:
https://github.com/Plailect/Guide/wiki/Troubleshooting#ts_sys_a9lh

1. Ensure you have a working payload.
   1. Check for the existence of arm9loaderhax.bin in the root of your SD card. Verified
      
   2. If you are following the AuReiNand guide, check that
      1. /aurei/firmware.bin exist; and Verified
         
      2. /aurei/firmware.bin is the correct one for your console. Verified
2. Test booting Decrypt9
   1. On AuReiNAND, hold L + R on boot Fails
3. Try this test payload (mirror).
   1. Rename /arm9loaderhax.bin, if it exists, to something else.
   2. Place the arm9loaderhax.bin from the archive linked above in your SD root.
   3. Insert your SD card into your 3DS and power on.
   4. Press A. Your 3DS should power off; this means arm9loaderhax is working and something else is broken; your device is not bricked. Powers off by pressing A

So by going off that, something else is broken, I'm just not sure what.

It might be that you're using an old version. Try this one:
http://workupload.com/file/Y9KNCIV3

 

[SkyChotik]

When I followed the guide, everything was emunand only (nothing about rednand anywhere) it took me a few times to even figure out how to boot some things before the system started.
My recommendations at this point are basically "Try to go back and change any settings you missed by booting sysnand and using browserhax to load hblauncher"

I never really tried aureinand because the setup just seemed more complicated than it needed to be.

Edit: Listen to Just Passing By, he knows more than I do, I just want to be helpful <3

 

[Just3DS]

Copy the AuRei portion of the files from AuRei files again (arm9loaderhax.bin in root of sd card, files in aurei folder, etc).

 

[dg_dex]

I had the same problem a few days back. I ended up resolving the problem by literally starting over again. I have no idea why Decrypt9 stopped working. I have the a similar layout on my SD card as you.

Hold on a minute. I just noticed that you have a Decrypt9.log entry on the root of your SD. This would mean that Decrypt9 has booted some time or another recently.

I have these files on the root of my SD.

| Slot0x05KeyY.bin
| slot0x11key96.bin
| slot0x25KeyX.bin
| arm9loaderhax.bin
| AuReiNand.dat
| 3ds
| aurei
| Nintendo 3ds

 

[gamecaptor]

Just Passing By, you the man! That worked (sort of, I got an error which I'll get to that in a second). Interesting that I didn't see that newer version on the site.
SkyChotik, I appreciate you chiming in! That's why I love the GBATemp community! Sometimes just throwing ideas out there gets the brain moving.
Just3DS, thank you for the suggestion, but since Just Passing By's link worked, I don't want to mess with anything.
dg_dex, good catch, didn't put any thought into that. It would be left over from Part 4 (Getting the OTP). Perhaps that was playing a part?

So NOW that it loaded properly by holding down the L+R I received the following message:
-- Decrypt9WIP (2016/03/29) --
Counting 15 submenus and 112 features
Initializing, hold L+R to pause

Initializing SD card... success
0x03 KeyX & KeyY: automatically setup
0x23 KeyX: loaded, verified, setup
0x28 KeyX: already setup
0x1B KeyX: not found
Finalizing Initialization...

Initalization: partially failed
(A to continue)

After pressing A it then loaded me into the Decrypt9WIP menu.

A few follow up questions:
Should that last message, "partially failed", be concerning?
I realize I will be copying the emuNAND data into the sysNAND in the next step, but (in it's current state) when I boot on my 3DS should it be taking me to the sysNAND (9.2) or emuNAND (10.7)?

 

[Shadowtrance]

Just Passing By, you the man! That worked (sort of, I got an error which I'll get to that in a second). Interesting that I didn't see that newer version on the site.
SkyChotik, I appreciate you chiming in! That's why I love the GBATemp community! Sometimes just throwing ideas out there gets the brain moving.
Just3DS, thank you for the suggestion, but since Just Passing By's link worked, I don't want to mess with anything.
dg_dex, good catch, didn't put any thought into that. It would be left over from Part 4 (Getting the OTP). Perhaps that was playing a part?

So NOW that it loaded properly by holding down the L+R I received the following message:
-- Decrypt9WIP (2016/03/29) --
Counting 15 submenus and 112 features
Initializing, hold L+R to pause

Initializing SD card... success
0x03 KeyX & KeyY: automatically setup
0x23 KeyX: loaded, verified, setup
0x28 KeyX: already setup
0x1B KeyX: not found
Finalizing Initialization...

Initalization: partially failed
(A to continue)

After pressing A it then loaded me into the Decrypt9WIP menu.

A few follow up questions:
Should that last message, "partially failed", be concerning?
I realize I will be copying the emuNAND data into the sysNAND in the next step, but (in it's current state) when I boot on my 3DS should it be taking me to the sysNAND (9.2) or emuNAND (10.7)?

No, that missing key isn't anything to worry about, if i doesn't exist on your sd card then of course it won't be found and fail.

 

[Just Passing By]

No, that missing key isn't anything to worry about, if i doesn't exist on your sd card then of course it won't be found and fail.

He's talking about the
"Initalization: partially failed
(A to continue)"

I think it's fine. All of the main functions should be intact.

 

[Shadowtrance]

I know, and if you read the output you'd see what i was talking about... 0x1B KeyX: not found so of course it is going to "partially fail" initialization.

 

[gamecaptor]

ok, thanks all. That's what I suspected, but I wanted to be certain.

To my other question, before I move onto the next step, Copying RedNAND data to SysNAND, should it be taking me to the sysNAND (9.2) or emuNAND (10.7) when I power on my 3DS? I believe that is correct, but I want to be certain.

 

[pancakes077]

ok, thanks all. That's what I suspected, but I wanted to be certain.

To my other question, before I move onto the next step, Copying RedNAND data to SysNAND, should it be taking me to the sysNAND (9.2) or emuNAND (10.7) when I power on my 3DS? I believe that is correct, but I want to be certain.

That doesn't matter for Copying RedNAND data to SysNAND. Just make sure that you Dump from RedNAND and Inject into SysNAND, i.e. just follow the steps carefully.

To answer your question though, AuReiNand has 2 modes, Regular Mode and "Updated sysNAND" mode. Regular Mode autoboots RedNAND. "Updated SysNAND" mode autoboots SysNAND.

You're about to delete RedNAND, so it really doesn't matter.

 

[gamecaptor]

That doesn't matter for Copying RedNAND data to SysNAND. Just make sure that you Dump from RedNAND and Inject into SysNAND, i.e. just follow the steps carefully.

To answer your question though, AuReiNand has 2 modes, Regular Mode and "Updated sysNAND" mode. Regular Mode autoboots RedNAND. "Updated SysNAND" mode autoboots SysNAND.

You're about to delete RedNAND, so it really doesn't matter.

Ah, ok, that helps a lot. It's the terminology that confuses me still. So that explains why when I Disable "Updated SysNAND mode (A9LH-only)" it boots me into sysNAND. Thanks for your help pancakes007!https://gbatemp.net/members/pancakes077.387263/