Manual OTA update for rooted device - Moto G6 Questions & Answers

Manual OTA update for rooted device - Moto G6 Questions & Answers

The phone that I would like to update is a Moto G6, type M390A. The phone is currently running Android 8.0.0, build OPS27.104-92. The phone is rooted, stock ROM, and has TWRP and Magisk installed.
Earlier today, I followed the instructions here https://highonandroid.com/android-howtos/how-to-ota-update-rooted-pixel-phones-without-computer/ to update my Pixel 3XL. The instructions were almost flawless – the only two minor ‘gotchas’ were 1) having to first update to the most recent version of TWRP (when I tried the version that was a few months old, I received a kDownloadPayloadPubKeyVerificationError) and 2) I had to reinstall Magisk after the reboot mentioned in Step 9. Bottom line – the process went quickly and easily. Needless to say, all of my apps, settings, and data were unaffected by the upgrade.
I am hoping that the experience with the Moto G6 might be as smooth and easy. However, there are three differences of some concern:
The OTA zip file is not from the Motorola site – I found what appears to be the proper file here: https://www.skyneel.com/moto-g6-pie - I selected the ‘Download Moto G6 Pie Android 9.0 OTA ROM’ link.
The TWP file is only available as a .img file, not a zip file.
For the Pixel 3XL, the OTA was a minor version upgrade as it was already running Android 9; for the Moto G6, this would be a major version upgrade.
My question for the group is simply this: Using the files mentioned above, if I follow the procedure described in the first link; namely copy ota.zip, magisk.zip, and twrp.img to the phone; reboot to TWRP and install, in order, OTA, TWRP, and magisk; and then reboot; will I likely succeed in updating the phone while not messing up my data, settings, and data?
Thank you.

There are a bunch of g6's. Trying to apply an OTA at random will fail. Your pixel has a/b partitions, g6 does not. A only.
The best way I know to update a Moto is, make sure you know your exact model number, and update channel. Both can be found in about phone section in settings. Download a full firmware package (not an update zip) and either
1. Extract it and flash every partion with fastboot
Or
2. Use RSDlite (windows PC program) and flash the firmware with that. Then flash TWRP again (or just boot it) and flash magisk.
I prefer option 2. Easy peasy. And RSDlite will ask if you want to use flashfile.xml (wipes data) or the servicefile.xml (doesn't wipe data.
RSDlite basically performs all of the fastboot flashes for you, and the servicefile skips the data format.
Even if you restore 5je stock recovery, most attempts at trying to flash an OTA zip will fail. You may have made some changes to the system at some point which will trigger an assert prop failure.
Plus the OTA would have to be for your specific g6.
Someone else may chime in with different instructions.
But this is not a Pixel. There are like 20 something different g6's and update channel combos.

madbat99 - I appreciate your taking the time to provide a thorough reply, thank you. Sadly, I still have questions: Following is a screen grab of the About Phone tab.
{
"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"
}
You indicated that I need:
Exact model number: It appears to simply be moto g6
Update channel: I see a 'Software channel' - is this the same thing?
When I went looking for firmware, I found this page https://www.getdroidtips.com/moto-g6-plus-play-stock-firmware/, but
Android 9.0 is not shown as being available (but other sites suggest that at least a beta version has been released)
I do not see the existing build listed, thus I am worried that none of these are correct
Would you please be so kind as to point me directly to an appropriate source of firmware files for this phone?

groston said:
madbat99 - I appreciate your taking the time to provide a thorough reply, thank you. Sadly, I still have questions: Following is a screen grab of the About Phone tab.
You indicated that I need:
Exact model number: It appears to simply be moto g6
Update channel: I see a 'Software channel' - is this the same thing?
When I went looking for firmware, I found this page https://www.getdroidtips.com/moto-g6-plus-play-stock-firmware/, but
Android 9.0 is not shown as being available (but other sites suggest that at least a beta version has been released)
I do not see the existing build listed, thus I am worried that none of these are correct
Would you please be so kind as to point me directly to an appropriate source of firmware files for this phone?
Click to expand...
Click to collapse
So your software channel is fi. Not sure where to get that one. Clicking on hardware in that menu gives you your model number. Under SKU. See in screenshot. I'll look for a firmware for you.

Forgot screenshot

You have a Google fi device. It doesn't appear pie is available for yours yet. It will be, I would wait if I were you.
here are the currently available firmwares for your model. There are ones that have been updated to pie, and one or more of those may be able to be flashed to your phone. I don't know what that would do to your fi eligibility/connectivity. So someone else will have to chime in on that.
The 2 firmwares on that page are newer than what you are on. Newer security patch updates than you have now. Good.
Now if you want pie, skip to the bottom of your thread here!

@groston
I found this post, where a member with the fi version of the g6 that says he flashed the pie firmware for the retail g6 and all went well. I will also link the post that he mentions which contains the flashfile.

madbat99 - again, thank you! The version for this phone is PVT1, SKU XT1925-6.
In your opinion, can I use the zip file linked in the post your cited with the RSDlite process you outlined, specifically using the servicefile.xml approach? The SKU for the phone the poster mentioned is XT1925-5 reteu - close, but the same?

Here is the post with instructions and links to everything you need. It's official Moto firmware, so no "need" to even have an unlocked bootloader (but I'm sure yours is already unlocked).
So now you have a couple options. you can either update to the newest Oreo security patch for your device, or update to pie if you like.
---------- Post added at 09:16 PM ---------- Previous post was at 09:06 PM ----------
groston said:
madbat99 - again, thank you! The version for this phone is PVT1.
In your opinion, can I use the zip file linked in the post your cited with the RSDlite process you outlined, specifically using the servicefile.xml approach?
Click to expand...
Click to collapse
Yes you can use RSDlite to flash it if you want.
But... With the jump from Oreo to Pie, and switching software channels, I would recommend a data wipe. Meaning the flashfile in RSDlite.
You can try without the data wipe, then if something doesn't work properly for you you can always wipe data afterwards.
@groston do you have RSDlite?
Guess I might as well grab you link for that too, lol
I realize that the bulk of that post was from a RETEU version, but the person quoting it said they have the fi version and it worked.

