Related
I unlocked my bootloader, flashed Chainfire's systemless boot.img, flashed TWRP twrp-2.8.7.1-angler.img and when I took into recovery TWRP is asking me for a password to decrypt. I don't remember setting a password and don't know if there is a default one.
Can anyone help?
exSD said:
I unlocked my bootloader, flashed Chainfire's systemless boot.img, flashed TWRP twrp-2.8.7.1-angler.img and when I took into recovery TWRP is asking me for a password to decrypt. I don't remember setting a password and don't know if there is a default one.
Can anyone help?
Click to expand...
Click to collapse
Give this a shot?
Dees_Troy said:
When you set up a lock screen PIN / pattern / password, you are presented with an option to require a password when turning on the device. If you say no to this option, your device is encrypted using "default_password" as the password.
Click to expand...
Click to collapse
RojoNinja said:
Give this a shot?
Click to expand...
Click to collapse
I tired both a pin/default_password. Neither seems to work.
Do I need to format userdata to decrypt?
Your device is likely encrypted and TWRP can't read the contents of your SD card unless you format /userdata first. This will wipe everything on your phone. The nexus 6P rooting guide will explain this in detail. I'd link it here but I'm new on here and I don't really know how. Look in the Nexus 6P general section. It should be stickied at the top.
Here's the link to the rooting guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
What happens if you boot up and set a password? Does that password work for TWRP?
Cares said:
What happens if you boot up and set a password? Does that password work for TWRP?
Click to expand...
Click to collapse
I flashed the stock image and redid the process.
I booted the phone and did not set any password/pin/fingerprint/etc. No security. Then I redid the boot.img, recovery.
I was then able to reboot into TWRP without the password prompt. Flashed systemless SuperSU and rebooted.
Now I'm stuck in the Google loading screen and has been there for a while. Looks like maybe it's not liking the new boot.img?
exSD said:
I flashed the stock image and redid the process.
I booted the phone and did not set any password/pin/fingerprint/etc. No security. Then I redid the boot.img, recovery.
I was then able to reboot into TWRP without the password prompt. Flashed systemless SuperSU and rebooted.
Now I'm stuck in the Google loading screen and has been there for a while. Looks like maybe it's not liking the new boot.img?
Click to expand...
Click to collapse
You're likely not on the latest build, so you'll have to use the images on Google to put yourself on the MDB08K (or higher) build before proceeding with the modified boot img (unless your devices can get the OTA). Many of the devices shipped with MDA89D out of the box.
Kusanagi Fire said:
You're likely not on the latest build, so you'll have to use the images on Google to put yourself on the MDB08K (or higher) build before proceeding with the modified boot img (unless your devices can get the OTA). Many of the devices shipped with MDA89D out of the box.
Click to expand...
Click to collapse
Is D or K the latest?
exSD said:
Is D or K the latest?
Click to expand...
Click to collapse
Latest is M. Modified boot was created based on K, but I believe has no problems working on M.
Kusanagi Fire said:
Latest is M. Modified boot was created based on K, but I believe has no problems working on M.
Click to expand...
Click to collapse
For some reason I thought D was the latest and flashed that. I'll upgrade to M and use the modified K boot.img.
That should clear it all up. Thanks for your help bud. I appreciate it. Let me know if I can ever help you sometime.
exSD said:
For some reason I thought D was the latest and flashed that. I'll upgrade to M and use the modified K boot.img.
That should clear it all up. Thanks for your help bud. I appreciate it. Let me know if I can ever help you sometime.
Click to expand...
Click to collapse
No worries. Happy to help. I had this problem when trying to root my phone, as well. It happens to the best of us. Hope that clears everything up for you and you're able to enjoy this beauty.
Is this normal for TWRP to ask for a password if you have pattern password turned on. So do I need to turn off all of my security before flashing TWRP 2.8.7.1
Right now my bootloader is unlocked, M6.0 all stock. I’ve been waiting for the source code to be release by Google so we can get a official root SU
boxcar8028 said:
Is this normal for TWRP to ask for a password if you have pattern password turned on. So do I need to turn off all of my security before flashing TWRP 2.8.7.1
Right now my bootloader is unlocked, M6.0 all stock. I’ve been waiting for the source code to be release by Google so we can get a official root SU
Click to expand...
Click to collapse
I'm not sure how TWRP would handle the pattern password. You can flash TWRP 2.8.7.1 and give it a shot. If it doesn't work, just download the stock image and extract the recovery.img from it and flash it back to stock.
Kusanagi Fire said:
No worries. Happy to help. I had this problem when trying to root my phone, as well. It happens to the best of us. Hope that clears everything up for you and you're able to enjoy this beauty.
Click to expand...
Click to collapse
Hey, FYI, that was my issue. Flashed the M image, then the K systemless root boot.img and all is working well now. No password prompt on latest TWRP either.
Resetting the pin worked for me
was having the same problem on Nexus 6P- had previously TWRP/rooted with no problem, don't remember being asked for a password.
After flashing recovery/radio/ROM back to stock and then later deciding to root again ran into this.
Android was still booting up OK so just set a new pin in Settings-->Security-->ScreenLock and selected the require PIN to start option. This PIN then worked as the password in TWRP to decrypt.
I was having the same issue with TWRP 2.8.7.2, I decided to flash TWRP 3.0.0.1 and I did not get prompted for the password. Not sure if this a true solution so at some point I may just decrypt data.
From another forum, This worked for me and couple of other people too
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.
rdskhalsa said:
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.
Click to expand...
Click to collapse
Tnx mate, your method worked like a charm for me.
I think I'm having a twist on this problem.
After using Lineage for a while I tried another rom (carbon) which I now think has encrypted my data. I tried going back to lineage but now I cannot access my data, nor the backups I made for both Lineage and Carbon.
I think that if I can put the backup of carbon back I should also have my files back. But with and encrypted file system I can not get back to Carbon.
I think I did set "ask for password at boot" in Lineage but I took off the pattern+ finger prints before making the backup and I did not set pattern or fingerprint after installing carbon.
Is there a way to get back to carbon?
Your data is no longer accessible. Once your storage has been encrypted, the only way to un-encrypt is to flash a full stock Google image, and then do a factory reset from the stock recovery. If you had any backups on PC, you could then restore them and be back in business. This USUALLY only happens to you one time and you never forget. Think of it as a housecleaning day.
Hey guys! I've having some trouble getting my device set up with root and encryption, while ending with a locked bootloader. I hope I can find some help.
Here is the procedure I tried:
Unlocked the bootloader
Did a full restore to MHC19I through fastboot
Flashed this boot.img
( This is so I can encrypt the user data partition after getting into Android, and it also allows a system-root without getting a boot loop )
Flashed the twrp-3.0.0-1-angler.img recovery
Locked the bootloader
Booted into TWRP without ever going into Android yet
Sideloaded BETA-SuperSU-v2.68-20160228150503.zip
Booted into Android and setup with my Google account, I used a fingerprint and set a PIN, and selected "PIN required on startup"
Update all the stock apps, with some reboots in between
Then encrypted the phone through security settings
Now here is where I'm having trouble.
When I boot into TWRP after having encrypted the user data partition, it asks for my password, as it should, but it won't take my PIN. It tells me "Password failed, please try again" and "Failed to decrypt data." Is the password prompt not asking for the PIN I set? Does TWRP only support decryption with a password, or something? Can I not use a fingerprint to lock the device? What am I missing here?
Is there perhaps another procedure to getting Android setup with TWRP, root, and user data encryption while ending with a locked bootloader?
Thank you in advance for all your help!
You need a modified Twrp for this new Base. Just have a look around
Gorgtech said:
You need a modified Twrp for this new Base. Just have a look around
Click to expand...
Click to collapse
Is the "twrp-3.0.0-1-angler.img" image here not the new modified TWRP for MHC19I?
edit: According to this post, I'm using the correct version of TWRP.
Yes, this one should fit. I had the same problem before.
mylios101 said:
Hey guys! I've having some trouble getting my device set up with root and encryption, while ending with a locked bootloader. I hope I can find some help.
Here is the procedure I tried:
Unlocked the bootloader
Did a full restore to MHC19I through fastboot
Flashed this boot.img
( This is so I can encrypt the user data partition after getting into Android, and it also allows a system-root without getting a boot loop )
Flashed the twrp-3.0.0-1-angler.img recovery
Locked the bootloader
Booted into TWRP without ever going into Android yet
Sideloaded BETA-SuperSU-v2.68-20160228150503.zip
Booted into Android and setup with my Google account, I used a fingerprint and set a PIN, and selected "PIN required on startup"
Update all the stock apps, with some reboots in between
Then encrypted the phone through security settings
Now here is where I'm having trouble.
When I boot into TWRP after having encrypted the user data partition, it asks for my password, as it should, but it won't take my PIN. It tells me "Password failed, please try again" and "Failed to decrypt data." Is the password prompt not asking for the PIN I set? Does TWRP only support decryption with a password, or something? Can I not use a fingerprint to lock the device? What am I missing here?
Is there perhaps another procedure to getting Android setup with TWRP, root, and user data encryption while ending with a locked bootloader?
Thank you in advance for all your help!
Click to expand...
Click to collapse
First: Why did you re-lock the bootloader? You cant flash any twrp updates or update with factory images.
Second: You should have just flashed supersu in twrp before any booting?
When clean installing I personally follow these:
fastboot flash bootloader
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-02.50.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot format userdata
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash recovery twrp
fastboot reboot-recovery
While in twrp I:
adb push supersu to /sdcard/
then flash supersu in recovery
then wipe dalvik/cache in twrp
finally let the phone boot and set up normally. Leaving bootloader unlocked
Gorgtech said:
Yes, this one should fit. I had the same problem before.
Click to expand...
Click to collapse
You've had the same issue before that I'm having now? What was your fix?
I've flashed system, boot and vendor before. Also updated the bootloader and the radio and was asked for a password which I could not get rid off. I had to sideload supersu and also flash a modified Twrp after. Now I can access the recovery like I was used to. It's the latest Base which causes trouble.
thepoetlives89 said:
First: Why did you re-lock the bootloader? You cant flash any twrp updates or update with factory images.
Second: You should have just flashed supersu in twrp before any booting?
Click to expand...
Click to collapse
I lock the bootloader for obvious security reasons, but it leads to the user data partition being wiped, which prevents the partition from encrypting on initial Android setup.
I do flash Supersu through TWRP before my first boot to Android, otherwise TWRP gets wiped out.
I'll give your procedure a try! Thank you.
mylios101 said:
I lock the bootloader for obvious security reasons, but it leads to the user data partition being wiped, which prevents the partition from encrypting on initial Android setup.
I do flash Supersu through TWRP before my first boot to Android, otherwise TWRP gets wiped out.
I'll give your procedure a try! Thank you.
Click to expand...
Click to collapse
As far as i know with 6.0.1 with the stock boot.img it automatically encrypts on first boot, even with an unlocked bootloader.
thepoetlives89 said:
As far as i know with 6.0.1 with the stock boot.img it automatically encrypts on first boot, even with an unlocked bootloader.
Click to expand...
Click to collapse
No, I believe the problem is that it does not automatically encrypt on first boot when I lock the bootloader. My work around was using a modded boot.img so I can encrypt post-setup through the security settings menu, but I can't decrypt with TWRP. Without the boot.img and a locked bootloader, it sits in a bootloop and never encrypts. through the security settings option.
I have to confirm this, but it looks like the only way to get the device encrypted, rooted, and TWRP accessible is to not use the modded boot.img and leave the bootloader unlocked, which I'd rather not. Regardless, I'll give it a try and report back.
mylios101 said:
No, I believe the problem is that it does not automatically encrypt on first boot when I lock the bootloader. My work around was using a modded boot.img so I can encrypt post-setup through the security settings menu, but I can't decrypt with TWRP. Without the boot.img and a locked bootloader, it sits in a bootloop and never encrypts. through the security settings option.
I have to confirm this, but it looks like the only way to get the device encrypted, rooted, and TWRP accessible is to not use the modded boot.img and leave the bootloader unlocked, which I'd rather not. Regardless, I'll give it a try and report back.
Click to expand...
Click to collapse
I was able to encrypt with the modified boot.img that supersu makes when you flash it over the one that comes with the factory image. Bootloader unlocked.
Gorgtech said:
I've flashed system, boot and vendor before. Also updated the bootloader and the radio and was asked for a password which I could not get rid off. I had to sideload supersu and also flash a modified Twrp after. Now I can access the recovery like I was used to. It's the latest Base which causes trouble.
Click to expand...
Click to collapse
How did you sideload supersu? I have the same problem as you
Fastboot format userdata in terminal.
kunal_07 said:
How did you sideload supersu? I have the same problem as you
Click to expand...
Click to collapse
I'm using the "adb sideload" function under "advanced" in TWRP. Another user suggested doing an "adb push" and then using the regular TWRP install instead. I'm going to try that and see what happens.
edit: sideloading vs pushing supersu made no difference. Android is still not encrypting the user data partition on first boot.
edit 2: After some testing, it looks like flashing the latest beta of Supersu is what is preventing Android from encrypting, which is obviously a problem. Without flashing Supersu, TWRP doesn't persist and I can't get root access.
I was able to root using RC SuperSU 2.69 using chainfire auto root
Easy solve.
1. Create 4 digit screen lock pin code when booted in rom settings>security
2. Use flashify to flash newest twrp
3. Boot into new twrp and use new pin code to decrypt data
When flashing new version of TWRP it automatically encrypt the data with "default_password" but if you try to use that as your password it will not work. If you create a pin, then use that pen to decrypt the password it will work. Then if you go back into your booted up rom and change the password to none TWRP will not ask you for a password.
Can't remember steps 1. And 2. Might be switched
i just updated to the mch19i build via fastboot (since i'm rooted and can't take an ota apparently - has anyone made twrp-able zips for those updates yet?) and am having this same problem. what's different about this build that we need a different twrp for?
asj0422 said:
i just updated to the mch19i build via fastboot (since i'm rooted and can't take an ota apparently - has anyone made twrp-able zips for those updates yet?) and am having this same problem. what's different about this build that we need a different twrp for?
Click to expand...
Click to collapse
Well for one thing twrp 3.0.0.1 allows for vendor images to be flashed to the vendor partition. The previous ones you can't. That's why I updated with flashify. Two seconds of easiness. Just set a 4 digit lock screen pin before because twrp encrypts with unknown password upon first boot that's why you assign it one.
The only way for otas is to side load or fast boot flash.
Or. Run a custom ROM and get flashable zips for updates, these work great with all these Google update releases
Hi everyone, I hate to bring back an old post but I am new to XDA today so I'm getting used to it.
Well, I'm a first time ROM user, PureNexus + ElementalX kernal (amazing). But I had a question regarding this encryption and TWRP. I know older versions of TWRP had issues with entering the encryption password, I want to encrypt mine but I want to be sure that this issue has been fixed. I can't find anything online regarding it either. Can anyone help me out?
Device: Nexus 6P
ROM: PureNexus 7.1.2_r24
Kernal: ElementalX 5.03
TWRP: 3.1.1
Any information would be helpful! Before I encrypt! Just don't wanna do it then be stuck.
Ayeeebroham said:
Hi everyone, I hate to bring back an old post but I am new to XDA today so I'm getting used to it.
Well, I'm a first time ROM user, PureNexus + ElementalX kernal (amazing). But I had a question regarding this encryption and TWRP. I know older versions of TWRP had issues with entering the encryption password, I want to encrypt mine but I want to be sure that this issue has been fixed. I can't find anything online regarding it either. Can anyone help me out?
Device: Nexus 6P
ROM: PureNexus 7.1.2_r24
Kernal: ElementalX 5.03
TWRP: 3.1.1
Any information would be helpful! Before I encrypt! Just don't wanna do it then be stuck.
Click to expand...
Click to collapse
Not sure what you are asking. If you've set a PIN, use it when promoted by TWRP.
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
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.