Related
Hi Guys,
I'm basically knox free im on 4.2.2, can anyone give me
a: a brief guide to easiest way of rooting and installing a recovery i.e TW or CWM, hopefully one click solution?
b: If I go onto 4.4 kitkat will I have to have a knox bootloader even with a custom rom?, if so is 4.4 worth it?.
c: &
d:Mod Edit removed due to asking for best ROM ( not allowed on xda)
At the moment main thing I want to do is safely root and install recovery without triggering knox as I want the chance to install custom roms and not void my warranty as I can always use triangle away at a later date.
BTW have done a lot of reading but want to be 100% sure and would really like some experienced advice.
Many thanks
Mav
a) Use Saferoot -> HERE
b) TWRP -> All info HERE
c) and d) Try it by yourself. Read the rules of XDA too :highfive:
Thanks
but a few things, will rooting cause the knox to come on?, as im confused also how do i know if my bootloader is locked or not?, if it does make the bootloader custom can I change it back?.
Thanks
Mod Edit
You may continue with this thread , but please do not ask for best ROMS.
Saferoot , AFAIK , does not trip knox flag
malybru
Forum Moderator
maverick7777 said:
Thanks
but a few things, will rooting cause the knox to come on?, as im confused also how do i know if my bootloader is locked or not?, if it does make the bootloader custom can I change it back?.
Thanks
Click to expand...
Click to collapse
If you have an old bootloader you won't even have KNOX on it, lucky you.
If you have the new bootloader, it comes with KNOX.
You can check if you have a new or old bootloader by putting your phone in Download mode (Volume down + Home + Power buttons).
If the the top left corner is syas stuff like "KNOX warenty" etc. you have the new one.
Rooting using saferoot as mentioned earlier will not trigger KNOX anyways.
Installing a custom Recovery as well as installing a custom ROM will trigger KNOX (if you indeed have the new bootloader with KNOX offcourse).
I am so new, and so sorry, but this might be simple for others.... I am trying to undue what I did like 6 months ago. I know I downloaded something from the web from here (drawing a blank on the name, but it looked like the "anarchy A", it was just a quick easy way to ROOT. I don't think I did anything else, I know I never added a custom ROM. Can someone just tell me where to check to see what is modified. Then maybe I will be able to undue the rest.
hisandherturbo said:
I am so new, and so sorry, but this might be simple for others.... I am trying to undue what I did like 6 months ago. I know I downloaded something from the web from here (drawing a blank on the name, but it looked like the "anarchy A", it was just a quick easy way to ROOT. I don't think I did anything else, I know I never added a custom ROM. Can someone just tell me where to check to see what is modified. Then maybe I will be able to undue the rest.
Click to expand...
Click to collapse
Did you root your phone? Or did you install custom recovery? Or custom kernel? All of these may lead to the "Device has been modified" message.
You may also want to check for the Knox Warranty Status with Phone INFO ★Samsung★ app.
I did "root" it... it was a software root, I can not remember what it was called..... like I tried to explain, it looked like an "A".
thank you for the APP... KNOX is 0x0.... what else can I look at?
If you keep your phone, it really does not matter, but If you are going to sell it, then flash full image with Odin, it will bring everything back to stock, removing the root, all the red letter messages, etc. If you need help with using Odin, let us know.
TowelRoot was the software I used....
vndnguyen said:
Did you root your phone? Or did you install custom recovery? Or custom kernel? All of these may lead to the "Device has been modified" message.
You may also want to check for the Knox Warranty Status with Phone INFO ★Samsung★ app.
Click to expand...
Click to collapse
TowelRoot is the software I used... also, I am pretty sure I didn't install any recovery.... isn't there somewhere I can look to see what is/was done?
hisandherturbo said:
TowelRoot is the software I used... also, I am pretty sure I didn't install any recovery.... isn't there somewhere I can look to see what is/was done?
Click to expand...
Click to collapse
Hummh, you may need to post all screenshots from Phone INFO ★Samsung★ app for further investigation. Without the detailed info, no one can say anything for sure.
Here are some, is this enough?
hisandherturbo said:
Here are some, is this enough?
Click to expand...
Click to collapse
Not really enough, but I didn't see anything abnormal in your device info.
May be the reason is because your device has been rooted .
Try the following:
- Reflash the stock firmware. You will lost root.
- Or use Wanam Xposed > Security hacks > Fake system status.
Actually the very first screen you posted clearly says charger info requires root and it's blank so it doesn't seem like you have a root ATM and none of the 4 screens posted has Knox info, again its first page on the phone info (general info header) on the bottom, should say Knox warranty void 0 (good) or 1 for flag being tripped.
---------- Post added at 02:39 AM ---------- Previous post was at 02:24 AM ----------
Actually the very first screen you posted clearly says charger info requires root and it's blank so it doesn't seem like you have a root ATM and none of the 4 screens posted has Knox info, again its first page on the phone info (general info header) on the bottom, should say Knox warranty void 0 (good) or 1 for flag being tripped.
I really appreciate the help!
I "un-did" the towelroot, and KNOX does say 0X0.....
Here are the other screen shots....
If I remember correctly.... before when the towelroot was there, root info says I was rooted, and my device status was NOT custom.... so, I think it was something other then the root that did it.
My KNOX is still 0
I've tried to "factory data reset" from both the Android software and also the boot up screen (after I wiped the cache).
No matter what I do Device Status is still "custom"
There has to be something/somewhere I am missing.....
Here is a picture of my download page.... showing the custom status
For future searches.... FIXED..... I Downloaded Samsung KIES 3... and let it update the firmware... then I was official.
Hi guys!
Haven't been here for so long. I don't even know how to begin...
Well, here goes. As the title of this thread states, I need to unroot my device. It is a g900f snapdragon/international version. It's running 5.0 atm, vodafone cnx region.
I am writing this because I can't find any answer on the forum. I've seen many similar threads, but with no answers.
Can I unroot it without losing all my data? I don't want to just rewrite the entire firmware... Just a quick patch like the one used for rooting. Or something.
Please help me, or at least help me find an answer.
Settings of SuperSU have a full unroot option
*Detection* said:
Settings of SuperSU have a full unroot option
Click to expand...
Click to collapse
Thank you. I hope it will work with no issue and completely unroot my device. Don't care for the warranty, didn't have any to begin with.
EDIT:
Sorry but it's not working at all. That option is crap. The only thing it did was uninstall SuperSU.
Any other ideas please?
Anyone else got a good idea? Or any idea at all?
Lucian Andries said:
Thank you. I hope it will work with no issue and completely unroot my device. Don't care for the warranty, didn't have any to begin with.
EDIT:
Sorry but it's not working at all. That option is crap. The only thing it did was uninstall SuperSU.
Any other ideas please?
Click to expand...
Click to collapse
SuperSU is root, uninstalling it removes root, just try to use a root app now, it will fail
Factory reset your phone
*Detection* said:
SuperSU is root, uninstalling it removes root, just try to use a root app now, it will fail
Factory reset your phone
Click to expand...
Click to collapse
You couldn't be more wrong than this... Root and SuperSU are TWO different things! Only that SuperSU allows you to do some other stuff that I don't know and don't care.
I had to rewrite the entire Firmware to unroot. What a drag...
Oh well, thanks anyway.
Lucian Andries said:
You couldn't be more wrong than this... Root and SuperSU are TWO different things! Only that SuperSU allows you to do some other stuff that I don't know and don't care.
I had to rewrite the entire Firmware to unroot. What a drag...
Oh well, thanks anyway.
Click to expand...
Click to collapse
You have a lot to learn
Root = access to, and R/W permissions on system files
SuperSU grants you R/W access to the root system files
So SuperSU = Root
There are other root apps, but SuperSU is the main one
Unrooting via SuperSU settings = Full unroot
If you altered system files while you were rooted, then the device knows it has been modified regardless if SuperSU is installed - in that case, of course you need to re-write the firmware to get back to stock....
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
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.