Blue screen or weird mariko issue

[PreHeX]

Trying to launch emuMMC from [hekate v6.2.0 & Nyx v1.6.2] with [Atmosphère 1.7.1] on firmware 18.0.0. on an "unpatched Nintendo Switch v1" I launch it and get following Error Message:

HOS panic occured!

Color: ####, Code: 01 Press any key...

the Color of the "####" is blue.

What do i do?

[Raph9213]

Try redownloading the latest hekate version, v6.2.0 had a bug on the first release where it couldn't boot before on all v1 switch

[CTCaer]

Yep I broke booting on all eristas with a typo mistake. The redownload should fix that. I will keep the issue open for now.

[mayt04]

I still get the Blue screen…even thought I downoalded the latest Hekate with the new link,I have an Erista

[hanstoribio]

I downloaded the new version and I still have the blue screen problem

[BlytheScythe]

Same here, I'm still getting the blue screen and I have an Erista. I've tried booting into Atmosphere via fusee.bin and my emuMMC works, it's just that loading Atmosphere's package3 via Hekate's FSS0 doesn't work for some reason. If you need anything else that I can check, let me know.

[muxi1]

Shut down your consoles completely and reboot. Then the error will be fixed.

[mayt04]

I will try,thank you! EDIT:still doesn’t work

[hanstoribio]

I confirm, it doesn't work

[PreHeX]

I formatted the SD Card just to be sure and installed Hekate,Atmosphere and the Sigpatches again (all from the latest release) and made a fresh emuMMC and tryed to launch...

same error Unfortunately

[muxi1]

Then you still have the faulty version. Download the latest version again from the release section and replace all the data on your SD card. At least it works for me now on my Erista v1. I have a 400 GB SD card in use.

[hanstoribio]

If you enter from the hekate menu and choose sysnand or emmu it does not work, but if you inject the direct fuuse.bin it does work

[CTCaer]

Well either github or the browser seems to be caching it. Someone else even reported BlobNotFound github error or the link not working at all. The updated zip should have MD5: 20cb6c523a61512651e7070a343b8f4d

Also r2p loads the payload on boot, so a power off is mandatory. Finally while extracting it, the option that replaces files and merges folders should be selected.

[muxi1]

I've heard from other users who are still having issues with 512GB, 1TB and 1.5TB capacities, especially under the OLED Switch.

[mayt04]

The zip i downoalded has this MD5 Hash: 20CB6C523A61512651E7070A343B8F4D Perhaps I need to delete my bootloader folder from my microSD and then put the one from the zip? Because I just extracted the .zip then I putted the bootloader folder in the SD and I selected replace

[hanstoribio]

