[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

knoelli

Member
Jul 26, 2020
7
2
Hamburg
i think you forgot to remove /system/xbin/su as well
Another tip: add an empty file called "secure", permission 644 at /system/phh will pass SafetyNet
Thanks a lot for your input. I'll check with AndyYan's next update to add /system/phh/secure, passing SafetyNet would be a nice feature. However, /system/xbin/su does not exist in the rom.
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,558
4,000
Beijing
AOSP Android 12 source has dropped just now, and unlike previous years, this time I'm joining the day-1 fun in my way.
I've already (re-)done most of my frameworks_base personal mods and, as a demo, applied them on top of an aosp_arm64 build, which you can download here. It's also RW-enabled so you can poke around it further. The modifications themselves are open-sourced here, some of which could be of use to custom ROM makers.
Note that, booting- and feature-wise, this would be no different from Google's aosp_arm64 build, so if you're looking for a daily driver, this isn't it.

EDIT: Emphasize that this build is merely an appetizer/demo - it won't get support or updates.
 

Attachments

  • Screenshot_20211005-000022.png
    Screenshot_20211005-000022.png
    102.7 KB · Views: 1,967
  • Screenshot_20211005-000004.png
    Screenshot_20211005-000004.png
    2.1 MB · Views: 1,973
  • Screenshot_20211005-000052.png
    Screenshot_20211005-000052.png
    2.2 MB · Views: 1,963
Last edited:

Zool_Cz

Member
Mar 28, 2006
34
13
Sedlcany
zool.sw22.cz
Hi guys,
I'm looking for some custom ROM for Lenovo K9 4GB RAM (L38043 Android 8.1.0).
Assembly number L38043_ROW_OPEN_USER_M6762_O_MTK_4G_S0301_18A11.
Is this ROM compatible with this phone?
Thx Jenda
 
Last edited:

Crrrr

Senior Member
Hi guys,
I'm looking for some custom ROM for Lenovo K9 4GB RAM.
Is this ROM compatible with this phone?
Thx Jenda

Hi, this is a GSI, so it isn't device specific. However, you should first learn what type of device and arhitechture you have, to know what file to install.

To start with, you can install an app that tells you this, for example this Treble info app: https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

First, you need your device to be compatible with Project Treble.

Secondly, to select the right file, you need to see (i) if your device is compatible with vndk, (ii) if it is A, A/B etc. (iii) if it is arm64, a64 etc.
 
  • Like
Reactions: Zool_Cz

Zool_Cz

Member
Mar 28, 2006
34
13
Sedlcany
zool.sw22.cz
Hi Crrrr,
I used to check it in app Treble Check and Droid Hardware Info and here is the info:
This device support Project Treble.
Architecture is ARM64.
Device is not rooted yet, first I need to check if the ROM is compatible, then I can perform a root.
Required image is: system-arm64-aonly-vndklite.img.xz so this is correct image:
lineage-18.1-20210914-UNOFFICIAL-treble_arm64_bvS-vndklite.img.xz ?

Thx for pushing me further Jenda
 

Crrrr

Senior Member
Hi Crrrr,
I used to check it in app Treble Check and Droid Hardware Info and here is the info:
This device support Project Treble.
Architecture is ARM64.
Device is not rooted yet, first I need to check if the ROM is compatible, then I can perform a root.
Required image is: system-arm64-aonly-vndklite.img.xz so this is correct image:
lineage-18.1-20210914-UNOFFICIAL-treble_arm64_bvS-vndklite.img.xz ?

Thx for pushing me further Jenda

You missed a step, you didnt look if your device is A-only or AB. From what you wrote, your device may be A-only.

lineage-18.1-20210914-UNOFFICIAL-treble_arm64_bvS-vndklite.img.xz is for AB devices.

Read with more attention. Take your time!

If you look with more attention at the link to the download, you also have some explanations there:

treble_arm_av* ARM 32-bit, A-only 32A treble_arm_bv* ARM 32-bit, AB 32B treble_a64_av* ARM 32-bit with 64-bit binder, A-only A64A treble_a64_bv* ARM 32-bit with 64-bit binder, AB A64B treble_arm64_av* ARM 64-bit, A-only 64A treble_arm64_bv* ARM 64-bit, AB 64B
 

Crrrr

Senior Member
AOSP Android 12 source has dropped just now, and unlike previous years, this time I'm joining the day-1 fun in my way.
I've already (re-)done most of my frameworks_base personal mods and, as a demo, applied them on top of an aosp_arm64 build, which you can download here. It's also RW-enabled so you can poke around it further. The modifications themselves are open-sourced here, some of which could be of use to custom ROM makers.
Note that, booting- and feature-wise, this would be no different from Google's aosp_arm64 build, so if you're looking for a daily driver, this isn't it.

Hi, unfortunately I wasn't able to boot after install. I tried a few times and even by using the TWRP option reboot to system.

Samsung A20e.
 

Atanassoww

Senior Member
May 14, 2019
164
26
AOSP Android 12 source has dropped just now, and unlike previous years, this time I'm joining the day-1 fun in my way.
I've already (re-)done most of my frameworks_base personal mods and, as a demo, applied them on top of an aosp_arm64 build, which you can download here. It's also RW-enabled so you can poke around it further. The modifications themselves are open-sourced here, some of which could be of use to custom ROM makers.
Note that, booting- and feature-wise, this would be no different from Google's aosp_arm64 build, so if you're looking for a daily driver, this isn't it.

EDIT: Emphasize that this build is merely an appetizer/demo - it won't get support or updates.
Can i install it on Redmi 9T (juice)? I am currently using xiaomi.eu rom
 

Tropaion

Senior Member
Jan 4, 2021
56
67
Hi, I'm new to treble an read a bit about it, pretty interesting concept.
I have a tablet which supports it: "Device supports Project Treble. VNDK 30.0 is bundled alongside it. Seamless System Update is also supported (A/B system partition). Arch: 64bit ARM, system-as-root is also supported."

So it looks to me that this ROM does work.
But is it also useable with tablets?
 

Crrrr

Senior Member
Hi, I'm new to treble an read a bit about it, pretty interesting concept.
I have a tablet which supports it: "Device supports Project Treble. VNDK 30.0 is bundled alongside it. Seamless System Update is also supported (A/B system partition). Arch: 64bit ARM, system-as-root is also supported."

So it looks to me that this ROM does work.
But is it also useable with tablets?

Always do a back-up beforehand, for example with TWRP. If for your tablet you do not have a custom rom, you can try a GSI. Usually, for the most used devices you can find a customized custom rom on XDA. For te rest, your only option is a GSI. You need to do your research.
 

Tropaion

Senior Member
Jan 4, 2021
56
67
Normally I use LineageOS or ArrowOS for every device I have, but sadly for newer tablets there aren't many ROMs and I don't someone will make one for the Xiaoxin Pad Pro 2021. Maybe in holidays I will try to make one since I'm an IT student.
But it looks there isn't even an TWRP for my tablet.
 

Unmesh 9830

Member
Oct 2, 2021
14
1
Hi, this is a GSI, so it isn't device specific. However, you should first learn what type of device and arhitechture you have, to know what file to install.

To start with, you can install an app that tells you this, for example this Treble info app: https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

First, you need your device to be compatible with Project Treble.

Secondly, to select the right file, you need to see (i) if your device is compatible with vndk, (ii) if it is A, A/B etc. (iii) if it is arm64, a64 etc.
What is vndk
 

Chaplin0906

Senior Member
Sep 10, 2021
66
11
AOSP Android 12 source has dropped just now, and unlike previous years, this time I'm joining the day-1 fun in my way.
I've already (re-)done most of my frameworks_base personal mods and, as a demo, applied them on top of an aosp_arm64 build, which you can download here. It's also RW-enabled so you can poke around it further. The modifications themselves are open-sourced here, some of which could be of use to custom ROM makers.
Note that, booting- and feature-wise, this would be no different from Google's aosp_arm64 build, so if you're looking for a daily driver, this isn't it.

EDIT: Emphasize that this build is merely an appetizer/demo - it won't get support or updates.
Can vndk-lite a/b support this gsi ?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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.
    10
    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
    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.
    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.