Homebrew ARM9Loader -- Technical Details and Discussion

[sj33]

If we want to update our A9LH to be able to use new features such as screen init, do we have to reinstall the actual A9LH itself? Or just recompile some files and add them to SD?

 

[Aroth]

Well this is wonderful....

I got a9lh working on my O3DS, mostly just messing around to test stuff out and decide if it was worth the trouble on my N3DS.

For the most part everything seems to work well enough, but decrypt9 is basically fucked for me atm.

I am aware the a9lh version is gutted atm and only works for basic dumping and injection, so I figured I could load into sysnand (on 9.2) and boot up the .3dsx version for the other stuff like decryption and H&S dumping and injection (which seems broken on the a9lh version atm). Unfortunately it doesn't work at all for me. It flashes a red screen twice and loads back into the HBL. I suspect this is because the only way I have atm to load into sysnand is by directing AuReiNand to load sysnand instead of emunand, but firmlaunch means it is using the 2.50-x firm which breaks decrypt9.

Anyone know of a way to simply bypass cfw altogether and load sysnand without firmlaunch? Otherwise a9lh is useless for me since it would prevent me from using the features of decrypt9 I primarily use.

 

[Hakujou]

Well this is wonderful....

I got a9lh working on my O3DS, mostly just messing around to test stuff out and decide if it was worth the trouble on my N3DS.

For the most part everything seems to work well enough, but decrypt9 is basically fucked for me atm.

I am aware the a9lh version is gutted atm and only works for basic dumping and injection, so I figured I could load into sysnand (on 9.2) and boot up the .3dsx version for the other stuff like decryption and H&S dumping and injection (which seems broken on the a9lh version atm). Unfortunately it doesn't work at all for me. It flashes a red screen twice and loads back into the HBL. I suspect this is because the only way I have atm to load into sysnand is by directing AuReiNand to load sysnand instead of emunand, but firmlaunch means it is using the 2.50-x firm which breaks decrypt9.

Anyone know of a way to simply bypass cfw altogether and load sysnand without firmlaunch? Otherwise a9lh is useless for me since it would prevent me from using the features of decrypt9 I primarily use.

AuReiNAND can boot SysNAND using firmware90.bin, and Decrypt9 works perfectly with it.

But I have to admit that a way to go to "vanilla" SysNAND would be great.

 

[dark_samus3]

Well this is wonderful....

I got a9lh working on my O3DS, mostly just messing around to test stuff out and decide if it was worth the trouble on my N3DS.

For the most part everything seems to work well enough, but decrypt9 is basically fucked for me atm.

I am aware the a9lh version is gutted atm and only works for basic dumping and injection, so I figured I could load into sysnand (on 9.2) and boot up the .3dsx version for the other stuff like decryption and H&S dumping and injection (which seems broken on the a9lh version atm). Unfortunately it doesn't work at all for me. It flashes a red screen twice and loads back into the HBL. I suspect this is because the only way I have atm to load into sysnand is by directing AuReiNand to load sysnand instead of emunand, but firmlaunch means it is using the 2.50-x firm which breaks decrypt9.

Anyone know of a way to simply bypass cfw altogether and load sysnand without firmlaunch? Otherwise a9lh is useless for me since it would prevent me from using the features of decrypt9 I primarily use.

with AuReiNAND hold L and A to boot into 9.0 firm with reboot patches disabled, run d9, profit

 

[RednaxelaNnamtra]

If we want to update our A9LH to be able to use new features such as screen init, do we have to reinstall the actual A9LH itself? Or just recompile some files and add them to SD?

you could use my bootloader(Bootctr9), the newest version is able to initialize the screen by itself. Or you could use dark samus updater to update the payload on nand.

 

[sj33]

Thanks. The screen init was just an example, my question was really about how to keep A9LH updated. I'll look into Dark Samus' updater.

 

[dark_samus3]

Thanks. The screen init was just an example, my question was really about how to keep A9LH updated. I'll look into Dark Samus' updater.

Here you are

https://gbatemp.net/attachments/installer-zip.40687/

 

[Hakujou]

Here you are

https://gbatemp.net/attachments/installer-zip.40687/

It doesn't include the latest commits (today's ones), right ?
Do you plan to release another updater ? (Otherwise it's not a big deal, arm9loaderhax is not very long to compile/install)

 

[dark_samus3]

It doesn't include the latest commits (today's ones), right ?
Do you plan to release another updater ? (Otherwise it's not a big deal, arm9loaderhax is not very long to compile/install)

No it doesn't, but one isn't really a big deal and the other is only for during compile

 

[Hakujou]

No it doesn't, but one isn't really a big deal and the other is only for during compile

I agree, I just like to keep my things updated ^^
Will compile it again tonight, no problem

 

[fr3quency]

with AuReiNAND hold L and A to boot into 9.0 firm with reboot patches disabled, run d9, profit

So with different button combinations, we can load older/newer FIRMs? What's the purpose? Can't we have a CFW on sysNAND with 10.6 firm(or whichever was the latest one)?

 

[dark_samus3]

So with different button combinations, we can load older/newer FIRMs? What's the purpose? Can't we have a CFW on sysNAND with 10.6 firm(or whichever was the latest one)?

running brahma payloads, which require <9.3 firm

 

[RednaxelaNnamtra]

Here is a dev Build of my bootloader with the option to disable the splashscreen, filelogging and screen logging.
For file and screen login simply set the Values("fileLog","screenLog") in the "GLOBAL" section to 0.

For splashscreen settings set splash to 0 for disableling or 1(or higher) for enableling(global or for the payload).
The current default setting for the splash is 0 and for both loggin option 1.

 

[fr3quency]

running brahma payloads, which require <9.3 firm

So if we choose to boot 10.6 FIRM, we will boot the vanilla sysNAND whereas if we choose to boot <9.3 FIRM, we will load a CFW? Don't specific games(.CIA always) require a higher FIRM version?

 

[dark_samus3]

So if we choose to boot 10.6 FIRM, we will boot the vanilla sysNAND whereas if we choose to boot <9.3 FIRM, we will load a CFW? Don't specific games(.CIA always) require a higher FIRM version?

No, the firmware is patched before being launched, so it is still custom... you just can't launch something like Decrypt9 once booted into that state, I personally have a 9.2 emuNAND that I use with the 9.0 firm for booting D9, since the emuNAND patch doesn't affect it

 

[fr3quency]

No, the firmware is patched before being launched, so it is still custom... you just can't launch something like Decrypt9 once booted into that state, I personally have a 9.2 emuNAND that I use with the 9.0 firm for booting D9, since the emuNAND patch doesn't affect it

And what's the benefit of having a CFW on sysNAND(other than GB games). Can't it get bricked if something goes wrong or if you install a shit .CIA?

Sorry man, I'm trying to understand the whole philosophy. I appreciate your posts and help.

 

[dark_samus3]

And what's the benefit of having a CFW on sysNAND(other than GB games). Can't it get bricked if something goes wrong or if you install a shit .CIA?

Sorry man, I'm trying to understand the whole philosophy. I appreciate your posts and help.

it's fine... yes it can still get bricked, but since we can launch arm9payloads on boot though, we just load up decrypt9 from there, restore NAND and call it a day... however decrypt9's crypto functions don't work due to a firm never being booted and never setting up the needed info

 

[fr3quency]

it's fine... yes it can still get bricked, but since we can launch arm9payloads on boot though, we just load up decrypt9 from there, restore NAND and call it a day... however decrypt9's crypto functions don't work due to a firm never being booted and never setting up the needed info

So we CAN restore the NAND.bin if something goes wrong. What are the Decrypt9's crypto functions for though? If we can already restore a NAND.bin(by lauching arm9payloads on boot as you said), what do we needs those crypto functions for?

 

[dark_samus3]

So we CAN restore the NAND.bin if something goes wrong. What are the Decrypt9's crypto functions for though? If we can already restore a NAND.bin(by lauching arm9payloads on boot as you said), what do we needs those crypto functions for?

well we could then get rid of 9.2 emuNAND, and just always have the latest sysNAND... crypto functions are things like making xorpads, decrypting CTRNAND, injecting health and safety, etc.

 

[fr3quency]

well we could then get rid of 9.2 emuNAND, and just always have the latest sysNAND... crypto functions are things like making xorpads, decrypting CTRNAND, injecting health and safety, etc.

I really thank you for your posts.

So now I follow these guides in the order I specify(?):
1)https://github.com/Plailect/OTP/blob/master/Old_3DS_Spider.md (I have and Old 3DS XL WITHOUT Cubic Ninja)
2)http://gbatemp.net/threads/how-to-compile-and-install-arm9loaderhax.415776/
3)http://gbatemp.net/threads/tutorial-swap-sysnand-and-emunand-arm9loaderhax-only.415724/