Database Info

[klte][CWM Advanced Edition] PhilZ Touch

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
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:
Galaxy S5 Unified (klte): International, Canada, Sprint, TMO
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/klte
Notice: ATT and VZW are locked. You must unlock them to be able to flash a recovery
Click to expand...
Click to collapse
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

reserved

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.

PlayfulGod said:
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.
Click to expand...
Click to collapse
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

Phil3759 said:
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
Click to expand...
Click to collapse
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.

PlayfulGod said:
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.
Click to expand...
Click to collapse
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:
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
Click to expand...
Click to collapse
See if you can now access internal storage in write mode

Phil3759 said:
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
Click to expand...
Click to collapse
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.

PlayfulGod said:
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.
Click to expand...
Click to collapse
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

Phil3759 said:
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
Click to expand...
Click to collapse
I will give that a try. thanks
img built and linked to tester(s).

PlayfulGod said:
I will give that a try. thanks
img built and linked to tester(s).
Click to expand...
Click to collapse
Thanks,
will watch your thread and wait for testers before wasting more time on it

Phil3759 said:
Thanks,
will watch your thread and wait for testers before wasting more time on it
Click to expand...
Click to collapse
Philz, its boot looping! it doesnt work at all !

leoaudio13 said:
Philz, its boot looping! it doesnt work at all !
Click to expand...
Click to collapse
Can you post a stock recovery.img please!

Phil3759 said:
Can you post a stock recovery.img please!
Click to expand...
Click to collapse
Here you are : https://drive.google.com/file/d/0B3HkAzPm36j4b05kbDNtTVA1ZnM/edit?usp=sharing

I'll test this on Friday. Verizon S5 on it's way that day.
Sent from my SCH-I545 using XDA Premium 4 mobile app

Philz,
Thank You for all you did.
Every time i'm buying a new phone, i have the pleasure to get your recovery "ready to install".
Great work, great support.

Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable

Phil3759 said:
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Click to expand...
Click to collapse
Has this been tested on a 900H Model?

Phil3759 said:
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Click to expand...
Click to collapse
Gahhh! Ive been waiting for yours to test. Now im in Cambodia on business. Will test when im bak by 2mo tks again Philz
Sent from my SM-G900F using Tapatalk

leoaudio13 said:
Gahhh! Ive been waiting for yours to test. Now im in Cambodia on business. Will test when im bak by 2mo tks again Philz
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
LoL
Two months!
Hope someone else will test before

Phil3759 said:
LoL
Two months!
Hope someone else will test before
Click to expand...
Click to collapse
U dissapeared since I post u the stock recovery lol. I was wondering
Sent from my SM-G900F using Tapatalk

AdBlocking on Rooted Z5

Hi,
A while back I rooted my phone because I had had enough of missing out on xposed modules and had had enough with all the Ads!! When did Android become so riddled with adverts. (i know its not android itself before you say anything)
Anyway I managed to root my phone using the methods highlighted in the forum. I've got xposed working perfectly but I am still seeing averts in apps and on web pages. Correct me if I'm wrong but I should be able to hide these now. I've come from Galaxy S4 which I had rooted from day 1 so I never saw a single advert (in app or webpage) but now on my rooted Z5 I am still seeing a lot. Many apps (baconreader for example) have had the ads in there hidden but many still persist.
I've tried all the options I can see to be available to me
In no particular order and never installed at the same time incase they conflict.
- Adaway (this errors when applying the host file saying the copy failed)
- Adblock plus (app not browser)
- Adfree (this is what I used on my S4)
- MinMinGuard (tried different modes on this one and still no luck and no errors to speak of)
None of them error apart from AdAway.
Have any of you guys got a totally adfree experience on the Z5? If so how have you managed this?

I am using Adguard, it costs 8$ a year. That's almost free I think.

I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk

Funkmasterchilla said:
I am using Adguard, it costs 8$ a year. That's almost free I think.
Click to expand...
Click to collapse
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?

TimDawg said:
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?
Click to expand...
Click to collapse
AdAway is working for me.
Like I said ensure you can remount /system as r/w.
Sent from my E6683 using Tapatalk

