Homebrew Can Arm9loaderhax be installed on New 3ds?

[ThePanchamBros]

Can it? I read that someone tried to use the tutorial on the GitHub for arm9loaderhax on a new 3ds and bricked. Can anyone confirm it works on new 3ds? Thanks

edit: when I restore my sysnand from when I backed up the original, can I also do so with my original emunand?

 

[MsMidnight]

it does, they just didnt use the emunand unbricker tool

 

[RealityNinja]

It works!

 

[Ann0ying]

There are lots of new 3ds(es?) with A9LH, mine included. If you follow the instruction chance of bricking your ds is VERY VERY VERY small.

 

[Razorzeto]

That guide say pretty much everything, it's known for being idiot proof, so read well before every step!

 

[gaga941021]

It absolutely works!

 

[KaduPSE]

It was actually first implemented on a N3DS, wasn't it?

 

[ThePanchamBros]

it does, they just didnt use the emunand unbricker tool

ok thx, so if I just follow the regular GitHub guide step by step word for word I will be fine?

 

[rileysrjay]

A9lh works fine on a new 3ds, such as mine. Just make sure you follow plaicets guide word for word or you will brick your system.

 

[Pikm]

Can it? I read that someone tried to use the tutorial on the GitHub for arm9loaderhax on a new 3ds and bricked. Can anyone confirm it works on new 3ds? Thanks

edit: when I restore my sysnand from when I backed up the original, can I also do so with my original emunand?

It's pretty much the exact same process on all systems. N3DS is just a little bit harder because the (emu)NAND becomes bricked on the 2.1.0 downgrade and you have to repair it before you flash it to sysNAND and get the otp. Honestly it would be a whole lot safer if someone developed a cfw that can boot 2.1 fw.

 

[Just Passing By]

It's pretty much the exact same process on all systems. N3DS is just a little bit harder because the (emu)NAND becomes bricked on the 2.1.0 downgrade and you have to repair it before you flash it to sysNAND and get the otp. Honestly it would be a whole lot safer if someone developed a cfw that can boot 2.1 fw.

Actually you're wrong about that. Now you don't have to repair it anymore. OTPHelper does that all for you, so the steps for n3ds and o3ds are the exact same now.

 

[Razorzeto]

It's pretty much the exact same process on all systems. N3DS is just a little bit harder because the (emu)NAND becomes bricked on the 2.1.0 downgrade and you have to repair it before you flash it to sysNAND and get the otp. Honestly it would be a whole lot safer if someone developed a cfw that can boot 2.1 fw.

One click setup it's much safer know, and does everything for you.

 

[Pikm]

Actually you're wrong about that. Now you don't have to repair it anymore. OTPHelper does that all for you, so the steps for n3ds and o3ds are the exact same now.

One click setup it's much safer know, and does everything for you.

One click setup still has to repair it though, and that adds about +10 minutes to the process.

 

[3xkrazy]

The main dev pused a major rewrite on github yesterday. It currently doesn't work with my jpn n3ds, because It fails the validation check on arm9loaderhax.pack during the installation. I even supplied it with the same dependencies from the previous version.

 

[Just Passing By]

One click setup still has to repair it though, and that adds about +10 minutes to the process.

It doesn't make it harder though and in the end it's not in anyway more dangerous then o3ds.

 

[daxtsu]

This exploit came about because of the N3DS (or rather, the way they decided to handle booting security on N3DS 9.6+), so yes it can be installed on it.

 

[zoogie]

This exploit came about because of the N3DS (or rather, the way they decided to handle booting security on N3DS 9.6+), so yes it can be installed on it.

Yeah exactly.
It's honestly a miracle it works on old3ds since you're installing new3ds firmware on it and using a new3ds exploit.

 

[Logan Pockrus]

Step for step, word for word, and you'll be fine! I did it, too!

 

[Scarlet]

Finished setting up my third N3DS for A9LH earlier, it's safe if you can follow the instructions as far as I know ^^

 

[regnad]

The main dev pused a major rewrite on github yesterday. It currently doesn't work with my jpn n3ds, because It fails the validation check on arm9loaderhax.pack during the installation. I even supplied it with the same dependencies from the previous version.

Have you told Plailect this? This sounds like a big problem he should be made aware of.

Where did it fail? Before the downgrade to 9.2 or 2.1? Did it just refuse to do the downgrade?

I downgraded a friend's JP N3DS to 9.2 (but not 2.1) the other day using the update cias on the Plailect site. Both SafeSysUpdater and the Plailect updater failed at maybe the third or fourth cia during validation, but the Plailect updater still went ahead and downgraded, and did it successfully.