Database Users

[GUIDE] A tutorial to install the xposed framework on rooted HTC Desire 816 phones

I know many of us are quite frustrated with the xposed module installation on the rooted htc phones. The main culprit for it is the busy box application. This application contains all the terminal commands necessary to break the security of the stock mobile system. It is not a virus application though but install those commands and provide you the functionality to execute the framework changes needed for some important apks like Titanium backup, adfree, xposed module, etc etc..
On HTC devices with Kitkat 4.4.2 specifically, due to the (S-ON) security feature, the busybox app will not get installed easily as apk even on the rooted custom roms. It must be installed separately along with the cwm recovery after updating the supersu. That is why many busybox installers lying on the play store are not working/effective anymore.
It could also be due to the busybox files getting installed either in the incorrect path/location (due to change in the internal sd card path in 4.4.2 kitkat versions) or the S-ON feature must be stopping from installing at the right place. Whatever may be the reasons for not working, there is fix for this issue and the steps are outlined below.
DISCLAIMER: Please don't blame me if you corrupt your device by following the below process. I am pretty sure that the below process works flawlessly, but the reason for failing or corrupting your device could be a combination of several existing issues in your phone. So I take no responsibility for your bricked devices.
Now the coolest part:
1. Your HTC desire 816 must be rooted and should have working clockworkmod recovery. Otherwise this trick doesnt work at all.
2. First lets fix the busy box app - Go to playstore and download Busybox on Rails free apk from here: https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
3. Open the Busybox on Rails app, select the Operation option as "Cleanup & Install" and method as Recovery (and not "normal"). This will reboot your device into recovery and install the busy box application.
4. Reboot the system. Vola Busy box should have installed correctly now. To confirm that reopen the same Busybox on Rails app and see if the System Status shows up as OK. If it does, your busybox is successfully installed. If not by any chance, try repeating the steps 2, 3 and 4 again. It should work.
Some people install the terminal apk from play store and execute some su commands to verify if the busybox is installed properly. But that is for people having much knowledge on software scripting side of things.
5. Now lets install the xposed module - search for the xposed module apk from here http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401 and install it. Remember to download the xposed disabler apk zip as well, just in case if your mobile gets corrupted, you can flash that to bring back your original settings.
6. Install the xposed module and open Framework within the apk
7. Before hitting the Install/update option, change the Installation mode from defaulted Classical (Write to /system directly) mode to the middle one Recovery (flash zip automatically) mode. Dont change anything else in the settings.
8. Now hit Install/update
9. Phone will reboot the system into recovery mode, install the xposed module.
10. Reboot the phone and Volaaaaaaaa!!!!!!!!!! Enjoy the xposed framework in your mobile, which opens the endless opportunities to tweak your mobile.
Hit the thanks button if I have helped you in any way.
This method might works on all HTC models with S-ON security feature and 4.4.2 android Kitkat version, but have not tested it myself though. However, my friend did say it worked on HTC one latest model. Dont blame me if it doesn't by any chance.

