Well I went through Sanders guide of how to unlock bootloader and flashing recovery I tried it 3 times since each time decryption didn't happened as listed and asked for stupid password on each time of booting into recovery or even for restart, "I would like to know if there is any work around of decrypting Moto g5s plus there r several zips indicates force decryption but only for specific devices I wonder if someone can make one for Moto g5s plus!?"
Thanks in advance
The password TWRP asks for is just to mount your encrypted data. You can press the back button to access TWRP but you just won't have access to files in data. You need to reformat data if you want to have a decrypted data partition (Note: this will wipe you existing data). Go to Wipe and, tap Format Data, and slide to format. Before rebooting system, go back and flash Magisk (or an alternative) so that data doesn't get re-encrypted.
How can change the password?
Related
I have installed twrp 3.0.0-1 recovery and cm-13.0-20160315-NIGHTLY-titan. I made a fresh install. When i try to encrypt the phone, in settings > security > encrypt phone, the phone reboots on android logo. After a few secondos it reboots and don't encrypt.
Hi,
I had the same trouble some times ago, I made an answer here and search for information but I have found nothing.
I found fortuitously that when I formatted the data before the install (and not only erase the partitions) the ROM encrypted without problem. I tried it (problem and solution) with Minimal OS, CM13, and others MM ROMs.
I'm not developer and maybe it's not the information you need but maybe it can help you.
Sorry for the English.
Hi, same issue here.
Moto G 2nd Gen 2014 (XT1068)
Android stock 6.0 (OTA)
TWRP 3.0.0-2
SuperSU 2.62-3 Beta
ROM and SD card as internal memory (approximately 3 GB of data)
First, I have tried to encrypt after rooting. But the device restarted and stayed stuck to the big M Motorola logo. I never see the encryption progress (in percentage).
Then I need to hold POWER for 10 seconds in order to reboot the device.
Second, I have tried a trick from this post : http: //androidforums.com/threads/how-to-encrypt-a-rooted-device.866968/#post-6746987
Connect the device to a PC.
Enable USB Debugging.
Open an elevated command prompt in adb folder, and type : adb shell
Type : su
Accept the root permission request on the device.
$ will turn into #
Type : pkill -KILL daemonsu
Encrypt the device.
But that didn't work...
EDIT : Factory reset > Encrypt > Root
Chainfire said:
It's a known issue. You need to be unrooted for the encryption procedure to work. You can root again after encrypting.
Click to expand...
Click to collapse
JainMayurD said:
Finally, I am able to encrypt/decrypt MOTO G 3rd Gen XT1550. It took lot of trials and finally works. Below are the steps one has to follow to encrypt and decrypt
Encrypt - rooted Host
---------------------------
Factory reset the rooted mobile
Encrypt mobile
Install super su to get root permission
Your phone is rooted and encrypted
To decrypt, again factory reset the mobile. It will be decrypted and install super su to get root access.
Encrypt -Unrooted Host
-----------------------------
On unrooted phone “encrypt phone” was successful
Decrypt was not working on the same phone afterword's
Reset the phone to factory mode, it will be back to decrypted state.
Setting -> backup and factory reset
Thank You!
-Mayur
Click to expand...
Click to collapse
have you tried below steps
Encrypt - rooted Host
---------------------------
Factory reset the rooted mobile
Encrypt mobile
Install super su to get root permission
Your phone is rooted and encrypted
To decrypt, again factory reset the mobile. It will be decrypted and install super su to get root access.
Thank You!
-Mayur
Yes, I quoted your message.
It seems to be the only way to achieve root+encryption.
longerXDA said:
Hi,
I had the same trouble some times ago, I made an answer here and search for information but I have found nothing.
I found fortuitously that when I formatted the data before the install (and not only erase the partitions) the ROM encrypted without problem. I tried it (problem and solution) with Minimal OS, CM13, and others MM ROMs.
I'm not developer and maybe it's not the information you need but maybe it can help you.
Sorry for the English.
Click to expand...
Click to collapse
Don't work for me...
I wiped, formated and nothing.....
Hi,
What I do is format data, reboot to recovery, erase everything but external SD, instal ROM & Gapps, reboot system, put a pin code and when battery is more than 80%, encrypt.
Every time I made it in this order.
You can use the multiROM TWRP, I used it because I read here that it can read encrypted partition. The link is in the multirom thread.
I'm with a titan device, I don't know if it matter...
Good luck!
Hi to all!
It seems custom ROMs are not supports encryption of user data... Why?
After stock MIUI on Xiaomi Redmi 4X I try sevral custom ROMS, and from all of it I cannot encrypt user data partition.
Custom ROMs are (all latest official): Resurrection Remix, AOSP Extended and LineageOS 14.
My steps:
0) flash phone with stock recovery via MiFlash (to restore "innocent state");
1) install latest TWRP (v3.1.1);
2) wipe all partotions except SD card and insstall custom ROM from SD card;
3) new system initial setup without "ask password on boot";
4) go to Settings -> Security -> Encrypt User Data;
Phone performs reboot and data still not encrypted.
All three custom ROMs behave the same at this point.
If perform initial setup with "boot password prompt", user data is whown as encrypted in Security settings, but TWRP still not asks password on booting to recovery mode. And I can unpack backup archive produced by TWRP (it seems not encrypted).
So, my question: if I not produce mistake, it seems custom ROMs are not friendly with data encryption, why? And is it possible to fix it?
p.s.
Also I try to erase data with "fastboot format userdata" and configure phone again. It not helps to solve problem.
Hi. Perhaps anybody can bring some light into this encryption issues?
My situation is a little different:
I installed LineageOS 14.1 from TingyiChen. But did not format /data. So it is still encrypted. I did not try to restore an backup from data within twrp yet. But I have read that there can occure problems?
The official version of twrp (3.2.1.0) is not able to decrypt /data. But there is an inofficial version (3.1.1) that works with encrypted data? Please tell me what's the difference? Is it only the switch "TARGET_HW_DISK_ENCRYPTION "? Why did TingChen remove encryption feature two weeks ago in his github repo (Sorry, I'm not allowed to post links yet)?
Fingerprint unlock is not working after reboot anymore. I have read that this also is because of encrypted data. partition. Please tell me what's the problem here or point me to a thread which covers this topic. I was unable to find one yet.
If I do a backup of my data partition in twrp and format it to disable encryption. Can I then restore this backup or what do I need to do for disabling encryption without loosing my data?
Thank you for your answers.
Regards,
Oliver
olistudent said:
Hi. Perhaps anybody can bring some light into this encryption issues?
My situation is a little different:
I installed LineageOS 14.1 from TingyiChen. But did not format /data. So it is still encrypted. I did not try to restore an backup from data within twrp yet. But I have read that there can occure problems?
The official version of twrp (3.2.1.0) is not able to decrypt /data. But there is an inofficial version (3.1.1) that works with encrypted data? Please tell me what's the difference? Is it only the switch "TARGET_HW_DISK_ENCRYPTION "? Why did TingChen remove encryption feature two weeks ago in his github repo (Sorry, I'm not allowed to post links yet)?
Fingerprint unlock is not working after reboot anymore. I have read that this also is because of encrypted data. partition. Please tell me what's the problem here or point me to a thread which covers this topic. I was unable to find one yet.
If I do a backup of my data partition in twrp and format it to disable encryption. Can I then restore this backup or what do I need to do for disabling encryption without loosing my data?
Thank you for your answers.
Regards,
Oliver
Click to expand...
Click to collapse
Wipe Internal Data & perform Clean flash, you will have to dothis everytine you flash ROM. Some says Custom TWRP (redwolf port) Have solved the issue, but Better wipe Internal everytime you flash a ROM
---------- Post added at 08:10 PM ---------- Previous post was at 08:06 PM ----------
it's very easy for anyone with just a little bit of knowledge to get around any kind of security that TWRP might have. All they have to do is flash one of the other recoveries that's available that doesn't have password protection to get around it. You can Still flash a Custom Recovery by PC without prompting a pass again. And you're Internal is already Encrypted. Stay at MIUI with Unlocked bootloader if you're too much concerned with the security.... But an expert will use test points to Unlock that too...
I am in trouble of loosing all my userdata after following the below process:
1. I was on stable 4.5.1 and not encrypted.
2. flashed blue_spark 8.52 recovery.
3. Reboot to recovery and full wiped (except user data).
4. Flashed OOS beta 18 and Magisk 14.3.
5. Rebooted and waited for 20 min but was still on rebooting process.
6. Force rebooted to recovery and alas!, twrp asking for decrypt password!!!
7. Reboot to system and message appears as 'Encryption Unseccessful'
I am not been able to access any partition including userdata from TWRP (as it's asking password), OOS also not booted as well.
Now I will be grateful if someone have any knowledge to skip TWRP password and provide access to userdata to recovery/copy data (photos/files etc) from the device before format userdata and start over again.
If your data was previously decrypted then disable encryption, format data, install a ROM that does not enforce encryption, then try looking on the Play Store for photo recovery apps.
Note that it will not be possible to recover data from the encrypted part of the device. If you left it running for 20 minutes, the chances are your data is almost entirely gone at this point.
Like stated above, your data is probably destroyed since you interrupted the encryption process.
Have you tried "default_password" as the password in TWRP?
Previously I installed omnirom and set a screen pattern now when I rolled back to oxygen OS 5.0.2 I set a different pattern but secure boot pattern is still the old one I've Used in omnirom, I wanted to install new version of that rom now and when i Did reboot TWRP won't decrypt data with my present pattern.
Can someone help me bypass and decrypt the data, I've my important files in it.
With this bug I've to format my data to use my phone but I want my data, help me out.
Have you tried to decrypt data with another TWRP, like BluSpark or acuicultor?
So, quick explanation. Pie update showed up on my OP3T and I have an unlocked bootloader, TWRP 3.3.0-1 and Magisk 18.1 on OOS 5.0.8 (Oreo). Additionally I had a second user account and a Work Profile on my main account.
After reading on the decryption issues (and against my better judgement), I decided that maybe it could work through System Updates since it detected root and was going to install the full package. Big mistake. Got a "Decryption unsuccessful" and sadness.
I had of course taken a full TWRP backup to be safe.
I'm going to put the detailed explanation below (hidden) because it's quite long.
Now in more details. Along with the TWRP back up, I had an oandbackup -backup- of all apps (main and secondary account, but not work) and manually copied all internal storage files on my PC. After the "Decryption unsuccessful" message, I pressed the "Reset Phone" button (probably a stupid decision) thinking I'm good since I have a backup. Phone rebooted, with TWRP replaced (as expected), and I'm in the new OS. Played around a bit in Pie [added my account, registered a fingerprint and PIN, connected to WiFi and checked a few apps] and then I thought, "ok, time to go back", and then it happened.
I rebooted the device and it asked for password to boot (which was the PIN I added in the OS), and then rebooted again in Fastboot to flash TWRP again in order to restore the backup.
TWRP flashed successfully and I copied over my backup. Restored System, Data and Boot, wiped Dalvik & Cache, rebooted, shows the Oneplus logo, gets stuck for a bit and then goes to Fastboot. Ok...probably messed up somewhere, let's try again. Same thing.
I guess the notion that I had the TWRP backup made me feel safe, because I continued to experiment.
After a full 24hours awake trying to restore my phone to its previous state, I have the following:
Restoring System, Data and Boot results in the device booting and showing the Oneplus logo and then after a few seconds, going to Fastboot.
Restoring EFS, Recovery and/or Cache makes no apparent difference.
Restoring Data and Boot, but System Image instead of System makes the device boot and start a lengthy process (possibly of encrypting the entire Data partition) lasting about 2hours, during which the device becomes hot enough (~45C / ~113F) that holding it for more than a couple of seconds is very uncomfortable. After it finishes the lockscreen has my wallpaper, app notifications (like VPN) show up and the second account is there, however my old PINs for either accounts don't work and the Data partition can no longer be accessed in TWRP
Code:
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
[COLOR="red"]Unable to mount storage[/COLOR]
Successfully decrypted with default password.
Updating partition details...
...done
[COLOR="red"]Unable to mount storage
Failed to mount '/data' (No such file or directory)[/COLOR]
Full SELinux support is present.
[COLOR="Red"]Unable to mount /data/media/TWRP/.twrps[/COLOR]
MTP Enabled
When Data is inaccessible in TWRP, only formatting it can bring it back (empty, of course). And then it needs to be formated to F2FS again as well (Oneplus uses F2FS for the Data partition).
Flashing the Oxygen OS 5.0.8 zip file after restoring System works the same as restoring with System Image.
The closest I've come to restoring my device to how it was before is either:
Restoring System, Data and Boot , in which case booting ends up in Fastboot.
OR
Restoring Data and Boot, and System Image, and then not being able to login (plus, no access to Data from TWRP).
I have literally no idea what else to do. If anyone has any idea or suggestion, it would be greatly appreciated.
I'd rather wait for some suggestions before trying to flash other zip files that deal with encryption, since I never had to do that when I first rooted with Magisk.
------------------------------------------------------------------------------
How the device is supposed to be:
Bootloader unlocked
TWRP Recovery 3.3.0-1
OxygenOS 5.0.8 (Oreo)
Magisk 18.1
Main user account
Secondary user account
Work Profile (with Shelter) on Main user account
What I have available:
Full TWRP backup of all partitions [Data, System, Cache. System Image, EFS, Recovery, Boot]
oandbackup backups of Main & Secondary user accounts (apps and APKs)
Manual file backup of Main user account's Internal Storage
All OxygenOS Oreo zip files that Oneplus was releasing over time
TWRP images (3.2.1-0 and up)
Stock OxygenOS recovery (they used to have it available)
Magisk Installer/Uninstaller/Manager APK
Time on my hands
Sleep deprivation points
Enough will to live