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?"
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!
I'm on 6.0.1 and installed systemless root + busybox + TWRP recovery through the skipsoft tool.
Everything was working fine for a day or two.
I then wanted Xposed. So I installed xposed v79 arm64 and at first everything worked ok. Added gravitybox mm and started fiddling. Shortly root issues followed. Tasker somehow didn't acquire root, that's how I first noticed it. Nor did the "hibernate + lock" command in Greenify work which also requires root. Wondering wth is going on I went into supersu and it said the su binary cannot be found. No wonder root apps didn't work properly. Gravitybox still worked however but I assume this works at a lower level.
Everything worked fine until I got to the xposed part. Not sure if it was xposed or gravitybox that did it. Why is this happening and what can I do? I uninstalled gravitybox and now I have root again though supersu was VERY VERY slow in getting the list of root apps up in a way it never was before. Took minutes, but it did work and root apps function again. Other issues happened to: calculator fc for example.
Would I be better off with traditional root or what's up? I do have backups from before installing xposed thank god, so I'm not sitting in the **** here, but I'd sure like this all to work together.
TigerSoul925 said:
I'm on 6.0.1 and installed systemless root + busybox + TWRP recovery through the skipsoft tool.
Everything was working fine for a day or two.
I then wanted Xposed. So I installed xposed v79 arm64 and at first everything worked ok. Added gravitybox mm and started fiddling. Shortly root issues followed. Tasker somehow didn't acquire root, that's how I first noticed it. Nor did the "hibernate + lock" command in Greenify work which also requires root. Wondering wth is going on I went into supersu and it said the su binary cannot be found. No wonder root apps didn't work properly. Gravitybox still worked however but I assume this works at a lower level.
Everything worked fine until I got to the xposed part. Not sure if it was xposed or gravitybox that did it. Why is this happening and what can I do? I uninstalled gravitybox and now I have root again though supersu was VERY VERY slow in getting the list of root apps up in a way it never was before. Took minutes, but it did work and root apps function again.
Would I be better off with traditional root or what's up? I do have backups from before installing xposed thank god, so I'm not sitting in the **** here, but I'd sure like this all to work together.
Click to expand...
Click to collapse
This is just a long shot but if you have BusyBox install in su/bin try installing it into system/xbin and reboot. good luck.
boxcar8028 said:
This is just a long shot but if you have BusyBox install in su/bin try installing it into system/xbin and reboot. good luck.
Click to expand...
Click to collapse
I have busybox installed in /system/xbin, was this your suggestion?
TigerSoul925 said:
I have busybox installed in /system/xbin, was this your suggestion?
Click to expand...
Click to collapse
yeah, I had some other apps that had some issues with BusyBox installed into su/bin but after reinstalling BB into system/xbin fixed it for me.
boxcar8028 said:
yeah, I had some other apps that had some issues with BusyBox installed into su/bin but after reinstalling BB into system/xbin fixed it for me.
Click to expand...
Click to collapse
Oh, well not my issue then since they have been there all along it seems very sketchy too. It's as if it sometimes work at boot, sometimes not. Very weird. I don't know what it is but it must be some kind of combination.
Further analysis: some reboots it works, some it doesn't. Random weirdness surrounding root apps and also none-root apps. Calculator sometimes FC's and it seems all this is coming and going. Worse when Gravitybox is activated. I still have no clue what this is or what to do.
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?
I have the XT907 which was successfully rooted, so I presume(d). Last night I did nothing out of the ordinary. I plugged it in to charge, as it was almost dead. I woke up and took it off the charger, went out to smoke while coffee brewed, ran Clean Master app and it asked for SU permission (SuperSu). It didn't strike me as odd because I have it set so apps that update are required to ask for SU permission again. Only this time it wouldn't accept the permission I granted it. I tried again and it still wouldn't authorize (I was using the memory boost and I was trying to stop an app from auto starting when this happened). It told me to manually check the authorization in SuperSU. I did and it's listed there, all permissions granted. I ran RootCheck and it asked and was granted SU permission. I downloaded RootChecker just for a second opinion, and it too was granted SU permissions.
Before, during and after all of this, aside from the above mentioned Root checking app, I've downloaded one app onto my XT907: WiFi Password(Root). I needed the PW for my work's WiFi. It was denied SU permission. I've removed Clean Master from SuperSU, forced stopped Clean Master, rebooted Phone. Clean Master asks for permissions, is supposedly granted said permissions, but still won't accept them.
So two apps tell me I do NOT have Root on my phone, while two root checking apps say I DO have Root. I've not uninstalled or reinstalled anything or changed any settings as to get a further opinion on the matter. I rooted my device with KingRoot and uninstalled with SuperSU about a month or so ago. This is the first issue I've had. Any idea what gives? I'm a little stumped on this one.
It seems the issue is only with some apps. I've managed to fix the issue with Clean master by disabling SuperSU, re-enabling it then rebooting. Clean Master was granted permission and accepted it. So far I've not run into other issues. All root checking apps still say I have a proper root. If the issue continues, how about a reinstall of SuperSU? If I lost root, how would I regain it?
A while back I was able to achieve root on my ZTE 2050 (which also goes by about 20 other names.) I was continuously having issues with the phone locking up, I couldn't access the root files, as well as many other issues. I tried installing BusyBox to see if that helped. I was able to access the root files, but if I moved or deleted anything, the phone would begin to freeze up again. Every time it froze and I would restart it, I would lose cell service until I rebooted the phone between 4 - 6 times. Finally what I figured out is that the folder BusyBox was installing the applets in, /system/sbin, were fighting against Magisk and it's BusyBox. After deleting BusyBox and reinstalling it in /system/bin and applying the option to have it reinstalled upon every boot, I have no issues accessing and modifying the root system. Don't know if anyone else has had trouble with that, but if so I hope this helps. Now if I could only figure out why I lose stock recovery once the phone is rooted or could even install TWRP I'd be doing pretty good.