I just got the OTA update notification for the VZW Pixel, fully stock, unrooted, locked bootloader. Never joined the beta either. So now we'll see if any of these BT and reboot issues have been resolved. Here's hopin'
Update size: 938.4 MB
bobby janow said:
I just got the OTA update notification for the VZW Pixel, fully stock, unrooted, locked bootloader. Never joined the beta either. So now we'll see if any of these BT and reboot issues have been resolved. Here's hopin'
Update size: 938.4 MB
Click to expand...
Click to collapse
do you have always on ambient display with this update?
Tech_Savvy said:
do you have always on ambient display with this update?
Click to expand...
Click to collapse
Yes I do. Everything seems to have rolled over fine. Update screen was not the bouncing thingies but simply the G logo. Haven't rebooted to see.. oh just a little of the dots, then a quick G and then it was up. Like maybe 10 seconds for a reboot. Wow.
bobby janow said:
I just got the OTA update notification for the VZW Pixel, fully stock, unrooted, locked bootloader. Never joined the beta either. So now we'll see if any of these BT and reboot issues have been resolved. Here's hopin'
Update size: 938.4 MB
Click to expand...
Click to collapse
I just downloaded and installed it with a unlocked bootloader no problem. It's still unlocked and I just rooted it.
All the OTA images are available at https://developers.google.com/android/ota. You can all download as you wish.
henrique.mageste said:
All the OTA images are available at https://developers.google.com/android/ota. You can all download as you wish.
Click to expand...
Click to collapse
Anyone know which one is for Verizon?
jackdubl said:
Anyone know which one is for Verizon?
Click to expand...
Click to collapse
The .012 image. It is meant for all the phone's not covered by the .011 build.
Always On Ambient Display
Either, this didn't make it through in my update somehow or I'm overlooking the setting.
Can anyone offer any help on enabling this feature?
Thanks!
Man, that's annoying, I still haven't gotten it on my Project Fi pixel. I left vzw because I never got updates!
skyline315 said:
Either, this didn't make it through in my update somehow or I'm overlooking the setting.
Can anyone offer any help on enabling this feature?
Thanks!
Click to expand...
Click to collapse
I'd like to know as well
Where is the setting for always on ambient display? All I see is the regular ambient display, where it turns on for new notifications.
speedy859 said:
Where is the setting for always on ambient display? All I see is the regular ambient display, where it turns on for new notifications.
Click to expand...
Click to collapse
I've asked around and consensus seems to be that it was NOT included in this update after all. Looks like they're saving it for the Pixel 2.
JoeHockey said:
Man, that's annoying, I still haven't gotten it on my Project Fi pixel. I left vzw because I never got updates!
Click to expand...
Click to collapse
Im on fi I just downloaded the ota and then sideloaded it.
Go to settings - display - advanced and it will be towards the bottom.
Nevermind, misread. It is only for notifications. You can make it turn on when you pick it up though. By turning on "lift to check phone"
Sent from my Pixel using XDA Free mobile app
Misterxtc said:
I just downloaded and installed it with a unlocked bootloader no problem. It's still unlocked and I just rooted it.
Click to expand...
Click to collapse
Hi,
Can you let me know what version of twrp.img u used for fastboot? I tried rc1 and alpha 1. Both locked my phone up.
Really appreciate ur help
randogg65 said:
Hi,
Can you let me know what version of twrp.img u used for fastboot? I tried rc1 and alpha 1. Both locked my phone up.
Really appreciate ur help
Click to expand...
Click to collapse
I use the modded one for O here. You need to fastboot and load TWRP every time you use it because it is not flashable yet.
Misterxtc said:
I just downloaded and installed it with a unlocked bootloader no problem. It's still unlocked and I just rooted it.
Click to expand...
Click to collapse
which root method did you use since you didn't sideload? thanks.. jforgive me if it's been posted. ust getting back onto the forums and currently reading up
Misterxtc said:
I use the modded one for O here. You need to fastboot and load TWRP every time you use it because it is not flashable yet.
Click to expand...
Click to collapse
Thanks! Really appreciate it
honourbound68 said:
which root method did you use since you didn't sideload? thanks.. jforgive me if it's been posted. ust getting back onto the forums and currently reading up
Click to expand...
Click to collapse
I can't remember where I got the file I used so I would say try here.
Meanwhile...
cbusm30 said:
I'd like to know as well
Click to expand...
Click to collapse
There are also 8.0.0 factory images as well (along with the usual older factory images) - they are all here: http://www.infinitiofsuitland.com/VehicleSearchResults?search=new
To play it safe, I grabbed one 7.1.2 and one 8.0.0 factory image for the Pixel to put through the wringer (since this would be the first Pixel I've ever put through the paces).
Related
http://www.droid-life.com/2015/07/01/verizon-says-android-5-1-1-lmy47z-is-ready-for-its-nexus-6/
It's happening! LMY47Z.
Not yet hitting my phone, but perhaps by tomorrow ...
I had Verizon's 5.1 build on my phone, but I didn't wait. I just flashed 47Z because I'm on an AT&T MVNO, so I don't know if I would have received the OTA.
It's not on the official Nexus factory image page.
ckarrow2 said:
It's not on the official Nexus factory image page.
Click to expand...
Click to collapse
technically it is, it just doeant say verizon.
simms22 said:
technically it is, it just doeant say verizon.
Click to expand...
Click to collapse
It's LMY47Z, right?
Turgur said:
It's LMY47Z, right?
Click to expand...
Click to collapse
Someone on androidcentral forums confirmed it is. they received LMY47Z as an OTA to their verizon nexus 6 last night coming from E.
I got the ota yesterday, unrooted, flashed stock recovery, and went to accept the ota, started flashing then it said error and stopped, now it says up to date
I just want know if they changed radio but I doubt
Does it have any "Verizon authorized software" added?
I hope it doesn't but according to the letters Verizon sent out responding to the FCC complaints that is why they would not activate a nonVerizon Nexus 6 on their network until Google said that the software could be sent out to those phones via the OTA.
Paul1201 said:
Does it have any "Verizon authorized software" added?
I hope it doesn't but according to the letters Verizon sent out responding to the FCC complaints that is why they would not activate a nonVerizon Nexus 6 on their network until Google said that the software could be sent out to those phones via the OTA.
Click to expand...
Click to collapse
More like they wanted an ota to convert it to the VZW version and they got it. The bloat wasn't really the issue.
coldconfession13 said:
I just want know if they changed radio but I doubt
Click to expand...
Click to collapse
Same baseband as the existing LMY47Z
To anyone who's receiving the OTA from LMY47E to LMY47Z - if you're able to, please take a few minutes to grab the OTA URL and share it in this thread. Instructions for getting the OTA URL can be found here, and this will allow people who haven't received the OTA to sideload it.
Thanks!
Question, I have a VZW Nexus 6 I got from a Verizon store a few weeks ago. My firmware version is LMY47l
Is that the correct one? I see you guys talking about an "E" version... When I went back from Android M preview, did I flash the wrong stock ROM in Wugs Nexus Root Toolkit?
SquireSCA said:
Question, I have a VZW Nexus 6 I got from a Verizon store a few weeks ago. My firmware version is LMY47l
Is that the correct one? I see you guys talking about an "E" version... When I went back from Android M preview, did I flash the wrong stock ROM in Wugs Nexus Root Toolkit?
Click to expand...
Click to collapse
Nope and if a phone from Verizon came with that, you were likely sold a returned device instead of a new one.
adrynalyne said:
Nope and if a phone from Verizon came with that, you were likely sold a returned device instead of a new one.
Click to expand...
Click to collapse
No, this is my fault. I tried out the Android M preview, and got tired of the FC's and bugs, so I used the Nexus Tool Kit to flash back to stock, and I guess I grabbed the wrong firmware download. I have the Z version for Verizon and will flash that to get me back on track.
SquireSCA said:
Question, I have a VZW Nexus 6 I got from a Verizon store a few weeks ago. My firmware version is LMY47l
Is that the correct one? I see you guys talking about an "E" version... When I went back from Android M preview, did I flash the wrong stock ROM in Wugs Nexus Root Toolkit?
Click to expand...
Click to collapse
Seems that way
Doh!
Ok, so is the 5.1.1 version on this page the one I want to flash to get me up to the latest CORRECT version for this phone?
http://www.randomphantasmagoria.com/firmware/nexus-6/shamu/vzw/
SquireSCA said:
Doh!
Ok, so is the 5.1.1 version on this page the one I want to flash to get me up to the latest CORRECT version for this phone?
http://www.randomphantasmagoria.com/firmware/nexus-6/shamu/vzw/
Click to expand...
Click to collapse
That link is being block from my end(im at work) so I cant verify that.
mademan420 said:
That link is being block from my end(im at work) so I cant verify that.
Click to expand...
Click to collapse
Here is a screen cap:
SquireSCA said:
Here is a screen cap:
Click to expand...
Click to collapse
Looks like that would be it:good: LMY47Z
Are you running stock unrooted now with stock recovery?
Has anyone else receive an update just now on their pixel xl? It's 33.8mb in size. I disabled the updates and it shows restart to upgrade. -_-
Verizon or what?
thewebsiteisdown said:
Verizon or what?
Click to expand...
Click to collapse
it was a google update. but yes on verizon..
What build is it in your settings now
I got the same update and I'm Verizon running running Google firmware 'L' with elemental kernel and root. The update said it was 45mb
Google store pixel xl
moosc said:
Google store pixel xl
Click to expand...
Click to collapse
I'm on Verizon but installed the Google firmware and my update size is the exact same!! That makes me feel better...
guaneet said:
What build is it in your settings now
Click to expand...
Click to collapse
nde63p
TechBSwift said:
I'm on Verizon but installed the Google firmware and my update size is the exact same!! That makes me feel better...
Click to expand...
Click to collapse
were you able to order your daydream headset yet? if so how did you do it?
if you flashed the viper4android mod that might be why
diabl0w said:
if you flashed the viper4android mod that might be why
Click to expand...
Click to collapse
nah, its still completely stock and didnt do anything yet.
Are you rooted n bootloader unlock?
TechBSwift said:
I'm on Verizon but installed the Google firmware and my update size is the exact same!! That makes me feel better...
Click to expand...
Click to collapse
moosc said:
Are you rooted n bootloader unlock?
Click to expand...
Click to collapse
TechBSwift said:
I'm on Verizon but installed the Google firmware and my update size is the exact same!! That makes me feel better...
Click to expand...
Click to collapse
curious as well.
Who's going to be the one to try the update first? Not it!!!
Mine is completely stock, non modified bootloader. No update here yet.
I tried but it failed. I'm rooted n unlocked
TechBSwift said:
Who's going to be the one to try the update first? Not it!!!
Click to expand...
Click to collapse
My **** automatically installed it.
I spoke to jcase in the other thread, he stated it was nothing more than the p firmware update since I'm on on L
TechBSwift said:
I spoke to jcase in the other thread, he stated it was nothing more than the p firmware update since I'm on on L
Click to expand...
Click to collapse
So we're good on the p update?
Is anyone not on Verizon getting g this update?
Edit 2: speculation be damned. This seems to be a true release build and not a leaked developer preview like has been hypothesized. Flagged REL for a release build. https://imgur.com/uU0bR2S
THIS IS FOR PIXEL XL ONLY OF COURSE. November 22nd OTA Build NPF26J
Includes bug fixes and performance enhancements. New Modem and Kernel. Kernel updated to include Double Tap To wake and Lift to Wake. May be other features. Don't know.
https://ota.googlezip.net/packages/.../09c7f402fd047c0d631fdd6c4168c934d3b9451b.zip
Pulled from Reddit thread.
Edit: Apparently you have to be on V build before flashing.
https://www.reddit.com/r/GooglePixe...f26j/?st=ivtsrfnz&sh=cae95dfe#bottom-comments
This will only work from the V build FYI
tw1tch175 said:
This will only work from the V build FYI
Click to expand...
Click to collapse
So this won't install on the VZW Pixel XL with NDE63X? I'd have to installed NDE63V first?
airmaxx23 said:
So this won't install on the VZW Pixel XL with NDE63X? I'd have to installed NDE63V first?
Click to expand...
Click to collapse
Yup, I'm locked so I'll just wait for the rollout.
I got the update message on mine but I'm rooted. Can I accept the download or do I have to do it a different way?
dnyc said:
I got the update message on mine but I'm rooted. Can I accept the download or do I have to do it a different way?
Click to expand...
Click to collapse
What build are you currently on?
dnyc said:
I got the update message on mine but I'm rooted. Can I accept the download or do I have to do it a different way?
Click to expand...
Click to collapse
It won't work on root, what build are you on currently?
dnyc said:
I got the update message on mine but I'm rooted. Can I accept the download or do I have to do it a different way?
Click to expand...
Click to collapse
I believe the update has to be sideloaded with adb on rooted phones.
Code:
adb sideload update.zip
lightning413 said:
I believe the update has to be sideloaded with adb on rooted phones.
Code:
adb sideload update.zip
Click to expand...
Click to collapse
It will fail, you cannot OTA on a rooted phone
tw1tch175 said:
It will fail, you cannot OTA on a rooted phone
Click to expand...
Click to collapse
Thank you, I thought I read it somewhere but can't find out where.
I'm not going to update anyway, perfectly happy with the way the phone is running with ElementalX kernel and don't want to mess it up
Will there be an update for the NDE63X build eventually or will we have to roll back to the V build?
I bought my pixel from Google but use on Verizon. My phone is running NDE63X. Should I be on V? Anybody else purchase from Google and run on Verizon that can confirm their build for me?
lightning413 said:
Thank you, I thought I read it somewhere but can't find out where.
I'm not going to update anyway, perfectly happy with the way the phone is running with ElementalX kernel and don't want to mess it up
Click to expand...
Click to collapse
Are you on the V or X build currently?
mjc2251 said:
I bought my pixel from Google but use on Verizon. My phone is running NDE63X. Should I be on V? Anybody else purchase from Google and run on Verizon that can confirm their build for me?
Click to expand...
Click to collapse
Pixel XL, Google Play Store, Verizon as carrier: NDE63X (unlocked & rooted)
tw1tch175 said:
Are you on the V or X build currently?
Click to expand...
Click to collapse
I'm on V
I'm on v. I'll do the adb method. Thanks. Root will still work afterwards?
dnyc said:
I'm on v. I'll do the adb method. Thanks. Root will still work afterwards?
Click to expand...
Click to collapse
Won't work and no
dnyc said:
I got the update message on mine but I'm rooted. Can I accept the download or do I have to do it a different way?
Click to expand...
Click to collapse
I couldn't flash until I was fully stock. Had to flash full system image without the wipe command before i could flash ota.
mjc2251 said:
I bought my pixel from Google but use on Verizon. My phone is running NDE63X. Should I be on V? Anybody else purchase from Google and run on Verizon that can confirm their build for me?
Click to expand...
Click to collapse
any phone with a verizon sim will get verizon builds which should be x. You can flash to v if you want to without harm.
scloutkst said:
any phone with a verizon sim will get verizon builds which should be x. You can flash to v if you want to without harm.
Click to expand...
Click to collapse
So what's the easiest way to go from the X build to the NPF26J build?
Just got a notification tonight about downloading and updating my Sprint HTC 10 to 2.51.617.2.
Has anyone received this update yet? I'm unlocked with Magisk root and don't want to go thru the update if it's going to break Safetynet (again!).
I got the notification too, but I have not allowed it to go in so far.
The update is actually 2.51.651.2 and is July 2017 security update. I did it yesterday without issues.
costy11 said:
The update is actually 2.51.651.2 and is July 2017 security update. I did it yesterday without issues.
Click to expand...
Click to collapse
It is only the security updates? It is 802MB! That is a lot of security! I doubt it would go in on mine anyway as I have too many system modifications.
lexridge said:
It is only the security updates? It is 802MB! That is a lot of security! I doubt it would go in on mine anyway as I have too many system modifications.
Click to expand...
Click to collapse
And "Performance enhancements" too, whatever they may be, as it had no further details on them.
For me, it broke the fingerprint sensor. It now works to unlock the phone only within the first 5 minutes or so after turning it off. After that, I have to use the pattern. It's like the sensor gets disabled during low-power suspend, but turning the screen on doesn't wake it back up. This started immediately after I received the update.
costy11 said:
The update is actually 2.51.651.2 and is July 2017 security update. I did it yesterday without issues.
Click to expand...
Click to collapse
We're you able to take the OTA with root and/or TWRP? Have you experienced any adverse effects?
radji said:
We're you able to take the OTA with root and/or TWRP? Have you experienced any adverse effects?
Click to expand...
Click to collapse
I took it OTA. I just got the phone a month ago and have only sim unlocked it, no root or twrp. Everything seems to be working fine still since the update.
I was unable to take the update with root and TWRP.
hegemon13 said:
For me, it broke the fingerprint sensor. It now works to unlock the phone only within the first 5 minutes or so after turning it off. After that, I have to use the pattern. It's like the sensor gets disabled during low-power suspend, but turning the screen on doesn't wake it back up. This started immediately after I received the update.
Click to expand...
Click to collapse
Anyone else experience this? I'm a bit hesitant to do the update if this is a real problem.....
Sent from my 2PS64 using Tapatalk
DNarsingh said:
Anyone else experience this? I'm a bit hesitant to do the update if this is a real problem.....
Sent from my 2PS64 using Tapatalk
Click to expand...
Click to collapse
I'm interested to know, too. Is it a fluke or coincidence that I might fix with a factory reset, or is anyone else seeing the same thing? If I'm going to reset anyway, might be time to go ahead and root it.
DNarsingh said:
Anyone else experience this? I'm a bit hesitant to do the update if this is a real problem.....
Click to expand...
Click to collapse
It happened to mine. Sometimes the scanner works, most times it doesn't.
Anyone know where I can get the 2.42.651.63 recovery to flash? I want to take the OTA but I did not backup the stock recovery when I flashed TWRP after the last update.
radji said:
Anyone know where I can get the 2.42.651.63 recovery to flash? I want to take the OTA but I did not backup the stock recovery when I flashed TWRP after the last update.
Click to expand...
Click to collapse
look in the firmware/RUU thread? https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
DNarsingh said:
Anyone else experience this? I'm a bit hesitant to do the update if this is a real problem.....
Sent from my 2PS64 using Tapatalk
Click to expand...
Click to collapse
Same issue here. I really don't want to reset the device to find out if it helps. I was hoping yesterday's update, 2.5.651.11 would fix it but it didn't.
OMJ said:
look in the firmware/RUU thread? https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
Click to expand...
Click to collapse
I downloaded the 2.42.651.63 firmware zip, but am unable to open it. 7-zip says its not a valid zip file.
Since manually installing this update, I can no longer change my SMS Notification sound using the stock SMS app.. No matter what I change it to, it still uses the default system sound. Any ideas how to fix this, without switching SMS apps?
lexridge said:
Since manually installing this update, I can no longer change my SMS Notification sound using the stock SMS app.. No matter what I change it to, it still uses the default system sound. Any ideas how to fix this, without switching SMS apps?
Click to expand...
Click to collapse
I tried everything from Sprint's based release. Fingerprint sensor issues everytime. On Leedroid's latest release. It's not firmware related, it's software. Something Sprint put in is messing with fingerprint sensor from sleep.
Sent from my 2PS64 using Tapatalk
Anybody install this yet?
jimlightner said:
Anybody install this yet?
Click to expand...
Click to collapse
I have been running 10.3 for a while and I am t-mobile locked but converted to International. Everything is smooth other than Gpay is not working and Playstore is not certified. This is because I am t-mobile variant.
jimlightner said:
Anybody install this yet?
Click to expand...
Click to collapse
Yes! I've been installed for a few weeks. All perfect.
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
I too got a push update notification. My question is this, can I update through the regular method as it's a full update or do I need to flash?
Originally t mobile variant I rebranded to international and sim unlocked. Also flashed to 9.0.17 and rooted via magisk. Any insight would be appreciated as I have heard improper updating can result in a brick. Thanks in advance
BoSavageYo said:
I too got a push update notification. My question is this, can I update through the regular method as it's a full update or do I need to flash?
Originally t mobile variant I rebranded to international and sim unlocked. Also flashed to 9.0.17 and rooted via magisk. Any insight would be appreciated as I have heard improper updating can result in a brick. Thanks in advance
Click to expand...
Click to collapse
Just do a local upgrade. Just follow the guide to save root.
jimlightner said:
Anybody install this yet?
Click to expand...
Click to collapse
Everybody has installed it... It's been out for days
Went for it yesterday. With an "ultimate guide" here on forum. I was 9.0.17 rooted with twrp description problems. So I downloaded update (1.8Gb) from official One+ site. And did local update, and all the steps to keep root. After finally booting up I got message that Magisk Manager stopped working, but everything was fine. So cleared app temp memory, and settings (for Magisk only) and next boot everything was ok.
Nope... 100% stock, 9.0.17 is ROCK solid, g-pay, samsung pay work perfectly & there really isn't anything in 10 I can't live without yet. So, I
see no need to update for now.
I'm also not updating yet, at least until they fix the keyboard offset issue and other things I've read about.
Luckily you can just freeze the system update app with Titanium.
sssarg said:
I'm also not updating yet, at least until they fix the keyboard offset issue and other things I've read about.
Luckily you can just freeze the system update app with Titanium.
Click to expand...
Click to collapse
There is no keyboard offset issue and so therefore it's never getting fixed. Designs can change, but there isn't going to be a fix for something that isn't a problem.
Causical said:
There is no keyboard offset issue and so therefore it's never getting fixed. Designs can change, but there isn't going to be a fix for something that isn't a problem.
Click to expand...
Click to collapse
Judging by all the people complaining about the empty space under the keyboard it does seems to be a problem, though.
sssarg said:
Judging by all the people complaining about the empty space under the keyboard it does seems to be a problem, though.
Click to expand...
Click to collapse
There is a Magisk module to deal with that (immersive gestural Navigation for Android 10), and an adb command to change the size of the space. It's a deliberate thing from Google so they'll perhaps remove it later or no but staying with Pie just for that.....
Causical said:
There is no keyboard offset issue and so therefore it's never getting fixed. Designs can change, but there isn't going to be a fix for something that isn't a problem.
Click to expand...
Click to collapse
It's not a bug, it's there for the swipe gesture, so that way you won't swipe the keypad when using gestures
Sent from my LG-G8 using Tapatalk
Question of the day. I've been waiting to do the A10 update for the issues it showed on the first days. I'm on a converted 6T from TMo, running 9.0.17. my major concern is the GPay thing I use it a lot. But researching here there's a way to make it work if I root the device. So can I update to 10.3.0 then root to get the GPay issue resolved with the Hide module on magisk? Or should I root on Pie then update?
phillymade said:
It's not a bug, it's there for the swipe gesture, so that way you won't swipe the keypad when using gestures
Sent from my LG-G8 using Tapatalk
Click to expand...
Click to collapse
This is pretty bad ux experience, and with the amount of complaints it seems and accidental keypress possibly when swiping is much better than losing all the text and keyboard closing with an accidental touch. At least give us the option to move it down, without having to go into ADB and setting an offset that then interferes with the way all apps render.