Last month I got the update from Android 4.4.4 to Android 5.
I have had problems in the past updating an ASUS Transformer Pad 300 when the update made my device worse and ASUS stopped doing updates. This forced me to learn how to root my ASUS device and install a custom ROM.
Seeing as I got burned installing an OTA update I wanted to ROOT my Nexus 4 and back it up before completing the update to Lollipop. So I followed the instructions from Cynogen Mod Installer. The instructions sounded straight forward in that I followed the on-screen instructions. However all I managed to do was wipe my phone, and from what I can tell DID NOT install any Cynogen Mod Installer.
http://beta.download.cyanogenmod.org/install
Today I have now done two Factory Resets of my Phone to Android 4.4.4. I also get OTA update requests. Each time I try to do the update, I get a message saying that my phone needs to Reboot to continue the procedure.
The phone reboots, and I see the little android robot on his back with a progress bar. When the progress bar reaches the end, I get an error message simply saying 'error'. I then have to hold the power key till the phone shuts down. When I turn the phone on again, I never get any requests to update to Android 5.
Have I done something horribly wrong and that I will never be able to update my Nexus 4 phone?
Instead of doing the factory resets, have you tried flashing the stock images through fastboot? That might fix it.
lolcakes203 said:
Instead of doing the factory resets, have you tried flashing the stock images through fastboot? That might fix it.
Click to expand...
Click to collapse
How do I do that please?
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Here is a great guide to return back to pure stock.
Related
I got my OTA update today, unfortunately something went wrong. I told it to install now, and the screen with the android and caution symbol showed up. After 10-15 minutes I hit the power button. I wasn't sure if I was supposed to wait for that screen to clear or if that screen wasn't a good sign. Well hitting power took me to recovery and said that there was an error with the install.
What did I do wrong. Was I just supposed to wait longer? I had previously rooted my phone with unrevoked, but was running the stock ROM, should I have unrooted it? Was it some other error?
Any insight into what happened so when the update comes back around I can do it right. Also is there anyway to get the OTA update back, or do I just have to wait patiently again.
jaredkent said:
I got my OTA update today, unfortunately something went wrong. I told it to install now, and the screen with the android and caution symbol showed up. After 10-15 minutes I hit the power button. I wasn't sure if I was supposed to wait for that screen to clear or if that screen wasn't a good sign. Well hitting power took me to recovery and said that there was an error with the install.
What did I do wrong. Was I just supposed to wait longer? I had previously rooted my phone with unrevoked, but was running the stock ROM, should I have unrooted it? Was it some other error?
Any insight into what happened so when the update comes back around I can do it right. Also is there anyway to get the OTA update back, or do I just have to wait patiently again.
Click to expand...
Click to collapse
You can not update a rooted phone. Go to my post on updating 2.2 made easy and you canupdate to 2.2 and reroot the phone. This is the OTA update.
I'm sort of in the same boat. I had rooted with unrevoked and was running cyanogenmod. I reverted back to stock (retaining root). I received the OTA notification, it downloaded and started installing, but showed the <!> with the android.
I thought...ok...I'll return back completely to stock (no root) and now I'm sitting waiting for another OTA notification.
It's been three days now, and still no notification. I've tried checking for updates so many times that I've lost count.
Does anyone know whether or not a failed update gets another OTA notification? -or- why the software shows up-to-date when it's still at 2.1u1?
Thanks
Either take it to Verizon for them to push it onto the phone or use one of the methods here.
fygar66 said:
I'm sort of in the same boat. I had rooted with unrevoked and was running cyanogenmod. I reverted back to stock (retaining root). I received the OTA notification, it downloaded and started installing, but showed the <!> with the android.
I thought...ok...I'll return back completely to stock (no root) and now I'm sitting waiting for another OTA notification.
It's been three days now, and still no notification. I've tried checking for updates so many times that I've lost count.
Does anyone know whether or not a failed update gets another OTA notification? -or- why the software shows up-to-date when it's still at 2.1u1?
Thanks
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/showthread.php?t=771178
[Q] {FIXED}Problem with new OTA update..??....software"failed to update" message....
I have downloaded the update and clicked update now three times, and keep getting a failed to update message??.....any ideas..??.....I am rooted, but have used Voodoo to unroot......edit (now have tried 7 times......gets to the little android, and about one third of the way through installing, I get the triangle of death)
EDIT: See response below.......
Same thing is happening to me, except the phone is useless, because if I pull the battery and let it start up normally, the auto-update shutdown happens, and the cycle starts all over again.
If it matters, I'm on a stock AT&T rom with an unlocked bootloader.
FINALLY!!!
Finally got it......went to Moto.....tried through manual update with sd card......didn't work.......tried Autoupdater......didn't work the first time......ran Autoupdater a second time and IT WORKED........try that......
Still not working for me, what do you mean by Autoupdater? I've tried the SD card method and the downloaded method.
I'm having the same problem. Stock rom, rooted. the only modding i've done is the webtop over hdmi hack. tried both the manual and auto update.
There are two options on Moto......one is sd card.....the other is Auto......
http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
But Voodoo did not save root......gotta find another way to root......not unlocking bootloader......maybe Pete's OneClick will update to 2.3.6 soon......
i factory reset to see if it would fix the update. ew ew ew ew motoblur ew ew ew ew ew. kill it with fire. oh the things i do for updates....
iM having problems with ota updates... phone is on 2.3.4 unlocked bootloader, i do the ota update... ended up failed to boot 4starting rsd.. flashing the 2.3.4 unlocked sbf brings phone back to life... i USED THE MOTOROLA SOFTWARE UPDATERand phone is on offical 2.3.6 software and firmware. with locked bootloader.
I keep trying the auto updater but How do I make my phone stop the auto shutdown. I cant make it stay on for more than 30 seconds I do a battery pull reboot the phone boots up fine works then 30 seconds later shuts-down and tries to install the update again and it gives me the exclamation with the android. Never mind I did a factory reset via recovery phone works fine.
acondie13 said:
I'm having the same problem. Stock rom, rooted. the only modding i've done is the webtop over hdmi hack. tried both the manual and auto update.
Click to expand...
Click to collapse
THAT.
this is the same problem that's happened literally every time there has been a carrier update. search on how to restore webtop hack to stock and you'll be able to update after that.
rooted, locked bootloader, some hacks like HDMI webtop got fail to update massage
Those who don't know how to restore some hacks to stock, just go to http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
choose Automated upgrade, download Motorola_Software_Update.exe, follow the steps to update.
Good luck!
Hey guys,
I'm on stock but with root. My phone doesn't reboot after the OTA update. Is this because I'm rooted?
Just to clarify - it's the system update app that doesn't work. It counts down to 0, then... nothing. Phone is usable, the updater doesn't reboot to update.
Same happened to mine (not rooted) I had to flash back to 4.2.1 and wipe data/cache to get my phone to start up. Then it ran the system update again and got stuck in the same loop. I'm sticking with 4.2.1 for now.
equallyunequal said:
Same happened to mine (not rooted) I had to flash back to 4.2.1 and wipe data/cache to get my phone to start up. Then it ran the system update again and got stuck in the same loop. I'm sticking with 4.2.1 for now.
Click to expand...
Click to collapse
Just flash the whole 4.2.2 rom from here https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz and reroot.
gee2012 said:
Just flash the whole 4.2.2 rom from here https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz and reroot.
Click to expand...
Click to collapse
I did that, and go the same loop as when I did the OTA; I had to go find an archive of the 4.2.1 ROM and flash that to get it to start up (even flashing many times and wiping user/cache).
I'm going to try sideloading the 4.2.2 update when I have time
Thanks, I'll try that zip. Just to clarify - my phone isn't even installing the update. It's not stuck on the black Reboot screen, it's stuck on the countdown screen where you tap REBOOT & INSTALL. So essentially the phone is usable.. the updater just doesn't seem to work
brpqzme said:
Thanks, I'll try that zip. Just to clarify - my phone isn't even installing the update. It's not stuck on the black Reboot screen, it's stuck on the countdown screen where you tap REBOOT & INSTALL. So essentially the phone is usable.. the updater just doesn't seem to work
Click to expand...
Click to collapse
That's not where mine is stuck, mine won't boot past the X logo
My Nexus 7 won't go past the "rebooting now" too. The tablet is usable but it never finishes the update. I have power cycled and started over but no luck. Is there a way to clear the update cache so it re-downloads the update?
Cannot update 4.3 on sprint galaxy s4
Im on 4.3 with my sprint samsung galaxy s4. i had finished doing the process of unrooting just to update my samsung software, now when it countsdown, it says rebooting now and doesnt reboot. any ideas why ? thanks
GuidoGoyaBeans said:
Im on 4.3 with my sprint samsung galaxy s4. i had finished doing the process of unrooting just to update my samsung software, now when it countsdown, it says rebooting now and doesnt reboot. any ideas why ? thanks
Click to expand...
Click to collapse
Hiya! Did you ever find an answer?
I'm on 4.2.2 stock system for sph-l720, rooted, used triangle away and tried to get update 4.3 to install.
***Do I need to unroot to get samsung/sprint updates? The update keeps appearing but all progress from "android system update" stops after download verified, then the "rebooting now" step goes forever. Like OP, phone works fine, just wanted to update so I get best of newer apps, then back to customizing :fingers-crossed:
To my delight, I got the OTA update or whatever it is, the official thingie to update to 4.4, icon and all.
I start it up, it goes through the motions, then it gives me a nondescript error (( The little Android looked like how it did when it's awaiting a bootloader instruction. ))
Does this mean my Android stock is borked? Do I need to factory wipe? I am confused. I did, however, download the Google-based Nexus 2012 KitKat build and I attempted to ADB it, and it gave me yet another error, with this - E:Error in /tmp/update.zip.
Any help that can be given would be wonderful.
I have the same issue. I wiped the cache and done a factory reset but it didn't fix the issue. I downloaded Nexus root toolkit as it has a unbrick feature and ran that but it seems to have made it worse, I can no longer get into recovery.
Hi guys,
I have searched around the forums and still unsure, weary of what to do. I got my nexus when they first came out. I used it for a while and eventually unlocked it so that i could get certain apps that needed root access. I dont think i flashed a custom rom on it though. I havnt updated android to 4.4 yet. Its been a long time since i updated anything. Hence the start of my dilemma. I went to backup my tablet. It told me SuperUser or the bootloader needed to be updated. So im like oh fine update. Tablet then restarts brings me to my boot screen and says downloading target do not turn off. Its been stuck like this and nothing happens. I held down the power and rocker buttons and got back to boot option screen. Here's where im lost and dont remember what to do. I have tried start, recovermode, restartbootloader, and nothing seems to work. They all bring me back to the dead little android guy
Here's the device info.
product name: manta
variant: wifi
h/w version 8
bootloader version: mantam03
carrier info: none
serial: ****
lock state: unlocked
reboot mode flag: recovery
I slightly recall when i first unlocked it using twrp or clockworkmod? I could be wrong. Either way i no longer have the rootkit nor the computer i originally used to unlock it. What software do i need to install to get me back up and running. I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.
Jshannon22 said:
... I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.
Click to expand...
Click to collapse
Considering that you have not used the N10 in a very long time your user data may not be all that important so here are some options.
1) You could flash the factory image for Android 5 which will wipe out your user data but give you a clean system including stock recovery.
2) You could flash the factory image for Android 5 but first you need to change the "flash-all".(bat,sh) script by removing the "-w" option which will prevent your userdata from being wiped. That takes some knowledge to edit the script but all you need is a simple text editor.
After either of those options you can root and replace your recovery. Root before you change your recovery or you will run into an issue due to specific changes in Android 5.
Instructions for installing a factory image.
Nexus 10 lollipop factory image.
How to install Android Lollipop factory image on Nexus 5, 7 and 10 (and keep your data)
Good Luck
I'm having similar issues! When trying to install lollipop over sideload it always errors and states not enough space.
I've formated all the data so I'm at a loss.
Any ideas to install lollipop?
Sent from my Galaxy Nexus using XDA Free mobile app
I'm concerned I've bricked the device. To be honest I'd be happy just to get kitkat back!
When the device powers up it automatically goes into a "no command" bootloop. With the android on its side with an exclamation point sign coming out.
Holding power and the volume it then goes to the android recovery where I have four options: reboot, apply update from adb, factory reset, wipe cache.
When in command, typing adb devices shows my device.
Using adb sideload I've tried to update, but I always get the error "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip
status 7 installation aborted"
So I downloaded the kitkat image and tried to run the script "flash all". But then the command screen just says "waiting for device"
After all that failed, I tried to hold power and the volume button when it restarts. That takes me to the odin screen, where it just states "downloading, do not remove target" The volume buttons do nothing. pressing the power button just reboots.
Any help would be much appreciated!
I have the same issue. There does not seem to be a way to install any (old) version of android. All I get is the same error message "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip status 7 installation aborted"
I did not root my device nor did I install a custom rom. I just started installing the OTA update and that's when the tablet got stuck in the boot loop thingy.
I also searched the internet and all I found were similar instructions on how to install factory images etc. using adb sideload.... as I mentioned, following those instructions lead to the error message.
I can' believe this.
Thanks for your help
I also have similar issue. I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device. As novice even I do not know to install ADB sideloaded.
Can you suggest how best I can revive N10?
Regards,
Guys,
I also had the exact problem. What finally worked for is to flash custom recovery (TWRP latest version) with "fastboot flash recovery <recovery.img>" command.
Then from the recovery I installed custom ROM (http://forum.xda-developers.com/showthread.php?t=1998585), as the official ROM also failed.
Hope it will help someone.
Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!
fliuwoek said:
Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!
Click to expand...
Click to collapse
No worries, glad it helped you.