Database Users

How to Root 4.3 with build MK6

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

[Q] root samsung galaxy note 3 with mobogenie

Hi friend sorry for my bad english. Today i discover a new method for root for samsung galaxy note 3. I don't try because i would lost my warrant and knox can grow. For make root it's important install mobogenie on pc and on your smartphone. When you enable usb debug mobogenie will install drivers on your pc. When you open mobogenie you can do many actions (install and delete app, backup, recover and root). someone try to root with mobogenie?

Numero17 said:
Hi friend sorry for my bad english. Today i discover a new method for root for samsung galaxy note 3. I don't try because i would lost my warrant and knox can grow. For make root it's important install mobogenie on pc and on your smartphone. When you enable usb debug mobogenie will install drivers on your pc. When you open mobogenie you can do many actions (install and delete app, backup, recover and root). someone try to root with mobogenie?
Click to expand...
Click to collapse
Knox grows yes.
Never heard of that. Why don't you just use cf autoroot. Knox safe methods are almost none existing on later firmwares.

kenny1991 said:
Knox grows yes.
Never heard of that. Why don't you just use cf autoroot. Knox safe methods are almost none existing on later firmwares.
Click to expand...
Click to collapse
because cf root grows my knox and safe root doesn't work on my note 3 mj7

Numero17 said:
because cf root grows my knox and safe root doesn't work on my note 3 mj7
Click to expand...
Click to collapse
to be frank...
MJ3 and above, you have to live with 0x1 if you want to root (at the moment).
those other rooting method flying around outthere is not proven safe though.
Like last time kingo was reported sending data to china server.
The safest root method currently is CF-autoroot for MJ3 and above. I said safe, in terms of no malware include inside. And it's proven safe to flash, with close to zero problem if you choose the correct file for your model. Only your KNOX will trip. but it's worth to sacrifice if you need root access.

Mmm..no i dont root for me its important 0x0
Sent from my SM-N9005 using xda app-developers app

[Q] Note 3 Manual Re-Root - no SU binary installed

I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.

Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app

hhai2pth said:
Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.

DrShenanigan said:
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.
Click to expand...
Click to collapse
You need to go on sammobile and download your stock firmware (you probably want to stay on 4.3 unless your particular phone and carrier have root capabilities on 4.4.2 which verizon and att do not yet have) then flash it through odin... just search your model # through sammobile and it will show all the available stock firmwares. That will at least get you running again then u will have to root it again from there
Posted from my beast of a VZW Note 3!!

I downloaded the firmware from that site and have tried to flash it.
I get an Error Meassage:
SW REV CHECK FAIL : [sb1]Fused 2 > Binary 1

DrShenanigan said:
I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.
Click to expand...
Click to collapse
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.

antique_sonic said:
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.
Click to expand...
Click to collapse
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.

DrShenanigan said:
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.
Click to expand...
Click to collapse
Try this, mate
http://forum.xda-developers.com/showthread.php?t=2466423

Kingroot on top of My KNOX, Working Great! !

I was concerned about Security with Kingroot so decided to try this. I'm on a RETAIL Verizon Note 4 running 4.4.4.
I did a factory restore then after setup, I DISABLED SDM, THEN I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot on the "Personal" side.
It worked. Root is, On Demand, temporary, And I think it is safer than using Kingroot without Knox.
I went into recovery to check but no Knox trip. I win!. I have two environments. One rooted the other as secure as you can get.
This is like having a dual boot on the fly. With this root you can at least use Adaway. You can get a lot done with it. This is the best root solution for the Retail Verizon Note 4. I am hoping to get developers interested.
O.K.,This is where I'm at. If someone could look at the pictures and tell me what I should add to the OP description, I'll do it. Look at the last two pictures, Knox would not let me take the screen shots because of security.
Check Out MOST ASKED QUESTIONS and Fixes in the next post.

MOST ASKED QUESTIONS
1. What phone is this for? Retail Verizon Note 4. This may also work on other un-rooted phones
2. What ROM are you on? 4.4.4 found HERE http://forum.xda-developers.com/not...w-to-roll-to-kk-4-4-4-lollipop-5-0-1-t3097054
3. How did you set up your google account? I set my personal side up with a "burner" email and the Knox side with the email I use every day.
4. How do you disable SDM? I used this: http://forum.xda-developers.com/and...---------------------------------------------
5.Where do you get My Knox" The Play Store.
6. Where did you get Kingroot? http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
7. What order do you install the software? Restore 4.4.4/Set up Google account./disable SDM/setup My Knox/Kingroot on personal side/=enjoy..... .......Note: this is not for use with SuperSUME.
8. Is root permanent? Some of the modification made when rooted are permanent but this Root is On Demand, temporary And I think this root method is safer than using Kingroot without Knox.
9. What about reboots. If a App ask to reboot first try not rebooting some changes will take effect without a reboot. If you have to reboot use a soft-reboot like SimpleReboot. You will almost always lose root with a hard reboot.
10. For an added security measure I am going to use the "Personal" root side as a playground and reboot before I open the My Knox Security side. Just to throw off any would be hackers.
Fixes
1. I found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select allow and then on the first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes
The same procedure may work for other apps. For some reason Adaway starts working without a reboot. You will need to clear and restart your browser.
Calm down, these things take time. First when you reboot allow your phone to settle down, a minute or two. Don't open anything. FIRST, Open and run kingroot. Once root is established run Adaway like I said. It probably will work the first time but if it fails just try again. It seem that once Kingroot gets to the point where it is not asked for permission, the reboots go away and it becomes more stable.
2. O.K., KNOX disables USB debugging, but I was able to uninstall Knox at the Playstore /Re-enable USB debugging/ then use gatesjunior's debolater app to remove SDM/ then install Knox /then root with Kingroot and it is working great again. I did try to put Super-Sume Pro on top but it would NOT work. I think Super-Sume Pro removes Knox. So I had to start over but I got it working great. If you need to use USB debugging for anything now we have to uninstall Knox. I'm still testing now.
-----------------------------------------------------------------------------------------
Check Back to post # 1 & 2 for updates.

