Database Info

[RECOVERY][totoro/CM11] TWRP 3.0.2-1 touch recovery [2016-10-16]

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/android_kernel_samsung_bcm21553-common
https://github.com/CyanogenMod-ARMv6/android_device_samsung_totoro
https://github.com/CyanogenMod-ARMv6/android_device_samsung_bcm21553-common
TWRP-240x320-ldpi-theme 2.8.7.0
TWRP-240x320-ldpi-theme 3.0.2-0
THANKS:
Dees_Troy.
TWRP team.
@psyke83 and BroadcomCM team for device tree and kernel source.

CHANGE LOG:
TWRP 3.0.2-1 [2016-10-16]
-TWRP now less than 5MB you can flash over stock PIT.
-Some UI improvement.
-Updated to latest changes.
TWRP 3.0.2-0 [2016-04-05] Removed
-Updated to latest changes.
TWRP 3.0.1-0 [2016-04-04] Removed
-Updated to latest changes.
TWRP 3.0.0-0 [2016-02-16] Removed
-Updated to latest changes.
-New theme reworked for ldpi (240×320).
TWRP 2.8.7.0 [2015-06-23]
-Fixed backup.
TWRP 2.8.6.0 BETA04[2015-04-10]
-Fixed all ui overlays.
-MTP enabled.
-Some changes I forgot.
TWRP 2.8.6.0 BETA03[2015-04-08]
-New UI hard coded from scratch.
TWRP 2.8.6.0 BETA02[2015-04-03]
-Fix inverted color
TWRP 2.8.6.0 BETA01[2015-04-01]
-Initial release
TWRP 3.0.2-1 now less than 5MB you can flash over stock PIT. If you want flash old TWRP3 look below
COLOR="Red"]For TWRP 3.0.0-0 to 3.0.2-0 we need boot partition size more than 5 MB[/COLOR]
Increase boot partition to 9 MB
1) Download totoro_moded.pit from here
2) Open odin and choose PIT then tick Re-Partition
3) Click on Start.
4) Reboot to recovery and flash TWRP 3.0.x-0
To restore stock PIT
1) Flash any kernel/recovery less than 5 MB, (eg twrp 3.0.2-1)
2) Download totoro_0623.pit from here
3) Open odin and choose PIT then tick Re-Partition
4) Click on Start.
Thank to Mohamed.Anwar for his work on modified PIT see thread

For me

Thanks
Sent from my C2305 using Tapatalk

BETA02 is up
-Fix inverted color

finnaly twrp for our device

I think this is the most advanced project for this device now, i liked it. Better than CWM [emoji57]

New portrait ui instead of watch ui takes some hours of work (porting and resize)
Realocate many buttons and lines to fix overlays.
guess new build soon Edit: BETA03 is up

Hello,
How can I flash it if I don't have CWM or TWRP installed? Thanks.

fdelente said:
Hello,
How can I flash it if I don't have CWM or TWRP installed? Thanks.
Click to expand...
Click to collapse
This is only to be used with cm11 as it's built into the cm11 kernel
come back here once you are using cm11 as then you will have CWM as it's built into the kernel

Is this not works with cm7? If yes please give me link to twrp which I need pls
Sent from my GT-S5360 using Tapatalk 2

doctor-who said:
Is this not works with cm7? If yes please give me link to twrp which I need pls
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
this is for cm11 only.
maybe in future will compile one for cm7

1% battery bug

Islam2001 said:
1% battery bug
Click to expand...
Click to collapse
Device tree uses fake bettery status (I dont know why)
BTW BETA04 is up and battery status is OK
-Fixed all ui overlays.
-MTP now enabled (not tested)
-Some changes I fogot

mohammad.afaneh said:
Device tree uses fake bettery status (I dont know why)
BTW BETA04 is up and battery status is OK
-Fixed all ui overlays.
-MTP now enabled (not tested)
-Some changes I fogot
Click to expand...
Click to collapse
Please , can you make it with OC?

Workaround method to get backup wroking
- Download and extract the attatchment file "twrps.zip" you will got ".twrps" without quotes.
- Copy .twrps to /TWRP folder on sdcard replace or remove the old one.
- Dont restore default in twrp settings menu (you will repeat steps again)

TWRP 2.8.7.0 touch recovery is up test and enjoy.

TWRP 3.0.0-0 coming soon
just some ldpi fixes to the UI and I will upload new build.
PS: screen shot say its 2.8.7.0 dont worry I tested the theme on the pre 3.0.0-0 version commit.

