Database Develop

how to decrypt in twrp?

I have my 3t unlocked and twrp flashed, but every time I boot into it, it indicates not able to decrypt data partition. Even after flashing with sideload, the pin which I set in preinstalled OS couldn't unlock it. Tried to disable boot up pin didn't help me out. Any hints?
Thankc

zphou said:
I have my 3t unlocked and twrp flashed, but every time I boot into it, it indicates not able to decrypt data partition. Even after flashing with sideload, the pin which I set in preinstalled OS couldn't unlock it. Tried to disable boot up pin didn't help me out. Any hints?
Thankc
Click to expand...
Click to collapse
Did you flashed dm-verity zip disabler or SuperSU zip before boot to system...?

cultofluna said:
Did you flashed dm-verity zip disabler or SuperSU zip before boot to system...?
Click to expand...
Click to collapse
It sounds like he just wants TWRP to be able to access his encrypted data, not to actually wipe and decrypt.
jcadduono said:
If your device isn't decrypting in TWRP, chances are you still have the old crypto key format from the 3.5.1 release firmware.
You can solve this by updating to 3.5.3 and changing your boot up password in your device OS's settings.
By changing your password after updating to 3.5.3 or newer, your OS will rewrite your crypto key to be compatible with TWRP.
You are free to disable your password after this if you don't want one, and TWRP will decrypt with the default password.
Click to expand...
Click to collapse
@zphou Did you do that stuff, like the TWRP thread tells you to?

Sounds like you need to factory reset. Thats how you remove encryption. Ive done it before on my other phone. Perhaps make a quick manual backup of the folders on your phone or use the splendid Huawei Backup app on the play store and throw that on your PC before resetting. You can restore apps to the exact state as before your reset. Encryption should be removed afterwards.

josephcsible said:
It sounds like he just wants TWRP to be able to access his encrypted data, not to actually wipe and decrypt.
@zphou Did you do that stuff, like the TWRP thread tells you to?
Click to expand...
Click to collapse
Yes. I followed the instructions and now with latest public beta, which is 7.0. I still can not access to data partition in recovery. Luckly, I could flash 3rd party rom with sideload, the only issue is not able to boot into system. So I have to flash the public 7.0 beta.

TWRP installed but asking for a password. Help required!! (Solved now!!)

While the TWRP is installed (used the one from @codeworkx) - I am not able to wipe dalvic/data/system since it is asking for a password. If the password is skipped, then while wiping it says cannot mount. Help required, if anyone faced similar issue.

debasish497 said:
While the TWRP is installed (used the one from @codeworkx) - I am not able to wipe dalvic/data/system since it is asking for a password. If the password is skipped, then while wiping it says cannot mount. Help required, if anyone faced similar issue.
Click to expand...
Click to collapse
Haven't updated on this one just yet but if you are unlocking the bootloader then you will have to disable the password before unlocking. I am currently on one by Rishabh Rao and is planning on updating today itself. Will inform you after updating.

Just updated the recovery no issue with password. Though there is another issue . It's showing all the touch logs while flashing any file normally or via ADB.

Just format the device

debasish497 said:
While the TWRP is installed (used the one from @codeworkx) - I am not able to wipe dalvic/data/system since it is asking for a password. If the password is skipped, then while wiping it says cannot mount. Help required, if anyone faced similar issue.
Click to expand...
Click to collapse
the password is usually because the data partition is encrypted, you will need to wipe data, to gain access to the data partition to be able to use it in twrp...

Even I am getting the same error, but I am just not able to get rid of it. I was on Lineage 13, then I restored nandroid backup from twrp. after that I started getting this enter password in twrp.
I tried 'fastboot format userdata' and it did nothing, then I factory reset my device from settings, but it is still asking for password.
Then I flashed stock recovery by Rishab, but I got only chinese characters in recovery and could not flash stock rom downloaded from LeEco site.
Please help!

Do you have the downloaded stock rom for le 2...if yes please share it.....

TWRP Asking for password. Please help. I've never set a password

TWRP is asking for password. I've never set a password. Please help me.

Try password as " password" , it may work !

Cyclops Maran said:
TWRP is asking for password. I've never set a password. Please help me.
Click to expand...
Click to collapse
Tell. Me exactly what u did..
Try : default_password if this doesn't work.. Then m sorry my friend u have to format full data..

