Hacking Question Yellow screen from EmuMMC boot after atmosphere update

[Regained]

I'm on version 9.2 firmware and wanted to update to 10.2 on emummc so i put on the latest atmosphere. When i get to Hekate and chose emummc, its giving me a yellow screen. I updated my rcmloader then with the latest fusee primary, and it boots all the way without a Hekate menu.

When i chose Reboot to payload, it takes me to Hekate, but when i select emummc, i get the yellow screen again.

Did atmosphere break my emummc partition? how do i fix this? thanks

 

[The Real Jdbye]

I'm on version 9.2 firmware and wanted to update to 10.2 on emummc so i put on the latest atmosphere. When i get to Hekate and chose emummc, its giving me a yellow screen. I updated my rcmloader then with the latest fusee primary, and it boots all the way without a Hekate menu.

When i chose Reboot to payload, it takes me to Hekate, but when i select emummc, i get the yellow screen again.

Did atmosphere break my emummc partition? how do i fix this? thanks

You need to update Hekate. You should always update Hekate at the same time as updating Atmosphere and sig patches.
Also, you probably have Hekate set to replace reboot_payload.bin automatically. Please stick with either Hekate or fusee-primary as your reboot_payload.bin and dongle payload, don't mix and match as that will only lead to confusion.

 

[Regained]

You need to update Hekate. You should always update Hekate at the same time as updating Atmosphere and sig patches.
Also, you probably have Hekate set to replace reboot_payload.bin automatically. Please stick with either Hekate or fusee-primary as your reboot_payload.bin and dongle payload, don't mix and match as that will only lead to confusion.

I've update to the latest Hekate and it still yellow screens. The update procedure is to copy over a new bootloader folder, and put in the fusee-primary.bin into payloads? The ini file for the old version was in bootloader, and now there's a new INI folder, do I copy the old ini file into INI?

my old config

[config]
autoboot=0
autoboot_list=0
bootwait=0
backlight=100
autohosoff=0
autonogc=1
updater2p=1

[CFW - sysMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

[Stock - sysMMC]
fss0=atmosphere/fusee-secondary.bin
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp

 

[The Real Jdbye]

I've update to the latest Hekate and it still yellow screens. The update procedure is to copy over a new bootloader folder, and put in the fusee-primary.bin into payloads? The ini file for the old version was in bootloader, and now there's a new INI folder, do I copy the old ini file into INI?

my old config

[config]
autoboot=0
autoboot_list=0
bootwait=0
backlight=100
autohosoff=0
autonogc=1
updater2p=1

[CFW - sysMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

[Stock - sysMMC]
fss0=atmosphere/fusee-secondary.bin
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp

You shouldn't replace hekate_ipl.ini as that will wipe your CFW boot entries. But if you want to boot fusee-primary directly with the dongle you should also disable updater2p and if you want to chainload from Hekate, you should replace the payload on your dongle with the Hekate one and leave updater2p enabled.

 

[Regained]

You shouldn't replace hekate_ipl.ini as that will wipe your CFW boot entries. But if you want to boot fusee-primary directly with the dongle you should also disable updater2p and if you want to chainload from Hekate, you should replace the payload on your dongle with the Hekate one and leave updater2p enabled.

Wow, thats alot of things i dont really know about.
Is updater2p a menu option in Hekate?
I dont know the difference between fusee-primary and secondary.
what is chainloading?
where is the hekate payload for the dongle?

thanks. its alot i know

 

[Draxzelex]

Wow, thats alot of things i dont really know about.
Is updater2p a menu option in Hekate?
I dont know the difference between fusee-primary and secondary.
what is chainloading?
where is the hekate payload for the dongle?

thanks. its alot i know

Updater2p is a line in the hekate_ipl.ini file. The difference between fusee_primary and fusee_secondary is that fusee_primary is, as the name implies, the primary payload. It then automatically chainloads into fusee_secondary if it is on your SD card. Chainloading is the action of using a different payload than the one you originally launched. The hekate payload for your dongle will depend on what type of dongle you are using.

 

[thehenryswanson]

I had the same issue. What I did was create a new emuMMC. I was then able to boot without getting the yellow screen. The only thing was that my games were missing so I copied and replaced the Nintendo folder from the original emuMMC into the new and everything is back working correctly.

 

[HollowGrams]

I'm on version 9.2 firmware and wanted to update to 10.2 on emummc so i put on the latest atmosphere. When i get to Hekate and chose emummc, its giving me a yellow screen. I updated my rcmloader then with the latest fusee primary, and it boots all the way without a Hekate menu.

When i chose Reboot to payload, it takes me to Hekate, but when i select emummc, i get the yellow screen again.

Did atmosphere break my emummc partition? how do i fix this? thanks

Notice about Atmosphere 1.0.0 and up: The fss0=atmosphere/fusee-secondary.bin in hekate_ipl.ini must be changed to fss0=atmosphere/package3