Hacking OFW don't turn on

[lyagushka]

After update CFW to 17.0.1 and Kefir to 725 with last hekate, OFW don't turn on even when i press vol+ to enter into recovery mode. Hekate and CFW is working

 

[petspeed]

Seems like you are affected by the known issue when updating to fw17. Try to boot sysmmc with latest atmosphere once. If that works shutdown the switch and start ofw normally. That should fix it

 

[lyagushka]

Seems like you are affected by the known issue when updating to fw17. Try to boot sysmmc with latest atmosphere once. If that works shutdown the switch and start ofw normally. That should fix it

How? In Launch i have only Atmosphere and Full Stock

 

[petspeed]

If you use Hekate as payload then add this to the hekate_ipl.ini file

[Atmosphere FSS0 sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1

Start Switch and choose Atmosphere FSS0 sysMMC from Hekate

If you use Fusee.bin as payload then rename the emummc folder on your SD card to something else and start the Switch
After it has started rename the folder back to emummc and restart the Switch

 

[lyagushka]

If you use Hekate as payload then add this to the hekate_ipl.ini file

[Atmosphere FSS0 sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1

Start Switch and choose Atmosphere FSS0 sysMMC from Hekate

If you use Fusee.bin as payload then rename the emummc folder on your SD card to something else and start the Switch
After it has started rename the folder back to emummc and restart the Switch

I use chip

 

[petspeed]

I use chip

That doesn't really matter, you still use a payload. I think it must be on you sd card when using a chip

 

[lyagushka]

That doesn't really matter, you still use a payload. I think it must be on you sd card when using a chip

thank, it work

 

[Hayato213]

thank, it work

What he gave you is wrong anyway since you are still on CFW from what he gave you.

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/icon_switch.bmp
{}

 

[petspeed]

What he gave you is wrong anyway since you are still on CFW from what he gave you.

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/icon_switch.bmp
{}

That was the whole idea to run Atmosphere on SysMMC just one time to fix the issue booting after upgrade to fw17 if the console had previously bee wiped with a homebrew tool.

 

[Hayato213]

That was the whole idea to run Atmosphere on SysMMC just one time to fix the issue booting after upgrade to fw17 if the console had previously bee wiped with a homebrew tool.

What you gave him boot into Sysnand CFW not Full Stock that he asks, if he has a clean OFW NAND then he is missing the stock=1 in the config.

 

[petspeed]

What you gave him boot into Sysnand CFW not Full Stock that he asks, if he has a clean OFW NAND then he is missing the stock=1 in the config.

Will that still fix the boot issue?
Anyway it doesn't really matter. It fixed the issue