Change all mentions of sysNAND to emuNAND, and you should be fine.
However, it won't work if this a second emuNAND on that same SD Card, if I recall from other people posting.
Follow all the steps as mentioned, with the word EmuNAND, and do all of the actions on your EmuNAND. Is that more clear?so I don't need to inject SecureInfo_A to my emuNAND? is the emuNAND able to detect SecureInfo_A from sysNAND ?
Follow all the steps as mentioned, with the word EmuNAND, and do all of the actions on your EmuNAND. Is that more clear?
If it tells you to "Navigate to SYSNAND CTRNAND -> rw -> sys"
Pretend it says "Navigate to EMUNAND CTRNAND -> rw -> sys"
And so on and so forth.
Yes u can. I did it successfully. Just carry some common sense, remember that you have to do everything with EmuNAND, and u shall be fine.
yeah that's goodeven if something go wrong with sysNAND I have tons of backups to restore it via Hourglass9 lol (Thanks A9HL )
Not sure if GW CFW does any signature patching. You basically need a CFW that does signature patching on SecureInfo_A for it to work. Luma3DS does it on A, but it will default to C if it sees that file, that way you can leave the SecureInfo_A untoched with Luma3DS. Since it'll use C, and patch that and use that.I can't boot my new US emuNAND in Gateway mod !! But it works fine with Luma3DS
I thought it was because I've edit SecureInfo_C and maybe Gateway didn't read any SecureInfo_X file other that SecureInfo_A .. so I edited the SecureInfo_A to match the emunand region the same way as SecureInfo_C ..
But still black screen in Gateway mod
Any thoughts?
Thanks
Not sure if GW CFW does any signature patching. You basically need a CFW that does signature patching on SecureInfo_A for it to work. Luma3DS does it on A, but it will default to C if it sees that file, that way you can leave the SecureInfo_A untoched with Luma3DS. Since it'll use C, and patch that and use that.
Not sure if GW CFW does any signature patching. You basically need a CFW that does signature patching on SecureInfo_A for it to work. Luma3DS does it on A, but it will default to C if it sees that file, that way you can leave the SecureInfo_A untoched with Luma3DS. Since it'll use C, and patch that and use that.
Should work. Though I've never done it. Doesn't hurt to try though.If I used a doner US SecureInfo_A from that iso site (shouldn't be modified so it wouldn't need any signature patching right?) So, should this works?
Should work. Though I've never done it. Doesn't hurt to try though.
hmm...I have plan to do it and now am searching for some information and found this thread.
But after finishing Plailect's tutorial, I failed to get into emunand by running HBL icon on home screen and trying to run Luma3DS.
I also cannot enter emunand via cubix ninja.
any suggestion?
3DS is on hacked sysnand v11.
hold select while booting to access Luma configuring menu
uncheck
Now you should boot to emuNAND
- "Autoboot SysNAND"