Busybox won't install to /su/xbin. Fix? - Samsung Galaxy Nexus

Hi, i am having problems getting busybox to install to the /su/xbin location. I am using NRT to root my phone and a the end of the rooting process a message pops up and says to check SuperSU to make sure everything is updated then open busybox and install it to /su/xbin (optional but recommended). Everytime i try i get a toast notification that says Systemless root is not configured. What can i do to fix it? it was working fine yesterday and it started doing this when i flashed Stock 4.1.1.

Related

[Q] SuperSU keeps stopping

I am on stock 4.3 and used the CF-autoroot to root my S3. When my phone rebooted it said unfortunately SuperSU has stopped. So, I googled the problem and someone said to download the latest apk and it should work. I did that and SuperSU did work and I installed titanium backup to make sure. However, after I installed Xposed and rebooted, it said that SuperSU has stopped again and I can't go in the app. Will I have to update it every time by downloading the apk when I reboot? When I go in the playstore it just says open and not uninstall or update.
Edit: Ignore the thread. I got it working after flashing the KNOX remover and flashing the latest SuperSU through TWRP.

SuperSU 2.76 fails to install after update to H15

I've updated with the OTA from H14 to H15. I restored the stock recovery beforehand and the update went without Problems.
Before starting the update I tried to "unroot" which also was stated neccessary by SuperSU in two dialogs. But this failed and might be the origin of the problem.
Afterwards SuperSU could not find the su binary so I tried to flash it via TWRP 3.0.2.0 which failed after the line "creating ramdisk backup".
Next I tried to dirty flash the H15 Rom, which also went without problems, but the SuperSU install failed at the same point.
I've attached the logfile of the aroma installer, containing the superSU logfile.
The phone works for the moment, without root / superSU but I would like to have it back
Does anyone have an idea / need more informations / can otherwise help ?
Henry

root problem

hi,
i just installed the last beta version of OOS (beta 14) and my phone was previously rooted.
when i instaled the update, i reflashed super SU and when the phone booted up i had TWRP and SuperSU flashed but all my apps said the phone wasn't rooted (superSU showed me the message about SU binary not being installed or whatever).
i then uninstalled SuperSU and rechecked and all my apps said my phone was rooted. what did i do wrong? i am thinking that this is a temporary root without SuperSU so i would love it if someone had a solution and coul help me
Try to flash the superSU.zip once again without clearing cache .....it would work
i tried with and without clearing cache, nothing works. i also tried 4 different supersu zip files.
i even reflashed OOS and tried again (don't know if that does anything)

Galaxy S3: Rooted but SuperSU hangs with black screen

I have a Galaxy S3 i747 running Android 4.3 with baseband I747UCUEMJ2. I rooted it back in the day using CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5. In the last few months it's been unstable and very slow, even rebooting or hanging up. It appears to be related to the SuperSU, b/c when I disabled SuperSU, everything seems to work smoothly again. So I tried updating SuperSU to the latest, v2.82, but same thing, plus now when I open SuperSU, the app shows a black screen and freezes. Sometimes I can end the task, but most of the time the phone is completely frozen up, requiring a force reboot.
Also, Root Checker says I'm not rooted, which I'm sure is b/c SuperSU is freezing up, thus failing to respond to Root Checker's request.
What I have tried:
1. Cleared System cache
2. Cleared SuperSu cache, can't clear its data though, nor uninstall it b/c it's considered a system file now.
3. Uninstalled SuperSU latest update v2.82, which puts it back at v1.62, still does the black screen and freezes
4. Installed Towelroot just to see if there were any issues with the root process. Towelroot said it was successful.
4. Tried to install the SuperSU.zip version via the Custom Recovery CWM v6.0.4.7, but it fails with the following error:
Installed failed
Finding update package...
Opening update package...
E:failed to map file
Installation aborted
5. Also tried the CF-Auto-Root-d2att-d2uc-NoKnox-samsungsghi747.zip version via the Recovery, but it also failed with same error as above.
Any suggestions to resolving this? If I need to flash a rom, could someone please suggest one that has most of the Samsung bloat removed and possibly running v4.4 KitKat? I've seen many, but I'm always concerned I will pick one that is not totally compatible with my phone.
I suggest flashing the latest stock ROM via Odin, set up the phone to make sure everything works. Then flash twrp, flash SuperSU from twrp.
https://forum.xda-developers.com/ga...ile-sgh-i747ucufne4v4-4-2attall-odin-t3305899

Fixing SuperSU

There's a known issue with SuperSU where if you are in superuser mode, you cannot browse the /sdcard path. There's a fix called bueller-fixsusdcard.zip you can apply in TWRP, but the problem seems to come back. Also, there are notifications about updating su that cannot be completed since you cannot seem to actually run the SuperSU app.
You can fix the first problem by flashing the latest SuperSU instead of bueller-fixsusdcard.zip. I used SR5-SuperSU-v2.82-SR5-20171001224502.zip. I have a rooted fully unlocked Fire TV 1 so I extracted the unlocked bootloader and flashed that in TWRP first. I don't know if I needed to actually do that, but I figured that it might be wise to start with a clean boot before flashing the new SuperSU.
The ability to be root and browse /sdcard has been good for a few days now. The other issue of not being able to run the SuperSU app still exists. BTW, I tired to install Magisk 14.0 a while back, but it leaves the FireTV in an unbootable state. I have to flash the boot_unlocked.img file in TWRP and then SuperSU to fix it. I wish someone would troubleshoot why it doesn't work. At least Magisk root can be hidden easier.

Categories

Resources