yashsingh1/xdaforums huggingface dataset:
[Android General] robberknight:
I don't have a Honeycomb device to test so I don't know.

You can just try it though. The script tests the password before changing anything. The test will fail if encoding is done different on Honeycomb. And the script also creates a backup before overwriting anything.

I consider the chance that the script breaks anything quite low. But it can very well be that the script aborts with an error because something is done different on Honeycomb.
[Android General] xdascrat:
sqlite3 binary

Some hints:

I failed to install "Sqlite installer for root".

So I grabbed sqlite3 from SuperOneClickv2.3.3-ShortFuse.zip.

Somehow it won't start within the python script. It throws "cannot locate register_android_functions" in def sqliteFound(self) which ends up with the error "sqlite3 command not found". Executing sqlite3 -version in the shell caused no problem.

I managed to get sqlite3 working by installing again from "Sqlite installer for root" after proper remount of /system in read-write mode

"mount -o remount,rw /dev/block/mmcblk0p15 /system"

The PIN-Lock works now!

Using S3 with DarkyROM III v2.0 (Android 4.0.4)
[Android General] robberknight:
Thanks for reporting this. Seems they either changed it in 4.0.4 or just Samsung on the S3.

That's nice to hear, seems like the encryption & pin stuff didn't change.
[Android General] salatiel:
i am getting can not read salt when executing. ideas ?

---------- Post added at 03:11 PM ---------- Previous post was at 03:04 PM ----------

using jelly bean by the way
[Android General] 88%:
I'm not in JB, but when I got a "can't read salt" error recently, I got through it by changing SU back to "prompt" and then clicking through the prompts. I have no idea if this might work for you though.
[Android General] morpheus4you:
Thank you for sharing this information. This is exactly what I was looking for :)

I think it is logical to have a complex password for booting your encrypted android, but using a simple pin for unlocking your screen. Who wants to enter their complex password every time the lockscreen pops up?

Im running cyanogenmod 9 on SGS2 and I will report back here if it doesn't work somehow.
[Android General] salatiel:
The easiest way to accomplish this is to set the password for the boot using vdc cryptfs changepw PASSWORD.

---------- Post added at 04:07 PM ---------- Previous post was at 04:04 PM ----------

that will change the password for the encrypted volume while keeping you pin whatever you initially set up
[Android General] srynoname:
can you please elaborte on this? I assume the steps would then be

1) encrypt android phone using normal GUI way from the settings

2) Change PIN to some easy to enter PIN for the lock screen

3) Use vdc cryptfs changepw PASSWORD to set a strong password for the authentication during boot?

Update: Yes, that is how it works. See http://blog.joelj.org/2012/08/02/st...setting-a-different-bootlock-screen-password/
[Android General] azoom1:
Script method is better than "vdc cryptfs changepw" on Galaxy S2 Epic Touch

This script is the way to go for the Galaxy S2 Epic Touch for at least 2 reasons:

1) Using the "vdc cryptfs changepw" method doesn't seem to work. I tried Cryptfs Password and EncPassChanger both of which fail with the error that the current password is incorrect. My presumption is that the EpicTouch stores the password differently than a Nexus. (I tried to use it command-line as well, but I'm not really versed in that method so I'm not sure I was doing it correctly.)

2) The EpicTouch also requires an alpha-numeric password in order to encrypt. It will not accept a PIN. You must choose a password with at least 6 characters, including one alpha and one numeric. Again, this is different than the Nexus which appears to accept a simpler numeric PIN for encryption.

Thus, using the "vdc cryptfs changepw" method would not be optimal because you'd still be stuck with the alpha-numeric PIN that you used to initially encrypt the device. Thus, this script method that changes the GUI PIN is much better.

A hint for those who are trying this and have never used SLA4/Python (as I was):

1) Load SLA4

2) Menu-View-Interpreters

3) Menu-Add

4) Select Python 2.6.2 - the SLA4 app will go get Python and intall it with the correct linking

5) Exit SLA4, then start Python and select Install, and when finished, exit Python

6) Put the pin_change.py file in the SLA4 "scripts" directory

7) Start SLA4

After that, when SLA4 is run you should see the script in the pick list. Upon selection SLA4 will pop-up an icon select-list. Pick the gear, which will run the script.

Thanks to the original poster for sharing this.
[Android General] iamus:
This is awesome! Thanks goes to the OP!

