Database Info

[Q] Moto G XT1028 (U.S Verizon) Lollipop

Hello, has anybody that owns a Moto G XT1028 (U.S Verizon) gotten the Android Lollipop update yet? I'm in need to know becuase i want to purchase a Moto G for Dev purposes but i would like it to be running Android Lollipop after purchase and checking for system updates. Btw im purchasing it 06/22/15. Please post screenshots if you have them.
If you do own one that has Lollipop could you please make a quick review, including the following topics.
- Battery life
- Preformance
- Any bugs
I would greatly appreciate it.

I was wondering the same thing ... I own a Moto G XT1028 (Verizon) but im still on Android 4.4.4 KitKat. I constiently check for updates almost daily. If i don't recieve the Android Lollipop update within the next 14 days, I'm: rooting, unlocking the botloader, installing a custom recovery and putting Cm12 on it. I originally didn't want to do that for warranty and safety reasons but i feel the need to have Lollipop. The update is way over due ...

There is no Lollipop firmware for the XT1028.
Sent from my XT1031

Motorola states "This device will be upgraded to the Android 5 Lollipop release of Android, pending partner support." here: https://motorola-global-portal.custhelp.com/app/software-upgrade-news/g_id/1949

motoinspri said:
I was wondering the same thing ... I own a Moto G XT1028 (Verizon) but im still on Android 4.4.4 KitKat. I constiently check for updates almost daily. If i don't recieve the Android Lollipop update within the next 14 days, I'm: rooting, unlocking the botloader, installing a custom recovery and putting Cm12 on it. I originally didn't want to do that for warranty and safety reasons but i feel the need to have Lollipop. The update is way over due ...
Click to expand...
Click to collapse
You can't root anyhow, unfortunately

aoleg said:
Motorola states "This device will be upgraded to the Android 5 Lollipop release of Android, pending partner support." here: https://motorola-global-portal.custhelp.com/app/software-upgrade-news/g_id/1949
Click to expand...
Click to collapse
Motorola has been saying that since Lollipop came out in November of last year. I wouldn't hold my breath waiting for it if I were you.
---------- Post added at 03:53 PM ---------- Previous post was at 03:38 PM ----------
motoinspri said:
I was wondering the same thing ... I own a Moto G XT1028 (Verizon) but im still on Android 4.4.4 KitKat. I constiently check for updates almost daily. If i don't recieve the Android Lollipop update within the next 14 days, I'm: rooting, unlocking the botloader, installing a custom recovery and putting Cm12 on it. I originally didn't want to do that for warranty and safety reasons but i feel the need to have Lollipop. The update is way over due ...
Click to expand...
Click to collapse
I rooted my xt1028 over a year ago after paying a "chinese middleman" $45 for a bootloader unlock code. Since then I have installed soooooooooo many roms, first Kitkat and then Lollipop. I must say that imo stock 4.4.4 Kitkat is better than anything else you can install on the xt1028. Every rom out there has one bug or another and even though you can do more customization with non-stock roms, it seems to be at the expense of better performance and battery life with stock. As for lollipop, I ran a lot of lollipop roms and I do not like it. Too many kiddie colors and childish building block icons. Google acts as if they are making their operating system for a bunch of kindergartners.
Oh, and other than paying someone for an unlock code, you can forget rooting the xt1028 or unlocking its' bootloader because Verizon has the phone on total lockdown.

Verizon can have my x1028 junk ass phone and I am going to get something else and straightalk..

still holding out hope that Verizon will push out an update. they just updated the first gen Moto X to Lollipop, so perhaps the Moto G is next in line...

How you unlock the bootloader in the xt1028,I can't unlocked, funking verizon
motoinspri said:
I was wondering the same thing ... I own a Moto G XT1028 (Verizon) but im still on Android 4.4.4 KitKat. I constiently check for updates almost daily. If i don't recieve the Android Lollipop update within the next 14 days, I'm: rooting, unlocking the botloader, installing a custom recovery and putting Cm12 on it. I originally didn't want to do that for warranty and safety reasons but i feel the need to have Lollipop. The update is way over due ...
Click to expand...
Click to collapse
.
..

we stayed last

XT1028 lollipop is out!

alcuin said:
XT1028 lollipop is out!
Click to expand...
Click to collapse
Unfortunately, my wife is in a quite sticky situation. Verizon locked the device so it can't be activated, but that's not really the problem... We can't figure out how to bypass the Setup Guide (all the old ways are now patched). Can't use it until that's figured out.

alcuin said:
XT1028 lollipop is out!
Click to expand...
Click to collapse
I confirm my XT1028, also adopted the Android 5.1

Just got mine. Maybe the root community can crack this one. Maybe a better chance on rooting this version.

The same here
DamianHelixTV said:
Unfortunately, my wife is in a quite sticky situation. Verizon locked the device so it can't be activated, but that's not really the problem... We can't figure out how to bypass the Setup Guide (all the old ways are now patched). Can't use it until that's figured out.
Click to expand...
Click to collapse
I have the same problem, this has a solution?

deathkryz said:
I have the same problem, this has a solution?
Click to expand...
Click to collapse
I hope the wonderful Android community does what I think it'll do and figure out a bypass to the new Lollipop Setup Wizard.

DamianHelixTV said:
I hope the wonderful Android community does what I think it'll do and figure out a bypass to the new Lollipop Setup Wizard.
Click to expand...
Click to collapse
Hoping for a solution as well, as I only use the device on WiFi.
I suppose I'll hold off on installing the update, for now.

can anyone with a bootloader unlocked XT1028 pull the 5.1 partitions and post them? or has anyone seen the stock partitions for 5.1 anywhere?
as for those stuck at the setup guide... was data wiped causing you to have to set the device up? or does it force the setup guide either way?
hopefully someone can post the images so I can get my device out of fastboot mode and poke around

autoprime said:
can anyone with a bootloader unlocked XT1028 pull the 5.1 partitions and post them? or has anyone seen the stock partitions for 5.1 anywhere?
as for those stuck at the setup guide... was data wiped causing you to have to set the device up? or does it force the setup guide either way?
hopefully someone can post the images so I can get my device out of fastboot mode and poke around
Click to expand...
Click to collapse
There's someone reporting on Reddit that he got past it by deleting the cache repeatedly in recovery mode. I might go ahead and update, just for the heck of it.
http://www.reddit.com/r/motog/comme..._update_notification_on_xt1028verizon/cx03pe5
UPDATE: I updated, and everything works great! I didn't have to set up the device, it just carried over everything with the new look. I have no idea why anyone would be stuck at the activation screen, when I didn't even have to set it up again...weird

autoprime said:
can anyone with a bootloader unlocked XT1028 pull the 5.1 partitions and post them? or has anyone seen the stock partitions for 5.1 anywhere?
as for those stuck at the setup guide... was data wiped causing you to have to set the device up? or does it force the setup guide either way?
hopefully someone can post the images so I can get my device out of fastboot mode and poke around
Click to expand...
Click to collapse
The reason I'm stuck at Setup is because after the update we factory reset (it updated just fine, just wanted a 'fresh' start)
---------- Post added at 06:37 AM ---------- Previous post was at 06:28 AM ----------
Belac77 said:
There's someone reporting on Reddit that he got past it by deleting the cache repeatedly in recovery mode. I might go ahead and update, just for the heck of it.
UPDATE: I updated, and everything works great! I didn't have to set up the device, it just carried over everything with the new look. I have no idea why anyone would be stuck at the activation screen, when I didn't even have to set it up again...weird
Click to expand...
Click to collapse
Thank you! Will test NOW. Well if I can ever get the recovery menu to show up.

Converting Verizon Pixel to Google Store Version

I recently bought a verizon Pixel and have already unlocked the bootloader and flashed a stock image NDE63V that comes directly from google. I'm using it on T-Mobile. If I relock the bootloader at this point will everything be ok? I've read something about people saying it would brick the phone if you relock after flashing unsigned code, but the official stock images from google are signed. Will I get official updates for the unlocked google store version of the Pixel?
-edit- I decided to live dangerously, re-locked the bootloader, and now I have a completely stock google store pixel

My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app

brainymd said:
My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't think anyone knows. Right now I flashed stock google ROM through fastboot which replaced bootloader image, I am using it with T-Mobile, and I relocked bootloader. I'm going to assume it would get stock google updates.

I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.

mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
I also have a Verizon version. Is there an advantage to flashing the Google version of updates as opposed to Verizon? For the moment I have an unlocked bootloader with TWRP and SuperSU installed. I tried installing an OTA update and it failed.
If I want to install one of the image updates posted (such as NDE63X from Verizon available right now) do I need to run the "flash-all" script? Could I just flash system or something else? Or should I expect it to overwrite my custom recovery and I'll have to restore that?

As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.

mruno said:
As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.
Click to expand...
Click to collapse
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.

mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.

ohioDroid said:
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.
Click to expand...
Click to collapse
If the gestures were not in that update, they should be soon in an upcoming OTA according to reports. I am currently using the double-tap gesture with the ElementalX kernel (enabled within its app).
Edit: I think this app can enable lift to wake. I bookmarked it after finding a post about it here until I read Google will be adding this feature soon.
fink.nottle said:
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.
Click to expand...
Click to collapse
I am not sure as I haven't had a nexus device since the Samsung Galaxy Nexus on Verizon .

On a lot of their devices Verizon likes to update bootloaders to only accept new updates. It's likely that if they patch out the ability to use dePixel8 in a future update, they will prevent people from flashing older builds. C'Est la Vie I guess

Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?

Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?

aholeinthewor1d said:
Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?
Click to expand...
Click to collapse
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
tobalaz said:
Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?
Click to expand...
Click to collapse
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.

jmartin72 said:
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.
Click to expand...
Click to collapse
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc

aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I bought my Verizon Pixel yesterday. Unlocked in 20 seconds and within a few minutes TWRP 3.0.2-0 for sailfish is installed and SuperSU 2.78-SR5 has been flashed. Works perfect.

aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I feel your pain! I'm also coming from the S5 for 2.5 years. Had everything (almost) perfect with systemless root, twrp, xposed, adaway, etc. (but no Android Pay) . Now with this Pixel and Verizon-depixel8 unlocked bootloader, I'm trying to piece together the best plan for having the most stuff working.
So far, bootloader unlocked, and I flashed the full 7.1.1 images from Google. Then I tried using the setup wizard and it brought over my account info and wifi passwords and such from my S5 by directly connecting the phones, and it downloaded my apps from google play, but I need app-data.
So, now I'm thinking this would be the process if you want to have a rooted pixel, and be able to reboot into a "clean" boot for Android Pay?:
1) boot TWRP alpha2 (since RC1 having problem rooting?)
2) install TWRP alpha2 zip
3) install stock-safetynet kernal to boot_a
4) boot into boot_a
5) setup Android pay, add credit cards, etc.
6) boot into TWRP and install root with SR5 to boot_b
7) boot into boot_b and restore other app backups with Titanium Backup, install Adaway/hosts
8) no Xprivacy /Xposed available yet, right?
9) restore backed up apps from old phone with Titanium Backup (from cloud, etc.)

I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app

bobhinkle said:
I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes you can still use it on Verizon. Advanced Calling is a feature i am not too familiar with. Is that HD Calling? If so then yes that will work as well works on my phone without issue.

So from here I can flash Google's bootloader and Google image and then when updates come out just use the Google ones
Sent from my Pixel using XDA-Developers mobile app

Question for those with a Play store version of the Pixel: what is your bootloader version on the 7.1.1 software?
For reference my Verizon store Pixel has BL version 8996-12001-1610061102.
Thanks in advance!

OTA Update to Oreo

Hey guys... Does anyone know when I should expect my update to Oreo OTA. I don't plan on becoming a beta tester or flashing it myself.
So if anyone has an idea of when Oreo will be pushed out to the masses, I'd appreciate it!
Thanks!

