I have installed TWRP and rooted my 3a XL and would now like to change the boot password to a phrase rather than the PIN used to lock the display. This worked fine on my old phone running Android 7, as well as on my tablet running the same version. The software I used, cryptfs password, however, does not work on Android 9 (the software was last updated 2016).
Is anyone using some other software to accomplish this? Just to be clear, I want the display lock PIN to remain as it is and only change the boot password.
Related
Hi, I made this thread in a different section and haven't gotten an answer, so might've been in the wrong place.
I have for the first time rooted my HTC Desire. And for the first time also just installed a ROM, LeeDroid 3.0.6-R2. Everything works fine, so I think, but one thing.
I've set up my Exchange account to my work and entered a new pin code. The pin code works every time when the phone locks and I need to enter the pin to unlock it. But as soon as I go into Clockwork Recovery mode and then do nothing but restart the phone, it doesn't accept my pin code. After 8 failed attempts it wipes my phone automatically.
When it happened the first time I thought I messed up with the pin code. So I wiped the phone and started over (not reflashing the ROM), setting up Exchange with the same pin code. But it didn't accept the one I used previously. So I choose a new one, simple, 0000. Tried several times to unlock with the pin after the phone had locked. Then just now I rebooted again with Clockwork Recovery and just restarted the phone and it again won't accept my pin code.
I don't want to disable the policy and not have a pin code via some app.
Has anyone had this issue before? It's like my pin code isn't saved once I go into Recovery mode. But it still enforced the policy.
I've also tried just adding the pin code lock, without activating the ActiveSync, and that also gives me the same error. One time I managed to make it work. I set the pin, reboot normaly which worked ok, then go into recovery and reboot. It worked. But the 2nd time i went into recovery mode it stopped working again.
Any suggestions or help is appreciated.
TIA
I'd post this problem directly in the LeeDroid thread. You might try out another ROM, but it sounds like a ROM issue.
Gangir said:
Hi, I made this thread in a different section and haven't gotten an answer, so might've been in the wrong place.
I have for the first time rooted my HTC Desire. And for the first time also just installed a ROM, LeeDroid 3.0.6-R2. Everything works fine, so I think, but one thing.
I've set up my Exchange account to my work and entered a new pin code. The pin code works every time when the phone locks and I need to enter the pin to unlock it. But as soon as I go into Clockwork Recovery mode and then do nothing but restart the phone, it doesn't accept my pin code. After 8 failed attempts it wipes my phone automatically.
When it happened the first time I thought I messed up with the pin code. So I wiped the phone and started over (not reflashing the ROM), setting up Exchange with the same pin code. But it didn't accept the one I used previously. So I choose a new one, simple, 0000. Tried several times to unlock with the pin after the phone had locked. Then just now I rebooted again with Clockwork Recovery and just restarted the phone and it again won't accept my pin code.
I don't want to disable the policy and not have a pin code via some app.
Has anyone had this issue before? It's like my pin code isn't saved once I go into Recovery mode. But it still enforced the policy.
I've also tried just adding the pin code lock, without activating the ActiveSync, and that also gives me the same error. One time I managed to make it work. I set the pin, reboot normaly which worked ok, then go into recovery and reboot. It worked. But the 2nd time i went into recovery mode it stopped working again.
Any suggestions or help is appreciated.
TIA
Click to expand...
Click to collapse
I had a similar sounding problem when I upgraded from LeeDroid 2.3d to 2.4.1.
The flash worked ok and all seemed good.
I then rebooted and was no longer able to enter the device PIN (not the SIM PIN).
I had been restoring all applications and all system data using Titanium backup.
Looks like not a good idea. had to re-flash. Just restoring Missing applications
was ok.
Could this be your problem?
I have done it a few times by restoring from Titanium Backup. But I've also tried just after I flashed the phone and nothing else but enter a pin code and it still wouldn't work after I rebooted from recovery.
I also thought about that I restored from Titanium. Perhaps the old accounts or something like that. I have now not rebooted my phone for a couple of days since I fear it will bugg out again.
Hello,
I'm having a weird issue with my Note 7 that I didn't have at all until tried to root for the first time....
It randomly restarts, sometimes is very often and sometimes it take a few hours to do it, but when it does it just restarts out of nothing and when Android loads again it asks me for a password that doesn't even exsits
"To start your device, enter your password" (Picture attached)
This started to happen after used the rootable kernel that was published before SuperSU 2.77 Beta but even reflashing the stock firmware, bootloader, modem, CSC it keeps doing it even when my Android is not yet configured (at the first Welcome screen before setting the phone up), so there is no password at all at this point. I've tried my Google account password, but it doesn't work.
This message is the same that comes up when you select "Secure Boot" so you need to enter a password or PIN to decrypt your data and be able to load it, but I don't have that option checked, and could not be checked when the phone is not even configured.
The way to work around this issue is flashing the no-verity-opt-encrypt mod that is not supposed to be needed anymore after SuperSU 2.77 has been released. So flashing this mod will get me into my Android home screen but it will eventually restart again and I need to flash this mod again.
This is what I've tried so far and it keeps happening:
- Flashed the rootable kernel when it was published and the no-verity mod. I formated data as indicated in the post. Then this problem appeared.
- Flashed stock firmware, bootloader, modem, csc thinking this would remove any trace of the mods I flashed, but kept happening.
- Factory reset from the Samsung recovery, had the "no verity" errors sometimes and sometimes not.
- Flashed other firmwares, bootloaders, modems, csc from other countries but for the same model N930F and kept happening.
- Flashed custom ROMs, formated system, data, everything.
- Flashed stock firmware again.
- Flashed custom ROMS again with the new SuperSU 2.77 and keeps happening.
I have done every single flash that actually exists for the Note 7 and formated everything with no luck....
Has anyone have this issue or had it at all at some moment? If so... How did you manage to get rid of this message?
I hope someone can help, If it was faulty phone I think it would restart at any point even in Recovery or Download mode, but only happens inside of Android.
Seems a common problem I think?
http://forum.xda-developers.com/showthread.php?t=3444510
Sent from my Nexus 6P using Tapatalk
Yep, saw that post... But never seen anyone complaining about the phone asking for a password when reboots (only when it crashes) its like it was asking for a password to decrypt the phone.
Hello,
I have recently flashed the Marshmallow update to my phone coming from WW-2.20.40.194. It was encrypted and used a PIN on both the boot and the lock screen. With Lollipop, I can decrypt my phone in TWRP by entering my lock screen PIN. However, neither TWRP 3.0.2.0 nor a TWRP repack (found at: https://drive.google.com/drive/folders/0Byp0425xydUaYzk1anRCak0zZXc) on Marshmallow are able to decrypt the phone, saying the password is invalid. I have tried the lock screen PIN, "default_password", as well as using an app called "SnooperStopper" to change my encryption password to something other than my lock screen PIN, with no luck. Is anyone else experiencing this or have a fix?
If i recall you must unencrypt before any flash. Your encryption key is now lost along with all your data. Sorry.
Sent from my ASUS_Z00AD using XDA Premium HD app
Maybe you'll need to downgrade to L, decrypt the phone, upgrade to M again and encrypt it a second time.
After uploading the M update, Asus also uploaded a rom to downgrade from M to L, so anyone can perform a downgrade just the same way they did the upgrade.
Thanks for the replies! I haven't lost any data, since I backed everything up manually beforehand. However, even if I didn't backup the data, I can still unlock the phone itself (get past the lock screen and to all my files), just not through TWRP's lock screen. I've tried encrypting before and after upgrading to Marshmallow, with the same results.
UPDATE:
Just tried again with TWRP (tethered and untethered) on a clean install, same results. Steps:
Used fastboot to completely erase phone (data, cache, dalvik, system, etc).
Flashed stock recovery for Lollipop (WW-2.20.40.194).
ADB sideloaded WW-2.20.40.194 in stock recovery.
Wiped data and cache again in stock recovery.
ADB sideloaded Marshmallow (WW-4.21.40.134).
Rebooted to system, logged into Google account, set up system, etc.
While setting up system, chose to lock device with PIN.
After setup, encrypted the phone.
Rebooted to bootloader.
Fastboot boot TWRP.
Tried to enter PIN, says invalid. Tried to enter "default_password", says invalid.
Fastboot flash TWRP, same results.
Hi yes, ive had the exact same problem running a nightly build of CM13 / Android 6.0.1. It just tells me the password is wrong. TWRP 3.0.2.0
Personally I think something changed in recent Android builds and TWRP just hasnt figured out that its broken yet. TWRP 3.0.2.0 is almost 6 months old now ...
I need to find a way to update my roms also so this is a problem.
I am glad to hear it is not just me having this issue. I believe this as well, though TWRP 3.0.2.0 worked just fine on an older version of XOSP (CM13-based, I think from a build around December 2015). Something must have changed since then.
I have discovered the problem. You can read all about it here.
http://forum.xda-developers.com/gal...wrp-mount-encrypted-partition-recent-t3468989
tl;dr
Snapdragon 800+ CPU phones (any maybe others) have HW_Crypro (hardware crypto chip) and Android 6 + enables this. Which requires recompiled TWRP with support for HW_Crypto
Doesn't the last TWRP 3.2.3 solve this issue
https://dl.twrp.me/Z00A/
Or have you find a working TWRP build that can decrypt?
Running Pixel Experience ROM. I always used TWRP but due to changes in the ROM in an update 2 months ago I had to install Orange Fox. All worked well. Trying to install latest update, but when I now reboot in recovery it asks for encryption password. I've tried my screen pin but that's not accepted.
I don't want to format my data partition.
Then, install TWRP again, which worked fine before, but now has the same problem: Asks for encryption password.
How can I fix this please?
Hi!
After the last update to Android 9 my phone doesn't recognize unblock pin at all.. pin is correct, i have the same one on several devices.
Phone is full stock, blocked boot, never rooted, no usb debugging enabled.
Now i can only receive calls..
I've tried to reflash last stock ROM 10.4.1.0 by "mi flash pro", but it's not possible cause the status of ROM was changed to beta.
What else can i do to unblock?
I can't reset or wipe, it contains indispensable files and apps.
Thanks a lot to community for any help.
Do you mean you can't pass the lock screen?