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.
Hey Guys -
I hope this is the correct forum to post this in - its the closest I could find...
After owning an Nvidia Shield (now "Portable") and loving it, I went ahead and purchased an Nvidia Tablet which came in 3-4 days ago. It's great except for that without the Controller (which is on Backorder ), you really can't do anything a standard tablet doesn't do.
Once updated, I rooted it and proceeded to install all the tools and apps I use. One thing I had always wanted to try out was the Modded Google Play. I saw that it had an installer so installed it and applied the modded version. Once back up, I had some difficulty with stability so went back to the original version installed (4.8.20.)
Since then, sometimes when I boot up, WiFi doesn't work and is disabled. I'm not saying I can't connect, but that it's in the "Off" position and greyed out to where I cannot turn it on! After a 2nd reboot, it would work again.
Yesterday, I rebooted and it was disabled again. This time, though, no matter how many times I restarted, it was still disabled!! I tried uninstalling / reinstalling Google Play a few more times as well as a few other reboots with no luck.
I will also say that I tried one more thing which may be the cause. I tried out Freedom to check it out, but it crashed when opening plus I found out it takes away functionality so uninstalled it. After uninstall, I found out the hard way that I had to rename my hosts file to get online working. At that point, though, WiFi would at least be enabled.
Any suggestions for what I can do? If I need to restore to OEM, I will - I just need to know the correct process as I am rooted. I'm on build KOT49H.20258_426.6902.
Thanks!
I had this happen when I first booted mine up. Then again when I unlocked the bootloader. I didn't do anything other then keep trying and it came on. It hasn't done it since.
Sent from my XT1060 using Tapatalk
Thanks for the reply. I ended up just performing a full reset and starting from scratch. At least I know what I want installed on it, now. That resolved the issue and it retained the root.
Thanks Guys
I was really worried about it, I chatted with nvidia support and they said to return it to the store. For whatever reason it started working, and hasn't done it since. I've seen a couple posts on it, so it might be a software bug.
Sent from my SHIELD Tablet using Tapatalk
Hi all. 1st post here.
I've been having a lot of trouble with my Galaxy Tab 2 lately. I rooted it a long time ago. Never had trouble with it. A few days ago, after charging it, I tried to start it, but when it starter, after a minute or so, it restarted. Normally the tablet only did that when it was froze due to many apps or processes being used at the same time. The problem is that the tablet never started properly after that one time. It's on some type of infinite loop. It starts, stays on for 1 or 2 minutes and then freezes and restarts. Well, i thought what most people would think at the moment: "I need to reset the tablet". I went to Recovery mod, made the format, but when the tablet rebooted, everything was untouched. No format. Odd to me. I then tried to return to stock. If it after that the problem was still there, at least I could be able to call for warranty. Odin gave me a lot of failed errors when I was trying but there was once that it said "Pass". Rebooted, still the same. Updated the recovery, tried to format, still the same. I'm running out of options right now. I don't really know what can be the problem and how can I fix it. I thought that if there was a way to format it like in recovery but using my PC it would do something (or not)
I appreciate any type of help.
So, I know am not as knowledgeable as most on this forum, so please be gentle!
I am using the TF700-t, 64 GB internal, with a 64 GB sdcard.
I installed Crombi-kk 4.4.4 on my TF700 a few months ago. Everything worked fine for a couple of months, then I started noticing apps would freeze, the tablet would suddenly reboot on its' own volition...the tablet seemed to have a mind of its' own!
I formatted the tablet, reinstalled, clean install of apps (no backed up data), it worked fine for a few weeks, then the same issues, along with app icons suddenly disappearing from the main screen and new app icons appearing on their own. Really spooky!
Three days ago, I formatted the tablet, installed Crombi-kk again, clean app install, worked fine for a few hours, then started misbehaving again, with the same issues, but now some of the apps (e.g.: Alarm Clock Xtreme) did not function at all (resulting in me oversleeping and being late for work).
Today, I formatted the tablet twice, reinstalled Crombi-kk, installed apps, and rebooted after each app installation (prior to opening the apps). I am noticing that some apps (specifically Google Play Music) refuse to open on the tablet (Apollo works fine). Several apps take a significantly long amount of time to open. There is no seeming pattern as to the issue.
Call me perplexed in North Carolina! Any suggestions or ideas as to what could be occuring? I am on the verge of going out and purchasing a new tablet (but it will not be another ASUS), but do not really want to spend the bucks.
Are you on the correct bootloader???
Other than that, I would recommend to flash a different rom and see if you get the same problems.
I would start with CROMI-X or even stock rooted, try ZOMBi, CM11 - lots to choose from.
That should tell you if this is rom specific or unique to your tablet.
Since I have had this tablet remote it has behaved completely erratically. I thought maybe a software update would fix the issue but it is still the same POS as day one. Constant reboots. Always goes through an optimizing apps process. (for a different number of apps each time). It doesn't always complete the optimizing process before it reboots so now it usually just goes into a weird boot loop 95% of the time. I have done a factory reset on the device many times and it always goes back to the same behavior. Everything points to a corrupt install of whatever pos vizio android rom came installed. I was hoping someone out there had a good install and could create a rom image for me to flash on this pos before I just break the damn thing.
And what I have been using in the meantime is my phone with the vizio smartcast app.