Hacking Does anyone know the controls for aurienand a9lh?

[funnystory]

Would anyone be so kind as to share the list of button controls for a9lh? I am looking for a way to check to make sure the options are as I want them.I heard about a user bricking his n3ds by updating through sysnand although I think he was on cakes and I just want to make sure everything is good.

 

[Halvorsen]

With no updatedsysnand flag
---------
Holding L - load sysnand using firm90 (for 9.2 firmwares, will lock and freeze on sysnands >9.2)
Holding R - load sysnand
idle - load emunand.
---------
Updated sysnand mode
---------
L - load emunand 9.2 with firm90. Read above.
R - load emunand.
idle - load sysnand.
--------
AuReiNAND mod
--------
L - Load your first emunand, using firm90 if necessary.
R - Load second emunand
idle - load sysnand.

 

[funnystory]

With no updatedsysnand flag
---------
Holding L - load sysnand using firm90 (for 9.2 firmwares, will lock and freeze on sysnands >9.2)
Holding R - load sysnand
idle - load emunand.
---------
Updated sysnand mode
---------
L - load emunand 9.2 with firm90. Read above.
R - load emunand.
idle - load sysnand.
--------
AuReiNAND mod
--------
L - Load your first emunand, using firm90 if necessary.
R - Load second emunand
idle - load sysnand.

I want to make sure the sysnand updates box is ticked,how do I go into the aureinand menu?

 

[Deleted User]

Hold select when booting/powering on.

If you're only using updatedsysNAND, just check the first 2 and leave Force A9LH Detection off.

 

[funnystory]

Hold select when booting/powering on.

If you're only using updatedsysNAND, just check the first 2 and leave Force A9LH Detection off.

what does a9lh detection do

All 3 were checked even though I only checked 2 during the setup

If any of these get unchecked can i get a brick??

 

[Deleted User]

No. If you check the wrong ones it just wouldn't boot or give an error. Not a brick by any means.

In any case, might want to read through the AuRei thread to get more familiar with the CFW as a lot of questions are answered in the OP.

Settings:
These can be set in a menu which appears when the configuration file is missing, or if you hold SELECT on startup.
"Force A9LH detection": If, for some reason, you want to use the non-A9LH version of the CFW (the .dat + .3dsx from HBL) after booting with the 9.0 FIRM on Arm9LoaderHax, you can force A9LH behavior with this setting. It's not needed otherwise.
"Use pre-patched FIRMs": If you wish to have a slightly faster boot at the expense of up to 3 MBs of SD space, you can enable this setting.
"Updated SysNAND mode": Switches to "updated SysNAND mode", as described above.

 

[funnystory]

No. If you check the wrong ones it just wouldn't boot or give an error. Not a brick by any means.

In any case, might want to read through the AuRei thread to get more familiar with the CFW as a lot of questions are answered in the OP.

Settings:
These can be set in a menu which appears when the configuration file is missing, or if you hold SELECT on startup.
"Force A9LH detection": If, for some reason, you want to use the non-A9LH version of the CFW (the .dat + .3dsx from HBL) after booting with the 9.0 FIRM on Arm9LoaderHax, you can force A9LH behavior with this setting. It's not needed otherwise.
"Use pre-patched FIRMs": If you wish to have a slightly faster boot at the expense of up to 3 MBs of SD space, you can enable this setting.
"Updated SysNAND mode": Switches to "updated SysNAND mode", as described above.

I just read it I am a bit unclear though.

"Updated sysNAND" mode:
- For this, you need A9LH (it has no effect otherwise). You can toggle it in the configuration menu.
- Normally sysNAND is autobooted.
- If you hold L on boot, emuNAND will be booted with the 9.0 FIRM (firmware90.bin) so you can use exploits (you need to create a 9.0/9.2 emuNAND for this!). Please note that you can't have two 9.0 emuNANDs, and that the 9.0 emuNAND must be the first (or theonly) one.
- If you hold R on boot, emuNAND will be booted with the firmware.bin on the SD card. Also holding B boots the second emuNAND (if present). This has no effect if you only have one emuNAND.


