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:
- sdcard
- Decryption works
- Otg works
- F2FS support
- Fastboot boot command support
- Fastbootd
Not working:
- backups
- other?, you tell me
DANGER:
- NO SLOT CHANGER (BRICK DEVICE)
Download:
UPDATE 01-03-2023
This project it abandoned , I don't have the phone to continue the development
last android supported it A11 not flash on 12+ and
(stableR.25) (LAST) (finally for end support support a11-)
(stableR.21)(old)
To Flash the TWRP:
INSTALL RECOVERY (PERM INSTALL)
Code:
fastboot flash recovery twrp.img
BOOT RECOVERY (TEMP BOOT)
Code:
fastboot boot recovery twrp.img
Reccomended ADB and Fastboot binaries (FOR MOTOROLA DEVICES):
TinyFastbootScript
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/Moto-tree-folders
COFFE:
Paypal
BETAR (R) = BETA
=============================================
=============== CHANGELOG ================
=============================================
UPDATE 01-03-2023
This project it abandoned , I don't have the phone to continue the development
stable r.25
update TWRP source to 3.5.1-r10.0 (source for dynamic)
stable r.21
- fix touch for ft8756 display
- improve partitions
fix backups and rework dt
- reduce 67mb to 35mb recovery
stable r1 (final betar )
- fix Decryption
betar 18 ()
- fix sdcard
- Decryption don't works (break for now)
betar 17 (private)
- private build
betar 16
- update source code to TWRP 3.5.0_10 (build with - - -OMNI/AOSP 10)
betar 15
: build fastbootD (install work c
touch work in nova display
===============================================
============= TOUCH NO WORK?? ===============
===============================================
report you display
USE:
adb shell
ls /sys/class/touchscreen
and send me you display name in telegram
I thought it was a personalized recovery alternative! I'm still expecting. :confuso: :confuso:
ramasterdev said:
I thought it was a personalized recovery alternative! I'm still expecting. :confuso: :confuso:
Click to expand...
Click to collapse
yep , twrp is custom recovery
Thank you Sebastian for your efforts.
I tried this TWRP by "fastboot boot recovery.img" without flashing it.
Because I'm rooted I checked my sys/class/touchscreen to see if I had a novatek screen.
NVT-ts
Novatek_ts
Thanks for confirming that this was the correct screen Sebastian!
sebastian3567HD said:
Reserved
changenlog:
beta 15
: build fastbootD (install work c
touch work in nova display
no work touch report you display
adb shell
ls /sys/class/touchscreen
and send me you display name
telegram https://t.me/seba_3567
Click to expand...
Click to collapse
My display is ft8756
Thanks
ReneZeiss said:
View attachment 5153427
Click to expand...
Click to collapse
work
Kikowtf said:
My display is ft8756
Thanks
Click to expand...
Click to collapse
I'm still working to put that screen to work!
ReneZeiss said:
Thank you Sebastian for your efforts.
I tried this TWRP by "fastboot boot recovery.img" without flashing it.
Because I'm rooted I checked my sys/class/touchscreen to see if I had a novatek screen.
NVT-ts
Novatek_ts
Thanks for confirming that this was the correct screen Sebastian!
Click to expand...
Click to collapse
test in NVT-ts (work) (use fastboot boot recovery.img for test you display )
Hi Sebastian,
I also have a new Moto G9 Plus and the touchscreen is ft8756. I've tried various TWRP images with the same result; unable to enter anything on the touchscreen.
I understand from the posts that you are still working on this touchscreen.
I have searched Google and the forums and cannot find a feasible answer. I am unable to create a full backup on internal or external storage due to the error seen in the screenshot (it gets stuck in the same position with the same error on both storages). Can someone point me in the right direction or assist me in rectifying the issue? Thanks in advance.
Have new g9 plus and after recovery flash end up in bootloop TWRP can't control because touch screen not working.... 200€ bye bye.....
Waiting for new Odessa file
hampik said:
Have new g9 plus and after recovery flash end up in bootloop TWRP can't control because touch screen not working.... 200€ bye bye.....
Waiting for new Odessa file
Click to expand...
Click to collapse
turn the phone off, boot into fastboot, and flash the stock image (you'll have to search for how to flash stock image on this phone), and see if that will fix the issue
Not-working touch screen I'm bypass this issue
by using PC mouse put USB receiver in phone trough USB-c to USB from Samsung box
now I'm root with new type of display
+1 touchscreen ft8756, is it possible to use it with other twrp?
Miha1l said:
+1 touchscreen ft8756, is it possible to use it with other twrp?
Click to expand...
Click to collapse
Here's a link to a tested working copy of TWRP for Odessa: https://www.androidfilehost.com/?fid=17248734326145738599
A working copy of TWRP 3.5.0 that works with ft8756 touchscreen. I have personally tested it - https://www.androidfilehost.com/?fid=17248734326145738599
hampik said:
Have new g9 plus and after recovery flash end up in bootloop TWRP can't control because touch screen not working.... 200€ bye bye.....
Waiting for new Odessa file
Click to expand...
Click to collapse
can you explain that better?
hampik said:
Not-working touch screen I'm bypass this issue
by using PC mouse put USB receiver in phone trough USB-c to USB from Samsung box
now I'm root with new type of display
Click to expand...
Click to collapse
can you give me information about your problem?
Related
Code:
#include
/*
* Your warranty is now 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod/CWM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This is CWM for Wiko Stairway. As there are no custom roms (yet), this might not be very useful as of now
Do not install on any other device than the Wiko Stairway - I have not tested it on other clones (e.g. the Canvas4 210).
Note:
- The recovery has been compiled from Cyanogenmod 10.1
- minimal device tree that builds recovery https://github.com/chrmhoffmann/android_device_wiko_stairway
- the battery driver problem seems to have been resolved with newer kernel source from wiko, so please upgrade to 0.3
Before proceeding please make a complete backup for ALL partitions (especially the recovery with e.g. MTK Droid Root & Tools).
Thxs go to:
- bgcngm/mtk-tools
- the guys who make MTK droid root & tools
- wiko for updating the source
What works
- you can adb into the CWM
- backup and restore (boot, data, cache, system)
- install from .zip files
Installation
a) Get fastboot executable (apt-get install android-tools-fastboot)
b) and then bring device in fastboot mode (power up then press Vol Down + Vol Up -> Follow the instructions to fastboot)
c) on command line "fastboot flash recovery cwm-recovery-wiko-stairway.img"
d) on command line "fastboot reboot"
e) bring device to recovery (power up then press Vol Down + Vol Up -> follow the instructions to recovery)
Changelog 0.3
- kernel now compiled from new Wiko source STAIRWAY_Opensource_new46752.zip which seems to fix the battery thermo issue
- stripped down kernel (without sound, etc.) to fit into recovery partition size. no other changes to kernel source
Download
http://goo.im/devs/chrmhoffmann/wiko/cwm-recovery-wiko-stairway-0.3.img
md5sum 8e571b2815177232623f71e9383eb593
---------------
Older versions:
Changelog 0.2
- backup and restore also the boot.img
- make it possible to install ext4 images from CM e.g.
Download
http://goo.im/devs/chrmhoffmann/wiko/cwm-recovery-wiko-stairway-0.2.img
md5sum 34532ab6f463f10edf033ef026cd0efd
Changelog
- tried nandroid backup/restore: seems to do the trick
- new self-compiled kernel! YAY!
- stripped down version of kernel (disabled wifi, sound, debug, etc). CWM is complete though.
Download
http://goo.im/devs/chrmhoffmann/wiko/cwm-recovery-wiko-stairway-0.1.img
md5sum d84ac35f07ef44e2f2614edd28b0cb15
---------------
Even older versions:
md5sum: a5fa40a7fab9f0e20c2a967ce87a7723
link: http://goo.im/devs/chrmhoffmann/wiko/cwm-recovery-wiko-stairway.img
Reserved
As usual
0.1
New version with self-compiled kernel. Please read disclaimer.
[SVP, lisez le OP.]
device tree
Hi,
The device tree is here: https://github.com/chrmhoffmann/android_device_wiko_stairway
(the perl header builder is taken from bgcngm. thx!)
It should now build from scratch. The kernel is still a binary blob (self compiled though) as the MTK kernel build system is .... errr... different.
Chris
I confirm that another way is to install the CWM recovery with Mobileuncle MTK tools https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox :good:
Hi,
How is it to remove the custom recovery to return to after-sales service ?
Comment supprimer le recovery custom que vous proposez afin d'envoyer le smartphone à Wiko ?
Thx
... reflasher la ROM stock de base ... si tu l'as trouves
... flash again the basic stock ROM ... if you find it
Michel38280 said:
... reflasher la ROM stock de base ... si tu l'as trouves
... flash again the basic stock ROM ... if you find it
Click to expand...
Click to collapse
Il n'y a pas un recovery.img ?
Can somebody provide a mirror please?
[edit] sorry wrong post . thanks [/edit]
0.3
Hi,
new version available. New kernel source from wiko seems to fix the battery thermo driver issue. Amazing that they released new source. Thx, WIKO!
800 downloads and only two thanks in the OP!
Chris
Perfect !
Thanks !
chrmhoffmann said:
Hi,
new version available. New kernel source from wiko seems to fix the battery thermo driver issue. Amazing that they released new source. Thx, WIKO!
800 downloads and only two thanks in the OP!
Chris
Click to expand...
Click to collapse
Hi chrmhoffman,
Great job (and I already hit may thx buttons), but it seems that in my Wiko Stairway it doesn't mount the SD card.
Everytime I select "mount external_sd" it just says "Error mounting /external_sd".
I can only access internal SD.
Can you advise me on that?
thx
I think it should mount the sdcard with the other menu options for mounting. I don't think I can remove that option.
Chris
Sent from my FP1 using xda app-developers app
Thx for the fast response.
chrmhoffmann said:
I don't think I can remove that option.
Click to expand...
Click to collapse
I'm not asking to remove the option. I actually can't access the external SD.
Usually I have to copy whatever I want to flash to internal SD (and this already got me in some troubles when I format the system and forget to copy the rom).
So when you say
chrmhoffmann said:
I think it should mount the sdcard with the other menu options for mounting.
Click to expand...
Click to collapse
Which one are you speaking about because I tried them all. What am I doing wrong?
Thx, again
Sorry I got confused.... Mounting external sd card works for me. Did you try version 0.3?
I tested with 0.3 and I was able to go to "mounts and storage"-> "mount /external_sd"
Is the card partitioned? What filesystem is the card formatted with? fat should work.
Can u provide file /tmp/recovery.log from the recovery when that happens?
Chris
PS: adb pull /tmp/recovery.log
It's not so simple to intall, like latest ROM...
chrmhoffmann said:
Hi,
new version available. New kernel source from wiko seems to fix the battery thermo driver issue. Amazing that they released new source. Thx, WIKO!
800 downloads and only two thanks in the OP!
Chris
Click to expand...
Click to collapse
@ chrmhoffmann can you please please compile any touch based recovery for wiko stairway/Canvas4 as we badly need it to flash various ROMs
Thanks in advance:thumbup:
Sent from my Wiko Stairway using xda app-developers app
chrmhoffmann said:
Code:
#include
/*
* Your warranty is now 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod/CWM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This is CWM for Wiko Stairway. As there are no custom roms (yet), this might not be very useful as of now
Do not install on any other device than the Wiko Stairway - I have not tested it on other clones (e.g. the Canvas4 210).
Note:
- The recovery has been compiled from Cyanogenmod 10.1
- minimal device tree that builds recovery https://github.com/chrmhoffmann/android_device_wiko_stairway
- the battery driver problem seems to have been resolved with newer kernel source from wiko, so please upgrade to 0.3
Before proceeding please make a complete backup for ALL partitions (especially the recovery with e.g. MTK Droid Root & Tools).
Thxs go to:
- bgcngm/mtk-tools
- the guys who make MTK droid root & tools
- wiko for updating the source
What works
- you can adb into the CWM
- backup and restore (boot, data, cache, system)
- install from .zip files
Installation
a) Get fastboot executable (apt-get install android-tools-fastboot)
b) and then bring device in fastboot mode (power up then press Vol Down + Vol Up -> Follow the instructions to fastboot)
c) on command line "fastboot flash recovery cwm-recovery-wiko-stairway.img"
d) on command line "fastboot reboot"
e) bring device to recovery (power up then press Vol Down + Vol Up -> follow the instructions to recovery)
where to put fastboot flash recoverry command ? pc cmd ?
kind of noob here so please explain the procedure.
thanks
Click to expand...
Click to collapse
please a video for how to do?
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>
/*
* Your warranty is not void.
*
* 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:
All function in a normal TWRP
Multi-language support
USB OTG
Decrypt /data
F2FS
Tips:
kernel is based on CAF Oreo-MR1 tag: LA.UM.6.5.r1-05300-8x96.0
All QSEE blobs(decrypt related) are pulled from OxygenOS Open Beta 30
I just tested compatibility with encrypted Oreo OxygenOS and LineageOS, no guarantee it works with any pre-Oreo encrypted /data
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot flash recovery imgfilename.img" in command line
5. Reboot and enjoy it
Download:
https://twrp.me/oneplus/oneplusthree.html
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/TeamWin/android_device_oneplus_oneplus3
https://github.com/dianlujitao/android_kernel_oneplus_msm8996/tree/staging/lineage-15.1
XDA:DevDB Information
TWRP, Tool/Utility for the OnePlus 3
Contributors
dianlujitao
Version Information
Status: Snapshot
Created 2018-01-31
Last Updated 2018-02-01
@dianlujitao Download link leading to github not to download page
vny10 said:
@dianlujitao Download link leading to github not to download page
Click to expand...
Click to collapse
No mate the link automatically downloads the file.
ps_minky16 said:
No mate the link automatically downloads the file.
Click to expand...
Click to collapse
Fixed now
@dianlujitao
what happens to this thread now > [Recovery] Official TWRP for the OnePlus 3 & 3T
@jcadduono retired as its Maintainer?
and TWRP OnePlus 3 page reflects build twrp-3.2.1-0-oneplus3.img with build date as: 2017-12-09 23:34:16 EST
kamilmirza said:
@dianlujitao
what happens to this thread now > [Recovery] Official TWRP for the OnePlus 3 & 3T
@jcadduono retired as its Maintainer?
and TWRP OnePlus 3 page reflects build twrp-3.2.1-0-oneplus3.img with build date as: 2017-12-09 23:34:16 EST
Click to expand...
Click to collapse
As you can see, the (old) manteiner abandoned the thread.
For the download, as you can read: "http://build.twrp.me/twrp-3.2.1-0-oneplus3.img(will be available on TWRP site soon)"
It means that for now you have to download the new TWRP build from that link.
And it will be avaible on official TWRP website later.
I'm on Nougat currently, if I flash this via and old bluespark TWRP will I end up in bootloop?
Korax94 said:
I'm on Nougat currently, if I flash this via and old bluespark TWRP will I end up in bootloop?
Click to expand...
Click to collapse
if you flash it within TWRP - then no, you will not end up in bootloop
i can flash this twrp on last blu spark right? i am currently on omni.
your answer is literally one post above
Is there a workaround for the slow TWRP loading issue.
I always had this with every version when it takes more than a minute for the TWRP to load.
Op3t
dinindourden said:
Is there a workaround for the slow TWRP loading issue.
I always had this with every version when it takes more than a minute for the TWRP to load.
Op3t
Click to expand...
Click to collapse
you must be on F2FS
going EXT4 reduces startup significantly
Sent from my OnePlus 3T using XDA Labs
kamilmirza said:
you must be on F2FS
going EXT4 reduces startup significantly
Click to expand...
Click to collapse
Thanks for the tip, I will back up and try.
dinindourden said:
Is there a workaround for the slow TWRP loading issue.
I always had this with every version when it takes more than a minute for the TWRP to load.
Op3t
Click to expand...
Click to collapse
That's weird, I'm on stock file format too (eversince) and never ever experienced a "one minute TWRP splash screen", it's more like 10 seconds, no matter what TWRP version or how full storage is...
Sent from my OnePlus 3T using XDA Labs
dinindourden said:
Is there a workaround for the slow TWRP loading issue.
I always had this with every version when it takes more than a minute for the TWRP to load.
Op3t
Click to expand...
Click to collapse
Only time I had very slow twrp load, was when I was using a certain theme, was very gfx intensive. Stock twrp or basic themes load fast.
TWRP website has been updated with the unification between OP3 and 3T.
https://twrp.me/oneplus/oneplusthree.html
dinindourden said:
Is there a workaround for the slow TWRP loading issue.
I always had this with every version when it takes more than a minute for the TWRP to load.
Op3t
Click to expand...
Click to collapse
Welcome to ext4. As time goes on, it'll take a longer time to mount f2fs partition.
kamilmirza said:
@dianlujitao
what happens to this thread now > [Recovery] Official TWRP for the OnePlus 3 & 3T
@jcadduono retired as its Maintainer?
and TWRP OnePlus 3 page reflects build twrp-3.2.1-0-oneplus3.img with build date as: 2017-12-09 23:34:16 EST
Click to expand...
Click to collapse
jcadduono hasn't been active since Nougat. In fact official Nougat TWRP is based on my tree, but I'm not actually "maintaining" it. Now some people cannot mount /data in TWRP after installing Oreo, time to fix it and keep it up-to-date.
Hi there, I'm currently on OOS Beta 22 on my 3T. I wanted to root my device with magisk. But I have come across so many posts describing about decryption problem, such as 3T stock bootimage has dm-verity which prevents from booting if I swipe to enable system modifications. To get rid of this I have to flash 'dm-verity forced encryption disabler script'. But I read in the OP that all the blobs related to these problem has been fixed by the dev! If so do I have to flash this zip in BTW the rooting procedure.
just installed the latest and now it won't accept my password. i tried changing it and disabling it from the security settings but it does not work. the previous twrp i used never ascked for passes. log attached.
This TWRP Recovery Is Compiled From Source & Officially Supported
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.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Official TWRP Page: https://twrp.me/oukitel/oukitelk10.html
GitHub Release : Here (release name : TWRP-OUKITEL-K10)
Version Information
ROM OS Version: 8.1 Oreo
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel
Reserved For Future Updates
I need a device owner to check for these information below. Reach me if you have the device and willing to help this to be official.
For verifying BOARD_FLASH_BLOCK_SIZE
For verifying PIXEL_FORMAT
Instructions To Check
PIXEL_FORMAT : Install AIDA64 App. Under Display section, try to find GL_EXT_texture_format_ line and note down the last portion of that line GL_EXT_texture_format_BGRA8888. That should be in BGRA8888 or BRGA8888 format. Send me that info with screenshot.
Can't find download link.
There is official twrp 3.2 out there for oukitel k10 already as I believe.
We need a rom developers for our phones.
a602820922 said:
Can't find download link.
There is official twrp 3.2 out there for oukitel k10 already as I believe.
We need a rom developers for our phones.
Click to expand...
Click to collapse
You think i am joking ?
I wrote the gerrit patche for adding oukitel mix2 to official TWRP, in the same patch bigbiff added OUKITEL for the first time.
Can't find download link ? Jesus... see attachment.
Download the recovery.img and test. If have the device i will ask you to read post #2.
omg that are really good news thx for your hard work on my phone ♥
i need backup my phone after it i can unlock my bootloader and try this can i use it with android 7 or need i update my android first to 8.1 ?
today i flash android 8.1 on my phone and your recovery
target reported max download size of 134217728 bytes
sending 'recovery' (20540 KB)...
OKAY [ 6.268s]
writing 'recovery'...
OKAY [ 0.292s]
finished. total time: 6.562s
it´s working more or less
i have one problem my internal storage in twrp is 0 mb if i wipe it it´s ok i can see the real mb if i restart phone and go into android and them back to twpr the storage it´s again 0 mb
can you fix that problem pls :*
ADB is working, OTG is mounted one-time, MTP does not work but i´m happy with my android 8 update
thx chankruze you are an awesome developer <3
ps cant post screenshot cause i have not 10 post ... i send it privat
Xian K10 said:
i have one problem my internal storage in twrp is 0 mb if i wipe it it´s ok i can see the real mb if i restart phone and go into android and them back to twpr the storage it´s again 0 mb
Click to expand...
Click to collapse
That's due to the encryption,
Every time you boot your mobile phone on it starts encrypting our device automatically.
You have to disable this function.
If you want disable it than thare is no possibility to have an access to the storage.
Sent from my K10 using Tapatalk
verifying PIXEL_FORMAT
It is BGRA8888
Recovery does not work, stuck in boot loop.
After flashing this recovery, the /data partition is broken.
Even with an older TWRP version, e.g. 3.2.1.0, no recovery of the /data partition is possible.
This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. 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.
Disclaimer
Code:
/*
* Your warranty might not be void (thanks Xiaomi). However...
*
* 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 RECOVERY
* 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.
*/
Requirements
Xiaomi Mi 9 SE (of course)
Unlocked bootloader
Some knowledge on how to deal with your device... and patience.
Flashing InstructionsI assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
Optional: Flash stock vbmeta with the following command (attached if needed):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x-y-KudProject-grus.img
Where x and y are version of TWRP you're going to flash.
IMPORTANT: After flashing, immediately press and hold Power + Volume Up for about 10 seconds to reboot to recovery.
Swipe the option to allow modifications. This will prevent stock ROM from replacing recovery, however be aware that you might need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!
Downloads
Webserver | MEGA
Old releases only: OSDN | AndroidFileHost
Known Issues
/dev/null
Special Thanks
Dees_Troy and everyone behind TWRP
Everyone on Mi 9 SE community
Device Sources
TWRP repository fork
Device tree
Kernel source
Changelogstwrp-3.5.2_9-1-KudProject-grus
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Updated kernel to MoeSyndrome kernel based on Android 10
Mount firmware partition as read-only
Added support for formatting Cust partition in GUI
twrp-3.4.0-0-KudProject-grus
Merged TWRP source changes up to 22 June 2020 (UTC+8)
Supports decryption of userdata on Android 10-based MIUI and custom ROMs using Android 10 crypto blobs (might not be backwards compatible)
Restored system and vendor (non-image) backup support
Added support for backing up persist (and the image)
Build some blobs from source
Updated remaining blobs from V11.0.2.0.QFBEUXM
Updated prebuilt kernel to latest Pie
twrp-3.3.1-3-grus-20190802
Switched to source-built kernel
Updated blobs from MIUI China developer 9.7.4
Added support for F2FS in kernel (tell me if decryption breaks on this file system though)
Added persist into fstab
Added vendor-side touch firmware
Get CPU temperature from proper thermal zone
Disabled vbmeta checks
Only allow image backups for system and vendor
Symlinked /system to /system_root/system for backward compatibility
Misc stuffs
TWRP and f2fs-tools upstream changes
twrp-3.3.1-2-grus-20190609
Fixed wrong USB-OTG mount point
twrp-3.3.1-1-grus-20190603
Updated prebuilt kernel and DTBO from MIUI China developer 9.5.30
Corrected vendor image flashing
Support for wiping /vendor
Support for flashing and backup up (as part of boot) DTBO
Defined TW_SCREEN_BLANK_ON_BOOT
(Properly) excluded TWRP app
Included private recovery configuration
twrp-3.3.1-0-grus-20190531
Initial build.
Notes
Don't use fastboot boot to boot the recovery; it'll proceed to boot system instead using recovery's kernel. If this happens with your current kernel's boot image security patch being older than recovery one, you're basically busted as FBE keys are upgraded the time newer combination of system + vendor + boot image security patches are detected.
If you're out of luck in this situation, the only way to resolve is to format data (just backup your data to somewhere safe before doing so).
If you flash disabled vbmeta, you can't flash stock MIUI zips until the original vbmeta is restored.
Wrapped key support is added into recovery just for anticipation, although not defined by default in fstab.
I can't test it since EEA device so far is on March ASB as of V10.2.5.0 stable.
Otherwise, basic functionalities including decryption should work.
Edit: grus doesn't have anti rollback enabled at this moment, but Xiaomi may enable it in the future...
it is save changed from wzsx150 twrp ? or must on fastboot ?
bonbibonkers said:
it is save changed from wzsx150 twrp ? or must on fastboot ?
Click to expand...
Click to collapse
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
ok, gonna test it out , many thanks great work ??
Thanks! working so far so good
krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
Working fine when flashing from wzsx150 twrp version.
krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol
rzki03 said:
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol
Click to expand...
Click to collapse
Just ignore it. That same CPU temperature glitch also happens on sirius.
Wow, finally an *actual* twrp
Sent from my Mi 9 SE using Tapatalk
krasCGQ said:
Just ignore it. That same CPU temperature glitch also happens on sirius.
Click to expand...
Click to collapse
okay then. thank you!
@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks
denzel09 said:
@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks
Click to expand...
Click to collapse
So this release doesn't have Backup/Restore working?
luisbelmont said:
So this release doesn't have Backup/Restore working?
Click to expand...
Click to collapse
Yes, it has. My request was a bit different.
denzel09 said:
Yes, it has. My request was a bit different.
Click to expand...
Click to collapse
Oh, perfect! Thank you. What advantages does your request have?
luisbelmont said:
Oh, perfect! Thank you. What advantages does your request have?
Click to expand...
Click to collapse
To backup and recover dtbo image before and after flashed this custom kernel: https://forum.xda-developers.com/mi...nel-okitakernel-v1-0-mi-9-se-27-2019-t3934029
Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).
puppetminds said:
Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).
Click to expand...
Click to collapse
Kinda off-topic, but well rebasing over CAF is a tough job...
Sent from my Mi 9 SE using XDA Labs
This TWRP recovery Is compiled from source & will be supported officially soon
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 project
* 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.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. Not tested yet
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery image and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then use your device key combo to boot into TWRP recovery mode.
Enjoy !
Downloads
Android File Host: https://www.androidfilehost.com/?w=files&flid=296748
Official TWRP Page: Yet to submit
Contributors
chankruze
Source Code: https://github.com/N00bTree/android_device_ulefone_Armor_6
Version Information
Status: stable
Thank you! I can confirm this also works on the Armor 6E.
i have been able to flash it but its pretty useless as i cant decrypt it and no other options show up
mentalik said:
i have been able to flash it but its pretty useless as i cant decrypt it and no other options show up
Click to expand...
Click to collapse
I had same problem, I flashed https://androidfilehost.com/?fid=6006931924117895653 and formatted internal data.
thanks that solved it for me
jonezy82 said:
I had same problem, I flashed https androidfilehost.com ?fid=6006931924117895653 and formatted internal data.
Click to expand...
Click to collapse
How do i even flash that? twrp is refusing to let me do anything.
Yoosk said:
How do i even flash that? twrp is refusing to let me do anything.
Click to expand...
Click to collapse
EDIT: Have you tried to select "cancel" when you get into twrp?
You can get past of decryption by selecting "cancel".
You need to format your internal storage, then flash that .zip from usb-otg usbstick.
FYI: I got my phone screwed once, I just flashed stock firmware with sp_flash_tool and it formatted storage for me.