Related
Hi,
I used Lineage for a long time on my Nexus 4 (mako) without a problem. But for some reason I could not flash it on this phone if my life would depend on it. I updated the stock rom to OPXS27.109-49-5 (XT1789-06) and tried all the following combinations TWRP 3.2.1-1 and 3.2.2-2 with Lineage 15.1 2018/07/03 | 2018/07/10 | 2018/07/17.
I follow this steps:
- start developer mode and push twrp-3.2.2-2 to sdcard
- reboot bootloader
- fastboot boot twrp 3.2.2-2 image
- install twrp 3.2.2-2.zip
- reboot to recovery
- reboot to bootloader
- fastboot -w
- until this point everything works like a charm
- fast setup no connects etc.
- activate developer mode
- push os (lineage-15.1-20180717-nightly-nash-signed.zip)
- push twrp 3.2.2-2.zip
- reboot to recovery
- optional: wipe Dalvik/ART Cache | System | Data
- install OS.zip
- optional: reinstall twrp.zip
- reboot system
- Softbrick
The phone will now constantly reboot and it is even impossible to turn it off. I can get to bootloader if I connect the phone to a PC and hold the key combination for bootloader. In bootloader I can't choose anything using the phone itself and I can't call recovery from fastboot either. I can however allfalsh back to stock or use reboot and reboot bootloader command.
I would be most grateful for some help or suggestions what might be the problem here.
Thanks in advance.
Regards.
After 07-17, the process is much simpler.
Start with a Flashall at this point.
Reboot, confirm you're on at least 27.1.2
Go to bootloader, boot TWRP 3.2.2 image.
Then follow the steps given by npjohnson(https://forum.xda-developers.com/z2-force/development/official-lineage-os-15-1-t3816540)
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
(Optionally) Flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though please note that it will need to be re-installed on update.
ADB sideload the newest weekly
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - Only MindTheGApps arm64 are compatible, OpenGApps are not compatible with A/B yet: MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Unseeablething said:
After 07-17, the process is much simpler.
Start with a Flashall at this point.
Reboot, confirm you're on at least 27.1.2
Go to bootloader, boot TWRP 3.2.2 image.
Then follow the steps given by npjohnson(https://forum.xda-developers.com/z2-force/development/official-lineage-os-15-1-t3816540)
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
(Optionally) Flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though please note that it will need to be re-installed on update.
ADB sideload the newest weekly
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - Only MindTheGApps arm64 are compatible, OpenGApps are not compatible with A/B yet: MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Click to expand...
Click to collapse
+1000 - Thanks for letting him know. This is the right process to follow.
npjohnson said:
+1000 - Thanks for letting him know. This is the right process to follow.
Click to expand...
Click to collapse
Thank you both for your replies and the guide.
I tried this method, but sadly it failed in Step 2/2 install ( ADB sideload the newest weekly) with the error "Unable to find partition for path '/cache'.
I see you list OCSX-version in your guide which points to the US-Version of the phone (Single-SIM) whereas the rest of the world including me got dual-Sim.
Is it really only for the US-phone (I would guess that is not the case.) or is my error completely unrelated to that?
Thanks in advance.
HorstA said:
Thank you both for your replies and the guide.
I tried this method, but sadly it failed in Step 2/2 install ( ADB sideload the newest weekly) with the error "Unable to find partition for path '/cache'.
I see you list OCSX-version in your guide which points to the US-Version of the phone (Single-SIM) whereas the rest of the world including me got dual-Sim.
Is it really only for the US-phone (I would guess that is not the case.) or is my error completely unrelated to that?
Thanks in advance.
Click to expand...
Click to collapse
Our phone does not have a cache partition.
If it helps, take a tour to the guides: https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto G7
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction:
This is the Official Lineage OS 16.0 thread for the Motorola Moto G7, codename river.
Join our Moto G7 Development Telegram Group!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine with SafetyNet patcher modules, though is not supported.)
Download:
LineageOS Updater
XDA:DevDB Information
river-lineageos, ROM for the Moto G7
Contributors
erfanoabdi, SyberHexen
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-11-16
Last Updated 2020-08-09
Copy Partitions Zip
- courtesy @ @filipepferraz
Download
Reserved
sim card is not working
currently I use
lineage-16.0-20191118-nightly-river version
XT1962-5 (Europe/Global) model
The phone didn't detect sim card.
It is dual sim model but in any slot, didn't work.
' . ' said:
currently I use
lineage-16.0-20191118-nightly-river version
XT1962-5 (Europe/Global) model
The phone didn't detect sim card.
It is dual sim model but in any slot, didn't work.
Click to expand...
Click to collapse
Did you try removing the sim and put back in while the system is on?
SyberHexen said:
Did you try removing the sim and put back in while the system is on?
Click to expand...
Click to collapse
I did, and tried when power off as well.
The other OS versions (NOV.15, NOV.16) also showed 'No sim' state.
But after I roll back to stock rom, they are working again.
SyberHexen said:
Did you try removing the sim and put back in while the system is on?
Click to expand...
Click to collapse
And I don't know why, but on your unofficial latest Lineage os (lineage-16.0-20191001-UNOFFICIAL-river) , the sim card working well...
but on the official version, didn't work.
' . ' said:
And I don't know why, but on your unofficial latest Lineage os (lineage-16.0-20191001-UNOFFICIAL-river) , the sim card working well...
but on the official version, didn't work.
Click to expand...
Click to collapse
My last build there was with prebuilt vendor.img
This official LOS 16.0 includes a source built vendor.img
install gapps
SyberHexen said:
My last build there was with prebuilt vendor.img
This official LOS 16.0 includes a source built vendor.img
Click to expand...
Click to collapse
does anyone know where I can download the gapps, the android version is 9.1, they don't accept at https://opengapps.org/
alguien sabe donde puedo descargar las gapps, la version de android es 9.1, no aceptan en https://opengapps.org/
I am having issues with installing Lineage OS 16.0 on my G7 (XT1962-1). I'm using the file named lineage-16.0-20191118-nightly-river-signed.zip. I followed the instructions on the https://wiki.lineageos.org/devices/river/install page.
My phone's bootloader is unlocked, Developer Options are configured to allow OEM unlocking, and USB debugging. Motorola firmware version PPOS29.114-134-4 from the US Retail channel was installed. I subscribe to Google Fi.
1. I temporarily booted TWRP 3.3.1-2 using the "fastboot boot twrp-3.3.1-2-river.img" command. The file was downloaded from the TWRP URL for River. I pushed the twrp-installer-3.3.1-2-river.zip to the phone using adb and did an install zip procedure. TWRP was installed to both the a and b slots. I rebooted recovery and TWRP 3.3.1-2 launched normally.
2. In TWRP, I formatted data to remove encryption. I then wiped Dalvik/ART cache and system in the Advanced Wipe menu. I rebooted TWRP as per recommendation when formatting the data partition.
<<edit>> I did install the copy-partitions-ab.zip at this point.
3. I used the adb sideload procedure per the Lineage installation instructions for the ROM file referenced above. The installation appeared to complete normally.
4. I restarted adb sideload to install open_gapps-arm64-9.0-micro-20191119.zip which was downloaded from the opengapps.org site.
This is where things go abnormally. The open-gapps installation script starts to run and then ab-ends with error 64. The architecture doesn't match the installation file. The script reports my phone is arm, not arm64. I think we all know that the G7 hardware is arm64. So, I downloaded the open_gapps-arm-9.0-micro-20191119.zip and tried installing. That attempt generated error 70 (insufficient space in the system partition). I ran a df -k command in a terminal window in TWRP and /system is mounted with almost 3GB of space available.
I was very confused at this point, but I decided to try installing Magisk 20.1 using TWRP zip file install procedure. Interestingly, the magisk install script reported the architecture as arm (not arm64) and completed normally.
I tried to reboot the system, but TWRP warned that no OS was installed. I cancelled the reboot and did a power off.
I'm not new to LineageOS installation, I've been running LineageOS on my Nexus 6 for a couple of years. Please review the steps I've done and let me know what I'm screwing up. Thanks.
Try "fastboot -w" as formatting data in TWRP breaks boot. "No OS" warning in TWRP can be ignored
cou94114 said:
I think we all know that the G7 hardware is arm64. So...
Click to expand...
Click to collapse
Don't have this device yet myself, but to your point, Motorola has been known to put out a 32 build on 64 hardware before, and so the corresponding Lineage build was also 32. The Moto Z Play for instance.
Given your issues, it would be good to have confirmation from the OP as to what is the case with the G7.
cou94114 said:
I am having issues with installing Lineage OS 16.0 on my G7 (XT1962-1). I'm using the file named lineage-16.0-20191118-nightly-river-signed.zip. I followed the instructions on the https://wiki.lineageos.org/devices/river/install page.
My phone's bootloader is unlocked, Developer Options are configured to allow OEM unlocking, and USB debugging. Motorola firmware version PPOS29.114-134-4 from the US Retail channel was installed. I subscribe to Google Fi.
1. I temporarily booted TWRP 3.3.1-2 using the "fastboot boot twrp-3.3.1-2-river.img" command. The file was downloaded from the TWRP URL for River. I pushed the twrp-installer-3.3.1-2-river.zip to the phone using adb and did an install zip procedure. TWRP was installed to both the a and b slots. I rebooted recovery and TWRP 3.3.1-2 launched normally.
2. In TWRP, I formatted data to remove encryption. I then wiped Dalvik/ART cache and system in the Advanced Wipe menu. I rebooted TWRP as per recommendation when formatting the data partition.
<<edit>> I did install the copy-partitions-ab.zip at this point.
3. I used the adb sideload procedure per the Lineage installation instructions for the ROM file referenced above. The installation appeared to complete normally.
4. I restarted adb sideload to install open_gapps-arm64-9.0-micro-20191119.zip which was downloaded from the opengapps.org site.
This is where things go abnormally. The open-gapps installation script starts to run and then ab-ends with error 64. The architecture doesn't match the installation file. The script reports my phone is arm, not arm64. I think we all know that the G7 hardware is arm64. So, I downloaded the open_gapps-arm-9.0-micro-20191119.zip and tried installing. That attempt generated error 70 (insufficient space in the system partition). I ran a df -k command in a terminal window in TWRP and /system is mounted with almost 3GB of space available.
I was very confused at this point, but I decided to try installing Magisk 20.1 using TWRP zip file install procedure. Interestingly, the magisk install script reported the architecture as arm (not arm64) and completed normally.
I tried to reboot the system, but TWRP warned that no OS was installed. I cancelled the reboot and did a power off.
I'm not new to LineageOS installation, I've been running LineageOS on my Nexus 6 for a couple of years. Please review the steps I've done and let me know what I'm screwing up. Thanks.
Click to expand...
Click to collapse
try to roll back stock and install again without install 'copy-partition.zip'. I had same problem but after do that I can install it.
With latest rom, sim cards working perfectly and stable!
In particular, the microphone function is greatly improved compared to the manufacturer ROM!
Thanks!
Amazon have an "exclusive" G7 which is dual SIM and cheap for black Friday. I've seen suggestions it ships with bloatware but can be flashed with vendor's standard image. Is this the same as "river" and likely to work with official or unofficial LO 16? It may be the same as the dual sim version mentioned in previous post on this thread?
Slight problem. Im getting an error 70 while installing gapps. And attempting to resize the system partition through twrp does nothing.
This phone has been a pain in the ass with anything like this since I got it. But, I was finally able to get the rom installed and fully booted, But gapps just will not install. Even with Pico, it still says not enough space.
What am i missing? Ive never had a such a problem rooting a phone before I got into motorolas lol
crypysmoker said:
Slight problem. Im getting an error 70 while installing gapps. And attempting to resize the system partition through twrp does nothing.
This phone has been a pain in the ass with anything like this since I got it. But, I was finally able to get the rom installed and fully booted, But gapps just will not install. Even with Pico, it still says not enough space.
What am i missing? Ive never had a such a problem rooting a phone before I got into motorolas lol
Click to expand...
Click to collapse
I had the same issue. It's not the size of the partition, its the order the software is installed and the reboots done during the process. I joined the telegram group for the G7 and found some very helpful information related to the installation of LineageOS 16.0 on the G7. Here are the steps for a clean flash.
Very important - Flash the copy-partitionsAB.zip to replicate the slot A and slot B layout.
- Clean flash:
1) Put the phone in bootloader mode
1.2) Connect phone to PC with a USB cable.
1.3) In a Command prompt window, run "fastboot getvar all".
1.4) Make slot A the active slot "fastboot set_active a".
1.5) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)
1.6) check active slot in Reboot menu - set to A
2) Flash lineage zip
3) Flash twrp installer zip
3.5) Format data while in TWRP.
4) Reboot to bootloader from TWRP.
5) fastboot -w (this will wipe your userdata partition)
6) Reboot to TWRP recovery (it should be installed when you flashed the twrp-installer zip)
6.5) check active slot in Reboot menu - set to A
7) Flash opengapps zip (use the arm64 version)
7.5) Flash magisk zip (optional, only if you want root)
8) Reboot system on slot A
The G7 is my first A/B slot device and I struggled with the configuration. TWRP recovery is part of the boot partition. Installing the lineage zip, then the TWRP installer zip seems to be the required order. Then, rebooting TWRP from the installed image works to install OpenGApps. The active slot is very important, too. Many times during my installation ordeal, I would think that slot a was active, but it was slot b. I installed the copy-partitions zip when we were made aware of no bootloader on slot b a few weeks ago.
Good luck.
To install gapps successfully, reboot twrp after installing lineageos:
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload lineage-16.0-20191122-nightly-river-signed.zip
* adb reboot bootloader
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload open_gapps-arm64-9.0-nano-20191121.zip
In other news: Does NFC work for anyone?
reddich said:
To install gapps successfully, reboot twrp after installing lineageos:
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload lineage-16.0-20191122-nightly-river-signed.zip
* adb reboot bootloader
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload open_gapps-arm64-9.0-nano-20191121.zip
In other news: Does NFC work for anyone?
Click to expand...
Click to collapse
I don't see a step to flash twrp installer. Do you permanently install twrp in your procedure?
Awesome. Thank you guys. Looks like the main problems I was having are not fastboot -w and not rebooting fully into twrp to flash gapps. After flashing the twrp installer and rebooting, I would get a totally different recovery. I've rooted hundreds of phones, but these a/b phones seems to just be a huge pain in the patooty.
---------- Post added at 09:17 AM ---------- Previous post was at 09:08 AM ----------
reddich said:
To install gapps successfully, reboot twrp after installing lineageos:
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload lineage-16.0-20191122-nightly-river-signed.zip
* adb reboot bootloader
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload open_gapps-arm64-9.0-nano-20191121.zip
In other news: Does NFC work for anyone?
Click to expand...
Click to collapse
These phones do not have NFC capabilities.
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
hatemelectr said:
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
Click to expand...
Click to collapse
Some images simply do not work, so you will need to check for other images simply.
Just install this one : https://github.com/phhusson/treble_...nload/v222/system-quack-arm64-ab-gapps.img.xz
root&gapps&backlight working
of course you'll need Device+ID.apk and register ID with Google but that's easy and simple
Device: Huawei 8x Max AR00
The Quack version works but sadly it is Android 10. I have found many Android 12L GSI roms that I would like to use but the brightness is an issue on all of them. Anyone know how to copy the Quack backlight vendor display and patch it to the newer GSI roms? Tried buildprop GSI wont boot (Crdroid, Lineage 19) Tried Dirty flashing, obviously didn't work. Can't seem to find the file containing the slider brightness limitations. Phherson gives rom backlight options and tried several combinations, and yes rebooted everytime none of them work. Any ideas?
riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
After trying many different gai variants and versions I found they all have an issue with browsers. Both chrome and edge freeze after scrolling a bit. I'm wondering if this because the GSI uses too much storage space and cannot buffer? Tried to port GSI onto other partitions such as cust, prod didn't work. Even Magisk flashes successfully but does not appear in the rom. The a and b is confusing like EMUI uses both and the TWRP does not decrypt and no Verity commands don't work either. The havoc rom seems to work the best with gapps pico flashed.
~ Android 12 backlight issues had to revert to android 10
~ All GSI have the common browsers freezing. Have to use VIA browser (basic)
~ Magisk won't install have to port to ramdisk, but isn't that the TWRP recovery?
Hello, which one is the Qualcomm driver to be installed for sdm660?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
- Selinux is enforcing
- FBE build, don't use twrp for these builds
- Custom kernels are NOT supported
- Read the instructions carefully
Downloads
- Here
Flashing instructions
- Here (Suggestions for improving the guide are welcome)
Sources:
- LineageOS
- Kernel Tree
Happy modding!
Reserved
Good news
Great!
Okay but does it run Crysis?
Stonks
I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot
a1291762 said:
I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot
Click to expand...
Click to collapse
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
for now you can use some old build i made https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220319-UNOFFICIAL-daisy.zip
i should upload a new one as soon as possible (maybe tomorrow/today)
Its_Vixano said:
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
Click to expand...
Click to collapse
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
My recovery process:
* Boot into TWRP
* Flash Lineage 18.1
* Boot into (Lineage 18.1) recovery
* Install Lineage 19.1
* Boot into (Lineage 19.1) recovery
* Flash Gapps and Magisk
* Boot into system
a1291762 said:
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
Click to expand...
Click to collapse
Avoid using the 'fastboot boot' command, somehow it doesn't works
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery
Its_Vixano said:
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery
Click to expand...
Click to collapse
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.
a1291762 said:
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.
Click to expand...
Click to collapse
It should work, but sometimes it takes a couple of tries with reboots in between. I did not find a pattern yet, but in general flashing boot and doing the power vol+ combo should be fine. Maybe it's a timing thing, not sure. Try to switch which button you press first maybe, or try to press them at the exact same time. A bit weird, yeah
UPDATE: pressing the + button just a bit earlier seems to be doing the trick for me!
just done a test build for fixing the privapp permission issues (random bootloops caused by some normal reboots), seems fine here but i don't really trust my self
https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220329-UNOFFICIAL-daisy.zip
report if something will be wrong with it
edit: Apparently it's fine so
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting
Its_Vixano said:
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting
Click to expand...
Click to collapse
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Yep, that's the right way to update the rom
I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer
nabav said:
I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer
Click to expand...
Click to collapse
- Just follow the instructions, everything is written here
- Should be stable enough for daily driving it, sadly i don't use daisy anymore as a 'primary' device
- I also use fdroid and adaway and they don't require root
a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Hi a1291762,
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used? If it is an upgrade procedure rather than an update procedure (are those to be expected at all?) can you give a more detailed explanation? I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?). Does your procedure work with fastboot or adb? Whatsoever, though it is not my daily driver I am very happy with my Mi A2 Lite with TWRP and Magisk but I also like playing... (with 75 years).
Thanks for all of your efforts!
grufty47
grufty47 said:
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used?
Click to expand...
Click to collapse
The OP guide seems to be written for people coming from something other than Lineage. The first part of it sets up the Lineage recovery and formats user data.
Since I was coming from Lineage and already had the recovery, I figured I could skip those steps. The OP guide says you can skip formatting data if you're coming from Lineage and I figured the recovery can't have changed too much.
I don't know how much testing was done for a Lineage 18 -> 19 upgrade. It worked for me but I barely had anything installed when I did it. Make backups in case of data loss and all that.
Something I don't understand in the OP guide is the suggestion to use the copy_partitions script. It only seems useful if your phone is somehow in an odd situation where miscellaneous A and B partitions don't match? It can't hurt to run it I guess.
grufty47 said:
can you give a more detailed explanation?
Click to expand...
Click to collapse
My 18->19 upgrade process matches the 19 "OTA" process. Refer to the OP guide for screenshots and details.
1. Boot to recovery
2. Sideload the lineage zip
3. Reboot to recovery (changes the active slot)
4. Sideload gapps
5. Sideload Magisk
The lineage zip is like a "full OTA" for the stock ROM. Flashing it overwrites system, boot and vendor, hence the need to flash gapps and magisk again. But the recovery only supports flashing to the current slot, hence the reboot in the middle.
grufty47 said:
I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?).
Click to expand...
Click to collapse
FBE has to do with encryption. I found this that might help explain it.
https://www.reddit.com/r/LineageOS/comments/hd534a
Booting TWRP 3.5.2_9.2 (fastboot boot twrp.img) shows only garbage names under /sdcard plus a bunch of other places (but not all of /data). So I guess TWRP doesn't support FBE encryption? I'm not sure why that matters for flashing system partitions, but if any of lineage, gapps or magisk expects to write to places covered by FBE then clearly that's not going to work properly under TWRP.
Since you have installed TWRP over the Lineage recovery, you'll have to get a Lineage recovery back on your phone before you can upgrade. Using the provided recovery should work I guess? If not, you could use TWRP to flash the most recent Lineage 18 zip, which will also replace TWRP with Lineage recovery. Part of the reason I attempted the 18->19 upgrade in the first place is because I couldn't get the provided recovery to boot on my phone.
I hope that helps.
Lincoln
Hi all, after have lost hours and hours traying to install the latest LineageOS for MicroG, I made a facotry reset of the Oneplus 9 Pro (to Android 11), than updated de devices to the latest update (incl. Android 12 and all avaiable updates) and THAN trayed to install LineageOS for MicroG following strictly the Manual of LineageOS (link). It seams to be perfect, until the first start of LIneageOS. I see the first setup screen (Welcome to LineageOS), on the left corner "Emergency call) and on the right the START button, but the screen doesent react andt on the upper right corner I see an empty battery icon. What can I do?? I'm at the end of my knowledge.
In a step of Installing LineageOS (without MicroG) it is necessary to install the dtbo and vendor boot partitions. Maybe the problem is here?
What I have installed:
- dtbo.img (20220823)
- vendor_boot.img (20220823)
- lineage-19.1-20220820-microG-lemonadep-recovery.img
- lineage-19.1-20220824-microG-lemonadep.zip
In Recovery I see "Version 19.1 (20220824)" is installed.
PS: The volume up and down button works...
(unwanted post)
enoironline said:
Hi all, after have lost hours and hours traying to install the latest LineageOS for MicroG, I made a facotry reset of the Oneplus 9 Pro (to Android 11), than updated de devices to the latest update (incl. Android 12 and all avaiable updates) and THAN trayed to install LineageOS for MicroG following strictly the Manual of LineageOS (link). It seams to be perfect, until the first start of LIneageOS. I see the first setup screen (Welcome to LineageOS), on the left corner "Emergency call) and on the right the START button, but the screen doesent react andt on the upper right corner I see an empty battery icon. What can I do?? I'm at the end of my knowledge.
In a step of Installing LineageOS (without MicroG) it is necessary to install the dtbo and vendor boot partitions. Maybe the problem is here?
What I have installed:
- dtbo.img (20220823)
- vendor_boot.img (20220823)
- lineage-19.1-20220820-microG-lemonadep-recovery.img
- lineage-19.1-20220824-microG-lemonadep.zip
In Recovery I see "Version 19.1 (20220824)" is installed.
Click to expand...
Click to collapse
boot is equivalent to recovery
you must be on lastest official firmware
there are also spare firmware you can flash to get aligned
Psk.It said:
boot is equivalent to recovery
you must be on lastest official firmware
there are also spare firmware you can flash to get aligned
Click to expand...
Click to collapse
How can I be on latest official firmware? Before installing LIneageOS for MicroG I installed all possible Updates of the stock Version of Oneplus, than during the installation process I installed the two vendor-files as described in the manual. Do you have links to the spare firmware or better Installation guides?
enoironline said:
How can I be on latest official firmware? Before installing LIneageOS for MicroG I installed all possible Updates of the stock Version of Oneplus, than during the installation process I installed the two vendor-files as described in the manual. Do you have links to the spare firmware or better Installation guides?
Click to expand...
Click to collapse
If you installed C62 (or latest version for your device) you should be OK
(you can try reading other rom theads, some have the link to spare firmware)
for set-up, i prefer taking dtbo, vendor_boot and boot images from payload.bin file already in the rom.zip (using payload_dumper tool)
once "preliminary set-up" is done, reboot to recovery, then format data and sideload the rom
if you need extra flashing (magisk, kernel, what else) reboot recovery and sideload it
Psk.It said:
If you installed C62 (or latest version for your device) you should be OK
(you can try reading other rom theads, some have the link to spare firmware)
for set-up, i prefer taking dtbo, vendor_boot and boot images from payload.bin file already in the rom.zip (using payload_dumper tool)
once "preliminary set-up" is done, reboot to recovery, then format data and sideload the rom
if you need extra flashing (magisk, kernel, what else) reboot recovery and sideload it
Click to expand...
Click to collapse
that is certainly purposeful, but much too difficult for my most modest knowledge.
Ironically, I installed the normal LineageOS without MicroG in the meantime (to be able to use the device) and it works reasonably stable. As soon as I know what I have to install additionally when, I'll probably do again first a factory reset to the original operating system of oneplus, all updates and then I try it again with lineageos for microG. Remains to be seen what else I need to install and when :-/ It's frustrating to cannot follow an official Installation guide without having souch issues.
I can't understand why it has to be so difficult and full of detours that one can't do it if one doesn't have in-depth knowledge. Really a pity.
enoironline said:
that is certainly purposeful, but much too difficult for my most modest knowledge.
Ironically, I installed the normal LineageOS without MicroG in the meantime (to be able to use the device) and it works reasonably stable. As soon as I know what I have to install additionally when, I'll probably do again first a factory reset to the original operating system of oneplus, all updates and then I try it again with lineageos for microG. Remains to be seen what else I need to install and when :-/ It's frustrating to cannot follow an official Installation guide without having souch issues.
I can't understand why it has to be so difficult and full of detours that one can't do it if one doesn't have in-depth knowledge. Really a pity.
Click to expand...
Click to collapse
unfortunately official lineage build does not support signature spoofing, this means you need gapps (Nick gapps is the most used , you can check-out also mind-gapps)
crDroid and riceOS are a couple of roms that allow signature spoofing, you will be abile.to run micrpG on those
about payload_dumper just google it, it's a tool for unpagkage images from the a rom file
about increase of complications, we all must thank you Google 1st and OnePlus (or Oppo) in second place
Psk.It said:
for set-up, i prefer taking dtbo, vendor_boot and boot images from payload.bin file already in the rom.zip (using payload_dumper tool)
once "preliminary set-up" is done, reboot to recovery, then format data and sideload the rom
if you need extra flashing (magisk, kernel, what else) reboot recovery and sideload it
Click to expand...
Click to collapse
I'm looking right now, interesting. You wrote, you prefer taking dtbo, vendor_boot AND Boot Images from payload.bin. When to load dtbo and vendor_boot is describet in the installation guide of lineageOS, but when do you use/install the from you mentioned boot image?
enoironline said:
I'm looking right now, interesting. You wrote, you prefer taking dtbo, vendor_boot AND Boot Images from payload.bin. When to load dtbo and vendor_boot is describet in the installation guide of lineageOS, but when do you use/install the from you mentioned boot image?
Click to expand...
Click to collapse
Instead of recovery
basically:
dump payload
flash btbo
flash vendor_boot
(someone suggest to reboot in fastboot)
flash boot
from fastboot menu go to recovery
finally sideload the zip
enoironline said:
Hi all, after have lost hours and hours traying to install the latest LineageOS for MicroG, I made a facotry reset of the Oneplus 9 Pro (to Android 11), than updated de devices to the latest update (incl. Android 12 and all avaiable updates) and THAN trayed to install LineageOS for MicroG following strictly the Manual of LineageOS (link). It seams to be perfect, until the first start of LIneageOS. I see the first setup screen (Welcome to LineageOS), on the left corner "Emergency call) and on the right the START button, but the screen doesent react andt on the upper right corner I see an empty battery icon. What can I do?? I'm at the end of my knowledge.
In a step of Installing LineageOS (without MicroG) it is necessary to install the dtbo and vendor boot partitions. Maybe the problem is here?
What I have installed:
- dtbo.img (20220823)
- vendor_boot.img (20220823)
- lineage-19.1-20220820-microG-lemonadep-recovery.img
- lineage-19.1-20220824-microG-lemonadep.zip
In Recovery I see "Version 19.1 (20220824)" is installed.
Click to expand...
Click to collapse
Hey just wanted you to know that I had the exact same problem, I posted about it here:
https://www.reddit.com/r/LineageOS/comments/wyr4v9
and after a few failed attempts I basically had to hose and reset to stock with MSM (which was hard since I don't have a Win computer, but that's a solution for another day).
I think the other poster is right, you do need to flash firmware first before installing. Have you tried this? I'll try it tonight and report back, as I need to get this running before Monday.
hyve9 said:
Hey just wanted you to know that I had the exact same problem, I posted about it here:
https://www.reddit.com/r/LineageOS/comments/wyr4v9
and after a few failed attempts I basically had to hose and reset to stock with MSM (which was hard since I don't have a Win computer, but that's a solution for another day).
I think the other poster is right, you do need to flash firmware first before installing. Have you tried this? I'll try it tonight and report back, as I need to get this running before Monday.
Click to expand...
Click to collapse
Actually I have the plan to go back to Stock with MSM, than reinstall all updates of the original Oneplus 9 Pro, than reinstall the actual version of LineageOS MicroG (20220824) after dumping payload and flashing dtbo, vendor_boot and boot like psk.lt wrote.
wondering what you will accive.
Psk.It said:
Instead of recovery
basically:
dump payload
flash btbo
flash vendor_boot
(someone suggest to reboot in fastboot)
flash boot
from fastboot menu go to recovery
finally sideload the zip
Click to expand...
Click to collapse
I'm trying to dump payload. I installed the latest Python version, than downloaded payload_dumper from this link , done what described on the website and now in cmd I have the Message:
File "C:\Users\X\Desktop\Payload_dumper\payload_dumper.py", line 67
<title>payload_dumper/payload_dumper.py at master · vm03/payload_dumper · GitHub</title>
SyntaxError: invalid character '·' (U+00B7)
Do I understand it right, that the script of the tool has an error? Do you have a link of a Payload_dumper Tool that works and from where I can download it? I also found this link and in the text you can download the Tool from here , but I do not trust 100% this sources :-/
enoironline said:
I'm trying to dump payload. I installed the latest Python version, than downloaded payload_dumper from this link , done what described on the website and now in cmd I have the Message:
File "C:\Users\X\Desktop\Payload_dumper\payload_dumper.py", line 67
<title>payload_dumper/payload_dumper.py at master · vm03/payload_dumper · GitHub</title>
SyntaxError: invalid character '·' (U+00B7)
Do I understand it right, that the script of the tool has an error? Do you have a link of a Payload_dumper Tool that works and from where I can download it? I also found this link and in the text you can download the Tool from here , but I do not trust 100% this sources :-/
Click to expand...
Click to collapse
I made It! Using the tool from this website (link to the tool) I was able to extract all files. Now I can start.
Last LineageOS for MicroG Version (20220824) finaly INSTALLED (what a fight!).
Many thanks to Psk.lt and hyve9 for your help!
A quick guide for newbes like me:
Install on a PC:
- adb
- the last qualcolm driver ect
- python
download on the PC:
- MSN Tool to go back to stock OS
- payload Dumper Tool (THANK YOU PSK!!!)
- the newest LineageOS for MicroG Version
On the Oneplus 9 Pro:
- With MSN Tool back to Stock OS
- Install all possible Updates (in my device it was C61!)
- Install Oxygen Updater from an app Store or apk
- Install the REALLY last Update for your device (in my Case C62)
- download the last LineageOS for MicroG Version (.zip)
- open the .zip file and copy out the payload.bin file
Than like Psk.lt wrote, with the Payload Dumper dump the payload-file and extract btbo, vendor_boot and boot files
Safe the following files under adb
- btbo
- vendor_boot
- boot
- the lineageOS for MicroG file
Start with the installation like described in the LineageOS guide, but
- use the own btbo and vendor_boot files
- for recovery, insted of using the recovery-file from LineageOS for microG, use the boot file (extractet with Payload dumper)
- finally sideload the LineageOS for MicroG file (.zip)
End
A question: in the future can I use the oxygen Updater under LineageOS for MicroG to install all the newest updates, or does it work only if using the stock OS?
enoironline said:
A question: in the future can I use the oxygen Updater under LineageOS for MicroG to install all the newest updates, or does it work only if using the stock OS?
Click to expand...
Click to collapse
you should use embedded updater (settings - system - update) but you will not be able to copy the zip if you don't have root
If you want backup the updated zip, you should sideload via pc
enoironline said:
Last LineageOS for MicroG Version (20220824) finaly INSTALLED (what a fight!).
Click to expand...
Click to collapse
Let me know how you are liking it, im debating it or CRDroid.
ajolly said:
Let me know how you are liking it, im debating it or CRDroid.
Click to expand...
Click to collapse
I'm using LineageOS with MicroG since the End of last year and had never real problems, only the installation progress is complicated (if you follow only the official installation guides of LineageOS and from LOS-MicroG). Last week I had LineageOS without MicroG installed and I must say, I did not really missed the MicroG functions, maybe because the apps I'm using do not need necessarely the functions of MicroG / would mainly need the messaging function, but can still run and function without. It dipend what you want to accive with the OS, if you want to be compleetly G-free under LineageOS, than you have to change at your own a few more things like DNS setting, systemwebview... I can't compare LinOS-MicroG with CRDroid, beacause I never used it.
What I do not like in V 19.1 vs 18.X is the bigger format of the quick setting tiles. I know that it's possible to change it, but I have to find out how to do it in the simplest way.
A function that I miss in LineageOS (for MicroG) is a Sandbox function like in Graphene, but using Shelter helps, even if not as good as a Sandbox.
What I really don't like is the fact, that LineageOS for MicroG doesn't ships Updates with the firmware, and their Installation Guide is not really helpful (do what is described by LineageOS... and it's not really what you have to do).
What I really like is how long the battery life lasts, at least with V18 and it has surely to do with my user's habits. Now to find out how it will be under V19.1.
Over all: I like it and do not want to replace it (for now).