Hacking help! I have Gone and messed up [ipatched switch]

[Simba580]

I have ipatched switch version x.x.x use to be 4.1.0
I was following this very helpful guide - https://switch.homebrew.guide/index
backed up everything got everything working manged to boot into CFW through hekate emuMMC
i am use to the 3ds scene with the emuNAND so i thought i was in something similar so i then tried to use ChoiDujourNX just like the instructions said to use to update the switch.
so i updated (yes i checked to make sure i as on CFW) but then as i restarted the switch .. my original sys has been updated to 8.1.0.

so am i stuck now? how do i use my backups to downgrade? or am i stuck now with this new version?

 

[enderer]

you burnt fuses if you restarted into Horizon OS. stuck for sure. if for some reason you stayed in cfw, you can downgrade or restore your backup.

 

[Hayato213]

Look like you updated the wrong nand, you are stuck on 8.1.0 if you did indeed updated your sysnand.

 

[Simba580]

still have fake news installed ... i get to the pegascape logo gives me message that there's no scrips compatible for your firmware version.
is it possible to do something with that perhaps?

 

[Resaec]

No. You were hasty and didn't take your time to read all of the warnings and instructions while performing dangerous tasks.
You are now stuck on 8.1.0+

 

[pLaYeR^^]

CFW doesn’t mean that you are automatically in EmuMMC. You can also boot in SysNAND with CFW.

 

[Kafluke]

Those guides should instruct users to change the theme of emu nand so they know if they are in sysnand or not.

 

[jajamundo]

This is why atmoshpere is not for the average user. Sorry, but this happen because you didnt unlink your Nands. So whatever you do to your emuMMC affects your sysnand.

There is no way to hack an ipatched unir on 8.0.1. Maybe never will because ir patch the existant exploit.

 

[pLaYeR^^]

This is why atmoshpere is not for the average user. Sorry, but this happen because you didnt unlink your Nands. So whatever you do to your emuMMC affects your sysnand.

There is no way to hack an ipatched unir on 8.0.1. Maybe never will because ir patch the existant exploit.

You don’t need to unlink... His mistake was that he updated SysNAND and didn’t check.

 

[altorn]

i accidentally updated my "SysNAND CFW" to 8.1.0 without ChoiDujourNX / AutoRCM. Now I have burnt my fuses, good thing I have an unpatched Switch.
my mistake was following a youtube video, which the person was doing it wrong as well because he was already banned.

 

[bird333]

This is why atmoshpere is not for the average user. Sorry, but this happen because you didnt unlink your Nands. So whatever you do to your emuMMC affects your sysnand.

There is no way to hack an ipatched unir on 8.0.1. Maybe never will because ir patch the existant exploit.

What is this? How do you do it?

 

[Paulsar99]

Damn that sucks. Sadly it will probably be a long wait for patched switches to be hacked above 4.1.0.

 

[Simba580]

This is why atmoshpere is not for the average user. Sorry, but this happen because you didnt unlink your Nands. So whatever you do to your emuMMC affects your sysnand.

There is no way to hack an ipatched unir on 8.0.1. Maybe never will because ir patch the existant exploit.

i cant believe i forgot to unlink them dam its always the little things that get you.

 

[jajamundo]

You don’t need to unlink... His mistake was that he updated SysNAND and didn’t check.

He wrote the he makes sure he was on CFW. So he was on emunand.

What is this? How do you do it?

Emunand is an exact copy of your sysnand. It means it uses the exact info on your SD Card to. Unlink the Nands means that you have separates files on both emunand and sysnand.

In SX OS is really simply as just format one of the Nands, because when you set up the emunand it createa a emutendo folder and you dont have this problem. But in atmosphere this is not the case. It creates a folder named emuMMC and there is suppose to be another Nintendo folder. Then you need to tell atmoshpere wich Nintendo folder you are using with sysnand and with emunand and then you just format one of the Nands. If everything goes well, you should have separates Nands. Thats why I just said atmoshpere is not for the average people.

i cant believe i forgot to unlink them dam its always the little things that get you.

Sorry man, but sometime this things happen. Now you have to wait until there is a new exploit or buy a new switch and pray it still on 4.1.0

 

[pLaYeR^^]

He wrote the he makes sure he was on CFW. So he was on emunand.


Emunand is an exact copy of your sysnand. It means it uses the exact info on your SD Card to. Unlink the Nands means that you have separates files on both emunand and sysnand.

In SX OS is really simply as just format one of the Nands, because when you set up the emunand it createa a emutendo folder and you dont have this problem. But in atmosphere this is not the case. It creates a folder named emuMMC and there is supposed to be another Nintendo folder. Then you need to tell atmoshpere wich Nintendo folder you are using with sysnand and with emunand and then you just format one of the Nands. If everything goes well, you should have separates Nands. Thats why I just said atmoshpere is not for the average people.



Sorry man, but sometime this things happen. Now you have to wait until there is a new exploit or buy a new switch and pray it still on 4.1.0

You can also boot with CFW to SysNAND...

 

[bird333]

He wrote the he makes sure he was on CFW. So he was on emunand.


Emunand is an exact copy of your sysnand. It means it uses the exact info on your SD Card to. Unlink the Nands means that you have separates files on both emunand and sysnand.

In SX OS is really simply as just format one of the Nands, because when you set up the emunand it createa a emutendo folder and you dont have this problem. But in atmosphere this is not the case. It creates a folder named emuMMC and there is supposed to be another Nintendo folder. Then you need to tell atmoshpere wich Nintendo folder you are using with sysnand and with emunand and then you just format one of the Nands. If everything goes well, you should have separates Nands. Thats why I just said atmoshpere is not for the average people.



Sorry man, but sometime this things happen. Now you have to wait until there is a new exploit or buy a new switch and pray it still on 4.1.0

Thanks for the reply. Where in the atmosphere config is it specified which folder to use for sysnand? Wait are you talking about in the 'emummc' config file?

 

[jajamundo]

Thanks for the reply. Where in the atmosphere config is it specified which folder to use for sysnand? Wait are you talking about in the 'emummc' config file?

Yes, the emummc config file is the one I'm talking about

 

[Simba580]

He wrote the he makes sure he was on CFW. So he was on emunand.


Emunand is an exact copy of your sysnand. It means it uses the exact info on your SD Card to. Unlink the Nands means that you have separates files on both emunand and sysnand.

In SX OS is really simply as just format one of the Nands, because when you set up the emunand it createa a emutendo folder and you dont have this problem. But in atmosphere this is not the case. It creates a folder named emuMMC and there is suppose to be another Nintendo folder. Then you need to tell atmoshpere wich Nintendo folder you are using with sysnand and with emunand and then you just format one of the Nands. If everything goes well, you should have separates Nands. Thats why I just said atmoshpere is not for the average people.



Sorry man, but sometime this things happen. Now you have to wait until there is a new exploit or buy a new switch and pray it still on 4.1.0

now I'm looking for a new 4.1 switch its been really difficult.

Thank you for the guide on how to split Nands.

Its something that's hard to find

 

[pLaYeR^^]

now I'm looking for a new 4.1 switch its been really difficult.

Thank you for the guide on how to split Nands.

Its something that's hard to find

Better look for an unpatched one. Then you can hack it on any firmware.

 

[Simba580]

Better look for an unpatched one. Then you can hack it on any firmware.

those are out of circulation almost by now.

Closest was maybe patched
But my previous one was the same.

Anyhow i hope others learn from my mistakes and don't end up like me.