Hmm, the OP says the update blocks menuhax so it's a bit confusing.nothing will happen to sysnand, so you won't lose menuhax/a9hl/etc
Thanks for the fast reply.
Hmm, the OP says the update blocks menuhax so it's a bit confusing.nothing will happen to sysnand, so you won't lose menuhax/a9hl/etc
10.6 does block menuhax, but that doesn't mean your 9.2 or lower sysnand has lost exploits.Hmm, the OP says the update blocks menuhax so it's a bit confusing.
Thanks for the fast reply.
Can you explain exactly what A9LH lets you do, compared to a normal CFW? So can you update your system whenever you want, whichever way you want (through Settings, eShop, or whatever), on sysNAND, and unsigned stuff will still work? Or is it purely just the same as using CFW except faster to boot (so still with emuNANDs etc and if sysNAND is updated past 9.2 then it will no longer work)?That's one reason I stick with emuNAND, even though I have A9LH. The only real advantage right now in switching to sysNAND entirely is no more double DSiWare and GBA installs. That and maybe ever so slightly faster load times into NAND.
Can you explain exactly what A9LH lets you do, compared to a normal CFW? So can you update your system whenever you want, whichever way you want (through Settings, eShop, or whatever), on sysNAND, and unsigned stuff will still work? Or is it purely just the same as using CFW except faster to boot (so still with emuNANDs etc and if sysNAND is updated past 9.2 then it will no longer work)?
I couldn;t find any threads explaining, maybe because the people with enough knowledge to get A9LH working already know what it's good for, and the plebs who aren't going to do it don't need to know![]()
Wow, that's great! Thanks for replying. Why do people bother with emuNANDs then? I guess to protect against installing anything corrupted?Basically A9LH gives you Arm9 Kernel right at boot, before the FIRMs are decrypted. This provides full privileges on Sysnand regardless of system version, 100% and faster boot rate for Emunand, and even brick recovery. I believe, when it's fully developed, you might be able to update Sysnand however you want safely.
Yeah, besides that, at this point you cannot boot your 3ds without the SD card inserted with a firmware.bin already in it.Wow, that's great! Thanks for replying. Why do people bother with emuNANDs then? I guess to protect against installing anything corrupted?
So if I update my rx tools in emuNAND to 10.6, nothing is going to happen and not cancel menuhax, my only way to launch homebrew in sysNAND 9.2? ThanksUpdating emunand is safe, because updating your emunand does nothing to affect what happens on sysnand, and sysnand is where your menuhax lives.
Correct. Sysnand is sysnand and emunand is emunand. They're basically 2 separate consoles that just so happen to live on the same hardware.So if I update my rx tools in emuNAND to 10.6, nothing is going to happen and not cancel menuhax, my only way to launch homebrew in sysNAND 9.2? Thanks
Thanks, will try to update laterCorrect. Sysnand is sysnand and emunand is emunand. They're basically 2 separate consoles that just so happen to live on the same hardware.
So if I update my rx tools in emuNAND to 10.6, nothing is going to happen and not cancel menuhax, my only way to launch homebrew in sysNAND 9.2? Thanks
Yes it does.10.6 emunand not working on new 3ds xl with gateway 3.7.1
Well, menuhax still worked AFAIK and that was fixed with this update.If they did this update means that someone has found a few hacks to 10.5?![]()
And of course my dumbass friend who was using menuhax updated even tho I told him not to -_-
They have for quite a while now... (10.6 still worked right out of the box. No GW update required).Gateway dont even support 10.5 or 10.6 yet
mabey because the fucking boot loader uses the .3dx files not the cia to boot? its not that fucking hard to figure out manHi I'm a little confuzzled on 2 probably simple things. I updated the hbl.cia in emunand and it now loads 2.6 but opening hbl from the boot manager still loads 2.5. I'm using grid launcher and have it renamed to bhbl because a tutorial I followed to set up cfw said to, so I had to edit the path of hbl.cia to bhbl to get it working.
Also when turning on the 3ds right before boot manager starts it flashes the text 2.5 beta. Will that always be normal or should it say 2.6 or something...
There's no need to insult those who have ASD...man this site is overridden with autism
i really dont get all the griping about them calling it stability updates when they literally fix vulnerabilities in their code, thus preventing unstable and exploitable states.
the fact that no one would happen on those instabilities just by chance doesn't change that it's literally what they do.