Here is the RSDlite I use (plus a bunch of other useful programs). Check my screenshot, I circled the one you want.
One last thing, you might want to pop in to the thread I linked and ask others about flashing it on the fi version. Just so you cross all the t's and dot all the i's.

groston said:
madbat99 - again, thank you! The version for this phone is PVT1, SKU XT1925-6.
The SKU for the phone the poster mentioned is XT1925-5 reteu - close, but the same?
Click to expand...
Click to collapse
This is the part that I saw that related to your phone.

I asked Google Fi tech support if they could point me to a firmware version for the fi software channel. Here is there (not terribly helpful) reply:
I see that you'd like to update OS to Android 9.0 on your Moto G6. Please know that we only control updates of Android One model devices such as Moto X4 and Pixel Designed for Fi phones. For devices such as Moto G6, LG V35 and LG G7 users need to check with the OEM. Therefore, I'll provide you the manufacturer contact details. They'll definitely help you with the update.
We've looked into all possible options to provide you the firmware file. However, I'm sorry to say that we didn't find any firmware file which can be used to update OS to Android 9 on your Moto G6. Please be assured, Motorola will help you with the OS update.
Click to expand...
Click to collapse
I will follow madbat99's suggestions...

Related

[Q] Which Factory Image? (Project Fi -5.1.1)

Just started using Project Fi today and a 5.1.1 update wanted to download. I assume this is due to Project Fi stuff. I cannot install as I am rooted but locked bootloader. My Nexus currently has LMY470 on it and was purchased from Amazon for use on GSM. When I look at the images on the developers site I see LMY47Z for Sprint Only and LYZ28E for T-Mobile Only. When I search around I found a coupe of references that I should be using LMY47Z (for Sprint) on this phone for 5.1.1. I am just going to load the factory image but want to be sure I use the correct one. Can anyone confirm this?
Thank you.

Yep that's the right one, its actually Sprint and international only. honestly the T-Mobile one works fine too but for safety sake, I'd use the Sprint/international image, 47Z.
Sent from my Nexus 6 using Tapatalk

HolyAngel said:
Yep that's the right one, its actually Sprint and international only. honestly the T-Mobile one works fine too but for safety sake, I'd use the Sprint/international image, 47Z.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It's also The ATT and Verizon image.

prdog1 said:
It's also The ATT and Verizon image.
Click to expand...
Click to collapse
Yeah, all but tmo basically ^^
Sent from my Nexus 6 using Tapatalk

Thank you!
HolyAngel said:
Yep that's the right one, its actually Sprint and international only. honestly the T-Mobile one works fine too but for safety sake, I'd use the Sprint/international image, 47Z.
Click to expand...
Click to collapse

