• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GSI][10] LineageOS 17.x GSI (all archs)

Should I build *vS variants (with PHH-SU)?

  • Build *vS (SU), replacing *vN (no SU)

    Votes: 6 33.3%
  • Build *vS alongside *vN

    Votes: 8 44.4%
  • Keep things as is

    Votes: 3 16.7%
  • Don't care

    Votes: 1 5.6%

  • Total voters
    18
  • Poll closed .
Search This thread

Matty1993

Senior Member
May 7, 2018
631
314
Great work andy mate flashed to MT6580 Konka SP3 running Oreo vndk with 1gb RAM and what was originally 8.1GO /system before being wiped and booted straight up within 15 seconds selinux is Enforcing and can even relock the bootloader and still boots up perfectly fine no more orange state :laugh: i use fastboot to send the image rather than twrp as i need the stock recovery after flash else it only reboots to recovery again instead of system so im assuming it needs stock recovery to create the cyrptofs in order to boot im assuming.

Few bugs i did find are after a few days the camera and flashlight both stop working at same time together for some reason also sometimes after clean flash even unsure if this is just devive specific but i cant get adb logs via shell so will install a logapp and capture the errors and edit this with comment with a link to the log

Fantastic work again anyway i cant install gapps as not enough system space left but idk gapps only slows phone down anyway plenty of other places to find apps so big :good::good: from me
 
Last edited:

osamarin

Member
Jul 3, 2019
8
2
Hello! Great thanks for your ROM. Everything works perfectly and stable on my Samsung A50 except root access.

If I use Magisk installed to the recovery partition (the only way to get Magisk working on my device), often reboots occure.

The modified magisk for phh from https://sourceforge.net/projects/developerluke-roms/files/phh-magisk/ seems does not have an option to install into recovery.

There is no still addonsu for lineageos 17 available.

I'd like to rebuild build LOS 17.1/gsi with WITH_SU=true for eliminating necessarity of magisk. Where can I download the source code of your ROM?
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,290
3,570
Beijing
Hello! Great thanks for your ROM. Everything works perfectly and stable on my Samsung A50 except root access.

If I use Magisk installed to the recovery partition (the only way to get Magisk working on my device), often reboots occure.

The modified magisk for phh from https://sourceforge.net/projects/developerluke-roms/files/phh-magisk/ seems does not have an option to install into recovery.

There is no still addonsu for lineageos 17 available.

I'd like to rebuild build LOS 17.1/gsi with WITH_SU=true for eliminating necessarity of magisk. Where can I download the source code of your ROM?

Magisk does work alright on my A60, but it's a Snapdragon instead of Exynos so probably not that relevant.
You don't need PHH-Magisk for AB.
AddonSU has been abandoned by LOS. Try this repackaged PHH-SU instead.
 

osamarin

Member
Jul 3, 2019
8
2
Has anyone here tried this GSI on any of the Samsung Galaxy A Series (A10, A20, A30, A50 etc.)?

I use it on both A40 and A50.

A40: works everything, including magisk root
A50: works stable without root.

---------- Post added at 04:47 PM ---------- Previous post was at 03:50 PM ----------


Unfortunally, this does not get installed correctly and does not work.

Where is the source code of gsi/lineageos?
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,290
3,570
Beijing
Where is the source code of gsi/lineageos?

Everything needed is already in OP, although they might not be up-to-date (due to reason I mentioned earlier). But let me emphasize - addonsu has been abandoned by upstream and you will not get it whatsoever. Well, unless you ported it over without the Privacy Guard framework, in which case the entire community would thank you for your selfless contribution.
You should politely ask @Spaceminer to debug your case instead.
 

Spaceminer

Senior Member
Everything needed is already in OP, although they might not be up-to-date (due to reason I mentioned earlier). But let me emphasize - addonsu has been abandoned by upstream and you will not get it whatsoever. Well, unless you ported it over without the Privacy Guard framework, in which case the entire community would thank you for your selfless contribution.
You should politely ask @Spaceminer to debug your case instead.

Yes, I definitely want to look at this. I have a feeling that it's the same twrp bug that I'm trying to fix for the Moto G7 Play.
@osamarin

