Hey I believe many people have questions around the KNOX and warranty void if you root/install custom recovery.
So I woud like to know:
Is there any software besided KingOroot (doesn't work in A5 510M) or Kingroot (I'm not installing that thing because plenty of people says it steal your data or are impossible to remove) which can root without messing with partitions / custom recovery, meaning it won't trigger the knox counter?
Has anyone confirmed that by only having the KNOX counter triggered samsung has denied to give warranty? Even if the phone is unroot?
Is there any method that roots the device without KNOX tripping?
Thanks
if you are on a 5.1.x device, you might wanna give systemless root a try, i think they ported it to 5.1.x as it was a Marshmallow solution initially.
aside of that, nope.
also, a few regions, like Europe, do not accept root, and especially knox triggering as a warranty void.
and my personal two cents, trigger it, no worth at all, if your device ends up unbootable, there is no way they are going to bother reading through your chip of what you have done, most of the time you'll win the procedures if you need warranty
PlutoDelic said:
if you are on a 5.1.x device, you might wanna give systemless root a try, i think they ported it to 5.1.x as it was a Marshmallow solution initially.
aside of that, nope.
also, a few regions, like Europe, do not accept root, and especially knox triggering as a warranty void.
and my personal two cents, trigger it, no worth at all, if your device ends up unbootable, there is no way they are going to bother reading through your chip of what you have done, most of the time you'll win the procedures if you need warranty
Click to expand...
Click to collapse
thanks pal! I believe samsung has made it very easy for support to check whether the knox is triggered or not, otherwise how would it help anything with them fixing less phones?
In germany (its in europe,lol) knox counter on 1 is not a problem when in warranty,just look my thread in q/a section.
The only way they would know that is through going in Download Mode... So, this is just a crazy thought, but I always planned that if something went so wrong that I couldn't fix it myself (I mean if I can go to Download I can probably still fix whatever is wrong unless the device is bricked), I would just break the volume buttons, so that they can't get to Download Mode either. I know, a rash decision, but just food for thought.
Kingroot is easily removed. Don't believe all the silly scare mongering.
It's the most successful root exploit available without tripping knox.
ashyx said:
Kingroot is easily removed. Don't believe all the silly scare mongering.
It's the most successful root exploit available without tripping knox.
Click to expand...
Click to collapse
I have read plenty of cases of the thing working like a virus, sending data to china, making it impossible to remove. I will not put that in my phone. I have tried kinOroot and it didn't work. But sent stuff outside anyways...
fscussel said:
I have read plenty of cases of the thing working like a virus, sending data to china, making it impossible to remove. I will not put that in my phone. I have tried kinOroot and it didn't work. But sent stuff outside anyways...
Click to expand...
Click to collapse
So you just go from what read rather than try it yourself and you think KingOroot is different? It does contact servers in China, that's how it works.
It's easily removed by simply uninstalling or using SuperSume.
Millions of people have used it and I don't know of one documented case of someone being hacked after using it lol.
KingRoot contacts servers in China because it takes little-to-no space. A version of it that doesn't have to contact any server, and still grant you root access... Well, such an app would be over 3GB big, and would be of the same size, even after it finishes the job and gets you root access. It would be extremely inefficient, and that is an understatement. The servers in China contain the exploits that can be used to grant access to root without using a custom recovery (as a custom recovery would trip KNOX). There are thousands and thousands of files in those servers. As I said, it would be possible to make a one-click-root app that can root thousands of devices and that doesn't make contact with any server, but you would have to include all those thousands of files in the app, in order for it to work. No one is crazy enough to do such a thing.
ashyx said:
So you just go from what read rather than try it yourself and you think KingOroot is different? It does contact servers in China, that's how it works.
It's easily removed by simply uninstalling or using SuperSume.
Millions of people have used it and I don't know of one documented case of someone being hacked after using it lol.
Click to expand...
Click to collapse
King-V said:
KingRoot contacts servers in China because it takes little-to-no space. A version of it that doesn't have to contact any server, and still grant you root access... Well, such an app would be over 3GB big, and would be of the same size, even after it finishes the job and gets you root access. It would be extremely inefficient, and that is an understatement. The servers in China contain the exploits that can be used to grant access to root without using a custom recovery (as a custom recovery would trip KNOX). There are thousands and thousands of files in those servers. As I said, it would be possible to make a one-click-root app that can root thousands of devices and that doesn't make contact with any server, but you would have to include all those thousands of files in the app, in order for it to work. No one is crazy enough to do such a thing.
Click to expand...
Click to collapse
I have read that if you try to remove it you can in fact brick your cell...
fscussel said:
I have read that if you try to remove it you can in fact brick your cell...
Click to expand...
Click to collapse
Holy smokes...is this serious? :sly:
ashyx said:
Holy smokes...is this serious? :sly:
Click to expand...
Click to collapse
why so funny? Reson is simple:
After people install kingroot it add many unwanted programs, and also refuses to be uninstalled. People then try to use SuperSU ME to remove it and leave just supersu, and in this process many have got a bricked device. They say this happens because of the kingroot's code to fight anything that tries to remove it.
Now, are you some sort of associate of kingroot?
PlutoDelic said:
if you are on a 5.1.x device, you might wanna give systemless root a try, i think they ported it to 5.1.x as it was a Marshmallow solution initially.
aside of that, nope.
also, a few regions, like Europe, do not accept root, and especially knox triggering as a warranty void.
and my personal two cents, trigger it, no worth at all, if your device ends up unbootable, there is no way they are going to bother reading through your chip of what you have done, most of the time you'll win the procedures if you need warranty
Click to expand...
Click to collapse
systemless root needs custom recovery installed as far as I can tell. So knox counter already 0x1 because of custom recovery.
Also I would like to know, if I install custom recovery, and the an OTA update comes, for 6.0, I would have to first remove TWRP, as so to use the OTA, after that, reinstall TWRP, would that trigger the knox again?
0x2 ??
fscussel said:
why so funny? Reson is simple:
After people install kingroot it add many unwanted programs, and also refuses to be uninstalled. People then try to use SuperSU ME to remove it and leave just supersu, and in this process many have got a bricked device. They say this happens because of the kingroot's code to fight anything that tries to remove it.
Now, are you some sort of associate of kingroot?
Click to expand...
Click to collapse
They say, he says, she says, do you actually have a clue what you are talking about?
I'm pretty sure I do.
It can be removed like any other app.
If you actually knew what you were talking about you'd know that.
It wont allow another root exploit to easily replace it, this is down to some silliness between Chainfire and King team. It is a pain but it can still be removed or replaced no problem. I wrote a whole guide how to do it.
Literally millions have achieved root with KingRoot and for many is the only way they can.
I dont advocate it nor am I against it.
Dont judge something until you've tried it.
I'll say no more on the matter now as I'm getting dizzy.
ashyx said:
They say, he says, she says, do you actually have a clue what you are talking about?
I'm pretty sure I do.
It can be removed like any other app.
If you actually knew what you were talking about you'd know that.
It wont allow another root exploit to easily replace it, this is down to some silliness between Chainfire and King team. It is a pain but it can still be removed or replaced no problem. I wrote a whole guide how to do it.
Literally millions have achieved root with KingRoot and for many is the only way they can.
I dont advocate it nor am I against it.
Dont judge something until you've tried it.
I'll say no more on the matter now as I'm getting dizzy.
Click to expand...
Click to collapse
1) I don't know if it works in my A5 2016 510M, can't find a compatible list or a report.
2) I have read reports of problems uninstalling it.
3) I have read reports of problems uninstalling it with SuperSU Me, including bricking.
4) I find you very arrogant.
fscussel said:
1) I don't know if it works in my A5 2016 510M, can't find a compatible list or a report.
2) I have read reports of problems uninstalling it.
3) I have read reports of problems uninstalling it with SuperSU Me, including bricking.
4) I find you very arrogant.
Click to expand...
Click to collapse
You are obviously learning what you know from other misinformed users.
1. Just try it if it doesn't work it doesn't work just uninstall it.
2. As I have said, no such issue.
3. There's a reason why replacing it with SuperSU bricks some devices and it has absolutely nothing to do with kingroot.
If you attempt to replace it with SuperSU on anything above 5.0.2 on a Samsung device it's likely to soft brick it and cause a boot loop.
This is due to Samsungs root restriction policy in the kernel. The same goes for Android 6.0 devices.
To root with supersu on these devices you need a patched boot.img to remove the selinux restriction.
4. I find you very misinformed.
ashyx said:
You are obviously learning what you know from other misinformed users.
1. Just try it if it doesn't work it doesn't work just uninstall it.
2. As I have said, no such issue.
3. There's a reason why replacing it with SuperSU bricks some devices and it has absolutely nothing to do with kingroot.
If you attempt to replace it with SuperSU on anything above 5.0.2 on a Samsung device it's likely to soft brick it.
This is due to Samsungs root restriction policy in the kernel. The same goes for Android 6.0 devices.
To root with supersu on these devices you need a patched boot.img to remove the selinux restriction.
4. I find you very misinformed.
Click to expand...
Click to collapse
very misinformed but I have just saved my device from brick, because if you did your work your would see it's android 5.1.1 and it's samsung.
Now let me know if it works with a samsung 5.1.1 with KNOX and perhaps I will try it.
Also let me know how to remove it and install SuperSU over it.
fscussel said:
very misinformed but I have just saved my device from brick, because if you did your work your would see it's android 5.1.1 and it's samsung.
Now let me know if it works with a samsung 5.1.1 with KNOX and perhaps I will try it.
Also let me know how to remove it and install SuperSU over it.
Click to expand...
Click to collapse
Kingroot won't brick your device, replacing it with supersu will. Not sure where in this discussion I said anything to the contrary? :what:
ashyx said:
Kingroot won't brick your device, replacing it with supersu will. Not sure where in this discussion I said anything to the contrary? :what:
Click to expand...
Click to collapse
very non-productive answer... please check again
Related
The first 3 things I did when I got my S4 were:
- Open the packaging
- Update the firmware
- Root the ROM
Then... I find out afterwards about this knox fiasco and guess what? I'm 0x1 - I ain't even mad bro.
What I am mad about however, is the fact I cant seem to achieve a full device root, only can on do what most are calling a 'partial root' - and that's whether that be by installing a pre-rooted rom or using a flashable root file.
That affects me because half my root apps work, and half don't.
For instance: Titanium Backup? all good... Helium? Says cant work, no root (yes I know about desktop method)
So my questions are these:
1. Is there a definite way of achieving full device root on a knox-enabled rom?
2. If not, how likely is it to be possible in future?
3. If unlikely (or impossible) is the only option an AOSP rom? and are they even fully rootable when knox enabled?
If there is no hope on the horizon, I think I'm gonna have to flog this sucker on eBay.
melvatron said:
The first 3 things I did when I got my S4 were:
- Open the packaging
- Update the firmware
- Root the ROM
Then... I find out afterwards about this knox fiasco and guess what? I'm 0x1 - I ain't even mad bro.
What I am mad about however, is the fact I cant seem to achieve a full device root, only can on do what most are calling a 'partial root' - and that's whether that be by installing a pre-rooted rom or using a flashable root file.
That affects me because half my root apps work, and half don't.
For instance: Titanium Backup? all good... Helium? Says cant work, no root (yes I know about desktop method)
So my questions are these:
1. Is there a definite way of achieving full device root on a knox-enabled rom?
2. If not, how likely is it to be possible in future?
3. If unlikely (or impossible) is the only option an AOSP rom? and are they even fully rootable when knox enabled?
If there is no hope on the horizon, I think I'm gonna have to flog this sucker on eBay.
Click to expand...
Click to collapse
1. No.
2. Probably not.
3. AOSP is always the best option if full device control is something you want. Knox is something that prevents root from working properly. There is little to no hope on the horizon, so my advice is: Get your listing ready.
Don't you feel "safer" having Knox protecting your device from you (and protecting Samdung from warranty liability)?
Yeah sure, I feel safer.... if by safe, you mean imprisoned and my freedom restricted.
I coulda just bought an iPhone off the bat if i wanted that kinda safety!
If you have rooted your N6P and you are at a store and want to use Google Pay, is there a way of quickly (on the fly as it were ) unrooting the phone,, making purchase and then rerooting?
Go into SuperSU. Uncheck Enable Superuser. Add your cards. Turn root back on and you're good to go. It appears the only caveat to root is that you're unable to add payment methods. You should be able to pay.
Cares said:
Go into SuperSU. Uncheck Enable Superuser. Add your cards. Turn root back on and you're good to go. It appears the only caveat to root is that you're unable to add payment methods. You should be able to pay.
Click to expand...
Click to collapse
Have you actually tested this at a terminal? Everything I've read says root or custom roms will not work with Android Pay. You can unroot and add the cards, but it will still not function at a POS terminal. I am yet to find someone that can confirm it works the way you mentioned. Everyone agrees that you can add the cards... but that's where the functionality stops.
Tried this method on my Nexus 6. It knows I'm rooted, even if I've disabled SU entirely and rebooted.
Have a search about, at least one of two people have confirmed that they have paid with root disabled, but only if the system partition hasn't been changed
So how do you ensure the system partition is not changed?
kboya said:
Have a search about, at least one of two people have confirmed that they have paid with root disabled, but only if the system partition hasn't been changed
Click to expand...
Click to collapse
Pardon my ignorance here... but doesn't rooting the device modify the system partition? If not... maybe that's the difference with the other threads I've seen. Everyone was using custom roms as far as I know. I'd like to be able to root so I can use adblocker and still use Android Pay. I can live without a custom rom on stock android... but I really miss adblocker.
teknomar7 said:
Have you actually tested this at a terminal? Everything I've read says root or custom roms will not work with Android Pay. You can unroot and add the cards, but it will still not function at a POS terminal. I am yet to find someone that can confirm it works the way you mentioned. Everyone agrees that you can add the cards... but that's where the functionality stops.
Click to expand...
Click to collapse
I just added my cards. I'll test it out later today. Need to find a store that takes Android Pay
teknomar7 said:
Pardon my ignorance here... but doesn't rooting the device modify the system partition? If not... maybe that's the difference with the other threads I've seen. Everyone was using custom roms as far as I know. I'd like to be able to root so I can use adblocker and still use Android Pay. I can live without a custom rom on stock android... but I really miss adblocker.
Click to expand...
Click to collapse
There's a root without changing system. As I said, have a search about. I read it earlier today or perhaps yesterday. There's a thread about the root without system.
Thanks... found the link.
http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
cool, no worries.
So I can confirm that Android Pay will not let you add cards while rooted, but it will let you complete a payment at a terminal while root in SuperSU is enabled. So once you have your payments setup, you can root and use Android Pay.
I own a store with a terminal that accepts Android Pay and have tested it a few different ways over the past 2 days. Every way worked. Unrooted, root simply disabled, root enabled.
The only thing root does is makes it so you can't add a card.
And I have regular root, not the new systemless root.
ArkAngel06 said:
So I can confirm that Android Pay will not let you add cards while rooted, but it will let you complete a payment at a terminal while root in SuperSU is enabled. So once you have your payments setup, you can root and use Android Pay.
I own a store with a terminal that accepts Android Pay and have tested it a few different ways over the past 2 days. Every way worked. Unrooted, root simply disabled, root enabled.
The only thing root does is makes it so you can't add a card.
And I have regular root, not the new systemless root.
Click to expand...
Click to collapse
Can you still pay after a reboot? Thanks.
It works. I wish the misinformation would simply stop. It has worked on devices in the past, it works on devices now and it will most likely work on devices in the future. We had threads before launch how root would disable bank apps, fingerprint sensor, android pay etc and it is all simply untrue.
It works.
boxcar8028 said:
Can you still pay after a reboot? Thanks.
Click to expand...
Click to collapse
Lol, I'll have to try tomorrow.
Was this explanation debunked, then?
http://www.xda-developers.com/googl...-with-root-and-android-pay-in-the-xda-forums/
You
Aridon said:
It works. I wish the misinformation would simply stop. It has worked on devices in the past, it works on devices now and it will most likely work on devices in the future. We had threads before launch how root would disable bank apps, fingerprint sensor, android pay etc and it is all simply untrue.
It works.
Click to expand...
Click to collapse
Yes, but Google stated that Android Pay can't be used with root. So of course there will some question to it.
source
And root absolutely does effect Android Pay. However if seems only while adding payment methods, and nothing once they are added.
What Google is using to determine if the device has been tampered with: https://koz.io/inside-safetynet/
Its definitely an interesting and pretty secure setup. Since it seems to happen real-time, maybe they turned off the "su_files" check and thats why Android Pay works on rooted devices now.
boxcar8028 said:
Can you still pay after a reboot? Thanks.
Click to expand...
Click to collapse
So tried it again today after rebooting with root enabled and it does not work. So there you go. Android Pay does not work while rooted, period.
It does work with root simply disabled in the SuperSu app and then a reboot.
Maybe the new systemless root, though chainfire said if it does work, it was unintentional and Google will probably patch it.
ArkAngel06 said:
So tried it again today after rebooting with root enabled and it does not work. So there you go. Android Pay does not work while rooted, period.
It does work with root simply disabled in the SuperSu app and then a reboot.
Maybe the new systemless root, though chainfire said if it does work, it was unintentional and Google will probably patch it.
Click to expand...
Click to collapse
This is correct. If you try to pay, after adding your cards and re rooting, it will fail.
You must disable root again to pay. You can reenable after.
*I know this must have been answered before, I am sorry for playing the newbie, but I couldn't find this anywhere.
I need to know exactly what is at stake for rooting my device, what would I lose access to, and what not.
I've read somewhere that you lose DRM or something like that, is that meaning I will not be able to watch Netflix download and go, or Google Play Music, etc? what does it means?
LionLorena said:
*I know this must have been answered before, I am sorry for playing the newbie, but I couldn't find this anywhere.
I need to know exactly what is at stake for rooting my device, what would I lose access to, and what not.
I've read somewhere that you lose DRM or something like that, is that meaning I will not be able to watch Netflix download and go, or Google Play Music, etc? what does it means?
Click to expand...
Click to collapse
You will lose your warranty because you have to unlock your bootloader but if anything goes wrong you can always relock your bootloader and take your phone to a service center and claim your warranty they don't even check it in most cases other than that everything works fine
Sent from my Moto G4 Plus using Tapatalk
prajwal2001 said:
You will lose your warranty because you have to unlock your bootloader but if anything goes wrong you can always relock your bootloader and take your phone to a service center and claim your warranty they don't even check it in most cases other than that everything works fine
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
LionLorena said:
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
Click to expand...
Click to collapse
Nothing else only warranty
Sent from my Moto G4 Plus using Tapatalk
LionLorena said:
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
Click to expand...
Click to collapse
Provided you're still on the stock ROM, I don't think rooting affects your anti-theft protection (I recall it's called Factory Reset Protection?). Even if you've enabled OEM unlocking in Developer Options, someone resetting your phone would still need your Google credentials to use the device. Also, if you're logged into your device at the time, you could still locate and wipe your phone via Android Device Manager.
Of course, with an unlocked bootloader and custom recovery (as is generally required to root), someone could still flash a custom ROM and bypass those protections and, also, could in theory still access your data. (but only if they have physical access to your device)
As for DRM, I'm not sure but some apps have been/are now detecting the presence of root and will refuse to work (Snapchat, Pokemon Go, some banking apps come to mind) or for other devices, Android Pay and other security dependent features may not work. I recall magisk, a root manager, does have the ability to mask root from those apps, as well as pass SafetyNet, which is Google's security/anti-tamper detection. Your experience may vary. However, some apps require root access to function properly (e.g. kernel managers, battery monitors) just as to how they function, it's entirely up to you if you see yourself using those rooted apps on a regular enough basis. The root managers available (e.g. SuperSU, magisk) are supported and work well, just ensure you're using the latest versions, and if you're on stock Nougat, to flash a custom kernel prior to rooting (since the stock kernel won't permit modifications, if I recall).
Overall, in my view, you're trading security and warranty (as mentioned by prajwal2001) for convenience/flexibility by rooting - the flexibility alone to flash what you wish is what interested me in rooting my device, if anyone else has any other comments, feel free to add.
echo92 said:
Provided you're still on the stock ROM, rooting shouldn't disable your anti-theft protection (which I recall is Factory Reset Protection). Even if you've enabled OEM unlocking in Developer Options, someone resetting your phone would still need your Google credentials to use the device. Of course, with an unlocked bootloader and custom recovery (as is generally required to root), someone could still flash a custom ROM and bypass those protections and, also, could in theory still access your data. (but only if they have physical access to your device)
As for DRM, I'm not sure but some apps have been/are now detecting the presence of root and will refuse to work (Snapchat, Pokemon Go, some banking apps come to mind) or for other devices, Android Pay and other security dependent features may not work. I recall magisk, a root manager, does have the ability to mask root from those apps, as well as pass SafetyNet, which is Google's security/anti-tamper detection. Your experience may vary. However, some apps require root access to function properly (e.g. kernel managers, battery monitors) just as to how they function, it's entirely up to you if you see yourself using those rooted apps on a regular enough basis. The root managers available (e.g. SuperSU, magisk) are supported and work well, just ensure you're using the latest versions, and if you're on stock Nougat, to flash a custom kernel prior to rooting (since the stock kernel won't permit modifications, if I recall).
Overall, in my view, you're trading security and warranty (as mentioned by prajwal2001) for convenience/flexibility by rooting - the flexibility alone to flash what you wish is what interested me in rooting my device, if anyone else has any other comments, feel free to add.
Click to expand...
Click to collapse
Hm I see.
That's a pretty big downside
I guess I will pass root for now, I was only wanting to do to use the ADB via USB OTG and boot disk creator.
Thanks everyone for all the information!
LionLorena said:
Hm I see.
That's a pretty big downside
I guess I will pass root for now, I was only wanting to do to use the ADB via USB OTG and boot disk creator.
Thanks everyone for all the information!
Click to expand...
Click to collapse
That's fair enough - there's nothing stopping you from rooting your device, then performing what you need, before unrooting your device. (Just curious, does what you want to do require root, or are there other non-root methods?)
However, this will still involve you voiding your warranty (via unlocking your bootloader), and may also involve re-flashing your stock firmware to remove the custom recovery (and relock your bootloader, if you wish, though this won't recover your warranty, sadly). Honestly though, it's your device, up to you what you wish to do
echo92 said:
That's fair enough - there's nothing stopping you from rooting your device, then performing what you need, before unrooting your device. (Just curious, does what you want to do require root, or are there other non-root methods?)
However, this will still involve you voiding your warranty (via unlocking your bootloader), and may also involve re-flashing your stock firmware to remove the custom recovery (and relock your bootloader, if you wish, though this won't recover your warranty, sadly). Honestly though, it's your device, up to you what you wish to do
Click to expand...
Click to collapse
Yeah the warranty is not on top of my mind right now, my concern are the other issues it may cause, such apps not working, and security issues.
Like, I had a Sony Xperia Play back some years and past a week I root it, and past 2 weeks it was on Cyanogenmod.
I had Bricked that device countless times and had somehow fixed, I had also replaced several internal components as well, but back then there were no DRM stuff and all, so the rooting part is not what I fear, is just this new wave of side effects regarding it.
LionLorena said:
Yeah the warranty is not on top of my mind right now, my concern are the other issues it may cause, such apps not working, and security issues.
Like, I had a Sony Xperia Play back some years and past a week I root it, and past 2 weeks it was on Cyanogenmod.
I had Bricked that device countless times and had somehow fixed, I had also replaced several internal components as well, but back then there were no DRM stuff and all, so the rooting part is not what I fear, is just this new wave of side effects regarding it.
Click to expand...
Click to collapse
There is no DRM to lose on Motorola devices. On Sony devices, what you said is applicable. As for apps that refuse to work with root access, you can simply switch to Magisk, and enabled hiding root access from all apps.
zeomal said:
There is no DRM to lose on Motorola devices. On Sony devices, what you said is applicable. As for apps that refuse to work with root access, you can simply switch to Magisk, and enabled hiding root access from all apps.
Click to expand...
Click to collapse
That's motivating.
And I've found a topic that says I don't even need to flash the custom recovery, I can simply hot boot it and do my stuff and keep the stock recovery.
LionLorena said:
That's motivating.
And I've found a topic that says I don't even need to flash the custom recovery, I can simply hot boot it and do my stuff and keep the stock recovery.
Click to expand...
Click to collapse
There's no real point of not changing the stock recovery, unless you are planning to stick with a rooted stock ROM. If you keep the stock recovery, you'll be able to enable OTA stock updates.
From a security standpoint, if your device is lost, it becomes much easier for an attacker to breach your system and much harder for you to protect it. However, according to most security principles, once your device is lost from you, it's no longer your device, anyway.
zeomal said:
There's no real point of not changing the stock recovery, unless you are planning to stick with a rooted stock ROM. If you keep the stock recovery, you'll be able to enable OTA stock updates.
From a security standpoint, if your device is lost, it becomes much easier for an attacker to breach your system and much harder for you to protect it. However, according to most security principles, once your device is lost from you, it's no longer your device, anyway.
Click to expand...
Click to collapse
The OTA updates are one of the reasons, yes.
And yes, from that point of view you are right.
I'm currently using some tracking solutions such as Cerberus, and disabling some features while the phone screen is locked, such as quick settings, and power off menu.
Also the extra layer of security imposed by Google version of iCloud, passes me some sense of safety.
The main thing that bothers me related to custom recovery is that the attacker can replace my software entirely.
While with stock I can have some time to recover the device using the tactics. Enabled.
And root could potentially aid me in that, I could add Cerberus to /system and etc.
You lose security. Every person with knowledge can access to your phone through TWRP, use the File Manager to erase files.key (this erases your gesture or PIN of lock screen) and can see all your info. If you unlock bootloader, every person can flash TWRP and do this steps.
alaindupus said:
You lose security. Every person with knowledge can access to your phone through TWRP, use the File Manager to erase files.key (this erases your gesture or PIN of lock screen) and can see all your info. If you unlock bootloader, every person can flash TWRP and do this steps.
Click to expand...
Click to collapse
thats why i'm thinking 3 times before doing it.
I wish you a good day. I know most people use this phone with custom rom. But since I am a clumsy person, I did not even dare to get root privileges. I cannot use any phone with root authority for a long time. Can I get root authority once and put the applications I want on the system and turn off the root authority?
TheSecondOne said:
I wish you a good day. I know most people use this phone with custom rom. But since I am a clumsy person, I did not even dare to get root privileges. I cannot use any phone with root authority for a long time. Can I get root authority once and put the applications I want on the system and turn off the root authority?
Click to expand...
Click to collapse
Clumsy? Not unless you constantly drop your device. The words you're looking for are "inexperienced" and "concerned".
To be honest, unless you have a compelling reason these days to embed apps in /system, it's best not to. In any case, it is possible to root long enough to embed apps in the system partition and then remove root. If the apps have features that require root however, those features will not function unless rooted. Also note that rooting will trip Samsung Knox. If you need Knox, you can't even attempt to root or else the Knox container is lost.
Strephon Alkhalikoi said:
Clumsy? Not unless you constantly drop your device. The words you're looking for are "inexperienced" and "concerned".
To be honest, unless you have a compelling reason these days to embed apps in /system, it's best not to. In any case, it is possible to root long enough to embed apps in the system partition and then remove root. If the apps have features that require root however, those features will not function unless rooted. Also note that rooting will trip Samsung Knox. If you need Knox, you can't even attempt to root or else the Knox container is lost.
Click to expand...
Click to collapse
Thank you very much for your answer.
What are the security vulnerabilities that I need to be aware of after getting root privilege? if i want to install custom rom what is the most stable rom? android version does not matter.
Security vulnerabilities? Ask Google, i.e. search. There should be plenty of discussion on the topic there.
What is the most stable ROM? I couldn't answer your question even if I wanted to, as I don't have an I9500; the hardware is different. Plus, what I believe is stable may not match your expectations. You'll have to try out the various ROMs until you find one you like.
Hi!
I want to hide su binary from my phone temporarily to trick apps into thinking that my phone is not rooted. I thought I could just rename su binary from TWRP but I could not find that. It's not inside /system/xbin/ or /system/bin/.
It's more complicated than that.
You may simply need to check your Play Integrity responses. See this thread.
For more details on how the Magisk patch works, see this post. Don't start arbitrarily messing with things, though.
Start with the basics, though. Which apps are failing? Make sure you are using the Play Integrity fix. Add those apps to DenyList just to be safe. If they are Samsung specific apps, be aware that Knox Guard is tripped by flashing modified/custom firmware, and cannot be reversed, even if the device is returned to stock.
Thanks!
V0latyle said:
It's more complicated than that.
You may simply need to check your Play Integrity responses. See this thread.
For more details on how the Magisk patch works, see this post. Don't start arbitrarily messing with things, though.
Start with the basics, though. Which apps are failing? Make sure you are using the Play Integrity fix. Add those apps to DenyList just to be safe. If they are Samsung specific apps, be aware that Knox Guard is tripped by flashing modified/custom firmware, and cannot be reversed, even if the device is returned to stock.
Click to expand...
Click to collapse
I rooted my phone with TWRP 3.1.0.0 and SuperSU 2.7 instead of Magisk. How much of it still applies and how much does not? I actually rooted it like 5 years ago already, now I just have app that does not like rooted phone.
sysctl said:
Thanks!
I rooted my phone with TWRP 3.1.0.0 and SuperSU 2.7 instead of Magisk. How much of it still applies and how much does not? I actually rooted it like 5 years ago already, now I just have app that does not like rooted phone.
Click to expand...
Click to collapse
I'd recommend switching to Magisk. Chainfire hasn't been in the scene for years.
V0latyle said:
I'd recommend switching to Magisk. Chainfire hasn't been in the scene for years.
Click to expand...
Click to collapse
Tnx. Will attempt this. How should I do that? Should I click "full unroot" from SuperSU? Will I also loose my data and apps or will it just unroot? Or should I do it from TWRP instead?
sysctl said:
Tnx. Will attempt this. How should I do that? Should I click "full unroot" from SuperSU? Will I also loose my data and apps or will it just unroot? Or should I do it from TWRP instead?
Click to expand...
Click to collapse
Unrooting won't wipe data. It doesn't matter how you do it.
V0latyle said:
Unrooting won't wipe data. It doesn't matter how you do it.
Click to expand...
Click to collapse
Tnx.
Also SuperSU asked if I want to disable Knox when it first started. Do you happen to know how to revert that? Would like to revert my phone to pre-SuperSU state in that regard as well. Just in case. Also will I be more vulnerable to viruses/malware when it stays disabled? Or should this knox question be separate topic already? Didn't want to spam this forum too much but it's also not connected to original question that much.
sysctl said:
Tnx.
Also SuperSU asked if I want to disable Knox when it first started. Do you happen to know how to revert that? Would like to revert my phone to pre-SuperSU state in that regard as well. Just in case. Also will I be more vulnerable to viruses/malware when it stays disabled? Or should this knox question be separate topic already? Didn't want to spam this forum too much but it's also not connected to original question that much.
Click to expand...
Click to collapse
I honestly don't know that much about Knox but having it disabled doesn't make your device any more vulnerable than being rooted. Be mindful of what you install, and don't grant root access to apps you don't trust.