[GSI][13] LineageOS 20 TrebleDroid-based

Search This thread

sanjibukai

Member
Apr 2, 2016
21
2
Hello all..
I have a question that can be related to the previous question..
So I have a working LineageOS 20 on my phone (Poco M4 Pro 4G) which is also rooted with Magisk.

Now I wanted to install Gapps, but it seems the only way to do it is to use a custom recovery (TWRP).
The problem is that TWRP seems to not exist for my device and unofficial TWRP are stated to be only compatible with Android 11 (on my device the latest stock ROM is under Android 12)..

Do I need to rollback to a previous version of Lineage OS under Android 11 (or even using an older stock ROM) in order to have a working TWRP?

Isn't there another way to install a custom recovery?

I guess that in any caseif I succeed to have a working TWRP, I'll need to start over Magisk and Lineage OS installation, right?

Or maybe is there a way to just install the Gapps without using a recovery?
It seems the distribution preferred by LineageOS is MindTheGapps https://www.xda-developers.com/download-google-apps-gapps/
 

sanjibukai

Member
Apr 2, 2016
21
2
There's a pre-GAPPS'd variant (*_gN).
I did installed that one: lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img which I belied should be one with Gapps, eight?
But it seems that all in all, among the Gapps, there's only Google, Play Store and Voice Search.
So I thought that I still needed to install MindTheGapps (or any other gapps distrib) in order to have a little more..
 

uschipower

Senior Member
Mar 14, 2009
110
9
Someone who hasn't heard of Magisk, what a rare sight these days...
you misunderstood me
I know Magisk, and also DeltaMagisk

You wrote "Root with Magisk. Yes these do support Magisk out of the box, usually no need to do Securize or weird stuff."

I am not sure if you meant to use
lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img
which shall include SU, and Magisk-App is only the app which control su (you wrote "S: *Built* with PHH Superuser (app needed)"
or
if I should use Magisk normally on
lineage-20.0-20230324-UNOFFICIAL-arm64_bvN-vndklite.img
and patch boot-partition.

I have tested to patch boot in arm64_bvN-vndklite.img. This seems that this doent work.
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,713
4,260
Beijing
So I thought that I still needed to install MindTheGapps (or any other gapps distrib) in order to have a little more..
The integrated one is already MTG. Download the "heavier" apps straight from Play Store, no reason to further blow up the size of the images (which already prevents some older devices from flashing).
I am not sure if you meant to use...
You want both Magisk and GAPPS, so pair it with a *_gN image.
Unfortunately, if Magisk doesn't want to work with GSIs on your device, then none of us are really in a position to help you (the author is kinda anti-GSI). *_gS is also not an option, since PHH-SU is known to disturb SN.
 

uschipower

Senior Member
Mar 14, 2009
110
9
@AndyYan
Because I was asked in another thread, does your *.img change/modify/add something on boot partition?
Which partitions are affected/changed when flashing your *.img?
Thanks.

@ all
have anybody rooted his device with one of AndyYan's *N-*.img (= Images without integrated PHH Superuser) successfully with Official Magisk or MagiskDelta?
 
Last edited:

Hatrackman

Senior Member
Feb 25, 2015
72
1
51
Victoria
www.capitaldaily.ca
@AndyYan
Because I was asked in another thread, does your *.img change/modify/add something on boot partition?
Which partitions are affected/changed when flashing your *.img?
Thanks.

@ all
have anybody rooted his device with one of AndyYan's *N-*.img (= Images without integrated PHH Superuser) successfully with Official Magisk or MagiskDelta?
Ya, I got Magisk. I'm running lineage-20.0-20230322-UNOFFICIAL-gsi_arm64_gN and just flashed it right after I flashed that using a patch previously generated through it's app.
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,713
4,260
Beijing
Because I was asked in another thread, does your *.img change/modify/add something on boot partition?
Which partitions are affected/changed when flashing your *.img?
Only /system.

I see you're asking around whether other GSIs support Magisk better. This is quite device-specific, and even if people report success with all sorts of other devices, yours might not necessarily do.
 

uschipower

Senior Member
Mar 14, 2009
110
9
just flashed it right after I flashed that using a patch previously generated through it's app.
Which device do you have?
Did you use the Magsik app to modify a boot-Image-File which you you have flashed then.
Or did you use Recovery to patch installed boot-partition directly?

If using boot-File, where have you taken from the file? From latest stock-rom?
 
May 17, 2020
8
0
Port Harcourt
Screenshot_20230329-124944_Chrome.png
howfo I fix this color error
 

sso003

Member
Sep 3, 2012
30
22
Big thanks @AndyYan . I'm using this GSI as my daily driver on a Lenovo Legion Y70 and it works great. I truly appreciate your contribution to this community.
 
  • Like
Reactions: sanjibukai

sanjibukai

Member
Apr 2, 2016
21
2

wojtekojtek

Senior Member
Nov 29, 2022
60
15
Poland
Microsoft Lumia 950/950 XL
This is a universally useful and non-intrusive (default OFF) mod, so I added it to TD as well.
LOS has "rooted debugging" in Developer Options. Turn that on then "adb root" for a rooted shell.

I just realized that you've been comparing across devices, i.e. you aren't controlling variables properly...

This might actually happen - I'm starting to observe it on some very recent OPlus (=OPPO+OnePlus+Realme) devices. Unfortunately I don't have a way out, nor am I really interested in checking "why" at the moment. Perhaps use Magisk for /system changes instead?
Okay
I have now system rw
but
1) how to chnge bootanimation? there's no /system/media folder...
2) how to make /vendor rw?
3) how to DisableForcedEncryption?
 

