yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] andy356:
Restore system. The main point of custom recovery here is to be able to flash zips.

System image can be flashed using fastboot when custom recovery isn't available or not functioning properly, I guess.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] kylemd:
[MENTION=455439]bgcngm[/MENTION], sorry to be a pain but I've just done a clean install to the latest nightly and this SuperSU bug still persists :(

Let me know if there is anything I can do to help.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vcx77:
Flash this SuperSU by twrp and ready

http://www24.zippyshare.com/v/geLnQIVz/file.html
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] kylemd:
Didn't work. Is that file any different to the SR4 zip shared by Chainfire? As I've already tried 2.76, 2.77, 2.78 stable, SR1-4, 2.52. None flash successfully.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] kylemd:
Got it working, finally. For those of you who have the same problem after converting to F2FS, here's what I did to get SuperSU working.

1) Format all partitions as EXT4.

2) Install CM13 and SuperSU (I used v2.78 stable, NOT SR4)

3) Backup /data, copy backup to your PC/OTG.

4) Reboot recovery, swipe to allow modifications.

5) Format /data and /cache as F2FS.

6) Restore /data backup you took earlier. Ignore the error saying it may not boot.

7) Flash SUmount from osm0sis' thread, which will mount /su properly.

8) Under "Advanced", run "Fix contexts"

9) Flash OpenGapps and your other zips. (Optional)

Judging by this and the logs I posted earlier it seems like SuperSU can't mount /su. Why, I'm not sure, but it has something to do with /data being F2FS. Just don't update SuperSU as you'll have to go through all of this again! it actually seems that the binaries will stuff up if you flash anything from recovery.

EDIT - Tried to replicate it again and SuperSU complains that the binaries don't exist again. Moving back to EXT4 until it's sorted.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Unfortunately latest TWRP is not compatible with nougat beta MIUI8. After flash ROM via TWRP it will stuck at Mi logo during booting. [MENTION=455439]bgcngm[/MENTION] Is there any chance to fix it?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] Kag:
Not able to decrypt encrypted nougat ROM even with 3.0.2-3
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Next week MIUI8 based on Android 7.0 will be released for public and no official TWRP support yet unfortunately. Only the ZCX TWRP recovery compatible with nougat MIUI8

Can we count new nougat MIUI8 compatible official TWRP release in near future?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
When Nougat package is official, then TWRP will support it officially.

Let's see if [MENTION=631273]Chainfire[/MENTION] can shed a light on this. I posted in the SuperSU support thread already.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
[MENTION=455439]bgcngm[/MENTION]:

as I said Android 7.0 based MIUI8 6.12.8 china developer, xiaomi.eu developer builds for Mi5 have been released for public!

http://en.miui.com/thread-432582-1-1.html

https://xiaomi.eu/community/threads/6-12-8.36620/
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] andy356:
Chainfire replied to your post. Was it helpful in determining the problem?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Where is the reply?

He said when nougat package is official, then TWRP will support it officially.

But nougat MIUI is official already and released for public
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] andy356:
I was addressing bgcngm. Chainfire replied to his post about 5 posts later.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] Oehr:
Decryption does not work reliably: After I changed the password within android, TWRP is unable to mount the data partition (rejects old and new pw). Only changing it back to the original password it was encrypted with (within android), will allow TWRP to access the data partition.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] chan200606:
Does anyone else have this problem with 3.0.2.3?

After creating a backup of boot, system, data and efs, I find that the backup files for boot and efs cannot be copied to another machine; only the data and system files can be copied. If I create a backup of boot, system and data under 3.0.2.0, all the backup files can be copied away. I think the same problem was in 3.0.2.2 too.

For reference I am on MIUI 8 global developer 6.11.3.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ogghi:
Hi Guys, I get the issue of not being able to decrypt data in TWRP 3.0.2-3. I installed CM14.1 nightly...

I managed to the a log off my device (adb shell): http://pastebin.com/NsbxJ5UP

Hopefully this helps to get this sorted?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
Can confirm - tried with multiple password methods without being able to decrypt. A possible workaround is to clean install an earlier build (pre 1214) and encrypt that, and then flash to a newer build in recovery.

---------- Post added at 11:28 AM ---------- Previous post was at 11:27 AM ----------

I had this issue too. Did you try moving these files via MTP only?

