[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tomek0000:
Good to read it. Maybe you do not have too much info , but I can help (new version looks more sofisticated) :

SKKK TWRP v3.8.3 - A12 | TWRP 3.6.2

Updated: 13/07/'2022

Download (https://dl.akr-developers.com/?dir=skkk/TWRP/A12) | V3.8.3 A12 (https://dl.akr-developers.com/?file=skkk/TWRP/A12/v3.8.3_A12/[BOOT]3.6.2_12-RedmiK40-RedmiPOCOF3_v3.8.3_A12-alioth-skkk_4f7299ea.img)

Changelog (https://telegra.ph/TWRP-by-Skkk---alioth-07-13)

[865 series]: Mi 10/Mi 10pro/ Mi 10 Extreme Commemorative Edition/k30pro/k30s Extreme Commemorative Edition

[870 Series]: Mi 10s/k40/k40s/ Mi 12x

[888 series]: Mi 11/Mi 11pro/Mi 11ultra ?8G1?: Mi 12/Mi 12pro/k50g

Features:

1. Support data decryption (Android 12 password decryption)

2. Support flashing > 4G packages

3. MTP supports transferring >4G files

4. ADB sideload supports >4G files

5. Fastbootd

6. OTG supports exfat

7. MIUI update support (see below)

8. Vibration if there is no part in TWRP The function option indicates that the device does not support it

!!! Description of some TWRP warning prompts:

Partition mount failure

1: It is normal that the xx partition may fail to mount after the VAB (virtual a/b) device has been flashed rom slot, save the trouble of restarting!

(The default is to use Magisk patching, if you want to use Magisk Alpha, please change it in the settings!

The function is equivalent to the patching boot.img function of the magisk manager)

2: Some official repackages use super.img as the flashing file. After flashing, it indicates that the xx partition failed to mount,

and restarting the system indicates that the system is not installed. This is a normal phenomenon. As long as twrp prompts to flash successfully!

The update failed when flashing the package:

1. There is a scratch partition . The system partition is set to be readable and writable. Increase the scratch partition detection.

If this partition is not allowed to continue to operate scratch, you can check the Android documentation.

It will occupy super space and cause the update to fail (including miui).

The official rec appears that this partition needs to be deleted, and there are 4 methods:

Method 1:--Enter miui-computer to connect to usb and execute the adb command: adb enable-verity

Method 2:--Wire brush(stock?)once, the wire brush package has super.img Can solve the problem

Method 3:--Enter the latest twrp, advanced-terminal execute the command: lptools remove scratch

vab device Do not use lptools, if there is a problem, you can flash the complete package (a, b2 slots must be flashed)

Method 4:-- twrp-restart-fastboot, after entering fastbootd mode, use the fastboot command to delete the partition: fastboot delete-logical-partition scratch

2:The package downloaded and decrypted by the non-vab device through the system update cannot be directly selected,

but it can be supported by enabling miui update and from The system update restarts to complete the update.

Note: A11 stands for Android 11, A12 stands for Android 12, A12 only supports Android 12

Three ways to enter Fastbootd:

a. Enter TWRP-restart-Fsstboot

b. adb reboot fastboot

c. fastboot reboot fastboot

!!!The img file provided is forbidden to flash to the boot partition under any circumstances

There are 4 types of flashing methods for ordinary devices:

All IMG files are prohibited from flashing to the BOOT partition! Labels:

[BOOT]:

1. Use: fastboot boot rec.img to temporarily boot! ! !

2. VAB device: Advanced - flash current TWRP/install recovery ramdisk

[REC]:

1. Only flash recovery partition: fastboot flash recovery|recovery_ab|recovery_a|recovery_b rec.img

2. Boot to twrp again: fastboot reboot recovery

[REC_BOOT]: [BOOT] + [REC]

[REC] tags can be flashed using not limited to the following tools, and 5 methods are provided: (All VAB devices must be flashed! )

1. The backup and restore function in the beep tool [Scene5] (below), manually select the complete path, otherwise there is no response (below). py transaction

2. Other apps or tools - flash the image to the recovery|a|b|ab partition

3. Non-VAB devices have TWRP: enter the TWRP and flash the corresponding img to the recovery partition.

4. The VAB device already has TWRP: Advanced - install recovery ramdisk Select the new twrp image file to update TWRP 5.

Fastboot method:

Brush: fastboot flash recovery|recovery_ab|recovery_a|recovery_b rec.img

Start: fastboot reboot recovery

[BOOT] OK There is one method for temporary boot, or you can use other tools to temporarily boot:

1. Fastboot method:

first boot to TWRP: fastboot boot rec.img

VAB device can install TWRP: Advanced - flash into the current TWRP/install Recovery ramdisk

to set the system partition read After writing, if you want to modify it in twrp?,

use the advanced-terminal command ? to remount it with rw, twrp is mounted as read-only by default, and I will not change it to read-write

Please baring teeth use twrp to mount the corresponding partition. After mounting, execute the corresponding command to remount

mount -o rw,remount /system_root

mount -o rw,remount /vendor

mount -o rw,remount /product mount -o rw, remount

/system_ext

The file manager

twrp has different settings/options in vab and non-vab. If not, it does not support this feature, for example: MIUI update...

There is a risk in flashing the machine, and your data cannot be guaranteed to be 100% safe. In order to reduce unnecessary losses , please back up your data to another location!