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
This is not tested, before test it make a backup and please report what is working and what is not working
Thanks ! I hope come quickly other improvements.
Flashed it and it booted successfully.
bhaiwala said:
Flashed it and it booted successfully.
Click to expand...
Click to collapse
Decryption is working?
Decrypted by entering locksreen pin
bhaiwala said:
Decrypted by entering locksreen pin
Click to expand...
Click to collapse
So seems all is working...
Gsis working?
good job！goodjob ！
and how to use f2fs for redmi note8
I have tested the recovery in my device. And it's working good. Thanks .
ridershahmir said:
Gsis working?
Click to expand...
Click to collapse
They should work
wsdyleon said:
good job！goodjob ！
and how to use f2fs for redmi note8
Click to expand...
Click to collapse
f2fs is already in use on note 8 for userdata
working super fine
nice work
cRaZyzMaN said:
working super fine
nice work
Click to expand...
Click to collapse
On factory Global rom?
Will it works on China rom flashed into Global?
Zozomon said:
On factory Global rom?
Will it works on China rom flashed into Global?
Click to expand...
Click to collapse
Try it.
Zozomon said:
On factory Global rom?
Will it works on China rom flashed into Global?
Click to expand...
Click to collapse
that i dont know
I install this twrp, and working perfectly thanks again
please say the type of ROM (China or global) where it was installed, thanks
miguelm18 said:
please say the type of ROM (China or global) where it was installed, thanks
Click to expand...
Click to collapse
global version
installed it on my phone with stable rom, sadly it not stays permanently. after reboot stock recovery appeared
SKAssi said:
installed it on my phone with stable rom, sadly it not stays permanently. after reboot stock recovery appeared
Click to expand...
Click to collapse
Flash magisk to keep it
Related
Update 180914:
Always believe something wonderful is just going to happen.
WARNING:I‘m not responsible for any consequences at all.This is an OEM rom ported from Redmi phone so it may cause wrong behaviors including partition overwritting and may brick your phone or break hardwares.I strongly recommend you take a completely full backup of your device and know how to recovery firmwares in case of any problems.
This is still in early stage and should be normal if some features are broken.
Working on Qualcomm fully-Trebled deivces.
Maybe working on other platfrom fully-Trebled deivces.
8.1 vendor (vndk27) should be needed.
Bugs:
Light HAL(Brightness acting strange, this is a MIUI traditional)
SELinux
Credits:
@erfanoabdi
Install for A-only:
1.enable Treble ,flash a fully-trebled 8.1 rom
2.Extract the .7z to your TWRP backup folder (/.../TWRP/BACKUPS/$(yourserialnumber)/
3.Restore MIUI10 /system with TWRP
4.flash two patch zip
5.wipe data,flash fbe_disabler and Permissiver (from tools) if needed for your device.
6.Reboot.
Normally it will boot to bootanimation.If it doessn't pass bootanim then take logs with
adb logcat > logcat.txt via PC.
NOTE:
IF YOU STUCK AT MI ACCOUNT LOGIN, make sure you flashed permissiver
If the device says your device has mi account locked, then pull simcard out and reboot to complete the setup.
If you're stuck at logo , please make sure you can boot sGSI
Telegram Group:
https://t.me/funtouchosp
For Chinese users you can contact me via Coolapk.See my signature.
v1:
Initial release
Download
GDrive https://drive.google.com/open?id=1hyyErzDrl-cre13AX4_A5aSAbRHurZvU
This for Aonly or A/B?
how about huawei device？
山海蓝精灵 said:
how about huawei device？
Click to expand...
Click to collapse
Idk, maybe need 8.1 vendor huawei device
fxsheep said:
WARNING:I‘m not responsible for any consequences at all.This is an OEM rom ported from Redmi phone so it may cause wrong behaviors including partition overwritting and may brick your phone or break hardwares.I strongly recommend you take a completely full backup of your device and know how to recovery firmwares in case of any problems.
This is still in early stage and should be normal if some features are broken.
Working on Qualcomm fully-Trebled deivces.
Maybe working on other platfrom fully-Trebled deivces.
8.1 vendor (vndk27) should be needed.
Bugs:
Light HAL(Brightness acting strange, this is a MIUI traditional)
SELinux
Credits:
@erfanoabdi
Install for A-only:
1.enable Treble ,flash a fully-trebled 8.1 rom
2.Extract the .7z to your TWRP backup folder (/.../TWRP/BACKUPS/$(yourserialnumber)/
3.Restore MIUI10 /system with TWRP
4.flash two patch zip
5.wipe data,flash fbe_disabler and Permissiver (from tools) if needed for your device.
6.Reboot.
Normally it will boot to bootanimation.If it doessn't pass bootanim then take logs with
adb logcat > logcat.txt via PC.
NOTE: If you're stuck at logo , please make sure you can boot sGSI
Telegram Group:
https://t.me/funtouchosp
v1:
Initial release
arm builds WIP
Download
GDrive https://drive.google.com/open?id=1hyyErzDrl-cre13AX4_A5aSAbRHurZvU
Click to expand...
Click to collapse
is volte working?
fxsheep said:
WARNING:I‘m not responsible for any consequences at all.This is an OEM rom ported from Redmi phone so it may cause wrong behaviors including partition overwritting and may brick your phone or break hardwares.I strongly recommend you take a completely full backup of your device and know how to recovery firmwares in case of any problems.
This is still in early stage and should be normal if some features are broken.
Working on Qualcomm fully-Trebled deivces.
Maybe working on other platfrom fully-Trebled deivces.
8.1 vendor (vndk27) should be needed.
Bugs:
Light HAL(Brightness acting strange, this is a MIUI traditional)
SELinux
Credits:
@erfanoabdi
Install for A-only:
1.enable Treble ,flash a fully-trebled 8.1 rom
2.Extract the .7z to your TWRP backup folder (/.../TWRP/BACKUPS/$(yourserialnumber)/
3.Restore MIUI10 /system with TWRP
4.flash two patch zip
5.wipe data,flash fbe_disabler and Permissiver (from tools) if needed for your device.
6.Reboot.
Normally it will boot to bootanimation.If it doessn't pass bootanim then take logs with
adb logcat > logcat.txt via PC.
NOTE: If you're stuck at logo , please make sure you can boot sGSI
Telegram Group:
https://t.me/funtouchosp
v1:
Initial release
arm builds WIP
Download
GDrive https://drive.google.com/open?id=1hyyErzDrl-cre13AX4_A5aSAbRHurZvU
Click to expand...
Click to collapse
AB support please!!!
wmfanboy25 said:
AB support please!!!
Click to expand...
Click to collapse
I don't have A/B devices ,so I don't get familiar with how A/B devices work,also this MIUI port is from an Aonly device, converting Aonly to A/B image is more difficult than vice versa
Global or Chinese?
Bootloop on Xiaomi Redmi Note 4 SD ( Mido ).
[email protected] said:
Bootloop on Xiaomi Redmi Note 4 SD ( Mido ).
Click to expand...
Click to collapse
take log or try clean flashing
Im flashing now to op5t and will report back soon.
Status:
1. Booted
2. Stucked in Sign in to your Mi Account, even if i disabled use cloud sync. I see is Couldn't check device security info.
Does this sgsi has arb feature?
Stuck at mi account log in. Couldn check device status
fxsheep said:
...
Click to expand...
Click to collapse
I want try at MiPad 4. It is arm64, aonly.
What do u think?
Can this be flashed on redmi note 3 pro (kenzo)?
other dead Rom
fountoutch Dead
Oos Dead
miui 10 Dead
I tried flashing this on the huawei p20 lite and I can't flash the patch 2. Gives error 1
ebautista said:
Im flashing now to op5t and will report back soon.
Status:
1. Booted
2. Stucked in Sign in to your Mi Account, even if i disabled use cloud sync. I see is Couldn't check device security info.
Click to expand...
Click to collapse
yogasetyaadi said:
Stuck at mi account log in. Couldn check device status
Click to expand...
Click to collapse
Reboot and retry, so many people booted
dcduartee said:
I tried flashing this on the huawei p20 lite and I can't flash the patch 2. Gives error 1
Click to expand...
Click to collapse
Mount vendor in twrp
dcduartee said:
I tried flashing this on the huawei p20 lite and I can't flash the patch 2. Gives error 1
Click to expand...
Click to collapse
Vendor mounted?
TWRP for Huawei P10 Lite
Working
Code:
[CENTER]* Touchscreen
* Adb
* Backup
* Wipe
* File manager
* MTP
[/CENTER]
Not Working
Code:
[CENTER]You tell me
[/CENTER]
Installation
Code:
[CENTER]* put you phone in fastboot mode and type
"fastboot flash recovery_ramdisk <grab_here_the_img>"
* reboot
[/CENTER]
Download
Code:
[CENTER][URL="https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P10%20Lite/Pie/TWRP/"]TWRP[/URL]
[/CENTER]
Credits:
@Pretoriano80
@haky 86
@OldDroid
@DarkDroidDev
Please support my work, it's very important! Thanks
DONATIONS
Regards !
Reserved
sorry for this request here, but please say me, will your stuff like this recovery and roms for p10 lite work on p8 lite 2017 because when im not wrong ive read some stuff work on different huawei phones with same chipsets etc, is it true?Big thanx, keep up your great work, have a nice day. Greeetz!!!
Great .. after testing on WAS-LX1A
i dunno why you're telling that mtp/backups doesn't work !
For me Backups work and internal storage / SD shown on windows normally
*Edit
Can't copy files
Thanks for your precious work .
-CALIBAN666- said:
sorry for this request here, but please say me, will your stuff like this recovery and roms for p10 lite work on p8 lite 2017 because when im not wrong ive read some stuff work on different huawei phones with same chipsets etc, is it true?Big thanx, keep up your great work, have a nice day. Greeetz!!!
Click to expand...
Click to collapse
I've installed RR and Bootleggers ROM's on P8 Lite 2017 and it works. All ROM's and Recoveries for hi6250 based devices (Kirin 655, 658, 659) will work on each other.
Hi, when trying to install your Android AOSP 9 pie ROM with this TWRP recovery... I get message
E3004: This package is for "hi6250" devices; this is a "warsaw"
please help?
GizmoTheGreen said:
Hi, when trying to install your Android AOSP 9 pie ROM with this TWRP recovery... I get message
E3004: This package is for "hi6250" devices; this is a "warsaw"
please help?
Click to expand...
Click to collapse
It could work if you edit the updater-script. In your rom zip open the updater-script file with text editor (Rom.zip/META-INF/com/google/android) and delete the first lines which are for the device verification including the ones giving the error output. This leads to no device check while flashing. :fingers-crossed: . For me it was really helpful in some cases.
NeoPreacher said:
It could work if you edit the updater-script. In your rom zip open the updater-script file with text editor (Rom.zip/META-INF/com/google/android) and delete the first lines which are for the device verification including the ones giving the error output. This leads to no device check while flashing. :fingers-crossed: . For me it was really helpful in some cases.
Click to expand...
Click to collapse
You would think when the same guy dev both Recovery and ROMS they would have that fixed? ^^;;
GizmoTheGreen said:
You would think when the same guy dev both Recovery and ROMS they would have that fixed? ^^;;
Click to expand...
Click to collapse
yeah, this is going to happen soon !
@DarkJoker360
How could I know if my device is hi6250 or warsaw?
chiduja said:
@DarkJoker360
How could I know if my device is hi6250 or warsaw?
Click to expand...
Click to collapse
hi6250 is the device chipset marking which matches multiple devices, warsaw is especially this device as in my case WAS-LX1A (WAS is warsaw). every warsaw is a hi6250 but not every hi6250 is a warsaw.
NeoPreacher said:
hi6250 is the device chipset marking which matches multiple devices, warsaw is especially this device as in my case WAS-LX1A (WAS is warsaw). every warsaw is a hi6250 but not every hi6250 is a warsaw.
Click to expand...
Click to collapse
Thank you, I asked it because I not capable of flash custom ROMs on my P10 Lite WAS-LX3 the problem is: after the clean installation of AOSP 9.0 mi phone get stuck in: your device is booting now... And then go to eRecovery not to TWRP and don't boot on system. I don't know what I have to do.
chiduja said:
Thank you, I asked it because I not capable of flash custom ROMs on my P10 Lite WAS-LX3 the problem is: after the clean installation of AOSP 9.0 mi phone get stuck in: your device is booting now... And then go to eRecovery not to TWRP and don't boot on system. I don't know what I have to do.
Click to expand...
Click to collapse
i had and still have the same results when trying to flash aosp. did you also decrypt your device before flashing any rom? could also be helpful in some cases.
NeoPreacher said:
i had and still have the same results when trying to flash aosp. did you also decrypt your device before flashing any rom? could also be helpful in some cases.
Click to expand...
Click to collapse
The first time that I tried to do the flashing I had to put my patron, but I've never did the decrypt, It's ****ty I tried a lot of "Solutions" but It doesn't worked.
ok alright the problembis that i tried to use "warsaw" codename instead of "hi6250" but it is not working for some reason, it is a flashing issue, and probably i have to revert my changes...
EDIT: before reverting my changes I wanted to try with LineageOS 16.0
Hi
Is there a prerequisite to use this recovery, I'm still using twrp 3.1.1-2 made by KingofMezi so still emui 5.0 but that recovery doesn't allow data backup because of the encryption. So I tried to flash yours it was ok in the command window but when I try to boot in recovery I get an error. I tried flashing again, downloading again and flashing but still doesn't work any idea?
I didn't want to upgrade the rom without a proper backup but none of the recoveries have been working.
Hi! Does someone try to install on a p20 lite?
@DarkJoker360 thanks for your work! Looks amazing.
I've never flashed TWRP before so I am bit nervous of bricking my phone!
I finally managed to unlock my bootloader by downgrading to EMUI 5.1.1, Android 7.0 (...). Will your TWRP work from this version? Is there any benefit/drawback of updating my phone to EMUI 8.0.0/Android 8.0.0 before flashing your TWRP?
P10Lite:
Model: WAS-LX1A
Build: WAS-LX1AC432B209
EMIU: 5.1.1
Android: 7.0
diy_solomun said:
@DarkJoker360 thanks for your work! Looks amazing.
I've never flashed TWRP before so I am bit nervous of bricking my phone!
I finally managed to unlock my bootloader by downgrading to EMUI 5.1.1, Android 7.0 (...). Will your TWRP work from this version? Is there any benefit/drawback of updating my phone to EMUI 8.0.0/Android 8.0.0 before flashing your TWRP?
P10Lite:
Model: WAS-LX1A
Build: WAS-LX1AC432B209
EMIU: 5.1.1
Android: 7.0
Click to expand...
Click to collapse
I asked myself the same question and tried to flash twrp on android 7.0 but it didn't work. I tried to upgrade to android 8 via erecovery but it failed. So i managed to upgrade it to B366 Emui 8 with dload (https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946) but i still could not flash twrp. So i entered erecovery mode again (press power, volume up & down for a few seconds) and with android 8 i could recover it to the official 8.0.0.376. After this step the flashing of twrp was finally successful. Thanks to darkjoker!!
New TWRP update is up !
Changelog
Code:
[CENTER]* Synced with latest TWRP source code
* FIxed flashing errors[/CENTER]
DONATIONS
Check OP for more info and download !
Team Win Recovery Project 3.x 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.
*
*/
By @pjgowtham and @mauronofrio
Note that two kinds of builds are available. The only difference between these builds is that one does adjust for the notch space and adds black border on top and the other TWRP shows as full screen.
Features:
- Temporarily disabled compatibility.zip check to allow flashing stock ROMs
- Ozip decryption
- Device data decryption
- Reboot to EDL
- Full android 9/10 support
and everything a TWRP usually does.
Release 02/02/20
- Updated kernel to android 10
- Updated blobs to android 10
Release 03/02/20
- Device data decryption support added
Release 04/02/20 (stable build)
-Disabled compatibility zip check to allow flashing stock ozip.
Release 08/02/20
- Added TWRP theme for notched devices (thanks to @mauronofrio)
Release 12/02/20[/B][/U]
- Added dtbo.img to the recovery so that it can support both Android pie and 10 firmware
Release 29/02/20
- Added the ability to backup, restore and flash persist partition
- Added the ability to backup, restore internal storage
Bugs :
None
XDA:DevDB Information
TWRP, Tool/Utility for the Realme XT
Contributors
pjgowtham, mauronofrio, thesprintster
Device Tree
https://github.com/pjgowtham/device_realme_RMX1921
https://github.com/mauronofrio/device_realme_RMX1921
Download Link
Stable build : 12/02/20
https://androidfilehost.com/?w=files&flid=304993
@mauronofrio s TWRP builds are included too.
FAQ :
Refer wiki here :,
https://forum.xda-developers.com/realme-xt/how-to/guide-unlocking-unbricking-custom-t4045505
Version Information
Status: Stable
Created 2020-02-02
Last Updated 2020-03-29
Thanks for your afford
can i flash magisk with this twrp and root andriod 10?
Data Decryption doesn't work.
If you can add it, it would be perfect.
ashruz.ash said:
Data Decryption doesn't work.
If you can add it, it would be perfect.
Click to expand...
Click to collapse
Should be fixed in the next build
sonu0070 said:
Thanks for your afford
can i flash magisk with this twrp and root andriod 10?
Click to expand...
Click to collapse
Yes, just remember to flash vbmeta immediately after you flash the magisk otherwise it will show recovery destroyed error
pjgowtham said:
Yes, just remember to flash vbmeta immediately after you flash the magisk otherwise it will show recovery destroyed error
Click to expand...
Click to collapse
Thanks for reply can you send me link of vbmeta
I am confused which one should I flash.
sonu0070 said:
Thanks for reply can you send me link of vbmeta
I am confused which one should I flash.
Click to expand...
Click to collapse
You would be okay with los vbmeta or any vbmeta for that sake. Just use the flags before flashing. I added FAQs in the original post just now.
EDIT:
Seems like there's issues with vbmeta. Use the vbmeta that's pinned on the wiki
pjgowtham said:
You would be okay with los vbmeta or any vbmeta for that sake. Just use the flags before flashing. I added FAQs in the original post just now.
EDIT:
Seems like there's issues with vbmeta. Use the vbmeta that's pinned on the wiki
Click to expand...
Click to collapse
Hi,
How did you unlock Realme XT with Android 10(realme UI) ...the Deeptesting app isnt working for unlock bootloader
Is there Process for Android 10 unlock before we flash TWRP and vmbeta img from other blog ?
Regards,
Diaz M
diazneoones82 said:
Hi,
How did you unlock Realme XT with Android 10(realme UI) ...the Deeptesting app isnt working for unlock bootloader
Is there Process for Android 10 unlock before we flash TWRP and vmbeta img from other blog ?
Regards,
Diaz M
Click to expand...
Click to collapse
Please refer the wiki. You should unlock on pie itself. That way you have unlocked bootloader on 10.
Why there is no 10 based custom roms for xt? Can't devs can port custom roms of realme x to xt atleast? The fingerprint issues are already solved, right?
ashruz.ash said:
Why there is no 10 based custom roms for xt? Can't devs can port custom roms of realme x to xt atleast? The fingerprint issues are already solved, right?
Click to expand...
Click to collapse
A week back we didn't have a wiki page, a backup of the stock recovery, a stable twrp. It's only been a week now since these work were done. On top of it, realme is not very proactive with the kernel sources. But its only a matter of time since we bring up lineage 17.1 or pixel experience. We are working on it.
Good to hear.
Backup taken via TWRP failed fr system image..this happens for both stock rom and custom rms too..has anyone taken successful backup
I get following error when flashed stock rom of Color OS ior RUI in TWRP
failed to mount /dev/block/bootdevice/by-name/userdata at /data
diazneoones82 said:
Backup taken via TWRP failed fr system image..this happens for both stock rom and custom rms too..has anyone taken successful backup
Click to expand...
Click to collapse
Try the latest build maybe
Do you have the indian variant of the device or something else?
Can i flash it on rui c.03
Samrra said:
Can i flash it on rui c.03
Click to expand...
Click to collapse
No u need to unlock your boorloader 1st kindly reas it. It doesnt work in realme ui
My twrp realme xt back to stock recovery...how to solve it?
Samrra said:
Can i flash it on rui c.03
Click to expand...
Click to collapse
Yes you can flash even on the yet to be released C.04
krizhiel said:
No u need to unlock your boorloader 1st kindly reas it. It doesnt work in realme ui
Click to expand...
Click to collapse
It works on realme UI
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:
- Android Q Support
- Decryption Support
- Vendor Partition Support
- Unified TWRP, so this works on OnePlus 5 and also on OnePlus 5T
- Android 11 Decryption
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 modified vbmeta:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP:
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Download:
TWRP 3.4.0-10 by mauronofrio
TWRP 3.4.0-0 by mauronofrio
TWRP 3.3.1-1 by mauronofrio
TWRP 3.3.1-0 by mauronofrio
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/mauronofrio/android_bootable_recovery
https://github.com/mauronofrio/android_device_oneplus_cheeseburger
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
Thanks to @eng.stk for the base source
Created 2020-03-27
mauronofrio 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>
[COLOR="red"][SIZE="6"]Download:[/SIZE
[B]Created[/B] 2020-03-27[/QUOTE]
could not flash it fro ADB,command returned cannot load twrp-3.3.1-0-mauronofrio.img.
should i type fastboot flash recovery twrp-3.3.1-0-mauronofrio-cheeseburger-dumpling.img to make it work?
i didn t try it and flashed it from TWRP / Install image,done.
is it OK this way or will i have any problems?
thanks for your job:good:
Click to expand...
Click to collapse
What's the difference between this recovery and Codeworkx or BlueSpark?
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
broky said:
could not flash it fro ADB,command returned cannot load twrp-3.3.1-0-mauronofrio.img.
should i type fastboot flash recovery twrp-3.3.1-0-mauronofrio-cheeseburger-dumpling.img to make it work?
i didn t try it and flashed it from TWRP / Install image,done.
is it OK this way or will i have any problems?
thanks for your job:good:
Click to expand...
Click to collapse
You have to write the twrp name
TWRP 3.3.1-1 for OnePlus 5/5T (cheeseburger-dumpling) by mauronofrio:
Fixed compatibility.zip problems.
TWRP 3.3.1-1 by mauronofrio
Thanks for this! Added mirrors as well as themed versions here.
until now,I have tried it with msm Xtended 10 & pixel experience 10 In op5 & works very well without problems...
Thanks!
What's the difference between this blu_spark?
black screen + blue LED
Hi,
I was in 3.2.1-x | blu_spark v8.73 (working) but could not install OnePlus5Oxygen_23_OTA_064_all_2004231206_e6e62df77f104cc0.zip Beta2 (Android 10) : error zip treble compatibility.
As you can see, I followed your method but I am not able to go in TWRP : black screen blue LED.
It is the same with : twrp-3.3.1-x_blu_spark_v9.110_treble-op5_op5t.img => black screen blue LED.
If I flash an old one I have : twrp-3.2.1-x_blu_spark_v8.61-op5_op5t.img : TWRP is OK.
What is the good way to go to Android 9 and to Android 10 beta2 from my xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full.zip and twrp-3.2.1-x_blu_spark_v8.61-op5_op5t.img ?
Please help.
c:\_\adbfastboot>fastboot flash recovery twrp-3.3.1-1-cheeseburger-dumpling-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (33296 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.030s]
finished. total time: 0.774s
c:\_\adbfastboot>fastboot boot twrp-3.3.1-1-cheeseburger-dumpling-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.716s]
booting...
OKAY [ 10.103s]
finished. total time: 10.827s
I solved my issue, it could help someone else...
One way from Android 8.1.0, to go to Android 9 and to Android 10 beta2 from my xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full.zip and twrp-3.2.1-x_blu_spark_v8.61-op5_op5t.img.
1- Go full OnePlus 5 stock : I used TOOL_ALL_IN_ONE_2.0.1.2 and the mauronofrio's fastboot ROM for OnePlus5 (OnePlus5Oxygen_23_OTA_029_all_1801292040_f50c278a6e154736-FASTBOOT.zip)
2- Using OTA update up to the last possible : 9.0.11
3- Download OB2 for OnePlus 5 from OnePlus website (OnePlus5Oxygen_23_OTA_064_all_2004231206_e6e62df77f104cc0.zip) and copy it to the root of internal memory. Apply it by local update.
4- Flash recovery (tested successfully with twrp-3.3.1-x_blu_spark_v9.110_treble-op5_op5t.img)
I will test the flash of twrp-3.3.1-1-cheeseburger-dumpling-mauronofrio.img
Thanks a lot to mauronofrio for all his devs.
accnetdev said:
Hi,
I was in 3.2.1-x | blu_spark v8.73 (working) but could not install OnePlus5Oxygen_23_OTA_064_all_2004231206_e6e62df77f104cc0.zip Beta2 (Android 10) : error zip treble compatibility.
As you can see, I followed your method but I am not able to go in TWRP : black screen blue LED.
It is the same with : twrp-3.3.1-x_blu_spark_v9.110_treble-op5_op5t.img => black screen blue LED.
If I flash an old one I have : twrp-3.2.1-x_blu_spark_v8.61-op5_op5t.img : TWRP is OK.
What is the good way to go to Android 9 and to Android 10 beta2 from my xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full.zip and twrp-3.2.1-x_blu_spark_v8.61-op5_op5t.img ?
Please help.
c:\_\adbfastboot>fastboot flash recovery twrp-3.3.1-1-cheeseburger-dumpling-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (33296 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.030s]
finished. total time: 0.774s
c:\_\adbfastboot>fastboot boot twrp-3.3.1-1-cheeseburger-dumpling-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.716s]
booting...
OKAY [ 10.103s]
finished. total time: 10.827s
Click to expand...
Click to collapse
Just tried this on my 5t, MSM-X v9. Made backup and restore, no problems. Anyone tried it on OOS beta 3?
Sent from my OnePlus 5T using XDA Labs
tcat007 said:
Just tried this on my 5t, MSM-X v9. Made backup and restore, no problems. Anyone tried it on OOS beta 3
oos 10 beta3 dont restore with twrp
Sent from my OnePlus 5T using XDA
Click to expand...
Click to collapse
Anyone tried this recovery on stable oos 10. Does backup restore works?
navinmholkar said:
Anyone tried this recovery on stable oos 10. Does backup restore works?
Click to expand...
Click to collapse
I just tried restoring OOS 10 stable, seemed to restore, but just bootlooped. I'm back on Derpfest.
mauronofrio said:
TWRP 3.3.1-1 for OnePlus 5/5T (cheeseburger-dumpling) by mauronofrio:
Fixed compatibility.zip problems.
TWRP 3.3.1-1 by mauronofrio
Click to expand...
Click to collapse
Many thanks for this release and for the job !
Two questions:
- Is your TWRP also compatible with P or only Q?
- Can a successful Nandroid backup/restore be performed with Q?
Eric_Lev said:
Many thanks for this release and for the job !
Two questions:
- Is your TWRP also compatible with P or only Q?
- Can a successful Nandroid backup/restore be performed with Q?
Click to expand...
Click to collapse
It works absolutely fine for me on Pie. Regarding nandroid backup/restore, that I haven't tried, but it should work, ideally.
It is not working for me at the stabel version of OOS android 10 with oneplus 5.
I get bootloob every time.
Does anybody has the same problem?
Did you mean to restore backup ?
If you've mean this no,you can t restore on Q.
I get bootloop too and many others as I ve read.
For now the only solution I have found is to flash ROM zip again without wipe anything and flash Magisk also.
That s what I do to avoid bootloop till a solution is found
TWRP 3.4.0-0 for OnePlus 5/5T (cheeseburger/dumpling) by mauronofrio:
Main changelog: https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
TWRP 3.4.0-0 by mauronofrio
Themed versions coming?
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on chiron
Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose ARM64 as Platform and 10.0 as Android, use the Variant you want. Recommended nano package)
Required TWRP recovery
twrp-3.3.1-chiron-20190608.img
Changelog:
Changes for chiron
Bug reports:
How to submit a bug report
LineageOS GitLab
Donate to support development:
Donate via PayPal to mikeioannina
Donate via PayPal to NeoArian
Donate via PayPal to LineageOS
XDA:DevDB Information
Official LineageOS 17.1 for Mi MIX 2, ROM for the Xiaomi Mi Mix 2
Contributors
mikeioannina, NeoArian
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI Stable V11.0.6.0
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-04-23
Last Updated 2020-04-23
No miui camera for this one?
I can't seem to update to the newest nightly
Code:
lineage-17.1-20200424-nightly-chiron-signed.zip
. The phone seems to be updating, (tried from within the settings and adb sideload) but when I check the updater app it says that the update is ready to install and the current version is from April 23rd.
Yea, there is something weird happening with the latest nightly. I did a clean install (factory reset,format data/system and all that stuff) and I still get April 23 as the build I have installed.
thank you so0 much
gaabrysz said:
I can't seem to update to the newest nightly
Code:
lineage-17.1-20200424-nightly-chiron-signed.zip
. The phone seems to be updating, (tried from within the settings and adb sideload) but when I check the updater app it says that the update is ready to install and the current version is from April 23rd.
Yea, there is something weird happening with the latest nightly. I did a clean install (factory reset,format data/system and all that stuff) and I still get April 23 as the build I have installed.
Click to expand...
Click to collapse
Same here.
Root method?
jimmys121979 said:
Root method?
Click to expand...
Click to collapse
Latest Magisk works fine.
I am enjoying this rom since 20 days.My phone is without root.i am missing some features.....
1 Auto call recording
2 Network videocall is not working
gaabrysz said:
I can't seem to update to the newest nightly
Code:
lineage-17.1-20200424-nightly-chiron-signed.zip
. The phone seems to be updating, (tried from within the settings and adb sideload) but when I check the updater app it says that the update is ready to install and the current version is from April 23rd.
Yea, there is something weird happening with the latest nightly. I did a clean install (factory reset,format data/system and all that stuff) and I still get April 23 as the build I have installed.
Click to expand...
Click to collapse
Use official TWRP that seemed to fix the issue for me
Mihail_Russian said:
Use official TWRP that seemed to fix the issue for me
Click to expand...
Click to collapse
Is your phone showing 24 th april as installed.my phone is showing 23 rd april after installing the 24 th build.
@mikeioannina Thank you very much for all your efforts!
I have version 17.1 installed, with the latest update. I installed it with the MIUI that I had with version 16.0 and the installation was with the Lineageos recovery. When I try to install Magisk, 78% doesn't follow and consequently it doesn't install.
If I install the TWRP recovery, "I don't lose anything?"? I have to install MIUI 11 ?. ? What is the advantage of Lineage recovery over TWRP?
fcaminab said:
I have version 17.1 installed, with the latest update. I installed it with the MIUI that I had with version 16.0 and the installation was with the Lineageos recovery. When I try to install Magisk, 78% doesn't follow and consequently it doesn't install.
If I install the TWRP recovery, "I don't lose anything?"? I have to install MIUI 11 ?. ? What is the advantage of Lineage recovery over TWRP?
Click to expand...
Click to collapse
Twrp recovery has all features of lineage recovery with so much extra goodies.
? Only?
fcaminab said:
? Only?
Click to expand...
Click to collapse
What is meant by your post ?
There will be some difference when Lineageos has prepared a recovery existing TWRP, that is my question:? What is the difference between the two recovery ?.
I don't think Lineage bothers to prepare something if there are no differences
Did a dirty upgrade install from 16, and stuck on the boot animation.
Then I did a wipe and install, but still stuck on the boot animation.
Anyone having the same issue?
markwithk said:
Did a dirty upgrade install from 16, and stuck on the boot animation.
Then I did a wipe and install, but still stuck on the boot animation.
Anyone having the same issue?
Click to expand...
Click to collapse
Hello, I'm on the same boat. I tried dirty flashing coming from LOS 16, then wipe and install but still stuck on boot animation.
I tried using the recommended TWRP and also Orange Fox, but same result.
glock24 said:
Hello, I'm on the same boat. I tried dirty flashing coming from LOS 16, then wipe and install but still stuck on boot animation.
I tried using the recommended TWRP and also Orange Fox, but same result.
Click to expand...
Click to collapse
Well, good to know I'm not alone. Did you also use the 20200426 build? I suspect the build is bad. Maybe try an earlier one?
I spent one night flashing LOS and failing, and then decided to try PE for the first time. It worked
fcaminab said:
There will be some difference when Lineageos has prepared a recovery existing TWRP, that is my question:? What is the difference between the two recovery ?.
I don't think Lineage bothers to prepare something if there are no differences
Click to expand...
Click to collapse
Very quick google search came back with this result: "Right now, Lineage Recovery is really only intended to be used on devices with Seamless Updates (aka A/B partitions) and, in that role, it is only intended to be embedded within the OS's normal Boot image."
You have posted this same question in a few threads now and only received the same answer each time, sir.
TWRP works just fine for our device and includes so much extra options compared to the lineage recovery.
Why not test them both out yourself? Find one you like that suits your needs.