Related
I used designgears' jh7_ota.zip to update my phone to JH7. It worked fine. The one reason why I used it was because the OTA update had gone through to 100% and then crashed. In the "About phone" menu it had the right kernel version and the right baseband version, but the Build number was stuck on ECLAIR and not showing ECLAIR.UCJH7 like it should. So after using the JH7_OTA.zip it showed the right build number and the PC Internet option was gone from USB options like it should have been. Also, the GPS started working pretty well.
The one thing that sucked was it completely wiped my phone. So after reloading all my apps and redoing all the customizations I finally got it back to how I like it. Then I happened to notice that the "Build number" had somehow reverted back to just "ECLAIR". I also noticed that "PC Internet" was back as an option when USB was plugged in. I have no idea how it reverted back after I had successfully installed JH7. I never used ROM Manager or Titanium Backup to restore anything, I just went and redownloaded everything and reinstalled everything.
Has anyone else seen or had this happen to them? I had to reinstall JH7_OTA.zip again. And again it wiped my phone out completely. Having to go back through and reinstall everything all over again. How annoying.
You could always master clear, flash stock JF6 and then use Mini Kies to get the update. That way you know you have a fresh install.
I just did that coming of Cognition, loved it but didn't use any of the useful features (mobile AP, tethering) to make it worthwhile. I still bought DG a beer, dude works hard.
That was what I did to get the JH7 update. Although, I did use designgears' zip file rather than mini kies. Mini Kies wasnt out at that time. I used odin one click to revert to stock JF6, then the first thing I did was install clockwork recovery, then I installed designgears' zip file. Everything worked great for weeks. Cant see how or why it reverted back to build number "ECLAIR" from "ECLAIR.UCJH7".
I reinstalled JH7 with DG's zip file again since I still had it on my sdcard. Its back to the right version, build number says the right thing and pc internet is not an option and gps seems to work good and battery life seems to be better again. If it monks up again I will flash back to JF6, then use mini kies to get the JH7 update and try that.
I dont know whether its android or its just this galaxy S, but I've never had such a glitchy phone before. Random software crashes, random shutdowns, half-baked gps, updates that dont work and even brick phones. Just seems like I cant go more than a day or two without something on this phone F'ing up. Is this how it is with android all the time? This feels like the microsoft windows world a la 1995-2000. I thought we moved past all these crashes and glitches with plug and play and with Windows XP.
May or may not be the same thing ... but ... my wife updated to the current release OTA and said it worked. However I noticed the other day that she still has the PC Internet option that shouldn't be there.
jahfry said:
May or may not be the same thing ... but ... my wife updated to the current release OTA and said it worked. However I noticed the other day that she still has the PC Internet option that shouldn't be there.
Click to expand...
Click to collapse
Go to About Phone and look at the build number on her phone. If it really took the full update it will say "ECLAIR.UCJH7". If it didnt it will still say "ECLAIR".
The very first time I tried to get the update OTA, it downloaded, then installed and it went to 100% on the install screen, but once it reached 100%, it then said "Update is failed". And when I rebooted it, the build number was still at "ECLAIR". and I still had PC Internet option and Quick Office wasnt installed and it acted kind of "glitchy".
When I downloaded and installed the zip file from Designgears, I could tell right away the the update was truly installed. Build number was "ECLAIR.UCJH7". PC Internet option was removed from usb options. Quick Office was installed. It ran a little smoother. GPS performance was somewhat better, and I did notice improved battery life.
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. Its been a while since I've lurked around here. Long story short, I've had a lot of life changes over the past year.. and I've also had a few system crashes/rebuilds so I've lost a lot of my old RT dev work & environment. Anyway, I'm looking to back into it and spare a few cycles playing around with things again. I recently dusted off my Surface RT and noticed I haven't updated it since Feb 2013 (!!). Given that the old JB thread is now locked, can anyone confirm that the JB still works with the latest/recent updates? If not, can anyone confirm the last update for which the JB still works correctly? I did some quick searches, but couldn't find any concrete info.
Thanks in advance!
Cheers!
It does with the new updates. Just don't install KB2973544 and KB2885699. One is an auto 8.1 update. Jailbreak doesn't work on 8.1.
Welcome back! Good to have you. The RT hacking scene has gotten pretty sad lately.
The jailbreak does still work on 8.0 (although I got one instance where it slowed the tablet terribly for a couple minutes then bluescreened with a stop message about a critical process dying, but usually it works fine). The current primary focus is on getting it working with 8.1. Read the first few parts of the 8.1 jailbreak threads to see what the problems are (in short: CSRSS is now a protected process so we can't debug it, and PatchGuard now checks the signature enforcement flag so the tablet will bluescreen after a while if you modify it). If you want to help, get in touch with @Myriachan (if you aren't already; I think there was somebody else working on it but I forget who) and see whether you can lend a hand.
If we can get past the first problem (protected process), I have some ideas how to handle the second one (PatchGuard). I can't guarantee it'll work, though; bypassing that stuff is hard and I've never tried before.
If you want to have a test install of 8.1 alongside your 8.0 install, that's possible. However, it takes a lot of storage space; I'm not sure if it can be done on the 32GB model.
GoodDayToDie,
Thanks for the summary! Glad to hear that I should be able to updated my 8.0 install and still JB.
I spent a few hours catching up on the 8.1 JB status/thread -- lots of good info in there. I might try my hand at dual booting (64GB Surface RT here) and poke around 8.1 -- I have a few ideas and I'd like to have a look at some of the binaries/changes.
I've also gotta setup my dev environment again -- but it looks like the newer WDK (for 8.1) makes life a lot easier. I'll see if I can get an updated build of ProcessHacker out soon.
Cheers!
On this front, is there any way to "selectively install updates" other than rushing to "Check Updates" and unchecking the ones we don't want, then immediately disable Windows Update afterwards? I'm concerned about downgrading to RT 8.0 and the auto 8.1 update automatically being installed, since RT auto-installs updates and I want to install the other updates...
They removed the UI for auto update behavior, but the registry value is still there and still works the same way. My tablet is set to notify me when there's updates but to not install anything (I forget if I told it to download them or not). You can also just turn off the automatic update feature entirely, in which case you need to remember to check manually as it won't prompt you.
Other than the awful 8.1 auto-grade "updates" already mentioned, there was an optional update released back in June, kb2962407, that seemed to break the jailbreak for me until I uninstalled it:
http://forum.xda-developers.com/win.../kb2962407-causing-jailbreak-to-hang-t2803626
It's no longer in the optional updates list so I'm not sure whatever happened to it. No one else ever mentioned anything about it that I saw, so perhaps my issue may have been a fluke, or nobody else ever bothered to install it. Jailbreak still works great on my Surface RT, and this is the only time I've seen anything that broke it (knock on wood).
I got a notification on my phone that there is a software update available for my phone. After reading up on it a bit, I decided it's not worth the hassle to update. I thought I had gone through steps to suppress firmware updates a while back but I guess not. What's the easiest way to suppress this warning? Let me know when you get the chance. Thanks, guys!
Well, a bit of an update, I found the original information on how to suppress OTA updates here:
http://forum.xda-developers.com/showpost.php?p=56693607&postcount=370
As I thought before, I had already gone through this step and disabled it (it was disabled in the hidden menu already). However, the update still seems to have popped up. t tried to auto update this morning but reported back that it suspects my system is rooted so it wasn't able to install. That's good news to a point (at least it didn't screw anything up) but I don't like that it even attempted it without me giving it permission.
Any idea what might have changed? Or is there a difference between an OTA update and a "software update"?
I don't know the answer but I am having the same problem. My phone keeps restarting and giving the error that it wasn't able to install. This actually happened before when I was on 4.X and eventually it bricked my phone and the AT&T store couldn't fix it so they gave me a refurb. It sucked because I didn't have all my photos backed up(I have since fixed that problem.) Now I am having the same issue and I don't want it to brick my phone. I also hate that it restarts automatically...I might need to use my phone for something at the moment. I also have tried the info in the link to disable OTA both phones and neither time has it worked. If anyone can help, please do. Thanks.
The only thing I have ever done and has worked every time is to root and then freeze a file called. "software update" or "update manager". Hope this helps.
I would actually like someone to put together an update.zip that will update us to the latest version without having to go through the hassle of flashing back to stock and what not.
I like the idea of LTE voice calls but not so much that I am willing to go through the work of starting over.
sent from a location using an app
In Titanium Backup (or similar app) find the app call "Software Update 2.3.3.1" and freeze it
That is what solved me receiving software updates and I no longer see the option in the About phone area.
I have a Pixel and recently received the 7.1.1 OTA update. This morning my phone restarted and failed to boot properly. It does boot, and I get to the home screen where all apps seem to be functional. But there are several problems, including 1) I can't turn on cellular data, 2) the home button and the task switcher button do not work. Also, when I press the back, home or task switcher buttons, I get vibration feedback which is not how I had the phone set. Another odd thing is that when I check settings, it shows that the phone is on Android version 7.1 It is as if the phone tried to revert back to 7.1, but did not do so fully. Another anomaly is that when I got to the Play Store, all my apps appear as if they are not updated, even though I just installed available updates yesterday.
When I go to System Update, it shows a 261.9 MB update available to download. I assume that's 7.1.1 OTA update. I could try downloading and re-installing it, but before doing so, I wanted to see if anyone thinks that could cause more problems. Or, does anyone have another suggested step I could take. I would like to avoid a factory reset, if possible. Hopefully, there's another simple, quick solution.
Most likely it is easily fixable by just flashing the full stock 7.1.1 image from Google. Unfortunately it will wipe your device, but it is basically a surefire way to fix whatever went wrong.
It sounds like what happened is the OTA failed somewhere, bad download etc. As the pixel has the dual partitions if an OTA fails it will revert back to the last known working system. As @renegadeone8 mentioned, flashing the full 7.1.1 zip should cure your issues. You will have to unlock the bootloader to do so. (No a bad idea anyway imho Incase you have errors)
No harm in trying the OTA again. If it fails you won't be any further behind than you are now.
I'm having very similar issues, I also have no notifications and cannot pull down the full drop down menu or turn my data back on.
Thanks, k.s.deviate. I wish I had read your response earlier. It probably would have been good for me to at least try re-installing 7.1.1 again. However, I read from users on a different forum that they had experienced odd behavior very similar to what I experienced. In their case they didn't realize, at first, that the problem was associated with the 7.1.1 update. So, they re-installed it. Unfortunately, they had the same problems re-occur. For them the only solution was a factory reset and then not downloading 7.1.1 again.
That's what I've done. Everything is working great now. Android shows the 7.1.1 update available. Based on your assessment, I'm partially tempted to try installing it again. However, if it does end up with problems again, like it did the first time, I don't feel like I have the time to go through the whole factory re-install process again. So, I'm just going to stick with 7.1 for now and wait until either 1) I feel I have more time or 2) Google releases another update (7.1.2 ?) that might fix this problem. Thanks, again, though for your feedback.
exactly same here, so bad download could be ruled out. Also I've seen discussion on reddit and google forum, but unfortunely no solution was presented