I went to do the OTA update today, but my update failed everytime, giving me a exclamation mark upon reboot. Now my phone is rooted and i had the webtop hack. Tried 3 times using OTA, and all failed, so i un did the webtop hack, got rid of the 3 apk files i added, then tried, still failed. Disabled outside apps, still failed. Then i downloaded the update to the sd card, tried that way, still failed.
So then i went to motos website and did the auto upgrade feature, and it took a long time for the program to install, but it finally connected to my phone, then at about 75% it failed, phone shut off, and then locked up. Tried reboot 3 times, never getting past splash screen. Took batt out, then let it sit. About 5 mins into att splash screen, i got a purple blinking light on my phone, then booted up and BAM!!! 2.3!!!
So even tho it said i failed, i have the new software!!! Lets hope it works ok.
Im on sort of the same boat here. I have 1.83 rooted through the GLADROOT after OTA update. i keep getting the exclamation mark upon reboot. After taking battery out and rebooting i still get the update failed message
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
Hi,
Ive already looked around the forum but cannot find an answer to my question.
I know my phone is not totally bricked, I understand there are probably ways of plugging it into a PC to force an update but i downloaded the OTA update that popped up on my phone last night. As I understand it is meant to update and keep all of your apps and saved data, which I chose to do instead of wiping anything with a manual update to save all the hassle.
The phone was rooted on froyo 2.2.2 orange uk rom but apart from that there were no other mods to the OS.
The phone came up with the "power off" message and now sticks on the black Motorola screen showing
"Failed to boot 2
starting rsd mode"
I can pull the battery out and the phone turns on for about 20 seconds, and I can use the OS in this time but then the "powering off" message comes back up
and it goes back to the error message on the splash screen.
Is there a way I can stop this OTA update from powering off my phone and getting stuck in this loop or do i have to wipe the phone and flash an sbf file?
Can you point me to the sbf file for the new orange gingerbread rom?
Thanks
ryan
Anyone?
When i turn phone on it works for about 20-30 seconds, before it restarts into the splash screen. It seems as if the phone is running some sort of script to continue with the upgrade but when it reboots it cant continue or something...
The OTA update didnt even start flashing, it just downloaded, then i clicked "install now" and it just rebooted to the error.
If i cant fix it easily, can I use RSDLite and an SBF file to go back to stock? Or can you only do this on an unlocked bootloader?
My bootloader is still stock. The only thing I did when I got the phone was root it so that I could install certain apps.
PLEASE HELP!
Link to Orange UK GB SBF is in Atrix 4G Android Dev forum in the Atrix Firmwares Superthread..page 25ish.
I RSDLited this SBF onto my Atrix (unlocked bootloader running Alien #4) with no problems.
This same route may be your only option...not sure about recovery of your apps etc..I have everything backed up via Blur, Google account and Titanium Pro, so no concern for me there.
FYI, this new rom seems to have little Orange bloat and runs great for me in stock form...just rooted...and battery life is very respectable.
I could really use some help here. Hang with me as I explain what I've done and what's happening.
About a month ago, I checked for OTA update. .78 showed up, but, before installing, I went online to see that the new update didn't jive with rooted and BL unlocked Razr Ms. So....I've basically been hitting "remind me later", twice a day, since then. So my alarm goes off this morning and, in my foggy eyed and foggy head state, I hit install update while trying to turn the alarm off.
Obviously, I lost root but BL is still unlocked. Thinking it would be easy to reroot, I uninstalled the superuser app that I got when I rooted with motochopper. Well I tried to reroot with no luck. I run the bat file and it gets here and progresses no further. *daemon started successfully*
When I try to boot into recovery I just get the android guy, on his back, with the red triangle over him. My recovery was TWRP 2.6, IIRC.
Any help would be greatly appreciated.
jabo052 said:
I could really use some help here. Hang with me as I explain what I've done and what's happening.
About a month ago, I checked for OTA update. .78 showed up, but, before installing, I went online to see that the new update didn't jive with rooted and BL unlocked Razr Ms. So....I've basically been hitting "remind me later", twice a day, since then. So my alarm goes off this morning and, in my foggy eyed and foggy head state, I hit install update while trying to turn the alarm off.
Obviously, I lost root but BL is still unlocked. Thinking it would be easy to reroot, I uninstalled the superuser app that I got when I rooted with motochopper. Well I tried to reroot with no luck. I run the bat file and it gets here and progresses no further. *daemon started successfully*
When I try to boot into recovery I just get the android guy, on his back, with the red triangle over him. My recovery was TWRP 2.6, IIRC.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
someone asked the same question you did (after yours): http://forum.xda-developers.com/showthread.php?t=2419648
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
avpatel said:
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
Click to expand...
Click to collapse
The exact same thing happened to me, i finally flashed 4.2.2. it booted, but then my IMEI disappeared and i couldnt make any calls. It was completely random. It is possible that the same thing is happening to you. If that is the case, the only fix I know is to change the board.
if you can flash CWM or TWRP, try wiping the system files and then flashing a rom to see what happens.
What do you mean change the board?
And for the rest of the suggestions I'd really appreciate a bit of an explanation - I'm not terribly experienced with messing with Android;
Well I did some research and I flashed TWRP, wiped system and data. I then flashed 4.4.4, but it didn't boot. I'll try to turn it on again tomorrow.
^^On stock 4.2.2, does your phone have an imei number? If not, you will need to send the phone to LG for repair.
avpatel said:
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
Click to expand...
Click to collapse
Did you wipe the system cache and dalvik cache BEFORE AND AFTER flashing a zip?
I've seen many instances of an unsucessful boot becuase the cache wasn't cleared AFTER flashing the zip.
If it still doesn't work I'd recommend you to redownload the system zip from the factory image site.
HI all,
Had the Note 4 for a month or two now, been successfully rooted for a couple of weeks too. Rebooted the phone today though, and it's just gotten stuck with a message saying "installing system update". It doesn't seem to progress no matter how long I leave it aside from the screen flashing.
I've tried to boot into recovery, but for whatever reason it just doesn't work, it always goes back to the update screen. Getting a bit worried now, any help would be great.
Cheers.
drojman said:
HI all,
Had the Note 4 for a month or two now, been successfully rooted for a couple of weeks too. Rebooted the phone today though, and it's just gotten stuck with a message saying "installing system update". It doesn't seem to progress no matter how long I leave it aside from the screen flashing.
I've tried to boot into recovery, but for whatever reason it just doesn't work, it always goes back to the update screen. Getting a bit worried now, any help would be great.
Cheers.
Click to expand...
Click to collapse
Flash stock f/w via Odin it should boot just fine, you'll have to re-root though.
For some reason installing CWM fixed it. It wiped my data, but it's back at least.