Ive got a weird issue that I cant seem to get around and I wanted to see if anyone else has had this problem.
I got a replacement phone from Verizon last week. It came preinstalled with JB and since we have Towelroot now, I let it take the OTA update.
I rooted with Towelroot and when I went to install SuperSU, it tells me Knox is active and asks me to disable and I say yes. At that point, the phone just sits there and grinds on disabling Knox. Ive let it sit an hour and it still just sits there grinding on Knox. Its never finished disabling Knox the first time and Ive flashed the phone back to factory and re-rooted 4 times now, Everytime its the same.
If I reboot after that and re-run SuperSU, it gives me the Knox warning again and when I say Okay, it immediately says Knox is disabled.
Check root and it shows Im rooted and behaves as such.
Then the problems start. I start getting stuff FCing all over the place. Ive tried to do a Fix Permissions from within BusyBox and that didnt seem to help at all. I unrooted and the problems went away. I rooted again and they came back and then I got stuck on the SuperSU Binary Needs To Be Updated loop where every time I update, it fails and closes SuperSU.
Has anyone had this issue and if so, did you figure out a way around it?
I had Same errors installing Chainfire's SuperSu Pro
But all is working good now.
it Gives root to what ever I grant access to, so no complaints here.
I Have seen other posts with same issue so I am sure CF is aware and working on the issue.
Also, I have not had any FC's since rooting and installing SuperSu
Thanks for the reply.. I think the FCs are due to Knox not being disabled properly but Im not sure.
Did Knox disable okay for you?
Related
I have Voodoo OTA Rootkeeper installed & had done a temp unroot, so I could access Amazon prime content, but now I can't get it to restore the root. Any ideas what I'm doing wrong? And it does say "root su restored" after I push the "restore root" button, but even after 2 device restarts, I'm still unrooted. NEED to get on the regular market!
Could it be because it update the os to 6.2? I don't recall what it was before & it never ASKED me to update it, but idk
LoriH7 said:
Could it be because it updated the OS to 6.2? I don't recall what it was before & it never ASKED me to update it, but I don't know.
Click to expand...
Click to collapse
I doubt it, it's working fine for me and many others on 6.2.
If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.
Thelgow said:
If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.
Click to expand...
Click to collapse
Thanks! I'd bet that's what happened. It's almost always connected to wifi & I've had it rooted for a couple of weeks. Thanks. Back to super one click....
Ok, so I rerooted, but all of my google services are broken still. Reinstalled the apks, but it refuses to install the googleframework.apk. It's on there, asks me about permissions & then says it won't install. I'm clearly missing a step or something.
wierd issue
When I try to reroot my KF after the 6.2 update it roots the device then attempts to reboot into root... and that is when it fails... it just sits on the kindle fire screen flashing like it is rebooting I let it sit for a few minutes and never fineness, however if I hold down the power it will shutdown and I can start it back up but only half way rooted ... and never finished installing superuser or busybody... any ideas?
Not sure about those issues. Different people reported different problems.
Seems not everyone used the same methods. for me googleframework and market worked perfectly fine afterwards, i didnt need to do anything else.
Once my KF updated to 6.2, I could not restore root through OTA Rootkeeper either. Connected it to my computer, ran SuperOneClick, root was restored and backed up my root once again. I think I needed to reset once to ensure that all of my sideloaded apks still worked.
Well I got it figured out I just did a factory reset and reapplied root and now it is working thanks guys
Sent from my Kindle Fire using xda premium
I rooted my phone using towel root, everything seemed fine until it started randomly crashing. Now the crashing happens like this, the screen will freeze (with like weird tearing) then either restart or stay frozen. The only root app I use is wifi tether router. I did notice supersu will fail to update the binaries. Not sure if that could be a cause.
My question is how do I unroot it. So I can at least attempt any kind of fix. I'm still under warranty.
Can anyone help me at all? Please
waterbottels said:
I rooted my phone using towel root, everything seemed fine until it started randomly crashing. Now the crashing happens like this, the screen will freeze (with like weird tearing) then either restart or stay frozen. The only root app I use is wifi tether router. I did notice supersu will fail to update the binaries. Not sure if that could be a cause.
My question is how do I unroot it. So I can at least attempt any kind of fix. I'm still under warranty.
Can anyone help me at all? Please
Click to expand...
Click to collapse
A thorough way to unroot and reset everything is to Odin back to stock and then do a factory reset. The stock tar can be found here.
kinstre11 said:
A thorough way to unroot and reset everything is to Odin back to stock and then do a factory reset. The stock tar can be found here.
Click to expand...
Click to collapse
I was able to get supersu to work again, could I do an unroot through that even if I used towelroot?
waterbottels said:
I was able to get supersu to work again, could I do an unroot through that even if I used towelroot?
Click to expand...
Click to collapse
There is an unroot option in SuperSU (although I've never done it so I don't know if it actually unroots or just cleans up things to allow a clean unroot. The other thing I'm not sure it does is restore Knox which is something that will be checked for by the manufacturer). If you're taking your phone back or sending it in under warranty you probably should make sure you uninstall anything you need root for prior to unrooting, but if you're on a custom rom or want to make sure everything is back to factory (including Knox) I would recommend doing what I suggested in my last post.
Same Problem
Same problem as OP. I had a Note 3 originally that I took the update to 4.4.2 and used Towelroot and everything was fine. I recently broke the bejesus out of my Note 3 and got a replacement under the warranty. I used Towelroot on the new Note 3 and I am getting random freezing and a weird line that appears across the screen once it freezes. Sometimes it will reboot others I need to pull the battery.
What is happening? I am now back to stock and want to root again. Anyone have a solution to this?
hello.
I have rooted my phone for some time with chainfire super user.
I started facing blue screen problems and random restarts now. thought maybe there is some hardware faults. started SU app and have choosed full unroot and problem have disappeared for some time.
What have happened and why?
firmware 4.4.2.
Currently i updated software through kies (nj1 update).
so far so good. no bluescreen for now.
update.. still getting randoms reboots... what is causing them?
I also had random reboots after I rooted. Though I don't think the super user app caused it. It happened only after I installed viper4android.
I changed roms since then and no problem.
Maybe you installed an app that causes it. Only thing I can suggest is, either change roms, or reinstall stock rom and root again
Did you delete Knox-related apps from /system?
no. i didn't delete them... should I? there were nothing mentioned about file delete in rooting manual so i did nothing.
Should I delete every file that contains word knox or any concrete files?
After I updated phone by kies, rooted again, data format couple times + dalvik cache clear, problem seems to disappear. for half day so far so good, no reboot.
to change rom will be next thing i will do if reboots reappear
Knox can cause problems on rooted phones. That's partly why you don't find Knox in ROMs based off stock. So yes, you should remove the Knox apps in /system.
just remembered... when I launched SU app it asked me do i want to disable knox. i choose yes.
is it enough for removing knox or it is necessary run for example DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0.zip
p.s. sadly i can't install busybox. after i click install it shows "checking system" forever
Choosing yes was the right answer, but while SuperSU does disable Knox, I'm inclined to believe it's only so that SuperSU can properly function and install the su binary and doubt it's permanent. However, I never tested this, as I delete Knox apps regardless.
I've tried various root methods without success, last one worked BUT was unable to access the play store, "my files" section or the basic package installer, making it imposible to disable the knox security log for the notification issue and everytime I successfuly root it I can install busybox, supersu and root checker but beyond that I am unable to proceed further. When I restarted the phone it stays stuck in the att boot logo while vibrating from 2-3 times on a loop.
From that point on I have to wipe memory/cache and start all over again...
I Started up the phone without supersu but even that it has factory reset, there is lag from the phone.
anyone help?
I'll post device info
there's also a problem I found myself trying to fix the first problems after rooting it was a "dm-vareity verification" problem, son't know if I spelled correctly but that was basically what it said
Thanks In Advanced. :laugh:
I have done a few very successful roots in the past but have experirnced my first issue today with a newly rooted SM-T360 Tab4 Active. I used "CF-Auto-Root-rubenswifi-rubenswifixx-smt360" and Odin 3.12.3. The root passed with no error messages and I moved on. Installed Supersu Pro and ROM Toolbox Pro. Along with Root Checker. Here is my issue, after the tablet sits running for a while it seems to lose its root credentials. Supersu and root checker both report the same thing. I may have found a connection with busy box making it happen but I'm still not sure. Anybody ever had this issue before?