It's arm9loaderhax.binWhere is the b9sinstaller? Root, luma/payloads?
If on root, you have to rename it to boot.bin (or how is it called on a9lh). If in luma/payloads, you need to launch luma chainloader (select+power).
It's arm9loaderhax.binWhere is the b9sinstaller? Root, luma/payloads?
If on root, you have to rename it to boot.bin (or how is it called on a9lh). If in luma/payloads, you need to launch luma chainloader (select+power).
It’s in Luma/payloads. I thought it was start + power, but I just tried select + power and the same thing happened.Where is the b9sinstaller? Root, luma/payloads?
If on root, you have to rename it to boot.bin (or how is it called on a9lh). If in luma/payloads, you need to launch luma chainloader (select+power).
The chainloader is in fact start+powerIt’s in Luma/payloads. I thought it was start + power, but I just tried select + power and the same thing happened.
So since it doesn’t work, does that mean it’s a hardware problem? And if so, who could I have fix it? I’m assuming Nintendo isn’t an option because it’s hacked.The chainloader is in fact start+power
Assuming this a hardware problem and that your motherboard is intact/functioning correct, your prime suspects are the SD card reader and one [or more] of the three flex cables (top LCD, speaker, and camera).So since it doesn’t work, does that mean it’s a hardware problem? And if so, who could I have fix it? I’m assuming Nintendo isn’t an option because it’s hacked.
Damn, that really sucks, because I have absolutely no experience in taking apart electronics and am really worried I’ll permenently damage the system (if it isn’t already). As for the SD Card reader issue, is that likely to be the problem when the Luma configuration screen appears and the home menu did load a few times? I guess I could try one of those third party repair services. I’m assuming there’s no way to back up the system’s data before sending it? Also, since apparently I was supposed to create a NAND backup when I first hacked the 3DS, where would that be stored? I don’t remember doing it but maybe I did.Assuming this a hardware problem and that your motherboard is intact/functioning correct, your prime suspects are the SD card reader and one [or more] of the three flex cables (top LCD, speaker, and camera).
Other than that, it could be anyone's guess in what's wrong with it. I would try the camera one first and replace the SD reader anyway if your n3DSXL was an early batch model from 2014 ~ 2015. Use a magnify glass to look at the cables for signs of damage and check for loose connections.
- If you don't hear a popping noise, it's probably not the speaker flex cable.
- If your top LCD was working when you had access to GodMode9 and then it stopped, it may or may not be this one.
- A rarity for the 3DS systems, you can disconnect the camera as it's the one component that can cause the n3DSXL to be in a brick-like state if it fails.
***
If you have the money to get another (used but working) n3DSXL on the cheap, you can eliminate the guesswork in which of those suspected parts are bad. Swap your motherboard over to the donor n3DSXL.
Unless you have a friend (or friend of a friend) who's great with electronics and will do it pro bono, you can try commissioning at a 3rd party Apple / phone repair specialists. Be ready to pay a pretty penny and know that results might not be successful.
It’s 7.0.5.What version of luma do you have on SD and what version of luma shows up with select+power?
Yah, don't mess with tinkering electronics you aren't willing to lose. If you had your games and save data already backed up, I might have recommended giving it a shot. Your n3DSXL is relatively replaceable; personally invested data not so much.Damn, that really sucks, because I have absolutely no experience in taking apart electronics and am really worried I’ll permenently damage the system (if it isn’t already). As for the SD Card reader issue, is that likely to be the problem when the Luma configuration screen appears and the home menu did load a few times? I guess I could try one of those third party repair services. I’m assuming there’s no way to back up the system’s data before sending it? Also, since apparently I was supposed to create a NAND backup when I first hacked the 3DS, where would that be stored? I don’t remember doing it but maybe I did.
Essentially the part of the back plate next to the screw was cracked, so just a little force is all I really needed to get it off. The only problem is that a part of that cover plate is still stuck to the screw which covers the part where I need to remove the battery. If that didn’t make sense, there’s a picture.Yah, don't mess with tinkering electronics you aren't willing to lose. If you had your games and save data already backed up, I might have recommended giving it a shot. Your n3DSXL is relatively replaceable; personally invested data not so much.
By the way, how are you able to access the micro SD card but not the battery on your n3DSXL, despite the striped screws holding the bottom cover plate?
***
I'm not familiar how much different A9LH works compared to B9S.
For boot9strap CFW, it's possibly to rename any *.firm files as boot.firm and place them on the root of the SD card.
Edit #2 - This allows you to launch something else other than Luma3DS.
I am hesitant to suggest trying the same for A9LH CFW on this for *.bin files, renaming GodMode9.bin or even SafeB9SInstaller.bin as arm9loaderhax.bin doing the same thing.
***
Edit #1 - Forgot to add, there's no way to backup your games as *.cia and later recover your encrypted save data unless you have access to GodMode9 to dump those games.
The file that controls encrypting the saves is retrieved at:
- [1:] SYSNAND CTRNAND/private/movable.sed <-VERY IMPORTANT if you game saves weren't backed up with a save manager.