Database Users

[Q] Updating while in in-between rooted state

Allow me to explain my vague topic.
My son and I both have a droid pro, and are both running update 3.8.7
However, both of our phones were rooted before the update came and simply let it update.
After it got updated I noticed I was not rooted anymore. And z4root would not unroot my phone, or root it anymore.
Basically it was in sort of an in-between state, between rooted and unrooted.
The way I had to fix mine was by running the 2.2.6 (or whatever it was )sbf I had found on TBH, and from there going through the update progress.
Problem with that was that I had to set it back to factory settings.
So, my son's phone is still in that in-between state. Does anyone here know if it will pose a problem when this new gingerbread update hits his phone?
Will I be forced to do a factory reset with a previous sbf in order to be able to do it without it bricking?

I can't speak from personal experience, but others here have strongly suggested unrooting before update to prevent problems like what you described. As for the latest update, there are not really any reports yet on how it has gone for rooted users yet.

Before the last 3.8.7 updated, my phone was rooted with z4root and I had some unimportant apps frozen, nothing that is really crucial. I went ahead with the update (using the update.zip) which worked just fine. Yes, z4root is a bit confused of what is going on but I would not worry about it - I guess it is just logging events and thinks that because u havent unrooted it thru the program, it must still be rooted. The update removes the root anyways .. but I went ahead to unroot it with aroot again which worked like a charm on 3.8.7. At the moment, I am going to updating to Gingerbread also using an update.zip and I can give you a detailed report on how things went in a little bit ...

tnt118 said:
I can't speak from personal experience, but others here have strongly suggested unrooting before update to prevent problems like what you described. As for the latest update, there are not really any reports yet on how it has gone for rooted users yet.
Click to expand...
Click to collapse
This.
You might be able to go through just fine without flashing the SBF, but it's always a good idea to unroot/unfreeze apps and be stock for an update. Always.

Not always.
After the update from 2.26 to 2.63 (cant remember?) I had rooted my phone with z4root and froze some unimportant bloat ware, I didnt touch any programs that I deemed important for the system. I then proceeded to update to 3.8.7 without unrooting or unfreezing apps! It worked fine. After this, the system was unrooted again, I rooted again with aRoot without any problems.Now, I upgraded to Gingerbread, also coming from being rooted. The individual updates remove the rooting and you are back at point zero and, as long as you dont have any important system utilities frozen, it will work absolutely fine.

vivid22 said:
Before the last 3.8.7 updated, my phone was rooted with z4root and I had some unimportant apps frozen, nothing that is really crucial. I went ahead with the update (using the update.zip) which worked just fine. Yes, z4root is a bit confused of what is going on but I would not worry about it - I guess it is just logging events and thinks that because u havent unrooted it thru the program, it must still be rooted. The update removes the root anyways .. but I went ahead to unroot it with aroot again which worked like a charm on 3.8.7. At the moment, I am going to updating to Gingerbread also using an update.zip and I can give you a detailed report on how things went in a little bit ...
Click to expand...
Click to collapse
Interesting. Well if the root has been removed then there is no problem.
My son has a lot less problems then I do so I never had to freeze any apps. Meaning I basically never had to root his phone to begin with. So I may just get away with doing nothing then.
I mean I had rooted his phone on the previous system, on 3.8.7 it never worked with z4root so I'm guessing it's not rooted at this point.
I'll try to double check
As for my own phone, I will need to keep an eye on how to after the new update. I have serious battery problems that I blame on useless background processes.
I'll just tell him to go ahead and run it, if it ever comes to us that is.
Thanks guys

That is true, but z4root is just mistaken in a sense that it is confused and thinks its still rooted while its actually not ... Unless you click unroot in z4root, it will always assume its still rooted. z4root will not work in the 3.8.7 version as its not compatible. You need to use aRoot for that. And I can confirm that all updates work, even when the phone is left rooted before the update! Every update automatically unroots (locks) the phone again anyways.