Just do the international 5.1 version and it will immediately download the OTA to 5.1.1 after boot.

Are you suggesting the LMY47I version and let it update to the 5.1.1 Project Fi version before I root?
skola28 said:
Just do the international 5.1 version and it will immediately download the OTA to 5.1.1 after boot.
Click to expand...
Click to collapse

Ok, so here you have a choice:
Project Fi 5.1 will OTA sometime this week to 5.1.1 - You will be on the Fi variant of Android OTA schedule if you flash a Fi variant of Android
The image linked below will update to 5.1.1 within a few minutes of booting (Google said they would upload the 5.1.1 image but they are still 'getting around to it'.)
LMY47I
https://dl.google.com/dl/android/aosp/shamu-lmy47i-factory-c8afc588.tgz
Both versions work with Project Fi; there are apparently minor changes to 5.1.1 for the Fi variant that makes it slightly better for Fi. They haven't disclosed what those changes are.
To be clear though, you can't OTA to Fi 5.1.1 from regular Android 5.1 nor 5.1.1

Thank you. I will try it out, I am wondering if it will work as I have had a minor issues with Fi and Google Support can't figure it out yet.
skola28 said:
Ok, so here you have a choice:
Project Fi 5.1 will OTA sometime this week to 5.1.1 - You will be on the Fi variant of Android OTA schedule if you flash a Fi variant of Android
The image linked below will update to 5.1.1 within a few minutes of booting (Google said they would upload the 5.1.1 image but they are still 'getting around to it'.)
LMY47I
https://dl.google.com/dl/android/aosp/shamu-lmy47i-factory-c8afc588.tgz
Both versions work with Project Fi; there are apparently minor changes to 5.1.1 for the Fi variant that makes it slightly better for Fi. They haven't disclosed what those changes are.
To be clear though, you can't OTA to Fi 5.1.1 from regular Android 5.1 nor 5.1.1
Click to expand...
Click to collapse

If I were in your shoes, I would probably get Fi 5.1, and wait for the update to Fi 5.1.1 OTA. I'm on vanilla 5.1.1 and using Project Fi and I have some minor annoyances too; however, from what I can tell, most people have minor annoyances as there really isn't a comprehensive list of 'recommended settings'. Additionally, there is a LOT of misinformation out there from people who don't really know what is going on - which is to be expected since there are really no experts yet
I'm REALLY hoping someone posts the Fi 5.1.1 so everyone could simply flash that to get on Fi 5.1.1.

Any idea where to get the Fi 5.1 factory image? I tried the one that you gave me about and the OTA that came in was LMY47Z and not LVY48C
skola28 said:
If I were in your shoes, I would probably get Fi 5.1, and wait for the update to Fi 5.1.1 OTA. I'm on vanilla 5.1.1 and using Project Fi and I have some minor annoyances too; however, from what I can tell, most people have minor annoyances as there really isn't a comprehensive list of 'recommended settings'. Additionally, there is a LOT of misinformation out there from people who don't really know what is going on - which is to be expected since there are really no experts yet
I'm REALLY hoping someone posts the Fi 5.1.1 so everyone could simply flash that to get on Fi 5.1.1.
Click to expand...
Click to collapse

mgerard said:
Any idea where to get the Fi 5.1 factory image? I tried the one that you gave me about and the OTA that came in was LMY47Z and not LVY48C
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...-fi-receiving-android-5-1-1-ota-build-lvy48c/

Thanks, I see why I was having a problem. My Nexus was purchased a few months ago and this update is only for Fi builds.
mademan420 said:
http://www.androidpolice.com/2015/0...-fi-receiving-android-5-1-1-ota-build-lvy48c/
Click to expand...
Click to collapse

mgerard said:
Thanks, I see why I was having a problem. My Nexus was purchased a few months ago and this update is only for Fi builds.
Click to expand...
Click to collapse
FI was working on Z build but C is the actual build. Supposed to help connectivity issues in some areas.

mademan420 said:
http://www.androidpolice.com/2015/0...-fi-receiving-android-5-1-1-ota-build-lvy48c/
Click to expand...
Click to collapse
That's not the Fi 5.1 factory image. Everyone has that OTA update.zip.
I bought my Nexus 6 direct from Motorola and I'm also trying to find a way to get onto the Fi build without much luck. There's a thread here with a LVY47H dump but it refuses to flash on my device even after I unlock the bootloader.

