I just unlocked and rooted my nexus 7 and choose to install busybox but its not showing in the list of installed apps. is there a way to check if it installed correctly? I don't want to reinstall it and corrupt my device. Thanks..
Install terminal emulator and enter su then some command line commands. If it works busybox installed right.
Sent from my Nexus 7 using xda app-developers app
where can I get this app?
lildishlvr said:
where can I get this app?
Click to expand...
Click to collapse
i got it.. thanks
busybox
jgr208 said:
Install terminal emulator and enter su then some command line commands. If it works busybox installed right.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
one more question, is busybox is installed, should it show up as an app in the list of apps installed on the nexus 7?
Busybox is not an app and won't show up as one because it isn't something you can run by itself. It is a component that other apps require to run.
Related
When i first open titanium backup a popup that says "Busybox is working but the su command does not elevate to root: whoami reports whoami applet not found instead of root/uid0". If i try to do anything with the app it tells me that system requirements are not met. Does anybody know what i need to do to get whoami working right?
Sent from my nook COLOR.
have you tried
1. look at bottom and click problem? and reinstall busybox
2. reinstall app
nookroot said:
1. look at bottom and click problem? and reinstall busybox
2. reinstall app
Click to expand...
Click to collapse
Thanks but that didn't change anything. I rebooted in between.
Sent from my nook COLOR.
Rooted my hero 2.1 and when I try to $ su , I get "must be suid to work properly". I've not ran into this before, What needs to be done to fix this ? thanks.
dude what are you talking about when u root u have super user aka su
Bierce22 said:
dude what are you talking about when u root u have super user aka su
Click to expand...
Click to collapse
Yea, you'd think that would'nt you.. When I run Regs "root me" , It tells me I'm already rooted, but when I try the command, $ su , I get the above message..or permission denied..
Houndog101 said:
Yea, you'd think that would'nt you.. When I run Regs "root me" , It tells me I'm already rooted, but when I try the command, $ su , I get the above message..or permission denied..
Click to expand...
Click to collapse
Also, I see # from adb shell command, but the phone thinks its not rooted. What up with that. If I try to install busybox it says " No root access" , rom manager the same thing...all I want to do is install a recovery so I can get off the stock rom..
Have you tried something as simple as updating su in the play store and trying? If not, try flashing an HERCIMG recovery through hboot.
Sent from my PC36100 using xda premium
anthony_s said:
Have you tried something as simple as updating su in the play store and trying? If not, try flashing an HERCIMG recovery through hboot.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Yes and Yes, Niether worked,, thanks tho.
Have you tried updating the su binary from within the su app itself?
Sent from my PC36100 using xda premium
Yes, that worked, thanks.
Houndog101 said:
Rooted my hero 2.1 and when I try to $ su , I get "must be suid to work properly". I've not ran into this before, What needs to be done to fix this ? thanks.
Click to expand...
Click to collapse
Old old thread but if someone encounters this again, it is due to busybox SU not having the correct permissions and can be corrected easily.
I got the info from here: ttp://forum.nas-forum.org/index.php?page=Thread&threadID=526
Quoted from that page:
Code:
su: must be suid to work properly
I finally discovered that /bin/busybox which provides su (and in fact almost all commands) has not its set UID , i.e. the unix rights are
Code:
rwxr-xr-x instead of rwsr-xr-x
i could finally change the rights with
Code:
chmod 4755 /bin/busybox
and su works fine again
Click to expand...
Click to collapse
Just thought I would share since I saw this on my synology NAS and it pretty much directly applies to this issue from an age ago.
yes, you need to su in order to make it work as administrator.
What is it ? ADB Shell . is it CMD command on Windows or what ?
muslimbaha said:
What is it ? ADB Shell . is it CMD command on Windows or what ?
Click to expand...
Click to collapse
https://developer.android.com/tools/help/adb.html
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
kt-Froggy said:
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
Click to expand...
Click to collapse
Sorry, but i know what it is now, how do i run it though? im trying to follow the htc desire hd guide to root my phone, which everything is done up until the point i have to test that i have root in debug mode. Not sure how to do this? run abd.exe? it just showed me a cmd window which runs and then dissapears.
If you got your phone rooted or want to test it run adb.exe shell the type su and hit enter. If the prompt change from $ to # you have root access
Sent from my LG-P990 using xda app-developers app
bitdomo said:
If you got your phone rooted or want to test it run adb.exe shell the type su and hit enter. If the prompt change from $ to # you have root access
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
What is likely to be the problem if it says SU permission denied?
If you are on stock, that means that you have no root access. If you have cm10 or cm10.1 you have to enable adb root access somewhere in the settings. I am sorry but I can not tell you at the moment where to enable it because I am on stock right now.
Sent from my LG-P990 using xda app-developers app
kt-Froggy said:
It's Android Debug Bridge. Basically, it's a command line interface from your PC to your phone. Think of a terminal emulator that you run on the phone itself. ADB is pretty much the same, but from a PC. It is part of Android SDK. You can also find it included in many installation packages posted here on XDA, e.g. CWM recovery. There is an executable and a couple of DLLs.
P.S.: TrymHansen beat me to it...
Click to expand...
Click to collapse
Thanks Bro for this information
guys I finally have been able to root mu atrix hd on jb . this is what worked for me http://forum.xda-developers.com/showthread.php?p=35905543#post35905543
Did you have partial root previously? If you didn't, a new thread was warranted. If you had partial root, why create a new thread?
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app. i was only able to invoke a root prompt. i looked all over the internet not just the xda forums. i tried mattigriffs root restore. i typed into a command prompt for several hours each day.. all i ever got was a root prompt in adb shell. no prompt on the phone emulator. this is the only page that has worked for me. i noticed right away that the code was written differently than any other that i tried. also the su used is different(it is described as wide open) any way because of this i felt that others who were /are in the same boat. no root. may be able to get root back. I hope that answers your question. have a great day! .
Simple yes or no would have worked. I was hoping that by chance someone was stating that they didn't have root previously and were able to obtain root using this method.
Someone tested if it works on 4.1.1 official without prior recovery Boodoo ota?
Sent from my MB886 using xda premium
ashraf sharif said:
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app.
Click to expand...
Click to collapse
Thats what happened to me as well
Would this work if i havent rooted my device prior tho official jb update
Sent from my MB886 using xda premium
My question too any idea
Sent from my MB886 using xda premium
sickkside13 said:
Would this work if i havent rooted my device prior tho official jb update
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
If I wasn't at work I would try it.
Lol me 2. I bought the phone online but it already came with jb i didnt knew the bootloader was locked .
Sent from my MB886 using xda premium
I think what that is fake
Sent from my MB886 using xda premium
i am no expert. and from my reading the forums. the consensus is that if you lost root after the upgrade then you have a chance of regaining it. this method was not meant as a root for atrix hd. but it worked for me. one thing that helps is the abilithy to invoke a root prompt in adb shell. i had a su-backup in /system/usr/we-need-root. ,/su-backup; su i was able to achieve shell root only until today. the the commands used are not identical to the ones i have tried for the past 11 days and the su used is described as 'wide open' whatever that means. Another thing i noticed was that the instructions said to download the su from the play store and update the binary while still in adb shell. , instead of rebooting. when i did this the binary finally gained root.I tried alot of methods none worked except for this one.i was not expecting this to work but it did. I dont know why. all i know is it worked for me. if you choose to try this . best of luck and i sincerely hope it works for you too.
This is gonna sound dumb but, how do I "log in to ADB" (Step 2)? I got the same problem u had and am trying to figure this method out.
Sent from my MB886 using xda premium
i got the shell prompt working with these commands found on this page http://forum.xda-developers.com/showthread.php?t=1911261
Code:
adb shell:
$ cd /system/usr/we-need-root
$./su-backup; su (that is a semicolon immediately after the ./su-backup)
# mount -o remount,rw /system
(do what needs to be done)
#exit
... su-backup must have permissions as such: (get permissions by typing this into adb shell: ls -l /system/usr/we-need-root ) If you get an error, than this specifically won't work for you.
Code:
Required su-backup permissions for manual root restore
$ ls -l /system/usr/we-need-root/su-backup
-rwsr-sr-x root ... basically, if you can find a su-backup with proper permissions (and cannot restore root with voodoo or supersu), you can manually use that to repair your root access configuration. Maybe this is well known... but to those who don't this could be useful.
Thanks
Man, I cannot figure this out for some reason.
Sent from my MB886 using xda premium
logging in to adb
cmdru1980 said:
This is gonna sound dumb but, how do I "log in to ADB" (Step 2)? I got the same problem u had and am trying to figure this method out.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
download java developement kit and android sdk
the sdk has a section called tools where you will find fastboot and adb unzip the files and install the drivers.your first cmd will be cd or'change directory" to wherever the adb folder is. then type adb shell. this should restart the daemon. good luck
This is what I get.
Sent from my MB886 using xda premium
Thank you, Ashraf! I think I got it. I really appreciate it!
Sent from my MB886 using xda premium
I am confused
Sent from my MB886 using xda app-developers app
adolfo778 said:
I am confused
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Yeah I'm confused now as well. If the people here did not have partial root to begin with and were running stock Jelly Bean firmware and then went through these steps to get root access, this needs to be made more clear. If these are users that already had root access from a previous attempt but temporarily lost it during the upgrade process, that should be clarified and merged over into another thread and perhaps edited into the first post.
I am using V4 kernel (http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958) on stock MRA58N with encryption disabled.
I cannot change resolution using
Code:
wm size 720x1280
after su. It gives the following error:
"Can't connect to window manager; is the system running?"
Do you have any ideas?
and why do you want to connect to windows to do it? there are apps that do it for you, or you can use a terminal emulator app on your phone as well.
simms22 said:
and why do you want to connect to windows to do it? there are apps that do it for you, or you can use a terminal emulator app on your phone as well.
Click to expand...
Click to collapse
I am actually using the terminal emulator. I have also tried the apps in the app store. They don't change anything either.
kolpa06 said:
I am actually using the terminal emulator. I have also tried the apps in the app store. They don't change anything either.
Click to expand...
Click to collapse
i use this one, resolution changer https://play.google.com/store/apps/details?id=com.nomone.resolution_changer it works, and works well. unless you dont have root..