Hello! I faced an issue after flashing rom (did it million times before). I had Chinese stock ROM and decided to move to regular worldwide stock rom. I used TWRP 4.0.0.
I flashed the rom, rebooted, system asks for decryption password as always (PIN appeared somehow a long ago and it was pin of mine), but pin is incorrect. I didn't change pin at all. I didn't have even pin on latest rom, but somehow it is changed. The same in TWRP, I cannot access TWRP now. I tried "default_password", tried my old pin which I was used, but no luck. What can I do in this situation?
Related
Background details:
- I had a good working Galaxy S4 running Stock 4.4.4, with Root/Safestrap/TWRP (Phone was not encrypted)
- I rebooted into Safestrap and did a full TWRP backup to my ext SD card [fat32]
- I tried to install CM-12 zip via Recovery Mode, but I think I missed a step and something didn't work out. So I,
- Rebooted back into Safestrap and selected "Restore" from the options. Restore ran for a while, rebooted and restarted successfully.
Now here's the strange part. Restore appears to have completed successfully because I can now see my original wall paper and the unlock screen. BUT my 4-digit numeric PIN doesn't work to unlock the screen. And it looks like wifi and cell phone service aren't connecting. So I"m stuck. I've tried the known-good PIN multiple times, but same results.
I guess I could Odin back to stock and go through the process of installing all my app's and setting them up, but I really don't want to do that.
Any idea why my PIN would not work or would have changed?
Which Version of TWRp do you use?
I remember that it's a known problem with some Version and the only way to prevent it, is to reset the PIN before backuping.
But you could try to delete the /data/sytem/locksettings.db to reset your PIN
If that not works try to delete the .key files in /system/data and create a new PIN after rebooting
Hi all. had an issue while trying to load up LinageOS last night. Was having trouble with keeping root. Seem to have solved that by using Magisk 11.6 and the SUaddon rather than any superuser version.
Anyhow as part of this i went back to a TWRP backup of which i had 3 different versions (stock and lineage) available being a bit ocd with backups. They all flashed ok, but for ALL of them, when the phone booted it kept telling me had wrong pattern when i tried to unlock. Not good. Thought only way back was to factory reset and do all the app loading and setup again.
After a bit of searching found this thread and this post.
https://forum.xda-developers.com/showpost.php?p=69189392&postcount=65
Worked a treat.
The other methods didn't and i suspect are obsolete.
Anyow, posted for info if anyone else runs into this problem. Success dependent on having working TWRP and being able to boot to that as you need to use the File Manager capability in TWRP.
Seeyahs!
Same thing happened to me last week, when I tried lineage, found the answer on HTC forum,.
So avoid that from happening , before you make a backup, unlock all securities( pin, password, fingerprint) then make a backup, next time you restore your backup, it will boot without any issues.
ta for that. will try.
I got a notification for system update. When I rebooted, my tablet started up in TWRP. The update finished (I don't Know if it was successful or not). After I rebooted into system, my usual PIN is not working, do I can't get access. I'm away from home and away from my PC for a couple of weeks, so I'm limited in what I can do.
Does anybody know how to get a PIN to work? Looks like TWRP has been replaced with regular recovery on partition 1, but I have TWRP on partition 2 also. Is there a way to get into TWRP on partition 2 without a desktop PC?
I have the same problem, after the system update yesterday my old pin does not work anymore. What could I do?
So, before you updated, was your tablet rooted? Did the update use TWRP or the stock recovery? Did you have a pin set before the update?
before the update I use PIN and fingerprint reader, device was not rooted.
The update was offered by the device and ran normally.
Now my PIN does not work anymore. I do not have an "ok" button
when entering the PIN and I do not remember if there was one before?
My pin was reset after I updated, but I thought it was because I had replaced the stock recovery with TWRP. I've heard that there's a bug in TWRP that can mess up your pin. Now it looks like the pin problem is happening with stock updates, too. I'm surprised that other people haven't reported it.
If you had TWRP installed and you were able to boot into it, there's a way that you can use the TWRP file manager to delete the pin lock files. In your case, you will probably have to do what I ended up doing. I copied into Huawei eRecover and reset the tablet. That means it was wiped and I had to restore my apps and settings. You could try to get in touch with Huawei support first and see if they have a solution, since it appears that a stock update caused the problem. Please post back again if you find a solution.
Hi
Yeasterday a friend gave me his phone (Xiaomi redmi note 7 codename lavender) and knowing i work with custom roms, he asked me to open bootloader and instal twrp and PixelExperience as rom.
I brought his phone home, inserted my SIM card, logged into my MI and added account.
I launched fastboot using ADB, activated MiUnlocker and it unlocked just fine. The phone wiped and i cofigured it, opened programmer options and clicked USB debug etc.
Again using ADV I launched fastboot and type „fastboot flash recovery twrp.img” (for reference twrp was from orange foxy)
Everything showed up, I wiped memory and inserted SD memory card with Pixel Experience, and instaled the ZIP, everything was allright so I started rebooting the system. And here is the issue, phone got stuck in a bootloop (I gave him one hour to load but it didn't).
I thought allright, let's restart that bad boy, i gave him another 15 minutes to load and still nothing.
I decided to reinstal, so I activated recovery, wiped memory and flashed zip again, waited another 15 minutes and still nothing. I thought maby the rom was corrupted so I downloaded AOSP, wiped memory, flashed rom and waited aditional 30 minutes and still nothing. I browsed Reddit and XDA and found out that is better to use „classic” TWRP not orange foxy. Once again fastbooted and flashed TWRP and it worked but requested password for memory (there was no password to begin with). I downloaded mi flash, downloaded tgz from xiaomi website and flashed it. It loaded, i made config once again and decided to instal TWRP „classic”, and again twrp „classic” asked me about password to memory despite having no password to begin with, i tried his old passwords, my old MiCloud password, even logged into MiUi and created password 1234 and password was still incorect.
I instaled twrp orange foxy and it didn't asked for password, so i tried instaling PixelExperience, but again bootloop. After 6 hours of trying i gave up, so i ask for help. My friend realy wants this.
Thanks in advance for all advices and sorry for terrible english, its my second language.
LemoN_PL said:
Hi
Yeasterday a friend gave me his phone (Xiaomi redmi note 7 codename lavender) and knowing i work with custom roms, he asked me to open bootloader and instal twrp and PixelExperience as rom.
I brought his phone home, inserted my SIM card, logged into my MI and added account.
I launched fastboot using ADB, activated MiUnlocker and it unlocked just fine. The phone wiped and i cofigured it, opened programmer options and clicked USB debug etc.
Again using ADV I launched fastboot and type „fastboot flash recovery twrp.img” (for reference twrp was from orange foxy)
Everything showed up, I wiped memory and inserted SD memory card with Pixel Experience, and instaled the ZIP, everything was allright so I started rebooting the system. And here is the issue, phone got stuck in a bootloop (I gave him one hour to load but it didn't).
I thought allright, let's restart that bad boy, i gave him another 15 minutes to load and still nothing.
I decided to reinstal, so I activated recovery, wiped memory and flashed zip again, waited another 15 minutes and still nothing. I thought maby the rom was corrupted so I downloaded AOSP, wiped memory, flashed rom and waited aditional 30 minutes and still nothing. I browsed Reddit and XDA and found out that is better to use „classic” TWRP not orange foxy. Once again fastbooted and flashed TWRP and it worked but requested password for memory (there was no password to begin with). I downloaded mi flash, downloaded tgz from xiaomi website and flashed it. It loaded, i made config once again and decided to instal TWRP „classic”, and again twrp „classic” asked me about password to memory despite having no password to begin with, i tried his old passwords, my old MiCloud password, even logged into MiUi and created password 1234 and password was still incorect.
I instaled twrp orange foxy and it didn't asked for password, so i tried instaling PixelExperience, but again bootloop. After 6 hours of trying i gave up, so i ask for help. My friend realy wants this.
Thanks in advance for all advices and sorry for terrible english, its my second language.
Click to expand...
Click to collapse
Instead of trying 6 hours, you should read carefully first few posts at orangefox thread: https://forum.xda-developers.com/showpost.php?p=79771468&postcount=2 especially about encryption... Use latest orangefox recovery and Format data partition (wipe not enough!).
Hello,
last week i decided to upgrade to A11 rom (PE+). Before i ran PE+ A10 for months without problems.
I upgraded my ofox to latest 11.1 stabile. Then Format data, wipe etc.
Now whenever i installed a rom, after a short time when rebooting system my pin isnt recognized anymore from screen lock. Theres always this "wrong pin" warning. So i cannot access my phone.
Ofox cant decrypt seither, because oft wrong pin...
Since then i Tried many different Roms (A11 and A10) and even different recoverys (twrp, los, older ofox) and firmwares.
I also reverted back to my old PE+ A10...and now even there the bug appears!
I also tried deleting all files with "lock" in it under data/system...but that leads to neverending boot-time...
It is so annoying..i dont know now i can get my phone back to function properly...
Maybe anyone has a clue?