Related
Cannibal Open Touch 3.0 Alpha 10
Disclaimer:
While we try to test our work as much as possible, it is always a possibility that something could go wrong and screw up your phone. We are not responsible for any damage that is done to your device, either directly or indirectly, as a result of using Cannibal Open Touch or any other Project Open Cannibal projects. Any damage done to your device is your responsibility and your responsibility only. We do this for fun, and we simply like to share our work.
What is Cannibal Open Touch?
Cannibal Open Touch is a custom recovery (like ClockworkMod or TWRP), created purely out of love for the platform and the desire to contribute something cool to the community. The name embodies everything that Cannibal Open Touch is. We take what we believe are the best features of popular recoveries like TWRP and ClockworkMod and, well, cannibalize them along with rolling out our own features.
Features:
Full Touch UI
Complete theme support, including app for management of themes (we'll get to that in a sec)
On-device backup and restore
Backup and restore via ADB
Much much more planned!
Bugs:
During installation, the standard Android installing icon gets displayed instead of the custom dialog box.
If you find a bug, please do not report it here! Instead, report it in the GitHub repository!
Screenshots
See the Screenshots tab above. (Or click me if you're using Tapatalk!)
Nandroid has been replaced!
Nandroid is in fact gone, and has been replaced with a much more robust backup solution. Backups can now be made either with ADB (the recommended way) or via the new Backup and Restore item in the main menu. Backups made via the built-in menu can be copied to a PC and restored via ADB, and backups made via ADB can likewise be copied to your device and restored using the Backup and Restore menu.
Code:
adb backup -f mybackupfilename.ab boot system data cache
You can also restore said backup by using adb, like so:
Code:
adb restore mybackupfilename.ab
Downloads:
Cannibal Open Touch flo builds (latest: CannibalOpenTouch-2.99.10_flo.img)
How to install:
Download the latest Alpha image
Reboot to bootloader:
Code:
adb reboot bootloader
Flash the image with fastboot
Code:
fastboot flash recovery /path/to/downloaded/recovery.img
Boot into recovery mode
Alternatively, you may boot the image instead of flashing it:
Code:
fastboot boot /path/to/downloaded/recovery.img
Changelog:
3.0 Alpha 10 (2.99.10)
Themes are now stored in /cache/cot/themes to fix an issue introduced with FDE.
3.0 Alpha 9 (2.99.9)
Real menu scrolling! (but volume keys still work)
All backup/restore operations now verify that you want to take action
Resized UI to be more usable on all device resolutions
Themes can now display a battery charge indicator (depends on individual theme settings)
3.0 Alpha 8 (2.99.8) (not released)
Not released
3.0 Alpha 7 (2.99.7)
On-device backup and restore
3.0 Alpha 6 (2.99.6)
Complete theme support
Recovery settings (Theme settings and Unsigned ZIP flashing)
The preceding list is not 100% complete. See the project source code page for the full commit list.
Cannibal Open Touch themes app:
We are currently seeking Alpha testers for an app that will let users download and choose themes without rebooting to recovery mode. Currently there are 20 slots open. If you wish to join please PM me. The only requirement is you must have a Google+ account and are willing to submit proper bug reports, should any arise.
Cannibal Open Touch Themes:
You can now make your own themes for Cannibal Open Touch! See the example themes (it's pretty self-explanatory). Themes must be installed in /sdcard/cot/themes/theme_name (or /data/media/cot/themes/theme_name) in order to work. Please feel free to submit pull requests to have your custom themes added to the theme repository. They will also be packaged and made available to download via the Cannibal Themes app (mentioned above)!
Contribute to Project Open Cannibal
If you like our work and want to see more, consider a donation to the project!
Project Open Cannibal gerrit: http://review.projectopencannibal.org
Credits:
tdm, for the superb touch code (and lots more)
sblood86, for joining the project and leading the charge to greatness
thenameisnigel, for picking up our webhosting while I was gone
anyone else who has ever contributed to any Android-related project
XDA:DevDB Information
Cannibal Open Touch, Tool/Utility for the Nexus 7 (2013)
Contributors
drewwalton19216801, Sblood86, thenameisnigel, tdm, CyanogenMod, Koush and many others
Source Code: https://github.com/ProjectOpenCannibal/android_bootable_recovery-cm
Version Information
Status: Alpha
Created 2014-10-26
Last Updated 2014-12-03
Nice work!
looks promising keep up the good work.
Awesome stuff great work much appreciated
Cannibal Open Touch 3.0 Alpha 10
Disclaimer:
While we try to test our work as much as possible, it is always a possibility that something could go wrong and screw up your phone. We are not responsible for any damage that is done to your device, either directly or indirectly, as a result of using Cannibal Open Touch or any other Project Open Cannibal projects. Any damage done to your device is your responsibility and your responsibility only. We do this for fun, and we simply like to share our work.
What is Cannibal Open Touch?
Cannibal Open Touch is a custom recovery (like ClockworkMod or TWRP), created purely out of love for the platform and the desire to contribute something cool to the community. The name embodies everything that Cannibal Open Touch is. We take what we believe are the best features of popular recoveries like TWRP and ClockworkMod and, well, cannibalize them along with rolling out our own features.
Features:
Full Touch UI
Complete theme support, including app for management of themes (we'll get to that in a sec)
On-device backup and restore
Backup and restore via ADB
Much much more planned!
Bugs:
During installation, the standard Android installing icon gets displayed instead of the custom dialog box.
If you find a bug, please do not report it here! Instead, report it in the GitHub repository!
Screenshots
See the Screenshots tab above. (Or click me if you're using Tapatalk!)
Nandroid has been replaced!
Nandroid is in fact gone, and has been replaced with a much more robust backup solution. Backups can now be made either with ADB (the recommended way) or via the new Backup and Restore item in the main menu. Backups made via the built-in menu can be copied to a PC and restored via ADB, and backups made via ADB can likewise be copied to your device and restored using the Backup and Restore menu.
Code:
adb backup -f mybackupfilename.ab boot system data cache
You can also restore said backup by using adb, like so:
Code:
adb restore mybackupfilename.ab
Downloads:
Cannibal Open Touch d2lte builds (latest: CannibalOpenTouch-2.99.10_d2lte.tar)
How to install:
Download the latest Alpha image
Reboot to Download Mode:
Code:
adb reboot download
Flash the image with ODIN
Boot into recovery mode
Changelog:
3.0 Alpha 10 (2.99.10)
Themes are now stored in /cache/cot/themes to fix an issue introduced with FDE.
3.0 Alpha 9 (2.99.9)
Real menu scrolling! (but volume keys still work)
All backup/restore operations now verify that you want to take action
Resized UI to be more usable on all device resolutions
Themes can now display a battery charge indicator (depends on individual theme settings)
3.0 Alpha 8 (2.99.8) (not released)
Not released
3.0 Alpha 7 (2.99.7)
On-device backup and restore
3.0 Alpha 6 (2.99.6)
Complete theme support
Recovery settings (Theme settings and Unsigned ZIP flashing)
The preceding list is not 100% complete. See the project source code page for the full commit list.
Cannibal Open Touch themes app:
We are currently seeking Alpha testers for an app that will let users download and choose themes without rebooting to recovery mode. Currently there are 20 slots open. If you wish to join please PM me. The only requirement is you must have a Google+ account and are willing to submit proper bug reports, should any arise.
Cannibal Open Touch Themes:
You can now make your own themes for Cannibal Open Touch! See the example themes (it's pretty self-explanatory). Themes must be installed in /sdcard/cot/themes/theme_name (or /data/media/cot/themes/theme_name) in order to work. Please feel free to submit pull requests to have your custom themes added to the theme repository. They will also be packaged and made available to download via the Cannibal Themes app (mentioned above)!
Contribute to Project Open Cannibal
If you like our work and want to see more, consider a donation to the project!
Project Open Cannibal gerrit: http://review.projectopencannibal.org
Credits:
tdm, for the superb touch code (and lots more)
sblood86, for joining the project and leading the charge to greatness
thenameisnigel, for picking up our webhosting while I was gone
anyone else who has ever contributed to any Android-related project
XDA:DevDB Information
Cannibal Open Touch, Tool/Utility for the Verizon Samsung Galaxy S III
Contributors
thenameisnigel, Sblood86, drewwalton19216801, tdm, CyanogenMod, Koush and many others
Source Code: https://github.com/ProjectOpenCannibal/android_bootable_recovery-cm
Version Information
Status: Alpha
Created 2014-11-23
Last Updated 2014-12-03
Reserved
Reserved
Sounds great. Cant wait to try it. Thanks for all your hard work on this cool new recovery!
Is this seed able to be used on phones with a locked boot loader?
Thanks for your hard work. I wish I had a unlocked bootloader to try it out on this phone. I've used it on other phones and really liked it.
can we flash with something like flashify or do we have to use odin?
dvaderx said:
can we flash with something like flashify or do we have to use odin?
Click to expand...
Click to collapse
You try mobile Odin.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Click to expand...
Click to collapse
This is an unofficial port of TWRP for Samsung Galaxy Pocket Plus. The original work code is done by @Alonso1398 but since he disconnected his updates for our device I'm carrying this project from now on
About
TWRP is an open source, community project that was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After their work on the EVO 4G they wanted to work on a project that would work on more devices than just the EVO 4G and they settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
Disclaimer
I am not responsible for bricked devices or dead SD cards, your are the one who decided to flash this recovery
Click to expand...
Click to collapse
Bugs/What's not working?
-Themes, will its not broke but use 240×240 themes (its preferable to stay away from it)
Download links
- TWRP Flashable zip
- recovery.fstab
- recovery.img
How to take a backup
1 - Open the terminal emulator.
3 - type "su" (without quotation marks).
3 - Grant root permission.
4 - Type "dd if =/dev/block/mmcblk0p6 of=/sdcard/recovery.img".
5 - Go to the root of the device's internal memory (sdcard) and copy that backup to a secure location.
How to install
- Installing as flashable zip
1 - Download the TWRP recovery.zip and place the root of the memory card.
2 - Reboot your custom recovery.
3 - Select install zip from SD / choose Zip.
4 - Choose TWRP recovery.zip.
5 - Then reboot to recovery.
6 - Enjoy TWRP installation mode.
OR
- Flashing as an image
1 - Download the file and place in in the root of the device's internal memory (sdcard).
2- Open the terminal emulator.
3 - Type "su".
4 - Type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6".
5 - Wait a few seconds, then restart the device and enter recovery mode and enjoy your TWRP.
OR
- Installing with ZIT flasher
1 - Download ZIT Flasher, recovery.fstab, TWRP recovery.img.
2 - Install and open the ZIT Flasher.
3 - Press in settings, click on recovery.fstab, look for the file and press it.
3 - click MAIN, press in BROWSER, search for "recovery.img".
4 - Restart the device and enter recovery mode and enjoy the TWRP.
FAQ
Visit the official TWRP FAQ
Support
If you have found a bug, please consider posting it in this thread, also grab recovery.log in /tmp or I can't help you.
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Changelog
12-12-15
-Ported again
-Full SELinux support
-Updated keys
-Official changelog
14-12-15
-Initial Port
-Official changelog
Opensource
-Device Tree : https://github.com/XadoA/android_device_samsung_coriplus
-Kernel Source : https://github.com/Alonso1398/android_kernel_samsung_coriplus
Gotta try dis
Which version is more stable for samsung galaxy pocket plus, 2.6.03 or 2.8.7? Regards
Sent from my GT-S5301 using XDA Free mobile app
I can not install rom breeze with this version of recovery, instead with version 2.6.3, I do it without problems..saludos
Sent from my GT-S5301 using XDA Free mobile app
hey hey. i need this. the links are broken. can you put here new links?. please
rodrigo151515151515151 said:
hey hey. i need this. the links are broken. can you put here new links?. please
Click to expand...
Click to collapse
in case anyone needs this, here is twrp 3.4 for coriplus
twrp-34-coriplus.img | by MLXProjects for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Just leaving this for the future (you can already find it at galaxy pocket forum)
MLX said:
in case anyone needs this, here is twrp 3.4 for coriplus
twrp-34-coriplus.img | by MLXProjects for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Just leaving this for the future (you can already find it at galaxy pocket forum)
Click to expand...
Click to collapse
thanks!! :U
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP 3.0.0-x OFFICIAL Builds, Tool/Utility for the HTC Pico (Explorer)
Contributors
MSF Jarvis, abhi_qwerty, thewisenerd,Dees_Troy
Source Code: https://github.com/TeamWin/android_device_htc_pico
Version Information
Status: Stable
Current Stable Version: 3.0.0-2
Stable Release Date: 2016-03-22
Created 2015-12-31
Last Updated 2016-03-23
Reserved
Features:
- Material UI thanks to @z31s1g
- F2FS compatible
- Supports OpenRecoveryScript commands placed in /cache/recovery -- Was borked in 2.8.0.0 and 2.8.5.0
- Data backups are now functional; backup sd-ext if you're on one of my ROMs
- Issues with bootloops due to dirty flashes solved. For those on aw3som3 or CM 12.1, use respective images from my TWRP Experiments Thread.
Reserved
Bugs(Currently very minor ones, thank god)
- MTP borked on Arch Linux (reported by @abhi_qwerty)
- USB Storage borked on Windows (tested by me)
Useful Links
- Flashing Guide
- NAND Recovery
MSF Jarvis said:
Since this is an alpha build, I'll need all the feedback I can get. I currently require feedback for whether USB Storage and MTP are working or not. @chankya, wanna help?
Click to expand...
Click to collapse
hey MSF yes both MTP and usb storage worked for me i booted up your cyanogen os build with this recovery that worked too. Let you know if i found any bug :good:
chankya said:
hey MSF yes both MTP and usb storage worked for me i booted up your cyanogen os build with this recovery that worked too. Let you know if i found any bug :good:
Click to expand...
Click to collapse
Thanks. @abhi_qwerty has also confirmed his download. He'll also confirm if they work on Linux.
MSF i tried this on ubuntu 15.10 so it is working on linux don't know about windows
chankya said:
MSF i tried this on ubuntu 15.10 so it is working on linux don't know about windows [emoji14]
Click to expand...
Click to collapse
Means it'll probably work on my Wily Werewolf system too. Will check Windows compatibility at night when Dad comes back from office. Sometimes helps to have a non-techie family[emoji6]
MSF Jarvis said:
Means it'll probably work on my Wily Werewolf system too. Will check Windows compatibility at night when Dad comes back from office. Sometimes helps to have a non-techie family[emoji6]
Click to expand...
Click to collapse
True story :good::good:
Mission accomplished.
USB Storage is dead on Windows 8.1, but MTP works almost as fast as USB Storage. Shouldn't be an issue for anyone.:fingers-crossed:
@abhi_qwerty, have a read of this and then tell if the issue persists.
Does this work with older JB and KitKat ROMs that are not aw3some based?
hrkh83 said:
Does this work with older JB and KitKat ROMs that are not aw3some based?
Click to expand...
Click to collapse
Unfortunately not. But I can cook something up if there's people wanting that.
Edit: Though that'll qualify as unofficial, as it'll be a personal build. That'll show up on the Experiments thread, if ever.
MSF Jarvis said:
Unfortunately not. But I can cook something up if there's people wanting that.
Edit: Though that'll qualify as unofficial, as it'll be a personal build. That'll show up on the Experiments thread, if ever.
Click to expand...
Click to collapse
@MSF Jarvis
Yes.
I would be deeply grateful if you could make a non-aw3som3 based updated TWRP available for me and other users who want to install older ROMs.
hrkh83 said:
@MSF Jarvis
Yes.
I would be deeply grateful if you could make a non-aw3som3 based updated TWRP available for me and other users who want to install older ROMs.
Click to expand...
Click to collapse
Available here
MSF Jarvis said:
Available here
Click to expand...
Click to collapse
@MSF Jarvis
Thank you very much. I am deeply grateful. I will try it and report back.
hrkh83 said:
@MSF Jarvis
Thank you very much. I am deeply grateful. I will try it and report back.
Click to expand...
Click to collapse
Good. I haven't got around to trying this out so testers are appreciated.
hrkh83 said:
@MSF Jarvis
Thank you very much. I am deeply grateful. I will try it and report back.
Click to expand...
Click to collapse
But I don't see any download on it. Are you sure you downloaded the right recovery image??
Sent from my HTC Explorer A310e using Tapatalk
!!!!!!!!!! Serious help needed !!!!!!!!!
I flashed 2.8.7.0 using Rashr(Cause my phone usb somehow got fu*ked up and couldnt do fastboot using pc).
Now I am trying to flash new ROM . It's not allowing boot any ROM, i dint get any error while flashing , success msg is coming but it's not booting up(even I aint seeing any ROM bootanimation) and again TWRP recovery menu is coming. Already tried flashing 4 ROMS no luck :'(
And I also tried flashing new recovery(old version) using 'image' toggle but it's giving 255 error.
Please help me I anit using my mobile and I dnt have any other mobile.
ReX-Hell2heAven said:
!!!!!!!!!! Serious help needed !!!!!!!!!
I flashed 2.8.7.0 using Rashr(Cause my phone usb somehow got fu*ked up and couldnt do fastboot using pc).
Now I am trying to flash new ROM . It's not allowing boot any ROM, i dint get any error while flashing , success msg is coming but it's not booting up(even I aint seeing any ROM bootanimation) and again TWRP recovery menu is coming. Already tried flashing 4 ROMS no luck :'(
And I also tried flashing new recovery(old version) using 'image' toggle but it's giving 255 error.
Please help me I anit using my mobile and I dnt have any other mobile.
Click to expand...
Click to collapse
Which ROM were you using before this?
Sent from my pico using XDA Labs
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:
Unofficial TWRP 3.0.2-0 for Ulefone Metal
Mirror 1
MD5 - 10286EE1255C8371A2E5F720896D02C2
SHA-1 - E6C0875ADA34EB1CDE5D5A648D3F8B9AC883EFDA
INSTALLATION:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
XDA:DevDB Information
RECOVERY] Unofficial TWRP for Ulefone Metal, Tool/Utility for the Android General
Contributors
Jonny
Source Code: https://github.com/JonnyXDA/android_device_ulefone_metal/tree/Omni
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-11-20
Created 2016-10-31
Last Updated 2016-11-20
FAQ:
- None yet!
DEVICE-SPECIFIC CHANGELOGS:
3.0.2-0:
-Fully built from source for Ulefone Metal
Current TWRP "bugs" for Ulefone Metal:
NONE
Thanks for your work.
Recovery not mounting sd card.
Here is log:
Internal build from ulefone forum works.
Mounting sd card works.
Thanks.
here is log:
dropbear2 said:
Internal build from ulefone forum works.
Mounting sd card works.
Thanks.
here is log:
Click to expand...
Click to collapse
Internal? You mean the build I posted there this morning?
Jonny said:
Internal? You mean the build I posted there this morning?
Click to expand...
Click to collapse
Yes, build posted this morning.
dropbear2 said:
Yes, build posted this morning.
Click to expand...
Click to collapse
Cool, I'll update this thread with it in a bit.
This build twrp in downloads (2016-11-02 16:29) does not work.
Is not the same as the build in ulefone forum.
This twrp works: http://ota.cm.mkoas.de:8080/job/TWRP Ulefone Metal/ws/recovery.img
dropbear2 said:
This build twrp in downloads (2016-11-02 16:29) does not work.
Is not the same as the build in ulefone forum.
This twrp works: http://ota.cm.mkoas.de:8080/job/TWRP Ulefone Metal/ws/recovery.img
Click to expand...
Click to collapse
I know, I said I would get round to updating this post as well, I haven't been able to yet as I've been busy
Jonny said:
I know, I said I would get round to updating this post as well, I haven't been able to yet as I've been busy
Click to expand...
Click to collapse
sorry,
I thought that you replaced.
Thread updated with the new links (eventually!).
Apologies for the delay
Hey,
i've flashed TWRP and when i boot it, the phone just shows the ulefone logo and then restarts..
I tried to flash with flashtools and via fastboot flash recovery...
Its possible to flash custom rom, which works quite nice, but TWRP won't come up so i can't root phone or do nandroid backups.
Any help? Any idea how to get logs of what happening?
BTW: reflashed offical stock does the same, displays ulefone logo and reboots..
EDIT:
Flashed recover as boot, and boot as recovery:
Normal boot (should start TWRP now) reboots all the time.
Recovery boot (should boot normal boot.img now) works and boots the System..
So there has to be a problem with the downloaded TWRP/Recovery Image not working on my phone..
It's normal Ulefone Metal don't know why it doesn't work.. wpuld like so see some logs or something
Edit2:
Flashed twrp-3-0-2-4es-by-mdsdev from needrom,
which worked.. don't know why any other one didn't...
I can not find the scatter mentioned in the post. I tried to install it with another scatter or another TWRP, but when I try to run the recovery it simply restarts.
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
sinrequilorios said:
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
Click to expand...
Click to collapse
It is not my fault if existing ROM's don't flash properly, we faced this problem on Elephone P9000, it is because the people who develop the ROM's don't use the proper mount points, if they did, it would flash. Instead, they use the mount points for the ported recoveries which are not correct.
End of story, not my fault and I will not support the people that this happens to.
sinrequilorios said:
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
Click to expand...
Click to collapse
Jonny said:
It is not my fault if existing ROM's don't flash properly, we faced this problem on Elephone P9000, it is because the people who develop the ROM's don't use the proper mount points, if they did, it would flash. Instead, they use the mount points for the ported recoveries which are not correct.
End of story, not my fault and I will not support the people that this happens to.
Click to expand...
Click to collapse
I think here's some confusion. As far as I understand it, it's not a problem of neither the recovery, nor wrong mount points.
There's just a newer revision of the model it seems. This newer models only work with recovery, built against stock pre-built kernel (aka ports).
Our rom is built for being flashed by this recovery, because this recovery is the only compiled one. Unfortunately, there's nothing which can be done without ulefone updating the kernel source code.
DerTeufel1980 said:
I think here's some confusion. As far as I understand it, it's not a problem of neither the recovery, nor wrong mount points.
There's just a newer revision of the model it seems. This newer models only work with recovery, built against stock pre-built kernel (aka ports).
Our rom is built for being flashed by this recovery, because this recovery is the only compiled one. Unfortunately, there's nothing which can be done without ulefone updating the kernel source code.
Click to expand...
Click to collapse
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Jonny said:
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Click to expand...
Click to collapse
Ug..
GPL source code is provided on our Metal thread...
https://github.com/MediatekAndroidDevelopers/android_kernel_ulefone_metal
Cheers
M.A.D. Team
Jonny said:
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Click to expand...
Click to collapse
Of course we didn't build upon your kernel. Why should we have done this?
We are using your recovery, or more detailed, we are suggesting to use your recovery.
What's your problem? We did not disrespect you in any way.
Sent from my Thor using Tapatalk
DerTeufel1980 said:
Of course we didn't build upon your kernel. Why should we have done this?
We are using your recovery, or more detailed, we are suggesting to use your recovery.
What's your problem? We did not disrespect you in any way.
Sent from my Thor using Tapatalk
Click to expand...
Click to collapse
^^ THIS