Its asking for the encryption password. The default password is "default_password" (without the quotes) try that. And if doesn't work then enter Bootloader (fastboot mode) and enter the following commands into CMD.
Code:
fastboot format userdata
Code:
fastboot format cache
Code:
fastboot reboot
This will unencrypt your phone and you'll be able to boot/enter TWRP normally.
Please do note that you'll lose ALL of your data from the commands.
Also, I'm not sure about this but you also might need to flash TWRP again.

Cyclops Maran said:
TWRP is asking for password. I've never set a password. Please help me.
Click to expand...
Click to collapse
If you have set a pin as security try putting that in.
If you haven't then you can do above mentioned methods.

Finally Solved the problem! Thanks guys! I flashed my previous rom and everything worked. The problem seems to be in the twrp itself.

Cyclops Maran said:
Finally Solved the problem! Thanks guys! I flashed my previous rom and everything worked. The problem seems to be in the twrp itself.
Click to expand...
Click to collapse
How is this possible?
Firstly, if u cannot enter into TWRP, then how did you flash the ROM?
Secondly, even if you somehow flashed the ROM how does it do away the password error ?? Did it replace the recovery? Recovery image is not usually included in custom ROMs.
:cyclops:

MoonBlade said:
How is this possible?
Firstly, if u cannot enter into TWRP, then how did you flash the ROM?
Secondly, even if you somehow flashed the ROM how does it do away the password error ?? Did it replace the recovery? Recovery image is not usually included in custom ROMs.
:cyclops:
Click to expand...
Click to collapse
I know right!?
I was running out of options. i thought why don't i flash the last rom that was running on this device. i can't explain how or why. I flashed the twrp again and than the rom. i can't explain but it installed the rom. It worked.

So you froobs can't read the dm-verity warning on TWRP page and just flash the one damn zip that prevents from this.
And the problem is in Kernel and firmware
I had trust in XDA-members. But the faith is gone.

Cyclops Maran said:
I know right!?
I was running out of options. i thought why don't i flash the last rom that was running on this device. i can't explain how or why. I flashed the twrp again and than the rom. i can't explain but it installed the rom. It worked.
Click to expand...
Click to collapse
Wait, were you able to get past the twrp password thing without formatting just by flashing the rom? Why did you have to flash twrp again before the rom? Did you do a clean flash or dirty flash? Your internal drive was not wiped?
My problem is basically that I was unable to get into my phone so I deleted the 5 gatekeeper/lockscreen keys from data/system. Now I can only see the wallpaper and a blank screen that doesn't allow me to do anything. It doesn't let me allow me to set a new pin. TWRP is asking me for a password that I never set. I've been trying to figure out how to access my data without formatting, but I'm running out of options too..

CoCoGirl886 said:
Wait, were you able to get past the twrp password thing without formatting just by flashing the rom? Why did you have to flash twrp again before the rom? Did you do a clean flash or dirty flash? Your internal drive was not wiped?
My problem is basically that I was unable to get into my phone so I deleted the 5 gatekeeper/lockscreen keys from data/system. Now I can only see the wallpaper and a blank screen that doesn't allow me to do anything. It doesn't let me allow me to set a new pin. TWRP is asking me for a password that I never set. I've been trying to figure out how to access my data without formatting, but I'm running out of options too..
Click to expand...
Click to collapse
Your signature doesn't mention a OnePlus 3 or 3T. But if you're using one of these, then I suggest you try the Blu Spark 8.61 TWRP from here https://forum.xda-developers.com/on...vice-development/kernel-t3404970/post67463496
Sent from my OnePlus3T using XDA Labs

CoCoGirl886 said:
Wait, were you able to get past the twrp password thing without formatting just by flashing the rom? Why did you have to flash twrp again before the rom? Did you do a clean flash or dirty flash? Your internal drive was not wiped?
My problem is basically that I was unable to get into my phone so I deleted the 5 gatekeeper/lockscreen keys from data/system. Now I can only see the wallpaper and a blank screen that doesn't allow me to do anything. It doesn't let me allow me to set a new pin. TWRP is asking me for a password that I never set. I've been trying to figure out how to access my data without formatting, but I'm running out of options too..
Click to expand...
Click to collapse
I was able to flash the rom.

