It should be. It booted fine before trying to inject my emunand copy into my sysnand. Even the chainloader worked fine.Make sure you put boot.firm of Luma3DS at the root of your SD/microSD card. Otherwise it won't boot.
It should be. It booted fine before trying to inject my emunand copy into my sysnand. Even the chainloader worked fine.
What is even weird is that only my legit cias are the only ones to show on my home menu, everything else seems to be lost.
Decrypt9Wip.firm chainloaded from luma. I restored a copy of my emunand i did yesterday with the same tool but with its .3dsx format.Which tool and version did you use to restore your emunand into your sysnand?
Maybe. I downloaded the lastest release that is supposed to support sighax. Once i was into decrypt9 i used the option to restore to sysnand (but not the one that says keep a9lh since i never had a9lh). The process seemed to go fine until it rebooted without showing luma pin lock feature.Maybe you used the option to overwrite your b9 or an old version that keeps your a9lh but not a b9... But if you cannot boot the luma config and you can only see your legit cias... I would say you don't have a9lh nor b9 anymore
That might've been your downfall not choosing the keep a9lh option.Maybe. I downloaded the lastest release that is supposed to support sighax. Once i was into decrypt9 i used the option to restore to sysnand (but not the one that says keep a9lh since i never had a9lh). The process seemed to go fine until it rebooted without showing luma pin lock feature.
So, am i screwed after all?
Welp...That might've been your downfall not choosing the keep a9lh option.
At least i feel like i did something good, this way people wont do the stupid shit i just did.You may need to follow the guide from the beginning.
Maybe d0ke should add a "keep sighax" option or something like that, or if the a9lh would have done the job
That's uncalled for and completely unnecessary.That's what you get for still using an EmuNAND!
It was just an user error from my part. Emunand was and is fine, i just screwed up when i restored it without keeping a9lh.That's what you get for still using an EmuNAND!
But is it? SysNAND CFW has been a thing for a long time!That's uncalled for and completely unnecessary.
But is it? SysNAND CFW has been a thing for a long time!
I'm curious, what happens if you boot without a SD card?It was just an user error from my part. Emunand was and is fine, i just screwed up when i restored it without keeping a9lh.
And just what are you trying to say?And say has using an emuNAND.
And just what are you trying to say?