Installed latest TWRP (3.1.1.0)
Couldn't successfully decrypt storage, but was able to bypass by cancelling.
Pushed latest SuperSU (SuperSU-v2.82-201705271822.zip) through adb to /sdcard. Image seems to flash successfully. However it is now bootlooping back to TWRP. Tries to boot once, fails, will restart and then boot back to TWRP.
Now this is all probably due to the inability to properly wipe the dalvik cache. It reports it fails when wiping, the hunch I got is again encryption.
Any suggestions?
If you have not set a password, the default TWRP password should be: default_password
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?
First there are shortcuts for this, but I wanted to be sure I covered every step and where one is at each point, since it can be helpful for recovery or simply to see where one is. There are of course other ways but I just went through on a GM1917 and verified each of these steps, so that others do not need to piece together multiple threads. I'm assuming here we want to start from scratch, never a bad idea if you are willing to lose data, or else you have no choice and need to start from scratch.
Posts used:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I'm going to disable Encryption as well, because when written TWRP was not decrypting it and also because I find it a pain and simply put I do not need it on my phone, but those steps are optionally shown below, as well as root.
Next I'm doing this using files for the GM1917 (US/Internaltional), but you can replace both the fastboot version and the OTA for your device and the current version.
Before you begin: I'm assuming an unlocked boot loader
Be warned the steps below result in total loss of all DATA on the phone
Time: This takes about 45 minutes to an hour to complete.
I'm assuming you can get to fastboot mode, beyond that your phone can be seriously messed up, but as we are starting from scratch it should be ok.
Boot into Fastboot mode: (Vol- & Vol+ & power)
Use: 9.5.3-GM21AA-OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_aa37bad-FASTBOOT to restore a prestine copy of 9.5.3 to slot A (only writes slot A)
Force it to power off on reboot (Vol+ & Power)
Reboot to fastboot mode (vol- & vol+ & power)
Now you should check which slot are you using with this command "fastboot getvar current-slot"
Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
Now we have TWRP on Slot B and 9.5.3 on Slot A we are on Slot B
If asked to decrypt, if not skip this step: Format Data, Then Internal Storage, Data and cache
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
Reboot -> Select Slot A
Reboot Select Recovery
We now have TWRP on slots A and B. 9.5.3 on Slot A and 9.5.4 on Slot B
Back in TWRP we are now on Slot A:
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
We now have TWRP on slots A and B. 9.5.4 Slots A and B
At this point you can boot up 9.5.4 Stock from Slot A by selecting Reboot System or we can root / disable encryption
To disable encryption (suggested if you do not care as it makes TWRP easier):
Optional: block the ROM from encrypting storage as we can not currently decrypt.
upload the zip: adb push Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip /cache
- Install -> /cache -> Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Note: this only affects the current slot (A in this case) which is fine
Reboot->System
At this point you have 9.5.4 Stock without Encryption on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B.
Complete inital setup (I do the minimal at this point)
- Set a password, to verify if Dm-Verity_ForceEncrypt is working or not
Enable Developers Options
Enable Advanced Reboot in Developers Options
Note: My suggestion is to now power off and restart to ensure you have Wifi, as this is picky for some reason, and it is best to be sure.
Power -> Off
Power back on and verify that Wifi is still working, it should be.
If you want root:
Power -> Recovery
Upload Magisk: adb push Magisk-v19.2.zip /cache
- Install -> /cache -> Magisk-v19.2.zip
Wipe Dalvik
Reboot System
Finally: Verify that Safenet is passing in Magisk, it should be
You have 9.5.4 Stock with Encryption and Root on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B. I hope having this in one place can help others, as I've tried to lay out exactly what I did each step of the way.
Parting suggestion: Maybe a good time to create a backup, one with EFS and Modem to just to be safe!
ERIC
I would love to leave this device permanently decrypted as well for convenience, but I do want lockscreen security enabled.
On the 6T, if you flash the dm_verity disabler zip, the drawback is that you couldn't enable lockscreen security. You could set a PIN, but the system would never recognize it, even if it was entered correctly. So once your screen went off, you had to either format internal storage from recovery to boot into a no-lockscreen system, or use file manager in TWRP to manually delete the files to disable lockscreen.
I'm thinking that 7Pro is the same way. Can someone confirm?
Thanks
reaper000 said:
I would love to leave this device permanently decrypted as well for convenience, but I do want lockscreen security enabled.
On the 6T, if you flash the dm_verity disabler zip, the drawback is that you couldn't enable lockscreen security. You could set a PIN, but the system would never recognize it, even if it was entered correctly. So once your screen went off, you had to either format internal storage from recovery to boot into a no-lockscreen system, or use file manager in TWRP to manually delete the files to disable lockscreen.
I'm thinking that 7Pro is the same way. Can someone confirm?
Thanks
Click to expand...
Click to collapse
I'm using A pattern, and fingerprint without issues. on 9.5.3 and 9.5.4.
ERIC
trying to use this guide and getting fastboot: unrecognised option `--set-active=b'
reaper000 said:
I would love to leave this device permanently decrypted as well for convenience, but I do want lockscreen security enabled.
On the 6T, if you flash the dm_verity disabler zip, the drawback is that you couldn't enable lockscreen security. You could set a PIN, but the system would never recognize it, even if it was entered correctly. So once your screen went off, you had to either format internal storage from recovery to boot into a no-lockscreen system, or use file manager in TWRP to manually delete the files to disable lockscreen.
I'm thinking that 7Pro is the same way. Can someone confirm?
Thanks
Click to expand...
Click to collapse
I saw o xXx Telegram that you can decrypt 7 Pro and also have lock screen security...
I too can confirm working lockscreen while remaining decrypted. Much appreciation to the OP!
Though I took a few shortcuts and used an otg USB drive, it still worked. Here's what I did:
(keep in mind that I am on 9.5.3, already had an unlocked bootloader, and had already used a patched boot.img that I injected via fastboot to achieve root)
To decrypt:
- downloaded dm_verity disable zip, magisk 19.2, and TWRP installer zip, and copied them to USB drive. Also, backup internal storage.
- used Magisk manager app to flash TWRP installer and Magisk 19.2
- reboot to recovery
- formatted internal storage (type yes, completely formatted the data partition and lost all media, photos, downloads, etc)
- twrp factory reset
- flashed dm-verity disabler zip and magisk 19.2 from otg USB drive
- reboot to system
Complete initial setup, repopulate internal storage with mefia (mp3, downloads, etc) from backup.
To upgrade to 9.5.4 once decrypted:
- download full 9.5.4 zip
- reboot to TWRP
- flash 9.5.4 zip and TWRP installer
- reboot to TWRP
- flash dm_verity disable zip and Magisk
- wipe dalvik
- reboot to system
Life is so much better decrypted.
earthbend said:
trying to use this guide and getting fastboot: unrecognised option `--set-active=b'
Click to expand...
Click to collapse
Need a newer version of fastboot this that case.
reaper000 said:
I too can confirm working lockscreen while remaining decrypted. Much appreciation to the OP!
Though I took a few shortcuts and used an otg USB drive, it still worked. Here's what I did:
(keep in mind that I am on 9.5.3, already had an unlocked bootloader, and had already used a patched boot.img that I injected via fastboot to achieve root)
To decrypt:
- downloaded dm_verity disable zip, magisk 19.2, and TWRP installer zip, and copied them to USB drive. Also, backup internal storage.
- used Magisk manager app to flash TWRP installer and Magisk 19.2
- reboot to recovery
- formatted internal storage (type yes, completely formatted the data partition and lost all media, photos, downloads, etc)
- twrp factory reset
- flashed dm-verity disabler zip and magisk 19.2 from otg USB drive
- reboot to system
Complete initial setup, repopulate internal storage with mefia (mp3, downloads, etc) from backup.
To upgrade to 9.5.4 once decrypted:
- download full 9.5.4 zip
- reboot to TWRP
- flash 9.5.4 zip and TWRP installer
- reboot to TWRP
- flash dm_verity disable zip and Magisk
- wipe dalvik
- reboot to system
Life is so much better decrypted.
Click to expand...
Click to collapse
I have tried your steps, but failed to decrypt the data partition.
I also tried different ways to flash:
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip
* Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
but all failed.
My 1+7 Pro is GM1910.
Decryption is quite easy on my OnePlus 5T. Could you help me with some hint?
tinyfish said:
I have tried your steps, but failed to decrypt the data partition.
I also tried different ways to flash:
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip
* Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
but all failed.
My 1+7 Pro is GM1910.
Decryption is quite easy on my OnePlus 5T. Could you help me with some hint?
Click to expand...
Click to collapse
I suppose "decrypt" is actually a misnomer.
The more accurate description is "disable forced encryption on initial and subsequent boots".
You aren't actually decrypting your current data partition, you're preventing a BLANK data partition from being encrypted upon initial boot of a virgin operating system.
The reason I'm saying all this is the most common reason for the no_verity disable zip to fail is because users have not done a factory reset AND not formatted their internal storage (you have to type the word "yes" or you haven't done it) before flashing no_verity and magisk.
Also ensure your no_verity disabler zip wasn't a bad download (md5 checksum)
If this doesn't work, then you're left with what I've termed a "scorched earth format" (you select everything except usb drive to wipe in advanced wipe, and then format internal storage with a typed yes). You then install FROM A USB DRIVE the latest full ota zip + twrp on both slots with the appropriate twrp reboots, then magisk + no_verity, twrp reboot then magisk yet again and finally system reboot.
reaper000 said:
I suppose "decrypt" is actually a misnomer.
The more accurate description is "disable forced encryption on initial and subsequent boots".
You aren't actually decrypting your current data partition, you're preventing a BLANK data partition from being encrypted upon initial boot of a virgin operating system.
The reason I'm saying all this is the most common reason for the no_verity disable zip to fail is because users have not done a factory reset AND not formatted their internal storage (you have to type the word "yes" or you haven't done it) before flashing no_verity and magisk.
Also ensure your no_verity disabler zip wasn't a bad download (md5 checksum)
If this doesn't work, then you're left with what I've termed a "scorched earth format" (you select everything except usb drive to wipe in advanced wipe, and then format internal storage with a typed yes). You then install FROM A USB DRIVE the latest full ota zip + twrp on both slots with the appropriate twrp reboots, then magisk + no_verity, twrp reboot then magisk yet again and finally system reboot.
Click to expand...
Click to collapse
I have formatted the data partition, and the Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip is valid.
Anyway I succeeded after upgrade to latest H2OS 9.5.5, with the same steps.
Thanks for your help.
Time-Saver!
QUOTE=egandt;79606005]First there are shortcuts for this, but I wanted to be sure I covered every step and where one is at each point, since it can be helpful for recovery or simply to see where one is. There are of course other ways but I just went through on a GM1917 and verified each of these steps, so that others do not need to piece together multiple threads. I'm assuming here we want to start from scratch, never a bad idea if you are willing to lose data, or else you have no choice and need to start from scratch.
Posts used:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I'm going to disable Encryption as well, because when written TWRP was not decrypting it and also because I find it a pain and simply put I do not need it on my phone, but those steps are optionally shown below, as well as root.
Next I'm doing this using files for the GM1917 (US/Internaltional), but you can replace both the fastboot version and the OTA for your device and the current version.
Before you begin: I'm assuming an unlocked boot loader
Be warned the steps below result in total loss of all DATA on the phone
Time: This takes about 45 minutes to an hour to complete.
I'm assuming you can get to fastboot mode, beyond that your phone can be seriously messed up, but as we are starting from scratch it should be ok.
Boot into Fastboot mode: (Vol- & Vol+ & power)
Use: 9.5.3-GM21AA-OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_aa37bad-FASTBOOT to restore a prestine copy of 9.5.3 to slot A (only writes slot A)
Force it to power off on reboot (Vol+ & Power)
Reboot to fastboot mode (vol- & vol+ & power)
Now you should check which slot are you using with this command "fastboot getvar current-slot"
Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
Now we have TWRP on Slot B and 9.5.3 on Slot A we are on Slot B
If asked to decrypt, if not skip this step: Format Data, Then Internal Storage, Data and cache
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
Reboot -> Select Slot A
Reboot Select Recovery
We now have TWRP on slots A and B. 9.5.3 on Slot A and 9.5.4 on Slot B
Back in TWRP we are now on Slot A:
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
We now have TWRP on slots A and B. 9.5.4 Slots A and B
At this point you can boot up 9.5.4 Stock from Slot A by selecting Reboot System or we can root / disable encryption
To disable encryption (suggested if you do not care as it makes TWRP easier):
Optional: block the ROM from encrypting storage as we can not currently decrypt.
upload the zip: adb push Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip /cache
- Install -> /cache -> Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Note: this only affects the current slot (A in this case) which is fine
Reboot->System
At this point you have 9.5.4 Stock without Encryption on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B.
Complete inital setup (I do the minimal at this point)
- Set a password, to verify if Dm-Verity_ForceEncrypt is working or not
Enable Developers Options
Enable Advanced Reboot in Developers Options
Note: My suggestion is to now power off and restart to ensure you have Wifi, as this is picky for some reason, and it is best to be sure.
Power -> Off
Power back on and verify that Wifi is still working, it should be.
If you want root:
Power -> Recovery
Upload Magisk: adb push Magisk-v19.2.zip /cache
- Install -> /cache -> Magisk-v19.2.zip
Wipe Dalvik
Reboot System
Finally: Verify that Safenet is passing in Magisk, it should be
You have 9.5.4 Stock with Encryption and Root on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B. I hope having this in one place can help others, as I've tried to lay out exactly what I did each step of the way.
Parting suggestion: Maybe a good time to create a backup, one with EFS and Modem to just to be safe!
ERIC[/QUOTE]
Hello @tinyfish
Just dropping a note to thank you for the procedure. I wanted to achieve the same thing and I have been doing so through my own trial-and-error (and I'm actually documenting my steps as I go with the same intention of sharing to the community).
Apparently someone already beat me to it and I even used this written procedure. It worked for me. Although there are a few "differences" in the way I did it:
1. Instead of OOS version 9.5.4 I used OOS version 9.5.13 which is the latest Android Pie for the OnePlus 7 Pro as of this writing.
2. I used the latest version of the "DM-Verity and Forced Encrypt Disabler" zip which is version 10.20.2019 as of this writing. The older version didn't work and resulted to "Settings" app force-closing and thereby preventing me from booting. I didn't investigate but I assume that the reason is because the 05.21.2019 version is "older" than the OOS version 9.5.13 that I was flashing. I could be wrong. But it is important that I write it here so that it is made known and investigated by someone who has the time/knowledge/energy for it.
There are certain important apps that I use that couldn't run properly on Android 10, so I had to revert to Android 9 (Pie).
Thank you once again!
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
Here are the details of my issue,
When trying to encrypt through "Settings > Biometrics & Security > Encrypt device"
It shows an "encrypting" screen
Keeps working on encryption for 1-2 minutes
then Reboots
When I check status, it's not encrypted
Please help.
Also, other than the encryption issue, phone is functioning normally.
Note 8 Model: SM-N950F/DS
Android Ver: 9
Build: PPR1.180610.011.N950FXXUFDUE4
Kernel: 4.4.111-21737876
Knox Ver: Knox 3.2.1, API level: 27, TIMA 3.3.0
Rooting method: (Magisk, Twrp, Force encrypt disabler, KG/RMM lock remover)
twrp: twrp-3.5.2_9-0-greatlte.img
I attached the files used during rooting process.
As a reference, I am also adding the rooting process I followed.
----------------------------------------------------------------
Enable OEM unlocking from dev menu
Shutdown
Reboot into bootloader mode (hold Bixby + VolDown, then Power, all concurrently)
When bootloader appears, press Vol up to enable flashing mode
Run Odin, and connect phone, wait until connected com port is displayed
On Odin, select twrp image in “AP” field
On Odin, from options, unselect “Auto Reboot”
Start flashing. Wait until flash is “Passed”
Disconnect phone and close odin.
Reboot the phone into recovery mode (Warning: Failure to do so may trigger KG/RMM lock, which will lock down the phone for 7 days. It’s a safeguard against phone theft)
Shutdown from flashing mode (hold Bixby + VolDown, then Power, all concurrently)
As soon as the screen goes dark, release VolDown, while still holding Bixby and Power button, and at this moment, pres VolUp.
This should boot phone into TWRP recovery mode
Format /data partition (Format > Format Data)
Reboot > Recovery
Once recovery is complete, connect phone to computer
From Mount, ensure that MTP is enabled, and data partition is mounted
Data partition should be available on computer
In data partition, add
KG/RMM lock remover
Magisk
Force encrypt disabler
From TWRP, flash files in provided order
Phone is rooted
----------------------------------------------------------------
jeredralph said:
Here are the details of my issue,
When trying to encrypt through "Settings > Biometrics & Security > Encrypt device"
It shows an "encrypting" screen
Keeps working on encryption for 1-2 minutes
then Reboots
When I check status, it's not encrypted
Click to expand...
Click to collapse
I think the DM-Verity zip that you flashed has got something to do with re-encrypting your device. The zip is supposed to prevent re-encryption every time you boot your device.
Also TWRP won't work properly if you device is encrypted.
If you really want a rooted device with encryption then use the patch method with magisk.
Finally got it working! Required some brute force and two days of my time.
Thanks @spawnlives for the hint about DM-Verity zip. But, only removing the zip was not enough.
Here's how things worked out so far.
Trial series 1
Flash stock sim inserted (BL > AP > CP > CSC)
Flash TWRP
Format /data
Flash zips (KG/RMM lock remover, Magisk)
Boot system
Issue: Encryption doesn't work. Same as before (system works on encryption for a bit, reboots, not encrypted)
Additional issue: Region code got corrupted (got //BRI, instead of my region code XXV/XXV/BRI). Samsung refused to check for update due to invalid code (don't remember the specifics).
Magisk status (preserve DM Verity: off, preserve Force Encrypt: on)
Trial series 2
Flash stock with sim inserted (BL > AP > CP > CSC)
Boot system
1 issue fixed: region code is now valid
Flash TWRP
Flash zips from microsd (KG/RMM lock remover, Magisk)
Format /data and /preload
Boot system
Initialize (greetings > connect wifi > choose security scheme (pattern), choose secure startup)
Magisk status (preserve DM Verity: off, preserve Force Encrypt: on)
Notes
I noticed something strange. The Encrypt device option is now gone, and instead there is Secure startup, while I am not sure about the specific differences between these two options, the device appears to be encrypted on boot. Cause, it's asking for pattern on every startup (before activating cellular and other core features). Also, TWRP can not decrypt /data partition anymore.
Trial series 2 resolved my issue of having a rooted Android while still having the /data partition encrypted.
I guess, at least now my data is secured against device theft or loss, considering, thief has to erase the /data partition to use the device again. Please correct me if I am wrong.
Issues yet to resolve
On my OnePlus 3t, TWRP has a cool feature enabled, that can decrypt /data partition using pattern. I am not sure why TWRP on Note 8 doesn't prompt pattern for decrypting /data partition.
I encountered an error, "unable to find crypto footer". Could it be the reason? How could it be mitigated?
Data partition is encrypted. I can flash zip from microsd. But, didn't yet have the chance to check whether flashing another zip will trigger integrity violation during secure startup check (the step where I enter secure startup pattern).
Please help me with these issues.