LeOS 20 for Samsung A51

[grm34]

Hi harvey,

I was using LeOS-R without any worries until the July 2022 version, but bootloop with any new R version on my Samsung A51 (4G).

To get security updates and because R no more maintained, I updated my firmware to A13 and now I'm getting bootloop with any version (R, T, 20). I'm currently stuck on an unofficial version of LOS20 (the only which boot).

I'm thinking of the kernel (BlueFly2.0 versus GrassKernel on A13). Any idea how to get me unstuck? Bootloop even after flashing the kernel after ROM.

Thanks a lot.

[LeOS-GSI]

If you have A13 firmware you can only use A13 or above GSIs. Is it original OEM A13 firmware ? If yes, do you have a vbmeta partition ? If you have you flashed vbmeta.img with the special command ?

A GSI is created to work with original OEM firmware. If you are using custom firmware it will cause issues most time. Some users have used a custom LOS-20 ROM (not GSI) to upgrade firmware. In some cases that is working.

I have searched my telegram group and it seems, only LeOS-R is working on A51. LeOS-20 is not working

[grm34]

I was on X00TD with Pie firmware on A11 GSI before this f** Samsung.

It's official Samsung fw (bin6) and yes I have 2 vbmeta partitions. I'm gonna look on this, vbmeta was included with twrp.

I'm already using LOS 20 and that's not help.

Thanks a lot for your answer.

[LeOS-GSI]

I'm already using LOS 20 and that's not help.

LOS-20 rom or GSI ??

[grm34]

A rom but it's an unofficial one.

[grm34]

Incredible Samsung.

I can wipe only :

• Dalvik/ART Cache
• Data
• Internal Storage
• Cache

Flash onto :

• Boot
• DTBO Image
• Odm-Image
• Optics Image
• Prism Image
• Product Image
• Recovery
• System Image
• Param
• Vbmeta Samsung
• Vbmeta System
• Vendor Image
• Super (system vendor product odm)

And I have to flash a patch first to be allowed to flash img onto System.

[LeOS-GSI]

Sorry, don't know what you are meaning. GSI must be flashed in system partition and vbmeta in vbmeta partition. So what is the issue ?