Ok.
I just found the update on droidforums and went ahead and installed on my phone because I couldn't wait for Verizon
Later on ill do my sons phone as well. Im sure it will go well so ill report back to help ease the mind of others.

yeah so it wasnt a problem. I ran the same update.zip file i found and my sons phone is running nicely.

vivid22 said:
Not always.
After the update from 2.26 to 2.63 (cant remember?) I had rooted my phone with z4root and froze some unimportant bloat ware, I didnt touch any programs that I deemed important for the system. I then proceeded to update to 3.8.7 without unrooting or unfreezing apps! It worked fine. After this, the system was unrooted again, I rooted again with aRoot without any problems.Now, I upgraded to Gingerbread, also coming from being rooted. The individual updates remove the rooting and you are back at point zero and, as long as you dont have any important system utilities frozen, it will work absolutely fine.
Click to expand...
Click to collapse
It may work just fine, and it may even work fine most of the time, but it's still a good idea to unroot before installing a stock update. A lot of issues can potentially come up. Unrooting doesn't hurt anything since the updates break root anyway. It's just a good precaution. A lot of people had major issues with the last 2.2 update when they installed it without unrooting first.
It looks like all is well on updating with the Gingerbread release. But better than safe than sorry I say.

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

Need root, but not a custom ROM

Situation:
I'm on Verizon with a Note 3 running 4.4.2. The methods shown for rooting almost always make the assumption that people want to run a custom ROM. I do not. The Safestrap developer bailed on the project, and nobody knows if it can be used in the future anyway.
Goals:
1. This is a business phone, not something that I want to continuously frog around with. I just want to be able to record telephone conversations when using my Bluetooth headset exactly the same as when I'm not, maybe a decent backup, and basically get my Verizon Note 3 and Android's functionality up to the level of where Windows Mobile has been since 2009. From what I understand, to do that may require the Xposed Framework.
2. Be able to give root back and have everything back like it was if necessary.
3. Be able to take OTA updates. I don't care if I need to uninstall some apps, give root back, accept the OTA update, take root back, and reinstall the apps. OTA updates don't happen often anyway.
4. Not lose the phone warranty in the process if possible. It seems one of the required apps for the root process is SuperSU. One of the options is to disable KNOX. Other than everyone doing it, and being recommended for vague reasons, why would I want to do that? Can you re-enable it later?
Thanks!

Towel root should do what you want. I currently don't know of anyone that used towel root or kingo that tripped Knox. Since you're on NC4 probably kingo isn't an option so it's towel root.

thegamerdarkseid said:
Towel root should do what you want. I currently don't know of anyone that used towel root or kingo that tripped Knox. Since you're on NC4 probably kingo isn't an option so it's towel root.
Click to expand...
Click to collapse
So Towel root and what? I'm guessing SuperSU without having it disable KNOX...or?

IT_Architect said:
So Towel root and what? I'm guessing SuperSU without having it disable KNOX...or?
Click to expand...
Click to collapse
You have to use SuperSu for root privileges.

IT_Architect said:
So Towel root and what? I'm guessing SuperSU without having it disable KNOX...or?
Click to expand...
Click to collapse
Towel Root is What you use to gain ROOT. Towel Root is basically a Program/Software that you will use to ROOT your Note 3. I used Kingo so I don't know much about Kingo but its probably not much different than Kingo, but based on what the other person said you need to use Towel Root. One thing you will want to do AFTER you go through the ROOT process is, Look in your app drawer & see if SuperSU is installed, if it is, you are Rooted, if it is Not, you are Not. I would also Download Root Checker from the Play Store to Verify you have ROOT.
SuperSU or Superuser is an app that gets installed in your phone when you Root it, that Manages what other apps you Grant/Deny Root permission. It does Not ROOT your phone. You do not need to download it from the Play Store. It is only in the Play Store to give you Updates, Its not meant to be as an initial download. Hope this Helps Bud. Happy Rooting! :laugh:

