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.

[Q] Actually bricked a samsung i500. Help?

So...here's the thing. Supposedly it's impossible to 100% brick an i500. Well I believe I managed it. If not, I would REALLY like to fix it. I use it just for media stuff these days, like reading and music. So...here's what I did. I know it was stupid.
1. Rooted my Samsung Fascinate i500 from Ntelos.
2. Got a bunch of replacement apps, like Go Launcher EX, and pretty much every other thing the GO team came up with.
3. Used Titanium Backup to delete system apps(like the launcher, basic internet, and some other stuff) instead of freezing them. I am an uber noob. It shows, yes?
This was all some time ago, when it was actually connected to a plan and used as a phone. It still worked...most of the time. It would derp and freeze up occasionally, but otherwise worked fine.
4. At some point a few days ago I somehow uninstalled something that caused the wifi to cycle itself back on no matter what I did (including turning on airplane mode, it just turned airplane mode off and cycled the wifi back on) causing battery drain, since it's constantly searching for SVC. So since I couldn't figure out what happened to cause this, I decided it was time to finally get a custom ROM. I used ROM Manager to try and flash a custom rom I cooked in this online kitcheny thing.
It didn't work. Anyway, I went into the recovery and cleared the cache thingies, hoping it would help.
Instead, I no longer have a launcher. Since the default launcher was gone, apparently it won't let me use my Go Launcher EX anymore, or even bring up the menu to set it as a default.
I went through the steps to flash a new ROM or the original I found using ODIN3 and the download screen. I can get to the download screen fine...but ODIN3 won't recognize my phone. At all. Ever. I do have the right drivers, if I'm not mistaken.
Well...at this point, I don't know what the hell to do. I don't have the money for a new one, or I'd get it and start over and do it right this time.
Halp?

This problem is solved.
So...yeah. I forgot I had to use the original cable. My bad. I fixed it. Hooray!

[Q] Nvidia Tablet - WiFi Disabled

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

Verizon Galaxy SG 3 i-535 failure to load efs

Folks,
During a recent power outage my battery completely drained for the first time. Powering on after a full charge, started getting screen msgs (yellow text) info on some system internals. tried rebooting, and got "failure to load efs". and the phone comes back up in Factory test mode. I had never attempted any modification on this phone and everything looked stock to me. I had bought used from B&H, so cannot swear to its complete history. Samsung recommended a "smart Recovery from Best Buy that after two swap-outs i am still getting all the above msg's. I have no experience in rooting or anything else, but have a background in software. Info found through searches seems to indicate Verizon Samsung sg3's may be the most difficult to add mods. I found a stock rom, and loaded it successfully via odin. Best Buy guy said he loaded an original stock as well, and still no luck. Even though this happened after a hardware issue, and i know its firmware, at a loss as to what is causing this. it generally degrades performance of the phone in everything, including linking to playstore to download apps. I have everything backed up, with nothing to lose if anyone has a path to a working phone....I'm game. running 4.4.2

Question S22 ULTRA BOOTLOOP PROBLEM/RESCUE PARTY

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.