Hey guys!
I've tried to update my android 2.2 to gingerbread, both with the official update and the oxygen update, with the same result: my phone reboots, starts doing something - I get a green statusbar - and after about 1/4th of the bar it all ends up with a phone with a read exclamation mark and a red triangle.
The first time I got there, I though this was something that should happen, and left my phone around for two hours without anything happening.
I googled around and ended up doing a hard reset, which didn't change a thing.
I then tried to go into recovery mode from the boot meny, and end up with the exact same result.
So... what the hell is happening? Anyone got a clue? I would really appreciate some kind of sollution!
Its probably because you have a corrupted update file.
Try downloading it again.
If your branded to a certain carrier, then download the update for that carrier.
I've downloaded the update each time I've tried to make the update. I've tried with the oxygen ROM too, and tried loading recoverymode both from boot menu and clockworkmod. Nothing works. Amen...
So let me get this straight, you are trying to do OTA updates with a custom ROM + clockworkmod!?
It does not work like that. OTA updates are ONLY for 100% stock phones (ok, you can have Radio S-OFF, but no root). As you are using a custom ROM, why don't you just flash a Gingerbread based ROM instead of trying to mess around with OTAs, which obviously is impossible?
Uh, well, I have the standard ROM, but I did not know that it's impossible to install OTA updates when my phone's rooted. But it obviously doesn't work out
I've tried with the oxygen gingerbread release too, but same **** as I described in my original post happens. So what I've done:
- Install OTA update - failed
- Install oxygen-rom - failed
then, Hard reset +
- OTA update, without root - failed
- go into recovery mode from boot-menu - failed
hard reset + root +
- oxygen gingerbread - failed
- recovery mode from boot meny - failed
- recovery mode from ROM manager - failed
I really hoped that a hard reset would do the trick, but there you go...
Again, you cannot get any OTA because you have ClockworkMod.
Sent from my Desire HD using Tapatalk
So... How do I get any update if I can't install Oxygen either? (assuming Oxygen's ROM also qualify as OTA...)
Flash this ROM from CWM Recovery like any other ROM. Its Gingerbread with root, nothing else added.
Thanks!
But I'm still having serious problems getting into recoverymode, or even backing up my existing ROM. It seems whenever I do ANYTHING that requires my DHD to reboot, it ends up with the phone-with-red-eclamationmark-sign. No matter if I've done a hard reset either...
Holene said:
Thanks!
But I'm still having serious problems getting into recoverymode, or even backing up my existing ROM. It seems whenever I do ANYTHING that requires my DHD to reboot, it ends up with the phone-with-red-eclamationmark-sign. No matter if I've done a hard reset either...
Click to expand...
Click to collapse
The red exclamation mark is the stock recovery, so you dont have clockwork recovery. I would recommend starting from scratch installing clockwork then all should be good
Oh, nice to know But I used ROM manager to flash clockwork recovery (at least it said so).
When you say start form scratch, would that imply hard reset, root it, flash CWR and hopefully it will work?
Holene said:
Oh, nice to know But I used ROM manager to flash clockwork recovery (at least it said so).
When you say start form scratch, would that imply hard reset, root it, flash CWR and hopefully it will work?
Click to expand...
Click to collapse
Yes, you did S-off? As that would explain why clockwork didn't flash
Oh, well, uhm.
No.
Damn Thanks!
I have a sprint phone and am trying to update my phone to 4.2.2. A few months ago when I first got the phone I had attempted to root it. Long story short, it totally didn't work (i accidentally installed verizon root), had to use odin to reinstall my radios and whatnot. In the end, I decided to just not root my phone.
However, I think i am screwing my phone up to the point that it won't update. Whenever I try to let it update, it goes into (what i imagine) is the recovery mode where it shows a picture of the android bot with a red alert sign as if there is an error. Furthermore, I went in to fastboot and tried to go to recovery but can't (it shows that same android with it's front open and an error sign on it).
I am not even sure where to start here. Any advice? I tried to reinstall my recovery using the nexus toolkit but that didn't work.:crying:
do this: http://forum.xda-developers.com/showthread.php?t=1626895
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.