Xposed
vbrsekhar said:
I know many of us are quite frustrated with the xposed module installation on the rooted htc phones. The main culprit for it is the busy box application. This application contains all the terminal commands necessary to break the security of the stock mobile system. It is not a virus application though but install those commands and provide you the functionality to execute the framework changes needed for some important apks like Titanium backup, adfree, xposed module, etc etc..
On HTC devices with Kitkat 4.4.2 specifically, due to the (S-ON) security feature, the busybox app will not get installed easily as apk even on the rooted custom roms. It must be installed separately along with the cwm recovery after updating the supersu. That is why many busybox installers lying on the play store are not working/effective anymore, mainly because of the files getting installed either in the incorrect path/location (due to change in the internal sd card path in 4.4.2 kitkat versions) or the S-ON feature must be stopping from installing at the right place. Whatever may be the reasons for not working, there is fix for this issue and the steps are outlined below.
DISCLAIMER: Please don't blame me if you corrupt your device by following the below process. I am pretty sure that the below process works flawlessly, but the reason for failing or corrupting your device could be a combination of several existing issues in your phone. So I take no responsibility for your bricked devices.
Now the coolest part:
1. Your HTC desire 816 must be rooted and should have working clockworkmod recovery. Otherwise this trick doesnt work at all.
2. First lets fix the busy box app - Go to playstore and download Busybox on Rails free apk from here: https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
3. Open the Busybox on Rails app, select the Operation option as "Cleanup & Install" and method as Recovery (and not "normal"). This will reboot your device into recovery and install the busy box application.
4. Reboot the system. Vola Busy box should have installed correctly now. To confirm that reopen the same Busybox on Rails app and see if the System Status shows up as OK. If it does, your busybox is successfully installed. If not by any chance, try repeating the steps 2, 3 and 4 again. It should work.
Some people install the terminal apk from play store and execute some su commands to verify if the busybox is installed properly. But that is for people having much knowledge on software scripting side of things.
5. Now lets install the xposed module - search for the xposed module apk from here http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401 and install it. Remember to download the xposed disabler apk zip as well, just in case if your mobile gets corrupted, you can flash that to bring back your original settings.
6. Install the xposed module and open Framework within the apk
7. Before hitting the Install/update option, change the Installation mode from defaulted Classical (Write to /system directly) mode to the middle one Recovery (flash zip automatically) mode. Dont change anything else in the settings.
8. Now hit Install/update
9. Phone will reboot the system into recovery mode, install the xposed module.
10. Reboot the phone and Volaaaaaaaa!!!!!!!!!! Enjoy the xposed framework in your mobile, which opens the endless opportunities to tweak your mobile.
Hit the thanks button if I have helped you in any way.
This method might works on all HTC models with S-ON security feature and 4.4.2 android Kitkat version, but have not tested it myself though. However, my friend did say it worked on HTC one latest model. Dont blame me if it doesn't by any chance.
Click to expand...
Click to collapse
Sir,
Please advice what is the advantages for installing this?
is this will solve link2sd problem?

heppojo said:
Sir,
Please advice what is the advantages for installing this?
is this will solve link2sd problem?
Click to expand...
Click to collapse
The only advantage of installing busybox and xposed installer is to open up endless opportunities of tweaking your mobile to look and behave the way you want (in most cases). Also some finest apps like titanium backup, and others etc use these busy box services too.
The link2sd app may or may not work and in my view it is totally unrelated. I havent tried that much, so cannot comment much on that I am afraid.

heppojo said:
Sir,
Please advice what is the advantages for installing this?
is this will solve link2sd problem?
Click to expand...
Click to collapse
I have tried and it worked.
vbrsekhar said:
The only advantage of installing busybox and xposed installer is to open up endless opportunities of tweaking your mobile to look and behave the way you want (in most cases). Also some finest apps like titanium backup, and others etc use these busy box services too.
The link2sd app may or may not work and in my view it is totally unrelated. I havent tried that much, so cannot comment much on that I am afraid.
Click to expand...
Click to collapse
Lnk2Sd is somehow useful for users with partition, very useful for low internal memory devices. Though a high quality SD card is necessary. Thanks to this tutorial. CONFIRMED WORKING for Xposed Framework.

Huge thanks for this. Got xposed working on my phone - running 4.4.2 with S-on / boot loader unlocked from HTC
Sent from my HTC_D816x using XDA Free mobile app

This is a off topic Que , but I require urgent help ..
I haven't rooted my device nor did I do any trick with it , but now my device is showing TAMPERED on hboot menu .. is this means my warranty is void .. how that can happen with even connecting my phone to pc.. can I suggest any way of removing it or unlocking my bootloader other than HTC Dev site, or any way to s off it . .. warranty issues
Sent from my HTC Desire 816 dual sim using XDA Free mobile app

sonnu said:
This is a off topic Que , but I require urgent help ..
I haven't rooted my device nor did I do any trick with it , but now my device is showing TAMPERED on hboot menu .. is this means my warranty is void .. how that can happen with even connecting my phone to pc.. can I suggest any way of removing it or unlocking my bootloader other than HTC Dev site, or any way to s off it . .. warranty issues
Sent from my HTC Desire 816 dual sim using XDA Free mobile app
Click to expand...
Click to collapse
It is very unusual to see that happen without you connecting to pc and trying to unlock the bootloader from HTC dev site. This was first time hearing that this can happen without trying to root or alter the mobiles internal system.
Anyways, to unlock bootloader, you have to go via HTC site and there is no other alternative as of now. The moment you unlock your bootloader, you will see that TAMPERED message in the hboot. If you are also receiving the red text while booting HTC that "This device has been tampered/altered and is development purposes only.... blah blah blah message", then definitely it has been unlocked bootloader.
May be your phone is a unlocked version, which requires the vendor to unlock the bootloader first and then have to unlock the service carrier. In this case you would get that message for sure, without you having to do anything. This way you will not have manufacture warranty, but will have the vendor warranty. Check with the place where you bought that piece.
Btw, if you find out that it has already been unlocked, then you might as well can root it as it makes your piece worth buying. All the best.

