The 4.0.4 OTA update was waiting for me when I woke up this morning. I started the install but when it went to reboot it hung up with a picture of the Android man on his back with a red error/warning triangle.
I haven't done anything with it, hoping someone might be able to help me out.
The phone is rooted but running 4.0.2 stock rom. the battery was a little low when i started the install, but i plugged it in before starting.
Thanks in advance for help,
jvoosh
the reason is that your phone is rooted ,so ... if you want OTA ,you had better unroot you rom or ruu
so can I hard reset the phone (pull the battery) without screwing anything up and then figure out how to unroot the phone?
thanks for your help,
j
Ditto
I'm in exactly the same boat, and hope someone answers this before I try a battery pull.
EDIT: I read around and found some people describing our situation, and mentioning that they did battery pulls to no avail. So I did, and nothing broke. However, the update didn't go through, and now I'm trying to figure out why this happened.
Same issue
I'm having the same issue. Phone got the IMM76k update, and after downloaded, was prompted to restart and install. So i did, gets through part of the install, and then goes to the android man on his back with a red exclamation mark. Have tried multiple times, all to no avail. Now, when I click check for update, it says system up to date, but still on 4.0.2.
Non-rooted, bootloader unlocked...anyone have any luck fixing this?
After downloading update, get Android man on back with red exclamation point
I'm having some difficulty getting the update to install, along the lines of some of the comments posted before mine:
I was able to force download the OTA update (IMM76K) according to the instructions on this original post. (It took a few tries, but eventually worked.)
I select the "Restart & Install" option (which is the only option available to me), and it restarts.
I get the relatively familiar Android man with his blue-green glowing polyhedron wireframe guts spinning, and a progress bar beneath him. After getting through what looks like about 20%, it slows down significantly, and I get the Android man on his back with a red exclamation point above him where the polyhedron used to be. I don't recall seeing any specific error message any of the three times that I tried this. (The first time, I did a battery pull; the second and third times, I just waited, and it eventually restarted on its own.) Needless to say, I'm still on 4.0.2.
I'm afraid I'm not very familiar with different version names and so forth (e.g,. I don't know what yakju is), but this was a phone that Verizon sent me in December 2011 here in the US.
Here's the information from my "About phone" page:
Model number: Galaxy Nexus
Android version: 4.0.2
Baseband version: I515.09 V.EK05 / I515.EK02
Kernel version: 3.0.8-gaaa2611 [email protected] #1
Build number: ICL53F
When I first got the phone, I immediately unlocked the bootloader and rooted it. I did NOT install a custom recovery, nor did I install any custom ROM.
It sounds like there might be some kind of validation error, but I do not recall doing anything that would make my OS non-stock, except perhaps side-loading Google Wallet, but since that doesn't even require root, I can't imagine that it would have any effect. My Superuser app shows only the following apps to have ever used root permissions: BusyBox Free, Secure Settings, Superuser, Terminal Emulator, and Titanium Backup. I've only used BusyBox and Secure Settings with Tasker to automate certain tasks, but nothing crazy! Mostly, I just need root for Titanium Backup. (I cannot recall exactly what I restored from my stock Gingerbread Droid X, but I was very careful to only restore apps and their corresponding app data--and I avoided restoring any Google-provided apps.) Even my tethering is done through an app not requiring root (SVTP).
Any advice (not requiring that I do a factory reset or flash a custom recovery or ROM) would be greatly appreciated! I'd also like to hear about people who have similar circumstances, but didn't have problems updating (so that I can rule out various factors).
Thank you in advance!
same exact issue here.
A "solution", albeit less than ideal
The OTA update eventually came to my phone naturally, and it still didn't work. (No surprise there.)
I called up Verizon tech support, and they had me do the Google Services Framework workaround to try to force the update again. Of course, it didn't work.
They said "We're going to need you to reset your device." (i.e., to factory default).
I told them that was wholly unacceptable, since I want to make sure that all my settings are preserved. (I'm kind of obsessive compulsive about things being set the way I like them, and Titanium Backup, as great a program as it is, has sometimes caused some trouble for me when restoring system settings, and especially since I'd be doing a restore after upgrading the OS, I was nervous about that option.)
Verizon got Samsung on the phone. They had no advice except "We're going to need you to reset your device." Both the Verizon rep and I told him that wasn't acceptable.
So Verizon's "solution" was to send me a new device, allow me five days to get everything transferred over, and then have me return the old device.
Up side: In case there was something wrong with my hardware or something else got messed up, I get a new device that I can get set up with the exact same settings as the old one.
Down side: The "new device" is refurbished, so there could potentially be some kind of baggage.
The "new device" came with 4.0.2. I booted it up without the SIM card, skipped all the logging in to Google, and immediately started going through the steps to unlock the bootloader and root the device. (I used the Galaxy Nexus Root Toolkit, which worked like a charm on a 64-bit Windows 7 machine I had lying around.) After unlocking and rooting, I logged into the device with my Google credentials and let it restore my settings and apps that I had downloaded from Google Play.
Then, it notified me that the 4.0.4 (IMM76K) update was available, so I installed that, and it worked without a problem.
Then, I installed the SIM card and got the new device activated through Verizon's website for activation.
Then, with both devices side by side, I went through every phone setting and made sure it's what I wanted, I made sure every app was installed (and if it was a non-Google Play app, I restored it through Titanium Backup), and I restored data for apps that don't store their data in the cloud (e.g., various games) through Titanium Backup. (I made a backup of my old device with Titanium Backup and transferred it over to the new device after getting the new one up and running.)
Everything seems to be working just fine, and the "new device" runs a bit faster and smoother than the old device, and that's with both devices rebooting and then going through the exact same "click paths", side by side.
So it's a bit of a hassle, but everyone who has a Galaxy Nexus should still be under warranty, so if you're polite with your Verizon tech support representative, they may be willing to help you out.
Verizon can sometimes be infuriating with their update release schedule and keeping their customers informed, but they sure do a good job accommodating their customers in other ways.
I realize this isn't really a "solution" to the Android man on his back problem, but this seemed to be the path of least resistance for me, and I'm pretty happy with the outcome so far. (It's been less than 24 hours since I got the "new device" set up!)
Other things I realized I should have tried (and still may, before I wipe my phone and send it back):
- uninstalling BusyBox (through the app itself, since it makes modifications to the system) and Secure Settings
- unrooting
Good luck!
My friend who has a nexus has his bootloader unlocked and CWM on it. He got the OTA today on his way into work and like you guys, he has a broken android when he boots up. We can get into CMW but we are unable to mount his internal SD storage onto our computer and he has no ROM zips on his phone. Any advice as to how to get his phone up and running?
Will wiping the system/data fix it? Is there a way to get a ROM like AOKP onto the device outside of CWM?
Edit: After several reboots it decided to just boot into the stock ROM. Really strange. Anyhow, flashed AOKP and all is well now.
Related
I upgraded my AT&T Samsung Captivate from Froyo to Gingerbread a couple weeks ago, when AT&T released it. I had nothing but problems with it - my phone would reboot repeatedly, it would freeze multiple times a day. I tried factory resets, GSM resets, removing apps, nothing helped. My phone was basically unusable. I gave up and took it to a local AT&T Service Center. They seemed very aware of the problems, and recommended reverting it back to Froyo. I had them go ahead and do it. They got Froyo back on it, although they somehow broke the Contacts. Each time they pressed the Contacts icon the phone would Force Close. The "tech" didn't know what to do about it, and recommended that I go to the AT&T Retail Store and see if I was eligible to buy a new phone! Once home, I did a Factory Reset (from the Menu button), which resolved the Contacts issue.
I'm OK with having Froyo instead of Gingerbread. There are a couple features I like better in Froyo anyway (Data Network Mode off the power button, Silent option from the pulldown menu). The only thing I miss is the ability to install non-Market apps. I figured the easiest way to get that would be to root the phone (I had rooted a previous Captivate, but didn't do this one after it was replaced, since I was waiting for the Gingerbread update). Anyway, I downloaded the latest version of SuperOneClick and installed it, but when I try to run it I get an error message, saying that SOC stopped working and Windows is looking for a solution. I’ve tried running it on Win7 32 bit and Vista 32 bit machines with the same results. I’ve tried running it as an Administrator. I’ve Allowed it when asked for permission. Is there something I'm missing in order to get the program to run? I know there are other ways to root it, and other ROMs that I could run that people here would say are way better. I like SOC because it's fast, easy, and allows me to unroot if necessary. Froyo does what I need it to do, so I don't need a different ROM. Can someone just please tell me what I need to do to get SuperOneClick to run?
BTW, before anyone suggests it, before even trying to root I called AT&T Tech Support and asked them to push a patch which would allow me to install non-Market apps. After 1 hour and 22 minutes on the phone, in which the tech consulted his manager, and a higher level tech support in Alabama, they determined that it could not be sent to my phone (just kept saying Pending). They really couldn't explain why it wouldn't work, just that it wouldn't. Rooting seems to be my best and easiest bet.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I managed to get SuperOneClick running and was able to root my phone. I think the problem was that I had downloaded multiple versions in my attempt to get it to work and they weren't playing together well.
Maybe it could be a driver incident... check it how to fix it dude.
So I've read here about people doing upgrades to 1.63.xxxx stock ROM, but whenever I run HTC update I'm told there are no updates :/
Do you have to be on T-Mobile network for OTA update/upgrade to work or what?
Sorry to tell you this but u have missed the update. I don't know no other way to get it but your not missing nothing. Hell I'm not even using the stock launcher so yea.
MT4GS said:
So I've read here about people doing upgrades to 1.63.xxxx stock ROM, but whenever I run HTC update I'm told there are no updates :/
Do you have to be on T-Mobile network for OTA update/upgrade to work or what?
Click to expand...
Click to collapse
For the OTA, yes, you would have needed to be on T-Mobile. However, there are pure stock 1.63.531.2 as well as "tweaked/optimised/debloated" versions of that ROM now available here to download and install, if you're rooted.
I am running the MikTouch 0.7 ROM, which is an optimized version of the stock 1.63.531.2 ROM. It is fast, clean, everything works as it is supposed to work without any weirdness.
Thx for replies.
I can't get "MikTouch" or any other ROMs because I haven't "rooted" my phone yet. I never do anything if I don't fully understand "what it does", and since nobody have answered my questions here:
http://forum.xda-developers.com/showthread.php?t=1659952 -
and being new to Android and to this phone - I only did what I did understand... so my phone is unlocked but not rooted yet (and still with s-on).
What I did to get OTA update:
- I removed my SIM card
- I removed my microSD card
- Shutdown the phone.
Then I charged my phone and removed battery for few seconds when it was full, and inserted the battery and microSD card back (also I moved everything off the card and formatted on my computer before I inserted it back).
- Entered hboot menu (volume down + power button)
- Selected Factory Reset
After phone rebooted and started up it asked me to setup gmail account- I wanted to follow this "setup wizard", but without SIM card there was no data connection and it seems impossible to finish it without logging-in to gmail first (? it seems that way?) so I just cancel it and I setup my home wi-fi connection, and once I saw wi-fi working I restarted the phone.
"Setup wizard" started again after reboot and this time I finish setting up my gmail account.
- Then I had notification about HTC update available. I run it, and after it rebooted itself 2 times (maybe 3 times, I didn't stare at it all the time) it wiped out everything (I think) because it started with "setup wizard" again, so I knew it must have updated the ROM. I went to my phone's About Phone -> Software number and sure it is version "1.63.531.2.710RD" now
I have hard reset it again ("factory reset") and am using it since morning.
There are few changes I have noticed so far.
edit: Main difference I have noticed so far: "Visual Voicemail" somewhat partially work with my provider (Wind does NOt have visual voicemail). By partially I mean that now when I have new voicemail I also have another notification as if it came from the person who left the voicemail, saying for example "(number) I have left you a voicemail (length of the message). Press 00021 to listen to the message or go to voicemail" or something like this. When I touched the clickable "00021" it went straight to this message in my voicemail - nice! - even though Wind Mobile doesn't have Visual Voicemail, so I guess it is some general GSM networks option I didn't knew about. Anyways, with previous software I never had such message or notification, phone simply showed usual Voicemail icon and notification only.
MT4GS said:
Thx for replies.
I can't get "MikTouch" or any other ROMs because I haven't "rooted" my phone yet. I never do anything if I don't fully understand "what it does", and since nobody have answered my questions here:
http://forum.xda-developers.com/showthread.php?t=1659952 -
and being new to Android and to this phone - I only did what I did understand... so my phone is unlocked but not rooted yet (and still with s-on).
What I did to get OTA update:
- I removed my SIM card
- I removed my microSD card
- Shutdown the phone.
Then I charged my phone and removed battery for few seconds when it was full, and inserted the battery and microSD card back (also I moved everything off the card and formatted on my computer before I inserted it back).
- Entered hboot menu (volume down + power button)
- Selected Factory Reset
After phone rebooted and started up it asked me to setup gmail account- I wanted to follow this "setup wizard", but without SIM card there was no data connection and it seems impossible to finish it without logging-in to gmail first (? it seems that way?) so I just cancel it and I setup my home wi-fi connection, and once I saw wi-fi working I restarted the phone.
"Setup wizard" started again after reboot and this time I finish setting up my gmail account.
- Then I had notification about HTC update available. I run it, and after it rebooted itself 2 times (maybe 3 times, I didn't stare at it all the time) it wiped out everything (I think) because it started with "setup wizard" again, so I knew it must have updated the ROM. I went to my phone's About Phone -> Software number and sure it is version "1.63.531.2.710RD" now
I have hard reset it again ("factory reset") and am using it since morning.
There are few changes I have noticed so far.
edit: Main difference I have noticed so far: "Visual Voicemail" somewhat partially work with my provider (Wind does NOt have visual voicemail). By partially I mean that now when I have new voicemail I also have another notification as if it came from the person who left the voicemail, saying for example "(number) I have left you a voicemail (length of the message). Press 00021 to listen to the message or go to voicemail" or something like this. When I touched the clickable "00021" it went straight to this message in my voicemail - nice! - even though Wind Mobile doesn't have Visual Voicemail, so I guess it is some general GSM networks option I didn't knew about. Anyways, with previous software I never had such message or notification, phone simply showed usual Voicemail icon and notification only.
Click to expand...
Click to collapse
If you are "unlocked", you could easily flash CWM Recovery and other ROMS, it just requires an extra step since you are still S-On (flashing the boot.img through fastboot). Also, being unlocked means you can also easily root with just a simple flash. So, you could flash the MikTouch ROM and enjoy the same 1.63.531.2 level of service but in a more optimized and tweaked manner, that is also rooted.
But, if you're happy the way you are, then, "if it isn't broken, don't fix it".
Yes the MikTouch seems like the one I would love to try. I always prefer "minimal ROMs", because if I like the ROM I usually keep it forever and I don't want any obsolete app's "junk bytes" taking space inside the ROM image.
The stock 1.45.x and 1.65.x ROMs seem actually usable, but even though T-Mobile have crapped them with much less garbage (than what I usually saw in their Windows Mobile ROMs), there are still many "apps" I would like to get rid of. So yes, I would want to root my phone at least for "debloating" purpose.
Unfortunately most of knowledge and instructions here always assume the reader already knows more than "basics" about Android. But what is obvious to the devs actually often confuse noobs to Android like myself... That's why I'm still "stuck" unrooted yet.
For example:
You said "easily flash CWM Recovery" - OK, but what are the exact steps? (I have already asked this here: http://forum.xda-developers.com/show....php?t=1659952 ) Not to mention I still don't know which recovery I should actually go with (CWM or "Stock") and why...
MT4GS said:
Yes the MikTouch seems like the one I would love to try. I always prefer "minimal ROMs", because if I like the ROM I usually keep it forever and I don't want any obsolete app's "junk bytes" taking space inside the ROM image.
The stock 1.45.x and 1.65.x ROMs seem actually usable, but even though T-Mobile have crapped them with much less garbage (than what I usually saw in their Windows Mobile ROMs), there are still many "apps" I would like to get rid of. So yes, I would want to root my phone at least for "debloating" purpose.
Unfortunately most of knowledge and instructions here always assume the reader already knows more than "basics" about Android. But what is obvious to the devs actually often confuse noobs to Android like myself... That's why I'm still "stuck" unrooted yet.
For example:
You said "easily flash CWM Recovery" - OK, but what are the exact steps? (I have already asked this here: http://forum.xda-developers.com/show....php?t=1659952 ) Not to mention I still don't know which recovery I should actually go with (CWM or "Stock") and why...
Click to expand...
Click to collapse
Since you are S-On Unlocked, you could flash CWM Recovery (version 5.0.2.7). That gives you much more capability, like doing a nandroid backup/restore. You would do that using flashboot. Obtain the correct recovery.img, do fastboot flash recovery recovery.img and then you're ready. From then on you can boot into HBOOT, choose Recovery and then flash ROMs or other packages, including the SU (for rooting). The Miktouch ROM is already rooted, so all you would need is to flash CWM, then the ROM. Since it is still Sense, as soon as I signed in with Google, it automatically synced all my apps and contacts, which is a nice bonus.
Hello all,
I'm sorry, but I couldn't find any device-related subforum for the Samsung Galaxy Rugby (GT-S5690M). If my questions are in the wrong section, please move it to the right place (mods)?
So here's the story: I just got my first smartphone. Since it's locked to Bell, it has some bloatware and need for sim-unlocking. I did a lot of reading and through some tutorials I managed to root Android and got rid of some bloatware (just four Bell apps). So far so good! Then I tried to unlock the phone. There are some apps in the Google Play that state that they can unlock the phone for free ("works on various Galaxy models").
I tried them out, but none of them could provide a solution. The last app I tried (Galaxy_S Unlock) requested that BusyBox were to be installed, so I did. During the installation the app remarked that already some BusyBox version was installed, but not the version that it was trying to install. I was suppose to try another type of installing (I used the normal/safe mode). But it said it was already installed, so good enough. Right? I tried the unlocking app again, but it still said it had errors getting to communicate with BusyBox. None of the unlocking apps gave me the impression that they changed anything in the system.
I figured that maybe a reboot of the phone would fix this. However, now the phone got several issues:
- booting takes forever (18 minutes) It does the animated Samsung logo (though, not with sound any more) and then keeps on slowing the glowing Samsung name.
- the speaker doesn't seem to be working at all
- it can no longer check for updates. After agreeing with the disclaimer, it says it can't connect.
- KIES doesn't see the phone any more.
- the phone is generally very slow now. Even when typing a password the phone sometimes hangs for about 5-10 seconds. Loading the disclaimer for the Software Updater takes 10-15 seconds.
I tried to reset to factory defaults and reload the rooting zip file again, but to no avail.
I've been trying to read up on the isolated symptoms, but I'm simply starting to feel overloaded with all the info, especially since I'm a Android newbie.
Does anybody recognize these symptoms and, more important, has any tips on what to try to restore whatever has gone wrong?
Additionally, I would really be interested in knowing if there's a way to force-upgrade to Jelly Bean. It appears that this firmware hasn't been made available to Rugby users yet through the regular update channels. But are there alternatives?
Thanks in advance!
I got a notification on my phone that there is a software update available for my phone. After reading up on it a bit, I decided it's not worth the hassle to update. I thought I had gone through steps to suppress firmware updates a while back but I guess not. What's the easiest way to suppress this warning? Let me know when you get the chance. Thanks, guys!
Well, a bit of an update, I found the original information on how to suppress OTA updates here:
http://forum.xda-developers.com/showpost.php?p=56693607&postcount=370
As I thought before, I had already gone through this step and disabled it (it was disabled in the hidden menu already). However, the update still seems to have popped up. t tried to auto update this morning but reported back that it suspects my system is rooted so it wasn't able to install. That's good news to a point (at least it didn't screw anything up) but I don't like that it even attempted it without me giving it permission.
Any idea what might have changed? Or is there a difference between an OTA update and a "software update"?
I don't know the answer but I am having the same problem. My phone keeps restarting and giving the error that it wasn't able to install. This actually happened before when I was on 4.X and eventually it bricked my phone and the AT&T store couldn't fix it so they gave me a refurb. It sucked because I didn't have all my photos backed up(I have since fixed that problem.) Now I am having the same issue and I don't want it to brick my phone. I also hate that it restarts automatically...I might need to use my phone for something at the moment. I also have tried the info in the link to disable OTA both phones and neither time has it worked. If anyone can help, please do. Thanks.
The only thing I have ever done and has worked every time is to root and then freeze a file called. "software update" or "update manager". Hope this helps.
I would actually like someone to put together an update.zip that will update us to the latest version without having to go through the hassle of flashing back to stock and what not.
I like the idea of LTE voice calls but not so much that I am willing to go through the work of starting over.
sent from a location using an app
In Titanium Backup (or similar app) find the app call "Software Update 2.3.3.1" and freeze it
That is what solved me receiving software updates and I no longer see the option in the About phone area.
I'm on stock rooted ROM 20H sep 2018. Last time I checked (just now) this is still the latest verion.
However my H910 keeps bugging me about new update available from AT&T.
Does that happen to you guys?
It didn't give me any info about versions and so on.
Should I proceed?
I got it too. Came here to see if it was just me. I'm on H910 Oreo stock rooted.
Warning: DO NOT try to silence the nagging by blocking the notifications. AT&T/LG will treat "quit bothering me" like "go ahead, have your way", and simply go ahead and try to install the update without even bothering to ask you next time. If you're running RootedStock, you'll end up in a slow semi-bootloop where Android boots, you'll have about 3-5 minutes, then it will forcibly install the update, reboot, you'll end up in TWRP, and when you reboot to system (or power off, then power up later), the whole cycle will repeat.
I'm not sure how robustly my solution worked, but here's how I broke out of it. So far, about 15 minutes after rebooting, it seems to have worked. Since I'm writing this AFTER seemingly fixing the problem, I'm writing it from memory, and can't say with 100% certainty which step was actually the one that fixed the problem for me. I actually began the process of installing Titanium backup about a half-dozen FOTA-reboot cycles before tripping over another post here that advised deleting /cache/FOTA. Titanium Backup might, or might not, be an essential element of my apparent success. I honestly don't know. If you own it, use it... you have nothing to lose. If you don't already own it, try just deleting /cache/FOTA first from TWRP's file manager and see whether it works (temporarily or permanently).
Anyway... here's the approximate path to slaying the FOTA beast:
1. I installed Titanium Backup from Google Play. It actually took two reboot cycles to do this... you REALLY have to be ready to unlock the phone, launch Google Play, search for Titanium, and trigger its installation while standing a few feet from your wifi AP for it to finish the download and begin installing it before the next forced-update attempt begins. When it does, swear violently. It'll make you feel a tiny bit better.
1b. When FOTA forces the reboot into TWRP, try deleting /cache/FOTA before rebooting. It might work to temporarily slay the FOTA beast, it might not. If it does, it'll save you about 30 minutes of FOTA-reboot misery for the remaining steps. Feel free to repeat this after each of the following steps. It can't hurt.
2. On the next cycle, launch Google Play the moment your phone finishes booting, and go back to Titanium Backup. Hopefully, it'll be installing. With a little luck, installation will finish before FOTA begins. Then sigh, and let FOTA waste another 5 minutes of your time.
3. On the next cycle, launch Ti backup, give it permanent root permission, and give it permission to do everything it wants. Then, try to launch Google Play, search for Titanium, scroll down, select Ti Backup pro key, and try to initiate installation before FOTA kicks in yet again.
4. On the next cycle, launch Google Play, search for Titanium, scroll down, select the pro key, and begin installation if it isn't already downloading and/or installing. 99% likely you'll end up going through another round of FOTA misery.
4b. If FOTA is still forcing reboots up to this point, repeat step 1b before step 5.
5. On the next cycle, launch Titanium Backup, give it any additional permissions it wants, then select Backup/Restore, scroll down to "FOTA Update 8.0.0", and freeze it.
5b. If FOTA kicks in again, repeat step 1b.
If, despite deleting /cache/FOTA, then freezing FOTA Update 8.0.0 using Ti backup, then deleting /cache/FOTA again, it's still happening... well, then my solution didn't work for you (and possibly not for me. I'll start breathing again normally if my phone is still working normally tomorrow).
Anyway, hopefully this will help someone. I suspect a lot of people running RootedStock Oreo are going to get stung by this. I'd guess that more than a few v20 owners actually bought theirs long after AT&T's previous forced update, and have never actually HAD to deal with blocking forced updates with their current ROM.
It's entirely possible that purchasing Ti backup (I don't think the free version can freeze apps) will be essential for the H910 going forward if you want to keep using what was, prior to yesterday, the newest rooted-stock Oreo ROM without having AT&T's FOTA harass you every few hours (or wipe your phone and reflash once someone releases a newer build based on the current update). Trust me, you can't swat it away forever. I went through this forced-update nagging bull**** years ago with my Motorola Photon. Someday, when you least expect it, the dialog will come flying at you when you're driving and trying to select a song using Amazon Music, or in the middle of a phone call, or semi-distracted, or scrolling down a web page while the phone is bogged down because it's grinding its wheels in the background preparing to harass you about updating again, and you WILL accidentally click "ok" & have your life go down the toilet for the next few hours until you're able to dig yourself out of the mess.
Bite the bullet, and freeze FOTA Update 8.0.0 now, while you can still do it without burning an hour of your life waiting for reboot after reboot.
For those finding their way here, make sure to back up in the brief period of time before you get hamstrung if you can't freeze the process. I am/was bone stock H910 and after ATT forced the update on me, my phone now won't finish starting up and functionally boot-loops now until I pull the battery.
It will start, get to the home screen, I might get 5-15 seconds of actual usable time with the phone before it freezes, goes back to the bootscreen and will get warmer and warmer and give me less and less time until it freezes in the middle of the ATT logo. Tried pulling SD card and SIM card, just in case. The sim card removal bought me enough time to get the phone to tell me it was "finished updating" but upon attempting to power down and start re-inserting cards, the phone locked up and bootlooped.
No idea what this update is for but it seems to have killed my phone rather handily, beware.
FWIW, airplane mode does not stall the update either.
bitbang3r said:
Warning: DO NOT try to silence the nagging by blocking the notifications. AT&T/LG will treat "quit bothering me" like "go ahead, have your way", and simply go ahead and try to install the update without even bothering to ask you next time. If you're running Roote
Bite the bullet, and freeze FOTA Update 8.0.0 now, while you can still do it without burning an hour of your life waiting for reboot after reboot.
Click to expand...
Click to collapse
Hope I'm not jinxing myself, but this appears to have worked for me.
I have gotten a "update could not be installed" popup, which I'm taking to be a good sign.
Still annoying, since I have auto-updates turned off.
Ugh, it popped up again. Confirmed, FOTA is still frozen.
It initiated the update for me on its own. Luckily I noticed and plugged it in or it would have died and maybe bricked the phone.
I don't notice a difference. Same Android version (8.0) same security patch (Sept 2018). The ATT version might have gone from H to I.
Yep, it started nagging me again, too. Goddamn it, this is really starting to piss me off.
Okay, on mine I think when I delete /cache/FOTA while in TWRP, it might not actually be deleting the folder.
I deleted the folder in recovery mode, then rebooted and went straight to X-plore file manager. The FOTA folder was either still there, or it just recreated itself on boot. I deleted it again in X-plore and it's now been working since my previous post.
Fingers crossed.
I just rooted a H910 yesterday, and this morning the same "slow boot loop" with the update started. I tried different things, and what so far seems to have worked was:
1. Entered TWRP recovery (from the last "update cycle." (Not like I had a choice.)
2. Wiped everything and re-installed Oreo, and all other zip and img files back to the way I originally set it all up.
3. After phone was booted up, I DID NOT have a SIM card in it, nor did I enable WiFi.
4. Temporarily skipped all the Google sign in stuff.
5. Enabled Developer options, and turned off "automatic system updates." (Not Google Play Updates!)
6. Re-booted phone and then confirmed that the above setting still showed "off."
7. Enabled WiFi and connected.
8. Set up Google account and other misc settings.
9. Restored a backup that I had made prior to the phone doing the update reboot loop, but was careful to uncheck settings. I did not use Titanium Backup. I used the built in one.
NOTE: This is not my daily driver phone. It is meant to be used as an emergency backup phone in the event that my regular phone (Samsung Galaxy S Series) falls in a canal or gets run over by a truck. (Or City Bus)
So far so good. I will use the phone for the day and check again the following morning to see if it starts the forced update. I will check back here in a few days and let everyone know what the end result was.
My theory is that if the phone does not have a chance via cell data or WiFi to get any FOTA updates prior to me turning off the "automatic system updates" that is in the Developer Options, it will never check in with AT&T's update server.
I am not sure about this, and if someone else knows, please correct the following:
I don't think AT&T "pushes" updates out. At least the type of updates we are talking about. I believe the software in the phone periodically polls an AT&T update server, and "pulls" any update at a schedule time, or time interval. My working theory is that turning off the automatic system updates will disable this automatic check, or polling routine. If it already has an update that it downloaded prior to turning off automatic system updates, its too late.
Thanks for everyone's input on this in advance.