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

Development [RECOVERY] [UNOFFICIAL] TWRP-3.5.1 [20210702]

Search This thread

raz123

Senior Member
Oct 25, 2010
239
48
You can backup and restore multiple times IF you're not going to perform a format data.

If you do backup -> format data -> restore, your files are gone because of the limitation of A/B.

Why?

Because decryption keys wont work on a new partition/formatted data.

Is this a forever limitation?

Would disabling encryption bypass this limitation?
 

vasishath

Senior Member
Nov 30, 2013
884
5,342
30
Chandigarh
Xiaomi Poco F1
Xiaomi Poco F3
New build uploaded.

CHANGES:-

* Fixed TWRP auto flash error after flashing ROM. (It was due to magisk)
* Fixed fastbootd commands returning "command not allowed on locked device"


Limitations have been updated to mention an issue with flashing magisk and backuptool after ROM flash :-

Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.

Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
 
Last edited:

noslen69

Senior Member
Sep 23, 2015
100
4
New build uploaded.

CHANGES:-

* Fixed TWRP auto flash error after flashing ROM. (It was due to magisk)
* Fixed fastbootd commands returning "command not allowed on locked device"


Limitations have been updated to mention an issue with flashing magisk and backuptool after ROM flash :-

Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.

Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
 

GtrCraft

Recognized Developer
Jun 3, 2013
6,656
17,329
Moto G5 Plus
Xiaomi Poco F1
Thanks for the update, I do have a question though.
I have yet to find a scenario where I don't have to use format data when switching roms.
I build them al myself and they have the neede commit. But everytime to I try to switch I can't flash anything else or I have bootloop. And have to format data in the end to make it work. Do I miss something? Or is there a certain order to flash things?
 

vasishath

Senior Member
Nov 30, 2013
884
5,342
30
Chandigarh
Xiaomi Poco F1
Xiaomi Poco F3
Thanks for the update, I do have a question though.
I have yet to find a scenario where I don't have to use format data when switching roms.
I build them al myself and they have the neede commit. But everytime to I try to switch I can't flash anything else or I have bootloop. And have to format data in the end to make it work. Do I miss something? Or is there a certain order to flash things?
along with the commit, also check the vendor security patch version. It should be >= ur current rom
 

Dgonix

Senior Member
Aug 10, 2013
143
19
Hi I have a problem when using TWRP-3.5.2-alioth. In Fastboot, when I do Advanced-Flash current TWRP, it crumbles. I reboot - data is not available, so I can't install the firmware on the current MIUI xiaomi.eu.
 
  • Like
Reactions: jurarj

Mother_Teresa

Senior Member
Jul 11, 2012
165
19
@Dgonix
Just to share my similar successful experience;

Using the nesbrassy twrp -> https://forum.xda-developers.com/t/best-method-to-install-twrp-on-poco-f3.4313205/#post-85415277


I just booted the same twrp from fastboot, used pattern to decrypt and after succesful boot did the advanced->flash current twrp.

Using default (miui global 12.5.3) which was already rooted with magisk 12.3 before.
Reason I flashed the recovery instead of just booting it was because some update was enforced (reboot after) and lost my root (adblock ;)).

My guess as to your failing would be the decryption. How did you get to decrypt on initial booting twrp?
Also, using alternative kernel?
 
Last edited:

jozefkuruvila

Member
Jun 28, 2017
16
1
Hi, I'm facing an issue while flashing Vasi's latest twrp (Released on: 25/07/'21). After flashing the twrp, I am unable to boot back into twrp using power + volume up. What happens is that the twrp logo will come and then after a few seconds miui will start to load. These are the steps i followed:

Firstly removed fingerprint and pin
Used the command fastboot boot twrp.img
The recovery comes up
Then go to advanced
Fash current twrp and swipe to flash
Flash is completed. Reboot to system.
Then I turn off again. Try entering twrp using power + volume up. But the twrp screen comes and then phone boots to miui.

Anyone faced similar issues?
 

Mother_Teresa

Senior Member
Jul 11, 2012
165
19
Hi, I'm facing an issue while flashing Vasi's latest twrp (Released on: 25/07/'21). After flashing the twrp, I am unable to boot back into twrp using power + volume up. What happens is that the twrp logo will come and then after a few seconds miui will start to load. These are the steps i followed:

Firstly removed fingerprint and pin
Used the command fastboot boot twrp.img
The recovery comes up
Then go to advanced
Fash current twrp and swipe to flash
Flash is completed. Reboot to system.
Then I turn off again. Try entering twrp using power + volume up. But the twrp screen comes and then phone boots to miui.

Anyone faced similar issues?



- Maybe you should select a different slot (in twrp) A/B?

- Have you tried an alternative twrp? (I am using the nesbrassy twrp -> https://forum.xda-developers.com/t/best-method-to-install-twrp-on-poco-f3.4313205/#post-85415277)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 45
    home.png
    backupname.png

    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.


    FEATURES AND FIXES:
    1. No need to reboot TWRP after flashing ROM, to flash gapps or any other zips. All zips you flash after a ROM will automatically go to the new slot.
    2. No need to flash TWRP everytime after flashing a ROM. TWRP automatically flashes itself after a zip (Controllable via a toggle)
    3. Supports Hentai OS encrypted devices
    4. Supports flashing MIUI zips
    5. Supports Vibration
    6. Supports wiping data without wrecking encryption.

    BUGS:

    On encrypted devices, if u unmount and remount /data, it will show garbage files in storage. This is because of metadata encryption and to fix it, reboot recovery.


    SUPPORTS AND TESTED ON:
    Mi11x (aliothin)


    UNSUPPORTED (BUT MAY WORK):
    Poco F3, Redmi K40 (alioth)


    FLASHING INSTRUCTIONS:

    Boot into attached boot.img using the following command:
    Code:
    fastboot boot twrp-aliothin.img

    Once booted, go to Advanced -> Press "Flash current booted TWRP"

    KNOWN LIMITATIONS:

    The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-

    1. You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
    2. You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
    3. Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
    4. Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
    5. If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
    6. If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
    7. If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
    8. Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
    9. Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.

    CREDITS:

    @Nebrassy for original TWRP and device tree. I also repurposed some of his commits from gerrit.


    SOURCE CODE:

    Kernel (Prebuilt)
    : https://github.com/ArrowOS-Devices/android_kernel_xiaomi_alioth


    DOWNLOADS:

    https://drive.google.com/file/d/1oY5WxfXYPRLumCcaPPFGuq9OhtB3CM_X/view?usp=sharing


    MD5:- 0909f61c83ce9876843dabba5bf1247e


    TELEGRAM GROUP LINKS:

    https://t.me/PocoF3GlobalOfficial
    https://t.me/pocoF3GlobalUpdates
    22
    New build uploaded. Download link stays the same.

    CHANGES:

    * Fix a bug due to which some ROMs failed to flash if currently on a custom ROM.
    * Fix "flash current TWRP" failing when decryption failed.
    * Fix data wipe not wiping ROM data completely.

    Also, it seems if the ROM you are flashing does not support encryption, you can format your data partition after a reboot (as opposed to what I mentioned in the known limitations section earlier.)
    14
    New update released.


    CHANGE:-

    * Fix a bug in data wipe with password/pattern set
    12
    New build uploaded.

    CHANGES:-

    * Fixed TWRP auto flash error after flashing ROM. (It was due to magisk)
    * Fixed fastbootd commands returning "command not allowed on locked device"


    Limitations have been updated to mention an issue with flashing magisk and backuptool after ROM flash :-

    Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.

    Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.