I have one question though, Is there a way I can modify the python script to use the pattern instead of the pin ?
[Android General] azoom1:
S3 with JB 4.1.1 - "can't read salt"

Although this worked great on my Sprint S2, I've just upgraded to the S3, (running JB 4.1.1) and I'm getting stuck at "can't read salt". I did what I could and I looked through the script and confirmed the database is at the same location in the S2 and S3. However, although I can find the salt in the S2 database, it does not appear in the S3 database. Obviously, that's why it's getting the error. Unfortunately, I can't find any information as to where the salt in stored in JB. My thought was to make a small modification to the script and point it to the correct database.

This script made using encryption on the S2 very pleasant. Any assistance you can give in helping to get it working on JB/S3 would be greatly appreciated.

Thanks.
[Android General] creiss:
Awesome... but

Hey there!

Awesome little script that just works.

I am running on my Galaxy S3 here, feeling a lot more secure.

However, I just upgrades to Android 4.1.1 (Build JRO03C.I9300XXDLIH) and the script does change the password to a pin, leaving the encrpytion password intact, but it wont switch the device to pin input screen. I rather have the text box field, which is kinda annoying to use.

Would that be easily to fix for you?

Cheers,

and thanks for all the hard work,

much appreciated!

-Christian.
[Android General] azoom1:
Bonnwhe entire

Used this on the S3 with 4.1.1 and it worked perfectly. Thanks so much. :good:
[Android General] targetjr:
Using PIN for lockscreen and Password for Encryption

Figure out how to get the Galaxy S3 from Sprint to use the PIN numeric entry screen for my lockscreen, and a password and full-keyboard prompt for encryption.

The issue is that on stock ROMs for Sprint Galaxy S3 (and I believe this is true for many other S3 ROMs), you must use a full keyboard/password for the lockscreen and encryption. Using the EncPassChanger and other scripts based on cryptfs changepw won't switch the lockscreen entry method from keyboard to numeric keypad if your password contains only numbers. The following script keeps encryption password entry method (full keyboard) independent of lockscreen entry method (e.g., PIN).

The key is that you can enable encryption independent of your lockscreen via the following command syntax

su vdc cryptfs enablecrypto <wipe|inplace> <passwd>

The process for having a PIN lockscreen and a long password for system encyrption is

1) Set a PIN for your lockscreen as normal

2) From a terminal on a rooted system (tested on rooted stock Sprint G3), type

> su

> vdc cryptfs enablecrypto inplace <LongSecurePassword>​

Then wait...after about 30 seconds your android will reboot and the encryption process will begin. After encryption completes (about 1 hour) your system will reboot and eventually prompt for the <LongSecurePassword> to gain access to your system. You will only need to enter that password once for each reboot / power-on. The lockscreen will continue to use the original PIN input method and PIN code.

It might be possible to use this technique to even have a lockscreen with pattern or no security, while the device remains encrypted. That possibility has not been tested.

