[P5100][CWM Advanced Edition] PhilZ Touch - Galaxy Tab 2 10.1" Android Development

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
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
Since many requests to port it to P5100, here it is released
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
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:
P5100 - P5110 - P5113
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Dualboot edition by @ketut.kumajaya
http://forum.xda-developers.com/showthread.php?p=42012268#post42012268
Click to expand...
Click to collapse

Great work bro.....thank you so much......
Sent from my GT-N7100 using xda premium

Philz you beauty! Welcome to the P5100 land! Finally something to look forward to in this otherwise zzzz P5100 forum. I was really planning to sell off this tablet due to the lack of top notch recoveries and kernels. Now I have eternal hope because Philz our saviour is here!
People, you just have to try his Kernels. He is a legend! Just check out the Note N7000 forums if you want to check out his fabulous work and fan following

About touch:
1- when you touch a menu to select: is the selection precise and working as expected
2- bottom virtual buttons: do they work as expected?
3- If it is slow, try to reduce the Scroll Sensitivity setting and reduce menu height. Play with both to find a sweet point¨
Try to describe what happens with precision. A video would even be better, so that I can get what you mean. I won't be able to help much as I do not have the device, without these

Here are the screenshots. The touch works perfect. There's no lag whatsoever. The bottom navigation buttons work as they should. Hopefully we'll be gifted with a Kernel soon

This works great on my 5113. The Aroma file manager seems really useful. I wasn't totally sure how to set it up so I'll write the steps here in case anyone else is wondering.
I downloaded the zip from here: http://forum.xda-developers.com/showthread.php?t=1646108
You can "install" the zip file from recovery which really just runs the file manager. It doesn't really install anything. When you exit you go back to recovery.
However, if you want to use it from inside PhilZ's recovery do this:
Go to /sdcard/clockworkmod
Create a directory called .aromafm
Copy the zip file you downloaded into that directory
Change the name of the zip file to aromafm.zip
Now you can use the Aroma FM menu item from the recovery to launch the file manager. The first time you run it from a new location you get the "help" overlay screen. I did the above steps in the file manager itself. Pretty cool. And having a terminal from inside recovery is great when you need to fix something and aren't at home.

aashayjardosh said:
Here are the screenshots. The touch works perfect. There's no lag whatsoever. The bottom navigation buttons work as they should. Hopefully we'll be gifted with a Kernel soon
Click to expand...
Click to collapse
Big thanks for the screen shots. At least I can see how the display is looking
I decided on purpose to not enlarge the bottom buttons as I thought it would be harder to use them if spread along all the width. Is it ok?
As for menu toggle options not being completely right aligned, it is a limitation in current stock CWM, and I feel no need to increase the buffer to make it right align
wd5gnr said:
This works great on my 5113. The Aroma file manager seems really useful. I wasn't totally sure how to set it up so I'll write the steps here in case anyone else is wondering.
I downloaded the zip from here: http://forum.xda-developers.com/showthread.php?t=1646108
You can "install" the zip file from recovery which really just runs the file manager. It doesn't really install anything. When you exit you go back to recovery.
However, if you want to use it from inside PhilZ's recovery do this:
Go to /sdcard/clockworkmod
Create a directory called .aromafm
Copy the zip file you downloaded into that directory
Change the name of the zip file to aromafm.zip
Now you can use the Aroma FM menu item from the recovery to launch the file manager. The first time you run it from a new location you get the "help" overlay screen. I did the above steps in the file manager itself. Pretty cool. And having a terminal from inside recovery is great when you need to fix something and aren't at home.
Click to expand...
Click to collapse
Yes, but you can also just double tap outside menu area, and it will launch aroma

Phil3759 said:
Yes, but you can also just double tap outside menu area, and it will launch aroma
Click to expand...
Click to collapse
Forgot about that, but you still have to do the setup to put the zip file with the right name in the hidden directory, no?

wd5gnr said:
Forgot about that, but you still have to do the setup to put the zip file with the right name in the hidden directory, no?
Click to expand...
Click to collapse
yes, sure
So, for p5100, you confirm that touch works as expected? Even the double tap and other shortcuts I guess

Phil3759 said:
yes, sure
So, for p5100, you confirm that touch works as expected? Even the double tap and other shortcuts I guess
Click to expand...
Click to collapse
Yes, the touch works perfect. Flashed 2-3 ROM's just for fun for testing it. The double tap and other shortcuts (the ones i checked) are all cool.
And yes the bottom navigation buttons are also good at this size. Infact they're perfect for the wider screen. Cheers!

Phil3759 said:
yes, sure
So, for p5100, you confirm that touch works as expected? Even the double tap and other shortcuts I guess
Click to expand...
Click to collapse
Yes, all work great.

wd5gnr said:
Yes, all work great.
Click to expand...
Click to collapse
Actually, I may have found a problem related to the 5113. I have installed some kernels through this recovery but when I went to install the latest CM nightly I get an assert failure where it is looking for p5110 or p5113. I've installed many of these in the past. I may revert to old CWM and see if it works, but I feel it must be related to this recovery, perhaps because it doesn't know I have a 5113?
Update: Reverting to normal stock worked.

wd5gnr said:
Actually, I may have found a problem related to the 5113. I have installed some kernels through this recovery but when I went to install the latest CM nightly I get an assert failure where it is looking for p5110 or p5113. I've installed many of these in the past. I may revert to old CWM and see if it works, but I feel it must be related to this recovery, perhaps because it doesn't know I have a 5113?
Update: Reverting to normal stock worked.
Click to expand...
Click to collapse
Just delete the assert line from your updater-script file in zip
For other variants, follow instructions and i will release for your phone
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
Just delete the assert line from your updater-script file in zip
For other variants, follow instructions and i will release for your phone
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I have done that before for other reasons. Just thought I'd mention it.

wd5gnr said:
Yeah I have done that before for other reasons. Just thought I'd mention it.
Click to expand...
Click to collapse
CM ROMs have an extra safety check which cant be avoided by deleting assert prop lines in updater script.
It's under META-INF\com\android\metadata
With N7000 it shows this - "post-build=samsung/GT-N7000/GT-N7000:4.0.3/IML74K/ZCLP6:user/release-keys
post-timestamp=1364279894
pre-device=GT-N7000