mohammad.afaneh said:
TWRP 3.0.0-0 coming soon
just some ldpi fixes to the UI and I will upload new build.
PS: screen shot say its 2.8.7.0 dont worry I tested the theme on the pre 3.0.0-0 version commit.
Click to expand...
Click to collapse
Wooohooooo greaat bro, go on, eagerly waiting btw , I just accessed a twrp recovery which is totally material themed , on cm12.1 , is it possible to port? (expecting too much xD )

raisul2010.5396 said:
Wooohooooo greaat bro, go on, eagerly waiting btw , I just accessed a twrp recovery which is totally material themed , on cm12.1 , is it possible to port? (expecting too much xD )
Click to expand...
Click to collapse
Why to port if we can compile it from source. And there is no ldpi theme at all, I redone every thing from zero.
And we dont have cm12.1!

[OFFICIAL][TWRP][hennessy] TWRP for Redmi Note 3 - MTK

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:
You can find more information and download links on our website.
Xiaomi Redmi Note 3 MTK
TWRP Downloads
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][hennessy] TWRP for Redmi Note 3 - MTK, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
HostZero, jcadduono, Dees_troy, MSF Jarvis
Source Code: https://github.com/TeamWin/android_device_xiaomi_hennessy/tree/android-5.1
Version Information
Status: Stable
Created 2016-06-10
Last Updated 2016-06-10

Reserved
Device Tree Changes
OFFICIAL 3.0.2-1 Changelogs:
Code:
1. Fix NVRAM mounting issues
2. Added Sub Partition Secro
3. Added Logo Partition
4. Fixed CPU Temp Issues

I just install this TWRP in RN3MTK .
And nice .
It work less lag when scrolling .
---------------------------------------
I just try to wipe data . somehow it say "Failed to mount '/nvram' (invalid argument)" .

i second this, i get the same failed to mount nvram error
flashing works but cannot backup/write all the partitions

Not displayed temperature CPU.
> CPU: 0°

kmzway000 said:
I just install this TWRP in RN3MTK .
And nice .
It work less lag when scrolling .
---------------------------------------
I just try to wipe data . somehow it say "Failed to mount '/nvram' (invalid argument)" .
Click to expand...
Click to collapse
Thank you NVRAM will be fixed in next major update.

pashkovwins said:
Not displayed temperature CPU.
> CPU: 0°
Click to expand...
Click to collapse
CPU Temperature Cannot be fixed because on MTK Devices we cannot find CPU Temp path.

zip edition ?

'Faile to mount /nvram' When are next major update?.. by any chance, Is there a problem with using TWRP??! and I'm always appreciative of you!!! Have a nice day~~

moaa123 said:
'Faile to mount /nvram' When are next major update?.. by any chance, Is there a problem with using TWRP??! and I'm always appreciative of you!!! Have a nice day~~
Click to expand...
Click to collapse
en.miui.com/thread-208503-1-1.html
this 3.0.0 image doesn't have the same nvram error problem

moaa123 said:
'Faile to mount /nvram' When are next major update?.. by any chance, Is there a problem with using TWRP??! and I'm always appreciative of you!!! Have a nice day~~
Click to expand...
Click to collapse
https://gerrit.twrp.me/#/c/1603/
Submitted patch.
Changelogs:
Fix NVRAM Mount
OEM and secro added.

laviniu_c said:
en.miui.com/thread-208503-1-1.html
this 3.0.0 image doesn't have the same nvram error problem
Click to expand...
Click to collapse
Wait for 3.0.3-0
https://github.com/TeamWin/android_device_xiaomi_hennessey/tree/android-5.1

HostZero said:
Wait for 3.0.3-0
https://github.com/TeamWin/android_device_xiaomi_hennessey/tree/android-5.1
Click to expand...
Click to collapse
thank you! may i share this with en.miui.com/thread-293773-1-1.html ? i think mr feds64 either has a similar fix already or is working on one to get the tutorial for the unlock/twrp working properly for hennessy

laviniu_c said:
thank you! may i share this with en.miui.com/thread-293773-1-1.html ? i think mr feds64 either has a similar fix already or is working on one to get the tutorial for the unlock/twrp working properly for hennessy
Click to expand...
Click to collapse
Its fine. I have fixed NVRAM Issues and got few other backup partitions to be added. So I have fixed it, Once you will get TWRP 3.0.3-0 it will be all fixed twrp.

3.03 doesn't seem to have been built and uploaded yet?

