Database Info

no 3 button combo -OTA UPDATE FIXED FOR ME

I got the OTA update today and it failed (phone was rooted). CheckedOnce it rebooted I tried the 3 button combo to get into recovery and it worked. As well as going into DL mode using USB. Hopefully this will fix others who could only get into recovery and dl mode using ADB. Also, even though it "failed" it did update to JH7. haven't checked GPS....

Same for me.
Sent from my SAMSUNG-SGH-I897 using XDA App

I got the same results as you but my GPS is still terrible.
Sent from my SAMSUNG-SGH-I897 using XDA App

Rooted and Lag fix installed. Update "failed" but seems to have installed JH7 (no new apps though). I get a GPS lock indoors now, something that has never happened before but a 40 minute drive in the car today yielded no locks ever, even after two reboots. It seems like it may have helped in one regard but dang, driving around in a convertible for 40 minutes should have gotten a GPS lock.
The three button recover mode worked the first time I tried it after the JH7 install. Before today I spent easily an hour+ trying every key combination documented and I never once saw recover. After the update I hit recovery on the first attempt, cool fix that wasn't even documented officially.

I'm getting the same results. I've spent countless hours googling and trying every key com possible trying to get into recover mode prior to the OTA update and nothing worked. Last night i checked to see if the update is available for my phone and it was. The phone downloaded everything without a problem, it rebooted and pooped out at 50%. After reading this post I tried the 3 finger salute and like you guys i got it to work.
When you guys check the baseband version did it change? There were reports of failed updates but baseband version changed. (mine didn't)

I did the root when I got the phone. I cancelled the original OTA update for reasons I don't know.
then I tried 3 button combo and IT DIDN'T WORK!
I tried to do the update again and kept getting communications error .
I tried to flash the JH7 ROM, that still didn't fix it.
Used Odin3 to go back to stock and try to update, this time it downloaded the update but crashed at 50%, JH7 never installed (said JM6 in about). But low an behold, that 50% somehow fixed the 3 buttom combo!
went back and flashed Cog 2.1 and 3 button still works!!!

Another 3 button combo fixed by OTA JH7.

Fixed for me. Further updates will be less nerve racking for sure now.

Mine worked in the past. I did not try it after I put cognition on the first time and then last night had a horrible brick moment cause I did a stupid restore.
I work like a champ now thanks to the good folks at this message board. The only thing is I cannot get into download or recovery mode which is concerning to me. I need the ability to do this from cold start, the only way in for me right now is once booted to go in terminal emulator and issue the command.
Does anyone have any suggestions for me? I am running cognition 2.1.1 right now, I have done 1 restore with Odin as well.

Mine worked in the past. I did not try it after I put cognition on the first time and then last night had a horrible brick moment cause I did a stupid restore.
I work like a champ now thanks to the good folks at this message board. The only thing is I cannot get into download or recovery mode which is concerning to me. I need the ability to do this from cold start, the only way in for me right now is once booted to go in terminal emulator and issue the command.
Does anyone have any suggestions for me? I am running cognition 2.1.1 right now, I have done 1 restore with Odin as well.

[Q] Force Close out of the box!!! What do i do?

Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks

uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
If you can get to the factory reset in the settings menu that would the first thing to do. And then check for an update. Make sure you set the wifi to not turn off and I would keep the screen from shutting off while downloading the update. Check in settings "about Device". If your not 3389 or higher then you need to update

I had this problem back in November when I first got my tab. Even though nothing seemed to work right, I was able to connect it to my desktop and push across clockworkmod v .08 and a custom rom. So, I never used the original rom more than 10 minutes.
If you can't get it connected while booted in original rom, then Bekit's NVFLash full restore procedure works really well. Just follow the steps carefully and it's a quick and painless factory reset to a known working rom.
These things are virtually unbrickable (is that a word?).

uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
badfrog is correct. If you factory reset the device it should be fine from there - then you set up your wifi and get the update.
Go into your app drawer and choose Settings. I don't remember if you can do it from the menu button as I'm on a different launcher.
Inside Settings go to Security and select Factory Data Reset. Do this, the unit will reboot and come back up at which point you'll be asked to set it up. It may take some time. Set your Date and Time correctly and set up your Wifi and such.
Once that's done you'll likely get a prompt to update very soon after Wifi connects. DO NOT DO IT, yet.
Within Settings, go into Display and set the Display Timeout to Never.
This ensures that the tablet doesn't sleep or turn off your wifi while it's downloading the update. It's not likely to happen but if your connection is on the slow side and the timeout is set too low, it can mess things up.
Once you've done that, proceed to let the tablet update itself. Again, it may take a bit of time.
Once it's done, make sure you take not of what you have. You'll find this information under Settings in the About section. The last version I got was 3389 - but something newer MAY be there for you. If you get anything less than 3389 then you will have to wait until you get another notification for an update. I don't remember how they work - but I THINK you should get the newest one there.
Once you've confirmed you're on the most current build, It may not be absolutely necessary to do it, but I would factory reset again just to clear the 'gunk' of the older TnT out in case there is actually any.

When I got mine and powered it on the 1st time, I got a bunch of FCs. I powered off and then on, and no more FCs, and it was fine after that. I think I posted asking about that, and someone (roebeet, I think) said it was a known problem. I don't remember the TNT version, but it was the one before 3389, or one before the one before 3389.
Jim

It is a known problem, especially with the older firmware. Sometimes the FC's are so bad that you can't even get into the settings to do a data wipe.
I've actually called CS about this, as an example of why they need an offline updater of some kind to get around issues like these. Suggestion: if you don't want to install clockworkmod, at least try to update the firmware to the latest and greatest, via one of the newer stock ROMs we're retrieved:
http://forum.xda-developers.com/showthread.php?t=842000
That might get you enough access to get into the Settings menu and do the factory restore.

[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!

Can't get Galaxy S7 from custom back to normal, so many issues, please help

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!