- Joined
- Jan 13, 2015
- Messages
- 3,825
- Trophies
- 1
- Location
- The State of Denial
- Website
- gbatemp.net
- XP
- 5,666
- Country
I'll give that a try. It would make sense if the system redownloads the update everytime it goes to sleep, assuming that you didn't update because of a bad download.When Nintendo pushes a new FW update, try putting your 3ds into sleep mode(with WIFI on) about 5-10 sec and open it
I got rid of my JPN N3DS emunand's update nag using this method. I don't know how exactly it works
but I guess this deletes the existing update files and abort downloading new updates before it finishes.
i don't think it redownloads the update every time you go into sleep, that will us a huge amount of data in the end. i think it tchecks first if there is a new update available.I'll give that a try. It would make sense if the system redownloads the update everytime it goes to sleep, assuming that you didn't update because of a bad download.
i do, im on O3ds, gateway, 9.0 sysnand, 9.7 emunand.Why not just update? Your sysNAND is safe as long as you're sure that you're in your emuNAND.
Edit: Just realized that you might not have an O3DS.
i do, im on O3ds, gateway, 9.0 sysnand, 9.7 emunand.
yeah, I think i'm just going to update. I've been waiting to see if anyone reports any issues with 9.8 before i do, but it seems to be kosher at this point.
I thought there was a way to extract the NAND filesystem, mount the NAND filesystem on a PC, and manually delete the update and then restore. Not sure where the thread is for this now (if it even existed). Also, this seems like a lot of work for something that will just happen again and again.
There is also the safe-mode boot, but I've never heard that works with emuNAND nor do I think it would work.
How are you monitoring your network activity? Is it within your router, or do you have some 3rd party program? I looked in my router and I feel comfortable in saying that that feature is not available to mine (Actiontec MI242WR)I can attest to the above, though in my case, I needed to wait a bit more than 5-10s. I found it fixes once it contacts the updatecdn server, in my case I just watched my access logs and the second updatecdn showed up, I disabled the wifi, and now my nag is gone.