Hello,
I am following this Part 1-5 guide: https://github.com/Plailect/Guide/wiki/
However, my situation does not line up with the A9LH setup guide.
My Old 3DS XL has sysNAND firmware 4.3.0-10U, and I'd have to upgrade to 9.2.0 using a newer Super Smash Bros. 3DS cartridge (I already dumped the cartridge, and checked its actual firmware with Crappy Tiny Reader; it is indeed 9.2.0.) So, the first question I have is; Will 9.2.0-10U (old browser version) be a working substitute for 9.2.0-20U?
The next problem is the Gateway-created emuNAND. The emuNAND has some important data that I definitely do want to keep. Would this emuNAND be compatible with the tools and be treated like a normal emuNAND? I have already extracted this emuNAND to a BIN file and would like to know if A9LH would work properly once this emuNAND is A9LH-modified and flashed to the sysNAND.
If necessary, please point out any issues that could arise, along with a solution (if any).
Thanks,
Andrew21
I am following this Part 1-5 guide: https://github.com/Plailect/Guide/wiki/
However, my situation does not line up with the A9LH setup guide.
My Old 3DS XL has sysNAND firmware 4.3.0-10U, and I'd have to upgrade to 9.2.0 using a newer Super Smash Bros. 3DS cartridge (I already dumped the cartridge, and checked its actual firmware with Crappy Tiny Reader; it is indeed 9.2.0.) So, the first question I have is; Will 9.2.0-10U (old browser version) be a working substitute for 9.2.0-20U?
The next problem is the Gateway-created emuNAND. The emuNAND has some important data that I definitely do want to keep. Would this emuNAND be compatible with the tools and be treated like a normal emuNAND? I have already extracted this emuNAND to a BIN file and would like to know if A9LH would work properly once this emuNAND is A9LH-modified and flashed to the sysNAND.
If necessary, please point out any issues that could arise, along with a solution (if any).
Thanks,
Andrew21