The Stock rom didn't has a section to encrypt device. And when i tried to use other roms like Mokee 71.2/81.0, LineageOS 14.1 by BeYkeRYkt, and RR 5.8.5 by arceoxis, they all failed in a same way. When I press the button to start encrypt, it just reboot into a black screen with a green mascot of the Android, and about 5s later, the device just boot in to system and did nothing.
Actually, I once imperfectly encrypted the device with RR 5.8.5, but it just encrypted the /Data partition. A truly successful encryption should be encrypted more than just /Data, like /System. But now I can't even do this imperfectly encrypt again. I have no idea how to solve this problem.
Thanks.
Related
The topic should be SM-A300H can't encrypt. The other issue I solved.
So this is my issue: Encryption doesn't install correctly. I am using lollipop.
After choosing encrypt my device in settings/security it reboots, and shows the green android symbol, but nothing more happens. It shows the green android character for about 15 seconds, and then it boots as usual without encrypting the system.
I did a wipe with TWRP 3.0.2-1-ashyx because of the encryption problem, I wanted to try out with a fresh install and see if it was possible to encrypt the system but it did not make a difference.
I had rooted the device with Kingroot before the wipe, and kingroot was still installed even after doing the wipe which is odd. I tried uninstalling kingroot after the wipe as well but encrypt still didn't work, same problem.
So if there's a solution to this problem I would be grateful if you can help me.
Additional question: in case I cannot get encryption to work for some yet unknown reason, is there any 3rd party app I can try that will encrypt the entire system? I am not looking to encrypt single files, only full system encryption is good enough.
*deleted*
Flash the stock firmware then boot to recovery and factory reset.
You should then be able to encrypt.
Be forewarned that if you do encrypt you will no longer be able to mount data or storage in twrp.
Hi, ive been wondering why all those roms folks put out are unable to encrypt the /data partition.
Any rom i tried so far is soft rebooting after i invoked the encryption option. No encyption happening at all.
And if i do it manually via adb shell > su # vdc cryptfs enablecrypto wipe password somethingpw
I sort of soft brick the device boot until i whipe the data partion via twrp.
Thereof i am wondering why its broken in the first place and if theres a chance if folk will fix this over time or any 3rd Party Roms will be stuck w/o a chance to encrypt personal data.
Myau said:
Hi, ive been wondering why all those roms folks put out are unable to encrypt the /data partition.
Any rom i tried so far is soft rebooting after i invoked the encryption option. No encyption happening at all.
And if i do it manually via adb shell > su # vdc cryptfs enablecrypto wipe password somethingpw
I sort of soft brick the device boot until i whipe the data partion via twrp.
Thereof i am wondering why its broken in the first place and if theres a chance if folk will fix this over time or any 3rd Party Roms will be stuck w/o a chance to encrypt personal data.
Click to expand...
Click to collapse
I was facing issues with my LOS 15.1, afaik unencrypted. Then I flash stock Oreo Feb using Mi Flash tool, with option 'clean all and lock'. Then I root it with magisk and flash LOS 15.1. The next thing I know, my phone is encrypted
kopitalk said:
I was facing issues with my LOS 15.1, afaik unencrypted. Then I flash stock Oreo Feb using Mi Flash tool, with option 'clean all and lock'. Then I root it with magisk and flash LOS 15.1. The next thing I know, my phone is encrypted
Click to expand...
Click to collapse
Did you dirty flash or whipe the installed OS?
Myau said:
Did you dirty flash or whipe the installed OS?
Click to expand...
Click to collapse
Clean install, i.e. wipe all.
kopitalk said:
Clean install, i.e. wipe all.
Click to expand...
Click to collapse
Thank You, for confirming that Encryption works, i was almost at the verge of returning the phone.
Got it to work now.
....
The tldr of all i tested and messed around with is:
If you whipe Data trough twrp, with the special dialog where you have to type in YES. which folk reccomend to use to remove encryption,
will mean you brick the encryption and requires a re-flashing of the stock rom.
Secondly if you only go into advanced whipe, Art, System and data and then install a rom, it should say 'decrypted with default password'
Which is a dead give away that encryption might going to work just fine, rebooted into bootloader w/o into system, installed gapps pico, (eeh) and magisk, which also mentioned something about encryption as the log ran trough. Then rebooted into system, and now it says encrypted. And i can set up a boot pin/password before it fully boots. GREAT!
Soo.... If it says decrypted and won't encrypt, you have to flash stock, check its encrypted. Then install costum rom without removing encryption.
Once you removed it, its back to stock rom for new a /data setup/encryption.
Hi folks,
I need some help. I have had my X820 I ordered from bangood for about a month now. I have tried a variety of ROMs on this device, and twrp-3.2.1-0-x2.img. This morning I tried to give the latest lineageOS a try. I did the typical wipes, and flashed lineageOS & gapps. After reboot google play started to throw all types of errors.
I booted back into TWRP, and this time it would only mount in read only. I tried the trick to change the /data partition fron ext2 back to ext4, did wipes again, installed ROM + Gapp, reboot but still have crashing playstore and google background processes.
I went from an already installed AICP to LOS. I did do a complete TWRP backup of AICP beforehand. The weird thing is that if I do a complete wipe again from TWRP, and do a fresh install of Pixel Experience [AOSP] all works normally. And after I did another wipe from TWRP after Pixel Experience, and restored my AICP backup all is working fine now both in TWRP & AICP. Has anyone had something simular happen like this before?
You have to install the latest unofficial TWRP build in order to use see your /data partition with the latest LineageOS installed. It's indicated on the thread's FAQ.
Hi, sorry for my bad englich,
i have install LineageOS 15.1 and GAPPS (it is a lidle bit tricki, but ist works after that i have no pin protection to phone und eable encrytion filesystem, i was not ask to pin/key for that, encrytion was finished, reboot of OS work fine. Then i secure the phone with a pin, all works fine, reboot, unlock...
Bevore i update to next new lineageos OTA version i would make a backup, but twrp can't mount filesystem and ask for pin/key to mount. But my pin don't work???
What key use encrytion without display lock pin on default???
Hi,
TWRP can't decrypt the data partition when it has been encrypted with Oreo.
If you want have an encrypted data partition, you will have to go back to LOS 14.1 (format the data partition before!), then enable the encryption there.
Afterwards you can upgrade to LOS15.1 again. Important: Only perform a "Wipe" of the data partition, do not format it again (upon formatting the encryption gets lost).
Alternatively you can wait until TWRP will support Oreo encryption, but no one can tell you how long this will take.
thanks for info.
this is a not a bug, this is a function
I hope this will implemented, although the phone is getting old.
I will probably make your way over 14.1 for testing.
So I am trying to upgrade my version of LineageOS from 14 to 15.1. I was having problems because my phone didn't have the '/vendor' partition. I heard that re-installing OxygenOS will mount '/vendor' so that's what I tried to do. However, I was still getting the error about not having '/vendor' mounted, so I tried using a version of TWRP that removed the check for '/vendor'. Unfortunately, I still could not install OOS. Then, I tried to just flash updated firmware for my phone, which should install the '/vendor' partition, but now I am stuck on the Lineage loading screen.
When I boot back into recovery, TWRP does not ask me for my phone password, and all the files are encrypted (or hashed, or whatever). This could be a problem for my phone loading?
walker_flocker said:
So I am trying to upgrade my version of LineageOS from 14 to 15.1. I was having problems because my phone didn't have the '/vendor' partition. I heard that re-installing OxygenOS will mount '/vendor' so that's what I tried to do. However, I was still getting the error about not having '/vendor' mounted, so I tried using a version of TWRP that removed the check for '/vendor'. Unfortunately, I still could not install OOS. Then, I tried to just flash updated firmware for my phone, which should install the '/vendor' partition, but now I am stuck on the Lineage loading screen.
When I boot back into recovery, TWRP does not ask me for my phone password, and all the files are encrypted (or hashed, or whatever). This could be a problem for my phone loading?
Click to expand...
Click to collapse
Have you used latest blu spark or codeworkx recovery with vendor partition support? Also mounting the created vendor partition within twrp might be necessary after flashing stock oos and proceed further.