m0byn

Senior Member
Feb 13, 2023
73
15
One thing, though: Whenever I try to register my fingerprint, systemui immediately crashes. Maybe the attached log helps to find the cause? Thanks!

Edit: The issue is fixed in latest Treble Droid release: https://github.com/TrebleDroid/plat...mmit/2f67d9f7b996f4143a1fcc7dc1a64819ab3b5429.
Does it already work for you? I tried it on my Samsung Galaxy A50 on the March bvN variant and it shows the exact same behavior!
EDIT: this is the logcat

Edit: @AndyYan is there a way to know if the mentioned fix is included in the current version of LOS? The Samsung A50 shows the exact same behavior as described in the quoted post!
 

Attachments

  • logcat_fingerprint_a50.txt
    773.5 KB · Views: 8
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I've decided that I'm skipping this month's update to LOS20 Light/TD. Please read #290 in Light for details.

    If I enable the spoofing option the apps still don't work.
    At least tell what the apps are? Although in #2 I did state that I can't help with GAPPS/SN, I might still try... when I have time.
    I just wanted to suggest the use of torrents as a means of distributing your GSI images.
    SF provides statistics; I doubt torrents would allow me to accumulate accurate statistics?
    There also isn't a compelling reason on my side. I need faster and more convenient uploads, and SF offers SFTP which runs at a good rate over VPN.
    I've already verified that the issue also exists on all of @phhusson's AOSP builds after that date.
    I've diffed patches before/after the dates you mentioned, there are BT-related patches, but are either dormant (only activates on command) or applies to specific vendors.
    If you've pinpointed dates on TD AOSP, please tell me the dates (these are more precise than my monthly updates, you now). If you're fed up with my incompetence/inactivity, try contacting PHH too (the TG group might get you more attention).
    1
    Evening all, I have the latest BVN A64 Andy Yan image installed on my SM-T510 after initially following MagenDanz' guide including his version of TWRP but am still having issues with powering the device off? Also I am unable to install magisk

    I get an error stating " Failed to mount system_root, I have flashed multi disabler previously in TWRP

    Thanks in advance

    Issues powering off from where? TWRP? Android?

    If the partitions in your super partition don't have shared_blocks, you should be able to mount it this way from TWRP terminal:

    mount -o rw,remount /
    mount -o rw,remount /system_root

    This of course assumes you have a super partition.

    As for Magisk, just patch your stock boot.img, flash with Odin from download mode.
    1
    Apologies, from the system, I hold power button, select power off and it just sits there until I have to hold down both volumes and power button
    Never seen this behavior on any gsi that I've ran on both of my Samsung devices.
    1
    According to other posts its a common fault on the SM-T510? I suppose ill just have to never turn it off ha, usb file transfer works fine along with everything else I've tested and its much snappier without all the bloatware

    Thanks for replies
    Try another gsi. Probably same behavior on others though, most gsis share a lot of source code. If a bug exists in one, it's probably also in others released around the same date. But some bugs/issues are device-specific. Not much you can do except file a bug report and wait.

    The best place to file a bug report is here, it's where most gsis derive their code from:

    1
    When will you release lineage os 21
  • 33
    640px-Lineage_OS_Logo.png

    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.

    MUST-READ BACKGROUND - Android 13 and the two approaches:
    As some of you already know, due to various reasons, @phhusson , who kickstarted the GSI trend and committed to it over the years, is backing out from future development
    - there won't be any AOSP 13+ builds or patches directly from him. He did most of the heavylifting for fixing bugs and implementing features, and selflessly supported more than his AOSP GSIs and more than devices he own. For the situation of GSIs today, we owe him a big thank-you.
    Earlier, inspired by @PeterCxy , I took the "light" approach, which starts over from AOSP's generic gsi_* target and adds the minimum amount of fixes needed for my own devices, intentionally leaving many legacy devices behind. For more details about it, visit its own thread.
    Meanwhile, a number of existing builders incl. myself have formed the TrebleDroid organization, with PHH himself helping us in technical issues. TD will forward-port PHH's final patches (v415) onto Android 13 and attempt to fix new issues. This is still a new and ongoing process, but if done right, will have compatibility and feature-completion on par with past PHH-based GSIs. This thread contains LOS builds based on TrebleDroid's collective work, which supposedly suits legacy devices, Samsung, etc. better than "light".

    Disclaimer:
    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.

    MUST-READ - reporting bugs:
    If you want to report a bug, then you MUST try reproducing on an AOSP reference build of around the same date from TrebleDroid, and ONLY proceed to report here when it's specific to this GSI. This filters out bugs common to all TD-based GSIs, which you should still let me know, but it might not be mine to fix. I might silently ignore your report if you skip this.

    Download:
    https://sourceforge.net/projects/andyyan-gsi/files/
    Scroll down for the naming rules of variants.
    Compressed as .xz archives - extract first.

    Stuff on GitHub (builders-only):
    Most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
    Thanks to:
    • The LineageOS team
    • @phhusson - shaped the treble community, and still takes care of TrebleDroid at a higher level
    • @PeterCxy - coded critical fixes such as sysbta
    • The TrebleDroid builders
    • ...and more
    Donate?
    https://paypal.me/AndyCGYan
    9
    Notes:
    • 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, or even a year ago.
    • I now daily-drive "light", so I can't test TD-based builds as extensively as before. For the same reason, I likely won't build/upload any TD-based "personal" build either.
    • While most >=A13 GSIs out there are going to be TD-based, some perform better than others - some devs have their own patches that haven't been merged into TD yet. I myself will stay close to TD's raw patchset as much as possible, without picking patches from others left and right. If you find another GSI working better, don't just complain - try to narrow down which ones, and the intersection of them might be an unmerged patch that, if approved, would be merged into TD and benefit all.
    • GAPPS builds are offered as-is without guarantees. As a Chinese I can't/won't help with GAPPS/SN issues - please help each other out.
    • ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
    • Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
    • On *S variants, install PHH-SU and you'll get basic root for apps, good for devices that don't play well with Magisk or when you don't need modules.
    • Refer to this post for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.
    7
    Updated all variants with April security patches and in sync with TD 20230417. [Insert obligatory backup-and-test warning here]

    All modern Xiaomi/Redmi devices should be able to see high refresh rates now (if supported), without having to spoof properties globally.
    6
    Updated all variants with July security patches. [Insert obligatory backup-and-test warning here]

    I just realized that I haven't included PHH-SU app in *S (while I did over at Light) - this has been corrected.

    @Jonny - although I still very much doubt that the uname change is related to the alarm, adding it back is trivial, so now it's back.
    6
    Updated all variants with Android 13 QPR2 and March security patches. [Insert obligatory backup-and-test warning here]

    As usual with "feature drops", things can change or break majorly.

    Fixed in-call audio on Snapdragon 8 Gen 2 (SM8550), tested on OnePlus 11, should pave the way for future QCOM SoCs as well. Users of other SM8550 devices like Xiaomi 13 and RedMagic 8 Pro/+ might want to try this out too. Also pushed to TD upstream, so in case you don't like LOS, it's still coming to your favorite TD/-based GSI later.

    Imported some SN fixes from HentaiOS - GAPPS users should now get CTS profile match as well.

    Fixed videos sometimes getting stuck after pausing and resuming, thanks @Cozzmy13 for working it.

    Fixed two-pane layout in Settings for tablets - set an appropriate density then force stop Settings for it to take effect.

    And finally for builders, starting this month LOS has moved to Git LFS for hosting their Chromium webviews. Please re-init the repo with "--git-lfs" flag BEFORE syncing again or you will hit errors. If you already have a bad sync, clear the residue and re-init:
    Code:
    rm -rf external/chromium-webview/prebuilt/*
    rm -rf .repo/projects/external/chromium-webview/prebuilt/*
    rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*