Database Users

Samsung Galaxy S5 (SM-G900W8) and AppRadio2 + App Radio Unchained

Hello,
I have done some searching with not alot of luck. I am trying to get my S5 touch controls to work on my AppRadio2. Everything works but there is no touch input. I read that this is due to the SELinux being in Enforcing mode. The SELinux app does not work from changing the status from Enforcing to Permissive. I was told that a custom kernel has to be used in order to change this and get my app radio touch working.
I apologise in advance if this has been covered already or if this is in the wrong spot. i would like to know if anyone got their phone working with their appRadio's.
My phone has 4.4.2
CF-Auto Root (stock with root)
Philz Touch Mod Recovery.

Reidicus said:
Hello,
I have done some searching with not alot of luck. I am trying to get my S5 touch controls to work on my AppRadio2. Everything works but there is no touch input. I read that this is due to the SELinux being in Enforcing mode. The SELinux app does not work from changing the status from Enforcing to Permissive. I was told that a custom kernel has to be used in order to change this and get my app radio touch working.
I apologise in advance if this has been covered already or if this is in the wrong spot. i would like to know if anyone got their phone working with their appRadio's.
My phone has 4.4.2
CF-Auto Root (stock with root)
Philz Touch Mod Recovery.
Click to expand...
Click to collapse
I would also like to get this working. tried using my s5 with my app radio and no luck...

Possible solution
I tried to provide you a link to a workaround that solved it in my S4, but I'm not allowed to publish external links here. So try searching in Google: appradio "pm disable com.sec.knox.seandroid"
With tasker automation, I could make it work in my S4 without changing to a custom kernel. Let me know if it works in the S5 also, because it's probably my next acquisition!
Reidicus said:
Hello,
I have done some searching with not alot of luck. I am trying to get my S5 touch controls to work on my AppRadio2. Everything works but there is no touch input. I read that this is due to the SELinux being in Enforcing mode. The SELinux app does not work from changing the status from Enforcing to Permissive. I was told that a custom kernel has to be used in order to change this and get my app radio touch working.
I apologise in advance if this has been covered already or if this is in the wrong spot. i would like to know if anyone got their phone working with their appRadio's.
My phone has 4.4.2
CF-Auto Root (stock with root)
Philz Touch Mod Recovery.
Click to expand...
Click to collapse

Any luck?
Any luck with the S5 and touch controls in ARU?
thorosso said:
I tried to provide you a link to a workaround that solved it in my S4, but I'm not allowed to publish external links here. So try searching in Google: appradio "pm disable com.sec.knox.seandroid"
With tasker automation, I could make it work in my S4 without changing to a custom kernel. Let me know if it works in the S5 also, because it's probably my next acquisition!
Click to expand...
Click to collapse

No, still no luck. Everything works but the touch screen. Very frustrating!
Sent from my SM-G900W8 using XDA Premium 4 mobile app

In case you didn't find a solution, in my G900M I got touchscreen working after I installed Omega ROM with its permissive kernel!
Sent from my SM-G900M using XDA Premium 4 mobile app

I'm not much on custom roms. I prefer to stay stock with a custom kernel with permissive mode if at all possible.
Sent from my SM-G900W8 using XDA Premium 4 mobile app

Custom Kernel
Reidicus said:
I'm not much on custom roms. I prefer to stay stock with a custom kernel with permissive mode if at all possible.
Sent from my SM-G900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you ever find a custom Kernel? I would prefer stock rom, as well.

Same here and no luck so far

Go get this ROM after rooting http://forum.xda-developers.com/showthread.php?t=2955996
Love it

A heads up - TowelRoot did not work on my Sprint S5 (but I got it rooted using Odin)