jasonsc1 said:
Towel Root is What you use to gain ROOTSuperSU or Superuser is an app gets installed in your phone when you Root it, that Manages what other apps you Grant/Deny Root permission...You do not need to download it from the Play Store. It is only in the Play Store to give you Updates
Click to expand...
Click to collapse
That makes sense.
So what I'm thinking is:
1. Root
2. Make sure SuperSU is there to know I'm rooted.
Later when there is an update:
- Refuse it until there is a way to get root without triggering KNOX.
- Uninstall root apps.
- From SuperSU give root back, which should bring it back to stock.
- Then allow the OTA and hopefully it will not trigger KNOX
I'm guessing it would be best not to install xposed framework because it makes system changes, which could cause things to go wrong during an update.
All that I need in the near term is to get my Bluetooth voice recording back.
Thanks!

IT_Architect said:
That makes sense.
So what I'm thinking is:
1. Root
2. Make sure SuperSU is there to know I'm rooted.
Later when there is an update:
- Refuse it until there is a way to get root without triggering KNOX.
- Uninstall root apps.
- From SuperSU give root back, which should bring it back to stock.
- Then allow the OTA and hopefully it will not trigger KNOX
I'm guessing it would be best not to install xposed framework because it makes system changes, which could cause things to go wrong during an update.
All that I need in the near term is to get my Bluetooth voice recording back.
Thanks!
Click to expand...
Click to collapse
That sounds like a Pretty good plan. I Rooted my Note 3 a while back. I was on JB & I'm still currently JB. ACTUALLY Its been a while since I've been on XDA. When I did Root my Note 3 there was NO WAY to ROOT Kit Kat 4.4.2. I did NOT know there was a way to ROOT it now. If there is Can you post a Link. Everything I've read says theirs No Way to Root Kit Kat but its been a while since I researched it. In my case After I Rooted my Note 3 I Froze SDM the app that receives Versions OTA updates. I kept getting one wanting me to Update to Kit Kat. I did not want to Lose my Root & then be on Kit Kat & not be able to Re-Root my Note 3. XDA has a version of Kit Kat made my a couple of the Developers, Beanstown106's & Hashcode's (the guy who made safestrap) that Already has Root. I'm going to Flash their Kit Kat version once I grow the Kahunas. I also Froze Knox so it could Not trip, although it did not Trip when I Rooted my Note 3 via Kingo but I'm on a different version than you.
Also You will Not need to Uninstall the Root apps. They will have No Effect on your phone. They will just not have Root permissions. I also don't see a need to Un Root- Re Root. I would just not accept the OTA Updates. I also have Xposed Framework with several modules & it & them have No negative effects on my Note 3. Anyways Hope this Helps somewhat, Post that Kit Kat Root Link if you can. Thanks
Here is a Link to what Im going to do.
http://forum.xda-developers.com/showthread.php?t=2740466

jasonsc1 said:
If there is Can you post a Link. Everything I've read says theirs No Way to Root Kit Kat
Click to expand...
Click to collapse
There are at least two:
1. Towelroot - Free
2. One Click Root - 2 packages to choose from: $29.95 package which includes root only and $39.95 which includes rooting + removal of bloatware + 30 days free tech support.
jasonsc1 said:
After I Rooted my Note 3 I Froze SDM the app that receives Versions OTA updates... I also Froze Knox so it could Not trip, although it did not Trip when I Rooted my Note 3
Click to expand...
Click to collapse
What did you use to freeze them with, Titanium?
jasonsc1 said:
Also You will Not need to Uninstall the Root apps. They will have No Effect on your phone. They will just not have Root permissions.
Click to expand...
Click to collapse
However they make changes in the system area, which I was concerned might foul up the OTA or trip KNOX.
jasonsc1 said:
I also don't see a need to Un Root- Re Root. I would just not accept the OTA Updates.
Click to expand...
Click to collapse
I am a little gun shy that if the OTA finds it rooted, it will trip KNOX and not do any more OTAs.
jasonsc1 said:
I also have Xposed Framework with several modules & it & them have No negative effects on my Note 3.
Click to expand...
Click to collapse
That is the only other product I looked at. It looks interesting, but I don't see that it brings anything to the table that I want. I'm not a customization guy, I just need to get basic functionality out of the phone such as call recording under Bluetooth and be able to backup my entire phone and settings.
Thanks!

