Okay i finally got my emunand updated and nands unlinked. Can I link my Nintendo ID now?
Yes, link your NNID in your emunand.
Okay i finally got my emunand updated and nands unlinked. Can I link my Nintendo ID now?
What if i would need to unlink just follow the same steps?Yes, link your NNID in your emunand.
What if i would need to unlink just follow the same steps?
10.4 is safe in emunand? for 2ds o3ds and o3dsxl?
yes and thats the firmware i updated my emunand to like 20 hours ago. it shows 10.4 in system settings too.10.4 came out Monday
What if i would need to unlink just follow the same steps?
unllinking nands and linking/unlinking nnid are different things, you shouldn't have any need to unlink nnid againWhat if i would need to unlink just follow the same steps?
i think fbi does support some kind of networking install, which lets you use wireless to send the cia data while the game installs, so you don't have to two times space problem. but you need stable wifi and it generally takes longer.Is there a way to get around the "Need twice the space the .cia uses to install" thing? My SD card is merely 4gb, but EmuNAND+RxTools lower my total space to 2.6 gb, so i cannot install any game 1.3+ gb.
Ive been unable to find an answer to this question that wasn't dated late 2014, so I'm wondering if the situation has changed.
Is there any way to prevent eShop/badge arcade/any Nintendo connection from deleting installed dlc? I've got the mii plaza games in .CIA form and every day, the badge arcade uninstall them. Not necessarily a big deal, but tedious to install them again all the time.
Cheers,
Ace
Fair enough, just thought I'd check! Thanks for the quick reply!nope. connecting to these services checks your tickets and stuff (cfw usually makes it so the system ignores them, but nintendo servers still do their thing), and you dont have the right tickets so it voids them. sadly, there's no way around that yet
Anyone else familiar with this problem?Hey, so I got CFW working on my 9.2 emuNAND, all fine and dandy. But when I update my emuNAND to 10.3 via SysUpdater, or 10.4 via Nintendo's official method, and my 3DS freezes after a seconds when I boot up my emuNAND. An error message then pops up asking me to turn it off, and rebooting it does the same thing over and over again. Only way to fix this is injecting my emuNAND.bin into the SDcard. What am I doing wrong? This is a Japanese n3DS btw.
not sure but weren't n3ds' supposed to stay away from anything higher than 9.5 on emunand?Anyone else familiar with this problem?
EDIT: Never mind I fixed it, had to turn off the wifi and get the tubehax DNS on for some reason???
not sure but weren't n3ds' supposed to stay away from anything higher than 9.5 on emunand?
Do I just use sysUpdater to update to 9.2, or do I need to find one of those 9.2 Smash 3DS carts?OK, I got my n3DS XL downgraded, but what about 3DS systems below 9.2? Do they need to be updated? If so, how?
Here's my group's updated list of 3DS systems:
n3DS XL: 9.0.0-20U sysNAND, 4GB SDHC (never hacked)
n3DS XL: 9.2.0-20U sysNAND, 4GB SDHC (downgraded from 10.3.0-28U, sysNAND backed up, emuNAND not set up yet)
o3DS XL: 6.0.0-11U sysNAND, 4GB SDHC (never hacked)
o3DS XL: 4.3.0-10U sysNAND, 9.2.0-20U emuNAND, 16GB SDHC (Gateway only)
o3DS XL: 4.5.0-10U sysNAND, 9.4.0-21U emuNAND, 4GB SDHC (Gateway only)
o3DS XL: 9.2.0-20U sysNAND, 4GB SDHC (never hacked)
o3DS: 9.2.0-20U sysNAND, 2GB SDHC (never hacked)
o3DS: 3.0.0-6U sysNAND, 2GB SDHC (never hacked)
o3DS: 7.1.0-15U sysNAND, 2GB SDHC (never hacked)
o3DS: 9.2.0-20U sysNAND, 2GB SDHC (never hacked)
o3DS: 4.5.0-9U sysNAND, 2GB SDHC (never hacked)
o3DS: 4.5.0-10U sysNAND, 2GB SDHC (never hacked)
What should be done with the 3.0, 6.0, 7.1, and 9.0 systems? 4.3, 4.5, and 9.2 are fine as-is, right?
What's better to have on sysNAND, 4.3 or 9.2? How would I update to 9.2?
I have a copy of Paper Mario: Sticker Star that updates to 4.3, but I don't own a copy of Smash with 9.2 on it.