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?
Related
Hey Everyone -
I got my Kindle two days ago and decided to root last night.
I first upgraded to 6.2.2 and then followed the new directions for rooting.
After some hiccups getting the computer to set up ADB correctly (ran into some conflicts with the drivers installed with my Nexus) I got everything working. I followed all the directions provided and installed superuser.
Here is where my problems begin...
I side loaded root explorer but I can't switch the file system over to R/W. When I load up the app I never see it requesting root permissions or see them granted. The superuser log is 100% empty.
When I load up OTA RootKeeper in order to try and watch prime videos I see the following:
Superuser app installed - checked
Device rooted - checked
Root permission granted - unchecked
Filesystem supports root protection - checked
Protected su copy available - unchecked
It seems to me like my device is somewhere between rooted and not and I can not for the life of me figure out what to do next. I can't install the market, OTA Rootkeeper won't work so I can watch prime videos. I lost functionality and gained nothing.
Any suggestions?
hmm...
thats kinda what happened to mine, i had root explorer but not superuser. I just restored it back to factory settings and re-rooted it, and now it works just fine with no problems. Good luck!
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?
Hi Everyone,
Over in the Nexus 5X Q&A forum, member Tarv posted a problem which was the same that I started experiencing yesterday. Basically, there's no data connection (LTE, etc) while rooted, and Busybox installers can't find the su binary and think I'm not rooted, and Adaway doesn't work. Supersu by Chainfire shows Busybox and Adaway as having root access, though. All other root apps and activities, including Xposed, seem to work fine.
When I unroot, my data connection returns to normal. When I root again, the connection is lost, and the Busybox problem returns.
That's the basics, but below is a more detailed description as I posted to Tarv in the Nexus 5X forum, where I describe my theory regarding Busybox corruption.
"Hi Tarv, I've given you a "thanks" because you've saved me the time of writing pretty much what you wrote regarding my Nexus 6P. I started to experience this problem yesterday. Here are some details.
Everything was working fine. All my Nexus rooting through the years has successfully been done via NRT. NRT is not the problem, as this problem began long after already being rooted and well after using it recently to update to the newest 6.01 security patch.
I think the problem might be a corruption of the Busybox installation, though I'm open to being told that I don't I have a clue of what I'm talking about. I'm referring to the applets or whatever they're called, not the installation app.
The reason I think this is because I noticed a few days ago that when I tried to update Busybox to the newest version (1.24.2 from 1.24.1) via the Busybox Pro installer by Sterickson, it indicated the installation was successful, but the version number shown as being installed was still the old one. When I looked at the directory where Busybox was installed (/su/xbin), all of the applets were zero bytes. This bugged me, so I foolishly decided to uninstall the applets via the Busybox Pro installer and then reinstall, even though a warning popped up that this might cause problems.
It was after this that I lost my data connection (LTE, HSPA, etc.). Also, as you described, the Busybox installer will no longer proceed beyond saying that the su binary can't be found. Other installers also fail, including Busybox on Rails. Most root apps work fine, but not Adaway. Otherwise, the 6P with root works as expected, including using Xposed modules.
Upon unrooting, everything goes back to normal regarding the data connection. Rooting again results in no data connection.
There's probably a method via ADB to correctly reinstall Busybox, but I don't want to do that until someone confirms this is the likely issue. Otherwise, I suspect a full reinstallation of the OS might be needed.
OK guys and gals, ideas?"
I’m by no means an expert, but I’ve always been tech savvy or at least been able to research and follow directions for things I’d like to do on my devices. I flashed my rom using Odin to fix the bootloop, but I still need a way to successfully move the app to system apps without getting stuck in a bootloop. Here is what I have done or attempted so far:
1. I have a Galaxy Tab 4. I recently rooted this device using Kingo Root.
2. After I rooted the device I confirmed I had root access and everything seemed ok. I have used this app before to root other devices with no problem. I wanted to root this device so I could move Fake GPS Location Spoofer to the system apps folder and make it a system app.
3. I used lucky patcher to move the app to the system apps folder. However when it went to reboot my device, my device became stuck in a bootloop. After trying to repair the os, I successfully used Odin to flash my rom (android 5.1.1) and fix the problem.
4. After attempting to move the app with other file folder systems with root access, I still can’t move this app without it resulting in a bootloop.
What am I missing or doing wrong? Any suggestions, solutions, or insight would be welcome. If you need additional information or detail, just let me know. Thanks!
Update: After some more testing I believe that the rooting with Kingo Root is the problem and not the attempts at moving the app to system app. I flashed the 5.1.1 Rom with Odin then proceeded to to reroot the device with KIngo Root. Once I did that and it showed as successful. I restarted my device and I got the bootloop problem. I've tried rooting the device SM-T330NU using the method in the general section of the samsung tab 4 forum but was not able to boot into recovery and got a different bootloop problem that would go black and then blink repeatedly. I made sure to use the download for the 8.0 so I'm not sure what is going wrong.
Suggestions?
Update 2: I managed to finally root my device with the CF method. I am still not sure why the other methods I used didn't work.
Hi all im new to the site been rooting for a while now just as im using pokemon go i changed my root to the magisk systemless root it seemed great for the first day,then i came across an issue the root in the manager wouldnt turn off?? Now it keeps saying su binary is out of date but it trys installing another superuser app then it conflicts i dont no how to fix this as ive never used magisk till now hope someone what ive done wrong and can help thanks for your time.