[Q] Having trouble updating to Lollipop - Nexus 4 Q&A, Help & Troubleshooting

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.

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

VZ LG GPad 8.3 OTA VK81024A

04/17/2015 Update to this posting; -24A OTA rooted 1st time using Stump after dozens of Brute Force fails on 23A-
Can anyone else confirm Stump Root working for 24A on their own devices?
Original Stump Thread; http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
New OTA software update VK81024A just released this week. From what I've read and VZW's PDF, the only thing that was changed was 4G LTE coverage. In my experience with Verizon, they only release updates for this device to patch root methods and add bloat. This would have been my 3rd update to my GPad (had I accepted) without measurable positive impact. I personally cannot believe that they spent the time and money to fix LTE coverage that, in my experience, had no noticeable issue to begin with.
I would still be waiting for Lollipop on my VZ G3, if I didn't go ahead and root/ROM just last month. With the Lollipop ROM being available to the Korean G3 as early as November of LAST YEAR, my faith in Verizon getting us the updates we want and deserve (I purchased a flagship phone, and a popular tablet) is nonexistent.
Okay, I'm done ranting (for now) about the "Great Satan" that is VZW...the only carrier with good coverage here in my area of NY. Does anyone have any experience with this update? Anyone try rooting it (maybe Stumproot will start working again)? I am tempted to accept it if I could assist the community by doing so. Please tell me your thoughts.
VK810 OTA update from 23A to 24A keeps root
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf
Just got mine this morning. Hadn't been using the tablet for a few days. Would not take OTA. Downloaded the file but kept kicking an error. Ended up hooking it up USB and using the upgrade assistant. Paranoia got the better of me and I "unrooted" first. Brute force stump (climbed to 6800 I think) did the trick just like before. Must say I was disappointed. I had not read what the "upgrade" consisted off but figured since they jumped from 23A to 24A it would be something substantial. I notice some minor cosmetic changes but that's about it. The 4gLTE "Update: or "Upgrade" isn't going to make much difference in my neck of the woods. 3G is about the best you can hope for here in this little town for the time being.
DeanGibson said:
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf
Click to expand...
Click to collapse
Did the same thing as you, OTA installed and still rooted
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
On every Android device, if you want to take an OTA, you have to either be 100% stock, or at least have stock recovery, kernel, bootloader, and other partitions, and only have done minor things with the system partition - not have debloated at all.
Sent from my VK810 4G
Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
If the LG Mobile Support Tool factory restores the whole phone (recovery included) then this may be the best option till someone posts the KDZ with rooted 24A. This was my root method and it may work for you.
After searching through forums for weeks looking for viable root options (rollback and Purplerake or Towelroot, ADB scripting, and all others) and running Stump as often as I remembered (probably 30 times on 23A) I finally have it! I didn't see any up to date threads on rooting the VK810 and all the old threads had too many broken links to actually perform the steps.
Here's how it went down;
1.) Installed the latest LG USB drivers from LG's site ( http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427 ).
2.) Download LG Mobile support tool ( https://docs.google.com/file/d/0B687...p2NlhhalU/edit ).
3.) Run the LG Mobile Support Tool program.
4.) Switched tablet USB mode to "Internet Connection / Ethernet" and after a few moments the LG Tool recognized my VK810.
5.) In LG Tool, click on "Options -> Upgrade Recovery" on the upright corner.
6.) It should start downloading stock firmware right away, if it says "Downloading" but there is no file size or progress, then you need to disable firewall.
7.) After the download, it will start "Upgrading".
8.) When the tablet rebooted I was on the latest VZW VK81024A which shocked me because I thought it was going to put the factory image (JB 4.2), but not to give up hope, I retried Stump...1st time rooted the thing!
9.) Followed Stump Root's directions (Reboot after app tells you to, Install SuperSU APK from market, Uninstall StumpRoot) and poof!
10.) Enjoy rooted 24A KitKat
It is very possible that 24A broke the fix VZW had for 23A (even though many people had success with 23A) and one need only take 24A OTA to Stumproot if they were not able to prior, but this is how my experience went down.
MANY thanks to @roirraW "edor" ehT, @jcase, & @jim380 for producing the threads and software that led to my rooting.

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.

WARNING - Do not use OTA to get Android N Beta Preview before reading this!

