Can someone tell me how can I disable the encryption on my phone or Decrypt it. I had enabled encryption some weeks ago and am having re-thoughts on this. Want to decrypt. Is this possible? I dont see and option in the phone to do that.
coolmalayalee said:
Can someone tell me how can I disable the encryption on my phone or Decrypt it. I had enabled encryption some weeks ago and am having re-thoughts on this. Want to decrypt. Is this possible? I dont see and option in the phone to do that.
Click to expand...
Click to collapse
It is not possible to decrypt the existing data, a factory reset is the only way to remove the encryption. You may be able to backup using adb backup or PC Companion, factory reset, and then restore.
cschmitt said:
It is not possible to decrypt the existing data, a factory reset is the only way to remove the encryption. You may be able to backup using adb backup or PC Companion, factory reset, and then restore.
Click to expand...
Click to collapse
Thanks. Finally did the reset. Had to flash the new firmware anyways. So, did both together. Will never encrypt again.
Did you have problems with the encryption? Why did you have second thoughts?
I've now installed TWRP (of this flavor : twrp-3.0.2-1-oneplus3t.img ), and supersu after updating firmware to 3.5.3 on the 3t I received yesterday. It installs without problem. I've not touched encryption and I'm very wary of using TWRP at the moment, because it always asks me for the encryption password. When I initialized the phone after this setup, the only password/entry entities I entered were a) a 4-digit pin, and b) 3 fingerprints. They work fine.
When I try to boot to TWRP, I always am prompted for a password immediately. I have no idea what the password is, and have tried my known-to-be-correct PIN , no luck. I have tried hitting cancel, and then only if I agree to mount /system as RO can I enter TWRP without it trying and failing to decrypt everything which corrupts storage.
I've read the entire (TWRP) thread a couple of times, but maybe it was too late at night. I'm wondering if anyone can tell me what step I'm missing, or if I'm trying to do something that can't be done because of what was just said above (encryption isn't fully supported by TWRP yet?) , or if I just should know the password and let TWRP decrypt it. Finally, is there a way to just decrypt the phone while booted and is that even called for?
I'd like to use TWRP which seems fine in every other respect (well, I don't yet know if I can make a backup & restore, so that isn't fine), but am held up by the password entry at the start of each session. Many thanks for getting it this far and thanks for any help you might give.
hachamacha said:
I've now installed TWRP (of this flavor : twrp-3.0.2-1-oneplus3t.img ), and supersu after updating firmware to 3.5.3 on the 3t I received yesterday. It installs without problem. I've not touched encryption and I'm very wary of using TWRP at the moment, because it always asks me for the encryption password. When I initialized the phone after this setup, the only password/entry entities I entered were a) a 4-digit pin, and b) 3 fingerprints. They work fine.
When I try to boot to TWRP, I always am prompted for a password immediately. I have no idea what the password is, and have tried my known-to-be-correct PIN , no luck. I have tried hitting cancel, and then only if I agree to mount /system as RO can I enter TWRP without it trying and failing to decrypt everything which corrupts storage.
I've read the entire (TWRP) thread a couple of times, but maybe it was too late at night. I'm wondering if anyone can tell me what step I'm missing, or if I'm trying to do something that can't be done because of what was just said above (encryption isn't fully supported by TWRP yet?) , or if I just should know the password and let TWRP decrypt it. Finally, is there a way to just decrypt the phone while booted and is that even called for?
I'd like to use TWRP which seems fine in every other respect (well, I don't yet know if I can make a backup & restore, so that isn't fine), but am held up by the password entry at the start of each session. Many thanks for getting it this far and thanks for any help you might give.
Click to expand...
Click to collapse
I would start over. Get the stock recovery and flash it. Then factory reset the phone. Do not put a pin or a fingerprint at all after you have booted to the phone. Go straight to the bootloader and do the twrp flashing instructions. after you have flashed and i believe if you want to be decrypted you format data than flash supersu again. Boot into system and then back to twrp and see if that worked. I remember doing this on my nexus 6p but not sure if the kernel has to support the decryption. remember when you do a back up of your phone never never never back it up with pin or passwords or fingerprint. You wont be able to restore succesfully from my experince with the nexus 6p. make sure you back everything up before doing this and i am not responsible for any problems occured. and make sure you are on the latest update from oneplus. hope this helped
cameljockey1 said:
I would start over. Get the stock recovery and flash it. Then factory reset the phone. Do not put a pin or a fingerprint at all after you have booted to the phone. Go straight to the bootloader and do the twrp flashing instructions. after you have flashed and i believe if you want to be decrypted you format data than flash supersu again. Boot into system and then back to twrp and see if that worked. I remember doing this on my nexus 6p but not sure if the kernel has to support the decryption. remember when you do a back up of your phone never never never back it up with pin or passwords or fingerprint. You wont be able to restore succesfully from my experince with the nexus 6p. make sure you back everything up before doing this and i am not responsible for any problems occured. and make sure you are on the latest update from oneplus. hope this helped
Click to expand...
Click to collapse
That's exactly how I did it the first time, without password, without setting up phone, and when it got to TWRP (the first time), I was presented with the password prompt. When I hit cancel it went by it, but then said it was decrypting (which I didn't want), and corrupted my storage.
When I reinstalled 3.5.3, I did the same thing again, and that time was not corrupted so I was able to install supersu. At this point I've entered some fingerprints and a pin. TWRP says it supports encryption so I'm wondering about where the password comes from.
Thanks for your quick response. I'm still awaiting some reply over in the TWRP forum as well.
hachamacha said:
That's exactly how I did it the first time, without password, without setting up phone, and when it got to TWRP (the first time), I was presented with the password prompt. When I hit cancel it went by it, but then said it was decrypting (which I didn't want), and corrupted my storage.
When I reinstalled 3.5.3, I did the same thing again, and that time was not corrupted so I was able to install supersu. At this point I've entered some fingerprints and a pin. TWRP says it supports encryption so I'm wondering about where the password comes from.
Thanks for your quick response. I'm still awaiting some reply over in the TWRP forum as well.
Click to expand...
Click to collapse
Are you sure you had 3.5.3 the first time you did it?
c_86 said:
Are you sure you had 3.5.3 the first time you did it?
Click to expand...
Click to collapse
Yes, it was the first thing I did. After receiving the 3t, I skipped over all the prompts (to avoid entering accounts, waiting for sw upds and to not enter passwords) and went to software updates and allowed the 3.5.3 update to occur.
Then I did the things described above.
-----
In the interests of my trying to understand everything I'm reading about 6.x and encryption. I'm getting the drift that phones with 6.x + are encrypted as a matter of course. Is that the case (or how do I tell if it is)? If it is by default encrypted, then is there a default password before you have entered any specific pin or swipe pattern , etc?
Another question: When TWRP asks for a password, what exactly does it want to do? Does it want to decrypt the data for it's own operations (so just a twrp-level decryption) or does it actually want to completely decrypt partitions? If so, why? Is that the only way TWRP can work these days with default encrypted platforms?
Thanks.
hachamacha said:
Yes, it was the first thing I did. After receiving the 3t, I skipped over all the prompts (to avoid entering accounts, waiting for sw upds and to not enter passwords) and went to software updates and allowed the 3.5.3 update to occur.
Then I did the things described above.
-----
In the interests of my trying to understand everything I'm reading about 6.x and encryption. I'm getting the drift that phones with 6.x + are encrypted as a matter of course. Is that the case (or how do I tell if it is)? If it is by default encrypted, then is there a default password before you have entered any specific pin or swipe pattern , etc?
Another question: When TWRP asks for a password, what exactly does it want to do? Does it want to decrypt the data for it's own operations (so just a twrp-level decryption) or does it actually want to completely decrypt partitions? If so, why? Is that the only way TWRP can work these days with default encrypted platforms?
Thanks.
Click to expand...
Click to collapse
Flash stock recovery, install stock 3.5.3 zip, flash TWRP beta 3 and then SR4. I went through same problem and this got me in(would accept my phone password. )
ghettopops said:
Flash stock recovery, install stock 3.5.3 zip, flash TWRP beta 3 and then SR4. I went through same problem and this got me in(would accept my phone password. )
Click to expand...
Click to collapse
Is that the TWRP beta 3 from the TWRP thread? I thought I saw it mentioned in there. Thanks.
I've done the rest once so will give beta 3 a shot before I resign myself to putting the whole thing back together. Not that big a deal I suppose. I finally realized (after reading quite a bit) that 6.x + comes encrypted and that all versions of TWRP don't handle it right, so I suppose there's no easy way around it. (I'm wondering about this link I happened upon: https://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/ )
hachamacha said:
Is that the TWRP beta 3 from the TWRP thread? I thought I saw it mentioned in there. Thanks.
I've done the rest once so will give beta 3 a shot before I resign myself to putting the whole thing back together. Not that big a deal I suppose. I finally realized (after reading quite a bit) that 6.x + comes encrypted and that all versions of TWRP don't handle it right, so I suppose there's no easy way around it. (I'm wondering about this link I happened upon: https://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/ )
Click to expand...
Click to collapse
Yes page 9 or 10 OP gives me a link
The solution for me:
I received this reply in the TWRP thread in Development from the OP:
Quote:
Originally Posted by jcadduono
try setting a non-pin password on boot in your OS, like, an actual password, this should convince 3.5.3 to rewrite your crypto key in working format
then see if that new password works on twrp
if it does, you can probably set it back to pin and the pin might start working in twrp
if it doesn't, let me know
-----------------------
Yes, that completely fixed the entire mess and thanks to everyone else for their suggestions. Funny that I never had noticed the word "password" in the security settings, so I tried pin.
Now I've got an encrypted 3t with working TWRP, makes backups, tried a restore and f2fs, no real changes from stock aside from adding TWRP, picking a password, etc.
This seems to happen when you've got the fingerprint method enabled with PIN or password for that matter.
My experience:
I update from Oxygen 4.1.6 to 4.1.7 with TWRP and something went wrong because the phone stuck in bootload for more then half hour.
I've reboot and it appeared 'Encryption Unsuccessful' and it locked my phone. I tried to go to TWRP and it required the password that was 'default_password' but after it not allowed me to mount data and it seemed that there weren't any data in my phone.
I couldn't wipe, format or install other rom because I received error like 'unable to mount X'.
I've solved downloading the Oxygen Recovery and with a USB OTG, flashing it on my phone (with 'mount image' in TWRP).
I rebooted in Oxygen Recovery and it also asked me the password. I've just pushed 'Forgot password' and it formatted my phone.
The phone rebooted without problems (and without any data :\)
Hope to be useful for someone else in my same situation
You can get back in, without loosing any Data.
Go to TWRP
Choose Advanced
Select Terminal
Type this commands:
Code:
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
reboot
Use Android again
I encountered this problem after I updated TWRP to version 3.2.1-0.
I regularly update my rom with TWRP and had never been prompted to enter a pin/password before. My lock screen pin was not accepted.
Seems this issue is a bug in a number of TWRP versions. I fixed it by flashing back to version 3.1.1-2. You can download and flash from a list of historical TWRP versions in Android by downloading the official TWRP app, so I didn't need to mess around sideloading it. Rebooted into TWRP, straight in, no problems.
astralbee said:
I encountered this problem after I updated TWRP to version 3.2.1-0.
I regularly update my rom with TWRP and had never been prompted to enter a pin/password before. My lock screen pin was not accepted.
Seems this issue is a bug in a number of TWRP versions. I fixed it by flashing back to version 3.1.1-2. You can download and flash from a list of historical TWRP versions in Android by downloading the official TWRP app, so I didn't need to mess around sideloading it. Rebooted into TWRP, straight in, no problems.
Click to expand...
Click to collapse
Same problem on one of my 3Ts, the other is working with the Oreo based TWRP.
Oreo based Red Wolf Recovery is working: https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/recovery-red-wolf-recovery-project-t3805416
These things are weird:
1. Why does one 3T work, but not the other 3T ?
2. Why does (Oreo based) Red Wolf Recovery work?
3. Why is OOS Beta 29 able to decrypt Data perfectly?
I assume it's a decryption related bug in Oreo based TWRP.
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
SourPower said:
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
What exactly is it you're trying to do? What TWRP are you using? What ROM?
You sound surprised that you can't see your Storage when you haven't entered a Password to Decrypt? That is, after all, what it's supposed to do. What security have you set up on your phone? Did you have Boot time security?
With so little useful information to go on it's hard to help. I'd recommend trying Red Wolf Recovery in any case. It's magic at solving many issues.
Sorry lol what happen was I was updating to latest stable oos, and had standard encryption set up. I wipes caches, and flashed latest rom, then magisk and again twrp (which I should not have) and then my phone had a quick reset. From there it was locked with twrp, neither my pin or default_pw worked so I just formated my phone, after copying data and important things to PC. Everything is good now just had to waste my own time.
For those of you facing twrp encryption when you set a password on the phone, remove your lock screen password and twrp will no longer be encrypted.
raeee1 said:
For those of you facing twrp encryption when you set a password on the phone, remove your lock screen password and twrp will no longer be encrypted.
Click to expand...
Click to collapse
Not so. I removed the password and TWRP still asks for a password.
hachamacha said:
The solution for me:
I received this reply in the TWRP thread in Development from the OP:
Quote:
Originally Posted by jcadduono
try setting a non-pin password on boot in your OS, like, an actual password, this should convince 3.5.3 to rewrite your crypto key in working format
then see if that new password works on twrp
if it does, you can probably set it back to pin and the pin might start working in twrp
if it doesn't, let me know
-----------------------
Yes, that completely fixed the entire mess and thanks to everyone else for their suggestions. Funny that I never had noticed the word "password" in the security settings, so I tried pin.
Now I've got an encrypted 3t with working TWRP, makes backups, tried a restore and f2fs, no real changes from stock aside from adding TWRP, picking a password, etc.
Click to expand...
Click to collapse
This did not work for me.
Hi Friends,
I setted-up secure start up ( i.e a pattern lock appear when booting the device) when i installed lineage os, but i soon got annoyed with it. My problem is I don't know how to turn it off.
SOLUTIONS tried:-
1. I checked Each and every setting on my phone to turn it off but couldn't found any on lineage os
2.I tried flashing even a different rom , Havoc OS but the secure start up pattern lock still persist
3.when setting up havoc os , i tried disabling it by clicking 'no' when havoc os startup asked to enable secure start up but nothing happened
And Now even my TWRP recovery has a pattern lock due this problem and Wiping my phone didn't solve it.
Any Help PLease????
Solved:
goto>fastboot mode (bootloader)>connect to pc with adb running>type in cmd>fastboot erase userdata
PreciousPulkit said:
Hi Friends,
I setted-up secure start up ( i.e a pattern lock appear when booting the device) when i installed lineage os, but i soon got annoyed with it. My problem is I don't know how to turn it off.
SOLUTIONS tried:-
1. I checked Each and every setting on my phone to turn it off but couldn't found any on lineage os
2.I tried flashing even a different rom , Havoc OS but the secure start up pattern lock still persist
3.when setting up havoc os , i tried disabling it by clicking 'no' when havoc os startup asked to enable secure start up but nothing happened
And Now even my TWRP recovery has a pattern lock due this problem and Wiping my phone didn't solve it.
Any Help PLease????
Click to expand...
Click to collapse
Some people can clear the password by setting a new password and selecting No for secure boot. But that has never worked for me.
See the discussion here https://forum.xda-developers.com/on...ageos-15-1-oneplus-3-3t-t3739169/post76890649
So, try that first and if it doesn't work, the only other option is to reformat the data partition. You'll lose everything in your internal storage, so back it up on external storage.
Sent from my OnePlus3T using XDA Labs
The only way to make it go away is to wipe your phone. Including the internal storage.
I was pissed when I found out.
BillGoss said:
Some people can clear the password by setting a new password and selecting No for secure boot. But that has never worked for me.
See the discussion here https://forum.xda-developers.com/on...ageos-15-1-oneplus-3-3t-t3739169/post76890649
So, try that first and if it doesn't work, the only other option is to reformat the data partition. You'll lose everything in your internal storage, so back it up on external storage.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Thanks For the reply But I have Tried wiping my phone, everything including internal storage but nothing seems to help. Any other solution?
ast00 said:
The only way to make it go away is to wipe your phone. Including the internal storage.
I was pissed when I found out.
Click to expand...
Click to collapse
Thanks For the reply But I have Tried wiping my phone, everything including internal storage but nothing seems to help. Any other solution?
PreciousPulkit said:
Thanks For the reply But I have Tried wiping my phone, everything including internal storage but nothing seems to help. Any other solution?
Click to expand...
Click to collapse
Plug your phone into a computer, go to bootloader mode and then use cmd to type "fastboot erase userdata".
This should decrypt your device. Be careful though, booting a stock ROM or anything with the stock kernel will auto encrypt it again without warning you.
ast00 said:
Be careful though, booting a stock ROM or anything with the stock kernel will auto encrypt it again without warning you.
Click to expand...
Click to collapse
But it won't set boot password up on its own though
przemcio510 said:
But it won't set boot password up on its own though
Click to expand...
Click to collapse
True. But I consider encryption itself a curse. There really should be a way to decrypt without wiping the phone.
ast00 said:
True. But I consider encryption itself a curse. There really should be a way to decrypt without wiping the phone.
Click to expand...
Click to collapse
Consider that if you lose your unencrypted phone or it gets stolen, a thief can read your data, access all your accounts and bypass FRP.
przemcio510 said:
Consider that if you lose your unencrypted phone or it gets stolen, a thief can read your data, access all your accounts and bypass FRP.
Click to expand...
Click to collapse
If it's rooted encryption doesn't help. Secure startup does, but it introduces so many problems with simple things like restoring a backup that it's not worth it for me.
And like I said, encryption alone doesn't make a difference as long as you TWRP.
ast00 said:
Secure startup does, but it introduces so many problems with simple things like restoring a backup that it's not worth it for me.
Click to expand...
Click to collapse
Never had such issues
ast00 said:
And like I said, encryption alone doesn't make a difference as long as you TWRP.
Click to expand...
Click to collapse
Actually encryption without secure startup doesn't make sense at all
przemcio510 said:
Never had such issues
Actually encryption without secure startup doesn't make sense at all
Click to expand...
Click to collapse
Which is exactly why forced encryption on every single damn phone is stupid. Ask the user on the first startup if they want this or not. If someone is too stupid to decide this for themselves after a simple, one paragraph explanation, they don't deserve a smartphone.
But the current implementation is unreliable and frustrating to anyone looking to modify the software on their phone. Granted, we are the minority.
ast00 said:
Plug your phone into a computer, go to bootloader mode and then use cmd to type "fastboot erase userdata".
This should decrypt your device. Be careful though, booting a stock ROM or anything with the stock kernel will auto encrypt it again without warning you.
Click to expand...
Click to collapse
Thanks This Worked Very well
ast00 said:
Plug your phone into a computer, go to bootloader mode and then use cmd to type "fastboot erase userdata".
This should decrypt your device. Be careful though, booting a stock ROM or anything with the stock kernel will auto encrypt it again without warning you.
Click to expand...
Click to collapse
Does this mean a Gapps ROM as stock would encrypt it too?
SchwarZWeiSs said:
Does this mean a Gapps ROM as stock would encrypt it too?
Click to expand...
Click to collapse
Not sure what you mean by gapps rom.
Stock Oxygen OS is the only thing that will encrypt it. You can use custom roms based on Oxygen OS though.
ast00 said:
Not sure what you mean by gapps rom.
Stock Oxygen OS is the only thing that will encrypt it. You can use custom roms based on Oxygen OS though.
Click to expand...
Click to collapse
Thanks!
Hey guys I'm on Xiaomi EU Rom and TWRP keeps asking me for a password whenever I boot into it I've tried formatting the data it works but then when I need to boot into the recovery again i need to format it again
Don't know what's causing this
Try using the pin number that is used to unlock your phone.
When you want to update the Rom, disable fingerprint et PIN. After, boot to recovery and no need to enter password.
Strykar said:
Try using the pin number that is used to unlock your phone.
Click to expand...
Click to collapse
Thank you so much man this actually worked, it decrypted the data and let me update the phone
CleverFogs said:
Thank you so much man this actually worked, it decrypted the data and let me update the phone
Click to expand...
Click to collapse
Yep, it works like designed. The moment you set a pin under android, the data gets encrypted and twrp will ask for that pin.