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.
Hello, I have just received my Zenfone 2 today. I bought it from a Chinese website. It comes with 32GB ROM and 4GB RAM. It has all the Google Services installed even when you try to reset it they are still installed. Everything is working fine, except when I try to disable an application the phone reboots after I click "OK" and the application doesn't actually disable, that's the issue I'm having at the moment. But for the question, I was wondering how could I update my phone? Is there anyway to update it automaticly or do I have to upgrade it using USB Cable. If so, wich version (CN or WW) that I should install when Updating? Because when I asked the website they said it is CN and when I got to About device and go to build number it says WW.
I think they have flashed it to WW firmware to get the Google Apps. I'm not really sure! But wich updates should I install thought? And I also don't get the "Check for update" button.
Anyone? Please help
ClarnTV said:
Anyone? Please help
Click to expand...
Click to collapse
I think you can just download the latest WW stock manually (as once you are with WW, the device expects it), rename to MOFD_SDUPDATE.zip on the root of your MicroSD card and then reboot to recovery to allow it to get picked up.
Hope this helps.
joel.maxuel said:
I think you can just download the latest WW stock manually (as once you are with WW, the device expects it), rename to MOFD_SDUPDATE.zip on the root of your MicroSD card and then reboot to recovery to allow it to get picked up.
Hope this helps.
Click to expand...
Click to collapse
Thank you so much for your reply. Well the device says that it is CN when I go to recovery mode, even the packaging that came with it such as the manual is in chinese. Even the website says it is chinese version. But for some reason it has the Google apps installed just like the WW even if you factory reset it. Wich one should I pick then? CN or WW to update my phone. And for the build number there's WW not CN
ClarnTV said:
Thank you so much for your reply. Well the device says that it is CN when I go to recovery mode, even the packaging that came with it such as the manual is in chinese. Even the website says it is chinese version. But for some reason it has the Google apps installed just like the WW even if you factory reset it. Wich one should I pick then? CN or WW to update my phone. And for the build number there's WW not CN
Click to expand...
Click to collapse
I am going by this:
mhp1995 said:
4) Changing from CN to WW version
Credit goes to: vivix
Please follow these steps to change your firmware from CN version to WW version:
NOTE: PLEASE DOWNLOAD THE CORRECT RECOVERY IMAGE...
ZE550ML = Z008
ZE551ML = Z00A
Download the latest recovery image (For Z00A=2.19.40.22 , For Z008= 2.19.40.13) from http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
Boot to fastboot mode (Power + Vol Up)
Using ADB command prompt flash files by using fastboot commands :
Code:
[/B][/FONT][CODE] [FONT=Century Gothic][B]fastboot flash recovery recovery.img
[/B][/FONT] [FONT=Century Gothic][B] fastboot flash boot boot.img
[/B][/FONT] [FONT=Century Gothic][B] fastboot flash fastboot droidboot.img
[/B][/FONT]
[*]Reboot phone
[*] Download the latest OTA... For Z00A= 2.19.40.22 click here ......... For Z008=2.19.40.13 click here
[*]FOR Z00A users: Rename OTA file from UL-Z00A-WW-2.19.40.22-user.zip to UL-Z00A-CN-2.19.40.22-user.zip to get notification about update available.
[*]FOR Z008 users: Rename OTA file from UL-Z008-WW-2.19.40.22-user.zip to UL-Z008-CN-2.19.40.22-user.zip to get notification about update available.
[*] Update via notification about new update available
[*] Wait till update will finish (approx 10 min)
Click to expand...
Click to collapse
Seems, depending on how they did it, they may have flashed the WW recovery as well. If not, you can still do that (step 3).
joel.maxuel said:
I am going by this:
Seems, depending on how they did it, they may have flashed the WW recovery as well. If not, you can still do that (step 3).
Click to expand...
Click to collapse
Hi, thank you so much for helping me out joel.
Well, I'm actually new to this I have no idea what all this is.
How to install the OTA thought? After downloading Z00A OTA and renaming it what should I do?
ClarnTV said:
Hi, thank you so much for helping me out joel.
Well, I'm actually new to this I have no idea what all this is.
How to install the OTA thought? After downloading Z00A OTA and renaming it what should I do?
Click to expand...
Click to collapse
From there, turn the phone off, and wait a minute.
Then, hold down the vol-up button, and press the power button holding that too.
When the phone starts to vibrate, can let go of power, but keep holdin onto vol-dn until you get to Fastboot (first screen past the splashscreen).
Press Volume-Down twice, and press the power button again. As long as the downlaod is renamed and on the root of the MicroSD, recovery will now open, and start to process the update.
my phone stopped startup after latest OTA firmware update this morning. It stuck on bootloop screen. Tried reboot a lot of times, w/ and w/o charging cable (100% charged), but still no luck.
Any idea/advise please? Thank you.
You can go to recovery and try format cache partition
Install the last big update (firmware) from ASUS website on your device. Be careful about ww/cn etc. Use manual OTA updates after that too update your phone... Here is a good tutorial, helped me a few times as well. Feel free to ask if you have more questions.
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Have you had a root access ?? If yes had you did full unroot before applying ota ?
Hi! I have a big problem with my A5 2017. Today my phone pop-up the Oreo update, so I was decided to install it (finally!). First of all, I want to appoint that I have bought this phone from the carrier Claro in Argentina. Everything was fine, it downloaded the 1.56 GB of the OTA update but the problem was during installation. It got stuck at 32%, it failed. It rebooted and then an error message pop up to confirm to send to Samsung. I pressed yes and I gave it another shot and again stuck at 32%. Since I wanted to have Oreo so bad, I opened Smart Switch to update it with my laptop and the USB cable. Here's where all the drama began, Smart Switch recognized my phone and the new update, I pressed yes and I waited for the download. Everything was fine, I though that I was going to have Oreo on my phone. It began installing the update and all of the sudden it got sutck at 92% and again an error appear on screen. I pressed ok and this time there was another message saying that I have to use Emergency recovery option from Smart Swicht, I thought there wouldn't be a problem but when I procceded I had to past a code to recover my phone which I did but then it took 4 hours to download the emergency firmware to recover the previous firmware. When everything was set to installation the progress bar got stuck again at 90% this time. Now, I don't know what to do, I have this permanent message on screen "An error occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." I can't turn off my phone, I can only use the download mode. So my question is what Software do I have to flash in order to recover my phone? I'm downloading the Oreo update (which gave me problems before) but honestly, this is the first time that happens something like that. Do I have to flash Nougat like I had? I'll trip knox I guess but right now I can only think off flashing the lastest firmware through Odin. What would you recommend me to do? Thanks in advance!
pavelvlach said:
Hi! I have a big problem with my A5 2017. Today my phone pop-up the Oreo update, so I was decided to install it (finally!). First of all, I want to appoint that I have bought this phone from the carrier Claro in Argentina. Everything was fine, it downloaded the 1.56 GB of the OTA update but the problem was during installation. It got stuck at 32%, it failed. It rebooted and then an error message pop up to confirm to send to Samsung. I pressed yes and I gave it another shot and again stuck at 32%. Since I wanted to have Oreo so bad, I opened Smart Switch to update it with my laptop and the USB cable. Here's where all the drama began, Smart Switch recognized my phone and the new update, I pressed yes and I waited for the download. Everything was fine, I though that I was going to have Oreo on my phone. It began installing the update and all of the sudden it got sutck at 92% and again an error appear on screen. I pressed ok and this time there was another message saying that I have to use Emergency recovery option from Smart Swicht, I thought there wouldn't be a problem but when I procceded I had to past a code to recover my phone which I did but then it took 4 hours to download the emergency firmware to recover the previous firmware. When everything was set to installation the progress bar got stuck again at 90% this time. Now, I don't know what to do, I have this permanent message on screen "An error occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." I can't turn off my phone, I can only use the download mode. So my question is what Software do I have to flash in order to recover my phone? I'm downloading the Oreo update (which gave me problems before) but honestly, this is the first time that happens something like that. Do I have to flash Nougat like I had? I'll trip knox I guess but right now I can only think off flashing the lastest firmware through Odin. What would you recommend me to do? Thanks in advance!
Click to expand...
Click to collapse
You can get out of download mode by holding volume down and power button until screen goes black. If it was me, I would download the latest oreo firmware for your model and flash it in Odin. If that didn't work I would huck it across the floor. JK
iloveoreos said:
You can get out of download mode by holding volume down and power button until screen goes black. If it was me, I would download the latest oreo firmware for your model and flash it in Odin. If that didn't work I would huck it across the floor. JK
Click to expand...
Click to collapse
Yes, I did it. I've managed to download the lastest firmware, oddly the one that won't install via OTA or Smart Switch. I was wondering if I can flash an unbranded version from my country the next time, I couldn't do it the last time with Nougat. How can I do it if my phone is from a company? Thanks for your answer!
I hope this post help if someone has the same issue after updating an erroneous firmware from Samsung servers via OTA or Smart Switch. My company is Claro from Argentina. My solution was to download the latest firmware from sammobile's site and flash it though Odin. This phone with Oreo is amazing! Cheers.
pavelvlach said:
Yes, I did it. I've managed to download the lastest firmware, oddly the one that won't install via OTA or Smart Switch. I was wondering if I can flash an unbranded version from my country the next time, I couldn't do it the last time with Nougat. How can I do it if my phone is from a company? Thanks for your answer!
I hope this post help if someone has the same issue after updating an erroneous firmware from Samsung servers via OTA or Smart Switch. My company is Claro from Argentina. My solution was to download the latest firmware from sammobile's site and flash it though Odin. This phone with Oreo is amazing! Cheers.
Click to expand...
Click to collapse
It should work to flash unbranded firmware, but I am not sure what would happen with your CSC. Personally, I would stick with the right one. But if you you want to change CSC to unbranded, there is a tutorial somewhere on XDA.
Hey everybody,
Today I decided to disregard all of my warnings about the Huawei Firmware Flasher and downloaded the latest available EMUI 10 ROM 10.0.0.168 supposedly for the Mate 20 x
The flash went fine (like never before) but after the reboot, I am greeted with a message that says: "your device has install another operating system" and a link supposedly for recovery instructions.
There are 3 options to chose from below the message. one of them is wait 5 sec and the device will continue booting, another is to press the Vol Up for 3 secs to go to the Recovery and the third one was reboot if I'm not mistaken.
If I leave it, it shows a booting message but nothing happens for a while and then the device reboots to the same message.
Recovery option works but trying the erecovery produces an error trying to locate firmware.
Tried factory reset, no change.
Tried flashing older firmware (one that I did not had issues before) and it gives an error the moment the flashing tries to start.
My bootloader is still locked...
AL00 8/256
Ideas?
I think its because you installed a beta version winch is coming for every specific phone using its IMEI number. so, the rom was flashed but will not work because its not pushed for your phone.
Unfortunately, downgrade from android 10 is not easy to go back to your official old rom.
My suggestion is to wait for few weeks until they release official EMUI10, it should resolve this Softbrick.
OrionBG said:
Hey everybody,
Today I decided to disregard all of my warnings about the Huawei Firmware Flasher and downloaded the latest available EMUI 10 ROM 10.0.0.168 supposedly for the Mate 20 x
The flash went fine (like never before) but after the reboot, I am greeted with a message that says: "your device has install another operating system" and a link supposedly for recovery instructions.
There are 3 options to chose from below the message. one of them is wait 5 sec and the device will continue booting, another is to press the Vol Up for 3 secs to go to the Recovery and the third one was reboot if I'm not mistaken.
If I leave it, it shows a booting message but nothing happens for a while and then the device reboots to the same message.
Recovery option works but trying the erecovery produces an error trying to locate firmware.
Tried factory reset, no change.
Tried flashing older firmware (one that I did not had issues before) and it gives an error the moment the flashing tries to start.
My bootloader is still locked...
AL00 8/256
Ideas?
Click to expand...
Click to collapse
Try this to me I happen the same after 2 attempts I gave with the correct sign and now I am with emui 10 https://r.tapatalk.com/shareLink/to...7&share_fid=3793&share_type=t&link_source=app
Enviado desde mi EVR-L29 mediante Tapatalk