Hello, I have an problem with encryption stuck at "time remaining 00:00" forever.
I have tried to encrypt again several times and it won't complete.
A forced reboot results in a corrupted filesystem.
Is this a known issue?
I have the exact same issue with OnePlus 5. I installed LineageOS, disabled the forced encryption (flashed no-verity-op5.zip and formatted data) and then chose encryption from settings. The phone booted and started encrypting. It has now been in state "Encrypting. Wait while your phone is being encrypted. Time remaining: 00:00" for five hours. I already stopped it once after waiting for more than one hour and it resulted in corrupted filesystem. I'm not expecting this encryption phase to finish at all.
Related
So I have been having issues with random hangs during boot and subsequent filesystem corruption. I say filesystem corruption because TWRP prompts me for a password because it thinks the drive is encrypted and certain partitions/directories fail to be restored to with the dalvik cache failing to be wiped seeming to be a consistent.
So in a nutshell rebooting my phone without first going into TWRP and performing a cache/dalvik wipe inevitably causes filesystem corruption. I discovered this pattern last night when flashing a zip, booting the phone and setting things up, rebooting directly into recovery and making a backup and doing nothing else, rebooting, noticing the phone hang after a few minutes of the "Samsung Galaxy S4" splash screen, then rebooting in recovery being prompted for a password, then formatting data, then restoring the backup I had just made, and having the phone bootup successfully after that. Since then a bit of trial and error has only demonstrated to me that without wiping the cache/dalvik some filesystem gets corrupted rendering the phone unable to boot.
So I am curious if anybody has any idea what might cause this except maybe a bad internal SD card. I am pretty tech savvy but I do not have nearly as much experience troubleshooting these phones as many of you guys.
I have tried everything short of restoring to stock which I am going to attempt later if nobody is able to shed some light on this issue.
Thank you.
Try re-loading recovery via Odin.
Check out this thread close to your issue
I am attempting this now. I did not realize that you meant stock recovery when I first wrote this post.
czahrien said:
So I have been having issues with random hangs during boot and subsequent filesystem corruption. I say filesystem corruption because TWRP prompts me for a password because it thinks the drive is encrypted and certain partitions/directories fail to be restored to with the dalvik cache failing to be wiped seeming to be a consistent.
So in a nutshell rebooting my phone without first going into TWRP and performing a cache/dalvik wipe inevitably causes filesystem corruption. I discovered this pattern last night when flashing a zip, booting the phone and setting things up, rebooting directly into recovery and making a backup and doing nothing else, rebooting, noticing the phone hang after a few minutes of the "Samsung Galaxy S4" splash screen, then rebooting in recovery being prompted for a password, then formatting data, then restoring the backup I had just made, and having the phone bootup successfully after that. Since then a bit of trial and error has only demonstrated to me that without wiping the cache/dalvik some filesystem gets corrupted rendering the phone unable to boot.
So I am curious if anybody has any idea what might cause this except maybe a bad internal SD card. I am pretty tech savvy but I do not have nearly as much experience troubleshooting these phones as many of you guys.
I have tried everything short of restoring to stock which I am going to attempt later if nobody is able to shed some light on this issue.
Thank you.
Click to expand...
Click to collapse
I'm having this same issue on my gf's Kindle Fire I w/CM10.2, but without the prompt for password. So annoying! Did you ever fix it? - http://forum.xda-developers.com/showthread.php?t=2563695
About a year ago, my Nexus 7 (2012 wifi) started occasionally locking up, then (after a couple of minutes) rebooting and getting stuck on the boot animation. This would happen once every month or two. The only fix was to disconnect the battery, then reboot to recovery and do a restore. Sometimes I only needed to restore /system; sometimes I had to restore /data too. This continued after I moved from Kitkat to Lollipop.
The other night it happened again, and this time things are worse. I boot into TWRP and try to restore, but it only finds /system. It can't see /data or /cache.
I'd love to solve the underlying problem, but for now, any ideas on how to resurrect /data?
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 have a 6P running the 1st beta of 7.1.2 and in attempt to update the next one I flashed the update again and I forgot to flash a custom kernel after it. My data partition had about 70gb worth of files and it was previously unencrypted, my phone has been booting for the past 15 minutes or so and it's really hot, does that mean that it's currently encrypting my data and that it'll be done eventually or is my data screwed? (This happened to me once before and I rebooted to recovery thinking it was bootlooping and it said that my data is corrupted because I interrupted the encryption, so I'm afraid that'l happen again again all because of the encryption that I don't want and I never asked for)
Edit: after 25 minutes it finished booting and all my data is still alive but encrypted. It was worth waiting and not corrupting my data.
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?