missing number pad on lock screen - unable to unlock [answered]

Question

0

missing number pad on lock screen - unable to unlock [answered]

asked 2017-10-26 00:35:36 +0300

fl0rp
161 ●6 ●7 ●19

dear co-sailors,

today an error-message was prompted on my aquafish (converted jolla c) on SFOS 2.1.3.3. it said something about me not being able to make phone calls and that this could only be restored by a restart. i remember having had that error message once before (don't recall when/which device/version/etc.), therefore i did indeed reboot the phone. unfortunately since after the reboot the number pad on the lock screen is missing. the phone boots just fine, even connects to the mobile phone network. from start/status screen i can swipe into the camera app or the ambience-selection also just fine. swiping left or right just brings up an empty page, where otherwise the number pad appears. it tried punching in my number combination blindly, in case the number pad might just have been completely opaque or something like that - to no avail, no feedback.

maybe also worth mentioning: i have the pattern unlock patch installed, yet not activated - so i use a number combination to unlock my phone. also wifi is disabled therefore i wont be able to ssh into the phone and poke around.

pointers (or a straight fix) are much aprechiated, as i couldn't find anything on together (might be pebcak, though).

cheers, fl0rp

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by pawel
close date 2017-10-26 14:58:46.339991

Comments

in my case it was related to mazelock patch

when ever.i did activate it the empty pannel would appeaer. not from the beginning since approx one.month.

the only.workaround was as you did describe, recovery uninstall all patches and reboot

pawel ( 2017-10-26 15:01:06 +0300 )edit

in my case it was related to mazelock patch
when ever.i did activate it the empty pannel would appeaer. not from the beginning since approx one.month.
the only.workaround was as you did describe, recovery uninstall all patches and reboot
pawel ( 2017-10-26 15:01:06 +0300 )edit

Accepted Answer

2

answered 2017-10-26 13:38:24 +0300

fl0rp
161 ●6 ●7 ●19

fixed it by clearing the number combination from recovery mode like so:

user@laptop $ telnet 10.42.66.66
-----------------------------
     Jolla Recovery v2.0
-----------------------------
Welcome to the recovery tool!
The available options are:
1) Reset device to factory state
2) Reboot device
3) Shell
4) Perform file system check
5) Run sshd
6) Exit
Type the number of the desired action and press [Enter]: 
3

If you continue, this may void your warranty. Are you really SURE? [y/N] y

  2 logical volume(s) in volume group "sailfish" now active

Type your devicelock code and press [ENTER] key:
(please note that the typed numbers won't be shown for security reasons)
[OK] Code accepted.
/ # mount /dev/mapper/sailfish-root /mnt/
/ # chroot /mnt/
bash-3.2# /usr/lib/qt5/plugins/devicelock/encpartition --clear-code
Enter security code:
bash-3.2# exit
/ # umount /mnt/
/ # exit

step-by-step that'd be:

power off phone
enter recovery-mode by pressing volume-up + power
hook up telephone and computer with a usb-cable
execute telnet 10.42.66.66 on computer
start shell
enter number combination (devicelock code)
mount the system partition
chroot into system partition
clear the number combination (devicelock code)
exit chroot
umount system partition
reboot

i was able to figure this out thanks to these:

edit flag offensive delete publish link

missing number pad on lock screen - unable to unlock [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by pawel
close date 2017-10-26 14:58:46.339991

Comments

1 Answer

Question tools

Stats

Related questions

missing number pad on lock screen - unable to unlock [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by pawel close date 2017-10-26 14:58:46.339991

Comments

1 Answer

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by pawel
close date 2017-10-26 14:58:46.339991