Galaxy S3, can't unlock.

[AnAndroidDroid]

Hello, I've been using my S3 for about 4 months without any major issues until now.

The phone is not rooted, I am not using a lock screen app or a launcher app, locked to Rogers. Haven't installed a new app for at least a week I think, although I'd imagine some of the existing apps have been updated (none today I don't think).

When I press the unlock button, the lock screen comes up normally (I use pattern lock), but the moment I input my pattern, the screen goes off.

When I press the lock button again to turn the screen back on, I can very briefly see my home screen before the screen turns off again. The home screen, when I can see it, is extremely dim, dimmer than the lowest brightest setting.

At this point, when I press the lock button again, the same thing happens (EDIT: this also happens when I press the home button). If I leave it alone for a while and press the lock button, the lock screen will come up normally.

So, the logical conclusion would be, the phone thinks that the screen timed out, as opposed to me turning it off by pressing the lock button, because I have it set up that the phone locks immediately when I press the lock button, but doesn't lock for I think 5 seconds, if the screen times out on its own.

I've tried battery pull, as well as starting the phone without sim or sd card, all to no avail.

Has anyone encountered this before and know of a solution? Or any suggestions?

I am still under warranty, but I'd hate to go through that. I want to avoid doing a factory reset even, since I've never backed up my phone (no lectures please) and I got quite a bit of crap on it. Speaking of which, would I even be able to do a factory reset at this point?

I would appreciate any help whatsoever. Thanks.

 

[meyerweb#CB]

To answer the last question first, you can probably still do a factory reset by booting into recovery. If it gets to that point, we'll tell you how.

Does the battery have a good charge on it? If you're not sure, plug the phone in for an hour or two to make sure that's not why the screen goes off immediately.

 

[AnAndroidDroid]

Thanks for replying,
Battery shows 55%, but while I wait for further answers, I will charge it just in case.


Also, when I press "emergency dial" from lock screen, the stock dialer shows up normally.

 

[AnAndroidDroid]

Well, the lock screen bypass bug present on samsung devices (the one that was all over Android news websites a few weeks ago) seems to work.

Got to the home screen, notification bar doesn't work, phone seems sluggish, and screen times out (but doesn't lock) every few seconds. Also can't seem to lock the screen anymore (without doing a restart). Not sure if all of this is normal once you used this bug to bypass the lock screen?

Anyway, obviously can't use the phone like that, I'm just hoping this will shed some light on the issue, and someone may be able to connect the dots.

Also, now I may be able to go into settings and tweak stuff, if anyone wants me to try something.

Not sure if I'd be willing to disable lock screen though, because if that doesn't solve it, I won't be able to get back in using the lock screen bug.

 

[AnAndroidDroid]

Solved.

Went into settings, and screen timeout was set to "()", which was an option above "15 seconds". Normally that option isn't there (obviously), not sure what prompted the phone to not only create that option, but also automatically switch to it. Anyway, changed it to something else and upon restart, the problem is gone, and the "()" is no longer an option under screen timeout.

Hopefully this thread will help others if they ever come across this. Would still like to know what's caused this, but I don't think I ever will find out.

On a side note, I am now afraid of installing Samsung's next update (if Rogers ever decides to push it..), which will surely contain a fix for the lock screen bypass bug. Meaning if it happens to me again, I'm screwed.

 

[GSDer]

So that you don't have to be afraid of updates or Factory Resets you may want to take a look at:
Call Logs Backup & Restore: http://market.android.com/details?id=com.riteshsahu.CallLogBackupRestore
Carbon: http://market.android.com/details?id=com.koushikdutta.backup
Easy Backup: http://market.android.com/details?id=com.mdroidapps.easybackup
MyBackup Pro: http://market.android.com/details?id=com.rerware.android.MyBackupPro
SMS Backup & Restore: http://market.android.com/details?id=com.riteshsahu.SMSBackupRestore
These are just a few examples of apps that you can use to backup whatever is important to you. Of course, be sure to sync your contacts/calendar with Google (if that's your preference), or use that capability in the appropriate backup selection that you make.
Depending on the direction you choose, you can make a backup to the SDCard or one of your cloud accounts.
Glad you were able to work through that strange problem - thanks for following up, since I'm sure someone else will find it useful.

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk 2

 

[meyerweb#CB]

..what?

Spam. I've reported it.

 

[meyerweb#CB]

Solved.

Went into settings, and screen timeout was set to "()", which was an option above "15 seconds".

That's very bizarre. Apparently some data corruption during the update.While problems caused by OTAs aren't unheard of, this is the first I've heard of this one. I second GSDer's suggestion to look at backup software.

 

[AnAndroidDroid]

So that you don't have to be afraid of updates or Factory Resets you may want to take a look at:
Call Logs Backup & Restore: http://market.android.com/details?id=com.riteshsahu.CallLogBackupRestore
Carbon: http://market.android.com/details?id=com.koushikdutta.backup
Easy Backup: http://market.android.com/details?id=com.mdroidapps.easybackup
MyBackup Pro: http://market.android.com/details?id=com.rerware.android.MyBackupPro
SMS Backup & Restore: http://market.android.com/details?id=com.riteshsahu.SMSBackupRestore
These are just a few examples of apps that you can use to backup whatever is important to you. Of course, be sure to sync your contacts/calendar with Google (if that's your preference), or use that capability in the appropriate backup selection that you make.
Depending on the direction you choose, you can make a backup to the SDCard or one of your cloud accounts.
Glad you were able to work through that strange problem - thanks for following up, since I'm sure someone else will find it useful.

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk 2

Thanks, I'll definitely take a look at those

Sent from my SGH-I747M using Tapatalk 2

 

[AnAndroidDroid]

That's very bizarre. Apparently some data corruption during the update.While problems caused by OTAs aren't unheard of, this is the first I've heard of this one. I second GSDer's suggestion to look at backup software.

I haven't updated my device since I got the phone months ago.

But yea, I couldn't find any mention of this issue anywhere.

Sent from my SGH-I747M using Tapatalk 2

 

[meyerweb#CB]

Ah, something I read made me think this happened after an OTA. My mistake.

 

[AnAndroidDroid]

Ah, something I read made me think this happened after an OTA. My mistake.

Probably when I said I'm now scared to update. I only meant that because any future update would fix the lockscreen bypass bug.

Sent from my SGH-I747M using Tapatalk 2

 

[vincent08]

It seems their is hardware problem with the phone. Kindly take the phone to any cell repair store.

 

[AnAndroidDroid]

It seems their is hardware problem with the phone. Kindly take the phone to any cell repair store.

I think there was some sort of a conflict between apps. Haven't had this issue since.

Sent from my SGH-I747M using Tapatalk 4 Beta