BillGoss said:
Your signature doesn't mention a OnePlus 3 or 3T. But if you're using one of these, then I suggest you try the Blu Spark 8.61 TWRP from here https://forum.xda-developers.com/on...vice-development/kernel-t3404970/post67463496
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I'm using a OnePlus 5, but the problem seems to be the same across all the OnePlus phones . Also I'm on android nougat and I didn't try to upgrade to Oreo. Is the bluespark fix for people who tried to upgrade to oreo?
Cyclops Maran said:
I was able to flash the rom.
Click to expand...
Click to collapse
Ah, thanks. Did you have to flash gapps after? I think my rom is an aroma installer.. but that shouldn't be a problem right?

CoCoGirl886 said:
I'm using a OnePlus 5, but the problem seems to be the same across all the OnePlus phones . Also I'm on android nougat and I didn't try to upgrade to Oreo. Is the bluespark fix for people who tried to upgrade to oreo?
Ah, thanks. Did you have to flash gapps after? I think my rom is an aroma installer.. but that shouldn't be a problem right?
Click to expand...
Click to collapse
No I didn't. You can always gapps afterwards.

pahapoika91 said:
So you froobs can't read the dm-verity warning on TWRP page and just flash the one damn zip that prevents from this.
And the problem is in Kernel and firmware
I had trust in XDA-members. But the faith is gone.
Click to expand...
Click to collapse
Maybe he used SuperSu to root? I dont' see a dm-verity zip for that. You have to use the bluspark TWRP posted above this reply and set your password in the ROM through another app or through the system settings in that case. I had the same problem. Also, I could have used "default_password" but I didn't know that until after I did all the fastboot flashing...
Or do you know of another zip SuperSu users can flash?

The password which its asking for is the one which is our lockscreen password
OxygenOS encryptes our devices with the password we enter on lockscreen so to decrypt just enter the same password

[email protected] said:
The password which its asking for is the one which is our lockscreen password
Click to expand...
Click to collapse
I confirm, I was stuck at this TWRP password, trying "password" and "default_password", but only my lock screen code / PIN code (they are the same for me) made it threw.

wasaru said:
i confirm, i was stuck at this twrp password, trying "password" and "default_password", but only my lock screen code / pin code (they are the same for me) made it threw.
Click to expand...
Click to collapse
thank you so much!

wasaru said:
.. but only my lock screen code / PIN code (they are the same for me) made it threw.
Click to expand...
Click to collapse
So what you're saying is, entering the very thing it was asking for works?

kunal1540 said:
If you have set a pin as security try putting that in.
If you haven't then you can do above mentioned methods.
Click to expand...
Click to collapse
That's the ticket

[Solved / Fixed ]Cannot decrypt the phone after flashing the flyme build

Hi ,
I am not a noob, but yesterday out of curiosity flashed the flyme build in the unified section. However, after the TWRP reboot to system, it did not boot. So tried to reboot the recovery and success. But the villian was there, encryption password. I tried giving my phone PIN, it said wrong password.
After half an hour, i installed the stock image(3.5.1) using the msm tool. Well it booted fine and phone is usable. Unlocked the bootloader and flashed the latest TWRP,.
The villian is back, asking for password. Now it is taking any password, always say wrong password. Ok in case i skip the decrypt screen, i cannot access the sdcard to flash new rom.
Is this the end of story of my op3t?

Have you tried "default_password"?

Didgeridoohan said:
Have you tried "default_password"?
Click to expand...
Click to collapse
Tried everything. The phone boots into OOS 3.5.1 after msm tool flash without password. Even it behaves very well. Only after the TWRP installation. It is stuck for password. I think its end of story.

Prashanthme said:
Tried everything. The phone boots into OOS 3.5.1 after msm tool flash without password. Even it behaves very well. Only after the TWRP installation. It is stuck for password. I think its end of story.
Click to expand...
Click to collapse
Then I don't know... Usually if TWRP suddenly starts asking for a password without having set one, using "default_password" will work.
You could try flashing a kernel that disables forced encryption and then format data to unencrypt.

