Database Info

[Q] Help - Verizon 4.0.4 OTA - Galaxy Nexus

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.

unknowingly bought a rooted G Flex 2 LSS996

Hello everyone,
Around the black friday weekend, I have purchased a LG G Flex 2 LSS996 on a ebay store. It was unlocked and worked as advertised on 5.1.1.
I could never install any android or firmware updates, which didn't bother me until I also got the throttling/ overheating problem. That's when I noticed that the phone actually is rooted. I wish to upgrade my Android now, which is why I am thinking of unrooting the phone. I thought of ROMs as well, but I haven't found any and I don't have the time and knowledge for ROMs or Xposed Framework.
I'm not sure why or how this phone was rooted, but I fear it has something to do with the carrier unlock since it is a LSS996 for Sprint. Because I want to use this phone outside of the US, the phone would be unusable for me in case the phone gets the carrier lock again if I unroot. Would this be the case?
I'd be happy about any reply! Thanks!
EDIT: still looking through this forum.
Just found this: http://forum.xda-developers.com/g-flex2/help/managed-to-gsm-ls996-awaited-apn-t3090484
Meaning that the seller probably did the same thing right? Will unrooting lock the phone again? I'm not sure what exactly what unrooting does to the phone in regards to these files. I would unroot via SuperSU
Some other things worth mentioning:
- The "hands-free activation" (not sure what it's called in English, I use the phone in German), which starts on every phone start up, never finishes properly. I can let it run through its 5 cycles or press activate, either way it fails.
- When I press "activate this device" in the system settings, a black screen with "self service" on top opens and the immediately closes.
- When I want to update PRL, profile or firmware in system settings -> software updates, I always get an authentication error.
Other than that and the throttling/ overheating issue, the phone works just fine.

I also have the same device. The phone is rooted because someone modified system files to unlock it. You can flash an unrooted system image for your software version and update the phone, and you wont lose carrier unlock. The things you have mentioned are normal for such a device, since it is not unlocked by Sprint.

Thanks for the reply!
How do you suggest flashing? I'm not finished researching, but so far flash fire looks like the most convenient option.

How do I fix strange behavior after 7.1.1 OTA update?

I have a Pixel and recently received the 7.1.1 OTA update. This morning my phone restarted and failed to boot properly. It does boot, and I get to the home screen where all apps seem to be functional. But there are several problems, including 1) I can't turn on cellular data, 2) the home button and the task switcher button do not work. Also, when I press the back, home or task switcher buttons, I get vibration feedback which is not how I had the phone set. Another odd thing is that when I check settings, it shows that the phone is on Android version 7.1 It is as if the phone tried to revert back to 7.1, but did not do so fully. Another anomaly is that when I got to the Play Store, all my apps appear as if they are not updated, even though I just installed available updates yesterday.
When I go to System Update, it shows a 261.9 MB update available to download. I assume that's 7.1.1 OTA update. I could try downloading and re-installing it, but before doing so, I wanted to see if anyone thinks that could cause more problems. Or, does anyone have another suggested step I could take. I would like to avoid a factory reset, if possible. Hopefully, there's another simple, quick solution.

Most likely it is easily fixable by just flashing the full stock 7.1.1 image from Google. Unfortunately it will wipe your device, but it is basically a surefire way to fix whatever went wrong.

It sounds like what happened is the OTA failed somewhere, bad download etc. As the pixel has the dual partitions if an OTA fails it will revert back to the last known working system. As @renegadeone8 mentioned, flashing the full 7.1.1 zip should cure your issues. You will have to unlock the bootloader to do so. (No a bad idea anyway imho Incase you have errors)
No harm in trying the OTA again. If it fails you won't be any further behind than you are now.

I'm having very similar issues, I also have no notifications and cannot pull down the full drop down menu or turn my data back on.

Thanks, k.s.deviate. I wish I had read your response earlier. It probably would have been good for me to at least try re-installing 7.1.1 again. However, I read from users on a different forum that they had experienced odd behavior very similar to what I experienced. In their case they didn't realize, at first, that the problem was associated with the 7.1.1 update. So, they re-installed it. Unfortunately, they had the same problems re-occur. For them the only solution was a factory reset and then not downloading 7.1.1 again.
That's what I've done. Everything is working great now. Android shows the 7.1.1 update available. Based on your assessment, I'm partially tempted to try installing it again. However, if it does end up with problems again, like it did the first time, I don't feel like I have the time to go through the whole factory re-install process again. So, I'm just going to stick with 7.1 for now and wait until either 1) I feel I have more time or 2) Google releases another update (7.1.2 ?) that might fix this problem. Thanks, again, though for your feedback.

exactly same here, so bad download could be ruled out. Also I've seen discussion on reddit and google forum, but unfortunely no solution was presented

After upgrading to Nougat S6 keep showing ' System Update Ready To Install' daily.

Hi, please be kind to a newbie here.. I'm in my 70's and obviously have no idea what I'm doing with the new (to me ) technology. My Galaxy S6 (verizon) is completely stock and keeps draining battery, needed to charge twice daily! Since I couldn't find obvious problem I downloaded SmartSwitch , did the system backup and doing research on internet I read somewhere the new firmware supposedly improve battery life. So I downloaded the Nougat firmware along with Odin and proceed. All went well, was able to restore all the settings and as far as I can tell all is well. The phone battery can last 2 days easily. Now the problem. . Every day now I'm getting notifications on my phone "System Update Ready To Install". When told to install it, the phone goes thru it's routine, downloading the update, rebooting, and installing.. Just to stop on 'blue screen' @27%
everytime! When using the SmartSwitch and clicking on the phone it does say the phone is up to date. So my questions are..
a) Why I get notification on phone, and Samsung SmartSwitch says the opposite?
b) Should I ignore the notifications and just live with the nag message?
c) Should I disable notifications for this, and stop it from appearing?
d) How to go about doing that>
Any suggestions/ideas (other than replacing the phone) are appreciated.
Thank you.

H910 OTA update popped up today?

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.