UPDATE: Solution below!
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
UPDATE: Google posted signed OTA zips that can be used to recover from this situation. You can now use adb sideload to side load the full OS in OTA form. Go to https://developer.android.com/preview/download-ota.html to download.
Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.
kalinskym said:
Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.
Click to expand...
Click to collapse
If you unlock the bootloader and enable USB debugging prior to installing the Android N preview (via OTA), you should be fine. You're essentially leaving yourself a backdoor to flash the factory image should the OTA fails.
Yes, I wish I know this earlier, and now I have a bricked Nexus 9 with me. :sad
Ouch, had that issue and went here looking for help. Should have waited before I tried it ?
THIS IS CRAZY! OTA should work :-\
So crazy to hear that you are all having the same issue with the Android N Developer Preview on Nexus 9!
I have had exactly the same experience today when I enrolled my device for the OTA. It downloaded and started to install fine, but got stuck with the android on his back with the red exclamation mark. It then rebooted and is now stuck on the Google logo. I have tried using adb to push files, factory reset/wipe cache & nexus root toolkit. However, I had NEVER set the OEM unlock option and that seems to have left me stuck!
I'm hoping someone will figure out an amazing fix! Just in case no one does, I called Google and as I purchased it from the play store they have offered me a replacement. Sadly I'm living in Thailand and they can only arrange it to my home country, Australia. So sorry they wouldn't help you Naddie
I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?
sashinde said:
I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?
Click to expand...
Click to collapse
Gee, I hope we're still on MMB29V... But since the OTA seemed to have failed during the update, the system partition may be partially whatever build this Android N preview is and partially MMB29V - which is to say ... It's completely borked for ANY OTA update to fix it via side loading.
Does anyone even have the OTA zip for MMB29V to N preview for we poor souls to try?
Sent from my iPad using Tapatalk
Hello. Sorry for my english. The same from here. I called Google and they offered me a replacement. I said yes. Waiting for a new Nexus 9. I hope you will find the solution.
Enviado desde mi Nexus 6P mediante Tapatalk
Naddie, have you contacted HTC or Google yet about getting a replacement?
My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.
I tried updating via the beta program, but there was an error and now my Nexus 9 is softbricked. I can get to fastboot and recovery, but can't boot into Android. And, worst of all, I don't have USB debugging enabled, so I can't do an ADB flash or even OEM unlock.
Can anyone help me out?
naddie said:
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
Click to expand...
Click to collapse
Nexus 9 is FAMOUS for OTA's failing and leaving you with a "brick".
The good news is that the sky IS NOT falling, even with the bootloader locked and debugging OFF, you can still recover it. All you need to do is reboot into recovery, and "adb sideload" the update.zip again.
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
greiland said:
My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.
Click to expand...
Click to collapse
The switch unflips every reboot anyway, so that wouldn't have helped you to begin with.
What "Update" would I sideload? I did my original update via OTA.
Fixed Brick on Nexus 9 OTA Android N update
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !
Good to know. I just signed up for the beta program. My bootloader is unlocked from day one because I always flash the stock image of the security updates. The USB debugging is on
Sent from my Nexus 6 using Tapatalk
inthelandofnod said:
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !
Click to expand...
Click to collapse
Can you please explain more detailed? Are you sure it's volume up because recovery is volume down. And what to do then in recovery?
Please, give us more info!!!!
Enviado desde mi Nexus 6P mediante Tapatalk
I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?
So this might be resolvable if someone has found the Android N OTA...
srideep said:
I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?
Click to expand...
Click to collapse
OTAs won't apply if you don't have stock recovery.

Question about 6.0.1 Update for Verizon S5 that is on Straight Talk

Hi all,
A couple quick questions here. I've done some reading up, but most of the information is more in depth than I need at the moment so I'm looking for some quick answers.
My SO has a Verizon S5, that has a locked bootloader, is not rooted, and is still on 5.0.
She swapped carriers a while back, so is no longer on the Verizon network. The IMEI is clean, and her Verizon account is fully paid, and everything on the phone works fine, aside from it being stuck on 5.0.
It will not update via the automated system, because I assume it's trying to reach out to straight talk for the update and gets a response that it's on the newest version.
I downloaded the Verizon OTA update file (approximately 1 gb) for 6.0.1. It's named update.zip to allow for automated updating.
Here are my questions:
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
Thank you very much for your assistance!
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
jesimpki89 said:
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
Click to expand...
Click to collapse
Thank you very much for your thorough response. It sounds like it will be a nice smooth flash, and I will use the full Odin version instead of the OTA file, to ensure it goes through comfortably.
Odin looked like it wanted to wipe the apps, so I ended up using the stock recovery/installer that's built in, and placing the OTA update file on the external SD card.
That worked like a charm. It took a bit, as expected, but all of the apps and info were ok after.
The only thing I can't sort out is why I can't find an option for the "Themes" setting in touch wiz. Any suggestions? I realize I could have her go to a third party launcher, like nova, but I have all of the theme options on my note 3, that's ported to MM note 5, and the theme option is still right there in the settings list, per normal. Maybe I'm just not seeing it, but I couldn't find an option on her S5 during 5.0, or now on 6.0.1. Is that something they never updated for the older phones?

Categories

Resources