I wonder if ADB Pull would work?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] Frank Ivan:
I confirm...
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] chan200606:
I tried moving the files via MTP from a PC, as well as from the phone to a NAS using ES F ile Explorer. Haven't tried ADB pull but imagine that would fail as well.

Looks like it's not a problem with my setup, but indeed a bug (feature?) of 3.0.2.3. To be safe, I'll go back to 3.0.2.0 until this is resolved.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
I'll try making an encrypted backup in twrp. I imagine it would all be within an archive. Perhaps that could be transferred?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
Just letting you know, I was able to move an encrypted backup to my PC over MTP. Still using 3.0.2-3

The partitions I selected were: Boot, System, System Image, Data and EFS.

Hope this helps - good luck
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] chan200606:
That's great - thanks for trying this out. This would work for me, as I can then maintain several versions of backup but can't afford to have more than one backup on my 32GB Mi5.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ogghi:
Any idea when we could expect a fix for decryption not working in latest version?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
We shouldn't be asking for ETAs.

If encryption is a must for you, I suggest you backup your installation of CM14.1, flash CM13, encrypt on CM13, then restore 14.1 from recovery.

I've just done this about 5 minutes ago, can confirm it works fine, and I'm still able to access TWRP and install updates without issue. The only downside I can think of, is that you won't be able to change your decrpytion password whilst on Nougat.

Once TWRP properly supports FDE in android 7.1, you might want to clean install (format data) to directly encrypt on Nougat.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ogghi:
True, sorry for asking about ETA!

Thanks for the hint, will try this! If I only could back it up...cannot access the partition from TWRP :cyclops:
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
Ah yeah, I found myself in that situation too. Best you can do is backup your device data to your PC and start over. It sucks, I know.

Maybe it would be worth waiting for a newer version of TWRP. Might be worth checking Ethan's Twitter and Google+
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ogghi:
Thanks for the headsup!

I will probably just wait until new TWRP release...hopefully coming soonish ;)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
I'm hoping for the same, but I can't guarantee anything!

If only Google didn't change it every year!

Or rather; if only Google handled FDE properly earlier on.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Nougat based MIUI is released for a while and still no fully compatible TWRP version. If official MIUI dev release installed via latest TWRP then it will stuck at Mi logo....
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] FcukBloat:
and? so?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
So would be nice to see new fully nougat MIUI compatible TWRP release...
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] FcukBloat:
ok so you can just wait I guess, without claiming for anything... ;)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Oh no...I just forwarded MIUI user needs ;)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] azazello22:
And nobody cares my friend. Not to be rude, just how it works.

sent from my MI5
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Yeah I know...I just gave it the chance ;)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
Encryption support for CM14.1

Worth noting that TWRP 3.0.3-X has been trickling through for some devices. This includes support for FDE on Nougat based ROMs (No need to encrypt on Marshmallow and then flash forward) as well as Nougat's new file-based encryption, which allows for partial functionality on boot (such as alarms and emergency calls).

I'm not suggesting that this version of TWRP will be available for the Gemini anytime soon; just reassuring you guys that it's working in general.

Props to everyone that got it working! It's a shame google screw around with encryption every year.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
Any plans for updating TWRP to support Android 7 encryption? As vikashhero writes above, it seems there's a way to handle it.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ogghi:
I'd love to see that, but as always, I guess we should not ask for ETAs ;)

For now the trick with encrypting in Android 6 works...
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Time will come.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Finally good news ...
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Moved to post #3.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
You absolute beauty.

---------- Post added at 01:43 PM ---------- Previous post was at 01:35 PM ----------

[MENTION=455439]bgcngm[/MENTION] I can't get this version to boot after flashing it via Fastboot. I'll try installing it through other means and I'll get back to you.

Thanks again for sharing.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ogghi:
Hi [MENTION=455439]bgcngm[/MENTION]

Many thanks!!

Will try tonight to do a clean install with 7.1 and see if encryption works.

Cheers

David
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
Let me know if you can get it to boot. For me, the TWRP logo just flashes on for a milisecond, then the screen goes black. Then it just keeps repeating.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] Bimalhort:
Same thing here also, I am using MIUI dev
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] shabtab:
Working for me, but if the internal storage is encrypted then the twrp doesn't show up it just gets stuck in a bootloop, so I installed the old TWRP and wiped the Internal Storage then flashed this test build and Voila it worked. Thanks.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] edgarf28:
Doesn't boot for me, black screen with the TWRP boot screen flashing

