Related
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,
I have ran into some rather severe complications of rooting my LG G3 and I don't know where to find the needed information to repair the damage done to my advices functionality.
Okay so to summarize what led to my phones current state I had to downgrade the firmware to vs98510b to root the phone. The downgrade and rooting went fine, however once I got root access I decided to remove a good portion of the bloatware software on the phone to try and increase performance and security. I used a root access level program to uninstall a total of 42 bloatware apps installed by LG and Verizon. After I rebooted the device I discovered that somehow the lg keyboard had been removed with the other bloatware, seeing as thats the only keyboard app installed by default I basically had no on screen keyboard at all in order to fix that I had to use bluetooth to send a keyboard apk to my phone to install.
After I finally got my keyboard back and functioning again I discovered that my phone was no longer being detected when plugged into my computer. on the phone it stated that I needed to install the USB drivers or plug and unplug the device back in to fix the issue, it would not get resolved by either method. So I looked more into what apps had been removed when I removed the bloatware and it looks like the file manager, keyboard and a few other apparently important bloatware had been removed.
If I connect the phone to the computer adb claims no device is connected, and if I boot the phone into download mode it never goes past 0% however it wont get detected by my computer itself at all. From what I have found so far it appears I need to flash the phone back to the complete stock state to get the bloatware reinstalled, however without a pc connection about 99% of the tutorials I have found cannot be used since it wont connect to the pc anymore. I am completly stuck and need advice and possibly a set of links to read on or guide to follow to repair the phone. Finally the last thing I noticed was the phone battery status cannot be detected through the android ui I have to actually use different battery monitoring software just to even know the correct charge level.
I look forward to yours alls response .
Hi,
Here's a dedicated help thread in your device section that you can ask for help in,
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
Also, you really need to know what you're debloating. One wrong thing and you're in a mess. A way to try to avoid this is using titanium backup to freeze bloat, instead of uninstalling it. Then if you're able, you can always unfreeze if you need to. Uninstalling is not gaining you much space, as those apps tend to be very small in size. ?
Good luck!
Okay you may lock this thread now since you redirected me to the correct forum
You can lock this thread if you like since you linked me to the correct forum/thread regarding this issue .
Thanks for the help
PS I attached the list of all my system apps currently on the phone I removed 42 total system apps, however I am unsure as to which ones they were as when I went to fix the problem I factory wiped the phone to try and repair the issue. However, after trying that I basically narrowed the issue down to needing to flash the stock rom back onto the phone to get the bloatware back. I would have to do it all from the phone though without the computer since some of the bloatware I removed makes it unable to connect to my computer now .
Ask for help in the link I gave.
But I'll say, you removed many things that I don't know what they are for. So chances are you don't know what they're for either.... A number of them could be causing you issues.
Never debloat things you are unsure of. You want to know exactly what they are for, and know that they are safe to freeze.
And again... Freeze them, don't uninstall them... That's my opinion anyway. All of those combined take up very little space. ?
I did actually ask for help in the other thread I just wanted to give you the curtousy of replying to your questions.
In regards to the removal of the bloatware itself. I have never had a rooted or even rootable phone before, bloatware removal in computers never negatively effected me thats why when I did a rather short set of searches regarding to the apps I removed they seemed like they would be fine to remove, however the effects made things I didnt remove not function aswell. I have learned my lesson if I want to avoid bloatware I am better off installing a custom rom and recovery than messing with the android bloatware integreted in the stock firmware.
You can close this thread
Well after a few days of what I can only describe as a nightmare I did manage to repair my phone back to a stock state, I even managed to get a customer rom on it called Ressurrection Mod!
Woot woot overcame my epicfail!!!
EDIT: In case anyone wants to know how I resolved the situation my fiances phone me and her got the same exact phones and models. When I rooted her phone last night the idea came to me to use a Nandroid backup from her phone to overwrite the data on my phone to restore all the bloatware. After doing so my phone is back to functioning correctly again! . All I had to do was rename the backup from her phone to match the generated hash on my phone so that TWRP would recognize the backup!!!
Got my note back in November, rooted through odin in December. Everythings been grand and perfect.
Till I watched a video on youtube 2-3mnths ago about good rooted apps (wanted to get more daring other than xposed) loaded gsm gestures app? I think was the name. Kept it for a week, didnt use it. Uninstalled it, phone rebooted, instead of the normal "app uninstalled"
After that my phones been laggy, freezes, and freezes and turns off. Its factory wiped itself 8 times. I have countless posts on Reddit timelining everything. Long short is, tried liquid smooth to see if that would fix my problem, lost text messaging with that could only text for an hr a day, flashed stock sprint firmware and rerooted afterwards, have been slow to reload apps on phone, incase of factory reset or whatever. my phone is now taking 75+ batter pulls to get into a normal boot, every 15bat pulls it jumps into download mode "could not do normal boot ddi_mms read fail" and now an ssl text ive only seen once today, ill try and write that down if it happens again.
Finally when I get back into my phone, sometimes I have to update prl to get service again, the other day my phone lost signal and all my network settings were unselected, I had to select them all and my phone was fine, then I was on the phone and it cut me out in the middle of a call and said roaming lost or something, and I had to reapply cdma/lte on sprint.
Im beyond frustrated, im getting married in 2 weeks, and going out of country immediately after, so I need a working phone as most my business is conducted through it. I have no upgrade on sprint, and cant afford to throw out 400$ for a "new" note 4
Please please please someone help me.
Thanks for your time.
Matt
Hi,
Here's a thread on returning to stock firmware. That should give you a fresh start,
http://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3056478
If you want to find other options, you could ask for other ideas in your device section here,
http://forum.xda-developers.com/note-4-sprint/help?nocache=1&z=7997657528612763
Good luck!
So, the other day I tried to root my Galaxy S7, which probably wasn't the best idea. I sort of messed up and had an issue, and ended up with a phone that is "Custom" (an icon appears on the boot up screen that says this and it also says this in "About Phone" in the settings) but not rooted (according to Root Checker and other apps).
This wouldn't be a big deal but it left my phone with random icons on the top notification bar, and also with a notification that says something about unauthorized software or changes. It also made my phone *really* laggy, killed the battery life, and then all my apps started crashing upon opening them.
I wanted to get rid of this at all costs, so after I decided to try and flash stock firmware. (**Was this the right choice?** Really, I'm and amateur and it was stupid of me to try anything like this in the first place.) Anyway, I installed USB Drivers, Got ODIN, and got the Stock Firmware. More problems only arised.
The first time failed, then I realized I didn't install the drivers (oops). But everytime I fixed one problem, another one popped up. I've tried 3 different versions of ODIN (sometimes it fails at system.img.ext4, sometimes it fails at boot.img). I think ODIN is the problem, but maybe it's the firmware I downloaded, maybe it's just my phone.
I don't know if there is a glaring flaw or what, I mean I dont have any other cords to use and I've been trying to get another version of the SM-930V stock firmware but every link is a petty website that makes your download take thirty ****ing yeras unless you pay them.
I'm getting really desperate, I just want my phone back. Any help is GREATLY appreciated. Thanks!
hi everyone! I just wanted to explain my situation here so that maybe someone can help me understand what is happening.
I own the Exynos variant of this phone 12/256.
Being a huge fan of debloating my entire life, i got the phone and after some time, seeing that the battery life won't improve, I started digging.
At first, i have removed MANY apps that are useless, but have never touched system related apps, maybe bixby or smth. Nothing happened. Then the OneUi 5.0 came, beta, installed it, then the stable came, installed it, had a factory reset done to start fresh and i got to debloating again. And for about two weeks everything worked smoothly. Then i was at work one evening and i started seeing my phone acting weird, mobile data going on and off(kinda always on 4g+ at work) so i decided to restart the phone. Clicked restart, put it in my pocket and after 5 mins i felt it warm in my pocket. Checked it and saw it was restarting in a loop and after a few more restarts it said " rescue party/ etc/etc, your phone failed to restart multiple times bla bla". The only way to get it up and running was to delete all apps inside that menu then the phone would boot in safe mode so i could backup my data, then i had to factory reset it again. This happened 3 times, in a 1.5 week period. Last time i debloated, i only uninstalled youtube, youtube music, microsoft onedrive, etc etc. Haven't even touched anything related to a system app, because in that menu it would say some system files are missing or smth like that. This evening I ve got the update with the November security patch, downloaded it, installed it and now it's looping again.
Does anyone know what might be the cause? Because obviously i didnt get rid of any system app this time.
Contact Samsung support. Possibly to be replaced under warranty
Maybe just download a firmware that doesn't have much bloat then see if the issue keeps happening without you debloating. If it doesn't happen anymore and then you start debloating things and it happens, then you know your problem.
More than likely you've de-bloated something you shouldn't have.
Back up all your data (if you're still able to), then factory reset & flash clean stock ROM.
Thereafter, flash a de-bloated custom ROM or do a very careful de-bloat yourself (plenty of guides on XDA).
Everything I've debloated was done side by side to a parallel xda thread for samsung debloating, it's not like it was 100% out of my head. Disabling bixby, microsoft onedrive, samsung free, upday, ar core elements inside and out of the camera, live messages from the s pen doesnt look to me like it should make the phone go bootlooping.
I've flashed the first stable firmware last night after the incident, updated it to the latest november update and I'm keeping an eye on it. If it randomly goes bootlooping and to rescue party, I'm taking it to samsung in my city.
stefancrisxd98 said:
Everything I've debloated was done side by side to a parallel xda thread for samsung debloating, it's not like it was 100% out of my head. Disabling bixby, microsoft onedrive, samsung free, upday, ar core elements inside and out of the camera, live messages from the s pen doesnt look to me like it should make the phone go bootlooping.
I've flashed the first stable firmware last night after the incident, updated it to the latest november update and I'm keeping an eye on it. If it randomly goes bootlooping and to rescue party, I'm taking it to samsung in my city.
Click to expand...
Click to collapse
dont root your phone, you might lose your warranty.
i see you flashed the firmware so keep an eye one the phone, debloating shouldnt have to do anything with this issue, a lot of us debload and have not faced this kind of issues.
i did debloat mine, i bought my phone with A12 and it took me 2 days to set it up including the date transfer and debloat, then i received A13 which i installed and kept using it without a reset which i should have done but i was very busy.
I haven't rooted this one, not yet because it's new and I don't need anything root acces can give me at this popoint. Although I have rooted many phones before, including samsung, I've never encountered this before, even though I've seen it was introduced by google in A11 or smth. I dont know.
What variant is your phone? Maybe you can give me a file with what you've debloated so far to compare.