every time I try installing it, the phone crashes
I'm on stock, rooted lollipop
I have installed busybox using below app
busybox on rails,
use installation method as recovery and then proceed,
play.google.com/store/apps/details?id=me.timos.busyboxonrails&hl=en
Related
I'm currently running the stock SM-T310 4.4.2 build. I have my device rooted (verified by Root Checker Basic) and I have SuperSU installed via Play (SuperSU Free v2.4).
Yet every time I am in TWRP and attempt to flash a rom, the ROM install fails immediately and at Reboot, TWRP asks if I want to install/fix Root permissions. What is going on and why is there a discrepancy?
I have a galaxy s3 I747UCUFNJ2 that I tried rooting with CF-Auto-root, installed TWRP recovery and managed to get SuperSU updated but when i go to open SuperSU it won't open with message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Device status shows custom instead of official. I dont want to have to totally wipe the phone just root with no custom rom.....
What am I forgetting??
Since you have TWRP, just flash supersu.zip from TWRP.
Try busybox from play store
Do you have Knox?
You might need to freeze it with TIBU or remove it.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Just wondering if viper4android works on the new 6.0.1 update?
On my T805 it doesn't...
I got it working.
Root
Install BusyBox
Reboot to recovery
Flash viper and the supolicy zips
Reboot
Install viper drivers
Reboot
Use any script execution app (I use ROM Toolbox Pro) to run 50viper.sh found in system/su.d
Open viper and make your changes
You will have to run that script EVERY time after a reboot. For some reason the script isn't running on boot.
Sent from my SM-T700 using Tapatalk
I am running Android 7.0.0 on my P2 rooted with phh Superuser.
However, I want to switch to SuperSU, which as per my understanding (which is very limited in this matter) will happen after I properly uninstall Superuser.
I have researched quite a bit and found out that phh Superuser does not have an inbuilt unroot option unlike SuperSU.
I also flashed the SuperSU .zip file hoping it would delete the current Superuser, but in vain.
I tried to delete su and busybox from /bin and /xbin using Root Explorer but could not find those files in that location.
So I am really helpless now so as what to do in order to have SuperSU installed on my phone.
Try this:
UnSU Script
Flash in Custom Recovery
Videophile said:
Try this:
UnSU Script
Flash in Custom Recovery
Click to expand...
Click to collapse
Thanks for replying.
I flashed the .zip you suggested. It deletes the phh Superuser app but does not unroot.
I can tell this because when I flash the SuperSU .zip and install the app, upon launching it says su binary occupied.
And when I reinstall phh Superuser, it works as it did before.
So I'm afraid, it has not solved my problem.
aeonwiz said:
Thanks for replying.
I flashed the .zip you suggested. It deletes the phh Superuser app but does not unroot.
I can tell this because when I flash the SuperSU .zip and install the app, upon launching it says su binary occupied.
And when I reinstall phh Superuser, it works as it did before.
So I'm afraid, it has not solved my problem.
Click to expand...
Click to collapse
Correct, this will only help with removing Root successfully.
You'll then need to root via SuperSu or Magisk or phhSuperuser.
I've made a post about Magisk rooting here that you can follow, this will use Magisk Manager as your Superuser manager.
In that post I mention flashing your original boot.img which will remove any instances of SU you have previously installed if the zip I provided in my previous post does not work for you.
Thanks, I will try that.
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.