[RECOVERY][3.4.0-10][ginkgo/willow]Off/Unof TWRP for Xiaomi Redmi Note 8/8T (Stable)

Search This thread

wsdyleon

Senior Member
Feb 2, 2012
589
42
58
I can confirm the 3.5A9 from geoanto555 does work with encryption for Android 11/MIUI 12.5 (Xiaomi.eu) ROMs - I just used it yesterday.

However, please be warned - geoanto555's version for some weird reason has the /persist and /cust partitions open for formatting - I accidentally wiped my persist partition and had to extract the .img from the fastboot ROM and then flashed it with OrangeFox to get my sensors working again. There is no reason at all that any TWRP should allow you to wipe these partitions, so please be careful when using it.

Also fwiw, flashing the decrypt/dmverity zip after flashing MIUI 12.5 does work for disabling encryption, so you can use TWRP/OrangeFox with Android 11 based ROMs, as long as you're willing to part with encryption
i flashed the vendor ,persist via fastboot,still sensor dead,also tried fastboot official roms,same issue with me.
another,ask for decrypt/dmverity zip,please.
geoanto555's version can format data l
partion ,but still has problem with decrypt on android 11,
 

CommieColin

Senior Member
Nov 28, 2014
181
46
48
Albany, NY
i flashed the vendor ,persist via fastboot,still sensor dead,also tried fastboot official roms,same issue with me.
another,ask for decrypt/dmverity zip,please.
geoanto555's version can format data l
partion ,but still has problem with decrypt on android 11,
Hey dude, I would highly recommend using OrangeFox recovery to flash the persist.img to your persist partition - here's a guide I wrote about it An Easy Guide to Restoring/Repairing Your Persist Partition on Unlocked Xiaomi Phones | XDA Developers Forums (xda-developers.com)
 
  • Like
Reactions: wsdyleon

madeskjet

Member
Feb 19, 2021
14
1
3
Xiaomi Redmi Note 8T
Android 10
LineageOS 17.1-202110215-NIGHTLY-ginkgo
TWRP 3.4.0_9-10-mauronofrio


Backup options?

Boot
Dtbo
Cache
Recovery
System Image
Vendor Image
Data
Modem
EFS
 

Uluru25

Senior Member
Nov 27, 2016
68
8
18
Redmi Note 8
Solved

HELP === HELP === HELP!
I need to format (!) my /data partition in TWRP (3.4.0.0-mauronofrio) since I made some mistakes after flasshing a new custom ROM to my Redmi Note 8T (willow) and now try to restore my nandroid (for MSMXtended XQ13, A10).
I successfully flashed the new custom rom (CrDroid 7.3, A11) and succesfully booted the rom. Then I flashed from TWRP magisk-v21.4.zip (without issues) and rebooted. Back in TWRP I realized that I flashed the ROM errounessly without disabling encryption (all folders in /data/media have cryptic names like "8nfut+wi3ZV..." and so far and so on). Thus, my idea was to reflash CrDroid followed by flashing DFE and for doing so to format (!) beforehand /data. But HERE my problems begun: if trying to format /data this failed with several red lines. I flashed the DFE.zip (hoping for a miracle which surely did not happen).

Thus I tried to reflash the CrDroid.zip withouth formatting /data beforehand but ended in a bootloop, thus powered off and booted again to TWRP.

To make my dilemma perfect I did not enable USB debugging (or authorized my PC as accepted device for USB debugging) when I booted into the new ROM (thus a check via "adb devices" does not show my phone).

My hope is to be somehow able to format /data so that I can restore my old nandroid or can again install CrDroid.

For this I also tried to wipe /data (not possible) in TWRP and also to format /data from curently f2fs to a different file system (via TWRP/Wipe/Advanced Wipe/Repair of Change File System) or to choose here "Repair File System". I also opened the Terminal within TWRP (but honestly do not know if I could solve the problem from here).

To make it short: nothing helped me to get /data formatted.

And since not being an expert I fear that I have now a serious problem...

After all these useless attempts the result if trying to format /data is like this:
---
E: Unable to decrypt FBE device
E: PageManager::LoadFileToBuffer failed to open '/data/system/storage.xml' - (Invalid argument)

Updating partition details ...
Error opening: '/data/misc/recovery" (Operation not permitted)
Error opening '/data/misc/bluedroid" (Operation not permitted)

[and so far and so on for several lines, then]
...done
Full SELinux support is present.
MTP Enabled
Wiping data without wiping /data/media...
Error opening: '/data' (Operation not permitted)
Error changing file system.

