Hacking a9lh boot rate not 100%

  • Thread starter Thread starter cots
  • Start date Start date
  • Views Views 8,494
  • Replies Replies 67
just wiping over the SD contacts or just re-seating it is always worth a try. a wonky insert can have glitchy connection for whatever reason with some cards.
 
You have 3... no, 6 possible causes. From most likely to least likely:

1.- User error
2.- Fragmented NAND
3.- Bad files
4.- SD card files not "cleaned up" after a9lh installation
5.- Defective SD Card, dirty contacts &/or botched soldering job on the mobo showing up just now
6.- Defective Nintendo 3DS™ system
 
  • Like
Reactions: G25900 and Queno138
Last edited by ZaMaster,
The only time my n3ds with A9LH didn't boot is when I bricked it messing with the home menu system files (twice) :D

I've yet to see someone who hasn't a 100% boot rate with a perfect SD card.
 
That's certainly user error. Try doing a system format .
Did you even changed themes to destroy menuhax?
 
If i had a dollar for every computer or electrical product ive had arrive new doa i could build another computer.
 
Although, if they are using A9LH SysNand CFW, all they need to do is perform a system update and it'll overwrite any issues the previous downgrading might've had! (Just make sure that you have the NTR firmware.bin in your /luma/ folder)

Just curious, why is the NTR firmware.bin needed in the luma folder before updating? Is that what blocks native firm overwriting (or whatever)?
 
Thanks, but that didnt answer my question. Or at least I dont think it did lol
Actually, that's exactly it: firmware.bin contains NATIVE_FIRM, so we "emulate" an older version from the sd card to substitute in for your actual NATIVE_FIRM. Because it's outdated (9.2), it lets us take advantage of some exploits which otherwise wouldn't have been possible, such as running NTRCFW or downgrading the system version. (There's probably more to it, but that's about the extent of my knowledge on this...)
 
Actually, that's exactly it: firmware.bin contains NATIVE_FIRM, so we "emulate" an older version from the sd card to substitute in for your actual NATIVE_FIRM. Because it's outdated (9.2), it lets us take advantage of some exploits which otherwise wouldn't have been possible, such as running NTRCFW or downgrading the system version. (There's probably more to it, but that's about the extent of my knowledge on this...)


Ah ok. I just assumed by ur post earlier that its "needed" in the luma folder before updating a9lh sysnand. Like shit could go wrong if it iSnt.
 
Ah ok. I just assumed by ur post earlier that its "needed" in the luma folder before updating a9lh sysnand. Like shit could go wrong if it iSnt.
Downgrading could potentially go wrong without it, yes, although it isn't really permanent if you're downgrading EmuNand and already have an EmuNand backup.
 
Ah ok. I just assumed by ur post earlier that its "needed" in the luma folder before updating a9lh sysnand. Like shit could go wrong if it iSnt.
It is also worth nothing that apps only read the VersionMajor and VersionMinor, not the VersionRevision numbers. This influences what CrispyYoshi basically said "running things we could otherwise not run"
 
  • Like
Reactions: FTRBND
Okay, so I got a new SD card and I have the same problem - about 1/3rd of the time when I power on the 3DS I watch the bottom screen power up with no Wifi light and then I get a black screen. I did find a work around. I boot holding START then exit the app using START and the bootrate is 100%. I wonder why I can't just turn on the N3DS with a9lh. Weird problem.
 
Okay, so I got a new SD card and I have the same problem - about 1/3rd of the time when I power on the 3DS I watch the bottom screen power up with no Wifi light and then I get a black screen. I did find a work around. I boot holding START then exit the app using START and the bootrate is 100%. I wonder why I can't just turn on the N3DS with a9lh. Weird problem.

If you have the option, you may want to try replacing the SD reader itself. It's probably the most painless hardware swap possible on N3DS XL (one ZIF cable after cover removed).

It could also be an "inrush current" causing a failure with the SD reader. Having that slight delay via start may be just enough to allow the system's electrical to stabilize, or the SD reader to stabilize, or ...
 

Site & Scene News

Popular threads in this forum