Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[klte][CWM Advanced Edition] PhilZ Touch

OP Phil3759

View First Unread
4th April 2014, 09:08 PM   |  #1  
Phil3759's Avatar
OP Recognized Developer
Thanks Meter: 32,024
 
9,397 posts
Join Date:Joined: May 2012
Donate to Me
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/show....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


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 long press outside a menu (2 sec and slightly change pressure after the delay)

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:
Quote:

Galaxy S5 Unified (klte): International, Canada, Sprint, TMO

http://goo.im/devs/philz_touch/CWM_A...d_Edition/klte

Notice: ATT and VZW are locked. You must unlock them to be able to flash a recovery

special credits to @PlayfulGod for his unified device tree
https://github.com/playfulgod

XDA:DevDB Information
[klte][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Samsung Galaxy S 5

Contributors
Phil3759

Version Information
Status: Stable

Created 2014-04-04
Last Updated 2014-04-16
The Following 105 Users Say Thank You to Phil3759 For This Useful Post: [ View ]
4th April 2014, 09:09 PM   |  #2  
Phil3759's Avatar
OP Recognized Developer
Thanks Meter: 32,024
 
9,397 posts
Join Date:Joined: May 2012
Donate to Me
reserved
Last edited by Phil3759; 11th April 2014 at 05:43 PM.
The Following 12 Users Say Thank You to Phil3759 For This Useful Post: [ View ]
4th April 2014, 09:20 PM   |  #3  
PlayfulGod's Avatar
Recognized Developer
Flag Dalton
Thanks Meter: 2,979
 
1,789 posts
Join Date:Joined: Sep 2010
Donate to Me
More
You did notice that there was a issue with internal storage right?? It was suggested I could fix using a init file but I've not had a chance to work on it yet. If you happen to have the same issue and fix it, please share and let me know what you did.
The Following User Says Thank You to PlayfulGod For This Useful Post: [ View ]
4th April 2014, 09:37 PM   |  #4  
Phil3759's Avatar
OP Recognized Developer
Thanks Meter: 32,024
 
9,397 posts
Join Date:Joined: May 2012
Donate to Me
Quote:
Originally Posted by PlayfulGod

You did notice that there was a issue with internal storage right?? It was suggested I could fix using a init file but I've not had a chance to work on it yet. If you happen to have the same issue and fix it, please share and let me know what you did.

ups, sorry, I did not notice
Link to the exact issue?
Sure if I find a fix I will share all sources. That's what I always do now, outside the touch code
The Following User Says Thank You to Phil3759 For This Useful Post: [ View ]
4th April 2014, 09:45 PM   |  #5  
PlayfulGod's Avatar
Recognized Developer
Flag Dalton
Thanks Meter: 2,979
 
1,789 posts
Join Date:Joined: Sep 2010
Donate to Me
More
Quote:
Originally Posted by Phil3759

ups, sorry, I did not notice
Link to the exact issue?
Sure if I find a fix I will share all sources. That's what I always do now, outside the touch code

not sure of the source of the issue, but its internal sd/storage is read only. So no backups can be made to internal storage. Restoring data works fine tho.

TWRP doesnt have this issue tho, so I think its in the device repo and prolly something simple. lol

Also this is only known to work with the G900F so far. The kernel src I have on github is technically for the G900D, but its working in CWM. Just seems to be missing model specific dts files.
4th April 2014, 10:21 PM   |  #6  
Phil3759's Avatar
OP Recognized Developer
Thanks Meter: 32,024
 
9,397 posts
Join Date:Joined: May 2012
Donate to Me
Quote:
Originally Posted by PlayfulGod

not sure of the source of the issue, but its internal sd/storage is read only. So no backups can be made to internal storage. Restoring data works fine tho.

TWRP doesnt have this issue tho, so I think its in the device repo and prolly something simple. lol

Also this is only known to work with the G900F so far. The kernel src I have on github is technically for the G900D, but its working in CWM. Just seems to be missing model specific dts files.

Not having the device makes it a too long debug process. Also, seems few users interested in debugging it
About write to sdcard, it is probably a selinux permission issue. At least that's what I most often encountred
I looked at your twrp sources. They use custom selinux permission files

Well, in fact they are using Samsung enforced permissions and they run this at boot:
Code:
toolbox setenforce permissive
You'll have to mount /system for that than unmount it as we have still no setenforce in busybox (they are in Pruvot custom busybox repo though)

Can you try this:
Quote:

  • ensure you are not using the recovery.fstab file in your device tree but the fstab.qcom
  • adb shell:
Code:
mount /system
/system/bin/toolbox setenforce permissive

See if you can now access internal storage in write mode
4th April 2014, 10:27 PM   |  #7  
PlayfulGod's Avatar
Recognized Developer
Flag Dalton
Thanks Meter: 2,979
 
1,789 posts
Join Date:Joined: Sep 2010
Donate to Me
More
Quote:
Originally Posted by Phil3759

Not having the device makes it a too long debug process. Also, seems few users interested in debugging it
About write to sdcard, it is probably a selinux permission issue. At least that's what I most often encountred
I looked at your twrp sources. They use custom selinux permission files

Well, in fact they are using Samsung enforced permissions and they run this at boot:

Code:
toolbox setenforce permissive
You'll have to mount /system for that than unmount it as we have still no setenforce in busybox (they are in Pruvot custom busybox repo though)

Can you try this:


See if you can now access internal storage in write mode

Agreed, debugging w/o the device is a pita. lol
I seen that as well and had the tester try to set it. Not sure if they mounted system first, so will have them try it again to make sure. If they did, it didnt help.

I will have to check and see which fstab I have it using too. When I hear from my tester I will test all your suggestions. And thanks.

Its using the fstab.qcom.
Last edited by PlayfulGod; 4th April 2014 at 10:32 PM.
4th April 2014, 10:43 PM   |  #8  
Phil3759's Avatar
OP Recognized Developer
Thanks Meter: 32,024
 
9,397 posts
Join Date:Joined: May 2012
Donate to Me
Quote:
Originally Posted by PlayfulGod

Agreed, debugging w/o the device is a pita. lol
I seen that as well and had the tester try to set it. Not sure if they mounted system first, so will have them try it again to make sure. If they did, it didnt help.

I will have to check and see which fstab I have it using too. When I hear from my tester I will test all your suggestions. And thanks.

Its using the fstab.qcom.

Oh, you're also doing it blindly
It can be possible, but not with such a non existing feedback from users

If you think testers are just able to boot and check, try to add the needed lines to postrecoveryboot.sh (inherited from msm8960-common/recovery)
Code:
mount [BLKID] /system
/system/bin/toolbox setenforce permissive
umount /system
However, I think you need the blkid, not sure the path symlink to partition will work
You cannot just make a mount /system from postrecoveryboot.sh as the fstab file is not yet generated by recovery at that level
4th April 2014, 10:50 PM   |  #9  
PlayfulGod's Avatar
Recognized Developer
Flag Dalton
Thanks Meter: 2,979
 
1,789 posts
Join Date:Joined: Sep 2010
Donate to Me
More
Quote:
Originally Posted by Phil3759

Oh, you're also doing it blindly
It can be possible, but not with such a non existing feedback from users

If you think testers are just able to boot and check, try to add the needed lines to postrecoveryboot.sh (inherited from msm8960-common/recovery)

Code:
mount [BLKID] /system
/system/bin/toolbox setenforce permissive
umount /system
However, I think you need the blkid, not sure the path symlink to partition will work
You cannot just make a mount /system from postrecoveryboot.sh as the fstab file is not yet generated by recovery at that level

I will give that a try. thanks

img built and linked to tester(s).
Last edited by PlayfulGod; 4th April 2014 at 11:19 PM.
The Following User Says Thank You to PlayfulGod For This Useful Post: [ View ]
4th April 2014, 11:47 PM   |  #10  
Phil3759's Avatar
OP Recognized Developer
Thanks Meter: 32,024
 
9,397 posts
Join Date:Joined: May 2012
Donate to Me
Quote:
Originally Posted by PlayfulGod

I will give that a try. thanks

img built and linked to tester(s).

Thanks,
will watch your thread and wait for testers before wasting more time on it

Post Reply Subscribe to Thread
Previous Thread Next Thread