[ROM][UNOFFICIAL][jd2019][9 Pie] LineageOS 16.0 for the Lenovo Z5s L78071 - Lenovo Z5 Pro (No GT) Q&A, Guides, Development

[ROM][UNOFFICIAL][jd2019][9 Pie] LineageOS 16.0 for the Lenovo Z5s L78071 - Lenovo Z5 Pro (No GT) Q&A, Guides, Development

{
"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 9 Pie, 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.
Known issues: (as of May 19, 2020)
- FM Radio app doesn't work; It actually works, just once every two attempts: If it crashes the first time, select close app, clear apps from background and try again; I'll find a definite fix soon;
- Wi-Fi signal strength doesn't show on status bar, only in the wireless screen;
- Fingerprint reader doesn't work;
- SELinux is currently set to permissive;
Instructions:
- This is a FULL ROM build, meaning your BOOT, DTBO, SYSTEM and VENDOR partitions will be overwritten. Backup first!
- You need firmware version 11.x.y (preferably 11.3.169 - recovery encryption only tested with that version), any will do. 10.5 will not work
- Download TWRP from the files section, fastboot flash it (if you don't have custom recovery yet)
- Download patched vbmeta.img
- Download the latest build
- (Optional) Download Gapps (arm64 9.0, any flavor) and Magisk
- Boot to recovery (whichever you have), flash the new recovery
- Reboot to recovery, now your data is decrypted, flash vbmeta, latest build, magisk and gapps
- Format DATA completely to start from scratch since encryption is different
- Reboot
Downloads:
Builds: https://sourceforge.net/projects/lineageos-lenovo-z5s/files/
Source code:
LineageOS: https://github.com/LineageOS
Kernel and Device Tree: https://github.com/jacoghi
Reporting Bugs:
DO NOT Report bugs if you're not following the instructions!
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

Changelog:
May 19, 2020:
- Initital release, everything working except for FM and fingerprint reader;
- Kernel is completely overhauled and updated to LA.UM.7.8.r1-08500-SDM710.0;
- Audio drivers are stock 11.3.169 (we don't have the sources);
- Wifi is open-source, with MAC randomization currently being tested;
- Call recording already works;
- BT Audio works for calls and everything else, HD codecs being optimized;
- Wifi Display works perfectly on my cheap chinese Android TV Box. Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
- Camera2API is active, RAW pictures are also enabled;
- Build will automatically encrypt your device, I had to fool Lenovo's BS keymaster to make it work, so it has to be enabled;
- As of now, I don't care if your apps work or not, that's not my problem, just let me know about hardware issues;

jacoghi said:
Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
Click to expand...
Click to collapse
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!

carlshark said:
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!
Click to expand...
Click to collapse
Thanks for confirming that to me, great to know. Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd? And you can use magisk without any issues, I'm using it here right now, no problems.

jacoghi said:
Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd?
Click to expand...
Click to collapse
No, sorry. If that changes, I will let you know
I can imagine most of the users that are here are currently using a GSI. The stock 11.3.169 from here can actually be installed via TWRP. Flashing it would revert to stock recovery so users need to reinstall the TWRP recovery image during the same session. That's how I ensured that I was running an 11.x firmware after using all those GSIs from 4PDA. Hopefully this helps others to revert to stock so they can use your LOS build.

Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download

And what is apparently massive news for us, our phone will get an Android 10 official update, meaning we'll be able to boot lineage 17.1 with the updated audio drivers (in theory). Anybody in China or who knows how to trick their system and able to get ahold of these files?
https://club.lenovo.com.cn/thread-5849244-1-1.html

jacoghi said:
Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download
Click to expand...
Click to collapse
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.

carlshark said:
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.
Click to expand...
Click to collapse
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man

jacoghi said:
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man
Click to expand...
Click to collapse
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.

jacoghi said:
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
Click to expand...
Click to collapse
Oh, right, I totally forgot all about that. Should have tried enabling compression or saving to internal storage.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.
Click to expand...
Click to collapse
I've found a 4PDA post regarding updating to 11.5 and reposted the good stuff here. Hope it helps. Thanks for your good work!
---------- Post added at 06:38 AM ---------- Previous post was at 06:35 AM ----------
seisa said:
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo
Click to expand...
Click to collapse
I know this is the wrong thread to answer this, but we can't really help you out without some more details. Were you trying to install through recovery? Through QFIL?
From the looks of it, sounds like you have a bootloop. Try doing QFIL again and unlocking bootloader, or the other way around - sometimes it works for me that way.

I have Z5s 6GB/128GB model, sold as Global Version & Global ROM.
It does have EU LTE bands, so it probably is somewhat "global".
The downside: I am at 10.5 version with no updates available. Seller also told that there are no updates.
Two questions:
1. Is it absolutely necessary to have 11.3+ to install this LineageOS ROM? What is blocking installation if I have 10.5? Can I brick it?
-- EDIT: I will answer myself: Yes it is needed. LineageOS did not flash over 10.5 and gave an error. That was validation error before flashing, so no harm done.
2. Is it safe to install Chinese ROM on this device? Is it possible to loose something in the process? Like LTE bands or something else important?
-- EDIT: Seems to be ok.
I really want to install LineageOS or some other google free AOSP ROM. But I do not want to loose important features or brick it in the process.
Thanks.
EDIT: I installed Arrow OS GSI at the moment over 10.5 and it seems to work. But still looking forward to get pure LineageOS installed.

I have one problem that is hardware related:
Microphone level is quite low compared to my previous phone and people are complaining about low volume when I call.
Is there any way to add more gain? I tried to search but did not find easy and straightforward answer. Most solutions refer to methods/files that do not exist on this ROM.
What I found was complaint that there is still no way to easily manage audio stuff in android...
Mic Test (lauresprojects.com.mictest) app confirms that recording levels are considerably lower in both direct sound and communication mode when comparing to my other phone.
Otherwise seems to working quite nicely. Thanks for your good work.

I can't use face unlock with this ROM.

Is there still some active development at this project?
Is there some active development at this project?

Related

ROM: Sony AOSP 8.1 (H3113) (unofficial)

{
"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"
}
Sony AOSP project
Disclaimer
I'm not liable for anything YOU do to YOUR device, YOU are doing it and it's YOUR device.
What is it?
It's a project developed and maintained by Sony Xperia Developers team.
You can get more informations here: https://developer.sony.com/develop/open-devices/
Can I build it by myself?
Sure, just follow these instructions and have patience!
What works and what doesn't?
According to this official page, almost everything seems to be fine.
How can I flash it?
Follow these steps:
Unlock the bootloader (this will erase your data and will void warranty): https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Setup fastboot on your PC (there are many guides for this step)
Download and unpack the zip archive
Open a shell into the folder containing unpacked files
Run these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (it’s not necessary to flash userdata every time)
Download and unpack the corresponding vendor image from here: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open a shell into the folder containing unpacked image
Run this command:
fastboot flash oem SW_binaries_for_Xperia_xxxxx.img (where "xxxxx" varies depending on the file)
(optional) In case you want to flash GApps, Magisk or other mods, you can use TWRP: https://forum.xda-developers.com/xa2-ultra/development/recovery-twrp-3-2-1-0-touch-recovery-t3774193
Reboot the device and enjoy!
Download link
You can get the builds from my AFH folder: https://androidfilehost.com/?w=files&flid=269497.
I haven't done any change to Sony's source code, these are vanilla builds.
Credits
All credits go to Sony and Google.
XDA:DevDB Information
Sony AOSP, ROM for the Sony XA2 Ultra
Contributors
axxx007xxxz
Source Code: https://github.com/sonyxperiadev
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-05-08
Last Updated 2018-05-08

Reserved
NOTE: I'm in no way associated with Sony, these are unofficial builds and are made for pesonal usage.
Also, these builds are untested so I can't assure they're going to work!

Reserved 2
Post reserved for future usage.

Reserved 3
Post reserved for future usage.

Reserved 4
Post reserved for future usage.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r20
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 81032020581dd636ab9d7f8414609bad07332288
Last commit of sonyxperiadev/kernel: 1df958f2943c6c5cae31018e42d2f42e8a55c4b3
Last commit of sonyxperiadev/device-sony-nile: c775da101d57377979cdcb79b1ba1b5bbd3739a4
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=818222786056029296.

It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).

Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying. And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it.
Click to expand...
Click to collapse
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.

roirraW "edor" ehT said:
I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.

Casserole said:
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.
Click to expand...
Click to collapse
You're welcome! I'm not suggesting that you flashing Magisk or anything is the cause of this on this ROM, it's just related to changes in Android 8.1 and that it doesn't really necessarily mean there's something wrong. I'm sure there are ways around it, but since I'm not a developer and I don't know what triggers it, I don't know.

Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?

tombassi said:
cool down dude !! XDA is not the correct please for these bad words. if you don't know what you are doing that is not the Developer fault and if you need no bugs stay with the stock ROM.
Click to expand...
Click to collapse
Thanks! With "almost everything seems to be fine", I meant that most of the main parts (should) work.
Camera is a known problem on Sony devices due to DRM keys getting erased on bootloader unlock.
Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).
Click to expand...
Click to collapse
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
then reboot the phone and test.
These come directly from H4113 makefile, I can't assure you everything will be fine after this, but you can give it a try.
As per the fingerprint, it's currently broken on all variants, I'm sorry.
mirco_pa said:
Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?
Click to expand...
Click to collapse
Sony website reports it as currently not working on AOSP, I'm sorry.

axxx007xxxz said:
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Click to expand...
Click to collapse
I think SD card problem was related to something else, because it started working after reformatting.
But there were also problems with SIM card, it worked on first boot, but after removing and inserting it again device shown that there were no signal, so your solution may be helpful in this situation. I can't test it due to limited amount of time, though.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r26
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 1c992d7f3f2ef8d0b53397e23227e10489e40bec
Last commit of sonyxperiadev/kernel: ab6fd5b1a4126cfdd4391eefe8eba17eb6626781
Last commit of sonyxperiadev/device-sony-nile: 7d57c76da9ce47849429347e77e013781e63db2f
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=890278863836285554.

Can you build one for H4113? You shood have files for it too

Thanks axxx007xxxz for sharing these builds! They helped me recover Android on my completely wiped h3113 pioneer. Both the 8.0 and 8.1 build work for me. Downloading them to my PC was the hardest part, for some reason the download often fails.
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Thank you!
roirraW "edor" ehT said:
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I get the same error message right after booting, also without root. It's annoying, but I guess I can live with it.
P.S. As I'm a new user, I cannot use links yet. Please use these footnotes instead:
*: https[colon]//developer[dot]sony[dot]com/develop/open-devices/downloads/software-binaries
**: https[colon]//developer[dot]sony[dot]com/develop/open-devices/guides/aosp-build-instructions/build-aosp-nougat-8-1-oreo-4-4/#tutorial-step-6

1. parts of android which are closed source, graphics driver for example. you won't see them.
2. eng should give you more debugging options, like working adb logcat without enabling developer options which is sometimes needed while you're porting android to new device and there's just black screen on the phone for example. correct me if i'm wrong.
3. flashing worked through twrp for me but i had to build unsingned zip.
regarding the internal problem message, just ignore it.

davidhozic said:
Can you build one for H4113? You shood have files for it too
Click to expand...
Click to collapse
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Nonstop decay said:
Downloading them to my PC was the hardest part, for some reason the download often fails.
Click to expand...
Click to collapse
Unfortunately, Android File Host is problematic sometime.
Nonstop decay said:
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Click to expand...
Click to collapse
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.

axxx007xxxz said:
I can make a H4113 build if you want to test it though.
Click to expand...
Click to collapse
Just wondering aside from not being supported in Sony's open device program what exactly is needed to get the H3223 from getting AOSP 8.1 built for it? I can't imagine the kernel being much different on the H3223 from any of the other XA2 Ultra single sim models, right?

axxx007xxxz said:
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Unfortunately, Android File Host is problematic sometime.
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.
Click to expand...
Click to collapse
Yes plese make a build for H4413, i get so many random errors and every time i fix an error there appears another. And is the build for this model supposed to work with h4113? Aren't the boot images incompatible?

[OFFICIAL] [NIGHTLIES] LineageOS 16.0

Reserved

Reserved

Thank you， ota ：）

How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras

7bob said:
How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras
Click to expand...
Click to collapse
Check again.

Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?

zidemizar said:
Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?
Click to expand...
Click to collapse
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.

npjohnson said:
Check again.
Click to expand...
Click to collapse
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?

7bob said:
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?
Click to expand...
Click to collapse
Just follow general guidelines. We already had testers and upgrading from 15.1 to 16.0 didn't cause any issues. Obviously, if you do run into an issue, it is suggested to clean flash first to see if it was a borked update

npjohnson said:
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.
Click to expand...
Click to collapse
Do you have a screenshot showing that it shows under screenlock settings?
Also what gaaps did you use when installing, I used the reccomended mindthegaaps and it kept giving me errors related to pixel apks.

link if image does not work
https://imgur.com/a/1eoVcgk
This is what shows under my screenlock setting, I do not have the setting that allows me to lock the phone using the fingerprint reader, this is from a fresh Lineage 15.1 installation with mindthegaaps, nothing else is installed on it. Had the same issue with lineage 16

Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.

Now I have installed los 16 and it was instructive for me. Learning by doing. After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP? I'm on slot b now and on system_a is nothing. If I want update later, I have to do just flash the zip over TWRP and then reboot it and then maybe flash gapps again, because it's the first update on slot_a? Hope that's works because the encoding problem. Don't have the key.

AmazerG said:
Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.
Click to expand...
Click to collapse
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
allrightlite said:
After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP?.
Click to expand...
Click to collapse
Remove your fingerprint and screen lock method prior to entering TWRP. If you came from a stock ROM you must format data before flashing LOS. Updates can be done automatically with the updater, or manually thru recovery. The latter requires more time with no added benefits. Also encryption is enabled with custom ROMs.

So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done

I have tries at this moment to update over the lineage updater in settings and it's stopping with installation error. After try to reboot to TWRP it's endet up in reboots. But LOS16 stats normally again after press power button a little bit. Now I try again to update. Presumably it isn't working again. I think I will reflash twrp first and try then over this to update. Good idea or what's going wrong on my phone?
I must do new install. All broken. Holy crap. Hope this time I get it working.

7bob said:
So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done
Click to expand...
Click to collapse
what are the steps to update from firmware 8.0 to LineageOS 15.1 or 16, please
unlock bootloader, twrp, magisk (no problem),
My phone locks the boot loader again when I try to install a custom ROM
my firmware (TWRP, magisk)
RETAIL/NASH_RETAIL_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
in any way I thank you :good:

Ok, I have found out how get it working. Updater app not working here, always installation error after end of update process. Don't know why. So now I have a way found out, which seems to be working every update. Go to TWRP, flash los16 new zip and, this is very important (understand it very late xD) don't forget to flash twrp installer zip directly after los 16, because otherwise on the other slot is the stock recovery again. So, after this boot to the other slot with twrp directly from your phone and flash gapps every time, every update. Here I forgot it and nothing of the play store and co. was working anymore. Android Framework ID was away, too. Is there an easier way to update over TWRP or do I have to do so? And what happend to, backup wasn't possible to restore, maybe cause thought encoding?
The new update process with A/B is not easy to understand directly But the rom is a beast, very very good. Why I update and switch to los16? That's easy, because the bluetooth bugs on stock oreo was terrible (and no 8.1-batterie icon ) and lags on few drm videos and here and there. Speed of the UFS-flash going slower and slower, no its 3 times faster again. This phone works really great with LOS16. Very good work! It's not easy to understand all, but I will get it in my brain
Edit: There is another point, which could be interesting. Netflix shows error on start up (15001) and this even though safety net is passed. Hm.. Have downloaded from play store. Maybe older version does do this job, don't know.

Ace42 said:
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
Click to expand...
Click to collapse
Is there anything different between Sprint Z2 force and Tmo ones in terms of hardware such as lack some band or what?

[ROM] Dirty Unicorns 14.7 {Bonito} (09/13/20)

{
"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"
}
About Us:
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.
Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.
We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_bluecross
Flashing Instructions:
If you have a device that uses TWRP
Verify that you're using the latest version of TWRP
Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
Flash the latest version of this ROM
Reboot and ENJOY!
If you have a device that does not use TWRP
Download boot.img and ROM zip from DU server
Reboot into bootloader and flash the boot.img
Code:
fastboot flash --slot all boot boot.img
Reboot to recovery
Go to recovery select factory reset
Select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Reboot and ENJOY!
If you're just updating DU on a device without TWRP
Download ROM zip from DU server
Reboot into recovery and select Apply update from ADB to flash the zip
Reboot system now and ENJOY!
**All bugs and feature requests must be reported to JIRA**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
**If you fail to follow these instructions, please don't bother reporting any bugs**
Download Links:
Build(s) - Bonito
Other Links:
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
JIRA (Bug Reporting / Feature Requests) - http://jira.dirtyunicorns.com/
Telegram - https://t.me/dirtyunicorns / https://t.me/DirtyUnicornsSupport
XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel 3a XL
Contributors
NYCHitman1, jbats
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-13
Created 2020-08-08
Last Updated 2020-09-13

Thank you so much!
I've used nothing but DU since March and I'd like to thank you for your continued work on our device. Hopefully now more people will find and appreciate your efforts!

Sweet a new rom to try out

@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.

41rw4lk said:
@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.
Click to expand...
Click to collapse
Currently, no. However, we are planning to do this in the future.

Just flashed & loving it so far. Great to see the team still working. I'm trying to remember the first phone I flashed dirty on. Maybe htc m8. It was so long I don't recall

I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation

godpowerrr said:
I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation
Click to expand...
Click to collapse
We're not making anymore variations of the boot animation. We have a light version and a dark version. That's good enough for us.
As for the lack of customization, we include what we find useful. We're never going to be one of these cookie cutter kitchen sink ROM's you see littered across XDA. If you would like to make a particular feature request, check the OP for instructions on how to do so.

FYI
Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.
Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
Code:
C:\Users\Russell\Downloads\Android\ADB and Fastboot>adb sideload du_bonito-v14.6-20200808-1220-OFFICIAL.zip
serving: 'du_bonito-v14.6-20200808-1220-OFFICIAL.zip' (~47%) adb: failed to read command: No error
In recovery
Code:
Step 1/3
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
E:Error in /sideload/package.zip (status 1)
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.

ssurell said:
Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.
Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
In recovery
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.
Click to expand...
Click to collapse
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.
TWRP does not work on Q for Pixel 3 and 4.
Please do some research before messing with the device further.

NYCHitman1 said:
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.
TWRP does not work on Q for Pixel 3 and 4.
Please do some research before messing with the device further.
Click to expand...
Click to collapse
I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery

ssurell said:
I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery
Click to expand...
Click to collapse
Unfortunately, it doesn't. The flash-all script only flashes to the active slot on the device, so you would have to manually change slots and run said flash-all script again to be completely up to date. As for the platform-tools versions, I believe 30.0.4 is the latest revision available at this time. Might be a good idea to download that and delete everything else you have.
Outside of this, our flashing instructions are very clearly labeled and should get you through the process of flashing DU as long as you follow the instructions that are applicable to you.

ROM is running great. Do we have to do a full wipe or can we just clear cache between uodates

sjpritch25 said:
ROM is running great. Do we have to do a full wipe or can we just clear cache between uodates
Click to expand...
Click to collapse
You don't have to wipe at all between updates. It's written in the OP. Please read the instructions.

Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!

champ784 said:
Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!
Click to expand...
Click to collapse
Could be a larger platform issue. You could provide logs to Google, but seeing as R is literally right around the corner -- they'll likely ignore it until the revision is out to the masses.

Download from DU site fails
I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?

NYCHitman1 said:
Could be a larger platform issue. You could provide logs to Google, but seeing as R is literally right around the corner -- they'll likely ignore it until the revision is out to the masses.
Click to expand...
Click to collapse
Yeah that's what I figured. The second Android R releases, I don't see anyone caring ??

socksi said:
I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?
Click to expand...
Click to collapse
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.
I will reach out to our webmaster and have him look into it. Stay tuned.

NYCHitman1 said:
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.
I will reach out to our webmaster and have him look into it. Stay tuned.
Click to expand...
Click to collapse
It fails even when using a VPN tunnel. Most probably it's not my Internet connection.
Maybe some kind of GEO blocking? I'm from Germany.

[ROM][Android 11][UNOFFICIAL]LineageOS 18.1[LG G8][alphalm]

WARNING: Carriers in the US are shutting down 3G networks. This ROM does not have VoLTE capability at this time, so calls will not be sent or received if your carrier has disabled 3G.
If you are in the US and wish to use this ROM, please check your carrier's 3G support and if there are any dates set for a 3G shutdown. If you are outside the US, this is unlikely to affect you, but do a google search anyway.
At the time of writing this disclaimer (March 18, 2022) AT&T has already disabled 3G and T-Mobile will shut down 3G networks for prior sprint users by the end of the month.
{
"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 18.1 (Android 11) for US LG G8 (G820*)
LineageOS (also known as “Lineage”) is a free and open-source operating system based on Android. It is the successor to the custom ROM CyanogenMod.
Code:
#include "std_disclaimer.h"
/*
* 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.
*/
This is an unofficial build of Lineageos 18.1 (Android 11) for the US LG G8.
THIS IS NOT A GSI
This works on all carriers!
This will only work for the US LG G8.
This will only work for alphalm, not alphaplus.
This will not work on the 'G8s' or the 'G8x'.
This will not work on Korean models.
YOU HAVE BEEN WARNED.
Partition Backup:
Please backup all important partitions and data before installing this ROM. THis is very important for certain carriers including AT&T, as they do not provide the KDZ firmware files, so once you install lineage, you may not easily be able to go back if you haven't made a backup, though it's a good idea for anyone attempting to install any ROM on any device.
Important partitions are:
boot
product
vendor
dtbo
vbmeta
system
Make a backup of these in QFIL (both _a and _b slots of each, You will need to use QFIL during the following bootloader unlock guide so you can make this backup during that process.
Bootloader Must Be Unlocked
There's a guide for this linked below. This step is a must.
This must be installed from TWRP or other custom recovery on stock.
Please make sure latest stock firmware is installed. This may not be completely
necessary, but having an old firmware image installed has caused me
issues with call audio and such while developing this ROM.
What Works
Bluetooth
Wifi
Call/SMS (WARNING: Carriers in the US and perhaps other countries are disabling 3G, so no more calls and possibly even texts if this happens with your carrier!)
Data 2G/3G/LTE
Camera (GCam is required for wide angle back camera)
Audio
NFC
GPay Contactless Payments (Requires Magisk Hide)
Hotspot
Google Assistant Voice Match
Nearly Everything!
What Doesn't Work
VoLTE/VoWiFi/IMS - LG has a complicated proprietary IMS, so no VoLTE at all!
Assistant Voice Match while screen is off
AOD (I'm working on this)
Please let me know in the comments
Requirements
US LG G8 on any carrier
Latest firmware installed on device (may work with older firmware but results will vary)
Latest unofficial LineageOS zip (on github, linked in thread) and TWRP zip (attached to thread)
SD Card or adb for sideloading (see step 5)
PC with Windows (Linux is possible if you know what you're doing. Check out bkerler/edl on github, it works the same way as QFIL, but requires a small amount of Linux knowledge/experience.)
How to install
Unlock Bootloader and root with Magisk (Follow guide linked below)
Make a backup of all your data (I strongly recommend making a backup of your partitions with qfil (or EDL for linux users))
Download TWRP and the Lineage zip
Installl TWRP (Follow quick guide in attached archive)
Place Lineage zip and anything you want to install through recovery on external SD card (Can also be sideloaded with 'adb sideload', If so, skip this step)
Boot into TWRP or other custom recovery with volume and power shortcut
Install Lineage zip from sdcard or sideload (I always recommend sd, there's less to go wrong)
Once it completes, reboot into recovery again. There's an option for this in TWRP to skip the button combo. TWRP IS GONE. YOU WILL BOOT INTO LINEAGE RECOVERY. USE THIS FOR REMAINING STEPS.
Format Data (This is completely necessary. You will be returned to recovery on boot if you do not follow this step.)
Install Gapps, Magisk, and anything else from sd or with adb sideload. (If you don't want/need root, you can skip installing Magisk
Format Data Again (System will send you back to recovery to do it if you don't)
Reboot to system and enjoy!
A big thanks to SGCMarkus for everything he has done for LG devices on this platform. This wouldn't be possible without his work. Go buy him a coffee or something!
Big thanks to those I haven't named from the V50 G8 G8s Telegram group as well
Other Credits
J0SH1X
enforc
Links
Guide For Unlocking Bootloader
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose posted by Seasee606
GCam For Wide Angle Back Camera
GCam Hub MGC_8.1.101_A9_PV0i
Go to this link and download MGC_8.1.101_A9_PV0i_libs_MGC.apk
Others will work, but some not as well. I've noticed some issues with this version crashing. If you experience this, try other versions from the link above.
GApps
Only install GApps packages for Android 11!
NikGApps
Highly recommended. (Because I use it and I know it works, it doesn't necessarily mean it's best though.) Follow download buttons. Go to Releases > NikGapps-R. Packages will be here. Info about what each package contains is on the page linked above.
MindTheGApps
I've tried this once and It seemed alright, but it was a little minimal for my taste. It's linked by LineageOS so it's here.
OpenGapps
I haven't tried this at all, but it's also linked by LineageOS so it should be here.
Download
Release: LineageOS 18.1
Release Date: 2021-10-13
MD5: 8e63d765ea7fe90c6fe9ebf4975c2a35
Filename: lineage-18.1-20211013-UNOFFICIAL-alphalm-signed.zip
Size: 908 MB (951854628 B)
Device: LM-G820 USA
Android Version: 11
Download from Github
Release Page
Sources / Device Tree
https://github.com/xmusjackson/android_device_lge_alpha-common
https://github.com/xmusjackson/android_device_lge_alphalm
https://github.com/xmusjackson/android_device_lge_sm8150-common
https://github.com/SGCMarkus/android_device_lge_common/tree/76432f76c5994bd1033d01150433f081a8c6dee3
https://github.com/xmusjackson/android_kernel_lge_sm8150
https://github.com/SGCMarkus/android_hardware_lge/tree/64bef53ae00f0496e35bc59a61a07ad40537d706
https://github.com/xmusjackson/proprietary_vendor_lge_alpha
Screenshots
Spoiler: Screenshots
Screenshots from LM-G820QM7 (Open US)
Attached is a copy of the archive containing TWRP for the G8. I downloaded this from telegram and take no credits, there just isn't a thread about this here that I've seen. The instructions to install are included in the archive.
Please let me know of any bugs in the comments!
Thanks!

Downgrading and Crossflashing
This ROM requires your device to be on stock Android 10. Downgrading may be necessary, with some devices requiring a crossflash for the process!
Crossflashing
Crossflashing is only for those who own a G8 from a carrier that doesn't provide a KDZ (firmware image). There is no practical purpose to crossflash unless you really don't want the carrier bloatware, but there are easier ways to remove this.
There is a guide for crossflashing Here.
I haven't tried to crossflash personally but I've seen much success. The G8/G8X/v50 Telegram group (specifically the notes there) can definitely be a lot of help to anyone with an AT&T or Sprint G8 that wishes to go this route.
Downgrading
First, you have to download the appropriate firmware. You can select your preferred firmware here:
https://lg-firmwares.com/lg-lmg820qm-firmwares/
but this one is for the openus model and should work for sprint and at&t models:
https://lg-firmwares.com/downloads-file/25195/G820QM20f_00_NAO_US_OP_0402
Second, you have to use LGUP with some slight modifications to flash the firmware to your device.
NOTE: This works without an unlocked bootloader and will relock the bootloader on your device. If you've unlocked your bootloader previously, you'll have to repeat the process.
Here is a brief guide for downgrading taken from this post:
(DO NOT FOLLOW THIS GUIDE IF YOU NEED TO CROSSFLASH)
Quote from TheLoonyRebel:
...
And here's the software you will need to get the job done:
https://www.androidfilehost.com/?fid=8889791610682884898
1. Install the LG drivers if you haven't already.
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
2. Install LG Up
3. Install the LG Common DLL
4. Copy the UI confilg files to C:\Program Files (x86)\LG Electronics\LGUP\model\Common
5. Turn off the G8.
6. Once off hold up volume up then insert your USB into the phone.
7. Open LG Up. If you get an error message ignore.
8. Select REFURBISH in LG Up
9. Load the KDZ file by drag and drop where it says BIN file
10. Click start
11. Once the downgrade is done installing the phone will reboot...
...
Click to expand...
Click to collapse
Do not follow the bootloader unlock method in that thread as it will fail miserably and soft brick your phone, only follow the downgrade method quoted above.
If there are any questions, please ask in the comments.
Edit: I've attached the necessary files in case that androidfilehost link becomes dead in the future.

Thank you for your efforts!

Can i install rom for G820N Korea ?
Can you help me fix vibration for G820N ?
I using Los gsi rom but my phone hadn't vibration

minhthien0711 said:
Can i install rom for G820N Korea ?
Can you help me fix vibration for G820N ?
I using Los gsi rom but my phone hadn't vibration
Click to expand...
Click to collapse
I don't think this rom would work on your device, but I could be wrong. Either way, I do not recommend trying it. Also, I've never used a GSI but I've heard they're buggy in general.

After two days of use, I found that the functions of always on display are abnormal, and the side Google buttons cannot be customized

lufan said:
After two days of use, I found that the functions of always on display are abnormal, and the side Google buttons cannot be customized
Click to expand...
Click to collapse
There's a feature in Lineage called Ambient Display, alongside AOD. It's hard to find in settings, but if you go to your quick settings tiles and tap the edit button, there will be a tile for Ambient Display to add. Disabling this made the display behave more normally for me.
If this does not fix your problem, please elaborate
As for the side Google buttons, I'm not sure what you're referring to, please be more specific.

Thank you for your efforts!
I was about to get rid of my Sprint G8 for not receiving any software updates for half a year haha
Edit: Just installed and its working flawlessly on Sprint G8

Thank you!
I tested MindTheGapps, contacts and calendar couldn't sync, because google play service had no rights.
Just set the rights, it's perfect.

cheger32 said:
There's a feature in Lineage called Ambient Display, alongside AOD. It's hard to find in settings, but if you go to your quick settings tiles and tap the edit button, there will be a tile for Ambient Display to add. Disabling this made the display behave more normally for me.
If this does not fix your problem, please elaborate
As for the side Google buttons, I'm not sure what you're referring to, please be more specific.
Click to expand...
Click to collapse
Thank you for your reply. I tried to turn off ambient display and turn on AOD. After locking the screen, AOD information will be displayed for a second or two, then flash once and disappear

lufan said:
Thank you for your reply. I tried to turn off ambient display and turn on AOD. After locking the screen, AOD information will be displayed for a second or two, then flash once and disappear
Click to expand...
Click to collapse
It seems this is a bug. I will look into it and add it to the list. Thanks.

First of all Thank you for your great work you saved the life of my Lg G8, so I will tell my experience after 3 days of use, deactivate everything that would have to do with the AOD because it is not working correctly even though in my case It is not essential, the ROM is really smooth and everything else works correctly, I am using it with Open GApps and it has not given me problems, the truth is the ROM is on the right track, but I only had a problem and it is time to playing the device hangs it stays bibrando until it forces the closing of the app, it does not always do it but when it happens annoying, I also feel that it does not go so fluid in the games compared to the stock, but it is nothing serious perhaps with a better kernel you can get more out of the ROM but for the moment it is a great advance for the LG G8 and again Thanks for your work!.

Thank you for taking the time for making this ROM OP! Will install later today and report back.

I disabled time sync, reboot. System time back to compile time.

starboi4eva said:
Thank you for taking the time for making this ROM OP! Will install later today and report back.
Click to expand...
Click to collapse
Been using this rom for two days and it is amazing. Fast and barely any issues apart from what is mentioned above. My only personal gripe is the slight drop in gaming performance than stock.

hi. can i do this with lg lmg820um Android 9 pie version. I will be glad if you answer

Alrighty, So I've been using the ROM for 2 days and I have a minor grievance with the OS itself which I'm sure is out of your control, Wallpaper zoom is incredibly annoying and the most common work around is an app called KLWP which is compatible with stock rom but not this one. My current solution is an app called SB Wallpaper Changer, under portrait setting it to single and Fixed, fixes the problem. But this breaks any system function that bases colors on the wallpapers color.
That all being said TYVM OP, stock rom on my device was falling apart at the seams, and while it may have taken me 15 hours to get LOS working it's ages better than stock.
Also edit: MY Phone was a Model LM-G820TM but reported as a 850UM in LG Bridge, don't even wanna know why. Android Reports LM-G820 after unlock and LOS

orkhan96 said:
hi. can i do this with lg lmg820um Android 9 pie version. I will be glad if you answer
Click to expand...
Click to collapse
I don't think this would work. Your device's firmware should be updated to android 10. The ROM does not install this, it is retained from original stock ROM. This would probably result in a brick.

Ok so I'm about a week in, the fingerprint scanner is just, gone. It's not that it isn't reading, it's just not an option. The fingerprint scanner is completely gone from the system settings, any attempt to communicate with it fail immediately. it just, disapeared from the software. Restarting or factory reseting didn't do anything, it's still gone.
Edit: Gonna try and go through recover to update then reflash if needed, pain
Edit 2: reflashed, still gone

Skye_h said:
Ok so I'm about a week in, the fingerprint scanner is just, gone. It's not that it isn't reading, it's just not an option. The fingerprint scanner is completely gone from the system settings, any attempt to communicate with it fail immediately. it just, disapeared from the software. Restarting or factory reseting didn't do anything, it's still gone.
Edit: Gonna try and go through recover to update then reflash if needed, pain
Edit 2: reflashed, still gone
Click to expand...
Click to collapse
How strange I have been for 2 weeks and I still have not had that problem in relation to fingerprints, will the sensor of your device have been damaged?

Development [CLOSED][ABANDONED] [OFFICIAL] [Rosemary/Secret/Maltose] Project Kasumi 1.x for Redmi Note 10S

{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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.
*/
Another weebified custom ROM aiming to be a home for weebs - Based on Project Materium, an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:
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.
Click to expand...
Click to collapse
We offer vanilla, GApps and AuroraOSS variants. If you install a vanilla variant, the only supported GApps package is MindTheGapps (GApps/AuroraOSS builds are not available for a few devices due to space issues).
Download & instructions:
Install MIUI 12.5 if you have updated to anything Android 12.
Fully install custom recovery of your choice.
Flash the ROM. You can also sideload it with ADB if you want to.
!!! If you'll flash Magisk, you'll need to enable "Reflash (recovery) after installing a ROM" after choosing the ZIP as well !!!
After flashing, reboot to recovery.
Format data.
Flash Magisk if you want to.
Reboot to system and enjoy!
Download (Taken down due to discontinuation)
IMPORTANT: If you are coming from another ROM, you need to format data (TWRP > Wipe > Format Data > *type "yes"*).
IMPORTANT: If you want to keep Magisk after each OTA, you need to make it flash to inactive slot **right before rebooting** (Magisk > Install (In "Magisk" card) > Install to inactive slot)
About:
Features:
Latest security patches merged from LineageOS
SafetyNet passing unconditionally without Magisk/with kdrag0n's SafetyNet fix
Many optimizations coming from Stellar OS/Project Materium/droid-ng
New wallpapers & bootanimation
QS customization (tint, rows customizer, data usage)
Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
Kill app from notification
Notification pulse
KitKat-style notification ticker
Screenshot sound toggle
Per-app volume
WiFi & Bluetooth timeout
Smart Charging & Cutoff
Sensor, Wakelock and Alarm blocker
Battery info on lockscreen
Improved microG support (signature spoofing, location support)
...and more! (We accept suggestions!)
What's working:
Almost everything
Bugs:
Microphone doesn't work when speaker is enabled during calls.
You tell me.
Sources are available at https://github.com/ProjectKasumi and https://github.com/Kasumi-Devices
Full list of device sources used;
Device tree
Linux kernel tree used
Vendor tree for proprietary blobs
ROM Founded By: Yuki (AITEx64)
ROM Developed By: Beru Hinode
ROM Designed By: Ayuko, Qirkl and UsiF.
ROM OS Version: 1.3 "PoPiPa" R2
ROM Kernel: Customized Linux 4.14.186 from MiCode
ROM Firmware Required: MIUI 12.5.16.0.RKLMIXM (Global)
Based On: Project Materium 1.0 (LineageOS 18.1)
Version Information
Status: Discontinued
Last Stable Version: 1.4 "PoPiPa"
SELinux Status: Permissive
Initial Release Date: July 20, 2022

poggers! atleast some buildbot didn't post it this time

J6idot said:
poggers! atleast some buildbot didn't post it this time
Click to expand...
Click to collapse
It wasn't even their build, they just took my build and posted it away! XD

Let's goo. Very awesome work here

Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...

solidamage said:
Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...
Click to expand...
Click to collapse
I could never get used to MIUI myself so I feel you. For custom ROMs, there are quite a lot built (buildbotted) with practically the same bugs as well; you can check them out in respective Telegram groups/channels!

Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon

i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.

nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
It happens to me too ... Any advice?

Is this available on Android 12?

nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?

Oxydeme said:
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?
Click to expand...
Click to collapse
yup did all the steps in the thread

nintendobuster420 said:
yup did all the steps in the thread
Click to expand...
Click to collapse
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked

Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc

nintendobuster420 said:
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc
Click to expand...
Click to collapse
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
still no fast charge, will keep it tough
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
@HistoriaXV @nintendobuster420 hope you could success flash in the next days

Oxydeme said:
Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon
Click to expand...
Click to collapse
System reports "Charging slowly" but my battery fully charges from ~10% in just 1.5~2 hours.

nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
I have recently pushed a boot fix about this, you can flash it and format data to get it fixed.

Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
I use the OFOX from Woomy and it works with it too, so it's not recovery fault.
You mentioned firmware requirement there, good shot! Glad to see someone that's not from the development team finally noticing it!

Oxydeme said:
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
Click to expand...
Click to collapse
The vbmeta required is shipped along with the ZIP itself, so whether if you disable it or not, you can always keep verity enabled AS LONG AS YOU DON'T MODIFY ANYTHING INCLUDING INSTALLATION OF TWRP. The boot problem was due to some missing permissions required with Lawnchair 12.0, which was platform-specific issue. I have mitigated it as the lead developer of Kasumi and now just waiting for LineageOS to merge August '22 ASB on their Lineage 18.1 branches to ship newer builds. Until then, I have placed a little flashable that you can slap in on the recovery. It's global (means will work on all devices with latest Kasumi build installed). In fact, all it does is just putting the new permission XML file.
Oxydeme said:
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Click to expand...
Click to collapse
Not at all. Even though I have Secret, everything should be around the same across all variants, given that Woomy also tested it only for NFC during initial bringup before.
Oxydeme said:
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
Click to expand...
Click to collapse
The dedication and the hassle... My God, it's just pure inspiration to me. XD
Oxydeme said:
still no fast charge, will keep it tough
Click to expand...
Click to collapse
As I said previously, it's what system reports presumably due to some SEL denials. I tried to get as many as possible sorted out, still no luck. But just as a fact, it actually is fast charging.
Oxydeme said:
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
Click to expand...
Click to collapse
Well, thank you I guess. ^^;
Before I begin with replies to these, just referring to "dude", I'm a girl so I would prefer you calling me with "dudess" or "dudette" instead. Again, all up to you. No forces here.
The debloat is rather Lineage talent, I really just based on Materium and added things on top.
That 13 GB system partition is something that's coming from partition values from source, so whatever you do unless you flash GSI, it will always be 13 GB. See GitHub:Kasumi-Devices/[email protected]/BoardConfig.mk (Partitions section, BOARD_SYSTEMIMAGE_PARTITION_SIZE flag) for more info.
Eh, I still can't find a way to get CPU info properly, I guess it's related to kernel? Unsure though.
And some more tweaks will come as well, just stay tight! I'm working hard on another update! ;3

Sambit0789 said:
Is this available on Android 12?
Click to expand...
Click to collapse
Unfortunately no. Kasumi 1.x.x are all Android 11. Android 12 Kasumi will be possible only once our internal tests will be done and I finally finish working on Kasumi v2. Hundreds hyped, gradually widening audience, looking into the release of it. xD

Database Develop

welcome