Weird situation started tonight. Phone is my sons and is completely stock. If i pop the battery out and boot it, i am able to get in from lockscreen and use the phone without issue. If i let the screen timeout or lock it the screen will not respond to touch what so ever essentially locking me out of the phone unless i pop the battery again. Ive tried the basics, hard reset, changing lock screen settings. Any ideas? Even with a reset im leaning towards a software issue as it works fine once i do get in. I appreciate any input, thanks
Had a simular issue mine was caused with an issue regarding superuser permissions and my set cpu enabling when screen timed out. Seemed my cet cpu wasn't getting superuser and wasn't abling my phone to turn on.
Sent from my DROID3 using XDA App
ryfhoff said:
Weird situation started tonight. Phone is my sons and is completely stock. If i pop the battery out and boot it, i am able to get in from lockscreen and use the phone without issue. If i let the screen timeout or lock it the screen will not respond to touch what so ever essentially locking me out of the phone unless i pop the battery again. Ive tried the basics, hard reset, changing lock screen settings. Any ideas? Even with a reset im leaning towards a software issue as it works fine once i do get in. I appreciate any input, thanks
Click to expand...
Click to collapse
Restore using a SBF, if you look under the general tab, probably page 2, look for my fast/easy unbrick. This can be applied to a unbricked device as it restores EVERYTHING back to 5.6.890 (leaves SD cards alone though). That should fix your problem.
Related
my g1 keeps on restarting after i downgraded my phone to rc29 so i can root it. this never happen to me before. if i have my charger plugged into my phone, when the phone loads and passes the g1 screen onto the android screen, it'll automatically reboot itself. if my charger isnt connected. it wont reboot, it'll just turn off. i have 2 g1s and both battery are working perfectly. what am i doing wrong? i can enter to recovery mode and fast boot without any problem. DREAMIMG is installed correctly also. a little help will be great! thanks in advance
I've just ran into this myself. I am running Biffmod 2.0, went into UI settings, changed LED notification for missed call, it rebooted, changed it back, still rebooting, rebooting itself ever since. Put it on charge as I have to go out. Picked it up, missed call. Rebooting. Went into Menu to look at LED settings, still rebooting.
:/
Give up. GAME OVER.
Well, not so dramatic. Short answer for me = Hard reset. Not much on there anyway. Done too much reflashing for that.
Scorpia said:
Give up. GAME OVER.
Well, not so dramatic. Short answer for me = Hard reset. Not much on there anyway. Done too much reflashing for that.
Click to expand...
Click to collapse
all i know that it's not bricked. there has to be a way to fix it.
WEIRD! i got it working now. took the phone apart to the main board and put it back on slowly. and WOILA! it worked lol
Hi I tried using the search function but I think it's disabled at the moment. The screen on my friends droid always stops responding. And since it's locked theres no way to use the phone. Restarting the phone / a battery pull doesn't solve it. It just stays non responsive. The screen is still working sort of, I can see the battery charge moving and when texts are received they display at the top. But when I call her phone from mine the screen stays at the lock screen. Any help would be greatly appreciated. My friend is stressing over this so I'm trying to help her out.
Hi, I am having the same problem. I tried uninstalling some applications from a custom recovery, and even doing a factory reset didn't solve anything. I also tried booting without the SD card, without any luck. Actually I'm thinking about taking it to Motorola to have it repaired or replaced, cause I have no idea left about anything possible to try.
Sometimes when I leave my Nook alone for awhile and then come back I am unable to wake it up by pressing one of the hardware keys. I have to plug it in and it boots up(rather than just waking up) has anyone else had a similar problem?
THis is seemingly random. It was on sleep all night and I woke it up to read this morning(after about 8+ hours of being in sleep mode). Just now however I tried to wake it up and it would not(after less than 45 min of being in sleep mode).
I'm having a similar problem. I've found that I can also make it come on by holding the power button long enough for it to do a shutdown (30 seconds I think) and then turning it back on. After I did a factory reset it worked correctly for a week and is now doing the same thing. I've had the issue on the stock software and with root applied. I'm going to return it today.
I know it's not helpful, but at least you aren't the only one with the problem.
How does the return process work? Can I just box it up and take it back to the store?
You might try a full factory reset before returning it. Do the 8X reboot and then the 3 button data reset. See if this helps as it may be a software issue and this may help/eliminate the problem.
Yes, I have seen this before. Are you running SetCPU on it? I removed it from a friends device and it resolved the problem in that particular case. He was going to return it as well. He probably would have had the same issue with the next one since he would have potentially installed the same apps (with the same settings) on it from backup. SetCPU may not be completely at fault since it may have been setup wrong. All I know is that, it stopped happening after it was removed.
I was using CPUtuner up until a few days ago. I was however using Settings Profile Lite so I don't know if that may have had something to do with it.
I've had a similar issue ... occasionally it won't turn on, and I need to hold the button down for 20 seconds or so to get it to reboot.
However, I've found that if I use the N button to bring it out of standby, that it happens so infrequently that I haven't taken the time to troubleshoot if this behavior persists in an un-rooted state.
Sounds like exactly the same issue I have with a SetCPU for Windows Mobile. Locks up the device on wakeup and needs a soft reset to get it back up and running. Almost made me late for work as my phone is my alarm.
I believe it also had the same effect on the EVO I had for a bit but configuring to a more strict setting and keeping it from throttling up and down seemed to help. (OnDemand setting over conservative I believe)
About the return, yes just box it up with the cord and take it back. I told them the issue and they exchanged it for a new one with no problem. I did the full factory reset before I took it back so that I could unroot the device and it still displayed the same behavior. So far on the new one I have no problems. I do notice that the power button click action is better on the new one. Perhaps that was a problem with the one I had.
Hmmm. Okay. I just attempted to wake up my nook with no luck after doing the factory resets last night. I will probably be boxing it up and exchanging it tomorrow.
Sent from my NOOKcolor using the xda app
I used to have the same problem and found that all I had to do was uninstall and reinstall auto-nooter and problem solved. Im not sure if you're rooted or not.
I get that once in a while... haven't looked much into it but if I plug it in it'll reboot or if I hold the power button for a while it'll also reboot. No biggie... I'm a WM user for a very long time. I've learned to live with the little annoyances
I got mine exchanged, the lady just wanted to update my softwre because she was sure that would fix it, then of all things the screen crapped out and wouldn't respond to her touches anymore so I got a new one.
I haven't rooted this one yet.
Did ATT release some sort of stealth patch over the weelend? As of Sunday morning my home button now links to Desktop Home instead of the standard Android home. My phone also gets stuck in landscape mode.
I am running stock froyo with root and clockwork only installed!
The funny part about this is I can restore to a previous saved backup and have it start in non landscape. But once I reboot, say goodbye to portrait mode. You get stuck in landscape.
Anyone else had this issue and fixed it?
Highly doubt it, not their speed.
Caution swyping! Read at your own risk.
No att did not send some update to you.chances are it is a messed up accelerometer for the rotation problem and possible a setting change or random bug that has affected the homer button
Sent from my SAMSUNG-SGH-I897 using XDA App
Well the funny thing is I do a factory reset and things are fun. No problems and every thing works perfect. Once i reboot after re-setting things up, it forces landscape mode and changes the home button. The accelerometer isn't broken. The reason I say this is because i can switch between between landscape and portrait just fine until I reboot the phone for the first time. If it was broken, it would not be able to do this.
One thing I am going to do is try and go back to factory in an area there is no service and see what happens. If it still does it, then I may be infected with something. But would be interesting since I haven't installed anything in weeks!
If ATT is sending stealth updates, then who knows what the heck they are doing with our phones!
There are no stealth updates. Recalibrate your accelerometer and it will work fine again. I never had the problem on my Captivate, but once I upgraded my brothers to KB1, his had the accelerometer issue. Horizontal calibration in Settings>Display fixed it.
I think I had the same problem.. Everything became landscape...
I just rebooted and it was fine..
Sent from my phone
Well recalibrating did not work. Still stuck in landscape mode. Rebooting does nothing. Still trying to find a place to test the theory that I was on first connect with ATT.
One other thing. If I clear the delvik cache, it rests the portrait mode and switches correctly from there until I reboot the phone. Then it switches back to landscape only. This is driving me nutts. I can not get this crap to top happening.
crystalhand said:
the homer button
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
D'oh!
I love a good typo
Sent from a Captivate on Bluedipity 6.2, SP#59, JQ1 with Xda App
So does anyone have any ideas on what to do with this? If I factory reset and clear delvik, I get the screen to work fine till I reboot. Once I reboot the phone, it gets stuck in landscape mode. I have tried everything on this and still can not get this to work. I am just about ready to ODIN it and see if that resolves the issue.
I have re calibrated about 50 billion times and it does nothing! Its not the exceleromitor since I can factory reset and it works till I reboot.
tnerb123 said:
So does anyone have any ideas on what to do with this? If I factory reset and clear delvik, I get the screen to work fine till I reboot. Once I reboot the phone, it gets stuck in landscape mode. I have tried everything on this and still can not get this to work. I am just about ready to ODIN it and see if that resolves the issue.
I have re calibrated about 50 billion times and it does nothing! Its not the exceleromitor since I can factory reset and it works till I reboot.
Click to expand...
Click to collapse
How about replace? That's where you are at.
replace as in bring it to att and get a new one?
Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?
sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)
The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol