Diskussion:Android Device Encryption

Aus NOBAQ
Version vom 2. Dezember 2014, 20:06 Uhr von 93.83.102.170 (Diskussion)

(Unterschied) ← Nächstältere Version | Aktuelle Version (Unterschied) | Nächstjüngere Version → (Unterschied)
Wechseln zu: Navigation, Suche

Kommentare zur Seite „Android Device Encryption


Inhaltsverzeichnis

M0rt15 meinte …

21. Februar 2014

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"

--M0rt15

Niki meinte …

21. Februar 2014

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!


--Niki

Ninety-9 meinte …

1. Dezember 2014

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.

--Ninety-9

Ninety-9 meinte …

2. Dezember 2014

OH, I DO HAVE A WARNING!!!

DO NOT EXCEED 16 CHARACTERS!!!!


"vdc cryptfs changepw" will gladly accept as many characters as you wish to enter. And why not? If I only have to enter this password on boot up, let's make it 20 or more!


Well, turns out that when you go to reboot your phone, Android only allows you enter a string of 16 characters. It would seem that my encryption is tied to a 17-character string and the phone is limited to a text box which only allows 16. I will probably have to Factory Reset.

--Ninety-9

Niki meinte …

2. Dezember 2014

Ninety-9, thanks for this info!

--Niki
Meine Werkzeuge