I updated to the mixrom TWRP via Flashify in order to flash updated ROM.
Once in TWRP (it took password fine during first loggin) I:
Cleared Cache and Dalvik
Flashed Rom
Flashed new Gapps (failed)
Flashed kernal patch (for trinity)
Flashed Kernal
Flashed SU
Rebooted
When I booted phone prompted to enter "Enter password to decrypt storage" it is telling me that it is the wrong password. I've never had any issues until today that I flashed 4.4. I know it is the correct password. I tried going back into TWRP and when I am prompted to enter the password, it says Failed and I am unable to see my files.
Can someone guide me as to how to correct this hiccup?
TIA
Does anyone know how to at least be able to extract the files?!?! I am desperate
Related
Hi All
I upgraded my Note 3 (HLTE 9005) from CM11 latest snapshop to the latest CM12 nightly.
I did full wipe before installing CM12.
My device was encrypted when using CM11 and on CM12 I did not make any change on the encryption (password etc)
On CM12 in the Security page I can see that the device is listed as encrypted.
This all is good, however I have an issue if I restart phone in recovery then I am unable to decrypt the device.
Error I get is that The password is incorrect.
Surprisingly if I now restart the phone then the phone starts properly in CM12 - without having to enter the password to decrypt the device.
So essentially I am not able to use TWRP anymore but can use CM12.
I am not sure what is wrong here or what I should do to get TWRP working again.
Any help - will be much appreciated!!
Thanks
Chirag
Goto Settings->Security->Screen Lock and select Password. Enter you Password and you should be prompted with an option to require password at boot, select that. Reboot into recovery and try again.
Same issues?
Heya,
I decided to nuke my beloved OP2 and start anew, this time including encryption. As I read in the encryption Q&A, the device should not be rooted when doing the encryption, as this can cause havoc.
If you want, you can skip the Italic part. Lets just say, all went well until I rebooted into recovery after setting my encryption password.
- I wiped everything, installed Oxygen OS 3.0.1, flashed the TWRP recovery image (which was recommended in the "how to install oxy 3 on OP2" guide. So it should be a compatible version).
- I boot up my phone and go to the android security settings. I put my phone on the charger and let it encrypt my system with the on-board encryption function. Everything goes well, device reboots fine, now encrypted.
- I went to the security settings again to set my password. I check "ask this password before booting". Now that the encryption is dealt with, I want to have my device rooted. I boot up into TWRP and, as expected, TWRP asks for the password that I just configured.
BUT TWRP won't accept my password, telling me it was wrong. I tried several times, checked that I didn't mess it up because of a foreign language (english) keyboard. When I rebooted the device, it accepted my password on the first try, booting normally afterwards.
I went into the security settings and chose a pattern instead of a password, to make sure the keyboard wasn't the cause of the failure. When booting into TWRP, it asks about my pattern now. But it doesn't accept it.
So I went back into the security settings and unchecked the "ask pattern before boot" part, hoping that TWRP might not need the pattern anymore. When I boot into TWRP now, it asks for a password again, although I have enabled a pattern only.
I rooted my devices several times already, without any problems. This is the first time that I use encryption, so I have no Idea what could be the cause of this problem. It just seems that TWRP has problems decrypting the OxyOs. Please keep in mind that I used the TWRP image that was recommended for OxyOS 3.0.1 in the official Oneplus Forum install guide, so it should be compatible with all the Software and Hardware.
Now that I can't access anything with my TWRP, I haven't installed my SuperSU yet. I can't see how I can gain root access without using TWRP. If I rooted the device first and then encrypted it, the TWRP problem would not matter, but that's exactly the thing that causes HAVOC.
Looking forward to ideas
Fennec
Edit: My progress:
- tried adb sideload the supersu.zip over the stock recovery (update from usb). Protocol error. Installation failed.
- tried all kinds of TWRP versions, starting at the newest 3.0.2. TWRP 3.0.2 claims to have solved the encryption issue, but when flashed I get a bootloop whenever I try to enter the recovery.
- I realized that my adb sideload failed because I used an old version of adb which I found on my laptop. The newest version managed to sideload the supersu and the xposed framework, giving me root rights. TWRP still does not work but at least I got root now :/
same: TWRP can not decrypt system partition on One Plus One, CM-13 and TWRP 3.0.2-0
I remember TWRP said: installation was not successful although it can boot into recovery...
Try fastboot official twrp-3.0.2-2 for me is working fine.
Remember to boot in recovery after flash
Sent from my ONE A2005 using Tapatalk
Hey guys,
I recently flashed to cm13 from the Android N Developer Preview and I formatted the userdata partition in order to decrypt the phone afterwards so TWRP could access /data but each time I boot up it's reencrypted. Any thoughts? I can't use TWRP at all to install zips or anything like that while the device is encrypted - it requires a password to decrypt /data. I've tried default_password, my pin, and rebooting before setting a password and none have worked. Please help I'm slowly dying without xposed. Also I'm not coming straight from the Android N Preview; I downgraded to M in order to get the right vendor image via the OTA update because when I tried to flash cm straight from the preview I got in a boot loop due to not having the right vendor.img if that makes any difference.
Alex
touchmywillis said:
Hey guys,
I recently flashed to cm13 from the Android N Developer Preview and I formatted the userdata partition in order to decrypt the phone afterwards so TWRP could access /data but each time I boot up it's reencrypted. Any thoughts? I can't use TWRP at all to install zips or anything like that while the device is encrypted - it requires a password to decrypt /data. I've tried default_password, my pin, and rebooting before setting a password and none have worked. Please help I'm slowly dying without xposed. Also I'm not coming straight from the Android N Preview; I downgraded to M in order to get the right vendor image via the OTA update because when I tried to flash cm straight from the preview I got in a boot loop due to not having the right vendor.img if that makes any difference.
Alex
Click to expand...
Click to collapse
You have to flash a modified boot img. The official one automatically encrypts your phone.
Where would I find one? I found one but it just put me in a boot loop. Is there a thread for that on here or any good places you know of?
If flashing zips is the only thing you are concerned about you could give flash fire a try. It worked great for me to flash some zips in nougat.
So, last week i installed 6.0 CM 13 android, I've encrypted the phone and everything was fine, two days ago I've installed new ROM (also android 6 cm13 ) and phone was still decrypted, after boot i was asked to enter my password and everything was fine.. .Today I've restarted my phone and when I try to enter password after boot it says that PIN is wrong.... I've tried to do WIPE from TWRP but it says that cannot mount partition ( TWRP asks for password too)..
What can I do? Sorry for my bad English.
Flashing the stock ROM might work. But you'll use everything.
Hello Guys
So i was trying to update my rooted Decrypted Nexus 6P from 7.0 to Developer preview 7.1 .
I followed the instructions to flash the OTA zip and then root it with SuperSu (http://forum.xda-developers.com/nexus-6p/general/available-android-7-1-developer-preview-t3483739).
I then flashed Franco's latest kernel as I usually end up doing that. The phone booted fine, but of course the camera had some problems as reported here (http://forum.xda-developers.com/showpost.php?p=69226309&postcount=373) which meant that the Franco kernel was at 7.0 and I needed 7.1 kernel.
So stupidly enough I just extracted the boot.img from the 7.1. OTA zip and flashed it through flashify app to revert to stock kernel for 7.1 and just re-started my phone.
But since that boot img was not patched it forced encryption on the phone which I did not realize until I found the phone was sitting at the boot animation for a long time and I just force re-started it.
Wrong decision . Now I have a phone that boots up to a screen which says Encryption Unsuccessful and has a button which asks me to wipe all the data.
Booting into TWRP asks me password for decrypting the data partition which I assume would be my PIN and supply it, but it sits on message saying 'Decrypting data' and just sits there endlessly. I have tried this as well (http://forum.xda-developers.com/showpost.php?p=66163153&postcount=826) i.e. trying the 3.0.0.1 twrp but that one does not like the PIN that I supply.
I followed this (http://forum.xda-developers.com/verizon-htc-one-m8/help/decryption-unsuccessful-currently-t3074855) to extract the whole data partition from my phone and essentially I have this 58 GB file which i tried to mount in Linux but unfortunately there is nothing that i see in that partition.
Is there anyone who has encountered this and has successfully retrieved their data??? I know it was stupid of me that I didn't take a backup of my internal storage plus the nandroid backup I had is on the phone .
Any help is much appreciated.
Thanks