[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

AboodySahhaf

Member
Dec 14, 2017
42
2
Why is there no flash system in TWRP? is there a way to install a ROM GSI on galaxy note 20 ultra ?
IMG_20210112_013052__01.jpg
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,778
4,414
Beijing
Updated all variants with January security patches and in sync with PHH v300.l. [Insert obligatory backup-and-test warning here]

@eremitein kindly let me pick his changes again - among which is restoration of /sbin, so we probably have Magisk support again, but I haven't tested this personally.

AB VNDKLite users, please be extra careful with this build. Just a hunch.
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,778
4,414
Beijing

AyHenry

Member
Apr 7, 2020
37
9
Google Pixel 2 XL
Updated all variants with January security patches and in sync with PHH v300.l. [Insert obligatory backup-and-test warning here]

@eremitein kindly let me pick his changes again - among which is restoration of /sbin, so we probably have Magisk support again, but I haven't tested this personally.

AB VNDKLite users, please be extra careful with this build. Just a hunch.
Please I beg you in the name of God, Don't include dynamic SU like eternityson did in CAOS, that stuff messes with magisk modules that requires terminal emulator. Please stick to bvs or bvn builds. Thanks for the great work, more grease to your elbow
 
Last edited:

AndyYan

Recognized Contributor
Jan 30, 2012
4,778
4,414
Beijing
Please I beg you in the name of God, Don't include dynamic SU like eternityson did in CAOS, that stuff messes with magisk modules that requires terminal emulator. Please stick to bvs or bvn builds.

Hoo, I didn't pick dynamic SU for now (more cuz I'm lazy), guess I made the right call?

Just tried installing the latest on a Razer Phone 2. No go on Magisk support.

I did hear that it takes more than just simply flashing to get Magisk to work (e.g. here), maybe that'd help?
 

eremitein

Senior Member
May 16, 2017
1,178
1,520
Xiaomi Mi A2 Lite
Please I beg you in the name of God, Don't include dynamic SU like eternityson did in CAOS, that stuff messes with magisk modules that requires terminal emulator. Please stick to bvs or bvn builds. Thanks for the great work, more grease to your elbow
it can messed only if you enabled SuperUser. if you want using Magisk just don't use superuser
(also you can call module's commands like /data/adb/modules/MagiskHidePropsConf/system/xbin/props)
 

alvinprimo

Senior Member
Updated all variants with January security patches and in sync with PHH v300.l. [Insert obligatory backup-and-test warning here]

@eremitein kindly let me pick his changes again - among which is restoration of /sbin, so we probably have Magisk support again, but I haven't tested this personally.

AB VNDKLite users, please be extra careful with this build. Just a hunch.
This fix sound on aonly vndk 26? Or I have to replace media.ecxtractor.policy again?
 

IamTheBRAVE

Senior Member
it can messed only if you enabled SuperUser. if you want using Magisk just don't use superuser
(also you can call module's commands like /data/adb/modules/MagiskHidePropsConf/system/xbin/props)
Yes you are right, the superuser in this gsi is on by default. @AyHenri needs to go to PHH's Settings >Misc > Securise to remove root first.
Edit: sorry, was thinking of another gsi, haven't tried this one yet. In some other gsis, superuser is off by default and needs to be activated in PHH's Settings > Misc > turn on superuser.
 
Last edited:

aeGea

New member
Jun 3, 2020
4
0
Is phh setting exists in this build?
Cant find it

edit. nvm. im a dumb
 
Last edited:

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.