Alright, this is interesting.
Upon receiving a Streetpass this morning on emuNAND, I attempted to enter the plaza. I get error code 009-8401 that says "The update data is corrupted." It wants me to go into data management and delete the update data, but I haven't yet (I was under the impression that visiting data management wiped out your .cias). If I hit OK, the plaza prompts me to re-download the software update data. Hitting yes brings me back to that same error screen, and I'm then kicked back to the home menu. What's that all about?
And I'm still getting an error upon trying to enter the eShop or Miiverse. Thinking it's something NNID related, but when I visit NNID Settings it kicks me back to sysNAND.
Is there a more centralized "Newbish Gateway Owner Questions" thread?
Data Management in SysNAND will wipe out your CIAs if you haven't unlinked. It's not a problem in EmuNAND. Maybe something's going on with your SD card since it says the update's corrupt. You could try backing everything up (including the EmuNAND via EmuNAND Tool), formatting with HP USB format utility, throw the launcher back on, format EmuNAND again, delete the new "Nintendo 3DS" folder, copy the old one back, inject your EmuNAND back, and see if that helps.
Is there any chance there is a fix for the black screens that appear when loading Classic mode through the 9.2 exploit?
I dont hace a GW cart, but it gives you the option to load without a red cart but leads to two black screens
Classic Mode will not boot without the Gateway card on NANDs (Sys or Emu) running firmware 8.x or higher I think (it may be 7.x). They probably should update that so that it checks the NAND and if the version's too high it just tells you to forget about it like Gateway mode does.
You can't. I also have a N3ds on 8.1-0-0J and it won't let me open the browser without a update or whatever the fuck it says because I can't read it. We N3ds users are in a bad spot right now if gateway can't fix the Mii exploit problem then we wasted money even buying the system. I would buy a sky3ds if you got the money because we might have a very long wait or if garyopa is right then next week I'm trying to keep my hopes up but when 2.0 was in beta it took forever for the final release
I have an Australian N3DS. My browser does work. It's still not exploitable. It's not a case of the Mii exploit needing fixed. It's working fine by all accounts. They deliberately didn't release it because they don't want people trying Ultra on the N3DS yet. Probably because EmuNAND is still not quite working right with firmware New 9.4 (not to be confused with firmware 9.4). The apps installed are quite different. If you could get into the browser, like I can, you would see that it looks very different from the normal 3DS browser. Firmware New 9.4 makes far more changes to the system than firmware 9.4 does. It turns on Amiibo access for example. This is probably why beta testers that had the Mii exploit were saying there was no EmuNAND.
Have a look at the files UpdateCDN uses in the 9.2 update alone (since I had to replace my bricked 3DS XL, I wanted to get it a 9.2 for the sake of completeness). Everything in the "9.0.0-20-stage2" folder is an N3DS-exclusive version of something. Kind-of strange that they would even have those for the US version, with the US version of the N3DS not even existing yet (though maybe it does if you're a developer).
Why not buy a Sky3DS if you're impatient? I did. No regrets. Zelda: ALBW was much better without the ghost images. You can always use it to run Ninjhax (since my N3DS is Australian, I'd need 2 Cubic Ninja carts to avoid the need for extra SD cards running EmuNAND 9.2). You can also use it to upgrade systems to 4.5 (especially useful with the downgrade going to 4.2), any future game exploit you won't be scrambling to get the game, and you can always hand it to a friend for some multi-player (you don't have worry about what firmware they're on either).
Now, about that aforementioned brick, can anyone with a hard mod try unlinking, and then restoring the linked NAND via the d-pad up + Downgrade option? I'd rather not end up with a second brick so soon, and I can't find any differences in the files EmuNAND Tool and the Gateway NAND dumper make, so I'm starting to think it bricked because real SysNAND can't be restored to a wiped profile (the system that bricked was unlinked from the profile the EmuNAND I tried to restore by renaming it to NAND.BIN used).