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 mako builds (latest: CannibalOpenTouch-2.99.10_mako.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 -c "lge.kcal=0|0|0|x" /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
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)
drewwalton19216801, for helping to spearhead the project and forward porting most of our old functions
thenameisnigel, for picking up our webhosting while Drew was gone and assisting with device ports
anyone else who has ever contributed to any Android-related project
XDA:DevDB Information
Cannibal Open Touch, Tool/Utility for the Google Nexus 4
Contributors
Sblood86, drewwalton19216801, 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
This device has been restricted to my testing only for too long now. Have at it...
Miles thanks!!
Tomorrow if i can, i will test it.
Thank you another time for your work.
Thanks dev for the work.
hy i need help i just flash your recovery and when i reebot brings me over again to recovery ,,,,,,
what can i do .... thx
---------- Post added at 06:01 PM ---------- Previous post was at 05:48 PM ----------
scooby25 said:
hy i need help i just flash your recovery and when i reebot brings me over again to recovery ,,,,,,
what can i do .... thx
Click to expand...
Click to collapse
can anyoane please healpe me
scooby25 said:
hy i need help i just flash your recovery and when i reebot brings me over again to recovery ,,,,,,
what can i do .... thx
---------- Post added at 06:01 PM ---------- Previous post was at 05:48 PM ----------
can anyoane please healpe me
Click to expand...
Click to collapse
I can't imagine any reason it would be rebooting into recovery if you're selecting reboot to android...
One possibility is that you typed fastboot flash boot <path to image> instead of fastboot flash recovery.
Grab a recovery log anyway though if you don't mind, we can try to see if something wonky is happening from the recovery side but honestly I doubt it.
To do that connect to your computer (you will need working adb drivers) and run the following
Code:
adb pull /tmp/recovery.log
Post the log on pastebin or similar and link it here.
Look like this recovery get no love... why ?
Does is support encryption?
No zip?
Could you please tell me where on the phone the backups are kept?
Sent from my Nexus 4 using XDA Free mobile app
Without trying I shouldn't comment but, little advise: SCREENSHOTS ARE MUST IN POST
(Lot of People like me give a try, Pic's describe more than words!)
Nice!
haven't tried it yet, still unfamiliar with those command.
btw, I love the ingress theme
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Reserved.
Dees_Troy said:
This has been available for a little while, but now I'm adding an official thread for it here on XDA.
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 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.
Click to expand...
Click to collapse
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium
florin250 said:
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
i dont think so......
but....we better wait answer from the expert
@OP
wow.....i just dream about this last night and today you give this.....thank you so much....
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
download stuck at 99,99%, why???
edit : downloading without download manager, now it's okay
In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?
sekhar13515 said:
In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?
Click to expand...
Click to collapse
The old TWRP recoveries never completely worked for OB.Sometimes it was the SD mounting, sometimes you couldn't restore the backup done with the same TWRP version and so on.I will try this because I like TWRP more than CWM but it's the last time if it won't work.
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
No, it's not but it's 2.3.20(not yet for OB of course).
USB storage not mounting.
Back to the "bomb proof" cwm 5.8.1.3 touch.
great share!Very good job, thank you.
there is a new version 2.3.1.1
timvdhoorn said:
there is a new version 2.3.1.1
Click to expand...
Click to collapse
ilko already said it here http://forum.xda-developers.com/showpost.php?p=34469364&postcount=6 and there is a newer version but it haven't been built to our device yet.
Updated!
Dees_Troy said:
Updated!
Click to expand...
Click to collapse
SDcard mounting as mass storage still not working, please check.
I was writing the same report : )
well, too bad. I like it but it's useless to me since I transfer files very often through recovery. I can't compile a flasher with that
Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk
Every new version always the same problem.
re4lsk said:
Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk
Click to expand...
Click to collapse
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.
Dees_Troy said:
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.
Click to expand...
Click to collapse
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source
re4lsk said:
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source
Click to expand...
Click to collapse
It's not that I need a kernel as much as I need the proper path to the lun file for whatever kernel I happen to be using. Since I don't have an Optimus Black I can't boot it up and look for it myself.
Hey there! It has been a while..
You may have noticed Team Win Recovery Project (short: TWRP) is available, but still not for our device,
and it seems I am the only one who spends time on making TWRP fully compatible
for our device which includes some bug fixes and modifications.
Both, TWRP and the kernel were compiled on my pc, using OS X Yosemite (10.10) as host system
from CM sources.
Use at your own risk.
I am not responsible for any damages on your device.
Click to expand...
Click to collapse
What is TWRP?
A fully touch driven custom recovery developed by TeamWin with a nice and easy to use user interface.
You can install your ROM's, backup it or restore it from/on your internal or external storage.
Backups can be compressed which saves alot of storage space and backups can have an individual,
user chosen name. Some unique features are an integrated filemanager, shell access,
rooting and the option to set a display timeout and display brightness.
TWRP includes alot of more features that I listed.. just explore yourself.
Download (also check the #Download page):
recovery263.img => TWRP 2.6.3.0 (STABLE)
recovery283_1.img => TWRP 2.8.3.0 (BETA)
For developers and for GPL reasons:
gkernel_x3_defconfig.zip => Used kernel defconfig (no kernel sourcecode changes have been made except mac os x specific kernel building fixes)
Sources (using cm10.2 sourcecode with cm p880 kernel):
p880_device: https://bitbucket.org/supergordon/device_lge_p880
p880_recovery_twrp: https://bitbucket.org/supergordon/twrp_lge_p880
p880_kernel: https://github.com/CyanogenMod/lge-kernel-p880
How do I install TWRP on my unlocked device?
Option 1: Fastboot
Code:
adb reboot oem-unlock
fastboot flash recovery recovery263.img
fastboot reboot
Option 2: ADB (put first the recovery image to the root directory of your internal storage)
Code:
adb shell
su
cat /sdcard/recovery263.img > /dev/block/mmcblk0p1
What device specific changes have been made?
Reboot options now properly working
Use CM's device specific fix to blank the display
Add missing external storage display name
Add missing screen brightness path
Modified display dimming delay
Fix rendering bugs that caused high battery consumption and device heat-ups
Add proper handling of the quadcore. Reduces backup time by about 10%.
UMS support (external storage only)
Since 2.6.3.0:
Using cm10.2 source
Using cm kernel
Exclude wiping sd-ext (bugfix for 2.6.1.0)
Since 2.8.3.0:
Now using twrp.fstab
Remove UMS support (TWRP has now MTP support. both internal and external storage are shown on the PC)
Add data/media[/0] button in Advanced page. Pressing the button toggles between /data/media and /data/media/0
Added missing option to (not) backup/restore recovery partition.
SD-Ext support (secondary partition of your microsd has to be ext4 formatted)
Using twrp sources from 30 december 2014
Click to expand...
Click to collapse
For changelogs on TWRP itself visit http://www.teamw.in/project/twrp2
My submitted patches on TeamWin's gerrit:
http://review.teamw.in/606
http://review.teamw.in/607
[July 1st] --> Both patches have been now reviewed and merged into the official TWRP sources.
Please report any bugs to help improving TWRP on our device.
Bug reports can be submitted here.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG Optimus 4X HD
Contributors
gordon0001
Version Information
Status: No Longer Updated
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-12
Current Beta Version: 2.8.3.0
Beta Release Date: 2014-12-31
Created 2013-09-17
Last Updated 2015-01-16
Reserved
Finally!!!...Thanks..Thanks..Thanks..
I follow you and your work and i hope that soon you release a gbootmenu 0.2 with twrp 2.5...
Or via terminale put the recovery.img in your sdcard and write:
1) su and agree superuser request
2) flash_image recovery /sdcard/recovery.img
Sent from my Wildfire S using xda app-developers app
gave thanks as appreciation =)
Sent from my LG-P880 using Tapatalk 4 Beta
Thanks awesome! i really like twrp much more than cwm.
Is it possible that Fix Permissions is not working? it takes about a second to finish, with cwm it was 5 to 10 minutes.
Thanks!
Fastboot mode :
cannot load 'recovery.img': No error
Why?
Thx
saenta said:
Thanks awesome! i really like twrp much more than cwm.
Is it possible that Fix Permissions is not working? it takes about a second to finish, with cwm it was 5 to 10 minutes.
Thanks!
Click to expand...
Click to collapse
no, thats fine. twrp uses its own way to fix permissions.
Gesendet von meinem LG-P880 mit Tapatalk 2
@tiflao
Recovery.img is not in your fastboot directory. I'm 100 percent sure
Sent from my LG-P880 using xda app-developers app
tiflao said:
Fastboot mode :
cannot load 'recovery.img': No error
Why?
Thx
Click to expand...
Click to collapse
be sure you change to the directory where you stored recovery.img at your terminal(linux, osx)/command prompt(windows) with the "cd" command.
Thx guys
@gordon0001:
How is the development of the next version of GBootmenu going on? I am really looking forward to see TWRP 2.5.0.0 and CWM 6.0.3.1 in just one menu.
Thanks for TWRP 2.5.0.0! Good work!
Thanks gordon0001. Will make flashing and everything else a lot easier. Installed using the All in one P880 kit.
Have a good weekend!
tool_king said:
@gordon0001:
How is the development of the next version of GBootmenu going on? I am really looking forward to see TWRP 2.5.0.0 and CWM 6.0.3.1 in just one menu.
Thanks for TWRP 2.5.0.0! Good work!
Click to expand...
Click to collapse
Hey!
Nice to see you like my work, but this thread is about TWRP and not GBootMenu. Post your questions about my other work in the correspondending release thread.
gordonbennet said:
Thanks gordon0001. Will make flashing and everything else a lot easier. Installed using the All in one P880 kit.
Have a good weekend!
Click to expand...
Click to collapse
Thank you!
The all in one kit installs an outdated, dangerous to use, version of TWRP.
Please install the new, updated version of TWRP or your hardware could be damaged.
Instructions can be found in the first post #1.
gordon0001 said:
Thank you!
The all in one kit installs an outdated, dangerous to use, version of TWRP.
Please install the new, updated version of TWRP or your hardware could be damaged.
Instructions can be found in the first post #1.
Click to expand...
Click to collapse
I forgot to add that I replaced the old one with your one in the toolkit's data files (just renamed the v2.5 to whatever the toolkit was using and deleted the old one).
Thanks for the concern though. Currently loving archived backups
TWRP is damn good! more functions, faster backup/restore etc., thanks!
Thanks for your work .. I love the recovery so much .. Thumbs up
Loving the touch,everything works as it should
updated to 2.6.0.0. see first post
the patches i submitted were reviewed, verified and merged into the official twrp sources. meaning with twrp 2.6.0.0 every device profit from it
http://review.teamw.in/606
http://review.teamw.in/607
Click to expand...
Click to collapse
gordon0001 said:
updated to 2.6.0.0. see first post
the patches i submitted were reviewed, verified and merged into the official twrp sources. meaning with twrp 2.6.0.0 every device profit from it
Click to expand...
Click to collapse
works perfect here
Sent from my LG-P880 using xda app-developers app
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
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.
Note, all images have already been loki'd. Just flash away!
AT&T Downloads
Verizon Downloads Special thanks to rhcp for helping test the update for G2 VZW to fix 4.4 rom install.
T-Mobile USA Downloads
Korean F320K Downloads
Sprint Downloads
Bell Canada Downloads
Rogers Canada Downloads
Be sure to thank @djrbliss for his work on loki for the G2. Without loki, recovery and ROMs would not be possible.
SWEET! Thanks!
EDIT: Guess it's not available yet. Can't find it.
Sent from my LG-D801 using Tapatalk 4
You're the MAN! Thank you for all of the hard work Devs! it only gets better from here
it was there a minute ago....
cslingerland said:
You're the MAN! Thank you for all of the hard work Devs! it only gets better from here
it was there a minute ago....
Click to expand...
Click to collapse
You have it? I can't seem to find it.
Sent from my LG-D801 using Tapatalk 4
Once the links go live again, and we install TWRP, does this mean we can flash ROMS now, or do we need to wait for G2-specific development?
Han Solo 1 said:
Once the links go live again, and we install TWRP, does this mean we can flash ROMS now, or do we need to wait for G2-specific development?
Click to expand...
Click to collapse
Once ROMs are available specifically for the G2, you can flash them.
Right now there are none, and flashing something from a different phone WILL cause issues.
chrisexv6 said:
Once ROMs are available specifically for the G2, you can flash them.
Right now there are none, and flashing something from a different phone WILL cause issues.
Click to expand...
Click to collapse
Oh boy. I just want a stock ROM with wifi-hotspot enabled. That’s it.
---------- Post added at 03:23 PM ---------- Previous post was at 03:07 PM ----------
So is this not working yet? When I hit "install OpenRecoveryScript" in GooManager, it says "no recoveries were found for your device".
It hasn't been put on the servers per say.
Sent from my LG-D800 using Tapatalk 4
whats the status on using goomanager to get recovery other then what we already know
I tried updating thru goo manager but it doesn't work. It downloads the new .IMG file but even though it says recovery installed, when I boot to twrp its still version 2.5.*.* any ideas on why this happens? Or how to fix? BTW I'm on a att galaxy s4 (jflteatt)
Sent from my SGH-I337 using XDA Premium 4 mobile app
SeveNVapoR said:
I tried updating thru goo manager but it doesn't work. It downloads the new .IMG file but even though it says recovery installed, when I boot to twrp its still version 2.5.*.* any ideas on why this happens? Or how to fix? BTW I'm on a att galaxy s4 (jflteatt)
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First, try posting in the correct forum for the correct device, this is the LG G2 section.
Second, change the download directory for GooManager from whatever it currently is to /sdcard/goomanager/ and that will fix it.
Your right...it worked
Sent from my SGH-I337 using XDA Premium 4 mobile app
Amazing work devs can't wait for more!
Sent from my LG-F320S using xda app-developers app
Fantastic work, thank you so much. Flashed, backed up, started removing system apps. Time to start working on a Custom Rom. Guess I ought to learn Aroma Installer, haven't made a rom since the the Bionic so I've never messed with it before.
Han Solo 1 said:
Oh boy. I just want a stock ROM with wifi-hotspot enabled. That’s it.
---------- Post added at 03:23 PM ---------- Previous post was at 03:07 PM ----------
So is this not working yet? When I hit "install OpenRecoveryScript" in GooManager, it says "no recoveries were found for your device".
Click to expand...
Click to collapse
I totaly feel you,
The phone itself feels solid except for all the crap bloatwear thats bugging down the ram and storage.
a clean rom with tethering is all this phone needs.
goomanager can't find any recovery for the F320K10m version,
is it possible?
can i hook my phone to PC and run adb and do fastboot flash recovery openrecovery-twrp-2.6.3.0-g2vzw.img ?
exciting stuff, this is great to see
drmp3z said:
can i hook my phone to PC and run adb and do fastboot flash recovery openrecovery-twrp-2.6.3.0-g2vzw.img ?
Click to expand...
Click to collapse
Considering this uses an exploit, almost 100% sure the answer is no.
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.2.1-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
CHANGELOG for 3.2.2-0:
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
CHANGELOG for 3.2.3-0:
Fix automatic installing of OTA zips on encrypted devices
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Fixed TWRP Decryption on Android version 7.1.2+ (i.e. 8.1 and 9.0)
TWRP release (twrp-3.2.3-20190202-ham) is based on Lineage-15.1 sources
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Download the latest version from here | Regular : twrp-3.2.3-20190202-ham
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:
Fastboot Install Method (No Root Required):
You will need the platform-tools from the Android SDK on your computer. Find the SDK Only section on the page linked and install the SDK and download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on your computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
Click to expand...
Click to collapse
You should now be in fastboot mode. Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot -i 0x2b4c flash recovery <recovery.img name>.img
Click to expand...
Click to collapse
fastboot -i 0x2b4c oem reboot-recovery
Click to expand...
Click to collapse
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Good work bro! But I'm unable to use both versions due to missconfigured onscreen touch sensor. Upper left button is reachable via touching of lower right part of the screen and so all other onscreen stuff is inaccessible completely...
adanoss said:
Good work bro! But I'm unable to use both versions due to missconfigured onscreen touch sensor. Upper left button is reachable via touching of lower right part of the screen and so all other onscreen stuff is inaccessible completely...
Click to expand...
Click to collapse
I guess, its kernel issue. The same was happening on lineage-15.0 with others. Thanks for reporting. Will check that issue and update new build.
[UNOFFICIAL][RECOVERY][ham] TWRP 3.2.1-0 touch recovery [11-12-2017]
Update:
1. Fix touch issue that was faced by some users.
2. Added option where you can now backup /persist , /firmware & /splash too.
3. Fix OTA assertions issue while flashing android version 7.1.2 & below.
4. And other bug fixes
Link updated in OP. Enjoy!
Now everything seems to work fine, even backing up to external USB stick via OTG. Haven't tried to restore via OTG though.
shubhambhise said:
Update:
1. Fix touch issue that was faced by some users.
2. Added option where you can now backup /persist , /firmware & /splash too.
3. Fix OTA assertions issue while flashing android version 7.1.2 & below.
4. And other bug fixes
Link updated in OP. Enjoy!
Click to expand...
Click to collapse
The new version is unable to decrypt data anymore. It always shows: Pattern failed, please try again!:crying:
Data is not mounting for me. I flashed this twrp with flashify. But later I flashed it through 3.1.0. Still it doesn't show data partition
Aroma gapps not working
Rafiq007 said:
Data is not mounting for me. I flashed this twrp with flashify. But later I flashed it through 3.1.0. Still it doesn't show data partition
Click to expand...
Click to collapse
Looks like ftfs partitions are not detecting
Confirmed. I have data as F2FS and it doesn't mount.
Ok. So those who are facing f2fs data mount issues in TWRP-3.2.1 contact me on telegram to test the the new version that hopefully fixes this issue.
Telegram ID - https://t.me/sb6596
how to backup previous rom in this new twrp?
[UNOFFICIAL][RECOVERY][ham] TWRP 3.2.1-0 touch recovery [17-12-2017]
Update:
1. Fix the data mounting issue on F2FS filesystem.
2. Hopefully encryption is fixed. Don't know cause I haven't checked.
Link Updated in OP. Enjoy!
shubhambhise said:
Update:
1. Fix the data mounting issue on F2FS filesystem.
2. Hopefully encryption is fixed. Don't know cause I haven't checked.
Link Updated in OP. Enjoy!
Click to expand...
Click to collapse
Awesome! Thank you!
shubhambhise said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.2.1-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks[/SIZE]
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Download the latest version from here | Regular : twrp-3.2.1-0-ham | Green : twrp-3.2.1-0-ham-green | ( To see how green themed twrp looks like? Head towards screenshot section )
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:
Fastboot Install Method (No Root Required):
You will need the platform-tools from the Android SDK on your computer. Find the SDK Only section on the page linked and install the SDK and download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on your computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
You should now be in fastboot mode. Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Hello, I am a Chinese user, Androidfile can not be used in China, can provide other solutions, I am very grateful.
shubhambhise said:
Update:
1. Fix the data mounting issue on F2FS filesystem.
2. Hopefully encryption is fixed. Don't know cause I haven't checked.
Link Updated in OP. Enjoy!
Click to expand...
Click to collapse
Still failed to decrypt data. The only one version of TWRP can decrypts data on my ZUK Z1 is this: https://forum.xda-developers.com/zu...-3-1-0-0-touch-recovery-t3572069/post71801936
Linzeal said:
Still failed to decrypt data. The only one version of TWRP can decrypts data on my ZUK Z1 is this: https://forum.xda-developers.com/zu...-3-1-0-0-touch-recovery-t3572069/post71801936
Click to expand...
Click to collapse
Thanks. I will go through it and will push an update.
Dzwa said:
Hello, I am a Chinese user, Androidfile can not be used in China, can provide other solutions, I am very grateful.
Click to expand...
Click to collapse
Here you go..??
https://drive.google.com/file/d/19RVLX9am9Qd-4xx0j9-XcUtjI0kswKCP/view?usp=drivesdk
Sent from my Lenovo Zuk Z1 using XDA Labs
Since 17.01.2018 there is an official Version of TWRP 3.2.1.
I have tried to flash it with the official TWRP app and got the message "failed".
Now i do not dare to flash the image file over the recovery. Has anyone of you sucessfully flashed the official TWRP 3.2.1 Recovery with the app or recovery?
Thank you for your answers
Matze1909 said:
Since 17.01.2018 there is an official Version of TWRP 3.2.1.
I have tried to flash it with the official TWRP app and got the message "failed".
Now i do not dare to flash the image file over the recovery. Has anyone of you sucessfully flashed the official TWRP 3.2.1 Recovery with the app or recovery?
Thank you for your answers
Click to expand...
Click to collapse
when you're going to flash img, select flash img option in twrp before flashing...
And then flash the recovery img...
[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of official builds.
Device Config: https://github.com/bigbiff/android_device_google_crosshatch
Hello, this is a test build for crosshatch users.
If others thing don't work, please report the issue and let me know.
I am opening this thread to replace @Dees_Troy's thread with his blessing.
http://twrp.me
Old Info
Download here:
Test1: https://build.twrp.me/test/crosshatch/twrp-3.6.0-0-test1-crosshatch.img
- fix backup and restore
- fix decryption thanks to @Captain_Throwback and his twrp-common tree which fixes the order of proprietary services starting: https://github.com/TeamWin/android_device_qcom_twrp-common
- supports 12 decryption with no pin set
- fully supports 11 decryption with keymaster
Thanks for the build. Tested on Android 11, latest Scorpion rom. Touch does not appear to be working.
ghostcrew said:
Thanks for the build. Tested on Android 11, latest Scorpion rom. Touch does not appear to be working.
Click to expand...
Click to collapse
Scorpion is not using a stock DTBO. You will have to use the fastbooted twrp adb shell session to install this flashable zip:
https://build.twrp.me/test/crosshatch/twrp-installer-3.6.0_11-0-crosshatch.zip
Push it to /sdcard with adb, and do twrp install twrp-installer-3.6.0_11-0-crosshatch.zip inside the adb shell
Then use adb to reboot to TWRP that is now installed as recovery in boot.
Thanks for TWRP for Pixel 3XL!
Thanks bro!. Dont use my pixel for much anymore but great to see someone still developing for it
Thank you for TWRP! Lifesaver. Tried this on my Pixel 3XL running on Evolution X, A11 .... Works great!
bigbiff said:
Scorpion is not using a stock DTBO. You will have to use the fastbooted twrp adb shell session to install this flashable zip:
https://build.twrp.me/test/crosshatch/twrp-installer-3.6.0_11-0-crosshatch.zip
Push it to /sdcard with adb, and do twrp install twrp-installer-3.6.0_11-0-crosshatch.zip inside the adb shell
Then use adb to reboot to TWRP that is now installed as recovery in boot.
Click to expand...
Click to collapse
I followed your instructions and now I have twrp on my phone and touch is working. Thank you for the instructions and thank you for TWRP on Pixel 3xl!
bigbiff said:
[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of official builds.
Device Config: https://github.com/bigbiff/android_device_google_crosshatch
Hello, this is a test build for crosshatch users.
If others thing don't work, please report the issue and let me know.
I am opening this thread to replace @Dees_Troy's thread with his blessing.
Download here:
Test1: https://build.twrp.me/test/crosshatch/twrp-3.6.0-0-test1-crosshatch.img
- fix backup and restore
- fix decryption thanks to @Captain_Throwback and his twrp-common tree which fixes the order of proprietary services starting: https://github.com/TeamWin/android_device_qcom_twrp-common
- supports 12 decryption with no pin set
- fully supports 11 decryption with keymaster
http://twrp.me
Click to expand...
Click to collapse
Hey, Biff. Thanks, of course. Just wondering if you are releasing it for Pixel 3... I am on P3XL, but my wife is on P3.
sliding_billy said:
Hey, Biff. Thanks, of course. Just wondering if you are releasing it for Pixel 3... I am on P3XL, but my wife is on P3.
Click to expand...
Click to collapse
We are supposed to have someone lined up. Has anyone posted in the blueline forums?
Was able to install TWRP on my Crosshatch however whenever I tried to use the ADB Sideload function to install a rom I would get this error:
serving: 'C:\Users\Zero\Downloads\Pixel 3 XL Project\EvolutionX\evolution_crosshatch-ota-sq1d.211205.016.a1-12251000-unofficial-unsigned.zip' (~0%) adb: failed to read command: No error
Logs attached. *XDA wont let me upload the files see below.
Logs
delete...
Zero_Shadow said:
Was able to install TWRP on my Crosshatch however whenever I tried to use the ADB Sideload function to install a rom I would get this error:
serving: 'C:\Users\Zero\Downloads\Pixel 3 XL Project\EvolutionX\evolution_crosshatch-ota-sq1d.211205.016.a1-12251000-unofficial-unsigned.zip' (~0%) adb: failed to read command: No error
Logs attached. *XDA wont let me upload the files see below.
Logs
Click to expand...
Click to collapse
I was able to sideload lineage-18.1. Does adb devices show sideload?
bigbiff said:
We are supposed to have someone lined up. Has anyone posted in the blueline forums?
Click to expand...
Click to collapse
Unfortunately, no.
bigbiff said:
I was able to sideload lineage-18.1. Does adb devices show sideload?
Click to expand...
Click to collapse
Yes I am able to use adb devices in my command prompt and see the device while adb sideload is active in twrp. Heres what happens.
I open up TWRP > Wipe (Factory Reset) then Advanced > ADB Sideload > Swipe to Start Sideload
I see Starting ADB Sideload feature
I go back to my computer and type adb devices (to confirm it see it) > adb sideload filename.zip (being the file of course).
Soon I hit enter I get a crash within TWRP and it goes back to the Main startup page for twrp.
When I go back to ADB Sideload I see this message:
E: fialed to mount /tmp/com.android.apex.cts.shim.
apex to loop device /dev/block/loop0. Reason: Device
or resource busy
E: Unable to create loop devices to mount apex files
E: Unable to load apex images frin /system_root/
system/apex
I did install TWRP to recovery using Advanced > Flash Current TWRP
If I use one of the recoveries for PE or Lineage I am able to flash using adb sideload.
*Edit 1: Now I did download the version from Telegram so let me try the one link above.
*Edit 2: Just tried with the one linked above same thing.
*Edit 3: Logs for review. https://drive.google.com/drive/folders/1PqKN_QzdGnFJTu4Ov-2iUzyzv85ZaD9D?usp=sharing
I could be doing something wrong so any help would be appreciated.
Zero_Shadow said:
Yes I am able to use adb devices in my command prompt and see the device while adb sideload is active in twrp. Heres what happens.
I open up TWRP > Wipe (Factory Reset) then Advanced > ADB Sideload > Swipe to Start Sideload
I see Starting ADB Sideload feature
I go back to my computer and type adb devices (to confirm it see it) > adb sideload filename.zip (being the file of course).
Soon I hit enter I get a crash within TWRP and it goes back to the Main startup page for twrp.
When I go back to ADB Sideload I see this message:
E: fialed to mount /tmp/com.android.apex.cts.shim.
apex to loop device /dev/block/loop0. Reason: Device
or resource busy
E: Unable to create loop devices to mount apex files
E: Unable to load apex images frin /system_root/
system/apex
I did install TWRP to recovery using Advanced > Flash Current TWRP
If I use one of the recoveries for PE or Lineage I am able to flash using adb sideload.
*Edit 1: Now I did download the version from Telegram so let me try the one link above.
*Edit 2: Just tried with the one linked above same thing.
*Edit 3: Logs for review. https://drive.google.com/drive/folders/1PqKN_QzdGnFJTu4Ov-2iUzyzv85ZaD9D?usp=sharing
I could be doing something wrong so any help would be appreciated.
Click to expand...
Click to collapse
What zip are you installing?
Tried the A12 builds for PE, EvoX and PixelDust same issue across the board.
Thanks a lot for this build!!! My Pixel3 XL keeps getting corrupt due to handing/wifi dropping, now finally I can have a Nandroid backup!
Need help installing pls. Tried many times with stock to no avail. Now trying with evolution Rom to no avail. My cmd is fastboot flash boot TWRP.img, which works with stock, but I'm unable to install or sideload and have to reflash the stock kernel to reboot the Rom. Same with evolution besides with stock I can attempt to reboot (after flashing twrp) which reboots to twrp, but won't reboot at all with evolution (until reflashing the kernel) I've been at this for a few hours now, any advice much appreciated.
brandonabandon said:
Need help installing pls. Tried many times with stock to no avail. Now trying with evolution Rom to no avail. My cmd is fastboot flash boot TWRP.img, which works with stock, but I'm unable to install or sideload and have to reflash the stock kernel to reboot the Rom. Same with evolution besides with stock I can attempt to reboot (after flashing twrp) which reboots to twrp, but won't reboot at all with evolution (until reflashing the kernel) I've been at this for a few hours now, any advice much appreciated.
Click to expand...
Click to collapse
You don't flash boot.img with this device. You temporarily boot it with fastboot boot img, then push it to sdcard and use twrp's install recovery ramdisk function.
nithin suresh said:
Thank you for TWRP! Lifesaver. Tried this on my Pixel 3XL running on Evolution X, A11 .... Works great!
Click to expand...
Click to collapse
Is there any possible way you could put instructions or how to install list for me I would greatly appreciate it. I have the pixel 3xl and have been having the hardest time getting twrp install as well as other items.