Updated all variants with April security patches. [Insert obligatory backup-and-test warning here]
Fun, I didn't do jack (pun intended) about it Guess it was something upstream...I am happy to inform you that the jack problem has been solved with the lineage-18.1-20220414 version, with regards to the Samsung A20e.
[Xiaomi Mi Play: 'lotus']
Hey there... I have a A partition scheme device (Xiaomi Mi Play, 'lotus').
I've attempted to install/boot 18, 17. While they won't even show the boot animation, version 16 is working. I'm using it for couple days.
The questionar: Is it possible to upgrade by flashing 17 or 18 'over it' with an img? Not a clean install, I mean.
Or flashing via twrp or 'fastboot flash system' will result the same as 'dd' command and ultimately will result in data loss?
I'd like to know this way works because I wasnt able to reproduce anything promising by clean installing 17 or 18.
Thanks!
UPDATE:
I've attempted to flash without formatting and performing clean installs. I was unable to make it work. Thanks all.
Huh, I think I didn't make myself clear, but my major concern woulbe be installing LOS18, or 17 but I couldn't managed to do it.
Am getting bootloop in The lastest version...idk if its only me...can anyone confirm?Updated all variants with May security patches. [Insert obligatory backup-and-test warning here]
Sh_t, I made zero changes on my side... I'll spare a test device and investigate. If one of you can log me the boot loop it'll be nice too. Others, please exercise extra caution.Bootloop since this (as other reported above). Using https://sourceforge.net/projects/an...1-20220511-UNOFFICIAL-a64_bvS.img.xz/download Also seems to be happening on the March release. https://xdaforums.com/t/umx-u696cl-unofficial-root-thread.4446111/
E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E AndroidRuntime: java.lang.IllegalStateException: Signature mismatch on system package com.qualcomm.qti.logkit.lite for shared user SharedUserSetting{11ffcb2 android.uid.system/1000}
At least you have ADB. While bootlooping, try:
adb shell
su
pm disable com.qualcomm.qti.logkit.lite
reboot
INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.qualcomm.qti.logkit.lite has no signatures that match those in shared user android.uid.system; ignoring!
@AndyYan thank you for this GSI project. In my case bootloop is at LOS logo. Clean wipe. Do you think exynos-based devices are not compatible with GSI ? thx@gregeerg 's bootloop had been narrowed down to the rogue QCOM LogKit app plus a dirty /data. However, as @keymanhattan 's device is Exynos-based, I suppose this reason doesn't apply to everyone. @Mohinesh @keymanhattan - as the last mentioned message said, waiting on your info.
It's not that clear cut. Go back to that post and post all info as required there.@AndyYan thank you for this GSI project. In my case bootloop is at LOS logo. Clean wipe. Do you think exynos-based devices are not compatible with GSI ? thx
It's not that clear cut. Go back to that post and post all info as required there.
In that case I am disoonnecting the usb and then restart phone pressing vol- + power and then connect usb again.In general (not only for this update) I get a bootloop at the LOS logo after recharging my Samsung A20e from zero battery. However, I discovered that if I simply log to TWRP and from there I select reboot to system I get a normal boot. Maybe this could do the trick in this case as well ...?
...? You should be flashing GSIs from fastboot/d. Custom recovery has never been important.Reason I'm still on OxygenOS is there hasn't been reliable TWRP for Oneplus Nord n100
...
Oneplus Nord N100 is arm64 a/b. I did read the guide on page 1 but I dunno with custom recover it would be so easy and custom recovery is important.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.