Nexus 6p ota 7.1.1 ota "Verification failed" - Nexus 6P Q&A, Help & Troubleshooting

Nexus 6p update 7.1.1 verificaton failed??? New to droid and not a developer I bought from pawn shop this summer. Showed software up to date and sim worked calls/data on cricket network. Phone running dirty unicorns? ROM? SuperSU? No clue DU? Read about Nexus/google sending monthly security patches/updates but nothing here since may,1 patch phone showed being done week before i bought the phone? Finally like 12/6?7? received a system update "7.1.1" day after they began rolling out to 6p's from what I think I maybe understand:/? So clicked on update which " fixes crucial bugs and improves stability and performance for your nexus 6p." 1270.1mb file "OK" starts the "downloading" showing as status bar slowly showing progress moving left to right. Half hour later+/- download completes "Verification failed" ??? Nothing updated goes back to update screen loops thru the process downloading 30+/- minutes or so then same " verification failed" Need help securing phone/personal data etc making it my own praying my privates life still private (besides google) and that I'm not owned!?! Hoped update would return me to factory settings along with my peace of mind but without verification maybe unicorns have a point:/

Suggest you follow this link... http://www.wugfresh.com/nrt/ The safest way to fix your issue. Seams you have custom rom in the phone, and you are trying to update with a factory rom. This website will help you get the phone back to a factory stock rom and from then on you will be able to get OTA updates without issues.

Related

Update to 4.2 fail on brand new Nexus 7