_Dennis_ said:
I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers

TimDawg said:
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers
Click to expand...
Click to collapse
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk

See MOAAB (mother of all ad block) in Android Development and Hacking. Costs 0 bucks and blocks hosts. That's the best if you are rooted bro

_Dennis_ said:
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I get an error saying no such directory. if i try to create it manually it fails...

TimDawg said:
I get an error saying no such directory. if i try to create it manually it fails...
Click to expand...
Click to collapse
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk

_Dennis_ said:
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.

TimDawg said:
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.
Click to expand...
Click to collapse
What super user app do you use? How was it installed?

_Dennis_ said:
What super user app do you use? How was it installed?
Click to expand...
Click to collapse
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.

TimDawg said:
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.
Click to expand...
Click to collapse
Probably your best bet. Sorry I couldn't be of any help.
Sent from my E6683 using Tapatalk

How did you rooted your z5?

luisfillipe said:
How did you rooted your z5?
Click to expand...
Click to collapse
I used the method for Z5 dual SIM posted in the dirty root thread in development section. There are other simpler methods for the regular Z5, again in development section. It requires bootloader unlocks for all of them and that causes you to lose some Sony DRM keys.
Sent from my SM-T710 using Tapatalk

I tried Adblock since i'm not rooted, but it occasionally drain battery in sleep mode so I removed it..

I've always used Lucky Patcher for that. It has hosts blocking as well as disabling google ad modules inside apps, making everything clean and bull$hit free.

