Related
Besides the SU Binary In /system/xbin, what else do I need for SuperSU to function?
It keeps saying the SU binary is not installed
SpikeyPsyche said:
Besides the SU Binary In /system/xbin, what else do I need for SuperSU to function?
It keeps saying the SU binary is not installed
Click to expand...
Click to collapse
did you download the su app from the playstore
jerrycoffman45 said:
did you download the su app from the playstore
Click to expand...
Click to collapse
I was rooted on MI9 using the DLV method. I updated to NC2, and the SU binary installed by SuperSU persisted in the /system/xbin/ directory, but the SuperSU app says it is not installed. I wanted to know what, if anything, I can do with the SU binary in place to get the SuperSU app up and running again.
SpikeyPsyche said:
I was rooted on MI9 using the DLV method. I updated to NC2, and the SU binary installed by SuperSU persisted in the /system/xbin/ directory, but the SuperSU app says it is not installed. I wanted to know what, if anything, I can do with the SU binary in place to get the SuperSU app up and running again.
Click to expand...
Click to collapse
i am not sure there is anything you can do till we get a root exploit for nc2
yeah, i too have still have su in system/xbin on NC2, but root isn't working. it's weird, but as stated above, we probably need a new exploit or something
Are the permissions correct on the su binary? Might as well check that before we start despairing.
DrAzzy said:
Are the permissions correct on the su binary? Might as well check that before we start despairing.
Click to expand...
Click to collapse
Yeah, I'm not allowed to set the permissions in Root Explorer without root, but it does show a preview and the permissions do match all the other files in xbin
YrrchSebor said:
Yeah, I'm not allowed to set the permissions in Root Explorer without root, but it does show a preview and the permissions do match all the other files in xbin
Click to expand...
Click to collapse
Same here, permissions match all the other binaries in xbin.
SpikeyPsyche said:
Same here, permissions match all the other binaries in xbin.
Click to expand...
Click to collapse
I wonder what this means. I figure we dont need a new kind of su binary, but there must be something in the new software that blocks it from working?
I hope it isn't in the kernel. I had a Sony device last, and we needed an ever so slightly modified kernel in order to get full root on 4.3. But I doubt if we will ever be able to flash kernels.
YrrchSebor said:
I wonder what this means. I figure we dont need a new kind of su binary, but there must be something in the new software that blocks it from working?
I hope it isn't in the kernel. I had a Sony device last, and we needed an ever so slightly modified kernel in order to get full root on 4.3. But I doubt if we will ever be able to flash kernels.
Click to expand...
Click to collapse
I'm guessing there is some setting or permission that needs to be changed.
Hi everyone. I'm new at this bands.
I have S5style_i8190XXANC2_v3 instaled on my phone. I tried to install ViperFX but i couldn't do that that because driver instalation fails. It says it's because of busybox not properly instaled or something like that.
What i want to know? how to install busybox correctly? i tried do that with a play store app BusyBox instaler but not solved the problem.
Can anyone help me?
Thanks and sorry for bad english.
pajocos said:
Hi everyone. I'm new at this bands.
I have S5style_i8190XXANC2_v3 instaled on my phone. I tried to install ViperFX but i couldn't do that that because driver instalation fails. It says it's because of busybox not properly instaled or something like that.
What i want to know? how to install busybox correctly? i tried do that with a play store app BusyBox instaler but not solved the problem.
Can anyone help me?
Thanks and sorry for bad english.
Click to expand...
Click to collapse
1)Install busybox installer app https://play.google.com/store/apps/details?id=stericson.busybox
2)Run busybox installer app
3)Install busybox from inside the running app
4)Done :good:
jstath1972 said:
1)Install busybox installer app https://play.google.com/store/apps/details?id=stericson.busybox
2)Run busybox installer app
3)Install busybox from inside the running app
4)Done :good:
Click to expand...
Click to collapse
I tried this to... Still not working.
Hey dude its have allready busybox :
Originally Posted by galaxy mini View Post
V3 is on its way, hope i get it ready and uploaded this week!!
- lighter version
- fixed layout bugs
- kill app with long press backbutton added
- few UI changes
- latest SU and busybox added
http://forum.xda-developers.com/showthread.php?p=52630772&highlight=busybox#post52630772 Post #163
You don't have to install another one. Maybe old version ViperFX? Make sure you use the version for Android 4.x
jstath1972 said:
Check if your phone is still rooted.
Click to expand...
Click to collapse
yes it is. i can use other apps that need's root. I can use greenify for exemple and other app to remove system apps that i don't need. All off them are working. I install the busybox and it's successful. But when I try to install the driver that Viper ask's it says: driver install failed, the busybox found on your device does not work. this usally means you installed the wrong or broken busybox.
jstath1972 said:
Hey dude its have allready busybox :
Originally Posted by galaxy mini View Post
V3 is on its way, hope i get it ready and uploaded this week!!
- lighter version
- fixed layout bugs
- kill app with long press backbutton added
- few UI changes
- latest SU and busybox added
http://forum.xda-developers.com/showthread.php?p=52630772&highlight=busybox#post52630772 Post #163
You don't have to install another one. Maybe old version ViperFX? Make sure you use the version for Android 4.x
Click to expand...
Click to collapse
Yes i'm using that version. but i'll try again.
pajocos said:
yes it is. i can use other apps that need's root. I can use greenify for exemple and other app to remove system apps that i don't need. All off them are working. I install the busybox and it's successful. But when I try to install the driver that Viper ask's it says: driver install failed, the busybox found on your device does not work. this usally means you installed the wrong or broken busybox.
Click to expand...
Click to collapse
Maybe old version ViperFX? Make sure you use the version for Android 4.x
jstath1972 said:
Maybe old version ViperFX? Make sure you use the version for Android 4.x
Click to expand...
Click to collapse
Nope... still not working. I don't know what i'm doing wrong... I really don't want to do this by brute force. That means reinstall rom to see what is going to happen.
I'll try to install previous version from busybox. it can be incompatible or something like that.
Install sd maid app and run it to see if the busybox in your device is ok.
If this app running and don't ask from you to install busybox then it's vipers fault.
jstath1972 said:
Install sd maid app and run it to see if the busybox in your device is ok.
If this app running and don't ask from you to install busybox then it's vipers fault.
Click to expand...
Click to collapse
yup. on geral vision, on busybox it says [Normal] so it must be viper fault... Can you point me any other good equalizer to s3 mini?
pajocos said:
yup. on geral vision, on busybox it says [Normal] so it must be viper fault... Can you point me any other good equalizer to s3 mini?
Click to expand...
Click to collapse
DSP Manager Equalizer for Android is the alternative to viper or you can look at the playstore.
thank you!!!
jstath1972 said:
Install sd maid app and run it to see if the busybox in your device is ok.
If this app running and don't ask from you to install busybox then it's vipers fault.
Click to expand...
Click to collapse
SD Maid doesn't check the devices system busybox.
Use a tool like https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator for that.
Viper Audio for Android devices
Viper Audio for Android devices can be installed without busybox... Just follow instructions...
1. Download v4a . zip
2. Flash using recovery like cmw. After reboot device .
3. Install viper Audio application, now everything done.
4. If you need to check driver status, check in menu...Done... View attachment 2947879
i am on .205 locked BL rooted with TOWELROOT,
but i am trying to install CWM by this method http://forum.xda-developers.com/showthread.php?t=2649923 it does not go further (as seen in attached file)
i also tried single recovery but same result, any body tell whats the metter?
Install busybox via busybox installer from playstore
pranavthombare said:
Install busybox via busybox installer from playstore
Click to expand...
Click to collapse
same result bro :crying:
Super su installed?
pranavthombare said:
Super su installed?
Click to expand...
Click to collapse
yes.
but it does not ask for SU permission, as normly i should b,,,
Does any other app ask for root?
When you open super su, does it shows any message?
pranavthombare said:
Does any other app ask for root?
When you open super su, does it shows any message?
Click to expand...
Click to collapse
yes normly it does as i install BusyBox its asked for permission as it is for Xposed Installer
Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
groggycl said:
Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
Click to expand...
Click to collapse
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
mhrajib said:
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
Click to expand...
Click to collapse
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
groggycl said:
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
Click to expand...
Click to collapse
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
mhrajib said:
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
Click to expand...
Click to collapse
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
groggycl said:
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
Click to expand...
Click to collapse
What kind of error do you get?? Can you do other operations through link2sd??
mhrajib said:
What kind of error do you get?? Can you do other operations through link2sd??
Click to expand...
Click to collapse
the error is the following..
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Thats the error. Tried with titanium backup pro version and it gets stuck "PROCESING" the thing... It uninstall the app I want to move to system app, but then never finishes processing..
I also used a app called mount "/system ro/rw". I grant it superuser permissions and when I hit the "mount /system rw" a message appears that says; "Your device might not be rooted or is it not compatible!"
groggycl said:
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Click to expand...
Click to collapse
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
leledumbo said:
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
Click to expand...
Click to collapse
I've installed busybox and when I try lsof /system it says "toybox: Unknown command lsof", is there any solution?
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
darkensx said:
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
Click to expand...
Click to collapse
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
mrmazak said:
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
Click to expand...
Click to collapse
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
darkensx said:
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
Click to expand...
Click to collapse
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
mrmazak said:
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
Click to expand...
Click to collapse
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
darkensx said:
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
Click to expand...
Click to collapse
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
mrmazak said:
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
Click to expand...
Click to collapse
Got it to work had to tell BusyBox installer to overwrite and symlink it apparently it's unchecked by default as its "not recommended to replace the systems version" :silly: go figure maybe under normal circumstances with a correctly functioning mount its bad but it fixed it stericson BusyBox installer did others weren't tested but I assume same result. But thanks for your help greatly appreciated it.
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
darkensx said:
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
Click to expand...
Click to collapse
magisk is working well in the r1?
dark8899 said:
magisk is working well in the r1?
Click to expand...
Click to collapse
yes but because of the way we have to initially unlock/root the r1 it doesn't pass safety net with magisk unless android is not passing safety net again with magisk. but like i mentioned some things can break root "busy box X" with certain apps. also xposed framework systemless and normal seem to work well.