Your payloads update them to ther current versionsSo which files on the dongle do I have to overwrite? The rentry isn't super clear on how to update the dongle.
Your payloads update them to ther current versionsSo which files on the dongle do I have to overwrite? The rentry isn't super clear on how to update the dongle.
Did you try my idea of using the newest version of Atmosphere?
Sorry, I am already on the most updated version of Atmosphere (1.5.3), but I decided to try it anyways and I still get the same error.
I thought he was referring to the most updated stable version.1.5.4 is the latest.
All versions arnt stable even 1.5.3 if they was there would not be updated versionsI thought he was referring to the most updated stable version.
I tried replacing the files with 1.5.4 prerelease and I'm still getting the same error.
Well either way, it's not working.All versions arnt stable even 1.5.3 if they was there would not be updated versions
Well either way, it's not working.
Has Binkinator been around? Seems like that guy has a solution to every problem (though I do appreciate any help so far).
Yes, well, I didn't, which is how I came to be here. Any suggestions on how I might fix this problem?Should of chise FAT32+eXFat
You sir have helped me without even trying! Thank you for giving me the idea to try using Fusee to boot my switch! It works! I have a similar problem where I tried updating using daybreak and it broke my switch when I try to boot to CFW -emuMMC through Hekate my switch hangs. But through fusee it boots just fine and my version is 16.0.3 AMS 1.5.3|E . Now the next step is how do I back up all my saves and whatnot in the event this thing crashes again?I just updated my CFW and FW to their latest versions using the rentry guide, but I am unable to boot into emummc through Hekate. When I try, it immediately goes into RCM mode, and injecting hekate again causes the following error message:
Panic occured while running Atmosphere.
Title ID: 0100000000000000
Error: UNK (0x6)
If I boot through fusee.bin, Atmosphere works fine. Does anyone know what I might have done wrong? I just migrated to a new sd card two days ago, but everything was working perfectly until I installed version 16.0.3 using daybreak. So far, I've tried using a completely fresh atmosphere folder, which didn't work.
Hekate not work because your hekate_ipl.ini isnt correct thenYes, well, I didn't, which is how I came to be here. Any suggestions on how I might fix this problem?
Post automatically merged:
You sir have helped me without even trying! Thank you for giving me the idea to try using Fusee to boot my switch! It works! I have a similar problem where I tried updating using daybreak and it broke my switch when I try to boot to CFW -emuMMC through Hekate my switch hangs. But through fusee it boots just fine and my version is 16.0.3 AMS 1.5.3|E . Now the next step is how do I back up all my saves and whatnot in the event this thing crashes again?
Ok. What do I need to do?Hekate not work because your hekate_ipl.ini isnt correct then
Thanks for the link but it doesn't answer any of the questions asked. eMMC also contains older version of the OS, emunand is way ahead.
You mean on switch or on PC?Use emutool, convert hidden partition emunand to file base, then convert it back to hidden partition.

Use emummc for homebrew, and use stock for emmc. clear out your serial number for emummc. that's the best course of action for now. 90dns isn't trustworthy to most people, so don't just use that.I have a modchip installed on my Nintendo Switch and I'd like to know the best route of avoiding a ban.
I want to play my official purchased games on my OFW and use homebrew apps on my CFW but what would be the best course of action?

JKSV requires a non-encrypted save, like one you dump from JKSV, to import a save. It also needs that save to be in the JKSV folder. From my understanding, you have a save on your emmc and need to move it to emummc. Is your emummc banned? Try moving your save to the emummc using the method you did to move it using emmc (legitly), if not. If your emummc is banned, I don't know what to do.I have a question on save files. So I have a switch that I was originally playing on that is not using CFW. I was playing TOTK on there. I got really far. Now I have this new switch that is running CFW. I'm running off SD via emuMMC.
I want to get my TOTK save data over from my legit switch over to my one using CFW. I pulled the SD, loaded back up in to OFW, linked the new switch and did a legit save transfer. It worked.
Now I put everything back on the switch the way it was with CFW but my save is not there. Likely because i'm running emuMMC and that save is stored on the system.
My question is, how can I get that save over to the emuMMC. I see a folder in the "emuMMC/RAW1/Nintendo/save". My assumption is that I just have to find it and put it in this folder and i should be good. I can't figure out where the legit save is though to move it.
I tried to download checkpoint.nro but it didn't run. the screen flashes, the checkpoint folder gets created and then goes away. So that didn't help.
Another issue I have is that I played TOTK for a little bit on this CFW switch so it has it's own save file. I loaded JKSV and it sees that save but not the one from the other switch that i want to use.
Sorry if this is all confusing. I'm equally confused.