This is an xpost from where i posted originally (Moto G - 2014) since I was in the wrong forum. Please forgive.
I'm running 4.4.4 stock on an XT 1040 (the LTE Canadian Rogers variant of the MotoG). I had unlocked the bootloader and rooted the phone, but other than that kept the stock image. About 2 weeks ago my wife, with the same model, was offered 5.0.1 (or some version of Lollipop) OTA. She upgraded no probs (other than hanging a long time on the download screen). About 3 days later I was offered OTA on my rooted MotoG. After running through the download, it rebooted and tried applying the update and got mid way through and rebooted back to 4.4.4 saying there was an error. I tried again, same problem. So I started reading posts and realized that while my image was stock, because of the way I must have gained root the OTA update wouldn't apply because the kernel must be altered.
So, I followed the instructions here (linky) to go back to the stock image, but now it's been about a week and I have not been offered the OTA again. A couple days ago I talked with Motorola about whether OTA is re-offered in situations like mine if its offered once and the guy said no and to call Google to get them to re-initiate it. I'm not really positive I trust that answer since he seemed kind of, well, "level1tech" and seemed anxious to get off the line.
Anybody know if the OTA is tied to your IMEI or google accounts and whether it's likely it will be offered again?
TIA
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!
Sorry, if it's been asked but I couldn't find an answer.
I have Verizon Pixel working on TMobile. bootloader is unlocked, phone is rooted and has TWRP installed. It is also updated to 7.1.1 via OTA. It currently has NMF26O firmware.
How do I update to NMF26Q? I get nothing via software check on the phone probably because it's rooted or on T-Mobile network.
Thanks for the help.
You can download it from:
https://developers.google.com/android/ota
And update using adb sideload
krelvinaz said:
You can download it from:
https://developers.google.com/android/ota
And update using adb sideload
Click to expand...
Click to collapse
That's what I thought. Do you know if update wipes everything and I need to reroot and TWRP.
radekmazur said:
Sorry, if it's been asked but I couldn't find an answer.
I have Verizon Pixel working on TMobile. bootloader is unlocked, phone is rooted and has TWRP installed. It is also updated to 7.1.1 via OTA. It currently has NMF26O firmware.
How do I update to NMF26Q? I get nothing via software check on the phone probably because it's rooted or on T-Mobile network.
Thanks for the help.
Click to expand...
Click to collapse
I would wait till Tuesday when the January update comes out. Only have to do it once. And the update is for overseas. Don't need it for T Mobile.
Why do you want NMF26Q? If you are not on O2 or China Unicom there's nothing there for you.
I have the Verizon pixel on Verizon and I personally would not install it, I did and I was having freezing and rebooting issues with a clean install. Plus like everyone else is saying, the newest security update will be
Thank you all.
I would wait for the January update, too.
FWIW, I fastboot flash-all updated to 26Q the day it came out. Works fine here....
Is it possible to flash June update NGK47L for TMobile on NH 47TH verizon
I'm considering buying a used Google Pixel that was purchased via Verizon. Through researching, it sounds like I should be able to just pop in my AT&T SIM and it should work. Is this correct?
What I don't want is a phone that has Verizon bloatware installed and delayed updates. Will I be able to install non-Verizon factory images? I see There multiple 7.1.2 factory images listed at https://developers.google.com/android/images for the Pixel. (N2G47O, May 2017) and (NHG47L, May 2017, Verizon). Will I be able to install the N2G47O version or would I be stuck installing the Verizon branded version.
Thanks for any help.
Also with the same question
Enviado desde mi Redmi Note 3 mediante Tapatalk
beand1p said:
I'm considering buying a used Google Pixel that was purchased via Verizon. Through researching, it sounds like I should be able to just pop in my AT&T SIM and it should work. Is this correct?
What I don't want is a phone that has Verizon bloatware installed and delayed updates. Will I be able to install non-Verizon factory images? I see There multiple 7.1.2 factory images listed at https://developers.google.com/android/images for the Pixel. (N2G47O, May 2017) and (NHG47L, May 2017, Verizon). Will I be able to install the N2G47O version or would I be stuck installing the Verizon branded version.
Thanks for any help.
Click to expand...
Click to collapse
I just recently picked up a google pixel , I traded a galaxy s7 edge for it. The google pixel was originally verizon, I just popped in my tmobile sim card and it was good to go. The only set back is if you want to unlock the bootloader, from reading various forums its possible IF the phone is on 7.1. Apparently if you upgrade with a non verizon sim or over wifi itll allow you the option to unlock the bootloader. You can uninstall all verizon apps, as for the image you are probably stuck on the verizon one for the time being till an unlock for a bootloader comes out. People have reported contacting google and being able to rma their verizon phone for a non verizon one to unlock the bootloader.
Been reading all of the relevant threads.
Installed the latest Android Studio / SDK tools.
Verizon Pixel XL, Android 7.1.2, Build NHG47N, June 5 2017 Security Patch.
Bootloader is locked.
Every time I attempt to do an OTA update over WiFi (To Oreo 8.0), it downloads successfully, and then fails.
A locked Bootloader on a Verizon Pixel XL is a showstopper for flashing ANY version of Android from a computer - Correct?
If a Pixel XL won't install an OTA update after downloading, there's nothing that can be done to correct it - Correct?
I am... in a dead end? Correct?
-FP
tenbbs said:
Been reading all of the relevant threads.
Installed the latest Android Studio / SDK tools.
Verizon Pixel XL, Android 7.1.2, Build NHG47N, June 5 2017 Security Patch.
Bootloader is locked.
Every time I attempt to do an OTA update over WiFi (To Oreo 8.0), it downloads successfully, and then fails.
A locked Bootloader on a Verizon Pixel XL is a showstopper for flashing ANY version of Android from a computer - Correct?
If a Pixel XL won't install an OTA update after downloading, there's nothing that can be done to correct it - Correct?
I am... in a dead end? Correct?
-FP
Click to expand...
Click to collapse
Side loading ota and beta/preview builds should still work/I think/ but you should probably just request an RMA cuz Google seems to like to throw money at replacing these phones when they can and I'm pretty sure OTA failure is something they cover