Updating partition details ...
Error opening: '/data/misc/recovery" (Operation not permitted)
Error opening '/data/misc/bluedroid" (Operation not permitted)

[and so far and so on for several lines, then]
...done
Failed to unmount '/data' (Device or resource busy)
cd "/data" && cd.. && mv "/data" "dataold" process ended with ERROR: 1
rm -rf "/data" process ended with Error: 1
Failed to unmount '/data" (Device or resource busy)

Updating partition details ...
Error opening: '/data/misc/recovery" (Operation not permitted)
Error opening '/data/misc/bluedroid" (Operation not permitted)

[and so far and so on for several lines, then ending with]
Error opening: '/data/ssh/empty' (Opeation not permitted)
...done

IS THERE ANYBODY WHO CAN GIVE ME SOME HELP TO GET MY PHONE WORKING AGAIN? I GUESS IF I CAN FORMAT /data I WILL BE ABLE TO RESTORE MY OLD ROM.

Thanks in advance!!!

Edit: Thanks to the solution proposed by breadpitt I could solve the problem!
 
Last edited:

Uluru25

Senior Member
Nov 27, 2016
68
8
18
Redmi Note 8
Try this...

go to recovery > unmount > unmount data and disable mtp > format data
Thanks! I wasn't able to clear the tick at "data" thus I can't unmount "data" but disabling MTP and then trying to format "data" led to another result than previously. I'm just checking if I can now restore my nandroid and will let you know. Thanks so far!

EDIT: Your proposed way (disabling MTP) worked, although the subsequent formatting showed some "red lines" but obviously /data was formatted so that I could restore my nandroid. As correctly mentioned by MichaelMay (even with somehow harsh words) I do not at all understand WHY this worked. Again, thanks for your very prompt answer!(y):giggle:
 
Last edited:

MichaelMay

Senior Member
Nov 15, 2020
124
51
28
Try this...

go to recovery > unmount > unmount data and disable mtp > format data

It doesn't recognise the encryption, how worthless would the encryption be if you could hack it like that? You need a proper recovery that can unencrypt data or you can't format it either.


HELP === HELP === HELP!
I need to format (!) my /data partition in TWRP (3.4.0.0-mauronofrio) since I made some mistakes after flasshing a new custom ROM to my Redmi Note 8T (willow) and now try to restore my nandroid (for MSMXtended XQ13, A10).
I successfully flashed the new custom rom (CrDroid 7.3, A11) and succesfully booted the rom. Then I flashed from TWRP magisk-v21.4.zip (without issues) and rebooted. Back in TWRP I realized that I flashed the ROM errounessly without disabling encryption (all folders in /data/media have cryptic names like "8nfut+wi3ZV..." and so far and so on). Thus, my idea was to reflash CrDroid followed by flashing DFE and for doing so to format (!) beforehand /data. But HERE my problems begun: if trying to format /data this failed with several red lines. I flashed the DFE.zip (hoping for a miracle which surely did not happen).

Thus I tried to reflash the CrDroid.zip withouth formatting /data beforehand but ended in a bootloop, thus powered off and booted again to TWRP.

To make my dilemma perfect I did not enable USB debugging (or authorized my PC as accepted device for USB debugging) when I booted into the new ROM (thus a check via "adb devices" does not show my phone).

My hope is to be somehow able to format /data so that I can restore my old nandroid or can again install CrDroid.

For this I also tried to wipe /data (not possible) in TWRP and also to format /data from curently f2fs to a different file system (via TWRP/Wipe/Advanced Wipe/Repair of Change File System) or to choose here "Repair File System". I also opened the Terminal within TWRP (but honestly do not know if I could solve the problem from here).

To make it short: nothing helped me to get /data formatted.

And since not being an expert I fear that I have now a serious problem...

After all these useless attempts the result if trying to format /data is like this:
---
E: Unable to decrypt FBE device
E: PageManager::LoadFileToBuffer failed to open '/data/system/storage.xml' - (Invalid argument)

Updating partition details ...
Error opening: '/data/misc/recovery" (Operation not permitted)
Error opening '/data/misc/bluedroid" (Operation not permitted)

[and so far and so on for several lines, then]
...done
Full SELinux support is present.
MTP Enabled
Wiping data without wiping /data/media...
Error opening: '/data' (Operation not permitted)
Error changing file system.

Updating partition details ...
Error opening: '/data/misc/recovery" (Operation not permitted)
Error opening '/data/misc/bluedroid" (Operation not permitted)

