[RECOVERY][12][ROSY] TWRP Recovery 3.7.0_12 [UNOFFICIAL]

Search This thread

baunilla

Recognized Developer
Apr 16, 2019
448
1,077
New build is up.
3.6.2_11-7
Code:
- Moved CryptfsHw service to vendor
- Relinked vendor.display.config libs
- Fixed MTP file transfers above 4GB
- Excluded Python from build
 

maziusK

Member
Dec 23, 2015
6
0
So i have a small question my data partition shows encrypted (FBE) on android 11 Miui 12.5 redmi note 8 on twrp after flashing it and cannot boot into system. I have read this happens because after i booted into twrp i swiped allow modifications, this triggered a security measure to prevent booting (i dont know how, i tried dirty flash same rom, also system.img, boot.img, patched vbmeta.. and still doesnt boot seemingly forcing me to format data). I realized that if i change encryption status through fstab file the phone goes from bootlooping into recovery to being stuck on rom logo.

Im concerned with regaining access to my data, i still have backups of original system.img and boot.img after the bootloop happened, its possible to decrypt it? Any twrp i tried fails asking for my pin or decrypting through command, but they seem to claim that are able to decrypt A11 FBE?
 

LGD Breath

Senior Member
Sep 15, 2021
210
20
22
West Bengal , India
So i have a small question my data partition shows encrypted (FBE) on android 11 Miui 12.5 redmi note 8 on twrp after flashing it and cannot boot into system. I have read this happens because after i booted into twrp i swiped allow modifications, this triggered a security measure to prevent booting (i dont know how, i tried dirty flash same rom, also system.img, boot.img, patched vbmeta.. and still doesnt boot seemingly forcing me to format data). I realized that if i change encryption status through fstab file the phone goes from bootlooping into recovery to being stuck on rom logo.

Im concerned with regaining access to my data, i still have backups of original system.img and boot.img after the bootloop happened, its possible to decrypt it? Any twrp i tried fails asking for my pin or decrypting through command, but they seem to claim that are able to decrypt A11 FBE?
Bro it is redmi 5 thread
 

ItsMe6789

Member
Jan 2, 2019
5
0
I can't go back orangefox... 😭
 

Attachments

  • IMG20221201061952.jpg
    IMG20221201061952.jpg
    2 MB · Views: 26

LGD Breath

Senior Member
Sep 15, 2021
210
20
22
West Bengal , India
I can't go back orangefox... 😭
I'll still prefer you to stick with twrp by baunilla ... NFS built of ofox have bootloop issue still this date .... I flashed ofox 12.1 to flash bananadroid 13 & device got bootloop after flashing complete of ofox 12.1 ... Stick with twrp by baunilla ... & use builds those are support twrp latest ... Like Los by baunilla // pos , rice by aditya ... No bootloop or recovery brick issue so far ... Hope u understand ... Ofox have always bootloop issue ( in 2gb every times )
 

ItsMe6789

Member
Jan 2, 2019
5
0
I'll still prefer you to stick with twrp by baunilla ... NFS built of ofox have bootloop issue still this date .... I flashed ofox 12.1 to flash bananadroid 13 & device got bootloop after flashing complete of ofox 12.1 ... Stick with twrp by baunilla ... & use builds those are support twrp latest ... Like Los by baunilla // pos , rice by aditya ... No bootloop or recovery brick issue so far ... Hope u understand ... Ofox have always bootloop issue ( in 2gb every times )
ok, thanks for the advice
I will use this recovery with crdroid 9.0
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    New build is up.
    3.7.0_12-4
    Code:
    - Updated Gatekeeper service definition
    - Disabled schedutil iowait_boost
    - Fixed FG Rslow charger compensation
    1
    I can't go back orangefox... 😭
    Try to format data on baunilla's TWRP and flash OrangeFox after. It may work..

    You'll have to set-up your phone from scratch again though.
  • 20
    2HtVAF5zfNMlmKhF0QYqCSr1rsstB1btNfdKl7WvGTcZkOSKCYNxdXwsSizx9VhiPg=w240


    Team Win Recovery Project 3.x
    Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its 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.

    Code:
    /*
    * Your warranty is now maybe void.
    *
    * I am not responsible for bricked devices, dead SD cards, thermonuclear
    * war, or you getting fired because the alarm app failed. Please do some
    * research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    *
    */

    TWRP 3.7.0_12 for Xiaomi Redmi 5 (rosy)
    • Android 12.1 AOSP-based recovery
    • FBE + FDE Data decryption support
    • USB MTP & Sideload support
    • System as root (SAR)

    Installation

    Method 1. Flash from fastboot:
    • Reboot to Bootloader (fastboot mode)
    • Type fastboot flash recovery twrp-xxxx-rosy.img
    • Reboot device or type fastboot reboot

    Method 2. Flash from recovery:
    • Reboot to Recovery
    • Select Install then Install Image
    • Select file twrp-xxxx-rosy.img
    • Select partition Recovery
    • Flash the image and reboot



    Information
    TWRP Recovery for the Xiaomi Redmi 5

    OS Version: Android 12.1
    OS Kernel: Linux 4.9.x
    Based On: AOSP

    Recovery Source: GitHub
    Kernel Source: GitHub
    Device Source: GitHub

    Created 2020-12-28
    Last Updated 2022-12-01
    5
    New build is up.
    3.7.0_12-0
    Code:
    - Twrp release: 3.7.0 based on Android 12.1
    4
    New build is up.
    3.6.2_12-0
    Code:
    - Twrp release: 3.6.2 based on Android 12.1
    - Added FBE + FDE Data decryption support
    4
    New build is up.
    3.7.0_12-4
    Code:
    - Updated Gatekeeper service definition
    - Disabled schedutil iowait_boost
    - Fixed FG Rslow charger compensation
    4
    New build is up.
    3.7.0_12-3
    Code:
    - Fixed supply type probe issue at bootup
    - Bumped power-supply limit for pmic voters
    - Reduced kernel wakelocks from FuelGauge