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
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 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?
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S
I clean flashed (wiped data, both caches and system from TWRP) Codename Phoenix, the latest build from Telegram, and flashed the recommended 8.1 Gapps, but didn't flash Magisk as I only had a 15.x build which causes bootloops unless flashed after a 14.x build which I didn't have on my internal storage.
It flashed fine, I began to set everything up and then locked my device. I was able to unlock it with my passcode as normal, but after about 10mins it stopped recognising my passcode and I couldn't unlock with fingerprint either as "additional authentication" was required.
EDIT: Should probably add I also went into trusted agents and disabled "Smart Unlock" or whatever the Google thing is, and enabled Quick Unlock (the thing that automatically unlocks your phone when you get your passcode correct). After that it stopped working.
I came from the latest Open Beta (OB3) of OxygenOS.
I figured- no problem, I'll just restore from a backup that I'd made before flashing Code Phoenix. Unfortunately, TWRP no longer recognises my passcode to decrypt my data, and default_password doesn't work either.
I have no idea what to do. I've flashed the latest blu_spark TWRP build, and there's no difference. Is the only solution to wipe my internal storage?
You enable quick unlock option which mess up with encryption keys. Only option is format data our remove user data from fastboot.
It is best to stay decrypt if you don't know what you are doing?
elliottweaver said:
I clean flashed (wiped data, both caches and system from TWRP) Codename Phoenix, the latest build from Telegram, and flashed the recommended 8.1 Gapps, but didn't flash Magisk as I only had a 15.x build which causes bootloops unless flashed after a 14.x build which I didn't have on my internal storage.
It flashed fine, I began to set everything up and then locked my device. I was able to unlock it with my passcode as normal, but after about 10mins it stopped recognising my passcode and I couldn't unlock with fingerprint either as "additional authentication" was required.
...........................
Click to expand...
Click to collapse
Do you have a backup you can restore?
Hi
I was running Resurrection Remix on my S9 but due to my job I kept knocking the screen and pocket dialling random people.
So I wanted to revert back to another rom I had previously backed up as it had prevent accidental touches as a feature to prevent any further pocket knocks.
Yet once restored my IMEI had been lost and all three backup were now useless as it had lost the EFS Backup?!?
I had managed to get my phone working but smart switch had decided to put a v2 (binary 2) bootloader on.
Now when I attempt to boot any lineage based rom I am stuck at the bootscreen.
I have wiped everything, formatted data (by typing yes), and even tried dm verity and flashing twrp bootloader to try and trick the phone yet to no avail.
Has anyone else had this problem and found a solution or do I have to now wait until lineage based roms catch up with v2 boot images? (As most are on BRE5/8).
Thanks
Probly gotta wait till they update it. Odin back to stock
UPDATE: I have managed to get the phone to boot lineage.
I succeeded by flashing lineage, gapps, magisk and BRE5 Vendor zip file.
Seems to be all good.