IT_Architect said:
There are at least two:
1. Towelroot - Free
2. One Click Root - 2 packages to choose from: $29.95 package which includes root only and $39.95 which includes rooting + removal of bloatware + 30 days free tech support.
What did you use to freeze them with, Titanium?
However they make changes in the system area, which I was concerned might foul up the OTA or trip KNOX.
I am a little gun shy that if the OTA finds it rooted, it will trip KNOX and not do any more OTAs.
That is the only other product I looked at. It looks interesting, but I don't see that it brings anything to the table that I want. I'm not a customization guy, I just need to get basic functionality out of the phone such as call recording under Bluetooth and be able to backup my entire phone and settings.
Thanks!
Click to expand...
Click to collapse
Ok, I Rooted my Note 3 back in March, at that time there was No Way to Root Kit Kat. I did a lil Looking around & did find that you can Now Root Kit Kat.
No, I did not use Titanium, I do have it. I usually use Titanium just to backup my apps/data. I Froze the SDM app which is the app that Looks for/Receives OTA. So I do Not get any Updates. I don't see reason too. The only OTA that has came out since I bought my Note 3 is the Kit Kat OTA. If you Freeze that app you will have No Problems.
To my Knowledge the Only ROOT apps that can make changes to the System area is the Xposed apps/Modules. No other Root App that I know of makes any changes to the System area, unless you let it, & that can be reversed & the Apps STILL dont have to be Uninstalled. I can not think of ANY Reason to Uninstall the ROOT apps because there is Nothing about them that could cause Knox to Trip. I got NOTHING.
Yes Xposed opens a WHOLE NEW WORLD of Customization's. After having it, I could not live without it. I LOVE be able to Truly own my device. XPrivacy Guard gives me the Warm & Fuzzy that the 2 GPS tracking alarms I have on my Gixxer give me. I control what Permissions apps have, what information they can receive. I could not Live without XPosed or XPrivacy Guard,

jasonsc1 said:
Ok, I Rooted my Note 3 back in March, at that time there was No Way to Root Kit Kat. I did a lil Looking around & did find that you can Now Root Kit Kat.
Click to expand...
Click to collapse
I might add that 4.4.2 there is, but NOT 4.4.4 without tripping KNOX. I know the 4.4.2 settings interface is quite a bit different than JB, but whether that translates into anything useful, I don't know. I do know most docs are for JB. Thus, if there is anything in 4.4.2 worth having that you don't already have via root, now might be the time IF they are still rolling 4.4.2. You don't want to snag 4.4.4 by accident. I know that I haven't received an update request yet, and I am on 4.4.2, but the S5 gets 4.4.4. From the little reading I've done, there is little difference between 4.4.2 and 4.4.4 except KNOX has been updated, and a massive bug roll-up . (What those bugs might be, I have not researched.) Moving to KitKat, you also incur the problem of apps writing anywhere to the SD card. IMO, the biggest difference between JB and KitKat 4.4.2 and KitKat 4.4.4 is security. 4.4.4 on the Note 3 does NOT give you the new Touchwiz that the S5 gets with 4.4.4.
"At the beginning of June, Google released two new Android 4.4 KitKat updates. First was Android 4.4.3 KitKat, a massive bug fixer. A few days later, the company pushed out its Android 4.4.4 KitKat update. Both were, and still are, bug fixers aimed at squashing major Android 4.4.2 KitKat problems and they continue to land for key devices as we push toward the fall. I am miffed by the omission of the new TouchWiz on the 4.4.4 update on the Note 3"
There aren't any bugs that I noticed, and until they give you something other than putting you into tighter and tighter box, you might want to wait until they come out with something that benefits you.
jasonsc1 said:
No, I did not use Titanium, I do have it. I usually use Titanium just to backup my apps/data. I Froze the SDM app which is the app that Looks for/Receives OTA. So I do Not get any Updates. I don't see reason too. The only OTA that has came out since I bought my Note 3 is the Kit Kat OTA. If you Freeze that app you will have No Problems.
Click to expand...
Click to collapse
Back to my original question, what did you freeze it with, and BTW, is SDM the name of the program, or is that an abbreviation for something?
jasonsc1 said:
To my Knowledge the Only ROOT apps that can make changes to the System area is the Xposed apps/Modules. No other Root App that I know of makes any changes to the System area, unless you let it, & that can be reversed & the Apps STILL dont have to be Uninstalled. I can not think of ANY Reason to Uninstall the ROOT apps because there is Nothing about them that could cause Knox to Trip. I got NOTHING.
Click to expand...
Click to collapse
That is very helpful, and clarifies things for me.
jasonsc1 said:
Yes Xposed opens a WHOLE NEW WORLD of Customization's. After having it, I could not live without it. I LOVE be able to Truly own my device. XPrivacy Guard gives me the Warm & Fuzzy that the 2 GPS tracking alarms I have on my Gixxer give me. I control what Permissions apps have, what information they can receive. I could not Live without XPosed or XPrivacy Guard,
Click to expand...
Click to collapse
What is Gixxer? There is Privacy Guard, and XPrivacy. I assume you mean XPrivacy.
Thanks!