I installed everything from scratch and the blue screen still appears (I'm using the new file)

[CTCaer]

That's the correct zip hash. How you inject it? PC or loader?

[mayt04]

That's the correct zip hash. How you inject it? PC or loader?

I used the Hekate's USB Transfer feature,maybe I should turn off the console,put the SD on the PC and then put the folder?

[PreHeX]

the latest .zip indeed has the MD5 Hash: 20cb6c523a61512651e7070a343b8f4d and i replaced it in the SD card i even tryed different ways over USB and Sd card removing still same error

[muxi1]

It worked 1-2 times, now I get a blue screen again. The payload is loaded via a dongle.

[mayt04]

Also I use TegraRcmGui with the latest hekate.bin

[BlytheScythe]

I've downloaded and extracted to SD card the correct .zip file. I personally use Rekado to push my payloads.

I still run into the same error.

I've tried clearing the system cache and any pending update, didn't fix it. Powered off, booted into RCM and pushed the latest Hekate payload and when I tried booting into Atmosphere, nothing. Blue screen still.

[CTCaer]

@muxi1 on erista you need to replace reboot_payload.bin also if it is set to be replaced to hekate

[HaiKonofanDesu]

I already got the Bluescreen Fix Update and it fixes the initial Blue Screen. (using TegraRCMGUI 2.6)

Opening emuNand or SysNand once works, rebooting and (at leasst) switching to the other results in a blue screen. Have not yet tested if booting in the same one also results in a blue screen.

[BlytheScythe]

I've replaced my reboot_payload.bin as well, still having the same issue. I use it so that I can reboot to Hekate so that I can use USB transfer tool mainly (and to update my setup when needed).

[lucasaf04]

@CTCaer On OLED (Aula) I get a glitchy screen after the 3 second delay when trying to boot ams v1.7.0 (emummc and sysmmc). OFW boots fine. HOS 17.0.1 I'm downgrading to v6.1.1 for now.

[mayt04]

Yeah,works fine with 6.1.1

[Raph9213]

As @HaiKonofanDesu said, the first boot works fine for first time, and then do the "Blue Screen Code 01" panic after injecting again with Reboot Payload or with Studious Pancake, replacing manually atmosphere/reboot_payload.bin fixes the issue

[CTCaer]

anyone that does not have erista should state that btw, like @lucasaf04

and as I said, if behavior changes on erista after a reboot (r2p), it's because of reboot_payload.bin

[muxi1]

@muxi1 on erista you need to replace reboot_payload.bin also if it is set to be replaced to hekate I use a forwarder payload as reboot_payload.bin, which always loads the payload.bin (aka hekate_ctcaer_x.x.x.bin) from the SD card root.

and this has always worked very well so far.

[HaiKonofanDesu]

I already got the Bluescreen Fix Update and it fixes the initial Blue Screen. (using TegraRCMGUI 2.6)

Opening emuNand or SysNand once works, rebooting and (at leasst) switching to the other results in a blue screen. Have not yet tested if booting in the same one also results in a blue screen.

Using Hekate and Atmosphere on Eristas

[HaiKonofanDesu]

As @HaiKonofanDesu said, the first boot works fine for first time, and then do the "Blue Screen Code 01" panic after injecting again with Reboot Payload or with Studious Pancake, replacing manually atmosphere/reboot_payload.bin fixes the issue

@Raph9213 with what file did you replace the reboot_payload.bin?

[mayt04]

So we need to rename the latest hekate_ctcaer.bin to reboot_payload.bin then we put it into the atmosphere folder,select replace and it should fix it on erista?

[CTCaer]

@muxi1 hekate uses the version to decide if it should launch an "updated" self. I didn't change that. So you are supposed to change all payloads that are hekate manually with updated hekate. (e.g. Injector/loader payload, payload.bin, update.bin, reboot_payload.bin or whatever other thing is used on weird setups, like in payloads folder.)

[Raph9213]

As @HaiKonofanDesu said, the first boot works fine for first time, and then do the "Blue Screen Code 01" panic after injecting again with Reboot Payload or with Studious Pancake, replacing manually atmosphere/reboot_payload.bin fixes the issue

@Raph9213 with what file did you replace the reboot_payload.bin?

With the hekate .bin payload in the zip file, the "hekate_ctcaer_6.2.0.bin" file, and renamed to "reboot_payload.bin"

It seems that the "Update Reboot 2 Payload" settings doesn't work anymore to "replace" the reboot payload for hekate?

[mayt04]

So we need to rename the latest hekate_ctcaer.bin to reboot_payload.bin then we put it into the atmosphere folder,select replace and it should fix it on erista?

tried this,still doesnt works

[CTCaer]

@Raph9213 It does work, I just didn't change the version on the fixed payload, so old and new are still 6.2.0. It uses that to check if it needs updating, it doesn't randomly update it. So the update.bin and reboot_payload.bin do not get updated because of that. (That's the annoying state of eristas. On mariko it's a bit simpler. Since reboot_payload is not used.)

[PreHeX]

As @HaiKonofanDesu said, the first boot works fine for first time, and then do the "Blue Screen Code 01" panic after injecting again with Reboot Payload or with Studious Pancake, replacing manually atmosphere/reboot_payload.bin fixes the issue

@Raph9213 with what file did you replace the reboot_payload.bin?

With the hekate .bin payload in the zip file, the "hekate_ctcaer_6.2.0.bin" file, and renamed to "reboot_payload.bin"

It seems that the "Update Reboot 2 Payload" settings doesn't work anymore to "replace" the reboot payload for hekate?

does not work same error On erista

[HaiKonofanDesu]

@mayt04 @PreHeX You sure you have the updated Version?

1) Download the UPDATED files that include the Bluescreen Fix (hekate_ctcaer_6.2.0_Nyx_1.6.2, make sure your browser does not cache) 2) Shut down your Switch 3) Inject SD Card into PC 4) Open atmosphere folder and delete "reboot_payload.bin" file 5) Unzip the new "hekate_ctcaer_6.2.0_Nyx_1.6.2" 6) Open the Folder and copy the "hekate_ctcaer_6.2.0.bin" file 6) Paste it into the atmosphere folder and rename it again to "reboot_payload.bin" 7) Inject SD Card into PC, start Payload and you should be good to go.