Having some guys look into this.

doctor-cool said:
I was concerned about Kingroot and security so decided to try this.
I'm on a retail Verizon Note 4 running Gatesjunior's Safe 4.4.4.
I did a factory restore then after setup, I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot . It worked. Now sometime when I reboot I get the Unlock logo with the words Custom on the boot screen just like the DE Note 4 . I went into recovery to check but no Knox trip. I win the Root Price. I have two environments. One rooted the other as secure as you can get.
Click to expand...
Click to collapse
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app

warriorpluto said:
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app
Click to expand...
Click to collapse
did you test it?
Extreme Syndicate L

This is like having a dual boot on the fly
gatesjunior said:
Having some guys look into this.
Click to expand...
Click to collapse
I have two separate Google play store account on two separate partitions .
Can you get it to work with SuperSuMe Pro.
All this time we have been disabling Knox and actually My Knox is your friend.

I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...

Wetzel402 said:
I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...
Click to expand...
Click to collapse
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.

doctor-cool said:
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.
Click to expand...
Click to collapse
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.

gatesjunior said:
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.
Click to expand...
Click to collapse
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.

doctor-cool said:
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.
Click to expand...
Click to collapse
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L

elliwigy said:
did you test it?
Extreme Syndicate L
Click to expand...
Click to collapse
No. I havemt backed up my phone yet to try. Ill do it when I get home and try
Sent from my SM-N915V using XDA Free mobile app

not random
elliwigy said:
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L
Click to expand...
Click to collapse
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:

doctor-cool said:
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:
Click to expand...
Click to collapse
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L

elliwigy said:
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L
Click to expand...
Click to collapse
I meant when AdAway disables the commercials it is worth the trouble. But yes most of the time the root results are temporary . But once you get it set up your good to go and it is worth the trouble until your battery dies
-----------------------------------------------------
Edit: I may have found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select alow and on first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes

I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr

Hotdizzle said:
I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr
Click to expand...
Click to collapse
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.

doctor-cool said:
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.
Click to expand...
Click to collapse
I have the retail note 4

Hotdizzle said:
I have the retail note 4
Click to expand...
Click to collapse
Then...l don't know. I'm on safe 4.4.4, how about you?
-----------------------------------------------------
I just read your post 16 . Your on LP I'm on KK

LOL this works?!? how did nobody ever try this until now.. I'm speechless

Fail to set system rw

http://imgur.com/7mxqR4v
I want to set my system as rw but it fails everyway i do it. I tried Adb Shell but it doesnt work even though no error appears after entering in the code line. Ive tried the google play store app to enable rw for system, but it also does not work. After each of these steps i attempt to move an apk to system/app to check if its working. But it fails everytime. Also, when i attempt to use the rooting too in es explorer, it says my device is not compatible or needs root. Although titanium back up and battery calibrator, both which requires root. Work pefectly fine. I have supersu 2.7.1 on a Galaxy S5 g900t 5.1.1

Have you actually gone through the rooting process? everything I've just read indicates you haven't, and you don't actually tell us you have done so. Some of the functions in the apps you mention don't require access to root, so they may *appear* to work correctly.
I use SD Maid on my rooted phone, but I can also use it on my kids unrooted tablets....The same for root explorer....
The only difference is that some of the processes in these apps don't work on my kids tablets.....
Simply installing SuperSU from the playstore will not give you root access.
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Have you actually gone through the rooting process? everything I've just read indicates you haven't, and you don't actually tell us you have done so. Some of the functions in the apps you mention don't require access to root, so they may *appear* to work correctly.
I use SD Maid on my rooted phone, but I can also use it on my kids unrooted tablets....The same for root explorer....
The only difference is that some of the processes in these apps don't work on my kids tablets.....
Simply installing SuperSU from the playstore will not give you root access.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
"Although titanium back up and battery calibrator, both which requires root. Work perfectly fine"
SuperSu 2.7.1 is not compatible with Galaxy S5 5.1.1 Stock

Frankie_Xenon said:
"Although titanium back up and battery calibrator, both which requires root. Work perfectly fine"
SuperSu 2.7.1 is not compatible with Galaxy S5 5.1.1 Stock
Click to expand...
Click to collapse
It appears you've answered your own question then.....One of those cases where a little prior research would have prevented the need to start a thread here on XDA.....I guess you live and learn....
http://i.imgur.com/rVnFwJM.jpg