Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
What's new in 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
What's new in 3.1.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
What’s new in 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.
What’s new in 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
changes included in version 3.0.0 are:
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - Languages that require large font files like Chinese & Japanese won't be available on most devices. Some languages may only be partially translated at this time. Translations are welcome over at 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
Many, many minor fixes and tweaks
DOWNLOAD:
TWRP Ghost Folder
How to install:
Download .img file
Restart your device in bootloader
flash via fastboot
fastboot flash recovery twrp-3.x.x-x-Ghost-UNOFFICIAL.img
enter into recovery or reboot
Enjoy
[older Downloads]
twrp-3.0.0-0-Ghost-UNOFFICIAL.img
twrp-3.0.0-0-Ghost-UNOFFICIAL-29022016-WithRF.img
twrp-3.0.0-0-Ghost-UNOFFICIAL-29022016-withoutRF.img
TWRP-3.0.0.0-RMRF-Ghost-UNOFFICIAL.img
TWRP-3.0.0.0-Ghost-UNOFFICIAL.img
TWPR-3.0.2-0-RMRF-GHOST-NIGHTLY-UNOFFICIAL.img <-- Fast format flash etc but you can't change format ejem EXT4 to F2FS
TWPR-3.0.2-0-GHOST-FIXED-NIGHTLY-UNOFFICIAL.img <-- slow format flash etc but you can change format ejem EXT4 to F2FS
TWRP-3.0.2-0-Ghost-UNOFFICIAL-20160517.img
TWRP-3.0.2-ghost-UNOFFICIAL-Nougat.img
TWRP-3.0.3-0-03062017-LPAS23.12-21.7-1-GHOST-UNOFFICIAL.img
CHANGELOG in second post
If you like my work, you can buy me a coffee with your donatives. All donations are appreciated.
XDA:DevDB Information
TeamWinRecovery, Tool/Utility for the Moto X
Contributors
TeamMex, TeamMEX
Version Information
Status: Testing
Created 2016-02-06
Last Updated 2017-05-20
Reserved
What’s new in 3.1.0-0: 2017-03-09
Removed unused flags
Fix mtp broken in 3.1
Fixed Graphical Glitch
Red Letters are made by TWRP read about VOLD and more in the TWRP changelog in OP
Moved to TWRP 3.1
What’s new in 3.0.3-0: 2017-02-13
Fixed issue with ext4 (Formatting in ext4 no longer takes a life.)
build ramdisk on LZMA
Builded DT on lz4c
Improve backup display names with emulated storage
Fix crash during check for TWRP app
Fill uid/gid for screenshots at compile time
Allow custom bootloader msg offset in block misc
more here...https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
What’s new in 3.0.2-0: 2016-05-17
Update spanish translation
Partition: Fix parsing of several twrp fstab flags
Fix decrypt of odd number length PIN on hardware crypto
Restore TW_SCREEN_BLANK_ON_BOOT functionality.
Languages: Update Japanese translation
Languages: Add font for Japanese
Improve greek translation
Rewrite TWRP fstab flag processing
Rewrite FS fstab flag processing
Remove char/string conversions in fstab processing
Wait to mount until after fstab processed
What’s new in 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.
What’s new in 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
3.0.0-0 28/03/2016
Merge code from upstream libtar + bug fixes
Don't add subpartitions to restore list
Change to dd for wiping crypto partitions
gui: fix font scaling for zip themes
Fix RELINK of toybox for twrp
partitions: Fix path based Find_Next_Storage
Remove busybox modprobe to fix slow performance for some devices
3.0.0-0 29/02/2016
Fix slow format && installing rom
Add back pixel format for TWRP 585
Supress secure erase
Fix no exfat-fuse rules
Fix up logd make file rules
Remove inexplicable checks for enabling/disabled UMS support
cryptfs: major overhaul and cleanup
Restore some old decrypt functionality
Patternpassword: update large grid password scheme
Fix adopted storage when andsec flag is present
Fix OEM compile
twrp: Add support for TW_SECONDARY_BRIGHTNESS_PATH
minuitwrp: fix and hopefully speed up fbdev screen flipping
Fix storage selection with adopted storage
partitions: Fix path based Find_Next_Storage
Remove busybox modprobe to fix slow performance for some devices
Fix verifier_test build
minuitwrp: retry opening fb0 if it failed
Unix file endings and remove execute permission
Reserved
I was Looking Forward This , Thanks Mate
Awesome.
Enviado de meu XT1058 usando Tapatalk
Flashify method works perfectly, no issues.
is it normal to get a "(bootloader) Variable not supported" message?
edit: trying to get into twrp it says 'no command' with a dead android
oh I seem to recall that I have to use mfastboot (Motorola's modified version of fastboot)?
edit: yep, using mfastboot worked! (I got the file here if anyone needs it)
x000x said:
is it normal to get a "(bootloader) Variable not supported" message?
edit: trying to get into twrp it says 'no command' with a dead android
oh I seem to recall that I have to use mfastboot (Motorola's modified version of fastboot)?
edit: yep, using mfastboot worked! (I got the file here if anyone needs it)
Click to expand...
Click to collapse
Yeap is normal
""(bootloader) Variable not supported" Anyway installs although that message.
cheers.
I'm getting stuck when I try to wipe the cache and/or cache dalvik... What's going on? In the previous twrp I don't get stuck.
abacate123 said:
I'm getting stuck when I try to wipe the cache and/or cache dalvik... What's going on? In the previous twrp I don't get stuck.
Click to expand...
Click to collapse
take log from advanced and copy log post the log in this thread
I tested Before publish and all works fine.
cheers
abacate123 said:
I'm getting stuck when I try to wipe the cache and/or cache dalvik... What's going on? In the previous twrp I don't get stuck.
Click to expand...
Click to collapse
Happens when wiping system, too.
Just hangs forever on make_ext4fs, need to reboot to get back to a usable recovery.
Now my /system and /cache can't be mounted or wiped even in fastboot...
Backups don't seem to work right either, considering apparently a backup I made under this TWRP build just disappeared...
Lyokacanthrope said:
Happens when wiping system, too.
Just hangs forever on make_ext4fs, need to reboot to get back to a usable recovery.
Now my /system and /cache can't be mounted or wiped even in fastboot...
Backups don't seem to work right either, considering apparently a backup I made under this TWRP build just disappeared...
Click to expand...
Click to collapse
"Backups don't seem to work right either, considering apparently a backup I made under this TWRP build just disappeared..."
It seems that nobody here reads something warns that make backup of everything.
I builded this using Marshmallow branch for Moto X and it maybe cause to the disappearance of their contents in SD, and created in folder called 0 or legacy, I warned in OP, now I maded Test's about all, Creating backups, restoring backups, wiping partitions etc and everything works fine
EDIT:
If anyone have problems with System go to mount's and mount system partition.
In next release I add Forced Not unmount System.
cheers
I did actually read, and I did have backups of my backups, for what it's worth. I was well aware that it may be unstable.
I was just trying to let you know what happened.
I'd get a log, if I could, but seeing as I have to restart the phone and I can't get adb to work in recovery, I can't help in those regards.
gran trabajo,
congratulations
Wipe cache and dalvik/art cache takes a life ?
Somebody else?
Enviado desde mi Moto X mediante Tapatalk
looks awesome, but i have the same problem - stuck's in wipe cache...
I flashed it via TWRP 2.8.7
CsR0501 said:
Wipe cache and dalvik/art cache takes a life
Somebody else?
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
rorschach181 said:
looks awesome, but i have the same problem - stuck's in wipe cache...
I flashed it via TWRP 2.8.7
Click to expand...
Click to collapse
I don't have that problem, try to format cache in to F2FS and then wipe, if have the same issue take a recovery log and post in this thread
cheers.
TeamMex said:
I don't have that problem, try to format cache in to F2FS and then wipe, if have the same issue take a recovery log and post in this thread
cheers.
Click to expand...
Click to collapse
When I format cache in to F2FS and wipe I enter in a bootloop... Rom RR :/
Enviado desde mi Moto X mediante Tapatalk
CsR0501 said:
When I format cache in to F2FS and wipe I enter in a bootloop... Rom RR :/
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
no no, Format to F2FS then EXT4, my rom(kernel) is the only one supporting F2FS cache by default.
CsR0501 said:
When I format cache in to F2FS and wipe I enter in a bootloop... Rom RR :/
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
TeamMex said:
no no, Format to F2FS then EXT4, my rom(kernel) is the only one supporting F2FS cache by default.
Click to expand...
Click to collapse
Or you have to get this fix: http://forum.xda-developers.com/moto-x/development/mod-f2fs-ghost-t3154581
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.
{
"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.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
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!
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 website.
Xiaomi Redmi 3
TWRP Downloads
Contributors
Anik_khan
Reserved
How to use F2FS
Download TWRP from the link above
Grab a rom that supports F2FS
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache partition
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, feel free to ask me.
NOTE:
Xiaomi added dm-verity check on Bootloader. You will be need to disable it for modifying system. You can do it simply via adb.
Connect phone with adb (you need to execute this command with root)
Code:
adb root
Code:
adb disable-verity
That's it
Enjoy
Nice, great work Anik!
Birthday gift for yourself
Its only for unlock bootloader ?thanls
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
cranio84 said:
Its only for unlock bootloader ?thanls
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
It says on the first post in red letters that bootlocker needs to be unlocked.
Poslano sa mog Redmi 3 koristeći Tapatalk
Thank you! I will flash this once I have unlocked my BL.
@Anik_khan can i execute flash the root only via adb? Or any method how to root dev rom locked bootloader?
After flashing (which went pretty smooth)....the recovery page only shows a mobile screen with usb plugged in, no stock or twrp!!! am I doing something wrong here?
raad.sobhan said:
After flashing (which went pretty smooth)....the recovery page only shows a mobile screen with usb plugged in, no stock or twrp!!! am I doing something wrong here?
Click to expand...
Click to collapse
Is your bootloader unlock before flashing twrp recovery?
v0ne said:
Is your bootloader unlock before flashing twrp recovery?
Click to expand...
Click to collapse
ya, this was the first thing I did after unlocking.
raad.sobhan said:
ya, this was the first thing I did after unlocking.
Click to expand...
Click to collapse
I too have that problem. Could it be that I went back to the latest rom available (V7.2.4.0.LHP) ?
I unlocked the bootloader from dev rom.
Switched back to V7.2.4.0.LHP, but checked for bootloader : still unlocked.
Then i proceeded to fastboot flash the recovery, everything went fine with the regular fastboot message confirming transfert and write, but when I reboot into recovery mode, it shows the Xiaomi recovery picture like @raad.sobhan described.
I'll try in few minutes with dev rom to see if it changes anything.
Ok so, I tried with dev rom miui_HM3_6.3.17 and same result.
Here's a pic of the recovery once the following commands were issued:
Code:
X:\XX\XX>fastboot flash recovery TWRP_3.0.0-0-ido.img
target reported max download size of 268435456 bytes
sending 'recovery' (13496 KB)...
OKAY [ 0.438s]
writing 'recovery'...
OKAY [ 0.500s]
finished. total time: 0.938s
X:\XX\XX>fastboot reboot
rebooting...
finished. total time: 0.000s
@Anik_khan, if there's any logs I could grab to sort the problem out, let me know.
you need
fastboot.exe flash recovery TWRP_3.0.0-0-ido.img
and then
fastboot.exe boot TWRP_3.0.0-0-ido.img
the first boot from file actually make this recovery flash permanent
Oh thanks ! I feel dumb for not trying to boot directly the img file.
mouhii said:
Oh thanks ! I feel dumb for not trying to boot directly the img file.
Click to expand...
Click to collapse
Also, make sure to execute commands from the second post! They will terminate any possible recovery replacement!
usblaidas said:
Also, make sure to execute commands from the second post! They will terminate any possible recovery replacement!
Click to expand...
Click to collapse
Yeah, that's what I was planning to do but once under the recovery
mouhii said:
Yeah, that's what I was planning to do but once under the recovery
Click to expand...
Click to collapse
you have to execute them before even flashing recovery
usblaidas said:
you have to execute them before even flashing recovery
Click to expand...
Click to collapse
Oh I didn't realise that but it makes sense.
However when I use adb root under android, I have "adbd cannot run as root in production builds". Do I need a modified boot.img for that or am I missing something ?
mouhii said:
Oh I didn't realise that but it makes sense.
However when I use adb root under android, I have "adbd cannot run as root in production builds". Do I need a modified boot.img for that or am I missing something ?
Click to expand...
Click to collapse
Make sure to go to Security app, Permissions, and make sure to enable root
{
"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
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.
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point.
We also have a large support community with many people who are willing to answer questions
and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G.
After our work on the EVO 4G we wanted to work on a project
that would work on more devices than just the EVO 4G and we settled on working on a recovery.
Today TWRP is the leading custom recovery for Android phones.
This is a continuation of @dadi11's project.
compiled with latest android-9.0 source, combined TeamWin and omnirom
updated and modified device trees
support for g3ds variant
Nebula Kernel (-Nebula_Rev12.5-Final_MM)
AROMA support
useful TWRP functions enabled (logd/logcat...)
new extensions supported (usb-otg, exfat, ntfs-3g...)
parted binary added
thermal-engine with config
optional red theme
backup of /recovery
TWRP app removed
nano binary
You might want to have your ROM rooted before flashing, just in case something goes wrong.
To install TWRP, you need to be rooted, of course.
first method (best and recommended)
boot to recovery
click install and select Install Image on the right bottom corner
flash latest recovery image
second method
place latest recovery image on the internal storage
open terminal and type following
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/<recovery image name>.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
If you want to contact me, head for my telegram.
I also really recommend joining telegram: G3 development channel for more information about my projects!
The thread has been designed by me, please don't copy it.
There are always two files, a normal and a -themed one.
If you want red-colored overlay, download the -themed one. Otherwise, you get blue.
MEGA (recommended)
AndroidFileHost
Rooting your phone by Linus Tech Tips
Root: Magisk
3__HacerPermisivo.zip - use this to switch your kernel selinux to permissive
bootimage_adb_unsecure by @AdrianDC - for debugging
Mr_Bump.zip by @dadi11 - flash this when you occur Secure booting error (boot certification verify)
If you want to report an issue, please use the issue tracker providing your variant and the most information you can.
@ppajdek for help with kernel and stuff
@dadi11 for releasing the sources
@sleeplessnerd for decryption
@osm0sis for nano binary
@Eliminater74
@walter79
github.com/omnirom
github.com/minimal-manifest-twrp
github.com/itsHardStyl3r
gitlab.com/HardStyl3r
device and kernel sources
local_manifests
Important: information about open sources from HardStyl3r
XDA:DevDB Information
TeamWin Recovery Project (TWRP) 3.3.1-0 for LG G3, Tool/Utility for the LG G3
Contributors
HardStyl3r
Version Information
Status: Stable
Created 2018-07-07
Last Updated 2020-03-17
3.3.1, 17.03.2020
G3
Code:
* Updated Nebula Kernel to 12.5-Final version
* New, compressed red theme (by hardStyl3r)
* Encryption highly unrecommended on Android 10 yet!
TWRP
Code:
* otautil: Android.bp libziparchive added
* updater: removed unused variables in installer
* updater: duplicate function definition
* minuitwrp: Include some missing variables related to screen blanking
* language: turkish update
* Fix 'system/etc/ld.config.txt' not found error
* crypto: fde: decrypt master key first
* Fix ORS backup and restore for system-as-root
* crypto: add more missing newlines
* openrecoveryscript: do not skip decryption even if using block.map
* partitionmanager: add /etc to Local_Path
* Move decryption error from logerror to loginfo
* bootable: read all asserts in case there are more than one.
* Prevent errors caused by /data/per_boot/
* crypto: add some missing newlines
* Removing fake error: E: recv error on uevent
* Complete overhaul of Dutch translation:
* recovery: wipe bootloader message from index 0 when using custom offsets
* android-5.1: use char constructor for default on c++ streams
* recovery: Move bldrmsg offset symbols to bootloader_message.cpp
* /sbin should come first in the linker search path.
* Encryption: try wrapped key also for device without metadata support
* ldconfig: add /sbin to search.paths
* cache: Fix typo in twrp-functions.cpp for A/B devices
* Add ld.config.txt for Android 8.x+ trees
* Fix typo in comment
* Update Portuguese (Portugal) translation
3.3.1, 21.06.2019
G3
Code:
* d851: Fix kernel, apply mkbootimg and bump the images
TWRP
Code:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
3.3.0, 17.04.2019
Code:
* 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 (Dees_Troy with thanks to topjohnwu of course)
3.2.3-0
G3
Code:
* added nano binary (https://www.nano-editor.org/), thanks to @osm0sis
* complete rebase
* cleaned flags
* fstab update: fix modem backup and restore
TWRP
Code:
* android-9.0 support
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
3.2.2-0
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
3.2.1-0
Code:
* 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)
3.2.0-0
Code:
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
3.1.1-0
Code:
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
3.1.0-0
Code:
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
Reserved 2
Reserved 3
Nice job
Great Work ???
Good job
Thank you for keeping things updated
Just a heads up to everyone, LS990 versions are not booting. The following error comes up:
[4540] Fastboot mode started
D855 themed version working good till now (made a backup and flashed a kernel)
luciferin said:
Thank you for keeping things updated
Just a heads up to everyone, LS990 versions are not booting. The following error comes up:
[4540] Fastboot mode started
Click to expand...
Click to collapse
that's a lot for feedback, I made a mistake while building vs985 and ls990. they were using d855 kernel.
I am building fixed versions and gonna upload them in 10 minutes
//edit done!
HardStyl3r said:
that's a lot for feedback, I made a mistake while building vs985 and ls990. they were using d855 kernel.
I am building fixed versions and gonna upload them in 10 minutes
//edit done!
Click to expand...
Click to collapse
New upload is working great here! Nicely done, and thank you for the good work.
Thank You so much 4 this... Greatly appreciated about 2 flash this badboy right now :good:
Great job!
@HardStyl3r, thank you for this. The lack of thermal engine support from the official version was holding me back from upgrading from TWRP v3.0.3 built by @dadi11 because these phones heat up like hell when flashing something. Now thanks to you, I'm able to upgrade to the newest and the latest and the greatest... :good:
---------- Post added at 06:43 PM ---------- Previous post was at 06:23 PM ----------
For the people that do not like the red themed version of the recovery, since @HardStyl3r was kind enough to build both themed and un-themed versions, you can flash the un-themed version and use a theme from here courtesy of @z31s1g. I can confirm as have other users that the v3.2.1 TWRP theme works just fine with TWRP v3.2.2!
After installing the custom theme, if you cannot see CPU temperature in the top left corner, you can get it back by following the instructions provided here. I just tried it and it works!
brilliant work ! but i don't know if it's just me that i think the older build(3.0.2.0) was snappier than this one, i'm on D850 btw
cydia_Droid said:
brilliant work ! but i don't know if it's just me that i think the older build(3.0.2.0) was snappier than this one, i'm on D850 btw
Click to expand...
Click to collapse
the older builds feels snappier on d855, but only just a little bit. I used the same sources as dadi11 did, so I guess it's related to TWRP
Feedback F400 variant (problems)
1. In the process of backing up (it shows 3 times "Unable to locate partition by backup name": radio, rpm ,tz) (First Screenshot)
2. Still during the backup process, it got stuck in 16 MB. I waited for more than 10min, and still nothing happened. (Second Screenshot)
3. After that, i decided to cancel the backup process, and then it showed " createTarFork( ) process ended with ERROR:255 " (Third Screenshot)
4. Afterwards, i tried to flash back dadi11 TWRP.img, but it could not (Failed).
5. And then, i decided to restore only the "recovery" partition from a nandroid backup which i had previously backed up using dadi11 TWRP. This also showed an error.
6. Tried rebooting to recovery but couldn't anymore (a screen appeared written "750 fastboot mode") (So at that moment, i knew i had lost recovey)
7. Lastly, i removed battery and inserted it again.
Booted into system and installed Rashr, and then i was able to flash dadi11 TWRP.
8. Phewww, what a history
Continuation of last post
With dadi11 TWRP, when i mark all partitions to backup, the TWRP itself says
" Total number of partitions to backup: 10 " during the backup process.
It does backup of the following: boot, cache, data, efs1, ef2, radio, recovery, rpm, system, tz.
Your recovery (3.2.2-0) says : "Total number of partitions to backup: 8"
I don't know what's missing.
I am puting here the photos of dadi11 recovery, just so you can see.
SDA93 said:
1. In the process of backing up (it shows 3 times "Unable to locate partition by backup name": radio, rpm ,tz) (First Screenshot)
2. Still during the backup process, it got stuck in 16 MB. I waited for more than 10min, and still nothing happened. (Second Screenshot)
3. After that, i decided to cancel the backup process, and then it showed " createTarFork( ) process ended with ERROR:255 " (Third Screenshot)
4. Afterwards, i tried to flash back dadi11 TWRP.img, but it could not (Failed).
5. And then, i decided to restore only the "recovery" partition from a nandroid backup which i had previously backed up using dadi11 TWRP. This also showed an error.
6. Tried rebooting to recovery but couldn't anymore (a screen appeared written "750 fastboot mode") (So at that moment, i knew i had lost recovey)
7. Lastly, i removed battery and inserted it again.
Booted into system and installed Rashr, and then i was able to flash dadi11 TWRP.
8. Phewww, what a history
Click to expand...
Click to collapse
I had an issue restoring data. Error 5. I forget what else it said since I had an official copy of 3.2.2 and flashed it, rebooted back into recovery, and was able to restore the data partition with no issue
@SDA93
I am speechless. I can't understand the issue nor reproduce it. I tested backup, restore, flash, AROMA and terminal before releasing on my d855 and everything went really snappy. Have you managed to get out of it?
HardStyl3r said:
@SDA93
I am speechless. I can't understand the issue nor reproduce it. I tested backup, restore, flash, AROMA and terminal before releasing on my d855 and everything went really snappy. Have you managed to get out of it?
Click to expand...
Click to collapse
Yes.
As said in the post, i installed Rashr and used it to flash again dadi11's TWRP.
I also don't know the cause of the problem. Probably the F400 recovery has a problem that the d855 doesn't.
I also checked the md5 hash to avoid corrupted download, but it was correct.
---------- Post added at 04:15 PM ---------- Previous post was at 04:14 PM ----------
jdmst77 said:
I had an issue restoring data. Error 5. I forget what else it said since I had an official copy of 3.2.2 and flashed it, rebooted back into recovery, and was able to restore the data partition with no issue
Click to expand...
Click to collapse
Are you using F400 variant?