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.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
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!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
More information:
Most Xperia S kernels are probably including CWM by default in the boot image. About a month ago I submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that I wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed. This same setup is possible in other kernels including stock Sony kernels. On our website's download link you will find a copy of a recent stock ICS kernel for the Xperia S that includes TWRP as well as the extract_elf_ramdisk utility.
If the kernel you have installed doesn't support this extract_elf_ramdisk setup, then you won't be able to use the GooManager installed copy of TWRP. Bug your kernel or ROM developer and ask them to update their images so that you can choose what recovery you want.
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Thanks a lot but from your site can we get only 2.4.0.0. And it's for the oldest rom kernel (.452). Can you please update the ramdisk and modem for the our Xperia S?
anychange for locked BL?
Advance Stock Kernel 17 comes with CWM.
How Can I install this over CMW?
eScapeeXc said:
Thanks a lot but from your site can we get only 2.4.0.0. And it's for the oldest rom kernel (.452). Can you please update the ramdisk and modem for the our Xperia S?
Click to expand...
Click to collapse
You should take a look at the "Download - FOTAKernel Image" header. There's no need to install that stock kernel, you can also just push the recovery. The way described on the website requires you use Terminal Emulator but there's an easier way. (I also don't really understand which is the right version because there is 2.4.3.0 for nozomi and 2.4.3.0 for LT26i and afaik that's the same device).
Just install GooManager on your phone, select "Flash ROMs" and there should be a message asking if you have a custom recovery. Select to install one and the latest version of TWRP will be installed.
I'm using Stock+ kernel, that already had TWRP 2.4.1 recovery, after doing this with GooManager I have TWRP 2.4.3.0. If you're using any of the other .55 kernels it should be work as well.
mrkidvn said:
anychange for locked BL?
Click to expand...
Click to collapse
No idea.
darkerm said:
Advance Stock Kernel 17 comes with CWM.
How Can I install this over CMW?
Click to expand...
Click to collapse
That's basically the same question eScapeeXc asked so the answer is the same .
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
Is it works on locked bootloader?
Sent from my LT26i using xda app-developers app
Will:
dd if=/dev/zero of=/dev/block/mmcblk0p11
remove the recovery?
Is there a way to choose between the recovery from the kernel and this one on fota while booting?
How many space has the fota partition on our device?
algates said:
Is it works on locked bootloader?
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
It needs a modified ramdisk. So it will not work.
Sv: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
Dees_Troy said:
More information:
Most Xperia S kernels are probably including CWM by default in the boot image. About a month ago I submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that I wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed. This same setup is possible in other kernels including stock Sony kernels. On our website's download link you will find a copy of a recent stock ICS kernel for the Xperia S that includes TWRP as well as the extract_elf_ramdisk utility.
If the kernel you have installed doesn't support this extract_elf_ramdisk setup, then you won't be able to use the GooManager installed copy of TWRP. Bug your kernel or ROM developer and ask them to update their images so that you can choose what recovery you want.
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Click to expand...
Click to collapse
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?
twk99 said:
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?
Click to expand...
Click to collapse
Yes.
twk99 said:
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?
Click to expand...
Click to collapse
[email protected] said:
Yes.
Click to expand...
Click to collapse
Keep in mind, if kernel you are using doesn't implement elf extract then it will not read FOTA partition so it still use recovery that came with kernel.
And almost all kernel came with CWM.
Sv: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
tosa.th said:
Keep in mind, if kernel you are using doesn't implement elf extract then it will not read FOTA partition so it still use recovery that came with kernel.
And almost all kernel came with CWM.
Click to expand...
Click to collapse
I understand that. I am using latest FXP CM10 so it should work right?
i rooted my uncle sxs like this http://forum.xda-developers.com/showthread.php?t=2133063 after that i installed cmw with this http://forum.xda-developers.com/showthread.php?t=1756346
yes i have unlocked the bootloader. but now the recovery says cannot mount cache/recover/log etc.
i post this here because after installing opensemc 0.4 the problem is still there. only after a factory reset and installing 2 times it will boot.
is this a problem some one reconizes?
R: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
raydekok said:
i rooted my uncle sxs like this http://forum.xda-developers.com/showthread.php?t=2133063 after that i installed cmw with this http://forum.xda-developers.com/showthread.php?t=1756346
yes i have unlocked the bootloader. but now the recovery says cannot mount cache/recover/log etc.
i post this here because after installing opensemc 0.4 the problem is still there. only after a factory reset and installing 2 times it will boot.
is this a problem some one reconizes?
Click to expand...
Click to collapse
I read that FXP official kernel support external recovery from 3-4 release
But maybe raymanfx has not implemented this
Btw that recovery is a crap.. Try advanced stock kernel
Sent from my Xperia S using xda app-developers app
just flash this thru the current recovery?
and install rom again?
twk99 said:
I understand that. I am using latest FXP CM10 so it should work right?
Click to expand...
Click to collapse
I don't use FXP, so I don't know is it support elf extract.
Check with FXP team about their kernel if it does support then you are good to go.
reading a bit more and i can instal the recovery thru goomanager and thats it. so i install the recovery again. is it so simpel?
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
Installing seems ok. But how can I uninstall twrp from fota?
Sent from my LT26i using xda premium
raydekok said:
reading a bit more and i can instal the recovery thru goomanager and thats it. so i install the recovery again. is it so simpel?
Click to expand...
Click to collapse
quote myself. this worked but under mount he can not select mount /system.
under my phone i can. what would that be?
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
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.
CHANGELOG for 3.1.1-0:
-waiting for official docs, looks like any thread has been updated.. Nor official website
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: doc (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
INSTALLATION:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
Download:
3.1.0: Google Drive
3.1.1: Android File Host
XDA:DevDB Information
Unofficial TWRP for the UMI SUPER, Tool/Utility for all devices (see above for details)
Contributors
joe2k01
Source Code: https://github.com/joe2k01/android_device_umi_SUPER/tree/TWRP
Version Information
Status: Testing
Created 2017-03-19
Last Updated 2017-05-14
Flashing said OK in Flash Tool but nothing is different in power+volup or power+voldown.
Using the latest March rom from their forum.
Problem with TWRP
gayfagxxx said:
Flashing said OK in Flash Tool but nothing is different in power+volup or power+voldown.
Using the latest March rom from their forum.
Click to expand...
Click to collapse
Same problem !
any solutions :crying:
Same problem as the friends above @SerialFlasher33 and @gayfagxxx .
I transfer the TWRP successfully via sp flash tool, pore at the time of loading anything on the screen nothing.
Already tried several versions of TWRP.
Here I have android 7 already with update.
rexbauru said:
Same problem as the friends above @SerialFlasher33 and @gayfagxxx .
I transfer the TWRP successfully via sp flash tool, pore at the time of loading anything on the screen nothing.
Already tried several versions of TWRP.
Here I have android 7 already with update.
Click to expand...
Click to collapse
SerialFlasher33 said:
Same problem !
any solutions :crying:
Click to expand...
Click to collapse
gayfagxxx said:
Flashing said OK in Flash Tool but nothing is different in power+volup or power+voldown.
Using the latest March rom from their forum.
Click to expand...
Click to collapse
You must boot in TWRP exactly after flashing it: Flash in SPFT then start pressing volup and then press power
could you also share this new build here?
https://forum.xda-developers.com/general/general/umi-install-custom-recovery-twrp-cwm-t3385733
any scatter file provided to flash it via Flashtool?
thnx
megthebest said:
could you also share this new build here?
https://forum.xda-developers.com/general/general/umi-install-custom-recovery-twrp-cwm-t3385733
any scatter file provided to flash it via Flashtool?
thnx
Click to expand...
Click to collapse
You can use the stock ROM's scatter file
joe2k01 said:
You can use the stock ROM's scatter file
Click to expand...
Click to collapse
I know my friend, it's not for me but for all users that can be in trouble without scatter provided (if they come from stock Umi Super).
So is only a suggestion..
thanks anyway
joe2k01 said:
You must boot in TWRP exactly after flashing it: Flash in SPFT then start pressing volup and then press power
Click to expand...
Click to collapse
Thanks, this worked.
I used the latest march rom on my phone and loaded the scatter from the same rom. I obtained the rom file and the flash tool on the UMi forums.
Then I un-ticked everything and changed the location to the recovery, pressed download, shutdown my phone, waited for it to be done, unplugged it, held volup+power and now it works.
Unfortunately for me it does not work ... I tried to start immediately the phone into recovery but after a short flash the display starts the system stock umi
@bastard81 can you try to connect your phone(powered on) and from adb type adb reboot recovery ?
joe2k01 said:
@bastard81 can you try to connect your phone(powered on) and from adb type adb reboot recovery ?
Click to expand...
Click to collapse
I tried, but even this system seems to not work. The phone will restart, and for a moment I see the display flashing. After it starts immediately with the system but without going into recovery ...
I do not know what else to try .. From the developer options have also enabled the oem unlock. Also tried without. Reinstalled 3 times with spflashtool and everything works perfectly. But the recovery just does not want to work.
Ps thanks for your support
bastard81 said:
I tried, but even this system seems to not work. The phone will restart, and for a moment I see the display flashing. After it starts immediately with the system but without going into recovery ...
I do not know what else to try .. From the developer options have also enabled the oem unlock. Also tried without. Reinstalled 3 times with spflashtool and everything works perfectly. But the recovery just does not want to work.
Ps thanks for your support
Click to expand...
Click to collapse
I guess you some how corrupted recovery partition, try to backup your IMEIs and then try the option format all+reflash on SPFT. You'll lose IMEI
worked well with me (Y)
Hi joe2k01 from the forum 4PDA. Thanks for the work. Put Your TWRP3.1.0 through TWRP3.0.2 and tested on firmware v7.01_20170123. While there are no errors.
Cant Get into Anything But TWRP
I Flashed Twrp, Twrp works fine, just nothing else. Even flashed a rom and have no boot just twrp.
TIA
joe2k01 said:
Team Win Recovery Project 3.x
Click to expand...
Click to collapse
you ****ing young hacker. you need to make reference to the authors , when you take other people's files...
jemmini said:
you ****ing young hacker. you need to make reference to the authors , when you take other people's files...
Click to expand...
Click to collapse
WTF is wrong with you man? You are in the credits list on GitHub. I took only your kernel since you are anti-opensource and don't want to explain how you built it.
bastard81 said:
I tried, but even this system seems to not work. The phone will restart, and for a moment I see the display flashing. After it starts immediately with the system but without going into recovery ...
I do not know what else to try .. From the developer options have also enabled the oem unlock. Also tried without. Reinstalled 3 times with spflashtool and everything works perfectly. But the recovery just does not want to work.
Ps thanks for your support
Click to expand...
Click to collapse
The same for me
Im on stock v3.02_20161121 odex from silent27 had TWRP 3.02 and just flashed TWRP 3.1.1 super img. over and it worked just fine.
On top of that flashed a twrp theme(310x v.2 hdpi light play theme by z31s1g) wich on TWRP 3.02 themes didnt worked for me.
. 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.
Disclaimer:
HTML:
/* Your warranty is now void! I'm not responsible for bricked devices, dead SD cards or anything else that may occur to you and / or your device.
* Do it at your own risk!
This recovery was not made by me, i'm just sharing it in easier ways to download. The guy behind this is wzsx150, thank him for it.
After a lot of pain researching and trying to download from Baidu servers i finally managed to get this custom TWRP to get rid of force encryption on stock MIUI because this recovery can successfully decrypt with no need to do a format data.
Just installed magisk v20.2 on stock MIUI global 11.0.4 and it works. :good:
Info
- Based on TWRP 3.3.1
- Build date: 2019.11.19
- Model: Redmi 7, Red Rice 7
- Developer: wzsx150 (profile)
Install Instructions
Warning: unlocked bootloader needed!
Fastboot
1. Download IMG file below
2. Rename file to recovery.img and put it into your adb path (if you don't have adb check this link)
3. Reboot your device into fastboot mode by holding down vol - and power button while device is off and connect to PC
4. Open cmd in your adb path and run the following command: fastboot flash recovery recovery.img
5. Run fastboot reboot, and hold down vol + key until device enters into twrp
Custom Recovery
1. Download ZIP file below to internal storage
2. Reboot to recovery
3. Install zip
4. Reboot to recovery
Downloads
IMG: https://drive.google.com/uc?id=16zXoYeviDUeV9zsSeDjyi_P8NnQkJhLr&export=download
ZIP: https://drive.google.com/uc?id=1ZF4C5-B9rlHKJVO0GbtS_ZjT5VlX1taH&export=download
Special Thanks
- TeamWin for building TWRP for a lot of devices, including this one
- wzsx150 and LR.Team for making this mod
- Firmwarex.net for providing a free Baidu account to download from their servers
Source: https://www.weibo.com/6033736159/IgY1Ex98h?from=page_1005056033736159_profile&wvr=6&mod=weibotime
Works backups AND restore opción?
mcf7 said:
Disclaimer:
/* Your warranty is now void! I'm not responsible for bricked devices, dead SD cards or anything else that may occur to you and / or your device.* Do it at your own risk!
This recovery was not made by me, i'm just sharing it in easier ways to download. The guy behind this is wzsx150, thank him for it.
After a lot of pain researching and trying to download from Baidu servers i finally managed to get this custom TWRP to get rid of force encryption on stock MIUI because this recovery can successfully decrypt with no need to do a format data.
Just installed magisk v20.2 on stock MIUI global 11.0.4 and it works. :good:
Info
- Based on TWRP 3.3.1
- Build date: 2019.11.19
- Model: Redmi 7, Red Rice 7
- Developer: wzsx150 (profile)
Install Instructions
Warning: unlocked bootloader needed!
Fastboot
1. Download IMG file below
2. Rename file to recovery.img and put it into your adb path (if you don't have adb check this link)
3. Reboot your device into fastboot mode by holding down vol - and power button while device is off and connect to PC
4. Open cmd in your adb path and run the following command: fastboot flash recovery recovery.img
5. Run fastboot reboot, and hold down vol + key until device enters into twrp
Custom Recovery
1. Download ZIP file below to internal storage
2. Reboot to recovery
3. Install zip
4. Reboot to recovery
Downloads
IMG: https://drive.google.com/uc?id=16zXoYeviDUeV9zsSeDjyi_P8NnQkJhLr&export=download
ZIP: https://drive.google.com/uc?id=1ZF4C5-B9rlHKJVO0GbtS_ZjT5VlX1taH&export=download
Special Thanks
- TeamWin for building TWRP for a lot of devices, including this one
- wzsx150 and LR.Team for making this mod
- Firmwarex.net for providing a free Baidu account to download from their servers
Source: https://www.weibo.com/6033736159/IgY1Ex98h?from=page_1005056033736159_profile&wvr=6&mod=weibotime
Click to expand...
Click to collapse
Thanks a lot ? so this should work to install any custom rom? Like the pixel experience one?
Sent from my Xiaomi Redmi 7 using XDA Labs
Jojethegamerpro said:
Works backups AND restore opción?
Click to expand...
Click to collapse
I haven't tested but it should work
SammyInTheCity said:
Thanks a lot ? so this should work to install any custom rom? Like the pixel experience one?
Click to expand...
Click to collapse
If you're planning to install a custom rom, any custom recovery should work, including this one.
The main advantage of using this recovery is that you can bypass the stock rom (maybe stock based roms too) force encryption to access your partitions on recovery.
mcf7 said:
If you're planning to install a custom rom, any custom recovery should work, including this one.
The main advantage of using this recovery is that you can bypass the stock rom (maybe stock based roms too) force encryption to access your partitions on recovery.
Click to expand...
Click to collapse
Okay thanks, I have my bootloader locked at the moment, but when I finally am able to unlock it I'll definitely use this
Sent from my Xiaomi Redmi 7 using XDA Labs
Thank you for sharing
Ask password for decryption
But my phone isn't encrypted
Tried my lock screen password it didn't work
Tried to remove all passwords but still asks for password
hamedhd said:
Ask password for decryption
But my phone isn't encrypted
Tried my lock screen password it didn't work
Tried to remove all passwords but still asks for password
Click to expand...
Click to collapse
Which recovery did you used before this? And what's your rom?
For the first time i used LR.Team's recovery i installed recovery, did a format data(due to the password issue as you), installed miui global and magisk and the system booted properly and after that recovery didn't asked for password anymore and i've been able to mount partitions and do other stuff.
I can't flash gapps using this twrp, fix it please
Me_Only said:
I can't flash gapps using this twrp, fix it please
Click to expand...
Click to collapse
I'm not the dev behind this project, i'm just sharing wzsx150's work in an easier way to download. You can contact him on the source link at the bottom of OP.
I only tested this twrp with stock rom which doesn't need gapps and encountered no issues.
mcf7 said:
I'm not the dev behind this project, i'm just sharing wzsx150's work in an easier way to download. You can contact him on the source link at the bottom of OP.
I only tested this twrp with stock rom which doesn't need gapps and encountered no issues.
Click to expand...
Click to collapse
same here but the custom roms that doesn't include gapps sucks, that's the problem with this twrp it cant flash gapps, thanks for the response bro.