Hi,
Just rooted my nexus 5x (duh). Using the wugfresh auto unlock/root method.
The method used by the tool is the good ol classic non-systemless method. It rebooted and i was presented with my rooted phone. Upon inspection I discovered that the busybox app was also installed. When I ran it I saw that it wasn't installed. So i installed it. At least I tried. Becuase I couldn't install it at all. No error whatsoever, just that the installation could not complete. Tried different apps no luck. One app displayed that it couldn't write to system/xbin. Odd. I installed it trough recovery. Worked fine. Then I downloaded whatsappx from the exposed repo. Told me sqlite3 wasn't installed. Same problem couldn't write to system/xbin. Or couldn't remount to r/w. How do I fix this?
Related
I attempted to root my friend's G2 first using Visionary+ R14 and temp root would work (the SU.apk is in the app drawer), so I attempted the perma-root and as soon as I granted it root access it would immediately reboot. Once I rebooted SU was still in the app drawer but rom manager kept saying the SU apk wasnt found in /system/bin or /system/xbin. I looked for it manually and searched for it but it couldnt be found anywhere, yet it was in the app drawer after a reboot.
I tried it a few more times and couldnt get it to work, I booted into the bootloader and saw that S-on wasn't off. After feeling competent enough I decided to push the hboot.img and the wpthis-OTA.ko to the sdcard (since I didnt have adb handy) and then copied them both to /data/local via the terminal. When I tried to insert the kernel module it gave me the expected error so I proceeded to flash the new hboot and that was also successful. I ran visionary again (guide doesnt say temp or permanent method, so i did temp), and once it was finished I typed sync into the terminal, waited a minute and rebooted.
Once android was fully loaded up again, I loaded up rom manager and it still complained that it couldnt find su.apk, I searched for it and it still wasnt there, yet it was still in the app drawer. I rebooted into the bootloader and saw that the protection was finally S-OFF, yet root access didnt seem to be (fully) available.
It also mentioned at some point that my su.apk was out of date and it downloaded the most up to date one for me but I had no way to flash it.
Whats wrong here?
This should either be in an existing thread about the rooting methods you're talking about, or in one of the other forums, such as Q&A
Sorry to bother everyone.
In preparation for the 4.04 update, I flashed the stock 4.02 ROM and then was prompted to install the VZW OTA update. This flashed OK. I went ahead via adb and flashed cwm-recovery and then installed the su.zip file via the recovery console.
Once rebooting, I'm able to pop open an adb shell and type su and become the superuser, however none of the apps that require root no longer work -- root explorer, busybox installer, etc.
I'm guessing its a problem with my su file (possibly). Does anyone have any suggestions to troubleshoot? Thanks.
The problem I'm having specifically is gaining root access....fail (within su app).
Hi,
i have a rooted Desire Z currently running CM9 RC2, and I've noticed recently that my # shell has been replaced by a [email protected]:/ and it seems like I don't have root access there. I can't ls in /data/ for example, and su throws a permission denied error. However, apps that require root access(such as Titanium Backup) still seem to work. I noticed this happen right after I installed and ran Busybox. I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access. I'm not sure if this app is what caused it, but it was when I noticed it.
In any case, short of a nandroid restore how do I get back shell root access and the proper shell?
Thanks.
Most likely your root access under System Settings -> Development was changed from "ADB and Apps" to "Apps Only".
PS: why would you be installing busybox, CM9 came with it (likewise with superuser and su).
Thanks. That worked.
Like I mentioned in my original post
I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access.
Click to expand...
Click to collapse
goister said:
Thanks. That worked.
Like I mentioned in my original post
Click to expand...
Click to collapse
Though your quote here conflicted so wasn't sure :
I noticed this happen right after I installed and ran Busybox.
Click to expand...
Click to collapse
Sorry for the confusion, by running busybox I meant simply launching the Busybox app(which is just an installer, not busybox itself), but not clicking the "install busybox" button in the app to actually install busybox on my phone.
Just installed 4.4.3 using WugFresh's excellent NRT keeping my data.
All went OK. At the end I told NRT to Root and install TWRP. Again OK.
Except that I don't have BusyBox installed. The app isn't present. SU is OK. A root checker app shows I am rooted and that BusyBox isn't installed.
There are no BusyBox files in \system\xbin or \system\bin.
Tried Google Play for Stericson's BusyBox and when the app tries to install it gives "Incompatible update" error and stops.
Found the apk file in \data\app and it comes up with "Not installed" error.
Found the zip file that NRT stored for TWRP to install and tried re-flashing that in TWRP. It says it was successful but BusyBox Installer app not available.
It was previously installed and OK under 4.4.2 this morning.
Everything else is as it was as far as I can see.
Any ideas what's going on?
Thanks
I installed another BusyBox Installer instead and that went OK.
Don't know what the problem is with Stericson's version.
I've got some strange problems when trying to use an app which requires superuser.
I've unlocked my bootloader, flashed TWRP and (tried to) flashed SU. But now, when I try to get SU in any app it tells me, that this is not possible.
Unlocking was done with [ToolKit] OnePlus 3 ToolKit, Unlock Bootloader, Flash TWRP, Root, and More! [v2.0]
SecureSettings tells me: Root access was not detected. The System+ module...
ES Explorer tells me: Sorry, test failed. This feature cannot run on your device
There is no overlay from SuperSU, asking if SU should be granted, and the only entries inside the SuperSU app is the ADB shell and Thermux. In this two cases the window popped up and asked if I grant SU, when calling su.
Where should the SU binaries be located? I've got a folder located directly in
Code:
/
but nothing in
Code:
/system/bin
or
Code:
/system/xbin
It uses systemless root, you won't find any supersu files in /system.
If you have twrp installed I would just grab the latest supersu beta and flash it, those toolkits always seem to cause issues that can be bypassed by learning how to do the basics yourself
Already flashed it by myself. The toolkit just pushed the zip with fastboot into storage. Then I flashed it using twrp. Also download latest version, copied it onto phone and flashed that zip. Same result...