TWRP Password Failed issue - Xiaomi Mi Mix 2S Questions & Answers

Hopefully i am posting this in the right place if not let me know I've recently installed LOS to my Mi Mix 2s running Pie.Yet when I boot into recovery it now asks for a password to decrypt the data partition when I never set one on there. I tried to input my actual login password for my phone and it was a failure. Tried 'default_password' but also a failure.I've already tried wiping and reflashing LOS and the proper 3.3.0-0 TWRP recovery yet the issue still persists.. I wanted to encrypt my phone but I'm stuck with leaving my phone unlocked if i want to backup my phone or update.Otherwise i'm back to square one with the password failed.This method i found on here https://forum.xda-developers.com/an...n-recovery-t3530008/post79573991#post79573991 also did not work for me. Can anyone help me with this issue?

That happened to me all the time. Usually it is the pin you set for the ROM you're running at the moment. You should be able to use the 'format data' option. This will wipe all partitions, so be prepared to lose your current pictures, etc, and install a new ROM via adb or something.
Sent from my Mi MIX 2S using Tapatalk

Related

Can't use twrp on oreo, it's asking for decryption key

I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
JimZiii said:
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
Click to expand...
Click to collapse
TWRP is not fully supported under Oreo. It can't handle the full disk encryption. I've read that it is possible to set PIN / password *before* TWRP is installed and then it would work with the pass or pin you set before. But this didn't work for me. And I think there is no point in using it. Backup / restore function don't work and there might be more functions do not work.
If it's for magisk, there is also a way to install it without TWRP and / or there is no need to have access to storage. Installer just patches the ramdisk and you're good to go in ignoring the errors.
Sent from my FRD-L09 using XDA Labs
cypher187 said:
TWRP is not fully supported under Oreo. It can't handle the full disk encryption. I've read that it is possible to set PIN / password *before* TWRP is installed and then it would work with the pass or pin you set before. But this didn't work for me. And I think there is no point in using it. Backup / restore function don't work and there might be more functions do not work.
If it's for magisk, there is also a way to install it without TWRP and / or there is no need to have access to storage. Installer just patches the ramdisk and you're good to go in ignoring the errors.
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
So what are you using instead if you want to flash something? I found some posts saying you can get twrp working with the encryption if you do a factory reset and data format in twrp, that way you should get encryption that twrp can read but I've tried this several times and my phone refuses to boot every time, it's not even boot looping, it just stays on that blue honor loading screen and with the little animation in the text so it didn't freeze. If I then try to do a factory reset in stock recovery it stops on 99%, forcing me to reboot, it then starts over and jumps to 100 and when it boots up pretty much all apps are gone, even system apps and keyboard apps so you can't type. If I try factory reset again the same thing happens, stops at 99 and so on
Now I have to recover it through erecovery.
Yea, I patched stock boot in the manager instead
JimZiii said:
So what are you using instead if you want to flash something? I found some posts saying you can get twrp working with the encryption if you do a factory reset and data format in twrp, that way you should get encryption that twrp can read but I've tried this several times and my phone refuses to boot every time, it's not even boot looping, it just stays on that blue honor loading screen and with the little animation in the text so it didn't freeze. If I then try to do a factory reset in stock recovery it stops on 99%, forcing me to reboot, it then starts over and jumps to 100 and when it boots up pretty much all apps are gone, even system apps and keyboard apps so you can't type. If I try factory reset again the same thing happens, stops at 99 and so on
Now I have to recover it through erecovery.
Yea, I patched stock boot in the manager instead
Click to expand...
Click to collapse
I didn't come in the situation to want to flash sth - except magisk. And I didn't want to try it as it gains no access to internal storage.
Boot screen takes up to 30 mins or more after formatting storage. Kernel encrypts it during this time. I cannot say if TWRP is able to read this encryption since it is hardware based. I think it is possible as TWRP should use same kernel on treble ROMs - as far as I know.
So... Just being very patient could make it - theoretically.
Let me know if it can :good:
Sent from my FRD-L09 using XDA Labs
JimZiii said:
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
Click to expand...
Click to collapse
Try removing pin/password in settings and see if it still asks for key.
ante0 said:
Try removing pin/password in settings and see if it still asks for key.
Click to expand...
Click to collapse
It does. And I tried it already right after flashing RROS system image (treble) and before setting a PIN and / or after removing PIN.
Look here https://forum.xda-developers.com/honor-8/help/internal-storage-encryption-t3452737 for background knowledge about this encryption.
Only way to get TWRP fully working on our device is to remove encryption through formatting the storage. But the kernel will encrypt every time while booting and TWRP will not be able to access storage anymore.
With the Nougat custom ROMs this was not relevant because they were using LOS kernel not the stock one. Treble ROMs are using stock kernel - which is, of course, an advantage.
And I didn't get TWRP to work *with* encryption (with entering PIN or whatsoever). I hope anybody can and tell me how to do or what I did wrong
Also I want a (safe) way to use it. Specially as I know that it's use is not supported by OpenKirin Team it should be safe before I really want to use it.
Sent from my FRD-L09 using XDA Labs
cypher187 said:
It does. And I tried it already right after flashing RROS system image (treble) and before setting a PIN and / or after removing PIN.
Look here https://forum.xda-developers.com/honor-8/help/internal-storage-encryption-t3452737 for background knowledge about this encryption.
Only way to get TWRP fully working on our device is to remove encryption through formatting the storage. But the kernel will encrypt every time while booting and TWRP will not be able to access storage anymore.
With the Nougat custom ROMs this was not relevant because they were using LOS kernel not the stock one. Treble ROMs are using stock kernel - which is, of course, an advantage.
And I didn't get TWRP to work *with* encryption (with entering PIN or whatsoever). I hope anybody can and tell me how to do or what I did wrong
Also I want a (safe) way to use it. Specially as I know that it's use is not supported by OpenKirin Team it should be safe before I really want to use it.
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
You can Format Data (removes encryption) and edit /vendor/etc/fstab.xxxx and remove the fileencryption line on /data.
I don't have an Honor 8 so I can't check it, but this is how it was done on Mate 9/10 before we got TWRP with decryption on Oreo.
Of course, flashing a new firmware will replace fstab so you'd have to edit it again/restore previously edited one.
Edit: Also, for fun, default password for decryption is "default_password", so you could try that. It most likely will do nothing. This is done automatically when you have no password/pin set.
cypher187 said:
I didn't come in the situation to want to flash sth - except magisk. And I didn't want to try it as it gains no access to internal storage.
Boot screen takes up to 30 mins or more after formatting storage. Kernel encrypts it during this time. I cannot say if TWRP is able to read this encryption since it is hardware based. I think it is possible as TWRP should use same kernel on treble ROMs - as far as I know.
So... Just being very patient could make it - theoretically.
Let me know if it can :good:
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
Oh ok, never knew it could take that long but I guess it makes sense. At one attempt I even waited 20-30min ?
I'll give it another shot when I got some time over.
But I just finished restoring everything from hisuite and changing back all my settings for the 6th time since hisuite don't save your system settings.
Do you know if it's possible to make a nand backup without twrp? Getting a complete nandroid backup would really help when you're not sure if the factory reset will help
---
JimZiii said:
Oh ok, never knew it could take that long but I guess it makes sense. At one attempt I even waited 20-30min
I'll give it another shot when I got some time over.
But I just finished restoring everything from hisuite and changing back all my settings for the 6th time since hisuite don't save your system settings.
Do you know if it's possible to make a nand backup without twrp? Getting a complete nandroid backup would really help when you're not sure if the factory reset will help
Click to expand...
Click to collapse
Unfortunately there is no way. Only with HiSuite or sth else. If your device is rooted you can use TitaniumBackup. It can provide a more complete backup of apps, app-data and settings.
Sent from my FRD-L09 using XDA Labs
Hi.
I use the fstab mod and do a full data format in TWRP. After that the data partition decrypted, but FRP locked, oem unlock grayed and I can't do set my google account. If I want to set the google account, the process is start but the screen is turn to black (navigation buttons show on the bottom of the screen) and nothing more. Some seconds later its drop me back to settings page.
TWRP installed.
Bootloader unlocked
Rooted with Magisk
FRP locked
Stock recovery not flashed back because HWMT show FRP locked
Mumtaz77 said:
Hi.
I use the fstab mod and do a full data format in TWRP. After that the data partition decrypted, but FRP locked, oem unlock grayed and I can't do set my google account. If I want to set the google account, the process is start but the screen is turn to black (navigation buttons show on the bottom of the screen) and nothing more. Some seconds later its drop me back to settings page.
TWRP installed.
Bootloader unlocked
Rooted with Magisk
FRP locked
Stock recovery not flashed back because HWMT show FRP locked
Click to expand...
Click to collapse
Install a full package via dload method. Take an 'unbrick' guide from the guides section if you need. You can use a 'FullOTA' package for your region which you can download with FirmwareFinder by TeamMT.
Sent from my FRD-L09 using XDA Labs

