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

one plus nord accidental wipe of phone\ query about rooting to get data back

Good morning XDA really after some advice. I managed to wipe my phone last night by ending up in the boot options when putting it into my phone holder in the car. Unfortunately it set itself to Chinese and then i must have said yes to reset.
For some inexplicable reason it has not been backing up lots of my data (I'm sure i set that to backup to google drive) such as whatsup chats google photos etc since upgrade it in Jan by the looks of it. I've looked at a number of recovery software but they don't seem to bring much back or to do a deep scan they need to be rooted.
Is rooting the only way to look at the physical storage. As I'im pretty sure I'm correct in thinking that the data is not physically wiped as such. just removed the data table?
On my old oneplus 3 i rooted it and that stopped me getting updates. I'm hopping that some of you guys can help me with these question?
1) is there any software to get this back and if so what do people recommend
2) if I was to root my phone as (dr.phone wants to do for a deep scan) would this stop me getting updates.
3) and or would it be easy enough to re root back to how it would have been prior to rooting so that oneplus would update normally

Why didn't my apps install on my new U11+ ?

I just bought a U11+ as an upgrade to my U11 and am configuring it, which is taking longer than I expected because neither of the two backups I did (htc's and Backup Your Mobile) installed most of the apps (or their data). Also, I've had two System updates in the last two days.
I got my custom background, the Keep Notes app (plus its data) and Facebook; that's pretty much it.
What did I overlook?
Oh, yeah... I cannot find a setting to keep the display on when powered. Anyone know how to do that?

If you did a jump to a new OS version or device that may be why.
If you did any major firmware updates on the new device, it's factory reset time.
Otherwise clear the system cache.
Manually loading them may be your only option.
Welcome to the fking planet

blackhawk said:
If you did a jump to a new OS version or device that may be why.
Click to expand...
Click to collapse
That occurred to me when I (finally) checked the OS version and saw that it was 8.
I've been getting update notices for the last two days and the most recent one (the third) was the Android 9 OS (update # 2.19.401.2). Where can I check on official updates so I can get an idea when this will stop (because manually looking for updates this morning got me nothing, then I saw the update prompt a couple hours later).
Updated to 9, rebooted and verified that Google Drive is connected, but I'm still not getting Backup & Restore to work. Will have to experiment with the others.

Jeff in 92833 said:
That occurred to me when I (finally) checked the OS version and saw that it was 8.
I've been getting update notices for the last two days and the most recent one (the third) was the Android 9 OS (update # 2.19.401.2). Where can I check on official updates so I can get an idea when this will stop (because manually looking for updates this morning got me nothing, then I saw the update prompt a couple hours later).
Updated to 9, rebooted and verified that Google Drive is connected, but I'm still not getting Backup & Restore to work. Will have to experiment with the others.
Click to expand...
Click to collapse
I learned long ago that if your OS is fast, stable and fulfilling its mission, let it be.
I've been on Pie for 2 years, my last reload was 1.5 years ago, still fast and stable with minimum maintenance. What's not to like?
Unless you start screwing with the firmware and bring in new issues that need fixed.
Security generally isn't an issue unless you do something stupid.
There's no saving dumb bunnies... be careful what you load and download.

blackhawk said:
If you did a jump to a new OS version or device that may be why.
If you did any major firmware updates on the new device, it's factory reset time.
Otherwise clear the system cache.
Manually loading them may be your only option.
Welcome to the fking planet
Click to expand...
Click to collapse
I did a Factory Reset (but it stayed Android 9). I did this because I had 'restored' a lot of files from Backup Your Mobile's (aka BYM) work on my U11.
Two things are bothering me:
1) The HTC Transfer Tool is not working this time (it transfers the PIN Code, but never gets to CONFIRM. After repeated attempts following reboots, etc., I have noticed that the PIN Code sometimes flickers off and back on again; what's up with that?).
2) BYM transferred my SMS and MMS to my U11+, but clicking on a text message that includes an MMS just makes the message thread avatar flicker and stay on the message thread listing (not even a flicker of the thread is displayed).

You mean screen lock codes?
First I don't password lock devices. You're the most likely one to end up getting locked out.
If you do use one I wouldn't attempt to back it up and transfer it. If it gets corrupted what follows won't be fun.
Pie's a good OS.
Clearing the system cache never hurts to try when experiencing glitches.

blackhawk said:
You mean screen lock codes?
First I don't password lock devices. You're the most likely one to end up getting locked out.
If you do use one I wouldn't attempt to back it up and transfer it. If it gets corrupted what follows won't be fun.
Pie's a good OS.
Clearing the system cache never hurts to try when experiencing glitches.
Click to expand...
Click to collapse
No, I did not mean screen lock codes. The HTC Transfer utility worked the first time I tried it before the Factory Reset, but it's not working now. The PIN Code is displayed on the source phone, but it doesn't activate the confirmation button to do the transfer.
I have since learned that many of the apps that were copied over via Google Play's utility also transferred the data, but not all the apps were transferred.
More research to be done, it seems.

Jeff in 92833 said:
No, I did not mean screen lock codes. The HTC Transfer utility worked the first time I tried it before the Factory Reset, but it's not working now. The PIN Code is displayed on the source phone, but it doesn't activate the confirmation button to do the transfer.
I have since learned that many of the apps that were copied over via Google Play's utility also transferred the data, but not all the apps were transferred.
More research to be done, it seems.
Click to expand...
Click to collapse
My bad... I use Google search a lot and it doesn't need to be that specific model or OS version most times. Many of the issues are long standing. I even use solutions for other manufacturers models. Whatever comes in handy.
And/or just play with it until I work it out.
I haven't used that app. If you upgraded the firmware or are transferring data from another device these kind apps can screw up especially with app settings.
If you're doing a factory reset because of an issue or a crash they can inadvertently reload the root cause of the issue.
It's nice to save the homescreen, theme, icon setting on a reload using these though. Most apps I hand reload/configure or use the app's backup setting file like with Poweramp or DIGI Clock which are very intensive to set from scratch.
Critical data I save in a master backup folder(s) as files. Be ready to reload at any time as most crashes while rare give little or no warning. Redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Most times a factory reset is to give the device a clean slate. Looking over app settings while setting them up helps to spot things you may have previously missed. It helps a lot to be familiar with the nuts and bolts at the user interface level. Many times when troubleshooting this is where the answers lurk.
I consider my first load or two on a new phone trail runs. After which it's pretty well sorted out for a clean load. I do the same on PCs. Android's are very forgiving but poorly written apps or the user can still skew hidden user settings that are hard to find/access on a stock device. A stable, fast load is a pleasure to use and will run well for a long time with only simple maintenance on a stock Android.