Blue screen or weird mariko issue about hekate HOT 83 CLOSED

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.

from hekate.

@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.

from hekate.

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

from hekate.

@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
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.

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.

from hekate.

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

it works now thank you very much

from hekate.

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

from hekate.

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

from hekate.

@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.)

from hekate.

@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!

from hekate.

@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.

from hekate.

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

from hekate.

Fix for every Erista Model/Switch v1

Launch latest Hekate

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

it works thank you very much

from hekate.

@CTCaer I tried PreHeX's update.bin and it works. I've also just tried the test you've sent and it works as well. I do find it hard to believe that I haven't updated all the necessary paylaods (even after a multiple times) but I'm glad it works properly now. Thank you so much!

Well it's the same exact payload (the one in updated release), just copied pasted in every known location and filenames.
That's the issue with erista and every loader out there. Everyone used every single random place.
Anyway on the real update, that won't be needed since update.bin will have version 6.2.1 or 6.2.2.

from hekate.

@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!

from hekate.

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

from hekate.

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

from hekate.

v6.2.1 stable release is out

from hekate.

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

from hekate.

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

from hekate.

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.

from hekate.

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

from hekate.

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

from hekate.

I confirm, it doesn't work

from hekate.

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

from hekate.

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.

from hekate.

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

from hekate.

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.

from hekate.

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

from hekate.

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

from hekate.

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

from hekate.

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

from hekate.

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?

from hekate.

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

from hekate.

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

from hekate.

Also I use TegraRcmGui with the latest hekate.bin

from hekate.

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.

from hekate.

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

from hekate.

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.

from hekate.

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).

from hekate.

@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.

from hekate.

Yeah,works fine with 6.1.1

from hekate.

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

from hekate.

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

from hekate.

@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.

from hekate.

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

from hekate.

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?

from hekate.

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?

from hekate.

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?

from hekate.

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

from hekate.

@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.)

from hekate.

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

from hekate.

Thank you for the patience guys

from hekate.

@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

from hekate.

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

from hekate.

@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

from hekate.

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

from hekate.

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"

from hekate.

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

from hekate.

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.

from hekate.

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

from hekate.

Un'installazione pulita su 2 diverse schede SD mi dà una schermata nera o un arresto anomalo dello schermo sia su OFW che su CFW

It works like this for me too, if I put hetake 6.1.1 it works otherwise it doesn't work and it does what it does for you

from hekate.

If i inject the new fusee.bin i can access atmosphere but it always crashes after 10 seconds
And yes its an Oled (sorry)

from hekate.

@PreHeX so you didn't update one of the relevant payloads.
That test.zip basically had all relevant locations that the payload could be.

from hekate.

@CTCaer I tried PreHeX's update.bin and it works. I've also just tried the test you've sent and it works as well.
I do find it hard to believe that I haven't updated all the necessary paylaods (even after a multiple times) but I'm glad it works properly now. Thank you so much!

from hekate.

@PreHeX so you didn't update one of the relevant payloads. That test.zip basically had all relevant locations that the payload could be.

Okay got it

from hekate.

I replaced the old payload.bin and update.bin with the last payload.zip/bin and still doesn't work (Oled)

from hekate.

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

from hekate.

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?"

from hekate.

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

from hekate.

@lucasaf04 had also that error in one of my attempts

from hekate.

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

from hekate.

Mariko:
@lucasaf04 @mirivedan @Callegari02
payload.zip

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

from hekate.

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

from hekate.

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"

from hekate.

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

from hekate.

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

from hekate.

sure
sec

from hekate.

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.

from hekate.

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

from hekate.

from hekate.

I'll put the p3 in hats and try again

from hekate.

@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.

from hekate.

Have you blanked your prodinfo???

from hekate.