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

[lucasaf04]

Erista (V1) @PreHeX I gave you a special one to try, to bypass all payload locations. @BlytheScythe Anyway, both of you extract this and use payload.bin for injection (tegrasmash or loader) test.zip

Mariko (all): @mirivedan @Callegari02 I said if it's a mariko you should state it. Try this. Replace payload.bin and update.bin with that. payload.zip

Still not working. emummc and sysmmc show glitch screen but on the top says: Pkg1 decryption failed. Failed to launch HOS. 17.0.1

[Callegari02]

Ho sostituito i vecchi payload.bin e update.bin con l'ultimo payload.zip/bin e continua a non funzionare (Oled)

It says to me "pkg1 decryption failed
pkg1 corrupt?"

[Callegari02]

Erista (V1)@PreHeXTe ne ho dato uno speciale da provare, per bypassare tutte le posizioni del carico utile.@BlytheScytheAd ogni modo, entrambi estraetelo e usate payload.bin per l'iniezione (tegrasmash o caricatore) test.zip
Mariko (tutti):@mirivedan @Callegari02Ho detto che se è un mariko dovresti dichiararlo. Prova questo. Sostituisci payload.bin e update.bin con quello. payload.zip

Continua a non funzionare. emummc e sysmmc mostrano la schermata del problema tecnico ma in alto dice: decrittografia Pkg1 non riuscita. Impossibile avviare HOS. 17.0.0

Me too

[mirivedan]

@lucasaf04 had also that error in one of my attempts

[BlytheScythe]

@CTCaer I don't have much going on on my SD card, really. Pretty much the minimum stuff you need for CFW stuff and that's pretty much it. As for the payloads, I only use update.bin and reboot_payload.bin. I've noticed that you've added payload.bin to the root and hekate.bin in the payloads folder, none of which I usually use. Oh, and the Rekado's payloads which I update manually as well.

I usually update through Hekate's USB tools and just drag and drop, as per instructions. Therefore, update.bin should be up-to-date. As for the reboot_payload.bin, I made sure to update that one.

Maybe the issue lied with the versioning? As soon as you set it to 6.2.1, it magically worked. I'm not entirely familiar with the technical stuff but I'd hate myself to fail at copy-paste. :D

Anyway, thanks for the hard work dealing with all of the issues. Keep up the good work!

[lucasaf04]

Well let's see if @CTCaer finds the issue. Take your time, v6.1.1 works fine.

[CTCaer]

Mariko:
@lucasaf04 @mirivedan @Callegari02
payload.zip

Also what sdram each one of you have? (dram id from helate -> console info -> hw info)

[Callegari02]

Mariko: @lucasaf04 @mirivedan @Callegari02 payload.zip

Inoltre, quale sdram avete ciascuno di voi? (id dram da Helate -> informazioni console -> informazioni hw)

my dram id is: 05: xynix H9HCNNNBKMMLXR - NEE 4GB

[Callegari02]

Mariko: @lucasaf04 @mirivedan @Callegari02 payload.zip

Inoltre, quale sdram avete ciascuno di voi? (id dram da Helate -> informazioni console -> informazioni hw)

I replaced the file but still:
"Pkg1 decryption failed
Pkg1 corrupt?
failed to launch HOS"

[CTCaer]

payload3.zip
btw it would be easier to debug that in discord but anyway

[Callegari02]

payload3.zip tra l'altro sarebbe più semplice eseguire il debug in discord ma comunque

it works now thank you very much

[CTCaer]

@lucasaf04 @mirivedan try payload3 and also report the dram id back.

[mirivedan]

sure
sec

[lucasaf04]

@CTCaer Fixed. Same dram id as @Callegari02
Discord link? just in case

[CTCaer]

you can join retronx discord and then dm me at ctcaer tag.
That whole thing is weird af. The erista issue was straight forward, just a typo and then "pushing" wrong payload from most users.
But the mariko one, is sth else.

[mirivedan]

@CTCaer OFW is ok
CFW boots up but crashes after 10 sec (4 times)

[lucasaf04]

@mirivedan weird, I've been playing since he pushed the fix. I'm on 17.0.1 btw

[mirivedan]

[mirivedan]

I'll put the p3 in hats and try again

[CTCaer]

@mirivedan well I can't actually control what happens inside CFW (old sysmodules, themes, etc). That's atmosphere/HOS side.
That's an ssl error which means you are using cal0 blanking or something which you shouldn't use.
This is the wrong place for such support.

[josete2k]

Have you blanked your prodinfo???

[mirivedan]

I replaced payload.bin and update.bin by payload3 in the Hats package and it seems to be stable now.
Big thanks to @CTCaer for the wondeful skills And thank you all for the support

[CTCaer]

hekate_ctcaer_6.2.0_Nyx_1.6.2_v3.zip was added in release to fix the issues.
Version still at 6.2.0. A new release with 6.2.1 will only happen when I'm sure everything is ok.

Remember to replace reboot_payload.bin if you have erista and use hekate for it.

[CTCaer]

v6.2.1 stable release is out