Notices


Reply
Thread Tools
Posts: 1 | Thanked: 1 time | Joined on Apr 2014
#11
Originally Posted by ivir View Post
Hi,
Due I forgot device lock number I figured how you can ask on correct device lock or reset it.

For this purpose is there app /usr/lib/qt5/plugins/devicelock/encpartition

Arguments:
Code:
--is-set lockcode
--check-code <oldcode>
--clear-code <oldcode>
--is-clear-device-set ???
--unset-clear-device ???
--imei <something>
--clear-code <oldcode>
--set-code <oldcode> <newcode>
--set-config-key ???
--developermode ????
--clear-device <oldcode>
True/False are returned via exit code where 0 - success, 1 - fail
else as standard output.

Configuration is stored at directory /usr/share/lipstick/devicelock/ and encrypted/hash key is stored at /usr/share/lipstick/devicelock/.devicelock.enc, quite interesting are stored texts at binary file encpartition:
41414141, 42424241, 123456789012345 and /dev/block/platform/msm_sdcc.1/by-name/QOTP . More on http://www.onlinedisassembler.com/odaweb/4fDoTf/0

Unfortunately still don't know how reset device lock without sending to repair facility or brute-force.

Test all numbers with length 5 takes less than 3 hours on the phone with utilizing 20% of CPU.
Could you please explain how I use the posted app (zip file)?
 

The Following User Says Thank You to samuels For This Useful Post:
ZogG's Avatar
Posts: 1,389 | Thanked: 1,857 times | Joined on Feb 2010 @ Israel
#12
Originally Posted by rainisto View Post
You report theft to your local police, and they will report imei to operators imei db, and they will use blocklist depending what country you are in.
The phone would not come back to you anyway, so maybe t makes harder for theft to sell it, but eventually he will, but in cost of making it harder for users, by locking themselves out.

Let's compare it with gmail locking you out forever till you contact them for 5 mistakes. It sounds great, but it's not that practical, so it makes only pain for users.

There are other options that can be used i think.
__________________
IRC nick on freenode ZogG
imgrup
 

The Following User Says Thank You to ZogG For This Useful Post:
Posts: 120 | Thanked: 841 times | Joined on Jul 2015 @ Berlin, Germany
#13
At the risk of digging out an insanely old thread:
Simply removing /usr/share/lipstick/devicelock/.devicelock.enc and then running

Code:
/usr/lib/qt5/plugins/devicelock/encpartition --set-code
will reset the code (or probably just using the settings-app will work too).

You can remove the file using any "As Root" file explorer from openrepos.
 

The Following 5 Users Say Thank You to jakibaki For This Useful Post:
olf's Avatar
Posts: 99 | Thanked: 362 times | Joined on Aug 2015
#14
Originally Posted by jakibaki View Post
At the risk of digging out an insanely old thread: [...]
Thank you so much, I never found this information, which enabled me to "upgrade" my testing phone to a fully capable backup phone, again.
For more than two years I lived with the awkward situation to have full control over the device (as root), but being unable to set the lock-code (fortunately "automatic locking" was unset, so the device became my testing phone).

Cheers!
 

The Following 5 Users Say Thank You to olf For This Useful Post:
Posts: 1,779 | Thanked: 4,145 times | Joined on Feb 2011 @ Germany
#15
Originally Posted by olf View Post
Thank you so much, I never found this information, which enabled me to "upgrade" my testing phone to a fully capable backup phone, again.
For more than two years I lived with the awkward situation to have full control over the device (as root), but being unable to set the lock-code (fortunately "automatic locking" was unset, so the device became my testing phone).

Cheers!
I was once in pretty much the same situation, but didn't dare to do what @jakibaki has done (in the end I remembered that I had indeed changed the code, and I could remember the new one

Thanks for confirming that this works
 

The Following 2 Users Say Thank You to reinob For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 16:42.