Downgrade from 19 / Rescue my Switch

[grandem]

Hey,

I updated my SYSNAND to version 19, and now my EMUNAND is giving me the following message:

"Failed to match Warmboot with fuses!
If you continue, sleep mode won't work."

I attempted to downgrade using the new Atmosphere version, but it didn’t work. During the process, I accidentally replaced my .ini file, so now I don’t have any launch options available.

What’s the best way to recover my old .ini file? And once I've recovered it, what's the proper method to safely downgrade?

 

[randy_w]

Why do you want to downgrade sysnand? Atmosphere 1.8.0 was released last week, just update it and it should work.

As for the warmboot warning, you need to boot your updated sysnand at least once, it will dump warmboot firmware automatically and the warning message should go away.

As for the ini file, you can use this one as template:

[config]
autoboot=0
updater2p=1

[STOCK (SYSMMC)]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp
{}

[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
usb3force=1
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
usb3force=1
{}

Don't forget to update sigpatches and hekate too

 

[grandem]

That makes sense thx for that. Makes it easier.

With that ini files SYSNAND stock booted.

With the SYS CFW
and EMUNAND
I get Failed to apply "nosigchk"

 

[josete2k]

[config]
autoboot=0
updater2p=1

[STOCK (SYSMMC)]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1

[CFW (SYSMMC)]
fss0=atmosphere/package3
emummc_force_disable=1

[CFW (EMUMMC)]
fss0=atmosphere/package3
emummcforce=1

Why the {}?

 

[randy_w]

That makes sense thx for that. Makes it easier.

With that ini files SYSNAND stock booted.

With the SYS CFW
and EMUNAND
I get Failed to apply "nosigchk"

Like I said you need to set up sigpatches and sys-patch module. You can get the latest one from the sigpatch thread.

Why the {}?

idk, think it's used to group boot entries, came from an ini I used a long time ago

 

[grandem]

Like I said you need to set up sigpatches and sys-patch module. You can get the latest one from the sigpatch thread.


idk, think it's used to group boot entries, came from an ini I used a long time ago

Ok I tried that with the patches from the site.

Now I am getting Errort while loading fss0:
Atmosphere package 3
Wrong in cfg or launch HOS!



If i only put atmosphere without the syspatches I am back to the nosigchk error.

So it seems that's where i am messing up =.