- Joined
- Aug 6, 2017
- Messages
- 19,244
- Solutions
- 7
- Reaction score
- 10,211
- Trophies
- 2
- Age
- 32
- Location
- New York City
- XP
- 14,111
- Country

If you used the AIO tool, then it probably installed some type of bloat. Delete your /atmosphere folder and download a fresh one from the official GitHub page.Not that I know of. I was wondering if maybe it was either sys modules that had been installed OR the "graphics enhancing cheats" available on all in one downloader?
Did you have file or partition based emuMMC?Can somebody help me? I had a working emuMMC on my hacked switch with firmware 16.0.2, when I saw that a new atmosphere version came out I decided to try AIO updater since I've never used it before, I clicked on update atmosphere, atmosphere crased and when I rebooted to hekate I could no access the emuMMC anymore, either by hekate or fusebin, I deleted the atmosphere and bootloader folder as well as the switch and config folders on the sd card, placed the new version of atmosphere, hekate and patches on the sd card but I still cannot access emuMMC, I get an atmosphere logo splash and then black screen up until I turn off my switch, what could possible be the issue and how can I fix it?
Someone made this a couple of years ago so you can go ahead and give it a shot.Hello,
Is it possible or is there some kind of applet that allows you to upload screenshots from the switch to Twitter?
My emunand has incognito enabled (blank serial number) and a edited DNS, so i don't think it will work the default way.
Keys are only stored on the internal storage of the Switch so having an SD card inserted or not doesn't affect the keys being dumped. Also, insta-bans are a myth; bans are distributed at random times whenever Nintendo feels like spreading a ban wave.So I haven't touched my switch in years, but now I wanted to start using it and decided to update everything. I followed the known guides, but while reading the page on Rentry about dumping your keys I saw that it said to copy both prod.keys and title.keys, but I only had a backup of one file so I decided to dump my keys again. Then I did something stupid and FORGOT to put my micro sd card back in my switch so I now I'm worried that it dumped the keys on the internal storage of the switch...
Does anyone know if that is what happened? And if so, is it harmful (as in will I now get instantly banned for "modifying" my switch)?
There is an issue with one or more of the save files inside your console. Back them all up with a homebrew save manager such as JKSV or Checkpoint then get rid of all of them. Slowly restore it until the console encounters a problem or you're done restoring the save files. You don't have to touch anything on the SD card but if you do end up wiping it, do not follow rentry guide. Its not very good at all. Instead, I would highly recommend following switch.homebrew.guide instead.Hi!
I have a Switch v1 Erista with SX core installed. I run Hekate + Atmosphere with emuNAND and recently Atmosphere started giving this problem when I boot it:
A fatal error occurred when running Atmosphere. ProgramID: 010000000000002b Error Desc: std::abort() called (0xffe) Failed to save report to the SD card! (00000202) Press POWER to reboot.
I tried several options and couldn't solve it, so I'm thinking to format my microSD and make a clean install of everything.
Besides a backup of the savegames, do I need to keep anything from the SD? Or do I just wipe the SD and start over with the Rentry guide?
Maybe someone has a guide about doing this kind of cleanup?
Thanks!
The problem is you are using the AIO updater which is a very buggy tool notorious for causing many issues. Stop using it immediately and download the latest patches from this thread.Hello, Time for my routine update errors lol I updated amto and hekate, and can boot fine but none of my games or tinfoil launch. I get unable to start software. Iv put what I think are the correct sigpatch files, and iv tried to use the app AIO to update the sigpatches. not sure what im doing wrong.













