Hi,
not sure if the problem is général or ROM related...
This morning after new kernel flashing, I rebooted, and at the same time was talking to some people.. so I looked at my phone at least 5 min later, and the boot process was done for long, and SIM card was locked...
I didn't find how to manually launch the PIN code identification process, had to reboot...
Is there a way to do it without rebooting ?
Striatum_bdr said:
Hi,
not sure if the problem is général or ROM related...
This morning after new kernel flashing, I rebooted, and at the same time was talking to some people.. so I looked at my phone at least 5 min later, and the boot process was done for long, and SIM card was locked...
I didn't find how to manually launch the PIN code identification process, had to reboot...
Is there a way to do it without rebooting ?
Click to expand...
Click to collapse
Not sure about this, but I think turning flight mode on/off will bring the pin id screen back.
TrymHansen said:
Not sure about this, but I think turning flight mode on/off will bring the pin id screen back.
Click to expand...
Click to collapse
Thanks I will try if this happens again... I made a test but after 10 min the PIN code screen was still there so I wonder was it didn't last that long this morning...
No matter thanks again.
Striatum_bdr said:
Thanks I will try if this happens again... I made a test but after 10 min the PIN code screen was still there so I wonder was it didn't last that long this morning...
No matter thanks again.
Click to expand...
Click to collapse
I think I have the solution to your problem. I am using pbs shell 3d, and sometimes while it restarts (after booting phone) the pin screen does not appear. It seems to happen with a few launcher or similars to spb shell. It has happen to me quit offen. The solution is to install a task killer. If it happens again, drag the task killer and kill all runningprogrmas. The pin screen will appear straight away.
Maliacrete said:
I think I have the solution to your problem. I am using pbs shell 3d, and sometimes while it restarts (after booting phone) the pin screen does not appear. It seems to happen with a few launcher or similars to spb shell. It has happen to me quit offen. The solution is to install a task killer. If it happens again, drag the task killer and kill all runningprogrmas. The pin screen will appear straight away.
Click to expand...
Click to collapse
Ok thanks, I'll try this too if needed.
Related
Happened this morning, I noticed that my diamond2 is not responding when pressing the power button as usual... black screen!
It wakes-up in two cases:
1. soft reset with the stylus.
2. removing the battery and putting it back then pressing the power button.
This happens after I leave it turned off for 5 minutes. It is working fine as long as I don't turn it off. When it is off 5 minutes then no response!
Note: I am using the latest htc rom.
Don't know if this is a software or hardware problem. Any help is much appreciated.
I have actually had a fairly similar problems with my TD2. Not regular and not at spercific times like after 5 minutes but there have been times when my screen doesn't want to turn back on, the device is still on because it still make some of the regular sounds, eg the ping on the home button but the screen is dead.
Like you it will only wake again after a battery out reset, sometimes after several attempts.
I'm pretty sure this is hardware related as like you i'm on an official rom. The first time this happened was after using the phone as a modem and it got quite hot so i think perhaps heat is loosening the connection to the screen, only a guess though so any other opinions welcome.
After trials for 8 hours, I figured out a work around.
I Forced the mobile to work in the GSM only band, from that moment, it is back to normal... 3G is important to me, but I think I will wait until the WinMobile 6.5 is out for our TD2... may be this will solve the issue!
Hard reset it at least once..... That may take care of the freezing issue.
tomtommy306 said:
Hard reset it at least once..... That may take care of the freezing issue.
Click to expand...
Click to collapse
did not solve the problem! could this be a network problem or the device's radio rom?
My phone did the same, i disabled the TouchFLO and it worked Fine
mkh1983 said:
My phone did the same, i disabled the TouchFLO and it worked Fine
Click to expand...
Click to collapse
This one also did not solve the problem. Any other suggestions!
Problem solved
As I guessed, it was a network error and problem sovled after changing my Sim Card and getting a new updated one from the Service Provider!
Now my TD2 can sleep well and get back whenever called
6.5 is out, has been out for a while now for the TD2...What are you waiting for, might solve this issue...gogogo!
Free Man said:
6.5 is out, has been out for a while now for the TD2...What are you waiting for, might solve this issue...gogogo!
Click to expand...
Click to collapse
I have the same problem and i notice that sleep everytime who i use Alarm(clock)...
Noticed that??????
Some times alarm clock sound doesn't work.... the audio level is high...
Free Man said:
6.5 is out, has been out for a while now for the TD2...What are you waiting for, might solve this issue...gogogo!
Click to expand...
Click to collapse
I am afraid I have to bump the thread.. I received my device from the HTC service with a new 6.5 ROM installed, and I started having this problem. The deviced sleeps and does not react to pressing Power button, neither to pulling the stylus. The only way how to wake it is to remove the battery and switch it on again. Any idea how to solve this?
The same problem
cassper1 said:
I am afraid I have to bump the thread.. I received my device from the HTC service with a new 6.5 ROM installed, and I started having this problem. The deviced sleeps and does not react to pressing Power button, neither to pulling the stylus. The only way how to wake it is to remove the battery and switch it on again. Any idea how to solve this?
Click to expand...
Click to collapse
My TD2 starts the same problem . After some standby time the power button stops working. I tryed to re-flash ROMs , Hard Reset, Change the battery, and nothing solve the problem. The Power Button not working! The only way is soft reset... Any idea?
This is referred to as the "Standby of Death"
The only fix I am aware of is to flash a custom ROM.
hello guys. there is no need to flash a new rom. i had same issue, but hard reset and backup restore helped me. try this on your phone. for back-up, use sk tools
http://www.s-k-tools.com/index.html?sktools/m_feat.html
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Do a hard reset / wipe. That's my suggestion.
Try booting into recovery (Home Button, Vol Up + Power), and resetting your cache and wiping it. Then try logging in with your Google account. If all else fails, try changing your Google password on the PC then logging in on the phone. And then if it still fails, looks like you need to flash the phone again. Next time, don't enter the thing wrong! Stop rushing haha .
I wasn't rushing, I was playing with the lock. It takes about 30 times before it's permanently requiring the username/password. But really...you can't blame me for not expecting this. :/
I'm currently trying to flash a new ROM but I've run into another problem - I can't get it to boot into downloader/recovery. It's not the lack of the 3 button combo - I've managed to reach Recovery and Downloader ONCE each in the past, but never again since.
And now with all my efforts to boot into recovery/downloader, it now cannot boot into normal usability mode (or in my case, locked mode). Instead, the Galaxy S logo loops endlessly.
Sigh.
Have you read the thread for the fix for Galaxy S variants that are lacking the 3 Button Combos? It's in Android Development. Maybe try that? Or, can you still connect the phone and connect with Kies?
I can't turn on the phone anymore, meaning no changing to USB debugging etc. And I'm having problem accessing recovery/download, even though I definitely HAVE done each of them once before and therefore do not have the 3 button problem.
Without turning on my phone, Kies can't detect it
So what happens when you power on?
Now, it shows the first Galaxy S splash screen, then shows the boot logo, then nothing. The boot logo continues to glow endlessly.
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
okpc said:
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeah it's continuously shining. Haven't left it for up to five minutes though... And even then it probably won't help since I'm still locked out of the phone, and unable to access download/recovery mode to reflash it.
After waiting for a long time, the logo disappears, screen goes black. Menu and back buttons light up. Nothing else.
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
PaulForde said:
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
Click to expand...
Click to collapse
Good advice considering he said his 3 button combo stopped working =))
All I did when I got that black screen was adb reboot recovery and wiped and phone bootedup fine. But only if you have debuging enable and and sumsung drivers. Hopes this help.
Sent from my SGH-T959 using XDA App
Can't enable USB debugging when phone can't be turned on at all.
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
danamoult said:
Can't enable USB debugging when phone can't be turned on at all.
Click to expand...
Click to collapse
you need to be able to enter recovery mode for you to solve this problem
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
dear friend dont worry or panic... i'll tell you a trick , go to the samsung customer care and tell them that your phone gets heated up very often and today it just refuses to boot up normally...
since your device cannot get into recovery mode or download mode the company will never know that you had played with the system files in the device or not... (rooted )..
since the samsung people will also try to get your device in recovery mode.. but when it will not go to the recovery mode you will get a mother board replacement under warranty.....
this heating up of the device is a common problem in the galaxy here in india.. so use this excuse and i know it works 100% ... (just dont tell them that you had rooted and lagfixed your device )
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
OzzYGuY said:
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
Click to expand...
Click to collapse
distortedloop said:
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
Click to expand...
Click to collapse
chill my dear friend.... it cant be true.... its just his 1st post.. and samsung cannot be so dumb to leave a password protected keypad that can be cracked so easily.. even i tried the back key on a call with a password lock.. i cannot get passed the lock screen....
So my brand new 24 hour old Xperia Z1 will not start and only goes to a blank screen with the backlight on. It does show the SONY splash screen before this for a second.
The only way to shut it down is to do an up volume and on button combo or to hit the red reset button.
I've tried starting with the SIM and SD Card out but it doesn't seem to make a difference.
The phone has pretty much not been used at all so I am a bit shocked. Is there any thing I can try? It was working last night.
24 hours out of the box, just send it back for a new one.
even if its starts working again, for a £600 device I would just send it back and say you are not happy and want a new one
30Seconds said:
So my brand new 24 hour old Xperia Z1 will not start and only goes to a blank screen with the backlight on. It does show the SONY splash screen before this for a second.
The only way to shut it down is to do an up volume and on button combo or to hit the red reset button.
I've tried starting with the SIM and SD Card out but it doesn't seem to make a difference.
The phone has pretty much not been used at all so I am a bit shocked. Is there any thing I can try? It was working last night.
Click to expand...
Click to collapse
Did you wait a minute or two ?
mines takes ages to boot up after the sony logo...dont know what it is
MeLViN-oNe said:
Did you wait a minute or two ?
mines takes ages to boot up after the sony logo...dont know what it is
Click to expand...
Click to collapse
I went off and left it for about 10 minutes and it did finally restart. I suppose there is some sort of software conflict issue going on.
I did a factory wipe and it runs like lightning now. No idea which app is causing the conflict.
30Seconds said:
I went off and left it for about 10 minutes and it did finally restart. I suppose there is some sort of software conflict issue going on.
I did a factory wipe and it runs like lightning now. No idea which app is causing the conflict.
Click to expand...
Click to collapse
first boot up, upgrading apps..there is loads that can causea long boot, but nothing that needs a thread about a bootloop
MeLViN-oNe said:
Did you wait a minute or two ?
mines takes ages to boot up after the sony logo...dont know what it is
Click to expand...
Click to collapse
This is one of the fastest phones on the market and this shouldn't be happening. After I did my restore I set up again and synched and auto-updated apps and I had the same problem. I then tried deleting all of my uploaded apps one by one until they were all gone but this didn't help and the boot times were still about 5 minutes, often with the phone booting without remembering the brightness setting or even not booting at all.
So I did a factory reset again but this time did not account synch on setup or auto update apps and that seems to have fixed it for me. The phone is very fast and boots in under 30 seconds now, and runs without any lag whatsoever. I wish I could identify specifically what the issue is but so far no luck.
Hello,
My phone is almost a month old now and first two weeks were fine no problem at all. Now last few days it has been randomly rebooting itself when I swipe my lockscreen to open. It never does this when I am using the phone only sometimes when I'm unlocking the screen by swiping or just directly go from notifications etc. This happens like twice a day depending how much I use my phone.
I also feel like it first started to happen when I updated it. To be honest I am not sure what it did update. I also installed bunch of apps which I did delete later.
What should I do next? Factory data reset? Or is there a way to see the "crash report" or something to see whats causing it?
tldr; phone randomly reboots after lockscreen, what to do
Thanks.
Stompdaroach said:
What should I do next? Factory data reset? Or is there a way to see the "crash report" or something to see whats causing it?
tldr; phone randomly reboots after lockscreen, what to do
Thanks.
Click to expand...
Click to collapse
After the update if some issues show up is recommended to do a Factory Reset. Start do that.
eclyptos said:
After the update if some issues show up is recommended to do a Factory Reset. Start do that.
Click to expand...
Click to collapse
Agreed. If that does not work, re-flash the phone with a stock FTF to start over. If the problem continues after that, it must be some hardware issue.
eclyptos said:
After the update if some issues show up is recommended to do a Factory Reset. Start do that.
Click to expand...
Click to collapse
I did that and didnt get single reboot yesterday. Too bad I didnt try this earlier. Thanks.
I am having the exact same issue.
Here is that I have done that didnt work.
Reset (vol up/pwr)
reset using red button by sim card
factory data reset
software install using pc companion
However, After each one I set the phone back up how I had it. I had the gmail widget on the lock screen. the phone would reboot at random times right after attempting to unlock. I removed the gmail widget and it hasnt happened since! I sat here locking and unlocking for about 15 minutes and it hasnt rebooted.
IN SHORT TRY TO REMOVE THE WIDGETS BEFORE ANYTHING ELSE
Hope this helps
brianb1998 said:
i am having the exact same issue.
Here is that i have done that didnt work.
Reset (vol up/pwr)
reset using red button by sim card
factory data reset
software install using pc companion
however, after each one i set the phone back up how i had it. I had the gmail widget on the lock screen. The phone would reboot at random times right after attempting to unlock. I removed the gmail widget and it hasnt happened since! I sat here locking and unlocking for about 15 minutes and it hasnt rebooted.
In short try to remove the widgets before anything else
hope this helps
Click to expand...
Click to collapse
it has not rebooted since i originally posted this. It is now 4/25
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on
Nope it's off
Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.
The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater