Hacking Some a9lh questions

[Jiro2]

1) Part 4 section I step 10 says "Get into the Homebrew Launcher on SysNAND through the entrypoint of your choice." I have menuhax. Is it okay to get into the Homebrew Launcher by running a CFW through the Menuhax and then using yellow8's homebrew launcher, or do I have to directly run the homebrew launcher from menuhax? Would this be messed up depending on what NATIVE_FIRM the CFW uses? If so, are there particular CFWs (such as rx in Pasta mode, or AuRei with a firmware90.bin) that will work?
1a) Part 4 section II step 1 and part 5 section II step 4 say the same thing. Same question there.
2) Part 5 section 1 step 34 says "Reboot back into RedNAND and complete initial setup without signing into your Nintendo Network ID". I then have to repeat steps 29-34. Step 29 requires using the eshop. Using the eshop automatically signs into your Nintendo Network ID. Must I do something to prevent that? Or will the procedure have deleted the NNID at that point anyway?
3) Plailect's guide describes a setup where you can hold select, start, Y, or X to boot various things. Are all of these things also capable of booting through ctrbootmanager9 or are there some things that are only bootable using keys?
4) I understand that Gateway doesn't directly work with a9lh, but are there ways to indirectly use it, like booting AuReiNand with a firmware90.bin and then running Gateway on top of that?
5) How safe is a9lh against Nintendo updates? I know I can always unbrick, but the AuReiNand might still need a new firmware.bin, so I shouldn't just update whenever Nintendo has a new firmware out, right?
6) If I follow the instructions in Plailect's guide, and I copy EmuNAND to SysNAND, but I don't get rid of EmuNAND, then my EmuNAND and SysNAND will be linked, right?
7) Part 5 section II step 9 says "Your 3DS should reboot into the AuReiNand menu." If I have menuhax, will it reboot into Menuhax instead? Or will it reboot into AuReiNand because a9lh executes early in the boot process, but starting AuReiNand will then boot into Menuhax? Or would it completely skip Menuhax? Or does the process delete the Menuhax? Or do I have to manually delete the Menuhax?

 

[Docmudkipz]

1, Launching HBL through a cfw implies it will be on emuNAND, it's asking for Sysnand so go straight from menuhax

2. By not signing in in the first place it wont sign in anyway

3. A boot manager is a boot manager. Nothing is limited by keys or what not. If you like the graphical boot manager then go for it by all means

4. You'll need to either have 9.2 sysnand or emunand to use it. It won't work with a 10.7 nand

5. All of the cfws have firm0 firm1 write protection which blocks any kind of updates or modifications to them while the system is running

6. Yes

7. Menuhax doesnt work on 10.7. By the end of the guide you'll have an updated sysnand, AuReiNand will be the only thing able to run as well as any other arm9 payloads you have

 

[Jiro2]

1, Launching HBL through a cfw implies it will be on emuNAND, it's asking for Sysnand so go straight from menuhax

What? That's not true. You can run a CFW on SysNAND and have the homebrew launcher installed in it.

2. By not signing in in the first place it wont sign in anyway

I just tried going into EmuNAND, not signing in, and going to eshop. It automatically signed in without asking me first.

All of the cfws have firm0 firm1 write protection which blocks any kind of updates or modifications to them while the system is running

That wasn't my question. AuReiNand uses a firmware.bin file. If Nintendo creates a new firmware, the AuReiNand firmware.bin might not match the one that goes with the new Nintendo firmware. Will that prevent AuReiNand from booting?

Menuhax doesnt work on 10.7. By the end of the guide you'll have an updated sysnand, AuReiNand will be the only thing able to run as well as any other arm9 payloads you have

Huh? The question was about part 5 section II step 9. This step is not at the end of the guide and takes place before the 10.7 is copied to SysNAND, so it does not have 10.7 at that point.

 

[Docmudkipz]

