Will this be possible? I was wondering if providing the apk files would help since I got accepted into the beta program but I tripped knox without knowing that Samsung Pay is going to be disabled.
Both apks are in the zip. The framework is what activates Samsung Pay.
https://drive.google.com/file/d/0B9tlO7cZO3X_SEpRZElabFNEeW8/view?usp=docslist_api
Same issue I hope some creates a workaround
Bump for this. I will love whoever does this forever
goobyjr9 said:
Will this be possible? I was wondering if providing the apk files would help since I got accepted into the beta program but I tripped knox without knowing that Samsung Pay is going to be disabled.
Both apks are in the zip. The framework is what activates Samsung Pay.
Click to expand...
Click to collapse
Where were these files located on your device? I'm trying to debug it, but I'm having trouble finding the original location of the apk.
Edit: I have reason to believe that Samsung Pay will work once the beta is over, and that as long as the device is not CURRENTLY rooted, it will work. Let me check with some people, and I'll be back with an update by Monday
just_parker said:
Where were these files located on your device? I'm trying to debug it, but I'm having trouble finding the original location of the apk.
Edit: I have reason to believe that Samsung Pay will work once the beta is over, and that as long as the device is not CURRENTLY rooted, it will work. Let me check with some people, and I'll be back with an update by Monday
Click to expand...
Click to collapse
Well first of all my device is rooted WITH KNOX tripped. That's how I was able to access the apk files.
bump? any updates?
just_parker said:
Where were these files located on your device? I'm trying to debug it, but I'm having trouble finding the original location of the apk.
Edit: I have reason to believe that Samsung Pay will work once the beta is over, and that as long as the device is not CURRENTLY rooted, it will work. Let me check with some people, and I'll be back with an update by Monday
Click to expand...
Click to collapse
Parker, now that beta is over, is what you believe true? I am considering going back to straight stock if it will work with Samsung Pay but I just don't want to go through that if my tripped knox will prevent me from using Samsung Pay... Thanks!
I know this a little late but i have confirmed that samsung pay does not work with a tripped KNOX even if on stock rom and stock kernel. I am not even rooted and I don't have a custom recovery installed but it still didn't work.
BlackMeat_420 said:
I know this a little late but i have confirmed that samsung pay does not work with a tripped KNOX even if on stock rom and stock kernel. I am not even rooted and I don't have a custom recovery installed but it still didn't work.
Click to expand...
Click to collapse
Yeah neither will the fingerprint scanner for logging into certain banking apps that have the fingerprint option.
Once you have rooted your device, it will be damaged irreversibly.
It's more satisfying to keep root, install a custom rom and xposed and rootcloak.
Samsung pay will not work anyways "i think" but at least the banking apps will work 100%!
GuarDiShar said:
Once you have rooted your device, it will be damaged irreversibly.
Click to expand...
Click to collapse
Rooting doesn't damage anything. Software CHOOSING do be a douche is the issue. Assign the blame where it belongs.
Related
My company has instituted use of MaaS360 as a MDM for BYOD android phones. The IT folks are preventing rooted and jailbroken phones from accessing corporate email from exchange.
On my Galaxy S4 I have tried several things to work around, including OTA Rootkeeper, Hide my root app, and SuperSU's temporary unroot. However MaaS360 manages to find out that the phone is still rooted. I tried the solution posted for Mobileiron on this site (freezing the MDM using TiBU immediately after rooting) but that does not work either.
My IT department is fine with "temporary" unroot but they do not think that it is possible to do so in MaaS360 while still ensuring that the device is not permanently rooted. I am wondering if someone knows how MaaS360 figures out that a device is rooted and whether there is a way for it to nor report when the device is temporarily unrooted using one of the methods discussed above.
Have you found a solution to this problem? I was wondering the same thing.
walletless said:
My company has instituted use of MaaS360 as a MDM for BYOD android phones. The IT folks are preventing rooted and jailbroken phones from accessing corporate email from exchange.
On my Galaxy S4 I have tried several things to work around, including OTA Rootkeeper, Hide my root app, and SuperSU's temporary unroot. However MaaS360 manages to find out that the phone is still rooted. I tried the solution posted for Mobileiron on this site (freezing the MDM using TiBU immediately after rooting) but that does not work either.
My IT department is fine with "temporary" unroot but they do not think that it is possible to do so in MaaS360 while still ensuring that the device is not permanently rooted. I am wondering if someone knows how MaaS360 figures out that a device is rooted and whether there is a way for it to nor report when the device is temporarily unrooted using one of the methods discussed above.
Click to expand...
Click to collapse
cloudspy said:
Have you found a solution to this problem? I was wondering the same thing.
Click to expand...
Click to collapse
Nope... the only solution is to do a permanent unroot after setting up the ROM/device to your liking and before adding the MaaS360-enabled account.
Sounds like a reasonable solution to me. Thank you.
walletless said:
Nope... the only solution is to do a permanent unroot after setting up the ROM/device to your liking and before adding the MaaS360-enabled account.
Click to expand...
Click to collapse
walletless said:
Nope... the only solution is to do a permanent unroot after setting up the ROM/device to your liking and before adding the MaaS360-enabled account.
Click to expand...
Click to collapse
Yes, I find it alright. Make sure you reboot twice after doing a perm unroot (and before adding your MaaS360 enabled account). Sometimes it takes a additional reboot before the phone actually removed all su-related binaries.
Sent from xda-developers mobile app on Galaxy S4 using GOLDENEYE ROM
walletless said:
Yes, I find it alright. Make sure you reboot twice after doing a perm unroot (and before adding your MaaS360 enabled account). Sometimes it takes a additional reboot before the phone actually removed all su-related binaries.
Sent from xda-developers mobile app on Galaxy S4 using GOLDENEYE ROM
Click to expand...
Click to collapse
Could you please confirm that it's okay to have a custom ROM flashed while using MDM so long as the device is no longer rooted?
I'd like to do this without ever getting flagged in the first place. My plan is to uninstall maas360, root the device, flash my custom rom, perm unroot the device, reboot twice and reinstall maas360. Will this be okay?
Thanks
illmatik said:
Could you please confirm that it's okay to have a custom ROM flashed while using MDM so long as the device is no longer rooted?
I'd like to do this without ever getting flagged in the first place. My plan is to uninstall maas360, root the device, flash my custom rom, perm unroot the device, reboot twice and reinstall maas360. Will this be okay?
Thanks
Click to expand...
Click to collapse
I believe that answer depends on how your organization has set security policies on the MDM. For me, I have been using custom ROM (GoldenEYE) for several months now, and not been flagged so long as I add the exchange account after doing a full unroot and rebooting twice. You may want to check with your IT if they are OK with custom ROMs.. Most IT would be OK if you unroot I guess.
The steps you outlines are fine - I pretty much use the same sequence everytime I update to a newer version of the ROM. So far, no problems since 6+ months!
you may want to try rootcloak plus http://forum.xda-developers.com/showthread.php?t=2607273
I'd be very interested in hearing if it works for Maas.
abandon42 said:
you may want to try rootcloak plus http://forum.xda-developers.com/showthread.php?t=2607273
I'd be very interested in hearing if it works for Maas.
Click to expand...
Click to collapse
Long-time lurker, first time poster just to confirm that yes the Rootcloak Xposed module worked for Maas360 on my HTC One! -Thanks
Rootcloak settings?
miguelsaps said:
Long-time lurker, first time poster just to confirm that yes the Rootcloak Xposed module worked for Maas360 on my HTC One! -Thanks
Click to expand...
Click to collapse
Excellent. Thanks, Miguelsaps.
What settings did you use in Rootcloak?
SkyHawk4 said:
Excellent. Thanks, Miguelsaps.
What settings did you use in Rootcloak?
Click to expand...
Click to collapse
No problem! All I did was download the RootCloak 1.4 framework in Xposed, then soft-rebooted my phone and and sent myself the Maas360 registration once again and it allowed me to complete it!
Edit: sorry I added the com.fiberlink... in Rootcloak firstly.
miguelsaps said:
No problem! All I did was download the RootCloak 1.4 framework in Xposed, then soft-rebooted my phone and and sent myself the Maas360 registration once again and it allowed me to complete it!
Edit: sorry I added the com.fiberlink... in Rootcloak firstly.
Click to expand...
Click to collapse
hi, could you please share with us your complete settings?
I have n5, currently Cataclysm rom (which comes prerooted), and both xposed with rootcloak and cydia with rootcloak+.
Maas 4.41 still detects root.
if you have an older version, could you please backup it and send me the link to it?
thanks!
mic
Success!
I've succeeded at this. http://forum.xda-developers.com/showpost.php?p=51990953&postcount=4
Hello
I speak very little English, excuse me for my English
I'm not new to the Root,I have a Samsung S4 Root with a lot of application for whom I need a root
My problem is that my company asked me to set the phone control app MaaS360
I installed MaaS360, the app tells me that I do not respect the safety and policy MaaS360 tells me to reset the phone to the original without Root.
I seek a way to make him believe that the phone is not root
Do you have any idea?
It's very urgent
Best regards
Maas360 Validating Samsung enterprse license
hi guys,
im having a problem with my maas360. after activating the maas as a device administrator im stuck with the loading page saying validating samsung enterprise license what does it means ? btw my phone is samsung note 3 and rooted with a custom rom installed.
i dont think i have the same problem with guys years ago . can you please help me with this ?
I have same problem... But ONLY with MIUI - with Flyme, EUI, Lineage, CM... all UNROOTED : MAAS360 WORKING
... And I not understand WHY! (all other app, control my machine... And the result is ALWAYS : UNROOTED)
Inviato dal mio Le X527 utilizzando Tapatalk
Does MAAS360 app is able to check remotly what you install or not? I mean I have I want to install teamviewer on my work tablet and Im afraid that they will notice I installed it. I just want to be in trouble. Does maas360 send any signal to administrator what is installed what not?
Thank you for your help
Hello guys! I'm new to the S5 section and even more new to the T-Mobile area since I'm on AT&T network. I come from a S4 that I could root without tripping Knox and at least use different variants of TW rooms using Safestrap.
I was under the impression that Tmobile S5 version was not as tight as the AT&T version but after reading a few threads I'm not sure.
I have to say that I love the stock UI of S5 more than the one on the S4. That said I still would like to have more control over a few things.
So I could live with a rooted S5 with Xposed Installer and Wanam and a few other Xposed modules.
But I would not like to trip my phones Knox counter.
I wonder if that is possible under BNH5 firmware and how?
Can I root using Towelroot and intall Xposed, Wanam and a few other customization modules without tripping my phone's Knox counter?
Also Would I be able to go back to a virgin Stock Rom without tripping the counter?
I would appreciate all the help.
Thanks.
chiquito3 said:
I wonder if that is possible under BNH5 firmware and how?
Can I root using Towelroot and intall Xposed, Wanam and a few other customization modules without tripping my phone's Knox counter?
Also Would I be able to go back to a virgin Stock Rom without tripping the counter?
Click to expand...
Click to collapse
You cannot root NH5 software directly with towel root, but there is a thread that shows exactly step by step how to downgrade to a version that towel root will root and then go back to the latest. This procedure does NOT trip Knox. Knox is tripped anytime you load a custom recovery or kernel.
So, if you just want root so you can run Xposed and Wannam and what not, that's not a problem and you can odin back to stock if you need to for a return. Look around here on the TMO S5 threads and you'll find all this hashed over and over.
Good Luck!
Hit thanks if I've helped.
chiquito3 said:
Hello guys! I'm new to the S5 section and even more new to the T-Mobile area since I'm on AT&T network. I come from a S4 that I could root without tripping Knox and at least use different variants of TW rooms using Safestrap.
I was under the impression that Tmobile S5 version was not as tight as the AT&T version but after reading a few threads I'm not sure.
I have to say that I love the stock UI of S5 more than the one on the S4. That said I still would like to have more control over a few things.
So I could live with a rooted S5 with Xposed Installer and Wanam and a few other Xposed modules.
But I would not like to trip my phones Knox counter.
I wonder if that is possible under BNH5 firmware and how?
Can I root using Towelroot and intall Xposed, Wanam and a few other customization modules without tripping my phone's Knox counter?
Also Would I be able to go back to a virgin Stock Rom without tripping the counter?
I would appreciate all the help.
Thanks.
Click to expand...
Click to collapse
Yes you can root your phone but you will have to roll back the firmware back NE6 and then use towel root. Once you do that, then you can use pc odin to flash the nh5 firmware and use mobile odin pro to flash the NH5 software back onto your phone and retain root. Just remember that you will not trip knox using the method above, but if you flash a custom recovery or non tmo s5 kernel you will trip knox. There are a few threads here that you help you root and upgrade to keep root. Make sure you read thru some of the rooting threads before you do anything to your phone, It is your responsibility to make sure you know how and what your are doing when flash your phone, We are not responsible if you forget to read or flash something that is not for your type of phone, if you brick your phone or if you trip knox. Also Remember that if you do trip knox, there currently is no way to reset the knox counter, so please Do Not Ask.
Have fun and read before you decide to do anything to your phone..
Sorry for the question but could you pont me to the right thread. I found one that wad NJ ot so clear or explicit.
Sent from my SM-G900T using Tapatalk
chiquito3 said:
Sorry for the question but could you pont me to the right thread. I found one that wad NJ ot so clear or explicit.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2784025
chiquito3 said:
Hello guys! I'm new to the S5 section and even more new to the T-Mobile area since I'm on AT&T network. I come from a S4 that I could root without tripping Knox and at least use different variants of TW rooms using Safestrap.
I was under the impression that Tmobile S5 version was not as tight as the AT&T version but after reading a few threads I'm not sure.
I have to say that I love the stock UI of S5 more than the one on the S4. That said I still would like to have more control over a few things.
So I could live with a rooted S5 with Xposed Installer and Wanam and a few other Xposed modules.
But I would not like to trip my phones Knox counter.
I wonder if that is possible under BNH5 firmware and how?
Can I root using Towelroot and intall Xposed, Wanam and a few other customization modules without tripping my phone's Knox counter?
Also Would I be able to go back to a virgin Stock Rom without tripping the counter?
I would appreciate all the help.
Thanks.
Click to expand...
Click to collapse
First Question is do you have premium handset protection? If so then I wouldnt worry about Knox at all. Handset protection covers everything including running over your phone with a car . I have had devices that I didnt have insurance on in the past when I was a NOOB that had the warranty flag tripped and never had any problems at T-Mobile with replacing it . T-Mobile would rather replace a knox tripped phone over replacing a phone with a cracked screen because they just re-flash the device and pass it along to the next person . It doesnt cost them anything like it would having to repair cracked screens etc... I have the S5 G900T and I rooted while I was still in the T-Mobile store buying it LOL . The sales guy told me their was no way to root it at the time (which he was wrong ). Anyway I understand kind of why you wouldnt want to trip knox but at the end of the day it really wont matter if tmobile is your carrier . There really isnt a difference between a tripped phone and one that isnt when it comes to getting it replaced . I know this from experience and many many others on XDA will tell you the same .
spirodave said:
T-Mobile would rather replace a knox tripped phone over replacing a phone with a cracked screen because they just re-flash the device and pass it along to the next person ..
Click to expand...
Click to collapse
It's my understanding that the KNOX security flag is a electronic fuse. Once tripped it's burned to 1 state and a "re-flash" won't repair that.
That said, I could see T-Mobile taking it back because of the value of the replaceable parts, including an intact display. Enough profit is made on the extended protection plans that T-mobile could grind them all up and use them for fancy pavement surfacing. I've yet, for example to replace "anything" under an extended service plan. I get them to be careful, but there's been plenty of $$$ for those plan providers.
Extended service plans? Total and absolutely guaranteed profit for vendors.
galaxyuser88 said:
http://forum.xda-developers.com/showthread.php?t=2784025
Click to expand...
Click to collapse
I read the towelroot thread but it does not say anything on how to downgrade firmware version.
Sent from my SM-G900T using Tapatalk
hI THIS IS WHAT YOU NEED TO DO
1. DOWNLOAD G900TUVU1ANE6 FULL STOCK TAR FROM HERE https://www.androidfilehost.com/?fid=23501681358541270
2. uNZIP THE FILE AND FLASH IT USING PC ODIN. WHICH YOU CAN GET HERE https://www.androidfilehost.com/?fid=23212708291676783
3. ROOT WITH TOWELROOT . TOWELROOT IS HERE https://towelroot.com/
4.DOWNLOAD MOBILE ODIN PRO FROM THE PLAYSTORE IT WILL COST YOU AROUND $6
5.DOWNLOAD THE NEWEST STOCK TAR TMB-G900TUVU1BNH5 FROM SAMMOBILE OR FOR A MUCH FASTER LINK GET IT HERE https://mega.co.nz/#!F0gFFIpL!SdOFS_5OSOB6b1WUSxfVR286LgrAeDdugRRC5-G0dQ8
6. UNZIP THE FILE AND COPY IT TO YOUR SDCARD OR INTERNAL STORAGE ON YOUR PHONE.
7. USING MOBILE ODIN PRO CHOOSE THE OPEN FILE SELECTION AND THEN CHOOSE THE FILE THAT YOU COPIED TO THE PHONE
8. IGNORE THE WARNING FROM MOBILE ODIN REGARDING KNOX. IT WONT TRIP. TICK EVEROOT AND INJECT SUPERSU FLASH THE PHONE .
YOUR PHONE SHOULD BE ROOTED UPON ONCE IT RESTARTS AND ON THE NEWEST FIRMWARE.
YOUR BOOTLOADER CAN NOT BE UPGRADED BY MOBILE ODIN. THAT CAN BE FLASHED SEPERATELY BY USING PC ODIN.LOOK FOR THE BOOTLOADER FILE IF YOU WISH TO UPGRADE IT BUT IN MY OPINION IT IS NOT CRITICAL TO INSTALL AT THIS POINT. MOST OF THESE FILES CAN BE FOUND HERE http://forum.xda-developers.com/showthread.php?t=2761412 OR HERE http://forum.xda-developers.com/showthread.php?t=2715487
IF YOU CANT FIND SOMETHING USE GOOGLE.
FINALLY WHATEVER HAPPENS TO YOUR PHONE IS SOLELY YOUR RESPONSIBILITY.
I WOULD READ THESE THREADS BEFORE DOIN G ANYTHING
http://forum.xda-developers.com/showthread.php?t=2790292 http://forum.xda-developers.com/tmobile-galaxy-s5/general/nh5-stock-rom-ur-phone-to-stock-t2901732 http://forum.xda-developers.com/showthread.php?t=2784025 http://forum.xda-developers.com/tmo...all-updatetmb-g900tuvu1bnh5-size-1-5-t2873090 http://forum.xda-developers.com/tmo.../experimental-how-to-root-triggering-t2845421
LASTLY YOU NEED TO KNOW THAT XPOSED DOES NOT PLAY WELL WITH THE S5 IT BREAKS PRIVACY MODE S HEALTH CAUSES LAG AND IS ONLY USEFUL ON DALVIK. ONCE ANDROID L IS RELEASED . IT WILL BE USING THE ART ANDROID RUNTIME WHICH IS NOT COMPATIBLE WITH XPOSED .
HAVE FUN!
I've just bought edge few days ago and wanted to know if rooting was worth it.
Will fingerprint still work?
Will i lose any functions?
is it easy to remove root and go back to stock?
which custom rom is most stable?
thanks
Will fingerprint still work? DEPENDS ON THE METHOD OF ROOT
Will i lose any functions? SAME AS ABOVE
is it easy to remove root and go back to stock? YES
which custom rom is most stable? I like Xtestolite with the newest unikernal
Running 5.0.2, rooted with Ping Pong Root.
Fingerprint unlock still works.
Haven't noticed any functionality failure, aside from no OTA updates...
As for unrooting, there are guides out there on the internets, however, from my understanding it boils down to "Use smart switch".
Can't speak on custom roms yet. Haven't taken the plunge and given up my Knox status... yet.
There doesn't appear to be an exploit for 5.1.1 yet (please someone correct me) to allow us to root 5.1.1 without flashing (and therefore tripping Knox) unless you are running a T-Mobile specific variant of our beautiful phone.
Hope that helps?
Mischala said:
Running 5.0.2, rooted with Ping Pong Root.
Fingerprint unlock still works.
Haven't noticed any functionality failure, aside from no OTA updates...
As for unrooting, there are guides out there on the internets, however, from my understanding it boils down to "Use smart switch".
Can't speak on custom roms yet. Haven't taken the plunge and given up my Knox status... yet.
There doesn't appear to be an exploit for 5.1.1 yet (please someone correct me) to allow us to root 5.1.1 without flashing (and therefore tripping Knox) unless you are running a T-Mobile specific variant of our beautiful phone.
Hope that helps?
Click to expand...
Click to collapse
You say installing custom roms will affect knox. That is not entirely true. As long as the rom is based on the original kernel k box should stay 0*0
Snowby123 said:
You say installing custom roms will affect knox. That is not entirely true. As long as the rom is based on the original kernel k box should stay 0*0
Click to expand...
Click to collapse
I was under the impression that flashing Anything that was not a signed Samsung package would trip the knox bit.
can you link any technical explanation on how the Knox detection functions? I haven't been able to find anything about it except Samsung's spiel about how Knox protects corporate users.
Mischala said:
I was under the impression that flashing Anything that was not a signed Samsung package would trip the knox bit.
can you link any technical explanation on how the Knox detection functions? I haven't been able to find anything about it except Samsung's spiel about how Knox protects corporate users.
Click to expand...
Click to collapse
Honestly I understand little of the technical jargon but I have proof that not all roms trip knox
Some useful info. Thanks all.
I've updated to the 5.1.1 so probably won't root for the time being as seems some have faced issue.
riz157 said:
Some useful info. Thanks all.
I've updated to the 5.1.1 so probably won't root for the time being as seems some have faced issue.
Click to expand...
Click to collapse
Nothing wrong with that. Although root has both pros and cons, it is only useful for some. No matter which you choose, it will be a good choice.
the phone in question is a T mobile Galaxy S5, used to be mine running full root since 4.4.4 and had cn 11 on it, now wife is useing it and she wated it stock, so I odined the latest stock t mobile 5.0 firmware onto it, since then it has updated twice to 5.1.1 as I'm not too familiar with 5.1.1 I figured I better ask if it can be rooted.
if it can it will be much appreciated, right now it has done random reboots three times so far today and she is about to go back to Applel
5.1.1 can be rooted using hispasian's kernel. It can find in the android development thread. BTW, tell your wife that Apple is tight about "rolling back" and/or if at all, to previous ios versions if the new version stinks. I was lucky to perform rollbacks on older iphone generations but the newer ones are harder for obvious reasons. I stayed on 4.4.2 because of towelroot -- I'm not too fond of 5.1.1 because of the lag and unstable root methods right now.
Any questions? Please let me know. We would wan't want your spouse to join the "dark side" we call Apple. =) <couldn't resist the star wars pun there>
Thanks I'll loom there here in a minute I want her to be an android person I like androids better because you can remove the SD card, Apple has no SD card, plus as long as it's not a s6 you can swap batteries, I usually keep two spares in my Jeep when we go looking in NC for houses just in case
Sent from my SCH-I545 using XDA Free mobile app
I meant FOL1 in the original thread
Please excuse my stupidity
well in another thread i was wondering if flashing TWRP+CM still works on FOL1 & the user said yes, so.... i'm sure root is always possible, unless your question is to keep knox (you're probably out of warranty anyway)
there are modified TW roms that are prerooted if self rooting fails
random reboots with what apps installed? disable any you dont use, disable gestures, samsung crap, etc etc...
I don't want knox, I don't want 5.1.1 either what I want is to put 4.4.4 on in or 4.4.2 and root it real fast before it updates
wolfen1086 said:
I don't want knox, I don't want 5.1.1 either what I want is to put 4.4.4 on in or 4.4.2 and root it real fast before it updates
Click to expand...
Click to collapse
not sure what the rush is, there is no such thing as sudden updates that you cant stop, if you flash 4.4 then it's stuck on 4.4, but what if the newer baseband wont work well with the old android?
also, 4.4 is crap, you'll be insecure with fewer features & so on
i really find it unlikely that 5.1.1 is causing all problems, also you could even try 5.0.1
wolfen1086 said:
I don't want knox, I don't want 5.1.1 either what I want is to put 4.4.4 on in or 4.4.2 and root it real fast before it updates
Click to expand...
Click to collapse
Turn off wifi and mobile data....
I tried but I was too late it went to 5.1.1, it is rooted though so until XDA cones out with a way to unlock the bootloader I have to wait. Because if I try installing TWRP like I did at first it hangs on the custom love indicator screen
Sent from my SCH-I545 using XDA Free mobile app
wolfen1086 said:
I tried but I was too late it went to 5.1.1, it is rooted though so until XDA cones out with a way to unlock the bootloader I have to wait. Because if I try installing TWRP like I did at first it hangs on the custom love indicator screen
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
uh, at&t variant is locked, tmobile is unlocked... something is odd with this whole thread
Is there a root method for FOL1 that doesn't void Knox?
Playb3yond said:
Is there a root method for FOL1 that doesn't void Knox?
Click to expand...
Click to collapse
No, but it's hilariously easy to get Samsung to honor a warranty on a device with a tripped Knox flag, if that's what you're worried about
thisisapoorusernamechoice said:
No, but it's hilariously easy to get Samsung to honor a warranty on a device with a tripped Knox flag, if that's what you're worried about
Click to expand...
Click to collapse
What about OneClickRoot.apk
thisisapoorusernamechoice said:
No, but it's hilariously easy to get Samsung to honor a warranty on a device with a tripped Knox flag, if that's what you're worried about
Click to expand...
Click to collapse
What about OneClickRoot.apk
thisisapoorusernamechoice said:
No, but it's hilariously easy to get Samsung to honor a warranty on a device with a tripped Knox flag, if that's what you're worried about
Click to expand...
Click to collapse
I have tried kingroot, kingoroot and kingroot pc version.
All of these are failed can I root without tripping Knox or can I reset my flash counter? (I read flash counter is e-fused)
Galaxy S9+
SM G965F
If there were a way to root WITHOUT tripping Knox, do you think there would ever be a root that did trip it?
Sent from my SM-G965U using Tapatalk
tdevaughn said:
If there were a way to root WITHOUT tripping Knox, do you think there would ever be a root that did trip it?
Sent from my SM-G965U using Tapatalk
Click to expand...
Click to collapse
Sorry I can't understand English very well, can you explain a little bit? If I root my device with tripping knox (0x1) can I use Samsung Health or Galaxy Wearable and get OTA updates?
I use Samsung Health an Wearable with root, no Problems.
But you don't get OTA Updates anymore.
WodanGrimnar said:
I use Samsung Health an Wearable with root, no Problems.
But you don't get OTA Updates anymore.
Click to expand...
Click to collapse
Thank you for helping, my last questions:
Can I download them and install manually or by firechain? This is my first root so will I get important disadvantages?
Download manually.
Beside tripping Knox and no OTA's anymore no disadvantages. Maybe your guarantee is Void after rooting.
Don't do it! It's not worth it. You will lose guarantee. Google Camera is also available without root, if that's one of your reasons.
selimsandal141 said:
can I reset my flash counter? (I read flash counter is e-fused)
Click to expand...
Click to collapse
The answer to this is no.
It's an actual fuse that blows.
Jogg3r said:
Don't do it! It's not worth it. You will lose guarantee. Google Camera is also available without root, if that's one of your reasons.
Click to expand...
Click to collapse
scottusa2008 said:
The answer to this is no.
It's an actual fuse that blows.
Click to expand...
Click to collapse
So what are the disadvantages of knox trip and flash counter other than guarantee?
selimsandal141 said:
So what are the disadvantages of knox trip and flash counter other than guarantee?
Click to expand...
Click to collapse
Besides the usual risks involved with a rooted device...
Knox becomes permently disabled and any apps that depend on it will not work.. So Samsung pay, samsung health, secure folders, samsung pass are a few I know of that would not work.
Other apps may also pick up on the knox trip and/or detect the root will also not work.. Depending on the root utility or what's all included with the root used sometimes you can hide the root from some apps, sometimes you can't. I would not suggest being of the mindset that once done you won't have to worry about it.. As apps are updated things can change.
On a a side note there have been ways to get Samsung health to work posted on the internet, but how well they work or for how long may vary.
Samsung Health works without any Problems here, sync with Gear S3 without issues.
Rooted with Magisk, Soldiers Rom and Firmware.
I rooted my Note 9 SM-N960N with Magisk, Knox tripped, but working S-Health, Samsung Pass (with little tweak with the help of Es File Explorer)
Izmile said:
I rooted my Note 9 SM-N960N with Magisk, Knox tripped, but working S-Health, Samsung Pass (with little tweak with the help of Es File Explorer)
Click to expand...
Click to collapse
Can you tell us what tweak you did to get Samsung pass to work?
Samsung Pass Working On Rooted Device
ShaDisNX255 said:
Can you tell us what tweak you did to get Samsung pass to work?
Click to expand...
Click to collapse
Sorry for the late reply!
Well basically, you just have to rename the Samsung Pass app's extension located in:
1. system/priv-apps folder
2. system/data/app folder
Then reboot your device...
This guy over here found the solution for this: https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977
Edit:
Original Samsung Pass menu is now replaced with toggle buttons. Flip the toggles and you're set!
Check attached images (I'm rooted, with a custom kernel, working Samsung Pass).
selimsandal141 said:
Sorry I can't understand English very well, can you explain a little bit? If I root my device with tripping knox (0x1) can I use Samsung Health or Galaxy Wearable and get OTA updates?
Click to expand...
Click to collapse
First I rooted mine using custom rooted kernel (ElementalX), that time I was not able to use S Health, but this method solved the problem: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
But I'd recommend you to root your device through Magisk. (You have to install TWRP, then flash Magisk.) It's systemless, this way you can get OTA updates!
It should be worth noteing that the classic root that many users are pointing to will trip knox, however there are methods that do not trip knox but are not exactly the same persistent root methods. Both S7 and S8 had the same problem but yet methods existed that allowed rooting without triggering knox.