4

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

 1 year ago
source link: https://forum.xda-developers.com/t/official-9-10-twrp-3-6-0-for-poco-f1-beryllium.4181357/page-8#post-87628231
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Top Liked Posts

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.

There is a new official TWRP build for our device, v3.7.0.

Since it's still based on the Android 9 branch, I suspect it still won't support FBE decryption for A12+. However, it may yet fix FDE decryption on A12; there is one entry in the changelog that sounds relevant. Sadly, I've lost the ability to test that.

Interestingly, the Android 12 branch changelog lists "FDE compatibility".

Since there is no official maintainer anymore, there might be some obvious bugs, who knows. I do not plan on testing it, just wanted to notify people here.
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.

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?

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.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK