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.
Hello everyone.
So I just got this phone off of ebay recently, and yesterday I started getting the "System UI has stopped" message. I select the OK button and it just keeps repeating the same error and wont let me access the desktop.
Phone is stock, no root or twrp, with the latest sw update, and I am using Nova Launcher instead of the stock launcher.
I googled this problem and it seems that you need to reboot into recovery and wipe cache partition. I did that, and upon reboot I still get the same error.
I ended up going back into stock recovery and factory resetting.
Has anyone else encountered this problem?
UPDATE...
After factory resetting, I restored phone as a new device. A short time later, after updating apps and downloading some others, I once again got the System UI stopped error. Going back to my backup phone until I can get this sorted out.
UPDATE #2...
Sent BLU a trouble ticket via their tech support page on Sunday. In the meantime, did ANOTHER factory reset and whatnot over the weekend, and the phone was fine up until about an hour ago, and I got the same error.
This time, I called them directly. They actually had my trouble ticket on file, and asked me if I did a hard reset, which I have done MANY times.
They then apologized, and asked me where I bought the phone from (ebay auction).
They then told me that I need to obtain the original sales receipt of the phone in order to process a warranty claim. Now I gotta ask the person who sold me the phone if they still have the receipt?????
This is ridiculous.
Anyway, back to my Moto X pure 2015 until I get this sorted out.
Back to the matter at hand and not how unnecessary you may think it is to obtain a receipt for your purchase...
Can anyone install "MTK Engineering" from the Play Store, go to the "Log and Debugging" tab, open MTKLogger, start recording a video of the device, press play, reproduce the issue, then press stop to stop capturing logs?
BLU needs our help to capture logs since they can't reproduce the issue.
vicks1008 said:
Back to the matter at hand and not how unnecessary you may think it is to obtain a receipt for your purchase...
Can anyone install "MTK Engineering" from the Play Store, go to the "Log and Debugging" tab, open MTKLogger, start recording a video of the device, press play, reproduce the issue, then press stop to stop capturing logs?
BLU needs our help to capture logs since they can't reproduce the issue.
Click to expand...
Click to collapse
My advice would be: In SP flash tool load the Android scatter txt from the GIONEE E8 ROM(which can be found in the development thread), after loading that uncheck the top check mark so it clears all the other check marks. Then double click on the system field, navagate to where you have the stock BLU pure xl system image located(which can be found in the development thread), double click on it to load it into the system field. Then click download on SP flash tool, plug usb into computer, power off your phone hold the volume down key while plugging USB into phone. Then wait till the progress bar goes across the bottom in sp flash tool once its done flashing it will say success and now you will be flashed back to stock system. Hopefully this will get rid of whatever is corrupting your system.
Try running the phone without Nova .. I tried several launchers - and things didn't quite go right. What I've found is that not all applications run as smoothly as my OPO use to run - probably because my OPO was rooted and I pretty much did whatever I wanted with it. Not with this running stock - I don't have "proof" but the Pure XL really didn't like it when I installed a different launcher and/or themes .. once I uninstalled the launchers/themes - I rebooted and it was fine.
Jaybird thanks for the suggestion. However, I still had this issue even on stock launcher. I ended up selling the phone anyways.
And I must say here, I apologize if people were annoyed with the fact that I mentioned needing a receipt for my phone in order to send it in for repair/exhange.. This phone has been out for less then a year and in my opinion should be covered under warranty, whether i have a receipt or not.
Its 2016, don't tell me they can't look up the serial number and see that it's under warranty. But whatever.
Just would like to chime in and say I randomly got this same issue after getting a phone call. Suddenly I have no UI what-so-ever but apparently everything else works. I did see this flash of some screen saying "Preparing files for first time use..." just before I lost all ability to use my phone. And despite going into TWRP and clearing both Cache and Dalvik Cache I still have no ability to use my phone.
---------- Post added at 06:13 PM ---------- Previous post was at 05:54 PM ----------
I managed to get the phone working. Ran the factory reset through TWRP and it seems to be back in working order.
My brother inlaw won some cheap (he won it in a vending machine ) Android tablet (7") where you turn it on, you get a splash screen (Tablet PC, Keep Moving Forward) with some animation on that text, then the tablet reboots. Every now and then I have gotten to what seems to be the main screen (like maybe 2 or 3 times) but as soon as you touch the screen it reboots.
I know jack about Android but told him I would take a look. I assume a hardware problem or maybe something corrupt in the software. I have been able to boot into what I will call the root menu. I have tired clearing the user cache as well as a factory reset. No help.
I am thinking it is a hardware issue but it would seem worth reinstalling the software (4.4.4). I have not had much luck figuring out if I can do this (everything I seem to find is on updating the OS not reinstalling or flashing), where to get the files/rom or how to do this. Any direction would be appreciated
Hi
Assist is where we guide new users and we expect senior members to be able to navigate the site without assistance and ask for help in the correct sections
Sorry but thread closed
Hey!
So I have been using an android phone from 3 years now and I have been stuck in an huge problem! And I need your help in order to solve this problem. Here is the problem so basically I have a Freetel nico (Japanese brand) which is about 3 to 4 years now running on top of stock kitkat rom or in other words the same rom when I unboxed it. After few months my screen cracked on the bottom near the capacitive touch keys. After the crack the home buttom stopped working! I was all okay with that and the next day my notification panel started glitching and stopped showing any notifications which was really annoying. Now I knew that there some serious problem, so I taught of resetting the phone so I went in the setting and tried factory reset. After few minutes it didn't go to system recovery but the phone just restarted itself. I tried it once again and got the same problem, next step I had was to hard reset it by going into the recovery. When I hold the button and let go it didn't take me to the recovery this time also. So in conclusion I came to know that there was no recovery inside the phone (I did erase the phone through recover about 2 times before this incident everything went well during that time). Moving on I rooted the phone and installed SuperSU and other softwares that could install recovery mode to the phone. I got the same result this time also, I also tried installing a different rom through the stock system update app same result.... After a year of all this work I taught it would be best just giving it to the company service center but I came to know that the company had no longer selling this device and there is no service available .
After all of that tries above I still continued to solve this problem I tried ADB resetting it through pc no luck here also! So if you guys could recommend me some apps or softwares I could try in order to reset my phone please do let me know in the comments. Or you could also ask any scripts that you want to know from the phone which could solve the problem I can do that also!
Thank you
Darshan
Hey there forums.
I've been an active browser of XDA but never really created an account but I've done so to have assistance with a particular situation with my device.
So the other week, i had spent 150 dollars on a Sony Xperia XA F3115 from Vodafone, Australia and it turns out that the bootloader was locked because of Vodafone and i wasn't going to pay 50 dollars to unlock it. I alternated and browsed the internet (Mostly XDA but other sources aswell) to figure out if there were any methods of bypassing this, whether it be easy or not - I was willing to try anything that seemed like it had a chance to work, without a 100% failure rate. Reading responses to particular methods, i was drawn into one method of just reflashing the stock firmware onto the device and then rooting, flashing and doing everything from there (as the device was no longer locked by Vodafone at that point).
I have completed this task as of this morning, and the device booted successfully. As soon as i unlocked my device, i had received the general android setup window but half way through, i got spammed with "Name has stopped responding" countless times to the point where the phone was literally unusable, it would just pop up again right after closing it - So i decided to restart the device. This was probably a big mistake, it booted fine but it said "Android is updating" and had the whole "Applications updating 100 out of 255" stuff happening. Then it booted to the lock screen, which i had previously setup before i flashed the device which didn't really surprise me too much.
Then it rebooted. Now every single time i boot the device, it reboots to the "Optimizing apps blah out of blah" and then will reboot upon the notification bar popping up, but no lock screen. I decided that my best cause of action was to download another firmware and try that one instead, but I'm unable to boot my device into bootloader mode as it's impossible to happen. I turn off my device, plug it in and hold the volume down button but it refuses to work anymore.
Now that the situation has been explained, I'd really like your help to see if i can have this resolved. I'm baffled as to why Vodafone even locked it to begin with, since the phone was prepaid and had nothing to do with any sort of plans - nor was it even available as a plan. I don't have the money to buy a new phone, and they have already denied me a refund. I need this phone for work and the mistakes i made were stupid - Please, i need assistance. You're all hopefully more tech savvy than i am in the field of mobile phones.