My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks
Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?
Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0
Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.
Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?
My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app
Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!
chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.
I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.
newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.
My phone won't turn on and is stuck on loading screen after trying to download an Asus update.
I didn't mean to install the update as i knew a problem would occur. I have the 2.3ghz version of the phone with 64gb of storage with Lollipop.
When i try to go into recovery it says it is installing update for a couple seconds then it gives an error so i can't get into that.
Can someone help me and give detailed instructions on what to flash and how to flash something to my phone via ADB or something?.. The phone is also rooted obviously
I gave as much information as i can think of right now.
I greatly appreciate any help. I have looked at some threads but I don't know how or what to flash and if it even relates to my phone at all.
This is what I've looked at so far:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
http://forum.xda-developers.com/zenfone2/help/phone-wont-boot-update-t3126603
Thanks , Austin
try to reflash again the system.img or firmware and use this for rooting make more easy https://drive.google.com/file/d/0B936USMlQhtKbmZLZDE3N1JMazA/view
Thanks for the fast response . But how may i flash this to my phone? And is that toolbox for the zenfone 2?
Nevermind i figured out how to flash the image and that type of stuff.. But idk what image i should flash. I go to the Asus website and find the latest version which is 2.20.40 but on the XDA post it has like 2.13.10 or the lower versions.
Would it be ok to flash any system image to it? Mine has 2.19.40.22 on it right now when i checked in recovery. ( Which i got working , It was giving an error)
Thanks
Hmmm
Trying to flash the firmware to the phone and in adb it says it cannot read the firmware. I literally copy and paste and try almost everything and it says it cannot read it still. I don't know what to do if anyone can please help.. Been stuck without a phone for days :/
I typed adb sideload UL-Z00A-WW-2.19.40.22-user.zip and it will not read it or do anything.
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
I can flash stock images supplied from Google with no issue, but the big issue here seems to be when I try to install any OTA update, specifically (in this instance) the Marshmellow update.
I always hit "Reboot and Install". It always shuts off and gives me the little android robot with his antennas wiggling, and it shows a progress bar while saying "Installing system update..." and about 1/4 into doing so, everything stops, the Android robot is now laying down with his little chest open, and a big red exclamation icon is popping out, and under him it just says "Error!"
And that's it. The tablet will just stall there for about a minute and then reboot itself. The OTA will re-download itself and I'm back to square one.
I have no idea why it's doing this, or if I did something wrong in the unrooting process, or how to make this stop.
Please help T_T
EmperorOfNyte said:
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
I can flash stock images supplied from Google with no issue, but the big issue here seems to be when I try to install any OTA update, specifically (in this instance) the Marshmellow update.
I always hit "Reboot and Install". It always shuts off and gives me the little android robot with his antennas wiggling, and it shows a progress bar while saying "Installing system update..." and about 1/4 into doing so, everything stops, the Android robot is now laying down with his little chest open, and a big red exclamation icon is popping out, and under him it just says "Error!"
And that's it. The tablet will just stall there for about a minute and then reboot itself. The OTA will re-download itself and I'm back to square one.
I have no idea why it's doing this, or if I did something wrong in the unrooting process, or how to make this stop.
Please help T_T
Click to expand...
Click to collapse
I have the same problem
I actually was about to start a new thread near exact to yours.
EmperorOfNyte said:
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
Click to expand...
Click to collapse
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
airberger said:
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I don't want to flash it manually, and I want it to be able to install OTAs normally because I'm trying to sell it to a friend and don't want them to constantly to be seeing a "Update Available" notification that wont go away.
Nothing? No ideas? ......Anyone?
airberger said:
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I tried this using ADB sideload, got "signature error"??
Hello everyone here, im a noob around these parts but hope that this beautiful community might help me.
So heres the deal, my gf got an xperia m, that outta the blue started acting out, what i mean for this is, rebooting, outta nowhere and eventually a couple of days later it died.
Making my investigations to get to the problem and therefore the solution, she stated that putting it on the SUS or SONY Pc Companion didn't help at all, plus keep getting error 0x0000067 or 0x000007d5 on PC Companion.
After seeing this, she says tried to unlock the bootloader to install a CWM 6.0 for the 15.4.A.1.9 software, wich it had running, didnt got through since the moment she enter the command through fastboot to check the bootloader status throgh the command fastboot flashing get_unlock_ability but no response just stuck on three dots.
Also tried to flash through FLASHTOOL installing the drivers and everything as ive done with other decives checking everything is okay, which they are, since ive succefully recovered an brick C1904 using CWM with a previous Backup, but the tool gets stuck on flashing loader and wont give a percentage.
Tried Flashing remotely the CWM.img to the boot, but it wont flash, always failed, as for specifics about the code, If really needed ill post them on the next reply.
Hope Someone can Help me,
Regards Jmaquilon
Which error are you getting while flashing the recovery? is it something like remote command not allowed ? If it is then try to flash the recovery in the boot partition (I have done the same many time cuz there are some problem s with my current kernel)and what happens is instead of system the recovery boots up ..
If this doesnt works then try xperiafirm it may bring your phone back to life!
Hope it helps!
Just flash stock rom using flashtool software. Download the Stock Sony Xperia M Rom here http://forum.xda-developers.com/showthread.php?t=2699085 and flash it using flash mode in flashtool. Good Luck
Hello All,
I was excited too about the new update but sadly I am unable to update to it. I downloaded the update but when the device rebooted it gave me an error.
I don't have the screenshot but it was the white screen with green android and red text saying there was an error.
I had recently unlocked the bootloader successfully but was unable to get the TWRP installed even after multiple attempts ( I think a corrupted version of TWRP is installed). Since the device was working fine and I didn't want to brick it, I let it be and kept on using it. Until today, when the update came and I am unable to get it.
Any idea how I can get back to the state my phone was before I messed it up. Please note that I am unable to get the TWRP installed even after multiple updates.
Will the Huwai Suit help in that?
Thanks for reading.
Cheers!
Well that's just sad to hear!! I don't exactly know what happened...am saying this because my phone's bootloader is also unlocked...i updated yesterday only and all went fine...
dsmith16 said:
Well that's just sad to hear!! I don't exactly know what happened...am saying this because my phone's bootloader is also unlocked...i updated yesterday only and all went fine...
Click to expand...
Click to collapse
I think it's because of the incorrect installation of TWRP. I tried installing TWRP multiple times and it started giving errors. Since my phone was booting properly and I did not want to risk bricking it, I left it as it was and continued using the phone.
Is there any way we can either un-install TWRP and lock bootloader again. ?
Update: Huwai suit didn't help.