You have to make sure to restore system to the version using the same encryption libraries as used the last time you could decrypt the data partition. If all fails you will have to format your data partition and loose it all.

pitrus- said:
You have to make sure to restore system to the version using the same encryption libraries as used the last time you could decrypt the data partition. If all fails you will have to format your data partition and loose it all.
Click to expand...
Click to collapse
I have already lost the data. TWRP not allowing me to enter the sdcard storage to flash anything. Can u brief me how to format the data partition.

Just bootup phone into fastboot mode from the unlocked bootloader menu, then connect to PC and run "fastboot format userdata" from a path with either fastboot in or anywhere of you've added the folder with fastboot in you PATH variable.

pitrus- said:
Just bootup phone into fastboot mode from the unlocked bootloader menu, then connect to PC and run "fastboot format userdata" from a path with either fastboot in or anywhere of you've added the folder with fastboot in you PATH variable.
Click to expand...
Click to collapse
Did this. But after should i flash the stock image again? Because system is not booting and stuck in oneplus logo.
How about fastboot erase options?

I disabled encryption one year ago to avoid this problem, and therefore have never experienced it. But why don't you do a compete MSM restore? That should restore even the data partition.

pitrus- said:
I disabled encryption one year ago to avoid this problem, and therefore have never experienced it. But why don't you do a compete MSM restore? That should restore even the data partition.
Click to expand...
Click to collapse
Let me try once i go home and update u. Thanks for the response..
Will format the data from fastboot. and flash the stock image. Hope this works.

Finally happened to work.
Installed a different version twrp made the trick. But this time i erased the recovery and flashed again. After that wiped all the data and then sideloaded the rom from adb and it did the trick..

pitrus- said:
I disabled encryption one year ago to avoid this problem, and therefore have never experienced it. But why don't you do a compete MSM restore? That should restore even the data partition.
Click to expand...
Click to collapse
Can you please tell me how you disabled encryption?

Vidicgapi said:
Can you please tell me how you disabled encryption?
Click to expand...
Click to collapse
You do this by flashing the latest no-verity-opt-encrypt zip file after formatting the data partition and also after each update of the OS.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip

Official TWRP 3.2.3-0 for Essential PH-1

I bought an Essential during one of Amazon's sales and I have finally produced a working, official TWRP for the device. I tested it on Essential's 9.0 official firmware with August security patches. Touch works and TWRP is able to decrypt your data even if you have a PIN / pattern / password set. MTP may or may not work, depending on what kernel you are using. The screen is still not using the right-most edge of the screen, but I've implemented a few dirty hacks that I will clean up later to make TWRP fit the screen better. It is NOT recommended to use custom themes at this time on this device due to the screen weirdness.
Since the Essential is an AB device that does not support fastboot boot, you will have to flash the initial TWRP image to the boot partition. You can either switch slots following the instructions on our website or download the latest factory image or make sure you have a recent copy of your current ROM so you can reflash the boot image. Take your pick. Especially for your first install, I recommend doing the install when you are close to computer so you can fix anything that may go wrong.
https://twrp.me/essential/essentialph1.html
#TWRPisEssential

Reserved.

Thank you more than you'll know man!!!!!

Fantastic! Thanks for the support

Sick! Thanks man!

Good deal, how does it handle September patches?

Forgive me if I'm missing something here, but does this mean it will always be on a slot?

hottcakes said:
Forgive me if I'm missing something here, but does this mean it will always be on a slot?
Click to expand...
Click to collapse
Edit
Proper thread with install instructions.
https://forum.xda-developers.com/essential-phone/how-to/guide-how-to-install-twrp-root-t3841922
edit end
how to install
fastboot getvar current-slot
say you get a
fastboot flash boot_b twrp.img
fastboot --set-active=b
now if you use volume rockers to go to recovery and then press power button to select you should boot into twrp.
Once in twrp, flash the twrp zip file.
then go to reboot. and change slot to a.
now reboot to system and you should boot into Android and you should also have twrp on both slots.
if you get current slot as b, then use "a" slot to flash twrp image.
video for those who need one. Also, has root instructions.
https://www.youtube.com/watch?v=7PYBYDbapho

@Dees_Troy thank you very much, this is greatly appreciated!
By the way, should the time zone work?
Thanks again!

