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)
Related
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
Hi,
a few weeks ago I got a Samsung X Cover 2 after my loved Defy boke down...Thanks to the rooted image that theboegl created I examined the device and started to port CWM to the device. Some photos of CWM on the S7710 are here. Sorry - cant post outside links before I did 10 posts....attached.:silly: Thanks to OliverG96 who worked on CM for the S3 mini that is quite similiar to the skomer it wasn't a hard job to get it running.
The source is on my github account. (no link - see above - just google: github flxo). Feel free to comment and improve....
Code:
sudo heimdall flash --pit skomer.pit --Kernel2 recovery.img
DISCLAIMER: Use this recovery image at your own risk! You are responsible to any harm that is caused to your device during the use of this software.
Download
Mirror
CWM Changelog:
2013/07/08: Added kernel build with source from Samsung Open Source. Fixed external_sd stuff that enabled restore and backup to the sd.
2013/07/09: Fixed CWM boot loop (reboot recovery menu item or reboot syscall). Updated j4fs and param kernel modules.
2013/07/11: Added ext4 capabilities to installer (needed for otapackage). Updated fstab with reserved area at the partition end.
2013/07/19: Updated to version 6.0.3.3. edit: weird reboot issue.
2013/07/19: Updated to version 6.0.3.6 (cm-10.1). Sideload still not functional.
2013/11/03: Updated to version 6.0.4.4 (cm-10.2).
2013/11/09: Fixed USB and sideload. Do not use.
2013/11/14: Updated to version 6.0.4.5. Added param and j4fs modules to recovery.
2014/01/12: Updated to version 6.0.4.6. <-- USE THIS VERSION
TWRP Changelog:
2013/12/07: Initial TWRP version from Omnirom 4.3 branch
2013/12/21: Source update. Minor kernel fixes.
Thanks for your work!
For those who want to try this beta-build:
download the newest odin-flashable build from here - thanks to @flxo
start Odin >= 3.07
select the downloaded CMW in the PDA section
unselect autoreboot if you would like to test it after flashing immediately
plug your XCover2 in
flash it
let it reboot/if you want to test cwm now:
power off by holding the power button
hold Volume +, Home and Power button simultaneous
you should see cwm
done
BTW: no one should just follow me by doing a reboot recovery, though I have created an odin-flashable restore - build 12.07.2013 for getting out of the "boot to recovery" loop without loosing data.
flxo said:
Hi,
a few weeks ago I got a Samsung X Cover 2 after my loved Defy boke down...
Thanks to the rooted image that theboegl created I examined the device and started to port CWM to the device. Some photos of CWM on the S7710 are here. Sorry - cant post outside links before I did 10 posts....attached.:silly:
Thanks to OliverG96 who worked on CM for the S3 mini that is quite similiar to the skomer it wasn't a hard job to get it running.
The source is on my github account. (no link - see above - just google: github flxo). Feel free to comment and improve....
I did not try yet to flash a zip with the CWM port but so far the graphics look good and the SD is mounted. I attached the recovery image to this post:
Hang on.
cheers,
flxo
sorry for the short description, but it's Friday 9pm and I really shouldn't sit in front of my computer...
Click to expand...
Click to collapse
I'll try this out. Oh and if this works, I'll see if I can start porting any roms to this device now
---------- Post added at 11:28 AM ---------- Previous post was at 10:50 AM ----------
Yo, I made a flashable odin.tar! Enjoy testing guys, cheers
http://rapidshare.com/files/2716144166/recovery.tar.md5
I keep my fingers crossed for it.
It will open new world for our phone.
Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2
TheBoegl said:
BTW: no one should just follow me by doing a reboot recovery, though I have created an odin-flashable restore for getting out of the "boot to recovery" loop without loosing data.
Click to expand...
Click to collapse
Thanks. That fix is exactly what I need right now...
Everyone be carefull - this image is absolutely untested and may brick your device....
Lum_Os said:
I'll try this out. Oh and if this works, I'll see if I can start porting any roms to this device now
---------- Post added at 11:28 AM ---------- Previous post was at 10:50 AM ----------
Yo, I made a flashable odin.tar! Enjoy testing guys, cheers
http://rapidshare.com/files/2716144166/recovery.tar.md5
Click to expand...
Click to collapse
Has anyone tried
kolmanb said:
Has anyone tried
Click to expand...
Click to collapse
Tried flashing, works like a charm. Just hold volume up, home and power, let go of power when you feel vibration and keep hold volume up and home button and you're in cwm! Gonna try port first custom rom, cm10 from s2 and see if it truly works
Hello,
I have just tested : very good ! very good !
Thanks a lot.
:laugh:
Works perfectly super !:laugh::good:
backup: ok
restore: ok
Apology : restore works fine
install zip : from sd card; ext.sd card ok
kolmanb said:
Apology : restore works fine
install zip : from sd card; ext.sd card ok
Click to expand...
Click to collapse
Thanks!
I changed the recovery.fstab to mount the external SD on /sdcard. Storing backups on the real SD is IMHO more convenient.
The updated image is: 20130606_recovery.img
Thanks to TheBoegl for the hint.
flxo said:
I changed the recovery.fstab to mount the external SD on /sdcard. Storing backups on the real SD is IMHO more convenient.
Click to expand...
Click to collapse
Thats great. For everyone who want to flash this with odin try this image - it is the packed version of @flxo.
I have reupped the previous recoveries because they were unflashable with odin.
I really apologize for that mistake my Finnish, Slovenian and Bulgarian members if Odin is stuck, just unplug your phone and select the new image, plug it in again and flash.
This double post is to inform the few of you who have downloaded the file already.
I created an Odin flashable .tar.md5 of the 20130606_1_ version. I tried it myself, works fine.
One nitpicky question: flxo, shouldn't it be 20130706? It's July after all
flxo said:
[*]reboot recovery: reboots device normally. failed.
Click to expand...
Click to collapse
20130606_1_ fixed that for me, the device froze for half a minute and then rebooted into recovery.
EDIT:
Bad news: Somehow, the phone exclusively reboots into recovery now. I don't know if it's due to choosing "reboot recovery" or something else...
HeavyMoertel said:
Bad news: Somehow, the phone exclusively reboots into recovery now. I don't know if it's due to choosing "reboot recovery" or something else...
Click to expand...
Click to collapse
I guess you found my fix for that in the second post :good:
TheBoegl said:
I guess you found my fix for that in the second post :good:
Click to expand...
Click to collapse
Yeah, well, I really shouldn't have followed you on that, I guess.
But many thanks for reminding me of your fix. :highfive:
---------- Post added at 12:45 AM ---------- Previous post was at 12:13 AM ----------
Issue: factory reset formats the whole SD card.
I'm so sorry, can you tell me how to install CWM, I tried to Odin MOD but nothing Nest, thank you very much.
you were faster than i thought.
I've added the description and link in the second post.
Let me know if you need more information.
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.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Features:
-touchwiz ui with near stock functionality
-based on Tab A and Tab S frameworks
-Tab S2 apps
-Tab S3 UI Sounds
-SPen features
-theme support
-pre-rooted (magisk)
-deodexed
-debloated
-knox removed
-all apps support multiwindow
-some minor changes like removing safe volume warning, overlay fix etc
-ported IronKernel from @Tkkg1994 (read more about kernel features here: https://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-ironstock-kernel-v3-2-t3531295 )
Notes:
full wipe required!
First boot takes 10 minutes
For some features root required
Device encryption doesn't support here
If you don't want to install root, remove magisk folder from install zip
If you don't have working spen, flash stock rom before this one.
If you want to make custom rom based on my rom, you're welcome.
Thanks to @Miron24 for testing rom
Download:
02feb
gdrive: https://drive.google.com/open?id=1sAiyxBEkEDEWtOiuMvOM53DKWmAVWHQx
Thanks to @Tkkg1994 for the kernel
Kernel sources:
https://github.com/bonuzzz/IronKernel
I'll download and give this a shot. I really need all apps in multi windows.
How works SPEN?
write me please your feedback, what working or not working in hardware part
won't work on p600,
@maxximboy black screen after bootloader without any reboots?
@bonuzzz
Do your roms (P900, P600, T900) work on 3G devices(P901, etc.)? I want to test your rom on my P601. Do you plan to port Tab A 10.1 with S Pen apps to your roms?
Miron24 said:
@bonuzzz
Do your roms (P900, P600, T900) work on 3G devices(P901, etc.)? I want to test your rom on my P601. Do you plan to port Tab A 10.1 with S Pen apps to your roms?
Click to expand...
Click to collapse
if you dont need 3g support, so it should working. but current version doesn't boot on p600. trying to find, where is problem in kernel. wait for fix.
do you want exact app from tab A ?
Hi there, good to see this kind of development. I tried flashing, but install was unsuccessful.
Previous ROM is Resurrection Remix for P600
Went to recovery, did factory reset on TWRP, then wiped System partition
Flashed your zip, and out comes on the terminal:
This package is for "v1awifi, v2awifi, n1awifi, n2awifi, klimtwifi, chagallwifi" devices, this is a "lt03wifiue"
Updater process ended with ERROR: 7
So I assume the problem lies somewhere with the device name/code, but I'm not sure how to change this. From what I've searched it's in build.prop, but that doesn't exist one /system is wiped. After wiping everything I tried flashing AICP Rom, but still the same error code comes out when I tried flashing your .zip. Have any other tips? I assume you also have a P600 no? How did you get it to boot?
EDIT: Thanks for correcting noob mistake @mosimchah
Pact said:
Previous ROM is Resurrection Remix for P600 ie AOSP based
Click to expand...
Click to collapse
Resurrection Remix is lineage based, and lineage is caf based (not AOSP)
Sent from my LEX727 using XDA Labs
---------- Post added at 06:07 PM ---------- Previous post was at 06:00 PM ----------
bonuzzz said:
if you dont need 3g support, so it should working. but current version doesn't boot on p600. trying to find, where is problem in kernel. wait for fix.
do you want exact app from tab A ?
Click to expand...
Click to collapse
Check out the unofficial Lineage 13.0 kernel, it's based on the tab s mm source and works on the p600
https://github.com/exynos5420/andro...configs/cyanogenmod_deathly_n1awifi_defconfig
https://github.com/exynos5420/andro...tree/091b5954799bbfbb38bced4ac6342c5939900348
Sent from my LEX727 using XDA Labs
ok, lt03wifiue is also p600. I didn't know that. you could remove assert in updater-script to disable check device.
@Pact I have P900
OK, I removed the assert lines as per this guide:
https://forum.xda-developers.com/showpost.php?p=31519426&postcount=186
Used 7zip, edited the file mentioned above, deleted the lines, 7zip recompiles that, moved it to SD card and started flashing. Of course I did a factory reset beforehand, and wiped /system too. The usual stuff appears:
Checking config . . .
Formatting system . . .
Extracting system . . .
The flash was successful, then the Magisk installation lines appear and that was good too.
Once that's done, I flashed the kernel provided above, and that complete, I rebooted the tablet, no other warnings or anything like that appearing during installation. The Galaxy Note screen appeared, then the screen went black (lights on, nothing else displayed). I thought this was normal for a new flash, then I waited till 20 minutes and it's still like that. So I forced a reboot (long press power button) and the Galaxy Note screen appeared again, this time I've waited 5 minutes and nothing else happens - still lighted screen with nothing else. The backside is hot during both reboots, so something is definitely happening using CPU cycles, but I'm not sure what. Should I dirty reflash next?
bonuzzz said:
ok, lt03wifiue is also p600. I didn't know that. you could remove assert in updater-script to disable check device.
Test please this kernel
https://yadi.sk/d/WGxcpVrn3K6G7R
@Pact I have P900
Click to expand...
Click to collapse
Make sure you're using the proper vendor blobs
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/n1awifi
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/nx-common
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/exynos5420-common
Using the tab s blobs could cause it to not boot
Pact said:
OK, I removed the assert lines as per this guide:
https://forum.xda-developers.com/showpost.php?p=31519426&postcount=186
Used 7zip, edited the file mentioned above, deleted the lines, 7zip recompiles that, moved it to SD card and started flashing. Of course I did a factory reset beforehand, and wiped /system too. The usual stuff appears:
Checking config . . .
Formatting system . . .
Extracting system . . .
The flash was successful, then the Magisk installation lines appear and that was good too.
Once that's done, I flashed the kernel provided above, and that complete, I rebooted the tablet, no other warnings or anything like that appearing during installation. The Galaxy Note screen appeared, then the screen went black (lights on, nothing else displayed). I thought this was normal for a new flash, then I waited till 20 minutes and it's still like that. So I forced a reboot (long press power button) and the Galaxy Note screen appeared again, this time I've waited 5 minutes and nothing else happens - still lighted screen with nothing else. The backside is hot during both reboots, so something is definitely happening using CPU cycles, but I'm not sure what. Should I dirty reflash next?
Click to expand...
Click to collapse
Sent from my LEX727 using XDA Labs
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
bonuzzz said:
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
Click to expand...
Click to collapse
I'm not using this ROM, just happened to see the thread
Sent from my LEX727 using XDA Labs
bonuzzz said:
@maxximboy black screen after bootloader without any reboots?
Click to expand...
Click to collapse
no no black or blank screen, it wont flash the rom, message was something like, my p600 is not compatible.
View attachment tombstones.zip
View attachment last_kmsg.txt
bonuzzz said:
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
Click to expand...
Click to collapse
Hre's those files. After the second black blank screen that I mentioned in my previous post, I rebooted to recovery and grabbed these from the file manager. There's 10 tombstone files in the folder so I zipped it up. Hope it helps.
I am really excited about this rom, and cant wait to flash it on my p600..... i am not techies as you guys, so my question is, what do i need to do to make it work?
thanks all
maxximboy said:
I am really excited about this rom, and cant wait to flash it on my p600..... i am not techies as you guys, so my question is, what do i need to do to make it work?
thanks all
Click to expand...
Click to collapse
It need proper kernel ...patience
I need a tester, who will spend some time to flash couple of builds. write in pm
thanks in advance
TWRP has come to the SM-G360P!
In order to install this, follow these instructions:
Enable OEM Unlock in developer settings
Enter download mode (Press and hold home + volDown + Power when powered off)
Using Odin, click the 'AP' tab and select the twrp-3.1.1-0-coreprimeltespr.tar file you've downloaded.
Flash the TWRP image, then hold home + volUp + Power
Congratulations, you are now booted into TWRP!
BUGS:
None, as far as I'm aware.
DOWNLOAD
If you appreciate any of what I've done for this device and wish to buy me a coffee or something of the sort, you can donate to me at [email protected] (Paypal)
XDA:DevDB Information
TWRP for coreprimeltespr, Tool/Utility for the Samsung Galaxy Core Prime
Contributors
minz1
Source Code: https://github.com/minz1/android_device_samsung_coreprimeltespr-twrp
Version Information
Status: Stable
Created 2018-02-18
Last Updated 2018-02-18
NOTE: Every time you first turn on TWRP, you'll have to turn the display on then off for the touchscreen to work.
This TWRP seems to function just fine, but when I boot to twrp it gets stuck in a recovery bootloop and the only way to get it to boot to the system is to reflash the image with Odin. Have you had this issue, and if so is there a fix? I'm really good at modding ROMs but have never built a recovery. I do have a TWRP 2.8 for the device that has some minor bugs like clock and stuff but it reboots correctly. Maybe you could compare the two and try to fix the 3.1.
RealWelder said:
This TWRP seems to function just fine, but when I boot to twrp it gets stuck in a recovery bootloop and the only way to get it to boot to the system is to reflash the image with Odin. Have you had this issue, and if so is there a fix? I'm really good at modding ROMs but have never built a recovery. I do have a TWRP 2.8 for the device that has some minor bugs like clock and stuff but it reboots correctly. Maybe you could compare the two and try to fix the 3.1.
Click to expand...
Click to collapse
Sorry, I haven't had that issue at all.
minz1 said:
Sorry, I haven't had that issue at all.
Click to expand...
Click to collapse
Interesting. I'm gonna try and reflash it, I may know what the issue is. The first time, I extracted it and used Flashify...and then used Odin because I couldn't get back to the system. I used the TWRP to go directly to DL mode when I Odin flashed it instead of doing the vol-, home, and power routine. Maybe there lies the issue. I'll report back in a bit.
Sent from my SM-G360P using Tapatalk
---------- Post added at 01:19 PM ---------- Previous post was at 12:51 PM ----------
minz1 said:
Sorry, I haven't had that issue at all.
Click to expand...
Click to collapse
There is definitely some kind of issue, regardless of how I flash it...it just reboots back into TWRP. I haven't tried to make a backup with it, but I used it's terminal to flash my other image back on...it seems to be a good working TWRP, it's just giving me the problem of not being able to boot to anything else except DL mode. Hopefully we can figure out, I'd like to use it since it's newer than the 2.8 I'm using.
Sent from my SM-G360P using Tapatalk
---------- Post added at 01:36 PM ---------- Previous post was at 01:19 PM ----------
I just figured out something else, it seems if you only boot to it with the button combination it's works fine, but if you use any other means (adb, terminal, etc.) to boot into TWRP it will endlessly boot back into itself.
Sweet!
I was having the same problem, however, I think you figured out the solution, awesome job man! Thanks =P
RealWelder said:
This TWRP seems to function just fine, but when I boot to twrp it gets stuck in a recovery bootloop and the only way to get it to boot to the system is to reflash the image with Odin. Have you had this issue, and if so is there a fix? I'm really good at modding ROMs but have never built a recovery. I do have a TWRP 2.8 for the device that has some minor bugs like clock and stuff but it reboots correctly. Maybe you could compare the two and try to fix the 3.1.
Click to expand...
Click to collapse
Just wanted to drop in and say that I used to have the 360t1 which was the metro pcs version of this phone and across the entire device line up there was an issue with using any method except the hardware keys (ie: the vol up/down, home, and power combinations) to boot to recovery or download mode it would cause an endless boom loop. I am %100 certain that is the problem here. If I remember reading correctly it was something with the way the kernel was compiled or something that caused this issue and it was at such a deep level in the kernel that it was something that would happen even with custom kernels. So to the OP it's not your build of the recovery that os the cause. Nice work by the way. Glad to see more people getting their hands dirty with development for lower end devices. So as a rule of thumb with the core prime always use the hardware keys to reboot to any mode. NEVER USE ANY third party app to reboot, not even just to reboot. Hope this was helpful for you. Happy modding!!!