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:
Code:
/*
*
* 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 work
- Otg work
-Vibrator
- Zip Flash
- Mtp/adb
- F2FS support
- Fastbootd
- Adb sideload
- Backup restore and images flash
Not working:
-Tell me
INSTALLATION:
1. Download the TWRP image file to your PC.
2. Put your device into fastboot.
3. Type the following command to flash the recovery:-
Code:
fastboot flash recovery "name_of_recovery.img"
4. On installation of TWRP , to boot the recovery do:-
Code:
fastboot boot "name_of_recovery.img"
The device will automatically reboot into TWRP.
5-A. You are using Xiaomi.eu Miui or custom Rom?
You can enjoy with a functional Data Decrypt
5-B You are using Miui EEA - Global -Cn or any custom rom that doesn't ship custom vbmeta.
6. Download this zip, copy by pc or using otg and flash this zip that will prevent twrp replacing.7. Download VbMeta and flash by fastboot
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
7. Reboot into twrp (Take longer Time)
Code:
fastboot boot "name_of_recovery.img"
8. Format Data and Reboot
NOTES:
By Command fastboot boot, recovery will decrypt everytimes you need, also with Global Rom and without patched vbmeta.
Download:
TWRP
VbMeta
(Version tag will follow vendor, a lower version tag than your vendor does not mean that recovery will not work)
Kernel Source: HERE
Donation:
PayPal: paypal.me/manuelbiancodev
Telegram Group: @MBsRoom
One user reported that MTP doesn't work after formatting data, and reboot back to recovery also doesn't make it work again.
Personally I haven't tried it, but the mentioned issue is kinda similar to the last build of mauro's twrp for the phone, so just want to let you know and hope someone else can confirm.
I didn't find how to decrypt data using schema.
huyhung411991 said:
One user reported that MTP doesn't work after formatting data, and reboot back to recovery also doesn't make it work again.
Personally I haven't tried it, but the mentioned issue is kinda similar to the last build of mauro's twrp for the phone, so just want to let you know and hope someone else can confirm.
Click to expand...
Click to collapse
doesn't work after formatting data
zeduck said:
I didn't find how to decrypt data using schema.
Click to expand...
Click to collapse
there are problem to decrypt with 12.2.4 such as umi have to fastboot boot the recovery to decrypt
Thank you.
thought id give it a try...formatting data does indeed make the sdcard inaccessible via mtp; seems the necessary directories isnt created after formatting. if you have a rom installed, you will need to boot back into the rom then reboot to twrp which will now be mtp accessible. tested only on crdroid.
edit: managed to get mtp to work after formatting. after format data reboot to system but on the poco bootscreen, hold down vol up and power key to re-enter twrp, mtp then seems to work
New instructions for eea and global user, post updated.
Decryption works for both PIN and Pattern on EU weekly beta.
PIN didn't work with TWRP3.4.2b but now it is OK with your TWRP. Thank you!
okay.. finally can use my pin again..
cant mount /vendor /product /ODM
With this recovery we don't need anymore to format internal storage every time we change rom?
Redmi K30 Pro Zoom Edition: longer boot into recovery, than LR.Team's TWRP, but PIN decryption works (on mine it worked with LR.Team's too, but I had to cancel password input).
cerealguy said:
With this recovery we don't need anymore to format internal storage every time we change rom?
Click to expand...
Click to collapse
This is rom dependant, if you flash stock global or eaa for example, Yes is needed
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
manuelbianco said:
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
Click to expand...
Click to collapse
Touchscreen not working on this version.
karnasw said:
Touchscreen not working on this version.
Click to expand...
Click to collapse
Maybe you clicked into download latest but so dowloaded umi version download this https://sourceforge.net/projects/mbroms/files/TWRPLMI/MBTWRP_08-03-2021.img/download
manuelbianco said:
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
Click to expand...
Click to collapse
All fine on my Poco F2 Pro. Touchscreen works.
manuelbianco said:
Maybe you clicked into download latest but so dowloaded umi version download this https://sourceforge.net/projects/mbroms/files/TWRPLMI/MBTWRP_08-03-2021.img/download
Click to expand...
Click to collapse
You're right. I downloaded latest not LMI. My bad, sorry.
Do I have to do something special to backup and restore? I want to try some roms but I hate having to config back everything after rollback to the previous ROM.
Related
Official TWRP For Moto G5 Cedric
Post 1 - Instructions
Post 2 - FAQs
For full details and notes see
Official TWRP for Cedric Site
For TWRP news change logs etc see
TWRP Official Site
Instructions
For non rooted and rooted phones
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Download Official TWRP Image
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button)
Connect phone to PC
Open a command prompt where you have fastboot and the TWRP image file located
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed)
To permanently flash twrp replacing stock recovery
Code:
fastboot flash recovery recovery.img
To only boot to twrp temporarily keeping stock recovery
Code:
fastboot boot recovery.img
Select recovery using the volume keys and power button to select
Now read important notes section For Stock Rom Users at the end of this post and the FAQs in the 2nd post
Note for Windows 10 users who use the powershell and not cmd
The command will become
Code:
./ fastboot flash recovery recovery.img
Or
Code:
./ fastboot boot recovery recovery.img
For rooted phones only
If you are already rooted you can upgrade your TWRP version using the official TWRP app
Download TWRP App
Select Cedric as your device
Download the TWRP image
Select the TWRP to flash
Now read the FAQs in the 2nd post
Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing Magisk zip which will disable it for you
Source Code
TWRP 32bit For Cedric Github Source
TWRP 64bit For Cedric Github Source
XDA:DevDB Information
[Official] TWRP 3.5.2_9-0 Moto G5 Cedric [32/64bit Roms], Tool/Utility for the Moto G5
Contributors
TheFixItMan, JarlPenguin
Source Code: https://github.com/TeamWin/android_device_motorola_cedric
Version Information
Status: Stable
Current Stable Version: TWRP 3.5.2_9-0
Stable Release Date: 2021-04-05
Created 2017-11-03
Last Updated 2021-04-05
FAQs
Q - Does the official twrp version support 64bit roms?
A - Yes - as of version 3.4.0-1
Q - I get error 255 when trying to flash a rom
A - You are using a 32bit twrp version. Please update to the latest 64bit version
Q - Can I use the 64bit version on 32bit roms?
A - Yes the 64bit version supports both 64bit & 32bit roms
Q - Does the official twrp version support treble rom?
A - Yes - as of version 3.4.0-1
Q - Does this recovery support decryption of data
A - Yes on all current 32/64bit roms - If you swap roms you will need to format data first to remove encryption before flashing the new rom then you can encrypt again
Q - My phone keeps booting to recovery on restart and can only be started normally through the bootloader
A - First try removing your SD card and see if your phone boots - If that doesn't work see This Post
Q - Where is the disable dm-verity zip?
A - You can download it Here
or old version can be found Here
Q - Where is the Magisk zip
A - See Magisk Thread
You may need to manually install the magisk manager app apk depending on which rom you are using
Q - It says "image not signed or corrupt" when I flashed image
A - This is normal as the image is not signed by Motorola
Q - When restoring backup I get an error starting Extracttarfork
A - Sometimes you need to format data before restoring backup - In fastboot mode enter the command
fastboot erase userdata
This will format all data on internal storage (pictures music documents downloads etc) so backup first!
Reserved
Thanks
Happy to hear that we got the official twrp support
I have a cedric device. I unlocked my bootloader. Then through fastboot i tried to install twrp-3.1.1-0-cedric.img.
But it says "image not signed or corrupt".
As on the other threads, they said that to directly go into recovery mode ignoring other things. But that did not work. It said "no command".
Please help with flashing twrp.
Edit- It worked after 5-6 attempts.
aashaydesh said:
I have a cedric device. I unlocked my bootloader. Then through fastboot i tried to install twrp-3.1.1-0-cedric.img.
But it says "image not signed or corrupt".
As on the other threads, they said that to directly go into recovery mode ignoring other things. But that did not work. It said "no command".
Please help with flashing twrp.
Click to expand...
Click to collapse
It will always say that because the image is not signed by Motorola
As long as it says write OK at the end
The easiest way is to type
fastboot flash recovery then drag the recovery image into the terminal window - this will automatically complete the rest of the command
I'll also write a note for Windows 10 users who use the power shell
You need to put ./ first
Just to let everyone know about encryption on oreo roms
If you have previously encrypted your phone you must remove encryption before flashing an oreo rom by doing format data from the wipe menu (different from wipe data) & booting the phone fully to check encryption has been removed
You can then flash the oreo rom
After flashing this rom you can encrypt the phone again if you want
Encryption is fully supported
My TWRP (official) can decrypt data of lineageos 15 rom (32bit) as Iv just tested it
bootloop to recovery and SD-ext
I went through all this procedure of unlocking and installing twrp yesterday. As I nearly experienced a heart attack, I would like to kindly ask you to expand your Q/A-section for the mental safety of my fellow G5 users.
If you follow each step, you still can run into the bootloop-to-recovery trouble. My system was formatted with an SD-card as extended internal memory, and I formatted everything exept SD-ext, which I might have done. Clearing the misc partition had no success until I removed the SD-card, and rebooted TWRP.
So basically my recommendation is: remove your SD-card before the procedure.
Happy flashing and thank you for your guide.
TheFixItMan said:
FAQs
Q - My phone keeps booting to recovery on restart and can only be started normally through the bootloader
A - See This Post
Click to expand...
Click to collapse
No-New-Phone said:
I went through all this procedure of unlocking and installing twrp yesterday. As I nearly experienced a heart attack, I would like to kindly ask you to expand your Q/A-section for the mental safety of my fellow G5 users.
If you follow each step, you still can run into the bootloop-to-recovery trouble. My system was formatted with an SD-card as extended internal memory, and I formatted everything exept SD-ext, which I might have done. Clearing the misc partition had no success until I removed the SD-card, and rebooted TWRP.
So basically my recommendation is: remove your SD-card before the procedure.
Happy flashing and thank you for your guide.
Click to expand...
Click to collapse
Added to Faq and guide
Hi, sorry if this is a silly question, but just thought I'd ask to be on the safe side... Is it safe to flash TWRP 3.2.0 that is now available for cedric through the TWRP app or would it be better to give it a miss for now?
RaddingtonBear said:
Hi, sorry if this is a silly question, but just thought I'd ask to be on the safe side... Is it safe to flash TWRP 3.2.0 that is now available for cedric through the TWRP app or would it be better to give it a miss for now?
Click to expand...
Click to collapse
Should be fine - changelog on twrp site
New twrp version available
What's new in 3.2.0-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
Boot
Twrp 3.2 problem not shutdown phone always restart system
Go twrp and shutdown always restart system.Use Android 8 Oreo Rom
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
TheFixItMan said:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Click to expand...
Click to collapse
Thanks a lot for maintaining cedric, you are king man
I unlocked the bootloader and flashed the twrp on my friends Moto g5 and after that if I restart it boots up to recovery only. I did all that's said in the xda forums and still the problem exists.i then wiped away all partitions and installed lineage 14.1. even now the problem exists. After lots of trying I found that going to bootloader and pressing start boots the phone normally. But it's tough to to it always he has to power on the phone. Can someone help me solve this problem
Sent from my Motorola Moto G 2014 using XDA Labs
ProGamer02224 said:
I unlocked the bootloader and flashed the twrp on my friends Moto g5 and after that if I restart it boots up to recovery only. I did all that's said in the xda forums and still the problem exists.i then wiped away all partitions and installed lineage 14.1. even now the problem exists. After lots of trying I found that going to bootloader and pressing start boots the phone normally. But it's tough to to it always he has to power on the phone. Can someone help me solve this problem
Sent from my Motorola Moto G 2014 using XDA Labs
Click to expand...
Click to collapse
Read the faq!
Nice
Thanks Men
Does it have support for 64 bit roms?
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.
*
*/
I’d recommend to read everything in this post, if you care about your phone.
If you already unlocked your bootloader, start with step 3.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Flash Galaxy A20e TWRP.tar via Odin or heimdall
Reboot into TWRP AS SOON AS THE FLASHING PROCESS IS DONE because otherwise TWRP will get replaced with the stock Android recovery
If you want to flash a GSI, skip to step 7
Factory reset in TWRP and reboot to stock
Wipe everything in TWRP excluding SD Card / USB OTG
Put a GSI image file onto an SD Card, alongside GSI_Fix_boot.zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Flash the GSI image, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, flash GSI_Fix_boot.zip, wipe cache and reboot.
Enjoy
Current bugs
Encryption/Decryption on stock does not work, you cannot read the internal storage while using the stock firmware
ADB and USB connection / USB OTG does not work
Latest release: https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view?usp=sharing
Social media
Twitter: https://twitter.com/xyn_dev
Telegram: https://t.me/xyn_dev
Reserved.
Wow finally... thx a lot for that
Xyn XDotnest said:
Reserved.
Click to expand...
Click to collapse
Great work
Can you now install GSIs
Make sure you backup boot, data, system before you start
physwizz said:
Great work
Can you now install GSIs
Make sure you backup boot, data, system before you start
Click to expand...
Click to collapse
Yep, GSIs work, I am currently using Descendant X on mine.
Xyn XDotnest said:
Yep, GSIs work, I am currently using Descendant X on mine.
Click to expand...
Click to collapse
Beautiful
I'm stuck at GSI (PixelExperience) installation. I've extracted the img file on sd card and the wizard is asking which partition should be used to flash image (boot,recovery,product image,system image,vendor image).
ZemoDroid said:
I'm stuck at GSI (PixelExperience) installation. I've extracted the img file on sd card and the wizard is asking which partition should be used to flash image (boot,recovery,product image,system image,vendor image).
Click to expand...
Click to collapse
System
A few Questions about the process
Xyn XDotnest said:
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.
*
*/
I’d recommend to read everything in this post, if you care about your phone.
If you already unlocked your bootloader, start with step 3.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Flash Galaxy A20e TWRP.tar via Odin or heimdall
Reboot into TWRP AS SOON AS THE FLASHING PROCESS IS DONE because otherwise TWRP will get replaced with the stock Android recovery
If you want to flash a GSI, skip to step 7
Factory reset in TWRP and reboot to stock
Wipe everything in TWRP excluding SD Card / USB OTG
Put a GSI image file onto an SD Card, alongside GSI_Fix_boot.zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Flash the GSI image, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, flash GSI_Fix_boot.zip, wipe cache and reboot.
Enjoy
Current bugs
Encryption/Decryption on stock does not work, you cannot read the internal storage while using the stock firmware
ADB and USB connection / USB OTG does not work
Latest release: https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view?usp=sharing
Social media
Twitter: https://twitter.com/xdotnest
Telegram: https://t.me/dotnest
Click to expand...
Click to collapse
,
Hey thanks for this, I´ve got a few questions about the process that might also help others.
Do you recommend this method of rooting still over the new method using Magisk?
Do we still need to wipe everything in TWRP after first boot? And what specifically steps should we take to wipe?
Can you recommend any specific GSI images that are known to boot on the A20e (A202F) because so far I've tried LineageOS 17.1 / AOSP system -quack-arm64-ab-gapps.img and system -quack-arm64-ab-vanilla.img / Crdroid and nothing gets past the loading icon.
Do we still need to flash Disable_Verity_ForceEncrypt and GSI_Fix_boot.zip if not installing a GSI ?
a few notes
for anyone else. It helps if you boot into the rom and install magisk manager via APK (recent version is fine) before installing it via TWRP. After I did that rooting worked properly.
Lost ADB for some reason though, might be unrelated.
I also think that the a20e (SM-a202f) is an A device and not an A/B partition device at least according to treble check app.
ADB and USB connection / USB OTG does not work
Click to expand...
Click to collapse
oh.....right. that stinks
moogle said:
,
Hey thanks for this, I´ve got a few questions about the process that might also help others.
Do you recommend this method of rooting still over the new method using Magisk?
Do we still need to wipe everything in TWRP after first boot? And what specifically steps should we take to wipe?
Can you recommend any specific GSI images that are known to boot on the A20e (A202F) because so far I've tried LineageOS 17.1 / AOSP system -quack-arm64-ab-gapps.img and system -quack-arm64-ab-vanilla.img / Crdroid and nothing gets past the loading icon.
Do we still need to flash Disable_Verity_ForceEncrypt and GSI_Fix_boot.zip if not installing a GSI ?
Click to expand...
Click to collapse
1. This method does use Magisk
The tar file contains boot.img patched with Magisk
It also contains recovery.img and vbmeta.img
2. The boot.img is from Android 10 firmware so you need to upgrade to Q first.
3 there is a step missing in the instructions
It should say
6. Reboot the A20e into TWRP and mount everything you can.
Click Wipe then Format Data (not just wipe) - don't restart
Flash Disable_Dm-Verity_ForceEncrypt
Reboot to recovery and wipe both caches
Reboot system .
Click to expand...
Click to collapse
You can then backup boot, data and system for stock.
You can then install GSIs
I'm having some major problems with sd cards not being recognized by google play store as external storage and whatsapp unable to download images. any idea what it might be?
moogle said:
I'm having some major problems with sd cards not being recognized by google play store as external storage and whatsapp unable to download images. any idea what it might be?
Click to expand...
Click to collapse
What OS are you running?
physwizz said:
What OS are you running?
Click to expand...
Click to collapse
Just the stock android 10, I didn't find a GSI that worked for me.
moogle said:
Just the stock android 10, I didn't find a GSI that worked for me.
Click to expand...
Click to collapse
try Crdroid
physwizz said:
try Crdroid
Click to expand...
Click to collapse
Already have, and LOS 17.1 and AOSP system-quack-arm64-ab-vanilla
all of them got stuck at boot icon for an hour. Thats why I went back to stock.
I'm more interested in why I cannot seem to install discord or firefox from the app store, or whatsapp cannot download images.
moogle said:
Already have, and LOS 17.1 and AOSP system-quack-arm64-ab-vanilla
all of them got stuck at boot icon for an hour. Thats why I went back to stock.
I'm more interested in why I cannot seem to install discord or firefox from the app store, or whatsapp cannot download images.
Click to expand...
Click to collapse
Go into magisk and hide any apps that misbehave
physwizz said:
Go into magisk and hide any apps that misbehave
Click to expand...
Click to collapse
Tried it, no change, there's no apps misbehaving, just strange sd storage card behaviour
Is the SM-A202F/DS supported by these methods, I noticed in some other threads it wasn't working back in March, that's the unit I have.
moogle said:
Tried it, no change, there's no apps misbehaving, just strange sd storage card behaviour
Is the SM-A202F/DS supported by these methods, I noticed in some other threads it wasn't working back in March, that's the unit I have.
Click to expand...
Click to collapse
There is a fix here
https://forum.xda-developers.com/showpost.php?p=80184282&postcount=2
physwizz said:
There is a fix here
https://forum.xda-developers.com/showpost.php?p=80184282&postcount=2
Click to expand...
Click to collapse
Which part are you referring to in that thread?
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 TWRP, for Mi 11 lite 5G
bugs:
backup/restore is unreliable
adb sideload and fastbootd
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Contributors:
@VladV1V , @TheMalachite
Tree:
GitHub - TeamWin/android_device_xiaomi_renoir
Contribute to TeamWin/android_device_xiaomi_renoir development by creating an account on GitHub.
github.com
Kernel:
https://github.com/VladV1V/kernel_xiaomi_renoir
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimi11lite5g.html
Sorry, but the installation did not work for me... :-( What i have done:
- i renamend the downloaded file to "twrp.img"
- i copied this file to the internal storage
- i startet the phone in fastboot mode
- then i startet adb
- i used the command "fastboot boot twrp.img"
Then i saw the following:
downloading 'boot.img'...
OKAY [ 2.826s]
booting...
OKAY [ 0.201s]
finished. total time: 3.027s
But the phone only switched off and nothing happend. What's wrong?
EDIT: i solved the problem! I forgot to put the file "twrp.img" into the adb folder. After doing this, the installation worked! Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Hi, thank's for your work for our device...
I read somewhere, that if we have TWRP installed, that we cannot flash update with fastboot...I want to know if it's true and if yes, how can we flash update..we have to find recovery update, or we can extract from fastboot archive and flash it??
thanks for your answer
Rainman67 said:
Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Click to expand...
Click to collapse
certainly not available yet...you have to backup in internal storage and then copy to SD...
Another question: how to go back to stock recovery?
Rainman67 said:
Another question: how to go back to stock recovery?
Click to expand...
Click to collapse
I'm on Xiaomi EU ROM. After last update via fastboot Miui Recovery 5.0 comes back.
Great hopefully this leads to development of some easy to flash roms, cant wait to get rid of this buggy MIUI trash.
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
same with #8 boot into twrp and no touchscreen
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
Boot TWRP from fastboot and touch will work.
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
How did you flash it?
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Peterpaulmarie said:
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Click to expand...
Click to collapse
pm me on telegram if you can get logs and have adb access
dannejanne said:
Boot TWRP from fastboot and touch will work.
Click to expand...
Click to collapse
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
i just boot to try if it can boot in twrp lol, no need to flash it so far,if needed it i will use the method u guys said(real flash in)
Well then both of you make sure you're actually using the build from afh and only use it for fastboot boot, when you want to flash use flash current twrp don't flash it with fastboot
Touch works when using fastboot boot and when flashed, it Was already tested on multiple devices
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
doclucas said:
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
Click to expand...
Click to collapse
Touch already works normally without fastboot
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Yes, I can confirm. After start recovery wait 10-15sec touchscreen will work
With the test builds from telegram twrp was not able to recognize my SD card. Is this now fixed?
Is it possible to flash Xiaomi.eu weekly rom only by starting twrp from fastboot without installing it?
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 TWRP, for Mi 11i/Mi 11X Pro/Redmi K40 Pro
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_haydn
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomiredmik40pro.html
Thanks for sharing
Good job,but semms the Touchscreen doesn't work.
don't touch fish said:
Good job,but semms the Touchscreen doesn't work.
Click to expand...
Click to collapse
It does, wait a few seconds after boot
Nebrassy said:
It does, wait a few seconds after boot
Click to expand...
Click to collapse
I waited about five minute,and nothing happend.When I touch the screen,nothing happend or Sometimes twrp responds to the wrong touch position(for example:I touch the Cancel,It opend Language sittings).I can only use adb shell to use this recovery.
thanks，will it support flash miui rom.zip and support android 12 。。
Thank you ………………Testing now
Touch doesnt work for me either
im on xiaomi eu rom
Exodt said:
Touch doesnt work for me either
im on xiaomi eu rom
Click to expand...
Click to collapse
Pull log and send it
adb pull /tmp/recovery.log
Before flashing i removed my fingerprint and device lock Flashed successfully after 2nd step i installed twrp image via twrp recovery installed in phone in Advance - recovery ram disk -Twrp image - flash and after that i created a boot image and dtbo backup also flashed magisk zip btw my device was rooted previously with boot image method, in xiaomi eu 12.5.7.0. Touch takes time then it works … First internal storage was not showing so i go to mount and mount system and then it shows.
Maxx9 said:
Before flashing i removed my fingerprint and device lock Flashed successfully after 2nd step i installed twrp image via twrp recovery installed in phone in Advance - recovery ram disk -Twrp image - flash and after that i created a boot image and dtbo backup also flashed magisk zip btw my device was rooted previously with boot image method, in xiaomi eu 12.5.7.0. Touch takes time then it works … First internal storage was not showing so i go to mount and mount system and then it shows.
Click to expand...
Click to collapse
Can you check if fastboot booting the image has working touch?
Nebrassy said:
Can you check if fastboot booting the image has working touch?
Click to expand...
Click to collapse
Thats how i installed
Installation:
Removed Screen lock And Fingerprint
1.fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3.Go to advance system ram disk select twrp image and flash(if internal storage not showing then go to mount and mount storage)
4.after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Yes…it works for me …… when i run first command it booted but my storage wasn’t showing so i reboot to recovery and device reboted to stock recovery then i again put my device in fastboot and performed first command and it booted to twrp and touch takes 20 seconds for me to work ..
Nebrassy said:
Pull log and send it
adb pull /tmp/recovery.log
Click to expand...
Click to collapse
"adb: error: failed to stat remote object '/tmp/recovery.log': No such file or directory"
Tried it in booted twrp as well but adb doesn't work there.
Maxx9 said:
Thats how i installed
Installation:
Removed Screen lock And Fingerprint
1.fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3.Go to advance system ram disk select twrp image and flash(if internal storage not showing then go to mount and mount storage)
4.after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Yes…it works for me …… when i run first command it booted but my storage wasn’t showing so i reboot to recovery and device reboted to stock recovery then i again put my device in fastboot and performed first command and it booted to twrp and touch takes 20 seconds for me to work ..
Click to expand...
Click to collapse
It worked.
Flash Current TWRP did the trick.
I had to do a reboot.
Hold the volume up and power to go back to TWRP.
After that I could see the internal storage.
And flash Magisk.
*Do not unplug the cable. Unplugging was causing the touch to stop work on my MI11i EU 12.5.7
Thanks Maxx9!
I didn't unplugged the USB and removed the fingerprint + key as well.
But still didn't worked.
on xiaomi eu 12.5.8
Touche said:
It worked.
Flash Current TWRP did the trick.
I had to do a reboot.
Hold the volume up and power to go back to TWRP.
After that I could see the internal storage.
And flash Magisk.
*Do not unplug the cable. Unplugging was causing the touch to stop work on my MI11i EU 12.5.7
Thanks Maxx9!
Click to expand...
Click to collapse
Your welcome
Doesn't work on Indian ROM 12.5.5.0
Official Pixel Experience A12 Custom Rom For Xiaomi Redmi K40 Pro / Pro+ / Mi 11X Pro / Mi 11i is Available On Pixel Experience Official Website.
on my device twrp still freeze touch screen
same problem
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.
#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/Recovery
* 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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
The best thing ever happened for realme ui 2. Great work mate..!
Finally, a proper working Recovery for our device
Wow...Finally Working TWRP for RMX1931 on RUI2.
Thanks alot bro.
Can I flash this, when I'm on Lineage-18.1?
zheka99 said:
Can I flash this, when I'm on Lineage-18.1
Click to expand...
Click to collapse
Technically its possible...but you should do it after roms released based on rui2 firmware. If not , you will endup with broken OS. For now dont flash custom roms with this recovery.
can i flash magysk to optine root, wich version?
Isavar said:
can i flash magysk to optine root, wich version?
Click to expand...
Click to collapse
Magisk-92546e8a(23016) from CANARY all Ok!
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Leozgz85 said:
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Click to expand...
Click to collapse
Hi
was the same for me, had to reinstall everything, only started in TWRP. Would like to install the recovery but I don't feel like this error anymore.
Thanks. It's working.
Doesnt work for me, i cant boot to realme ui after flashing the vbmeta, i got stuck on recovery. (f.14)
This recovery is broken for me, it gives me no space left on sdcard even after a full data reformat, ozip extraction stops after 500mb.
It's just not working as it should 3.4 works best
arnodorian-r said:
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.
#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/Recovery
* 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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
Click to expand...
Click to collapse
I followed this guide and many others in the past 48 hours, with no success. Every time I flash TWRP and the VBMETA, I get stuck in TWRP bootloop.
I started unblocking the bootloader, rolling back to RUI1 - Android 9 and using the Deep-Test App.
After the roll back, I got the phone unblocked right, but then first soft-brick, with only bootloader available and no way to flash a working ROM. After some searches, I've finally managed to unbrick, using OPPO flash tool, and installing stock rom RMX1931_11_F.14_2021102817443142.
This gives me a working phone, RUI.2 - Android 11. Standard recovery.
I tried to flash TWRP and got the phone soft bricked again, in TWRP recovery bootloop.
I'd like to install TWRP and from there going to OrangeFox and finally install Lineage 19.1...
How can i first have a working TWRP recovery??? If you can support also following steps, would be amazing. Thank you!!!
I went few step further... but still I am not able to install a working custom recovery for my realme X2 pro.
I have now also rooted my device with magisk.
I just need a custom recovery to perform 2 actions:
- make a NANDroid backup;
- install a custom ROM.
Any advice? Thank you for your time!
Installed. Working like a charm with lineage 19.1. Only problem: can't access files in storage. Digging into the matter, it seems to be an issue with android 12's new encryption method, which can't be overriden by this version of the recovery. There's a brand new TWRP 3.7.0_9.0 in the official TWRP website which boasts to overcome this problem but, whenever I try to install it (with or without the vbmeta.img provided for version 3.6.0_11), the recovery won't start. Guess a new vbmeta.img is needed as everything goes ok reinstalling TWRP 3.6.0_11 and its corresponding vbmeta. Tried to extract and install vbmeta.img from the lineage zip file without success. Shall we have to patch vbmeta.img? How can we do that? Through Magisk? I've come across some "vbmeta patcher" apk... Am I pointing the right way?
can any one help me to unlock bootloader in realme x2 pro . i am on RUI 10 . i installed in depth tool it said seccesful but no bootloader just keep rebooting and showing fast boot for a moment .. help please i search every where for fix but no way to yet
I'm using the CN variant device, which I understand does not yet have confirmed support, nonetheless sharing the error I'm encountering in case it's a simple or obvious fix I'm missing.
Having followed all above steps, I'm able to flash and get into TWRP recovery, but decryption always failed (even after a dozen tries) with the following:
"Attempting to decrypt FBE for user 0...
Failed to decrypt user 0"
Much obliged for any insight on this. I'm attempting to get back on OF after successfully installing Lineage 19.1, which broke the OF recovery, and since OF needs to be installed as a ZIP, I need to get some version of TWRP working as an intermediary. Specifically this is because I didn't install GAPPS along with Lineage 19.1 (I misread the opening post, which seemed to imply that GAPPS was included in that particular ROM). So alternatively, if there's another way to get GAPPS onto the device without recovery (sideload won't work since I can't decrypt...) then that would be helpful too.
Thanks in advance for any insight on this!