Hello all,
I have a Galaxy S5 G900T and have a fresh install of the latest Android 6.0 (2016-02-09) nightly. It is working perfectly but I am trying to encrypt the phone and it is not working. This worked previously on Android 5.1. When I go to Settings > Security Encrypt phone, it doesn't ask for any kind of password, I press Encrypt Phone and it immediately reboots, briefly shows the green android logo as if it's going to encrypt then shows the Cyanogenmod boot animation. I have left it on this for approximately 45 minutes before I unplugged the phone and removed the battery, then powered it back on to a normal startup. I again tried the same thing after setting a lock screen with exactly the same results.
So this apparently has something to do with Supersu and systemless root (guessing) as I did a factory reset and reinstalled the OS without installing Supersu and this time encryption worked. But now I am having trouble changing the encryption password.
I have tried the "vdc cryptfs changepw password default_password newpwd" from an adb shell method but it seems to do nothing.
I can set a password via lockscreen, but I'd like to have my boot encryption password decoupled from my lockscreen password. Does anyone have this working?
Ok I figured it out. After running "vdc cryptfs changepw password default_password newpwd" you must run "vdc cryptfs verifypw newpwd". All is working now, hopefully this helps someone else out
Interesting find, I can indeed confirm this as I've been experiencing the same issue with my GS4A SGH-i537. I can encrypt fine with a fresh OS, but post root SuperSU install, it hangs at the boot screen immediately after a brief screen of the android robot.
So turns out everything isn't working as it should after all. It is not recognizing the encryption password now. I'm going to post a new topic though as this issue isn't really the same as the original here
Related
Hi There, sorry long post
As many others I have problems with encryption in combination with custom roms. Searched several threads but are stuck now
What I did:
several months ago: Installed various CM Lollipop based rom's, could not get encryption to work.
several moths ago: Backed out installing CM11 (kitkat) and encryption worked fine but cm11 is kinda old now..
So tried the last few days going to Lollipop again:
Wiped phone from stock recovery. Installed a stock ROM for my N9005. Rooted and TWRP 2.8.7 again. Formatted /data so no residues from the previous encryption should be in the /data.
Thought/hoped a Touchwiz based rom would give me better results so I installed the Norma V15 based tom (Note5 port). Installed and works fine without encryption. When trying to encrypt the phone reboots and nothing happens (I still see encrypt phone in the menu's and my company e-mail package still complains my phone is not encrypted).
I'm a bit of a noob in the logcat area but with the liveboot app I saved the boot messages after selecting to encrypt my note 3:
12-27 19:18:46.797 W/Cryptfs ( 286): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
<6>[ 6.581522] max77803_get_vbus_state: VBUS is invalid. CHGIN < CHGIN_UVLO
12-27 19:18:46.797 W/Cryptfs ( 286): Cannot get crypt footer and key
From other pages I found that there should be some room after the /data partition to store the encryption key. I hoped that by installing the stock Rom this would be corrected. Investigated further:
Found this page: http://forum.xda-developers.com/showthread.php?t=2469031&page=2
Uninstalled supersu. After that I could encrypt my phone. It rebooted and the encryption took about three minutes. Looked fine so far!
After encryption the phone rebooted as expected.
Right after prompting to enter the password a pop-up appears "Unfortunately, System UI has stopped". Ticking OK and I get just the background screen and I can't enter my password again! The Android UI never starts, the message keeps coming back.
It seems to me that the start of the UI can't complete because the password is not entered and I can't enter the password! Catch 22!
Any suggestions to proceed?
Is this a encryption problem now or somekind of system UI problem or is this Norma rom related?
(already tried system reset and format /data from TWRP).
Can go back through the stock rom route but end up again with an unencrypted phone (work e-mail needs an encrypted phone).
Thanks for helping!
I am running BPB1 on my s5 and enabled encryption. The phone showed an Android looking character, and then restarted or went black...I noticed for the past 90 minutes the screen was black and the blue LED kept blinking.
I held the Vol Up, Vol Down, power, and home buttons together. It rebooted into trying recovery...then retarted...waited on the Verizon Logo for 5 minutes, then came up with the Setup Wizard.
WTF?
At a loss as to what I should do? Get back into SS and restore a backup?
If you enabled it, the disabled, it probably wiped everything because that's what it's designed to do. If enabling it caused it to factory reset like that, I'd restore a backup if you have one.
Sent from my SM-G900V using XDA-Developers mobile app
I created another thread, but basically if you have a rooted phone you have to open a terminal and do
su
pkill -KILL daemonsu
Prior to enabling encryption. I did this and it worked. I then tried it on the SD card, and it worked. Then, last night, tried to decrypt it..and that is where **** hit the fan. Granted, I didn't run those terminal commands again, because my 'user' in the terminal command appeared to be what I got the first time I ran pkill -KILL, which went from [email protected] to something like [email protected] But basically the phone appeared to have stalled during the decryption process. Once I got back in SS, my files appeared to still be on my SD card, so I tried to recover a backup....what I didn't realize is despite the file list being on the SD card, every single file was corrupt due to the messed up decryption.
So right now, I am very hesistant to do encryption again in case I ever need to decrypt in the future. I guess I don't see any logical reason to decrypt one day, unless I intend to sell the phone...but a factory reset would accomplish that.
This was what happened to me yesterday.
Sorry to digress... My phone was encrypted but not rooted. I have the encryption password. Any chance to get the data back from the phone?
Thanks.
J
poppers162 said:
If you enabled it, the disabled, it probably wiped everything because that's what it's designed to do. If enabling it caused it to factory reset like that, I'd restore a backup if you have one.
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Encrypted 6P with Nougat here. A week after flashing the OTA, unlocking the phone with the initial pin code worked fine, but I started having problems unlocking the phone again by swiping. It just wouldn't be swiped out of the way. It became more and more difficult . Had to reboot all the time in order to get access to the phone, through the pin code unlock.
Initially reflashing the OTA and removing 'trusted locations' for smart unlock seemed to do the trick. 10 hours later the phone went into the same problematic lock screen mode again. This time without any trusted locations.
Installed an alternative lock screen to see if that would work. This required disabling the default lock screen...
After the next boot up, the phone says that the password was correct, but 'decryption was unsuccessful" and the data is corrupt. Will need to perform a factory reset.
Does anyone know a way to avoid resetting the phone? Flashing back to the latest Marshmallow did not help.
Thanks so much.
OK, for anyone else finding themselves in this situation: make sure you get your backups off the phone before it's too late.
After a factory reset to Nougat everything is fine, but all my stuff is gone.
I got a notification for system update. When I rebooted, my tablet started up in TWRP. The update finished (I don't Know if it was successful or not). After I rebooted into system, my usual PIN is not working, do I can't get access. I'm away from home and away from my PC for a couple of weeks, so I'm limited in what I can do.
Does anybody know how to get a PIN to work? Looks like TWRP has been replaced with regular recovery on partition 1, but I have TWRP on partition 2 also. Is there a way to get into TWRP on partition 2 without a desktop PC?
I have the same problem, after the system update yesterday my old pin does not work anymore. What could I do?
So, before you updated, was your tablet rooted? Did the update use TWRP or the stock recovery? Did you have a pin set before the update?
before the update I use PIN and fingerprint reader, device was not rooted.
The update was offered by the device and ran normally.
Now my PIN does not work anymore. I do not have an "ok" button
when entering the PIN and I do not remember if there was one before?
My pin was reset after I updated, but I thought it was because I had replaced the stock recovery with TWRP. I've heard that there's a bug in TWRP that can mess up your pin. Now it looks like the pin problem is happening with stock updates, too. I'm surprised that other people haven't reported it.
If you had TWRP installed and you were able to boot into it, there's a way that you can use the TWRP file manager to delete the pin lock files. In your case, you will probably have to do what I ended up doing. I copied into Huawei eRecover and reset the tablet. That means it was wiped and I had to restore my apps and settings. You could try to get in touch with Huawei support first and see if they have a solution, since it appears that a stock update caused the problem. Please post back again if you find a solution.
Hello,
I am trying to encrypt my Note 4.. In the years I have tried, I only successfully got it encrypted once.
Right now, I have installed Lineage 15.1. Going through settings, my phone reboots twice, and then boots back up normally.
same thing happens if I use vdc cryptfs enablecrypto inplace .......
Earlier I tried vdc cryptfs enablecrypto wipe It just shows the Lineage 'frown' with the circle going across, it did this for hours. Took the battery out, when I booted back up, it did the same thing, just the circle going across.. I restored my backup without wiping it, have lost WiFi now actually, it won't turn on. So I'll be wiping it again tonight
When I was running the Samsung OS, it would only encrypt if I wasn't rooted.. Which was a non-starter. The one time I got it to encrypt, I started from stock, encrypted, ran KingRoot, then the application that swaps KingRoot for SuperSU.. The next time, the application wasn't successful at removing KingRoot..
I was hoping with Lineage I would be able to encrypt the storage again.
What do I have to modify n Lineage to enable Android's 'forceencryption'? I see this flag discussed, but not where to actually set it... Am I missing something obvious?