Lol, I meant to put what I used in my Last reply. I used Rom Toolbox Pro. It's also a Great App. I actually prefer it more than Titanium Backup. I believe because of the UI.
Glad to Help, what lil I can
Oh Gixxer is another name that Suzuki MC riders call their GSXR. I have a 08 GSXR 1000. A lot of riders call the GSXR, a Gixxer. Lol, or something like Gixxer 8k (08 GSXR 1000) would be mine. Lol. I sometimes assume everyone is a Rider. Lol. Sorry about that.
Yes I meant X PRIVACY Not LBE Privacy Guard. I've heard Horror stories about it. I have Never had a Problem with X PRIVACY yet.
Oh, One more thing, As far as Safe strap goes. You can definitely use it on your Note 3 right now. Yes the developer stop sending updates but trust me he's around. He's on here all the time, with New stuff. He helped develop the XDA Kit Kat Rom. His name is Hashcode. Again Safe strap is the ONLY way to go if you are going to flash Roms. That or TWERP, which is Harder (more complicated) to get on Note 3 & Not as Good. Safestrap is so Good bc you always can Boot into your Stock slot, while you still have a Custom slot too, if anything goes wrong, you could still Boot to the other.
Safestrap=The Best Custom Recovery, IMO
Later Bud. I work nightshift this weekend, so it's time for me to get some sleep to be back at it, at 6pm this evening.

This are my thoughts for everyone to critique. Let me know if there are any flies in the ointment before I proceed.
Prerequisites:
1. Go into Settings/Security, and make sure Unknown sources is checked, and Verify apps is unchecked.
Root for 4.4.2:
1. Install Towelroot
2. Install Check Root from Play Store and check for root
3. Download SuperSU zip file from the link on the developer's thread, http://forum.xda-developers.com/showthread.php?t=1538053. This will NOT come from the Play Store or Amazon. Then unzip it on your phone. Then go to the "common" directory, and run the APK. After that you may get a prompt to update the binaries.
4. When you Run SuperSU and it asks you if you want to disable KNOX, SAY NO!!!
5. Then install Titanium backup and Freeze KNOX, so you can Thaw it later.
____com.sec.enterprise.knox.attestation
____com.sec.knox.eventsmanager
____KLMS Agent
____KNOX
____Knox Notification Manager
____KNOX Store
Unroot back to factory for 4.4.2:
1. Go into Titanium Backup and Thaw KNOX.
2. Open ES File Explorer
____a. Go to Favorites and hit the / button
____b. Click on menu / Settings / and check Enable Root Explorer
____c. Also check Mount File System
____d. Click the back button
3. Then remove SU. (The developer is working on a way to do this automatically with his full unroot function, which will make this step unnecessary)
____a. Open ES File Manager
____b. To to system / bin and find the SU folder. Do a long press and delete
____c. Click the back button and go to system / xbin directory and find the SU file and delete if any present.
____d. Click the back button and go to system / app directory and find Superuser.apk and delete it if it on your phone.
4. Reboot. Root should be gone.
5. Do a factory reset, go to Settings / Personal / Backup and reset
Summary: This should put the phone back to stock for factory warranty, or to sell, or to simply start over.

