Hi guys, so i recieved the OTA a few hours back and it required me to have more battery life in order to continue with it.
I was charging it and realised that it would allow to me to continue as long as it was charging, so i continued with the operation.
It rebooted my nexus (everything stock, rooted using mskips all in one root) and then required a confirmation to continue. in my excitement i pressed power instead of vloume down (in order to scroll down to yes). i thought that i should just rather reboot my nexus and start the whole process again, but now it doesnt show that there is a update available, system update says my system is uptodate but i am still running 4.1.1
does anyone know how long it will take for OTA to come through again? or how i can "induce" it?
I would just flash the update manually. Check out links to download from Google site.
Rootbrain
yeah i guess, i was gonna do so anyway by monday if i hadnt gotten the OTA by then XD still would prefer OTA though....
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!
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.
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
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
travistyse said:
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
Click to expand...
Click to collapse
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
madbat99 said:
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
Click to expand...
Click to collapse
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
travistyse said:
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
Click to expand...
Click to collapse
The ota has a bunch of checks in it. If anything fails the checks, ota fails. When you root, there are system changes, boot.img changes, etc. All of which cause the ota to fail. Of course lineage and cm didn't have such strict checks in their update zips because they expect us to root and modify system. Manufacturers do not.