Hi,
I just received a brand new Nexus 7. I turned it on, logged into my account, and then the first thing I did was go to settings -> about -> check for system updates.
It started updating to 4.2
During the update, I got the android with red exclamation point.
Pressed power and volume up and it shows this. (See attached image)
I'm completely stumped. Its brand new and hasn't been rooted or modified.
I tried sideloading the update via adb but I get the same error.
Any ideas?
Any help would be greatly appreciated. Thanks
If you got it local, exchange it. You don't have a lot of time invested at this point to try to fix it.
I had the same exact problem but it was really easy to fix.
I downloaded the Nexus 7 toolkit and did the following:
1) Installed the Google Nexus 7 Drivers from the Nexus 7 Toolkit menu.
2) Unlocked my BootLoader from the Nexus 7 Toolkit.
3) Downloaded the factory stock rom for 4.1.2 in the Nexus 7 Toolkit.
4) Put my device in fastboot mode (power + volume down)
5) Selected the option to flash the device with the factory rom.
Once it was installed, I was able to apply the OTA update. Apparently many of these devices ship with this issue.
JayOui said:
I had the same exact problem but it was really easy to fix.
I downloaded the Nexus 7 toolkit and did the following:
1) Installed the Google Nexus 7 Drivers from the Nexus 7 Toolkit menu.
2) Unlocked my BootLoader from the Nexus 7 Toolkit.
3) Downloaded the factory stock rom for 4.1.2 in the Nexus 7 Toolkit.
4) Put my device in fastboot mode (power + volume down)
5) Selected the option to flash the device with the factory rom.
Once it was installed, I was able to apply the OTA update. Apparently many of these devices ship with this issue.
Click to expand...
Click to collapse
If you're going to go through the trouble of flashing a factory image to get the N7 up to date, just flash the latest. There's no need to waste time with the OTA at this point.
edit: the blurry image shows a patch assertion error on the kernel. This means that the installed kernel does not match what the OTA was expecting to find. This is typically indicative of the presence of a custom kernel.
comminus said:
If you're going to go through the trouble of flashing a factory image to get the N7 up to date, just flash the latest. There's no need to waste time with the OTA at this point.
edit: the blurry image shows a patch assertion error on the kernel. This means that the installed kernel does not match what the OTA was expecting to find. This is typically indicative of the presence of a custom kernel.
Click to expand...
Click to collapse
I agree it is indicative of a custom kernel but I had the same problem of a device pulled directly out of the box which was unfortunately shipped from Walmart since they were sold out on Google Play at the time. BTW, the box was sealed so unless Asus is shipping refurbished units as new, I don't see how this could have happened. If you google the error for the LNX device error, you will see this is more common that would be expected.
You are also correct that I could have flashed the 4.2.1 factory image, but at that point I wanted to make sure that I could actually get the OTA updates in the future. This showed I could as I was able to get the OTA update to 4.2 and then the subsequent update to 4.2.1.
You don't happen to have the original kernel or kernel information do you? I'd like to take a closer look at it to see what the deal is. Or do you happen top recall the build number that the device was shipped with?
Sent from my Nexus 4
This happened to me today, too.
I got a brand new 32GB wifi Nexus7 from the local electronics store.
Sealed box.
CBO serial
4.1.2 JZO54K preinstalled.
Made the OTA update.
At about half of the progress bar the red exlamation mark symbol came and the device rebooted on its own after waiting 1 minute.
And now 4.1.2 is still installed.
(everything stock and locked)
Can I fix it somehow else, without rooting etc?
Likewise, mines 4 days old and the update just won't install.
I tried to clear the "data" of Google Services Framework. Then did the OTA again but it failed again with the red triangle at about 1/3 of the loading bar.
Here is a workaround which didn't work for me (clearing data of Framework)
http://www.adilhindistan.com/2012/07/upgrading-nexus-s-to-jelly-bean-411.html
I tried it several times, even wiping /cache in stock recovery doesn't help.
I will continue to try the update. And either it will work all of a sudden or I really need to adb sideload the update manually on a fresh locked, unrooted device. Come on Google.
I gave up and flashed mine via ADB there's obviously something wrong with the OTA combined with the Nexus 7 32gb as it only seems to affect this model from looking at the stories.
I went to my local dealer. And after some evaluating and checking. They were able to to connect to their wifi. I then reproduced the failure in the shop. Then afterwards they called ASUS (The salesman let me talk to Asus directly, but they couldn't help, Google is responsible for software). And after this the salesman checked a demonstration model, which already had 4.21.
Then he asked the store manager I guess (at least he wore a suit as opposed to the others.)
And finally they exchanged my model to a new one. Now I have another CBO device but this time it updates flawlessly.
I'm happy.
JayOui said:
I agree it is indicative of a custom kernel but I had the same problem of a device pulled directly out of the box which was unfortunately shipped from Walmart since they were sold out on Google Play at the time. BTW, the box was sealed so unless Asus is shipping refurbished units as new, I don't see how this could have happened. If you google the error for the LNX device error, you will see this is more common that would be expected.
You are also correct that I could have flashed the 4.2.1 factory image, but at that point I wanted to make sure that I could actually get the OTA updates in the future. This showed I could as I was able to get the OTA update to 4.2 and then the subsequent update to 4.2.1.
Click to expand...
Click to collapse
I got my 32gb in December and have had the same problem. Google support said it was an asus issue and of course asus said it was a google issue. Both only had factory reset as a suggestion, which did not work. There seems to be hundreds of users with this issue because I have found tons and tons of people with the same problem, but no real answers. Rooting and flashing is of course a fix but not really a solution. I root my phones, but really do like the nexus as is and like you would want to be able to receive further ota updates without issue. I'm intrigued by your wrong kernal idea. I got mine new from a local gamestop.
I've attached a screenshot of my info. Can you tell me, please, is this the wrong kernal? If so and I follow your steps from the nexus toolkit, what will happen to everything that is on here? Will apps, data, personal file , and settings all be wiped? Are there any backup opttions? Not being rooted I can't use my titanium backup so will a copy to pc get everything?
Thanks so much!
@Sorraia3
That release - JRO03S - seems kind of old for a device which was purchased in December. Setting that aside though, there have been a few reports on here of "pure factory" JRO03S devices that would not properly accept the OTA update.
To know what the exact error condition is, you would either need to show a picture of the recovery screen with the error message, or if there is none, get a copy of the recovery log file (which might require root and therefore poses a chicken-vs-egg problem).
If you don't want to pursue a return/exchange/repair with Google/Asus, you could try identifying the exact problem - but to do that you would need to unlock the bootloader... which causes a full tablet wipe & in any event would be more difficult than just flashing a (new version of the) full factory ROM.
Look at the "return to stock with fastboot" thread for instructions on the latter.
You need to make backups of anything worth saving as the tablet gets completely wiped during this process. You might also want to look into the "Carbon" app for backing up market apps & their data on an unrooted device before you begin.
Also, the fact that you will be unlocking your bootloader does not mean that you need to flash custom ROMs or any other "rooting" activities - you can certainly just re-lock the bootloader after installing the factory ROM, and stay in a "pure stock" condition (with the newer factory ROM).
good luck
I know it has been awhile since I posted in this thread, but I got sidetracked. I'm now going to be taking care of this and was wondering if I can jump right to the newest build or should I graduate up them? If the latter, can someone give me the proper build order? If the former, what is the most current stable build I should use?
Also, I no longer seem to be able to find the thread mentioned "return to stock with fastboot" would you have a link for it?
Wait I think I just found it. Is this it?
http://forum.xda-developers.com/showthread.php?t=1907796
So the recommendation is to go through adb rather then use the toolkit?
Thanks much!
Sent from my Nexus 7 using xda premium

[Q] Having trouble updating to Lollipop

I wonder if anyone can help.
My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).
I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.
The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.
I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.
SimonP2 said:
I wonder if anyone can help.
My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).
I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.
The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.
I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.
Click to expand...
Click to collapse
I would flash the factory image using fastboot to 5.0.1. You'll have to unlock the device again. I'm not a fan of tool kits
Sent from my Nexus 9 using XDA Free mobile app
SimonP2 said:
I wonder if anyone can help.
My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).
I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.
The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.
I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.
Click to expand...
Click to collapse
In the toolkit options enable "Force Flash Mode" and try again; this will fastboot flash the img files individually and overcome the issues with Google's new Lollipop factory packs, where the fastboot update cmd, is not working properly (as written in their own incldued flash-all.bat).
In the future.. rather than PM'ing me and making a thread.. just post in the NRT threads.
{{ WugFresh }}
It took a lot of fiddling about and several boot loops but eventually I managed to install 5.0 (using NRT) and it updated to 5.0.1 (which is what I wanted to see to be sure it was working alright before I sell it) so all is well at last. Thanks for the suggestions.

