Yes although I forgot to mention that utilities such as Lakka or Android that operate outside of Horizon, the Switch operating system, actually carry a 0% ban risk since they never touch the system.I guess Lakka has a similar near zero ban-chance as has Android on the Switch?
got a nand backup
also yay new atmo
Yes although I forgot to mention that utilities such as Lakka or Android that operate outside of Horizon, the Switch operating system, actually carry a 0% ban risk since they never touch the system.
There is no guide for this sort of thing. All you really need to do is just make the Pokemon in the console that you don't play online then trade them over to the one you do play online. PkHex is still good enough to do the job and any save manager should be able to dump the data for you to use.
How do you load CFW? Meaning what software and/or hardware do you use to enter Atmosphere?
Just updated to Atmosphere 0.17 and Hekate 5.5.2 and the newest sigpatches, still got the same fatal error.
Did I brick my Switch or am I missing something obvious here. Thanks.
It would be riskier to dump them in directly because Nintendo might be able to detect it. Its safer to just trade them because Nintendo cannot verify if the game the Pokemon came from was legitimate or not. You also don't need to buy another copy as you can just pirate the game on your offline console. Well..it wouldn't really be piracy since you do own it but you get my point.Can i transfer my pokemon save from my online switch to offline switch and use save manager and transfer the dumped mons in new save from offline to online switch?
Or do i haven't to buy another sword / shield copy and have to trade one by one?
Whats the title ID of the fatal error
There is no title ID for the fatal error.
It's just Fatal error: [NXBOOT]: Unable to identify package1
So I finally got into Hekate after using TegraRCM instead of my usual RCMloader. When I pressed Payload and chose fusee-primary.bin, the error happened again.
got a nand backup?
It would be riskier to dump them in directly because Nintendo might be able to detect it. Its safer to just trade them because Nintendo cannot verify if the game the Pokemon came from was legitimate or not. You also don't need to buy another copy as you can just pirate the game on your offline console. Well..it wouldn't really be piracy since you do own it but you get my point.
It would be riskier to dump them in directly because Nintendo might be able to detect it. Its safer to just trade them because Nintendo cannot verify if the game the Pokemon came from was legitimate or not. You also don't need to buy another copy as you can just pirate the game on your offline console. Well..it wouldn't really be piracy since you do own it but you get my point.
You don't have to go online on the offline Switch to trade Pokemon.That is risky. Isn't there another way than trading from offline to online? I don't want to go online on the offline switch. I figured transferring saves was the safest way. I've seen people trade 70+ hacked mons to others without nintendo detecting. And ive watched people having 6 hacked mons battling online, and these 6 hacked mons are in fused form and you can't fuse more than one and they're battling with 6 and nintendo doesn't ban them.
https://gbatemp.net/threads/tutorial-from-sx-os-to-atmosphere.533337/Hi is there any guide to migrate from sx os to atmosphere 17.0. I have a v2 switch with system firmware 11.0, and no emunand.
I got the emuMMC backup a while ago. Is that the same thing?
If you got a working set of boot0/boot1 along with the eMMC Raw GPP then yes.
I tried to launch emuMMC from Hekate and got this screen instead.
I will try to restore emuMMC with my backup.
I can load sysMMC fine though. Is there anything bad if I use this instead of emuMMC?
Thank you guys for help so far!!!
Check your files on your SD, make sure they are up to date, it point about the sept folder are the files in there up to date?
Yes, I deleted switch, atmosphere and sept folders and copied the new ones from Atmosphere over. I did it a couple times with Atmosphere 0.16.2 and then did the same when 0.17. came out a few hours ago.