I'm not sure why, the .apk file for towelroot refused to run/launch and was complaining about some kind of parsing error. Since it's a binary a generic parse error was not all that useful in attempting to debug what was happening. I tried downloading it a couple separate time and transferring it over to the phone again, but same problem. And same problem running it from either the internal phone storage or my external microSD card.
So ... I then used the odin and CF-Auto-Root (instructions at http://www.ibtimes.com/how-root-sam...42-kitkat-using-cf-auto-root-tutorial-1577576) and got it working first try, perfect!
The only issue I find is that when I launch Super SU it ALWAYS asks about whether it should try to suppress Samsung Knox every time I open the app, and I always say cancel, and it's successful. Apps don't encounter this problem once you set Super SU to have a default action of "Grant" superuser permission.

Hmm... strange, I was able to use TowelRoot on my Sprint GS5. On both nd8 and ne5 firmwares with no issues

Might as well take it all the way with cf root anyway. Only reason not to really would be if its a company supplied phone where they check on knox status. Towel root is awesome, but msde for people who have a reason to worry about knox, or for those with a locked bootloader. Sprint is wide open so why not take advantage.
Sent from my SM-G900P using XDA Free mobile app

miked63017 said:
Might as well take it all the way with cf root anyway. Only reason not to really would be if its a company supplied phone where they check on knox status. Towel root is awesome, but msde for people who have a reason to worry about knox, or for those with a locked bootloader. Sprint is wide open so why not take advantage.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
The other reason is if you'd like to keep your warranty intact.
Knox trip = no longer covered by warranty, only insurance claim with deductible.
That said, for those with ERP it's hit or miss if the sprint store will check the knox flag if doing swap, but Samsung direct warranty generally does.
It also might be that users don't care to run another rom.
I'm fine on the stock rom, I rooted, and removed all the bloat and can basically do all the same tweaks.
I have custom PRL, icons etc. and my piece of mind for warranty

bryanu said:
The other reason is if you'd like to keep your warranty intact.
Knox trip = no longer covered by warranty, only insurance claim with deductible.
That said, for those with ERP it's hit or miss if the sprint store will check the knox flag if doing swap, but Samsung direct warranty generally does.
It also might be that users don't care to run another rom.
I'm fine on the stock rom, I rooted, and removed all the bloat and can basically do all the same tweaks.
I have custom PRL, icons etc. and my piece of mind for warranty
Click to expand...
Click to collapse
Warrenty is a reason to worry about knox, I have been pretty lucky in regards to turning in phones on warrenty. The one main drawback I would see with towel root is that there would be extra hoops to jump through to install things since you cant do a custom recovery. Not a problem for those with experience, but can trip up people who are not used to linux/android cli tasks. Look at the questions asked in these forums about issues with flashing zips, imagine supporting people with no tech background to do tasks from the cli or a file explorer. It would be cool if someone made a recovery apk for flashing zips from inside android, it might even already exist but I wouldnt know since I alwsys fully root and use custom recovery. I dont use roms so much, but flashable zips is a huge convenience IMO.
Sent from my SM-G900P using XDA Free mobile app

bryanu said:
The other reason is if you'd like to keep your warranty intact.
Knox trip = no longer covered by warranty, only insurance claim with deductible
Click to expand...
Click to collapse
Wrong.
Hardware is still covered with Knox tripped if it's for hardware. At least at my local store(s) and from what I have read on xda it seems to be the same all over.

The legend of the Knox warranty lives on. I've seen posts were people had knox tripped and their devices were still covered for "hardware" issues so I'm not concerned. I was talking to a Samsung rep today about rooting my s5!!!
Sent from my Galaxy Tab S

I am trying to root my Sprint S5, without success. I have tried pretty much every free route, apk included, to no avail. I use mac and linux, so Odin is out. Anyone know something that works? I apologize if this is answered in another thread, but I have not seen it anywhere here, so far.

will upgrading to Lollipop delete installed mod on KitKat?

Hello everyone
I just bought a new Samsung Galaxy S5 international (SM-G900F) and I am about to root it in order to be able to install a sound mod which boosts the sound. I was considering using the one from this thread: http://forum.xda-developers.com/showthread.php?t=2729652
Basically, it will modify the sound setting values found in mixer_path.xml file in /system/etc
How it is going to be done: (Help needed here)
Plan A- I am planning to downgrade to KitKat in order to root without triggering the Knox counter, then install the mod, then upgrade to LolliPop again.
Plan B- Alternatively, I can downgrade to KitKat and root, then install a prerooted lollipop rom (not sure if it will trigger the Knox counter), then install the sound mod.
Plan C- Maybe there is a method you can tell me about to access the system files of the phone from ADB on my pc without rooting and just modify the values found in mixer_path.xml file in /system/etc
Plan D- A less probable way would be to download an original Lollipop Rom, modify the mixer_path.xml file in /system/etc, save it and then flash it to the phone as an official Rom using Kies 3. I don't even know if this is possible.
Whichever method I choose to go with, I intend to unroot once the Mod is installed in order to get OTA updates. (Not sure how to do this)
My questions:
If I upgrade from KitKat to LolliPop, will it write a new mixer_path.xml file with the default values? Or will it keep the modified version of the file?
If I install the Mod on Lollipop, will an update (OTA) write a new mixer_path.xml file with the default values? Or will it keep the modified one?
Also, once my phone is rooted, I believe OTA updates will not work, so how do I manage to get back the OTA updates from Samsung without losing the modified version of mixer_path.xml file in /system/etc? I don't mind losing root access once I have my sound mod installed.
Thank you very much for your answers, and feel free to tell me what is the best plan or point me toward a better method to achieve this, or anything else that I might not know regarding rooting the S5 without triggering the Knox counter.
Have a great day

ofcourse your mods will reset to default values after update....
and if you want ota updates then you need to flash official stock rom via odin

shazore said:
ofcourse your mods will reset to default values after update....
and if you want ota updates then you need to flash official stock rom via odin
Click to expand...
Click to collapse
Thank you Shazore, I guess I will have to root after each update to reapply the mods, it's just that it might take weeks or months to find a vulnerability that allows to root a new build after an update. But I guess the S5 will not receive any further official updates after 5.1.1 which is a piece of cake to root, unlike marshmallow which imho will possibly take a while to get rooted.
Thank you again for the reply and have a great weekend

If you are worried about tripping knox, lollipop is NOT a piece of cake to root......
The only method of rooting LP (that I've read about) is CF Root which WILL trip knox......
If you want to keep knox at 0x0 and be running LP, then you need to 'towelroot' while on KK and use an app like Flashfire to inject root into a LP firmware as it's flashing it......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

keithross39 said:
If you are worried about tripping knox, lollipop is NOT a piece of cake to root......
The only method of rooting LP (that I've read about) is CF Root which WILL trip knox......
If you want to keep knox at 0x0 and be running LP, then you need to 'towelroot' while on KK and use an app like Flashfire to inject root into a LP firmware as it's flashing it......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
In all honesty, around June I spent like a week of googling and reading on how I can get root on lollipop without triggering knox but all I could find was unclear and incomplete tutorials which involved going back to Kitkat and root with towel root and update to lollipop using a modified lollipop rom from Alexander or something like that. I finally gave up because the method was not properly explained which made it too risky to trigger knox.
From your message it sounds like they came up with a new method (chainfire) which I would be happy to try if I have a clear tutorial to follow Would it be possible to point me to the tutorial you followed to root your S5 while keeping knox0?
Thank you in advance for your help

I used the first part of this tutorial to root while still on KitKat........
http://forum.xda-developers.com/showthread.php?t=2699648
then I froze the system apps that controlled firmware updating......
And here is the thread for Flashfire.....
http://forum.xda-developers.com/showthread.php?t=3075433
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

keithross39 said:
I used the first part of this tutorial to root while still on KitKat........
http://forum.xda-developers.com/showthread.php?t=2699648
then I froze the system apps that controlled firmware updating......
And here is the thread for Flashfire.....
http://forum.xda-developers.com/showthread.php?t=3075433
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Thank you for providing the tutorials to follow, it's sad that a full tutorial still doesn't exist, but hopefully people can find your post and get access to both tutorials
I am very excited to get started and about all the cool stuff I wanted to install once rooted.
I will see if I have time next week to backup everything that's on my S5 and get started with downgrading to KK and rooting, what scares me most is this Flashfire process as I have never tried it. I guess if it worked for you it should work for me too
If I encounter any problem I will post it here or/and in the relevant thread.
Thank you again and have a great weekend

Hey....no problem fella......
Just one thing though.......at no time have I ever used Flashfire.......My phone came with KitKat and remains to this day with KitKat......The only reason I even know about Flashfire is that I saw people mentioning it on the Mobile Odin thread (which I have purchased and used on my S2)
I have absolutely no intention of upgrading to lollipop until (if) xposed becomes compatible.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

keithross39 said:
Hey....no problem fella......
Just one thing though.......at no time have I ever used Flashfire.......My phone came with KitKat and remains to this day with KitKat......The only reason I even know about Flashfire is that I saw people mentioning it on the Mobile Odin thread (which I have purchased and used on my S2)
I have absolutely no intention of upgrading to lollipop until (if) xposed becomes compatible.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Thank you for the additional input, xposed is not something I use that often, I just have it on my Galaxy Tab 4 7" to customise the look and add some functionalities to the stock debloated rom.
One of the only reason I need root on my S5 is to have access to the sound settings XML file and boost the headphones amplifier, I don't like using apps that pretend to boost your volume when in fact all they do is to boost your gain which distorts the sound and make it sound louder at the price of poor sound quality. That's why I want to access the sound mixer and increase the output power of the sound card without altering the input gain.
Once someone figures out how to safely bypass the knox security to allow flashing everything out there, I will be more than happy to get a taste of Marshmallow on my S5 Till then, I guess I will have to try it out on my moto g 1st generation, it's amazing what Motorola did with that phone: Water resistant, updates almost as fast as a nexus, descent specs, good screen and long battery life. When I compare it to my S5 it feels like the moto g is a bargain comparing to my powerful but overpriced S5.
I shifted off topic, lol. I will try to find time next week to get root on my S5, thank you again for all the support

Yeah....It looks like Knox is here to stay, and it would seem that most devs have given up on trying to crack it.......
The main reason I use xposed is for Rootcloak......I use some apps that look for root access and refuse to open if they detect it.......
I need these apps, but at the same time, having an unrooted device is really not an option for me.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

keithross39 said:
Yeah....It looks like Knox is here to stay, and it would seem that most devs have given up on trying to crack it.......
The main reason I use xposed is for Rootcloak......I use some apps that look for root access and refuse to open if they detect it.......
I need these apps, but at the same time, having an unrooted device is really not an option for me.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
I didn't know knox cracking was being abandoned by the devs here. That's sad because all current and future Samsung devices will have the knox protection, which means one has to choose between keeping warranty on a bloated slow phone or customising their phone at the expense of losing the warranty. The loss is always on the consumer side and Samsung has everything to win: they win by pushing people to use their useless apps which generates more income for the company (through advertising or data collection), and if you don't want to use these apps and get a clean or custom rom, then you have to root and lose your warranty which gives Samsung a good way to escape their responsibilities whenever a device is faulty because of a bad manufacturing process, therefore they win by not having to fix or replace these faulty devices using the excuse that rooting could have been the cause of the damage.
I live in Germany and from what I have read on many threads here I will not be losing my warranty if I root because the European laws protect the consumer. I still wouldn't want to try my luck and would rather wait that my warranty is almost finished before carelessly rooting and trigger knox, my S5 is covered until December 2016.
Your needs for xposed are justified, there is always a choice to make but Kitkat is not a bad one, it's still a great version of Android and shouldn't cause you any troubles with apps built with lollipop in mind. The only negative thing about Kitkat comparing to lollipop would be the dalvik cache which doesn't give you the same fast launch speed for apps as you would experience under lollipop. But hey, what's 3 seconds longer to launch maps or chrome? It's not like there is fire in the house and you need to find an exit during these 3 seconds relying on Google maps, lol.
Since this thread seems active, I take the chance to ask a question:
I am setting up a phone to give to my mother which lives in another country and I am visiting her soon, I customised the original but rooted rom with the apps I judge useful for her and removed all the crapware.
The problem is: she might encounter a problem at some point (supposed in 6 months) and someone might reset the phone for her, she will be lost once the phone gets back to factory settings and no one around her will have the knowledge to set it the way I did.
So how can I implement the changes and integrate them into the factory image on the device? I don't want to do it through a NANDROID backup because she wouldn't know how to access the recovery and the process will be too complicated compared to just going to the settings and click on factory reset.
Anyone with a good idea or a useful link to another thread explaining g how to do this?

This app.......
https://play.google.com/store/apps/details?id=de.j4velin.systemappmover
will apparently convert 'user' apps into system apps. I guess it does so by moving them to the system app partition. If I understand this correctly, doing this will protect them from erasure even if a factory reset is done.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

keithross39 said:
This app.......
https://play.google.com/store/apps/details?id=de.j4velin.systemappmover
will apparently convert 'user' apps into system apps. I guess it does so by moving them to the system app partition. If I understand this correctly, doing this will protect them from erasure even if a factory reset is done.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
I checked this app on the store and I am going to give it a try, I will copy the apps I need after the reset to the system partition on my moto g and make a factory reset, I will report if it works
Just to make sure I don't get stuck on a bootloop, could you give me your opinion on what folder I need to copy the apps to? And should I copy the installed apps or should I copy the apk version of them? Thank you for your input
Right now the wife is giving me a headache because I spend more time on xda than with her, hahaha, I hope to get the chance to experiment with this app sometimes today.
I wish this app worked on my wife's brain, I need to debloated her and disable the app that makes her so annoying, hahaha
I will be reporting if the app works for creating a custom image for the reset as soon as it's done
Thank you once again.

Lol about the wife.....been there, done that, still wearing the teeshirt.......
About moving the apps.....I don't think you have to do any moving yourself.....
You just install the apps as normal then get the linked app to do the rest.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

keithross39 said:
Lol about the wife.....been there, done that, still wearing the teeshirt.......
About moving the apps.....I don't think you have to do any moving yourself.....
You just install the apps as normal then get the linked app to do the rest.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
I am finally back after spending yesterday and today testing various things I wanted to experiment I used the app you linked to transfer some apps to the system partition, it worked perfectly and the apps I added were still there after resetting my phone Thank you for that one, this will be very useful in the future
Unfortunately the app you linked couldn't do the opposite operation, it couldn't remove the default apps that I didn't need or that were bloatware because this option is not supported in lollipop, so I uninstalled them using titanium backup but I ended up getting error messages and had to restart to twrp recovery where I cleared the cache and the dalvik, unfortunately it didn't help and the phone didn't want to complete the boot, I then had to flash the rom again through adb, then the phone booted fine.
I repeated the operation of removing the unwanted apps using es file explorer and accessing the system folder to delete the apk of the unwatchable apps, this also generated errors and I ended up having the same story as the previous situation where I was unable to boot, my last resort was to flash the rom again.
I concluded that some apps I removed had some sort of link to other apps relying on them, either relying on the manufacturer's framework or it is a security bug I generated where an app is looking for one of the apps I removed to launch. At the end I gave up on seeking a clean rom and this time I will just remove the most annoying apps that are not related to the manufacturer.
As for the wife thing, I might be joining your club of single men, lol, a divorce seems inevitable, but that's definitely not the right place to discuss that
Once again thank you very much, your support was great and I shall pm you to join my future thread(s) the next time I have a query I have clicked the thank you button in every reply you posted, that's to show my gratitude

No problem fella.....i'm not an expert at *all* things Android, but if a question is asked, and I know the answer, I'll do what I can to help/advise.....
I'm still married myself (20+ years).....
All I'll say on that is.....I would have had a shorter prison sentence if I'd committed murder.....and best to leave it at that....lol
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

keithross39 said:
No problem fella.....i'm not an expert at *all* things Android, but if a question is asked, and I know the answer, I'll do what I can to help/advise.....
I'm still married myself (20+ years).....
All I'll say on that is.....I would have had a shorter prison sentence if I'd committed murder.....and best to leave it at that....lol
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Hahaha, I am not willing to serve a 20 years sentence and murdering is for the moment not one of my plans, I say for the moment, lol.
I decided to give to the xda community some of my knowledge as a way to pay back all the help I got in the forums, you can have a look at this link if you ever want to boost your sound
http://forum.xda-developers.com/general/general/guide-technical-explanation-boost-t3202087
Feel free to drop me a reply there if you think something needs to be improved or changed
I am still hoping to get a day away from my wife hopefully this week or the next one, so that I can root my S5 under Kitkat and upgrade to lollipop following the tutorials you shared on a previous post. I will report if it works or I will write here if I have some kind of problem (hopefully not, lol).
Till then I wish you a great day and thank you again for everything

S7, Samsung Health, Knox 0x1

Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k

databoy2k said:
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
Click to expand...
Click to collapse
I've read this:
Downgraded to 6.0.1. stock. Started SHealth, and again upgraded to Nougat.

databoy2k said:
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70712537&postcount=16

databoy2k said:
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
Click to expand...
Click to collapse
You could flash a custom ROM with Magisk installed to have everything working including AndroidPay
Magisk Bypasses Safteynet
Im currently using Superstock Rom and its great ... Playing PokemonGo, using banking apps and AndroidPay on a daily basis.
(and yes Shealth works)

EasyAndroidPro said:
You could flash a custom ROM with Magisk installed to have everything working including AndroidPay
Magisk Bypasses Safteynet
Im currently using Superstock Rom and its great ... Playing PokemonGo, using banking apps and AndroidPay on a daily basis.
(and yes Shealth works)
Click to expand...
Click to collapse
I've had exactly zero luck with Magisk in the past, albeit that was before the proper W8 firmware came out so I was also fighting through issues of using improper firmwares (which have just never worked quite right for me; it seems our Canadian W8's aren't just a CSC change from the F). I was also having problems accessing my carrier's resources, etc. Maybe it's fixed, but my goal was to go back to 100% stock (or as close to as possible). I guess I'm just finally giving up my flashing addiction for the time being.
mashardpro said:
I've read this:
Downgraded to 6.0.1. stock. Started SHealth, and again upgraded to Nougat.
Click to expand...
Click to collapse
Yep worked. Thanks; anyone looking for the updated solution this is certainly one. It did suck to not be able to use Google's app restore function though (as my Nougat backup didn't register as usable on Marshmallow). But I'm up and running and SHealth is happily purring away.
webjunky said:
https://forum.xda-developers.com/showpost.php?p=70712537&postcount=16
Click to expand...
Click to collapse
Thanks, but this had to be crossed with the recommendation above. I was mostly looking to see if there had been an update that I missed.

Make MyKnox work with LP/MM custom roms?

Hi guys! My daily driver is a GS7E but I finally got back my old N9005 after my sister got a new phone. I clearly remember that while using the note 3 there was a rom+kernel combo to make knox work even with root and 0x1 counter. I've been trying in the last 3 hours to make it work again (with xposed and tons of various zips) but nothing works, I still can't make My Knox work.
Every custom ROM I can find is Knox-debloated, but I want to use it..
Do you have any suggestion? I think I was using g00h's ROM but his profile got deleted as I can see, and there are no mirrors or whatsoever..
Thanks!

Mobox said:
Hi guys! My daily driver is a GS7E but I finally got back my old N9005 after my sister got a new phone. I clearly remember that while using the note 3 there was a rom+kernel combo to make knox work even with root and 0x1 counter. I've been trying in the last 3 hours to make it work again (with xposed and tons of various zips) but nothing works, I still can't make My Knox work.
Every custom ROM I can find is Knox-debloated, but I want to use it..
Do you have any suggestion? I think I was using g00h's ROM but his profile got deleted as I can see, and there are no mirrors or whatsoever..
Thanks!
Click to expand...
Click to collapse
Knox is discontinued by samsung myknox app has been removed from playstore it will not work anymore even knox counter is 0x0.
Nowdays in newer phones knox is replaced by something called secure folder.
Hope this will help you save some time