Use the above technique at your own risk. "Bad people" will still have easy access to your data (based on the lockscreen method chosen) until they reboot or power-cycle your android (when they will then be greeted by the request for your LongSecurePassword.

Also, I have not tried changing the PIN or lockscreen method after applying the above change. The unknown is how vendors have modified Android's lockscreen code - don't know how or when in the process they force the two to be kept in-sync.

-- TJ

BTW> more info on vdc command is via:

android.googlesource.com/platform/system/vold/+/b1596afa59c7108cc6ce23bab54a1bc41961806a/CommandListener.cpp​
[Android General] undyingnd:
error on S3 LTE

I tried it on my S3 LTE, but i get the message: "Can't find sqlite3 command". Afaik, SQLite is a part of the standar Android library, so it just seems to be the wrong version. Is there a simple work around for this problem?
[Android General] pulser_g2:
You can find apps on the market that will install it.

The binary isn't included in android, except for emulator builds.
[Android General] undyingnd:
works fine

ok, that was easy

works on S3 lte as well, thx
[Android General] haddy17:
I'm very happy to have found targetjr's post. Many thanks for the info. The default encryption handling of the Samsung ROMs is sub-par at best. One issue though, and I believe it stems from using the command, TWRP won't accept my encryption password and I am not able to mount storage. Anybody else have this issue when using targetjr's method above?
[Android General] doncaruana:
My GS3 is already encrypted. Do you think it would it be possible to do root it, do this hack, then "unroot" and have it retain the hack?
[Android General] fbiryujin:
First I apologize for responding to an old post, but I have a couple of questions.

After I do this, how do you decrypt again? I normally decrypt weekly to do a nandroid and perform updates/tweaks, and then reencrypt. Also has anyone tested changing the pin after encryption has been enabled? Does that break things?

Thanks so much!

TWRP never accepted my password even when using the standard encryption method. I'm on the Stock rom if that matters
[Android General] targetjr:
To decrypt you first use the standard menu options to set a long password for device security and then second you use the standard menu options to perform the decryption. It is quite straightfoward and needs no special commands or such.

Using the GUI you cannot change your pin. The GUI will force you to change your security to a long password. To change your pin you will either need to use a custom command or you will need to decrypt your device and then change the pin and then re-encrypt your device using the commands above.

Hope that helps.

--TJ
[Android General] fbiryujin:
Oh so I essentially just use the settings interface to change my PIN to the same password as my encryption password and then decrypt? Sort of like syncing the passwords I purposely avoided syncing?
[Android General] targetjr:
Exactly!
[Android General] fbiryujin:
Awesome thanks
[Android General] bitmonkey:
Thanks for the enablecrypto inplace command, I am expecting to use that when I receive the N4 I just ordered, but I wonder a couple of things:

- How will this interact with multiple users? If I want to create multi-users, perhaps I should create them first before encrypting?

- Has anyone yet actually tried it with face unlock?

- Does anyone know the custom command to later change a PIN without having to decrypt first? Presumably, with multiple users, I'd want to su to the user I was changing the PIN for first?

thanks
[Android General] jay.dumbali:
thanks
[Android General] LS1_01:
Modified version worked on the Nexus 4 with Cyanogenmod 10.1 as well! Thanks! :) The original script was giving the "password match hash failed" error likely because the password is stored in a different location on the Nexus 4 as well!
[Android General] IHawkMike:
Do Not Set the Password Longer Than 16 Characters

Just a warning for all of you to prevent making the same mistake I did: Do not set the password longer than 16 characters!

On my shiny new Galaxy S4 (SGH-M919) I am now locked out since the password field at boot does not accept extra characters. I'm attempting to decrypt with ADB but I might be stuck with a factory wipe as my only option.
[Android General] Am1G0:
too bad it wasn't wrote at top of the thread :\
[Android General] robberknight:
That's a problem only with the "vdc cryptfs enablecrypto..." method, right? Or does the android ui really allow you to set a longer password than it accepts later on?
[Android General] tarkboffin:
sqlite3 not found

Hi,

Nexus 7 (2012) Android 4.3 rooted

I couldn't get the Play app sqlite installer to work (cannot write to /system/xbin) so I installed sqlite3 manually to /system/bin.

(http://philbayfield.com/2011/04/08/installing-sqlite-on-a-rooted-android-phone/)

If I type sqlite3 in a terminal running on the tablet sqlite 3 runs successfully. (3.7.11).

The script will not run, however. I also tried placing sqlite3 in /system/xbin.

Any bright ideas out there?

Cheers

M.
[Android General] JackSlaterIV:
Hi robberknight (and all people here),

It would be nice to have a script that automatically submits the unlock password, a script that can be triggered by a Tasker event.

For example if you are at home (accessible wifi network) then the script unlocks the phone automatically.

So basically you'd have an encrypted phone when you go out, and an automatically unlocked phone when you are at home.

It's technically possible to make a script like that?
[Android General] mimox:
By "decrypt" you mean factory resetting or is there another way to decrypt? :confused:
[Android General] abhinavk:
I'm having the same problem for a different reason

I need to decrypt my SGS4 (except, AT&T SGH-i337) in order to do a full factory reset. Did you figure out how to decrypt over ADB?

Thanks,

--Abhinav
[Android General] texaslittleangel:
]Here's my problem, not sure if files can be pulled (I just need one file from my phone) given that debbugging is on

updated to the mixrom TWRP via Flashify in order to flash updated ROM.

Once in TWRP (it took password fine during first loggin) I:

Cleared Cache and Dalvik

Flashed Rom

Flashed new Gapps (failed)

Flashed kernal patch (for trinity)

Flashed Kernal

Flashed SU

Rebooted