Phil3759 said:
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
Since many requests to port it to P5100, here it is the first release, untested by me
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: Flash at your own risk, this is a first release, untested
http://www.mediafire.com/file/bj7vnfal8ca8h4q/philz_touch_4.90.8-p5100.tar.md5
http://www.mediafire.com/file/mc71ezq8eg6oqo8/philz_touch_4.90.8-p5100.zip
Click to expand...
Click to collapse
Great my bro but it possible to make for Tab 2 gt-p5110 pleassssseeeeeee.
thanks for your hard work

The one for 5100 doesn't work? There are no big diff, recovery wise
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
The one for 5100 doesn't work? There are no big diff, recovery wise
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
ok i test tonight and reply here ok philz ?
thanks
you think i can use my custom res of my note 2 with your recovery ? (with my config of your recovery for have fonts ustom background red etc etc same as your recovery note 2?)

brolee93 said:
ok i test tonight and reply here ok philz ?
thanks
you think i can use my custom res of my note 2 with your recovery ? (with my config of your recovery for have fonts ustom background red etc etc same as your recovery note 2?)
Click to expand...
Click to collapse
Just ensure the resolution, since it is inverted. Let me know and eventually post a screen shot
By the way, since you have a note 2. Can you let me know your opinion about touch difference between note 2 and this one?
Also, if you post a recent recovery.img from sammobile.com, i will repack for p5110 if needed
Sent from my GT-I9100 using Tapatalk 2

ok i see

Related

[Kernel] Samsung Galaxy Exhibit 4G rooted kernels v1.3/v1.5

