I have perm rooted my shift and downloaded busybox from market...is there any use for it or will it be helpful later?
gbL420 said:
I have perm rooted my shift and downloaded busybox from market...is there any use for it or will it be helpful later?
Click to expand...
Click to collapse
You need it to keep busybox, but not the installer app from the market.
I had to install the busybox from titanium and tried updating it through the installer in the market and noticed that I don't have the remount command. Is that something that needs to be compiled in a custom busybox?
Related
So I'm rooted and downloaded Super User app from market. I have a bunch of root apps but the only app listed in the super user app is Titanium. Any reason why the other rooted apps (Set Cpu, Minfree Manager, etc.) aren't listed?
Have they asked for superuser?
Via EVO on 4G with XDA App
awenthol said:
Have they asked for superuser?
Via EVO on 4G with XDA App
Click to expand...
Click to collapse
No it doesn't
Sent from my CM6 powered device
krazyflipj said:
No it doesn't
Sent from my CM6 powered device
Click to expand...
Click to collapse
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
richse said:
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
Click to expand...
Click to collapse
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
krazyflipj said:
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
Click to expand...
Click to collapse
What root did you use? I did mine manually so there may be some differences if you used a one click.
Edit: I just looked at noobnl's one click root and it uses the same script that contains the line:
#copies busybox su
cat /system/bin/jk-su > /sdx/su
so it should definitely be there even if you used his one click.
When you run the command "ls -l /system/bin/jk-su" what do you get?
I get this:
ls -l /system/bin/jk-su
-rwsr-sr-x root root 26264 2010-09-18 06:10 jk-su
Please delete
krazyflipj said:
Please delete
Click to expand...
Click to collapse
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
richse said:
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
Click to expand...
Click to collapse
Hey Richse, I'm trying to get this to work but it isn't.
rose1 said:
Hey Richse, I'm trying to get this to work but it isn't.
Click to expand...
Click to collapse
can you give me more information, what errors are you getting or what exactly is happening?
richse said:
can you give me more information, what errors are you getting or what exactly is happening?
Click to expand...
Click to collapse
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
rose1 said:
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
Click to expand...
Click to collapse
I'm not sure why cp doesn't work, it just means copy. An alternative to try is to delete jk-su and replace it with the su you updated. Use these commands in place of the cp command:
rm /system/bin/jk-su
cat /system/bin/su > /system/bin/jk-su
Make sure you do this after updating su in the superuser app and without rebooting in between. Let me know if you have any problems.
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
spdwiz18 said:
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
Click to expand...
Click to collapse
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
richse said:
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
Click to expand...
Click to collapse
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
spdwiz18 said:
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
Click to expand...
Click to collapse
I doubt you need to update root. The root I used was the original manual method by joeykrim. The one click just automates that method. There is no reason why you should have to reboot multiple times to get this working. You basically just replaced a file with a similar file and the script that was installed when you rooted uses that file to create a new su every time you reboot. Personally, I would wipe to stock with Odin and then use the manual root method to make sure nothing funny is going on with your phone. When you rebooted and the su was "original" you didn't lose root, it just meant that superuser wouldn't work. For now, as long as the 2.3.1 -ef sticks around superuser will work just fine. As an alternative you could try noobnl's newest stuff. Looks like he made it compatible with superuser, so I think that would negate the need to use this type of fix. I'm not sure what he did to add the compatibility but you could probably ask him.
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
rose1 said:
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
Click to expand...
Click to collapse
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
richse said:
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
Click to expand...
Click to collapse
Very true. I didn't think about that.
I have latest Noobls kernel flashed on top of DI07 and this fix did not work.First thing that dint work is i never got SuperUser prompt after i typed su in adb shell,i got su in windows but no prompt on the phone.
To make it short i did the whole procedure from BetterTerminal(now i got su prompt) rebooted and back to same problem.Man,this been bugin me for two days now,sometimes i reboot the phone and i have root permissions then i reboot again and they are gone!
Big question is:is everybody on Epic have same issue or is it just on certain phones,kernels or roms?
Hi guys. I have already rooted my Wildfire with unrevoked3 and worked like a charm. Superuser is OK, I installed Titanium Backup and I installed busybox with it.
But I can't find how to run the busybox shell with root. Can anyone help me?
I downloaded android sdk for my Ubuntu 10.10 (I don't use windows) and I typed as root: ./adb shell and the terminal has not root priviledges.
Is there anyway to do this? Also how to run busybox? Via Terminal Emulator?
I think that the Titanium Backup didn't installed correctly.
My goal is to get a root terminal
Thanks in advance
Assuming that stuff works the same as on my linux computer, you would just su in the terminal emulator, then cd into the busybox directory, then make sure you have execute permissions for it, and then just ./busybox. That should start busybox in shell mode. That's how it should work.I think.
xc1024 said:
Assuming that stuff works the same as on my linux computer, you would just su in the terminal emulator, then cd into the busybox directory, then make sure you have execute permissions for it, and then just ./busybox. That should start busybox in shell mode. That's how it should work.I think.
Click to expand...
Click to collapse
The busybox is executed in my machine not in my phone right?
No, on your phone. Open up terminal on your phone (you can get one off the Market or alternatively connect you phone to the computer and start a ashell using adb), then cd to the directory you have busybox in, and then ececute ./busybox. Remember, you can't put it on the SD card because it doesn't allow execution.
sorry for this Android newbie question..
I installed Titanium Backup on my Desire....but when I ran it, an error message says " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again".
My Froyo is rooted....but whats this BusyBox and where can I get it and install it?
thanks..
I'm assuming you haven't rooted yet. Turn wifi on. Get an app called "universal androot". You need to get a version at least 1.6.2. It's not in the market so you may have to look around. Install and Open it up. Tick the box that says "soft root". Click the button labelled "root ". When the application force closes, wait 10 second and do nothing. then click on force close. Toggle wifi on. Go to titanium. Press allow when asked for root privileges. If it doesn't come up, look around titanium. It should allow you to instal busybox. Busybox is a set of *NIX utilities that are better than androids builtin. It allows the apps to use more advanced features. And It helps users if they are knowledgeable though to know how to use it.
nope..mine is rooted already via unrevoked3
dinoalbert said:
sorry for this Android newbie question..
I installed Titanium Backup on my Desire....but when I ran it, an error message says " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again".
Click to expand...
Click to collapse
Same problem here
rooted with revok3
installed rom manager and did a first backup
install titanium n tried to backup apps
It said " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again"
could some one link me to busybox app for wildfire n guide on how to backup wit titanium
pl reply
realxception said:
Same problem here
rooted with revok3
installed rom manager and did a first backup
install titanium n tried to backup apps
It said " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again"
could some one link me to busybox app for wildfire n guide on how to backup wit titanium
pl reply
Click to expand...
Click to collapse
Go to titanium backup, go to problems then it,will install busybox
thanks , its worked
Im new to the mt4g and im trying to remove the bloatware from my girlfriends phone. So i installed visionary and got temp root. I checked the box that was suppose to make the system r/w. I downloaded linda file manager went to system/app and tried to delete some bloat and the phone is telling me its still read only. Now I dont need perm root, and im not going to flash a new rom for her I just want to remove the bloat. Can someone please help, oh and she got the ota 2.2.1.
Fear the beard...
jayprime said:
Im new to the mt4g and im trying to remove the bloatware from my girlfriends phone. So i installed visionary and got temp root. I checked the box that was suppose to make the system r/w. I downloaded linda file manager went to system/app and tried to delete some bloat and the phone is telling me its still read only. Now I dont need perm root, and im not going to flash a new rom for her I just want to remove the bloat. Can someone please help, oh and she got the ota 2.2.1.
Fear the beard...
Click to expand...
Click to collapse
I believe you need s-off with perm root. Or else the apps will come back each time you restart. But dont quote me on this
Sent from my HTC Glacier using XDA App
don't need perm root... if you have S=Off and temp root you can do
adb remount
or open a terminal and do
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
Then remove any offending .apk files from /system/app. Upon rebooting, you will no longer have rw access to system and you won't be rooted either, but the programs will be gone. You may want to go the simpler route of temp rooting and installing Titanium Backup then uninstalling them through that.
slhpss said:
don't need perm root... if you have S=Off and temp root you can do
adb remount
or open a terminal and do
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
Then remove any offending .apk files from /system/app. Upon rebooting, you will no longer have rw access to system and you won't be rooted either, but the programs will be gone. You may want to go the simpler route of temp rooting and installing Titanium Backup then uninstalling them through that.
Click to expand...
Click to collapse
Thanks for the response. Im pretty sure I have S=off because ive got titanium backup and cashe mate installed and both ask and have recieved super user permision. But when I fire up titanium it doesnt show any of my apps so im gonna try to remount through terminal emulator. Thanks for the terminal commands.
Fear the beard...
jayprime said:
Thanks for the response. Im pretty sure I have S=off because ive got titanium backup and cashe mate installed and both ask and have recieved super user permision. But when I fire up titanium it doesnt show any of my apps so im gonna try to remount through terminal emulator. Thanks for the terminal commands.
Fear the beard...
Click to expand...
Click to collapse
Click the problems button at bottom install busybox
Sent from my HTC Glacier using XDA App
mftek said:
Click the problems button at bottom install busybox
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This solved my problem, thank you.
jayprime said:
This solved my problem, thank you.
Click to expand...
Click to collapse
No problem
Sent from my HTC Glacier using XDA App
Running stock 9.2.1.17 rooted. I'm trying to install CWM via Recoveryinstaller but whenever I try and run the app it tells me I'm not rooted. I for sure am rooted I've been using root apps for the longest time and just finished doing a titanium backup. what gives?
regP said:
Running stock 9.2.1.17 rooted. I'm trying to install CWM via Recoveryinstaller but whenever I try and run the app it tells me I'm not rooted. I for sure am rooted I've been using root apps for the longest time and just finished doing a titanium backup. what gives?
Click to expand...
Click to collapse
Look in system/bin copy the su and paste it in system/xbin.
Run RecoveryInstaller again afterward.
Just found a post saying the same thing. Thanks for the reply that did the trick.
baseballfanz said:
Look in system/bin copy the su and paste it in system/xbin.
Run RecoveryInstaller again afterward.
Click to expand...
Click to collapse
Does this action affect SU ? I mean not to work or something elsa?
nope
The su is supposed to go into system/xbin but for some reason it get install in system/bin on some TF.
Am trying to get busybox installed, but the smart install just spins, and the "installing busybox" just hangs. I can verify that I have root... and am on Marshmallow
kendoori said:
Am trying to get busybox installed, but the smart install just spins, and the "installing busybox" just hangs. I can verify that I have root... and am on Marshmallow
Click to expand...
Click to collapse
change install directory to /su/bin/
mademan420 said:
change install directory to /su/bin/
Click to expand...
Click to collapse
I kept banging on it, and it eventually insalled into /system/xbin
Not sure what I did, or if it was just a matter of waiting long enough...
kendoori said:
I kept banging on it, and it eventually insalled into /system/xbin
Not sure what I did, or if it was just a matter of waiting long enough...
Click to expand...
Click to collapse
I got it right using busybox installer from Jrummy apps and there I selected busybox version 1.20.1
It was installed in first go.