Hello! I have a little big problem: I have a friend with an Old 3DSXL with RX Tools, he updated his emuNAND and got black screen. The thing is I didn't know what to do, so I found a video which explains how to solve the problem, and that was, as a matter of fact, an A9LH instalation with restauration of emuNAND. Step by step, we did everything we saw in the video. This was:
- Quit SD from 3DS, backup all data and boot into sysNAND (w/o SD), then erase all files (NO FORMATTING!) and put only a pack that was linked to the video, which were arm9.bin, arm9loaderhax.bin, arm11.bin, DEcrypt9.wip, and the folders "files9", "a9lh" and "luma". (I remember that a9lh or files9 had all the files like firm0, firm1, and all that stuff... If you need more detail on this, I could explain more)
- Turn on 3DS with SD and load Decrypt9 from browser
- Do "Auto CTRnand transfer" with D9 and, at the same time, a NAND backup
- Quit SD, erase "Nintendo 3DS" folder
- In 3DS with SD, boot SafeA9LHInstaller from browser and install
- Turn off console, boot recovery menu w/Start and boot Hourglass9
- Make emuNAND backup, and then inject it on SysNAND
- Format SD (FAT32, of course, with fat32format from cmd), put everything of the original emuNAND along the arm9loaderhax.bin and the "luma" folder w/payloads
The main problem, and what I've had open this thread, is because now in the sysNAND there's NOTHING, absolutely nothing from the old emuNAND, although it is in 11.3. What could've been wrong? It was the Nintendo 3DS folder? Because that's the only thing that comes to my mind, since emuNAND was always in the hidden partition. I really can't figure the problem, nor find anything similar on web... I'll be glad if you help me and my friend. Thank you and good night!! (well, at least here is night time, lol)
- Quit SD from 3DS, backup all data and boot into sysNAND (w/o SD), then erase all files (NO FORMATTING!) and put only a pack that was linked to the video, which were arm9.bin, arm9loaderhax.bin, arm11.bin, DEcrypt9.wip, and the folders "files9", "a9lh" and "luma". (I remember that a9lh or files9 had all the files like firm0, firm1, and all that stuff... If you need more detail on this, I could explain more)
- Turn on 3DS with SD and load Decrypt9 from browser
- Do "Auto CTRnand transfer" with D9 and, at the same time, a NAND backup
- Quit SD, erase "Nintendo 3DS" folder
- In 3DS with SD, boot SafeA9LHInstaller from browser and install
- Turn off console, boot recovery menu w/Start and boot Hourglass9
- Make emuNAND backup, and then inject it on SysNAND
- Format SD (FAT32, of course, with fat32format from cmd), put everything of the original emuNAND along the arm9loaderhax.bin and the "luma" folder w/payloads
The main problem, and what I've had open this thread, is because now in the sysNAND there's NOTHING, absolutely nothing from the old emuNAND, although it is in 11.3. What could've been wrong? It was the Nintendo 3DS folder? Because that's the only thing that comes to my mind, since emuNAND was always in the hidden partition. I really can't figure the problem, nor find anything similar on web... I'll be glad if you help me and my friend. Thank you and good night!! (well, at least here is night time, lol)