Please send me private message about this. I don't want to clutter up the thread.
 

osamarin

Member
Jul 3, 2019
8
2
You should politely ask @Spaceminer to debug your case instead.

Thanks. I already managed to get phh-su worked on Samsung A50: its installation script does not support the system-as-root layout, so I had to move installed files from /system/system to /system manually.

---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------

Please send me private message about this. I don't want to clutter up the thread.

Please look at PM.
 

Jazzda

Senior Member
Sep 18, 2019
107
14
Ask google
@AndyYan, Thank you very much for this ROM. :cool:
Just replaced /e/ with it in a Redmi7A with no problems and everything is working. I just miss the simple (flat) wallpapers that came with /e/
I only changed the launcher to Evie (I'm used to it), the browser to lightning, and installed latest Magisk to be able to use Battery Change Limit that needs root access to operate.
Really good job :good:
 

Jazzda

Senior Member
Sep 18, 2019
107
14
Ask google
@AndyYan, Thank you very much for this ROM. :cool:
Just replaced /e/ with it in a Redmi7A with no problems and everything is working. I just miss the simple (flat) wallpapers that came with /e/
I only changed the launcher to Evie (I'm used to it), the browser to lightning, and installed latest Magisk to be able to use Battery Change Limit that needs root access to operate.
Really good job :good:

Although It seems that the battery is draining a little too fast compared with /e/ (Pie). Is it a known problem?
 

smvsmv

Senior Member
Nov 16, 2014
180
36
Thanks!


I followed the instructions in the page you linked to. When I tried to flash ROM using fastboot, I get the following error
1. Trying to erase system - Erasing 'system' FAILED (remote: 'Partition table doesn't exist').
2. I tried ignoring that and flashed the ROM anyway. got the error FAILED (remote: 'This partition doesn't exist')

Any idea how to resolve this? I googled and couldn't find anything for this particular error. Admittedly, didn't go beyond page 1 results of google.

My phone is a UMIDIGI power 3 and running Android 10.
 

SHA_NDY

Senior Member
Oct 17, 2013
269
73
I followed the instructions in the page you linked to. When I tried to flash ROM using fastboot, I get the following error
1. Trying to erase system - Erasing 'system' FAILED (remote: 'Partition table doesn't exist').
2. I tried ignoring that and flashed the ROM anyway. got the error FAILED (remote: 'This partition doesn't exist')

Any idea how to resolve this? I googled and couldn't find anything for this particular error. Admittedly, didn't go beyond page 1 results of google.

My phone is a UMIDIGI power 3 and running Android 10.

I can only tell you that it worked in my case (HTC U11 Life) and I'm sorry for not having further ideas.
 
  • Like
Reactions: smvsmv

dhacke

Senior Member
Nov 4, 2018
737
309
I followed the instructions in the page you linked to. When I tried to flash ROM using fastboot, I get the following error
1. Trying to erase system - Erasing 'system' FAILED (remote: 'Partition table doesn't exist').
2. I tried ignoring that and flashed the ROM anyway. got the error FAILED (remote: 'This partition doesn't exist')

Any idea how to resolve this? I googled and couldn't find anything for this particular error. Admittedly, didn't go beyond page 1 results of google.

My phone is a UMIDIGI power 3 and running Android 10.

Mayby this helps:


Devices with Android 10 could have a new partition system which the xda gsi/treble guide doesn't cover. For example my pixel 4 xl has this new partition system.

If this is the case flashing and erasing a system is only possible in fastbootd mode.

So first i would check whether your fastboot is up-to-date and then try the commands in fastbootd mode again.
The command to go into fastbootd is 'fastboot reboot fastboot'.

A little info about fastbootd:
https://source.android.com/devices/bootloader/fastbootd
 
Last edited:

smvsmv

Senior Member
Nov 16, 2014
180
36
@dhacke Thank you! that helped and made some progress.
I was able to erase system and had to "delete_logical_partition system" because of resize error.
Now, when flashing the ROM, I get the below error
Sending sparse 'system' 1/9 (262140 KB) OKAY [ 7.861s]
Writing 'system' FAILED (remote: 'No such file or directory')

at this point, "fastboot getvar current-slot" returns a blank. I have tried both A/B and A only ROMS. Same result.

Reflashed Stock for now.. Hoping you can help take this through.
 
Last edited:

blazzer12

Senior Member
Jun 15, 2012
558
207
Samsung Galaxy A7 (2018)
Reserved

Couple of things to note at this point:
  • PHH's AOSP Android 10 GSIs are still marked as pre-release. Even on a device that runs Pie GSIs nicely, it's still possible to get broken media, camera, RIL or even flat-out no-boot. You are strongly advised to try PHH's original 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.
  • LineageOS 17.x is also still under development. Although most of the basics are already there, some features like custom battery icons are missing or WIP.
  • If using Magisk on an A-only device, a modified Magisk is required.
  • exfat SD cards still don't seem to work. Any help related to this would be appreciated.
  • The feature "Re-enabled lockscreen shortcuts by default" has been dropped - not that it can't be done, but Google again made ugly changes to the lockscreen, and with the shortcuts turned on it looks asymmetric and adds to the ugliness. Lockscreen shortcuts themselves might still come back with a future upstream update, just like how it did in 16.0.
  • In the 16.0 GSIs I've included changes that allow for automatic front camera actions for Xiaomi Redmi K20 Pro, but these have to be reworked for Android 10, and since I'm not using GSIs on my own K20P right now, I'm not interested in doing so. Consider these changes abandoned (for now).

Is this info still relevant? Will you delete this message once all/most things are sorted out?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 101
    640px-Lineage_OS_Logo.png


    Background:
    This is a natural continuation/extension of the LineageOS 16.0 GSIs I've been making since March 2019.
    If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank:
    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, see below
    • Revived navbar layout tuning via sysui_nav_bar tunable
    • Disabled "vendor mismatch" warning on boot
    • Signature spoofing support from MicroG (preliminary patch for Android 10)
    • Default stretch-to-fullscreen (force apps to render in 18:9)

    Extra tip:
    If you have a relatively low-end device and experience UI stutters, try this simple build.prop trick (technically a debug property, so use at your own risk). Thanks @SnapTheRipper for bringing it up!

    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: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.

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

    Couple of things to note:
    • Even on a device that runs Pie GSIs nicely, it's still possible to get broken media, camera, RIL or even flat-out no-boot on Android 10 ones. 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.
    • LineageOS 17.x has lost some features in the process of transitioning to Android 10, e.g. Privacy Guard and built-in SU.
    • If using Magisk on an A-only device, a modified Magisk is required.
    • exfat SD cards still don't seem to work. Any help related to this would be appreciated.
    • The feature "Re-enabled lockscreen shortcuts by default" has been dropped - not that it can't be done, but Google again made ugly changes to the lockscreen, and with the shortcuts turned on it looks asymmetric and adds to the ugliness. Lockscreen shortcuts themselves might still come back with a future upstream update, just like how it did in 16.0.
    • In the 16.0 GSIs I've included changes that allow for automatic front camera actions for Xiaomi Redmi K20 Pro, but these have to be reworked for Android 10, and I'm not interested in doing so (in fact I prefer manual controls). Consider these changes abandoned for now.
    18
    Updated all variants with July security patches and in sync with PHH v221. [Insert obligatory backup-and-test warning here]

    It's been a quiet month on both AOSP and PHH fronts...
    17
    Updated all variants with February security patches and in sync with PHH v212. [Insert obligatory backup-and-test warning here]

    All good and healthy here despite the coronavirus situation (naturally, I just stay indoors all day). Thanks for your concerns :)
    16
    Updated all variants in sync with PHH v208. [Insert obligatory backup-and-test warning here]
    Skipped r18 (December patch) for aforementioned instability.
    No more updates for the rest of 2019! (lol)

    BTW, here's a tip straight from PHH's TG channel, for those who are having trouble with GAPPS setup wizard:
    In ADB:
    adb shell settings put secure user_setup_complete 1
    adb shell settings put global device_provisioned 1
    This should skip the wizard entirely while also setting the proper flags.