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

[Perru]

Need to "fix bootloop"-option as officially described by twrp-team here?

• "NOTE: You also need to use the "Fix Recovery Bootloop" option present in the same Advanced Tab. Use that option after you have installed the recovery ramdisk successfully to avoid boot loops happening from installing TWRP Permanently."

or is that fixed in the new nebrassy-version "TWRP-3.6.2-alioth-Nebrassy-03-07-22.img" from here?
(especially, as in my actually installed twrp-version "3.6.2_12-RedmiPOCOF3_v3.7_A12" / "twrp-3.6.2_12-v3.7_A12-alioth-skkk.img" there is no more option "fix recovery bootloop" under "Advanced"...)

EDIT:
Just updated my TWRP successfully

• from "twrp-3.6.2_12-v3.7_A12-alioth-skkk.img"
• to "TWRP-3.6.2-alioth-Nebrassy-03-07-22.img"

by

1. Downloading new twrp-img-file from here
2. Copy downloaded img to internal storage of my Poco F3
3. Settings \ My Device \ 13 MIUI version (icon) \ ... (3-button-menu top right) \ Reboot to Recovery mode <Yes>
4. TWRP splash screen (nearly 30 seconds, patience) \ Insert your password (PIN \ Pattern)
5. Advanced \ Install Recovery Ramdisk \ <select the TWRP file from Step 1> \ <Swipe to Install>
6. Press <Reboot System> \ Done

No need / no more otion to "fix bootloop" und "advanced", seems, as official guide needs an update

 

[pakino2004]

Need to "fix bootloop"-option as officially described by twrp-team here?

• "NOTE: You also need to use the "Fix Recovery Bootloop" option present in the same Advanced Tab. Use that option after you have installed the recovery ramdisk successfully to avoid boot loops happening from installing TWRP Permanently."

or is that fixed in the new nebrassy-version "TWRP-3.6.2-alioth-Nebrassy-03-07-22.img" from here?
(especially, as in my actually installed twrp-version "3.6.2_12-RedmiPOCOF3_v3.7_A12" / "twrp-3.6.2_12-v3.7_A12-alioth-skkk.img" there is no more option "fix recovery bootloop" under "Advanced"...)

EDIT:
Just updated my TWRP successfully

• from "twrp-3.6.2_12-v3.7_A12-alioth-skkk.img"
• to "TWRP-3.6.2-alioth-Nebrassy-03-07-22.img"

by

1. Downloading new twrp-img-file from here
2. Copy downloaded img to internal storage of my Poco F3
3. Settings \ My Device \ 13 MIUI version (icon) \ ... (3-button-menu top right) \ Reboot to Recovery mode <Yes>
4. TWRP splash screen (nearly 30 seconds, patience) \ Insert your password (PIN \ Pattern)
5. Advanced \ Install Recovery Ramdisk \ <select the TWRP file from Step 1> \ <Swipe to Install>
6. Press <Reboot System> \ Done

No need / no more otion to "fix bootloop" und "advanced", seems, as official guide needs an update

this new version is only for A12 or for A11 as well? thank you for your response in advance

 

[uvzen]

When I enter TWRP is there a big lag for a few seconds and there is nothing I can do. Skkk twrp doesn't have this problem.

 

[Perru]

When I enter TWRP is there a big lag for a few seconds and there is nothing I can do. Skkk twrp doesn't have this problem.

yes, as i wrote: "nearly 30 seconds, patience" - dont know the reason, i am not the dev / publisher

 

[ItielO]

When trying to do

fastboot boot twrp.img

instead of booting to TWRP so i can

Flash current booted TWRP

i get booted to system.
Solutions?

 

[bmwbasti]

What´s the problem (with every version of TWRP that is allegedly able to decrypt data in MIUI13/Android 12...) when there is no input pattern for data-decryption at the boot/start of TWRP?
When i manually try to decrypt data there ist always a "password failed" error eventhough the password is definitly correct. It´s the same password which i have to put in at startup after th phone asked for the SIM-PIN.

 

[Veiranx]

What´s the problem (with every version of TWRP that is allegedly able to decrypt data in MIUI13/Android 12...) when there is no input pattern for data-decryption at the boot/start of TWRP?
When i manually try to decrypt data there ist always a "password failed" error eventhough the password is definitly correct. It´s the same password which i have to put in at startup after th phone asked for the SIM-PIN.

If decrypting via that way does not work, consider removing the security method altogether to see if that works.

 

[eliezerjk90]

I used the last version but the bug of settings not saved is still there. Does anyone experience the same? Or is it just me?

 

[gigavolthavoc07]

Hello nebrassy, is this working for Dirty flashing? like I'm currently in 13.0.3 and i want to flash 13.0.4 via twrp, is it doable or not?

 

[barturblits]

Had a faulty LOS update. Could not get it to boot so tried to restore the twrp backup I made just before updating. It warned about that the pattern should be removed before restoring. But that wasnt possible at that time and I also was under the impression that the latest version would not need that anymore because twrp decrypts data with pattern correctly. But restore failed, wouldnt boot up. Back to fresh install and neo backup. Up and running again.

 

[Deleted member 11975321]

Hi, how does decryption work? I've originally used Swipe + Fingerprint to unlock my phone, but even after switching to pin + fingerprint, then pin, then nothing, TWRP still can't decrypt data.

 

[ferreol-fr]

Hello,
Has anyone tried and succeeded, backing up and restoring the data partition on A12 with TWRP?

 

[fbirraque]

Hello,
Has anyone tried and succeeded, backing up and restoring the data partition on A12 with TWRP?

Didn't worked for me on Poco F3 running MIUI.eu Weekly.

 

[jkmaxfli]

I have to say that it is quite a disappointment. Poco F3 has been on the market for a long time and there is still no functional backup and recovery of the entire system via TWRP Recovery. Shame.

 

[DarthJabba9]

I have to say that it is quite a disappointment. Poco F3 has been on the market for a long time and there is still no functional backup and recovery of the entire system via TWRP Recovery. Shame.

It is not a Poco F3 issue. It is a wider Android 12 recovery problem. For further information, see Android 12 and data partition backup/restore.

Anyone who wishes to help with a solution is welcome to submit patches to the twrp Gerrit.

Edit, 6 August 2022: this issue has now been resolved upstream, and will require a new build of the recovery.

 

[ferreol-fr]

I have to say that it is quite a disappointment. Poco F3 has been on the market for a long time and there is still no functional backup and recovery of the entire system via TWRP Recovery. Shame.

As I read here, it's not a POCO F3 or a MIUI failure. The bug is related to FBE v2 encryption.
The other bug is the silence on this issue!
[edit]
@DarthJabba9 thank you for your support on OrangeFox (the only one to be clear on that issue)
[/edit]

 

[Adam Hui]

It is not a Poco F3 issue. It is a wider Android 12 recovery problem. For further information, see Android 12 and data partition backup/restore.

Anyone who wishes to help with a solution is welcome to submit patches to the twrp Gerrit.

This is most likely the answer why "android third party security trigerred" when i restored whole backup partition of my current pixel os by latest nebrassy's unofficial twrp.
I lost over my 40gb data since full wipe is the only sort of fastboot stuck.

 

[yeaka]

this twrp didn't work for my f3. it just went to a black screen/phone turned off. i used SKKK TWRP to be able to boot and install TWRP.

 

[Shyonnu]

Poco f3 global 13.0.4.0 / A12 tried / security update 1 June 2022:
1. skkk twrp
2. TWRP-3.6.2-alioth-Nebrassy-03-07-22.img
both result in a black screen even after waiting for 3 minutes.

Can someone recommend flashing MIUI. eu version with TWRP built in?
Would be grateful for any hints / download links links?
many thanks in advance!

 

[reg66]

Poco f3 global 13.0.4.0 / A12 tried / security update 1 June 2022:
1. skkk twrp
2. TWRP-3.6.2-alioth-Nebrassy-03-07-22.img
both result in a black screen even after waiting for 3 minutes.

Can someone recommend flashing MIUI. eu version with TWRP built in?
Would be grateful for any hints / download links links?
many thanks in advance!

Just a thought, have you checked you're using a USB 2.0 port instead of 3.0 etc, they can act up... and it is an Intel sys, rather than Ryzen...