Related
I don't know how this happened but I look over and see my thunderbolt rebooted (happens maybe once every one or two weeks). Not thinking much of it I look away and then look back a moment later to see the update screen! I would have ripped the battery out but I didn't want to risk bricking it.
I have been hitting reject to the update since it was first released and it's never updated on its own! This is a warning to anyone else that has been hitting reject all this time, it seems it somehow is starting the update process on its own now.
Italianguy said:
I don't know how this happened but I look over and see my thunderbolt rebooted (happens maybe once every one or two weeks). Not thinking much of it I look away and then look back a moment later to see the update screen! I would have ripped the battery out but I didn't want to risk bricking it.
I have been hitting reject to the update since it was first released and it's never updated on its own! This is a warning to anyone else that has been hitting reject all this time, it seems it somehow is starting the update process on its own now.
Click to expand...
Click to collapse
The phone doesn't auto-update.
g00s3y said:
The phone doesn't auto-update.
Click to expand...
Click to collapse
Well apparently it can because it has been sitting at my desk at work all day and I haven't touched it. It vibrated and I look over and see the HTC splash screen and then it went to the update logo. If it was just sitting there how else can you explain it?
It rebooted several times and now the data icon is different, mobile hotspot doesn't work, and there is a new Verizon data widget. It updated on its own.
Resistance is futile.
mine updated itself too last night. I plan to reject the update since i still had a working hotspot up too last night. I looked at my phone and the update was already in progress and halfway done.
No i am concidering root but wanted to stay stock. Someone just posted that they were rooted and stock and this automatic update caused their phone to brick.
what update? we haven't had a OTA since early july.
fixxxer2008 said:
what update? we haven't had a OTA since early july.
Click to expand...
Click to collapse
The same one. I never received the 7/8 update until last night. They are still pushing out the mr2 update which should give you an idea of how close GB is...not very
microdot said:
The same one. I never received the 7/8 update until last night. They are still pushing out the mr2 update which should give you an idea of how close GB is...not very
Click to expand...
Click to collapse
gb is closer than you think. i always said a fall release anyways.
microdot said:
They are still pushing out the mr2 update which should give you an idea of how close GB is...not very
Click to expand...
Click to collapse
Huh? It's coming Q2, and this is only June 86th.
I can confirm that the phone did "auto-update". I had been hitting reject on every notification for the update (so i could keep using the mobile hotspot). When i woke up this morning (or yesterday morning, i cant remember) - my phone had the new verizon icons, new version number, and mobile hotspot didnt work anymore (prompt to buy $30/month feature).
I'll guess i'll finally have to root and install some ROM.
mike.s said:
Huh? It's coming Q2, and this is only June 86th.
Click to expand...
Click to collapse
LOL!!!
That's why summer won't end. I don't have my GB update yet!
I can confirm my phone auto-updated last night too, it failed the updated and keeps rebooting.
g00s3y said:
The phone doesn't auto-update.
Click to expand...
Click to collapse
Yes it does. In fact, I suspect what happens is when the screen/menu pops up with 'accept, reject, or the 3rd option (??)', if you don't respond within a certain time, it defaults to 'accept'.
I think is too much coincidence that more than one person had the same issue the same night. Verizon you !#$% failz!
Same here. Updated this morning right when my alarm was supposed to go off. Luckily the flashing lights woke me, but it was too late as it was already on the update screen and couldn't risk pulling the battery.
Sent from my ADR6400L using Tapatalk
http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html
I got this from another thread, solution #1 seems to have done it for me...
i got the same problem as everyone else
===
So I plugged in my phone last night and rebooted it, only to find ClockWorkRecovery giving me a warning message saying that some update has failed (details below), and if I tell it to reboot, it will properly enter Android and load all my stuff, but within seconds of loading up properly, the phone FORCE shuts down.
Power Off - Shutting Down, and there is nothing I can do to stop it.
I have the latest CWM 4.0.1.5, i just flashed it. I did a backup just in case, as I don't know what steps to take.
While booting up..the phone will look like its installing something, but then fails.
Press the menu key, CWM opens up and I see the following.
===============
ClockworkMod Recovery 4.0.1.5
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: Signature verification failed
Installation aborted
================
I know Verizon has been bugging me with that firmware update, but I've been denying it every time. There is no way it would have downloaded already, would it? I didn't accept any software updates.
I've tried rebooting phone from cold shutdown, taking memeory card out. I have't restored to previous ROM, or dont any wipes/factory resets. I dont wanna attempt those unless I know what it's going to do.
At this rate, my HTC Thunderbolt is pretty much a brick.
========
UPDATE:
I followed the method 1 steps from the link bastukee posted and its been working so far so good.
i am currently rooted with the old software, is there anyway to update the software but still stay rooted? I dont want to keep seeing these annoying updates.
@blenderben
Mine did EXACTLY the same thing and solution #1 fixed it, the option to clear the cache. I'm going to actually use a non-stock ROM from now on.
yeah i wanna swap to CM7, but isn't it still in alpha?
Verizon auto push update to phone.
How can we stop it?
First off, thanks for xda. Favorite place for Android information. Droid charge is my 4th android phone and my knowledge of these phones isnt the greatest. Most I do is root and rom thanks to your guides.
Well anyways I just got my phone back from samsung after they repaired my Charge. It was in a boot loop, tried using CWR to install other roms but always stuck at samsung screen. Well I sent it in after unrooting and putting the stock rom back on. Here is what samsung said they did.
11/10/2011 6:20 PM-Melvin Garcia: The unit has left the technician. SOLUTION: Replaced PBA - PRL Updated - S/W Updated - Passed All
*11/10/2011//19:21:27//0001773863//Telephone//ASC*
SOFTWARE DOWNLOAD
PASSED RADIATION TEST
PASSED FINAL TEST
Well phone is working fine except the flashing triangle icon was on it, even with the stock factory rom. I romed humble 5.0 and the icon is still there. After research it appears its that I'm roaming, which im not. Same place I always lived. So I figured something maybe is wrong with my SIM card, so i took my girlfriend's Thunderbolt and swapped SIMs to test. My Charge still showed that icon while the Thunderbolt was fine. Is there any solution to this icon? Its rather annoying, a message pops up when doing certain things warning me that I am roaming and I should be careful of additional fees.
Any help would be greatly appreciated!
I randomly get this while 2 other charges that I'm next to don't.
Sent from my Gummy Charged GBE 2.1 using XDA App
It is 100% of the time though.
this may be late but I have the same issue. I sent it in again to fix this issue and it still came back with the blinking roaming triangle. Anyone that has had this ever had the issue resolved?
I installed the 9.18.79 update on my rooted with stock rom razr maxx hd. The only change i made to stock apps was the sqlite tether mod hack. I used voodoo ota rootkeeper and it worked fine, so I still have root. I do not have unlocked bootloader. Anyway, after that update, it keeps freezing and restarting. Doesn't matter what app, every 5 min to half hour, even when i'm not using the fon it will restart. Very annoying! Is there a fix for this or a way to uninstall update?
If you unlocked your bootloader I would say a factory reset would be worth a try. This way your phone is refreshed to pure stock. You will lose root but with an unlocked bootloader that doesn't matter because getting root back is easy.
If your bootloader is still locked, a data reset will cause you to lose root (edit: after posting this i am second guessing if a data reset will lose root. It might not. It had been so long since i have done that i can't remember. Lol) and there is no confirmed way of getting it back. Of course, if your phone is basically unusable with constant reboots, I think I would rather have a working phone without root than what you are currently dealing with.
Sent from my DROID RAZR HD using Xparent Purple Tapatalk 2
It's not unlocked and the update fixed the exploit to unlock it I didn't think I needed it unlocked anyway. I just wish I knew if vzw or a dev will come out with a patch for this so called update.
Mine is doing just about the exact same thing. I upgraded it on Saturday and it has rebooted more times than I can count. I hogs battery now too. I could get an easy 3 days before, I am no power user, the last 2 days I've used over 50% battery and have not done a thing. I used the OTA rootkeeper as well to keep root. I hardly have any apps frozen with Titanium Backup, unfroze them all, I'm running Nova Launcher. Funny thing is I did the exact same thing on my wife's phone with no issues. Hers is rooted too, stock ROMs. I was totally happy with the stock ROM, so I have not ROM'd this phone yet, want to now cuz it sucks but going to have to wait until I can root again. I tried wiping cache in Titanium and a couple times in the stock recovery. Did nothing.
---------- Post added at 09:24 PM ---------- Previous post was at 09:11 PM ----------
Wife says she has had problems keeping her bluetooth connected in her car, she said it disconnects frequently now. She just has a stock Lexus radio which worked flawless. DAmn you Verizon, these phones were AWESOME prior to this update, burn in hell haha!
I wiped cache in stock recovery as well
Is there a way to sbf the original stock file back to the fon? I've used sbf on a number of droid x but thats been awhile.
I have the exact same problem as OP, but the period between reboots can be as high as 2-3 days. Anyone have any idea what is actually wrong? Did they program in a random reboot to make us want to upgrade to the Droid Maxx?
Sent from my Motorola RAZR Maxx HD with Tapatalk 4
JungleKing76 said:
If you unlocked your bootloader I would say a factory reset would be worth a try. This way your phone is refreshed to pure stock. You will lose root but with an unlocked bootloader that doesn't matter because getting root back is easy.
If your bootloader is still locked, a data reset will cause you to lose root (edit: after posting this i am second guessing if a data reset will lose root. It might not. It had been so long since i have done that i can't remember. Lol) and there is no confirmed way of getting it back. Of course, if your phone is basically unusable with constant reboots, I think I would rather have a working phone without root than what you are currently dealing with.
Sent from my DROID RAZR HD using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
No, a FDR does not remove root.
Glad I have not updated yet. Matter of fact I froze the updater so it won't update.
well if fdr won't lose root with locked bootloader, i might try that, tho i'm pretty sure it won't help.
Well, I just did the data reset. Didn't lose my root. Reinstalled all of my apps with Titanium and will see if the lockups go away and if the battery life gets back to where it was prior to the update.
Still freezes and reboots. I guess I'll start removing apps and widgets to try and pinpoint. This sucks, was such an awesome phone prior to this ghetto upgrade.
Sent from my DROID RAZR HD using Tapatalk 2
Did fdr, still reboots.
I've deleted all widgets and still froze and rebooted. So, I ditched Nova launcher and went back to the stock launcher and so far so good. My wife runs the stock launcher and has had zero issues and I upgraded both phones at the same time. Both phones are rooted. I liked Nova a lot, but like stable phone better.
Will report back after more saddle time with stocker.
Sent from my DROID RAZR HD using Tapatalk 2
---------- Post added at 11:31 PM ---------- Previous post was at 11:17 PM ----------
Not the launcher locked up again. Gonna do the sbf I think, but not sure when I'm gonna have time in the next couple days. Bought the phone at BB because it was cheapest there and they basically said sorry no goon squad warranty nothing we can do. Gonna explore other options and call Verizon and ***** and see if I can get a warranty replacement somehow. Fingers crossed.
Sent from my DROID RAZR HD using Tapatalk 2
I'm having random freezes after the update. No reboots. I'm 100% stock. This is happening at least twice a day. Does anyone have any idea what's going on? Is it the update because I never had this issue before the ota. It also seems to happen after or during a call.
mcaspe1, I feel your pain. There is a utility on here to go back to 9.16.6. I did that and my phone is back to being awesome. I also read a thread over on droidrzr or something like that where you can use RSD Lite to flash the new radios, which I did too. FYI I called Verizon this morning and the phone has a factory 1 year warranty. I *****ed about the battery life and the constant freezing and restarting with the new software and they are sending me a new phone. If you don't want to mess with the utility to get you back to the old stuff, which is SUPER EASY, then call Verizon and tell them the new update version you got sucks ass. It could not have been easier. Note, if you didn't do a factory reset they will tell you to do that first.
al2fast said:
mcaspe1, I feel your pain. There is a utility on here to go back to 9.16.6. I did that and my phone is back to being awesome. I also read a thread over on droidrzr or something like that where you can use RSD Lite to flash the new radios, which I did too. FYI I called Verizon this morning and the phone has a factory 1 year warranty. I *****ed about the battery life and the constant freezing and restarting with the new software and they are sending me a new phone. If you don't want to mess with the utility to get you back to the old stuff, which is SUPER EASY, then call Verizon and tell them the new update version you got sucks ass. It could not have been easier. Note, if you didn't do a factory reset they will tell you to do that first.
Click to expand...
Click to collapse
Thanks for the info. I tried deleting a few apps which I thought could be causing it. If that doesn't work I'll definitely either flash back or call VZW. Thanks again.
Here's the link to the utility to get back to the old software and to root it, did it 3 times so far now! http://forum.xda-developers.com/showthread.php?t=2307439 I did options 1 & 3.
Here is the link to the instructions to install radios via RSD Lite: http://www.droidrzr.com/index.php/topic/22925-snatched-that-sheezy-soak-update/page-7#entry320685 Instructions are about halfway down, worked fine for me on the 9.16.6 to get the 15P radio.
Already got the notification from Verizon that my replacement shipped! I hope it still has 9.16.6 on it so I can unlock the bootloader after I see the shenanigans these new updates are doing to phones!
Before I started all of the flashing, I tried going back to stock launcher, unfreezing every app in Titanium Backup, killing every widget, clearing cache, and a factory data reset. I flashed back to 9.16.6 and it was all good for a few days, so took the update and it started locking up and rebooting again within 10 minutes of constant use. Must be something with the hardware that update doesn't agree with on some phones, because I think flashing the stock 9.16.6, then taking the update, and only installing tapatalk from the market and still having lockups, ruled out any apps I had running. The sucker would freeze when trying to set ringtones and check system versions and using chrome and tapatalk.
al2fast said:
Here's the link to the utility to get back to the old software and to root it, did it 3 times so far now! http://forum.xda-developers.com/showthread.php?t=2307439 I did options 1 & 3.
Here is the link to the instructions to install radios via RSD Lite: http://www.droidrzr.com/index.php/topic/22925-snatched-that-sheezy-soak-update/page-7#entry320685 Instructions are about halfway down, worked fine for me on the 9.16.6 to get the 15P radio.
Already got the notification from Verizon that my replacement shipped! I hope it still has 9.16.6 on it so I can unlock the bootloader after I see the shenanigans these new updates are doing to phones!
Before I started all of the flashing, I tried going back to stock launcher, unfreezing every app in Titanium Backup, killing every widget, clearing cache, and a factory data reset. I flashed back to 9.16.6 and it was all good for a few days, so took the update and it started locking up and rebooting again within 10 minutes of constant use. Must be something with the hardware that update doesn't agree with on some phones, because I think flashing the stock 9.16.6, then taking the update, and only installing tapatalk from the market and still having lockups, ruled out any apps I had running. The sucker would freeze when trying to set ringtones and check system versions and using chrome and tapatalk.
Click to expand...
Click to collapse
Well, Just had another freeze and now I'm fed up. Nothing I've done has helped. I'll revert back so I can have a working phone. I called and have a replacement coming. Thanks for the info. I have posted on the Motorola owner's forum regarding this. They are now aware.
A fellow poster, "Bertil", on the Motorola owners website has indicated they believe that turning off smart actions and clearing the application will stop the screen freezes. Says its been a week without any problem. I figure I'll try it out until my replacement comes tomorrow. I'll report back.
Here is the link. https://forums.motorola.com/posts/dd28537543?page=2
first off, I am new to the G3. I bought one used (in mint condition) and it had 5.0.1 on it. I loaded all my settings and apps that I typically use and to me it worked great...No huge amounts of lag...it was actually pretty smooth. Well when I installed TWRP, it wouldnt boot...it would get security boot error (or something like that)
So then I had to restore to stock...which downgraded it to 4.4.2 and I set up all my stuff on kitkat because the day I downgraded, it wasnt seeing the OTA update. Well the next day the OTA finally came through for 5.0.1...so I took it and when it it got done installing, this time, there was noticeable lag. Mostly from opening the app drawer...opening every time was a stuttering mess...also alot of the times scrolling screens.
I have read this phone is notorious for lag...but my original use with 5.0.1 wasnt bad...it was only after I downgraded to kitkat and then took the OTA.
should I have took the OTA, then factory reset, and then set it up? Maybe having everything setup on 4.4.2 and then taking the OTA caused the lag?
any help would be apprecaited...and I dont want to switch launchers...I always like to use the one that comes stock with the brand of phone.
thanks for any and all help.
joho5 said:
first off, I am new to the G3. I bought one used (in mint condition) and it had 5.0.1 on it. I loaded all my settings and apps that I typically use and to me it worked great...No huge amounts of lag...it was actually pretty smooth. Well when I installed TWRP, it wouldnt boot...it would get security boot error (or something like that)
So then I had to restore to stock...which downgraded it to 4.4.2 and I set up all my stuff on kitkat because the day I downgraded, it wasnt seeing the OTA update. Well the next day the OTA finally came through for 5.0.1...so I took it and when it it got done installing, this time, there was noticeable lag. Mostly from opening the app drawer...opening every time was a stuttering mess...also alot of the times scrolling screens.
I have read this phone is notorious for lag...but my original use with 5.0.1 wasnt bad...it was only after I downgraded to kitkat and then took the OTA.
should I have took the OTA, then factory reset, and then set it up? Maybe having everything setup on 4.4.2 and then taking the OTA caused the lag?
any help would be apprecaited...and I dont want to switch launchers...I always like to use the one that comes stock with the brand of phone.
thanks for any and all help.
Click to expand...
Click to collapse
Always after doing an major update factory resetting is always recommend
Sent from my iPhone using Tapatalk
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
dorlow said:
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
Click to expand...
Click to collapse
It is the fault of the rom you installed. Since it is de-bloated, then the developer of that rom might have accidentally removed an important app or service which is the cause of all of your problems. It can be fixed it by installing the stock rom via odin, rooting the phone and installing a different rom.
You paid to root your phone?
This particular crash was the first time it happened on this pre-debloated rom. The previous ones have all been on the stock rom.
ok, last night my phone required an att update. It attempted to update and rebooted. Stuck in a boot loop. Couldn't get out of it. Would just sit at the AT&T logo indefinitely. This was with the stock ROM rooted. So, I had to reload stock room unrooted again. Does anyone else have this problem with the rooted stock rom? Basically it runs for a few weeks. Then AT&T attempts to update and crashes the OS.
You can't OTA update a rooted phone
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
dorlow said:
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
Click to expand...
Click to collapse
Freeze the updater service / process / app, clear the cache to remove the downloaded update
Can u explain further how to freeze the updater service?
Ok, I looked up how to freeze the updater service and did that. I re-unrooted the phone, rooted it, then froze the updater service. My phone never updated. This morning an app was crashing. Rebooted it and same thing. Stuck on the at&t logo and won't boot. I'm having to re-default it again. The phone never updated from AT&T. But something crashed it last night. No clue. Problem is when this happens, the phone never boots back up so I can't look at it to find out why it happened.