Gotta say I was starting it get a be pissed off with how much more complicated it is to do root this phone than any other android phone I've tried to do in the past...
so I came to the assumption that I'm supposed to be booting into recovery and installing the zip through there like I used to do to install ROMs on my older android phones.
I've flashed a few AndroPlus kernels and no luck. One of them left me stuck in bootloop which I let go around roughly 10 times until I decided it was getting nowhere. I did eventually manage to get one installed without a bootloop.
I wanted to know what Kernel I was running so I installed 'Kernel Adiutor' which required BusyBox to be installed alongside it. I found I was unable to install BusyBox which I guess was caused by the same thing causing all my other issues.
I've tried going through this whole over complicated process again and I hit a problem was trying to execute these two lines:
Code:
adb shell mount /dev/block/platform/soc.0/by-name/system /system
adb shell mount /dev/block/platform/soc.0/by-name/userdata /data
I read through everything I could find again to see if I could work out what was going on. While looking for this I can across this line of code:
Code:
fastboot flash boot boot.img
which is to be run if you want to flash the kernel via adb. (you need to extract the zip provided by AndroPlus)
Once this line had been executed I booted up again and was able to install BusyBox which let me see which kernel I had which showed AndroPlus (v3 incase you're interested) so I then tried AdAway again.
BINGO
Only thing is on some websites, particularly xda there is still a gap showing where the Advert would be displayed if not blocked. This I can live with.
I can't beleive how much more complicated this phone is to root compared to my HTC Desire, Galaxy S2 & S4. All of them were plug phone in. Click a few times and the jobs done. Is there a reason this hasn't been done for the Z5?
Just want to say thanks to all that have tried to help.
Thanks to AndroPlus for his kernel which has sorted me out.
Not so much thanks to Sony as this whole process has put me off ever getting another Sony phone. Mainly the fact I've lost some functionality what with having to unlock the bootloader. Overall I'm happy though.
Cheers

How do you set SELinux to permissive on the J700P model?

Title, I can't figure out how to do this.
And as a side question, has anyone figured out how to unlock the bootloader?

Found this it might do the trick for permissive but the bootloader i wonder if a loki patch would work if it was applied to the recovery and boot image then you wouldnt need to unlock completely to flash but all the roms would need to be loki'd but the its better to have full unlocked bootloader. There is a unlock bootloader thread on here but im not sure whos all used it...
You can set the SELinux to Permissive temporarily by running the bellow two commands in Terminal emulator
su
setenforce 0
But it SElinux will change to default once you hard reboot your phone.. In order to keep it in permissive, you need to soft reboot always whenever reboot needed and it's quite annoying..
So I found a workaround to Set the SELinux to permissive on boot itself.
For this you need to have init.d support.. If you don't have just install it via universal init.d tool available in xda.. (just do a search, u will get it) install universal init.d and activate init.d..
Then go to /etc/init.d directory, create a file and rename it as "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx) .. Use root Explorer to edit and give permissions..
Now hard reboot your phone and you can see SELinux is set to "permissive" on boot itself..
---------- Post added at 04:14 PM ---------- Previous post was at 03:43 PM ----------
If loki would be something youd be interested in its a add on of android image kitchen it will loki patch youre boot image and i believe recovery is supported as well. It auto generates the loki patches for you all you have to do is drag and drop the images over the loki selection and it does the rest.
http://forum.xda-developers.com/showthread.php?t=2073775

CoffeeNAndroid said:
Found this it might do the trick for permissive but the bootloader i wonder if a loki patch would work if it was applied to the recovery and boot image then you wouldnt need to unlock completely to flash but all the roms would need to be loki'd but the its better to have full unlocked bootloader. There is a unlock bootloader thread on here but im not sure whos all used it...
You can set the SELinux to Permissive temporarily by running the bellow two commands in Terminal emulator
su
setenforce 0
But it SElinux will change to default once you hard reboot your phone.. In order to keep it in permissive, you need to soft reboot always whenever reboot needed and it's quite annoying..
So I found a workaround to Set the SELinux to permissive on boot itself.
For this you need to have init.d support.. If you don't have just install it via universal init.d tool available in xda.. (just do a search, u will get it) install universal init.d and activate init.d..
Then go to /etc/init.d directory, create a file and rename it as "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx) .. Use root Explorer to edit and give permissions..
Now hard reboot your phone and you can see SELinux is set to "permissive" on boot itself..
---------- Post added at 04:14 PM ---------- Previous post was at 03:43 PM ----------
If loki would be something youd be interested in its a add on of android image kitchen it will loki patch youre boot image and i believe recovery is supported as well. It auto generates the loki patches for you all you have to do is drag and drop the images over the loki selection and it does the rest.
http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
The init.d thing hasn't worked for me... oh well. As for the bootloader, yeah, I'm just going to wait for a guide on how to do it. I don't want to break my phone haha. Thanks anyway!

minz1 said:
The init.d thing hasn't worked for me... oh well. As for the bootloader, yeah, I'm just going to wait for a guide on how to do it. I don't want to break my phone haha. Thanks anyway!
Click to expand...
Click to collapse
It didn't work coz stock kernel does not support init.d , i think that i made a permissive kernel you can find it in the bounty thread

messi2050 said:
It didn't work coz stock kernel does not support init.d , i think that i made a permissive kernel you can find it in the bounty thread
Click to expand...
Click to collapse
That permissive kernel is the stock kernel and see it does support init.d.
https://play.google.com/store/apps/details?id=os.tools.scriptmanager
Id use use script manager and run it put it in the init.d folder and run it as script with root permissions

See init.d works with script manager

CoffeeNAndroid said:
That permissive kernel is the stock kernel and see it does support init.d.
https://play.google.com/store/apps/details?id=os.tools.scriptmanager
Id use use script manager and run it put it in the init.d folder and run it as script with root permissions
Click to expand...
Click to collapse
I have done that, and it hasn't worked. I dunno what's going on with this.

Download the test file in this thread and use its instructions to do everything correctly. Once its in init.d folder browse as root in script manager, press on the test file select open as script. Click root, boot, save... reboot then go into youre data folder and see if theres a test log. If theres a test log youre init.d is working
http://forum.xda-developers.com/showthread.php?t=1933849

Anyways iam running that permissive kernel and id hate to break it to you but theres no init.d included in the kernel. You dont need a permissive kernel anyways to get init.d. when i modified the optimus elite with a galaxy s3 apps2sd script the phone didnt have init.d or a permissive kernel and i ran init.d scripts through script manager.. its either flash the kernel which to remove permissive you have to flash stock kernel which removes root unless you flash in flashfire cause the kernel is included in the boot image so a clean flash of the stock boot removes root too. Or use script manager to get init.d and then add the perm script. With script manager you can turn it on and off alot easier and when you remove it doesnt remove youre root and you dont have to take steps to reroot...

Oh and the reason messi is being ****ty is cause i didnt help root the galaxy s6 active.. i dont make money off other peoples work.. since super su is chainfires id have all the money given to chainfire but messi believes in making money off people using stuff other people created. Making a boot image permissive is not really considered work.. messi would of had a fit if the money went to chainfire... it seems messi only focuses on the bountys to see how much money messi can make. I would of been the one to add root and wouldnt of got nothing for it. Messi would of felt entitled to the money for doing nothing but making a permissive kernel...

CoffeeNAndroid said:
Oh and the reason messi is being ****ty is cause i didnt help root the galaxy s6 active.. i dont make money off other peoples work.. since super su is chainfires id have all the money given to chainfire but messi believes in making money off people using stuff other people created. Making a boot image permissive is not really considered work.. messi would of had a fit if the money went to chainfire... it seems messi only focuses on the bountys to see how much money messi can make. I would of been the one to add root and wouldnt of got nothing for it. Messi would of felt entitled to the money for doing nothing but making a permissive kernel...
Click to expand...
Click to collapse
I dunno about the drama on these forums man.. if that's really true then I don't know...

messi2050 said:
It didn't work coz stock kernel does not support init.d , i think that i made a permissive kernel you can find it in the bounty thread
Click to expand...
Click to collapse
CoffeeNAndroid said:
That permissive kernel is the stock kernel and see it does support init.d.
https://play.google.com/store/apps/details?id=os.tools.scriptmanager
Id use use script manager and run it put it in the init.d folder and run it as script with root permissions
Click to expand...
Click to collapse
A constructive discussion is fine but anything else either take it to Pm or add each other to your ignore lists. Also there is no point in posting that you have added someone to your ignore list as you wont see their reply

Supersu is a free app... when the only thing you add is root access by supersu which is what the free version does then it should be distributed for free.. if anyone is entitled to money off of it then it would be chainfire.. to take someone elses work and charge money for it is ridiculous.. if i would of known that root provided was cf auto root i wouldnt of ever paid the $20 i kinda figured theyd make their own root method but that never happened... chainfire was the first to make a root boot image for marshmallow so technically everything would be credited to him... its easy to give someone credit but much more difficult to do the right thing and give that someone the money especially when youre motivated by money...

Check this post, selinux is set always permissive on my stock kernel, i don't have init.d support ?
https://forum.xda-developers.com/g2...w-to-set-selinux-to-permissive-t3329439/page4

I have permissive kernel on this model. There is a thread here with a version posted. I'll have him update the thread to State the process so far. Currently in testing phase

[5.12.17][g935u][root] stable method for g935u - bqd2 t-mobile

As we have all seen with this latest STOCK G935U [BQD2] Firmware for T-Mobile indeed it runs smooth and personally I have experienced better performance without all those carrier-bloat applications by default. Dating a week ago, I tried to root this build version and for some reason I experienced infinite bootloops after my device boots up. So I did some research as to what system apps could be causing this I still I can't believe that a network-related system application was causing this issue.
I am talking about com.samsung.sprint.chameleon as mentioned by @qwewqa here -> https://forum.xda-developers.com/tmobile-s7-edge/how-to/4-28-t-mobile-935-firmware-t3597866/page10
I will not go in-depth about what this is but this relates to a network configuration. I will post a reference on this if you guys feel like checking out...
https://community.sprint.com/t5/Archives/Chameleon/td-p/654097
FAST & STABLE ROOT METHOD FOR THE G935U under T-Mobile // S7 EDGE
1 - Download & Flash Via Odin the latest Firmware provided on this post. Thanks to @justda
https://forum.xda-developers.com/tmobile-s7-edge/how-to/4-28-t-mobile-935-firmware-t3597866
------------ HERE COMES THE MOST IMPORTANT STEP ON THIS GUIDE ----------​
2 - Install Package Disabler Pro from OSPolice. Play Store link ...
https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro&hl=es
3 - Open the application, activate Device Administrator, just hit next or ok or just follow through the setup and once the apps list loads up look for the system app with the name of: com.samsung.sprint.chameleon. Go ahead clear data and DISABLE it. After you are done disabling this system app, you are now safe and good to follow through the root method below.
4 - I suggest that you use the root.bat file provided by @Quickvic30 on this thread to root your device
https://forum.xda-developers.com/tmobile-s7-edge/how-to/heres-how-rooted-nougat-s7-edge-g935t-t3567502
IF YOU HAVE SUCCESSFULLY BOOTED UP YOUR DEVICE PAST THE SAMSUNG SCREEN WITHOUT ENDING UP IN BOOTLOOPS (Bootloops may occur within 30 seconds after booting up from the Samsung Screen) THATS IT, YOU ARE DONE!
### Post-Root Suggestions ###
Applications to Install:
Titanium Backup
Kernel Adiutor
L-Speed
SD Maid
THE FOLLOWING XML DEBLOAT PACKAGE IS FOR THOSE WHO ARE LOOKING INTO DISABLING THE MOST PACKAGES INCLUDING SOME STOCK APKS. PLEASE CAREFULLY GO OVER THE LIST ATTACHED AND JUST CONTINUE ON TO MAKE ANY MODIFICATIONS TO FIT YOUR NEEDS
### DEBLOATER FOR PACKAGE DISABLER PRO - SAFE TO DISABLE APPS & SYSTEM APPS [~1950 MB RAM FREE - SOMETIMES 2000 MB's] ###
Attached is the xml file for Package Disabler Pro that will free ~ 2 GB RAM on your device.

Since I don't see any mention of using the engineering kernel should I assume this method does not work for US models?

So basically you take qwewqa's discovery, make no mention of him, then pass it off as your own. Then copy and paste some steps from other people, and submit it as your work?

markmain2. 0 said:
Since I don't see any mention of using the engineering kernel should I assume this method does not work for US models?
Click to expand...
Click to collapse
As referred in the procedure section. The main and original root method goes to the forum thread linked above. As I briefly specified in the background info section, this is just a quick fix in performance and stability when applying root to this build.

tofu- said:
So basically you take qwewqa's discovery, make no mention of him, then pass it off as your own. Then copy and paste some steps from other people, and submit it as your work?
Click to expand...
Click to collapse
I didn't copy nor plagiarize any information from their respective owners. Credits are given, very briefly detailed information on the steps as to the main reason of this thread is just giving the list and proceed with the order of steps to successfully achieve root. The link that I attached in regards to the conflicting system app that where I noticed the issue with other models.
I didn't look into @qwewqa thread comment regarding this, and I apologize and edited to credit him on this finding.

The debloat list provided is extremely aggresive. It removes the stock gallery, stock calender, lock screen wallpaper, stock contacts, Bluetooth, and all google back up services.
Your list is great for the hardcore folks BUT you have to go back through the lost and re-enable the apps and clear the data then re disable them.
Sent from my SM-G935U using XDA Premium HD app

Brian,
Thanks for bringing it all together. I am currently rooted on T-Mobile QC1. I wanted to go to the U firmware wanted a tested way to root first.
Pat

Thank you kindly. Going to try this out right now

gonna give this a try, Any kernel tweak recommendations? how smooth/fast is it or does it lag like a bunch

any fix for the finger print sensor?

Im think the eng is conflicting with a app killing the fingerprint sensor

patcal said:
Brian,
Thanks for bringing it all together. I am currently rooted on T-Mobile QC1. I wanted to go to the U firmware wanted a tested way to root first.
Pat
Click to expand...
Click to collapse
Hey Pat,
In fact there is a way to root the U Firmware and achieve functionality and administration. All thanks to their devs for their work

black96ss said:
gonna give this a try, Any kernel tweak recommendations? how smooth/fast is it or does it lag like a bunch
Click to expand...
Click to collapse
As a matter of fact, the root.bat from @Quickvic30 does all the jobs needed. I strongly suggest running his method. No L Speed, no Kernel Adiutor. Just Titanium Backup to freeze/uninstall bloatware.

black96ss said:
gonna give this a try, Any kernel tweak recommendations? how smooth/fast is it or does it lag like a bunch
Click to expand...
Click to collapse
black96ss said:
any fix for the finger print sensor?
Click to expand...
Click to collapse
Hmmm...to be honest I didn't have any issues regarding the fingerprint sensor. Have you solved your issue by now?

Broken Fingerprint Sensor
purotijuana said:
Hmmm...to be honest I didn't have any issues regarding the fingerprint sensor. Have you solved your issue by now?
Click to expand...
Click to collapse
Yes, I also have the same problem. The fingerprint sensor has stopped working after flashing the Eng Bootloader.
Found the fix: Credits to qwewqa
Link

Dexolit said:
Yes, I also have the same problem. The fingerprint sensor has stopped working after flashing the Eng Bootloader.
Found the fix: Credits to qwewqa
Link
Click to expand...
Click to collapse
I tried to use this method but my phone won't let me change permissions. It pops up with a message that says "changing permissions was not successful. Please note that some file systems do not allow permission changes." Is there something special I need to do to enable permission changes?
Also I am using root browser to do this.

nickp22127 said:
I tried to use this method but my phone won't let me change permissions. It pops up with a message that says "changing permissions was not successful. Please note that some file systems do not allow permission changes." Is there something special I need to do to enable permission changes?
Also I am using root browser to do this.
Click to expand...
Click to collapse
Try another file browser. Root Explorer is what I have always used.

patcal said:
Try another file browser. Root Explorer is what I have always used.
Click to expand...
Click to collapse
Awesome man it worked! Thanks a lot. Root explorer seems pretty legit by the way. I've only ever used root browser.

nickp22127 said:
Awesome man it worked! Thanks a lot. Root explorer seems pretty legit by the way. I've only ever used root browser.
Click to expand...
Click to collapse
Glad it worked. I have been using Root Explorer for as long as I have been using & rooting android phones.

nickp22127 said:
I tried to use this method but my phone won't let me change permissions. It pops up with a message that says "changing permissions was not successful. Please note that some file systems do not allow permission changes." Is there something special I need to do to enable permission changes?
Also I am using root browser to do this.
Click to expand...
Click to collapse
I also had that problem too. Just extract the libs and overwrite them in /system/lib and /lib64, then change the permissions to rw-r--r--. Apparently, it only worked after overwriting the files.

[HELP] How to alter build.prop? Magisk Rooted

So I have my 930-F S7 systemless rooted with Magisk and with encryption.
I noticed that after rooting I wasn't able to use SmartView on my TV anymore, I've tried lots of things but eventually came to a proposed solution of editing build.prop and adding the following line to the end of it and it should work:
wlan.wfd.hdcp = disable
Click to expand...
Click to collapse
Unfortunately when trying to alter build.prop there was always an error saying it was read only, after a quick research it seems it's because it's a systemless root, so I should try doing it directly with Magisk.
Found myself to a helpful thread, that told me to put the above command line into a blank .txt and paste it into:
/sbin/.core/img/.core/post-fs-data.d
Click to expand...
Click to collapse
But it failed, I wasn't able to paste the file.
So I don't know what to do, has anyone faced this issue and can help me?

I was able to fix this issue and FINALLY be able to Smart View / Screen Mirror to other devices.
To do so I installed Didgeridoohan's MagiskHide Props Config Module. Installed a Terminal Emulator and proceeded to include the line mentioned on my previous post to build.prop.
After that, voila it was finally fixed.

Done.
The line is already present in my custom Rom. The problem is elsewhere.

CyberBeaR said:
I was able to fix this issue and FINALLY be able to Smart View / Screen Mirror to other devices.
To do so I installed Didgeridoohan's MagiskHide Props Config Module. Installed a Terminal Emulator and proceeded to include the line mentioned on my previous post to build.prop.
After that, voila it was finally fixed.
Click to expand...
Click to collapse
can please tell me the steps how did u you do tha
please
thanks.