decayed.cell said:
3.03 doesn't seem to have been built and uploaded yet?
Click to expand...
Click to collapse
Yeah Because its major release.
I am upstream Sources to MIUI 8 (6.6.30)
Then I will request for 3.0.2-1

Hi guys I have official 3.0.2 and efs backup don't work, on last release it's possible backup and restore efs partition? Thanks
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

the next release 3.0.3 fixes this, in the mean time, i think this is the one i have
edit: http://en.miui.com/forum.php?mod=viewthread&tid=208503
it sees all partitions and can back/restore them

It's possible flash an old 3.0.0 twrp form your link in recovery twrp 3.0.2 mode ?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

yep, that's how i did it too after i flashed 302 and lost the partitions
---------- Post added at 03:47 PM ---------- Previous post was at 03:47 PM ----------
p.s. always backup your data before any flash.

[RECOVERY][totoro/stock 2.3+] TWRP 3.0.3-0 touch recovery [2017-02-04]

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:
- SELinux contexts not supported in kernel
- Reboot to Recovery/Bootloader and Power Off
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:
Kernel based on GT-S5360-opensource-Update-4
TWRP-240x320-ldpi-theme 3.0.2-0
THANKS:
Dees_Troy.
TWRP team.

CHANGE LOG:
TWRP 3.0.3-0 [2017-02-04]
-Initial release

Works good
Found the bugs you listed
Rebooted to system but stucked on bootlogo
Yes it is bootloop
Can you bring me a stockrecovery.zip?
I am not so familiar with this device and i dont want to reflash and delete whole data
Thanks in advance

basem_ym said:
Works good
Found the bugs you listed
Rebooted to system but srucked on bootlogo
Yes it is bootloop
Can you bring me a stockrecovery.zip?
I am not so familiar with this device and i dont want to reflash and delete whole data
Thanks in advance
Click to expand...
Click to collapse
Flash any custom stock kernel, you can find them dev thread.

mohammad.afaneh said:
Flash any custom stock kernel, you can find them dev thread.
Click to expand...
Click to collapse
still working on cm9 project?

erriezzans said:
still working on cm9 project?
Click to expand...
Click to collapse
I think its a waste of time.
Maybe when I got a lot of free time.

I think I did something wrong
I installed your TWRP by stock recovery
I forgot about flashing temp cwm
I reflashed stock and reinstalled this recovery in the right way
Very good work thank you :good:
Just a small tip for who stucked in bootlogo:
Just grap a. Pit file and reflash stock firmware with [re-partition] checked in odin and then install this recovery by cwm
I found that installing this twrp by stock recovery will mess the data partition causing it to not mount in any way for some reason
Wish to see all the bugs fixed :victory:

twrp is nice
your twrp for the ldpi look nice, I love using twrp to install custom rom.

[RECOVERY] TWRP 3.2.1 UNOFFICIAL [touch-recovery][Coolpad Note 3 Lite]

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.1-0 is out now for Coolpad Note 3 Lite, Grab it right now.
What's new in 3.2.1-0:
* 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)
Changelogs for older versions
-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.
TWRP 3.1.1-0 Released
TWRP 3.1.1-0 is out now for all currently supported devices.
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
OLDER VERSION CHANGELOGS:
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:
Grab the latest build!
TWRP FOLDER
Note : Use 3.1.0 to flash Roms with old mount points ( mostly ported) and use 3.1.1 to flash Roms like MadOs, RR etc (Compiled ones)
New Improvements:
! Faster and Smoother than before
! Build from source
! supports Android 7.1.1
! MTP enabled
! Usb OTG supported(Fixed Now)
Credits:
-TWRP Team
@Dees_Troy
@kuberrocks96
-TeamZero
-mohancm
BUGS:
Not yet found
If you liked My developments Hit the LIKE/THANKS button :good:

Is it flashable for users using AOSP 7.1 ROM??

KritikXDA said:
Is it flashable for users using AOSP 7.1 ROM??
Click to expand...
Click to collapse
Yes it would work on all 3.18.xx kernel based roms

Its gone
I flashed TWRP in my phone yesterday using SP flash tool. It worked fine but today when rebooted again it booted into my stock recovery. What to do?

ojas.sinha said:
I flashed TWRP in my phone yesterday using SP flash tool. It worked fine but today when rebooted again it booted into my stock recovery. What to do?
Click to expand...
Click to collapse
Some faced this issue with old TWRP also , flash it via Flashify or TWRP itself again.

kuberrocks96 said:
Some faced this issue with old TWRP also , flash it via Flashify or TWRP itself again.
Click to expand...
Click to collapse
Now I don't have TWRP nor my phone is rooted.

Finally, a TWRP v3.1 for 3.18.19 kernel.
I ported this for my own device yesterday. Working good.
Thanks.

Great!
fr3akyphantom said:
Finally, a TWRP v3.1 for 3.18.19 kernel.
I ported this for my own device yesterday. Working good.
Thanks.
Click to expand...
Click to collapse
Good to hear that! Which Device you have?

Ported for my Primo RX5
kuberrocks96 said:
Good to hear that! Which Device you have?
Click to expand...
Click to collapse
I have ported this recovery to my device "Walton Primo RX5", not well-known, I know.
It is rebranded from "Gionee F103 Pro".
Thanks for the release. :good:

fr3akyphantom said:
I have ported this recovery to my device "Walton Primo RX5", not well-known, I know.
It is rebranded from "Gionee F103 Pro".
Thanks for the release. :good:
Click to expand...
Click to collapse
No worries.

Updated to 3.1.1

Decryption support (?)
kuberrocks96 said:
Updated to 3.1.1
Click to expand...
Click to collapse
Does it have Decryption support for previously encrypted Data partition (like v3.1.0 have)?

fr3akyphantom said:
Does it have Decryption support for previously encrypted Data partition (like v3.1.0 have)?
Click to expand...
Click to collapse
Yes it does have that, i am using different Mount Points here so that for our newer roms can be flashed easily with it, ported roms or older roms still require 3.1.0

support 8298-A01?

BlueNight1982BN said:
support 8298-A01?
Click to expand...
Click to collapse
No

MOD ACTION
THREAD CLOSED AT THE REQUEST OF OP.

[RECOVERY][UNOFFICIAL] 3.1.0-0 For Lenovo Vibe B [al732row]

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.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot in Fastboot Mode
3) Run this command
Code:
fastboot flash recovery twrp-3.1.0-0-al732row.img
4) done
OR:
Download For Lenovo Vibe B: HERE
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
TWRP For Lenovo Vibe B, Tool/Utility for all devices (see above for details)
Contributors
Carlos Arriaga
Source Code: https://github.com/Lenovo-VibeB
Version Information
Status: Stable
Created 2017-05-08
Last Updated 2017-05-07

Works!
And the LineageOS 13 and/or 14.1 ? When does it leave?

There was an attempt at LineageOS 14.1 by the very author in mid-May - but I haven't seen any new releases for 4 weeks now, and the existing ones check for product/device codes of al732row or A2016b30. I presume this is to save my A2016a40 (EMEA version) from a bad flash...

Hi, @Carlos Arriaga
TWRP 3.1.1-0 when will be available for Lenovo Vibe B (a2016a40) ?
Wich custom rom you recomand me fo this model of phone (a2016a40)?
Thank you.
Best regards,
Vlad

Hi @Carlos Arriaga
We have any issues with this rom(Lineage OS 14.1 for Vibe B (al732row) Nougat 7.1 ROM), not working camera, flashlight and wifi. Please fix this issues. When you'll release a new fixed version for this phone model (Lenovo Vibe B)? Thank you and i wait your reply. Please watch this video to see that issues
https://www.youtube.com/watch?v=vYRndBC_fJ8

Gg

Vlad Paul said:
Hi @Carlos Arriaga
We have any issues with this rom(Lineage OS 14.1 for Vibe B (al732row) Nougat 7.1 ROM), not working camera, flashlight and wifi. Please fix this issues. When you'll release a new fixed version for this phone model (Lenovo Vibe B)? Thank you and i wait your reply. Please watch this video to see that issues
https://www.youtube.com/watch?v=vYRndBC_fJ8
Click to expand...
Click to collapse
Fixed soon guy[emoji14]
Sent from my XT1526 using XDA-Developers Legacy app

Carlos Arriaga said:
Fixed soon guy[emoji14]
Sent from my XT1526 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thank you much.
Best Regards,
Vlad

New build TWRP
Changelog:
*Bump to 3.1.1
* Build with the last source LineageOS
* Last changes from OMNI-TWRP repo
* Add NVRAM Partition for backups.
Download: https://www.androidfilehost.com/?fid=745425885120742924
Sent from my 2014819 using XDA-Developers Legacy app

Carlos Arriaga said:
New build TWRP
Changelog:
*Bump to 3.1.1
* Build with the last source LineageOS
* Last changes from OMNI-TWRP repo
* Add NVRAM Partition for backups.
Download: https://www.androidfilehost.com/?fid=745425885120742924
Sent from my 2014819 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Installed succesfully the new twrp IMG from the old twrp. Instead of CPU temp up on left corner showing version number.
Thank you much. I wait and i hope you release CM 14.1 for a2016a40 version of Lenovo Vibe B. Thank you again.
Best Regards,
Vlad
{
"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"
}

@Carlos Arriaga
Please add pt-br language in next build the ROM Lineage 14.
Thank You for fixes in camera

Please update OP
Carlos Arriaga said:
New build TWRP
Download: https://www.androidfilehost.com/?fid=745425885120742924
Click to expand...
Click to collapse
Hi Carlos,
I'd like to ask you to update the 1st post of this thread if a new version is released - as the thread grows, announcements like this will be easily missed.
Of course, one still may parse https://www.androidfilehost.com/?w=files&flid=178517 (it's what I'm doing to stay in sync).
Cheers, S

Bugs version 3.1.1- 0
Last version of TWRP 3.1.1-0 isn't read sd card in ext4 format

Hi @carlosarriagacm, can you explain what https://www.androidfilehost.com/?fid=817550096634797042 is and why it's bit-wise identical to your (May 8) build? Thanks...

It's a pity that there's still no thread for custom ROMs for the Vibe B (did I miss something?).
On another thread, I have asked for assistance: If you have a A2016b30 running stock ROM, or any Vibe B running a custom ROM, please respond over there: https://forum.xda-developers.com/showpost.php?p=73995022&postcount=31 and clearly state which device you have (also in terms of single/dual SIM, this seems to be rather important)- thanks!

A2016A40?
Why no a2016a40 if there is an a2016a30 version? Aren't they identical? I have an a2016a40 (despite living in Brazil where the a30 should be sold) and wish to know if anyone here has sucessfully installed Carlos LineageOS version on this version of vibe b (a2016a30). Thanks.

Joao, there are reports that an a40 might lose one or both sim slots if flashed with the b30 firmware (there's no a30, btw).
Basically the two versions (for latam, and rest-of-world) seem to come with different basebands - and nobody yet has been able to identify the corresponding files in Carlos's rom (they may have been extracted from an older firmware version?)
The stock roms do indeed differ, also the build.prop files are different - a difference that isn't reflected by the custom rom.
Also someone reported a sound issue: https://www.lineageosroms.org/forums/topic/lineage-os-14-1-vibe-b-al732row-nougat-7-1-rom/ (second page).
In theory it's possible to go back to stock should something go wrong. In practice I don't have access to the device anymore...

steve8x8 said:
Joao, there are reports that an a40 might lose one or both sim slots if flashed with the b30 firmware (there's no a30, btw).
Basically the two versions (for latam, and rest-of-world) seem to come with different basebands - and nobody yet has been able to identify the corresponding files in Carlos's rom (they may have been extracted from an older firmware version?)
The stock roms do indeed differ, also the build.prop files are different - a difference that isn't reflected by the custom rom.
Also someone reported a sound issue: https://www.lineageosroms.org/forums/topic/lineage-os-14-1-vibe-b-al732row-nougat-7-1-rom/ (second page).
In theory it's possible to go back to stock should something go wrong. In practice I don't have access to the device anymore...
Click to expand...
Click to collapse
Still no any custom rom for our beloved a40 version? Im sick of stock rom 6.0. I wish to install Oreo on my phone but no chanse.

Vlad, if you feel lucky you may try and install Carlos's (or Eduardo's) rom over S235 - there's always a way back by FlashTooling stock whould something go wrong.
I'd advise to take all cards out before starting. Yes, SIM cards and memory card. TWRP 3.1.0-0 is supposed to accept the rom without changes. The usual wipes apply...
Good luck...

The ROM most recently built for the Vibe B seems to be ViperOS (by Eduardo Monteiro) but it's about 5 weeks old now. AFH fid=817906626617936324. No idea whether it would work with both LATAM and EMEA (ROW) devices (and which baseband files it uses)
Update: /system/etc/firmware/modem_1_lwg_n.img appears to be identical across this Viper ROM, and the latest LOS14.1 ROMs by CA and EM. I haven't been able to identify the stock ROM the file was taken from, but I fear it was a b30 one and the corresponding a40 stock would use a different one.
What (stock) baseband versions get reported in "About your phone" for both a40 and b30? Input, please...