I've been on Humble 1.42 for about a month now (please don't look down on me, haven't had time to switch since the drama) and I am starting to have some issues with my phone not waking. At random moments, my screen would refuse to turn on no matter what I do. It does, however, respond to me holding down the power button for a forced power off (hard reset?) Anyhow, has anyone else experienced this at all? I had a feeling it was my xfinity mobile app because I had been getting a lot of errors from it lately even though I rarely ever use it. Should I just switch to another rom or is there any other apps known to cause issues with this rom that I should be aware of?
On a side note, I have been on this forum and obsessed with android for the past year and been doing some serious thinking about making a career change into Android development. Been doing some java tutorials on youtube over the last few months and the such and think I'm about ready to start some real android app development. I credit some of the great developers on this site and the awesome experience at Dreamforce this week as the tipping point. Any ideas on additional resources I should look into?
There are a few things that could be causing this problem(that I'm aware of)
1) You may have sideloaded a "virus" app. I attempted to sideload an app once(will never do it again after what happened..) and it completely BROKE my phone. It made apps unable to isntall, the screen would take FOREVER to wake(if it ever did wake) and plenty of other problems. I tried rebooting and got stuck in a bootloop(boot animation would never end), did a factory reset and everything force closed on me so I was forced to flash the .md5/.pit to go back to bare stock and that finally fixed it.
2) Have you flashed Fuju Tweaks? This exact same thing happened when I flashed it on Gummy2.0, worked fine on Eclipse1.3.1 and even works for a lot of people on Gummy2.0 but it wouldn't work for me.
3) Try reflashing your ROM, that's how I fixed the Fuju Tweaks problem. It might fix whatever plagued your phone.
Just let me know of anything you've done recently and I'll try and diagnose the problem(if I didn't already).
Uh-Oh, a virus maybe? Yeah, I will just reflash later on, and change some passwords while I am at it.
I don't think it was that kind of virus but it definitely screwed up my phone.
Hi.
I got a standard Android Tablet for xmas, my daughter got the same model. They are the standard Wm8650 with the usual chinese stuff on them. Anyway I installed Uberoid, Modroid and UdroidX on them until we decided which we preferred. My daughter preferred Modroid and has had no problems. I preferred Uberoid so kept it.
Now my problem. Tried several ereaders but all kept freezing the system. Finally ended up back with Kindle and Calibre on my pc. This didn't freeze the system. However after finishing reading I went to Android Market and started to download a sci fi wallpaper. The system froze again. I rebooted but it froze on the little green man. I rebooted again but this time it didn't even get to the little green man. I tried to reinstall Uberoid and everything seemed to be going fine. The list was coming up upgrading....., upgrading....., then it came to the upgrading filesystem(NAND). The message came up but then instantly a second message came up saying *E* FileSystem Partition Missing. It then carried on with everything else except installing android. Now all that happens when I switch it on is a black screen. What can I do ???? Please????
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.
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.
Gday everyone.
I just got this phone and since it was first powered on I've had issues. I will likely be going back to the carrier tomorrow and asking for a replacement, but wanted to put my experience down here. Ive looked at a lot of other threads, but all of them involve unlocking of bootloader, flashing etc - I havent done ANY of this (yet). Its fresh out of the box.
Location: Australia
Carrier: Optus
Model: MHA-L09 (cant access extended model number)
So first up, had issues connecting to the carriers in-store wifi, which uses a captive portal.
When I finally got it going I was presented with a Chinese site - id accept this usually considering it is Huawei.
This phone is a replacement for my dead Note4 and as such I wanted to restore apps, as I had no internet, I skipped the process.
Got back to my office and connected to my wifi fine, so decided to factory reset to get a fresh start.
Noticed that after reset the initial process was in a different order. Restored from Google and all apps downloaded, happy days for a couple of hours, just waiting for my service to port over.
2 hours later, I decide to restart the phone, it gets hung up on the Optus logo which is displayed before the reboot starts.
Hard reboot.
System loads, I figure I may as well see about a firmware update. Get 'Package installer isn't responding' errors. Try again, works, no updates available.
Go to google photos, get 'Package installer isn't responding' error.
At this point I think, f**k - what is going on here.
So I reboot into recovery to wipe the cache. This processes fine, but then the option to reboot the phone doesn't work.
Hard reboot.
Boots into recovery without me touching it.
Hard reboot. - happens again.
So then I think, fine ok, I've upset the balance, lets do a factory reset.
Factory reset hangs on 99% for over 30 minutes.
Against better judgement - hard reboot.
Now I have the EMUI logo with a nice round 0% under it... and that's where its staying.
Thoughts?
I have to fly interstate on the weekend and cant really afford unreliable comms. Should I ditch the Huawei?
Thanks all.
So - it seems that nowhere did i find a mention of the fact that if i plug it into my PC and goto the recovery mode, it loads eRecovery. Whilst this didnt actually work (I believe it only works for CN firmware) It did give me a shutdown option. I shut it down and started it again and im back into a fresh install.
Lets see how I go now...
Never restore backups from other phone.
Wow, helpful.
I didn't restore the backup from another phone, just apps, ie google downloaded the apps I selected.
The device is still performing poorly, even a standard reboot does not succeed, instead it hangs on the carrier logo before actually rebooting.
Ill take it back to the store tomorrow and ask for another one, im hoping Ive just gotten a dud.