What? That's not true. You can run a CFW on SysNAND and have the homebrew launcher installed in it.



I just tried going into EmuNAND, not signing in, and going to eshop. It automatically signed in without asking me first.



That wasn't my question. AuReiNand uses a firmware.bin file. If Nintendo creates a new firmware, the AuReiNand firmware.bin might not match the one that goes with the new Nintendo firmware. Will that prevent AuReiNand from booting?



Huh? The question was about part 5 section II step 9. This step is not at the end of the guide and takes place before the 10.7 is copied to SysNAND, so it does not have 10.7 at that point.

I was assuming you were using the cfw launched through HBL to get into emunand, that's usually how it is until you get a9lh set up I'm pretty sure. With the exception of BootCTR which is menuhax anyway.

It shouldn't be signing into anything, rather it should ask you to sign in and you just close it from there. The point of that is to initialize the databases. If its signing you into the NNID you never signed into in the first place then theres a problem

That firmware.bin is patched and the patched one is loaded. Nintendo can't touch shit on your sd card. But If native firm is patched in a new update you'll have to wait for Aurora to update it to support the new version.

AuReiNand should load first anyway. You'll be flashing the former emunand to your sysnand from which you'll be unable to access menuhax from then on.

 

[Jiro2]

It shouldn't be signing into anything, rather it should ask you to sign in and you just close it from there. The point of that is to initialize the databases. If its signing you into the NNID you never signed into in the first place then theres a problem

Right now, when I got to eshop, my 3DS automatically signs in. It does not ask me first. Does the procedure in the guide delete the saved NNID or otherwise prevent the 3DS from doing this?

Is there a missing step in the guide "if your 3DS is set up to automatically sign in with your NNID in eshop, you must turn that off"?

AuReiNand should load first anyway. You'll be flashing the former emunand to your sysnand from which you'll be unable to access menuhax from then on.

My question is about part 5 section II step 9. This step happens before flashing the EmuNAND to SysNAND. At that point, the menuhax is still there. So my question is valid.

 

[Docmudkipz]

Right now, when I got to eshop, my 3DS automatically signs in. It does not ask me first. Does the procedure in the guide delete the saved NNID or otherwise prevent the 3DS from doing this?

Is there a missing step in the guide "if your 3DS is set up to automatically sign in with your NNID in eshop, you must turn that off"?



My question is about part 5 section II step 9. This step happens before flashing the EmuNAND to SysNAND. At that point, the menuhax is still there. So my question is valid.

Tinyformat does a soft nand format, effectively deleting any and all user data. This should include any login details. If it's auto-logging you into your NNID when you open the eshop then you may be on your sysnand. Double check.

Your question is not still valid. Anything to do with A9LH loads very early in the boot process, BEFORE the system and menuhax. If you need a visual representation it goes as such: Bootrom -> A9LH -> System Initialization -> Menuhax(If installed) -> System fully booted. Menuhax is still irrelevant by this point. Even if you boot into it you're supposed to open Decrypt9 through A9LH after the initial AuReiNand setup and flash your former emunand to the sysnand while retaining A9LH

 

[nl255]

That wasn't my question. AuReiNand uses a firmware.bin file. If Nintendo creates a new firmware, the AuReiNand firmware.bin might not match the one that goes with the new Nintendo firmware. Will that prevent AuReiNand from booting?

That firmware.bin is patched and the patched one is loaded. Nintendo can't touch shit on your sd card. But If native firm is patched in a new update you'll have to wait for Aurora to update it to support the new version.

Yes, that can be a problem if Nintendo makes an update that requires a new NATIVE_FIRM but you can do what I did and turn your emunand into a 9.2 emunand with a FTP server cia installed (and anything else you want, such as the hbl cia) rather than removing emunand entirely like the guide suggests. I did it that way because I have a n3ds and didn't want to have to mess with removing the back every time there was a system update that required a new firmware.bin.