[and so far and so on for several lines, then]
...done
Failed to unmount '/data' (Device or resource busy)
cd "/data" && cd.. && mv "/data" "dataold" process ended with ERROR: 1
rm -rf "/data" process ended with Error: 1
Failed to unmount '/data" (Device or resource busy)

Updating partition details ...
Error opening: '/data/misc/recovery" (Operation not permitted)
Error opening '/data/misc/bluedroid" (Operation not permitted)

[and so far and so on for several lines, then ending with]
Error opening: '/data/ssh/empty' (Opeation not permitted)
...done

IS THERE ANYBODY WHO CAN GIVE ME SOME HELP TO GET MY PHONE WORKING AGAIN? I GUESS IF I CAN FORMAT /data I WILL BE ABLE TO RESTORE MY OLD ROM.

Thanks in advance!!!

READ THE THREAD. USE THE SOLUTION PRESENTED!

There are multiple links to the solution, it's 3.4A9 by geoanto555 which will work fine for you.

All that time to post that and you could have spent 10 seconds reading the thread and found the solution ON THE SAME PAGE as your post?

Actually, just restore the original, this whole thing with following simple instructions and reading is too hard for you so you should never, ever use any custom recovery or ROM until you have learned to do that.
 

Uluru25

Senior Member
Nov 27, 2016
68
8
18
Redmi Note 8
It doesn't recognise the encryption, how worthless would the encryption be if you could hack it like that? You need a proper recovery that can unencrypt data or you can't format it either.




READ THE THREAD. USE THE SOLUTION PRESENTED!

There are multiple links to the solution, it's 3.4A9 by geoanto555 which will work fine for you.

All that time to post that and you could have spent 10 seconds reading the thread and found the solution ON THE SAME PAGE as your post?

Actually, just restore the original, this whole thing with following simple instructions and reading is too hard for you so you should never, ever use any custom recovery or ROM until you have learned to do that.
First of all thanks for your fast reaction to my issue - really acknowledged. Indeed I saw the postings regarding a proper custom recovery but I thought this way of replacing the recovery is blocked for me since I "locked me out" for any flashings via PC. I later realized that I can flash another recovery from within TWRP and therefore indeed downloaded the latest Mauronofrio, the greek one and Orangefox BUT as correctly recognized by you since I am despite the charming "Senior Member" status not at all "senior" in tems of custom rom flashing etc. I didn't want to make things worse at a step where maybe other solutions from helpful dudes like breadpitt and eventually you could prevent me from nuking my phone. And finally, regarding your comment "so you should never, ever use any custom recovery or ROM until you have learned to do that": trying somethings beyond the current experience (including running into issues which hopefully can be solved with the help from more experienced guys) is the way I try to gain more and more experience and to "learn to do that". Beyond my personal impression that you sometimes prefer a rather blunt or rude tone in your posts, I appreciate your willingness to help others who have an issue like me. Therefore, thanks for your answer.
 

MichaelMay

Senior Member
Nov 15, 2020
124
51
28
First of all thanks for your fast reaction to my issue - really acknowledged. Indeed I saw the postings regarding a proper custom recovery but I thought this way of replacing the recovery is blocked for me since I "locked me out" for any flashings via PC. I later realized that I can flash another recovery from within TWRP and therefore indeed downloaded the latest Mauronofrio, the greek one and Orangefox BUT as correctly recognized by you since I am despite the charming "Senior Member" status not at all "senior" in tems of custom rom flashing etc. I didn't want to make things worse at a step where maybe other solutions from helpful dudes like breadpitt and eventually you could prevent me from nuking my phone. And finally, regarding your comment "so you should never, ever use any custom recovery or ROM until you have learned to do that": trying somethings beyond the current experience (including running into issues which hopefully can be solved with the help from more experienced guys) is the way I try to gain more and more experience and to "learn to do that". Beyond my personal impression that you sometimes prefer a rather blunt or rude tone in your posts, I appreciate your willingness to help others who have an issue like me. Therefore, thanks for your answer.

If I'm blunt and harsh it's because I'm trying to get things done, not because I dislike you as a person (I don't know you, how could I?).

I also have a problem with people messing with **** they clearly do not understand because you shouldn't.

Here's my deal, ask questions and I'll help you. Do **** you shouldn't and I'll get annoyed and tell you to STOP doing that.

I have a recovery, ROM and stuff and do you know why I don't publish it? Doesn't matter how good my instructions are, people will not follow them or not understand some part and then blame me. I'd have something to offer if it wasn't for that and that is why so few devs here interact with users, there is absolutely no use in doing so because you just keep going and then we have to guide you through how to undo what you did.

