Homebrew ARM9Loader -- Technical Details and Discussion

  • Thread starter Thread starter Selver
  • Start date Start date
  • Views Views 584,611
  • Replies Replies 4,025
  • Likes Likes 42
I feel silly asking this .

How do I check that the arm9loaderhax.3dsx of dark_samus has been successfully installed over the old version?

I have the last aureinand but dont see any screen when I turn the 3DS .
 
So there is no way to get my OTP without messing with my sysnand with decrypt9? :unsure:
Only ways to get OTP are downgrade to 2.1 or a hardware attack on N3DS (downgrade works on either)
Read the OTP guide for more information on either of these (the hardware attack is mentioned in "Abstract")
 
Only ways to get OTP are downgrade to 2.1 or a hardware attack on N3DS (downgrade works on either)
Read the OTP guide for more information on either of these (the hardware attack is mentioned in "Abstract")
Are there high chances of bricking when downgrading to 2.1 on an old 3DS?
 
Are there high chances of bricking when downgrading to 2.1 on an old 3DS?
If you follow the guide exactly, the chances of bricking are extremely low.
Technically, a 2.1 downgrade does brick due to encryption changes, but that's why it's done on EmuNAND with the encryption swapped on PC before restoring.

You're in more danger installing A9LH itself than you are getting the OTP, IMO.
 
No matter what I do, the Hold R option does nothing for me on boot but hang on a black screen. Everything else works, L for sysNAND (patched), nothing for emuNAND, and A for decrypt9. Isnt holding R supposed to at least load the sysNAND under a different FIRM?? Im a perfectionist and this is driving me crazy.

Info: 9.2 sysNAND, 10.6 emuNAND with a9lh and the v0.2 version of the a9lh bootloader.
 
No matter what I do, the Hold R option does nothing for me on boot but hang on a black screen. Everything else works, L for sysNAND (patched), nothing for emuNAND, and A for decrypt9. Isnt holding R supposed to at least load the sysNAND under a different FIRM?? Im a perfectionist and this is driving me crazy.

Info: 9.2 sysNAND, 10.6 emuNAND with a9lh and the v0.2 version of the a9lh bootloader.
Holding R to boot a NAND with 9.2 doesn't seem to work, since it's trying to boot a 10.x FIRM on a lower firmware. This is my guess, at least.
 
Holding R to boot a NAND with 9.2 doesn't seem to work, since it's trying to boot a 10.x FIRM on a lower firmware. This is my guess, at least.
Thats what I figured was the problem (limited/growing knowledge about all of this), but I just wasnt sure. If that is the case, then I guess its not even something I need to worry about at the moment. That would make sense why it just hangs on a black screen then because I can tell its trying to load SOMETHING otherwise the backlight wouldnt come on.

So as long as nothing is wrong with my setup and it simply SHOULDNT be loading anything when I press R then I am content for now. I was just worried that I was missing SOME tiny fact and it was driving me crazy.

Cant wait until launching directly into the HBL via a9lh is possible.
 
No matter what I do, the Hold R option does nothing for me on boot but hang on a black screen. Everything else works, L for sysNAND (patched), nothing for emuNAND, and A for decrypt9. Isnt holding R supposed to at least load the sysNAND under a different FIRM?? Im a perfectionist and this is driving me crazy.

Info: 9.2 sysNAND, 10.6 emuNAND with a9lh and the v0.2 version of the a9lh bootloader.

This is the same problem I'm having and although it isn't needed, I can't wait for a fix.
 
So is there a directory of what CFW/Payloads that are available currently and what they do or have to offer.
 
  • Like
Reactions: Naked_Snake

Site & Scene News

Popular threads in this forum