I never claimed it was. I was giving him insight about the factory image not being available yet according to the article.

Seems there is something different in the phones shipped for Fi and the ones we have. Hopefully someone wiill figure it out soon.
mademan420 said:
I never claimed it was. I was giving him insight about the factory image not being available yet according to the article.
Click to expand...
Click to collapse

In order to use the OTA to LVY48C you have to first be on LVY 47H (N6 shipped through Project Fi). I just found this LVY47H link through the G+ community forum. I will try it tonight after dinner. Feel free to be the first to try at your own risk.
motofirmware LVY47H

How did that flashing go, might I ask? How exactly did you do it? I downloaded that zip file you linked to from Moto's site, but it wasn't a zip I could flash from a custom recovery, nor does it appear to have the proper file structure to be flashed via fastboot either. Inside the zip file there are the usual suspects like recovery, and radio, but the system image is in chunks?

robroy90 said:
How did that flashing go, might I ask? How exactly did you do it? I downloaded that zip file you linked to from Moto's site, but it wasn't a zip I could flash from a custom recovery, nor does it appear to have the proper file structure to be flashed via fastboot either. Inside the zip file there are the usual suspects like recovery, and radio, but the system image is in chunks?
Click to expand...
Click to collapse
I was able to flash my LMY47Z (purchased direct from Motorola 11/2014) to LVY47H and then sideload to LVY48C. Everything works fine so far.
Here is what I did:
Consumed a couple of cold margueritas.
Assumptions: Proper drivers are installed, adb is installed, unlocked bootloader, relevant *.img files copied to your platform-tools folder.
1) adb reboot bootloader
2) fastboot flash bootloader bootloader.img
3) fastboot flash radio radio.img
4) fastboot reboot-bootloader
5) fastboot flash recovery recovery.img
6) fastboot flash boot boot.img
7) fastboot flash system system.img_sparsechunk.0
Repeat this for the remaining 6 "sparsechunks" (1-6)
Tip: press the arrow up key to bring up your last command and change the last number for each file.
8) fastboot flash cache cache.img
9) fastboot reboot-bootloader
10) press "START"
System should restart; "Android is upgrading" "Optimizing app # of ###"
Using adb sideloaded LVY48C OTA.
Note: to sideload LVY48C you need adb 1.0.32 or newer (my version was older).
Using Wugfresh's Root Toolkit v.2.0.5 successfully rooted my phone.
{
"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"
}

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?

[ROM][UNOFFICIAL][jd2019][9 Pie] LineageOS 16.0 for the Lenovo Z5s L78071

{
"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?

[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?

[ROM][RAV/SOFIA][11][UNOFFICIAL] PixelExperience (Plus) [AOSP]

{
"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"
}
PixelExperience for [RAV*/SOFIA*]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
Face unlock
Lights
Sound/vibration
Known issues
FM Radio
You tell me
Downloads
Link to Post
Installation
Link to Post
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 11
Security patch level: November 2021
Build author/Device Maintainer: AbsoluteZeroEdge
Kernel Source: https://github.com/S4muel007/kernel_motorola_trinket
Device Source: https://github.com/ph4n70m-404/device_motorola_sofiar
Vendor Source: https://github.com/ph4n70m-404/vendor_motorola_sofiar
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Contributors
Vache for initial device and vendor sources + TWRP
ph4n70m & Beetle84 for tons of building help
S4muel007 for kernel
Thanks awesome peeps
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2021-11-20
Last Updated 2021-11-21

Download Links
TWRP
TWRP - Credit to Vache
https://drive.google.com/file/d/1SwiiptkODqLTnDF1GRknYrF2g2yPxdJY/view
Pixel Experience
11/20/2021 Build - Initial Build
https://drive.google.com/drive/folders/1pdStP6Rnph19wIu_plpDwjRa124yJvNK?usp=sharing
11/21/2021 Build - Added Moto Camera 2
https://drive.google.com/drive/folders/1dSnZUiuK5TlOEtZU8oQIbjjV-TxJgFyr?usp=sharing

Installation
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
FastbootD
1) Extract rom zip and open cmd prompt in the extracted folder
2) Reboot into fastbootd
Code:
fastboot reboot fastboot
3) Flash images
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
4) Format data
Code:
fastboot -w
5) Reboot, profit.
TWRP
1) Boot to bootloader
2) Flash TWRP (included download above)
Code:
fastboot flash recovery_a twrpfile.img
fastboot flash recovery_b twrpfile.img
3) Flash the rom
4) Format Data (not factory reset)
5) Reboot, Profit
5.1) (Optional) If magisk is desired flash it in TWRP after first boot

