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

[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

Wollyduke

New member
Apr 2, 2019
4
0
Hi, my device doesn't support twrp or any custom recovery (ulefone note 7p), how do I install gapps, and keep it from saying my device is uncertified.

I've tried using flashify, adb sideload and manually adding play store to /system/app but it seems I don't have access to system.

please help I've been at this for 6hrs now or is there a version of this rom (or similar) that comes with gapps?
 

master_lam

Member
Aug 2, 2012
27
7
Hi, my device doesn't support twrp or any custom recovery (ulefone note 7p), how do I install gapps, and keep it from saying my device is uncertified.

I've tried using flashify, adb sideload and manually adding play store to /system/app but it seems I don't have access to system.

please help I've been at this for 6hrs now or is there a version of this rom (or similar) that comes with gapps?
TWRP for your device: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-note-7p/
Google installer without root: https://androidfilehost.com/?fid=818070582850489460
 

Wollyduke

New member
Apr 2, 2019
4
0
Hi sorry for the late reply, the twrp above works to some extent but it causes my phone to bootloop to twrp recovery, anyway I flashed the gapps with this twrp, replaced it with my stock rom from fast boot now everything is working.........except auto brightness, miracast and the offline charging animation.
 

JuanTamqd21

Senior Member
Hi sorry for the late reply, the twrp above works to some extent but it causes my phone to bootloop to twrp recovery, anyway I flashed the gapps with this twrp, replaced it with my stock rom from fast boot now everything is working.........except auto brightness, miracast and the offline charging animation.
those can usually be fixed by custom vendor
 

Abdullah5490

Senior Member
Oct 16, 2016
81
15
Islamabad
www.blindHelp.net
Hello. I'm facing 3 problems with GSI ROMs on my device of which i'm not getting any clew. With the nature of all these 3 problems, I'm thinking that is it something wrong with the Vendor? Even the Vendor partition didn't modified during ROM flashing. Kindly throw some light after reading details below:
1. My phone is showing 3rd sim slot, which is fake (phone has only 2). 3rd one is named as "china unicom" and has no Service/signals available. Upon first startup, the phone's language automatic set to chinese instead of my local due to this fake sim. also, Whenever there's a phone number field in any app, The country always pre-selected as "china" and code is "+86", instead of my active sims/local taratory.
2. Mobile network on GSI is too slow even with LTE 100% signals and videos buffers allot.
Stock: 35-40MBPS, GSI: 2-5MBPS.
3. Battery usage stats are unavailable even after having overlay present for my device under system/product/overlay.

Device info:
Manufacturer: Infinix.
Name: Note7.
Model: X690B.
Platform: MTK6768, mediatek G70 chipset.
Stock: Android10.
GSI: android11 ().
Recovery: stock (no modification).
Bootloader: stock (no modification except unlock).
Device logs: Here
 

Claudio4780

Senior Member
Feb 6, 2016
175
45
Port Elizabeth
Howdy everybody. Question from an old man. My Xiaomi MI 9 SE Global (Miui 12.5) takes the "treble_arm64_bv" variant. Having checked my phone via the Treble Info app I've noticed "Your device supports the modern version of Project Treble, using VNDK version 30.0". Does it mean that I can also install "treble_arm64_bvS-vndklite.img" ?

If yes, which of the two variants is the better one and should I choose for installation... ?
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,290
3,570
Beijing
Just a quick reminder about EXT4 share duplicate blocks - it doesn't give you more space for mods such as GAPPS, rather the read-only nature makes it impossible to use /system-based mods. The way I see it, it's there for a number of older devices with smaller /system, just so they can flash it at all. As August builds are imminent, please double-check your votes.
 
  • Like
Reactions: Heeni

Shotg1

Senior Member
Apr 25, 2016
823
99
Manila
There are avs and bvs build what should i download for a only device




Corrected i saw the notes its ol its just link is gone
 
Last edited:

Top Liked Posts

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

    One notable change of this month is removing llkd (livelock daemon), which is known to mistakenly cause certain apps like Genshin Impact to freeze/restart after 10 minutes of usage. I've been running alright without llkd for a month by now, but if you notice a regression after this build, do let know.

    PHH is currently on a vacation; luckily, A11 is nearing its end, and A12 has been pushed back to Oct 4th (current leak), so there's no need to worry. I've also finished scouting A12 ahead for my personal changes and should be ready to publish them for other builders' reference, and build for generic target on release day.
    1
    Can you please help me in installing gapps in this GSI. My device is Realme x7 max ( mediatek 1200 ) and there is no twrp support. I can install this GSI without any issue but the issue is gapps as it require a recovery to install. Can you guide how I can install any kind of gapps into LOS. Do I need vndlite image ?
    you can install Magisk first and then flash Gapps for Magisk here.
    If your device says something about device not being certified by Google:
    1. Install Device ID.apk
    2. Copy the line that has the name "Google Service Framework" or "GSF"
    3. Go to https://www.google.com/android/uncertified and sign in your Google Account
    4. Paste the ID that you have copied and do the captcha.
    5. Copy the registered Android ID below the box and do step 4 again
    6. Go to Settings -> Apps and search for Google Play Store and Google Play Services
    7. Disable both
    8. Wait for a few minutes and enable them again
    9. Open Play Store and do the rest :)
    1
    I like to add (nano open) GApps to the rom and also prefer Magisk over phh-su, so I was looking for a way to make the system image writeable again. Some posts above a guide from PHH was given to unshare duplicate blocks directly on the phone once the image has been flashed, but I wanted to perform these steps before flashing the image.

    I came up with the following method to unshare duplicate blocks on a linux machine. Note that you need "simg2img" and "img2simg" to convert from and to sparse image file. Those tools should be available on most current linux distributions (i.e. on debian/ubuntu you can install them with a simple "sudo apt-get install simg2img img2simg").

    Here's are the commands to unshare duplicate blocks. Replace ##FILENAME## in the first line with the actual name of the downloaded .xz-image file:
    xz -d -k -c ##FILENAME## > ROM.img simg2img ROM.img ROM_RAW.img e2fsck -y -f ROM_RAW.img resize2fs ROM_RAW.img 3500M e2fsck -E unshare_blocks -y -f ROM_RAW.img e2fsck -f -y ROM_RAW.img resize2fs -M ROM_RAW.img img2simg ROM_RAW.img Lineage_RW.img

    If you want, like me, to remove phh-su in the process, use the following commands just after the "e2fsck -E unshare_blocks..." command:
    mkdir tmpdir mount -o loop,rw ROM_RAW.img tmpdir rm tmpdir/system/bin/phh-su rm tmpdir/system/etc/init/su.rc umount tmpdir

    The final image is then stored as Lineage_RW.img which can be flashed to the phone instead of the originally downloaded image.
  • 37
    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
    16
    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
    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.
    8
    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.