When I booted phone prompted to enter "Enter password to decrypt storage" it is telling me that it is the wrong password. I've never had any issues until today that I flashed 4.4. I know it is the correct password. I tried going back into TWRP and when I am prompted to enter the password, it says Failed and I am unable to see my files.

Is there a way to pull the files via ADB? If so how? That would be great and I wouldn't feel sick to my stomach for my stupidity
[Android General] Timmey806:
Why don't you simply use Tasker for this case? Make a new profile, State - Connected to your network then create a new task select display - lockscreen - off. In this case I recommend you to use an exit task to lock your display while not connected to your wi-fi. Done :)

I'm using this task since more than a year with CyanogenMod. Works great but sometimes you need to turn your display on befor tasker locks your phone.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Android General] thx1200:
Encrypt SD Card?

Is there a way to encrypt the SD Card through a command line option? I ran into the same issue on the GS4 where when I go to the SD Card encryption options it tells me I need to set a strong password first, so I can't do it from the GUI.
[Android General] xdascrat:
Works on 4.3 OmegaROM (v54) S3 Internation with minor fix

Many thanks to pulser_g2 and OP,

I tried the script, but the check in sqliteFound doesn't work properly.

On shell sqlite3 -version works without any problem.

Within the script the command gives this output

"CANNOT LINK EXECUTABLE: cannot locate symbol "register_localized_collators" referenced by sqlite3

At the end the solution was, to comment out the line "sys.exit(1)", and the script runs without problems -> and my screen has PIN Lock!
[Android General] kilurb:
This thread has been very helpful. I have a Sprint GS4 and used the command-line method to enable encryption and a different PIN on 4.2.2. Now, I've had to use Kies to update my phone to 4.3 and the entire device had to be wiped. So I don't have encryption yet. But I've got root access, so at least that's working. My problem is that I can't get either command line encryption nor the built-in encryption to work. The phone reboots but when it comes back on a couple of minutes later, it isn't encrypted. I attempted to use adb logcat, but the file I redirected the output to was empty after the phone restarted. Honestly, I sure I'm not using it correctly. My beliefe is that /data is not being unmounted, but I don't know how to figure out what's preventing it. If anyone has any tips on how to get the logging working, or insight into what else be wrong, I would appreciate it.

There is nothing else I've done to the phone that I think is odd.

Thanks all.
[Android General] dadnammit:
Device and SD card encryption use same keys?

Clarification: Do the "encrypt device" and "encrypt sd card" features use the same cryptfs key? I am using both modes of encryption and wondering if changing the cryptfs password as described above will apply to both?
[Android General] dadnammit:
Thanks to targetjr but what about SD card?

[MENTION=2461547]targetjr[/MENTION] : Your approach sounds easier than using the python script or one of the apps on Google Play. But what about the external SD card? How can one encrypt that from the command line?
[Android General] dadnammit:
Can't past boot pwd prompt after cryptfs command

I'm on 4.1.2 Jelly Bean on a Galaxy S Advance, stock ROM (I9070XXLQE_I9070BTUMP7_BTU), rooted.

After running the above "vdc cryptfs enablecrypto inplace" command, or after setting up device encryption normally through the menus and then running "vdc cryptfs changepw", I can't get past the password prompt on boot. It keeps saying try again.

Has something changed with the encryption implementation and the cryptfs commands no longer work?

Note: I'm using a 16-char password (the max that the input screen will take), just in case that is relevant.
[Android General] sorceror171:
Sadly, it's not working with a Verizon Galaxy S4. I get the "Password hash compare mismatch" message; presumably Samsung's changed the hash. Anyone have suggestions how to proceed? I purely can't believe a usability issue like this has gone on so long. I assume they can't imagine this'll work if they turn encryption on by default!
[Android General] netrin:
Bumping this thread because it's still a very relevant issue.

Has anyone found a solution to the "password hash compare mismatch" issue for Galaxy S4 and S5?

The script was so useful, but Samsung must have changed their hash or something--is there a quick fix to this? A non-programmer like me can't figure it out, but I hope someone with experience can take a moment to look at it!
[Android General] thomasjfox:
the open source "SnooperStopper" application allows you to set a different password for the full disk encryption (FDE). So you can have a simple PIN for the lockscreen and a full password on boot for FDE. Internally it uses "vdc cryptfs" commands to accomplish that. Works for me on lineage 13.x and 14.x.

It also can detect xx number of wrong PIN entries and automatically shutdown.

