The method is the same as other tutorials: 1) Use GW or Injected FBI to install Sysupdater on SysNAND 2) Upgrade 9.2 CIA by Sysupdater in Devmode But unlike other SysNANDs, 1) 7.0 - 8.1 don't have MSET exploit so they can't be booted by 414 method 2) Suffix -4 to -6 don't have - CakeHax Browser access - Ninjhax 1.X access - GW DG access so they can't be - booted by Browser on CakeHax based CFW like rxTools 3.X - booted by Ninjhax 1.X - performed a downgrade 3) JPN doesn't provide any 9.0 - 9.2 cartridge so they can't have any safe HBL access directly That is to say, only GW and non-CakeHax based CFW's Browser entrypoint are available on those 7.0.0-4J to 8.1.0-6J consoles. So, with all the disabilities listed above, the last hope for 7.0.0-4J to 8.1.0-6J to upgrade to 9.2 is the rxTools 2.5.2's Devmode. But has anybody tested it? -------- BTW, there was a rumour that - Upgrade emuNAND to 9.2.0-20J - GW DG emuNAND to 4.4.0-10J - Inject emuNAND 4.4.0-10J to SysNAND might work, but also untested. -------- BTW-2, O3DS 7.0.0-0J - 8.1.0-1J are incompletely DEAD, since - no browser exist - no Ninjhax 1.X & no GW/CFW Browser access - no MSET exploit - no 9.0 - 9.2 cartridge - no Ninjhax 2.X - the latest OS is no longer 10.3 so it can't upgrade then downgrade (regularly) There's only one option for those 7.0.0-0J to 8.1.0-1J: - Upgrade to 10.5 - Hard-backup 10.5 SysNAND - Inject 10.2 NATIVE_FIRM to 10.5 SysNAND and flash it back - Perform a 10.2 - 9.2 downgrade -------- Q: How come the f**king weird 7.0.0-0J to 8.1.0-6J SysNAND appear? A: That's because some people upgrade their 3DSes by cartridge without reading any sticky. They don't even know suffix -0 to -6 are lacking exploits & supports.