{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a simple app that will disable KNOX notifications in the statusbar. KNOX notifications will remain disabled until you flash a new ROM.
Requirements:
* A rooted Samsung device
Click to expand...
Click to collapse
Supported Devices:
* Samsung Galaxy Note 3
* Samsung Galaxy S4 (on new software that has KNOX)
* Probably any other Samsung device that comes out/gets updated with KNOX
Click to expand...
Click to collapse
Changelog:
v1.0.1 - Removed enable option, please see why here
v1.0 - Initial release
Click to expand...
Click to collapse
Play Store link: https://play.google.com/store/apps/details?id=com.viper.knoxdisablerfree
Reserved
Play store link is dead.
SOON TO BE TWEAKED NOTE 3
BACARDILIMON said:
Play store link is dead.
SOON TO BE TWEAKED NOTE 3
Click to expand...
Click to collapse
It takes a few hours before it goes live in the Play Store, but I attached the apk to the first post.
Updated the app to v1.0.1 and I removed the ability to enable KNOX notifications (not that many people would want to anyway). I did this because I was testing my own app, toggling disable and enable a ton of times and when I rebooted next, the phone wouldn't boot. Now, my next reboot was caused by me issuing an "adb reboot nvflash" to make the phone backup it's EFS and it seemed successful. Since I can't identify if it was the adb command that caused it or the enable button that caused it, I'm doing this as a preventative measure for now.
When I enabled KNOX, it gave me a message telling me I should reboot as a security measure due to an app (something like that) and I assume it's because it knew an app turned off KNOX at some point. I ignored it, maybe that was the cause, I'm not sure. My phone is soft bricked at this point, and I tried everything - using the .pit file posted by Garwynn for the Sprint version in combination with a stock tar flash numerous times with and without the Nand Erase All option checked (I tried this based on this guide, obviously didn't use any of the Verizon files), data/cache wipes in recovery - nothing. Nothing will allow the phone to boot, it always comes up and says "Process system is not responding" and then reboots itself, Bootloader says the current binary is Samsung Official but system status is custom, Odin can't even change that.
While I'm sure it's nothing to worry about, I just don't want this to potentially happen to anyone else.
do we have to run this at every boot? or is this a permanent setting?
thanks
sunwee said:
do we have to run this at every boot? or is this a permanent setting?
thanks
Click to expand...
Click to collapse
I'll add this to OP: permanent, in the sense that it will stay disabled until you flash a new ROM
uhm, used it but wanted to have back the notifications, now I can't
kersh said:
uhm, used it but wanted to have back the notifications, now I can't
Click to expand...
Click to collapse
Open terminal emulator, do this:
1) type "su" (lowercase, no quotes), hit Enter
2) Grant root access by hitting Allow
3) type "pm enable com.sec.knox.seandroid" (lowercase, no quotes), hit Enter
You will probably get a notification recommending that you reboot (it's KNOX that tells you this) and I would highly advise that you do that.
EDIT: You can also use v1.0 apk that is still in the first post, it does the same thing. It seems that the issue I had with my phone not rebooting was related to me doing an adb reboot nvbackup, but I want to confirm that when I get a new phone tomorrow before re-enabling the enable option in the app.
Works on Note 2 too
Hi,
I just want to tell you that this app works on Note 2, JB 4.3.
Thank you mate.
rooted, but no root access
Didn't work for my rooted Note 3 (was first on stock ROM rooted with Chainfires CF-Autoroot, then I flashed the Knox-free prerooted Close-to-stock Rom).
I have SuperSU installed, some root applications do work, but I got a problem with LBE security master and with Paragon NTFS&HFS+ and similar apps like NTFSmount.
Hoping that I can get rid of these apps being stopped (or in case of LBE my Note 3 just freezes) with the Knox Disabler, I tried it, but though I allowed SuperSU to give permissions, I got the attached message.
I guess that the reason for all these issues is a similar one, but I have absolutely no idea what to do. Any help is highly appreciated.
(There is also this thread about it. Since I guess it is a related issue I'll post a link: http://forum.xda-developers.com/showthread.php?p=46405351)
Hi,
I have the same problem then above, on the N9005 with X-Note v2 rom..
Paolo
-viperboy- said:
Updated the app to v1.0.1 and I removed the ability to enable KNOX notifications (not that many people would want to anyway). I did this because I was testing my own app, toggling disable and enable a ton of times and when I rebooted next, the phone wouldn't boot. Now, my next reboot was caused by me issuing an "adb reboot nvflash" to make the phone backup it's EFS and it seemed successful. Since I can't identify if it was the adb command that caused it or the enable button that caused it, I'm doing this as a preventative measure for now.
When I enabled KNOX, it gave me a message telling me I should reboot as a security measure due to an app (something like that) and I assume it's because it knew an app turned off KNOX at some point. I ignored it, maybe that was the cause, I'm not sure. My phone is soft bricked at this point, and I tried everything - using the .pit file posted by Garwynn for the Sprint version in combination with a stock tar flash numerous times with and without the Nand Erase All option checked (I tried this based on this guide, obviously didn't use any of the Verizon files), data/cache wipes in recovery - nothing. Nothing will allow the phone to boot, it always comes up and says "Process system is not responding" and then reboots itself, Bootloader says the current binary is Samsung Official but system status is custom, Odin can't even change that.
While I'm sure it's nothing to worry about, I just don't want this to potentially happen to anyone else.
Click to expand...
Click to collapse
Hi do you have a solution yet as i faced the same situation as you...any help will be appreciated
marcus70 said:
Hi do you have a solution yet as i faced the same situation as you...any help will be appreciated
Click to expand...
Click to collapse
For interim solution did you try disabling knox notification by using terminal emulator command? Its available in one of the threads
Sent from [email protected] Ass Note III SM-N9005
steff_1964 said:
Didn't work for my rooted Note 3 (was first on stock ROM rooted with Chainfires CF-Autoroot, then I flashed the Knox-free prerooted Close-to-stock Rom).
I have SuperSU installed, some root applications do work, but I got a problem with LBE security master and with Paragon NTFS&HFS+ and similar apps like NTFSmount.
Hoping that I can get rid of these apps being stopped (or in case of LBE my Note 3 just freezes) with the Knox Disabler, I tried it, but though I allowed SuperSU to give permissions, I got the attached message.
I guess that the reason for all these issues is a similar one, but I have absolutely no idea what to do. Any help is highly appreciated.
(There is also this thread about it. Since I guess it is a related issue I'll post a link: http://forum.xda-developers.com/showthread.php?p=46405351)
Click to expand...
Click to collapse
pvezzoli said:
Hi,
I have the same problem then above, on the N9005 with X-Note v2 rom..
Paolo
Click to expand...
Click to collapse
Did you follow the suggestions the screen told you?
marcus70 said:
Hi do you have a solution yet as i faced the same situation as you...any help will be appreciated
Click to expand...
Click to collapse
Had to replace the phone, unfortunately.
Sent from my Nexus 7 using Tapatalk 4
-viperboy- said:
Did you follow the suggestions the screen told you?
Click to expand...
Click to collapse
@ -viperboy-: First of all many thanks for your work!
Which suggestions you're speaking about? I granted SuperSU root access for Knox Disabler, and double checked that in the SuperSU settings.
When I start Knox Disabler, I get a small message on the lower screen area, that Knox Disabler got Superuser permissions. Then it takes 2 or 3 seconds, and I get the "Root Access Fail!" message.
I did only try the Knox Disabler so far with the pre-rooted Knox-free "Stock"-Rom, not with original Stock Rom rooted with Chainfires AutoCF-Method. And with this Knox-free Rom I do NOT get any Knox-message, but the behaviour of some apps like LBE or Paragon NTFS&HFS+ is exactly the same as with the rooted original Rom. Just without the "Prevention Information" window.
Should I flash the stock rom again? I think then I have to root again, since Mobile Odin doesn't work so far on the Note 3?
Best regards!
Hi Viper,
I have installed Terminal emulator, I did what you say on the link before, but at the end is steel not working..
Paolo
-viperboy- said:
Did you follow the suggestions the screen told you?
Had to replace the phone, unfortunately.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
thks for the fast response...guess no choice will go to the service centre tmr
it says "success" but the notifications are still there
any idea ?
Mohammed-noor said:
it says "success" but the notifications are still there
any idea ?
Click to expand...
Click to collapse
Which variant?
Related
I'm using a CM11 ROM, and Superuser is giving me problems - throws up errors now & again. I like and want to use SuperSU, but Superuser is integrated into the ROM.
How can I get rid of Superuser and replace with SuperSU (preferably just using my phone, no ADB).
setspeed said:
I'm using a CM11 ROM, and Superuser is giving me problems - throws up errors now & again. I like and want to use SuperSU, but Superuser is integrated into the ROM.
How can I get rid of Superuser and replace with SuperSU (preferably just using my phone, no ADB).
Click to expand...
Click to collapse
in the integrated superuser menu(can be found in device settings), if you open settings, you have the option of giving superuser access to "disabled" (by default it is apps only).
after disabling you just have to flash the supersu zip file(can be found on the supersu xda forum) via recovery mode. and you're done.
I flash the superSU.zip after flashing CM11 and Gapps so superSU is the main root app. Never had an issue.
Please keep it friendly and there is no need for name calling of any kind. We tend not to like people resurrecting old threads, but seen as this came in handy for someone there's no harm done.
Thread cleaned.
wedgess said:
Please keep it friendly and there is no need for name calling of any kind. We tend not to like people resurrecting old threads, but seen as this came in handy for someone there's no harm done.
Thread cleaned.
Click to expand...
Click to collapse
Thank you, mod. Wasn't trying to cause any problems, just trying to help a new member.
rdx93 said:
in the integrated superuser menu(can be found in device settings), if you open settings, you have the option of giving superuser access to "disabled" (by default it is apps only).
after disabling you just have to flash the supersu zip file(can be found on the supersu xda forum) via recovery mode. and you're done.
Click to expand...
Click to collapse
i'm having some problems in cm11 with superuser too so i took your advice and disabled it and flashed the supersu.zip but still no root and then i went back to enable it again under settings but now the superuser option is gone.
how do i fix this?
Just make clean flash of CM, then get SuperSU via store
JimZiii said:
i'm having some problems in cm11 with superuser too so i took your advice and disabled it and flashed the supersu.zip but still no root and then i went back to enable it again under settings but now the superuser option is gone.
how do i fix this?
Click to expand...
Click to collapse
In the SuperSU settings, there is a setting called something like "Respect Cyanogenmod Settings". Uncheck that.
Thnx alot! Works great! Now i just have to change that stupid google dialer that's in cm11
Sent from my GT-I9300 using Tapatalk
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Towel Pie Root is a one click untethered app to root the Moto X, Moto G and the Droid Series(maybe others but these for sure) running 4.4.3 and below. It does NOT and WILL NOT root 4.4.4 so stop asking about it!
I want to started off by Thanking Geohot for Towelroot and JCase for Pie root, without them this wouldn't have been possible and I take NO credit for their exploits. If either of them doesn't want this posted they may contact me and I will gladly remove it.
Towel Pie Root combines Towelroot's futex exploit with a modified version of Pie root's xbin.img mount into one app. To achieve a one click untethered root for write protected devices! This DOES NOT remove write protection, and is still technically a temp root, I did include the option to enable root on boot. Which will re-root your device every time you reboot your phone, it also includes the option to perform a full reboot, or a soft reboot from within the app.
Here is a more technical description of what my app does. It includes TR's libexploit.so(aka the native exploit by Geohot) which I use to gain root privileges. Once it has root privileges it then echo's the file path to my modified Pie root file to uevent_helper. It then causes a hotplug event to trigger the kernel to execute the file path just echoed to uevent_helper. My modified Pie root files, kill TR's daemonsu and mounts Pie root's xbin.img over /system/xbin. Then it copies the newer version of SuperSU's su binary and executes the new daemonsu daemon and viola root
If you enjoyed my app, please donate to Geohot at https://towelroot.com/, and JCase at [email protected]ninglogic.com! I do not want any donations, I set out to develop this app purely as a challenge to broaden my development skills not to get a donation.
Installation Instructions: You need to have unknown sources checked in Settings>>Security, and if you have Towelroot installed uninstall it. In order to use TR's exploit I had to name the app's package name to the same name as TR's package name, so you will have to uninstall TR to install my app. Also if you are currently rooted with Pie root please reboot before running my app, to clear Pie's su daemon, and to unmount Pie's xbin.img. Then just click Make it ra1n on Moto, and wait for it to say Root Acheived Enjoy! If you encounter any issues please uninstall v1.0 then re-install v1.1.
Download link:
Version 1.2 for 4.4.2 devices
Version 1.2 for 4.4.3 devices
Version 1.1
Version 1.0
Known Issues: If after running it says Failed to Achieve Root, close the app and clear it from most recent's then reopen the app.
Screen Recording: https://www.youtube.com/watch?v=f6fXs3VJQHg (I will try to update this video with the full installation steps)
Changelog
-v1.2 10/5/2014
---Created a new bin.img from the tmo 4.4.3 sbf to fix the wifi issues
---Changed the modstring for the XT1032 hopefully it works now if it doesn't then there isn't anything else I can do
---Redid the device check to not allow unsupported devices to run the app
-v1.1 9/22/2014
---Added Moto G support, if I missed a model number let me know
---Fixed the issue with Xposed not working by mounting a bin.img over /system/bin
---Added in the ability to Uninstall the app and all files
---Added in various checks and prompts
Additional Thanks:
Verttex(Dier325) - for being my main tester and testing the numerous test apk's I sent him
jpond83 - for testing
mohlsen8 - for testing on the Moto G
NipplesOfTheFuture - for testing, some workflow ideas, and for convincing me to try and get the bin.img method working correctly
iKrYpToNiTe said:
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Towel Pie Root is a one click untethered app to root Motorola devices running 4.4.2 maybe 4.4.3 and below.
I want to started off by Thanking Geohot for Towelroot and JCase for Pie root, without them this wouldn't have been possible and I take NO credit for their exploits. If either of them doesn't want this posted they may contact me and I will gladly remove it.
Towel Pie Root combines Towelroot's futex exploit with a modified version of Pie root's xbin.img mount into one app. To achieve a one click untethered root for write protected devices! This DOES NOT remove write protection, and is still technically a temp root, I did include the option to enable root on boot. Which will re-root your device every time you reboot your phone, it also includes the option to perform a full reboot, or a soft reboot from within the app.
Here is a more technical description of what my app does. It includes TR's libexploit.so(aka the native exploit by Geohot) which I use to gain root privileges. Once it has root privileges it then echo's the file path to my modified Pie root file to uevent_helper. It then causes a hotplug event to trigger the kernel to execute the file path just echoed to uevent_helper. My modified Pie root files, kill TR's daemonsu and mounts Pie root's xbin.img over /system/xbin. Then it copies the newer version of SuperSU's su binary and executes the new daemonsu daemon and viola root
If you enjoyed my app, please donate to Geohot at https://towelroot.com/, and JCase at [email protected]! I do not want any donations, I set out to develop this app purely as a challenge to broaden my development skills not to get a donation.
Installation Instructions: You need to have unknown sources checked in Settings>>Security, and if you have Towelroot installed uninstall it. In order to use TR's exploit I had to name the app's package name to the same name as TR's package name, so you will have to uninstall TR to install my app. Then just click Make it ra!n on Moto, and wait for it to say Root Acheived Enjoy!
Download link: http://www.androidfilehost.com/?fid=23578570567716728
Screen Recording: https://www.youtube.com/watch?v=f6fXs3VJQHg
Click to expand...
Click to collapse
Thank you Sir, and Jcase and geohot... now the big question... I just factory reset 4.4.2 and rooted Pie.. installed your entitlement hack.. worked dandy... than I tried the tr... and guess what..... your app no longer works.. so, do I need to do another factory reset and install this new towelpie app or will your entitlement hack not work with this either? Or should I be the test pilot and find out myself...
doitinthedirt said:
Thank you Sir, and Jcase and geohot... now the big question... I just factory reset 4.4.2 and rooted Pie.. installed your entitlement hack.. worked dandy... than I tried the tr... and guess what..... your app no longer works.. so, do I need to do another factory reset and install this new towelpie app or will your entitlement hack not work with this either? Or should I be the test pilot and find out myself...
Click to expand...
Click to collapse
No need to factory reset. Just make sure you uninstall the towelroot app.
Then install this Towel-root-pie app. JUST this app. Run it, you should be good from there.
iKrYpToNiTe, I know you don't want creditz, but this is also such a helpful and much appreciated tool. I do want to thank you for sharing it with us.
My thanks go out to jcase and geohotz as well. A smörgåsbord of thanks to all of you!!
tapa'd on my moto x
Not good, I can't get it to stop rebooting. 4.4.3 moto g. Selected root on reboot, and now it reboots over and over.
Edit: Factory reset my phone through recovery using instructions at https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
I'm at least back where I started from.
Sent from my Nexus 7 using Tapatalk
side note, don't try it on the moto G. I'm stuck in a bootloop.
edit: was going to try and uninstall the app before it reboots but so far no good.. might have to factory reset
edit2: apparently I'm not fast enough to hit okay for the uninstall.
edit3: YES! I win. I uninstalled faster than towelpieroot could trigger the reboot! whew... took like 20 tries...
For future reference, you can (attempt to) uninstall using adb. It takes a bit more knowledge, but it's simpler.
adb uninstall (package)
tapa'd on my moto x
chrisp6825 said:
For future reference, you can (attempt to) uninstall using adb. It takes a bit more knowledge, but it's simpler.
adb uninstall (package)
tapa'd on my moto x
Click to expand...
Click to collapse
I tried! I couldn't get to ADB while in fastboot. How would I get into ADB Shell if I can't get into anything outside of recovery?
chrisp6825 said:
No need to factory reset. Just make sure you uninstall the towelroot app.
Then install this Towel-root-pie app. JUST this app. Run it, you should be good from there.
iKrYpToNiTe, I know you don't want creditz, but this is also such a helpful and much appreciated tool. I do want to thank you for sharing it with us.
My thanks go out to jcase and geohotz as well. A smörgåsbord of thanks to all of you!!
tapa'd on my moto x
Click to expand...
Click to collapse
Worked perfect! thanks!
So I was already Pied... Pie files already pushed to phone prior to running trpie app.. does this app do the pushing or do we still need to run Pie on its own to push the files?
doitinthedirt said:
Worked perfect! thanks!
So I was already Pied... Pie files already pushed to phone prior to running trpie app.. does this app do the pushing or do we still need to run Pie on its own to push the files?
Click to expand...
Click to collapse
According to the message the OP sent me, PIE is no longer necessary - at all. He advised me that you can run this app on a bone-stock Moto X that has never had PIE used on it.
Have fun guys, AND HIT THE "THANKS" BUTTON TO THE OP!!!!!!
tronmech said:
Not good, I can't get it to stop rebooting. 4.4.3 moto g. Selected root on reboot, and now it reboots over and over.
Edit: Factory reset my phone through recovery using instructions at https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
I'm at least back where I started from.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
windraver said:
side note, don't try it on the moto G. I'm stuck in a bootloop.
edit: was going to try and uninstall the app before it reboots but so far no good.. might have to factory reset
edit2: apparently I'm not fast enough to hit okay for the uninstall.
edit3: YES! I win. I uninstalled faster than towelpieroot could trigger the reboot! whew... took like 20 tries...
Click to expand...
Click to collapse
I'm sorry it caused bootloops for you, I remove 4.4.3 from the OP so others don't try.
iKrYpToNiTe said:
I'm sorry it caused bootloops for you, I remove 4.4.3 from the OP so others don't try.
Click to expand...
Click to collapse
I --really-- can't believe this isn't getting more attention than this!!! Not to mention more "THANKS" for the OP?!?!
Guys, if you use this method, SHOW SOME APPRECIATION! Five-Hundred-Seven (507) views, as of this posting, and only 7 "THANKS"? Where's the other 500?
EXCELLENT Job, Sir.
I have been having issues using this method. I was already using Pie for several weeks and wanted to try this to survive reboots. As soon as I installed and ran it I actually lost the root that I already had. The Towel Pie Root app would say that I had root access but none of my other apps would agree. I would get the message at the bottom of the screen stating the app was granted super user permissions but then the app would tell me that i don't have root, I tried adaway, xposed, and root checker. I uninstalled SuperSU and switched over to the ClockworkMod SuperUser and that worked for root. The problem that I had after that is that the root apps that I was using no longer work. Adaway shows as disabled and when I try to enable it it fails. The same whit xposed, every time I try to update/install it fails. I removed Towel Pie Root and went back to rooting with Pie and I am getting the same results. Has the Towel Root portion of this changed something that I am now going to have to factory reset?
Edit:
After a few more reboots once TowelPieRoot was removed and starting Pie again from the beginning I now have root as it was with everything working. For now I am just going to keep things the way they were. I have my terminal emulator setup to run the last Pie command on every start so it always attempts to root first. This makes it really easy regain root even if my device does get restarted and I lose root..
wow thanks, will this work with Xposed framework? I was looking for a simple root method without voiding my warranty, this seems nice, I'm gonna try it, thank yoU!
I like the app.. seems to work great.. but the only issue I have is is the OTA going to be stopped from downloading? I have two moto x, one still on 4.4 and rooted with slap, and a new one on 4.4.2 rooted with this app. below is a shot of what I get when i force check an update with the slapped moto, this is with the 3c_OTA files renamed to .bak
I dont get the same message with the new moto on 4.4.2, what I get is "your moto is up to date" and the same two 3c_OTA files are also renamed to .bak files.
xposed works with gravity
yabbandroid said:
wow thanks, will this work with Xposed framework? I was looking for a simple root method without voiding my warranty, this seems nice, I'm gonna try it, thank yoU!
Click to expand...
Click to collapse
yes, it works. have it running now. make sure that you softboot from within xposed.
i realize this is my first post here, finally decided to sign up ONLY for the reason to thank the OP for this.
I've been frustrated trying to get towel to work come to find out that geohot sold out and replaced the .apk on the site, wow........ then you had something secret for us and it was this thread and release of towelpie, GREAT work and goodjob!
xt1058 worked in 4.4.3!
most excellent!!!!!!!!
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
can someone tell me or point me in the direction of how to get the exposed modules up and running. i use this towel root, then open exposed framework installer and hit install/update and get a pop up with some info where the last line says "failed to create a backup or /system/bin/app_process" i hit ok and there is still red dashes under active columns for both App_process and XposedBridge.jar? am i missing a step? the towel root app says "root achieved enjoy" when i use it.
yamaha83 said:
most excellent!!!!!!!!
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
can someone tell me or point me in the direction of how to get the exposed modules up and running. i use this towel root, then open exposed framework installer and hit install/update and get a pop up with some info where the last line says "failed to create a backup or /system/bin/app_process" i hit ok and there is still red dashes under active columns for both App_process and XposedBridge.jar? am i missing a step? the towel root app says "root achieved enjoy" when i use it.
Click to expand...
Click to collapse
You have to do a softreboot in exposed to get it to activate.
wooddale said:
You have to do a softreboot in exposed to get it to activate.
Click to expand...
Click to collapse
i tried that? it seems i have root since i can access the system folder with Solid Explorer. but when i open framework installer. hit install/update i get the error, when i softreboot and go it and hit install/update i get the same error. i have the instal set to classic, should it maybe be something different?
yamaha83 said:
i tried that? it seems i have root since i can access the system folder with Solid Explorer. but when i open framework installer. hit install/update i get the error, when i softreboot and go it and hit install/update i get the same error. i have the instal set to classic, should it maybe be something different?
Click to expand...
Click to collapse
Were getting off topic here PM me Thanks
Ways to root your Samsung Galaxy Tab 4 7.0All of the guys on the list is tested by me and it's working
For those guys who can't root their tablet, this thread is the right place for you
1. This is the Easiest Way to Root your tablet
KingRoot App Download it here
http://www.appsandroidapk.com/apk/kingroot-v4-6-2-apk-file-for-android/
Download the app
Before installing it Go to Settings > General Tab > Security > and Enable "Unknown Sources"
Install the app and Root your phone.
You might wanting to have a SuperSU instead of kingroot's SU
Google it SuperSU Me Download the latest version or you can find it here in this link
http://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
Update the SUBinary
Reboot
2. KingoRoot App apk version
Download Link
https://root-apk.kingoapp.com/
Download the app
Before installing it Go to Settings > General Tab > Security > and Enable "Unknown Sources"
Set your device atleast 10 minutes before sleep due to inactivity
Install and Root your Device
Do nothing while rooting "Like tapping or bringing down the notification bar" this is why i make you set the 10minute-sleep
1st/2nd attempt might fail but on the other hand it will succeed
You might wanting to have a SuperSU instead of kingoroot's SU
Google it SuperSU Me Download the latest version or you can find the link here
http://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
Update the SUBinary
Reboot
3. Root Using TWRP (old)
Requirements
TWRP link is here
http://forum.xda-developers.com/attachment.php?attachmentid=3128455&d=1421957427
Important: Odin3 v1.85 Direct download Link
http://forum.xda-developers.com/attachment.php?attachmentid=581913
PC
On your pc Open Odin3 v1.85
Click PDA and choose the tar file that you've downloaded
Tick Auto Reboot and F. Reset time
Now go to your device, Boot into download mode ( Power it off wait until it vibrates then press Home,Power and Volume Down Simultaneously)
Plug your device into your Computer (Install drivers here's the link http://www.mediafire.com/download/o3exocwabcxax3b/SAMSUNG_USB_Driver.exe)/ Some Pc install drivers automatically just wait them to install or if you already install the drivers skip driver installation procedure)
Click Start if the Odin detects your phone, your phone will automatically reboot
Now Boot your phone into Recovery Mode by (Turning it off and Press Power + Home + Volume up)
It will boot into TWRP
Press Reboot > System and it will ask you if you want to get root and swipe it to install
Update SuperSU and make another reboot
You can also update your TWRP using this zip file
https://www.androidfilehost.com/?fid=24052804347818249
Now if you really can't root your tablet and you're desperate, try another version of your stock firmware, you can find your stock firmware on Google, after that do this procedure again
Done.
Other Links to make your tab Rooted
http://forum.xda-developers.com/showthread.php?t=3111934
http://forum.xda-developers.com/tab-4/help/twrp-install-twrp-root-samsung-galaxy-t3095736
Developers that has credit on all of this
@BRoy_98
@pinksworld
@gatesjunior
and sorry if i haven't mentioned the others, i dont know who to give credits
SORRY SOME OF MY ENGLISH IS REALLY BAD
Yay another one, I think this is the fourth of this same exact thread
You might want to mention how kingroot/kingoroot send your personal data to Chinese servers and the twrp builds you linked to only work fur the SM-T230, SM-T230NU, and SM-T231, and will not work for any of the several other Tab 4 7" variants
Just imagine that I just put all those threads together ahaha: )
thisisapoorusernamechoice said:
Yay another one, I think this is the fourth of this same exact thread
You might want to mention how kingroot/kingoroot send your personal data to Chinese servers and the twrp builds you linked to only work fur the SM-T230, SM-T230NU, and SM-T231, and will not work for any of the several other Tab 4 7" variants
Click to expand...
Click to collapse
I dunno if that issue is real, but no worries we have supersu me
thisisapoorusernamechoice said:
Yay another one, I think this is the fourth of this same exact thread
You might want to mention how kingroot/kingoroot send your personal data to Chinese servers and the twrp builds you linked to only work fur the SM-T230, SM-T230NU, and SM-T231, and will not work for any of the several other Tab 4 7" variants
Click to expand...
Click to collapse
I dont think that if you install first supersu me and then kingroot your tab, after root turn wifi off and use supersu me, no data sent to anyone........ anyways it doesnt send your passowords etc to china, just like browser data and few app datas.... but theres no way to get passwords.... all are crypted or hidden well in smali
thelous said:
I dont think that if you install first supersu me and then kingroot your tab, after root turn wifi off and use supersu me, no data sent to anyone........ anyways it doesnt send your passowords etc to china, just like browser data and few app datas.... but theres no way to get passwords.... all are crypted or hidden well in smali
Click to expand...
Click to collapse
I wouldn't be sure about that. If you type in your password, once rooted, anything can easily capture the keyboard input and log it or send it out. Let me elaborate. It's like the guys who say, "Hey I have a firewall installed so it cannot communicate out." Yeah, o.k., so all the firewalls do is manage IPTABLES, so if I am an application and have root access, I can do what I want to avoid your firewall rules quite easily. Just a thought.
Hmm, updating the binary will remove the @#$%&* thing , we're just going to use the app to root our phone, and I guess wiping cache and dalvik is necessary
BTW tab 4 is best for gaming because of it looks and size but due to a stupid Samsung company, 1.2ghz + vivante gc1000 expect lagging, I hope some kind hearted will make a custom kernel for overclocking this tab.
BTW There's no Tex plugin on gltools, installing default will not work, so you have to find a cracked version of gltools, well if you do that... R.I.P expect force closes
gatesjunior said:
I wouldn't be sure about that. If you type in your password, once rooted, anything can easily capture the keyboard input and log it or send it out. Let me elaborate. It's like the guys who say, "Hey I have a firewall installed so it cannot communicate out." Yeah, o.k., so all the firewalls do is manage IPTABLES, so if I am an application and have root access, I can do what I want to avoid your firewall rules quite easily. Just a thought.
Click to expand...
Click to collapse
Well i didnt say anything about firewalls i was daying if you manually disable wifi and use king root, it wont be able to connect anywhere to send any data.... also you can search by date and time files made during root session and remove everything to prevent any keyloger to work
Have ODIN and a stock image ready!!!
Be careful with this root process! The sm-t237p 5.1.1 OH7 boot loops and won't hold the root or Philz recovery... Yet!:cyclops:
thelous said:
Well i didnt say anything about firewalls i was daying if you manually disable wifi and use king root, it wont be able to connect anywhere to send any data.... also you can search by date and time files made during root session and remove everything to prevent any keyloger to work
Click to expand...
Click to collapse
No. I can easily change the file and date stamp to match any given system file you already have so that it is not easy to find. Also, Kingroot will not run correctly and root your device properly if it cannot contact it's servers to download the proper exploit for your device. Now, if you are talking about disabling wifi only so that Kingroot cannot contact it's servers after you are rooted, well, if you use any data what so ever, it can use that same data connection. As an example, I have to have data of some type to login to my bank site, etc..
SM-T237P Specific maybe others with PhilZ recovery...
Root Success! Check this out... http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
gatesjunior said:
No. I can easily change the file and date stamp to match any given system file you already have so that it is not easy to find. Also, Kingroot will not run correctly and root your device properly if it cannot contact it's servers to download the proper exploit for your device. Now, if you are talking about disabling wifi only so that Kingroot cannot contact it's servers after you are rooted, well, if you use any data what so ever, it can use that same data connection. As an example, I have to have data of some type to login to my bank site, etc..
Click to expand...
Click to collapse
Well, atleast my bank account cant be logged with different ip and if its tried i recice message wheres code that you need write to bank website to access account.... however i havent lodt any accounts yet after rooting with kingroot, it has so manynusers that they cant check all information they recive, just like facebook and whatsapp... (they're spying watnu do but they have too many users so it would take like unlimited time to check all accounts and keybindings thru.....
K94U said:
Root Success! Check this out... http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
Click to expand...
Click to collapse
You can use any kind of cwm to flash a zip file that can root your device, This was an alternative way, just find a cwm to flash hehe
Siegharf said:
You can use any kind of cwm to flash a zip file that can root your device, This was an alternative way, just find a cwm to flash hehe
Click to expand...
Click to collapse
Flashing recovery trips KNOX (no warranty or OTA updates) and the other method sometimes doesn't... Also, the recovery/zip method stopped working on lollipop and marshmallow with the older SuperSU builds but... Chainfire has a new BETA SuperSU 2.6X that is a systemless root and now working on the newer Android builds using the recovery/zip method. This seems to work for mostly ALL Samsung and Nexus devices... Read about it here:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
I restored my nandroid backup in recovery just to try this on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... You might need to install busybox for things to work... :good: :laugh:
K94U said:
Flashing recovery trips KNOX (no warranty or OTA updates) and the other method sometimes doesn't... Also, the recovery/zip method stopped working on lollipop and marshmallow with the older SuperSU builds but... Chainfire has a new BETA SuperSU 2.6X that is a systemless root and now working on the newer Android builds using the recovery/zip method. This seems to work for mostly ALL Samsung and Nexus devices... Read about it here:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
I restored my nandroid backup in recovery just to try this on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... You might need to install busybox for things to work... :good: :laugh:
Click to expand...
Click to collapse
There's kies or custom ota flashing
K94U said:
Flashing recovery trips KNOX (no warranty or OTA updates) and the other method sometimes doesn't... Also, the recovery/zip method stopped working on lollipop and marshmallow with the older SuperSU builds but... Chainfire has a new BETA SuperSU 2.6X that is a systemless root and now working on the newer Android builds using the recovery/zip method. This seems to work for mostly ALL Samsung and Nexus devices... Read about it here:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
I restored my nandroid backup in recovery just to try this on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... You might need to install busybox for things to work... :good: :laugh:
Click to expand...
Click to collapse
235 LTE 5.1.1 rooted as well
http://forum.xda-developers.com/showpost.php?p=64255121&postcount=1
(not spamming in case anyone got the idea)
Hello!
I need some Help with my Shield Tablet. I own the "Nvidia Shield 32GB LTE" Version and did root it 2 or 3 Days ago. Now i got the Message for the new "4.2 Upgrade" but after trying to install said Upgrade, i get the laying Android with an "Error". I tried the Installation 2 Times with the same Result. Do i have to Factory Reset my Shield to be able to install OTA 4.2?
I have no Experience with anything related to Software modification and got my root with a YouTube Tutorial on the Shield. I'd like to keep the root, and would reroot if necessary.
Any Help is appreciated!
Informations that may be helpfull:
- I have the Nvidia Family Drivers installed
- I have "minimal ADB and Fastboot "
- I own the "32GB LTE P1761" Model
- I have Android 6.0.1 installed with the Security Patch from 1. March 2016 and Shield 4.1 (24.3.67.35) Software
- I used the "TUTORIAL - Root NVIDIA SHIELD Tablet / K1 - Android 6.0" Tutorial on YouTube
Once you're rooted, you cannot update via normal means as the regular OTA update will check the system partition to make sure it is untouched.
The easiest way to update is to simply have the updater download the Full OTA and install. Go to Settings -> About tablet -> System upgrade -> 3 vertical dots on top right -> Advanced -> Check full upgrade (check it).
When it updates, it will remove root and very likely the TWRP recovery.
After it's updated, you can then go back and flash TWRP 3.0.2-2 to the recovery partition and then flash SuperSU 2.76 within TWRP. You may have older versions of TWRP and SuperSU if you used the YouTube tutorial, so be sure to get these newer versions.
Thanks for the the Advice, it helped!
Now im facing another Problem. After updating and rerooting, i can't use Lucky Patcher to install FakeGPS as an System App. I get the Error "there is not enough space within the system partition to move the application. please free up space in /system then try again.". I should have plenty of Space left on Internal and the full 180GB on my SDXC but it doesn't want to install. :I Any Suggestions?
Also "Hide my root" tell's me that it can't finde the "su binary".
Damn i want a one-push-do-it-for-me button. :crying:
[email protected] said:
Thanks for the the Advice, it helped!
Now im facing another Problem. After updating and rerooting, i can't use Lucky Patcher to install FakeGPS as an System App. I get the Error "there is not enough space within the system partition to move the application. please free up space in /system then try again.". I should have plenty of Space left on Internal and the full 180GB on my SDXC but it doesn't want to install. :I Any Suggestions?
Also "Hide my root" tell's me that it can't finde the "su binary".
Damn i want a one-push-do-it-for-me button. :crying:
Click to expand...
Click to collapse
Your not allowed to discuss LP here so I can't help with that. But if I were you I'd look at enabling compatibility mode in supersu. This helps with programs that haven't been updated to work with systemless su. I think the reason you can't install as a system app is because the program isn't properly calling su.
Sent from my SHIELD Tablet K1 using Tapatalk
I haven't found anything regarding compatability mode in supersu. Hidden option?
[email protected] said:
I haven't found anything regarding compatability mode in supersu. Hidden option?
Click to expand...
Click to collapse
Google search it. It's a command you can enter, I think in adb, that will let legacy root apps be granted root properly. I know it's all over the supersu thread in relation to es file explorer
Sent from my Nexus 5X using Tapatalk
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
Exile1975 said:
Google search it. It's a command you can enter, I think in adb, that will let legacy root apps be granted root properly. I know it's all over the supersu thread in relation to es file explorer
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Also, do you have busybox installed? If not start there
Sent from my Nexus 5X using Tapatalk
Yes I have busybox installed, but didn't help much. I will look in to Factory reset since I don't have private Data on this Tablet and I belive i may have done something wrong with the reroot.
I did a quick search on the supersu compatibility mode bit with no useful Results.
[email protected] said:
Yes I have busybox installed, but didn't help much. I will look in to Factory reset since I don't have private Data on this Tablet and I belive i may have done something wrong with the reroot.
I did a quick search on the supersu compatibility mode bit with no useful Results.
Click to expand...
Click to collapse
https://r.tapatalk.com/shareLink?ur...hare_fid=3793&share_type=t&share_pid=67710325
[BETA][2016.07.05] SuperSU v2.76
Sent from my Nexus 5X using Tapatalk
Thank you Guys for all the Help! \o/ Feel Brofistet from me.
I found the cause for the Error. It was the actual .apk that i tried to install. I went back trough my Chrome History to find the first one i used and it worked flawlessly. I sometimes have to wonder how i survive outside my Room...
As some of you will know, Samsung have no longer allowed S-Health to work on devices where Knox has been tripped.
This guide will show you how to get the latest version of S-Health to run without this block
Rooted Devices
This method requires you to be rooted. You can always unroot after doing this
If you are not rooted you can root your device by following the instructions below:
Download TWRP and save it somewhere you will remember.
Open ODIN and press AP then select the TWRP file you just downloaded.
Put your phone into Download Mode by holding Power + Volume Down + Home.
Connect your phone to your computer using a USB cable. Then Press Start in ODIN.
Download SuperSU-v2.79-SR3 and save it to your phone's SD Card.
Power off the phone and then hold Power + Volume Up + Home to boot to TWRP.
Press Install and locate the SuperSU file you downloaded earlier. Select it and Install.
You are now rooted.
To remove root, simple open the SuperSU app from your app drawer, go to settings and select Full Unroot
Follow the steps below to remove the S-Health block.
Download a root file explorer (such as Root Explorer, Root Browser or ES File Explorer).
Open the root file explorer and go to the /system folder.
Open the file named build.prop in text editor
In the build.prop file look for ro.config.tima=1
Change this line to ro.config.tima=0, simply changing the 1 to a 0
Reboor phone
Run the S-Health app
Non-Rooted Devices
If you are not rooted and/or cannot root then you can follow the steps below to get S-Health working (this will only work if the app is not installed as a system app).
Uninstall the S-Health App (if you cannot uninstall the app, this means it is installed to the system partition. Try Method 2 below).
Install version 4 of the S-Health app which can be found HERE
Open the app and complete setup
Update the S-Health app via the app store
You should now be able to use the S-Health app without issue
You can now use S-Health even with tripped Knox!!
{Mod edit: Download links via a suspicious URL has been removed}
Cannot download your S Health 4.8.1. Clicking the link asks me to log in to Facebook but, when I do, I get Sorry, your request could not be processed. Please try again. Can you upload it somewhere else?
Wonderful! It worked!
Hi
I update to nougat today an checked if i can use s health abd i didn't notice any problem.......no Error....i can use it normally as i use to do....keep in mind that I already've lost the knox waranty and it tells me that i got the latest version of s health
norm2002 said:
Cannot download your S Health 4.8.1. Clicking the link asks me to log in to Facebook but, when I do, I get Sorry, your request could not be processed. Please try again. Can you upload it somewhere else?
Click to expand...
Click to collapse
Apologies. I have updated the link in the OP.
Hammoud Abbas said:
Hi
I update to nougat today an checked if i can use s health abd i didn't notice any problem.......no Error....i can use it normally as i use to do....keep in mind that I already've lost the knox waranty and it tells me that i got the latest version of s health
Click to expand...
Click to collapse
Ye some people don't seem to be locked out. I've no idea why.
CuBz90 said:
Apologies. I have updated the link in the OP.
Ye some people don't seem to be locked out. I've no idea why.
Click to expand...
Click to collapse
thank God then
My S health version is 5.4.1.0003. Working perfectly on Nougat. And have never had an issue with s health before.
Sent from my SM-G935F using XDA-Developers Legacy app
Shidapu said:
My S health version is 5.4.1.0003. Working perfectly on Nougat. And have never had an issue with s health before.
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Like I said, it works fine for some. This is for those that cannot access it.
Shidapu said:
My S health version is 5.4.1.0003. Working perfectly on Nougat. And have never had an issue with s health before.
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Also here works perfectly with knox 0x1
ManDone.vRs said:
Also here works perfectly with knox 0x1
Click to expand...
Click to collapse
yes, but if u ever do a factory reset will not work anymore...with knox 0x1
Anyone having problem on step 11?
I cant install the app, giving me "there a problem pardon the package"
I have "unknown source selected", and I have downloaded 3 other times the app to make sure there was no problem...
Can someone help me, m
Thank
frumy said:
yes, but if u ever do a factory reset will not work anymore...with knox 0x1
Click to expand...
Click to collapse
i made it twices to test the latest build nougat , is the same , every day in gym i use SHealth... is ok .
mar_wu said:
Anyone having problem on step 11?
I cant install the app, giving me "there a problem pardon the package"
I have "unknown source selected", and I have downloaded 3 other times the app to make sure there was no problem...
Can someone help me, m
Thank
Click to expand...
Click to collapse
Have you enabled "Allow installation of apps from Unknown Sources"?
Have you tried re-downloading the app? It may have corrupt whilst downloading.
CuBz90 said:
Have you enabled "Allow installation of apps from Unknown Sources"?
Have you tried re-downloading the app? It may have corrupt whilst downloading.
Click to expand...
Click to collapse
Thanks for the reply...
Yes set for installation from unknown sources...
Yesterday after many hours of playing... I remembered about permission setting...
So I set to
RW
R
R
Restarted, and boom. Done!
Thanks, works great, now I have S health. Again
I have 5.4.1
CuBz90 said:
As some of you will know, Samsung have no longer allowed S-Health to work on devices where Knox has been tripped.
This guide will show you how to get the latest version of S-Health to run without this block
This method requires you to be rooted. You can always unroot after doing this
You can now use S-Health even with tripped Knox!!
Click to expand...
Click to collapse
Cool mate !!
Working
Should we have the device rooted? true? The only one nougat rom i have is a stock no rooted. No way to install Shealth from system/app because I´m don´t have root permissions on this folder
and how do root the device on nougat? I read in different threads that currently rooting the device leads to broken wifi and brightness-adjustment.
Can somebody provide us with a proper root guide or does a simple unroot fix these problems after installing S-Health???
deliyan said:
Should we have the device rooted? true? The only one nougat rom i have is a stock no rooted. No way to install Shealth from system/app because I´m don´t have root permissions on this folder
Click to expand...
Click to collapse
sirhC6 said:
and how do root the device on nougat? I read in different threads that currently rooting the device leads to broken wifi and brightness-adjustment.
Can somebody provide us with a proper root guide or does a simple unroot fix these problems after installing S-Health???
Click to expand...
Click to collapse
Flash TWRP in ODIN.
Then boot to TWRP and flash SuperSU-v2.79-SR3
To unroot, open the SuperSU app and select 'Full unroot'. S-health will still work as normal.
I use this root method and it works without causing any issues to the functionality of my phone.
CuBz90 said:
Flash TWRP in ODIN.
Then boot to TWRP and flash SuperSU-v2.79-SR3
To unroot, open the SuperSU app and select 'Full unroot'. S-health will still work as normal.
I use this root method and it works without causing any issues to the functionality of my phone.
Click to expand...
Click to collapse
Shealth working with your tip.thanks