Homebrew Why did I bother with A9LH?

[nero99]

The big one for me is that DSi games (and GBA, but I don't really use that) will just work without having to install them to both sysnand and emunand.

Not to mention you can update your sysnand to the latest update while keeping a 10.3 emunand for use with NTR. Since NTR is no longer being updated, once Ninty releases an update that breaks using the 10.2 firmware.bin you won't be able to use NTR at all.

Ntr can be used on a9lh luma sysnand on the latest update since it protects writting to firm0&1 (your 9.0 firm I believe).

 

[wormdood]

faster and perfect bootrate, and brick protection. you really should've known this before you started.

You should have researched and known full and well going in that it was going to take several hours to complete.

in all fairness noobs toss around "the guide" whenever anyone has any problems related to the 3ds . . . like it was the answer to everything, while explaining nothing about a9lh or its benefits . . . so this is not a surprise thread here . . . it was bound to come up

 

[TheCyberQuake]

in all fairness noobs toss around "the guide" whenever anyone has any problems related to the 3ds . . . like it was the answer to everything, while explaining nothing about a9lh or its benefits . . . so this is not a surprise thread here . . . it was bound to come up

While I can agree, I also feel if you are going to do something like this to your 3ds you should always research what you are doing to make sure you fully understand what it is before jumping on board and doing it. When I found a9lh I researched it for a bit to weigh the pros and cons before deciding it was something I wanted to do. IMO I prefer to know as much as I can about the hack before doing it.

 

[Damon_girl]

The only downside to A9LH (and one of the reasons I haven't done it) is the fact that you need an SD card to boot it up. And if something happens to your SD card then congrats, you have a pretty paperweight.

 

[zoogie]

The only downside to A9LH (and one of the reasons I haven't done it) is the fact that you need an SD card to boot it up. And if something happens to your SD card then congrats, you have a pretty paperweight.

That's being worked on and the solution should come soon. McDonalds soon, not gateway soon.

 

[wormdood]

That's being worked on and the solution should come soon. McDonalds soon, not gateway soon.

yeah let me know when that's done maybe I'll join the "master asshole race"

 

[TheCyberQuake]

The only downside to A9LH (and one of the reasons I haven't done it) is the fact that you need an SD card to boot it up. And if something happens to your SD card then congrats, you have a pretty paperweight.

If your SD dies all you need to do is buy a new SD and then put arm9loaderhax.bin back onto the SD along with any accompanying files (/luma/ folder for luma3DS) and then the 3ds will work perfectly fine again. Which you can simply download those files if you need them again. So only a temporary paperweight until you buy a new SD card.

Edit: At this point is there ever really a time anyone uses a 3ds without an SD? It's pretty much pointless unless you are purely using only cartridges. So for me needing an SD really isn't that big of a deal because I already constantly use an SD card, and I have several SD cards in my possession. But I mean if your SD card fails, you can just run to the store the same day to pick up an SD and have the 3ds back up and running in just a few minutes once you have the new one.

 

[gamesquest1]

well i have seen at least one thread where someone SD slot appears to have stopped working at all with any SD cards, i also had a 3DS that could not read SD cards at all, even with a new SD slot installed.....combined with a9lh = bricked, if you were using menuhax/mset it would just mean you loose cfw support but can still play all your legit carts still.........so you could probably sell the console on, not everyone cares about CFW's and would be happy to get a cheap 3DS even though it cant read SD cards, they could still get a sky3ds

 

[Thelonewolf88]

The only downside to A9LH (and one of the reasons I haven't done it) is the fact that you need an SD card to boot it up. And if something happens to your SD card then congrats, you have a pretty paperweight.

You won't. Just get a new SD card and make a new directory structure with luma and arm9loaderhax.bin on the root.

 

[nl255]

Ntr can be used on a9lh luma sysnand on the latest update since it protects writting to firm0&1 (your 9.0 firm I believe).

No, that has nothing to do with it. NTR is dependent on the kernel, or native_firm version which is stored in ctrnand not firm0/firm1. When you put firmware.bin in sd:/luma/ you are telling Luma to use the 10.2 native_firm instead of the one from 11.0. Try it sometime, go into the luma folder and rename firmware.bin to something else, then try to use NTR on 11.0.

 

[trigao]

Yes, it works now but only because Ninty's 11.0 update is still compatible with using the 10.2 firmware.bin. When 11.1 comes out most likely they will update the system menu and other modules to require 11.0/11.1 nfirm and thus NTR won't work anymore after said update. That will also break downgrading via hardmod as well.

Aaaaaa.....i think i understand now
For the same reason you can downgrade from 11.0 after a9lh instalation(you "broken" nativ_firm)
The ntr cfw works....right?

 

[nl255]

Aaaaaa.....i think i understand now
For the same reason you can downgrade from 11.0 after a9lh instalation(you "broken" nativ_firm)
The ntr cfw works....right?

No, you can downgrade from 11.0 via a9lh/luma because luma patches out the downgrade checks (as of version 5.5, if you try to downgrade 11.0 on luma 5.4 or lower it won't work and you will have to restore a nand backup). The way I understand it, the bootloader loads firm0 (or firm1 if firm0 is corrupt and then firm0/firm1 loads native_firm which then loads everything else. If you don't have firmware.bin in the luma folder, then it will load native_firm from ctrnand just like on a stock system and then patch it as it is loaded into memory. If you do have firmware.bin in the luma folder then it will load native_firm from the firmware.bin file. In other words, when you have firmware.bin in sd:/luma you are essentially running a frankenfirmware. That is, you are running 11.0 but with the 10.2 kernel. And what NTR requires is the 10.2 kernel.

 

[Phil5004]

Is it still hard to install A9LH?
And.. Is there an Updated Manual?
AND how high is the brick chance?
Mabey I going to install A9LH

 

[BADDINOROX99]

no real beneficial reason exept now you won't feel pressured to switch over to a9lh every time you ask for help or have a question

 

[Hamstermascot]

I dunno, I've heard of some people updating their emuNAND and also having sysNAND updated. That was quite a while ago, though, and I dunno how common that is now.

That happens when the Nands are linked. If you unlink them you're basicly dualbooting. If the nands are linked they're still part of eachother. Like having a virtual machine on your 3ds.

 

[Lumince]

No, you can downgrade from 11.0 via a9lh/luma because luma patches out the downgrade checks (as of version 5.5, if you try to downgrade 11.0 on luma 5.4 or lower it won't work and you will have to restore a nand backup). The way I understand it, the bootloader loads firm0 (or firm1 if firm0 is corrupt and then firm0/firm1 loads native_firm which then loads everything else. If you don't have firmware.bin in the luma folder, then it will load native_firm from ctrnand just like on a stock system and then patch it as it is loaded into memory. If you do have firmware.bin in the luma folder then it will load native_firm from the firmware.bin file. In other words, when you have firmware.bin in sd:/luma you are essentially running a frankenfirmware. That is, you are running 11.0 but with the 10.2 kernel. And what NTR requires is the 10.2 kernel.

But sadly all nintendo needs to do is make the system not boot if a lower native firm is being loaded. But there will more than likely always be a way around it as long as you have a CFW already installed.

 

[gnmmarechal]

If your SD dies all you need to do is buy a new SD and then put arm9loaderhax.bin back onto the SD along with any accompanying files (/luma/ folder for luma3DS) and then the 3ds will work perfectly fine again. Which you can simply download those files if you need them again. So only a temporary paperweight until you buy a new SD card.

Edit: At this point is there ever really a time anyone uses a 3ds without an SD? It's pretty much pointless unless you are purely using only cartridges. So for me needing an SD really isn't that big of a deal because I already constantly use an SD card, and I have several SD cards in my possession. But I mean if your SD card fails, you can just run to the store the same day to pick up an SD and have the 3ds back up and running in just a few minutes once you have the new one.

Lots of games dont let u play without a card anyway. Pokemon, SSB...

 

[Slartibartfast42]

So I went through the hassle of installing A9LH on my N3DS. What was the point of this again? Besides faster boot ups, what benefits are there? Just struggling to justify the amount of time I spent getting it to work when my emuNAND cfw worked just fine.

The main benefit is safety, stability, user experience. You are now brick proof and future proof.

 

[Dracari]

Yes, it works now but only because Ninty's 11.0 update is still compatible with using the 10.2 firmware.bin. When 11.1 comes out most likely they will update the system menu and other modules to require 11.0/11.1 nfirm and thus NTR won't work anymore after said update. That will also break downgrading via hardmod as well.

Actually if you read a bit back to the Luma3DS Nightly changes what Broke NTR in 11.0 was the Patching of svcBackdoor a Nightly while back readded this./ and i assume should a future update broke using the 10.2 Firmware.bin either NTR's devs will update or it'll be fixed in Luma.

 

[Deleted User]

That happens when the Nands are linked. If you unlink them you're basicly dualbooting. If the nands are linked they're still part of eachother. Like having a virtual machine on your 3ds.

I know, but I've also heard of people having their sysNAND update even when their NANDs are unlinked. I dunno how it happens.