Related
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.
SCREENSHOT IS IN ATTACHMENT
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_b...863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
Download TWRP for D851 from here : twrp-3.1.0-0-D851-Unofficial.img
TWRP MATERIAL THEMES :
here => https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
CREDIT :
TeamWin Recovery Project
Android Matrix Development [https://web.facebook.com/groups/1024872487548231/]
Obaid Muneer
Nickron Davis
Sandeep Sethi
DroidPeepz_Inc.
Seems to work okay but when I try to use aroma I get a reboot.
cidxtc said:
Seems to work okay but when I try to use aroma I get a reboot.
Click to expand...
Click to collapse
Okay, I will look into it.
Thanks for notifying me
iykeDROID™ said:
Okay, I will look into it.
Thanks for notifying me
Click to expand...
Click to collapse
I know that on previous versions I had to use the older cm14 kernel instead of the new for aroma to work.
cidxtc said:
I know that on previous versions I had to use the older cm14 kernel instead of the new for aroma to work.
Click to expand...
Click to collapse
If you don't mind, can you upload that older cm14 kernel?
Thanks
iykeDROID™ said:
If you don't mind, can you upload that older cm14 kernel?
Thanks
Click to expand...
Click to collapse
Everything is on my pc which is dead right now.
cidxtc said:
Everything is on my pc which is dead right now.
Click to expand...
Click to collapse
Sorry about that bro.
Anyway i still try my best
error
Installed but does not start recovery
flako72 said:
Installed but does not start recovery
Click to expand...
Click to collapse
please make sure device is D851
iykeDROID™ said:
please make sure device is D851
Click to expand...
Click to collapse
I tried updating twrp and now I lost supersu so I can not reinstall twrp 3.0.2.0. How do I get supersu & twrp installed again? It still boots to RR is just missing SuperSu & twrp. I tried LG newest root method and it fails at restarting. I tried to manually put in download mode and it ends with "failed" I tried to install supersu.apk it says binary not installed. LG Newest root method v03 fails at 45%
RockNRoll Mullet said:
I tried updating twrp and now I lost supersu so I can not reinstall twrp 3.0.2.0. How do I get supersu & twrp installed again? It still boots to RR is just missing SuperSu & twrp. I tried LG newest root method and it fails at restarting. I tried to manually put in download mode and it ends with "failed" I tried to install supersu.apk it says binary not installed. LG Newest root method v03 fails at 45%
Click to expand...
Click to collapse
Do you have any recovery installed?
No. I can't reinstall twrp 3.0.2.0 with flashify because is says SuperSU has no binary installed. I lost SuperSU when I use Flashify to install twrp 3.1.0.0 I get error no binary installed. When I try volume & power to start recovery I get LG boot screen then RR 7.1.1 boots. No stock recovery either.
RockNRoll Mullet said:
No. I can't reinstall twrp 3.0.2.0 with flashify because is says SuperSU has no binary installed. I lost SuperSU when I use Flashify to install twrp 3.1.0.0 I get error no binary installed. When I try volume & power to start recovery I get LG boot screen then RR 7.1.1 boots. No stock recovery either.
Click to expand...
Click to collapse
I have used the 3.1 twrp and had no issues. Not sure what happened but sounds like you might need to restore a stock rom via tot or kdz files and a pc. Then root and flash twrp.
FYI if your restore to stock all files on internal storage will be deleted so backup any pics/files to your pc before restore.
Witch kdz file should I use. Will down grading from RR 7.1.1 to lollipop or marshmallow be a problem? Will lollipop be be easier to reroot?
I don't know why some other guys are facing my TWRP 3.1.0-0 boot issue.
pls make sure your are on T-Mobile-D851.
Also it uses a Nougat kernel.
iykeDROID™ said:
I don't know why some other guys are facing my TWRP 3.1.0-0 boot issue.
pls make sure your are on T-Mobile-D851.
Also it uses a Nougat kernel.
Click to expand...
Click to collapse
I was thinking the same "make sure you are on T-mobile-d851" also but did not say it because some people here get a little ruffled.
cidxtc said:
I was thinking the same "make sure you are on T-mobile-d851" also but did not say it because some people here get a little ruffled.
Click to expand...
Click to collapse
True though, Thanks :good: for that
Well, am still working of fix for Aroma File Manager as it keeps hanging then reboot to system.
hoping to fix soon
iykeDROID™ said:
True though, Thanks :good: for that
Well, am still working of fix for Aroma File Manager as it keeps hanging then reboot to system.
hoping to fix soon
Click to expand...
Click to collapse
Are you using a precompiled kernel? If so try the one found here https://github.com/Eliminater74/multirom_g3_devices
cidxtc said:
Are you using a precompiled kernel? If so try the one found here https://github.com/Eliminater74/multirom_g3_devices
Click to expand...
Click to collapse
Thanks.
I compile new kernel for use each time i want to work on it
. The full changelog
5G
OnePlus 6T
Win a Mi 9
Honor View20
Honor Hub
Android Q
Galaxy Note 9
LG V40
Snapdragon 855
Pixel 3
TWRP 3.3.1+ will no longer require installer ZIPs, adds a reboot to EDL mode button, and more
TWRP 3.3.1+ will no longer require installer ZIPs, adds a reboot to EDL mode button, and more
For most users, installing any kind of after-market software modification, whether it be a custom ROM, custom kernel, or other tool, requires the use of a custom recovery like TWRP. TWRP has been around for years as the go-to recovery solution for the XDA community. It’s open source and supports hundreds of devices. It offers features like full backup and restore, ADB sideloading, and much more. Today, the project has been bumped to version 3.3.1-0, bringing many improvements in decryption, new features, and a major change to the way TWRP is installed.
The full changelog outlining the many improvements in TWRP’s decryption support can be found below, but for users, the most important change will be the new way to install the custom recovery. Currently, installing TWRP on a device with A/B partitions requires booting TWRP temporarily and then installing it permanently using an installer script. Going forward, users will be presented with a new “install recovery ramdisk” option in recovery. This means that users can boot TWRP and then install it without downloading a separate ZIP file. XDA Senior Recognized Developer Dees_Troy worked with XDA Recognized Developer topjohnwu to make this possible by adapting Magisk‘s boot image patching for TWRP. Dees_Troy says the team will offer installer ZIPs this time around to give people a chance to update from older versions, but future TWRP releases won’t have separate installer scripts.
The other change that’s most relevant to users is the inclusion of a “reboot to EDL mode” button. Emergency Download mode can help you fully unbrick a device if you have the right tool, but the button combination to enter it isn’t as well known to users as the reboot to recovery method.
Here’s the full changelog for the update:
TWRP 3.4.0-0 Changelog
Merge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP
Developers behind (Dees_Troy with thanks to topjohnwu of course)
Directory Access
https://eu.dl.twrp.me/woods/
https://eu.dl.twrp.me/woods/twrp-3.4.0-0-woods.img
Fair warning don't restore previous backups from other versions of TWRP make a fresh one first[/SIZE]
:good:
Finally,a dev to keep woods alive
Well done good job sir. We support you. Contribute to moto e4 more.
Does it support the official OTA updates?
nabirosama said:
Does it support the official OTA updates?
Click to expand...
Click to collapse
Yes if your previous version is. From official channel
Abish4 said:
Yes it your previous version is. From official channel
Click to expand...
Click to collapse
On my device it is Software Channel "reteu", should be supported?
The original patch level is on my device october 2018, i think we can not expect updates from the manufacturer any longer.
I unlocked my phone, but fastboot boot twrp-3.3.1-0-woods.img is not booting into recovery. After entering the command in fastboot mode, the device is just restarting.
(Device unlocked message appears, so this should not be a problem.)
Source:
https://dl.twrp.me/woods/twrp-3.3.1-0-woods.img
fastboot boot twrp-3.3.1-0-woods.img
downloading 'boot.img'...
OKAY [ 0.509s]
booting...
OKAY [ 0.068s]
finished. total time: 0.577s
Click to expand...
Click to collapse
I need to make a full backup before flashing. Is this twrp not working with fastboot boot ... ?
Device Moto E4, woods, XT1762
I never try to boot TWRP with fastboot.I always flash it and everything is good. If you need a backup of the recovery partion, you can do that via adb. Everthing else can be backup'ed by TWRP.
Spielmops
Spielmops said:
I never try to boot TWRP with fastboot.I always flash it and everything is good. If you need a backup of the recovery partion, you can do that via adb. Everthing else can be backup'ed by TWRP.
Spielmops
Click to expand...
Click to collapse
The recovery backup would be some kind of a fail save, if twrp will not boot. If the direct boot would work, I had more faith. :fingers-crossed:
How can I backup the recovery over adb?
I found this:
https://android.stackexchange.com/questions/132314/can-we-backup-the-stock-recovery-img-in-any-way
But I still need root and I can not flash magisk without twrp (and system backup).
Update:
However, because it is working by others, i tried flash recovery twrp-3.3.1-0-woods.img (official), it seems to work.
Creating full backup now ...
Have a look here: https://android.stackexchange.com/questions/205354/show-adb-backup-manual
hi, I have the same problem (XT1761), any idea? thank you
maven33 said:
I unlocked my phone, but fastboot boot twrp-3.3.1-0-woods.img is not booting into recovery. After entering the command in fastboot mode, the device is just restarting.
(Device unlocked message appears, so this should not be a problem.)
Source:
https://dl.twrp.me/woods/twrp-3.3.1-0-woods.img
I need to make a full backup before flashing. Is this twrp not working with fastboot boot ... ?
Device Moto E4, woods, XT1762
Click to expand...
Click to collapse
hi, I have the same problem (XT1761), any idea? thank you
Click to expand...
Click to collapse
hi, I have the same advice ...
Spielmops
hi, solved (even if I don't know why)...
extracted "boot.img" from "[ROM][STOCK][TWRP] Original Stock Firmware-(woods) - TWRP Restore [ROOTED]"
boot.img link https://mega.nz/#!I9cSQC7D!44B_MFvW1wwB3VSF09P1C4-82dqY2i21INNVICFajac
and flashed it
fastboot flash boot boot.img
THEN flashed recovery (I used twrp-3.3.1-0-woods.img, but no matter what you use)
fastboot flash recovery twrp.img
NOW I am working recovery and just flashed a custom rom
Spielmops said:
hi, I have the same advice ...
Spielmops
Click to expand...
Click to collapse
hitman72 said:
hi, solved (even if I don't know why)...
NOW I am working recovery and just flashed a custom rom
Click to expand...
Click to collapse
Did you even try to disable verified boot ?
cause thats the almost every time with boot images on newer or updated devices..
The bootloader was unlocked in by activating USB-debugging, EOM-Unlock in the developer settings. In fastboot mode , only "fastboot oem unlock".
I used the twrp-3.3.1-0-woods.img on my Moto E4 (XT1762) woods. This version worked, but I could not start twrp without a flashing it.
dm verity disable
maven33 said:
I used the twrp-3.3.1-0-woods.img on my Moto E4 (XT1762) woods. This version worked, but I could not start twrp without a flashing it.
Click to expand...
Click to collapse
If you are moving from stock rom and locked device u need to unlock with official key or you can just format your device data... DMVERITY must be disabled at all cost or you have to flash entire stock software update to be running.
See or check post relating to disabling verity in FASTBOOT mode (probably zip) also reboot recovery after flashing.
:fingers-crossed:
hitman72 said:
hi, solved (even if I don't know why)...
extracted "boot.img" from "[ROM][STOCK][TWRP] Original Stock Firmware-(woods) - TWRP Restore [ROOTED]"
boot.img link https://mega.nz/#!I9cSQC7D!44B_MFvW1wwB3VSF09P1C4-82dqY2i21INNVICFajac
and flashed it
fastboot flash boot boot.img
THEN flashed recovery (I used twrp-3.3.1-0-woods.img, but no matter what you use)
fastboot flash recovery twrp.img
NOW I am working recovery and just flashed a custom rom
Click to expand...
Click to collapse
The mega link isn't working. Can you please update the link to the file.
Hey there, can someone please guide me how to install GSI on this device using OFOX or TWRP recovery please? Thank you in advance.
Try this tutorial
How to make GSI Flasher for Samsung Galaxy A51 Super Partition Image
How to convert a gsi image so that it can be installed on a dynamic partition or super image partition. It may be work for other Android devices. This tool will help you to install gsi image on Dynamic Partition or Super Image Partition...
forum.xda-developers.com
It should work fine.
ShaDisNX255 said:
Try this tutorial
How to make GSI Flasher for Samsung Galaxy A51 Super Partition Image
How to convert a gsi image so that it can be installed on a dynamic partition or super image partition. It may be work for other Android devices. This tool will help you to install gsi image on Dynamic Partition or Super Image Partition...
forum.xda-developers.com
It should work fine.
Click to expand...
Click to collapse
Nope, didn't work.
@ShaDisNX255
Any other ideas?
I check this in two apps both giving different answers.
Also I saw
andriyhar said:
Thank you.
Flash img ok.
Click to expand...
Click to collapse
He flashed a/b image
I check in the terminal using
getprop ro.build.ab_update
Got false
But when i flash havoc-os a only system it bootloop
So my question is am i suppose to flash a only or ab?
Also if you have used gsi i'd be glad to hear your experience.
Reading this thread
Aonly or A/B
Treble Check tell me Aonly and Treble Info tell me A/B. Which one must I choose?
forum.xda-developers.com
has lead me to believe
That i should flash a/b img
You can actually force A/B by flashing this zip:
MakeMeSAR.zip | by erfanoabdi for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Then it should flash A/B GSIs properly.
Will my recovery support it though.( Orange Fox by bekirakil)
Also I've only got 3.12GB system partition with no way of resizing it as this device has a dynamic partition
Plus the file name is makemesar and I'm sure that my devices is all ready system as root enabled.
This is just for ensuring you have AB, you can ignore it
System partition, hmmm, you can only flash small roms
I can confirm that you are suppose to use a/b img.
I flashed https://download.havoc-os.com/arm64-ab/Havoc-OS-v4.1-20210208-arm64-ab-Official.img.xz.
Unlike A-only img it booted and worked kindof.
I will not recommend this though as there is no way flash gapps for android 11 and not enough space to flash with a/b with gapps.
Also switched backed to lineage as it was causing random reboots.
Any help over making gsi stable will be much appreciated.
This post is meant for another fourm
When I restored the backup it failed but I was able to boot to lineage os which still contain gapps and magisk.
Since it showed failed I clean install everything again. The recovery read something like something something product partition, odm partion, system partiton.
Don't know if these logs are useful but I've attracted them below
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 Poco F3/Mi 11X/Redmi K40
touch and adb work
flashing works
USB OTG works
Decryption is working
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
3. select the new image
4. after that is done, if you were using a custom kernel, reflash it now
5. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_alioth
https://github.com/TeamWin/android_device_xiaomi_sm8250-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomipocof3.html
Unofficial android 12 builds: https://www.pling.com/p/1836619/
mirror: https://store.kde.org/p/1836619/
Thanks for your hard work
All function has usable especially decryption.
Thank you mate!! That's is very important for all the community .What version of magisk i have to install??But you mean flash the zip of magisk??Thanks.
Awesome, mate!
I've been waiting for this, thank you sir for your contribution!
@Nebrassy Nice work - tested on my crDroid working-build and all ok
I only can say thank you a lot!! I'll buy a beer
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
reas0n said:
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
Click to expand...
Click to collapse
I believe that rom has customized encryption, so it's not supported
Nebrassy said:
I believe that rom has customized encryption, so it's not supported
Click to expand...
Click to collapse
Damn.. I will wait for any officially supported custom ROM then so I could just get OTAs, I dont want to do another wipe and setup lol. thx anyway
raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
your what?
raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
Not shared as yet?
arifqur said:
Not shared as yet?
Click to expand...
Click to collapse
Not yet. Won't take long though when first release will be posted in development.
this works "out of the box" for poco f3 with miui 12.x?
Thank you
Henkl said:
this works "out of the box" for poco f3 with miui 12.x?
Click to expand...
Click to collapse
answering my own question: you have to unlock the phone first with MIUI unlock tool.
AND unlocking involves wiating on part of xiaomi site afer registering ...can be even 7 days..
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
The password is ur security PIN for unlocking ur phone.
No idea about backuping the boot.img in TWRP (I am not using it )
Nebrassy said:
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
Click to expand...
Click to collapse
I have entered a password but it failed. Is it a free password ?
EDIT : It's ok, sorry. the security PIN, of course !!!
EDIT 2 : And Thank you very much for your work and your help