Problème Mise à jour Samsung A5 2017 de 2.3 vers 2.9 via OTA

[Olive]

Bonjour,

J’ai réussi à flasher mon A5 2017 vers IodeOS 2.9, malheureusement le smartphone ne veut plus se déverrouiller.

Il me semble rentrer dans ce cadre là :

Encryption activated - Phone cannot be unlocked

Hi, I just installed latest iode on a Samsung Galaxy A5 phone. After some days playing with the phone I saw, that the device was not encrypted (LOS does this by default) - so I decided to activate encryption. Result: I cannot unlock the phone with my PIN any more. When booting there is a PIN entry and I give the PIN. Then the UI appears and the device is locked - I enter the PIN again - but it loops again and asks for the PIN. I reinstalled the phone - activate encryption and get the same odd …

J’ai apparemment le Secure Boot activé, car il m’est demandé un code PIN (qui fonctionne).
Mais ensuite, il m’est demandé le code de déverrouillage, qui ne fonctionne plus.

J’ai essayé les méthodes ci-dessous via adb (certaines demandent des accès root, que je n’ai pas).
Mais aucune ne fonctionne.

Avez-vous une astuce pour débloquer l’accès au contenu du smartphone ?

Merci d’avance pour votre aide,

Olivier

---

Méthode 1 :

adb shell settings put secure lockscreen.disabled 1
adb shell mv /data/system/locksettings.db /data/system/locksettings.db.old
mv: bad ‘/data/system/locksettings.db’: Permission denied
adb reboot

Puis celle-ci :

adb shell locksettings set-disabled true
Error while executing command: set-disabled
java.lang.IllegalArgumentException: Credential can’t be null or empty
at com.android.server.locksettings.LockSettingsService.doVerifyCredential(LockSettingsService.java:2065)
at com.android.server.locksettings.LockSettingsService.doVerifyCredential(LockSettingsService.java:2052)
at com.android.server.locksettings.LockSettingsService.checkCredential(LockSettingsService.java:2017)
at com.android.internal.widget.LockPatternUtils.checkCredential(LockPatternUtils.java:424)
at com.android.server.locksettings.LockSettingsShellCommand.checkCredential(LockSettingsShellCommand.java:313)
at com.android.server.locksettings.LockSettingsShellCommand.onCommand(LockSettingsShellCommand.java:89)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.locksettings.LockSettingsService.onShellCommand(LockSettingsService.java:2426)
at android.os.Binder.shellCommand(Binder.java:929)
at android.os.Binder.onTransact(Binder.java:813)
at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:1031)
at android.os.Binder.execTransactInternal(Binder.java:1154)
at android.os.Binder.execTransact(Binder.java:1123)

Méthode 2 :

adb shell
a5y17lte:/ $ settings put global LOCKSCREEN_AD_ENABLED 0
a5y17lte:/ $ settings put secure lockscreen.disabled 1
a5y17lte:/ $ locksettings clear
Error while executing command: clear
java.lang.IllegalArgumentException: Credential can’t be null or empty
at com.android.server.locksettings.LockSettingsService.doVerifyCredential(LockSettingsService.java:2065)
at com.android.server.locksettings.LockSettingsService.doVerifyCredential(LockSettingsService.java:2052)
at com.android.server.locksettings.LockSettingsService.checkCredential(LockSettingsService.java:2017)
at com.android.internal.widget.LockPatternUtils.checkCredential(LockPatternUtils.java:424)
at com.android.server.locksettings.LockSettingsShellCommand.checkCredential(LockSettingsShellCommand.java:313)
at com.android.server.locksettings.LockSettingsShellCommand.onCommand(LockSettingsShellCommand.java:89)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.locksettings.LockSettingsService.onShellCommand(LockSettingsService.java:2426)
at android.os.Binder.shellCommand(Binder.java:929)
at android.os.Binder.onTransact(Binder.java:813)
at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:1031)
at android.os.Binder.execTransactInternal(Binder.java:1154)
at android.os.Binder.execTransact(Binder.java:1123)
a5y17lte:/ $ locksettings set-disabled true
Error while executing command: set-disabled
java.lang.IllegalArgumentException: Credential can’t be null or empty
at com.android.server.locksettings.LockSettingsService.doVerifyCredential(LockSettingsService.java:2065)
at com.android.server.locksettings.LockSettingsService.doVerifyCredential(LockSettingsService.java:2052)
at com.android.server.locksettings.LockSettingsService.checkCredential(LockSettingsService.java:2017)
at com.android.internal.widget.LockPatternUtils.checkCredential(LockPatternUtils.java:424)
at com.android.server.locksettings.LockSettingsShellCommand.checkCredential(LockSettingsShellCommand.java:313)
at com.android.server.locksettings.LockSettingsShellCommand.onCommand(LockSettingsShellCommand.java:89)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.locksettings.LockSettingsService.onShellCommand(LockSettingsService.java:2426)
at android.os.Binder.shellCommand(Binder.java:929)
at android.os.Binder.onTransact(Binder.java:813)
at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:1031)
at android.os.Binder.execTransactInternal(Binder.java:1154)
at android.os.Binder.execTransact(Binder.java:1123)
a5y17lte:/ $ exit
adb reboot

Et enfin Méthode 3, le formatage de la partition de cache.

---