Hey XDA'ers. I need your help. I just bought a Captivate today from someone, and I realized (once I got home) that the phone would never let me advance from the "slide up to unlock" screen. I tried everything, and it won't unlock. The only way to actually get into the phone is by rebooting it and swiping up (like to unlock it normally) as soon as you can. If you lock and attempt to unlock it after that, it does nothing.
I unrooted the phone, did a soft factory reset (retaining 2.2 Froyo), a hard factory reset, and even did an Odin3 reset (back to 2.1), to no avail.
Is there anything I can do, or is this phone beyond help?
Thanks!
You should not longer have a "slide up to unlock" if you oden-ed back to stock AT&T 2.1. Stock 2.1 only had one unlock screen and it was the sliding glass. Or, is this what you had and it still wouldn't unlock?
Sent from my Cappy.
Yeah, it's the standard "sliding glass to unlock" screen.
I just rememebered that a similar thing happens when I am done with a phone call. It takes a good 10-15 seconds for my phone to register that yes, I am done with the phone call, and yes, I should be allowed to select "end call" after I'm done.
Anyway, it's all very frustrating having a phone that is usable only after a reboot (the slide to unlock screen actually does unlock only at this point.) Any ideas?
Any help here? http://www.androidzoom.com/android_applications/tools/screen-lock-suppressor_mqhk.html
pc103 said:
Any help here? http://www.androidzoom.com/android_applications/tools/screen-lock-suppressor_mqhk.html
Click to expand...
Click to collapse
This is more of a workaround as opposed to a fix, but if it works, then our friend here won't have to reboot every time the phone locks.
Just curious, did your seller say anything about the phone doing this?
~Gemuse
gemuse said:
This is more of a workaround as opposed to a fix, but if it works, then our friend here won't have to reboot every time the phone locks.
Just curious, did your seller say anything about the phone doing this?
~Gemuse
Click to expand...
Click to collapse
Well, I was able to just exchange the phone at an AT&T help center for free, without any problems.
And the guy I bought it from said that it had "no hardware issues." And what a lie that was. He wouldn't even answer my phone calls after I figured out that it didn't work. BUT, it all worked out for the best.
Related
Perhaps it's merely a training issue on my part, but does anyone here ever have the problem where the slide to unlock doesn't unlock. It always happens to me if the phone is locked and I get a text while it's locked, and sometimes even when no texts were received. The slider will slide all the way to the left or right, but then nothing happens. The only way I can get back to using my phone is to perform a soft reset.
I've experienced this same problem on several different ROMs. First on the NATF series and now on the last several Energy series.
Does this sound familiar to anyone? Any advice is greatly appreciated. BTW, I've searched all over, but wasn't successful in my searches. I may be searching the wrong key words.
Thanks in advance
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....
Yes you read it right I want to know how I can brick my phone or make it stop working completely. Now let me explain the reason why. I had installed an app called "Launcher Pro". Later I uninstalled it and that is when all hell broke lose. Basically when ever I would swipe my screen to unlock the phone, I would get constant error messages that would reappear the moment I would close them, and to make matters worse it would lock out the rest of the screen so I can not click any thing else (just like in windows vista and windows 7 when a UAC message pops up). This is further complicated by the fact that I have a Bell Canada Samsung Galaxy Phone, which does not have the 3 button recovery ability but that is not the end of my problems. I got this phone at a store called Best Buy and got their warranty. Now one of the things that voids the warranty is unlocking the phone, guess what?? My phone is unlocked. So since my phone is not dead, it boots up, the lock screen loads up, the top bar shows u the battery life and the fact it is getting service and can receive calls (but which I can not answer since when it comes to that screen, the screen freezes up with the error messages). So if I take the phone to Best Buy, they are going to pop in a different sim other then bell and when they see that it works, will hand me back my phone and void my warranty. So I need to have the phone in such a condition that they can not check that and yes there can be no physical or water damage either. How do I accomplish this?
Is it rooted ? Did u happen to enable usb debugging ?
If so a mere "adb reboot recovery" followed by a wipe data would solve ur issues
Ya it is rooted, but usb debugging is not activated and I can not activate it the normal way through the settings screen, if you would know a way to do it some other way, that would be great. Just to let every one reading this know, I do not want to change my phone if I can help it, if there is a way for me to fix this with out bricking the phone and getting a new one, I will be more then happy to keep my current phone. Thanks
Zink6 said:
Ya it is rooted, but usb debugging is not activated and I can not activate it the normal way through the settings screen, if you would know a way to do it some other way, that would be great. Just to let every one reading this know, I do not want to change my phone if I can help it, if there is a way for me to fix this with out bricking the phone and getting a new one, I will be more then happy to keep my current phone. Thanks
Click to expand...
Click to collapse
Have you tried booting into safe mode. Usually booting into safe mode will disable any 3rd party apps from loading. This might give you the chance to uninstall LauncherPro or even enable USB debugging. The method to get into safe mode for the Bell Vibrant seems tricky though:
Menu + Home + Power On right when you see the Samsung logo (specifically: http://forum.xda-developers.com/showpost.php?p=8583886&postcount=17) probably hold the keys. I know in the other Android phones (HTC Ion) you have to hold Menu from beginning til it boots.
http://forum.xda-developers.com/showthread.php?t=758678
Seems to work sometimes...
Why dont you just re-lock your phone?
Sent from my GT-I9000M using XDA App
Why unlocking it with code would void the warranty? if you flash, yes, maybe. but you enter the unlock code... isn't the official way? Don't bother how i got the code, I bought it, it's mine, i can unlock it. period. i dont understand how they would consider to void the warranty because you unlock with code. btw, Bell does give unlock code for 75$. so, my phone is not eligible for warranty?
MadWhips said:
Why dont you just re-lock your phone?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Guys c'mon.. At least read his post. He can't gain access to the phone at all right now. How do you expect him to relock?
Honestly with no adb you can't do much if u dont have 3button working
Try all those 3button tricks posted for those who can't get to recovery/download mode.
One if i recall is :
Turn off phone
Press n hold Home + Vol Down (or Vol up, up 2 u) + power
Keep holding, your phone will restart once, then twice, then let go off power button.
Its worth a shot
I work at best buy. They will not stick another sim card into the phone. Is it within the 30 day return policy? If its within 30 days go return it and show them the phone dont work and they will exchange it for you.. If its not within the 30 days they will most likely have to send the phone out to Samsung.
What i would do :
1. Take the phone back to the store.
2. Tell them the thing dont work...they wont know if its unlocked or rooted.
3. Ask them to exchange it under the manufactures warranty (if its not within the 30 days) and hopefully they will exchange it and not have to send it out to samsung.
WIN.
PM me if anything.
Asked the rep at best buy (by the way this is best buy Canada), and he said warranty is void if unlocked.
like eduard said, just take it do them. don't even ask or mention unlocking coz that will make them think that you have unlocked it.
take it there, say it doesn't work. done. don't ask, don't tell.
lol thats why you dont tell him you unlocked it! wow man.
its not about you telling them that u unlocked it, their procedure is to insert a different sim into the phone before sending it out for repair and/or exchange. And that is when I will be caught. So aside from giving best buy the phone, does any one else have any other ideas?
Did you try this?
http://forum.xda-developers.com/showthread.php?t=813580
I also have a Bell SGS. I got it from Wireless Wave and fortunately I have 3b recovery. You've tried both (up+home+power) as well as (down+home+power) right? You let go as soon as you see the boot screen that says i9000.
Drop it in the water?
zorxd said:
Drop it in the water?
Click to expand...
Click to collapse
Water damage is not covered by warranty.
From what i read, i can't imagine this is a hardware problem (though i could be wrong), so probably the worst that can be is that your phone needs a reflash. How much would that cost in CA if you can't talk it into a warrantee case?
Ya its not a hardware issue, its a software one. Let me give u more information. The phone boots and goes to the lock screen. Shows the correct time and date and shows on the top that it was connected to my phone service but the moment I swipe the screen to unlock, I get repeating messages, one of them reads "The process android.process.acore has stopped unexpectedly. please try again." and the other reads "The application TwLauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again". Both messages have a "force close" button on the bottom that takes the message away just for it to reappear a second later.
Also from what I have been reading in the forums, if I can only get my phone into usb debugging mode in any other way then the typical MENU > Settings > Applications > Development > USB debugging, it would solve all my problems. If any one knows how to do that, please share your knowledge.
There is a post on here for making a USB dongle that powers the phone straight into download mode.
You need a USB plug and a resistor.
You can then re flash.
Sent from my GT-I9000 using Tapatalk
Here's what you can do:
When you've started the phone (and the error messages come up) you connect your device to your PC with the USB cable.
At that point you'll see a new menu on the background (behind the error messages) for the selection of your connection (Samsung Kies, Mass Storage, etc...)
Click away the error messages very quickly and press the button Samsung Kies (you may have to try several times before you can do this but it's possible)
Then you open Samsung Kies and you use the procedure that is mentioned in the post below to reflash your device with a test firmware:
http://forum.xda-developers.com/showthread.php?t=766589
Make sure to read through that tread to know what codes you have to use in the registry. You should be able to flash your device in Kies with a (test/official) firmware this way.
In the end you my not even have to return it at all...
I have had two Galaxy S handsets auto-brick themselves. They were working fine and then suddenly they would not turn on. All I would get was a black screen. I could not even factory reset.
I've gotten the second set repaired by Samsung. They think that an app is causing the problem. What both handsets had in common was that they were unlocked. The first set had lag-fix but not the second. Also, both sets were running LauncherPro.
What do you think is bricking my phones? Now I am afraid to run any apps. I can't believe that sim-unlocking would brick my phone. That just doesn't make any sense. Is it LauncherPro then?
Thanks much.
anwark76 said:
I have had two Galaxy S handsets auto-brick themselves. They were working fine and then suddenly they would not turn on. All I would get was a black screen. I could not even factory reset.
I've gotten the second set repaired by Samsung. They think that an app is causing the problem. What both handsets had in common was that they were unlocked. The first set had lag-fix but not the second. Also, both sets were running LauncherPro.
What do you think is bricking my phones? Now I am afraid to run any apps. I can't believe that sim-unlocking would brick my phone. That just doesn't make any sense. Is it LauncherPro then?
Thanks much.
Click to expand...
Click to collapse
Were the phones actually bricked or did they just suffer from the mysterious comatose syndrome where the phone will essentially shut itself off and the only way to get it back on is to hold the power button for like 10 seconds or sometimes have to do a battery pull?
I am assuming that you tried these items on your past 2 devices. If they were actually bricked and the ONLY thing they had in common was the sim unlock then I would definately take a look at that to start.
Perhaps it was not the fact that they were unlocked but maybe the method you used to unlock them?
Anyone else have any ideas or answers?
I used the utility from xda that gives you the unlock code from your phone. Then I entered the unlock code the phone asked for it. Is there any other way to unlock it? Could it be the launcher?
PS: The phone was actually bricked.
8 days ago, I decided my s5 had had enough abuse, and got the z force. It's been an amazing phone, other than the heat, which has always seemed a little warm, but didn't do anything to slow the phone down. Up until today, it's been glitch free, and I loved it.
Until about six hours ago. I wasn't paying attention to the battery, it died in the middle of watching YouTube videos with my kids, so I let it finish powering down, plugged it in, and let it charge. Upon turning the phone back on, I got an error message saying the device failed validation and may not work properly. Five second delay and it powered on, and everything seemed to function normally. Rebooted the device, same screen. Factory reset the device, same screen. I took the phone back to Best Buy and got a replacement, and I'm hoping it doesn't happen again, I really happen to like this phone...but I'm curious. Moto's customer support's first question was if I'd unlocked the bootloader or rooted the device, but being verizon-locked, I'm well aware that isn't possible and haven't attempted it. Anyone have any ideas why my phone just randomly decided to fail the bootloader verification so I can try to avoid replicating this mess?
I'd like to know as well. I have the same message every time it boots but it doesn't seem to affect anything I've noticed so far.
Mace68 said:
I'd like to know as well. I have the same message every time it boots but it doesn't seem to affect anything I've noticed so far.
Click to expand...
Click to collapse
If you boot into the bootloader does it say if your device is locked or unlocked?
BladeRunner said:
If you boot into the bootloader does it say if your device is locked or unlocked?
Click to expand...
Click to collapse
No such luck lol. It says "oem_locked" and software status is "Official".
Sent from my XT1650 using XDA-Developers mobile app
I wanted to add that a factory reset didn't clear the message.
I also wonder if it has to do with turning on allow bootloader unlock in dev options. It seemed to have happened at about the same time I turned it on.
Mace68 said:
I wanted to add that a factory reset didn't clear the message.
I also wonder if it has to do with turning on allow bootloader unlock in dev options. It seemed to have happened at about the same time I turned it on.
Click to expand...
Click to collapse
Factory reset didn't fix mine, either. And as far as turning on the bootloader unlock option...I hadn't even enabled dev options on mine, so I'd assume that's just a coincidence on yours.