Database Info

Moto G LTE XT1045 updated to Lollipop rolled back to Kitkat

Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7

electriceccentric said:
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
Click to expand...
Click to collapse
Hi.
In my xt1040, i can flash CM 12 lollipop or a stock rom based from kitkat 4.4.4 without problems (I have a updated bootloader), to get OTA updates again, its necessary flash the stock rom (KK or LP), without root, PURE stock (with all "bloatware").
Now im using a optimized rom from:
http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
No bugs, amazing battery life, and a pure stock, no "bloatware", great ram management.
Sorry for bad english.

electriceccentric said:
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
Click to expand...
Click to collapse
You'll have to wipe the system anyway, updating it will be a waste of time...

Moto G generation 1 update to 5.1 lollipop

I do not have current service activated on my moto G but I have received the 5.1 lollipop update does anybody know of anything that's new with the 5.1 update other than a different UI design. I'm interested in seeing what is really that great about the new update for any possibilities of mods or secrets tips and tricks with this update if anybody knows of anything please let me know I'm excited and hoping for the best

My wife got the update (inactive 1st gen XT1028) it worked the 2nd time, then she factory reset and since the device is locked by Verizon (can't be activated) I've no idea how to bypass the Setup Guide. If ANYONE can help, very much appreciated!

DamianHelixTV said:
My wife got the update (inactive 1st gen XT1028) it worked the 2nd time, then she factory reset and since the device is locked by Verizon (can't be activated) I've no idea how to bypass the Setup Guide. If ANYONE can help, very much appreciated!
Click to expand...
Click to collapse
How far into the activation startup have you gone to? I saw someone say there is an option in "payment" that says "pay later".

Root-Access said:
How far into the activation startup have you gone to? I saw someone say there is an option in "payment" that says "pay later".
Click to expand...
Click to collapse
My device is locked (by Verizon) and can't be activated. So its just the beginning of the call then it tells me it can't happen and click hangs 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!

DON'T upgrade to Nougat by OTA!

This has already discussed in other posts here BUT I continue to see A LOT of people waiting for Nougat OTA like Santa Claus should bring to them... (or, even worse, trying to push it in their phones... )
So, I make this post just to give more visibility to all...
I'll try to write it clear...
Don't update your Z to Nougat by OTA!
Is it clear enough? :laugh:
Now some explainations...
Over the the common generic motivations (difficulties when not in full stock conditions, risk to brick it during process, OTAs that are the Evil... ), there is a strong one in this case: Nougat OTA for Moto Z (silently...) upgrades your bootloader too, from v. 90.xx to v. 91.xx...
This isn't really needed (Nougat runs flawlessly on v.90.xx too... ) BUT it introduces some tighter rules on what you can and what you can't anymore boot on it, limiting hacking and upgrading (to developed third part ROMs...) possibilities...
One of this rules is that with v. 91.xx bootloader you can't anymore boot to MM ROM!
Considering that as of today it seems that bootloader can't be donwgraded (some have soft/hard bricked their Z trying to downgrade it...), Nougat upgrade by OTA is a one way process.
If you consider that stock Nougat seems to have some bugs and issues (and, as of today, no Xposed available...!) and that some (all?) third part Nougat ROMs requires "MM" (v. 90.xx) bootloader to work, it seems not to be a great idea leave that Motorola upgrades silently your bootloader...
So?
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...

I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?

xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
Considering we on the Moto Z droid don't have an unlockable bootloader and/or ability to root I don't see it effecting you negatively, other than an exploit that may be discovered for marshmallow that would allow for root. We are at the mercy of a kind developer taking on the task. I really miss my hotspot without a fee... But I can go back to my Moto X if it is necessary.

xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
I agree with dap... proposed solution can't be used since of unlocked bootloader, BUT if I had a Droid I would have remained sticky to first SW release as long as possible because of the higher probabilities of a flaw to hack and root it...
With Nougat and newer (even more "locked"...) bootloader it will be harder...

those are a lot of steps... is there a way to just hide the nag/update screen that pops up? it keeps wanting to update or ask for a time to update or reminds me to update etc

enetec said:
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
Click to expand...
Click to collapse
Does the method you linked to even work with the VZW variant? It looks like it used to, but the Verizon stuff is all marked through and I'm not clear on the process.

hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...

aatjitra said:
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
Click to expand...
Click to collapse
Hello did you try to get down to MM? Thank you
regards

iron maiden said:
Hello did you try to get down to MM? Thank you
regards
Click to expand...
Click to collapse
No. I didn't.
I read in other thread that bootloader v91 won't work with MM.

Moto Z ( UAE ) no OTA yet
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?

How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?

yanniclord said:
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
Click to expand...
Click to collapse
You can't. The only thing you *can* do is tap the "Later" and then "Done" buttons. That will defer it for another 24 hours since it automatically fills in the phone's current time for the next check.
It's annoying, but it's only once a day.
EDIT: I thought you were referring to the VZW variant. If you're not and your phone is rooted, you might be able to disable or remove "Motorola Update Services". To do so, go to Settings > Apps > select "Show system" from menu (3 dots at top right) > scroll down and tap "Motorola Update Services"
I can't disable it on my VZW unit, but you might be able to. Or maybe you can remove the app via root (though I have no idea if that will cause further problems).

I too can confirm thr disabling motoservice in settings method. But you have to do it everytime you reboot your phone, it does t hurt me doing that.

I found a simple fix, get Titanium Backup and freeze that crap app, done.

yanniclord said:
I found a simple fix, get Titanium Backup and freeze that crap app, done.
Click to expand...
Click to collapse
There is another way for users with root eventually...

saif_khans said:
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
Click to expand...
Click to collapse
Simply use the method linked in OP. It uses retmx sw.

True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?

sam564 said:
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
Click to expand...
Click to collapse
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.

rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Variants doesn't matter all moto z is using same kernel source (I have Chinese moto z)
Let me explain, I'm trying to port farm-root for moto z
Here's the source : https://github.com/freddierice/farm-root
If anyone knows how to deal with ndk and other Stuffs, can install TWRP with this version of farm-root
But I'm trying to make it easier and here's big barrier called SELinux

rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Hope it happens. The phone (accidentally?) Downloaded the update and is now asking to install. I'm afraid one day it'll just automatically update on it's own.. I can't seem to find where the system update got downloaded to, otherwise I'd delete it

New maintenance release : Dec 2016 security patch

Should be popping up on your device (you might have to pull the SIM to trick your handset into seeing the update).
If you want to sideload : https://dl.dropboxusercontent.com/u/22067374/Blur_Version.24.221.8.clark_retus.retus.en.US.zip

Just got mine

You are not tricking it into checking with Google...The update comes from Moto servers. However the sim can cause the imei controlled rollout to not work correctly on some handsets thus removing the sim allows the phone to get back.in line so to speak.

nothing in eu yet

iks8 said:
nothing in eu yet
Click to expand...
Click to collapse
As far we know so far, this is for the XT1575 only... just the December 2016 security update to 6.0, very minor update. Started rolling our about a week ago... a big push seemed to happen on the 14th and 15th with many users receiving it those days.

autosurgeon said:
You are not tricking it into checking with Google...The update comes from Moto servers. However the sim can cause the imei controlled rollout to not work correctly on some handsets thus removing the sim allows the phone to get back.in line so to speak.
Click to expand...
Click to collapse
Edited/fixed

it has been rolled out worldwide... its been like (3weeks ) since i updated it...

Got mine yesterday

Is there any way to update without wifi? I have unlimited data through Cricket Wireless but the system will only let me do it over wifi.

Firefishe said:
Is there any way to update without wifi? I have unlimited data through Cricket Wireless but the system will only let me do it over wifi.
Click to expand...
Click to collapse
No, WiFi is required to get a Moto OTA.

Who the hell cares? This should have been the 7.x update! Too little too late Lenovo.

strafer69 said:
Who the hell cares? This should have been the 7.x update! Too little too late Lenovo.
Click to expand...
Click to collapse
Exactly! There's absolutely no excuse why the Pure hasn't been updated to Nougat especially since the phone uses a damn near vanilla Android! HTC 10 & LG G5 had theirs for over 2 months now & some Samsung S7/S7E has been getting theirs over the past few weeks. My wife regrets buying this phone now over the Nexus 6P last year & now can't wait to dump this phone for the upcoming Galaxy S8+.
Sent from my SM-G935P using Tapatalk

We should all agree that Pure program by GG is a fail. GG initiated it with HTC, Moto... with Pure Edition and commit that they would be upgraded just after Nexus lines

You guys are missing the point.
Nougat 7.1 came out in December. In order to have a smooth update to 7.1, you need the pre requisites which is the security update

piscesjoey said:
Exactly! There's absolutely no excuse why the Pure hasn't been updated to Nougat especially since the phone uses a damn near vanilla Android! HTC 10 & LG G5 had theirs for over 2 months now & some Samsung S7/S7E has been getting theirs over the past few weeks. My wife regrets buying this phone now over the Nexus 6P last year & now can't wait to dump this phone for the upcoming Galaxy S8+.
Click to expand...
Click to collapse
I understand your sentiment regarding the near vanilla, and I'm surprised Google didn't commit Lenovo to keeping the pure/style updated. Lenovo has given over to "standard business practices", which unfortunately means that the manufactures focus on updating their newest flagships first (Moto Z line, G5, GS7, HTC 10). This is nothing new and has been this way for a while. Once again, the rule applies: if you want the latest and greatest Android updates upon release buy a Google phone (Pixel). Aside from that I expect very little. If I want the latest and greatest, I turn to XDA and other sources for custom ROMs (which is nothing new for me).

_litz said:
Should be popping up on your device (you might have to pull the SIM to trick your handset into seeing the update).
If you want to sideload : https://dl.dropboxusercontent.com/u/22067374/Blur_Version.24.221.8.clark_retus.retus.en.US.zip
Click to expand...
Click to collapse
thanks for this, it was driving me crazy that I kept getting promoted to do this, but the update doesn't work with twrp and/or unlocked bootloader. How did you extract the update to sideload it?
---------- Post added at 11:56 PM ---------- Previous post was at 11:56 PM ----------
_litz said:
Should be popping up on your device (you might have to pull the SIM to trick your handset into seeing the update).
If you want to sideload : https://dl.dropboxusercontent.com/u/22067374/Blur_Version.24.221.8.clark_retus.retus.en.US.zip
Click to expand...
Click to collapse
thanks for this, it was driving me crazy that I kept getting prompted to do this, but the update doesn't work with twrp and/or unlocked bootloader. How did you extract the update to sideload it?

It'll be another 2-3 months to even get 7.0 and than no more updates. That's why **** motorola/lenovo nobody buy the G6 or G6 plus so they finally go out of business!
Sent from my XT1575 using XDA-Developers Legacy app

you don't extract it to sideload it ... you need to make sure you have original partitions (this will NOT apply to a modified system or boot), and then restore the factory recovery. Factory recovery has a sideload from ADB option.
If you have modified enough, you may have to backtrack to the last full system image (may 2016, I think it was), then do the sept update, followed by the dec update.
Those are available in other threads on XDA.

Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible

_litz said:
you don't extract it to sideload it ... you need to make sure you have original partitions (this will NOT apply to a modified system or boot), and then restore the factory recovery. Factory recovery has a sideload from ADB option.
If you have modified enough, you may have to backtrack to the last full system image (may 2016, I think it was), then do the sept update, followed by the dec update.
Those are available in other threads on XDA.
Click to expand...
Click to collapse
why is it so difficult to apply a few security patches. at this point i'll wait for nougut. I've been eyeing a few of the nougut roms, but I see comments about stability and features not working.
do we need to relock the bootloader too? or just no root, stock partitions, and stock recovery?