Reserved

I would like to try this but I have a question:
Is this rom for sofia or sofiar? The title of the post says sofia but the download link says sofiar.
which is it? I have the U.S. retail version of the Moto G Power, which is sofia.

classic757 said:
I would like to try this but I have a question:
Is this rom for sofia or sofiar? The title of the post says sofia but the download link says sofiar.
which is it? I have the U.S. retail version of the Moto G Power, which is sofia.
Click to expand...
Click to collapse
Yes it should work,
In the title it shows rav*/sofia* for wildcards meaning any rav*, or sofia* device

AbsoluteZeroEdge said:
Yes it should work,
In the title it shows rav*/sofia* for wildcards meaning any rav*, or sofia* device
Click to expand...
Click to collapse
Okay thank you. If I give it a try I will let you know how it goes.

I originally installed Beetle84's Havoc Rom, which he/she no longer supports, on my Moto G Power 2020 XT2041-4 using FlashbootD, but, soon, my battery life diminished until it barely lasted a day. So, I tried to flash the new Lineage 18.1, but it failed and I had to Rescue my device. It's now running the stock Android 11 (A!11) Rom. Other Cooks have suggested that I can't flash another Rom until I downgrade the device to A10, which I haven't been able to do. I wanted to try Vache's Moto Flash Tool, but I can't find instructions online. Do I have to downgrade to A10 to flash this Rom? If not, can I just follow the above instructions which are similar to Beetle84's instructions I successfully followed when I flashed his Havoc A11 Rom? Also, how does this Rom compare to Havoc?
Thanks

jhford said:
I originally installed Beetle84's Havoc Rom, which he/she no longer supports, on my Moto G Power 2020 XT2041-4 using FlashbootD, but, soon, my battery life diminished until it barely lasted a day. So, I tried to flash the new Lineage 18.1, but it failed and I had to Rescue my device. It's now running the stock Android 11 (A!11) Rom. Other Cooks have suggested that I can't flash another Rom until I downgrade the device to A10, which I haven't been able to do. I wanted to try Vache's Moto Flash Tool, but I can't find instructions online. Do I have to downgrade to A10 to flash this Rom? If not, can I just follow the above instructions which are similar to Beetle84's instructions I successfully followed when I flashed his Havoc A11 Rom? Also, how does this Rom compare to Havoc?
Thanks
Click to expand...
Click to collapse
unfortunately yes you have to downgrade to a10 for the rom to boot
for downgrade instructions it's rather self explanatory. just drop ur stock 10 firmware zip in the firmware folder and start the flash
after u downgraded just use the installation guide above
And for how it compares, Not sure. It's basically AOSP but with google apps, It's like havoc but more bare and made for pixel fans that want the pure pixel experience
if u want more features I would definitely point u towards ph4n70m's havoc build

AbsoluteZeroEdge said:
unfortunately yes you have to downgrade to a10 for the rom to boot
for downgrade instructions it's rather self explanatory. just drop ur stock 10 firmware zip in the firmware folder and start the flash
after u downgraded just use the installation guide above
And for how it compares, Not sure. It's basically AOSP but with google apps, It's like havoc but more bare and made for pixel fans that want the pure pixel experience
if u want more features I would definitely point u towards ph4n70m's havoc build
Click to expand...
Click to collapse
Thank you, but I don't understand this: "just drop ur stock 10 firmware zip in the firmware folder and start the flash." So, can you please give me specific downgrade instructions. I've tried and failed at least 6 times.

jhford said:
Thank you, but I don't understand this: "just drop ur stock 10 firmware zip in the firmware folder and start the flash." So, can you please give me specific downgrade instructions. I've tried and failed at least 6 times.
Click to expand...
Click to collapse
Well, in moto flash tool's root directory it has a firmware folder to place your device's stock firmware for it to flash, after that is done open up the tool and select the stock 10 package u placed