connorhiller said:
Hey guys... Does anyone know when I should expect my update to Oreo OTA. I don't plan on becoming a beta tester or flashing it myself.
So if anyone has an idea of when Oreo will be pushed out to the masses, I'd appreciate it!
Thanks!
Click to expand...
Click to collapse
I'm in the same boat. No one knows yet. There are not even factory images available nor full OTA images on the google site here.
https://developers.google.com/android/images
Until such time as they appear don't sweat it. After they do then you can re-ask your question but you'll probably get it before you can hit send. Someone said they got an OTA on Verizon from 7.1.2 to 8.0 but I'm a little leery of that claim since no one else I've seen has received it.
I believe it was destined for the Aug 21 deadline but some major problems have arisen and I believe it was pulled for further testing. Bluetooth is one of them, random rebooting, stuff like was on some dp4 devices. I also saw some volume control issues too. Yes, I know others haven't had issues and someone will post a link to the factory images on the android site but that doesn't help any of us with locked bootloaders. Besides the fact that I like the background install and being able to use the phone while it's updating. Then a simple reboot and you're done. It'll happen soon but no one knows when yet.

I am in UK and I have already received for Oreo OTA on Google Pixel set.
It can be flashfire updated as well for root purpose.

sitnaing said:
I am in UK and I have already received for Oreo OTA on Google Pixel set.
It can be flashfire updated as well for root purpose.
Click to expand...
Click to collapse
So you were on stock 7.1.2, locked bootloader, not rooted and you received an OTA to 8.0? I'm not sure what you mean by flashfire updated. An OTA installs in the background.

bobby janow said:
So you were on stock 7.1.2, locked bootloader, not rooted and you received an OTA to 8.0? I'm not sure what you mean by flashfire updated. An OTA installs in the background.
Click to expand...
Click to collapse
I am on 7.1.2 unlock bootloader with root.
You should also have received ota update if you are on locked bootloader with no root.
Some of ota roll out dependent on carrier. But if yours is google set, you would be able to receive by now.

sitnaing said:
I am on 7.1.2 unlock bootloader with root.
You should also have received ota update if you are on locked bootloader with no root.
Some of ota roll out dependent on carrier. But if yours is google set, you would be able to receive by now.
Click to expand...
Click to collapse
Well that's a bit of good news. One thing is that on G+ no one has posted the inevitable screenshot of the OTA notification (which are at best annoying but they do it anyway), so it must be rolling out very slowly. The other thing is that once an OTA is released the system images are usually available with the OTA images shortly thereafter. I don't see either of those at this point.
I mean I'm gonna wait and I'm sure it'll be here, but the question is when. I'm on VZW so they might be tweaking some things before the let Google release it. Not sure how that works.
Did yours install in the background and then a reboot to 8.0? How long was the bootup process if you watched it?

For carrier, like you said roll out will take some time. For me, time taken is similar to update and reboot as normal security patch monthly update where it should take longer as this is the whole different version. May be backbone still same but with just UI change and some tweaks.

Stuck on June update - ta-1043

After resetting my Nokia 6.1 phone, it still cannot find any update. Is anyone also stuck on the June patch ? Is that normal?

eipi1 said:
After resetting my Nokia 6.1 phone, it still cannot find any update. Is anyone also stuck on the June patch ? Is that normal?
Click to expand...
Click to collapse
I have TA-1043 and August update.

It sucks and Nokia seems to be silent on this. Everyone (or most) who have software build 2_22A_SP01 seem to be stuck on June. If you have a different build you are getting updates.

Same here : Nokia support reply that it's because my operator don't deploy that update over his network...
When I contact my provider he reply that it's not him who manage software updates on my phone.
I will try to contact Nokia support again with build number and the fact that others are stuck like me on June Update.

Ozhora said:
Same here : Nokia support reply that it's because my operator don't deploy that update over his network...
When I contact my provider he reply that it's not him who manage software updates on my phone.
I will try to contact Nokia support again with build number and the fact that others are stuck like me on June Update.
Click to expand...
Click to collapse
Bull IT Will come over WIFI. No problem.

No updates found over WiFi or cellular network

Hello,
go to
nokia.com/en_int/phones/security-updates
select nokia 6.1
and you 'll see that only 3 firmwares are on july update.
00WW_2_13B_SP03
00WW_2_22A_SP02
00WW_2_22E_SP01

I have 2_22A_SP01 and even with sim card out, in other words, Wifi only, no update is available and I (and many others) am stuck on June.

The option here is to unlock the bootloader and using OST LA, flash the system image again, there is a thread here to do this. For me everything worked fine, and I'm now on August SP

For people stuck with June Patch and a A or B builds variant, you can follow this guide (no bootloader unlock needed) :
community(dot)phones(dot)nokia(dot)com/support/discussions/topics/7000032724
It works and I'm now with the August Patch and a 2-22E build (I was 2-22A with June Patch before).
Follow exactly the different steps (skip Google account is very important)

eipi1 said:
After resetting my Nokia 6.1 phone, it still cannot find any update. Is anyone also stuck on the June patch ? Is that normal?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...pl2-222e-0-t3831764/post77389130#post77389130

It kinda worries me what HMD is doing. The shell is top notch and I actually applaud them for valuing scratch resistance over shatter resistance because one happens in an accident where the other is a constant bugger. But if they are going to do Android One with such problems Google better punish them for not staying up to standard.

Just got July SP on my 1043, however cannot install it...

Finally, phone updated on its own (without special measures), first to July, then to August security patch. Software is now 00WW_2_22E_SP02.

Could unlocked bootloader be the reason I cannot install OTAs ? Because I'm full stock since i flashed back 8.1 firmware using Ntools.

Try clearing data for Google Services Framework. It should work after that. I tried this yesterday but didn't get any updates. I just switch the phone off after that. This morning I powered it on, and 2 updates, July and August came in quickly. Just has to re-connect my google account and all is working well for now.
Hope this helps others.

VS995 updated to 20d security patch

I just received a security update to my LG V20. Does this mean android 9 is next?

Dbrown53 said:
I just received a security update to my LG V20. Does this mean android 9 is next?
Click to expand...
Click to collapse
Same here. I was shocked to see an update

I've been prompted but have not installed it. Some traffic on android central addressing this but it's weird. Version goes to vs99520d (from 20c) but for someone who installed it, the date did NOT change from 1 Oct 2018. One person was told by LG that this is their patch (Verizon tech support knows nothing about it and it is not on their web site) but I've spent a couple hours on the phone now with VZ and LG tech support and they have not been able to find anything at all related to this patch. Maybe it's perfectly fine but who put it out and what's in it?
androidcentral post is here https://forums.androidcentral.com/l...ity-update-my-verizon-lg-v20.html#post6847295

Did the security software version change. Mine is at version 4 not sure what it was before.

My security software version is MDF v2.0 Release 4 on VS99520c.

thchipmunk said:
My security software version is MDF v2.0 Release 4 on VS99520c.
Click to expand...
Click to collapse
Mine is the same, the android central user was told (by LG) that it was a 'security patch' so he was comparing the date under 'Android security patch level' but maybe it's OK for that date to remain the same. At this point I'm more holding off because of being stubborn but I'll probably install it in the next day or two.

It's official Verizon is now showing it on there software update page for the LG V20.

If you update, can you keep root?

You can use the snoopsnitch app to see what the security patch is run the adnroid security patch tester and send a screenshot

So, just got a VS995 in the mail, unrooted. Which is the better root method:
The dirty Santa - https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Or this flashable zip - https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669

baldybill said:
So, just got a VS995 in the mail, unrooted. Which is the better root method:
The dirty Santa - https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Or this flashable zip - https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
Click to expand...
Click to collapse
You need to use Dirty Santa to get unlocked bootloader then you can use zip file to flash oreo with root.

I was going to try to get root on VS99520d now that I have 3 V20's. Verizon is now claiming VS99520c is the latest. Using their software update utility VS99520c is all that is offered now. I do have a copy of what I believe are the OTA update files but God only know what to do with them. Hopefully WiFi calling now works on VS99520c now. This is the only reason I was interested in 20d in the first place.
Edit: I was just being impatient. I got the OTA update after about a half hour. I'm curious what the Verizon Update tool will say about this one "VZW Utility Application - LG"