At first I thought my problems stemmed from an update with WidgetLocker. However, I uninstalled that and the problems persist.
Description of problem:
So I boot the device to the lock screen.
I unlock the phone and all I see is my background with the taskbar at the top. No icons. I can't interact with anything. After a few seconds the screen goes dim and times out. Even if I touch the screen to keep this from happening.
I hit the power button to turn the screen back on. No response. I wait 30 seconds or so and it turns back on. I am greeted with "xxxx process/program has stopped responding do you want to force quit, wait, or send a report" (whatever program happens to be up, doesn't seem to matter, all programs cause this to happen). If I hit force quit the program still hangs. If I hit "wait" the program starts working. This isn't a very repeatable event in that sometimes when I turn the screen back on instead of the "force quit" screen I get the background with taskbar.
While all this is going on I am still receiving status updates, emails, texts, etc. Sometimes I can get to the point where icons appear on my homescreen but if I tap a program's icon the screen just freezes.
I have Go Launcher installed but this happens in Go Launcher or Sense.
Any ideas what is going on? So far I've:
restarted
removed battery
restarted without back on
restarted without sim card in
No luck.
I tried "restore" but after being shown green arrows and an icon of the device I immediately get an icon of the device and a red exclamation in a triangle.
Any help is greatly appreciated. I'm trying to avoid a hard reset.
I would run the RUU. I know you don't want to wipe, but I would back up your data as best you can and wipe it.
any recommendations for backing up? I can't really get to any apps right now.
What does RUU mean?
ROM update utility. Stock rom releases from HTC.
http://forum.xda-developers.com/showthread.php?t=1338916
Sent from my ADR6425LVW using XDA
well
I ran the phone down to 0% battery. Restarted it and things seemed ok. But just now it is starting to hang again so going to back it up and run that RUU.
I tried the RUU but was told it could not communicate with my phone even though I had it plugged in via usb.
Instead of installing the RUU I installed one of the leaked ICS updates (official one for the rezound). Now it functions somewhat better. There is still often a long wait between pressing home while in an application and going to the home screen. Also while the screen is off, pressing the power button to turn the screen on I have to wait a good minute for the screen to come back on. Any idea what in the world is going on?
Sounds weird. Anyway, here are a couple thoughts:
When you installed the ICS leak, did you do a complete wipe of everything? If not, do it and reinstall whatever ROM you like.
Otherwise, in recovery, wipe cache and dalvik again. While you're in Recovery, it wouldn't hurt to run Fix Permissions.
HTH - Good luck!
I did a factory reset to the ics rom.
How do I clear cache and what is dalvik.
I'm going to download one of the official rezound 2.3 update toms and flash it. If that doesn't work ill take it to a Verizon store and see what they can do. It is under warranty.
I've noticed that apps function fine the problem is getting to and from the home screens. It's then that the phone freezes up for a minute or so.
Ok was going to reset phone to 2.3 but got the main version error so going to try this trick to get the main version down to where I can "upgrade" to 2.3:
http://forum.xda-developers.com/showthread.php?t=1467099
dsiglin said:
Ok was going to reset phone to 2.3 but got the main version error so going to try this trick to get the main version down to where I can "upgrade" to 2.3:
http://forum.xda-developers.com/showthread.php?t=1467099
Click to expand...
Click to collapse
Everything get worked out?
I can't get temp root to work so I can install superuser. Working on that now.
seems ICS leak has no temp root ability. I've reached the end of my road as I don't know where to go from here.
Related
So here's a peculiar incident:
I have a CDMA TP with a stock ROM and a few basic apps I gathered from these forums and others. I've had it for less than a week.
Tonite, I went to check my text messages. Suddenly, the screen went black and the phone stopped responding. After pressing the power button and fiddling with the keys, I pulled out the stylus and did a soft reset. No response. Confused by this, I tried again, but still nothing. I removed the battery, and turned the phone back on. It froze at the "Touch Pro" screen with the rom/radio/etc info at the bottom. After repeating this a few times I decided to do a hard reset. So, I turn the device on and perform the hard reset. By this point the TP is only turning on SOME TIMES, and I have to take the battery out and put it back in often just to get it to start successfully. So, I finally get the device to boot up and it starts to configure WinMo. Suddenly, while configuring, it freezes. Now I try to turn it back on, and nothing happens.
Basically the device is stuck like this, shifting between not turning on at all and turning on but freezing at the "Touch Pro" screen.
So, my question is, what the heck is going on here? Has anyone else had this problem, or does this sound familiar to anyone? Any help would be greatly, greatly appreciated.
p.s. Yes, the battery is fully charged.
kameisama said:
So here's a peculiar incident:
I have a CDMA TP with a stock ROM and a few basic apps I gathered from these forums and others. I've had it for less than a week.
Tonite, I went to check my text messages. Suddenly, the screen went black and the phone stopped responding. After pressing the power button and fiddling with the keys, I pulled out the stylus and did a soft reset. No response. Confused by this, I tried again, but still nothing. I removed the battery, and turned the phone back on. It froze at the "Touch Pro" screen with the rom/radio/etc info at the bottom. After repeating this a few times I decided to do a hard reset. So, I turn the device on and perform the hard reset. By this point the TP is only turning on SOME TIMES, and I have to take the battery out and put it back in often just to get it to start successfully. So, I finally get the device to boot up and it starts to configure WinMo. Suddenly, while configuring, it freezes. Now I try to turn it back on, and nothing happens.
Basically the device is stuck like this, shifting between not turning on at all and turning on but freezing at the "Touch Pro" screen.
So, my question is, what the heck is going on here? Has anyone else had this problem, or does this sound familiar to anyone? Any help would be greatly, greatly appreciated.
p.s. Yes, the battery is fully charged.
Click to expand...
Click to collapse
Time to take it in and get a new one.....
Same problem here phone started b not coming out of lock mode. Backlight is on but no display on screen (if i tilt the screen left and right i can see light coming from behind) did about 6 hard resets and still same problem. also power button works whenever it wants to. this phone sucks @ss, i want my mogul back. on a second note my replacement will be here on wednesday.
Touch Pro stock rom purchased back in nov when it came out
yeah, i've had the same problem, i found if i hit my phone on the back or side and then batter pull and hit the soft reset while off, not the power button to turn it back on, it comes back on with color on the screen not just blank black screen with backlight, this works mostly every time, but when it doesn't, i just hold the power button down and do battery pull and hit the power button and it works, its like its got a combo of things you have to do before it works.. weird
Boot Up
I have also had similar problems. I for some reason sometimes have to remove my SD card and boot up without it for some reason. Not all the time, but every once in a blue moon. Not too sure how that affects anything, but you may try that too.
well i started a thread here ***help*** because i kinda have the same problem.
i downloaded some cabs, nothing fancy but i had some problems with a theme i downloaded. when i went to deleted i couldnt..... to make a story short, i took it to the sprint store where they tried to do a master reset/ hard reset and it wont take it. it wont do a thing... they say some important files are missing...
the phone works but not the way it should... the time on the home screen wont show up. and some other small things...
dont know how this happened but i would like to know... im worried about new programs to the phone now. ( getting a new one)
still want to see if i can fix this one.
Mayonesa said:
well i started a thread here ***help*** because i kinda have the same problem.
i downloaded some cabs, nothing fancy but i had some problems with a theme i downloaded. when i went to deleted i couldnt..... to make a story short, i took it to the sprint store where they tried to do a master reset/ hard reset and it wont take it. it wont do a thing... they say some important files are missing...
the phone works but not the way it should... the time on the home screen wont show up. and some other small things...
dont know how this happened but i would like to know... im worried about new programs to the phone now. ( getting a new one)
still want to see if i can fix this one.
Click to expand...
Click to collapse
Have you tried re flashing the ROM?
it wasnt HTC's fault for your phone's not booting...thats what happens when u try to mess with the hardware too much and you dont know what your doing
Would you want to sell???
Reboot Brick HTC process
****DOn't take battery out after hard boot***
1.just watch videohttp://www.youtube.com/watch?v=sk56olMkCtU and do what they do but dont take battery out. LEAVE phone STUCK on BOOT screen. Nothign else will move or work but you want phone just like that.
2. connect usb cable to active sync. (this may not link up but leave usb connected anyhow) Do not delete phone profile.
3.use rom like Download MightyROM6_Herman.exe avail at: http://www.lilrico.com/Mighty/mightyromblog/?p=454
4 although active sync is still attatched but may not be connecting. It will connect thru usb anyway when you run the rom software. http://www.youtube.com/watch?v=fV2I2WAFkg4&NR=1
This worked and kept phone from cutting on and off. and restored ROM. don't know about original htc boot. but your phone will work under this rom for now and you can go from there.
hey thanks plain ole dumb, it works now.
man I thought it was over.
thanks again
I pulled down the update this morning (finally) and now I am not getting my ring/chime when I receive a text or call. Just vibrate. And no, I'm not on vibrate... If I go into settings>sound and try to open the volume, ringtone, or default notification menus, the settings app freezes. Eventually I get a pop up asking if I want to wait or kill it. I've waited and waited and it never works. Killing it and trying again doesn't work either. Neither does a reboot. Everything else seems to work ok, from what I can tell so far. What is going on here?
Not sure if there is any relation, but as it finished up the app updates during the upgrade (I think it said starting apps) it froze. I did power + vol- to turn it off and then rebooted. Got the upgrade successful message.
Thanks for your help.
My phone froze on the exact same screen and I ended up doing the same thing. Here's the thing: From what I can tell, the phone wasn't really stuck. For some reason, it might take up to 2 hours for some people to make it past that point. So, something is running in the background, even though it is stuck.
If you perform a Power + Volume Down force shutdown, when you reboot it will eventually tell you that the install was successful. But..., everything that it needed to do wasn't really done. In my case, the only way to fix things was to perform a Factory Reset (not as scary as it really sounds). That fixed it for me.
Can't say it will work for everyone, but I do recommend it anyone who performed the forced shutdown because s/he though the phone had frozen.
illinicj said:
I pulled down the update this morning (finally) and now I am not getting my ring/chime when I receive a text. If I go into settings>sound and try to open the volume, ringtone, or default notification menus, the settings app freezes. Eventually I get a pop up asking if I want to wait or kill it. I've waited and waited and it never works. Killing it and trying again doesn't work either. Neither does a reboot. Everything else seems to work ok, from what I can tell so far. What is going on here?
Not sure if there is any relation, but as it finished up the app updates during the upgrade (I think it said starting apps) it froze. I did power + vol- to turn it off and then rebooted. Got the upgrade successful message.
Thanks for your help.
Click to expand...
Click to collapse
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
I posted this in the A500 forum as well, but it's probable that this is not a problem limited to my device, and it's also possible that there is a rom that might help me out.
I purchased my tablet on the day it came out, so it's long out of warranty. Everything has been fine with it until three nights ago.
I woke up in the morning to a crashed app alert. I don't get crashed apps often, but it does happen, so I hit ok. A few seconds later I was inundated with crashed app alerts. At that point, any app I opened would also crash immediately. Figuring a good reset would fix it, I turned it off...and it wouldn't turn back on.
I did finally get it to start by holding the volume up and power button.
But that didn't fix the problem. I've discovered that it is somewhat stable if I keep wifi off, but if wifi is on, within minutes everything starts to crash again.
I tried uninstalling some of the apps that crash, but when I restart, the apps are back. It doesn't matter what I uninstall, when I restart, it's back. Installed apps also disappear, the wallpaper resets...basically nothing I do sticks once I restart. I tried to factory reset using the button combination required for my device, and the screen gives the "erasing user data" message, but when it loads up, everything is just as I left it. I tried using the android os option to factory reset, but when I hit "erase everything", the button depresses, but nothing happens.
So obviously, I'm a bit perplexed.
I've never rooted it, and I ran an anti-virus scan a few hours before this all happened and it came up clean.
Anyone ever experienced this? Any advice? If no one has any ideas one how to fix it, is there a way to bypass the main os completely with a rom? I have absolutely no idea how those work, so it may be obvious that it won't, but I figured I'd check.
Thanks in advance! And thanks for reading this far, even if you have no advice!
OK, this is really weird - after getting the 4.2.2 update, my phone reboots itself every night, not 100% sure it's exactly the same time, but it's been while sitting in my pocket or on the table, not even in use. At first I assumed it was Zooper, which I had installed right after the update, but I disabled it yesterday and got the reboot again tonight.
I even checked my Tasker to make sure some auto-reboot profile hadn't installed itself!
Any hints about how to diagnose this? Do I have no choice but to remove apps one by one? Most of the apps I run are the same ones I run on my TF300 tablet which also has 4.2.2, so don't know if it could be an app.
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
PhysicalEd said:
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
Click to expand...
Click to collapse
the Factory reset will erase all ur Apps and will stay in 4.2.2 ......
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
PhysicalEd said:
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
Click to expand...
Click to collapse
The update may have screwed up somewhere in the middle, you could try to re-ruu your phone or unlock the bootloader and flash a custom rom, also the thing about the power button not putting the phone to sleep or doing anything than reboot on long press happened to me on each and every custom rom and I never did any OTA, got my phone, unlocked bootloader and flash away from sense, my hboot is still the one that it came with, but for me that thing happens really randomly, like once every 1 or 2 weeks, and when that happens for me the volume buttons stop working also till reboot, I was thinking I was the only one facing it so I kinda decided not to talk about that as I saw no one say anything about it, but I am also one of those for who the phone turns off exactly when my phone goes to 6% battery whatever I do, on whatever rom I am and even in the recovery, so I was thinking that maybe vodafone modified something on it, that's an other reason I didn't say anything about the buttons becoming unresponsive...
So what I would recommend is to re-ruu your phone or go to a custom rom (or if none solves anything the phone may have some kind of hard brick).
Just to help out anyone else who ever has this problem.
It was not location services.
I can see clearly in two logs an HTC process crashing. This seems to cause a cascade that leads to reboot.
I contacted HTC tech support, they suggested I boot up in a recovery mode and try to wipe data cache. They were surprised to find that attempting to do that caused a reboot.
So as Ranomez suggests above, they want me to re-do the update with the RUU when they release it, which they said would be "soon" last weekend.
On the other hand, my battery life after this update is fantastic, so I've decided I can live with this to not have to worry about recharging by mid-afternoon!