• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Development [RECOVERY] [UNOFFICIAL] TeamWin Recovery Project

Search This thread

Jaftdroid

Member
Apr 6, 2021
22
8
Hello everyone,

POCO X3 Pro user here.

Anyone else experiencing like a 3 to 5 seconds freeze on TWRP boot? Like, you can't do any action during that period. Is it normal or...

Best regards! Love this recovery.
 
  • Like
Reactions: pxotas

Naveenthemi

Senior Member
Just putting it out here, this TWRP works perfectly, no issues so far except for the delayed touch response at first (a user said the delay is for drivers to load, but I have never come across that delay in other devices running TWRP). It can decrypt internal storage and was able to flash xiaomi.eu and Magisk smoothly.

Thank you for your work.
 
  • Like
Reactions: kd276

Raviu

Member
Jun 11, 2021
8
1
Hey,
I've taken an encrypted backup using this TWRP
Now I need to restore it, it shows the backup number something like b9e02c91
But the problem now, it does not ask for decryption password and does not show any "Partitions to restore"

Please help me to recover my data
After taking the backup I've pulled the whole TWRP dir over adb, now I pushed it back.. I do this on other devices and it works.
 

ValgarBaldr

Member
Aug 14, 2021
12
3
Hi! I can't flash custom ROM using TWRP, I think I don't know how to do it. I wanted to install crdroid but in the post the instructions are "flash this, this and this, you're done" and I'm new to this.

I'm getting this error:
Installing zip file '/external_sd/crDroidAndroid-11.0-20210620-hotdogb-v7.7.zip'
Unmounting System...
I:AB zip
Flashing A/B zip to inactive slot: A
I:Mount: Unable to find partition for path '/system'
I:Copied file /system/bin/sh to /tmp/sh
Failed to parse build number in post-build-incremental=eng.mukesh.20210620.235802.
Package is for product OnePlus7T but expected vayu
To flash additional zips, please reboot recovery to switch to the updated slot.
I:Install took 0 second(s).
Error installing zip file '/external_sd/crDroidAndroid-11.0-20210620-hotdogb-v7.7.zip'
Updating partition details...
I:checking for twrp app
I:Data backup size is 4484MB, free: 100457MB.
...done
 

ValgarBaldr

Member
Aug 14, 2021
12
3

Nebrassy

Recognized Developer
Sep 17, 2015
972
1,806
Lattakia
Xiaomi Poco X3 Pro
Hey,
I've taken an encrypted backup using this TWRP
Now I need to restore it, it shows the backup number something like b9e02c91
But the problem now, it does not ask for decryption password and does not show any "Partitions to restore"

Please help me to recover my data
After taking the backup I've pulled the whole TWRP dir over adb, now I pushed it back.. I do this on other devices and it works.
Make sure you put it in the right directory, there should be two directories under backup, device ID, then name of backup and inside of that, the images

Then grab recovery.log
 

Raviu

Member
Jun 11, 2021
8
1
Make sure you put it in the right directory, there should be two directories under backup, device ID, then name of backup and inside of that, the images

Then grab recovery.log
Attached recovery log
And here is output of `ls` to confirm path:
```
$ adb shell ls /data/media/0/TWRP/BACKUPS/b9e02c98/1969-12-31--19-41-35_RQ3A210605005_release-keys
bluetooth.emmc.win
boot.emmc.win
data.f2fs.win000
data.f2fs.win001
data.f2fs.win002
data.f2fs.win100
data.f2fs.win200
data.f2fs.win300
data.f2fs.win400
data.f2fs.win500
data.f2fs.win600
data.f2fs.win700
data.f2fs.win800
data.info
dsp.emmc.win
dtbo.emmc.win
efs1.emmc.win
efs2.emmc.win
efsc.emmc.win
efsg.emmc.win
modem.emmc.win
recovery.emmc.win
recovery.log
super.emmc.win
```
 

Nebrassy

Recognized Developer
Sep 17, 2015
972
1,806
Lattakia
Xiaomi Poco X3 Pro
Attached recovery log
And here is output of `ls` to confirm path:
```
$ adb shell ls /data/media/0/TWRP/BACKUPS/b9e02c98/1969-12-31--19-41-35_RQ3A210605005_release-keys
bluetooth.emmc.win
boot.emmc.win
data.f2fs.win000
data.f2fs.win001
data.f2fs.win002
data.f2fs.win100
data.f2fs.win200
data.f2fs.win300
data.f2fs.win400
data.f2fs.win500
data.f2fs.win600
data.f2fs.win700
data.f2fs.win800
data.info
dsp.emmc.win
dtbo.emmc.win
efs1.emmc.win
efs2.emmc.win
efsc.emmc.win
efsg.emmc.win
modem.emmc.win
recovery.emmc.win
recovery.log
super.emmc.win
```
You didn't attach recovery log
 