Wrong pattern after booting TWRP / Can`t decrypt data

Hey guys.
Got a Oneplus 6 running lastest OTA with latest TWRP installed.
Before flash this latest OTA, I was running latest open Beta, flashed by TWRP, with no problems.
Just booted on TWRP today to flash latest Beta again, but when I drawed the patterns, TWRP restarts. Tryed some more times, same thing, put the right patterns, TWRP imagem boots into it again.
Rebooted into system, but the system said wrong pattern now. Can't boot in system anymore too.
Booted in TWRP again, went to File Manager, and deleted these files inside /data/system (Guess I ****ed up even more here)
locksettings.db-wal
locksettings.db-shm
locksettings.db
Now I can boot in system, but it stay stuck on Initializing system on screen, and I can access only configuration using the status bar. Tryed to set the same pattern on security, still don`t work on TWRP decrypting, and system keeps saying Initializing.
Got pretty stuck here, don't know nothing else to try, anyone have any clue on what I can do?
When asked for the pattern in TWRP instead of trying to enter it choose the "do not decrypt /data" option. Then you can format (not wipe) /data. Obviously you'll lose everything, including on internal storage.
And also, it may happen again if you don't flash the no_verity zip. That stops the ROM re-encrypting /data. See this thread for more info.
Looks like some Security Patch downgrade stuff. You flashed an older build, encryption gets messed up because the Security Patch date is older than the one previously installed, you'll have to format your Data partition to decrypt the storage.
As said above, running decrypted will prevent those situtations
Although some may advice running decrypted to avoid situations, I won't recommend it, especially if you're using TWRP. A person with a good knowledge would be able to do what you did and remove lockscreen security, compromising your important accounts.
And: instead of a pattern, it's recommended to use a PIN (at least 8 digits) or password (at least 6 letters/digits/specialchars)
remewer said:
Although some may advice running decrypted to avoid situations, I won't recommend it, especially if you're using TWRP. A person with a good knowledge would be able to do what you did and remove lockscreen security, compromising your important accounts.
Click to expand...
Click to collapse
To be honest, altough what you said is absolutely true, finding yourself in a situation where someone steals your phone, sees he can't enter it, but happens to know how to use TWRP to remove the lockscreen security or sideload your data is pretty far fetched.
Frankly, loosing your data over a bad flash seems a bit more threatening.
Totone56 said:
To be honest, altough what you said is absolutely true, finding yourself in a situation where someone steals your phone, sees he can't enter it, but happens to know how to use TWRP to remove the lockscreen security or sideload your data is pretty far fetched.
Frankly, loosing your data over a bad flash seems a bit more threatening.
Click to expand...
Click to collapse
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
remewer said:
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
Click to expand...
Click to collapse
Agreed, that is what i personally do. I like being able to flash anything and potentially having to format the whole storage without any worry. Using Google Photos, Keep, Doc, ect, using Spotify and syncing every contact really makes life easier.
remewer said:
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
Click to expand...
Click to collapse
Which is fine if you are only getting this issue directly after ROM flashing or at some other predictable time. But when I was getting it, my lockscreen code/pattern was initially working fine after flashing the ROM, then it would stop working at some seemingly random moment. So the only way I could reliably have any data stored was to run with /data unencrypted. Which I agree is not ideal.