I would suggest you drop the requirement to be able to take an OTA with a customized phone. It is almost always a better idea to (i) make your backups, investigate whether you can root the new release - and if so, then (ii) restore to full stock, (iii) take the OTA, (iv) re-root and (v) have your way with things.
The reasons are several, but at least one of them is that the OTA installers tend to do a top-level, recursive chmod()/chown() in /system/{x}bin, followed up with chmod()/chown() operations on individual files in those file subtrees as needed. This has the side effect of emasculating the "su" binary privilege escalation via setuid. I wouldn't be surprised if - as a result of SElinux enforcing mode - similar sorts of troubles start occurring due to similar resets/modding of SElinux extended attributes in the same file trees (e.g. if the OTA installer starts doing recursive chcon()s).
(The above is the raison de etre for apps like "OTA rootkeeper" and so forth - they attempt to work around this OTA installer side effect)
The second reason is that OTAs sometimes bundle a bootloader update. Samsung's strict rollback enforcement policies means that you probably will not be able to undo an OTA that you regret (for any reason) without triggering Knox.
I'm still on MJE. It made me happy when I bought the phone & is still making me happy, so the fact that there are new releases available doesn't bother me one whit. It is still a fantastic phablet (& I can exploit the WiFi tether bug without Wanam and all the related framework mods).
FWIW, I reviewed the .apk/.odex files that I "froze" (using "chmod 000", not TiBu); things have changed a little bit since MJE, but:
Knox Disable: ContainerAgent, ContainerEventsRelayManager, KLMSAgent, KNOXAgent, KNOXStore, KnoxAttestationAgent
OTA Nagware Disable: LocalFOTA, SDM
Asurian Spyware Disable: VMS.apk
Probably I should also disable SHealth too. These Samsung phones are bristling with surveillance crap, and there seems to be no end to it. Probably it's even worse now with KitKat. Who knew that the Orwellian future would be developed and financed by marketing companies ... and thereafter trivially co-opted by governments?
have fun with your phone.

I was pretty much settled on not rooting, and you come along and start making sense with solid business reasons. I also view Google, Samsung, Microsoft, and the government access for what it is, criminal activity. I simply want a phone that has the capabilities of my old Windows Mobile phone, and the same levels of privacy.
If they can spy on us, than a requirement for Google and all government personnel is to have 24 x 7 video and audio surveillance on them while they are at work, and every room in their house at home, and have it stream live on YouTube..

Just safestrap it already. Even on NC4 OTA, you can safestrap and install NC2 kernel and pick from many fantastic 4.4.2 ROMs. In the future, take the hypothetical 5.0 update and then you'll never have root, lol.
Anyway, you can return to stock NC4 if needed.
OR don't. Your loss.

