[OFFICIAL] [9/10] TWRP 3.6.0 for POCO F1 [beryllium]

Search This thread

Tremolo4

Member
Dec 2, 2017
27
25
Oh, you said FDE. Well most encrypted A12 ROMs are FBE.
You should do clean install at some point to move to FBE since I read you are upgrading since A9.
Ah :)
Yes, you're probably right I should reinstall soon in order to switch to FBE. I'll have to find a new way of backing up my data as I was using TWRP for that. I was just holding out hope that FDE support would be added back to TWRP soon.
 

REIGNZ3

Recognized Developer
I am using A12 (Lineage 19.1) with FDE. I have been upgrading since A9 or A10. As far as I know there is currently no recovery at all that can decrypt my data.

lineage use fbe tho
 
  • Like
Reactions: duttyend

Tremolo4

Member
Dec 2, 2017
27
25

lineage use fbe tho
Only on fresh installs. Not on my device, because I have not wiped data since at least A9. The very commit you linked says
However, we are able to retain FDE functionality on already encrypted devices by setting encryptable=footer fstab entry.
 

guhvanoh

Senior Member
Ah :)
Yes, you're probably right I should reinstall soon in order to switch to FBE. I'll have to find a new way of backing up my data as I was using TWRP for that. I was just holding out hope that FDE support would be added back to TWRP soon.
Have you tried the older TWRP versions, say 3.6.0 which support FDE, to see if they work? And what about the other recoveries - ofox, pbrp?
 

535iu

Senior Member
Feb 22, 2016
147
9
there were a zip that removes the password, unfortunately i can't find it, it may not need to system be decrypt because is a zip like rom, and even before decryption were available it worked...
Please, that zip file would help me a lot. I have already tried everything to recover my data. I tried all the current TWRP versions, I also contacted @REIGNZ3 several times (and shortly after he did me the favor of releasing new TWRP versions), but no TWRP version decrypts my data. I also tried updating the ROM (crDroid 8.4 from April 17) to the latest 8.4 and 8.5 (I previously informed myself that there were no partition changes). I also contacted @gwolfu months ago, but he could not help me. I don't have much money, but I can make a donation if someone can help me decrypt my data.

If anyone can help me, you can write me by private message or in this thread, please. I have been having this problem for over two months now.
 

Retrial

Recognized Contributor & Translator
Jun 10, 2015
1,973
4,398
Athens
Samsung Galaxy S4
Xiaomi Poco F1
Please, that zip file would help me a lot. I have already tried everything to recover my data. I tried all the current TWRP versions, I also contacted @REIGNZ3 several times (and shortly after he did me the favor of releasing new TWRP versions), but no TWRP version decrypts my data. I also tried updating the ROM (crDroid 8.4 from April 17) to the latest 8.4 and 8.5 (I previously informed myself that there were no partition changes). I also contacted @gwolfu months ago, but he could not help me. I don't have much money, but I can make a donation if someone can help me decrypt my data.

If anyone can help me, you can write me by private message or in this thread, please. I have been having this problem for over two months now.
Hello,

Sorry for late reply but I didn't paid attention earlier. You could try to post in my thread.

So as far I understand u are currently on crDroid encrypted, you bootloop and you want to upgrade to latest version of crDroid and TWRP without losing ur data.