oneplus6 seems damaged following a failed twrp restore

So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.
Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)
I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.
Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.
So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.
I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
@chrcol ..., but you've issues
chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.

TWRP Doesn't try to Decrypt

So I've noticed ever since the upgrade to Android 10 TWRP on my Oneplus 7 Pro cannot decrypt the /data partition. On Android 9 it would ask for a password to decrypt, however after moving to 10 it no longer asks for the password and instead tells me it can't mount or read /data. My work around has been a data format with disabling encryption/dm-verity. This seems to work as then TWRP is able to read data and back it up/restore like normal... Today I took an OTA update and did the normal TWRP & Magisk A/B retention stuff, but when I rebooted it re-encrypted the device and sent me straight back to my problem (currently restoring from an old backup.)
Has anyone else had this issue with TWRP not even trying to decrypt/ask for a pin? This is obviously pretty annoying when dealing with OTA updates considering they re-encrypt the device.
mnbvcxzl90 said:
So I've noticed ever since the upgrade to Android 10 TWRP on my Oneplus 7 Pro cannot decrypt the /data partition. On Android 9 it would ask for a password to decrypt, however after moving to 10 it no longer asks for the password and instead tells me it can't mount or read /data. My work around has been a data format with disabling encryption/dm-verity. This seems to work as then TWRP is able to read data and back it up/restore like normal... Today I took an OTA update and did the normal TWRP & Magisk A/B retention stuff, but when I rebooted it re-encrypted the device and sent me straight back to my problem (currently restoring from an old backup.)
Has anyone else had this issue with TWRP not even trying to decrypt/ask for a pin? This is obviously pretty annoying when dealing with OTA updates considering they re-encrypt the device.
Click to expand...
Click to collapse
You need to be running TWRP 74.

