As it states I received the security update Ota notification a few days back, went ahead and let android do its thing to update. Then about a half hour later it asks me again. I've don't that update at least 7 times and it still prompts me.
I haven't rooted or even unlocked my bootloader, as stock ad the day it was born. Does anyone have a suggestion?
Mine keeps saying error when it reboots and tries to flash the update but I'm running stock without root or anything just unlocked bootloader
lokoz89 said:
Mine keeps saying error when it reboots and tries to flash the update but I'm running stock without root or anything just unlocked bootloader
Click to expand...
Click to collapse
I don't even get and error, it's terribly annoying
bossman137 said:
I don't even get and error, it's terribly annoying
Click to expand...
Click to collapse
The constant notification is annoying. I know I can keep Google Services from showing them but it would be nice to keep for future updates.
Nobody else care to chime in? Never had OTA fail before on stock rom with no root or custom recovery.
Will probably have to sideload and see how that goes
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
Took an OTA update this AM in the US, but nothing seemed to change. Switched back to stock recovery, took update, downloaded, installed (no errors), rebooted, message said somethings about a Pre-Install APK, then nothing. Tablet info says I am now up to date, but nothing else seems to have changed.
I'm still on custom kernel (thor's), still on 3.1. I forget the GEN info, but I don't think that changed either.
Was this a pre-update update?
I got the update too.
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Ditto. Used stock recovery and unroot to get it to install. It's Gen 2.
Sent from my ADR6300 using XDA App
Same here, updated with no errors. Didn't lose root and it still says 3.1
With the update to 3.1 they sent out a smaller update a few days earlier. This one may be the same thing.
It's just a small update, about less than 20MB download. But I have no idea what's been changed.
GShyneDM said:
I got the update too.Same thing happaned to me
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Click to expand...
Click to collapse
Same thing happened to me...
System Update
System Update 4.010.13
(14.49MB).
A new system update is available for your device. A network connection is required to download and update your device. You may incur additional charges from your service provider. Thank you for not replacing me with the HP TouchPad.
Click to expand...
Click to collapse
i'm gonna hold off on installing this until i know more of what its all about...
I uploaded the zip in development, I don't think I'm gonna install either...
I also installed the 14MB update today. The tablet was rooted, but otherwise stock. After the update the tablet remains rooted. I have experienced no other issues.
Cheers,
A
I had the same experience as above. So far no issues.
This actually made me worried about the possibility of us to get an update to 3.2 on 8/25. Otherwise, they should just pass this incremental.
[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!
My phone keeps telling me to install ls980zv7_01_to_zv8_13. Whenever I say yes, it reboots, but as far as I can tell the update doesn't install and after a few days the update notification pops up again. I'm running Sprint's stock ROM, rooted.
Has anyone else had this problem?
Awk34 said:
My phone keeps telling me to install ls980zv7_01_to_zv8_13. Whenever I say yes, it reboots, but as far as I can tell the update doesn't install and after a few days the update notification pops up again. I'm running Sprint's stock ROM, rooted.
Has anyone else had this problem?
Click to expand...
Click to collapse
You could install a custom recovery and use Youdugs stock rooted ZV8 in deodex or odex...or try the update again but no haven't seen that problem
I'll do a nandroid before, but I shouldn't have to erase anything before installing that, right? Also, could you give me a link?
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
dmkozak said:
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
Click to expand...
Click to collapse
It's the first update of Google's announced security patch program. Expect frequent OS updates now to address security issues. This one patches the well publicized Stagefright MMS exploit.
That was my guess. I rarely text, or other, message, so I'm not too worried about Stagefright. My gut tells me to wait until others have installed. I have enough memory leak auto turn-off issues, that I'm afraid of making my phone worse than it is.
If Google would be so kind as to include a memory leak resolution in these updates, I'd jump all over it.
Well I had been postponing updating to Lollipop for months... (was still on 4.4.4 cuz I didn't quite like the new UI) and decided to update Sunday morning.
Big mistake.
The OTA 5.1.1 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome!
I currently can't even use my N4, and I'm trying to find a way to revert the upgrade, My 4.4.4 was rooted, and now it's not and I can't even enter Recovery mode.
Not sure if it's 100% related to your troubles, but I've been having similar random reboots lately and just general instability.
Edit: my bad, I just realized it was 5.0.1 I upgraded to.
update aug 10, 2015
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
robpoth said:
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
Click to expand...
Click to collapse
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Stevica Smederevac said:
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
ariesgodofwar said:
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
Click to expand...
Click to collapse
Yeah,you're right. Everything stock +locked bootloader for ota to work. I assumed he knew thhat part about everything stock.
Sent from my Nexus 4 using XDA Free mobile app
I have unlocked bootloader and still I updated successfully thru OTA. No problems at all.
Sent from my Nexus 4 using Tapatalk