Related
Hey everyone, this is a carryover post from the LG G7 Reddit. As of now, there are a number of people out there with US model firmware flashed phones that don't allow updating via normal methods (most commonly PM/Sprint phone flashed with ULM/Unlocked firmware). The only way for these users to update their phone is to flash an updated kdz with LGUP's refurbish option, which causes the phone to be wiped (while it's possible to backup most elements of the phone, it'd be ideal if a normal FOTA update could be obtained and executed on these devices). I used to own one of these phones, before obtaining a factory ULM version. The phone I bought was running the October (10g) update so I was hoping I could just capture the 10i update and share that to users that needed an alternative way to upgrade with the FOTA update.
However, LG apparently has their phone updates in a cumulative/rolled up package (in this case, my phone downloaded this 522MB file when updating, even though I'm sure only a small portion was ultimately needed). When opened with a program like 7-Zip, only one, much smaller file is shown (I don't know if this is actually a kdz file or something similar since 7-Zip is unable to correctly read the header/contents). This could very well be the same file one would download if using LG Bridge (although the PM/Sprint model => ULM/Unlocked converted phones are not detected by that program). I've only worked with HTC/Samsung/Nexus+Pixel-branded phones in the past, so I know little to nothing about LG's packaging and update methodology. Any assistance in creating (or explaining how one might go about creating) a FOTA file that could be sideloaded or flashed with LGUP would be amazing. Cheers!
Hello, updating with lgup doesn't need to be with the refurbish option. There is an update option witch keeps data.
Usually other kdz models can't be flashed on other models (but certainly possible). That also goes for update files.
FOTA updates can't be extracted with simply opening it with a 7zip. Btw how did you get the link to that update?
LameMonster82 said:
Hello, updating with lgup doesn't need to be with the refurbish option. There is an update option witch keeps data.
Usually other kdz models can't be flashed on other models (but certainly possible). That also goes for update files.
FOTA updates can't be extracted with simply opening it with a 7zip. Btw how did you get the link to that update?
Click to expand...
Click to collapse
Thanks for confirming the information about using the update option. Another XDA user, tycrek, was able to do the same with the aid of a modified dll file (which seems to be a requirement for getting official apps to recognize modified phones; LGUP Dualmode is nice too, even if you don't need to touch the dev side). I'm unsure what type of modifications their phone had from stock though (if any).
The used market is flooded with a lot of G7 phones that were originally Sprint models that have had the unlocked/Google Fi firmware flashed to them (there is an active thread here about the subject; one of the most prolific sellers of these phones is even actively posting replies). If anyone is unsure, go to the phone's Hardware Info in the Settings. If the model is LM-G710ULM but the S/N is blank, then it's likely one of these phones. OTA Updates as well as using Google Pay are both unavailable to these phones as well (flashing the Verizon firmware to the phone can supposedly fix both of these issues, however, I didn't know about this at the time and so I couldn't test it before getting a replacement).
As far as my use of 7-Zip, I was hoping that the file was, in reality, a zip file that just had its extension removed, but obviously, that's not the case =). I still want to figure out the format of this file and extract the contents from it (I'm just waiting for some free time to appear!) As far as obtaining the link, I was fortunate, in that my phone was due for an update that had already been released. Using the 1st method in this tutorial, I was able to capture the URL that my phone was updating from (LG seems to be making use of Limelight Network's CDN to give users faster downloads... I'm sure other files are being hosted as well, but I'm not sure how they could be located aside from trying to find a pattern in the naming scheme).
Anyone get the final official build of Android Q? Today, supposedly, is the day for the update to begin rolling out. Post here with your results!
Status: Running 10 now!
It's too early, its 7:40am in California now, I wouldn't expect it before 5pm...
If the update is released today, it is typically done between 9am and noon Pacific Time... I usually get it around 11am Central Time. That said, this is the "Monday" after a holiday in the US, so it could potentially be later in the day.
We will usually see the factory images appear first, and OTA updates available anywhere from a few minutes to as much as a few days later...
I take all this news of the update coming today with a grain of salt. Keep an eye on the Android Developer blog for more information: https://android-developers.googleblog.com
calinorg said:
It's too early, its 7:40am in California now, I wouldn't expect it before 5pm...
Click to expand...
Click to collapse
I realize that it's early in the day, I was just being preemptive ??
Full and ota images are posted on Android developers site, so ota should be there pretty soon...
Android images are available now, expect OTA's to happen soon... The full release announcement is available at https://android-developers.googleblog.com/
Have fun mashing the Check Update button.
EDIT: Oops, looks like @calinorg beat me to the punch on this one.
There are two Android 10 OTA files for the Pixel 3A XL. One ends in 19 and the other 20. How do you determine which one to download? Does it matter?
eddieb187 said:
There are two Android 10 OTA files for the Pixel 3A XL. One ends in 19 and the other 20. How do you determine which one to download? Does it matter?
Click to expand...
Click to collapse
As there is only one hardware platform, you would want to use the latest one, in this case 20... Remember to use the OTA image though and not the "factory" one. The factory one will wipe your device clean, the OTA image will not.
OTA images are available here: https://developers.google.com/android/ota
Make sure you understand how they are installed using 'adb sideload' method.
FYI... If you chose to update via the OTA file using 'adb sideload' the first boot takes about 10 minutes. Don't panic and just let it do it's thing. Even once it's "up and working" it still takes a while, be patient. Several other things will be updated as well, like Play Store libraries. I also had several app updates available after the upgrade.
Whole process start to finish after downloading the OTA zip file was about 20 minutes.
acejavelin said:
FYI... If you chose to update via the OTA file using 'adb sideload' the first boot takes about 10 minutes. Don't panic and just let it do it's thing. Even once it's "up and working" it still takes a while, be patient. Several other things will be updated as well, like Play Store libraries. I also had several app updates available after the upgrade.
Whole process start to finish after downloading the OTA zip file was about 20 minutes.
Click to expand...
Click to collapse
Thanks again acejavelin for all the info. I have been flashing the OTA security updates for some time now. I'd rather sideload then have to wait for OTA. I noticed two files sometimes in the past with my Nexus phones. All the monthly security patches for the pixel 3a xl so far have just one download file. I was just wondering why Google would upload two?
eddieb187 said:
Thanks again acejavelin for all the info. I have been flashing the OTA security updates for some time now. I'd rather sideload then have to wait for OTA. I noticed two files sometimes in the past with my Nexus phones. All the monthly security patches for the pixel 3a xl so far have just one download file. I was just wondering why Google would upload two?
Click to expand...
Click to collapse
I don't know... But the 20 image worked perfectly for me.
Downloading it now, 1.18 GB, was previously on Pie.
Sent from my Pixel 3a XL using Tapatalk
Just got the notification and downloading now!
OTA from Beta 6 is only 40.7MB. Guess there weren't many changes from the beta.
Anyone get the live caption feature working? I'm trying to figure out how to get it working
Do we have to be on the Magisk Canary channel to patch the boot.img file to retain root or is the Stable Channel good for Android 10?
Thanks
Pretty sure TWRP still isnt working on Android 10 so patched boot is the way to go. I suppose you could try sideloading magisk zip as well but I just used the patched boot option and it worked perfectly.
ctfrommn said:
Pretty sure TWRP still isnt working on Android 10 so patched boot is the way to go. I suppose you could try sideloading magisk zip as well but I just used the patched boot option and it worked perfectly.
Click to expand...
Click to collapse
Thanks! Did you patch the boot.img using the Magisk Stable Channel?
Just installed mine.. What's the difference? I do not see anything yet that stands out..
champ784 said:
Anyone get the live caption feature working? I'm trying to figure out how to get it working
Click to expand...
Click to collapse
I seem to remember reading somewhere that it wouldn't be active with the initial release.
Sent from my Pixel 3a XL using Tapatalk
Hi guys. I got a G8 from a friend whose friend's dad is a radio tower engineer for AT&T that got this phone early. It's a prerelease phone (says "not for sale") on the back, and it comes with software that is seemingly far behind what shipped with the public version of the device. It's Android 9 with the December 2018 security patch, SW version G820UM04b. This version is pretty buggy and doesn't have some features like air motion. It seems like the initial software release for the public phone was G820UM10g.
Whenever I try updating the device, it just says the software is already up to date. I've done more factory resets and tried more tricks than I can even recount. Got a fresh new SIM card. Called AT&T and got them to manually push the update to my IMEI (which is correctly registered), waited a day for the update. Tried LG Bridge but it's incompatible with AT&T devices. Looked for kdz files online for the AT&T version that I can flash using LGUP, but there's no AT&T files available (pls tell me if anyone knows of any out there).
I'm at my wit's end guys. Anyone have any ideas as to how I can get this phone updated? I'm realizing that I really took the ability to just unlock and flash my old OnePlus for granted
Where do you live ?
Mobile AT&T only support to update OTA if you live in US !
minhthien0711 said:
Where do you live ?
Mobile AT&T only support to update OTA if you live in US !
Click to expand...
Click to collapse
Sorry, forgot to clarify that. I live in the USA and I use AT&T.
On the face of it it's not looking good. There aren't any KDZs for ATT as standard, and you can't update OTA - one thing to check here is the S/N field, pre-production LG phones are usually missing this, which is usually why OTAs don't work.
However, pre-production devices can, sometimes, be cross-flashed. You could try using LGUP to flash a more recent US unlocked build. It is likely to give you the IMPL lock / mismatch / crossflashing not allowed error, but it's worth a shot.
If that doesn't work, your best bet will be to ask your friend's dad to take it in to work (when he can...) for whoever looks after devices for his team to flash it to production as a favour.
Folks with the Google purchased unlocked version....did you get the update? I have not so far. I know I can side load it but I am curious if it is just me.
Nothing for me. I'm curious tho, I had to sideload the Nov update to get the Verizon build. So now I'm waiting to see if the OTA will come for Dec.
Nothing for me either. If I wanted to sideload the OTA, would I get the one for US carriers? I don't see a Verizon specific one this time around.
Frankie1588 said:
Nothing for me either. If I wanted to sideload the OTA, would I get the one for US carriers? I don't see a Verizon specific one this time around.
Click to expand...
Click to collapse
My question exactly. I'm wondering if they are now doing away with the Verizon specific builds and keeping it standard across all US carriers. Same situation here and no update yet.
I haven't received the update yet either. I've got the files downloaded and ready but I'm gonna wait a little bit to see what happens.
I believe the .a1 update is for Canada, correct me if I'm wrong
bizdiddy said:
My question exactly. I'm wondering if they are now doing away with the Verizon specific builds and keeping it standard across all US carriers. Same situation here and no update yet.
Click to expand...
Click to collapse
I sideloaded the US carrier OTA to both mine and my wife's Verizon P6Ps with no issues.
spotmark said:
I sideloaded the US carrier OTA to both mine and my wife's Verizon P6Ps with no issues.
Click to expand...
Click to collapse
Just to confirm, yours are the unlocked variant from Google right? Thanks!
Frankie1588 said:
Just to confirm, yours are the unlocked variant from Google right? Thanks!
Click to expand...
Click to collapse
No, they are both bootloader locked Verizon variants.
Edit - My apologies. I didn't notice that you were asking about unlocked models.
At this point I've seen no evidence that anyone in the US on Verizon has had the update properly pushed OTA to their phone.
I miss the days when the "Check for Update" button worked and would actually pull the update.
jimistixx said:
At this point I've seen no evidence that anyone in the US on Verizon has had the update properly pushed OTA to their phone.
I miss the days when the "Check for Update" button worked and would actually pull the update.
Click to expand...
Click to collapse
Yup. I never got any OTAs since day 1 on mine. Had no issues with this with my 2 XL or 5.
I'm using unlocked on Verizon and had to sideload the US update. So far the phone is a lot more stable and reception seems to be slightly better.
Guyinlaca said:
I'm using unlocked on Verizon and had to sideload the US update. So far the phone is a lot more stable and reception seems to be slightly better.
Click to expand...
Click to collapse
Thanks! Going to sideload now.
Lets light up the Google forum a bit. There is already a thread on it so please add your experience. There is something missing between Google and Verizon.
Pixel 6 Pro not getting December update - Google Pixel Community
support.google.com
bizdiddy said:
My question exactly. I'm wondering if they are now doing away with the Verizon specific builds and keeping it standard across all US carriers. Same situation here and no update yet.
Click to expand...
Click to collapse
They always work towards having one US version. If you look at the history of the other phones on the factory image page you will see where they split apart but often come back together in a month or two.
So as we sideload we load the US version.
I have a pixel 6 pro unlocked purchased from Google and haven't received the update. I hate to ask but can someone point me in the right direction to side load the update. I've never side loaded an update and could use the assist. Thank you all in advance
jughead75 said:
I have a pixel 6 pro unlocked purchased from Google and haven't received the update. I hate to ask but can someone point me in the right direction to side load the update. I've never side loaded an update and could use the assist. Thank you all in advance
Click to expand...
Click to collapse
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
There are full instructions at the link above but let me give you cliff notes.
Download the platform tools to your computer so you have ADB.
Download the CORRECT OTA image from the link above and copy the zip to the platform tools folder. Do not extract it, leave it as a zip.
Connect your phone to your computer with USB Debugging turned on in Developer Options.
Reboot into recovery then issue the adb command to load the OTA file.
TonikJDK said:
Lets light up the Google forum a bit. There is already a thread on it so please add your experience. There is something missing between Google and Verizon.
Pixel 6 Pro not getting December update - Google Pixel Community
support.google.com
Click to expand...
Click to collapse
They don't even have the update on their software update page yet. The 11/16 update states it is October patch level. Lame. No wonder no one is getting it. There is zero reason to wait for a Verizon OTA any longer. I have the Google version unlocked on Verizon and flashed the US December build.
Google Pixel 6 Software Update | Verizon Customer Support
Get instructions on downloading the latest software update for performance improvements to your Pixel 6, including current Android security patches.
www.verizon.com
TonikJDK said:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
There are full instructions at the link above but let me give you cliff notes.
Download the platform tools to your computer so you have ADB.
Download the CORRECT OTA image from the link above and copy the zip to the platform tools folder. Do not extract it, leave it as a zip.
Connect your phone to your computer with USB Debugging turned on in Developer Options.
Reboot into recovery then issue the adb command to load the OTA file.
Click to expand...
Click to collapse
Thank you! I appreciate the help
Bumping this with a title change. Just learned my kids unlocked has not updated. He is on ATT.
So wondering if other carriers have the same issue.
I got impatient and sideloaded the OTA for my unlocked P6P on Verizon's network. I used the .017 OTA image and all went smoothly.
Title says it all, is there a non root way to hurry up the update? I haven't had the popup to update android and was hoping there's a way to check for updates
Settings/system I believe, to check for updates or you can download and sideload the update.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.
Sideload the OTA
NippleSauce said:
Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.
Click to expand...
Click to collapse
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.
pcriz said:
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.
Click to expand...
Click to collapse
You're pretty much correct here. I suppose that Google was a bad example to use. But essentially, the carrier builds allow the applicable carrier to also push apks through when you pull the update OTA. They're not necessarily packaged within the factory image - so I had some horrible word choices in my initial post as they don't really modify the image lmao. But (when looking at the older builds) if you just install the stock build instead of flashing one of the carrier builds, then you won't have to worry about any carrier apps being pulled in along with your OTA update.
But heck, if you're rooted and want to maintain root (and are thus manually updating whilst having OTA disabled), then you wouldn't have to worry about this at all, haha.
Samsung phones were a better example of this, as whenever I would do an OTA update on my S21U, it would also install around 4-5 T-Mobile bloatware apps. But if you manually installed the stock image, that wouldn't happen anymore when updating OTA.