I made the mistake of accepting the April 2018 update (VS9951BA) for my non-rooted Verizon VS995 and the update has been installing for over an hour now. Think I should let it continue or power off/remove battery?
Ideas?
In case anyone else runs into the same issue, I waited two hours just in case and finally pulled the battery. So far, the phone seems ok and the update seems to have installed successfully.
JCDinPGH said:
I made the mistake of accepting the April 2018 update (VS9951BA) for my non-rooted Verizon VS995 and the update has been installing for over an hour now. Think I should let it continue or power off/remove battery?
Ideas?
Click to expand...
Click to collapse
This had happened to me with the last update!
I removed the battery, waited for 5 minutes and put it back in. Everything worked fine.
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
I'm posting this in case someone sees something similar. I just updated ota from 4.010.11 to. 13 a couple days ago. I noticed suddenly when I checked battery usage that the system was awake all the time. It never slept. I ended up backing up my apps/data and wiping and reinstalling 4.010.11 fresh by itself. Seems something wigged out between all of the back to back ota's.
After reinstall and ota update to 4.010.13 my system now sleeps again.
dottat said:
I'm posting this in case someone sees something similar. I just updated ota from 4.010.11 to. 13 a couple days ago. I noticed suddenly when I checked battery usage that the system was awake all the time. It never slept. I ended up backing up my apps/data and wiping and reinstalling 4.010.11 fresh by itself. Seems something wigged out between all of the back to back ota's.
After reinstall and ota update to 4.010.13 my system now sleeps again.
Click to expand...
Click to collapse
Maybe it was something screwed up in /data. By any chance did you apply any mods/patches to the broken install?
Nope. No patches. Was true ota progression.
dottat said:
Nope. No patches. Was true ota progression.
Click to expand...
Click to collapse
Hmmm. . . Well sometimes odd things happen, as long as its working now
Okay guys,
Here's my issue. I'm on a D800 and I have tried multiple times to OTA update to lollipop however It sticks on the LG boot screen. I have tried using the LG flash tool to go back to 20c and OTA update all the way to lollipop from there with no results. I have tried to manual force OTA (http://forum.xda-developers.com/att-g2/general/links-manually-forcing-ota-20c-to-20u-t2828874) but I keep getting err 0x1111004 which I understand is an issue with the update script recognizing the phone being rooted and I'm not sure of a way around that. (I have tried multiple rooting methods with this all with the same error code) Looks like I may be stuck with the kk 4.4.4 until someone creates a stock lollipop rom or someone creates a TOT file. Yes I have an att sim card. I do not get service at my house but to my knowledge that should not be an issue. Any thoughts or suggestions would be greatly appreciated!
You must be on stock unrooted to get ota. Flash stock 4.4 kdz then ota.
_____________________________________Read more write less and be smart
siggey said:
You must be on stock unrooted to get ota. Flash stock 4.4 kdz then ota.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
I actually have been trying to update it on stock unrooted the whole time. If that were the issue I would not have posted. I got it resolved by leaving it on the LG logo screen over night and it took it nearly three hours to reboot and initialize boot up, but it worked. Strange, I didn't realize it was supposed to take that long.
ParkerG said:
I actually have been trying to update it on stock unrooted the whole time. If that were the issue I would not have posted. I got it resolved by leaving it on the LG logo screen over night and it took it nearly three hours to reboot and initialize boot up, but it worked. Strange, I didn't realize it was supposed to take that long.
Click to expand...
Click to collapse
You didn't do factory reset after flashing LP?
It happened to me
The same thing happened to me last night. I called AT&T and they said that is normal. They said Google has changed so many things it takes a while for everything to load. It took me a little over an hour before I saw the blue LED light flashing. Then it booted up and is working great!
sammyconigs said:
The same thing happened to me last night. I called AT&T and they said that is normal. They said Google has changed so many things it takes a while for everything to load. It took me a little over an hour before I saw the blue LED light flashing. Then it booted up and is working great!
Click to expand...
Click to collapse
Yep it seems so. I'm just impatient and I couldn't find any posts about the time it takes to update. The only one's that I could find were saying a little over thirty minutes to update so that's what I was going off of.
shut_down said:
You didn't do factory reset after flashing LP?
Click to expand...
Click to collapse
I did try to factory reset after flash the first few times. I did not this last time. I just flashed up to lollipop and let the LG logo sit after I wen't to bed.
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
Received this in Singapore.
Very hesitant to restart now in view of the Oct update that boot looped my phone causing me to factory reset.
Anyone else received this and successfully updated?
Thanks.
Yes,No problem in Germany...
jonnyhh said:
Yes,No problem in Germany...
Click to expand...
Click to collapse
Were you affected by the Oct update?
Received in India. Didn't face any problem with October or November update.
iluvatrix said:
Received this in Singapore.
Very hesitant to restart now in view of the Oct update that boot looped my phone causing me to factory reset.
Anyone else received this and successfully updated?
Thanks.
Click to expand...
Click to collapse
Any improvements or fixes??
iluvatrix said:
Were you affected by the Oct update?
Click to expand...
Click to collapse
No,never had problems until now.
Anyone who couldn't update from September to October can report if it's possible to go from September straight to November, and if it works without bootloop or resetting data?
Thanks.
iluvatrix said:
Received this in Singapore.
Very hesitant to restart now in view of the Oct update that boot looped my phone causing me to factory reset.
Anyone else received this and successfully updated?
Thanks.
Click to expand...
Click to collapse
I had the boot loop last time and factory reset. This one I had no issues.
danannnn said:
Anyone who couldn't update from September to October can report if it's possible to go from September straight to November, and if it works without bootloop or resetting data?
Thanks.
Click to expand...
Click to collapse
Yes, my wife's phone. I had boot looped on October's update and reseted. My wife decided to skip Oct. Now she has received the Nov update and tried to update and got the boot loop. She has unlocked bootloader and critical partition. Restarted 7 or 8 times and managed to boot back to Sept. She is stuck now.
xrayA4T said:
I had the boot loop last time and factory reset. This one I had no issues.
Click to expand...
Click to collapse
Same here. Looks like everyone has to get boot looped either on Oct or Nov update.
No problem with update October to November updater, always using charger and battery 100%.
iluvatrix said:
Yes, my wife's phone. I had boot looped on October's update and reseted. My wife decided to skip Oct. Now she has received the Nov update and tried to update and got the boot loop. She has unlocked bootloader and critical partition. Restarted 7 or 8 times and managed to boot back to Sept. She is stuck now.
Click to expand...
Click to collapse
/shrugs
Thanks for the heads-up.
iluvatrix said:
Same here. Looks like everyone has to get boot looped either on Oct or Nov update.
Click to expand...
Click to collapse
If only my phone would boot with >October version at all, wiping or not.
Not even EDL flashing made it boot into October. I'll give November a try on the weekend, but I'm not hopeful.
Hopefully BF or CM has great deals on pixel 4a. Can't wait to ditch this dumpster fire of a phone.
danannnn said:
/shrugs
Thanks for the heads-up.
If only my phone would boot with >October version at all, wiping or not.
Not even EDL flashing made it boot into October. I'll give November a try on the weekend, but I'm not hopeful.
Click to expand...
Click to collapse
I will wait for your update. Also because i´m in the same boot.
I am with september update. In October update i get boot loop a manage to get the phone working witout reset, after 7-8 restarts.
Now i want to know if i get again bootloop if i try to get November Update. I have bootloader unloack because of gcam, but don´t have root.
Bootlooped in Oct update and Bootlooped with Nov update... Thanks xiaomi
ki69 said:
I will wait for your update. Also because i´m in the same boot.
I am with september update. In October update i get boot loop a manage to get the phone working witout reset, after 7-8 restarts.
Now i want to know if i get again bootloop if i try to get November Update. I have bootloader unloack because of gcam, but don´t have root.
Click to expand...
Click to collapse
I just tried September -> November and no dice.
Got the "Try again / Reset" screen. After choosing Try Again 6 or 7 times it switched back to other slot and booted into September after one more Try Again.
At least it looks like it'll work when I choose to reset, which is better than I had before, but I didn't want to do it now.
Im fully stock, not even gcam mod, but keep bootloader unlocked due to how this phone is prone to bootlooping between updates.
iluvatrix said:
Received this in Singapore.
Very hesitant to restart now in view of the Oct update that boot looped my phone causing me to factory reset.
Anyone else received this and successfully updated?
Thanks.
Click to expand...
Click to collapse
Noooo the dreaded bootloop is back?!
I thought they fixed the bootloop (caused by wrong update being offered) a long time ago! I am on November update and haven't had any issues for the past 9 months...
I think the problem is really in bootloader unlock. Maybe october update had a relock of bootloader ant that why we get bootloop.
I updated to november no boot loop this time, my phone has bootloader unlocked but still stock, with October it had the boot loop and I chose to full reset, I'm disappointed too, waiting a pixel 4a to replace it first and last xiaomi for me.
Wifi had become very unstable since October update. Battery last 1-2 h less, it had an issue with the charging port so I bought a Chinese replacement which only is useful for charging not for data, as soon I get a new original one (very expensive) I'll switch this to lineageOS and keep for experiments
I bought a Chinese replacement which only is useful for charging not for data, as soon I get a new original one (very expensive)
Click to expand...
Click to collapse
Simeone had stolen my orignal data cable so I too bought a cheaper data cable as I was traveling and later come to know it wasn't working for data. Later bought Portronics Konnect L cable from Amazon.in around ₹109 or $1.50 and it's fast and has data transfer capabilities.