Good if you ever loose your phone :) Either it runs out of battery or someone else finds it and tries various lockscreen pincodes.
[EVO 4G General] joshuar9476:
I decided to take my Evo 4G for a swim with me yesterday. 2 hours later I discovered what I had done. I loved my Evo, but still have 7 months until my upgrade. No insurance. I got a Epic Touch for $275 so once that comes in i will be moving on. Thanks to everyone here who worked on new roms.
[EVO 4G General] ou2mame:
lol bag of rice? always works for me. i see evo's on craigslist here for like 100 bucks. you can make it happen! don't leave!
[EVO 4G General] joshuar9476:
I tried to dry it out in kitty litter, which was all i had on me at the time. However, I panicked and put the battery in too soon and heard all the components fry for lack of a better term.

I get a $200 damaged phone credit from my premium checking account. My wife has had the samsung for a few months now, and the images are a lot crisper on it. I figured it was time to move on.

At least I'm not leaving telling everyone how big of a pile of crap this phone was as i have in the past with other phones (I'm looking at you Blackjack II) ... The Evo is probably my #1 of all time. As someone who has had 15 different phones, that says a lot to me.
[EVO 4G General] ou2mame:
lol.. i've had so many bad phones. the touch pro was probably the worst pile i've ever had the displeasure of pulling out of my pocket. i learned my lesson with wet phones. just let them sit... and sit.. and sit... eventually they come back to life. that sucks though.
[EVO 4G General] Chirpout:
Yeah they are CL all day for $100
[Samsung Galaxy Nexus] kyrumo71:
Here is the Hulu apk that works on my Galaxy Nexus, menu button enabled in softkeys is required

http://db.tt/7U4sLGuV

Sorry if this was posted before
[HTC Rezound] texasman420:
Everytime I go to check for a software update it starts checking then goes off quickly without telling me if there was one or not. Any suggestions?
[HTC Rezound] CharliesTheMan:
Are you rooted?
[HTC Rezound] texasman420:
Yea I'm rooted but I'm using the ota root hider keeper were it unroots me for ota updates
[HTC Rezound] murhaava1:
I was in the same boat as you. Check out this thread:

http://xdaforums.com/showthread.php?t=1469246

You can check the first and last post in that. The way I got around it was by activating my sim in another rezound and then swapping back into my original and it all of a sudden worked. Dont really know why, but i know another person got it working that way too.
[AT&T, Rogers HTC One X, Telstra One XL] kilo89:
Is anybody having issues getting the Dropbox to integrate with the stock Gallery app? Everytime I try to select it from the drop-down list the Gallery app FC's.

I have a Rogers One X with SuperCID. I ran the 1.85 AT&T RUU on it and installed CleanROM 2.1.
[AT&T, Rogers HTC One X, Telstra One XL] tcl16:
I have the same issue on cleanrom 2.1 and now 2.2 as well. I'm not sure if this was happening before I started using cleanrom. Hopefully someone has a fix for this.
[AT&T, Rogers HTC One X, Telstra One XL] artjrv:
Yeah I just tried it now and getting same issue. I on cleanrom 2.2.
[AT&T, Rogers HTC One X, Telstra One XL] Skizzy034:
There was an issue scrosler stated in the cleanrom thread about there being a problem with dropbox and gallery but I thought I remember seeing that it was for people who flashed and were not on the 1.85 ruu.
[AT&T, Rogers HTC One X, Telstra One XL] kravguy:
Same here. On stock, 1.73, I remember it working cause I was like, that's pretty cool. Haven't been able to get it to work for quite awhile now (I'm on 1.85 running clean rom but was on 1.82 prior and it was a no go with it as well). It really was the only reason I was keeping that gallery app cause I normally use quikpic or some other app instead. With space being so limited now, most of my pics are up on either dropbox or facebook so it would be nice to have that integrated (and working).
[AT&T, Rogers HTC One X, Telstra One XL] shackman716:
so I never even noticed that you should be able to view your drop box gallery from your phone gallery (if Im seeing/thinking this correctly). But when I click on the drop down and select drop box it says there are no folders to view, am I missing something?
[AT&T, Rogers HTC One X, Telstra One XL] kilo89:
Do you have it set up to automatically upload pictures you take? AFAIK, It will only show pictures that are in the dedicated "Camera Uploads" folder that is set up when you enable this option.