Alright good to hear. I uninstalled it. Just a few more things I can clear off of my SD card nowUninstall menuhax. If you got A9L up and running, you don't need that anymore.
Alright good to hear. I uninstalled it. Just a few more things I can clear off of my SD card nowUninstall menuhax. If you got A9L up and running, you don't need that anymore.
put a splash.bin in your rei folderI 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 .
Only ways to get OTP are downgrade to 2.1 or a hardware attack on N3DS (downgrade works on either)So there is no way to get my OTP without messing with my sysnand with decrypt9?
Are there high chances of bricking when downgrading to 2.1 on an old 3DS?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")
Odds of bricking are pretty low, but they're still their. Follow the guide carefully and at you're on risk.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.Are there high chances of bricking when downgrading to 2.1 on an old 3DS?
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.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.
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.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.
so do i rename installer.bin to arm9loaderhax.bin or just copy over the files and boot normaly?it's named arm9loaderhax.bin, so just copy it and boot the console, you'll be greeted with a menu, just follow the instructions there and you'll be good to go
Rename the file to arm9loaderhax.bin.so do i rename installer.bin to arm9loaderhax.bin or just copy over the files and boot normaly?
cheers lol i just found it hereRename the file to arm9loaderhax.bin.
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.
If you're using (Au)ReiNAND then just place a splash.bin file into the /rei/ folder that's on your SD card.how can we create custom boot screen for the latest 0.2 a9lh bootloader?