[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)

Should I build *B with EXT4 share duplicate blocks?

  • Yes - my /system is small, I need every bit of space saving to make it fit

    Votes: 14 51.9%
  • No - I'm not short on space, and/or I prefer mountable /system

    Votes: 13 48.1%

  • Total voters
    27
  • Poll closed .
Search This thread
Mar 12, 2011
6
0
Fortaleza
[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.
 
Last edited:

Crrrr

Senior Member
[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.

If your problem is data loss you can use the Migrate app.
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,481
3,835
Beijing
Updated all variants with May security patches. [Insert obligatory backup-and-test warning here]

EDIT: Some bootloops happened below. Until those are cleared (resolved, or at least figured out why), exercise extra caution.
 
Last edited:
  • Like
Reactions: ROO3VER

gregeerg

Senior Member
May 12, 2022
106
14
Updated all variants with May security patches. [Insert obligatory backup-and-test warning here]

EDIT: been narrowed down to the rogue QCOM LogKit app plus a dirty /data. Thanks, Andy.

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://forum.xda-developers.com/t/umx-u696cl-unofficial-root-thread.4446111/
 
Last edited:

AndyYan

Recognized Contributor
Jan 30, 2012
4,481
3,835
Beijing

gregeerg

Senior Member
May 12, 2022
106
14
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.
EDIT: been narrowed down to the rogue QCOM LogKit app plus a dirty /data. Thanks, Andy.

Sent PM.
 
Last edited:

AndyYan

Recognized Contributor
Jan 30, 2012
4,481
3,835
Beijing
What @gregeerg sent me:
Code:
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}
Looks like the OS is tripping over a non-standard vendor app, and even more unexpectedly, if I understand correctly, happens on a clean wipe too.

@Mohinesh @keymanhattan Please post here in public (no PMs - leave debug traces available for searching in the future):
At least 1) which phase you looped at (OEM logo? LOS logo?), 2) wiped data or not and 3) does PHH's final AOSP R build work for you;
And ideally 1) logcat on this release, and 2) which (if any) previous LOS release once worked.
 
Last edited:

gregeerg

Senior Member
May 12, 2022
106
14
What @gregeerg sent me:
Code:
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}
Looks like the OS is tripping over a non-standard vendor app, and even more unexpectedly, if I understand correctly, happens on a clean wipe too.

@Mohinesh @keymanhattan Please post here in public (no PMs - leave debug traces available for searching in the future) - at least tell me which phase you looped at (OEM logo? LOS logo?), wiped data or not; ideally, logcat on this release, and which previous release once worked.
EDIT: been narrowed down to the rogue QCOM LogKit app plus a dirty /data. Thanks, Andy.

Correct, clean wipe/install. Not sure how to proceed.
 
Last edited:

AndyYan

Recognized Contributor
Jan 30, 2012
4,481
3,835
Beijing
Correct, clean wipe/install. Not sure how to proceed.
At least you have ADB. While bootlooping, try:
Code:
adb shell
su
pm disable com.qualcomm.qti.logkit.lite
reboot
And see if it goes further. If not, more logs, it might get stuck on some other apps.

I've added some more needed info on the above post, please go through and let me know what you missed too.

Also, I've tried reproducing on my side using a copy of the app I found in FairPhone 3. Unfortunately I can only semi-reproduce it - it does spew out a similar error on directly installing the APK:
Code:
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!
...but when embedded into vendor, it doesn't cause a bootloop and seems to just get ignored silently with no mentions of it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Updated all variants with July security patches. [Insert obligatory backup-and-test warning here]

    The nexT big Thing is around the corner, so in preparation I'll clear 18.x off my drive in a week. This will be the final batch of 18.x builds from me.

    As a farewell gift of sorts, I present to you GAPPS variants - regular for A64/64, and Go for 32/A64, matching the combo from PHH's AOSP. Compound that with A-only and VNDKLite, and we get a whopping 16 variants and close to 200GB of disk space eaten up by build artifacts (see why I didn't make them earlier?).
    I myself have minimally tested regular GAPPS by logging in and downloading an app from Play, while another user had daily driven it for a few days with no issues reported; Go GAPPS is entirely untested. Regardless, GAPPS will be treated with the same principle as 19.x - builds are offered as-is without guarantees, and you'll have to help each other out on GAPPS-related/-induced issues.
    To deal with the Play Protect certification error, visit here.
  • 50
    640px-Lineage_OS_Logo.png


    Background:
    This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019.
    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.

    Disclaimer:
    This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
    No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
    No guarantees that everything would work. This is a GSI, bugs are bound to happen.

    Download:
    https://sourceforge.net/projects/andyyan-gsi/files/
    Compressed as .xz archives - extract first.
    Vanilla except for these changes:
    • Modifications needed to make it build/boot/feature-complete
    • Revived navbar layout tuning via sysui_nav_bar tunable
    • Disabled "vendor mismatch" warning on boot
    • Signature spoofing support from MicroG
    • Default stretch-to-fullscreen (force apps to render in longer than 16:9)

    Stuff on GitHub (builders-only):
    Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: lineage_build_unified, lineage_patches_unified (where patches_treble_phh contains PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.

    Donate?
    https://paypal.me/AndyCGYan
    20
    Reserved

    Couple of things to note:
    • I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student.
    • As always, you are strongly advised to try PHH's AOSP first and identify/report issues there, before moving onto other GSIs that are based on his work. Please report bugs here only if it's specific to this GSI.
    • Thanks to patches from @eremitein , Magisk compatibility is partially restored. For devices that still don't play well with it (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.
    • A-only and VNDKLite targets are now generated from AB images instead of built from source, see sas-creator. Kinda hacky and might be buggy. Move on to an AB device if you can.
    • To mount /system RW on AB devices, refer to this.
    • exfat SD cards still don't seem to work. Any help related to this would be appreciated.
    9
    Initial builds are based on PHH v300.j and December security patches.
    Building-related bits have been published, but only for AB targets - I'm not sure if I want to integrate sas-creator yet.
    9
    March patch is ready, but due to lack of time, I'll have to postpone this month's update for a while. I worked on it yesterday but couldn't figure out a core problem in time.
    9
    Updated all variants with March security patches and in sync with PHH v302. [Insert obligatory backup-and-test warning here]

    Two years of GSIs. Life is trying to rob me of this "hobby" - I'll keep this going as long as I can handle it.