9

I have an Samsung Galaxy S3 Neo.

Bus 002 Device 042: ID 04e8:6860
Samsung Electronics Co., Ltd
GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]

The keyboard & language setting is português.

I today installed Android Device Manager and to test it's functionality I locked the phone with the password: "abcd" (4 letters were required).

After entering the password and confirming with the "OK" button of my keyboard, the phone showed me that the password is wrong. "Senha incorreta".

I reset the password after some tries to "123456" and the phone reloaded the lock screen. Again the password showed up to be wrong. I also tried the alphabetic password: "abcdefg" - same error.

I changed the language of my Google account from German to Portuguese and reset the password to "123456" again and I tried to really reboot my phone and unlock the SIM card again. But anyways I can not get through my lock of the Android Device Manager.

I tried to enter the password 35 times wrong with hope to get a chance to authenticate with my Google Account login.

I also tried to connect the phone with adb but it does not show up in this state with:

adb devices

So what can I do to get access to my phone again?

Ryan Conrad
  • 22,673
  • 9
  • 58
  • 81
tokam
  • 219
  • 1
  • 4
  • 7

3 Answers3

4

I tested this on a Nexus 5 (v5.0.1) running UK English. I locked the device with Device Manager then, without unlocking it, I used Device Manager to lock it a second time. I then used the second password to unlock the device. So, you should be able to change the lock password using Device Manager - it seems that only the last lock password is required to unlock it.

You can use a one character password to lock the device. Perhaps give that a try?

Another thing you could try (assuming you are using the web page to lock your phone) is to use Device Manager on a different Android device to lock your phone. Perhaps there is something wrong with the translation between the characters in the language entered into the web page and those entered into your phone.

Hopefully someone else might have a better answer than this. :(

Chris
  • 166
  • 1
  • 5
  • I tried éééééé as a password but the phone claims again that the password is wrong. – tokam Jan 04 '15 at 02:14
  • @tokam, perhaps use a single character (rather than six characters), and make it a simple ASCII character without an accent? For example, just one letter 'a'. As a lot of Android development happens in California, it wouldn't surprise me if an accented e caused problems. :) – Chris Jan 04 '15 at 02:16
  • Does not work too. The phone was new from today. I invested 2 hours to configure all. I will wipe it now and try to reproduce the problem. – tokam Jan 04 '15 at 02:19
  • Oh! If there's nothing important on the phone, maybe test Device Manager's "Erase" function. :-) If you can reproduce the problem, make sure you file a bug report with Google. – Chris Jan 04 '15 at 02:20
  • @tokam: Immediately before you try to reproduce the problem, may I suggest you do two things: 1. Enable USB debugging. 2. Make a full backup of your phone, apps, and all of your custom settings. Later on, please let us know whether or not you manage to reproduce the problem. – unforgettableidSupportsMonica Jan 04 '15 at 02:22
  • How to do that backup? Just copying some folders? – tokam Jan 04 '15 at 02:24
  • 1
    I reproduced it. I will now wipe the phone again.

    How to create the bug report? At the Google telephone support where I ask (before wiping the firste time) the lady gave me this obviously wrong link:

    https://support.google.com/chrome/answer/95315?hl=en

     – tokam Jan 04 '15 at 02:52
  • 1
    I created the bug-report: https://code.google.com/p/android/issues/detail?id=93132&thanks=93132&ts=1420376781 – tokam Jan 04 '15 at 13:06
  • Wrong Forum: Status closed! – tokam Jan 04 '15 at 20:33
  • 1
    @tokam My apologies. I gave you the wrong link - that was for developer related bugs. This is the one you need: https://code.google.com/p/android/issues/entry?template=User%20bug%20report . As well, I would suggest putting as much information into the bug report itself, rather than linking to this website. Finally, it would be interesting for you to try setting your phone to US English and trying to reproduce the problem. My guess is that it would work properly, in which case you'd have evidence that the problem is language related. – Chris Jan 04 '15 at 21:06
  • 1
    https://code.google.com/p/android/issues/detail?id=93741&thanks=93741&ts=1420586269 – tokam Jan 06 '15 at 23:18
  • @tokam: How to do the backup? I don't know. You can post a separate question if you like. – unforgettableidSupportsMonica Jan 13 '15 at 02:03
  • @tokam: Android Device Manager (ADM) is closed-source. There is no public bug tracker. Instead, go here, click the gear icon, then click "Enviar feedback". I recommend that you type your message in both your native language and in English. If you want an open-source alternative to ADM, you can use Open Device Manager instead. – unforgettableidSupportsMonica Jan 13 '15 at 02:04
0

I was having the same problem with ADM. I went to https://findmymobile.samsung.com and went to protect device (left hand side). I then clicked "Unlock screen". Took a minute but worked fine.

cde
  • 773
  • 6
  • 15
skifans
  • 111
  • 3
  • It seems like you did not use the Google Device Manager. That's why you received a vote down (from someone but not me). I was not able to solve the problem. – tokam Apr 03 '15 at 18:07
  • That's true. But the question didn't say that it needs to be unlooked via device manager. Also this way of unlocking your device will still work even if it was looked via device manager. – skifans Apr 04 '15 at 18:47
  • How did you lock the phone? With device manager? – tokam Apr 07 '15 at 11:43
0

The reason it won't work is that the current version of Google's ADM does not change the password when the lock screen is already applied. The current reasoning is that it is there to lock a device that was lost/stolen, not to change the password when forgotten. So even though it says it works, it isn't. There is a message that may pop up saying:

Since Google has verified that a screen lock is already set, the password you entered won't be needed.

Though it took a bit for that to pop up on ADM, and it goes away quickly. Thanks Google.

On top of that, Samsung's proprietary changes to Android also complicates things. If the device is also registered with Samsung via Find My Phone (The Samsung Device Manager), it needs to be unlocked from there.

There is no other normal workaround. Another option is to flash a custom recovery, and unlock it via root methods, highly depends on the phone.

Community
  • 1
cde
  • 773
  • 6
  • 15