Cannibal Open Touch 3.0 Alpha 9
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 hammerhead builds (latest: CannibalOpenTouch-2.99.9_e970.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 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 AT&T LG Optimus G
Contributors
drewwalton19216801, Sblood86, thenameisnigel, sblood86, thenameisnigel, tdm, CyanogenMod, Koush and many others
Version Information
Status: Alpha
Created 2014-03-23
Last Updated 2014-10-26
Reserved for future use.
Awesome to see your work here. I remember running it on my lg optimus s quite some time ago. Glad to see it here will try out tonight after work.
Making the iPhone jealous one user at a time.
Will this flash both kit kat and 4.2 roms
sent from a guy living in a van down by the river
Awesome! Works like a charm. I've missed this recovery. Only did a backup wipe and restore but great so far!
Making the iPhone jealous one user at a time.
Can someone post a picture of the recovery? The bottom sixth of my screen does not work so im curious if I will be able to properly use the recovery.
Sent from my LG-E970 using XDA Premium 4 mobile app
jriv said:
Will this flash both kit kat and 4.2 roms
sent from a guy living in a van down by the river
Click to expand...
Click to collapse
Yes, it is based on the very latest ClockworkMod so if it flashes in that, it will flash with this
Dr0!dFreek said:
Can someone post a picture of the recovery? The bottom sixth of my screen does not work so im curious if I will be able to properly use the recovery.
Sent from my LG-E970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There are blurrycam photos in the Screenshots section. Since we no longer use the on-screen buttons you should be fine.
Were the tab to download this thanks
Sent from my LG-E970 using xda app-developers app
cwbcwb said:
Were the tab to download this thanks
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
See the attached screenshot, it's pretty hard to miss.
Yea I do It took me a day to find it sorry I do have a issue tho how to flash this because I got the file its in SD card downloads but when I go to bootloader then recovery the file dose not show up in my downloads or the IMG
Sent from my LG-E970 using xda app-developers app
You have to flash from fastboot, the directions tell you how
Making the iPhone jealous one user at a time.
What dose that mean throw Odin or what because I did what the op said go to bootloader then to recovery I don't see nothing that tells me fastboot what I do see tho is in small print at bottom is fast boot but no bottom to click on
Sent from my LG-E970 using xda app-developers app
You have to have adb setup and installed on your computer. There is a smaller install that can be found on Google search for fastboot.
Once that is installed and the drivers for the phone, copy the img file to that directory.
Launch adb, the phone has to be in fastboot mode. Fastboot flash recovery nameofrecovery.img
Once complete use volume keys to select recovery
Making the iPhone jealous one user at a time.
cwbcwb said:
What dose that mean throw Odin or what because I did what the op said go to bootloader then to recovery I don't see nothing that tells me fastboot what I do see tho is in small print at bottom is fast boot but no bottom to click on
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Disclaimer-I am not recommending this app, nor claiming to know whether it will work.
Flashify states it will flash recovery img. Have seen people mention using it, but it may have been with a kernel img.
adfurgerson said:
Disclaimer-I am not recommending this app, nor claiming to know whether it will work.
Flashify states it will flash recovery img. Have seen people mention using it, but it may have been with a kernel img.
Click to expand...
Click to collapse
I tried it with twrp, it was unsuccessful for me so I just gave up on it.
Making the iPhone jealous one user at a time.
i get this unknown partition Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Roy>adb reboot bootloader
C:\Users\Roy>fastboot flash recovery/COT3.0-Alpha2_e970.img
unknown partition 'recovery/COT3.0-Alpha2_e970.img'
error: cannot determine image filename for 'recovery/COT3.0-Alpha2_e970.img'
C:\Users\Roy>fastboot flash recovery/sdcard/to/download/COT3.0-Alpha2_e970.img
unknown partition 'recovery/sdcard/to/download/COT3.0-Alpha2_e970.img'
error: cannot determine image filename for 'recovery/sdcard/to/download/COT3.0-A
lpha2_e970.img'
C:\Users\Roy>fastboot flash recovery/sdcard/download/COT3.0-Alpha2_e970.img
unknown partition 'recovery/sdcard/download/COT3.0-Alpha2_e970.img'
error: cannot determine image filename for 'recovery/sdcard/download/COT3.0-Alph
a2_e970.img'
C:\Users\Roy>fastboot flash recovery /path/to/downloaded/COT3.0-Alpha2_e970.img
error: cannot open '/path/to/downloaded/COT3.0-Alpha2_e970.img'
C:\Users\Roy>fastboot flash recovery/sdcard/to/downloaded/COT3.0-Alpha2_e970.img
unknown partition 'recovery/sdcard/to/downloaded/COT3.0-Alpha2_e970.img'
error: cannot determine image filename for 'recovery/sdcard/to/downloaded/COT3.0
-Alpha2_e970.img'
C:\Users\Roy>
---------- Post added at 04:58 AM ---------- Previous post was at 04:47 AM ----------
adfurgerson said:
Disclaimer-I am not recommending this app, nor claiming to know whether it will work.
Flashify states it will flash recovery img. Have seen people mention using it, but it may have been with a kernel img.
Click to expand...
Click to collapse
I want to say think you I just use that app and it work for me really well
Sent from my LG-E970 using xda app-developers app
Cwbcwb, I believe the issue was after recovery there wasn't a space, Just a heads up anyone else feel free to chime in.
Fastboot flash recovery nameofrecovery.img
That should have flashed it. Either way, glad you got it flashed.
Making the iPhone jealous one user at a time.
OK so I used this for a few days its cool and sick but when it comes to backing up and restoring it slow so I want back to my old one
Sent from my LG-E970 using xda app-developers app
cwbcwb said:
OK so I used this for a few days its cool and sick but when it comes to backing up and restoring it slow so I want back to my old one
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
I'll give you that one, compared to phillz touch or twrp. Also had issues with touch. I would push on one selection and another would select.
Making the iPhone jealous one user at a time.
cwbcwb said:
OK so I used this for a few days its cool and sick but when it comes to backing up and restoring it slow so I want back to my old one
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
mkfryan said:
I'll give you that one, compared to phillz touch or twrp. Also had issues with touch. I would push on one selection and another would select.
Making the iPhone jealous one user at a time.
Click to expand...
Click to collapse
Hence the "Alpha" state. Feel free to contribute patches.
Related
As some of you might know ive been working lately on porting TWRP to our device, and now, after many hours work, I can finally release it to the public.
GENERAL
Team Win Recovery Project 2.3, or twrp2 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.
Click to expand...
Click to collapse
http://teamw.in/project/twrp2
INFORMATION
There are 2 version:
- Flykernel 0.8 with only TWRP (v 2.3.2.3)
- Flykernel 0.8 with both TWRP (v 2.3.2.3) and CWM (v 6.1.0.9).
I also made a custom theme, see Download and Usage.
Its named: 'This is black and white'. As the name says its a black and white minimal theme.
INSTALLATION
- Make sure you are on a FXP based jellybean rom.
- Choose one of the the two images
- Flash them with fastboot : fastboot flash boot IMAGENAME.img
- You will also need the wifi modules of flykernel (0.8fix): http://www.mediafire.com/?16ytgk56ioiko6z
USAGE
- TWRP only recovery:
Use volume down when home led is pink
- CWM / TWRP dual:
Use volume down for CWM when home led is pink
Use power button for TWRP when home led is pink
- Custom TWRP theme:
Place the ui.zip (from download folder mediafire) in /sdcard/TWRP/theme
DOWNLOAD
http://www.mediafire.com/?lcdana76k8ews
BUGS
As far as I know and is tested there are 2 bugs:
- Mount USB Storage in TWRP
- Reboot to recovery (boot from recovery and rom)
Please report bugs if you find them.
Much work has gone in to this, so I would appreciate a Thanks or a donation
Also I want to give credit to Championswimmer for providing the base dualrecovery ramdisk.
Congrats bro you are ****ing awasome:beer:
Sent from my Xperia Ray using xda premium
File Type
My id10t corporate network drops img files, cannot download. I'll check it out when I'm home. Thanks! :highfive:
EDIT: Great Stuff! Successfully flashed dual, booted into both with no problem. Then I wiped and installed PACv18 with all my extras in one go by queueing the zip files. Rebooted the phone, all 100%
One thing I did notice: the time shown in TWRP was not my local time, I have GMT +2, where the time that was displayed was UMT -6 (Houston, Chicago those places) I think it's CST (not sure)
I did not attempt a backup/restore operation yet, but wiping flashing, queueing woks 100%
Good Job thomas !!
Very sweety thing! Using it daily - very great job done! I like it! Thanks man! Dual Recovery makes my day =)
Langes said:
My id10t corporate network drops img files, cannot download. I'll check it out when I'm home. Thanks! :highfive:
EDIT: Great Stuff! Successfully flashed dual, booted into both with no problem. Then I wiped and installed PACv18 with all my extras in one go by queueing the zip files. Rebooted the phone, all 100%
One thing I did notice: the time shown in TWRP was not my local time, I have GMT +2, where the time that was displayed was UMT -6 (Houston, Chicago those places) I think it's CST (not sure)
I did not attempt a backup/restore operation yet, but wiping flashing, queueing woks 100%
Good Job thomas !!
Click to expand...
Click to collapse
you can change time settings in twrp
will it work with CM10 FXP 150 ??
EDIT: err tried it works like a charm!!
Yes
Sent from my Xperia Ray using xda app-developers app
sarangkunte05 said:
will it work with CM10 FXP 150 ??
Click to expand...
Click to collapse
Should work
Sent from my Xperia Ray using xda app-developers app
how bout its performance??it is same as flykernel v8..:good:
ezr said:
how bout its performance??it is same as flykernel v8..:good:
Click to expand...
Click to collapse
So far, performance is same
It is fly kernel 0.8... Just another ramdisk
Sent from my Xperia Ray using xda app-developers app
thomas1991_12 said:
It is fly kernel 0.8... Just another ramdisk
Sent from my Xperia Ray using xda app-developers app
Click to expand...
Click to collapse
Just to clarify: So, if you were not on fly before, you need to flash WiFi modules from flykernel thread? I was on FlyKernel and WiFi still works like a charm
Langes said:
Just to clarify: So, if you were not on fly before, you need to flash WiFi modules from flykernel thread? I was on FlyKernel and WiFi still works like a charm
Click to expand...
Click to collapse
Yes thats correct (will update OP). Because sony devices dont have a seperate recovery partition, it needs to be embedded with the kernel.
do i need to wipe anything after install new kernel??
ezr said:
do i need to wipe anything after install new kernel??
Click to expand...
Click to collapse
Nope, shouldnt be necessary.
ezr said:
do i need to wipe anything after install new kernel??
Click to expand...
Click to collapse
I did not need to. I only wiped after successful boot to test if wipe and flashing works ok
To clarify a Android memory management issue (which I was unclear on) for others;
Both TWRP and TWRP/ CWM recoveries in the new kernel image increase the size of the files to be flashed into the boot sector (TWRP = 6.8MB, TWRP/ CWM = 8.3MB), FlyKernel 0.8 including CWM is only 5.3MB.
If a user is using FXP150 stock ROM build with the Xperia Keyboard flashed as well the /system folder is virtually full (974kB free only). Don't let that worry you! The boot sector that the new kernel image files (including recoveries) occupies is completely separate to the /system ROM part of the device and it will fit!!
This is fantastic, didn't know TWRP was miles ahead of CWM in terms of user friendliness.
Can you share your sources please? I want to port TWRP on my Xperia Mini
Just extract boot image
Sent from my Xperia Ray using xda app-developers app
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
I would appreciate a screen shot from your device, mainly under GUI options or custom backup menu where you select partitions
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Nexus 4 (mako)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Special thanks to McKael for his invaluable support in fixing for Nexus 4
Big thanks to Shaky156 and mustangtim49 for debugging it for the Nexus 4
hey philz used your recovery on s3 gonna try this for and report
Hi,
I used your recovery on my old S2 so I thought I'd try this. First impressions are good, touch needs to be calibrated though. I will upload screenshots soon
---------- Post added at 01:54 AM ---------- Previous post was at 01:39 AM ----------
Screenshots don't appear to be saving for me unless i'm doing something wrong. It says that it has taken the screenshot but when i look under clockworkmod/screenshots there are no screenshots
22sl22 said:
Screenshots don't appear to be saving for me unless i'm doing something wrong. It says that it has taken the screenshot but when i look under clockworkmod/screenshots there are no screenshots
Click to expand...
Click to collapse
Yeah, same for me too. Also having problems with the touchscreen. Will test it out more soon. Play around with backups and such but all in all, i'm loving it! Like having custom colours and such
Hey buddy, I flashed your recovery and I'll say, I love the colors and the other little things you've done to it. One problem is it's not quite ready yet. When I was booted to your recovery, I kept getting an error message "unable to find screen settings" I don't know if that's what it said exactly. Another issue is the touch control is not 100%, it's sensitivity is spotty. So, using the hardware keys, I attempted a nandroid and it got as far as data then failed at that partition. Anyhow, I modified mskip's old version of his toolkit to install your recovery through fastboot. I will link it here for anyone else interested in beta testing for you. When you launch the toolkit on windows 7 or 8(I have 8touch) just choose to permanently flash custom recovery, then choose either "philz" or cwmtouch-6.0.1.9, I renamed your file to trick the tool into flashing your recovery. If I can help, either message me here in your thread or via PM.
Edit: I've updated the toolkit to flash recovery 4.9.2.3. Big thanks to XDA Senior Member mskip for his awesome Toolkit that I molested to make it flash philz recovery. Remember, choose to flash cwmtouch 6.0.1.9 and it will flash philz instead through fastboot. This is for those who don't have a custom recovery installed yet.
New Toolkit
If I've helped, smash that "Thanks" button!
Big thanks,
If overall it works, then the small things will be fixed. It is an early release to spot bigger issues
- screen shots: is expected, I used a precompiled dynamic binary and it could fail for many reasons. I will look at it later
- dim screen: will be fixed in next release
- currently, custom backup and restore need a bit tweaking because of the additional partitions, I will fix it properly
- touch: I will release a version to calibrate screen. In next v5, this will be no more needed
Stay tuned and thank you for the early reports
I will keep the above warnings until I fix most important functions like the backup and restore
Here's a debug version for touch calibration
http://www.mediafire.com/view/?odqumulgia866fn
Please do the following:
Each time, only touch screen and immediately lift finger, do not keep it on screen
1- Reboot into recovery, do not touch screen at all
2- Touch and lift finger on top left corner (outside any menu)
3- Touch and lif on top right (outside any menu)
4- Touch and lift on bottom left (outside any menu)
5- Touch and lift on bottom right (outside any menu)
6- Touch middle of screen and swipe to left edge, slowly until you are out of screen. Do the same right, then top, then bottom
Now, do not touch the screen any more
Use hardware buttons:
- do a nandroid backup, not custom backup
- Go to Advanced / Error Report
- upload here the /sdcard/clockworkmod/recovery.log file you get
Re: [Nexus 4][CWM Advanced Edition] PhilZ Touch
Waoooooo philz is here loved your recovery in note 2. Good to see u here again
Sent from my Nexus 4 using Tapatalk 2
Re: [Nexus 4][CWM Advanced Edition] PhilZ Touch
I won't be able to try it till tonight (east coast U.S.) because I'm at work and I didn't bring my lappie. I'll try to get some free time and make a flashable zip or install it through terminal while I'm working.
mustangtim49/XDA Recognized Contributor
mustangtim49 said:
I won't be able to try it till tonight (east coast U.S.) because I'm at work and I didn't bring my lappie. I'll try to get some free time and make a flashable zip or install it through terminal while I'm working.
mustangtim49/XDA Recognized Contributor
Click to expand...
Click to collapse
Thank you and no hurry at all, really
It shouldn't take time to fix if I get enough logs and tests
Try to provide a log when the backup fails as that's a bit strange. Normal backup should work normally if things are left stock
Re: [Nexus 4][CWM Advanced Edition] PhilZ Touch
Phil3759 said:
Thank you and no hurry at all, really
It shouldn't take time to fix if I get enough logs and tests
Try to provide a log when the backup fails as that's a bit strange. Normal backup should work normally if things are left stock
Click to expand...
Click to collapse
I don't know if you are aware that the guys with TWRP recovery are having a lot of issues getting their recovery fully working on the N4. I'm pretty sure it has to do with the way the phone is partitioned for data and sd on the same partition, kinda. Anyhow, had a break at work and wanted to see what was happening if anything. I'll get to the new version tonight and run through those tests. Thanks.
mustangtim49/XDA Recognized Contributor
mustangtim49 said:
I don't know if you are aware that the guys with TWRP recovery are having a lot of issues getting their recovery fully working on the N4. I'm pretty sure it has to do with the way the phone is partitioned for data and sd on the same partition, kinda. Anyhow, had a break at work and wanted to see what was happening if anything. I'll get to the new version tonight and run through those tests. Thanks.
mustangtim49/XDA Recognized Contributor
Click to expand...
Click to collapse
I support many /data/media devices
If stock CWM works, this should and hopefully will work
Re: [Nexus 4][CWM Advanced Edition] PhilZ Touch
Phil3759 said:
I support many /data/media devices
If stock CWM works, this should and hopefully will work
Click to expand...
Click to collapse
I read that you supported numerous devices, I was just throwing it out there that they can't seem to get the partitions right. Which not only affects nandroids, it doesn't wipe when it says it is, ect...... I'm sure you'll get it, hell, half the fun is getting it right, lol! TTYL.
mustangtim49/XDA Recognized Contributor
mustangtim49 said:
I read that you supported numerous devices, I was just throwing it out there that they can't seem to get the partitions right. Which not only affects nandroids, it doesn't wipe when it says it is, ect...... I'm sure you'll get it, hell, half the fun is getting it right, lol! TTYL.
mustangtim49/XDA Recognized Contributor
Click to expand...
Click to collapse
If stock CWM works, then it is ok. If stock CWM doesn't work, then it could be hard in fact...
v4.91.4: debug
- fix nandroid, custom and twrp backup and restore for devices with different special partitions (/preload, /modem, /efs)
- better support for devices without secondary storage
- fix set brightness and auto dim screen for Nexus 4
http://www.mediafire.com/view/?6p6ppaba30oh6mq
Please, follow debug instructions of previous post to fix touch and nandroid backup if still issues
Re: [Nexus 4][CWM Advanced Edition] PhilZ Touch
Phil3759 said:
v4.91.4: debug
- fix nandroid, custom and twrp backup and restore for devices with different special partitions (/preload, /modem, /efs)
- better support for devices without secondary storage
- fix set brightness and auto dim screen for Nexus 4
http://www.mediafire.com/view/?6p6ppaba30oh6mq
Please, follow debug instructions of previous post to fix touch and nandroid backup if still issues
Click to expand...
Click to collapse
Here ya go, man, It was driving me nuts trying to find this log! A problem it's having is it can't find "sdcard/clockworkmod". Thankfully, your recovery was able to write at "data/media" instead. So, everything was there including my back up(where it should be) . Hope this log helps, thanks again buddy. http://db.tt/ifm0BsiD
Also, it seems the nandroid is good, so maybe that's a non-issue now.
mustangtim49/XDA Recognized Contributor
Re: [Nexus 4][CWM Advanced Edition] PhilZ Touch
Sadly, you forgot the touch calibration steps. So i cannot fix it. Please, someone do the calibration steps described above.
I will look at /sdcard issue
Brightness setting seems broken from log. I will look at it too
Sent from my GT-I9100 using Tapatalk 2
does this support usb storage mode? its kinda annoying to use adb to push files to flash :/
if not, i'd love to see this feature
Re: [Nexus 4][CWM Advanced Edition] PhilZ Touch
Phil3759 said:
Sadly, you forgot the touch calibration steps. So i cannot fix it. Please, someone do the calibration steps described above.
I will look at /sdcard issue
Brightness setting seems broken from log. I will look at it too
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Like this recovery, have pm you the touchscreen log, goodluck
Sent from my Nexus 4 using Tapatalk 2
Re: [Nexus 4][CWM Advanced Edition] PhilZ Touch
The Troll said:
does this support usb storage mode? its kinda annoying to use adb to push files to flash :/
if not, i'd love to see this feature
Click to expand...
Click to collapse
Not possible on a Nexus
DISCLAIMER:
Your device, your responsibility. I am not liable for anything you flash, including this.
As a result you'll probably want to read the rest of the thread and at least be aware of what you're flashing.
You've been warned.
CM: CWM Based Recovery for SPH-L720 (jfltespr)
Features:
This is comes from CM as it is provided in the source repos. I will be keeping it as such at this time.
Only deviations are to allow it to build properly and are generally from CM repos.
If modifications deviate from CM source we will set up a new repo.
Screenshots: None
Latest Build: v1.0
Tar/ZIP Mirror: [CWM][RECOVERY]Team SXTP CWM for Galaxy S4 (Team SXTP Site)
Flash Instructions:
Boot to Odin Mode and flash via Odin.
Summary Changelog:
Code:
v1.0 - Final Prealpha, successful operations and display
Prealpha Builds - Initial Buildup.
Source:
CyanogenMod Official Repositories
Device Dependencies:
android_device_samsung_jf-common
android_device_samsung_msm8960-common
android_device_samsung_qcom-common
Sprint GS4 Device Repository
NOTE: Due to potential copyright issues I do not include a vendor repo.
You can extract the files from the phone or ROM as needed - should you decide to build on your own.
Credits:
Early Bringup Advice: Entropy512, Shabbypenguin, Cordell12
Current Advisors/Collaborators: Noobnl (CM CDMA Maintainer)
Testers: Mohogalore, robbyamor, crawj and others
Steve Kondik (Cyanogen) for CM development and jf common work
The CM maintainters who continue to improve CM along with Mr. Kondik
The crew that is Paranoid Android - Pure Hybrid!
...and of course! You, the community, for your support as well! Thank you!
Heard this has bad graphics so will revisit asap
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
Heard this has bad graphics so will revisit asap
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Sorry for not reporting that here. Ever since I screwed up my phone I've been killing time by flashing every recovery firmware I got my hands on. I'll probably keep testing before the stock image comes out.
Running this now... as stated graphics do not redraw every other click but it does function normally otherwise. Just made a backup which completed normally.
edit... navigation is also a little touchy vol down will sometimes register as enter.
did a full wipe booted fine now to restore.
Thanks - working on a possible graphics fix at the moment.
Will post Alpha 4 when it's ready.
harrybozack said:
Sorry for not reporting that here. Ever since I screwed up my phone I've been killing time by flashing every recovery firmware I got my hands on. I'll probably keep testing before the stock image comes out.
Click to expand...
Click to collapse
Define screwing up the phone... just curious if can get it back running.
I have a stock ROM that is uploaded but will have to rename to pull from web.
restore completed and looks good
lafester said:
restore completed and looks good
Click to expand...
Click to collapse
Very nice! So you're functioning normally?
I will test this CWM to see how it works, i did test shabby penguins version and got a bug where it would only let me select every other selection and didnt recognize the selection.
Alpha 4 posted.
MoHoGalore said:
Very nice! So you're functioning normally?
Click to expand...
Click to collapse
yes everything restored that I can tell. navigating cwm is difficult though at the moment with the graphics error
same result on Alpha 3 for me. Will test Alpha 4
---------- Post added at 12:04 PM ---------- Previous post was at 12:00 PM ----------
just tested Alpha 4 and same results. Only lets me select every other selection and when i do make a selection the menu goes away and im left with the CWM logo and label on the bottom. Have to hold power to reboot.
when you have a blank screen hit vol down to enable the graphics
Sounds like need to play with recovery keys a little more. Glad it is functionally working though!
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
Define screwing up the phone... just curious if can get it back running.
I have a stock ROM that is uploaded but will have to rename to pull from web.
Click to expand...
Click to collapse
Well it's stuck in a boot loop. I flashed recovery firmware for the i9505 instead of my model phone and one of them screwed up big time. My own fault for being careless.
lafester said:
when you have a blank screen hit vol down to enable the graphics
Click to expand...
Click to collapse
well i did that but then it goes to a loose root access type screen. i always check no but then it reboots.
garwynn said:
Define screwing up the phone... just curious if can get it back running.
I have a stock ROM that is uploaded but will have to rename to pull from web.
Click to expand...
Click to collapse
Wait so you have the stock rom for the SPH-L720? I'd love to try flashing that to fix my problems.
Alpha 4 works, except you need to count key presses. Every other press changes highlighted selection but every press registers for choice (if that makes sense.) When pressing enter to make selection, press volume down to "wake up" the screen.
Backup successful. Restore successful.
I can make a video if that would be easier to explain what I'm seeing, if needed.
:edit: Location for backup is normal - /data/media/clockworkmod/backups - Must have been something I did. Disregard previous statement.
MoHoGalore said:
Alpha 4 works, except you need to count key presses. Every other press changes highlighted selection but every press registers for choice (if that makes sense.) When pressing enter to make selection, press volume down to "wake up" the screen.
Backup successful. Restore successful.
I can make a video if that would be easier to explain what I'm seeing, if needed.
:edit: Location for backup is normal - /data/media/clockworkmod/backups - Must have been something I did. Disregard previous statement.
Click to expand...
Click to collapse
You had the same experience as I did. Worked fine just hard to navigate.
In other news I just activated my phone and it did a factory reset and installed on the sprint crap. It did not wipe sd so my backup is still there. attempting to restore now.
update: restore successful
Update with Alpha 4 and testing of Garwynn's test builds: Actions taken in this order;
(Started with Alpha 4 already flashed)
1. Backup - Successful
2. Restore - Successful
3. Flashed Stock Dump Recovery - Successful
4. Flashed Stock Dump Kernel - Successful
5. Flashed Stock Dump Rom - Successful
6. Flashed Alpha 4
7. Performed Wipe Data/Factory reset- successful
8. Rebooted system
9. Restored previous backup - Successful
(Used Odin 1.85 for Stock build flashes)
Download
Mega
Installing
You can't flash this yet (I'm working on that, I promise) but you can boot from it!
NOTE: THIS IS A WIP. Not a lot has been really tested yet and this is posted merely for your enjoyment atm.
I don't suggest flashing anything yet, not that there is anything to flash heh.
Also, I take no responsibility if you break your watch, yada, yada.
To do this, make sure you have Android's tools (for fastboot), an unlocked bootloader, and the watch connected to your computer in Debug mode.
> adb reboot bootloader
<wait for the reboot to happen>
> fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Enjoy!
Did u push the tree to github?
1st built for me was a no go
wouldn't twrp make more sense since its touch based?
D-FUSE said:
Did u push the tree to github?
1st built for me was a no go
Click to expand...
Click to collapse
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
ptesmoke said:
wouldn't twrp make more sense since its touch based?
Click to expand...
Click to collapse
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
ptesmoke said:
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
Click to expand...
Click to collapse
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
dude1981 said:
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
jamcar said:
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Click to expand...
Click to collapse
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Click to expand...
Click to collapse
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Click to expand...
Click to collapse
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
PlayfulGod said:
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Click to expand...
Click to collapse
It's only booting because it doesn't work when flashed to recovery. The file size is around 8 mb whereas the legitimate recovery is 23 mb, which I'm sure is an issue. Is it possible that I'm only creating a ramdisk that gets paired with the watch's kernel and I need to make an image with both of them? Sorry, this whole uBoot stuff confuses me a bit.
PlayfulGod said:
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Click to expand...
Click to collapse
Heh, I'm not actually afraid of git, I guess, I'm afraid of the whole "making a device-specific git repo that can be easily pulled while building CM." I guess I just don't have the time atm to set it up properly, but dw, I'll get to it this weekend! :fingers-crossed:
dude1981 said:
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the iOS mod is something I downloaded awhile ago for my N5. I'm afraid I don't have the link anymore. Sorry, man.
Pepski said:
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
Click to expand...
Click to collapse
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Smith7018 said:
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Click to expand...
Click to collapse
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Pepski said:
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Click to expand...
Click to collapse
Weird... I don't even think you need root to push to /sdcard/ but I could be wrong. I'd suggest trying /sdcard/emoji.zip so it knows where to resolve. Also, I don't use Windows, but does the backslash work on adb as a file separator?
what happened to development on this?
If you're not familiar with the TWRP Builder project, you can read more about it here. And, searching through the latest list of TWRP Builder Downloads, I found a more recent TWRP build for the Moto E4 Plus (Owens).
Download: TWRP-3.2.2-owens-20180702.img
This tested fine on my XT1775, so I thought I'd pass it on.
To flash, just hold Power and Vol. Down on boot to enter the unlocked bootloader, then via ADB:
Code:
fastboot flash recovery TWRP-3.2.2-owens-20180702.img
UPDATE: This was posted in Android Forums 10 days ago by @Goose03, who submitted the necessary files to TWRP Builder. His original thread is here, but he requested that someone repost in XDA because he'd been banned.
Thank You
Okay, my thanks to @Goose03 then. I don't believe this is a duplicate of a thread on this forum, though, and XDA is really my go-to site for TWRP builds.
(On that Android Forums thread, he actually requested someone post on XDA, since he'd been banned. I didn't see that anyone had done that yet, and it really deserves its own thread.)
From @Goose03:
Heads up! Don't format data with this TWRP version! It doesn't work right. I'll look at the trees and get it fixed ASAP. For now if you need to format data use the original TWRP here: https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154
Click to expand...
Click to collapse
Don't use this build guys, nothing but problems here. 3.1.1 has been serving me well.
Looks like we've got a new build now that addresses the problem with formatting and bumps to v3.2.2. I've updated the OP.
Goose03 said:
Here you go. Fully working TWRP 3.2.2
https://github.com/TwrpBuilder/andr...ns/releases/tag/untagged-43dd6f9480dd2b924462
I tested making and restoring a backup and formatting data on my XT1776 at least and all is good. It was just missing a few things and it's built with omni_twrp-7.1.2 instead of 5.1.1 this time. This should work for Oreo also if and when we get it. Enjoy!
Edit: if anyone finds a bug please try to get a recovery log and report and post it here so I can get it fixed. Don't just ignore it and go back to the old recovery.
Click to expand...
Click to collapse
Working great on my 1775. I flashed in TWRP using the built in image flasher. Thank you for your work and for sharing with us.
Sent from my Pixel 2 XL using XDA Premium HD app
I ran [fastboot boot TWRP-3.2.2-owens-20180702.img], phone reboot to tWRP cover screen and stays there forever.
I have retail XT1775 with NPRS26.58-45-16 ROM. does it matter?
min1968 said:
I ran [fastboot boot TWRP-3.2.2-owens-20180702.img], phone reboot to tWRP cover screen and stays there forever.
I have retail XT1775 with NPRS26.58-45-16 ROM. does it matter?
Click to expand...
Click to collapse
flash no-dm-verity.zip from any thread