The other day my TP hung after I ignored a call while using it tethered. I soft reset it, but now it only boots to the TouchPro screen with red lettering on the bottom. Even though I have Sprite, it has been awhile since I ran a backup, however most of my important data is on a SD card. I was able to get into the firmware update screen and there use TeraTerm to run info commands. However I was very disappointed to find out that all of the MFG commands, such as 'd2s', 's2d', 'r2sd' have been removed. Obviously using Sprite ever day would help (I still use Archie for SMS messages), however it seems odd to me that no one has a ROM reader for this phone. When it is flashed does it not do a read back verify? I figured a post here wouldn't hurt, as I have looked extensively everywhere else. Has anyone put the boot loader back to .25 which had the ROM to SD command? I understand HTC reasoning behind removing these commands, still it would be nice if there was a way of pulling an image that way. Maybe Sprite could add it in to their backup software? My next step will be to re-flash and in doing so wipeout any chance of recovering more of my data. With a Windows based OS, there really needs to be more recovery options than what we currently have.
J!
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.
Hey everyone here at XDA, just wanted to share my recent experience with loosing my phone service after flashing MIUI from the clockwork rom manager app. Basically, i flashed the rom from within the rom manager app and really liked the rom until I noticed that I had lost data and phone service. Apparently I was stuck in roaming, with a little triangle replacing the 4g icon in the notification bar at the top of the screen. I did a bunch of searching through forums and everyone who was having this issue was having it due to the loss of there IMEI. The people afflicted by loss of service did not have the correct IMEI or any at all on their phone.
But my IMEI was there and it was correct. So I restored the nandroid backup I made at the time of flashing MIUI but that didn't solve the issue so I restored the backup I made when I originally rooted my phone and installed CWM. That still didn't fix it. Some forum posts were saying the SIM card might have been fried, some were saying that they had totally lost the ERI folder, or something... I was getting worried. The last thing I tried was flashing a stock 4.1.1 rom via Odin and still I had no service. Well I needed a phone for work so I went on the VZW site Monday morning and switched my service to an old blackberry storm (I know, right?) that I had laying around and went to work. When I got home I looked on the web some more and found info about accessing the hidden menu with a code that wipes all data and settings. Is this different than the factory wipe from the settings menu? Anyway I wiped via the hidden menu and after that the little roaming triangle was gone. I switched my service back to the Gs3, which involved taking out the SIM card and registering it again, and after that my service, data, and 4g icon was back. Problem solved. I am wondering though if I could have used the hidden menu/wipe feature from MIUI, and for that matter what caused my phone to get stuck in roaming?
I would like to root, and explore other roms but now I'm worried about this happening again. It doesn't help that someone told me service providers can deny service for rooting your phone. I don't know if that's true or not. I know now that I should make a IMEI backup, even though I don't think that was my problem. I recently took the ota and am back on stock 4.1.2. Just wanted to share this with everyone, and bounce it around to see if anyone has any ideas, and maybe this could help someone who is having the same issue. As far as the hidden menu and wipe code, I don't remember what it was but you could look it up if you need to try it.
Thanks everyone
mattunden said:
Hey everyone here at XDA, just wanted to share my recent experience with loosing my phone service after flashing MIUI from the clockwork rom manager app. Basically, i flashed the rom from within the rom manager app and really liked the rom until I noticed that I had lost data and phone service. Apparently I was stuck in roaming, with a little triangle replacing the 4g icon in the notification bar at the top of the screen. I did a bunch of searching through forums and everyone who was having this issue was having it due to the loss of there IMEI. The people afflicted by loss of service did not have the correct IMEI or any at all on their phone.
But my IMEI was there and it was correct. So I restored the nandroid backup I made at the time of flashing MIUI but that didn't solve the issue so I restored the backup I made when I originally rooted my phone and installed CWM. That still didn't fix it. Some forum posts were saying the SIM card might have been fried, some were saying that they had totally lost the ERI folder, or something... I was getting worried. The last thing I tried was flashing a stock 4.1.1 rom via Odin and still I had no service. Well I needed a phone for work so I went on the VZW site Monday morning and switched my service to an old blackberry storm (I know, right?) that I had laying around and went to work. When I got home I looked on the web some more and found info about accessing the hidden menu with a code that wipes all data and settings. Is this different than the factory wipe from the settings menu? Anyway I wiped via the hidden menu and after that the little roaming triangle was gone. I switched my service back to the Gs3, which involved taking out the SIM card and registering it again, and after that my service, data, and 4g icon was back. Problem solved. I am wondering though if I could have used the hidden menu/wipe feature from MIUI, and for that matter what caused my phone to get stuck in roaming?
I would like to root, and explore other roms but now I'm worried about this happening again. It doesn't help that someone told me service providers can deny service for rooting your phone. I don't know if that's true or not. I know now that I should make a IMEI backup, even though I don't think that was my problem. I recently took the ota and am back on stock 4.1.2. Just wanted to share this with everyone, and bounce it around to see if anyone has any ideas, and maybe this could help someone who is having the same issue. As far as the hidden menu and wipe code, I don't remember what it was but you could look it up if you need to try it.
Thanks everyone
Click to expand...
Click to collapse
My suggestion, never use Rom Manager to flash!! Stick to TWRP(I prefer twrp), CWM or Odin.
so after almost a week of being down ive finally got my phone back to a workable condition. however, its stuck in roaming mode.
i did lose my imei, fixed that but it didnt seem to fix the roaming issue.
first thing i tried was to get a new sim card and the vz rep said as soon as i got data it would update automatically. i dont know if it did now.
the phone info screen doesnt show vzw and the carrier but it seems like everything else is correct(maybe).
i cant seem to get into the service menu except for a few different ends of it. nothing too helpful to this.
im trying to avoid sending it out to get fixed but after thins i may be stuck.
steps i made to get where i am
odin with root66
boot to factory recovery and factory reset(just to get it to boot)
used nv reader writer to write my imei to the phone.
reboot
still roaming
now in between these steps i did a lot of swearing and pming of people.(THANKS)
there are also some smaller steps that may have no importance to the outcome, but thats no big deal(airplane mode, switching the network have been tried)
does anyone have any semblance of an idea of what i can do from here?
So been running c59 Android 11 for a couple of weeks. All working pretty well when today i noticed my device was not on Wifi..
I went to wifi settings the phone locked up and crashed - rebooted.
Same thing is occuring except now i have a little Sim icon and an X in where the celluar signal is.
I still can recieve calls though no network access at all!
Just tried aeroplane mode and now its stuck and i cannot turn off aeroplane mode..
tried the reset network settings.. no change..
this phone is rubbish.
looks like another factory reset coming up...
just for anyone else who has this issue. you need to Format Data through recovery.. you lose everything. this fixed it for me.
You lose nothing because people are supposed to BACKUP their stuff.
Smartphones haven't been around since only a few weeks ago, it shouldn't come as a surprise that at some point they can fail or like in this case for some reason need a formatting.
Craphead said:
You lose nothing because people are supposed to BACKUP their stuff.
Smartphones haven't been around since only a few weeks ago, it shouldn't come as a surprise that at some point they can fail or like in this case for some reason need a formatting.
Click to expand...
Click to collapse
If you think about it you should be able to format Application Data only and not lose your photos etc..
Even my old Nexus 4 from 9 years ago can do that..
actually every phone i have ever had could do that other than this one.
Why would the existence of personal photos cause a phone not too boot? So why would the manufacturer make you format them to reset the phone?
Just a poorly designed device really..
And for the record i did backup and do backup. Though i wanted to inform others who may have to perform this fix that they will lose data.