xdadevnube said:
Just safestrap it already. Even on NC4 OTA, you can safestrap and install NC2 kernel and pick from many fantastic 4.4.2 ROMs.
Click to expand...
Click to collapse
- I don't see the necessity of a custom ROM. I simply want to be able to record calls with my Bluetooth active. This limitation serves as a reminder that a lot less effort goes into Android than we tend to believe. This is a legal requirement for many businesses. Fortunately for Android, most development and innovation is done out of necessity by phone makers such as Samsung, etc.
- I also want to be able to prevent the update to 4.4.4.
- To do the rooting and SafeStrap, I would want to be able to un-SafeStrap, un-SuperSU, re-enable KNOX, and un-root back to factory. I haven't seen that discussed anywhere. The only thing I see to be able to get back to factory is this, if it works: http://www.galaxynote3update.com/un...tock-official-firmware-4-4-2-or-4-4-3-kitkat/ and it does not address SafeStrap. There is more to this than warranty, it is getting the phone back to stock to fix problems. There are thousands of posts of people having problems after rooting and installing custom ROMs.
xdadevnube said:
In the future, take the hypothetical 5.0 update and then you'll never have root
Click to expand...
Click to collapse
That's what concerns me. I understand why Samsung is doing what they are doing. IOS has been pushing Android out of the enterprise and government by support efficiencies and legislated security requirements. Samsung is the only Android they are allowed to buy. Thus, I've noticed:
- The newer it is, the more secure it is. Security in the ?NIX world is simplistic and limited. The easiest fix is to block functionality, and add KNOX as the enforcer and recorder.
- The features you gain with each new release, are less valuable than the features you lose from increased operating system security. Android is rapidly becoming as confining as the iPhone.
- Control over privacy becomes less and less with each new release.
While the progression makes sense from an operating system security standpoint, but runs counter to privacy control and functionality, the reasons why people buy Android.

To completely unroot and restore to stock. Uninstall safestrap recovery. Uninstall towelroot. Uninstall busybox. Uninstall superuser. Factory reset phone. Then flash NC4 with odin for good measure. You really dont need to install safestrap at all unless you want to do backups.

IT_Architect said:
- I don't see the necessity of a custom ROM. I simply want to be able to record calls with my Bluetooth active. This limitation serves as a reminder that a lot less effort goes into Android than we tend to believe. This is a legal requirement for many businesses. Fortunately for Android, most development and innovation is done out of necessity by phone makers such as Samsung, etc.
- I also want to be able to prevent the update to 4.4.4.
- To do the rooting and SafeStrap, I would want to be able to un-SafeStrap, un-SuperSU, re-enable KNOX, and un-root back to factory. I haven't seen that discussed anywhere. The only thing I see to be able to get back to factory is this, if it works: http://www.galaxynote3update.com/un...tock-official-firmware-4-4-2-or-4-4-3-kitkat/ and it does not address SafeStrap. There is more to this than warranty, it is getting the phone back to stock to fix problems. There are thousands of posts of people having problems after rooting and installing custom ROMs.
That's what concerns me. I understand why Samsung is doing what they are doing. IOS has been pushing Android out of the enterprise and government by support efficiencies and legislated security requirements. Samsung is the only Android they are allowed to buy. Thus, I've noticed:
- The newer it is, the more secure it is. Security in the ?NIX world is simplistic and limited. The easiest fix is to block functionality, and add KNOX as the enforcer and recorder.
- The features you gain with each new release, are less valuable than the features you lose from increased operating system security. Android is rapidly becoming as confining as the iPhone.
- Control over privacy becomes less and less with each new release.
While the progression makes sense from an operating system security standpoint, but runs counter to privacy control and functionality, the reasons why people buy Android.
Click to expand...
Click to collapse
It takes 10 minutes to root. And 10 minutes to unroot. Including safe strap. Nothing will trip knox. Beans has the stock nc4 ota rooted deodexed and busy boxed. All is needed to do what you want to do. You will find Zero anything for your stock odex ota. So root safestrap flash the stock rom and add call recording via xposed.... There is no other info you need that isnt already posted in a sticky.

