Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-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
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:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Note, at this point, I haven't tried to mess around with kernel source. The recovery image barely fits with the stock kernel and dtb. The bootloader will refuse to flash the recovery via fastboot flash command so you have to boot the recovery then use dd to flash it. Instructions and download links are on our website:
Mirror
We only tested this on XT1095 but it will likely work on other models. Back up your stock recovery first and use fastboot boot to test the image on other models before flashing.
Touch may be a bit finicky especially when trying to swipe the sliders to confirm actions.
First to post very cool.
@Dees_Troy
But any ways the recovery flashes just fine but you cant do a back up every time I try it fails I get
E:unable to create folder: /data/media/0/twrp(errno=13)
E:Failed to make backup folder
Also swiping left to right to unlock or even start the backup doesn't really work you have to keep trying over and over
also im running the pure edition if that helps any
Thanks look forward to the next test
Victara doesn't yet come up under the device names.
ewalk4866 said:
First to post very cool.
@Dees_Troy
But any ways the recovery flashes just fine but you cant do a back up every time I try it fails I get
E:unable to create folder: /data/media/0/twrp(errno=13)
E:Failed to make backup folder
Also swiping left to right to unlock or even start the backup doesn't really work you have to keep trying over and over
also im running the pure edition if that helps any
Thanks look forward to the next test
Click to expand...
Click to collapse
i'm experiencing the same behavior; don't know if this makes a difference but i'm booting into TWRP via fastboot. @Dees_Troy thanks for your time/efforts creating this recovery image. :good:
Dees_Troy said:
Note, at this point, I haven't tried to mess around with kernel source. The recovery image barely fits with the stock kernel and dtb. The bootloader will refuse to flash the recovery via fastboot flash command so you have to boot the recovery then use dd to flash it. Instructions and download links are on our website:
Mirror
We only tested this on XT1095 but it will likely work on other models. Back up your stock recovery first and use fastboot boot to test the image on other models before flashing.
Click to expand...
Click to collapse
Was able to boot and flash via fastboot as well as dd it. On all occasions I'm also experiencing no functionality. Loads up fine but nothing works
ZeroAlphawolf said:
Victara doesn't yet come up under the device names.
Click to expand...
Click to collapse
I dont see it either. I assume something that will come eventually.
I tested a little bit on XT1095 using "fastboot boot openrecovery-twrp-2.8.0.0-victara.img" command (did not flashed it yet). Did not checked all menu items but looks like menus works fine.
The same error trying to make backup:
E:unable to create folder: /data/media/0/TWRP (errno=13)
E:Failed to make backup folder
Ability to run backups should be fixed now.
Version 2.8.0.1 works perfectly on XT1097 (Brazilian Version)
Thanks so much !!!
{
"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"
}
Thank you Dees_Troy,
Now that you've made it possible to back things up custom ROM's can't be to far away. And by the way the theming is working perfectly as well.
Interesting, so this morning i opened Twrp and found that Victara is now listed, which is great, and downloaded the recovery that way, which gave me 2.8.0.0 which is no problem. It installed it in active Android, and i opened up to it. Even managed to back up, with no problems, on 2.8.0.0, to an OTG drive, which let me tell you is amazing since i had such issues with that on Nexus 5. Thanks for your guys hard work, i always stick with Twrp.
I'm still having issues with slide not working on 2.8.0.1. I was able to back up in twrp app though
bacup directly to computer 2.8.0.1 Victara?
If I boot the openrecovery twrp image via fastboot, can I back up directly to my computer? I have the 16GB pure edition with only 3 GB remaining storage, prior to backup attempt, which is not enough to backup to the device memory. I tried selecting OTG, but couldn't select it. Perhaps I have to install the recovery to the device, plug in a usb otg, then attempt backup to otg?
Im trying to avoid installing the recovery image, because there is no factory system image available from Motorola yet.
I don't think you will be able to properly use any of twrp without installing it as the recovery itself, permission issues. But i believe there is a tool up already that has a copy of the customer recovery with it, if you needed to revert.
Thank you Dees_Troy for this amazing work. There is a bug i noticed and i dont know whats causing it.... After i booted (not flashed) the recovery, i made a full backup.. Then when i hooked the phone thru usb to copy my backup to the computer.. i noticed that the backup folder was empty in the windows explorer window... and then i came up with these findings thru (root explorer app): /storage/emulated/0/twrp (empty) but /data/media/0/twrp has the backup and thats why it isnt showing in windows...
So how do i get the backup show in /storage/emulated/0/twrp???
Thank u again....
The backup should be in data/ media/ 0
yay! thank you for your work and getting twrp to the new moto x!
Great ...waiting for millions roms now...
Just tested on my XT1097 Retail Brazil to flash Cerberus into the system.
I used "fastboot boot" command and it worked like a charm. Thank you for this
Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-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
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:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device specific page on our website with manual install instructions.
Download links for all current and past versions.
There's no lg g watch r (lenox) available in twrp app. I have latest version of the app. What's wrong?
Sent from HTC One M8 running Viper One
Vi553r said:
There's no lg g watch r (lenox) available in twrp app. I have latest version of the app. What's wrong?
Sent from HTC One M8 running Viper One
Click to expand...
Click to collapse
You will not be able to use the app to flash this because of the way fast boot works. Unless they make a custom watch app to dd flash it.
Sent from my A0001 using XDA Free mobile app
first things first, kudos to tonu42 for posting the unofficial twrp back in december.
sadly, the 2.8.3.0 build somehow screwed up adb for me - but now with the official 2.8.4.0 and that "powerbutton to go back" functionality...just swell
eeermm....I just flashed the twrp recovery and now when I restart, it always goes into recovery. I can't seem to get to boot.
is this normal?
b0gd4n said:
eeermm....I just flashed the twrp recovery and now when I restart, it always goes into recovery. I can't seem to get to boot.
is this normal?
Click to expand...
Click to collapse
No it isn't normal. I flashed yesterday and haven't experienced this problem, you did flash recovery right? How are you trying to reboot btw?
TimmyUK said:
No it isn't normal. I flashed yesterday and haven't experienced this problem, you did flash recovery right? How are you trying to reboot btw?
Click to expand...
Click to collapse
yeah, so I booted in fastboot and did fastboot flash recovery open....zip
twrp works nice, but when I choose reboot system it starts recovery again.
I am also getting mounting errors (unable to mount data and storage).
EDIT: also, in twrp the Internal Storage is appearing as 0MB
b0gd4n said:
yeah, so I booted in fastboot and did fastboot flash recovery open....zip
twrp works nice, but when I choose reboot system it starts recovery again.
I am also getting mounting errors (unable to mount data and storage).
EDIT: also, in twrp the Internal Storage is appearing as 0MB
Click to expand...
Click to collapse
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
TimmyUK said:
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
Click to expand...
Click to collapse
yeah, I'm gonna try following this thread http://forum.xda-developers.com/g-watch-r/development/emergency-guide-how-to-blank-regenerate-t2984678
I'll try another twrp now.
TimmyUK said:
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
Click to expand...
Click to collapse
ok...so flashing previous version of twrp did not work, same problem with unable to mount.
now, this is weird. I flashed stock recovery, and the watch started straight away...
b0gd4n said:
ok...so flashing previous version of twrp did not work, same problem with unable to mount.
now, this is weird. I flashed stock recovery, and the watch started straight away...
Click to expand...
Click to collapse
That is weird, you running 5.0.1?
TimmyUK said:
That is weird, you running 5.0.1?
Click to expand...
Click to collapse
yeah, 5.0.1.
ok, so after I flashed the stock recovery, and restarted the device normally, I adb sideloaded the 5.0.1 update mentioned in the thread posted earlier.
I then flashed the latest twrp again, and it now seems to be all nice and fine. I can boot to twrp, and the stuff gets mounted and I can reboot the system as well.
dunno what, but smth went wrong the first time I flashed.
all fine now.
Really strange, glad you got it sorted.
@b0gd4n
I've had the same problem at first TWRP Flash.
That's why i've posted this guide
Schmurtz1968 said:
@b0gd4n
I've had the same problem at first TWRP Flash.
That's why i've posted this guide
Click to expand...
Click to collapse
erm, which guide?
b0gd4n said:
erm, which guide?
Click to expand...
Click to collapse
The one you've pointed in this Thread
I did bootloader unlock for my watch using fastboot oem unlock
did fastboot flash recovery twrp.img
fastboot reboot.
I do have TWRP but when i press reboot->System it keeps booting to twrp.
I know to properly flash things on my devices but something here is wrong.
anyone got twrp working after flashing wear 5.02 ?
2.8.5.0 works for me on 5.0.2, Supersu FC's after rebooting and attempting installation. I think this is already a known problem. Just need to do a little more digging.
<edit> Updating to the latest (v2.46) has seemed to have resolved my issue
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.
How to install:
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.
Android One
Check 2nd post for download link
XDA:DevDB Information
[TWRP][OFFICIAL] TWRP for Android One First Gen devices, Tool/Utility for the OEM Cross Device Development
Contributors
Anik_khan
Version Information
Status: Stable
Created 2016-09-26
Last Updated 2017-05-26
Reserved
Download latest official build from here
Reserved
Nice work...Thanks for bringing Official TWRP support for our devices.
The unofficial build from your website works perfectly but it has some options missing like reboot bootloader, and partition sdcard.
Hope such thing isn't there in the upcoming official build:good::good::good:
Utkarsh_Tiwari said:
Nice work...Thanks for bringing Official TWRP support for our devices.
The unofficial build from your website works perfectly but it has some options missing like reboot bootloader, and partition sdcard.
Hope such thing isn't there in the upcoming official build:good::good::good:
Click to expand...
Click to collapse
Try the new 3.0.2-4 build
It is using the official device tree with all my patches.
Official builds started!
Okay everyone, patch has been merged, only some time before TWRP 3.0.2-1 shows up officially
Edit : It's up!
MSF Jarvis said:
Okay everyone, patch has been merged, only some time before TWRP 3.0.2-1 shows up officially
Edit : It's up!
Click to expand...
Click to collapse
Stuck on boot logo after installing the official build :/
ndzaky said:
Stuck on boot logo after installing the official build :/
Click to expand...
Click to collapse
Same with me. The official build still doesn't boot while the unofficial build provided by the OP works fine
Utkarsh_Tiwari said:
Same with me. The official build still doesn't boot while the unofficial build provided by the OP works fine
Click to expand...
Click to collapse
Okay, so that sucks like ****. I was using the SAME device tree and could provide booting builds, I'll post version 3.0.2-5 unofficially with a clean build and a clean sync from TeamWin github and let you guys know.
JuiceSSH rocks. Build coming in 20 minutes tops
MSF Jarvis said:
JuiceSSH rocks. Build coming in 20 minutes tops
Click to expand...
Click to collapse
Build is up.
MSF Jarvis said:
Okay, so that sucks like ****. I was using the SAME device tree and could provide booting builds, I'll post version 3.0.2-5 unofficially with a clean build and a clean sync from TeamWin github and let you guys know.
Click to expand...
Click to collapse
unfortunately version 3.0.2-5 unofficial also doesn't boot.
tried flashing via recovery and also via fastboot but nothing works.
Utkarsh_Tiwari said:
unfortunately version 3.0.2-5 unofficial also doesn't boot.
tried flashing via recovery and also via fastboot but nothing works.
Click to expand...
Click to collapse
I have located the issue. Thanks for all your feedback(Cracked screen on friend's A1, two-three weeks no device to test on). WIll add the 3.0.2-6 build and we'll see how it goes!
Anyone know the best version to flash roms and etc? It seems as if I can't flash aroma based roms with version 3.0+ and also need to know what version will allow the charging icon to be shown while charging while powered down. Seems I can't find the best twrp version...any ideas?
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Tmobilefan906 said:
Anyone know the best version to flash roms and etc? It seems as if I can't flash aroma based roms with version 3.0+ and also need to know what version will allow the charging icon to be shown while charging while powered down. Seems I can't find the best twrp version...any ideas?
Click to expand...
Click to collapse
I haven't gotten around trying any AROMA based ROMs yet, but AROMA source code is more than two years old, we simply cannot keep making changes specifically for an outdated piece of software.
MSF Jarvis said:
I haven't gotten around trying any AROMA based ROMs yet, but AROMA source code is more than two years old, we simply cannot keep making changes specifically for an outdated piece of software.
Click to expand...
Click to collapse
Ok, with that said, which roms are able to be flashed with twrp 2.8? And, do you recommend a custom kernel for running cm 12.1 or cm 13? Thanks.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Tmobilefan906 said:
Ok, with that said, which roms are able to be flashed with twrp 2.8? And, do you recommend a custom kernel for running cm 12.1 or cm 13? Thanks.
Click to expand...
Click to collapse
All ROMs should be flashable and running a custom kernel is purely your own choice.
MSF Jarvis said:
All ROMs should be flashable and running a custom kernel is purely your own choice.
Click to expand...
Click to collapse
Used lean kernel and twrp 2.8..now my led flickers while charging. Ugh. Lol.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Tmobilefan906 said:
Used lean kernel and twrp 2.8..now my led flickers while charging. Ugh. Lol.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Click to expand...
Click to collapse
You know this isn't the Samsung forums, right?
MSF Jarvis said:
You know this isn't the Samsung forums, right?
Click to expand...
Click to collapse
Yes. I am aware of that. I'm on a samsung device now, but am customizing this one at the moment.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
---------- Post added at 03:30 AM ---------- Previous post was at 03:29 AM ----------
MSF Jarvis said:
You know this isn't the Samsung forums, right?
Click to expand...
Click to collapse
Yes. I am aware of that. I'm on a samsung device now, but am customizing a device like yours at the moment.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
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.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.
DOWNLOADS
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:
TWRP for Infinix Hot 2
Credits
@MSF Jarvis
@Nonta72
@Dees_troy
@jcadduono
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[OFFICIAL][TWRP][d5110] TeamWin Touch Recovery, Tool/Utility for the Infinix HOT 2
Contributors
HostZero, MSF Jarvis, Dees_troy
Source Code: https://github.com/TeamWin/android_device_infinix_d5110
Version Information
Status: Stable
Created 2016-06-08
Last Updated 2016-06-08
Reserved
How to back to stock recovery ?
0utc0ntr0l said:
How to back to stock recovery ?
Click to expand...
Click to collapse
Download STOCK recovery and flash it using TWRP.
Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition
youssef0789 said:
Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition
Click to expand...
Click to collapse
Thankyou I will work on patch soon.
youssef0789 said:
Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition
Click to expand...
Click to collapse
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Code:
dd if=PATH_TO_DOWNLOADED_FILE of=/dev/block/platform/mtk-msdc.0/by-name/recovery
This might different on android one rom.
Since jemmini's TWRP is only can flash boot images
RendyAK said:
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Code:
dd if=PATH_TO_DOWNLOADED_FILE of=/dev/block/platform/mtk-msdc.0/by-name/recovery
This might different on android one rom.
Since jemmini's TWRP is only can flash boot images
Click to expand...
Click to collapse
Thank You So Much I'll Give It A Try But I Tried To Flash It With This Method
1 . Download the latest image file (.img) from the download link above and rename it to twrp.img, then copy it into the same folder as the factory ROM.
2 . Open up the MTK Flash Tool and use the scatter loading button to select the scatter file for this device.
3 . Uncheck all partition boxes except for the RECOVERY partition.
4 . Click on the folder/filename path for RECOVERY, then browse to and select the twrp.img file.
5 . Click on the [Download] button in the MTK Flash Tool.
6 . Power off your device completely.
7 . Plug the device into the computer and wait for it to flash. If it fails to flash the first time, you may have to unplug the phone and click [Download] again. Try this a few times. If it still doesn't work, try a different USB port and USB cable.
And When I Flashed It It Was Successfully Installed But There Was A Problem It Doesn't Show My SD Card
youssef0789 said:
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Thank You So Much I'll Give It A Try But I Tried To Flash It With This Method
1 . Download the latest image file (.img) from the download link above and rename it to twrp.img, then copy it into the same folder as the factory ROM.
2 . Open up the MTK Flash Tool and use the scatter loading button to select the scatter file for this device.
3 . Uncheck all partition boxes except for the RECOVERY partition.
4 . Click on the folder/filename path for RECOVERY, then browse to and select the twrp.img file.
5 . Click on the [Download] button in the MTK Flash Tool.
6 . Power off your device completely.
7 . Plug the device into the computer and wait for it to flash. If it fails to flash the first time, you may have to unplug the phone and click [Download] again. Try this a few times. If it still doesn't work, try a different USB port and USB cable.
And When I Flashed It It Was Successfully Installed But There Was A Problem It Doesn't Show My SD Card
Click to expand...
Click to collapse
Yeah, that is the bug of this twrp :3 @HostZero
RendyAK said:
Yeah, that is the bug of this twrp :3 @HostZero
Click to expand...
Click to collapse
Sir,
If your not aware I had been doing testing series for TWRP for d5110 successfully i have compiled and people were like no issues, so i went up publishing and Recovery Partition Flashing! I am trying to work on patch. if possible can you provide me the mmc* partition list. (ex: mmcb500...) I need those for boot and recovery, so i will make stable.
- HostZero
HostZero said:
Sir,
If your not aware I had been doing testing series for TWRP for d5110 successfully i have compiled and people were like no issues, so i went up publishing and Recovery Partition Flashing! I am trying to work on patch. if possible can you provide me the mmc* partition list. (ex: mmcb500...) I need those for boot and recovery, so i will make stable.
- HostZero
Click to expand...
Click to collapse
Here it is.
From /proc/emmc on Infinix 5.1 Rom.
The sdcard partition should be the same with android one rom.
RendyAK said:
Here it is.
From /proc/emmc on Infinix 5.1 Rom.
The sdcard partition should be the same with android one rom.
Click to expand...
Click to collapse
Please do this
adb devices
su (root using TWRP or any other way)
ls -al /dev/block/platform/mtk-msdc.0/by-name
Now copy the partition table and try to give me.
This will provide the mmc/infinix partition table.
- HostZero
HostZero said:
Please do this
adb devices
su (root using TWRP or any other way)
ls -al /dev/block/platform/mtk-msdc.0/by-name
Now copy the partition table and try to give me.
This will provide the mmc/infinix partition table.
- HostZero
Click to expand...
Click to collapse
This can be do with Terminal tho :3
RendyAK said:
This can be do with Terminal tho :3
Click to expand...
Click to collapse
Thankyou I will enter new table and most probably 3.0.2-1 or wait for 3.0.3-0.
- HostZero
I would like to report several issues:
1. NVRAM should've mounted as emmc, not ext4 (there's error in the log), also you should make secro as a sub partition of nvram. In my previous encounter with mediatek, if your secro partition corrupted or missing, your IMEI will still not detected (or detected partially).
2. There's no micro SD card mount point, despite the card is detected. Why?
I decompiled the official image, make necessary edit, and recompiled again. Tested fine on my brother's hot 2.
Download here if you want.
awaaas said:
I would like to report several issues:
1. NVRAM should've mounted as emmc, not ext4 (there's error in the log), also you should make secro as a sub partition of nvram. In my previous encounter with mediatek, if your secro partition corrupted or missing, your IMEI will still not detected (or detected partially).
2. There's no micro SD card mount point, despite the card is detected. Why?
I decompiled the official image, make necessary edit, and recompiled again. Tested fine on my brother's hot 2.
Download here if you want.
Click to expand...
Click to collapse
Fixed All of Them:
https://gerrit.twrp.me/1640
- HostZero
HostZero said:
Fixed All of Them:
https://gerrit.twrp.me/1640
- HostZero
Click to expand...
Click to collapse
Why would you create a fix when it's already fixed? I submitted that like half a month ago dude...
https://gerrit.twrp.me/#/c/1598/
https://gerrit.twrp.me/#/c/1597/
You approved my changes then on gerrit. Why did you do this?
awaaas said:
Why would you create a fix when it's already fixed? I submitted that like half a month ago dude...
https://gerrit.twrp.me/#/c/1598/
https://gerrit.twrp.me/#/c/1597/
You approved my changes then on gerrit. Why did you do this?
Click to expand...
Click to collapse
Bro! I don't remember if I approved. Anyways your changes were not pushed to git. My changes are pushed & I have even got
CPU Temperature for this.
Logo Backup and OEM backup and few other changes which would make twrp more stable.
HostZero said:
Bro! I don't remember if I approved. Anyways your changes were not pushed to git. My changes are pushed & I have even got
CPU Temperature for this.
Logo Backup and OEM backup and few other changes which would make twrp more stable.
Click to expand...
Click to collapse
You +1'd my changes on gerrit. And it IS pushed to github, you can check the commits of mine in TWRP device tree, it is pushed on June 19th.
https://github.com/TeamWin/android_device_infinix_d5110/commits/android-5.1
While it is good you added more partition to backup (note: IIRC, oem partition is not used by infinix) and cpu temp, I only complained about my changes duplicated by you, and that you claimed it.
Anyways, please don't make a duplicate fix in the future
CPU TEMPRATURE, Theres a Fix That i discovered.
and OEM partition is there for d5110 as per me.
I have duplicated on NVRAM etc all are new.
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.
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"
}
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.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
DOWNLOAD:
1) Download TWRP from here
2) Flash via CWM or TWRP recovery
3) Enjoy
BUGS:
- You tell me
If you have found a bug, please consider posting it here. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, If you see someone that's struggling, feel free to point it out to me.Thanks!
SOURCES:
https://github.com/CyanogenMod-ARMv6/kernel_bcm21553-common
https://github.com/CyanogenMod-ARMv6/android_device_samsung_cooperve
https://github.com/CyanogenMod-ARMv6/android_device_samsung_bcm21553-common
THANKS:
Dees_Troy.
TWRP team.
@sohamsen for testing
@psyke83 and BroadcomCM team for device tree and kernel source.
CHANGE LOG:
TWRP 3.0.2-1-b1 [2016-10-19]
-Fix ext-sdcard mount.
TWRP 3.0.2-1 [2016-10-16]
-Fix boot.img restore issue.
-Updated to latest changes.
TWRP 3.0.2-0 [2016-09-16]
- Updated to latest version.
TWRP 2.8.7.0 [2016-09-16]
- Initial release
Finally TWRP now we can bid good bye to our old CWM
many thanks
can you post it ob google storage pls?
thanks for great effort bro TWRP is the best
kihope12 said:
can you post it ob google storage pls?
Click to expand...
Click to collapse
I will uploud it soon.
omerdeniz99 said:
thanks for great effort bro TWRP is the best
Click to expand...
Click to collapse
Welcome man, hope you enjoy it.
How to Access Developer
Thank you very much ! Works great so far .
TWRP 3.0.2-1 [2016-10-16]
-Fix boot.img restore issue.
-Updated to latest changes.
thanks bro
goodjob but how disable navigation bar in 3.x like 2.8 i really need that
5830i
Will it work on 5830i?
Syed Kashif said:
Will it work on 5830i?
Click to expand...
Click to collapse
yes but only if you are running cm11
Good one, no lags. Like!
If this is still in active development, you might want to change the sources links - mohammad92 has moved these repos into CyanogenMod-ARMv6. This means that you (might) be violating the GPL, but really I don't care, although some may even try to ban you from the forums for a broken link...
hackintosh5 said:
If this is still in active development, you might want to change the sources links - mohammad92 has moved these repos into CyanogenMod-ARMv6. This means that you (might) be violating the GPL, but really I don't care, although some may even try to ban you from the forums for a broken link...
Click to expand...
Click to collapse
Will update links soon
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"
}
TWRP 3.2.3-0 Released
What's new in 3.2.3-0:
* 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
What's new in 3.2.1-1:
* 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)
What's new in 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-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.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.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.
DOWNLOAD:
Downloads:
Twrp-3.0.2-0
Twrp-3.1.1-0
Twrp-3.2.1-0
Twrp-3.2.3-0 (Latest)
#Improvements:
! Faster and Smoother than before
! Build from source
! supports Android 7.1.1
! MTP Supported
! Usb OTG supported
! Android 8.1.x Supported
Credits:
-TWRP Team
@Dees_Troy
@sevenmax
@Deepflex
@mohancm
BUGS:
Not yet found
Screen shots are Attached:
If you liked My developments Hit like :good:
Great to have you...............
lalit387 said:
Great to have you...............
Click to expand...
Click to collapse
hey, Thank you
Hope This Recovery may Feels good
It works great. Thanks for sharing
mohancm said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
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.
DOWNLOAD:
#link:
Twrp-3.0.2-0
#Improvements:
! Faster and Smoother than before
! Build from source
! supports Android 7.1.1
! MTP enabled
! Usb OTG supported
Creadits:
-TWRP Team
@Dees_Troy
@jonnyxda
@deepLex
@leskal
@mohancm
@[email protected]
-AMT
BUGS:
Not yet found
Screen shots are Attached:
If you liked My developments Hit like :good:
Click to expand...
Click to collapse
Thank you bro
No bugs no issues TWRP is working great also the theme zip is working fine and it is themable. Finally a committed Dev for our k4 is here thnx @mohancm
Sent from my Lenovo Vibe K4 Note using XDA Labs
OTG in recovery not working for me
HeltonMax said:
OTG in recovery not working for me
Click to expand...
Click to collapse
I will test it again and inform you.
mohancm said:
I will test it again and inform you.
Click to expand...
Click to collapse
ok
Can I install this version with another version of TWRP?
DELETED
smartdetodos said:
yes ...
twrp version by versão do SevenMaxs 3.0.2-3
https://goo.gl/H9CK5j (OP forum) GTranslate russian to english
or
trwp gold(en) XDA
https://goo.gl/stQfTZ by @ramisumi
Click to expand...
Click to collapse
If you guys, got any bugs with other recoveries.
Don't ask me anything in this tread
DELETED
smartdetodos said:
I do agree with you @mohancm ...
Just to enlightenment and help...
sorry .. my bad
like instructions (read post #01)... @gabriel_agra
installations with others twrp compilations are NOT DEV's responsability ... but It theirs builders ...
I'm using @mohancm 's twrp and It works fine ... no lags or issues
best regards folks
---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------
[/COLOR @mohancm Should Do I "edit" the external links?
Click to expand...
Click to collapse
No worries, any recovery can be used.
I should tell that I am not helping for other recoveries,if you come out with bugs.
Good luck
@mohancm I do really appreciate your work...
Google+ Lenovo A7010 Brazilian Community'users had installed a lot your ROMs and twrp... and ... lol ...
they are very anxious for new builds... nougat and lineage ...
I realize that xda is more technician and there a basic support ... different audiences and public ...
but if a Brazilian user report anything there I will quote here ... with your permission of course...
Best regards and "valeu!!!" ...
PS. "valeu" is a brazilian expression like ... "yeah ... thanks Its cool man!!!"
smartdetodos said:
@mohancm I do really appreciate your work...
Google+ Lenovo A7010 Brazilian Community'users had installed a lot your ROMs and twrp... and ... lol ...
they are very anxious for new builds... nougat and lineage ...
I realize that xda is more technician and there a basic support ... different audiences and public ...
but if a Brazilian user report anything there I will quote here ... with your permission of course...
Best regards and "valeu!!!" ...
PS. "valeu" is a brazilian expression like ... "yeah ... thanks Its cool man!!!"
Click to expand...
Click to collapse
Sure , I will be with them
mohancm said:
I will test it again and inform you.
Click to expand...
Click to collapse
HeltonMax said:
OTG in recovery not working for me
Click to expand...
Click to collapse
@mohancm
report issue: USB OTG option doesn't recognize my otg usb drives
usb drives: Sandisk Ultra Dual 64GB and 32GB too
format type: exFat and FAT32 formatted
smartdetodos said:
@mohancm
report issue: USB OTG option doesn't recognize my otg usb drives
usb drives: Sandisk Ultra Dual 64GB and 32GB too
format type: exFat and FAT32 formatted
Click to expand...
Click to collapse
Yeah,I checked it. I will fix it
what is the best procedure to permanent unlock bootloader and how to flash TWRP via SPFlash without unlocking bootloader in ADB because i always unlock my boot after the twrp gone when i going to stock rom after bricked
edarick said:
what is the best procedure to permanent unlock bootloader and how to flash TWRP via SPFlash without unlocking bootloader in ADB because i always unlock my boot after the twrp gone when i going to stock rom after bricked
Click to expand...
Click to collapse
No permanent method of unlocking bootloader, once you flashed stock rom via so flash tool.again you need to unlock bootloader with fastboot.
Many guides are Thier on XDA unlocking and installing twrp.
You can choose whichever you prefer
Good luck