Raviu

Member
Jun 11, 2021
8
1
You didn't attach recovery log
I'm sure I've attached it, not sure why it's missed.

Any way, I've looked into the .log and found that it's looking for different backup dir name, so I changed it and it got working.. But it failed at later stage

I could get a list of partitions and could restore Boot and Super (including system) successfully.
But when I try to restore data, it reaches almost 80% then it fails:
I tried all different combinations of format data, factory reset, system reboot, and so on, no success
It always ends with this error
extractTarFork() process ended with ERROR: 255
Here is the log part for the error:

attempting to restore policy: a1980aad026a56fb9f25a1e54ac2152f
==> extracting: //data/vendor_ce/10/ (mode 40771, directory)
error looking up fscrypt policy for '//data/vendor_ce/10/' - 2CE10
tar_extract_file(): failed to extract //data/vendor_ce/10/ !!!
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/60caabed/1969-12-31--19-41-35_RQ3A210605005_release-keys/data.f2fs.win100'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/60caabed/1969-12-31--19-41-35_RQ3A210605005_release-keys/data.f2fs.win100' in thread ID 1
I:Joined thread 1.
I:Thread 1 returned an error -2.
Error during restore process.
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
I:eek:peration_end - status=1
 

Nebrassy

Recognized Developer
Sep 17, 2015
972
1,806
Lattakia
Xiaomi Poco X3 Pro
I'm sure I've attached it, not sure why it's missed.

Any way, I've looked into the .log and found that it's looking for different backup dir name, so I changed it and it got working.. But it failed at later stage

I could get a list of partitions and could restore Boot and Super (including system) successfully.
But when I try to restore data, it reaches almost 80% then it fails:
I tried all different combinations of format data, factory reset, system reboot, and so on, no success
It always ends with this error
extractTarFork() process ended with ERROR: 255
Here is the log part for the error:

attempting to restore policy: a1980aad026a56fb9f25a1e54ac2152f
==> extracting: //data/vendor_ce/10/ (mode 40771, directory)
error looking up fscrypt policy for '//data/vendor_ce/10/' - 2CE10
tar_extract_file(): failed to extract //data/vendor_ce/10/ !!!
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/60caabed/1969-12-31--19-41-35_RQ3A210605005_release-keys/data.f2fs.win100'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/60caabed/1969-12-31--19-41-35_RQ3A210605005_release-keys/data.f2fs.win100' in thread ID 1
I:Joined thread 1.
I:Thread 1 returned an error -2.
Error during restore process.
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
pigz: write error code 32
pigz: abort: write error on <stdout>
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
I:eek:peration_end - status=1
Looks like user 10 can not be restored, you can try deleting that directory from the tar and try restoring again (user/10, vendor*/10)
 

Raviu

Member
Jun 11, 2021
8
1
Looks like user 10 can not be restored, you can try deleting that directory from the tar and try restoring again (user/10, vendor*/10)
Thanks you hint enabled me to Restore the backup successfully, but the system does not boot any more and keep rebooting to recovery after showing logo for a little

I did the following , as user 10 is the work profile, You gave me a hint, I did the following:
1. Format data
2. Reboot system
3. Install island and create the work profile
4. Reboot into recovery and restore the backup
5. It restored successfully

It shows the following on terminal: - log attached - I'm sure there was no lock screen when taking backup, now it asks for a password to decrypt users restored from backup, I do not know which password

I:User 0 is not decrypted.
Attempting to decrypt FBE for user 0...
Failed to decrypt user 0
Unable to decrypt with default password. You may need to perform a Format Data.
 

Attachments

  • recovery.log.zip
    7.1 KB · Views: 2
Last edited:

Nebrassy

Recognized Developer
Sep 17, 2015
972
1,806
Lattakia
Xiaomi Poco X3 Pro
Thanks you hint enabled me to Restore the backup successfully, but the system does not boot any more and keep rebooting to recovery after showing logo for a little

I did the following , as user 10 is the work profile, You gave me a hint, I did the following:
1. Format data
2. Reboot system
3. Install island and create the work profile
4. Reboot into recovery and restore the backup
5. It restored successfully

It shows the following on terminal: - log attached - I'm sure there was no lock screen when taking backup, now it asks for a password to decrypt users restored from backup, I do not know which password