So take a look on the steps below:
  • Download latest TWRP by @REIGNZ3.
  • Download latest crDroid build.
  • Download latest GApps you use. (I recommend FlameGApps full with config but it's up to you)
  • Boot into to TWRP by REIGNZ via adb:
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-beryllium-v3.6.2-A12-V3.img
  • Wipe: System, System_EXT, Vendor, Cache, Dalvik / ART Cache
  • Go back to TWRP at Advanced and press the ADB sideload to dirty install the ROM and GApps via adb from your pc, type: adb sideload /path/to/rom.zip (if you have sdcard or USB OTG you can just install it via it without adb)
  • Then reboot to system.
  • If it boots, backup ur data just to be safe from now and go on and then remove ur pattern,pin and set it again, boot to twrp (make sure to flash twrp by reignz in recovery section because we previously just boot into it) and check if it can decrypt.

If you still have issues please post in my thread to not spam this thread.
 
Last edited:

recall1

Member
Jun 17, 2022
10
5
When i try to restore vendor or system_ext partition(s) from a succesfully made Backup it says Partition not found...? Also vendor and system_ext is not listed in restore options though it had succesfully been backuped.

does anyone else have the same problems with this twrp version? No new update since july 7th...
Or is it just me?

Im using the latest twrp-beryllium-v3.6.2-A12-V3 version by Reignz3 with awaken 2.9 vanilla rom
my phone is not encrypted
 
  • Like
Reactions: duttyend

TioCareca

Senior Member
When i try to restore vendor or system_ext partition(s) from a succesfully made Backup it says Partition not found...? Also vendor and system_ext is not listed in restore options though it had succesfully been backuped.

does anyone else have the same problems with this twrp version? No new update since july 7th...
Or is it just me?

Im using the latest twrp-beryllium-v3.6.2-A12-V3 version by Reignz3 with awaken 2.9 vanilla rom
my phone is not encrypted
its a bug no fix for now
 

Retrial

Recognized Contributor & Translator
Jun 10, 2015
1,973
4,398
Athens
Samsung Galaxy S4
Xiaomi Poco F1
When i try to restore vendor or system_ext partition(s) from a succesfully made Backup it says Partition not found...? Also vendor and system_ext is not listed in restore options though it had succesfully been backuped.

does anyone else have the same problems with this twrp version? No new update since july 7th...
Or is it just me?

Im using the latest twrp-beryllium-v3.6.2-A12-V3 version by Reignz3 with awaken 2.9 vanilla rom
my phone is not encrypted
This is source side bug as far as I remember Reignz said.
Current common bugs of TWRP based on A12 by REIGNZ are:
  1. There is low chance the Pattern/PIN not work in prompt to decrypt.
    Workaround: Boot to system and remove pattern/pin and set it again.
  2. Format Data may doesn't work at once.
    Workaround: Reboot again to recovery and then format data
  3. MTP may not work while you are in TWRP and connected to PC.
    Workaround: Go to Advanced > File Manager > Select Internal Storage and then PC should recognize the device.
  4. If you want to use DFE you may encounter some issues.
    Workaround: If you want to be decrypted and flash DFE always, use TWRP by REIGNZ based on A9 and mount the vendor before flashing it.
  5. Backup/Restore doesn't work, source side of twrp issue.
Note: Only work with FBE A12+ ROMs. It doesn't work with FDE.
 
Last edited:

Tremolo4

Member
Dec 2, 2017
27
25
I am still on FDE, not FBE, as noted previously in this thread.

I just tried the V4 version from @REIGNZ3 to see if it would decrypt my data. It did not work. Moreover, this time, it also seems to have corrupted something so that even booting to system now says "Wrong password" when trying to decrypt. Trying this recovery is the only thing I did between reboots. Only took a minute or two. I now have to do a fresh install, thereby switch to FBE, and restore apps from Seedvault and NeoBackup.

Sadly, I will have lost at least two weeks of data on some apps due to this.

So I'm warning anyone who has -- like me -- upgraded since Android 9 and will therefore still be on FDE to stay away from this recovery. It is not safe.

I'll refrain from using this recovery even after switching to FBE as I've lost trust in its developer to be honest. It seems the future of creating full data backups on Android is no longer by using a recovery.

Edit: Here are the steps I did for posterity.
0. reboot to fastboot from my running system
1. flash V4 recovery by REIGNZ3
2. reboot to recovery
3. go to Mount --> Decrypt Data
4. enter password
5. receive message about the password being incorrect
6. try again, no success
7. reboot back to system
8. enter password. now android tells me that my password is wrong
 
Last edited:

TioCareca

Senior Member
I am still on FDE, not FBE, as noted previously in this thread.

I just tried the V4 version from @REIGNZ3 to see if it would decrypt my data. It did not work. Moreover, this time, it also seems to have corrupted something so that even booting to system now says "Wrong password" when trying to decrypt. Trying this recovery is the only thing I did between reboots. Only took a minute or two. I now have to do a fresh install, thereby switch to FBE, and restore apps from Seedvault and NeoBackup.

Sadly, I will have lost at least two weeks of data on some apps due to this.

So I'm warning anyone who has -- like me -- upgraded since Android 9 and will therefore still be on FDE to stay away from this recovery. It is not safe.

I'll refrain from using this recovery even after switching to FBE as I've lost trust in its developer to be honest. It seems the future of creating full data backups on Android is no longer by using a recovery.
That recovery is for A12 and A 13 rooms so it's not for A9 encryption even if not told explicitly, I think its told somewhere but... Anyway supposedly you should clean flash updating from different ROM version in custom rooms as stated by almost all devs to avoid bugs...
 

Tremolo4

Member
Dec 2, 2017
27
25
That recovery is for A12 and A 13 rooms so it's not for A9 encryption even if not told explicitly, I think its told somewhere but... Anyway supposedly you should clean flash updating from different ROM version in custom rooms as stated by almost all devs to avoid bugs...
I am on Android 12 (newest LineageOS 19.1 build), as said multiple times before.

And yes, almost nothing was *told explicitly* about this recovery which should have been a red flag for me already, to be honest. I was just too curious.

So here goes: I am stating explicitly that the TWRP recovery by REIGNZ3 is to be avoided with FDE encryption, because it will effectively wipe your data without warning. I am also going to note explicitly again that FDE still works in LineageOS 19.1 / Android 12 for our device.

On another note, I find it hard to believe that everyone wipes their data on every new LineageOS version. Why the hassle when upgrading works fine?
 

TioCareca

Senior Member
I am on Android 12 (newest LineageOS 19.1 build), as said multiple times before.

And yes, almost nothing was *told explicitly* about this recovery which should have been a red flag for me already, to be honest. I was just too curious.

So here goes: I am stating explicitly that the TWRP recovery by REIGNZ3 is to be avoided with FDE encryption, because it will effectively wipe your data without warning. I am also going to note explicitly again that FDE still works in LineageOS 19.1 / Android 12 for our device.

On another note, I find it hard to believe that everyone wipes their data on every new LineageOS version. Why the hassle when upgrading works fine?
True, I still wipe all every time a number is up in a ROM and almost all flashaolics do it, but I understand why you would not wanted do that.
 

Retrial

Recognized Contributor & Translator
Jun 10, 2015
1,973
4,398
Athens
Samsung Galaxy S4
Xiaomi Poco F1
I am still on FDE, not FBE, as noted previously in this thread.

I just tried the V4 version from @REIGNZ3 to see if it would decrypt my data. It did not work. Moreover, this time, it also seems to have corrupted something so that even booting to system now says "Wrong password" when trying to decrypt. Trying this recovery is the only thing I did between reboots. Only took a minute or two. I now have to do a fresh install, thereby switch to FBE, and restore apps from Seedvault and NeoBackup.

Sadly, I will have lost at least two weeks of data on some apps due to this.

So I'm warning anyone who has -- like me -- upgraded since Android 9 and will therefore still be on FDE to stay away from this recovery. It is not safe.

I'll refrain from using this recovery even after switching to FBE as I've lost trust in its developer to be honest. It seems the future of creating full data backups on Android is no longer by using a recovery.

Edit: Here are the steps I did for posterity.
0. reboot to fastboot from my running system
1. flash V4 recovery by REIGNZ3
2. reboot to recovery
3. go to Mount --> Decrypt Data
4. enter password
5. receive message about the password being incorrect
6. try again, no success
7. reboot back to system
8. enter password. now android tells me that my password is wrong
I am on Android 12 (newest LineageOS 19.1 build), as said multiple times before.

And yes, almost nothing was *told explicitly* about this recovery which should have been a red flag for me already, to be honest. I was just too curious.

So here goes: I am stating explicitly that the TWRP recovery by REIGNZ3 is to be avoided with FDE encryption, because it will effectively wipe your data without warning. I am also going to note explicitly again that FDE still works in LineageOS 19.1 / Android 12 for our device.

On another note, I find it hard to believe that everyone wipes their data on every new LineageOS version. Why the hassle when upgrading works fine?
First of all, none forced you to use that recovery if you were already happy with what you had before.

You take your own risk when you mess with custom roms/recoveries and always should have backup of your main data.
I remember few posts back (here, here, here, here) people telling you that doesn't work with FDE.

I don't know what you did but decryption working fine for most people in A12+ with FBE if you did clean install. If when you boot to twrp and get the prompt to put ur pattern/pin to decrypt doesn't work, boot to ROM and remove pattern/pin and set it again, then try again on twrp. I personally never had to do that but few others had to do it.
About Backup/Restore this is source side issue of twrp based on A12 (instead of A9 which official is) as reignz already said.

I've highlight some common issues with workaround here but I will also add as note that doesn't work with FDE.

To reply to your question why is recommended to do clean install from one Android version to another, is because to clean up the system from old android version files that left behind, to not mixed things up, avoid bugs-glitches that may caused by this and more. Even on stocks ROMs you should that (from android version to another).

It's sad when people doesn't appreciate the work of developers and saying they lost the trust to them. You know it's hard to make everything work as the time goes on, on older devices like f1 and we should be happy that some devs still messing with it. This twrp by @REIGNZ3 saved a lot of A12+ ROMs which can now use encryption fine to improve security.
So I can say the opposite to you that FBE working fine with this recovery and should not be avoided as you said. Actually it's your only twrp choice that support decryption on a12+.

Most casual users choose a ROM, install it and then boot to recovery only for OTA updates etc or to perform clean or dirty installation. No reason to dig it more, especially if you compared it to aosp recoveries or to oem recoveries which doesn't have many option as twrp.

By saying all these, I will suggest to move our conversation in my thread since this thread is for Official TWRP and people may get confused with all these.
 
Last edited:

Tremolo4

Member
Dec 2, 2017
27
25
Thanks for your reply. I agree with most of what you say. I'm aware that what I'm doing with my phone is entirely at my own risk. I'm not demanding anything of any developer. I'm just stating my own experience and the consequences I personally draw from that.

Thank you for adding a note about FDE. It might save other people in my situation, if there are any left.

In other news, my Seedvault Backup was restored perfectly, very convenient. For Apps that disallow backup I used a two-weeks-old NeoBackup, which worked for most apps. Only some apps refused to work due to "security concerns" after restoring their data with NeoBackup. No big deal, just annoying.
 

REIGNZ3

Recognized Developer
I am still on FDE, not FBE, as noted previously in this thread.

I just tried the V4 version from @REIGNZ3 to see if it would decrypt my data. It did not work. Moreover, this time, it also seems to have corrupted something so that even booting to system now says "Wrong password" when trying to decrypt. Trying this recovery is the only thing I did between reboots. Only took a minute or two. I now have to do a fresh install, thereby switch to FBE, and restore apps from Seedvault and NeoBackup.

Sadly, I will have lost at least two weeks of data on some apps due to this.

So I'm warning anyone who has -- like me -- upgraded since Android 9 and will therefore still be on FDE to stay away from this recovery. It is not safe.

I'll refrain from using this recovery even after switching to FBE as I've lost trust in its developer to be honest. It seems the future of creating full data backups on Android is no longer by using a recovery.

Edit: Here are the steps I did for posterity.
0. reboot to fastboot from my running system
1. flash V4 recovery by REIGNZ3
2. reboot to recovery
3. go to Mount --> Decrypt Data
4. enter password
5. receive message about the password being incorrect
6. try again, no success
7. reboot back to system
8. enter password. now android tells me that my password is wrong
This recovery was never intended for FDE devices, and no rom has used FDE since A12, so stop blaming me when you were at fault.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I am still on FDE, not FBE, as noted previously in this thread.

    I just tried the V4 version from @REIGNZ3 to see if it would decrypt my data. It did not work. Moreover, this time, it also seems to have corrupted something so that even booting to system now says "Wrong password" when trying to decrypt. Trying this recovery is the only thing I did between reboots. Only took a minute or two. I now have to do a fresh install, thereby switch to FBE, and restore apps from Seedvault and NeoBackup.

    Sadly, I will have lost at least two weeks of data on some apps due to this.

    So I'm warning anyone who has -- like me -- upgraded since Android 9 and will therefore still be on FDE to stay away from this recovery. It is not safe.

    I'll refrain from using this recovery even after switching to FBE as I've lost trust in its developer to be honest. It seems the future of creating full data backups on Android is no longer by using a recovery.

    Edit: Here are the steps I did for posterity.
    0. reboot to fastboot from my running system
    1. flash V4 recovery by REIGNZ3
    2. reboot to recovery
    3. go to Mount --> Decrypt Data
    4. enter password
    5. receive message about the password being incorrect
    6. try again, no success
    7. reboot back to system
    8. enter password. now android tells me that my password is wrong
    I am on Android 12 (newest LineageOS 19.1 build), as said multiple times before.

    And yes, almost nothing was *told explicitly* about this recovery which should have been a red flag for me already, to be honest. I was just too curious.

    So here goes: I am stating explicitly that the TWRP recovery by REIGNZ3 is to be avoided with FDE encryption, because it will effectively wipe your data without warning. I am also going to note explicitly again that FDE still works in LineageOS 19.1 / Android 12 for our device.

    On another note, I find it hard to believe that everyone wipes their data on every new LineageOS version. Why the hassle when upgrading works fine?
    First of all, none forced you to use that recovery if you were already happy with what you had before.

    You take your own risk when you mess with custom roms/recoveries and always should have backup of your main data.
    I remember few posts back (here, here, here, here) people telling you that doesn't work with FDE.

    I don't know what you did but decryption working fine for most people in A12+ with FBE if you did clean install. If when you boot to twrp and get the prompt to put ur pattern/pin to decrypt doesn't work, boot to ROM and remove pattern/pin and set it again, then try again on twrp. I personally never had to do that but few others had to do it.
    About Backup/Restore this is source side issue of twrp based on A12 (instead of A9 which official is) as reignz already said.

    I've highlight some common issues with workaround here but I will also add as note that doesn't work with FDE.

    To reply to your question why is recommended to do clean install from one Android version to another, is because to clean up the system from old android version files that left behind, to not mixed things up, avoid bugs-glitches that may caused by this and more. Even on stocks ROMs you should that (from android version to another).

    It's sad when people doesn't appreciate the work of developers and saying they lost the trust to them. You know it's hard to make everything work as the time goes on, on older devices like f1 and we should be happy that some devs still messing with it. This twrp by @REIGNZ3 saved a lot of A12+ ROMs which can now use encryption fine to improve security.
    So I can say the opposite to you that FBE working fine with this recovery and should not be avoided as you said. Actually it's your only twrp choice that support decryption on a12+.

    Most casual users choose a ROM, install it and then boot to recovery only for OTA updates etc or to perform clean or dirty installation. No reason to dig it more, especially if you compared it to aosp recoveries or to oem recoveries which doesn't have many option as twrp.

    By saying all these, I will suggest to move our conversation in my thread since this thread is for Official TWRP and people may get confused with all these.
    3
    I am still on FDE, not FBE, as noted previously in this thread.

    I just tried the V4 version from @REIGNZ3 to see if it would decrypt my data. It did not work. Moreover, this time, it also seems to have corrupted something so that even booting to system now says "Wrong password" when trying to decrypt. Trying this recovery is the only thing I did between reboots. Only took a minute or two. I now have to do a fresh install, thereby switch to FBE, and restore apps from Seedvault and NeoBackup.

    Sadly, I will have lost at least two weeks of data on some apps due to this.

    So I'm warning anyone who has -- like me -- upgraded since Android 9 and will therefore still be on FDE to stay away from this recovery. It is not safe.

    I'll refrain from using this recovery even after switching to FBE as I've lost trust in its developer to be honest. It seems the future of creating full data backups on Android is no longer by using a recovery.

    Edit: Here are the steps I did for posterity.
    0. reboot to fastboot from my running system
    1. flash V4 recovery by REIGNZ3
    2. reboot to recovery
    3. go to Mount --> Decrypt Data
    4. enter password
    5. receive message about the password being incorrect
    6. try again, no success
    7. reboot back to system
    8. enter password. now android tells me that my password is wrong
    This recovery was never intended for FDE devices, and no rom has used FDE since A12, so stop blaming me when you were at fault.
    2
    That recovery is for A12 and A 13 rooms so it's not for A9 encryption even if not told explicitly, I think its told somewhere but... Anyway supposedly you should clean flash updating from different ROM version in custom rooms as stated by almost all devs to avoid bugs...
    I am on Android 12 (newest LineageOS 19.1 build), as said multiple times before.

    And yes, almost nothing was *told explicitly* about this recovery which should have been a red flag for me already, to be honest. I was just too curious.

    So here goes: I am stating explicitly that the TWRP recovery by REIGNZ3 is to be avoided with FDE encryption, because it will effectively wipe your data without warning. I am also going to note explicitly again that FDE still works in LineageOS 19.1 / Android 12 for our device.

    On another note, I find it hard to believe that everyone wipes their data on every new LineageOS version. Why the hassle when upgrading works fine?
    1
    This recovery was never intended for FDE devices, and no rom has used FDE since A12, so stop blaming me when you were at fault.
    Sorry for the confusion, I was not intending to blame you for anything. My apologies. I was merely informing people in this thread about how your recovery works with FDE and LineageOS 19.1 / A12.
  • 29
    unnamed.png


    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a full touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    TWRP built for the Poco/Pocophone F1. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery.

    Flash through twrp or fastboot

    To temporarily boot this recovery:
    Code:

    fastboot boot twrp*.img

    To permanently flash it:
    Code:

    fastboot flash recovery twrp*.img

    Download (beryllium)


    kernel source: https://github.com/LineageOS/android_kernel_xiaomi_sdm845

    XDA:DevDB Information
    [OFFICIAL] TWRP 3.4.0-1 for POCO F1 [beryllium], ROM for the Xiaomi Poco F1

    Contributors
    althafvly
    Source Code: https://github.com/TeamWin/android_device_xiaomi_beryllium

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 4.x

    Version Information
    Status:
    Stable

    Created 2020-10-24
    Last Updated 2020-11-16
    19
    10
    Finally @REIGNZ3 fixed encryption/decryption of latest TWRP 3.6.2.
    You can get it here or in my AFH mirror. You can also find it in my collection.
    Notes:
    • If you're using system_ext roms, use the system_ext version otherwise, use the non system_ext (NSE) version.
    • It is currently in beta, so please report any bugs if you notice.
    Bugs:
    • There is no system partition in Wipe section. Dev looking at it.
    • "Cannot mount the vendor" error message. Fixed in next build

    I tested it on crDroid and working fine. -OTA on crDroid also worked fine-
    Again many thanks to the Hall of Fame Developer @REIGNZ3. :cool:
    Update 01/07/2022:
    Fixed System issue. Everything seems to working now.
    Use the v2 builds. You can find it here or in my AFH Mirror.

    Did you thanks already @REIGNZ3? Do it, he deserve it :cool:
    9
    @althafvly

    Hi, TWRP has already been updated to version 3.6.2_9-0 this month for our F1.

    I have read that there are already mobiles that are already able to decrypt A12 memory with password. For example, the GT Neo 2. Please could you update our TWRP so that it can read the encrypted A12 memory?
    Finally @REIGNZ3 fixed encryption/decryption of latest TWRP 3.6.2.
    You can get it here or in my AFH mirror. You can also find it in my collection.
    Notes:
    • If you're using system_ext roms, use the system_ext version otherwise, use the non system_ext (NSE) version.
    • It is currently in beta, so please report any bugs if you notice.
    Bugs:
    • There is no system partition in Wipe section. Dev looking at it. Fixed
    • "Cannot mount the vendor" error message. Fixed

    I tested it on crDroid and working fine. -OTA on crDroid also worked fine-
    Again many thanks to the Hall of Fame Developer @REIGNZ3. :cool:
    8
    Decryption does not work for me, even with this version. Same error as with official TWRP: "Failed to decrypt data". Maybe FDE is not supported, only FBE? Can anyone confirm?
    only support for A12 use old recovery if u wanna use encryption for A11