Related
Hey folks,
One of the forum moderators pointed me at this thread ( http://forum.xda-developers.com/showthread.php?t=2586586 ) as a suggestion to getting a ROM for my S4 that would alleviate the com.android.phone process crashes I had with other ROMS.
After flashing jfltespr_mk2_deodexed from micro-sd card through the Team Win recovery, my phone is now stuck at the Samsung Galaxy S4 logo screen with (Set Warranty Bit: Kernel) in the upper left.
Having looked through numerous threads on this issue, it seems there's a number of different remedies, from reflashing to simply powercycling.
There wasn't anything that was of much use in http://forum.xda-developers.com/showthread.php?t=2527706 either.
I have odin, and can boot into Team Win Recovery, or download mode. Suggestions/tips/ideas would be appreciated. Thanks.
Seems like you already have Knox tripped. And those warnings are because Knox detected modified files on your phone at boot up. I would suggest to odinto stock MK2
Sent from my SPH-L720 using Tapatalk
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
cruise350 said:
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
dearastronomer said:
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
Click to expand...
Click to collapse
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
From the advice in this thread I was able to get back to stock ROM w/ root (CF-Auto-Root). Thanks for the tips, and for being patient.
I'm going to do some reading on Knox, because I'm getting conflicting reports on the ability to remove it.
leaderbuilder said:
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
Click to expand...
Click to collapse
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
cruise350 said:
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
Click to expand...
Click to collapse
True but it lock the bootloader from what I’m hearing
Hence stopping the installation of custom roms
So first off, I am have a lot of questions that I might as well ask.
First, will rooting my Rogers Samsung Galaxy S4 I337m mess anything up with the carrier? Like, will i still be able to call and text, etc?
Secondly, can my carrier track that I have a rooted phone?
And this is the most important question, how do I actually root this phone? Most of the methods I have tried don't work because the security app "KNOX" keeps denying access for the root to happen. I have tried many ways to remove KNOX from the phone, but none of them work....So how do I actually root this phone without having KNOX shut me down?
Anyways, thanks for the help!
Pellisco said:
So first off, I am have a lot of questions that I might as well ask.
First, will rooting my Rogers Samsung Galaxy S4 I337m mess anything up with the carrier? Like, will i still be able to call and text, etc?
Secondly, can my carrier track that I have a rooted phone?
And this is the most important question, how do I actually root this phone? Most of the methods I have tried don't work because the security app "KNOX" keeps denying access for the root to happen. I have tried many ways to remove KNOX from the phone, but none of them work....So how do I actually root this phone without having KNOX shut me down?
Anyways, thanks for the help!
Click to expand...
Click to collapse
So ...based on the question, and the fact that this is your first post, it appears you have a fair bit of reading to get through before doing it but yes the phone does everything rooted as it did before, you just have access to the whole file system (which means you will have the ability to break things that were "roped off for your protection" before rooting)
No your carrier doesn't know or care you are rooted... unless you do break something and bring it in asking them to fix it, then they will tell you you broke it yourself tough luck. (unless of course you reverse everything back to stock first)
FIRST read all (really... read all of it) of the 2nd and 3rd thread in "AT&T Samsung Galaxy S 4 General"
[GUIDE][INFO] The beginner's info thread (aka. the noob helper) and [HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2
Then you can root. The "CF Auto-root" method works perfectly on all the Canadian carrier versions (they only differ in carrier bloat.), then install a custom recovery, then install a good backup utility, I suggest TiBu (which will also allow you to remove Knox).
Good luck.
robinsonj said:
So ...based on the question, and the fact that this is your first post, it appears you have a fair bit of reading to get through before doing it but yes the phone does everything rooted as it did before, you just have access to the whole file system (which means you will have the ability to break things that were "roped off for your protection" before rooting)
No your carrier doesn't know or care you are rooted... unless you do break something and bring it in asking them to fix it, then they will tell you you broke it yourself tough luck. (unless of course you reverse everything back to stock first)
FIRST read all (really... read all of it) of the 2nd and 3rd thread in "AT&T Samsung Galaxy S 4 General"
[GUIDE][INFO] The beginner's info thread (aka. the noob helper) and [HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2
Then you can root. The "CF Auto-root" method works perfectly on all the Canadian carrier versions (they only differ in carrier bloat.), then install a custom recovery, then install a good backup utility, I suggest TiBu (which will also allow you to remove Knox).
Good luck.
Click to expand...
Click to collapse
Yes, I know this is my first post, and you may think I don't know much about rooting, but I have had some experience in the past. I did root my Samsung Galaxy Tab 2, first time I soft bricked it, then actually got to root and stuff to work, so I have some knowledge on what I am doing.
Those two threads that you have linked me, I have looked over and learn't some stuff from them. I have also downloaded CF Auto-Root for the I337m version. I know how to work it, through using Odin and download mode, exact same way I rooted my tablet.
I just have one more question though, rooting it with odin through download mode, that bypasses KNOX and allows the root to work? Cause if I tried rooting with any program like motochopper, KNOX would block it.
Pellisco said:
Yes, I know this is my first post, and you may think I don't know much about rooting, but I have had some experience in the past. I did root my Samsung Galaxy Tab 2, first time I soft bricked it, then actually got to root and stuff to work, so I have some knowledge on what I am doing.
Those two threads that you have linked me, I have looked over and learn't some stuff from them. I have also downloaded CF Auto-Root for the I337m version. I know how to work it, through using Odin and download mode, exact same way I rooted my tablet.
I just have one more question though, rooting it with odin through download mode, that bypasses KNOX and allows the root to work? Cause if I tried rooting with any program like motochopper, KNOX would block it.
Click to expand...
Click to collapse
OK just didn't want you to brick your phone by not really understanding Odin... It is writing to the system partition and has been known to make a mess if the wrong files are dropped in the bootloader or if a download is interrupted.
I'm afraid all I really know about KNOX is from reading about the problems with the 1.x implementation and that the latest was supposed to be the solution for BYOD in a secure enterprise...
I Odined CF Auto-Root and had no issues whatsoever... I'm pretty sure KNOX can only run inside the OS, so in download mode you're outside of where it can interfere with anything. After the root and a custom recovery the first thing I did was freeze all KNOX and "enterprise" files just in case.
robinsonj said:
OK just didn't want you to brick your phone by not really understanding Odin... It is writing to the system partition and has been known to make a mess if the wrong files are dropped in the bootloader or if a download is interrupted.
I'm afraid all I really know about KNOX is from reading about the problems with the 1.x implementation and that the latest was supposed to be the solution for BYOD in a secure enterprise...
I Odined CF Auto-Root and had no issues whatsoever... I'm pretty sure KNOX can only run inside the OS, so in download mode you're outside of where it can interfere with anything. After the root and a custom recovery the first thing I did was freeze all KNOX and "enterprise" files just in case.
Click to expand...
Click to collapse
Okay. Hopefully KNOX doesn't interfere with anything. I also noticed in download mode:
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-CONFIG-LSB: 0x20
Write Protection: Enable
eMMC Burst Mode: Enabled
So which ones trip when I root it? I know that the 'Current Binary' will trip if I install a custom rom, but, what about the KNOX stuff? I know that the Warranty Void will then turn to '0x1' and I think the kernel lock will change too, but not 100% sure.
Also, what about Write Protection? Will that have anything to do with writing new software onto the phone and will block it?
Pellisco said:
Okay. Hopefully KNOX doesn't interfere with anything. I also noticed in download mode:
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-CONFIG-LSB: 0x20
Write Protection: Enable
eMMC Burst Mode: Enabled
So which ones trip when I root it? I know that the 'Current Binary' will trip if I install a custom rom, but, what about the KNOX stuff? I know that the Warranty Void will then turn to '0x1' and I think the kernel lock will change too, but not 100% sure.
Also, what about Write Protection? Will that have anything to do with writing new software onto the phone and will block it?
Click to expand...
Click to collapse
You may want to look at the top of this page.... http://autoroot.chainfire.eu/ states CF-auto root will trip Knox warranty... if your rooting, you should install a custom recovery and do a nand backup before you do anything else root without backup can have some ill side effects if you mess around with your files/apps... ie delete something that is critical.... of coruse custom recovery trips something else too I forget what it was but I am sure it's been discussed a couple times throughout the forum.... all I can say is read lots.... most times someone can get you out of a jam but I prefer not to go there in the first place.. so I read before I do.... most here will tell you it's the best way.... pay close attention to those who have messed up... good indication of what not to do....
One other thing I noticed was that there are locked boot loaders on certain devices.
So I have been wondering, does the Rogers Samsung Galaxy S4 come with a locked boot loader? Cause if it does, and I try and root my phone, there is a high chance that it will brick the device.
Apparently this does not prevent OTA's. Like most, I didn't like Magazine UX or Knox so I flashed. Tripped the Knox Warranty Void =1. So I went to Sammobile and downloaded the July 2014 release and flashed it. Lo and behold, when I hit software updates it started downloading. Will let you know of my progress.
pworcester said:
Apparently this does not prevent OTA's. Like most, I didn't like Magazine UX or Knox so I flashed. Tripped the Knox Warranty Void =1. So I went to Sammobile and downloaded the July 2014 release and flashed it. Lo and behold, when I hit software updates it started downloading. Will let you know of my progress.
Click to expand...
Click to collapse
OK. It took me from ANF4 to ANI1!
pworcester said:
OK. It took me from ANF$ to ANI1!
Click to expand...
Click to collapse
and from ANI1 to ANK1! Sweet!!
KNOX is mainly meant to ensure an untampered device for corporate security purposes; not to prevent OTAs.
yes it just causes to end your guarantee in case you take it to samsung service
benveq said:
yes it just causes to end your guarantee in case you take it to samsung service
Click to expand...
Click to collapse
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
redpoint73 said:
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
Click to expand...
Click to collapse
I came from a tab2 10.1 that I could reset completely. Wasn't sure if knox would keep me from getting updates.
pworcester said:
I came from a tab2 10.1 that I could reset completely. Wasn't sure if knox would keep me from getting updates.
Click to expand...
Click to collapse
Its good to get more confirmation, in any case. There seems to be a good amount of mixed info about KNOX. So thanks for posting it.
redpoint73 said:
KNOX is mainly meant to ensure an untampered device for corporate security purposes; not to prevent OTAs.
Click to expand...
Click to collapse
Regardless of what it's meant for, if you trip Knox and then try to do an OTA you will get a message telling you you can't do that. Now, apparently manually flashing something removes that restriction, which is great, but the fact remains.
redpoint73 said:
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
Click to expand...
Click to collapse
I used Odin to flash the July 2014 relase. Prior to that I had the current relase falshed through Odin When I would check for updates it would tell me my device was modified. Going back to July and letting it OTA to current, now when I check for updates it says the latest software is installed.
thebobmannh said:
Regardless of what it's meant for, if you trip Knox and then try to do an OTA you will get a message telling you you can't do that. Now, apparently manually flashing something removes that restriction, which is great, but the fact remains.
Click to expand...
Click to collapse
You're right, I wasn't completely clear on the details of the situation (once modded, I don't believe in OTAs) so thanks for clarifying.
---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------
pworcester said:
I used Odin to flash the July 2014 relase. Prior to that I had the current relase falshed through Odin When I would check for updates it would tell me my device was modified. Going back to July and letting it OTA to current, now when I check for updates it says the latest software is installed.
Click to expand...
Click to collapse
Again, thanks for the clarification.
It's not the Knox status that matters for OTAs. It is the flag that identifies your setup as Custom that prevents OTAs. That is a result of having a custom recovery. For example, if I root my device, tripping Knox, and later decide to Odin back to stock without custom recovery, I can (and have) receive OTAs because my status is returned to Official. I can then re-root, flash custom recovery (thus resetting status to Custom), and no longer receive OTAs.
Sent telepathically
RiverCity.45 said:
It's not the Knox status that matters for OTAs. It is the flag that identifies your setup as Custom that prevents OTAs. That is a result of having a custom recovery. For example, if I root my device, tripping Knox, and later decide to Odin back to stock without custom recovery, I can (and have) receive OTAs because my status is returned to Official. I can then re-root, flash custom recovery (thus resetting status to Custom), and no longer receive OTAs.
Click to expand...
Click to collapse
Weird, all I did was root my T900 (via Odin), without installing a custom recovery, and was subsequently unable to take an OTA. I didn't really mess with it after that -- I switched to CM shortly after -- but that was my very limited experience. Could have been a fluke.
If you used CF Auto Root, part of the automated process mucks with recovery to achieve root (thereby rendering your status as Custom). One can Odin flash back to complete stock (which unroots and resets recovery to Official), but Knox remains tripped.
RiverCity.45 said:
If you used CF Auto Root, part of the automated process mucks with recovery to achieve root (thereby rendering your status as Custom). One can Odin flash back to complete stock (which unroots and resets recovery to Official), but Knox remains tripped.
Click to expand...
Click to collapse
Great info, thanks! THis is my first Samsung / Knox device so still learning the basics.
Would it be safe to dirty flash (flash without wiping /data, only /cache and dalvik) latest stock ROM over older stock ROMs (modified with custom recovery)?
Sorry to necro-ish-post. Just got one of these on sale and I'm getting used to the "Samsung Way" after a Nexus tablet.
Suppose I've rooted my ROM without tripping Knox. I'd imagine if another OTA comes along it might fail due to modifications to the ROM. Can I use Odin to reflash the system part of the ROM back to stock without tripping Knox, so that the OTA will subsequently work?
cmstlist said:
Sorry to necro-ish-post. Just got one of these on sale and I'm getting used to the "Samsung Way" after a Nexus tablet.
Suppose I've rooted my ROM without tripping Knox. I'd imagine if another OTA comes along it might fail due to modifications to the ROM. Can I use Odin to reflash the system part of the ROM back to stock without tripping Knox, so that the OTA will subsequently work?
Click to expand...
Click to collapse
Yep. You can get a stock ROM and flash it with ODIN. Knox won't be tripped and you will loose root. Other thing you can do is stay rooted, and flash with ODIN the new ROMs as soon as they are available. Instead of re-flashing the same ROM you are on right now, so you can get an OTA, why not wait until a new ROM is released and flash that new ROM then? You can reroot then, if you want (towelroot). Of course you have to keep an eye on the forum so you know when a new ROM is available. Or check samfirmware from time to time :good:
Good to know. I don't know if Lollipop is ever on the agenda for Tab Pro, but if so I'd imagine there won't be a way to get it Towelrooted.
HELP!!! U.S. version of sm-T520
I have the Sm-T520nzwaxar. I needed to flash a firmware to revert it to stock. I was aware of the region based firmwares, but I still flashed one. The process failed near the end. Odin said "Failed" and my tablet remained in download mode, didn't boot. Now, I have a tablet that is pretty damn bricked. It will only go to a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" and Download Mode.
I have determined that there is no such firmware for T520nzwaxar, despite being the U.S. model. The only thing I can hope for now is that such a file does exist or another firmware from another country would work.
PLEASE any help that can be given to a frimware that would work with this would be HUGELY appreciated.
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
As title said, what features im going to lose besides the OTA and knox?
Sent from my SM-G950F using Tapatalk
iiD4x said:
As title said, what features im going to lose besides the OTA and knox?
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Caution: This phone has dm-verity enabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
gunner007dc said:
Samsung Pay if you use it (any Knox dependant apps), Android Pay can work with Magisk but it's a cat-mouse game of passing SafetyNet. Some financial apps will refuse to work on rooted phones (some can be avoided with Magisk Hide) but if they mean anything to you it's best to check the apps to see if anyone reports problems with a rooted device. I know Netflix and other content providers sometimes block rooted phones.
Click to expand...
Click to collapse
:good: Thanks.
Fusseldieb said:
Caution: This phone has dm-verity enabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
Click to expand...
Click to collapse
Yeah, i did backup before rooting, Thanks.
Warrenty
Pokemon go
Warranty (tripping knox), Android & Samsung Pay and over-the-air updates.
Generally you have to unroot for the OTA updates to work, but sometimes that is not enough, you have to factory restore the device as well. There is the app "FlashFire" which help you keep root as you upgrade OTA, but I find this won't work on all phones.
These three reasons are why I simply do not root anymore. Now if you have a Google Pixel or OnePlus, they generally don't take away your warranty even if you unlock bootloader or root. Some manufacturer like HTC and Moto, generally you have to request a bootloader unlocking code in order to install custom recovery to root, and in requesting the unlock code you forfeit your warranty.
Is there a way to patch s Health to get it working?
Fusseldieb said:
Caution: This phone has dm-verityenabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
Click to expand...
Click to collapse
The only thing you said that is correct is that the phones have dm-verity. But given that is implemented by the boot. Img, you can either remove it with 1, an engineering boot, because you can disable dm verity with selinux in permissive. 2, flash a rom that doesn't contain the dmverity flag, seeing as the boot only checks dm verity against the partitions that contain the flag(which isn't many. And is none on a full custom rom) or 3, pull apart the boot image and remove the dmverity file.
And general root has no bearing on dmverity anyways unless an app attempts to obtain root during boot up.
But anyways. It really depends on the root method as to what you lose. If we can achieve root with a locked bootloader, you will still be able to use Samsung pay and other Knox apps with standard root hider
Hi all is there a saver root yet every one I see there was problems
cheers