(my question lies offset below, incase the reader wants to skip my paragraph and use it as reference. I had to type it all to give background to where I am now)
I have a DROID2 from Verizon Wireless running Android 2.2.3 Froyo, and have owned it for ~a year. One Day in early 2011 things started going wrong, like vibrate wouldn't work on messages (sms and email, using GoSms), my stock battery manager that told me % usage since last charge would crash when clicked, gmail and calendar wouldn't sync. I talked to a friend, backed up my phone, and reset to factory settings. then, he said that rooting was amazing, so I broke down, rooted my phone, backed it up with Droid X bootstrap recovery, and thought it was great. then my phone started to continually boot in recovery mode, even after I removed root and bootstrap. it also ran strangely sometimes and would be slow, but I figured that was my impatience. so i decided one day to root my phone (using z4root), use a root explorer, search my system files for ANYTHING with "recovery" that to me looked like that stupid bootstrap placed (because i read somewhere it made a file and it stayed in my system) and deleted those files. now, I have new problems:
apps that I had a few days ago (8-16-2011) and have NOT updated won't work on my phone from the market. the market app does not give me the ability to download, and online it says its not compatible with my phone, which is bull crap because I downloaded AND used the apps the day before, but deleted and wanted them back. some apps include: facebook, Heywire (2.6.1), and Adobe Flash 10.3. I reset my phone to factory TWICE yesterday in attempt to fix. when the phone first loads, the OLD market is installed, which I used to download Heywire before the new update came, which then said the SAME VERSION of Heywire is not compatible. there are also a few minor errors I have, the stock email app picture doesn't show in status bar, it is very slow, etc. I am currently NOT rooted and NEVER flashed a Rom. My friend said that I could just replace some files and it should be fine. Also, I have issues when powering on my phone. when I turn it off, to turn it back on I must 1. turn on 2. wait for Motorola "M" screen to dim 3. remove battery 4. turn on and wait for boot up My question is:
1. How do I figure out all the files I need?
2. Where can I get these files?
3. Is there a way I can get root access and just copy paste ALL system files back to the phone as if it is fresh out of the box?
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.
I have had an issue for a long time with the infuse where sometimes, after installing a GB based rom (not picking on gosooners, but it seems to happen most with his roms, ive never been able to run one)
i will boot the freshly installed rom, configure some stuff, and then at some point i will setup a PIN lock, or add my Exchange/corporate account (which does have a device admin policy) and then reboot (i'm not sure which of the two issues triggers it)
after doing this, i am locked out of my phone. the PIN i set up WILL NOT work at the password prompt, and no other password, credentials, SIM lock, anything you could have ever entered as a password into the phone, works, period, you have to reflash to get back in. and then the same thing happens.
happens with some ROMs consistently and not others... never with an ICS based rom.
any ideas?
Very strange, i have never heard of such problem.
Are you restoring any settings from the previous state with any app?
If it so keeps on happening try restoring all your settings (excluding the PIN Lock) and then the security lock of your choice at last after you rebooted and settled in. If not i suggest you try other ROM's. Don't know what else to say.
GOOD LUCK:fingers-crossed:
Hello all,
I'm sorry, but I couldn't find any device-related subforum for the Samsung Galaxy Rugby (GT-S5690M). If my questions are in the wrong section, please move it to the right place (mods)?
So here's the story: I just got my first smartphone. Since it's locked to Bell, it has some bloatware and need for sim-unlocking. I did a lot of reading and through some tutorials I managed to root Android and got rid of some bloatware (just four Bell apps). So far so good! Then I tried to unlock the phone. There are some apps in the Google Play that state that they can unlock the phone for free ("works on various Galaxy models").
I tried them out, but none of them could provide a solution. The last app I tried (Galaxy_S Unlock) requested that BusyBox were to be installed, so I did. During the installation the app remarked that already some BusyBox version was installed, but not the version that it was trying to install. I was suppose to try another type of installing (I used the normal/safe mode). But it said it was already installed, so good enough. Right? I tried the unlocking app again, but it still said it had errors getting to communicate with BusyBox. None of the unlocking apps gave me the impression that they changed anything in the system.
I figured that maybe a reboot of the phone would fix this. However, now the phone got several issues:
- booting takes forever (18 minutes) It does the animated Samsung logo (though, not with sound any more) and then keeps on slowing the glowing Samsung name.
- the speaker doesn't seem to be working at all
- it can no longer check for updates. After agreeing with the disclaimer, it says it can't connect.
- KIES doesn't see the phone any more.
- the phone is generally very slow now. Even when typing a password the phone sometimes hangs for about 5-10 seconds. Loading the disclaimer for the Software Updater takes 10-15 seconds.
I tried to reset to factory defaults and reload the rooting zip file again, but to no avail.
I've been trying to read up on the isolated symptoms, but I'm simply starting to feel overloaded with all the info, especially since I'm a Android newbie.
Does anybody recognize these symptoms and, more important, has any tips on what to try to restore whatever has gone wrong?
Additionally, I would really be interested in knowing if there's a way to force-upgrade to Jelly Bean. It appears that this firmware hasn't been made available to Rugby users yet through the regular update channels. But are there alternatives?
Thanks in advance!
Sorry, I know that this isn't the place for a A358t, but I didn't find a forum/thread dedicated to this device, so I went to the closest thing.
I have several problems with this phone that I can't seem to figure out.
First of all, it got 4 stubborn applications that wants to run... always. They are: engriks, engrils, Adobe Air and pro.
Engriks and engrils I can delete through the app manager, and 'pro' I can disable... which would work for me (would've being better if I could delete pro as well) but after a phone restart (or after sometime) [with internet/wi-fi] they reappear as working applications. Google didn't yield any results. I would like to get these apps deleted/removed or at least disabled so they don't run.
I've disabled Adobe Air but it keeps enabling itself for some reason... and then after some time starts crashing and closing almost every 5 minutes... so I disable it again and after some time it re-enables itself and the cycle continues.
There are 2 other apps that I can't Force Stop or disable at all (System Apps)... they are labled completely in Chinese, so I can't say what they are, what they do or anything about them... but I'm pretty sure it's just other crap that the phone can do with out.
I've tried to flash the phone to a different ROM (just reflash it to the original stock ROM as this one I think is compromised) but the SP Flash Tool doesn't seem to work on this MediaTek device... I've being battling drivers, apps, cords and just about everything today with this phone with nothing to show for it.
The problem with this phone is that it constantly crashes, bottlenecks, freezes, throws constant errors, app crashes/closes...
I managed to factory reset (recovery was in complete Chinese.... I don't know a gram of Chinese) and the first thing I see after setting up the phone is that the app Adobe Air crashed and needs to close...
If I could get any help with this I would greatly appreciate it... thanks in advance!
Root the phone and remove the apps from your phone completely