SM-G870A Failing to Update Past 4.4.2

Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.

My 6P WILL NOT update to 7.0

Long story short, my Nexus 6P will not update to 7.0. I just got the OTA update notification today but when I downloaded it and waited forever for it to optimize my apps, my phone boots into 6.0.1. I tried getting 7.0 from the android developer program about a month ago and I was able to download it then too, but again, the phone just goes back to 6.0.1 for some reason. I decided to just wait until I get the OTA but the problem has still persisted. Any ideas on why its stuck on 6.0.1? Any way to fix this?
Also, I bought this phone about 1 and a half months ago used from eBay. It has been working perfectly fine. Just wanted to put that info out there.
It's possible you bought the phone rooted and/or with a custom ROM or recovery? If you aren't completely stock, an OTA update will fail. This isn't necessarily a single 'right' answer question, but you should probably flash the factory image for a completely fresh install. Grab the factory image at https://dl.google.com/dl/android/aosp/angler-nrd90u-factory-7c9b6a2b.zip and follow the guide, section 14 at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and you should be able to update.
I just got the 7.0 OTA myself completely stock and when it rebooted it's still on 6.0.
Nobody else is having this problem?
I think you've both misread the update info. I received MTC20L update yesterday, which said that it contains September security patches and also prepares the device for Android 7.0.
The update never claimed that your device will update to Android 7.0. But don't worry, we'll get it soon, at least I hope so!
MTC20L is the Aug security update and the factory image has been posted for 1.5 months, so odd that you're getting it now. Most people would have been receiving N OTA updates. The only way for us to guess what is going on with the OP is if he edits it to include the build number.
I also just got MTC20L yesterday.6.0.1. No idea why no 7.0. Waiting sucks..........It's been a month since "rollout".
It's true I didn't read what the update was yesterday, but I'm 95% sure it had something with "7.0" on there. How do I know what I installed yesterday? I'm on 6.0.1, with the Sept 6 security patch, and MTC20L.
MTC20F was the August update, MTC20L is September one, released 6.9.
I took the developer preview (mistake as it was a hassle that I had to fix) but remember guys, Android N updates in the background, so while it reboots to update, it doesn't take forever with the whole "android is upgrading" screen. I got the NRD90T OTA yesterday (wierd because the NRD90U is on the webpage) and later in the day I gave it a reboot just the set it straight again. I forget the actual wording but there is a secondary partition for updates so they do it in the background, and then revert back after a reboot.

Unexpected Update: N950USQU8DVB1 2022-02-22

My Verizon Note 8 just received an update (N950USQU8DVB1) but I had thought that the phone was out of support and was not going to get any more updates. I don't see mention of this one on the Verizon update page. Does anyone know what this is about and why we are getting an update after the support window is over?
Hmmm. Just got the Verizon update also..it does show on web page now as available.
No idea why this came in a year after support ended...lots more than just security updates it seems. Glad I kept it
Can anyone confirm if this update made voLTE available?
Does anyone have the files available yet to download and flash?
I don't see them on sammobile.com yet, but I would like to get a copy if anyone can help.
This updated broke my phone. I updated last night and now I have a "No sim card" message. I took my phone to a repair shop and they couldn't fix it. They suggested maybe a flash/roll back, but they wouldn't do it for me. My phone was perfectly fine before I updated. Good times..............
Try booting to recovery mode and wiping the cache partition. My friend had a dual sim version and sim not found message happened to him, wiping cache and double checking network was set to auto fixed it for him.
Another method may be trying to connect to windows and download Verizon software assistant and select repair phone. Takes a while to download everything so be patient until it finishes. I recall it took a half hour. Hope it helps.

Categories

Resources