Diskussion:Android Device Encryption: Unterschied zwischen den Versionen
(Ein Kommentar wurde von Niki über die Programmerweiterung ArticleComments abgegeben.) |
(Ein Kommentar wurde von Ninety-9 über die Programmerweiterung ArticleComments abgegeben.) |
||
| Zeile 16: | Zeile 16: | ||
As stated in my update, I would STRONGLY urge you to take TWRP2! | As stated in my update, I would STRONGLY urge you to take TWRP2! | ||
| + | </comment> | ||
| + | == Ninety-9 meinte … == | ||
| + | |||
| + | <comment date="2014-12-01T19:54:46Z" name="Ninety-9"> | ||
| + | Worked Perfect! Galaxy S4 Kitkat. | ||
| + | |||
| + | I had already encrypted the device earlier and I was sick of the fact that I either needed a super-short startup password, or a super-long screen wake password. | ||
| + | |||
| + | With the device already encrypted before I read your post, I used Tasker and SS to set the new pin, and yes, it changed both the unlock and encryption code simultaneously. Then I ran the SU code within the Terminal Emulator and voila, I was able to change the encryption password without modifying the unlock pin. | ||
| + | |||
| + | Very happy with your method. Others suggested using python code and other overly complicated methods. I guess it helps that I already had SU, Tasker, Secure Settings, and Terminal Emulator installed, by coincidence, really. | ||
</comment> | </comment> | ||
Version vom 1. Dezember 2014, 21:54 Uhr
Kommentare zur Seite „Android Device Encryption“ <comments />
M0rt15 meinte …
<comment date="2014-02-21T06:05:40Z" name="M0rt15"> I keep getting errors on running /system/bin/setprop, any ideas what it means?
CANNOT LINK EXECUTABLE: cannot locate symbol "__strlen_chk" referenced by "/system/bin/setprop" </comment>
Niki meinte …
<comment date="2014-02-21T06:08:24Z" name="Niki"> Maybe your ld is not set up properly or so (e.g. missing environment variables).
As stated in my update, I would STRONGLY urge you to take TWRP2!
</comment>
Ninety-9 meinte …
<comment date="2014-12-01T19:54:46Z" name="Ninety-9"> Worked Perfect! Galaxy S4 Kitkat.
I had already encrypted the device earlier and I was sick of the fact that I either needed a super-short startup password, or a super-long screen wake password.
With the device already encrypted before I read your post, I used Tasker and SS to set the new pin, and yes, it changed both the unlock and encryption code simultaneously. Then I ran the SU code within the Terminal Emulator and voila, I was able to change the encryption password without modifying the unlock pin.
Very happy with your method. Others suggested using python code and other overly complicated methods. I guess it helps that I already had SU, Tasker, Secure Settings, and Terminal Emulator installed, by coincidence, really. </comment>
