Can’t enter open Decrypt9 from arm9loaderhax with AuReiNand

Discussion in '3DS - Flashcards & Custom Firmwares' started by gamecaptor, Mar 30, 2016.

  1. gamecaptor
    OP

    gamecaptor R.I.P. Densetsu. Legends never die!

    Member
    GBAtemp Patron
    gamecaptor is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    525
    281
    Jan 22, 2004
    United States
    Hyrule most of the time
    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:
    Warning: Spoilers inside!

    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:
    Warning: Spoilers inside!

    Anyone give me a clue as to what is going on?
     
    Last edited by gamecaptor, Mar 31, 2016
  2. SkyChotik

    SkyChotik Well-known Member

    Member
    146
    27
    Mar 22, 2016
    United States
    Last edited by SkyChotik, Mar 30, 2016
  3. gamecaptor
    OP

    gamecaptor R.I.P. Densetsu. Legends never die!

    Member
    GBAtemp Patron
    gamecaptor is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    525
    281
    Jan 22, 2004
    United States
    Hyrule most of the time
    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]
     
  4. SkyChotik

    SkyChotik Well-known Member

    Member
    146
    27
    Mar 22, 2016
    United States
    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.
     
    Last edited by SkyChotik, Mar 30, 2016
  5. gamecaptor
    OP

    gamecaptor R.I.P. Densetsu. Legends never die!

    Member
    GBAtemp Patron
    gamecaptor is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    525
    281
    Jan 22, 2004
    United States
    Hyrule most of the time
    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.
     
  6. Just Passing By

    Just Passing By GBAtemp Advanced Maniac

    Member
    1,562
    594
    Jan 3, 2016
    United States
    It might be that you're using an old version. Try this one:
    http://workupload.com/file/Y9KNCIV3
     
    gamecaptor likes this.
  7. SkyChotik

    SkyChotik Well-known Member

    Member
    146
    27
    Mar 22, 2016
    United States
    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
     
    Just Passing By and gamecaptor like this.
  8. Just3DS

    Just3DS GBAtemp Fan

    Member
    440
    109
    Jan 31, 2015
    Copy the AuRei portion of the files from AuRei files again (arm9loaderhax.bin in root of sd card, files in aurei folder, etc).
     
    gamecaptor likes this.
  9. dg_dex

    dg_dex GBAtemp Regular

    Member
    142
    32
    Feb 27, 2016
    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 likes this.
  10. gamecaptor
    OP

    gamecaptor R.I.P. Densetsu. Legends never die!

    Member
    GBAtemp Patron
    gamecaptor is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    525
    281
    Jan 22, 2004
    United States
    Hyrule most of the time
    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)?
     
    SkyChotik and Just Passing By like this.
  11. Shadowtrance

    Shadowtrance GBAtemp Addict

    Member
    2,482
    1,513
    May 9, 2014
    Hervey Bay, Queensland
    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.
     
    gamecaptor likes this.
  12. Just Passing By

    Just Passing By GBAtemp Advanced Maniac

    Member
    1,562
    594
    Jan 3, 2016
    United States
    He's talking about the
    "Initalization: partially failed
    (A to continue)"

    I think it's fine. All of the main functions should be intact.
     
    gamecaptor likes this.
  13. Shadowtrance

    Shadowtrance GBAtemp Addict

    Member
    2,482
    1,513
    May 9, 2014
    Hervey Bay, Queensland
    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 and Just Passing By like this.
  14. gamecaptor
    OP

    gamecaptor R.I.P. Densetsu. Legends never die!

    Member
    GBAtemp Patron
    gamecaptor is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    525
    281
    Jan 22, 2004
    United States
    Hyrule most of the time
    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.
     
  15. pancakes077

    pancakes077 Advanced Member

    Newcomer
    55
    2
    Mar 28, 2016
    Canada
    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.
     
    Last edited by pancakes077, Mar 31, 2016
    gamecaptor likes this.
  16. gamecaptor
    OP

    gamecaptor R.I.P. Densetsu. Legends never die!

    Member
    GBAtemp Patron
    gamecaptor is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    525
    281
    Jan 22, 2004
    United States
    Hyrule most of the time
    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!