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?
Related
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
[Q] Get "type password to decrypt storage" while trying to install custom ROM
I can access the modified bootloader (TWRP). While in the modified bootloader, I can press "install" and see the files in Internal storage. I additionally instaleld the Slimkat version. However, when I try to boot into the device, I get type password to decrypt storage. I have never explicitly set any password!
I have previously flashed my moto g and Lg device, so I'm not a complete neophyte. At the same time, I'm nowhere near the initiated and hence religiously follow the guidelines while trying to flash.
Now, the device is using f2fs because when I try to wipe data, it formats it with f2fs. Additionally, on bootup, Slimkat animation is showed instead of stock, so something seemed to have gotten installed.
Is my device bricked? I can't seem to find many valid resolution methods.
Should I try going back to stock with the nexus Rootkit? Any advice on what I can do here?
Ps. There is no data on the device worth saving.
Additionally, my device is in its warranty period, so if I cannot unbrick it, is there anyway to 1) flash stock and lock bootloader so that I can claim the warranty?
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
Hi,
sorry if that question has been already answered, but I cannot find an clear answer
I need to encrypt my cell phone, however each time I try I get an error telling that the encryption
did not finished correctly, and my cell phone is corrupteur and need to Factory reset
Is there a 7.1.2 Rom that exists with encryption working ?
if not do you know if a 6.x Rom exist that's support encryption.
Many thanks for your help.
I finely found a way to have ZUK Z1 encrypted under 7.1.2.
Below steps used:
Factory restore using All in One tool
Flash TWRP Official 3.0.2
Using TWRP installation of a 6.0 ROM
After boot and setup, enter Preference/Security/Encrypt
At this point ZUK Z1 appears encrypted
The issues are that under TWRP unable to mount or see files
I flashed lineage and open_gapps using the “adb sideload” option.
After a reboot, ZUK Z1 appears as encrypted
For the time being all is working fine, except the fact that TWRP cannot mount the device, because it’s encrypted. I guess that’s an issue with TWRP itself. I don’t know if a version exists to fix this ….
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Ecoka said:
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Click to expand...
Click to collapse
The 6.0 ROM that's worked for me was " Temasek-20160217-NIGHTLY-ham "
Make sure you fully factor restore using the All In One tool
boot your phone on V5 and setup your cell phone account
Then using TWRP install V6 ROM with the Temasek one.
then Encrypt your phone .... that's should work ok
then us "adb sideload" to inject the V7 Lineage ROM
Let me know at which step you are stuck !
Hey, sorry for long delay ...
It will work up to "Temasek-20160217-NIGHTLY-ham", flashing AOSP 4.6 (Android 7) by sideload will cause "Password wrong" problems while booting
decrypting data partition. Still hope to get a way working zu install AOSP 5.1 (Android 8.1) with full encryption. Tried TWRP 3.02 and newer 3..2.1.
no worry about "password", I already installed nightly build of Lineage without issues using sideload.
Of course I got the message about password, I just ignore it
the only point is that I had to install TWRP V2.8.7 and not 3.x. because with 3.x sometimes I was not able
to boot recovery mode.
Before each install I fully backup my cell phone in case of .... SMS, Pictures etc...
Good luck,
The problem is not the password while starting to recovery 3.x.x, its the password while booting...
1. Factory restore using All in One tool (okay, works)
2. Setup Phone and encrypt (works, okay - Password will be accepted)
3. Flash TWRP (3.02 / 3.2.1.0) - tried both (okay, works - Password for encryption Recovery will not be accepted
4. I skip that and sideload flash (clearing cache etc.) "Temasek-20160217-NIGHTLY-ham.zip" (okay, Recovery = not, While Booting = Password accepted) (I choosed PIN and something like : OfferMe#1963ZU several times)
5. I skip Password in Recovery and sideload flash (clearing cache) "lineage-14.1-20180124-nightly-ham-signed.zip" (okay, Recovery still not, While Booting = Password NOT accepted)
Seems no matter if Lineage ROM 14.1 or higher...
Still confused
I am not using password at boot. I only set a password to unlock the phone after boot.
I'm on MIUI 12, I'm not able to install TWRP recovery properly.. internal storage is encrypted.. not able to flash anything. anyone has a solution ? thanks in advance !
Harshadd30 said:
I'm on MIUI 12, I'm not able to install TWRP recovery properly.. internal storage is encrypted.. not able to flash anything. anyone has a solution ? thanks in advance !
Click to expand...
Click to collapse
When, entering TWRP, it asks you for PIN/password.
You have to enter your pin/password you have defined in Android for unlocking the screen.
TWRP must then confirm that it successfully decrypted for user 0 (for user 999 it would fail, do not wory about)
This is really nothing new, but you must not use an outdated TWRP that does not ask or does not support it properly
If having problems, reboot to Android and reset your pin/password.
Some TWRP versions may not support properly if you use pattern in Android - hence better switch to pin.
However, if you cannot make it with pin, reboot again to Android, redefine to pattern and try
zgfg said:
When, entering TWRP, it asks you for PIN/password.
You have to enter your pin/password you have defined in Android for unlocking the screen.
TWRP must then confirm that it successfully decrypted for user 0 (for user 999 it would fail, do not wory about)
This is really nothing new, but you must not use an outdated TWRP that does not ask or does not support it properly
If having problems, reboot to Android and reset your pin/password.
Some TWRP versions may not support properly if you use pattern in Android - hence better switch to pin.
However, if you cannot make it with pin, reboot again to Android, redefine to pattern and try
Click to expand...
Click to collapse
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Harshadd30 said:
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Click to expand...
Click to collapse
Make sure you use the latest official TWRP for davinci
Which "notifications" - it's about Passwords and Security in Android. You can try by removing Android unlock pin/pass, reboot to Android and set it again and then try with TWRP.
Again, make sure you use up-to-date TWRP, best the official
twrp-3.5.2_9-0-davinci.img (if you were not familiar with and TWRP does not ask, maybe you are on an ancient and maybe some unofficial TWRP)
HI, I updated to V12.1.4.0.RFJMIXM and tried to install the latest TWRP but booting into recovery mode TWRP is in this like read only mode and dosnt bring up the usual thing to decrypt your files. It says unmodified system partition. Keep system read only? TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root your device. Then it says keep read only or swipe to allow modifications. Any suggestions? Tried removing and adding security pin but didnt work
I need it to install magisk. I tried patching a recovery image with magisk which worked. But trying to boot to magisk with recovery dosnt work. I hold the keys and then when it vibrates let go but it always goes to stock recovery. Not system with magisk as it talks about.
Harshadd30 said:
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Click to expand...
Click to collapse
This seems like a bootloop. Did you change any roms before this happened? You might have to format (not wipe) your data partition which unfortunately will also delete all your files from the phone's internal storage.