Hi, already follow the guides and steps given and now how can I know xposed working on my phone? What should I do next?

You are a genius vbrsekhar :laugh: Installation has been successfully Thank you dear :highfive:

Syria_BoY said:
You are a genius vbrsekhar :laugh: Installation has been successfully Thank you dear :highfive:
Click to expand...
Click to collapse
Cheers buddy, glad to know that it worked. Thank you for acknowledging!

Im a little confused seeing this post. Is this an old probelm? I get xpoaed to install just fine. Some of the status bar mods are wonky . Am I missing something ? Lol.

carnivalrejectq said:
Im a little confused seeing this post. Is this an old probelm? I get xpoaed to install just fine. Some of the status bar mods are wonky . Am I missing something ? Lol.
Click to expand...
Click to collapse
This is for stock ROM's.

Yeah I know. I've only ever used stock and cm11. Never had a problem besides some of the status bar icons not all changing colors. Install always went fine.
Sent from my 710C using XDA Free mobile app

Yeah some HTC 816 devices have the problem with busy box installation and that is why xposed framework doesn't work immediately after rooting.

สุดยอดเลยนาจ๋าาาา

im getting problem to install busybox on rails shows missing applets

pls reply guys

sjadhav252 said:
pls reply guys
Click to expand...
Click to collapse
Don't worry...mine is also showing missing applets.
But exposed still works.
Install xposed using the recovery method.

how can i install viper4android it keep asking for roos access after phone reboot

sjadhav252 said:
im getting problem to install busybox on rails shows missing applets
Click to expand...
Click to collapse
Mine too, in the first try there is warning in CWM about losing root etc. (sorry for my goldfish memory), the second try is ok but Busybox stills show "missing applets". However, you can continue to install Exposed Framework.
Big thanks to vbrsekhar!

Towelroot Discussion Thread

Most of us were talking about Towelroot over in Jcase's PIE thread or over in collinjames' thread, but I think it's time it deserves it's own thread.
UPDATE:
@iKrYpToNiTe made the awesome TowelPieRoot which makes this method easier to use. You can still use this thread to root your phone, but I will be using his method from now on. Happy rooting!
Important Links:
Geohot's original post.
Towelroot's Homepage
Mod Strings
What is Towelroot?
Towelroot is a rooting method for most android phones, and it uses an apk to obtain root (dead simple too, push one button, no need for other tools and workarounds). (source)
Why do we use Towelroot in conjunction with PIE?
PIE nor Towelroot disables write protection. Both of them offer a temporary root that has to be applied after a reboot. The advantage to Towelroot is that it is an APK that sits on device, so unlike PIE, Towelroot can be run later, non-tethered to a PC, should you have to power off/on. So you use PIE first while tethered and initially rooting, then Towelroot allows you to continue rooting "on the go" in the future without needing a PC.
How does it work with the Moto X?
It works the same as PIE. It gives root access but the device is still write protected. It is also temporary and must be reapplied after a reboot. However, a soft/hot reboot can keep the root access, due to soft/hot reboots only rebooting the graphical Android shell.
What does it work on?
XT1049 - Republic Wireless, not confirmed, should work.
XT1052 - European
XT1053 -T-Mobile US, not confirmed, should work.
XT1055 - US Cellular, not confirmed, should work.
XT1056 - Sprint, not confirmed, should work.
XT1058 - AT&T, Rogers, Claro, Movistar, Vivo, Oi, TIM
XT1060 - Verizon
How do I use this tool?
Remember to apply PIE first!
1. On your device, go to here.It will start to download the .apk
3. On your device, go to Settings>Security>Unknown Sources and tick the box.
4. Run the downloaded apk, tr3.apk
5. Press "welcome to towelroot" 3 times.
6. Replace the last 0 with a 1, due to modstrings.
7. make it ra1n
Your device should now be rooted and you should be able to use apps such as Greenify and Titanium Backup.
Some applications that should work with root, might not work with this method.
Some people have experimented with using Superuser apps, but I have not seen a consistent method to use one.
How are we keeping root after reboots?
We aren't rebooting! Seriously, we soft/hot reboot which allows us to keep root after a graphical reboot. And even if you do reboot, you can always reapply the root with Towelroot. You just need to make sure you have applied jcase's PIE before hand.
Xposed:
jpond83 posted up some instructions in the PIE thread about how to get Xposed to work:
Make sure you have installed PIE before you try to use Xposed or it will NOT work. View jcase's PIE thread for more details.
jpond83 said:
1) install towelroot. Xposed installer, Busybox installer, power menu
2)run towelroot, click "welcome to towelroot", replace 0 with 1, make it rain.
3) run xposed and click install
4) run busybox installer and click install
5) run power menu and click "hot reboot"
6) enjoy root without using a PC.
Click to expand...
Click to collapse
Current problems/bugs
Some users have problems with soft/hot rebooting. Reapply PIE.
Random reboots.
Warning about using this exploit
Myself or anyone that has helped develop this are not responsible for anything that occurs to your phone by using this method.
As for this thread, feel free to post your experiences with this tool or any supplements to add.