If I have fingerprint/pattern protection, when I boot into twrp what will I see? Option to decrypt and continue without having to enter anything (I hope)? I don't want to be surprised and not know whether to continue or not.
Edit: Thanks for doing this!!!

Awesome!! Thank you so much!!
I am happy to report the touch screen in TWRP works fine with the September release.
NOTE: If you have MAGISK installed, you must install the stock boot image (to both slots), then install the TWRP patcher zip, and finally install Magisk LAST or the phone will continue rebooting into TWRP.
So once you are in TWRP, flash stock boot image, click reboot (don't actually reboot) and change to other slot, flash stock boot image, then flash TWRP installer zip, click reboot (don't actually reboot) and make sure you are on the slot your started with, now flash Magisk and reboot phone.
I only have one issue: if you have a pattern set for your lockscreen, TWRP will still prompt you for a password. So before booting into TWRP, change your pattern to a password (this way you don't lose all your stored fingerprints) and after getting back into Android, change back to your pattern. It decrypts perfectly fine with the lockscreen password; it just doesn't prompt for a pattern when a lockscreen pattern is set.
And a second very minor bug is the time and date shown in TWRP is incorrect.
Thank you again soooooo much!!!!
Edit: I found a fix for the issue with not being prompted for a pattern and being prompted for a password instead, even though you have a pattern set! The fix is if you have a lockscreen pattern, change it to a lockscreen password, boot into twrp, type your password (be very careful when you are typing because the screen and touch are sligly mis-aligned so look at the actual keys being pressed), reboot into Android, change your password back to a pattern, and now everytime you boot into TWRP, it will prompt you for your pattern. So, apparently, the pattern has to be set AFTER twrp is installed for twrp to recognize you have a pattern set and prompt you for it.

I had to remove Magisk before I could get twrp to stick. With Magisk I would just reboot back into recovery. Once the procedure is done with stock boot img you can reboot into recovery and flash kernel and magisk as you normally would with TWRP.
I should add that it also won't decrypt for me but not as big of a deal if you forget like it was when you had to flash a boot.img again with a PC.
Nice to have TWRP on a device again. Android doesn't feel right without it.

I know there is a thumbs up for the thanks but a it's also nice to hear. A sincere thanks to you and whoever might of helped along the way!

Ok so I'm going to ask is this permanent even if we flash a different rom or kernal to ethier slot

munchy_cool said:
how to install
fastboot getvar current-slot
say you get a
fastboot flash boot_b twrp.img
fastboot --setactive=b
now if you use volume rockers to go to recovery and then press power button to select you should boot into twrp.
Once in twrp, flash the twrp zip file.
then go to reboot. and change slot to a.
now reboot to system and you should boot into Android and you should also have twrp on both slots.
if you get current slot as b, then use a slot to flash twrp image.
Click to expand...
Click to collapse
Thanks this helped just one correction in the 2nd command fastboot --set-active=_b

gorm said:
Thanks this helped just one correction in the 2nd command fastboot --set-active=_b
Click to expand...
Click to collapse
Fastboot -ab accomplishes same thing. Use fastboot -aa for a slot.

Str0ntium said:
Fastboot -ab accomplishes same thing. Use fastboot -aa for a slot.
Click to expand...
Click to collapse
Good to know, thanks
Just nice to have a working TWRP .
Great day for future Essential Development:good:

galakanokis said:
I had to remove Magisk before I could get twrp to stick. With Magisk I would just reboot back into recovery. Once the procedure is done with stock boot img you can reboot into recovery and flash kernel and magisk as you normally would with TWRP.
I should add that it also won't decrypt for me but not as big of a deal if you forget like it was when you had to flash a boot.img again with a PC.
Nice to have TWRP on a device again. Android doesn't feel right without it.
Click to expand...
Click to collapse
I had a tough go at it also, having magisk already installed. Finally got it after a few trial and errors. And I have no decryption either... Something with magisk, perhaps? Either way, glad to have twrp back...

Wondering if this can now be modified to replace the ramdisk stock recovery for a permanent installation finally. Does this still rely on the Nougat kernel? I know building twrp on newer oreo kernel sources resulted in the touch driver not working at all.

Touch is not working for me, I'm on Sept security patch.