drewcam888 said:
To completely unroot and restore to stock. Uninstall safestrap recovery. Uninstall towelroot. Uninstall busybox. Uninstall superuser. Factory reset phone. Then flash NC4 with odin for good measure. You really don't need to install SafeStrap at all unless you want to do backups.
Click to expand...
Click to collapse
- When SuperSU is installed, it disables KNOX. If I uninstall SuperSU, will it re-enable KNOX, or if I flash back to Verizion KitKat 4.4.2 NC4 N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5.7z, from here, http://forum.xda-developers.com/showthread.php?t=2524572 will it restore the KNOX functionality?
- What happens to the ROMs in the ROM Slots when you uninstall SafeStrap recovery? Is the space released or...?
RomsWell said:
It takes 10 minutes to root. And 10 minutes to unroot. Including safe strap. Nothing will trip knox. Beans has the stock nc4 ota rooted deodexed and busy boxed. All is needed to do what you want to do. You will find Zero anything for your stock odex ota. So root safestrap flash the stock rom and add call recording via xposed.... There is no other info you need that isnt already posted in a sticky.
Click to expand...
Click to collapse
And it takes days of research to get to the 10 minutes to make sure what you read is accurate, and will work with your phone. I've read so many stickys, forum posts, blogs, and YouTube videos, that I've lost count. What I've learned is the custom ROM process is far from straightforward.
a. The SuperSU at the PlayStore is from an archeological dig. What I've read so far, I need at least 2.13 for things to work right, 2.16 is current, and 2.19 beta.
b. For the Note 3, just within KitKat 4.4.2 there is NC2, NC3, and NC4. From what I've gathered from a lot of reading and videos is that Safestrap-HLTEVZW-NC2-3.75-B04.apk is the ONLY one that works right with Verizon's NC4.
c. The whole idea of SafeStrap is to preserve the factory slot, and work from another slot. BeansTown106's rooted deodexed ROM, replaces the factory ROM.
d. BeansTown106's rooted deodexed ROM is not an NC4 kernel ROM. "The nc4 stock rom beans has posted isnt patched for the nc4 kernel. "
Thanks!

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

Root Apps and new OP6T...Set up

Hey guys...Been using my Nexus 6 forever and have had root since it went EOL. I have a new OP6T arriving tomorrow from T-Mobile and I can't remember since it's been so long. When I go to set up the new phone and it starts to download settings and apps from the play store, Since the new phone won't have root will it just omit the root apps automatically or will it try to download them also?
Just want to make sure I don't need to uninstall root apps from my Nexus 6 and let it backup before setting up my new OP6T.
Thanks!

I'm pretty sure it will download the root apps too. You can either uninstall once the restore is done or go to the Play Store during restore and stop the root apps from being installed.

Telyx said:
I'm pretty sure it will download the root apps too. You can either uninstall once the restore is done or go to the Play Store during restore and stop the root apps from being installed.
Click to expand...
Click to collapse
Yeah that's what I was thinking...I'll just have to stop the downloads on them. I just want to play around with it before I root...It's so close to stock Android and runs good enough from what I've read that the only reason I would root is for Substatum. So if the dark theme is good enough I may not even need that for now.
Thanks!

Downloading a root app won't root anything anyway. Must be unlocked first and root installed through fastboot

Striatum_bdr said:
Downloading a root app won't root anything anyway. Must be unlocked first and root installed through fastboot
Click to expand...
Click to collapse
Right...I'm aware of that, Just couldn't remember if the apps would download during setup if there was no root. I'll just have to stop them from downloading manually before they do. No need for them to be on the phone until I decide to root.

Jeffro64 said:
Right...I'm aware of that, Just couldn't remember if the apps would download during setup if there was no root. I'll just have to stop them from downloading manually before they do. No need for them to be on the phone until I decide to root.
Click to expand...
Click to collapse
If your 6T is from T-Mobile you have a wait to root it, if you want to.
40-50 days plus it needs to be paid off.
Some people have had luck getting the code earlier. YMMV

tech_head said:
If your 6T is from T-Mobile you have a wait to root it, if you want to.
40-50 days plus it needs to be paid off.
Some people have had luck getting the code earlier. YMMV
Click to expand...
Click to collapse
Yeah I have read that and seen people saying they got away with it as early as the second day of owning it. But I really have no reason to root other than maybe to use substratum at some point in the future or early EOL for updates...But even for either of those I don't think it will be anytime soon.