I am currently running NE3 firmware on my S4 Active. It's rooted via Towelroot. When I opened SuperSU it said something about KNOX detected do I want to disable it? I of course did and clicked yes. It said that it was disabled successfully, however I still see the lovely "Security Policy Updates" notification several times a day. Aside from some bloatware removed I haven't messed with KNOX. I had no problem disabling it on ML2, is there a different method needed for 4.4.2 NE3?
Not sure if this will help but I went into es file explorer and clicked root access then searched for the knox apk and renamed it by adding a 2 after apk so the file will not run.
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
gjrumptz said:
Not sure if this will help but I went into es file explorer and clicked root access then searched for the knox apk and renamed it by adding a 2 after apk so the file will not run.
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
I ran a zip file from a member one here that was supposed to delete all files related to Knox, however I still see "security policy updates" nag message. I used a root file explorer and searched for knox and it's not coming back with any results. Is this Security Policy garbage going to mess the phone's root up? It's nagging me to let it automatically update... which I don't allow anything to update on its own, but this message keeps coming up in my notifications bar...
Related
What you need is a rooted i-537 with safstrap installed.
make sure phone is rooted and you have safstrap installed.
prevent you phone from updating itself as shown in the root guide in this forum.
get a copy of the tethering provisioning apk from a custom rom. One that worked for me is attached to this thread.
put the custom tetherprovisiong apk on an external sim card for access. boot into safestrap and make sure stock rom is selected.
mount filesystem then open up safestaps file explorer and delete tetherprovisioning apd and tetherprovisioning odex from system/apps folder. Confirm that it is deleted.
Now paste the custom tetherprovisioning.apk into the same system/apps folder. Reboot phone into stock, rooted rom and enjoy wifi tether.
You should now be able to turn off and on with the normal method.
My phone: SGH-i537
Android version 4.3
Baseband I537UCUBML2
Rooted W/ Safestrap 3.71 installed
Thanks
RB8720
Can anyone confirm this method works on 4.4.2? I noticed rb8720 is on 4.3
I'm running rooted 4.4.2 and got it to work from this
post
http://forum.xda-developers.com/showthread.php?p=52218894
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Cool! Guess i am off to try. Backup in progress.
That was a no go. Cannot mount system in safestrap recovery.
Don't need to. I renamed all the tethering apks/odex files. Moved the apk in the thread I linked to to system/app using root browser. Changed the permissions to 644 and rebooted.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Could not get it to work. Guess i can wait for a method that works.
One thing I did notice was after I renamed all four tethering apks/index files, moved in the exploited apk and rebooted is I got the "upgrading screen" which one can only assume was my phone picking up on the new apk. Let me know if you have any questions,I banged my head on this for days before I found a working method.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Finaly tried your method and it worked like a charm. Never got the upgrade screen on boot up but it works fine. Thanks!
Replaced provision apk and system still says i need to upgrade my plan removed tether automation and system says no data or incorrect sim, at&t unlocked and running tmo/metro, any ideas?
Hi,
I have the lg optimus l90.
I used the towelroot app to root the phone. i used a terminal app to verify that i do have root. when the app opened, it displayed a $ sign but when i typed "su" and pressed enter it gave me a "#" prompt. so am i rooted?
also i was told to install the superSU app. why do i need this? can't i just uninstall the bloatware right now since i am rooted?
I installed the superSU app but it was not able to install the su binary because i did not reboot the phone after using towelroot. I uninstalled the SuperSU app. anyhow, what do I need to do now to remove those bloatware apps. there is no option to uninstall in the apps section of the android settings application.
finally, I read somewhere that i should use nobloat app to uninstall the bloatware but it is not uninstalling the bloatware. I uninstalled it.
so what do I do now?
any help would be much appreciated.
thanks.
Superuser is needed for apps to have root rights to your phone. Install superuser. Reboot phone and open app. Reboot again if needed. Rooting is useless without superuser installed
Sent from my LG-D410 using Tapatalk
helix3000 said:
Hi,
I have the lg optimus l90.
I used the towelroot app to root the phone. i used a terminal app to verify that i do have root. when the app opened, it displayed a $ sign but when i typed "su" and pressed enter it gave me a "#" prompt. so am i rooted?
also i was told to install the superSU app. why do i need this? can't i just uninstall the bloatware right now since i am rooted?
I installed the superSU app but it was not able to install the su binary because i did not reboot the phone after using towelroot. I uninstalled the SuperSU app. anyhow, what do I need to do now to remove those bloatware apps. there is no option to uninstall in the apps section of the android settings application.
finally, I read somewhere that i should use nobloat app to uninstall the bloatware but it is not uninstalling the bloatware. I uninstalled it.
so what do I do now?
any help would be much appreciated.
thanks.
Click to expand...
Click to collapse
Along with root and SuperSU, you will also need a root App manager or root file manager. I personally prefer to use ES File Explorer as it is both an application manager ( user and system ) as well as an awesome file manager.
There is no list of acceptable system apps to remove. So be very careful as to what you uninstall or you may endup with a soft bricked phone or one that spazzes out whenever it feels like it. I would recommend making backups of any app you want to remove before uninstalling it. At least you might be able to restore them if something goes wrong.
shinobisoft said:
Along with root and SuperSU, you will also need a root App manager or root file manager. I personally prefer to use ES File Explorer as it is both an application manager ( user and system ) as well as an awesome file manager.
There is no list of acceptable system apps to remove. So be very careful as to what you uninstall or you may endup with a soft bricked phone or one that spazzes out whenever it feels like it. I would recommend making backups of any app you want to remove before uninstalling it. At least you might be able to restore them if something goes wrong.
Click to expand...
Click to collapse
thank you both for the replies.
so what exactly is SuperSU for? when I opened it up I saw nothing in the apps list and I did not see anything else in the other lists within the app. also, I did not restart the phone before trying to update the su files and when I did restart the phone nothing updated. So, do I use something like ES file explorer to remove bloatware?
by the way, when I tried to surf the web after installing superSU app, the web browser was extremely slow. the webpages loaded very slowly but when after I uninstalled the superSU app, it was loading the pages fast again as normal. what's up with that?
thanks.
helix3000 said:
thank you both for the replies.
so what exactly is SuperSU for? when I opened it up I saw nothing in the apps list and I did not see anything else in the other lists within the app. also, I did not restart the phone before trying to update the su files and when I did restart the phone nothing updated. So, do I use something like ES file explorer to remove bloatware?
Click to expand...
Click to collapse
SuperSU is a binary executable that grants or denies superuser requests. Without it root is worthless.
You won't see anything in SuperSU permission list until an app asks for superuser permissions. When first opening the SuperSU app you should get prompted to update/install the su binary. Allow that action to happen.
helix3000 said:
by the way, when I tried to surf the web after installing superSU app, the web browser was extremely slow. the webpages loaded very slowly but when after I uninstalled the superSU app, it was loading the pages fast again as normal. what's up with that?
thanks.
Click to expand...
Click to collapse
That's because the su binary was never updated.
shinobisoft said:
SuperSU is a binary executable that grants or denies superuser requests. Without it root is worthless.
Click to expand...
Click to collapse
so in order to run something like the nobloat app I need to grant it permission to be a superuser? I never had to do anything like that when I ran the nobloat app and It actually worked. It still does not make sense to me what supersu is used for.
That's because the su binary was never updated.
Click to expand...
Click to collapse
I ran the towelroot app and it was successful. However, I did not reboot the phone before attempting to update the su binary and the superSU app said i should restart before updating. I restarted the phone but it never updated the su binary when I ran the superSU app again. What do I do now?
thanks.
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Sent from my XT1053 using XDA Free mobile app
kenosis said:
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Yes.
Freezing is just a method of renaming a system app. Unfreezing ALL of them too.
Being unlocked or safe strapped I always backed up my virgin system before making any modds so an update would go with just flashing stock recovery. Hiding root is needed sometimes too.
Thanks for your answer. I will just unfreeze freezed apps once 5.0 is available.
Sent from my XT1053 using XDA Free mobile app
kenosis said:
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Click to expand...
Click to collapse
It depends on how you freeze them.
Every OTA so far has included a pre-flash validation check for the phone. It scans the phone for particular files and parts, for their existence and to make sure their checksum or SHA hash the expected versions BEFORE the OTA will install. Any method that renames, deletes, or otherwise modifies the APK and/or ODEX file for stock apps can cause an OTA install to fail.
If you use the phone's built in App Manager (Settings -> Apps -> open the entry for the app you want, then hit DISABLE, or Uninstall Updates then Disable), you are fine.
If you use something like Titanium Backup to Freeze them, you will likely be ok, but keep in mind that when some past OTA's came out (think 4.2.2 and 4.4), using Titanium to freeze apps did cause the OTA to fail for some people.
Using a root capable file explorer to manually rename, delete, or otherwise modify the APK and/or ODEX file can also cause an OTA install to fail.
This is why you see so many say that "you need to be stock to take an OTA"
aviwdoowks said:
Yes.
Freezing is just a method of renaming a system app. Unfreezing ALL of them too.
Being unlocked or safe strapped I always backed up my virgin system before making any modds so an update would go with just flashing stock recovery. Hiding root is needed sometimes too.
Click to expand...
Click to collapse
If you RENAME a system app that the OTA's Pre-flash validation steps look for, the OTA will fail. So any method of "freezing apps" that involves renaming the APK or ODEX files certainly can cause an OTA install to fail.
But of course, if the APK/ODEX you rename is NOT looked at during pre-flash validation, then the OTA will not fail.
Hi KidJoe, thanks for your explanation. I use Android Tuner and freeze apps such as spotlight, hangout, Google+, Live Wallpaper... I can unfreeze. Is it OK to do like that?
Sent from my XT1053 using XDA Free mobile app
KidJoe said:
It depends on how you freeze them.
Every OTA so far has included a pre-flash validation check for the phone. It scans the phone for particular files and parts, for their existence and to make sure their checksum or SHA hash the expected versions BEFORE the OTA will install. Any method that renames, deletes, or otherwise modifies the APK and/or ODEX file for stock apps can cause an OTA install to fail.
If you use the phone's built in App Manager (Settings -> Apps -> open the entry for the app you want, then hit DISABLE, or Uninstall Updates then Disable), you are fine.
If you use something like Titanium Backup to Freeze them, you will likely be ok, but keep in mind that when some past OTA's came out (think 4.2.2 and 4.4), using Titanium to freeze apps did cause the OTA to fail for some people.
Using a root capable file explorer to manually rename, delete, or otherwise modify the APK and/or ODEX file can also cause an OTA install to fail.
This is why you see so many say that "you need to be stock to take an OTA"
If you RENAME a system app that the OTA's Pre-flash validation steps look for, the OTA will fail. So any method of "freezing apps" that involves renaming the APK or ODEX files certainly can cause an OTA install to fail.
But of course, if the APK/ODEX you rename is NOT looked at during pre-flash validation, then the OTA will not fail.
Click to expand...
Click to collapse
+1
kenosis said:
Hi KidJoe, thanks for your explanation. I use Android Tuner and freeze apps such as spotlight, hangout, Google+, Live Wallpaper... I can unfreeze. Is it OK to do like that?
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't used that app. Best thing to say is take an app that you know what the apk name is, use Android Tuner to freeze it, then use a root capable file explorer to look for the apk. If it's still named correctly and located in the original place on the phone, then you should be ok.
First off I am running lolipop and have been working to find a way to disable bloatware that you don't want. I can't root as I'm on a att s5 lolipop...
finally found out how to get those apps that can't be disabled disabled.
Instructions:
1. Find the app that your wanting to dissable... let's say for example My Magazine.
by default in lolipop this app can't be disabled without root... frown face.. bad day...
2.Search for an apk file online for that app you want to disable.
And install it.
3. Here's what happens now... since you just updated the system app yourself, you now have permissions over it.
So to disable the app go to app manager and look under downloaded. You will notice that now the app that previously could not be disabled... now can be. You also have the option to uninstal the update... update only unfortunately but oh well.
Now you have just succusfully disabled My Magazine or what ever other system app that can't be disabled.
If you need any help just ask.
Update.
I can only currently get this to work for my magazine on 5.0
Possibly a version issue where u have to fine a version newer.
in any case the my magazines I downloaded did install. And afterwards was able to disable
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
farquea said:
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
Click to expand...
Click to collapse
This post was a bit more informative than your "my device unrooted itself" post in the stable thread.
Dirty flash your system or use the file manager in TWRP to remove the offending folder.
I was thinking of trying that but fixed it a different way as I just posted in the SuperSU thread. But in case anyone else ever has this problem...
I fixed my issue. By disabling SuperSU and enabling again from the app settings and it gave me root. I then deleted a created su folder in system/bin that I manually created earlier when trying to get secure settings working.