You are welcome though, I was feeling generous.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi have been using twrp and updated magisk to version 22.0 when I reboot phone goes back to the device is destroyed. Flashing twrp and vbmeta again give a feedback

    target didn't report max-download-size
    Failed (Command write failed (No error))

    Need some help!!
    Found a fix.
    Update windows adb composite drivers and fastboot drivers, If running windows 7 like me update all Android drivers from the web.
    Flash orange fox recovery.img file then flash vbmeta.img
    Boot to recovery with volume up button and power button. NB: do not use fastboot boot recovery command this returns to system is destroyed screen!!!
    In orange fox recovery flash twrp.img latest version. It will reboot to twrp automatically.
    In twrp flash any older version of magisk preferably any 21. version and safely wait for another update. The 22.0 version patches both boot and recovery files.
    Tried it 3 times before posting. Thanks guys.
    1
    Found a fix.
    Update windows adb composite drivers and fastboot drivers, If running windows 7 like me update all Android drivers from the web.
    Flash orange fox recovery.img file then flash vbmeta.img
    Boot to recovery with volume up button and power button. NB: do not use fastboot boot recovery command this returns to system is destroyed screen!!!
    In orange fox recovery flash twrp.img latest version. It will reboot to twrp automatically.
    In twrp flash any older version of magisk preferably any 21. version and safely wait for another update. The 22.0 version patches both boot and recovery files.
    Tried it 3 times before posting. Thanks guys.
    good tips
  • 66
    Team Win Recovery Project 3.x, or twrp3 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:
    #include <std_disclaimer.h>
    /*
    *
    * We are 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 us for messing up your device, we will laugh at you.
    *
    */

    Features:
    - Decryption works
    - Otg works
    - Backups works
    - Flash Rom works
    - F2FS support
    - Fastboot boot command support
    - Compatibility.zip error fixed
    - Willow fully supported
    - Android 11 Decryption


    Download:
    TWRP 3.4.0-10 Unofficial by mauronofrio
    TWRP 3.4.0-0 Unofficial by mauronofrio

    TWRP 3.3.1-10 Unofficial by mauronofrio / Sourceforge
    TWRP 3.3.1-9 Unofficial by mauronofrio / Mediafire
    TWRP 3.3.1-8 Unofficial by mauronofrio
    TWRP Official Builds
    TWRP 3.3.1-5 Unofficial by mauronofrio
    TWRP 3.3.1-2 Unofficial by mauronofrio

    To Flash the TWRP:
    if it's the first time you flash the TWRP or you are getting problems of TWRP lost or device doesn't boot after flashed magisk or something else you need to flash a script to patch your vbmeta:
    VBMETA PATCHER
    To flash the TWRP:
    Code:
    fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
    Then reboot in TWRP manually or using a fastboot command.
    Code:
    fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
    or
    Code:
    fastboot oem reboot-recovery
    Flash the VBMETA PATCHER and reboot.
    REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.

    Reccomended ADB and Fastboot binaries:

    Adb and Fastboot Installer

    Source code:
    https://github.com/omnirom/android_bootable_recovery
    https://github.com/mauronofrio/android_device_xiaomi_ginkgo
    Using precompiled stock kernel

    My Telegram TWRP Support Group:
    https://t.me/twrp_Mauronofrio

    Donations:



    Credits:
    Thanks to @ash4win for the first test

    Created 2019-11-04
    14
    TWRP 3.3.1-8 Redmi Note 8 ginkgo/willow by mauronofrio:
    Added the fully support for redmi note 8t willow. (Now all is working)

    TWRP 3.3.1-8 Unofficial by mauronofrio

    p.s. sorry for the previous update
    11
    11
    TWRP 3.4.0-2 for Xiaomi Redmi Note 8 (ginkgo-willow) by mauronofrio:
    Fixed a recognition problem with a new willow version.

    TWRP 3.4.0-2 Unofficial by mauronofrio

    P.s. soon i will update also the official TWRP
    7
    Redmi Note 8 + TWRP Official 3.3.1.0 + MIUI 11.0.3.0 stable EU + Magisk 20.1 everything works fine.

    No factory reset, My steps after unlocked.
    - fastboot flash recovery twrp.img then boot TWRP
    - swipe to NOT read only. (/system can be modified)
    - format data then swipe to wipe data, cache (basic wipe) because i don't know the format data process also wipe cache or not.
    - flash EU ROM reboot recovery.
    - flash Magisk reboot recovery.
    - reboot system.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone