Hacking Is CFW / Arm9loaderhax a perma hack?

[tombi]

I cannot find any information if "Arm9loaderhax" or any other solution for CFW is a perm hack. Can it be revert back to the "normal" state of a 3DS? Always?

 

[zoogie]

I cannot find any information if "Arm9loaderhax" or any other solution for CFW is a perm hack. Can it be revert back to the "normal" state of a 3DS? Always?

Yes and yes and yes, if you have a hardmod.

 

[Vappy]

It's permanent for as long as you choose to have it. You can revert to stock by just restoring a NAND dump from before you installed it.

 

[tombi]

Okay. So I need to have a backup. That is okay for me. As long as I am on version 9.2 of SysNAND I am always able to use my backup, right?

Another question: Can you say me how I will be able to switch between SysNAND and EmuNAND after I have done everything? Or will I always automatically boot into EmuNAND? When and how can I boot into my normal SysNAND if I ever would need it? And what will happen if I don't insert my SD card?

I really cannot find any quick information how booting works with CFW, maybe I have missed something in the guides.

 

[Skyshadow101]

Yes, as long as you don't update your Sysnand in any way, you should be good.

To switch between Emunand and Sysnand, use this guide here.

If you have the latest update of A9LH, you can take out the SD and boot up the console, it will still work.

 

[Deleted member 370671]

Yes and yes and yes, if you have a hardmod.

Yes for the last one even if you don't have a hardmod, with ar9safeinstaller 2.0.

 

[zoogie]

Yes for the last one even if you don't have a hardmod, with ar9safeinstaller 2.0.

It's still very possible to brick an a9lh system although it's certainly less likely than ordinary cfw. (if stage1 is corrupt, for instance)

 

[Deleted-379826]

Okay. So I need to have a backup. That is okay for me. As long as I am on version 9.2 of SysNAND I am always able to use my backup, right?

Another question: Can you say me how I will be able to switch between SysNAND and EmuNAND after I have done everything? Or will I always automatically boot into EmuNAND? When and how can I boot into my normal SysNAND if I ever would need it? And what will happen if I don't insert my SD card?

I really cannot find any quick information how booting works with CFW, maybe I have missed something in the guides.

Everything can be on sysnand

 

[gnmmarechal]

It's permanent for as long as you choose to have it. You can revert to stock by just restoring a NAND dump from before you installed it.

EDIT: Never mind

 

[Deleted member 370671]

uh, pretty sure restoring a NAND backup doesn't affect the A9LH installation with Hourglass9 at the very least.

If you restore the backup with Decrypt9, you can choose to restore it "completely" or to restore it while keeping A9LH.

 

[Tephie]

If you restore the backup with Decrypt9, you can choose to restore it "completely" or to restore it while keeping A9LH.

Interesting

 

[ishygdaft]

Yes, as long as you don't update your Sysnand in any way, you should be good.

To switch between Emunand and Sysnand, use this guide here.

If you have the latest update of A9LH, you can take out the SD and boot up the console, it will still work.

Booting without an SD? Since when?

 

[Deleted member 370671]

Booting without an SD? Since when?

The latest safea9lhinstaller installs a mini CFW that will be used if no SD card / arm9loaderhax.bin file is found.

 

[ishygdaft]

The latest safea9lhinstaller installs a mini CFW that will be used if no SD card / arm9loaderhax.bin file is found.

Really? Neat! I'm using version 2.1, could you point me to this newer version? Sounds really handy if, say, the SD card breaks or the card reader craps out.

 

[gnmmarechal]

Really? Neat! I'm using version 2.1, could you point me to this newer version? Sounds really handy if, say, the SD card breaks or the card reader craps out.

https://www.reddit.com/r/3dshacks/c...hts_arm9loaderhax_fork_updated_merges/d4htime

 

[ishygdaft]

https://www.reddit.com/r/3dshacks/c...hts_arm9loaderhax_fork_updated_merges/d4htime

Thank you. I was looking in aurora's git and originally didn't see any mention of it, seems like the kind of improvement you'd want to show off more.

 

[tombi]

So do I understand correctly that I can install a CFW with A9LH by this guide (is it the best guide?) and then I will have a device that will automatically boot everytime from SD card or if it has been removed it will boot into a "mini CFW" from SysNAND and it will never easily boot into my 9.2 SysNAND ?

I still cannot find information how booting into the "original" SysNAND will work afterwards. I will normally always automatically boot into my EmuNAND from SD card, right?

I also didn't find information how to just use SysNAND for CFW and not EmuNAND (is it recommended? if yes, how can I do it?).

Of course I will create a backup of my SysNAND before I will start. (What guide is perfect to do this?)

 

[ishygdaft]

So do I understand correctly that I can install a CFW with A9LH by this guide (is it the best guide?) and then I will have a device that will automatically boot everytime from SD card or if it has been removed it will boot into a "mini CFW" from SysNAND and it will never easily boot into my 9.2 SysNAND ?

I still cannot find information how booting into the "original" SysNAND will work afterwards. I will normally always automatically boot into my EmuNAND from SD card, right?

I also didn't find information how to just use SysNAND for CFW and not EmuNAND (is it recommended? if yes, how can I do it?).

Of course I will create a backup of my SysNAND before I will start. (What guide is perfect to do this?)

The guide will have you use sysnand only if you install a9lh, emunand is still an option. If you use Luma, you can hold L on boot and it'll boot you into sysnand.
With Luma's chain payload loading you should be able to boot a nand management tool that'll make having an emunand moot, considering that if you brick you can just load one of said tools to recover a back up (but not in ALL cases)
As for sysnand only, you can switch your emunand and sysnand (should be detailed in the guide).

 

[ishygdaft]

wrong thread~

 

[tombi]

I have read a lot of times that users are bricking their devices once they downgrade to 2.1. I am a little bit afraid about this. Is there a high chance to brick it currently?

I will buy a new "New Nintendo 3ds XL" tomorrow. It will have a default version of around 9.9 - 10.5 I think. So i will downgrade it to 9.2 and afterwards do the other stuff, like downgrading to 2.1 (as it says in the guide). Do you think it is safe for me to do it on a fresh device directly with the guide?

Or are the 2.1 bricks only because users do it wrong?