I'm on the latest lineage nightly ROM.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] simplicio11:
Thanks [MENTION=455439]bgcngm[/MENTION]! I just install it from twrp and works fine. I don't have encrypted phone, but now I can do that. ;)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Can you detail what kind of bootloop? Is it the screen flashing endlessly like mentioned already here?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] shabtab:
Yes twrp logo is just flashing for a sec and keeping on flashing unless you reboot normally or in fastboot mode and flash the old twrp
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Okay, then there's a problem with encrypted devices. Did you encrypt the device again? If so, does the new TWRP continues to work?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Many thanks for that. Tested with latest Xiaomi.eu dev release. It works fine on my decrypted device, but we can't integrate it in the ROM if it doesn't work with encrypted device...
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
You can't and you shouldn't integrate until this is final. As stated it was a test release and it's now confirmed to have issues with encryption. I'll try to fix when I find some time.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] neodante:
When talk about “encrypted“ is about the close bootloader ? Or what ?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Great, thanks...I am waiting patiently. Your work highly appreciated!
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
No, bootloader is unlocked otherwise you couldn't even flash TWRP. Talking about encrypted device... userdata partition encrypted.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] neodante:
How I know if my device is encrypted ? And is better or worse have it ?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
If your device is encrypted then TWRP can't access data and internal storage
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] neodante:
Thanks, Ok, mine isn't encrypted ☺
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
That's not correct and can be misunderstood. :rolleyes: A fully working TWRP can decrypt data.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Not going to answer to your second question, but you can tell if device is encrypted if you go to Settings / Security.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] neodante:
Well... I didn't see this option, is a safety configuration that prevents attempts of stole your data. Very useful.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
Tested this with this workflow:

- Wipe all, including data to remove android 6 encryption

- Install test TWRP 3.0.3.0 using fastboot - boots OK to recovery

- Install latest lineage + nano gapps build using TWRP 3.0.3.0 - installs OK and everything runs as it should.

- Do devices encryption using just installed build - Encryption OK.

- Test boot to recovery - Not working, TWRP logo just keeps flashing in a loop.

Is there way to collect any log from that?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Do you mean without format data? Because TWRP can decrypt data by format data even in previous 3.0.2-3 release...
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Of course, without formatting data. That's the whole point of having decryption working. When you format data you simply remove encryption, you aren't actually decrypting it.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
Ah so, format data just just removed the encryption... So, if I understand well, if you will be fixed TWRP encryption issue then no need anymore perform format data even in official china MIUI release where the encryption is enabled by default?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
I tried to transfer files from pc to phone with TWRP 3.0.3-0 using adb sideload and adb push command but it ended in "error: closed" error message. Is it TWRP 3.0.3-0 bug?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
Sideload worked for me before I encrypted the device. Now I am kind of stuck with 0113 release since I cannot boot to recovery.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Someone out there running any AOSP based ROM with encrypted data can check if this is working now?

** link removed **
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
For me "adb push rom.zip /sdcard/" adb command doesn't work, it says error: closed

but "adb sideload rom.zip" ADB command works fine but it installs the ROM not transfer the file...

---------- Post added at 08:02 PM ---------- Previous post was at 07:59 PM ----------

What about MIUI users with encrypted data? If it is ok for testing then I can get you some official MIUI user with encrypted data for sure...
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
First I need to ensure that decryption is working with AOSP based crypto. Judging by your earlier comments, I don't even know if decryption ever worked on MIUI M based ROM.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
We have just used format data to remove encryption so far...Same way works with N based MIUI...
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
As I said, that's not the proper way of doing things. Decryption is one thing, removing encryption by formatting data is a totally different thing. If you're good with the last option, then the latest test release should do the trick.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] andy356:
How deeply is the recovery tied to the ROM and its functions? I used to think it was completely independent and ROM changes wouldn't interfere with the recovery at all, considering that the same recovery works with AOSP based, Lineage based and MIUI ROMs.

Is encryption one of those features which has to have the correct code on both the ROM level and recovery level to work properly?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
OK thanks for that info. I am looking forward to test it on xiaomi.eu MIUI release.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Not tied at all. But when it comes to encryption, things are not that easy. Some OEMs like to play tricks with this. Just as an example, TWRP for HTC One M8 is not able to decrypt devices that were encrypted with HTC Sense based ROMs.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] andy356:
Holy cow. No wonder XDA generally comes across as pissed off at OEMs in threads and articles. I thought the issue was mainly untimely kernel sources release or refusal to release them. When they pull stunts like this, what's a developer to do?

Thanks for the info! :good::)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
I forgot to say TWRP shows incorrect battery level 50% but maybe you have already informed... same in previous 3.0.2-3 release
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
It displays well for me since the first 3.0.3-0 test release. Is it still happening to you?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
If I reboot to TWRP from the system then it always displays incorrectly 50% but if I reboot to TWRP from TWRP then it displays correctly after that. Furthermore strange numbers always appears in status bar after TWRP booted up but it disappears after couple of secs.

Please find screenshots attached.

ROM: Xiaomi.eu MIUI 7.1.12 Android 7.0

TWRP: 3.0.3-0 Test 2
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] deusxx:
Yes. After switching to the twrp with that change in dts(?) File if I remember, battery stats show discrepancy from previous values. Mine had shown from 50% b4 ?25% inside twrp. I do not believe it is a persistent error. Since then I did not see anything similar.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
Tested this, it goes now to TWRP logo screen but freezes there.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ogghi:
Report from my side:

Wiped all

Flashed recovery 3.0.3-0-gemini-test2 from twrp 3.0.2

Flashed 20170115 LineageOS and 15012017 OpenGapps Pico

Set up some stuff, apps etc.

Enabled encryption, after some minute phone had black screen not reacting to anything.

Force rebooted to recovery, was not encrypted apparently.

Flashed LineageOS over again, reboot and it asked for key to decrypt.

Also in TWRP now it asks for decryption at boot. It works.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] CaioFerreira:
Do I need unlocked bootloader to flash TWRP?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Yes, you do.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] CaioFerreira:
Could you provide me a link with a safe tutorial to do so, please?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
See this: https://xdaforums.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243. That's the proper thread to ask questions about bootloader unlocking. ;)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
EDIT: was bit too quick, now I get stuck in part "Trying decryption" part when password has been given.

Found way to get this working too.

If you face this freeze above, change encryption password in android security settings and boot to back to recovery - recovery works and asks password.

Great job bgcngm!

---------- Post added at 07:29 PM ---------- Previous post was at 07:13 PM ----------

Can you get into actual TWRP with your password?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] bgcngm:
Thanks for testing. Where did you change the encryption password? Did you change your PIN in Settings / Security?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
From Settings/Security I used "Change encryption password". I also tried "Replace encryption password" which I guess should set encryption password same as pin/phone password. But TWRP behaves the same way on both cases.

Also for some reason now I cannot change encryption password at all and phone only accepts the password I set with "Change encryption password" first time. Even if I change it from same place.

Just to clear up: I am still stuck on TWRP "Trying encryption" part, was bit eager to post results.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ogghi:
There is now a dedicated entry saying saying change encryption password.

See attached screen shot. Also attached from password entry in TWRP.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
I get the same but what if you enter your password to that TWRP password entry?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
[MENTION=455439]bgcngm[/MENTION] I checked recovery logs when it gets stuck in "Trying Decryption" and this what is see when it gets stuck.

I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Is encrypted, do decrypt page first
I:Switching packages (TWRP)
I:Set page: 'decrypt'
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
crypt_ftr->fs_size = 52453304
Using scrypt with keymaster for cryptfs KDF
Trying to convert ascii string of odd length
Failed to convert passwd from hex, using passwd instead
keymaster module name is Keymaster QTI HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.

Let me know if you want full log.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ogghi:
It works just fine!
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
Ok, its different behaviour that I have. I guess there is some variables that are changing behaviour.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] graw2:
What kind of password asks TWRP? I have had same "enter password" screen at first boot into TWRP after I installed it for official China developer ROM...
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] nsn:
I tried this once more from clean install and face the same issue after I do encryption. I get stuck in "Trying Decryption"
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] vikashhero:
if it's asking you for text and if you haven't explicitly set an encryption password, the password should be "default_password". I think TWRP tries that by default, however.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] jauhari:
Now my TWRP Touch Screen Won't Work after flashed LineageOS 15/1 Unofficial... any clues how to fix it?

---------- Post added at 06:27 AM ---------- Previous post was at 06:21 AM ----------

after flash 3.2.3 the problem has been fixed... thanks :)