My HTC One is rooted and I have Adaway and Adfree installed. I generally install both on all of my devices and run them side-by-side, even though it might be redundant/overkill.
On my One, ads will spontaneously stop being blocked. I'll see them in apps all of a sudden or somewhere else. When I open Adaway and tap the update button, the One reboots without prompt. When it comes back up, I'm able to update Adaway and ads are blocked again.Rinse and repeat a few days later. Ad blocking works for a while, then this happens all over again.
I haven't tried removing Adaway yet, but it seems to be the cause of the problem. Has anyone else experienced anything like this? What are you using to block ads on your One?
Yea, I'd say big overkill on the adblocking. I just use Adaway, it works perfect for me.
I would go to both programs and set things as default, uninstall both programs, clear cache and wipe dalvik. Install only one program, update from there and see how things go from there.
Xstop said:
Yea, I'd say big overkill on the adblocking. I just use Adaway, it works perfect for me.
I would go to both programs and set things as default, uninstall both programs, clear cache and wipe dalvik. Install only one program, update from there and see how things go from there.
Click to expand...
Click to collapse
I could accept the fact that using both Adfree and Adaway together was the issue if I didn't have the same exact setup on my Nexus 10, Galaxy S4, Note 2, and Optimus G Pro with no issues whatsoever. I'm only having this issue on the HTC One and the fact that it reboots the phone when I launch Adaway makes me think it has something to do with that program.
I will try removing Adfree and see what happens.
Phone reboots because the stock kernel write protects the system partition and when the app attempts to remount it RW it blows up. There are kernel mods and ROMs that can bypass the write protection.
I explained how to make AdAway work without kernel mod in this thread (you need custom recovery however). Symlinking the hosts file to another partition is the suggestion from AdAway help section
Mantelinho said:
I explained how to make AdAway work without kernel mod in this thread (you need custom recovery however). Symlinking the hosts file to another partition is the suggestion from AdAway help section
Click to expand...
Click to collapse
So Adaway is the issue? What about Adfree? Does it work normally? ABP?
greyhulk said:
So Adaway is the issue? What about Adfree? Does it work normally? ABP?
Click to expand...
Click to collapse
No, they all use the hosts file method to block advertiser hosts. This file is located in the write protected /system partition (at least for S-On devices) and changes are lost after reboot. The symlink method (linking to a writable partition) may also work with Adfree or ABP, however what definitely works is flashing the modified hosts file via recovery. Both methods listed here
Why does HTC have to be so much more difficult than everyone else? First, there's S-Off, something you don't need on Samsung, LG, etc devices, and now this? Love my One, but I hate having to do a workaround for something that works so easily on all of my other devices.
/rant
Related
From what I've seen (e.g., Bloatware Disabler and ViperMod), the bloatware zappers out there are all permanent and thus survive a reboot (unlike the root itself).
I'm one of many that wants the option of a one-click root that is totally temporary but does everything you'd want (overclock, Hulu fix, etc). The missing piece of the puzzle here is a temporary bloat disabler or uninstaller.
Does this kind of mod exist? If so I'd be happy to incorporate it into my existing one-click roots.
I'm guessing that if the changes are non-permanent (i.e., are undone at reboot) then the best we can do is FREEZE and not uninstall the apps, right?
If that's true, I propose two roots: Root 1 strips out all the bloatware, overclocks, roots, etc etc (all the good stuff ). If you want to return to stock, Root 2 will reroot, REINSTALL THE DELETED APPS, then reboot so that you're back to stock in terms of system files.
Going either direction on this will, I think, be a step in the right direction.
(PS: I apologize for my noobishness; however, I've been creating some helpful tools for people recently and I think this is the next step, but some overall guidance first would really help! Please consider my earnestness before flaming! )
THANKS IN ADVANCE
The way pm disable works on apps and packages is permanent. You can do pm uninstall com.htc.taskiller (for example) and it should work, I have never tried it. Im 100% sure it will come back on a reboot, though. With vMBM, you can just enable everything from the Advanced menu in a few seconds. Were you aware of that?
I really like where your headed with this. I did manage to delete a single file and did an install of swype and it seems to be the only thing that sticks after reboot. Think it was the install file from oem.
has to be something to remove to prevent apps from reinstalling them selves.
Btw, after you ad this to your mod script when finished, can you throw in apfree install. Thanx in advanced.
-viperboy- said:
The way pm disable works on apps and packages is permanent. You can do pm uninstall com.htc.taskiller (for example) and it should work, I have never tried it. Im 100% sure it will come back on a reboot, though. With vMBM, you can just enable everything from the Advanced menu in a few seconds. Were you aware of that?
Click to expand...
Click to collapse
So you're saying that Vipermod simply freezes the apps, and they can be re enabled easily from a menu? Do apps stay frozen Thu reboot?
I guess what I'm thinking here is that I want a root that 100% strips out bloated (so I guess uninstall) but which either does NOT persist Thu boot or else can be restored later with one click deeply (i tried to explain this in OP. If I understand vipermod correctly, I think that'd be the second best option (merely freezing apps). Of course, in the preceding I'm assuming that uninstalled is better than frozen, all things being equal.
What do you think?
Sent from my PG86100 using XDA App
knightwolf123 said:
I really like where your headed with this. I did manage to delete a single file and did an install of swype and it seems to be the only thing that sticks after reboot. Think it was the install file from oem.
has to be something to remove to prevent apps from reinstalling them selves.
Btw, after you ad this to your mod script when finished, can you throw in apfree install. Thanx in advanced.
Click to expand...
Click to collapse
Right--my assumption is that with temp root I could go in and delete a **** ton of system files and totally destroy my phone--right?? Basically, to reiterate, BECAUSE WE'RE IN THE WORLD OF TEMP ROOT ANYWAY, AND REQUIRE FREQUENT REROOT, IF I'M GOING TO FREQUENTLY REROOT I MIGHT AS WELL HAVE THE OPTION TO NOT ONLY STRIP OUT BLOATED BUT **ALSO** QUICKLY RETURN TO STOCK (FOR WARRANTY, SERVICE, ETC.) Can you offer some guidance?
As to Adfree, there's no need to add that. I only want my oneclick to do stuff you'd otherwise have to do manually after rooting. This isn't necessary with Adfree--after root just use the fast reboot app and address works fine, no? (or does it NOT work? Angry Birds seems to have LESS ads but isn't totally adfree--I've been assuming it was simply "beating" the adfree app.)
Sent from my PG86100 using XDA App
How about just freezing apps with titanium backup? It sticks with a reboot and only takes a single click per app to freeze/unfreeze.
tapa tapa tapa
Titanium freeze uses the pm disable. Pm disable will stick through reboot. If you want to not have a system app only til reboot, just delete in terminal or with root explorer. And I believe a data/factory reset wipe would restore frozen apps
Sent from my PG86100 using XDA App
panamaniac said:
Right--my assumption is that with temp root I could go in and delete a **** ton of system files and totally destroy my phone--right?? Basically, to reiterate, BECAUSE WE'RE IN THE WORLD OF TEMP ROOT ANYWAY, AND REQUIRE FREQUENT REROOT, IF I'M GOING TO FREQUENTLY REROOT I MIGHT AS WELL HAVE THE OPTION TO NOT ONLY STRIP OUT BLOATED BUT **ALSO** QUICKLY RETURN TO STOCK (FOR WARRANTY, SERVICE, ETC.) Can you offer some guidance?
As to Adfree, there's no need to add that. I only want my oneclick to do stuff you'd otherwise have to do manually after rooting. This isn't necessary with Adfree--after root just use the fast reboot app and address works fine, no? (or does it NOT work? Angry Birds seems to have LESS ads but isn't totally adfree--I've been assuming it was simply "beating" the adfree app.)
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Require frequent reroot... Sorry to hear that. Only happens to me if I let battery run completely out.
Return to stock... Can't you use RUU for that?
Adfree... I've had really mixed luck with.
AS For bloat, I use titanium backup. No problems on my end.
panamaniac said:
So you're saying that Vipermod simply freezes the apps, and they can be re enabled easily from a menu? Do apps stay frozen Thu reboot?
I guess what I'm thinking here is that I want a root that 100% strips out bloated (so I guess uninstall) but which either does NOT persist Thu boot or else can be restored later with one click deeply (i tried to explain this in OP. If I understand vipermod correctly, I think that'd be the second best option (merely freezing apps). Of course, in the preceding I'm assuming that uninstalled is better than frozen, all things being equal.
What do you think?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Correct, it uses the pm disable command on apps. It stays after a reboot but can be easily re-enabled after a reboot.
basically this guy wants a script similar to vipermod that "rm stupid.apk" from the /system/app directory instead of "pm disable" which is very very simple. that way upon reboot it all returns
t3project said:
basically this guy wants a script similar to vipermod that "rm stupid.apk" from the /system/app directory instead of "pm disable" which is very very simple. that way upon reboot it all returns
Click to expand...
Click to collapse
So I guess I'm confused. If i temp root, then go into root explorer and delete all kinds of system files--they'll come back after reboot?
And yes, my root sticks til a true reboot, but not thereafter. Isn't that the case with everyone?
Sent from my PG86100 using XDA App
If you disable the app in titanium or thru adb then the .apk file still is on the phone..but NOT usable or loadable...if you uninstall the app then the file is off the phone...then if you do a reboot....the phone will reinstall the programs you deleted but the disabled apps stay disabled, invisible to the machine but the apk of that program is still on the machine..usually in /SYSTEM/APPS or /DATA/APPS. Ugly but it works like a charm. And from what I read...it is for everybody....hope this answers your question.
panamaniac said:
So I guess I'm confused. If i temp root, then go into root explorer and delete all kinds of system files--they'll come back after reboot?
And yes, my root sticks til a true reboot, but not thereafter. Isn't that the case with everyone?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
As said above yes they will come back. You have no write access to system. So although you think you are deleting them, you are not. You are only "deleting" them from cache. Disabling them, actually writes to an xml file in the data directory (which apps have access to). If you have fast boot turned on, you are not truly "rebooting" and that's why root stays.
Hi All,
i have an issue - i installed custom ROM, custom kernel, all is working except root.
I have two root apps - superuser (standard) and one from ROM supersu. One came with ROM, and i flashed another (standard) just after flash (not sure why really)
So - I have two supersusers - bot don't have root... irony
Any suggestion how to fix that? Also, how should i delete superuser (standard) from system/app folder (without root apparently)?
Thanks all!
"This app cannot be uninstalled if it was installed with your ROM or root. If there is no uninstall option, it's because you placed it in /system/app, not me. It is impossible for an app to be installed in /system/app by the Play store. In fact, the entire /system partition is read only at runtime. The only way for an app to be placed in /system/app is via a rooting process (which usually installs Superuser), or by remounting the system partition as read/write and manually putting it there."
this is from the play store page. I guess you could try using root explorer to delete it but don't know if it will work
The more important question is why don't you have root? You have two root apps installed on a custom ROM. You should be able to run SuperSU and let it update the su binary. Then you can use ROM Toolbox or TB to remove Superuser.
Posted using Tapatalk 2
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Jsparta26 said:
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Click to expand...
Click to collapse
That's already been suggested in the ROM thread on another site, but he seems to be trying to get around it without reinstalling the ROM. He said over there that he doesn't know why he installed SuperUser since the ROM came with another su app and neither do I. He should just go ahead and reflash the ROM.
For some reason this guy seems to want to do things differently from standard practices and then ask for help when it doesn't work. His latest post in the other thread was asking if he could flash the ROM after removing the kernel (boot.img)!
I'm not sure where he comes up with these ideas but he seems to be off doing his own thing even though he is new at this stuff. I'm not suggesting that you don't help him, but wanted you to be aware that he may be creating problems for himself.
ramjet73
Thanks for the heads up. Your right, it don't make sense to try something different if what we suggest to somebody has been a better and usually a full proof way of fixing a problem. But like you said if he wants to add to his own problems that's on him. Let's make this clear to him too since he is new. Nobody on this site or other sites are responsible if you blow up your device, your gf leaves you, or you burn down your house and get fired. :highfive:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
goja said:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
Click to expand...
Click to collapse
Set it to automatically grant permissions and turn notifications off, but remember that this is very insecure way so don't install any untrusted apps.
I've thought of that, but i'm not sure it would help : If it waits, let's say 2minutes, for showing pop-up asking for rights, then it would also wait 2minutes before automatically allowing apps...
2 minutes?? It should show immediately, so there is something wrong in your rom. Try to wipe cache and dalvik cache and fix permissions.
Man, this is not in MY ROM, this is in ANY roms... Seems that the more apps installed (=the more process running) the slower it'll be!
I agree. I have the same problem. I'm running CM13 (Marshmallow) on my old S3 i9300, and I flashed SuperSu (beta) for it. It work well, but its slow to grant permissions even when its meant to do so automatically. I've set it to start at boot, but this hasnt done much. Any fixes??
Same problem also here with every rom that I used it. Root in cm roms is almost instant.
same here on a custom cm12.1 rom
What the heck are you guys talking about? 2 minutes?! That is just plain wrong. I won't say impossible, cause you obviously have problems, but I have never seen that behavior you're talking about, and that is absolutely not caused by SuperSU or Superuser. Even my 7 years old HTC HD2 asks for, or grants root in 2 seconds max. Tell your developers to fix their ROMs.
Sent from my HTC One M9 using Tapatalk
Can it be that "Clean Master" or some other memory management software is pushing SuperSU back. Try uninstalling any memory management software.
never had issue having to wait for 2min either and ive rooted almost 50 diffrent phone from ics to lollipop to my current headache oppo mirror 5 still superSU still doing its job
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum¡*
Ur thread will b moved immediately.
BatDroid said:
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum�?�¡*
Ur thread will b moved immediately.
Click to expand...
Click to collapse
â?¦
I don't even know how to process this ?¦ try my way first¦
I'd bet anything the speed will be just as fast¦ and i forgot to mention, i always enable full logging? so full logging, no lag?vs no nothing, no app, security etc
loogielv said:
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
Click to expand...
Click to collapse
As he said i have dissabled notifications and worked, Thanks Man
I've had this problem on a Samsung Galaxy J7 (2016). It was because I disabled the encryption of /data. For details on how to solve it see here. I think there are probably other factors that can cause this, so this solution is probably not for everyone. But I would recommend checking your adb logcat to figure out if something is going on in the background that should not.
Since I installed SuperSu 2.79 on my klte on RR (los, android 7.1.1) the device started lagging, not a lot but enough to be annoying.
First off thanks for stopping and seeing if you could help with my problem.
I used towelroot to gain root and tweak stock on sprint note 3, which worked perfectly. After installing busybox, supersu, and Xposed installer I went about reclaiming my phone from bloatware and limptard features. At one point I searched what apks were safe to remove from TW based roms, one that wasnt specified in the list was rakein.apk which I ASSUMED (<-- the whole reason for the headache...not confirming its true function) was part of scrapbook due to its icon....nope it controlled pen window.
I need to find a way to reinstall rakein.apk to system/app without it being cleared upon reboot.
Steps attemped so far:
Restored through original backup method-failed
Manually placed apk in system/app, corrected permissions to rwrr-failed
^ that plus mounted system r/w then unmounting partition for reboot-failed
Sideload-failed
---------------
Havent seen anything other fixes except a fresh flash from sammy.
Theres nothing changed on my sprint note 3 except for xposed and active modules all of which ive scoured for possible solution.
Sadly I didnt have a current sys backup either.
Thanks again for everyones help.
Have a good day.
You can always Odin back to stock and reroot. If everything else fails.
Jataadroid said:
First off thanks for stopping and seeing if you could help with my problem.
I used towelroot to gain root and tweak stock on sprint note 3, which worked perfectly. After installing busybox, supersu, and Xposed installer I went about reclaiming my phone from bloatware and limptard features. At one point I searched what apks were safe to remove from TW based roms, one that wasnt specified in the list was rakein.apk which I ASSUMED (<-- the whole reason for the headache...not confirming its true function) was part of scrapbook due to its icon....nope it controlled pen window.
I need to find a way to reinstall rakein.apk to system/app without it being cleared upon reboot.
Steps attemped so far:
Restored through original backup method-failed
Manually placed apk in system/app, corrected permissions to rwrr-failed
^ that plus mounted system r/w then unmounting partition for reboot-failed
Sideload-failed
---------------
Havent seen anything other fixes except a fresh flash from sammy.
Theres nothing changed on my sprint note 3 except for xposed and active modules all of which ive scoured for possible solution.
Sadly I didnt have a current sys backup either.
Thanks again for everyones help.
Have a good day.
Click to expand...
Click to collapse
Ya... I was just hoping there was a reason for not being able to just restore it but I guess I broke it lol. Thanks
Sent from my SM-N900P using XDA Premium 4 mobile app
I have not used touch wiz for a while but what does pen window do? I use Tasker to pop an application menu and change keyboards when I detach the S-Pen. I am using SlimRom also.
Sent from my SM-N900P using XDA Premium 4 mobile app
It is just Samsungs version of a floating app windows. Adjustable by drawing the desired dimensions with the s pen. Multiples of the same windows. Rooted and equipped with aean developed app, all apps are pen window compatible.
Maybe you missed the odex?
Remove .apk extension from odex file. added it only cause of xda file type filter.
Check out this post
http://forum.xda-developers.com/note-4-att/general/supersu-please-t3110954
I tried it and got temporary root on my Verizon Note Edge. I know it is temporary but at least it is root.
I do not have the developer version btw..
Did you use the Note 4 .img file?
sbrownla said:
Did you use the Note 4 .img file?
Click to expand...
Click to collapse
I just followed the video that is posted in the OP and that gave me temporary root. I didn't use any .img files.
DV8 said:
I just followed the video that is posted in the OP and that gave me temporary root. I didn't use any .img files.
Click to expand...
Click to collapse
Doesn't it say to use one of the downloadable boot img files from the linked site? It's a boot.img file.
Also what sorts of things have you tried so far with it?
sbrownla said:
Doesn't it say to use one of the downloadable boot img files from the linked site? It's a boot.img file.
Also what sorts of things have you tried so far with it?
Click to expand...
Click to collapse
I have tried Root Explorer and it allows me to read and write to the SD card. I have Root Call blocker and that works as well, I have tried Xposed Framework and so far no go, it does a reboot and you will lose root. This is still a work in progress but it looks a lot more promising than a couple of months ago.
I did not use any img files due to mine being a note edge and I think those files are for those who have taken the lollipop upgrade on their Note 4's. Since we have not received the lollipop upgrade to our edge's yet you should be good to at least temporary root because it is only working on KitKat.
I was able to temp root with king root 4.0.1 apk ... and was able to remove bloatware files from: system/app and: system/priv-app but after reboot they are all back.
Update.... after temp rooting. . Install Titanium Backup and Freeze system apps will enable you to "turn off" apps that you otherwise wouldn't be able to disable through the stock app manager in settings menu.
See screenshot below. ...
Screenshot
Screenshot of TouchWiz disabled because I use a different Home Launcher. And YES it keeps disabled through a reboot.
Was able to turn off The KNOX apps as well... seems to keep root longer without rebooting. HOWEVER root doesn't last forever.. meaning apps like Titanium Backup will lose root... and you will have to reboot and run King root again to get temp root to freeze more apps etc.
This is still a work in progress, hopefully the losing root problem will be fixed soon.
This is nice but after messing with it all week I gave up. I could easily get temp.root and get SU installed but you lose root after about an hour even if you touch nothing. You will also get random reboots a lot and then have to start over.
Mike02z said:
This is nice but after messing with it all week I gave up. I could easily get temp.root and get SU installed but you lose root after about an hour even if you touch nothing. You will also get random reboots a lot and then have to start over.
Click to expand...
Click to collapse
If you install Titanium Backup and "freeze" all the Knox apps [see post 7, 8, & 9] you can keep root long enough to freeze all unwanted bloatware. That way you can at least "turn off" [disable] those apps from running in background etc. It's something more then we had.
Keep at it guys! I'll join when I get some time tomorrow and Monday
justjayhere said:
If you install Titanium Backup and "freeze" all the Knox apps [see post 7, 8, & 9] you can keep root long enough to freeze all unwanted bloatware. That way you can at least "turn off" [disable] those apps from running in background etc. It's something more then we had.
Click to expand...
Click to collapse
Yup, this worked. All week I was trying to "remove" these applications via tibu but yesterday I just froze them. I still lost root but see everything I froze is still listed as "Turned off" in Application manager. That will do for now, Thanks!
when you temp root, use TiBu to "convert to user app" this should move all the files to the user apps directory instead of system apps then try to uninstall and see if they come back after reboot. Just a hunch but I can't try since I don't have the retail version.
NekoShinigami said:
when you temp root, use TiBu to "convert to user app" this should move all the files to the user apps directory instead of system apps then try to uninstall and see if they come back after reboot. Just a hunch but I can't try since I don't have the retail version.
Click to expand...
Click to collapse
I do not see the option in Titanium Backup to ”convert to user app" .. Am I missing something?
justjayhere said:
I do not see the option in Titanium Backup to ”convert to user app" .. Am I missing something?
Click to expand...
Click to collapse
You need to long press on the app. Towards the end of the setting that popup you should see the convert to user app setting.
Easiest way I found was to freeze all the apps you don't want, filter for frozen apps then go through the list converting them to user apps
Edit: this doesn't work. They will install themselves back after doing this.
I figured they would come back.. freezing app is as good as it gets for now.
long press or swipe right to get to the additional options. also thank you guys for confirming that for me. i wasnt for sure since I dont have the retail version to test out on.
also i think i remember reading in the note 4 forum that they were able to get it perma deleted by uninstalling all updates then uninstalling the app or something along those lines. I will go back and read it again to be sure of what i read, i may have misread.
I used this method to disable knox and bloatware on my Verizon Edge even without root: http://forum.xda-developers.com/note-4-verizon/general/disable-knox-ota-root-t2972263
As far as temp root is concerned using King root, I suppose while on a rooted state, one can make changes to the system such as:
1) Enabling 3rd party apps like ES File Explorer to write to SD card by modifying platform.xml as described here: http://forum.xda-developers.com/showthread.php?t=2524277
2) Enabling hidden menu (if this is important to you) by modifying /efs/carrier/HiddenMenu file.
Even if you lose root, the changes you made to these files should stick, correct?