Development [RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project

[maximum117]

Screenshot of the TWRP log here

I have that error too. I tried to fix that error (tried rerestore backup, reboot, etc) but nothing help.

 

[PTX64]

twrp or nand /data backup has never been reliable. You could use backup made by app like migrate, swiftbackup, etc, they should be more reliable. Unless you're backing up partition other than /data (efs, modem, etc.), twrp should be fine,

I never tried Swiftbackup and Migrate 4.0 doesn't seem to properly support anything above Android 10. I did have some issues with Migrate and restoring app data in the past on my A11 en A12 devices.

Some people want a full backup of the data, even though some things will not work, like Signal that has it keys stored into a container. TWRP can also restore all Android settings, VPN, Wifi etc connections etc.

 

[PTX64]

While running the backup itself, it doesn't produce any errors on the screen and all seems fine (screenshot attached). But when you look at the backup log ( excerpt https://pastebin.com/8vv98bRM ), you'll see many "failed to lookup fscrypt tar policy for" errors.

First, I flashed the official fastboot images of Xiaomi onto the phone: mojito_global_images_V13.0.7.0.SKGMIXM_20220418.0000.00_12.0_global

Then I did a "fastboot erase" on the metadata, userdata, misc, apdp and multiimgoem partitions.

Next, I installed this 12.1 TWRP, Magisk 25.1, NikGapps-core-arm64-12-20220421-signed.zip and lineage-19.1-20220614-UNOFFICIAL-mojito.zip in the right order.

Then I did the same erase process as above and rebooted the phone into Lineageos without issues (and without multiple user profiles).

 

[PTX64]

I might be related that TWRP is using TW_USE_FSCRYPT_POLICY := 2 (2 = default, while the device might be using TW_USE_FSCRYPT_POLICY := 1 ) and when it's policy is '1' it must be specified in https://github.com/nebrassy/device_xiaomi_mojito-TWRP/blob/android-12.1/BoardConfig.mk

Looking at the previous errors at pastebin, which TWRP caused to bail out in the past on backups/restores (not anymore since https://gerrit.twrp.me/c/android_bootable_recovery/+/4231 ). Now it simply continues the backup assuming nothing is wrong, but without storing the right policy for each file and/or directory.

I:addFile '/data/vendor' including root: 0
failed to lookup fscrypt tar policy for '/data/vendor' - '7778812a000000000000000000000000

But when you run a check in the TWRP shell:

sunny:/ # fscryptpolicyget /data/vendor                                                                                                                       
000000007778812a

And without backing up and restoring files without their required policies, then this should cause problems. Where it exactly lies, I don't know yet.

But looking at https://gerrit.twrp.me/plugins/giti...ery/+/refs/heads/android-12.1/libtar/append.c and searching for 'failed to lookup fscrypt tar policy for'.... I have a feeling that it looks up the wrong hex ''7778812a000000000000000000000000'' instead of the 16 hexadecimal characters of '000000007778812a'

 

[Nebrassy]

New build is up

Fixed recovery settings not persisting
Fixed flashing older builds and firmware
added erofs support
Some misc fixes

 

[spider1163]

Does it fix the fscrypt policy for backup/restore?

 

[Nebrassy]

Does it fix the fscrypt policy for backup/restore?

No

 

[Mthw]

I just tried the linked version and it doesn't start. I did 'fastboot boot twrp.img' which did reboot me to TWRP but then it got stuck on the splash screen (?) and after a while screen started flashing like a bootloop. Did I do something wrong? I am currently on PixelOS with OrangeFox recovery.

I don't know what I did wrong but it works now with the latest version.

 

[philip130683]

with new version of twrp, it goes in fastboot mode. anyone have tested?

 

[Mthw]

with new version of twrp, it goes in fastboot mode. anyone have tested?

What are you saying? The latest version works well.

 

[philip130683]

What are you saying? The latest version works well.

sorry. i meant the redmi note 10 pro.

 

[alonsoj636]

sorry. i meant the redmi note 10 pro.

this isn't for the redmi note 10 pro
is for the normal redmi note 10

 

[Zirila]

Data restoration breakes the system. After backup and restore I get mi logo two times and recovery autostart. Rom PE a12 and PE+ a12. Stock kernel, no root or modifications.

Thank you for this 12.1 release Nebrassy. Decrypting /data works flawlessly.

But restoring a TWRP backup results into the problem described here above. Screenshot of the TWRP log here after it restarts into TWRP instead of the OS.

Been playing around with TWRP backups on this phone a year ago. You have to remove the device password/pattern in Android before you make a TWRP full backup. Then you can restore the backup. Well in theory. If i remember correctly, the best practice was to just flash the new ROM and only restore the /data partition (that was made without encryption password).

I never relied on this, though. Always make an app-wise backup as second safety option.

 

[PTX64]

Been playing around with TWRP backups on this phone a year ago. You have to remove the device password/pattern in Android before you make a TWRP full backup. Then you can restore the backup. Well in theory. If i remember correctly, the best practice was to just flash the new ROM and only restore the /data partition (that was made without encryption password).

I never relied on this, though. Always make an app-wise backup as second safety option.

I relied on my Note 10 like I did on my Linux systems, which was a very wise decision before making backups .

Asuming that the latest original firmware is used ( mojito_global_images_V13.0.9.0.SKGMIXM_20220616.0000.00_12.0_global_2e8598ffa6.tgz ), the /data partition is using a F2FS filesystem with FSCRYPT (ENCRYPTION_POLICY V2) file based encryption on top of it.

Each encrypted directory tree in /data is protected by a/the master key (per user / derived from a screenlock pin or password hashing), which may be a default master key when you've disabled the screenlock all together.

This TWRP 12.1 version can decrypt or unlock the default master key / data partition, which is fine. The only problem is that the TWRP sourcecode is unable to backup and restore the encryption policies of most or all encrypted directory trees, which is required.

To be exact, found in /vendor/etc/fstab.default when mounted in TWRP:

/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt latemount,wait,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,metadata_encryption=aes-256-xts:wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,quota,reservedsize=128M,checkpoint=fs

 

[x3r0.13urn]

New build is up

Fixed recovery settings not persisting
Fixed flashing older builds and firmware
added erofs support
Some misc fixes

I can't flash anything from inside twrp using 03/07 build. Even sideload always fails, had to revert to official 3.6.2-11.0 then it works again (sideload)

 

[maximum117]

Been playing around with TWRP backups on this phone a year ago. You have to remove the device password/pattern in Android before you make a TWRP full backup. Then you can restore the backup. Well in theory. If i remember correctly, the best practice was to just flash the new ROM and only restore the /data partition (that was made without encryption password).

I never relied on this, though. Always make an app-wise backup as second safety option.

Of course I removed pass/pin etc. before making backup and restoration. And I tried restore data partition only. More of that, to the official twrp if tou make backup with the pin/pass/fingerprint, after that wiped data, after that reboot to the system and set pin/pass/fingerprint that you used when made backup and after that restore backup you can boot system and get black desktop. But! if you reboot you get full worked system

 

[truevision]

I'm on MIUI 13 rooted, can I flash TWRP with fastboot flash boot <filename> without lose all data ?

 

[Mthw]

I'm on MIUI 13 rooted, can I flash TWRP with fastboot flash boot <filename> without lose all data ?

Yes, but not the way you said. You need to use 'fastboot boot twrp.img' and then in twrp there is an option 'flash current twrp' or something like that.

 

[truevision]

Yes, but not the way you said. You need to use 'fastboot boot twrp.img' and then in twrp there is an option 'flash current twrp' or something like that.

ok, thanx.
But I do fastboot flash in another rom and it was good, is a bad choice or I have only lucky ?