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.
Related
I'm having a major issue with installing a new rom. I currently have the Cyanmod on my phone. I wanted to change to a new rom, So I did the normal steps and was able to install the new rom. However, once my device booted up, it ask for a encrypted password. I know I didn't have a encrypted password set previously, So I tried restalling, wiping everything, and etc. Here is the weird thing, whenever I reinstall my previous rom cyanmod everything goes back to normal. I'm able to boot up and I don't have an encrypted password. Anyone have any solutions for this?
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.
Had a custom Stock LG ROM on my phone, decided I wanted something a lot lighter and faster so I went with resurrection ROM, everything went went fine during the install, wipe everything did the usual stuff, but pin lock doesn't work at all.
I set it up, but it doesn't work, when I go to change it the after entering my pin the settings just crash for the lockscreen security which is odd.
I think my pin is working but not actually being displayed?
So, I have a rooted OnePlus 3 with CM 13.1 Snapshot. But wanted to try CM 14.1. So I wipe Cache, Dalvik, Data and system, and install CM 14.1 nightly. After messing with it for a few days its was not daily driver ready for me. So same ting and install CM 13.1 back.
Now, I setup phone and all. I want to go back to TWRP to flash Exsposed. Suddenly it asks for a password (said no thanks in setup) so I assumed it would be my pin, but that was incorrect. I started the phone back up and asked for a start-up pin (even I said no thanks in setup) but that was my pin. So I tried to chance it into a pattern and hoped it would update in TWRP.
I go back to TWRP still incorrect, I go start my phone back up, but now it saying that the startup pattern is incorrect. I'm 100% sure is correct.
Now I can't enter TWRP and/or my phone.
Please help me, thanks.
Did u happen to restore from backup ?
You need clean install, else the pin information might had an issue,
This issue presence in 3.0.2.0 TWRP not sure whther it's been fixed or not.
Solution is dont use PIN (remove it) prior to doing backup
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
furiify said:
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
Click to expand...
Click to collapse
Same problem
i delete /data/system/locksettings.db with twrp file manager to get rid of this problem but i can not lock because all lock types freezes.