Related
help! please. I am look to root my samsung galaxy S4 Running android 4.3 with the build MK6.
PLEASE HELP?
Thank you
Use this method : http://forum.xda-developers.com/showthread.php?t=2293800
DaveRazr said:
Use this method : http://forum.xda-developers.com/showthread.php?t=2293800
Click to expand...
Click to collapse
Anything that will actually allow the install of a custom recovery?
arrush said:
Anything that will actually allow the install of a custom recovery?
Click to expand...
Click to collapse
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
jeboo said:
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.
Click to expand...
Click to collapse
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M
azuziel said:
Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Oops, didn't even realize it was i337m...:silly:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
I deleted Knox completely from my phone as well as all the AT&T Bloatware. My phone is better without it.
azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery
azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8
Ramsey said:
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery
Click to expand...
Click to collapse
regarding knox. It is safe to allow supersu to disable knox, i avoided it thinking it may trip bc wasn't sure how it went about freezing it. I tested, had supersu disable knox, rebooted, good to go.
Did an identical handset today, and failed to root. Did some poking and found out that kies3 appears to interfere with kingo, so uninstall temporarily when running kingo if you have issues.
Once supersu disabkes knox, you can then update the binaries via normal method. Also if kingo gets to the part where it asks about using odin method, say no, or it'll trip knox.unplug, reattach and try again. Had to do it thrice for an i377m i did today.
Heres what i did:
1 - connect usb to phone, and enable developer mode, then be sure to allow the dev prompt to always accept usb from this machine, phone will prompt to allow
2 - click root. Shouldn't get to odin question, id it does, dont allow odin method, restart the process.
3 - on successful root, you will see supersu install, grant it root, and allow it to disable knox.
4 update supersu binariez via normal method (don't need to use cwm/twrp on i377m only), it will prompt, until knox disabled, u wont be able to update binaries
5 - install busybox installer
I havent installed supersu as system app yet, i imagine its also safe to do so.
6 - check knox in download mode and ensure 0x0 for *both* knox codes
7- installed xposed and some modulez, greenify in particular, and enabled, recheck knox, still 0x0
Both phones i did with this method, once kies was removed, rooted BEFORE i had to install any camera exploits, or any other crap from play. If you habe trouble, reload samsung drivers, try another cable (i had a failure using a blackberry usb cable, switched to packaged smasung usb, worked fine), anothet usb, and even another computer. Old pc's with usb 1.1 wont work (well), usb 2/3 does work just fine.
Avoid clockworkmod, twrp, safesteap etc (or any other custom recovery) if you want to keep your warranty. If you dont care, then twrp/cwm work just fine, they will blow the knox efuse tho and set you 0x1. I work in IT and happen to know knox will work with exchange 2015 upon release. It will also screw up new versions of active sync, as your system isn't able meet the security requirements (having knox intact and not blown) of the organizations' corporate knox policies. Look for a bes like sys admin tool that expands on the remote wipe /lockz/ camera images etc, in the coming months. Exchange 2015 is still a ways away, but since you cant undo a blown efuse with any software, understand implications of blowing knox fully, not just warranty. And if you use exchange email, or plan to, keep knox untripped is best advice.
Gage_Hero said:
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8
Click to expand...
Click to collapse
Yes. Ok, kingo is just an interface for all known exploits. The emei sniffing was actually being performed by vroot. Kingo was simply running existing vroot code. I talked to kingo support last week, who assured me that emei check was pulled during latest release, the vroot method is still present, however iz modified to remove those bad lines. When you run kingo, it opens a connection to kingo server to pull each exploit/patch as one method fails, pulls another, then another, as needed. This keeps package small, and allows for on the fly repo updatez on their end without having to re-release a package.
Kingo does not record emei at all any longer, it was vroot doing it, and kingo bc they simply ran vroot method without editing.
So you will see kingo go online to grab each exploit as required, in the new version, but no emei tracking any longer.
Besides the trojan that was used before in vroot, is picked up by avg free, so youd know if it were still doing it. I ran tcpview and tcpdump while flashing root to my device and didnt see any connections to china, any longer.
This can be verified on both odficial Facebook and Twitter account of kingo. Their intention is to at one point to charge a couple bucks for this app, having it exhibit malicious behaviour is bad for business. Youll notice vroot has no support or contact methods. Kingo does.
Sent from my SGH-I337M
Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..
Ki Hi
Ramsey said:
Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..
Click to expand...
Click to collapse
You cannot update ota when system is modified, there is an xposed module that changes modified to official tho. Not sure if it trips knox, likely. When updates come, unroot, apply, reroot. There are other guides that can be found here to update keepinng root with odin, you'll have to use the search provided.
Feezing with Titanium backup is fine. Supersu doesnt delete knox, it disables knox notifications. The whole point here is not tripping knox. That's why supersu asks if you want to disable knox, and not delete it, bc only disables, knox services still present. Feezing with tb is same result. Just supsrsu is free, tb is paid (for freezing anyway), though if youre on these forums, should be using tb anyway , titanium backup, greenify donation, and tasker are 3 must have root apps. Tasker is great. I use it to auto enable bluetooth and wifi based on gps location, or driving in the car. Lots of youtube vids on tasker if you areny familiat with it.
Sent from my SGH-I337M
There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758
If it helps any 4.3 MK6 users, I rooted using the download from this site and can confirm that it works:
http://forum.xda-developers.com/showthread.php?t=2565758
ravi_mytouch said:
There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
Yep it does. Ive used it on a few i377m already. Wasn't available when i did mine. Kingo is relatively safe, latest release is, cant speak for previous or future versions. Kingo is just an interface that uses all known root methods (including vroot, and this method). Just keeps trying dif method til one works. Had this been available, would have used for mine. But it wasn't so setup a segregated lab at work, to test kingo and reports of malware. I didnt see any at that time via tcp dump and tcpview, however that could change since they just rip off other root methods/code to reuse, kingo does i mean. That said if you rooted with kingo, no need to repeat. Root is root (well, full root is full root), and no daemons u dont recognize running.
Sent from my SGH-I337M
Situation:
I'm on Verizon with a Note 3 running 4.4.2. The methods shown for rooting almost always make the assumption that people want to run a custom ROM. I do not. The Safestrap developer bailed on the project, and nobody knows if it can be used in the future anyway.
Goals:
1. This is a business phone, not something that I want to continuously frog around with. I just want to be able to record telephone conversations when using my Bluetooth headset exactly the same as when I'm not, maybe a decent backup, and basically get my Verizon Note 3 and Android's functionality up to the level of where Windows Mobile has been since 2009. From what I understand, to do that may require the Xposed Framework.
2. Be able to give root back and have everything back like it was if necessary.
3. Be able to take OTA updates. I don't care if I need to uninstall some apps, give root back, accept the OTA update, take root back, and reinstall the apps. OTA updates don't happen often anyway.
4. Not lose the phone warranty in the process if possible. It seems one of the required apps for the root process is SuperSU. One of the options is to disable KNOX. Other than everyone doing it, and being recommended for vague reasons, why would I want to do that? Can you re-enable it later?
Thanks!
Towel root should do what you want. I currently don't know of anyone that used towel root or kingo that tripped Knox. Since you're on NC4 probably kingo isn't an option so it's towel root.
thegamerdarkseid said:
Towel root should do what you want. I currently don't know of anyone that used towel root or kingo that tripped Knox. Since you're on NC4 probably kingo isn't an option so it's towel root.
Click to expand...
Click to collapse
So Towel root and what? I'm guessing SuperSU without having it disable KNOX...or?
IT_Architect said:
So Towel root and what? I'm guessing SuperSU without having it disable KNOX...or?
Click to expand...
Click to collapse
You have to use SuperSu for root privileges.
IT_Architect said:
So Towel root and what? I'm guessing SuperSU without having it disable KNOX...or?
Click to expand...
Click to collapse
Towel Root is What you use to gain ROOT. Towel Root is basically a Program/Software that you will use to ROOT your Note 3. I used Kingo so I don't know much about Kingo but its probably not much different than Kingo, but based on what the other person said you need to use Towel Root. One thing you will want to do AFTER you go through the ROOT process is, Look in your app drawer & see if SuperSU is installed, if it is, you are Rooted, if it is Not, you are Not. I would also Download Root Checker from the Play Store to Verify you have ROOT.
SuperSU or Superuser is an app that gets installed in your phone when you Root it, that Manages what other apps you Grant/Deny Root permission. It does Not ROOT your phone. You do not need to download it from the Play Store. It is only in the Play Store to give you Updates, Its not meant to be as an initial download. Hope this Helps Bud. Happy Rooting! :laugh:
jasonsc1 said:
Towel Root is What you use to gain ROOTSuperSU or Superuser is an app gets installed in your phone when you Root it, that Manages what other apps you Grant/Deny Root permission...You do not need to download it from the Play Store. It is only in the Play Store to give you Updates
Click to expand...
Click to collapse
That makes sense.
So what I'm thinking is:
1. Root
2. Make sure SuperSU is there to know I'm rooted.
Later when there is an update:
- Refuse it until there is a way to get root without triggering KNOX.
- Uninstall root apps.
- From SuperSU give root back, which should bring it back to stock.
- Then allow the OTA and hopefully it will not trigger KNOX
I'm guessing it would be best not to install xposed framework because it makes system changes, which could cause things to go wrong during an update.
All that I need in the near term is to get my Bluetooth voice recording back.
Thanks!
IT_Architect said:
That makes sense.
So what I'm thinking is:
1. Root
2. Make sure SuperSU is there to know I'm rooted.
Later when there is an update:
- Refuse it until there is a way to get root without triggering KNOX.
- Uninstall root apps.
- From SuperSU give root back, which should bring it back to stock.
- Then allow the OTA and hopefully it will not trigger KNOX
I'm guessing it would be best not to install xposed framework because it makes system changes, which could cause things to go wrong during an update.
All that I need in the near term is to get my Bluetooth voice recording back.
Thanks!
Click to expand...
Click to collapse
That sounds like a Pretty good plan. I Rooted my Note 3 a while back. I was on JB & I'm still currently JB. ACTUALLY Its been a while since I've been on XDA. When I did Root my Note 3 there was NO WAY to ROOT Kit Kat 4.4.2. I did NOT know there was a way to ROOT it now. If there is Can you post a Link. Everything I've read says theirs No Way to Root Kit Kat but its been a while since I researched it. In my case After I Rooted my Note 3 I Froze SDM the app that receives Versions OTA updates. I kept getting one wanting me to Update to Kit Kat. I did not want to Lose my Root & then be on Kit Kat & not be able to Re-Root my Note 3. XDA has a version of Kit Kat made my a couple of the Developers, Beanstown106's & Hashcode's (the guy who made safestrap) that Already has Root. I'm going to Flash their Kit Kat version once I grow the Kahunas. I also Froze Knox so it could Not trip, although it did not Trip when I Rooted my Note 3 via Kingo but I'm on a different version than you.
Also You will Not need to Uninstall the Root apps. They will have No Effect on your phone. They will just not have Root permissions. I also don't see a need to Un Root- Re Root. I would just not accept the OTA Updates. I also have Xposed Framework with several modules & it & them have No negative effects on my Note 3. Anyways Hope this Helps somewhat, Post that Kit Kat Root Link if you can. Thanks
Here is a Link to what Im going to do.
http://forum.xda-developers.com/showthread.php?t=2740466
jasonsc1 said:
If there is Can you post a Link. Everything I've read says theirs No Way to Root Kit Kat
Click to expand...
Click to collapse
There are at least two:
1. Towelroot - Free
2. One Click Root - 2 packages to choose from: $29.95 package which includes root only and $39.95 which includes rooting + removal of bloatware + 30 days free tech support.
jasonsc1 said:
After I Rooted my Note 3 I Froze SDM the app that receives Versions OTA updates... I also Froze Knox so it could Not trip, although it did not Trip when I Rooted my Note 3
Click to expand...
Click to collapse
What did you use to freeze them with, Titanium?
jasonsc1 said:
Also You will Not need to Uninstall the Root apps. They will have No Effect on your phone. They will just not have Root permissions.
Click to expand...
Click to collapse
However they make changes in the system area, which I was concerned might foul up the OTA or trip KNOX.
jasonsc1 said:
I also don't see a need to Un Root- Re Root. I would just not accept the OTA Updates.
Click to expand...
Click to collapse
I am a little gun shy that if the OTA finds it rooted, it will trip KNOX and not do any more OTAs.
jasonsc1 said:
I also have Xposed Framework with several modules & it & them have No negative effects on my Note 3.
Click to expand...
Click to collapse
That is the only other product I looked at. It looks interesting, but I don't see that it brings anything to the table that I want. I'm not a customization guy, I just need to get basic functionality out of the phone such as call recording under Bluetooth and be able to backup my entire phone and settings.
Thanks!
IT_Architect said:
There are at least two:
1. Towelroot - Free
2. One Click Root - 2 packages to choose from: $29.95 package which includes root only and $39.95 which includes rooting + removal of bloatware + 30 days free tech support.
What did you use to freeze them with, Titanium?
However they make changes in the system area, which I was concerned might foul up the OTA or trip KNOX.
I am a little gun shy that if the OTA finds it rooted, it will trip KNOX and not do any more OTAs.
That is the only other product I looked at. It looks interesting, but I don't see that it brings anything to the table that I want. I'm not a customization guy, I just need to get basic functionality out of the phone such as call recording under Bluetooth and be able to backup my entire phone and settings.
Thanks!
Click to expand...
Click to collapse
Ok, I Rooted my Note 3 back in March, at that time there was No Way to Root Kit Kat. I did a lil Looking around & did find that you can Now Root Kit Kat.
No, I did not use Titanium, I do have it. I usually use Titanium just to backup my apps/data. I Froze the SDM app which is the app that Looks for/Receives OTA. So I do Not get any Updates. I don't see reason too. The only OTA that has came out since I bought my Note 3 is the Kit Kat OTA. If you Freeze that app you will have No Problems.
To my Knowledge the Only ROOT apps that can make changes to the System area is the Xposed apps/Modules. No other Root App that I know of makes any changes to the System area, unless you let it, & that can be reversed & the Apps STILL dont have to be Uninstalled. I can not think of ANY Reason to Uninstall the ROOT apps because there is Nothing about them that could cause Knox to Trip. I got NOTHING.
Yes Xposed opens a WHOLE NEW WORLD of Customization's. After having it, I could not live without it. I LOVE be able to Truly own my device. XPrivacy Guard gives me the Warm & Fuzzy that the 2 GPS tracking alarms I have on my Gixxer give me. I control what Permissions apps have, what information they can receive. I could not Live without XPosed or XPrivacy Guard,
jasonsc1 said:
Ok, I Rooted my Note 3 back in March, at that time there was No Way to Root Kit Kat. I did a lil Looking around & did find that you can Now Root Kit Kat.
Click to expand...
Click to collapse
I might add that 4.4.2 there is, but NOT 4.4.4 without tripping KNOX. I know the 4.4.2 settings interface is quite a bit different than JB, but whether that translates into anything useful, I don't know. I do know most docs are for JB. Thus, if there is anything in 4.4.2 worth having that you don't already have via root, now might be the time IF they are still rolling 4.4.2. You don't want to snag 4.4.4 by accident. I know that I haven't received an update request yet, and I am on 4.4.2, but the S5 gets 4.4.4. From the little reading I've done, there is little difference between 4.4.2 and 4.4.4 except KNOX has been updated, and a massive bug roll-up . (What those bugs might be, I have not researched.) Moving to KitKat, you also incur the problem of apps writing anywhere to the SD card. IMO, the biggest difference between JB and KitKat 4.4.2 and KitKat 4.4.4 is security. 4.4.4 on the Note 3 does NOT give you the new Touchwiz that the S5 gets with 4.4.4.
"At the beginning of June, Google released two new Android 4.4 KitKat updates. First was Android 4.4.3 KitKat, a massive bug fixer. A few days later, the company pushed out its Android 4.4.4 KitKat update. Both were, and still are, bug fixers aimed at squashing major Android 4.4.2 KitKat problems and they continue to land for key devices as we push toward the fall. I am miffed by the omission of the new TouchWiz on the 4.4.4 update on the Note 3"
There aren't any bugs that I noticed, and until they give you something other than putting you into tighter and tighter box, you might want to wait until they come out with something that benefits you.
jasonsc1 said:
No, I did not use Titanium, I do have it. I usually use Titanium just to backup my apps/data. I Froze the SDM app which is the app that Looks for/Receives OTA. So I do Not get any Updates. I don't see reason too. The only OTA that has came out since I bought my Note 3 is the Kit Kat OTA. If you Freeze that app you will have No Problems.
Click to expand...
Click to collapse
Back to my original question, what did you freeze it with, and BTW, is SDM the name of the program, or is that an abbreviation for something?
jasonsc1 said:
To my Knowledge the Only ROOT apps that can make changes to the System area is the Xposed apps/Modules. No other Root App that I know of makes any changes to the System area, unless you let it, & that can be reversed & the Apps STILL dont have to be Uninstalled. I can not think of ANY Reason to Uninstall the ROOT apps because there is Nothing about them that could cause Knox to Trip. I got NOTHING.
Click to expand...
Click to collapse
That is very helpful, and clarifies things for me.
jasonsc1 said:
Yes Xposed opens a WHOLE NEW WORLD of Customization's. After having it, I could not live without it. I LOVE be able to Truly own my device. XPrivacy Guard gives me the Warm & Fuzzy that the 2 GPS tracking alarms I have on my Gixxer give me. I control what Permissions apps have, what information they can receive. I could not Live without XPosed or XPrivacy Guard,
Click to expand...
Click to collapse
What is Gixxer? There is Privacy Guard, and XPrivacy. I assume you mean XPrivacy.
Thanks!
Lol, I meant to put what I used in my Last reply. I used Rom Toolbox Pro. It's also a Great App. I actually prefer it more than Titanium Backup. I believe because of the UI.
Glad to Help, what lil I can
Oh Gixxer is another name that Suzuki MC riders call their GSXR. I have a 08 GSXR 1000. A lot of riders call the GSXR, a Gixxer. Lol, or something like Gixxer 8k (08 GSXR 1000) would be mine. Lol. I sometimes assume everyone is a Rider. Lol. Sorry about that.
Yes I meant X PRIVACY Not LBE Privacy Guard. I've heard Horror stories about it. I have Never had a Problem with X PRIVACY yet.
Oh, One more thing, As far as Safe strap goes. You can definitely use it on your Note 3 right now. Yes the developer stop sending updates but trust me he's around. He's on here all the time, with New stuff. He helped develop the XDA Kit Kat Rom. His name is Hashcode. Again Safe strap is the ONLY way to go if you are going to flash Roms. That or TWERP, which is Harder (more complicated) to get on Note 3 & Not as Good. Safestrap is so Good bc you always can Boot into your Stock slot, while you still have a Custom slot too, if anything goes wrong, you could still Boot to the other.
Safestrap=The Best Custom Recovery, IMO
Later Bud. I work nightshift this weekend, so it's time for me to get some sleep to be back at it, at 6pm this evening.
This are my thoughts for everyone to critique. Let me know if there are any flies in the ointment before I proceed.
Prerequisites:
1. Go into Settings/Security, and make sure Unknown sources is checked, and Verify apps is unchecked.
Root for 4.4.2:
1. Install Towelroot
2. Install Check Root from Play Store and check for root
3. Download SuperSU zip file from the link on the developer's thread, http://forum.xda-developers.com/showthread.php?t=1538053. This will NOT come from the Play Store or Amazon. Then unzip it on your phone. Then go to the "common" directory, and run the APK. After that you may get a prompt to update the binaries.
4. When you Run SuperSU and it asks you if you want to disable KNOX, SAY NO!!!
5. Then install Titanium backup and Freeze KNOX, so you can Thaw it later.
____com.sec.enterprise.knox.attestation
____com.sec.knox.eventsmanager
____KLMS Agent
____KNOX
____Knox Notification Manager
____KNOX Store
Unroot back to factory for 4.4.2:
1. Go into Titanium Backup and Thaw KNOX.
2. Open ES File Explorer
____a. Go to Favorites and hit the / button
____b. Click on menu / Settings / and check Enable Root Explorer
____c. Also check Mount File System
____d. Click the back button
3. Then remove SU. (The developer is working on a way to do this automatically with his full unroot function, which will make this step unnecessary)
____a. Open ES File Manager
____b. To to system / bin and find the SU folder. Do a long press and delete
____c. Click the back button and go to system / xbin directory and find the SU file and delete if any present.
____d. Click the back button and go to system / app directory and find Superuser.apk and delete it if it on your phone.
4. Reboot. Root should be gone.
5. Do a factory reset, go to Settings / Personal / Backup and reset
Summary: This should put the phone back to stock for factory warranty, or to sell, or to simply start over.
I would suggest you drop the requirement to be able to take an OTA with a customized phone. It is almost always a better idea to (i) make your backups, investigate whether you can root the new release - and if so, then (ii) restore to full stock, (iii) take the OTA, (iv) re-root and (v) have your way with things.
The reasons are several, but at least one of them is that the OTA installers tend to do a top-level, recursive chmod()/chown() in /system/{x}bin, followed up with chmod()/chown() operations on individual files in those file subtrees as needed. This has the side effect of emasculating the "su" binary privilege escalation via setuid. I wouldn't be surprised if - as a result of SElinux enforcing mode - similar sorts of troubles start occurring due to similar resets/modding of SElinux extended attributes in the same file trees (e.g. if the OTA installer starts doing recursive chcon()s).
(The above is the raison de etre for apps like "OTA rootkeeper" and so forth - they attempt to work around this OTA installer side effect)
The second reason is that OTAs sometimes bundle a bootloader update. Samsung's strict rollback enforcement policies means that you probably will not be able to undo an OTA that you regret (for any reason) without triggering Knox.
I'm still on MJE. It made me happy when I bought the phone & is still making me happy, so the fact that there are new releases available doesn't bother me one whit. It is still a fantastic phablet (& I can exploit the WiFi tether bug without Wanam and all the related framework mods).
FWIW, I reviewed the .apk/.odex files that I "froze" (using "chmod 000", not TiBu); things have changed a little bit since MJE, but:
Knox Disable: ContainerAgent, ContainerEventsRelayManager, KLMSAgent, KNOXAgent, KNOXStore, KnoxAttestationAgent
OTA Nagware Disable: LocalFOTA, SDM
Asurian Spyware Disable: VMS.apk
Probably I should also disable SHealth too. These Samsung phones are bristling with surveillance crap, and there seems to be no end to it. Probably it's even worse now with KitKat. Who knew that the Orwellian future would be developed and financed by marketing companies ... and thereafter trivially co-opted by governments?
have fun with your phone.
I was pretty much settled on not rooting, and you come along and start making sense with solid business reasons. I also view Google, Samsung, Microsoft, and the government access for what it is, criminal activity. I simply want a phone that has the capabilities of my old Windows Mobile phone, and the same levels of privacy.
If they can spy on us, than a requirement for Google and all government personnel is to have 24 x 7 video and audio surveillance on them while they are at work, and every room in their house at home, and have it stream live on YouTube..
Just safestrap it already. Even on NC4 OTA, you can safestrap and install NC2 kernel and pick from many fantastic 4.4.2 ROMs. In the future, take the hypothetical 5.0 update and then you'll never have root, lol.
Anyway, you can return to stock NC4 if needed.
OR don't. Your loss.
xdadevnube said:
Just safestrap it already. Even on NC4 OTA, you can safestrap and install NC2 kernel and pick from many fantastic 4.4.2 ROMs.
Click to expand...
Click to collapse
- I don't see the necessity of a custom ROM. I simply want to be able to record calls with my Bluetooth active. This limitation serves as a reminder that a lot less effort goes into Android than we tend to believe. This is a legal requirement for many businesses. Fortunately for Android, most development and innovation is done out of necessity by phone makers such as Samsung, etc.
- I also want to be able to prevent the update to 4.4.4.
- To do the rooting and SafeStrap, I would want to be able to un-SafeStrap, un-SuperSU, re-enable KNOX, and un-root back to factory. I haven't seen that discussed anywhere. The only thing I see to be able to get back to factory is this, if it works: http://www.galaxynote3update.com/un...tock-official-firmware-4-4-2-or-4-4-3-kitkat/ and it does not address SafeStrap. There is more to this than warranty, it is getting the phone back to stock to fix problems. There are thousands of posts of people having problems after rooting and installing custom ROMs.
xdadevnube said:
In the future, take the hypothetical 5.0 update and then you'll never have root
Click to expand...
Click to collapse
That's what concerns me. I understand why Samsung is doing what they are doing. IOS has been pushing Android out of the enterprise and government by support efficiencies and legislated security requirements. Samsung is the only Android they are allowed to buy. Thus, I've noticed:
- The newer it is, the more secure it is. Security in the ?NIX world is simplistic and limited. The easiest fix is to block functionality, and add KNOX as the enforcer and recorder.
- The features you gain with each new release, are less valuable than the features you lose from increased operating system security. Android is rapidly becoming as confining as the iPhone.
- Control over privacy becomes less and less with each new release.
While the progression makes sense from an operating system security standpoint, but runs counter to privacy control and functionality, the reasons why people buy Android.
To completely unroot and restore to stock. Uninstall safestrap recovery. Uninstall towelroot. Uninstall busybox. Uninstall superuser. Factory reset phone. Then flash NC4 with odin for good measure. You really dont need to install safestrap at all unless you want to do backups.
IT_Architect said:
- I don't see the necessity of a custom ROM. I simply want to be able to record calls with my Bluetooth active. This limitation serves as a reminder that a lot less effort goes into Android than we tend to believe. This is a legal requirement for many businesses. Fortunately for Android, most development and innovation is done out of necessity by phone makers such as Samsung, etc.
- I also want to be able to prevent the update to 4.4.4.
- To do the rooting and SafeStrap, I would want to be able to un-SafeStrap, un-SuperSU, re-enable KNOX, and un-root back to factory. I haven't seen that discussed anywhere. The only thing I see to be able to get back to factory is this, if it works: http://www.galaxynote3update.com/un...tock-official-firmware-4-4-2-or-4-4-3-kitkat/ and it does not address SafeStrap. There is more to this than warranty, it is getting the phone back to stock to fix problems. There are thousands of posts of people having problems after rooting and installing custom ROMs.
That's what concerns me. I understand why Samsung is doing what they are doing. IOS has been pushing Android out of the enterprise and government by support efficiencies and legislated security requirements. Samsung is the only Android they are allowed to buy. Thus, I've noticed:
- The newer it is, the more secure it is. Security in the ?NIX world is simplistic and limited. The easiest fix is to block functionality, and add KNOX as the enforcer and recorder.
- The features you gain with each new release, are less valuable than the features you lose from increased operating system security. Android is rapidly becoming as confining as the iPhone.
- Control over privacy becomes less and less with each new release.
While the progression makes sense from an operating system security standpoint, but runs counter to privacy control and functionality, the reasons why people buy Android.
Click to expand...
Click to collapse
It takes 10 minutes to root. And 10 minutes to unroot. Including safe strap. Nothing will trip knox. Beans has the stock nc4 ota rooted deodexed and busy boxed. All is needed to do what you want to do. You will find Zero anything for your stock odex ota. So root safestrap flash the stock rom and add call recording via xposed.... There is no other info you need that isnt already posted in a sticky.
drewcam888 said:
To completely unroot and restore to stock. Uninstall safestrap recovery. Uninstall towelroot. Uninstall busybox. Uninstall superuser. Factory reset phone. Then flash NC4 with odin for good measure. You really don't need to install SafeStrap at all unless you want to do backups.
Click to expand...
Click to collapse
- When SuperSU is installed, it disables KNOX. If I uninstall SuperSU, will it re-enable KNOX, or if I flash back to Verizion KitKat 4.4.2 NC4 N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5.7z, from here, http://forum.xda-developers.com/showthread.php?t=2524572 will it restore the KNOX functionality?
- What happens to the ROMs in the ROM Slots when you uninstall SafeStrap recovery? Is the space released or...?
RomsWell said:
It takes 10 minutes to root. And 10 minutes to unroot. Including safe strap. Nothing will trip knox. Beans has the stock nc4 ota rooted deodexed and busy boxed. All is needed to do what you want to do. You will find Zero anything for your stock odex ota. So root safestrap flash the stock rom and add call recording via xposed.... There is no other info you need that isnt already posted in a sticky.
Click to expand...
Click to collapse
And it takes days of research to get to the 10 minutes to make sure what you read is accurate, and will work with your phone. I've read so many stickys, forum posts, blogs, and YouTube videos, that I've lost count. What I've learned is the custom ROM process is far from straightforward.
a. The SuperSU at the PlayStore is from an archeological dig. What I've read so far, I need at least 2.13 for things to work right, 2.16 is current, and 2.19 beta.
b. For the Note 3, just within KitKat 4.4.2 there is NC2, NC3, and NC4. From what I've gathered from a lot of reading and videos is that Safestrap-HLTEVZW-NC2-3.75-B04.apk is the ONLY one that works right with Verizon's NC4.
c. The whole idea of SafeStrap is to preserve the factory slot, and work from another slot. BeansTown106's rooted deodexed ROM, replaces the factory ROM.
d. BeansTown106's rooted deodexed ROM is not an NC4 kernel ROM. "The nc4 stock rom beans has posted isnt patched for the nc4 kernel. "
Thanks!
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 know is there any way to root without using pc. My bootloader is unlocked. Need to flash twrp.
mapbond said:
Hi
I want to know is there any way to root without using pc. My bootloader is unlocked. Need to flash twrp.
Click to expand...
Click to collapse
Don't think so, no. Not without root anyway.
Kingroot might work but it's a horrible app that isn't worth the trouble it creates. If Kingroot works on this phone then you can probably install a custom recovery via something like Flashify or the TWRP app. The problem with Kingroot is that it's basically malware. It installs adware on your phone and won't give root access to anything that interferes with its functioning like Adaway or an alternate root app. It also sends God only knows what data from your phone to China. You are honestly better off not being rooted at all than using Kingroot. There are instructions for rooting with Kingroot and then switching root to SU but unless the instructions are extremely up to date they will not work. Kingroot is updated with the specific purpose of preventing you from being able to do anything that reduces the power Kingroot has over your phone. It can be uninstalled but the app makes certain you completely lose root functions before that happens.
no support
jhs39 said:
Kingroot might work but it's a horrible app that isn't worth the trouble it creates. If Kingroot works on this phone then you can probably install a custom recovery via something like Flashify or the TWRP app. The problem with Kingroot is that it's basically malware. It installs adware on your phone and won't give root access to anything that interferes with its functioning like Adaway or an alternate root app. It also sends God only knows what data from your phone to China. You are honestly better off not being rooted at all than using Kingroot. There are instructions for rooting with Kingroot and then switching root to SU but unless the instructions are extremely up to date they will not work. Kingroot is updated with the specific purpose of preventing you from being able to do anything that reduces the power Kingroot has over your phone. It can be uninstalled but the app makes certain you completely lose root functions before that happens.
Click to expand...
Click to collapse
i tried kingroot there is no support from there end. so i uninstalled it.
You can't. You need to unlock the bootloader if this phone and this requires a PC
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.