I'm glad this finally has a dedicated thread. Good job OP

I finally got it working. When I installed SuperSU it was lagging. But I kept it off. I even have hkthememanager running with KitKat all white settings from the nexus forum.
Sent from my XT1058 using XDA Free mobile app

The softboot/hot boot issue comes from not having busybox installed.

jpond83 said:
The softboot/hot boot issue comes from not having busybox installed.
Click to expand...
Click to collapse
I've installed 3 different Busybox installers:
Busybox by Stephen (Stericson)
Busybox Installer by JRummy Apps Inc.
Busybox X by Robert Nediyakalaparambil [root]
The first and the third one said they installed successfully, but the second one did not.
Even after 2 installations succeeding, I was still unable to soft/hot reboot.
Any ideas?

I use busybox installer with the blue icon. Never had a issue with softboot as long as I install everything in the order I stated in the other thread.

jpond83 said:
I use busybox installer with the blue icon. Never had a issue with softboot as long as I install everything in the order I stated in the other thread.
Click to expand...
Click to collapse
Guessing that is the Busybox Installer , I just get this when I try to install it. I have root access, but Busybox is not installing.
But when I use Busybox by Stephen, it says it installs correctly, and my Busybox checker says it does too, but Power Menu still won't Hot Reboot.

Have you ran pie root before? It needs to be ran on the device once before for it to work.

jpond83 said:
Have you ran pie root before? It needs to be ran on the device once before for it to work.
Click to expand...
Click to collapse
Replying the PIE exploit has seemed to fix it. Thank you.
Should I add to the original post that you need to install PIE?

dier325 said:
Replying the PIE exploit has seemed to fix it. Thank you.
Should I add to the original post that you need to install PIE?
Click to expand...
Click to collapse
Yes, its a must. It should only need to be ran once. After that you should never need it again unless you factory reset.

jpond83 said:
Have you ran pie root before? It needs to be ran on the device once before for it to work.
Click to expand...
Click to collapse
Wait, so you need to use PIE to make stuff work under towelroot work on the X?
If so, why not just stick with PIE? Why add towelroot?

KidJoe said:
Wait, so you need to use PIE to make stuff work under towelroot work on the X?
If so, why not just stick with PIE? Why add towelroot?
Click to expand...
Click to collapse
Did you read??? You only need to use pie once. After that you can reboot your phone as much as you want and just root with towelroot.

KidJoe said:
Wait, so you need to use PIE to make stuff work under towelroot work on the X?
If so, why not just stick with PIE? Why add towelroot?
Click to expand...
Click to collapse
Towelroot can work just by itself, but PIE adds some functionality that allows for easier softbooting.