[Poco F2 Pro][V12.5.5.0.RJKEUXM] Stuck on Boot Loop

Hello there, I need help :/
My Poco F2 Pro is stuck on a Boot loop, without any obvious reason.
The device became really laggy and painfully slow. Because of that, I wanted to restart it. But now it is stuck in a boot loop
I rooted the device using Magisk Canary 1 week ago. Yesterday, I installed the custom recovery "TWRP".
And with Titanium backup I froze a few system apps... which didn't seem to be so important (I googled them beforehand)
Today, I tinkered a little bit with AF+wall (which still doesn't really work), but except of this, nothing else.
I tried (using TWRP) to wipe the Data and Cache, but it fails "unable to mount /data/media/TWRP/.twrps
Also tried to change file system to ext2 and then back to ext4, but it again says "unable to mount"
What can I do now, resp. how can I get my device? I made a backup using Titanium, but it still is in the internal storage xD
OK.. I will give up the backup, I have all the important files backed up earlier anyways...
My plan is now to use MiFlash to flash the newest MIUI version [V13.0.2.0.SJKEUXM] onto my device.
Only fear is.. I have TWRP installed, and as far as I know, it does not support android 12... what will happen if I do this nervertheless?
And I want to get rid off TWRP nevertheless, so it would be perfect if it just gets replaced with the stock recovery...
sounds like a plan. still any question?
Nope, thank you, everything worked out as planned

Categories

Resources