Shoutout to @Raph9213 for the help and thanks CTCaer for the fast fix and the explanation why this is needed

I just didn't change the version on the fixed payload, so old and new are still 6.2.0. It uses that to check if it needs updating, it doesn't randomly update it. So the update.bin and reboot_payload.bin do not get updated because of that.

Aka we need to manually update the file for the fix to work.

[mayt04]

@mayt04 @PreHeX You sure you have the updated Version?

The Method descriped by Raph worked for me.

Open atmosphere and delete reboot_payload Copy the UPDATED (make sure it'S the fixed version) "hekate_ctcaer_6.2.0.bin" in the atmosphere folder and rename it again to "reboot_payload.bin"

Shutdown console and inject payload once more and it should work!

Ahh the same Version thin explains a lot, thanks for clarify!

I did this metod and it fixed the issue,thanks everyone!

[CTCaer]

@PreHeX preHeX.zip Extract that update.bin to bootloader/ folder and replace one. Try to boot. If that boots it means you didn't replace all relevant payloads.

No one else try that btw since I changed the internal version to 6.2.1 to bypass all that mumbo jumbo dancing around happening on eristas.

[CTCaer]

@mayt04 @PreHeX You sure you have the updated Version?

The Method descriped by Raph worked for me.

1. Download the UPDATED files that include the Bluescreen Fix (hekate_ctcaer_6.2.0_Nyx_1.6.2, make sure your browser does not cache)
2. Shut down your Switch
3. Inject SD Card into PC
4. Open atmosphere folder and delete "reboot_payload.bin" file
5. Unzip the new "hekate_ctcaer_6.2.0_Nyx_1.6.2"
6. Open the Folder and copy the "hekate_ctcaer_6.2.0.bin" file
7. Paste it into the atmosphere folder and rename it again to "reboot_payload.bin"
8. Inject SD Card into PC, start Payload and you should be good to go

Shutdown console and inject payload once more and it should work!

Ahh the same Version thin explains a lot, thanks for clarify!

When I make sure that everything is fixed and all can boot, I will do a hotfix update as 6.2.1 end of this week or next.

[mayt04]

Thank you for the patience guys

[PreHeX]

@PreHeX preHeX.zip Extract that update.bin to bootloader/ folder and replace one. Try to boot. If that boots it means you didn't replace all relevant payloads.

No one else try that btw since I changed the internal version to 6.2.1 to bypass all that mumbo jumbo dancing around happening on eristas.

no it still doesent work can i send u any logs somewhere or something because i even tried to turn on Logs but nothing happend...

and yeas im sure i have the updated version

[CTCaer]

@PreHeX how you update the payloads? also grab the sd:/bootloader/update.bin, zip it and upload it here.

[PreHeX]

@PreHeX how you update the payloads? also grab the sd:/bootloader/update.bin, zip it and upload it here.

via Hekate -> USB Tools -> SD Card

bootloader.zip

[CTCaer]

so you didn't update it. that has 6.2.0 as version.

[PreHeX]

so you didn't update it. that has 6.2.0 as version.

wait now im confused isnt that the latest ? or what do you mean "you didn´t update it"

[mirivedan]

A clean install on 2 different sd cards gives me a black screen or screen crash both on OFW or CFW

[BlytheScythe]

I've also double-checked whether everything's up-to-date and followed what HaiKonofanDesu posted. Still blue screen. Here's my update.bin as well: update.zip

EDIT: I've checked the PreHeX's update.bin and it's the same one I have and... that should be the latest? Latest update.bin's CRC32 is F36EB6C3, while the old one's 5E8E6669.

[PreHeX]

or should I wait until you fix it or 6.2.1 is released? I don't want to bother you now.