jpond83 said:
Did you read??? You only need to use pie once. After that you can reboot your phone as much as you want and just root with towelroot.
Click to expand...
Click to collapse
I'm sorry that it bothers you so much that I have a question I'm asking. But if you must know, YES I READ. I've read this thread, the PIE thread, and Does Towel Root have any potential in the Motorola field?
And if you can read, you would know that you didn't even answer my question of "why use both?". Instead you just sort of flaming me for asking something and said pie only needs to be run once which is already stated very clearly in what I quoted.
What I'm getting at with my question is something that is implied, but not stated.....
It is understood that since neither PIE nor Towelroot disables write protection on locked bootloaders, if you root with either PIE or Towelroot, you need to re-root after power off/on (or "hard" reboot as some are calling it). It appears the advantage to Towelroot is that it is an APK that sits on device, so unlike PIE, Towelroot can be run later, non-tethered to a PC, should you have to power off/on. So you use PIE first while tethered and initially rooting, then whatever it does allows Towelroot APK to continue working properly when "on the go" in the future without needing a PC.
If that is truly the case, then I think that should be highlighted better, and @dier325 should add it to the OP as many are missing that bit of information. It would also cut out some of the frustration by those encountering issues when running PIE again, after they had to power off/on. (as they could use PIE when first setting up, then towelroot if they lose root while away from their PC).
But it does beg a few more questions (at least by someone who is READING all of this, but not using either PIE or TowelRoot)...
Is PIE needed once before Towelroot only if you want Xposed? Or is it always needed once if you ever plan on using Towelroot? (i.e. Are there any cases where Towelroot alone works? like if you only want to block ads or tether. Or must you have used PIE once already, if you want to make use of Towelroot to root at all?)
Must it be done in a certain order? I.e. if you've used towelroot and realized you forgot PIE, can you just run PIE and be good? or must you reboot, use PIE, then use Towelroot again?
What changes are made by PIE that survive power off/on and enable Towelroot to work when trying to use Xposed?
If this information is accurate, can Geohot and Jcase work together on a single solution, and possibly single on device solution for the X?

KidJoe said:
It is understood that since neither PIE nor Towelroot disables write protection on locked bootloaders, if you root with either PIE or Towelroot, you need to re-root after power off/on (or "hard" reboot as some are calling it). It appears the advantage to Towelroot is that it is an APK that sits on device, so unlike PIE, Towelroot can be run later, non-tethered to a PC, should you have to power off/on. So you use PIE first while tethered and initially rooting, then whatever it does allows Towelroot APK to continue working properly when "on the go" in the future without needing a PC.
If that is truly the case, then I think that should be highlighted better, and @dier325 should add it to the OP as many are missing that bit of information. It would also cut out some of the frustration by those encountering issues when running PIE again, after they had to power off/on. (as they could use PIE when first setting up, then towelroot if they lose root while away from their PC).
Click to expand...
Click to collapse
This is a great explanation of why we are using both. I will add a paragraph to the OP that paraphrases what you just said.
KidJoe said:
Is PIE needed once before Towelroot only if you want Xposed? Or is it always needed once if you ever plan on using Towelroot? (i.e. Are there any cases where Towelroot alone works? like if you only want to block ads or tether. Or must you have used PIE once already, if you want to make use of Towelroot to root at all?)
Click to expand...
Click to collapse
Towelroot alone works, but we've found that some applications (i.e. Xposed, Busybox) don't work unless you have PIE. Using them together allows us to use them.
KidJoe said:
[*]Must it be done in a certain order? I.e. if you've used towelroot and realized you forgot PIE, can you just run PIE and be good? or must you reboot, use PIE, then use Towelroot again?
Click to expand...
Click to collapse
The method of each one must be done in order but it does not matter which one you apply first to the device. In fact I just had Towelroot running on my device and then applied PIE allowing for Xposed to work.
KidJoe said:
[*]What changes are made by PIE that survive power off/on and enable Towelroot to work when trying to use Xposed?
Click to expand...
Click to collapse
PIE allows us to keep Busybox installed on the device which allows us to Soft/hot reboot.
KidJoe said:
[*]If this information is accurate, can Geohot and Jcase work together on a single solution, and possibly single on device solution for the X?
Click to expand...
Click to collapse
I want to remind everyone that there are very few of us who are using both of these methods together currently. It is fine for these questions to be brought up for the uninitiated. As for them working together, I think Jcase stated that he wants to move away from the X, as well as I think he is on holiday due to his current signature. I don't know about Geohot but some people have created a thread over in the Moto G forum raising some money to buy the device for him after he said he would try to work on it if he had one.

I have jcases pie root on my x and g and i either always soft boot in xposed framework and keep phone on airplane mode when not in use and charge when necessary

KidJoe said:
If that is truly the case, then I think that should be highlighted better, and @dier325 should add it to the OP as many are missing that bit of information. It would also cut out some of the frustration by those encountering issues when running PIE again, after they had to power off/on. (as they could use PIE when first setting up, then towelroot if they lose root while away from their PC).
Click to expand...
Click to collapse
I have added another section to the OP explaining the situation.
cell2011 said:
I have jcases pie root on my x and g and i either always soft boot in xposed framework and keep phone on airplane mode when not in use and charge when necessary
Click to expand...
Click to collapse
Adding them together allows you to root without having to use a PC if you do reboot your device, say it dies.