Please go HERE for the Galaxy Exhibit Rooted Kernel.
reserved
<reserved>
Update
<reserved>
jocala said:
Linked below is a rooted kernel, the easy method to root your Samsung Exhibit II 4g!
Simply copy the zip file to your internal or external sdcard and reboot into recovery. Choose install zip from the menu and select the t679-root zip file. When it completes, you are rooted! Also installed are Busybox, Superuser.apk and su. Additionally, when finished you will have ClockworkMod 5.5.0.4 installed as well.
To boot into recovery, press and hold Vol-up then press power. After the plain white samsung logo appears, continue to hold the keys for two or three seconds then release. Recovery should start. However, sometimes recovery is balky...it may take more than one try.
This kernel is suitable for any stock (or stockish) Samsung Exhibit II 4g. Feel free to use it for your own projects. I don't insist on credit, but I do appreciate it.
[/B]
Click to expand...
Click to collapse
Sorry to sound ridiculous, but what exactly does this do for my phone? What benefits do I get?
Also it should probably be noted with the instructions to boot into recovery that (at least on my phone) you need to press the menu button after the Samsung logo disappears and the little android guy with an arrow and a box comes up
hotsauce126 said:
Also it should probably be noted with the instructions to boot into recovery that (at least on my phone) you need to press the menu button after the Samsung logo disappears and the little android guy with an arrow and a box comes up
Click to expand...
Click to collapse
Yep. That's been noted elsewhere, and I plumb forgot. Thanks for the reminder!
Faultyy said:
Sorry to sound ridiculous, but what exactly does this do for my phone? What benefits do I get?
Click to expand...
Click to collapse
EDIT: Please see the feature list in the OP.
jocala said:
Linked below is a rooted kernel, the easy method to root your Samsung Exhibit II 4g!
Simply copy the zip file to your internal or external sdcard and reboot into recovery. Choose install zip from the menu and select the t679-root zip file. When it completes, you are rooted! Also installed are Busybox, Superuser.apk and su. Additionally, when finished you will have ClockworkMod 5.5.0.4 installed as well.
To boot into stock recovery, press and hold Vol-up then press power. After the plain white samsung logo appears, continue to hold the keys for two or three seconds then release. Recovery should start. However, sometimes recovery is balky...it may take more than one try. When you see the box with the protruding arrow, press your menu key, far-left on the capacitive menubar.
This kernel is suitable for any stock (or stockish) Samsung Exhibit II 4g. Feel free to use it for your own projects. I don't insist on credit, but I do appreciate it.
Download HERE
Click to expand...
Click to collapse
Great.... Thanks so much, but besides the rooting and ClockworkMod , how is this Kernel different from the original stock one?
Overclock question
jocala said:
Linked below is a rooted kernel, the easy method to root your Samsung Exhibit II 4g!
Simply copy the zip file to your internal or external sdcard and reboot into recovery. Choose install zip from the menu and select the t679-root zip file. When it completes, you are rooted! Also installed are Busybox, Superuser.apk and su. Additionally, when finished you will have ClockworkMod 5.5.0.4 installed as well.
To boot into stock recovery, press and hold Vol-up then press power. After the plain white samsung logo appears, continue to hold the keys for two or three seconds then release. Recovery should start. However, sometimes stock recovery is balky...it may take more than one try. Some say that holding the capacitive home key in addition to power & vol-up helps enter stock recovery as well. When you see the box with the protruding arrow, press your menu key, far-left on the capacitive menubar.
This kernel is suitable for any stock (or stockish) Samsung Exhibit II 4g. Feel free to use it for your own projects. I don't insist on credit, but I do appreciate it.
Download HERE
Click to expand...
Click to collapse
Is this kenrnel overclockable? I took installed rebelrom, then flashed your kernel over it. everything works, but when I use setcpu or any other program like that it still shows 1024Mhz as max, do I have to edit the kernel somewhere to change the max value?
jocala said:
Linked below is a rooted kernel, the easy method to root your Samsung Exhibit II 4g!
Simply copy the zip file to your internal or external sdcard and reboot into recovery. Choose install zip from the menu and select the t679-root zip file. When it completes, you are rooted! Also installed are Busybox, Superuser.apk and su. Additionally, when finished you will have ClockworkMod 5.5.0.4 installed as well.
To boot into stock recovery, press and hold Vol-up then press power. After the plain white samsung logo appears, continue to hold the keys for two or three seconds then release. Recovery should start. However, sometimes recovery is balky...it may take more than one try. When you see the box with the protruding arrow, press your menu key, far-left on the capacitive menubar.
This kernel is suitable for any stock (or stockish) Samsung Exhibit II 4g. Feel free to use it for your own projects. I don't insist on credit, but I do appreciate it.
Download HERE
Click to expand...
Click to collapse
This is working on XquiziT...
Nice work and thanks!
ganovim said:
Great.... Thanks so much, but besides the rooting and ClockworkMod , how is this Kernel different from the original stock one?
Click to expand...
Click to collapse
Please see the feature list in the OP.
accessdenied12 said:
Is this kenrnel overclockable? I took installed rebelrom, then flashed your kernel over it. everything works, but when I use setcpu or any other program like that it still shows 1024Mhz as max, do I have to edit the kernel somewhere to change the max value?
Click to expand...
Click to collapse
Glad to hear it's working with Rebel, I'd like this kernel to be ROM-agnostic. When I installed over Rebel, my keboard failed when I tried to sign in to my wifi hotspot.
Overclock, not yet. Underclock, yes, just like in stock.
Wildchld said:
This is working on XquiziT...
Nice work and thanks!
Click to expand...
Click to collapse
Thank you for giving it a whirl
It's always something...
[deleted] this post referred to a deleted patch....
How about adding TUN/TAP support? Thanks.
mbuugg said:
How about adding TUN/TAP support? Thanks.
Click to expand...
Click to collapse
Already there, forgot to list it. Thanks!
I'm trying to learn as much as possible about this phone so I'm curious and asking. In the end how did you fix the problem of initramfs you had ?
Did you compile from samsung sources ? If yes, did you make a lot of modifications to the code ? If not did you do it another way ?
Nilpotent said:
I'm trying to learn as much as possible about this phone so I'm curious and asking. In the end how did you fix the problem of initramfs you had ?
Did you compile from samsung sources ? If yes, did you make a lot of modifications to the code ? If not did you do it another way ?
Click to expand...
Click to collapse
Samsung sources, yes. No mods yet, just module compiles. Working on cpufreq now.
stock phone:
I put the zip on root dir of my sd card via pc, enter stock recovery and choose install update, but when i navigate to the sdcard, there are no files or directories.
Any thoughts?
killi said:
stock phone:
I put the zip on root dir of my sd card via pc, enter stock recovery and choose install update, but when i navigate to the sdcard, there are no files or directories.
Any thoughts?
Click to expand...
Click to collapse
Are you telling it to install update.zip? Look for an option to select zip file. (right now I'm not running stock.)

[CWM] CWM-based Recovery for RK3188/RK3066/RK2928/RK2926/RK2918/RK2906

Mod Edit: Link removed
all credit goes to original CWM author koush and all its contributors. but they have no responsibility for this CWM-based Recovery. use this CWM-based Recovery at your own risk.
this CWM-based Recovery can write raw MTD partition such as kernel, boot, and recovery on RK3188, RK3066, RK2928, RK2926, RK2918, and RK2906 devices without any problem. this can be installed without Windows.
if you want to install zip with edify script which writes something to raw MTD partition, you have to use update-binary and/or flash_image included in this CWM-based Recovery image.
please see my site for detail.
* Known issues (2013/2/11)
- timestamp
backup may be named as 1970-01-01.xx.xx.xx. it's just a directory name on SD card. please rename it.
- dump_image
it says "mtd: read error (No such file or directory)" at the end. please ignore it, it should not be a problem.
* How to controll
- mouse
move up/down: up/down
left click: select
right click: back
- keyboard
cursor up/down: up/down
cursor left/enter: select
cursor right: back
- touch screen
swipe up/down: up/down
swipe left: select
swipe right: back
- button
volume up/down: up/down
power: select
back: back
- remote controller
up/down: up/down
left/ok: select
back: back
* about tools to make device specific image
you can use any tools which can be used to make custom rom for Rockchip devices. I'm using rkunpack, rkcrc, unpackbootimg, and mkbootimg.
if you don't know how to make custom rom for Rockchip devices, please ask google. many developers are already making custom rom for Rockchip devices, many information is already floating around.
where to download rkflash, rkflashtool, or RKAndroidTool.exe
CWM on my mk808b could be great, thanks!
Can any anyone please point me to where to download any of these tools?:
magnemann said:
CWM on my mk808b could be great, thanks!
Can any anyone please point me to where to download any of these tools?:
Click to expand...
Click to collapse
if you want to know how to install CWM, please read "how to install" page on my site, and try "from root shell" method.
if you want to know about these tools, I'll add more information including them on my site. but it will be done little by little.
and I think here is not the best place to talk about other topics. please try search box on XDA, or google.
regards,
fun_ said:
if you want to know how to install CWM, please read "how to install" page on my site, and try "from root shell" method.
if you want to know about these tools, I'll add more information including them on my site. but it will be done little by little.
and I think here is not the best place to talk about other topics. please try search box on XDA, or google.
regards,
Click to expand...
Click to collapse
Thanks alot for info! I'll try 'from root shell' method. Seems like the easiest way. :laugh:
How do i boot into CWM if stuck at boot?
I know I can do it with 'reboot'->recovery with reboot-app in finless 1.5. But I've been troubled with freeze at boot sometimes with no other option than to reflash rom.
magnemann said:
How do i boot into CWM if stuck at boot?
I know I can do it with 'reboot'->recovery with reboot-app in finless 1.5. But I've been troubled with freeze at boot sometimes with no other option than to reflash rom.
Click to expand...
Click to collapse
I only have a MK806. it has a button to boot recovery and bootloader. but sorry I don't know about other device...
if you are sure there is no button, then you need to flash some misc.img with USB flash tool.
sorry, I'm busy a little. please search about RKAndroidTool for RK3066 on google.
I got a report on another forum, this CWM works fine on MK808B.
backup will be named as "1970-01-01.xx.xx.xx" on (at least) MK806 and MK808B.
I'll investigate it. for now please rename it from PC or any explorer app. it's just a directory name on SD card.
Ah, a new cwm for my rk2918 device.
Thanks to fun_ stuff.
JDfense
http://androtab.info/clockworkmod/rockchip/
2013/1/19
update updater-script
add images for MK802III and UG007
latest stock rom for MK802III and UG007 has /system/etc/install-recovery.sh. it restores stock recovery on every boot. then, you need to disable it e.g.
Code:
chmod 644 /system/etc/install-recovery.sh
otherwise, installed CWM is erased and stock recovery is restored after reboot.
I added above code into updater-script in all my CWM.zip. if you install CWM.zip from CWM or adb sideload, it will be done automatically.
if you flash recovery.img from shell or rk tools, you need to do it manually.
if you update your device, install-recovery.sh may be re-enabled. then, you need to disable it again.
----
at this time all images are updated, but only updater-script in zip is changed. if you already installed CWM, no need to install this version.
hi fun!
I was wondering if I provide you with the parameter file and any other files you need if you could modify the build for our Minix Neo X5 device? thanks man!!
onelovekir said:
I was wondering if I provide you with the parameter file and any other files you need if you could modify the build for our Minix Neo X5 device?
Click to expand...
Click to collapse
I added images for NEO G4 and NEO X5. please try.
EDIT:
I noticed NEO G4 and NEO X5 have remote controller. can you try it?
if it doesn't work well, please try "Advanced Menu > key test" and tell me relation between button and key code.
probably VOL+/-, POWER and BACK can be used on this version, but DPAD up/down/left/right/ok will not work.
EDIT2:
little off-topic, X5 looks nice for me. is there any "take apart" pics?
EDIT3:
http://minixforums.com/threads/neo-x5-mod-heatsink-for-cpu.60/ interesting
hmm I want to see another side
http://androtab.info/clockworkmod/rockchip/
2013/01/20
CWM.zip can be installed from stock recovery (it may not work on some device)
if you already installed CWM, no need to install it.
fun_ said:
I added images for NEO G4 and NEO X5. please try.
EDIT:
I noticed NEO G4 and NEO X5 have remote controller. can you try it?
if it doesn't work well, please try "Advanced Menu > key test" and tell me relation between button and key code.
probably VOL+/-, POWER and BACK can be used on this version, but DPAD up/down/left/right/ok will not work.
EDIT2:
little off-topic, X5 looks nice for me. is there any "take apart" pics?
EDIT3:
http://minixforums.com/threads/neo-x5-mod-heatsink-for-cpu.60/ interesting
hmm I want to see another side
Click to expand...
Click to collapse
there is some take apart pics somewhere...let me see if I can find them. thanks for your help and I will test the new build today.
and oh yeah btw...X5 is very nice
for all,
if you can, please try to install from stock recovery. I hope it should be easy and it will work on all RK3066 products/stock roms.
but it doesn't work (invalid message) on Yuandao N50 RK2918 tablet.
I want to know that it works or doesn't work on which product/rom as much as possible.
fun_ said:
I added images for NEO G4 and NEO X5. please try.
EDIT:
I noticed NEO G4 and NEO X5 have remote controller. can you try it?
if it doesn't work well, please try "Advanced Menu > key test" and tell me relation between button and key code.
probably VOL+/-, POWER and BACK can be used on this version, but DPAD up/down/left/right/ok will not work.
EDIT2:
little off-topic, X5 looks nice for me. is there any "take apart" pics?
EDIT3:
http://minixforums.com/threads/neo-x5-mod-heatsink-for-cpu.60/ interesting
hmm I want to see another side
Click to expand...
Click to collapse
ok after further testing, your build so far looks good (although I haven't yet tried to flash a zip file). I just have been trying to get the keys right on the remote that it comes with. I have all the key test functions if you would like to rebuild the X5 version. up/down on the d-pad give you up/down on the screen. left on the d-pad is the select or ok button for CWM.
Re: [CWM] CWM-based Recovery for RK3066/RK2918 devices
fun_ said:
for all,
if you can, please try to install from stock recovery. I hope it should be easy and it will work on all RK3066 products/stock roms.
but it doesn't work (invalid message) on Yuandao N50 RK2918 tablet.
I want to know that it works or doesn't work on which product/rom as much as possible.
Click to expand...
Click to collapse
It works for the Minix Neo X5 perfectly! We just gotta get those keys straightened out.
HTC EVO LTE with Tapatalk
onelovekir said:
ok after further testing, your build so far looks good (although I haven't yet tried to flash a zip file). I just have been trying to get the keys right on the remote that it comes with. I have all the key test functions if you would like to rebuild the X5 version. up/down on the d-pad give you up/down on the screen. left on the d-pad is the select or ok button for CWM.
Click to expand...
Click to collapse
well, my English is not so good. I'm sorry asking again, d-pad up/down/left/right on remote worked on this version?
I want to see key test result.
onelovekir said:
It works for the Minix Neo X5 perfectly! We just gotta get those keys straightened out.
Click to expand...
Click to collapse
my CWM.zip (renamed to update.zip) can be installed from X5 stock recovery, right?
anyway, thank you for your cooperation!
Re: [CWM] CWM-based Recovery for RK3066/RK2918 devices
fun_ said:
well, my English is not so good. I'm sorry asking again, d-pad up/down/left/right on remote worked on this version?
I want to see key test result.
my CWM.zip (renamed to update.zip) can be installed from X5 stock recovery, right?
anyway, thank you for your cooperation!
Click to expand...
Click to collapse
Yes the up/down/left arrows work but not the right (i think cuz we don't need a fourth function), but ONLY (so far) on the stock remote that comes with the X5. Yes changing to update.zip works and I will get you the key test results in a little bit.
Thanks again for your work!
HTC EVO LTE with Tapatalk

[RECOVERY] Cannibal Open Touch Recovery for ZTE V967S

DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
UPDATE:
I updated the recovery to a new version, more stable, with CWM 6.0.4.4 basic structure (updated by me).
After a hard work with many failed builds, I succeded to compile from source a fully working recovery with touch support for ZTE V967S. I used for this the Project Open Cannibal source, named Cannibal Open Touch Recovery. It's a well done recovery, compatible with CWM, with usefull functions: for example advanced backup - you can backup only that partition you want, posibility to use themes, etc.​
Here you can see more images of the recovery, from a device with smaller screen, but you can check the options.
Touch navigation is made by touching bottom buttons menu, just like in Philz recovery or similar. First button is for exit or go back, second is key down, third key up and last is select or enter. Now you can save your phone buttons.
You should read this:
First time you boot in recovery will be a touchscreen calibration set up: you have to touch three times the red square. Also, first time you do a backup, it will take a little longer time, because it will be create directory structure and free up the space. After that it will be a joy, is fast, is powerfull, is full of options and is funny.​
CREDITS:
Project Open Cannibal who release and mantains this wonderful recovery.
Sblood86 for his help.
C3C076 for his help on tweaking recovery source.
bgcngm for his unpacking tool.​​Download from attachment.
Deleted.
Need your Help Master
Great to Have you Master in our MTK Community.
Today as master @yuweng told us try to port this recovery to our MT6577 Device with his auto port tool, but I failed doing so with that tool. So master will you assist me in doing these things for my device. I don't have a linux system and neither my Lappy is accepting it in any form, not even on VM.
My Device Info:-
Micromax A110
Resolution :- 480*854
MT6577 Device with JB 4.1 & 4.2.
Will please help in this. As I failed in philz recovery. So asking for your help here in this recovery also.
Thanks a ton for your time and for this awesome recovery.
BOND1987 said:
Great to Have you Master in our MTK Community.
Today as master @yuweng told us try to port this recovery to our MT6577 Device with his auto port tool, but I failed doing so with that tool. So master will you assist me in doing these things for my device. I don't have a linux system and neither my Lappy is accepting it in any form, not even on VM.
My Device Info:-
Micromax A110
Resolution :- 480*854
MT6577 Device with JB 4.1 & 4.2.
Will please help in this. As I failed in philz recovery. So asking for your help here in this recovery also.
Thanks a ton for your time and for this awesome recovery.
Click to expand...
Click to collapse
Thanks for appreciations,
This recovery is underestimated by users, but is very good. Only one thing, is dependat on display resolution. For your device this is not gonna work. Try this one here. I did it for yuweng to test his device (Ihope he will not be upset). But don't use the port tool. Instead, unpack it with michfood tool, change in ramdisk my files with yours from original or a working recovery (recovery.fstab from dev folder, and from root all files that are not for your phone except init executable), repack it and see if it works.
carliv said:
Thanks for appreciations,
This recovery is underestimated by users, but is very good. Only one thing, is dependat on display resolution. For your device this is not gonna work. Try this one here. I did it for yuweng to test his device (Ihope he will not be upset). But don't use the port tool. Instead, unpack it with michfood tool, change in ramdisk my files with yours from original or a working recovery (recovery.fstab from dev folder, and from root all files that are not for your phone except init executable), repack it and see if it works.
Click to expand...
Click to collapse
Thanks for your help master, I did like you said but other than touch screen, everything is working fine. Now need your suggestion on this. Got this recovery and really saying, users have under estimated it cause it have great potentials for future.
Also will like to know how to create a theme for this recovery, as, I am themer and know for my theming only.
BTW, Hats off to you Master. Recovery is awesome. And Touch will make it great further.
BOND1987 said:
Thanks for your help master, I did like you said but other than touch screen, everything is working fine. Now need your suggestion on this. Got this recovery and really saying, users have under estimated it cause it have great potentials for future.
Also will like to know how to create a theme for this recovery, as, I am themer and know for my theming only.
BTW, Hats off to you Master. Recovery is awesome. And Touch will make it great further.
Click to expand...
Click to collapse
Hm, I'm a little bit confused. Which recovery did you tried to port: mine from here from first post or the one I gave you that link? Because mine is for 540x960 resolution and the one from link is for 480x854. If you port that one it should work touch screen. Attention! is not the same as koush touch recovery, the touch area is only for those four nav buttons from bottom, like in early philz recoveries. I read that ProjectOpenCannibal's next recovery will be full screen touch and much improved.
For theme you need to create a folder in cotrecovery folder on sdcard, name it themes and look here https://github.com/ProjectOpenCannibal/sdcard_themes to see how a theme should look, then create one for your resolution and apply from recovery=>COT settings=>theme=>sdcard theme.
carliv said:
Hm, I'm a little bit confused. Which recovery did you tried to port: mine from here from first post or the one I gave you that link? Because mine is for 540x960 resolution and the one from link is for 480x854. If you port that one it should work touch screen. Attention! is not the same as koush touch recovery, the touch area is only for those four nav buttons from bottom, like in early philz recoveries. I read that ProjectOpenCannibal's next recovery will be full screen touch and much improved.
For theme you need to create a folder in cotrecovery folder on sdcard, name it themes and look here https://github.com/ProjectOpenCannibal/sdcard_themes to see how a theme should look, then create one for your resolution and apply from recovery=>COT settings=>theme=>sdcard theme.
Click to expand...
Click to collapse
No Sir I am not getting any touch in the below navigation buttons and a new problem also arised just now. Now all bitmap of recovery is not able to find any image inside the recovery. Do you know what problem is it actually....???
Its says like "E/ Couldn't able to find bitmap icon_overlay01.
Though I cross checked all are there.
I am using recovery of Master Yuweng that you suggested few post back.
EDIT:-
Got the Images back after installing the default theme. Actually I selected the theme RED but it was not there so it was saying like that. Now will create a theme and share to you also. BTW how can I adjust size and something to do with touch also...
Master You are awesome and your creations also.
BOND1987 said:
No Sir I am not getting any touch in the below navigation buttons and a new problem also arised just now. Now all bitmap of recovery is not able to find any image inside the recovery. Do you know what problem is it actually....???
Its says like "E/ Couldn't able to find bitmap icon_overlay01.
Though I cross checked all are there.
Click to expand...
Click to collapse
That error appear when you select sdcard theme but there is no theme on sdcard. You see first position "Boot Android", navigate with volume buttons volume up two times, power button to enter, volume down once, power to enter, volume down once, power button enter, select hydro press power and now you should see back all images.
I saw in yuweng post that he didn't gave you that link, so if he didn't gave it to you by pm, I don't think you have the right recovery to port.
Look I'll give you again, please try with this COT Recovery 480x854. The reason the touch won't work in your actual ported recovery is because you use mine and the touch area is out of your screen.
If you have that one (named yuweng-recovery.img) and the ported one don't work that must be related to your phone touch module location, and I will have to documents on this when I have time.
carliv said:
That error appear when you select sdcard theme but there is no theme on sdcard. You see first position "Boot Android", navigate with volume buttons volume up two times, power button to enter, volume down once, power to enter, volume down once, power button enter, select hydro press power and now you should see back all images.
I saw in yuweng post that he didn't gave you that link, so if he didn't gave it to you by pm, I don't think you have the right recovery to port.
Look I'll give you again, please try with this COT Recovery 480x854. The reason the touch won't work in your actual ported recovery is because you use mine and the touch area is out of your screen.
If you have that one (named yuweng-recovery.img) and the ported one don't work that must be related to your phone touch module location, and I will have to documents on this when I have time.
Click to expand...
Click to collapse
Just a last question Master,
Sorry for bothering you in everything. Do we have to replace the kernel files also or not...
Cause I am replacing that also So it could be the reason that touch is not working.....????
BOND1987 said:
Just a last question Master,
Sorry for bothering you in everything. Do we have to replace the kernel files also or not...
Cause I am replacing that also So it could be the reason that touch is not working.....????
Click to expand...
Click to collapse
Of course you should pack with your kernel, you only need my ramdisk. I don't think it's about kernel, I think is that resolution thing. In my first builds I didn't setup resolution, for debugging reason, and I didn't have touch either, but after setting correct width and height, everything worked like a charm. I'm using this recovery since I compiled and I'm very happy. The part I like most is the possibility to backup only that partition you want (if I want to backup data I can select to backup only data).
Good luck on porting. I hope this time it will work.
carliv said:
Of course you should pack with your kernel, you only need my ramdisk. I don't think it's about kernel, I think is that resolution thing. In my first builds I didn't setup resolution, for debugging reason, and I didn't have touch either, but after setting correct width and height, everything worked like a charm. I'm using this recovery since I compiled and I'm very happy. The part I like most is the possibility to backup only that partition you want (if I want to backup data I can select to backup only data).
Good luck on porting. I hope this time it will work.
Click to expand...
Click to collapse
Sorry to bother you again master,
But other than touch everything is working fine, may I know is it related to touch drivers or only resolutions.
Cause just checked my device specs and the resolution is saying "480*800" and the file that you gave me is 480*854 so because of this it is not working only for 54 pixels, though I know it's possible as like .9pngs.
If yes so please either do a favor and create another files with resolution "480*800" please.
The last favor please.....
BOND1987 said:
Sorry to bother you again master,
But other than touch everything is working fine, may I know is it related to touch drivers or only resolutions.
Cause just checked my device specs and the resolution is saying "480*800" and the file that you gave me is 480*854 so because of this it is not working only for 54 pixels, though I know it's possible as like .9pngs.
If yes so please either do a favor and create another files with resolution "480*800" please.
The last favor please.....
Click to expand...
Click to collapse
Aahh, there you go! Of course this is the reason. I will try to compile one for that resolution these days and I will post it here.
carliv said:
Aahh, there you go! Of course this is the reason. I will try to compile one for that resolution these days and I will post it here.
Click to expand...
Click to collapse
No Problem Master,
I can wait. I am posting this Recovery in my thread and Credits are yours and Master Yuweng's also for showing me this thread.
Thanks a ton for this awesome recovery.
BOND1987 said:
No Problem Master,
I can wait. I am posting this Recovery in my thread and Credits are yours and Master Yuweng's also for showing me this thread.
Thanks a ton for this awesome recovery.
Click to expand...
Click to collapse
Here it is COT Recovery 480x800 for MTK devices. I hope it works.
Enjoy porting.
carliv said:
Here it is COT Recovery 480x800 for MTK devices. I hope it works.
Enjoy porting.
Click to expand...
Click to collapse
Master,
Its same thing I am getting. Is there any file which is also responsible for making touch to work and one more thing master. There is no Navigation Bars in the new file.
But people have like the new recovery Master. Thanks & Lot for the Masterpiece work.
Here is My Thread :- Cannibal Open Touch Recovery
BOND1987 said:
Master,
Its same thing I am getting. Is there any file which is also responsible for making touch to work and one more thing master. There is no Navigation Bars in the new file.
But people have like the new recovery Master. Thanks & Lot for the Masterpiece work.
Here is My Thread :- Cannibal Open Touch Recovery
Click to expand...
Click to collapse
Well, you gave me wrong info. Your device does have resolution 480x854 not 480x800.
Delete cotrecovery folder from sdcard. Install back 480x854 ported recovery, boot in recovery and see if you get touch screen calibration (first thing after boot in recovery - a red square touch three times). Play a little with menu and boot back in Android. Now open cotrecovery folder from sdcard and give me the content of settings.ini file. Also tell me if your device has a /dev/input folder or tell me which folders do you have in /dev.
Just to test again, boot back in recovery and in COT settings do again touch screen calibration.
carliv said:
Well, you gave me wrong info. Your device does have resolution 480x854 not 480x800.
Delete cotrecovery folder from sdcard. Install back 480x854 ported recovery, boot in recovery and see if you get touch screen calibration (first thing after boot in recovery - a red square touch three times). Play a little with menu and boot back in Android. Now open cotrecovery folder from sdcard and give me the content of settings.ini file. Also tell me if your device has a /dev/input folder or tell me which folders do you have in /dev.
Just to test again, boot back in recovery and in COT settings do again touch screen calibration.
Click to expand...
Click to collapse
But Master, I am not able to touch the red dot, Its not responding. That's what I am saying that touch is not working in any version but in TWRP of ours touch is working fine. Here is the working touch TWRP recovery. May be it can help Master. Regarding I am still confused that its 480*800 or 480*854 but touch is not working in any of them.
Along with that I am uploading the whole dev/input folder and cotrecovery folder.
BOND1987 said:
But Master, I am not able to touch the red dot, Its not responding. That's what I am saying that touch is not working in any version but in TWRP of ours touch is working fine. Here is the working touch TWRP recovery. May be it can help Master. Regarding I am still confused that its 480*800 or 480*854 but touch is not working in any of them.
Along with that I am uploading the whole dev/input folder and cotrecovery folder.
Click to expand...
Click to collapse
Well, for some reason input directory is empty. This recovery has the same way as twrp to trigger touch.
Overwrite your settings.ini with the one attached (rename it to settings.ini).
Also give me your ported recovery.
carliv said:
Well, for some reason input directory is empty. This recovery has the same way as twrp to trigger touch.
Overwrite your settings.ini with the one attached (rename it to settings.ini).
Also give me your ported recovery.
Click to expand...
Click to collapse
Sir, After replacing the settings.ini in COTrecovery folder nothing changed. And I am attaching my ported recovery in the post. So Sir, do check it in your free time.
Thanks for supporting master or else I could never been able to port this recovery for us.
BOND1987 said:
Sir, After replacing the settings.ini in COTrecovery folder nothing changed. And I am attaching my ported recovery in the post. So Sir, do check it in your free time.
Thanks for supporting master or else I could never been able to port this recovery for us.
Click to expand...
Click to collapse
I need your device official boot.img and recovery.img
There is something wrong in your init.rc, but I need to look in those two files to be sure.

[tf700/tf700t][CWM Advanced Edition] PhilZ Touch

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
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:
Asus Transformer Prime TF700T (tf700t)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Phil3759 said:
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
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:
Click to expand...
Click to collapse
Will give it a test run.
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Frostbiter said:
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Click to expand...
Click to collapse
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Phil3759 said:
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Click to expand...
Click to collapse
Ah okay, well so far that's the only bug in the recovery I noticed, and I wouldn't have even noticed it if I had remembered to put the kitkat gapps on my device before wiping it. Haha
Really nice job though, I'm glad you brought it over since I've had issues with plain cwm in the past and twrp doesn't seem to be getting updated at the moment I thank you for bringing this to my tablet.
Thank you so much for this nice tool and give us choices. I flashed it and the UI is just beautiful. Now I'll go test all its functions.
:good:
Nice
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
lj50036 said:
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
Click to expand...
Click to collapse
Just tried this out using your zip to install. Works great. Recovery is nice and easy to navigate. Thanks to Phil and LJ.
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Thank you so much Philz!
I was dreaming about this, is not a joke, I've been using your amazing recovery in my jfltexx since always because it's the best.
I would be glad to help you.
Lord_Towers said:
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Click to expand...
Click to collapse
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
soyusado said:
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Lord_Towers said:
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Click to expand...
Click to collapse
LOL, i remember when i discovered that too face palm.
Is Philz touch coming to a 701t Near you?
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
SlappyWag said:
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
Click to expand...
Click to collapse
Open Terminal Emulator and enter this command
su
dd if=/storage/sdcard0/download/philz_touch_6.19.3-tf700t.img of=/dev/block/mmcblk0p4
Link is dead !
Another link ?
bump
Anyone got another link to this please?

[CASE CLOSED][Q] Possibility for SuperSU Pro Flashable ZIP?

Is it possible to insert the SuperSU Pro Key to flashable SuperSU (maybe with a little bit modification in the script?) so whenever I flash it, it is in Pro version automatically? No need for separate installation...
Odlanyer22 said:
Is it possible to insert the SuperSU Pro Key to flashable SuperSU (maybe with a little bit modification in the script?) so whenever I flash it, it is in Pro version automatically? No need for separate installation...
Click to expand...
Click to collapse
Why do you want pro.... You can enable all pro feature with out having pro key..... Check settings... It has an option for this...
Killwish said:
Why do you want pro.... You can enable all pro feature with out having pro key..... Check settings... It has an option for this...
Click to expand...
Click to collapse
So true sir...
There's no reason to answer why would I go to pro when I can enable pro features for free,,, when I have already the key.
What really matter for now is, if it possible to flash 2 apk in just 1 flashable zip.
I think its possible (somehow)... but I don't know how to create flashable zip. Moreover, I really don't know how to create additional script (or what script to be added) needed to be used in order for key be installed too while SuperSU is being flashed.
Seems like, I what to learn on how to create script that will command to install SuperSU then the key afterwards.
If I'm not mistaken (as I am not a developer or what but a totally noob)... commands/scripts in a flashable zip are written in .sh file?
Odlanyer22 said:
So true sir...
There's no reason to answer why would I go to pro when I can enable pro features for free,,, when I have already the key.
What really matter for now is, if it possible to flash 2 apk in just 1 flashable zip.
I think its possible (somehow)... but I don't know how to create flashable zip. Moreover, I really don't know how to create additional script (or what script to be added) needed to be used in order for key be installed too while SuperSU is being flashed.
Seems like, I what to learn on how to create script that will command to install SuperSU then the key afterwards.
If I'm not mistaken (as I am not a developer or what but a totally noob)... commands/scripts in a flashable zip are written in .sh file?
Click to expand...
Click to collapse
There is no ne to do this...... Just select any apk file abd put it to /system/app folder and restart your device
Would like to further understand something from this too
(i do have linux background)
Technically speaking, what is a rooted device? Is it having the su binary available? Is that what it means?
But then, supersu says that it needs a 'rooted device'.. this is quite rather confusing. doesnt supersu provide root access to apps?
couldnt you combine the key and the app using lucky patcher or a diffrent method?
My device:
Samsung Galaxy S2 Skyrocket (rooted)
Rom:AOSP
Carrier:At&t
Dont forget to thank me if i helped
Killwish said:
There is no ne to do this...... Just select any apk file abd put it to /system/app folder and restart your device
Click to expand...
Click to collapse
No luck... I flashed the SuperSU then push the key to system/app but the key didnt install itself.
That is why I am trying to fig.out how can I insert the key from the flashable zip.
biatche said:
Would like to further understand something from this too
(i do have linux background)
Technically speaking, what is a rooted device? Is it having the su binary available? Is that what it means?
But then, supersu says that it needs a 'rooted device'.. this is quite rather confusing. doesnt supersu provide root access to apps?
Click to expand...
Click to collapse
Not so sure, but a rooted device means having both the su binary and the root access manager (supersu)...?
shadowcreeper_1 said:
couldnt you combine the key and the app using lucky patcher or a diffrent method?
My device:
Samsung Galaxy S2 Skyrocket (rooted)
Rom:AOSP
Carrier:At&t
Dont forget to thank me if i helped
Click to expand...
Click to collapse
I'll thank you if you could give me the procedure on how to combine the key. (Or if I searched for it for giving me an idea)... I havent used Lucky Patcher before. If I am able to combine the two in just 1 apk, then I might just replace the existing apk from the flashable zip so when I flashed it, its in pro version automatically.
Odlanyer22 said:
No luck... I flashed the SuperSU then push the key to system/app but the key didnt install itself.
That is why I am trying to fig.out how can I insert the key from the flashable zip.
Not so sure, but a rooted device means having both the su binary and the root access manager (supersu)...?
I'll thank you if you could give me the procedure on how to combine the key. (Or if I searched for it for giving me an idea)... I havent used Lucky Patcher before. If I am able to combine the two in just 1 apk, then I might just replace the existing apk from the flashable zip so when I flashed it, its in pro version automatically.
Click to expand...
Click to collapse
ill do a little research on that, never attempted it myself but i hear you can and ive seen it happen
My device:
Samsung Galaxy S2 Skyrocket (rooted)
Rom:AOSP
Carrier:At&t
Dont forget to thank me if i helped
shadowcreeper_1 said:
ill do a little research on that, never attempted it myself but i hear you can and ive seen it happen
My device:
Samsung Galaxy S2 Skyrocket (rooted)
Rom:AOSP
Carrier:At&t
Dont forget to thank me if i helped
Click to expand...
Click to collapse
Ah no problem...
Let me research for that by myself.
So far, giving me an idea nearest to what I want to happen is a big help.
I'll give thanks, then.
UPDATE:
According to chelpus(DOT)defcon5(DOT)biz ...that was an exception to the capability of Lucky Patcher. It cannot be patched when the apps are in two parts (apk and pro key)... Btw, still thanks to everyone who effort to helped me.
Waiting for one who can really help me out for what I want.
Odlanyer22 said:
Ah no problem...
Let me research for that by myself.
So far, giving me an idea nearest to what I want to happen is a big help.
I'll give thanks, then.
UPDATE:
According to chelpus(DOT)defcon5(DOT)biz ...that was an exception to the capability of Lucky Patcher. It cannot be patched when the apps are in two parts (apk and pro key)... Btw, still thanks to everyone who effort to helped me.
Waiting for one who can really help me out for what I want.
Click to expand...
Click to collapse
Brother I tried this and it works for me.... You have to restart after putting apk file to system/app folder
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Odlanyer22 said:
No luck... I flashed the SuperSU then push the key to system/app but the key didnt install itself.
That is why I am trying to fig.out how can I insert the key from the flashable zip.
Not so sure, but a rooted device means having both the su binary and the root access manager (supersu)...?
I'll thank you if you could give me the procedure on how to combine the key. (Or if I searched for it for giving me an idea)... I havent used Lucky Patcher before. If I am able to combine the two in just 1 apk, then I might just replace the existing apk from the flashable zip so when I flashed it, its in pro version automatically.
Click to expand...
Click to collapse
Restart your device after putting apk to system /app folder
nthsfrn cels
Killwish said:
Brother I tried this and it works for me.... You have to restart after putting apk file to system/app folder
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Click to expand...
Click to collapse
Are you really pertaining to "pro key" apk too or other apk file?
It works for other apk but didn't work for pro key apk (in my case)...
AND I am wrong for my term "push" when I did not actually push it, but rather flashed it...
I flashed it right after flashing flashable SuperSU.
I placed the pro key inside a zip file>system>app (Idk where that zip file originated)... then flashed it
(all via cwm recovery).
(Btw, that zip file is really meant to flash apk to system/app or system/framework if you are afraid to push.)
Then after that, "reboot system now".
Viola! Nothings happen, but to go to system/app (look for the pro key) then install it there then restart.
(It works after that.)
..
Killwish said:
OK bro I have made flashable zip supersu.
Its here
View attachment 2841612
It is super user 2.01 pro
Flash it with any custom recovery
Click to expand...
Click to collapse
downloading and will try it later:good:
Killwish said:
OK bro I have made flashable zip supersu.
Its here
View attachment 2841612
It is super user 2.01 pro
Flash it with any custom recovery
Click to expand...
Click to collapse
OMG!
Downloading and try it ASAP...
FEEDBACK:
It doesn't work. Maybe you just put the pro key inside the zip and you didn't even bother to modify the script so its useless.
Only free version will going to install in the end.
Odlanyer22 said:
OMG!
Downloading and try it ASAP...
FEEDBACK:
It doesn't work. Maybe you just put the pro key inside the zip and you didn't even bother to modify the script so its useless.
Only free version will going to install in the end.
Click to expand...
Click to collapse
Not just copy pasted...... Sorry for that but now i updated file again...
Download again that file
this time 100% working
Killwish said:
Not just copy pasted...... Sorry for that but now i updated file again...
Download again that file
this time 100% working
Click to expand...
Click to collapse
Sorry!
Ok, I'll try to redownload...
Btw, thank you very much for the effort sir!
Killwish said:
OK bro I have made flashable zip
Its here
UPDATED
It is super user 2.01 pro
View attachment 2841940
Flash it with any custom recovery
Click to expand...
Click to collapse
Maybe you're unaware of this but i think you should remove this download immediately, you're givivg away the pro version for free
respawn
harrymason37 said:
Maybe you're unaware of this but i think you should remove this download immediately, you're givivg away the pro version for free
respawn
Click to expand...
Click to collapse
Okk ... I'll ... thank you sir
biatche said:
Would like to further understand something from this too
(i do have linux background)
Technically speaking, what is a rooted device? Is it having the su binary available? Is that what it means?
But then, supersu says that it needs a 'rooted device'.. this is quite rather confusing. doesnt supersu provide root access to apps?
Click to expand...
Click to collapse
Yes, exactly.
The problem is that people have adopted the term rooted to also mean access to the root of the filesystems, iow, the / directory. ("Just place this file on the root of your SD card," being the most common example of that usage.)
Anyway, with / access you can remount /system to rw instead of ro, and from there you can install the su binary (either in /system/bin or /system/xbin depending on how the dev made the installer).
The apk is simply the front end (user facing) management layer.
And then toss in the common Linux misunderstanding that's bled over to Android that su stands for super user. It doesn't, it stands for set user, but without arguments (the way most people have seen it) defaults to setting you to the root user.
As a Linux user, it might be just as well to think of the apk as your sudo access assistant, and to think of the grant/deny popup as analogous to confirming access with your password.
If you haven't already, install a good busybox (I prefer this one) -
Check out "BusyBox"
https://play.google.com/store/apps/details?id=stericson.busybox
And then Terminal Emulator and look around just as you would on Linux.
Your filesystem layout will make more sense one you use the df and mount commands there.
Hope this helps.
PS - Also, a thank you for taking down the pro download.
harrymason37 said:
Maybe you're unaware of this but i think you should remove this download immediately, you're givivg away the pro version for free
respawn
Click to expand...
Click to collapse
Let me be the one to apologize sir.
He just helping me out. But I do understand it too...
I really sorry!
And finally, it works 100%
All I want to know now is how did he insert the pro key. XD
So I can do it by myself anytime.
[CASE CLOSED]

Categories

Resources