AbsoluteZeroEdge said:
Well, in moto flash tool's root directory it has a firmware folder to place your device's stock firmware for it to flash, after that is done open up the tool and select the stock 10 package u placed
Click to expand...
Click to collapse
I have done that both zipped and unzipped several times and it has always failed. Maybe I downloaded the wrong firmware. I got it from lolinet. Do you have a link for the correct A10 firmware for Moto G Power 2020 XT2041-4?
BTW, since I'm now stock A11, I used Nova Launcher v6.x - new.version 7.x is incompatible with many of my widgets - today.to make the UI look identical to my rooted and rommed Nexus 7 2013 deb tablets, and it's pretty livable. Plus, Android Auto now works perfectly and never did when the phone was rooted and rommed. Food for thought.
[Edit] I flashed Vache's TWRP. I'd be pretty happy if I could make a Nandroid backup of my current stock setup. Have you done that?
Thanks again

jhford said:
I have done that both zipped and unzipped several times and it has always failed. Maybe I downloaded the wrong firmware. I got it from lolinet. Do you have a link for the correct A10 firmware for Moto G Power 2020 XT2041-4?
BTW, since I'm now stock A11, I used Nova Launcher v6.x - new.version 7.x is incompatible with many of my widgets - today.to make the UI look identical to my rooted and rommed Nexus 7 2013 deb tablets, and it's pretty livable. Plus, Android Auto now works perfectly and never did when the phone was rooted and rommed. Food for thought.
[Edit] I flashed Vache's TWRP. I'd be pretty happy if I could make a Nandroid backup of my current stock setup. Have you done that?
Thanks again
Click to expand...
Click to collapse
What's Moto Flash Tool's output? And I can't really decide the correct firmware for you phone, u need to see what software channel your phone is and select it here: https://mirrors.lolinet.com/firmware/motorola/sofia/official/
for nandroid backup well I'm not really sure, haven't done one before. a quick google search should do something for you.

AbsoluteZeroEdge said:
What's Moto Flash Tool's output? And I can't really decide the correct firmware for you phone, u need to see what software channel your phone is and select it here: https://mirrors.lolinet.com/firmware/motorola/sofia/official/
for nandroid backup well I'm not really sure, haven't done one before. a quick google search should do something for you.
Click to expand...
Click to collapse
Here's how I used Moto Flash Tool (MFT). Pasted A10 firmware in firmware folder. Connected phone in bootloader mode. Double clicked the MFT exe. A blank DOS window popped up and disappeared. That's it.

jhford said:
Here's how I used Moto Flash Tool (MFT). Pasted A10 firmware in firmware folder. Connected phone in bootloader mode. Double clicked the MFT exe. A blank DOS window popped up and disappeared. That's it.
Click to expand...
Click to collapse
make sure it's in a path with no spaces, i recommend putting it in a folder with of course no spaces again on any drive's root

AbsoluteZeroEdge said:
make sure it's in a path with no spaces, i recommend putting it in a folder with of course no spaces again on any drive's root
Click to expand...
Click to collapse
I followed you suggestion and only moved the folder to the root of C:\ that hosts the exe and the firmware, etc. folders. I double clicked the exe and for the first time, a usable batch file DOS window opened. So, it appears that I have a working setup. However, I'm going to think about rooting/romming this phone again, because I don't want to lose Android Auto (AA) again. But AA only works with a USB wired connection in my car, and I ordered an AAWireless device which should obviate the wired connection and allow my rooted/rommed phone to connect. I'll test it, and, if so, I'll flash your Rom Immediately.
Thanks for putting up with me.

I flashed this rom to my retail Moto G Power (2020) that was purchased from Google Fi. I make it to the Google logo screen on boot and it just sits there with the progress bar perpetually scrolling. Any advice?

NobleX13 said:
I flashed this rom to my retail Moto G Power (2020) that was purchased from Google Fi. I make it to the Google logo screen on boot and it just sits there with the progress bar perpetually scrolling. Any advice?
Click to expand...
Click to collapse
First boot usually takes a while, if it hasn't booted within 10 minutes it's stuck. Make sure you did a Format and not only a Wipe as well

Thanks. Upon further inspection when I executed a fastboot -w it wiped the data partition but did not format it. I'll try this again as time permits.
AbsoluteZeroEdge said:
First boot usually takes a while, if it hasn't booted within 10 minutes it's stuck. Make sure you did a Format and not only a Wipe as well
Click to expand...
Click to collapse

NobleX13 said:
Thanks. Upon further inspection when I executed a fastboot -w it wiped the data partition but did not format it. I'll try this again as time permits.
Click to expand...
Click to collapse
Yeah, fastboot -w usually has problems. Good luck!

Database Develop

welcome