Unable to boot Android on v6.2.0 with erista (v1) switch

[Mika58Carca]

Hello
I am writing to you because indeed, since the new update of hekate recently, console switch refuses to boot on Android.
It stays on the start screen and then nothing, forced to force the console off and then restart it.
Android runs on the old hekate update ( hekate v6.1.1 & Nyx v1.6.1 )

[CTCaer]

Since you actually checked to make sure there's a difference, what model you have?
And ofc which android flavor

[Mika58Carca]

Since you actually checked to make sure there's a difference, what model you have? And ofc which android flavor

To answer you, the model of my switch is a V1 erista.
I'm running Android with lineageos 11 of memory.
Android works very well on hekate 6.1.1 but since the final version, it doesn't work anymore, I have to downgrade the version of hekate to make Android work again

[RoblKyogre]

can also confirm that downgrading hekate to 6.1.1 fixed both this and #978 for me
i have a XAW1000 switch (so v1 erista), am running lineageos 18.1 (android 11) and fedora 39 kde (did actually attempt an install after upgrading to 6.2.0, it didn't boot then but booted when i downgraded to 6.1.1)

[maximo12345git]

can also confirm that downgrading hekate to 6.1.1 fixed both this and #978 for me i have a XAW1000 switch (so v1 erista), am running lineageos 18.1 (android 11) and fedora 39 kde (did actually attempt an install after upgrading to 6.2.0, it didn't boot then but booted when i downgraded to 6.1.1)

But you did downgrade Custom firmware also? cause I treid to put back old Hekate but I've had an error on reload

[Mika58Carca]

can also confirm that downgrading hekate to 6.1.1 fixed both this and #978 for me i have a XAW1000 switch (so v1 erista), am running lineageos 18.1 (android 11) and fedora 39 kde (did actually attempt an install after upgrading to 6.2.0, it didn't boot then but booted when i downgraded to 6.1.1)

But you did downgrade Custom firmware also? cause I treid to put back old Hekate but I've had an error on reload

In Hekate 6.1.1, atmosphere no longer works following the new Switch update 16.1.0 And Android works again.
In Hekate, the latest current update, atmosphere works again with the new Switch 16.1.0 update but Android doesn't work anymore

[RoblKyogre]

can also confirm that downgrading hekate to 6.1.1 fixed both this and #978 for me i have a XAW1000 switch (so v1 erista), am running lineageos 18.1 (android 11) and fedora 39 kde (did actually attempt an install after upgrading to 6.2.0, it didn't boot then but booted when i downgraded to 6.1.1)

But you did downgrade Custom firmware also? cause I treid to put back old Hekate but I've had an error on reload

i've actually yet to update to 18.1.0, so am still able to use cfw currently (6.1.1 doesn't support the latest firmware, 6.2.0 does)
will wait to upgrade until this gets fixed tho

[urherenow]

I finally had the chance to try the latest hekate and Atmosphere on my OLED, and I haven’t been able to reproduce any problem posted about the latest update. Emummc -> reboot -> emummc, no problem. Launching lineage 18.1, no problems. My console is not updated to 18 though, because I simply don’t have the bandwidth to download it right now. My v1 switch is at home so no testing that until December…

[CTCaer]

Fixed the issue. Get _v4.zip

[Mika58Carca]

Fixed the issue. Get _v4.zip

Thanks for your fix, everything works again with the latest version of hekate ! 😎

[josete2k]

Problems here with OLED.

Panic kernel with 6.2.0 v4.

This 6.1.1 compiled with 18.1.0 support works.

https://gbatemp.net/threads/rcm-payload-hekate-ctcaer-mod.502604/post-10438348

[CTCaer]

@josete2k This is the wrong issue, move to #969
(You are supposed to replace payload.bin, although with 6.1.1 as it you can just place the bootloader folder now)

[josete2k]

@josete2k This is the wrong issue, move to #969 (You are supposed to replace payload.bin, although with 6.1.1 as it you can just place the bootloader folder now)

Ops sorry.

Just for clarification:

I always replace all bin files in my SD.. payload.bin, reboot_payload.bin, update.bin and hekate.bin (this last in bootloader/payloads folder).

But with v4 I get a kernel panic message (when launching Android) in yellow letters, not blue o glitched screen... This is why I thought that this issue is the same I have.

HOS works fine as expected.

[CTCaer]

You talked about hos 18.1.0. Be specific without anything random remarks.
(because there's panic krnl for hos also and you could have used official 6.1.1 for that test.)

Nothing should affect L4T on mariko. Get the l4t panic log (L4T_panic.bin) since that's way after hekate.
And I suggest you to contact me in discord since it's easier to share files in succession there.

(Btw reboot_payload.bin is not used on mariko, as for the /payloads one, dunno why you use it)

[josete2k]

I know that about reboot_payload.bin , but I have an erista V1 too and I share same files for both consoles.

L4T_panic.bin is present in the SD but it's empty... I've checked with winhex.

I'll retry again in a few moments.

Thanks in advance.

EDT: Strange, it works now with v4 (windows had to repair SD). So sorry for bother you...

[CTCaer]

It's not readable at its whole. Only some KB out of the 2MB.
Don't try to micromanage that, because it has a certain binary format (yeah even the readable parts are part of that) and also has different behavior on mariko.
I need the file on its whole.

[CTCaer]

EDT: Strange, it works now with v4 (windows had to repair SD). So sorry for bother you...

Yeah that's why all that was weird. The 6.2.0 update basically only affected 3 paths:
erista HOS (unintended)
mariko HOS
erista L4T (unintended)

All 3 should be fixed on v4.

Anyway, many users normally use the switch on weekends, so the final proper release will happen early next week.
So there's still time for more testing.

[kevbenjam]

Thanks for trying to fix the issue with v4 @CTCaer. For me L4T is still not working via hekate 6.2.0 on Erista with Lineage OS 18.1 / 21. It hangs directly after showing "USB3 enabled" in the upper left corner.

[CTCaer]

Since you see uboot printing a message (usb3 enabled), it's not that issue. The recent regression doesn't even reach uboot or TZ fw.
Either you didn't follow the android guide to the letter or your sd card or reader might have issues.

[CTCaer]

v6.2.1 stable release is out