Wait so, if I hardmod my 3DS and install Arm9loaderHax this means I can use CFW on sysNAND in the latest FW and completely get rid of emuNAND?
Yes.
Wait so, if I hardmod my 3DS and install Arm9loaderHax this means I can use CFW on sysNAND in the latest FW and completely get rid of emuNAND?
Well yes, that's the whole point of going to A9LH; to get rid of emuNAND and use sysNAND with patches without going through some timetaking steps (for eg. autoboot menuhax works when sysNAND is about to show home menu, then has to run the exploit and then start the whole process again to boot patched sysNAND or emuNAND).Wait so, if I hardmod my 3DS and install Arm9loaderHax this means I can use CFW on sysNAND in the latest FW and completely get rid of emuNAND?
The point of emuNAND is twofold in that it allows you to have CFW access on lates FW which can't be done on sysNAND, while also being able to interact with the NAND easier, hardmod takes care of 2nd issue, but 1st issue still requires emuNAND.
Ahh ok, I understand that part. So, the updated sequence would be:1-2-3 will bring you an updated system with no way of reinstalling A9LH. You have to just setup ReiNand now and do the things you mentioned (you can use Decrypt9 if you boot SysNAND with 9.0 FIRM with L+R, until you turn the updatedsysnand flag on).
Copy the contents of the emunand Nintendo 3DS folder to sysnand Nintendo 3DS folder
Ah, so they would effectively be linked nands again? (Not that this matters as I would be deleting the emunand partition once this was all done).That would be an unnecessary step I think, since your sysNAND would then be using the movable.sed from emuNAND (meaning it'd automatically use your emuNAND's 3DS folder).
Ah, so they would effectively be linked nands again? (Not that this matters as I would be deleting the emunand partition once this was all done).
Great, thanks buddy. I'm going to try this now with a spare microSD card, and I'll write up a tutorial as I go in case others want to migrate from emunand to sysnand. I'll credit everyone who helped in this thread as I would really be writing up what you all helped me to do anywayCorrect. They'd be one and the same, as if you had just made a fresh emuNAND.
thank you, i would be interested in thisGreat, thanks buddy. I'm going to try this now with a spare microSD card, and I'll write up a tutorial as I go in case others want to migrate from emunand to sysnand. I'll credit everyone who helped in this thread as I would really be writing up what you all helped me to do anyway
Ah, so they would effectively be linked nands again? (Not that this matters as I would be deleting the emunand partition once this was all done).
Great idea. So I'm essentially swapping sysnand and emunandBest to keep emunand and downgrade it to 9.2 after unlinking. You'll need it for running firmware 9.0 apps.
So basically sysnand and emunand get flipped.
Great idea. So I'm essentially swapping sysnand and emunand
Would I downgrade it the same way you would a sysnand downgrade, using sysupdater?Yep. Things like Decrypt9 can only run on firmware 9.0.
Would I downgrade it the same way you would a sysnand downgrade, using sysupdater?
Actually regular one does ,just compile it with the newest commit addedRegular ReiNand won't, but https://gbatemp.net/threads/reinand-mod-o3ds-n3ds-sysnand.411110/ this will.
Although I think you actually need to downgrade emunand via sysupdater to 9.2 before injecting anyway.
You mean for when he goes to inject emuNAND partitions to sysNAND? That shouldn't be necessary, I don't think.
Nah if he wants to inject sysnand into emunand to 1:1 mirror his current sysnand/emunand.
Unless I missed something, ReiNand removed sysNAND mode, and also still needs the splashscreen commented out to work with a9lhax.Actually regular one does ,just compile it with the newest commit added
Unless I missed something, ReiNand removed sysNAND mode, and also still needs the splashscreen commented out to work with a9lhax.