I:User 0 is not decrypted.
Attempting to decrypt FBE for user 0...
Failed to decrypt user 0
Unable to decrypt with default password. You may need to perform a Format Data.
did you have a password on the system that you attempted to restore on?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hello, friends.
    I am a little bit confused about (present) capabilities of this TWRP, so I would like to make some questions.
    I am still in the unlocking process, so want to make my mind in advance about what I will face when "repairing" the X· Pro.
    The phone has come with EU stock and my idea is to keep it.
    Target; Root the stock with Magisk. ONLY
    Method: Patch the boot and flash it in boot partition
    So the idea is to

    1.- Install Magisk in the Phone
    2.- Copy boot.img in the phone
    3.- Patch the boot image
    4.- Fastboot boot this twrp
    5.- Locate the output of the step 3.- and flash it in boot partition using this twrp
    6.- Reboot to System

    Do you think this will work?

    As you are and want to continue on stock ROM, you don't need, better, it's useless to flash TWRP or any other custom recovery: once booted the stock MIUI will kill it.

    What you need to do is:

    1-be sure bootloader is really unlocked: when turning on device there will be an unlocked lock on the top of the screen, above the "MIUI"

    2- on mobile: download Magisk.apk (v23+ from official github) and install

    3-on PC: download EXACTLY same stock ROM you run on mobile, recovery file format (a .zip). Same version, location, everything.
    Open it with any ZIP tool and grab the boot.img file from it.

    4-copy the boot.img file from PC to mobile.
    On mobile: run Magisk and choose to install / patch a file / point it to boot.img
    Magisk will do its job and generate a "patched-boot.img" (details on Magisk github, on instruction / documentation section).

    5-copy the PATCHED boot.img from mobile to PC.
    On mobile: put it on fastboot mode (power + vol-)
    On PC: flash the PATCHED boot.img to mobile BOOT (by using fastboot command line)

    6-On mobile: reboot and run Magisk to finish its settings as you prefer.

    7-DO NOT re lock your bootloader. If you decide to do that sometime, ONLY do it AFTER a FULL flash of MIUI stock + reboot to check everything is fine (will replace boot + recovery + firmware + kernel + rom + remove root....everything to stock). If booting fine and clean, then only now you should relock bootloader.
    And to flash stock MIUI do NOT use TWRP or any other custom recovery, to avoid ARB (anti rollback) problems and others.
    1
    Is the rom update (miui stock) working in twrp?
    No, stock MIUI restore the stock MIUI recovery at every boot. To keep MIUI and TWRP at the same time you need to use a modded version of MIUI called Xiaomi.eu (Xiaomi.eu is also much better than stock since is also debloated and more light).
    1
    Hello, friends.
    I am a little bit confused about (present) capabilities of this TWRP, so I would like to make some questions.
    I am still in the unlocking process, so want to make my mind in advance about what I will face when "repairing" the X· Pro.
    The phone has come with EU stock and my idea is to keep it.
    Target; Root the stock with Magisk. ONLY
    Method: Patch the boot and flash it in boot partition
    So the idea is to

    1.- Install Magisk in the Phone
    2.- Copy boot.img in the phone
    3.- Patch the boot image
    4.- Fastboot boot this twrp
    5.- Locate the output of the step 3.- and flash it in boot partition using this twrp
    6.- Reboot to System

    Do you think this will work?

    It should work.
  • 32



    Introduction:

    Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully 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.

    Key Features:

    Touchscreen driven with real buttons and drag-to-scroll
    XML-based GUI that allows full customization of the layout true theming!
    Settings are saved to the sdcard and persist through reboots
    Ability to choose which partitions to back up and which to restore
    Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
    Onscreen keyboard
    Easy selection of internal/external storage

    In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.

    We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.

    Source Code:

    GitHub - https://github.com/TeamWin/android_bootable_recovery

    Gerrit Instance - http://gerrit.twrp.me

    If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.

    Hello, this is an alpha build of TWRP, for Poco X3 Pro Global/Indian (vayu/bhima)

    touch and adb work
    SD card and USB OTG are working
    Decryption is working


    Send me a beer: Crypto(Preferred) | PayPal

    Tree: https://github.com/nebrassy/device_xiaomi_vayu-TWRP

    Telegram group: https://t.me/NSSFB

    Download: https://www.androidfilehost.com/?w=files&flid=324966
    9
    new build is up

    fixed flashing stock rom on indian variant
    fixed super partition showing up twice
    added support for pstore
    fixed apex spam
    9
    new build is up

    -fixed decryption on stock
    -fixed vibration
    7
    uploaded new build, fixed adb sideload and fastbootd
    7
    new build uploaded

    - fixed kernel issue related to fastbootd