Hacking How do i remove a9lh?

[Awesomeslayerg]

Lets say sometime in the future i would like to remove a9lh because something happened.. How would i do it?

 

[matpower]

You need to restore your pre-A9LH backup AFAIK.

 

[Lumince]

Why would you want to remove this? It literally is the best thing to happen to 3ds's. And if you screw it up and brick it, it loads before the nand anyways so brick protection? Why remove that?

 

[FenrirWolf]

Alternatively you can boot a cfw that doesn't block FIRM writes and use sysupdater to downgrade your sysnand (from 9.2 to 9.0, for example). That would get you a normal FIRM0/FIRM1 again.

 

[ihaveahax]

Alternatively you can boot a cfw that doesn't block FIRM writes and use sysupdater to downgrade your sysnand (from 9.2 to 9.0, for example). That would get you a normal FIRM0/FIRM1 again.

if using New3DS, the corrupted key would still be there though, so you couldn't go back to 9.6+ sysnand unless you fix it, or use arm9loaderhax again, right?

 

[FenrirWolf]

if using New3DS, the corrupted key would still be there though, so you couldn't go back to 9.6+ sysnand unless you fix it, or use arm9loaderhax again, right?

That's a good question actually. Maybe I haven't thought my clever plan all the way through.

 

[gameking66]

You don't even need to do any of this. Just install your system's NATIVE_FIRM CIA to NAND with FIRM write patches disabled.

 

[AnukWolf]

You don't even need to do any of this. Just install your system's NATIVE_FIRM CIA to NAND with FIRM write patches disabled.

Kind of an unrelated question though: It's said everywhere that AuReiNand for instance protects the FIRM0/FIRM1 from being overwritten. So what if the OTA update from Nintendo just fails if it cant write to the FIRM partitions? Would we need some kind of patched update (or install it manually minus the NATIVE_FIRM) every time there is one available? Would we ever be able to update NATIVE_FIRM again?

 

[FenrirWolf]

Kind of an unrelated question though: It's said everywhere that AuReiNand for instance protects the FIRM0/FIRM1 from being overwritten. So what if the OTA update from Nintendo just fails if it cant write to the FIRM partitions? Would we need some kind of patched update (or install it manually minus the NATIVE_FIRM) every time there is one available? Would we ever be able to update NATIVE_FIRM again?

When you use a9lh, both your sysnand and emunand are externally firmlaunched. That's why you have firmware.bin and firmware90.bin on your SD card. If a future update comes out that requires a new NATIVE_FIRM, all you'd have to do is get the firmware.bin and replace the one on your card.

 

[AnukWolf]

When you use a9lh, both your sysnand and emunand are externally firmlaunched. That's why you have firmware.bin and firmware90.bin on your SD card. If a future update comes out that requires a new NATIVE_FIRM, all you'd have to do is get the firmware.bin and replace the one on your card.

Aaah, it all makes sense now Thanks!

 

[gameking66]

Kind of an unrelated question though: It's said everywhere that AuReiNand for instance protects the FIRM0/FIRM1 from being overwritten. So what if the OTA update from Nintendo just fails if it cant write to the FIRM partitions? Would we need some kind of patched update (or install it manually minus the NATIVE_FIRM) every time there is one available? Would we ever be able to update NATIVE_FIRM again?

FIRM writes are patched entirely and they're basically ignored even when done through official updates. Your 3DS will be unaffected and can update just fine.

 

[Ronhero]

You can't remove A9lh....Blood in blood out fam

 

[VinsCool]

You can't remove A9lh....Blood in blood out fam

Even if we could, I don't want to remove it anymore!

 

[Ronhero]

Even if we could, I don't want to remove it anymore!

Exactly but I couldn't help myself hahaha

 

[AppleSeeder]

You don't even need to do any of this. Just install your system's NATIVE_FIRM CIA to NAND with FIRM write patches disabled.

So if wanted to re-dump my OTP.bin (I mistakenly deleted all the backup files including this unique .bin file), I can just install NATIVE_FIRM from the corresponding firmware to roll back to official firmware, then follow Pailect's Guide and start over from Downgrading? My N3DS currenlty runs 10.7.0 and I have got oot3dhax as entrypoint.

 

[Queno138]

So if wanted to re-dump my OTP.bin (I mistakenly deleted all the backup files including this unique .bin file), I can just install NATIVE_FIRM from the corresponding firmware to roll back to official firmware, then follow Pailect's Guide and start over from Downgrading? My N3DS currenlty runs 10.7.0 and I have got oot3dhax as entrypoint.

As long as you have your 9.0-9.2 nand backup (of the same 3ds), you could use decrypt9 to restore the nand to sysnand.

Afterwards, basically follow phailect's guide.


And seriously.
Don't ever lose the OTP or the original nand.
(Or any nand backups, for that matter)

 

[AppleSeeder]

As long as you have your 9.0-9.2 nand backup (of the same 3ds), you could use decrypt9 to restore the nand to sysnand.

Afterwards, basically follow phailect's guide.


And seriously.
Don't ever lose the OTP or the original nand.
(Or any nand backups, for that matter)

Thanks for your prompt reply. Unfortunately, I said in my post that all the backup files were mistakenly deleted. I suppose @gameking66 's response would work for me?

 

[Queno138]

Thanks for your prompt reply. Unfortunately, I said in my post that all the backup files were mistakenly deleted. I suppose @gameking66 's response would work for me?

Welp.

Okay, if I'm not mistaken, he's talking about updating to firm right.

I think you may wanna ensure your present A9LH nand is on 9.0-9.2
(maybe create an emunand, downgrade it in emunand using plaisysupdater, ensure it works, then flash it over to your sysnand and pray it doesn't brick)


You could very well easily write to firm, but the issue in my mind is whether would you still be on a exploitable firmware.


Edit:

Weird idea,
Does downgrading A9LH sysNAND to 2.1 allows one to get their OTP?

Also, always back up before doing anything crazy.

 

[AppleSeeder]

Welp.

Okay, if I'm not mistaken, he's talking about updating to firm right.

I think you may wanna ensure your present A9LH nand is on 9.0-9.2
(maybe create an emunand, downgrade it in emunand using plaisysupdater, ensure it works, then flash it over to your sysnand and pray it doesn't brick)


You could very well easily write to firm, but the issue in my mind is whether would you still be on a exploitable firmware.


Edit:

Weird idea,
Does downgrading A9LH sysNAND to 2.1 allows one to get their OTP?

Also, always back up before doing anything crazy.

My console currently runs on updated sysNAND+CakesFW and I am thinking to replace it with Luma3DS. The problem is changing CFW to Luma would require placing OTP.bin in the luma folder.
I do not know whether downgrade updated sysNAND to 2.1 would work at all, so my plan is to restore everything to completely official firmware (10.7.0), then just start over from the beginning, treating it as a unmodded console.

 

[Kafke]

And seriously.
Don't ever lose the OTP or the original nand.
(Or any nand backups, for that matter)

I'm really bad at this. I have like 30 different NAND backups all over the place with really crappy labels/foldernames. Makes matters worse when you're trying to keep O3DS/N3DS separate. For A9LH stuff I just made a folder "NAND BACKUPS 9.2/10.7 BEFORE/AFTER AL9H", have the files appended with original/a9lh respectively, and a readme describing the state of each and which to restore if things go screwy. It's too important to get confused. I also have the OTP in there.