Thanks guys for clearing this up. I think Towel root should be renamed to something less middle east reference and it would be welcomed more.

So basically if we want more functionality with our root, we should do PIE first? I clicked over onto the PIE page but didn't really how it's done. I have towelroot down, but it seems PIE is a good idea to use in combo with towel root. I could be missing something though cause I'm in the XDA app at work.
I do understand though that PIE is a one time thing and we should just use towel root thereafter when we reboot and need to reroot again.
Sent from my XT1060 using XDA Free mobile app

Using PIE in conjunction with Towelroot allows you to use apps such as Xposed.
Sent from my XT1060 using XDA-FORUM, powered by appyet.com

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

5.1.1 [DOK2] Setup [Debloated & Systemless Root] [Viper4Android][Bettery Battery]

5.1.1 [DOK2] Setup [Debloated & Systemless Root] [Viper4Android][Bettery Battery]
I have seen a few people having issues with the DOK2 update and were looking for a step by step process of how to upgrade to the new firmware and optimize it to get goo performance. this thread will guide you through that process as well as link to the appropriate threads to download and get the needed files/add ons.
*****This process will wipe your phones internal storage and give you a clean install of the new firmware.
Step 1: Download the DOK2 firmware to your PC
There are a few places you can get this from:
Sammobile: N910T Firmware
Or XDA thread: Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2 UNMODIFIED Mirror
(You will need the entire firmware not just the modem and baseband)
Step 2: Download ODIN to you computer
From ODIN DOWNLOAD: ODIN 3.10.7
Step 3: Odin Flash new firmware.
The download from Sammobile or Mega should be a .zip file. you will need to unzip that file to find the .tar file which is what you will use for ODIN flashing the firmware.
If you need help using Odin to flash the firmware check out this post on Android Central: Help Thread
After you have completed the Odin Flash the phone should reboot and come to the setup screen with your new firmware.
Step 4: Odin Flash TWRP
Download TWRP to your computer: TWRP Downloads
Specifically you want this file: twrp-2.8.7.0-trltetmo.img.tar
Use Odin to flash TWRP recovery onto your device.
If you get lost you can check this tutorial: ODIN Help
Step 5: Reboot your device and setup
Once you have rebooted go ahead and set up your device. we will worry abou debloating and getting root after your device is setup.
Step 6: make a backup in TWRP
Once your device is setup make a TWRP backup of your setting
Step 7: Getting Root
*****Update: New SuperSu 2.64 beta. Works even better with Samsung phones. *******
You will need the latest SuperSU beta from the below thread.
SuperSU Beta Systemless Root
Newest version is 2.64
You will then boot into TWRP and flash that zip in recovery. This will give you "Systemless Root"
Systemless root allows you to use the stock kernel with SE LINUX enforcing, but still be able to use root apps. However this is not complete root. Some root apps that need to modify the system will not work. this is just a BETA root and is not final yet. check back to that thread for updates as they come out.
Once you have flashed the SuperSU zip reboot your device and verify your root apps are working.
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater V3.90 DeBloater
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps
http://forum.xda-developers.com/not...pt-touchwiz-bloating-script-222-apps-t3258537
This Option removes 222 applications. It is a simple download and flash in recovery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Step 9 Viper4Android on Systemless root.
Download the Viper4 Andriod/Beat installer
Viper4Android w/ Beat Audio
Flash the installer zip in TWRP and reboot your device
Download BusyBox Installer
BusyBox by Stephen (Stericson)
Install BusyBox
Reboot
install Viper$Android Drivers
Reboot
Download both the Viper4Android SU policy fixes
1.) ViPER4Android-supolicy.zip
2.) XM_V4A_Fix_by_androidexpert35.zip
Reboot into TWRP and flahs both of these. you can flash them at the same time just to them in the order above. [1 then 2]
Reboot the device and enjoy V4a.
******Also the Beat portion of the zip is a bit wonky sometimes. I have not yet been able to get it to opperate effectively, so you may want to disable it or freeze it with Titanium backup.
Disclaimer: NONE of these zips are mine. I am posting download links from my mega, because I pulled these files from 3 different threads and only one was from an OP. the main Viper4Android /beats install zip comes from here : [SUPER MOD][4.3+/6.0][ v6.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD!
*************************************************************************************************************************************************************************
With this setup I have easily gotten more than a days worth of usage. I average about 5.5 hours of SOT and 24 hrs between charges. Normally I plug in around 20 hours with about 40% battery left.
*****These are all items developed by other XDA USERS. Please provide the thanks on their respective threads as well.

Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is any way of getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.

James62370 said:
Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is anyway off getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.
Click to expand...
Click to collapse
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
The two main reasons to use this method are:
1.) It keeps the system intact, which allows you to use apps that check for root. (eg. Android Pay, Some Bank Apps etc)
2.) It allows you to use the stock kernel from 5.1.1. Currently the only way to get root on 5.1.1 and up is to install a custom kernel. Which is fine, and there are two really great option available with Emotion and Beast Mode, but I find the stock kernel gets me the best battery life and is the most stable.
ALSO this will be the way root is done going forward. 6.0.1 has a bunch of system file locks that prevent much of the system tinkering from happening. Chainfire (dev who built SuperSU) has a nice right up about the system partition on XDA right now explaining why some of the system tweaks we were used to will not be possible in the future. so at the very least this is good practice for getting ready for the Marshmallow update.

