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 have tried multiple times checking for updates over the past 2 weeks and my phone won't update. Is there a way to manually update? Like through my PC or something?
I would check to see if you have any disabled apps. I have done it numerous times, and have to re-enable them for updates to take.
ATT Phone + Updates
In my own experience, ATT usually takes a while until they release an update. I used to have a Note5 (locked to ATT) and it took FOREVER to get Android Nougat. When I finally got the update, Google announced that they were starting to develop Android Oxygen . I heard that the Samsung representatives @ Best Buy can help with installing updates manually but I cannot confirm this as I have never done it myself. If you want, you can call Best Buy to confirm if they can do this.
Hope this helps!
Are you on AT&T network? or are you using other provider?
You can only get OTA update through AT&T DM server.
Side loading AT&T update can reset your data.
specter491 said:
I have tried multiple times checking for updates over the past 2 weeks and my phone won't update. Is there a way to manually update? Like through my PC or something?
Click to expand...
Click to collapse
TheUprising said:
In my own experience, ATT usually takes a while until they release an update. I used to have a Note5 (locked to ATT) and it took FOREVER to get Android Nougat. When I finally got the update, Google announced that they were starting to develop Android Oxygen . I heard that the Samsung representatives @ Best Buy can help with installing updates manually but I cannot confirm this as I have never done it myself. If you want, you can call Best Buy to confirm if they can do this.
Hope this helps!
Click to expand...
Click to collapse
The thing is ATT has released 1 or 2 updates already and I never got them
power_book said:
Are you on AT&T network? or are you using other provider?
You can only get OTA update through AT&T DM server.
Side loading AT&T update can reset your data.
Click to expand...
Click to collapse
Yes on ATT network with a ATT phone
specter491 said:
Yes on ATT network with a ATT phone
Click to expand...
Click to collapse
I would backup and factory reset your phone. If you're savvy on flashing rom, you can directly update with odin or using SD card method.
if that doesn't work. I'd goto the Samsung experience center inside Bestbuy store.
or you can visit AT&T corporate store for help.
Yes we can help with updates at Best Buy. We use smart tool to update the phone. Just make sure you backup your device. Att is always the worst when it comes to update time and updates working correctly.
I work at Samsung and have to deal with att updates all the damn time.
You can install BK and force stop the Software Updater process that runs in the background. Then reboot and try updating again. That worked for me.
Sent from my SM-G955U using Tapatalk
https://forum.xda-developers.com/att-galaxy-s8+/how-to/adb-updates-g955u-att-t3606211
usually I would factory reset after backup
Check Update. For me i have update yesterday.
Orange phone .
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.
so i flashed to international rom then updated to android 10 and when i put in any tmobile sim card it says
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".
there is no unlock app on the android 10 open beta, im rolling back to android 9 to see if it fixes issue...
Rolling back does fix this issue but I am not sure why the issue exists in the first place. I did this yesterday - had the same problem and I used the rollback and phone was fine again.
berdo said:
Rolling back does fix this issue but I am not sure why the issue exists in the first place. I did this yesterday - had the same problem and I used the rollback and phone was fine again.
Click to expand...
Click to collapse
Hey forgot to update the thread, yes you are correct. Just rolled back. Really sucks because Android 10 is a really big difference to me. I just sold my pixel 3xl and I'm already used to it. I'll probably give it another try when there's an update.