Related
This Guide will work on S7 and S7 Edge Variants, probably also on other Samsung Phones. It doesn't matter if you have xposed and/or supersu installed
I did lately try to encrypt my device after installing my rom. So I tried to search on xda but I couldn't find anything useful until now.
After quit some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Attention, TWRP can't read /data partition after this guide, that's because twrp doesn't support samsungs encryption at all
Pre requests:
- A working pc with adb installed
- Enough battery (at least 80%)
- Charger in your near field
- Working internet connection
Steps:
1. Go to SuperSU application on your device
2. Head over to the settings Tab
3. Scroll down and hit Full unroot
4. Click continue, when it asks you to install stock boot.img say NO, also NO on restoring stock recovery
5. SuperSU app should disappear
6. Make one full reboot
7. Head over to settings, lock screen and security, set a password
8. Plug in your charger and start encryption
9. Wait until your phone has fully encrypted (this can take quit some time)
10. After your device has successfully encrypted, we want to gain root access again
11. Boot into TWRP recovery
12. You now need a pc with working adb connection
13. Click adb sideload on twrp
14. Download latest super su to your PC, you can get that from here: Beta Thread
15. Open a terminal on your PC
16. Put the supersu.zip in the same direction as your terminal is opened (example: user/home)
17. Type into terminal: adb sideload *supersu_name*.zip
18. Reboot your phone and you have a working, encrypted phone with root installed!
If this guide helped you, please share it and hit thanks as well! :good:
Tkkg1994 said:
After quite some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Click to expand...
Click to collapse
:highfive:
Reverting/decrypting data would require a data wipe from TWRP, correct?
lost_ said:
:highfive:
Reverting/decrypting data would require a data wipe from TWRP, correct?
Click to expand...
Click to collapse
Exactly, with twrp or stock recovery
With TWRP not being abled to access /data partition, would it still be possible to make a complete nandroid? Second, what about updates of the custom ROM? Isn't the complete phone encrypted after the process, like /system and external sd as well?
Swyped via Tapatalk
what about systemless posed. would it work with the encryption, or it must be uninstalled.
I would like to try and encrypt my phone but I have systemless xposed installed and I would like to keep it. any information on that regards ?
Unfortunately it didnt worked for me. After i starting the encryption the phone does make a usual restart and i dont see any encryption process.
It just reboots. I am running cfw "S7 extreme debloated".
Any ideas?
btw: how safe is a rooted and encrypted phone, if you can replace any time the custom recovery?
are the encrypted partitions /data and /sdcard really safe?
Thanks...
@Tkkg1994 : Hi, I tried this method while using your Superman ROM, but unfortunatly it didn't work for me. After un-root the encryption application behaved as before: It started, saying "Encrypting...", but after some minutes it just rebooted with doing anything. So the device is still not encrypted. I read somewhere else, that in order to get the encryption working, the stock boot.img needs to be flashed. But that instruction have been for a different device, I guess dealing with a standard android encryption (as far as I now, Samsung uses a different one).
I'm just wondering, what would happen when I choose 'Yes' for replacing boot.img in step 4?
bruzzy said:
@Tkkg1994 : Hi, I tried this method while using your Superman ROM, but unfortunatly it didn't work for me. After un-root the encryption application behaved as before: It started, saying "Encrypting...", but after some minutes it just rebooted with doing anything. So the device is still not encrypted. I read somewhere else, that in order to get the encryption working, the stock boot.img needs to be flashed. But that instruction have been for a different device, I guess dealing with a standard android encryption (as far as I now, Samsung uses a different one).
I'm just wondering, what would happen when I choose 'Yes' for replacing boot.img in step 4?
Click to expand...
Click to collapse
That step 4 actually means you should restore your boot.img.
I did it exactly this way and it worked back then when I tested it. Many things have changed since then. So it may needs some adaptions
Sent from my Hydra powered SM-N930F
OK, I tried the other option as well (i. e. saying 'yes' on the question about testoring the boot.img). What about the kernel, do you know which one you used at that time? I'm currently on the Superstock Kernel. So curious, whether this might have any effect as well...
Sent from my SM-G930F using XDA-Developers mobile app
@Tkkg1994: Sorry for pushing, but do you remember, which kernel you've used? And can you also tell me, what exactly is the difference between the Stock and the Superstock kernel in your Superman ROM? Thanks!
bruzzy said:
@Tkkg1994: Sorry for pushing, but do you remember, which kernel you've used? And can you also tell me, what exactly is the difference between the Stock and the Superstock kernel in your Superman ROM? Thanks!
Click to expand...
Click to collapse
Back then it was stock.
Stock is signed properly by samsung and can be used with trusted UI on while custom kernels have to disable real time kernel protection to even boot the phone
tefole said:
Unfortunately it didnt worked for me. After i starting the encryption the phone does make a usual restart and i dont see any encryption process.
It just reboots. I am running cfw "S7 extreme debloated".
Any ideas?
btw: how safe is a rooted and encrypted phone, if you can replace any time the custom recovery?
are the encrypted partitions /data and /sdcard really safe?
Thanks...
Click to expand...
Click to collapse
I managed to encrypt by choosing full unroot in supersu app (say no to image restore questions).
Sadly, with a bootloader open, encryption will be as good as a password used. It's only entered once upon boot if you use fingerprints.
After encrypting root can be installed by flashing the zip again from sdcard or adb sideload.
Does not work for me. After I sideload SuperSU the phone does boot but my password is not recognised anymore.
hav0c said:
Does not work for me. After I sideload SuperSU the phone does boot but my password is not recognised anymore.
Click to expand...
Click to collapse
Hi hav0c, Which version did you upload? I used this: CF-Auto-Root-herolte-heroltexx-smg930f.zip.
Hi,
Does anyone have experience encrypting s7 nougat superstock rom? Wondering if it is the same. Because nougat has file-based encryption.
gnowak84 said:
Hi hav0c, Which version did you upload? I used this: CF-Auto-Root-herolte-heroltexx-smg930f.zip.
Click to expand...
Click to collapse
I have used https://download.chainfire.eu/supersu
So this doesn't work if we are using a non-stock kernel?
Tkkg1994 said:
Back then it was stock.
Stock is signed properly by samsung and can be used with trusted UI on while custom kernels have to disable real time kernel protection to even boot the phone
Click to expand...
Click to collapse
Hi Tkkg1994,
Wanted to know if you have any tip on the encrypt? Your work is really great and thanks for that but due to work i need to get the phone encrypt.
So wanted to know if you can help out as i dont want to go on stock firmware
Thank you
I tried following the guide using SuperStock 2.6, but after encryption finishes I get "Verification failed"
I have the same fault, any idea´s to fix same.
Hi, I just got an LG G6 and ran through the process of rooting and unlocking my bootloader installing TWRP and such.
I did run into a hiccup that required me to download a ROM of the US997 14A model here https://forum.xda-developers.com/lg-g6/development/rom-lg-us997-14a-rom-t3656478
After getting that resolved, I went to encrypt my phone to find no option there. I checked on the other forums and reddit and people are saying it is "already encrypted."
However to confirm this, I launch TWRP through the phone after setting a password (I use whole word passwords)
All files are in plain view with the recovery not asking for any passwords which leads me to believe that the system is not encrypted.
This is highly concerning and potentially a deal breaker for me, is there something in the process I am missing or I did wrong?
Bubblewhip said:
Hi, I just got an LG G6 and ran through the process of rooting and unlocking my bootloader installing TWRP and such.
I did run into a hiccup that required me to download a ROM of the US997 14A model here https://forum.xda-developers.com/lg-g6/development/rom-lg-us997-14a-rom-t3656478
After getting that resolved, I went to encrypt my phone to find no option there. I checked on the other forums and reddit and people are saying it is "already encrypted."
However to confirm this, I launch TWRP through the phone after setting a password (I use whole word passwords)
All files are in plain view with the recovery not asking for any passwords which leads me to believe that the system is not encrypted.
This is highly concerning and potentially a deal breaker for me, is there something in the process I am missing or I did wrong?
Click to expand...
Click to collapse
If you have access to the internal memory from twrp than the phone is not encrypted, just flash a kdz trough lgup+uppercut and it'll be encrypted again
Killua96 said:
If you have access to the internal memory from twrp than the phone is not encrypted, just flash a kdz trough lgup+uppercut and it'll be encrypted again
Click to expand...
Click to collapse
If I flash the stock KDZ I will lose TWRP, was this loss of encryption due to unlocking the bootloader or loading TWRP? Are you given a password decrypt screen from TWRP If you try to access the phone through the bootloader?
Thanks.
Bubblewhip said:
If I flash the stock KDZ I will lose TWRP, was this loss of encryption due to unlocking the bootloader or loading TWRP? Are you given a password decrypt screen from TWRP If you try to access the phone through the bootloader?
Thanks.
Click to expand...
Click to collapse
Yeah, you'll lose twrp and root.
It's not due to bootloader unlock or twrp installation, you can decrypt the device only using the format data option in twrp.
I don't have an encrypted device so nope
I install twrp recovery but it need a kind of password that i don´t have. Anyone can help me?
JOSE_1889 said:
I install twrp recovery but it need a kind of password that i don´t have. Anyone can help me?
Click to expand...
Click to collapse
Hello,
The password that TWRP requires is your personal password/pin/pattern that you use to unlock your device, it's needed to desencrypt your data, because oreo have encrypt data not as Nougat and before.
Regards
black_arashi said:
Hello,
The password that TWRP requires is your personal password/pin/pattern that you use to unlock your device, it's needed to desencrypt your data, because oreo have encrypt data not as Nougat and before.
Regards
Click to expand...
Click to collapse
Yes. I discover it searching on internet. Thanks
I am on stock OTA 323, today I got notification for new 67 mb OTA update 326. When I downloaded it it just took me to twrp and did nothing. I don't want to unlock my device. How can I prevent my data, apps from losing. Pls help asap? Also in twrp internal storage is not detected it says 0 mb, I've tried flashing decrypt.zip ...
deepank singh said:
I am on stock OTA 323, today I got notification for new 67 mb OTA update 326. When I downloaded it it just took me to twrp and did nothing. I don't want to unlock my device. How can I prevent my data, apps from losing. Pls help asap? Also in twrp internal storage is not detected it says 0 mb, I've tried flashing decrypt.zip ...
Click to expand...
Click to collapse
You mean to say you flashed TWRP without unlocking bootloader ?
Tianhe said:
You mean to say you flashed TWRP without unlocking bootloader ?
Click to expand...
Click to collapse
Sry it was my mistake i mean i don't wanna lock my bootloader again
deepank singh said:
Sry it was my mistake i mean i don't wanna lock my bootloader again
Click to expand...
Click to collapse
Wait for Avinash to upload modified Stock ROM which can be flashed through TWRP. For exact steps consult his thread.
Edit: Just out of curiosity, did you use a Redmi phone before this ?
Tianhe said:
Wait for Avinash to upload modified Stock ROM which can be flashed through TWRP. For exact steps consult his thread.
Edit: Just out of curiosity, did you use a Redmi phone before this ?
Click to expand...
Click to collapse
Yeah Redmi 1s for a long time of period
https://drive.google.com/file/d/1P6s2A3kC_IXp7ReMS0ifEjxJ20vrLKG0/view
Flash this and
Decrypt and
Magisk if you want root.
Flashing full firmware will remove root and it will encrpt phone
deepank singh said:
Yeah Redmi 1s for a long time of period
Click to expand...
Click to collapse
So you must have used something like ZCX TWRP that is why you flashed the OTA straight off. ZCX TWRP had the option to flash incremental updates without any need of tweaking
Tianhe said:
So you must have used something like ZCX TWRP that is why you flashed the OTA straight off. ZCX TWRP had the option to flash incremental updates without any need of tweaking
Click to expand...
Click to collapse
Yeah earlier I didn't have any problem like this. Can you give me the solution for "not detecting my internal storage in twrp it says 0 mb"
deepank singh said:
Yeah earlier I didn't have any problem like this. Can you give me the solution for "not detecting my internal storage in twrp it says 0 mb"
Click to expand...
Click to collapse
It is 0 MB because system cannot be mounted because data is encrypted. Why do you need to mount /system or internal storage? The only possible reason I see is creating a TWRP backup with data.
Tianhe said:
It is 0 MB because system cannot be mounted because data is encrypted. Why do you need to mount /system or internal storage? The only possible reason I see is creating a TWRP backup with data.
Click to expand...
Click to collapse
Yeah I wanna creat TWRP backup
Aftab_khatri said:
https://drive.google.com/file/d/1P6s2A3kC_IXp7ReMS0ifEjxJ20vrLKG0/view
Flash this and
Decrypt and
Magisk if you want root.
Flashing full firmware will remove root and it will encrpt phone
Click to expand...
Click to collapse
Will I loose my apps and data after flashing it
A few days ago I updated my phone via TWRP, the process taken always worked:
1. Install firmware
2. Install decrypt.zip
3. Install Magisk
But this time, it didn't. After rebooting the phone, forced encryption started and after it was done, I found out that Magisk wasn't installed, on top of that, TWRP was replaced with the original recovery. Is there any way to re-root the phone?
Note: I have updated the phone in this manner a few times and nothing like this ever happened also, I tried reinstalling TWRP via fastboot, sins the bootloader is already unlocked, but got write errors, because of the forced encryption more than likely.
Are you sure you used the correct decrypt zip file ?
Tianhe said:
Are you sure you used the correct decrypt zip file ?
Click to expand...
Click to collapse
Yep, have used it in the past so i am sure it was the correct one.
User483901 said:
Yep, have used it in the past so i am sure it was the correct one.
Click to expand...
Click to collapse
There are different decrypt zips for Oreo & Pie. Also, there may be variations for different firmwares within the same version itself. Same goes for TWRP.
Tianhe said:
There are different decrypt zips for Oreo & Pie. Also, there may be variations for different firmwares within the same version itself. Same goes for TWRP.
Click to expand...
Click to collapse
Oh, didn't know that. But regardless, what does it matter what was used, I mean TWRP is no longer on the device so talking about which decrypt was used doesn't matter cuz it can't be used until TWRP is reinstalled which i think is impossible, cuz of the forced encryption, unless you know of a way.
User483901 said:
Oh, didn't know that. But regardless, what does it matter what was used, I mean TWRP is no longer on the device so talking about which decrypt was used doesn't matter cuz it can't be used until TWRP is reinstalled which i think is impossible, cuz of the forced encryption, unless you know of a way.
Click to expand...
Click to collapse
Encryption doesnt affect TWRP, the only drawback is that you cannot mount internal storage. However, if the TWRP version supports FDE natively then even that is possible. So encrypted devices can have TWRP recovery, you just need unlocked BL etc.
XDA
How to flash TWRP recovery in max Pro M1 without PC please help
@secreattecheme said:
How to flash TWRP recovery in max Pro M1 without PC please help
Click to expand...
Click to collapse
Is your phone bootloader unlocked?
I have never heard someone losing twrp by updating firmware. Perhaps you might have updated the rom which contained the stock recovery and hence replaced twrp. You can flash twrp again using fastboot. Remember that in order to remove encryption (since your phone has already encrypted the data) you'll have to format data from twrp and you'll lose all your data, even internal storage and twrp backups.
About decrypt.zip, there is a sequence of flashing it. It didn't always work for me though.
farhanshaikh671 said:
I have never heard someone losing twrp by updating firmware. Perhaps you might have updated the rom which contained the stock recovery and hence replaced twrp. You can flash twrp again using fastboot. Remember that in order to remove encryption (since your phone has already encrypted the data) you'll have to format data from twrp and you'll lose all your data, even internal storage and twrp backups.
About decrypt.zip, there is a sequence of flashing it. It didn't always work for me though.
Click to expand...
Click to collapse
No, I updated it by going to the Asus website and downloading the firmware update, have done the same with the Pie update and the one before it, edited the image file, so it can be flashed using TWRP and then did the steps in the OP.
Also, as said before i can't flash TWRP sins i get write errors in fastboot.