ShrekOpher said:
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater [http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294]
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps [http://forum.xda-developers.com/not...t-touchwiz-bloating-script-222-apps-t3258537]
This Option removes 222 applications. It is a simple download and flash in recoevery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Click to expand...
Click to collapse
Witch option is the easier? :silly:

Avide said:
Witch option is the easier? :silly:
Click to expand...
Click to collapse
Option #2 is WAY easier as long as you don't want to modify the script. You just download it to you phone boot into recovery and flash it. Then reboot. Takes 5 min.

ShrekOpher said:
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
Click to expand...
Click to collapse
Appreciate your reply. I was under the impression that the boatloader is already unlocked which is why we can flash a recovery without jumping through too many hoops. I know that a custom recovery trips Knox, but if there's a way to install the latest supersu through a utility such as flashfire or mobile odin, Knox won't be tripped.
I'm not really worried about warranty, just curious to see if it's possible to retain the integrity. Unfortunately both those options I mention requires the device to already be rooted which defeats what I'm trying to accomplish.
Hopefully someone will be able to figure something out in the near future.

Is it possible to use xposed with this?

So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?

masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.

chodaboy19 said:
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.
Click to expand...
Click to collapse
Well i'm on 5.0.1 right now pop rocks, so yeah i probably will wait since there isn't a particular feature... i'm using the DOK2 modem on COD6 rom right now.

Is there a list of apps you should disable via the debloater specific to the tmobile note4?

masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
There is no dark theme option as of right now, really it's the only thing i miss.

Will Rickards said:
Is there a list of apps you should disable via the debloater specific to the tmobile note4?
Click to expand...
Click to collapse
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.

I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL

chodaboy19 said:
I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL
Click to expand...
Click to collapse
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.

ShrekOpher said:
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.
Click to expand...
Click to collapse
I think I found the culprit after 2 days of googling and countless wasted hours. My specific problem was that Media process was running all the time which in turn was causing Google Play Services to run at all times.
The Media process includes 2 packages: Media Storage and Download Manager. Together they perform scanning and indexing of media files on the internal SD and external SD.
I came across this page:
http://geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain/
I did step #3 which states that having more than 1,000 files in a folder makes this process crap out. I reformatted my microSD card, then I copied back all the files to the microSD. Then finally I deleted most of the pictures so that no one folder had more than 400 images.
I rebooted my phone and it started to behave normally. The Media Process only ran for 5minutes and stopped. Google Play Services ran for 2min and stopped. I have been through 1 charge already and got 5hrs or so of screen time with heavy use, I was installing apps, configuring accounts, freezing apps with Titanium backup, etc.
Overall, it seems like I have a happy ending to my story, BUT I will post a followup if the phone craps out again.
EDIT:
How do you get it to show the time on battery?
Mine doesn't have that information:

Does anyone have any interest in me adding how to set up Viper4Android on Systemless root to this thread? Just curious if I should go through the trouble.

There is a new version of SuperSU 2.64:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Changelog:
20.12.2015 - v2.64 - BETA
- (systemless) Detect more boot image partition names
- (systemless) Blank partitions before writing to them
- (systemless) Ask to restore boot and recovery images on full unroot
- (systemless) Implement "uninstall competing superuser apps"
- (systemless) Samsung: prevent "KERNEL IS NOT SEANDROID ENFORCING" warning
- (systemless) Cleanup system install properly if present, fixes a number of possible bootloops
- ZIP: 6.0+: Detect firmwares that can reload sepolicy from /data and use system-based root on these ("allow init kernel:security { load_policy }")
- supolicy: Additional SELinux patches for M (reduced logging only)
- Update translations

ShrekOpher said:
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.
Click to expand...
Click to collapse
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk

AlexanderBlaQ said:
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Should be working now. Thanks for the heads up.

MM Custom rom, updated super user and lost root

Is there any easy way to get root back? Do I just flash a previous version of SuperSU with flash fire? Thanks.

You have to re run the root file on your pc.

helllmonkey said:
Is there any easy way to get root back? Do I just flash a previous version of SuperSU with flash fire? Thanks.
Click to expand...
Click to collapse
Just need to run the root.bat file from your PC and you'll be good to go. That can be found in the thread on how to root your phone, install Xposed, etc.
Then make sure not to to update SU. There are a few workarounds to simply avoiding the update, but in general you don't want to take it. It will make you lose root every time you update.

nyr2k2 said:
Just need to run the root.bat file from your PC and you'll be good to go. That can be found in the thread on how to root your phone, install Xposed, etc.
Then make sure not to to update SU. There are a few workarounds to simply avoiding the update, but in general you don't want to take it. It will make you lose root every time you update.
Click to expand...
Click to collapse
Actually is there a way to stop it from popping up, asking me to Update SuperSU or not everytime when I press auto update for my other apps in the Google Play?
There were once or twice I mistakenly pressed yes when updating other apps (obviously when I was daydreaming or sleepwalking) and I will have to root it again.

cn2661 said:
Actually is there a way to stop it from popping up, asking me to Update SuperSU or not everytime when I press auto update for my other apps in the Google Play?
There were once or twice I mistakenly pressed yes when updating other apps (obviously when I was daydreaming or sleepwalking) and I will have to root it again.
Click to expand...
Click to collapse
If you long press the notification in the notification pull down, you can then turn off app notifications for it. That would stop the reminder and the constant # symbol from sitting in your tray. That's what I did. If you open the app itself it will still tell you the binary needs to be updated, but you can just ignore it. Basically you're running the 2.78 or whatever SU app and binary that installs when you run the root.bat but you have installed the latest version so you don't have to see it in the store. Supposedly the most recent version of the app itself "fixed" the problem of losing root just by installing the app but we can't install the binaries on our phone. So you can try updating it in the store--I'm on 2.82 with old binaries. There's still I suppose a chance you could lose root, but then again you just rerun the root.bat.
So all in all I'd recommend downloading the 2.82 update. Don't try to install the binaries. Hide the notifications. Then you're good to go. If you somehow lose root in the process then rerun the root.bat and look around here further. Someone had another workaround with a modified version of SuperSU, but I never tried that because my setup was fine and I was tired or screwing around, LOL.
This, again, is why I will not buy another phone unless I know it can have the BL unlocked. I want to use Magisk and have a custom recovery. Tinkering around on this thing and risking bricks when you then have to re-flash everything, it just sucks.

nyr2k2 said:
If you long press the notification in the notification pull down, you can then turn off app notifications for it. That would stop the reminder and the constant # symbol from sitting in your tray. That's what I did. If you open the app itself it will still tell you the binary needs to be updated, but you can just ignore it. Basically you're running the 2.78 or whatever SU app and binary that installs when you run the root.bat but you have installed the latest version so you don't have to see it in the store. Supposedly the most recent version of the app itself "fixed" the problem of losing root just by installing the app but we can't install the binaries on our phone. So you can try updating it in the store--I'm on 2.82 with old binaries. There's still I suppose a chance you could lose root, but then again you just rerun the root.bat.
So all in all I'd recommend downloading the 2.82 update. Don't try to install the binaries. Hide the notifications. Then you're good to go. If you somehow lose root in the process then rerun the root.bat and look around here further. Someone had another workaround with a modified version of SuperSU, but I never tried that because my setup was fine and I was tired or screwing around, LOL.
This, again, is why I will not buy another phone unless I know it can have the BL unlocked. I want to use Magisk and have a custom recovery. Tinkering around on this thing and risking bricks when you then have to re-flash everything, it just sucks.
Click to expand...
Click to collapse
Cheers mate, perfectly works,
by Updating the SuperSU app, Not updating the SU Binary and long-press notification to shut the notification off.
Peace to the Earth again.:good: