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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.1.1-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
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_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (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
DOWNLOAD:
Device Explinations:
us996=US996
elsa=LS997,VS995,H910,H915 etc...
h918=H918
1) Download the latest version for your device from here: https://forum.xda-developers.com/devdb/project/?id=20590#downloads
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
2) Use Official TWRP app
3) Agree to use root permissions
4) Press "Select file to flash"
5) Navigate to either your external sdcard(xxxx-xxxx) or internal storage(storage/emulated/0) depending on where you placed the img.
6) Select the 3.1.0-0 image and press Flash to recovery.
7) Profit???
BUG REPORTING:
Please reply to this thread stating what is wrong and I will look into it. Bugs must be reproducible.
ROM DEVELOPERS:
This twrp image is no longer using the us996 as the universal assert. From now on please use "elsa" as your assert for roms other than H918 and US996 ROMS.
US996 assert is still us996.
Also if you use the build date assert it needs to be updated
XDA:DevDB Information
TWRP-3.1.1-0 Unofficial, Tool/Utility for the LG V20
Contributors
me2151
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.1.1-0
Stable Release Date: 2017-05-20
Created 2017-05-09
Last Updated 2017-05-20
BUGS:
exFAT issues on all build - Resolved - Download links updated - 05-09-17
OTG Issues - Confirmed
First because why not and the recovery works very well been testing it guys
SaintZ93 said:
First because why not and the recovery works very well been testing it guys
Click to expand...
Click to collapse
Second! Lol I have had no issue while testing this new Twrp either! You are a beast man... Keep up the great work!
Sent from my LG-LS997 using Tapatalk
OP, if I were near you, I'd hug you.
Thanks!
Is anyone having issues with their external storage (micro SD) not mounting on the H918 version?
AngryManMLS said:
Is anyone having issues with their external storage (micro SD) not mounting on the H918 version?
Click to expand...
Click to collapse
+1
I hadn't noticed that yet, but since you brought it to our attention I went ahead and checked for myself.
I can confirm there is a mount issue for sdcard.
I flashed back to previous TWRP version and sdcard mount is fine.
I'm sure it will get worked out soon.
Thank yoi for the find.
Also thank you to @me2151 for your contributions to this device and community!
Which on for ls997 Elsa or h918
AngryManMLS said:
Is anyone having issues with their external storage (micro SD) not mounting on the H918 version?
Click to expand...
Click to collapse
Can I get some more information regarding this? how is it not mounting, mtp? in general? What is your FileSystem on the sdcard?
stangdriver44 said:
+1
I hadn't noticed that yet, but since you brought it to our attention I went ahead and checked for myself.
I can confirm there is a mount issue for sdcard.
I flashed back to previous TWRP version and sdcard mount is fine.
I'm sure it will get worked out soon.
Thank yoi for the find.
Also thank you to @me2151 for your contributions to this device and community!
Click to expand...
Click to collapse
I need more information regarding this bug. my tester did not encounter this and I just looked through his log he sent me and i see no issues with external sdcard. It reads his sdcard and even gives me filesystem information. He is able to mount it properly and add and remove files through mtp. Can either you or Angryman PM me and ill give you my HO so we get get this resolved quicker?
pbedard said:
Which on for ls997 Elsa or h918
Click to expand...
Click to collapse
Please tell me this is a joke?
me2151 said:
Can I get some more information regarding this? how is it not mounting, mtp? in general? What is your FileSystem on the sdcard?
Click to expand...
Click to collapse
My file system is ExFat. On your 3.1.0.0 it's simply not letting me mount external storage (micro SD) at all when I got into mount and it shows 0 file size when I try to select storage. As noted the previous TWRP for the H819 has external storage working for me.
AngryManMLS said:
My file system is ExFat. On your 3.1.0.0 it's simply not letting me mount external storage (micro SD) at all when I got into mount and it shows 0 file size when I try to select storage. As noted the previous TWRP for the H819 has external storage working for me.
Click to expand...
Click to collapse
odd. i did send you a test build for you to try. let me know if it helps.
exFAT issue have been fixed. i am making the new builds atm and they will be replacing the old links
EDIT: Files updated. exFAT support is proper now.
we will eventually be able to back up the efs?
fix-this! said:
we will eventually be able to back up the efs?
Click to expand...
Click to collapse
efs partitions were already able to be backed up. but yes i have it enabled to be able to backup the efs partitions.
Okay just flashed on my 918 exactly as OP instructed and now i can't boot into TWRP. Seems like i lost recovery. Any ideas?
This is awesome!!!
Question, are there any other advantages aside from backing up & restoring?
nymikey said:
Okay just flashed on my 918 exactly as OP instructed and now i can't boot into TWRP. Seems like i lost recovery. Any ideas?
Click to expand...
Click to collapse
That is an odd issue. How are you trying to boot into twrp? have you tried "adb reboot recovery" from your system? I have cross flashed the h918 onto my ls997 using this method and it still boots fine. If you did indeed lose your recovery pm me and ill help you get it going again.
pbedard said:
I am sorry I won't post in u guys forums anymore thought asking questions is how learn but nevermind. As I won't try to help anymore either. Ciao! 9 years here never got talked down too.!!
Won't ever donate to both of you again either.
Click to expand...
Click to collapse
@pbedard The reason we act like this to you is because you always cause issues. you dont read OP threads and spread lies. I was told you were a problem on the Note 4 as well. so it isnt the devs. its you.
x_curtis said:
This is awesome!!!
Question, are there any other advantages aside from backing up & restoring?
Click to expand...
Click to collapse
For our specific devices i have noticed that backups and restores are much quicker. For the elsa devices there was still static on boot however @jcadduono did a neat little trick of blanking the screen on boot so it would fix that static. I have added the proper device tree fixes to the kernel twrp uses so that no longer is there. The kernel and device trees are fully updated as of release so its the latest and greatest.
nymikey said:
Okay just flashed on my 918 exactly as OP instructed and now i can't boot into TWRP. Seems like i lost recovery. Any ideas?
Click to expand...
Click to collapse
I had the same issue. Wouldnt boot to recovery so i just used the twrp apps flash recovery function to flash back to 3.0.2-1
me2151 said:
For our specific devices i have noticed that backups and restores are much quicker. For the elsa devices there was still static on boot however @jcadduono did a neat little trick of blanking the screen on boot so it would fix that static. I have added the proper device tree fixes to the kernel twrp uses so that no longer is there. The kernel and device trees are fully updated as of release so its the latest and greatest.
Click to expand...
Click to collapse
I noticed the backup speed after you replied, it IS noticeably quicker. I've been on AOSP's for a bit but I'll try out stock rom's to check out the boot up. Thanks for the new recovery
Related
TWRP 2.8.7.0 for LG G3
D850 / D851 / D852 / D855 / LS990 / VS985
Team Win Recovery Project 2.x, or twrp2 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.
Click to expand...
Click to collapse
Phone look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tablet look:
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
Features
* Bumped
* F2FS Filesystem Support
* Double Tap to Wake
* Modem Backup Support
Requirements
- Root
Installation Instructions:
A. With custom recovery already installed:
1. Download
2. Install TWRP in recovery
3. Reboot recovery
B. With stock recovery (Need ADB):
1. Download & extract zip
2. Move recovery.img to internal storage.
3. Open terminal window/command prompt to execute following commands
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
You should be in your updated recovery now
Downloads:
AndroidFileHost | BasketBuild
Warning
I am not responsible for anything that happens to your device!
Credits
@Dees_Troy & TeamWin - for TWRP touch recovery
@thecubed & Team CodeFire - for Bump!
Sources
https://github.com/777jon
https://github.com/omnirom
XDA:DevDB Information
[RECOVERY] TWRP touch recovery 2.8.7.0, Tool/Utility for the LG G3
Contributors
777jon, Dees_Troy
Version Information
Status: Stable
Created 2015-02-12
Last Updated 2015-06-23
FAQ:
Can I install via Flashify?
Yes, extract the recovery.img from the zip file and use Flashify to flash it.
How do I enter recovery mode?
http://youtu.be/ifi-ArGeTzQ
Change Log
Code:
06/22/15 (TWRP 2.8.7.0)
- TWRP 2.8.7.0 release
03/26/15 (TWRP 2.8.6.1)
- TWRP 2.8.6.0 release
03/01/15 (TWRP 2.8.5.1)
- F2FS Filesystem Support
- Double Tap to Wake
02/12/15 (TWRP 2.8.5.0)
- TWRP 2.8.5.0 release
01/13/15 (TWRP 2.8.4.0)
- TWRP 2.8.4.0 release
12/22/14 (TWRP 2.8.3.0)
- TWRP 2.8.3.0 release
12/09/14 (TWRP 2.8.2.0)
- Support Modem Backup
- Display "External SD" instead of "external_sd"
12/08/14 (TWRP 2.8.2.0)
- Initial release
- TWRP 2.8.2.0
this is update recovery twrp-2.8.0.0 ??
Does it support modem backup?
Sent from my LG-D855 using Tapatalk
I just flashed this and it does indeed have Modem backup options. Many thanks.
Nice Work Thanks :good::good::good:
Many Thanks for this, just flashed and now performing a backup and got the message :-
E: Unable to locate '/modem' partition for backup calculations
Backing up Boot...
Backing up System...
Backing up Data...
Backing up Cache...
E: Unable to locate '/modem' partition for backup process.
Backing up EFS...
Backing up efs2...
Updating partition tables
...done
[BACKUP COMPLETED IN 124 SECONDS]
Any idea why the modem partition is not being backed up...?
Thanks Again.
ask @Skin1980 to implement modem backup.
nikosblade said:
ask @Skin1980 to implement modem backup.
Click to expand...
Click to collapse
Adding the modem backup is very simple, just edit the fstab file in the ramdisk.
Skin1980, any chance you could do this please, I'm sure it would be appreciated by many users
teddy0209 said:
Does it support modem backup?
Click to expand...
Click to collapse
gsw5700 said:
Many Thanks for this, just flashed and now performing a backup and got the message :-
E: Unable to locate '/modem' partition for backup calculations
Backing up Boot...
Backing up System...
Backing up Data...
Backing up Cache...
E: Unable to locate '/modem' partition for backup process.
Backing up EFS...
Backing up efs2...
Updating partition tables
...done
[BACKUP COMPLETED IN 124 SECONDS]
Any idea why the modem partition is not being backed up...?
Thanks Again.
Click to expand...
Click to collapse
I'll include in the next update.
New TWRP build!
Changes
- Add support for D852
- Support Modem Backup
- Display "External SD" instead of "external_sd"
777jon said:
New TWRP build!
Changes
- Add support for D852
- Support Modem Backup
- Display "External SD" instead of "external_sd"
Click to expand...
Click to collapse
Thanks alot for this! I just decompiled your recovery image (.img) and repacked it and flashed via flashify but it failed! Is there some type of signing that needs to be done?
I'm only trying to replace curtain.jpg with the attached image
i can't change button vibration.
settings > vibration duration > button vibration is set to 80 and i cant change it to 0
sean222 said:
Thanks alot for this! I just decompiled your recovery image (.img) and repacked it and flashed via flashify but it failed! Is there some type of signing that needs to be done?
I'm only trying to replace curtain.jpg with the attached image
Click to expand...
Click to collapse
I think you need to rebump the recompiled recovery img...
@777jon and everyone interested in this recovery:
Latest release (12-09) doesn't boot, phone seem to be bootlooping in the recovery... had to roll back to 12-09 and everything works fine again.
EDIT: I'm on a D855 and I refer to that release.
EDIT2: Maybe a problem with my settings...
New release 10 Dec lost modem backup/restore support. D855
TWRP run greate and my Backup is okay with efs md5 and efs.img...
When install the theme from 2.8.0.0 gives Recovery Loop....
Say me..
Give theme for TWRP 2.8.2.0 ???
teddy0209 said:
I think you need to rebump the recompiled recovery img...
Click to expand...
Click to collapse
Can you confirm this @777jon
And thank you for the Dec. 10 update Much appreciated!
Just restored full nandroid and worked fine, many thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is for International SM-G900H Exynos models only!
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.
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
Universal
CHANGELOG for 3.2.0-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
-Fix gzip backup error in adb backups (bigbiff)
-Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
-Better support for installing Android 8.0 based zips due to legacy props (nkk71)
-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
-v2 fstab support (Dees_Troy)
-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
-Various other minor bugfixes and tweaks
CHANGELOG for 3.1.1-1:
- Fix twrp on emmc based devices
CHANGELOG for 3.1.1-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
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
CHANGELOG FOR 3.0.2-0
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
support new CM 13.0 pattern encryption (sultanqasim)
fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
libtar updated to latest upstream and fixes (jcadduono)
fixes for loading custom themes (_that)
TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
translation updates - added Italian, Czech and Polish and significant updates to Dutch
progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
fix input box text display (Dees_Troy)
reboot option after zip install complete (bigbiff)
other mostly invisible bug fixes and improvements
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
DOWNLOADS
https://dl.twrp.me/k3gxx/
HOW TO INSTALL???
follow instructions HERE
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy 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.
XDA:DevDB Information
TWRP 3.1.1-1 G900H, Tool/Utility for the Samsung Galaxy S5
Contributors
somadsul
Version Information
Status: Stable
Current Stable Version: 3.1.1-1
Stable Release Date: 2017-08-25
Created 2016-09-19
Last Updated 2017-09-08
XDA:DevDB Information
TWRP 3.2.0-0 G900H, Tool/Utility for the Samsung Galaxy S5
Contributors
somadsul
Source Code: Source Code : https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.2.0-0
Stable Release Date: 2017-12-01
Created 2016-09-19
Last Updated 2017-12-03
Reserved
Reserved
Can you give changelog or difference between your recovery and fevax's one
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
Also can I flash it via flashify???
TheDarkSithLord said:
Can you give changelog or difference between your recovery and fevax's one
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
Also can I flash it via flashify???
Click to expand...
Click to collapse
Yes, thread will update tomorrow, I was in hurry to upload recovery only,
You can extract tar.md5 as you get recovery.img & flash it with flashify
GRACIAS!
somadsul said:
Yes, thread will update tomorrow, I was in hurry to upload recovery only,
You can extract tar.md5 as you get recovery.img & flash it with flashify
Click to expand...
Click to collapse
Will try and report thanks)
@somadsul
Will try it :good:
Edit: Flashed the recovery and it works
TheDarkSithLord said:
Will try and report thanks)
Click to expand...
Click to collapse
Thanks to thread or post not to me Lord...
That's the great news. Thanks to OP
Sent from my SM-N930F using XDA-Developers mobile app
Flashed & its working. Thank you.
Just finished flashing via Odin, for some reason the zip wouldn't work, I'm on TWRP 3.0.0.0, anyway it works flawlessly now
iDouvie said:
Just finished flashing via Odin, for some reason the zip wouldn't work, I'm on TWRP 3.0.0.0, anyway it works flawlessly now
Click to expand...
Click to collapse
Ohh Sorry mate I will look into this,
Is there you get flashing error or flashed succesfully but still you are on old recovery?
somadsul said:
Ohh Sorry mate I will look into this,
Is there you get flashing error or flashed succesfully but still you are on old recovery?
Click to expand...
Click to collapse
When i flashed, it'd say something like Successfully flashed TWRP 3.0.0 and then end the installation but still remain on TWRP 3.0.0.0, it wasn't that big a deal since Odin works wonders, thanks for the update!
Flashed the recovery and it is working fine. Thank you
Mulmiz said:
Flashed the recovery and it is working fine. Thank you
Click to expand...
Click to collapse
Is you flashed zip or through the Odin?
iDouvie said:
When i flashed, it'd say something like Successfully flashed TWRP 3.0.0 and then end the installation but still remain on TWRP 3.0.0.0, it wasn't that big a deal since Odin works wonders, thanks for the update!
Click to expand...
Click to collapse
Yeah but its easy to flash others with older recovery so need to find the problem, I was tested & worked but for you not worked so wanted to find the problem
sent from my Tencent OS G900H
somadsul said:
Is you flashed zip or through the Odin?
Click to expand...
Click to collapse
yes Odin flash, I am trying to root my device, flashed latest SuperSu(2.78) twice, still my device is not rooted any idea ?
Mulmiz said:
yes Odin flash, I am trying to root my device, flashed latest SuperSu(2.78) twice, still my device is not rooted any idea ?
Click to expand...
Click to collapse
Is this problem you get after this recovery flash or you trying to root first time?
somadsul said:
Is this problem you get after this recovery flash or you trying to root first time?
Click to expand...
Click to collapse
I had twrp by Fevax and rooted. Lost recovery and root after update via kies. Was Planing to flash twrp again, saw your post and flashed your version of twrp. Your version of twrp flashed successfully but unable to root my device. I switched back to TWRP by Fevax and able to root
Thanks anyway
Mulmiz said:
I had twrp by Fevax and rooted. Lost recovery and root after update via kies. Was Planing to flash twrp again, saw your post and flashed your version of twrp. Your version of twrp flashed successfully but unable to root my device. I switched back to TWRP by Fevax and able to root
Thanks anyway
Click to expand...
Click to collapse
Strange...
Will find the problem but I am thinking that I have not faced this & I think 40 people are downloaded & no one is reporting other than you so waiting if any other report.
sent from my Tencent OS G900H
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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.
Click to expand...
Click to collapse
Images
Installation instructions
NOTE: Read the FAQ from Post #2 to ensure that you're installing the correct version of TWRP!!
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot download
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.2.1-1:
Code:
[LIST]Update device tree for Oreo decrypt support
[*]Update prebuilt kernel to 2.16.400.1 Oreo (patched for working touch)
[*]Update device tree to be in line with other HTC devices and clean up[/LIST]
Older Device-specific versions:
Code:
[SIZE="4"][COLOR="Green"]3.2.1-0:[/COLOR][/SIZE]
[LIST]Initial official release[/LIST]
Click to expand...
Click to collapse
TWRP Official Changelog
Current version: 3.4.0:
Code:
[URL="https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html"]Changes[/URL]
Older versions:
Code:
[SIZE="4"][COLOR="Green"]3.2.1:[/COLOR][/SIZE]
[LIST]minui fixes (cryptomilk)
[*]Better android-8.0 compatibility in ROM trees (Dees_Troy)
[*]Fix missing library in android-8.0 (nkk71)
[*]Fix inconsistent SDCard naming (DevUt)
[*]Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)[/LIST]
Code:
[SIZE="4"][COLOR="Green"]3.2.0:[/COLOR][/SIZE]
[LIST]Allow restoring adb backups in the TWRP GUI (bigbiff)
[*]Fix gzip backup error in adb backups (bigbiff)
[*]Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
[*]Better support for installing Android 8.0 based zips due to legacy props (nkk71)
[*]Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
[*]Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
[*]Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
[*]v2 fstab support (Dees_Troy)
[*]Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
[*]Various other minor bugfixes and tweaks[/LIST]
[SIZE="4"][COLOR="Green"]3.1.1:[/COLOR][/SIZE]
[LIST]Backups will now include adopted storage keys (Dees_Troy)
[*]Fixed an adb restore issue (bigbiff)
[*]Fixed rebooting when no OS is present (Dees_Troy)
[*]Fixed line wrapping in the GUI terminal (_that)
[*]Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)[/LIST]
[SIZE="4"][COLOR="Green"]3.1.0:[/COLOR][/SIZE]
[LIST]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 [URL="https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9"]here[/URL] (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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.3:[/COLOR][/SIZE]
[LIST]Partial release to help support the release of the [URL="https://www.xda-developers.com/team-win-releases-their-first-official-twrp-app-in-the-play-store/"]Official TWRP app[/URL][/LIST]
[SIZE="4"][COLOR="Green"]3.0.2:[/COLOR][/SIZE]
[LIST]Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
[*]Add Greek translation to some builds.[/LIST]
[SIZE="4"][COLOR="Green"]3.0.1:[/COLOR][/SIZE]
[LIST]support new CM 13.0 pattern encryption (sultanqasim)
[*]fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
[*]libtar updated to latest upstream and fixes (jcadduono)
[*]fixes for loading custom themes (_that)
[*]TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
[*]translation updates - added Italian, Czech and Polish and significant updates to Dutch
[*]progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
[*]fix input box text display (Dees_Troy)
[*]reboot option after zip install complete (bigbiff)
[*]other mostly invisible bug fixes and improvements[/LIST]
[SIZE="4"][COLOR="Green"]3.0.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[U]Additional Notes[/U]
[LIST]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 updated 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![/LIST]
[SIZE="4"][COLOR="Green"]2.8.7.0:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[U]Additional Notes[/U]
[LIST]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 [url]https://jenkins.twrp.me[/url] and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at [url]https://gerrit.twrp.me[/url] to help us keep devices up to date and working.[/LIST]
Click to expand...
Click to collapse
Downloads
NOTE: Read the FAQ from Post #2 to ensure that you're installing the correct version of TWRP!!
Download
Latest Official versions
Unofficial builds
Sources
Device tree
Click to expand...
Click to collapse
FAQ - Post #2
Known Issues
Encrypted backups are broken - DO NOT USE THIS FEATURE!!
Reboot recovery option doesn't work - device will only reboot to system (needs custom-built kernel to fix)
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your issue is determined to be 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 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!
Click to expand...
Click to collapse
Additional Help/Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the HTC U Ultra
Contributors
Captain_Throwback, TARKZiM, Dees_Troy, bigbiff,_that
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.3.0-0
Stable Release Date: 2019-04-15
Created 2017-02-18
Last Updated 2019-04-17
XDA:DevDB Information
TWRP maintainer for the HTC U Ultra, ROM for the HTC U Ultra
Contributors
tarkzim
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2019-04-18
Last Updated 2020-06-26
Frequently Asked Questions
Frequently Asked Questions (FAQ)
1. Why is this device different than my previous HTC device?
With newer devices, HTC has moved to a block-based OTA system. This means that even mounting system as read-write (as TWRP typically does during startup checks) will nullify the device's ability to take an OTA. Any other changes to the system partition will also cause an OTA to fail (even if that check is removed from the OTA zip) due to "unexpected contents."
2. Which version of TWRP am I supposed to use?
The best version to use is the latest official (3.2.3-0) from twrp.me.
3. Why is there a "System" backup option and a "System Image" backup option now?
The "System" option is the standard tar backup. "System Image" is a dd backup of the entire system block device (/dev/block/bootdevice/by-name/system). The "System Image" option is only relevant if your system is unmodified. This allows you to make a fully stock backup that can be restored later to take an OTA.
NOTE: You only need to choose ONE of these options when making a backup!!
[*]NOTE 2: If you are using a FAT32-formatted card, a "System Image" backup may fail, due to the 4GB file limit on that format. For a successful System Image backup, internal storage or NTFS/exFAT-formatted external storage must be used (either SD card or USB-OTG)
4. How am I supposed to root?
Since this device has dm-verity enabled and forces encryption by default, root can only be achieved using a "systemless" root method. Magisk is the recommended root solution, as it is actively developed and up-to-date. It also allows devices to pass Google's SafetyNet API for working contactless payments. See the below thread for full details.
Magisk
5. How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled/broken on this device's ABOOT, so TWRP must be fastboot flashed over stock recovery. You can however, extract the stock recovery.img from the OTA firmware.zip when it's received and use that to install the OTA.
An alternate method to obtain a stock recovery is listed below, but it requires 2 devices (either owned by you, or help from someone else in the forum):
Someone fastboot flash twrp and immediately make a backup of boot and upload it to XDA.
Once the above is available, someone else download that boot.img to their device, and fastboot flash twrp to the BOOT partition of their device.
Once the above is done, reboot the device, which will bring up TWRP, and then backup stock RECOVERY in TWRP, and upload to XDA.
Then, from within TWRP, use the Image install feature in TWRP to flash the stock boot.img.
6. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system).
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
[*]NOTE 2: It is possible to install an OTA without using stock recovery (i.e. installing it with TWRP). TWRP will not flash the firmware.zip included in an OTA file. Please see here for a detailed description of the process.
Reboot to system, install OTA.
7. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
8. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
9. After I restored my Data backup and boot back to Android, I'm entering the correct PIN/password, but it's telling me the password is wrong. What happened, and how do I fix it?
It appears that sometimes after restoring a backup of Data where security was enabled (such as a PIN or password lock), the device does not recognize the correct password. There are two ways to avoid this issue:
Disable security in Android before making a backup of data.
After restoring Data, while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone.
Thanks it works
..
Can someone test whether this TWRP build boots?
«link removed»
That's from the official TWRP Jenkins. It won't decrypt currently, but I really just want to confirm it boots. Thanks!
EDIT: @nenebear confirmed. Official support should *hopefully* be coming soon!
Captain_Throwback said:
Can someone test whether this TWRP build boots?
http://build.twrp.me/twrp/twrp-3.0.3-0-oce.img
That's from the official TWRP Jenkins. It won't decrypt currently, but I really just want to confirm it boots. Thanks!
Click to expand...
Click to collapse
Version twrp-3.0.3-0-oce.img is can boot.
So combine this with Magisk and Supersu and you're good for root?
D_JWhite said:
So combine this with Magisk and Supersu and you're good for root?
Click to expand...
Click to collapse
Did you read the FAQ?
You only need one root method.
Captain_Throwback said:
Did you read the FAQ?
You only need one root method.
Click to expand...
Click to collapse
I prefer the magisk/supersu combo, hence asking about both. Thanks for the response!
D_JWhite said:
I prefer the magisk/supersu combo, hence asking about both. Thanks for the response!
Click to expand...
Click to collapse
If you just want root, you don't need Magisk. SuperSU roots just fine without Magisk, and Magisk has its own root now, which allows you to pass SafetyNet checks and use Android Pay. The combination you speak of doesn't allow that.
Captain_Throwback said:
If you just want root, you don't need Magisk. SuperSU roots just fine without Magisk, and Magisk has its own root now, which allows you to pass SafetyNet checks and use Android Pay. The combination you speak of doesn't allow that.
Click to expand...
Click to collapse
Good shout, cheers for the heads up.
It can boot up, but it has lot of issues.
The adb not works.
The terminal also not works.
The file manager very limited.
External SD not works.
Reboot to recovery also broken.
banmeifyouwant said:
It can boot up, but it has lot of issues.
The adb not works.
The terminal also not works.
The file manager very limited.
External SD not works.
Reboot to recovery also broken.
Click to expand...
Click to collapse
Which version are you talking about? Not the one posted in the OP, obviously...
Captain_Throwback said:
Which version are you talking about? Not the one posted in the OP, obviously...
Click to expand...
Click to collapse
Then you can see a different OP then me...
https://forum.xda-developers.com/devdb/project/dl/?id=23204
banmeifyouwant said:
Then you can see a different OP then me...
https://forum.xda-developers.com/devdb/project/dl/?id=23204
Click to expand...
Click to collapse
Yeah, the OP that says if you have a bug to report, how to do it...I don't see a log anywhere. Did I miss it?
Again, that recovery was tested and confirmed to be fully working. Perhaps you have a different variant or some other variable, but without a log, it's just speculation.
Captain_Throwback said:
Yeah, the OP that says if you have a bug to report, how to do it...I don't see a log anywhere. Did I miss it?
Again, that recovery was tested and confirmed to be fully working. Perhaps you have a different variant or some other variable, but without a log, it's just speculation.
Click to expand...
Click to collapse
How would you make logs if you have no adb and no terminal?
banmeifyouwant said:
How would you make logs if you have no adb and no terminal?
Click to expand...
Click to collapse
Advanced -> Copy Log, like it says in the OP, perhaps? You said SD card wasn't working but I assume internal storage does. Also, when you boot into system, the log should exist at /cache/recovery/last_log (if you're rooted).
Hi
Need to unlock bootloader first ?
scumpicule said:
Hi
Need to unlock bootloader first ?
Click to expand...
Click to collapse
Yes.
Can someone please confirm that this version of TWRP boots/works/functions properly? Thanks!
https://forum.xda-developers.com/devdb/project/dl/?id=23493
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 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 (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
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
this will VOID YOUR WARRANTY am not responsible for any damage!
Links
beta 5
https://drive.google.com/file/d/1xRiveHDEM5EcwU8tvU5mpHZDeKbPXIVO/view?usp=sharing
BUGS
otg not working
Current status: BETA
HIT THANK BUTTON IF I HELPED
changelog
Beta-1
* Initial release
Beta-2
*Roms installation failed fixed have some problems but still installing n roms
*some bug fixes
Beta3
*system image backup and flash supoort
*bug fixes
*roms installation fixed
*some new features
Beta 4
*recovery backup and flash issue fixed
*some bugs fixes
beta 5
* MTP fixed
* based on latest vegito kernel
* minor bug fixes
Bugs
*otg
Good job, can we get some screenshots?
FardeenTGO said:
Good job, can we get some screenshots?
Click to expand...
Click to collapse
Yes will upload for now am busy
Sent from my SM-G532F using Tapatalk
Screenshots added
new twrp version coming with system image flash and many new features
new twrp version added
HIT THANK BUTTON IF I HELPED
Does the partition sdcard option work?
FardeenTGO said:
Does the partition sdcard option work?
Click to expand...
Click to collapse
Sorry not tested wait while test for now am busy
Sent from my SM-G532F using Tapatalk
odin flash file added
note: this is not a update just a odin flash file
Waiting
For stable version
Radwan Selo said:
For stable version
Click to expand...
Click to collapse
ok any bug you founded
test recovery
usb otg fixed (if you mounted usb and disconnected to use usb again reboot to recovery again)
screenshots not working
some bug fixes
note : this is test recovery mean not stable not beta only for testing
What do u recommend for flashing los14.1 and root addons and gapps aroma "testing or beta" version?
Or back to 3.0.2-0 ?
Is ur recovery 3.1.0-0 or 3.1.1-0?
BTW thank you.?
Radwan Selo said:
What do u recommend for flashing los14.1 and root addons and gapps aroma "testing or beta" version?
Or back to 3.0.2-0
Is ur recovery 3.1.0-0 or 3.1.1-0?
BTW thank you.
Click to expand...
Click to collapse
first its beta version not stable
second typing mistake in file name and in thread name
its twrp 3.1.1-0
and if recovery dont flash roms so why twrp:laugh:
my twrp flashing every rom
only two bugs
mtp(use mount usb instead)
otg
Radwan Selo said:
What do u recommend for flashing los14.1 and root addons and gapps aroma "testing or beta" version?
Or back to 3.0.2-0
Is ur recovery 3.1.0-0 or 3.1.1-0?
BTW thank you.
Click to expand...
Click to collapse
well flash stable lineage 14.1 and pico gapps
Beta 4
Recovery flash and backup issue fixed
Some bugs fixes
Improvements
https://drive.google.com/file/d/0B2BVNSuLC6xFVFZoQjZzdWtRaHc/view?usp=drivesdk
Hit thanks button if I helped
beta 5 twrp
MTP fixed (need confirmation )
based on latest vegito kernel
minor bug fixes
PRESS THANKS IF I HELPED
Closed at OP request
Team Win Recovery Project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an official build for Asus Zenfone 4 Max Pro (will be official soon, have to deal with many things)
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
CHANGELOG for 3.1.1-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
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
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
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!
DOWNLOAD:
TWRP for Zenfone 4 Max
WHAT'S WORKING:
- Everything in TWRP
WHAT'S NOT WORKING:
- You tell! with the logs actually! No logs? That means "NO FIX" and you gonna be ignored in this thread
This device uses dm-verity and force-encrypt!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a patched kernel that has dm-verity and force-encrypt disabled in the fstab or install lazyflasher
Click to expand...
Click to collapse
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
f2fs file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup (fstab)
ADB root
Full SELinux support
Built with android 7.1 tree
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
TWRP 3.1.1-0 for Asus Zenfone 4 Max, Tool/Utility for the Asus ZenFone 4 Max
Contributors
aaaaaaziskurnia
Source Code: https://github.com/TeamWin/android_device_asus_X00I
Version Information
Status: Stable
Created 2017-10-06
Last Updated 2017-10-12
Note:
Don't do backup the modem and persist partitions for now. It will breaks your baseband and you must flash modem file from stock zip.
Awesome. Thank you. Just pick one up at Bestbuy
---------- Post added at 08:33 PM ---------- Previous post was at 08:32 PM ----------
Thanks. Awesome. Just pick this phoen up at Bestbuy yesterday
Got jenkins working and build success
Is this support fbe?
zainifame said:
Is this support fbe?
Click to expand...
Click to collapse
Didn't have any encryption by the way. I don't like any encryption, makes me slow
nice share..
how to get back to stock recovery @aaaaaaziskurnia?
hi, I've already installed twrp via fastboot, but why it keep asking me password for decripting phone (at twrp screen).. do you have any idea how to solve this?
komtek said:
hi, I've already installed twrp via fastboot, but why it keep asking me password for decripting phone (at twrp screen).. do you have any idea how to solve this?
Click to expand...
Click to collapse
Wipe the userdata and disable force encryption with lazyflasher
nice post
can this work on zenfone 4 max pro? (X00ID)
nhuhoang said:
can this work on zenfone 4 max pro? (X00ID)
Click to expand...
Click to collapse
x00id is the model number for kc554kl
the box my phone in had both numbers and yes it works
nhuhoang said:
can this work on zenfone 4 max pro? (X00ID)
Click to expand...
Click to collapse
Yes.
curious
If i flash SuperSu via twrp will i brick my phone?
Possible to save stock rom before doing this?
wonderd4 said:
Possible to save stock rom before doing this?
Click to expand...
Click to collapse
The only way to save stock rom is todo a Nandroid backup,to do the Nandroid backup you have to have Twrp. So good luck
Gotcha. Is it possible to install twrp without changing the stock rom?
Really want to flash this phone, just want to make sure I can have a backup in case things go south. I've flashed a couple phones before, but so far in between I usually forget the steps.
nhuhoang said:
If i flash SuperSu via twrp will i brick my phone?
Click to expand...
Click to collapse
If the supersu is systemlessly installed. Yes, It wouldn't break yours.
Use Magisk 14.3 instead of Supersu. Magisk 14.0 the modules wont load.
I should of installed the oct 18 ota update before flashing twrp and magisk. I am not sure how to do that now.
wonderd4 said:
Gotcha. Is it possible to install twrp without changing the stock rom?
Really want to flash this phone, just want to make sure I can have a backup in case things go south. I've flashed a couple phones before, but so far in between I usually forget the steps.
Click to expand...
Click to collapse
Any help on this greatly appreciated.
wonderd4 said:
Any help on this greatly appreciated.
Click to expand...
Click to collapse
You can do a backup as soon as you flash custom recovery and before you flash root.