I am failing to comprehend what updated sysnandmode does,if this was unchecked what would unupdated sysnand do?

 

[Deleted User]

By default (if you checked absolutely nothing) turning on your unit would boot straight to emuNAND. [which if you're using updatedsysNAND you wouldn't have = black screen]

By checking updated sysNAND, the system now auto-boots to sysNAND instead of emuNAND if you touch nothing. [with firm0/firm1 patches applied]
If on updated sysNAND you for some reason wanted a emuNAND, holding L when it's chekced means it'll boot emuNAND with 9.0 firm (e.g. you wanted to use gateway))
Holding R would boot whatever firm (mostly 10.4 at this point), and if you had dual emuNANDS, holding B with R would boot the second emuNAND.

For someone who's just using sysNAND only, just check updated sysNAND/Use Pre-patched firms and be done with it.

As to reiterate the top, if you didn't check UpdatedSysNAND and tried to boot, it would just boot your emuNAND. If you didn't have an emuNAND, it would either error out, or just hang on a black screen.

Actually here's a better line straight from the thread about what happens when nothing is checked:

Regular mode:
- Normally emuNAND is autobooted. Holding B boots the second emuNAND (if present). This has no effect if you only have one emuNAND.
- If you hold R on boot, sysNAND will be booted with the firmware.bin on the SD card.
- You can boot SysNAND with the 9.0 FIRM. To do this hold L on boot. If you're not using A9LH and your console (O3DS) is not on 9.x, it will be detected and it will output an error.

 

[funnystory]

By default (if you checked absolutely nothing) turning on your unit would boot straight to emuNAND. [which if you're using updatedsysNAND you wouldn't have = black screen]

By checking updated sysNAND, the system now auto-boots to sysNAND instead of emuNAND if you touch nothing. [with firm0/firm1 patches applied]
If on updated sysNAND you for some reason wanted a emuNAND, holding L when it's chekced means it'll boot emuNAND with 9.0 firm (e.g. you wanted to use gateway))
Holding R would boot whatever firm (mostly 10.4 at this point), and if you had dual emuNANDS, holding B with R would boot the second emuNAND.

For someone who's just using sysNAND only, just check updated sysNAND/Use Pre-patched firms and be done with it.

As to reiterate the top, if you didn't check UpdatedSysNAND and tried to boot, it would just boot your emuNAND. If you didn't have an emuNAND, it would either error out, or just hang on a black screen.

Actually here's a better line straight from the thread about what happens when nothing is checked:

Regular mode:
- Normally emuNAND is autobooted. Holding B boots the second emuNAND (if present). This has no effect if you only have one emuNAND.
- If you hold R on boot, sysNAND will be booted with the firmware.bin on the SD card.
- You can boot SysNAND with the 9.0 FIRM. To do this hold L on boot. If you're not using A9LH and your console (O3DS) is not on 9.x, it will be detected and it will output an error.

I am pretty sure it is booting to sysnand and that I cloned emunand to my sysnand. Is there anyway to be absolutely positive to check that I am indeed on sysnand? Also as long as I maintain my current setup I can update with the update feature on my console correct? I saw a user go through the bad luck of bricking his console accidently(although he used cakes instead of aurienand.

 

[mutinize]

I am pretty sure it is booting to sysnand and that I cloned emunand to my sysnand. Is there anyway to be absolutely positive to check that I am indeed on sysnand? Also as long as I maintain my current setup I can update with the update feature on my console correct? I saw a user go through the bad luck of bricking his console accidently(although he used cakes instead of aurienand.

If your nands are unlinked you can try making a folder on one and see if the folder is there in the other nand. Otherwise you can go into settings and I think AuReiNand puts something in front of the system version (RXTools = Rx 9.2.0, ReiNand = Rei 9.2.0, Gateway = GW 9.2.0, not specific but going from memory). I have Au but I'm using a FAT32 64GB card so unfortunately I don't have that flag on my emu.

 

[funnystory]

If your nands are unlinked you can try making a folder on one and see if the folder is there in the other nand. Otherwise you can go into settings and I think AuReiNand puts something in front of the system version (RXTools = Rx 9.2.0, ReiNand = Rei 9.2.0, Gateway = GW 9.2.0, not specific but going from memory). I have Au but I'm using a FAT32 64GB card so unfortunately I don't have that flag on my emu.

Thing is I think i deleted emunand lol.

 

[Cuphat]

There shouldn't be any danger of bricking the console through updating - but there is the possibility that a future update would not be bootable through your current CFW without an update to the CFW. So, if you are worried about a firmware update, make a sysNAND backup so you can restore it if it isn't working. The beauty of A9LH is it lets you boot directly to Decrypt9 even if the actual system software won't boot. Keep backups handy, you never know when one might be useful for you.

 

[funnystory]

There shouldn't be any danger of bricking the console through updating - but there is the possibility that a future update would not be bootable through your current CFW without an update to the CFW. So, if you are worried about a firmware update, make a sysNAND backup so you can restore it if it isn't working. The beauty of A9LH is it lets you boot directly to Decrypt9 even if the actual system software won't boot. Keep backups handy, you never know when one might be useful for you.

can't nintendo overwrite the a9lh hack though?

 

[astronautlevel]

can't nintendo overwrite the a9lh hack though?

Not with FIRM0/1 protection

 

[Cuphat]

can't nintendo overwrite the a9lh hack though?

I think they'd need to exploit their own kernel to do that. Like, I'd never rule out the possibility, but it is unlikely. It never hurts to wait a few hours and let everyone else try it out first, though.

 

[dg_dex]

There shouldn't be any danger of bricking the console through updating - but there is the possibility that a future update would not be bootable through your current CFW without an update to the CFW. So, if you are worried about a firmware update, make a sysNAND backup so you can restore it if it isn't working. The beauty of A9LH is it lets you boot directly to Decrypt9 even if the actual system software won't boot. Keep backups handy, you never know when one might be useful for you.

Don't I know it. I was forced to restore my nand due to making some major mistakes after running this Aurora's CFW. I made the mistake of not having an emunand on 9.2. I only had a GW backup. Of course the headers are different. Luckily I had made a backup with A9LH on 9.2. I created an emunand from that and then ran GW through emunand to restore my clean 9.2 sysnand. What a headache that was. Backups are must have through Decrypt9 when anyone who attempts A9LH. Good tip.

 

[funnystory]

Don't I know it. I was forced to restore my nand due to making some major mistakes after running this Aurora's CFW. I made the mistake of not having an emunand on 9.2. I only had a GW backup. Of course the headers are different. Luckily I had made a backup with A9LH on 9.2. I created an emunand from that and then ran GW through emunand to restore my clean 9.2 sysnand. What a headache that was. Backups are must have through Decrypt9 when anyone who attempts A9LH. Good tip.

my emunand was on 10.7 and i injected the patitions onto my 9.2 and it works fine. You think i fucked up?

 

[astronautlevel]

my emunand was on 10.7 and i injected the patitions onto my 9.2 and it works fine. You think i fucked up?

Nope, should be good.

 

[funnystory]

Nope, should be good.

You know anyway to make sure I am really on sysnand? I am pretty sure I deleted emunand as I cant access it with L+R like i used to be able to but I really have no way of checking.

If all is good how come @dg_dex made a brick?

 

[astronautlevel]

You know anyway to make sure I am really on sysnand? I am pretty sure I deleted emunand as I cant access it with L+R like i used to be able to but I really have no way of checking.

If all is good how come @dg_dex made a brick?

Look at your SD card in a partition manager and see if there's 1-2 gigs of unallocated space in the beginning.

Not sure, probably user error. Dumping the partitions and injecting them should be fine, never heard of any problems with it as long as you don't touch FIRM0/1