I appologize if this is the wrong forum, please move the thread if it is.
I have a quick question for whoever can help. I have been working on a new ROM and have everything perfect now including Aroma installer. The only issue that I am having now though is that once installed, It doesnt seem to have working root. It installed supersu apk and it looks like all the files are in the correct places however when I start supersu it gives the "Supersu binary is not installed and cannot install it, this is a problem". Nothing else obviously has root either.
I would appreciate if someone can point me in the right direction as to what may be causing this. Thanks in advance!
tp2215 said:
I appologize if this is the wrong forum, please move the thread if it is.
I have a quick question for whoever can help. I have been working on a new ROM and have everything perfect now including Aroma installer. The only issue that I am having now though is that once installed, It doesnt seem to have working root. It installed supersu apk and it looks like all the files are in the correct places however when I start supersu it gives the "Supersu binary is not installed and cannot install it, this is a problem". Nothing else obviously has root either.
I would appreciate if someone can point me in the right direction as to what may be causing this. Thanks in advance!
Click to expand...
Click to collapse
I know this supersu below ships with the system binary, You may need to extract, or download su and install it to /system/xbin before installing supersu
httpscolon//f-droiddotorg/repository/browse/?fdcategory=Security&fdid=com.koushikdutta.superuser
pull su alone here httpcolon//downloads.androidsudotcom/superuser/su-bin-3.1.1-arm-signed.zip
you have to fix the url, i have too low a post count to post links
dougunder said:
I know this supersu below ships with the system binary, You may need to extract, or download su and install it to /system/xbin before installing supersu
httpscolon//f-droiddotorg/repository/browse/?fdcategory=Security&fdid=com.koushikdutta.superuser
pull su alone here httpcolon//downloads.androidsudotcom/superuser/su-bin-3.1.1-arm-signed.zip
you have to fix the url, i have too low a post count to post links
Click to expand...
Click to collapse
Thanks but I just double checked and the su binary is in system/xbin. I have also tried re-coppying a fresh su there in the outcome is still the same.
Pretty sure it makes a difference on what phone you are building for, because sometimes there can be something in the kernel preventing it too. And what kind of rom are you making? CM? Stock based (Touchwiz, etc)? Other?
tp2215 said:
Thanks but I just double checked and the su binary is in system/xbin. I have also tried re-coppying a fresh su there in the outcome is still the same.
Click to expand...
Click to collapse
What do you get if you type su in the terminal?
Also found this post that may be of use
http://forum.xda-developers.com/showthread.php?t=2479233
dougunder said:
What do you get if you type su in the terminal?
Also found this post that may be of use
http://forum.xda-developers.com/showthread.php?t=2479233
Click to expand...
Click to collapse
Thanks but nevermind. I figured it out, just forgot to update this thread.
tp2215 said:
Thanks but nevermind. I figured it out, just forgot to update this thread.
Click to expand...
Click to collapse
Good to hear.
What was the fix, for other that find this thread?
Related
Hello
I've been making my own rom and suddenly i don't know what i did but su has stopped working please could someone have a look at tell me whats wrong with it and maybe if their kind fix it for me by the way when you flash it it will cut out saying it was aborted but it still works fine also after the boot screen it will go black for a little bit but thats just the first boot that does that but anyway i have su installed (the one with the blue hash) but i did have the one with the ninja on aswell but neither worked the programs i was trying to use with just said no root acses Pleease someone help thanks
My Rom
File uploaded now
Most likely its because of the old libs and new su app. You can edit the su lib, but what I suggest is you ask a developer very nicely if you could use the SU lib and SU app from there rom.
Also, it may be developing, but still should be posted under Q&A section.
Okay thanks il shall ask one
Also please could a mod move this thanks
Thread moved to Q&A.
Could someone please post a step by step on how to properly install the speedy Gonzales script for us less savvy people. Thanks in advance.
You have to be rooted with tenfars recovery and the init hack: http://forum.xda-developers.com/showthread.php?t=1223771
Download the .zip file that says flashable in the title, it located at the bottom of first post. Move it to sd card. This one: http://forum.xda-developers.com/attachment.php?attachmentid=704624&d=1314689490
Open the System Recovery app and select Recovery Mode (unsure plugged in).
Select choose zip from sd card. Navigate to the file and flash it.
What part is the issue, let me know where you have questions.
Ok I am rooted and have tenfars recovery. Do I still need the init hack installed or just go ahead and install new script through system recovery. Confused on first part.
Yes you need the init hack. Its the first link I posted. Its same thing. Download zip. Move to sd. Boot into recovery, flash. May be able to flash the speedy hack right after, but id reboot first just to make sure.
You need to go back into the /etc/init.d folder and delete the kickasskernel and S00tweaks once everything is successfully flashed.
One last question. I notice that there are 3 init.d hacks do you use all 3 or just one. That's the only think im not sure of.
Which ever one you want, but only one. Each is different and the description should describe that difference. I am on the first one. Battery saver or what ever its called.
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
dust. said:
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
Click to expand...
Click to collapse
That's what the instructions say in the original post for speedy.
You know what sucks is that the guy who made this got bashed so much he pulled the script and closed the thread...
This is supposed to be a community you ask and answer questions it gets to the point were people are afraid to ask anything without searching for 3-5 days for something i don't understand why people on these types of forums bash each others work so much its ridiculous...that sucks i feel really bad for the OP of this script he was just trying something and he got the crap kicked out of him....venting
im not gettintg the zipalign logfile he mentioned. hmmm
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
I didnt at first either, but I didnt follow directions proper and do the init.d thing first. after I did that I had the zip log thingy in /data
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
Same here.
Sandso9 said:
Same here.
Click to expand...
Click to collapse
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flash it in recovery and let me know if that works and you see the zipalign logs.
0vermind said:
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/jmvpyf
Flash it in recovery and let me know if that works and you see the zipalign logs.
Click to expand...
Click to collapse
flash it over yours then? or before ?
Sandso9 said:
flash it over yours then?
Click to expand...
Click to collapse
Yeah. Let me know if it works or if it doesn't.
0vermind said:
Yeah. Let me know if it works or if it doesn't.
Click to expand...
Click to collapse
flashed this over yours and still no zip align log file in /data
Sandso9 said:
flashed this over yours and still no zip align log file in /data
Click to expand...
Click to collapse
Sorry, wrong link.
Blah blah blah blah, edit edit edit edit
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flashed the latest file and still no zipalign log in /data.
zetsumeikuro said:
Flashed the latest file and still no zipalign log in /data.
Click to expand...
Click to collapse
Lol same here
Sent from my OG Droid
Hi, when installing Busybox with Stericsson Installer it allow to choose between system/bin or system/xbin to install it, which one to choose and why ? What's the difference ?
I have another question, sorry but I don't want to make another thread.
SuperSU has an option "Survival Mode" that says that we must disable it before Nandroid Backup, what happends if I forgot to disable it ?
Thanks for your help, sorry if it was already asked (search results didn't help me).
For the installation paths, i dont really think it matters whether you put it in either of the above.
About survival mode, again i say it does not really matter whether you disable it or not. Your nandroid backup will go smooth.
Some developer can explain it to you in detail if any of the above really matters.
Sent from my LG-E730 using Tapatalk 2
Ok, thanks.
If anyone has more infos your welcome.
I always install to /system/xbin because you then don't overwrite the symlinks of the tools that point to toolbox (Android's poor version of coreutils). On the other hand, if you'd rather have the Busybox tools as default then install to /system/bin.
Regarding survival mode: AFAIR file system corruption (at least with my U8800pro) because CWM doesn't know how to remove the immutable attribute off the su binary, so I'd make sure it's off when restoring.
qwerty12 said:
I always install to /system/xbin because you then don't overwrite the symlinks of the tools that point to toolbox (Android's poor version of coreutils). On the other hand, if you'd rather have the Busybox tools as default then install to /system/bin.
Regarding survival mode: AFAIR file system corruption (at least with my U8800pro) because CWM doesn't know how to remove the immutable attribute off the su binary, so I'd make sure it's off when restoring.
Click to expand...
Click to collapse
Neither in htc wildfire nor in lg optimus sol disabling the survival is important. I have flashed and restored a hundred times but nothing happened..
Sent from my LG-E730 using Tapatalk 2
Well, I think this is definitely new so I put this right here: just downloaded Stericson's BusyBox Pro installer from Play Store (as usual) to my Moto X Play on 6.0 Marshmallow and it is asking for the unusual default installation path of "/su/bin". As discussed here, "system/xbin" or "system/sbin" are usually the preferred installation paths for BusyBox, so this change simply got me stuck in the process thinking where to install BusyBox. My first thought is that BusyBox is 'auto-choosing' where to be installed according to system characteristics and I should go on, make my life easier and just install where it is asking me to, but... I don't know. Does somebody have a similar experience?
CNK80Q3MX said:
Well, I think this is definitely new so I put this right here: just downloaded Stericson's BusyBox Pro installer from Play Store (as usual) to my Moto X Play on 6.0 Marshmallow and it is asking for the unusual default installation path of "/su/bin". As discussed here, "system/xbin" or "system/sbin" are usually the preferred installation paths for BusyBox, so this change simply got me stuck in the process thinking where to install BusyBox. My first thought is that BusyBox is 'auto-choosing' where to be installed according to system characteristics and I should go on, make my life easier and just install where it is asking me to, but... I don't know. Does somebody have a similar experience?
Click to expand...
Click to collapse
I am having the same question.. I have viewed each of the 4 directories using a root file explorer and noticed /bin /xbin and su/bin su/xbin all contain ifferent files so im not sure if doing that helped me o confused me more. Lol but im not sure it matters ,well im sure it makes differences but I cant find a difference other than some symlinks may be rewritten and handled by busybox instead of androids tool box.... Once again that means nothing to me without knowing what exactly androids tool.box is... I know a couple tool boxes but unfortunantly this is not one, ... So if anyone has a link to explain this or an educated opinion that would be great! Thanks..
Also looking for this answer rn.. haven't found it yet.. this is my first look, from experience I believe MM build is recognized and BusyBox recommends install location based on Android Version. I'll look for a more definitive answer and post if I find.
Shagerty said:
Also looking for this answer rn.. haven't found it yet.. this is my first look, from experience I believe MM build is recognized and BusyBox recommends install location based on Android Version. I'll look for a more definitive answer and post if I find.
Click to expand...
Click to collapse
UPDATING: I'm wondering that being MM, Busybox installer chooses su/bin path automatically (some suggest "su/xbin", which is not present in stock MM, hence installer su/bin choice) in order to make Busybox "systemless". SuperSu actually does the same. Though I'm pretty sure about this, I'm also looking for confirmation. Since this thread and its early answers even date back to 2012 when there was no MM and "systemless" stuff wasn't that popular (I assume) they point to install Busybox in "system/xbin" or "system/bin"...
babylonbwoy said:
Hi, when installing Busybox with Stericsson Installer it allow to choose between system/bin or system/xbin to install it, which one to choose and why ? What's the difference ?
Click to expand...
Click to collapse
It really doesn't matter where you install either system/bin or system/xbin.........it always symlink to other as example if you install to system/bin then it'll symlink to system/xbin and vice versa
Mainak007 said:
It really doesn't matter where you install either system/bin or system/xbin.........it always symlink to other as example if you install to system/bin then it'll symlink to system/xbin and vice versa
Click to expand...
Click to collapse
I think it's a little bit too late, thread is from 2012.
I'm done with all that now, no more flashing rom, no more bootloader unlock.
I used to get all the flagship but I didn't change since XZ5 Dual.
babylonbwoy said:
I'm done with all that now, no more flashing rom, no more bootloader unlock.
I used to get all the flagship but I didn't change since XZ5 Dual.
Click to expand...
Click to collapse
Why??.......do you frightened of bricking device??????
You can get all smartphone firmware Here
:highfive::fingers-crossed:
babylonbwoy said:
I think it's a little bit too late, thread is from 2012.
Click to expand...
Click to collapse
And I gave the answer for other who will visit the forum next time:angel:
Mainak007 said:
And I gave the answer for other who will visit the forum next time:angel:
Click to expand...
Click to collapse
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Robert4321 said:
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Click to expand...
Click to collapse
Doesn't matter..... Install anywhere and symlink to others
Mainak007 said:
Doesn't matter..... Install anywhere and symlink to others
Click to expand...
Click to collapse
Just install it to any folder in $PATH and execute it as any other command.
Code:
echo $PATH
Robert4321 said:
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Click to expand...
Click to collapse
Banking / payment apps are looking in 3 mentioned paths to detect whether Android got rooted or not: hence best is to install BB to custom path.
BusyBox Pro says that it can is unsuccessful at installing in the /system/xbin folder on my Moto G Stylus 5G, I don't suppose anyone could explain to me why this keeps happening could they? Also, I don't have the option to install to /system/sbin either. The only options I have are /system/xbin, /system/bin, and custom. But when I install and reboot i have to reinstall BusyBox Pro again. I noticed in the settings tab that you can have busybox, on every boot, reinstall to /sbin....how is this possible if you install to /bin? also, how can I get it to install to /xbin? there is also another option that says busybox will, on every boot, be removed from /sbin as long as busybox has been installed to /bin or /xbin, but the feature I'm speaking of assists kernels that re-install busy box to /sbin on every boot.....OMG!!! Which option do I choose? Or should I not choose any, and just reinstall each time i boot up, which will be very tedious.....Please HELP!!!..... Also, should I choose Smart Install? Or just use install without the Smart Install option ticked? Sorry I see there are similar posts here, but I don't really understand where I would install if i chose to install to a custom path, which is why I'm asking such questions if it seems repetitive I apologize. Thanks in advance!
hi friends, can any one tell me how to create a .zip file using terminal?
if yes,
can i set compression levels?
Nobody?
sent from my smultron
I don't think you can. The zip command isn't recognized in the terminal emulator. Try typing tar, you can use that, you can then chose which compression method you prefer.
cigognes said:
I don't think you can. The zip command isn't recognized in the terminal emulator. Try typing tar, you can use that, you can then chose which compression method you prefer.
Click to expand...
Click to collapse
ah! getting near to the 10 posts threshold limit eh mate? :good:
anyways,
i tried that but, i only need to create a .zip file.
any ways to add the required binary? or the source for zip applet to compile it with busybox?
ah! getting near to the 10 posts threshold limit eh mate?
Click to expand...
Click to collapse
Yes indeed, and I'll shamelessly add another post to my count.
I couldn't be bothered to try it out myself yet as I haven't really had the time to mess about. But the following seems like a way to get the zip package installed on your phone. First install opkg through the adb shell, then you can get the zip package installed. Once that's done you should at least be able to zip files, no idea if you can change compression parameters.
How to get opkg, well I'm not going to simply copy other people's work.
And unfortunately I'm not allowed to post links yet. However searching google for installing opkg manager on android and or linux tools coming to mcr should do the trick. First results each time.
cigognes said:
Yes indeed, and I'll shamelessly add another post to my count.
I couldn't be bothered to try it out myself yet as I haven't really had the time to mess about. But the following seems like a way to get the zip package installed on your phone. First install opkg through the adb shell, then you can get the zip package installed. Once that's done you should at least be able to zip files, no idea if you can change compression parameters.
How to get opkg, well I'm not going to simply copy other people's work.
And unfortunately I'm not allowed to post links yet. However searching google for installing opkg manager on android and or linux tools coming to mcr should do the trick. First results each time.
Click to expand...
Click to collapse
thanks man! i'll try that!
I am trying to download and install the framwork from the Xposed Installer.
After pressing install/update, I get the following problem:
Copying Xposed-Disable-Recovery.zip...
Mounting /system writable...
Segmentation fault
Could not mount /system writable
Trying to continue anyway...
Segmentation fault
Failed to create a backup of /system/bin/app_process
im using bluestacks for windows 8.1
Can someone give me basic step by step instructions please thank you
flyboyissac said:
I am trying to download and install the framwork from the Xposed Installer.
After pressing install/update, I get the following problem:
Copying Xposed-Disable-Recovery.zip...
Mounting /system writable...
Segmentation fault
Could not mount /system writable
Trying to continue anyway...
Segmentation fault
Failed to create a backup of /system/bin/app_process
im using bluestacks for windows 8.1
Can someone give me basic step by step instructions please thank you
Click to expand...
Click to collapse
Your issue is described here: http://forum.xda-developers.com/show...postcount=9912
If you have trouble after that, make sure your SuperSU (or SuperUser) app is updated as well as the superuser binary. Also a good idea to make sure busybox is installed and updated if you have more issues.
link
es0tericcha0s said:
Your issue is described here: http://forum.xda-developers.com/show...postcount=9912
If you have trouble after that, make sure your SuperSU (or SuperUser) app is updated as well as the superuser binary. Also a good idea to make sure busybox is installed and updated if you have more issues.
Click to expand...
Click to collapse
your link don't work
Invalid Forum specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post.
ill try second step
flyboyissac said:
your link don't work
Invalid Forum specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post.
ill try second step
Click to expand...
Click to collapse
Sorry about that, could have sworn I just copied and pasted the link from the thread. Here you go: http://forum.xda-developers.com/showpost.php?p=51314174&postcount=9912
That one works but the other one I posted which appears to be the same, does not. Confused..
If that stops working again, then it is linked from the OP on the Xposed Framework thread here: http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401 which oddly enough, explains this problem in the Installation section of the OP.
es0tericcha0s said:
Sorry about that, could have sworn I just copied and pasted the link from the thread. Here you go: http://forum.xda-developers.com/showpost.php?p=51314174&postcount=9912
That one works but the other one I posted which appears to be the same, does not. Confused..
If that stops working again, then it is linked from the OP on the Xposed Framework thread here: http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401 which oddly enough, explains this problem in the Installation section of the OP.
Click to expand...
Click to collapse
thanks for the help but his attach file dont work it trys to install but just disappears after a couple seconds
flyboyissac said:
thanks for the help but his attach file dont work it trys to install but just disappears after a couple seconds
Click to expand...
Click to collapse
I'm not sure I follow you. The download should be a zip that is flashable via recovery. I was helping another member with this issue and they had to reinstall their rom and used Xposed v2.5 vs v2.5.1 and that worked for them.