I'm attempting to get webtop from HDMI to work and attempted the install.bat thing but still nothing so I went to
http://forum.xda-developers.com/showpost.php?p=12580345&postcount=634
I can push those files but can not SU in adb shell
I am able to SU in terminal on my phone but not the adb shell
What can I do to get this working? I'm not sure what info you need from my phone to better assist but ask.
I'm running 2.2.2 rooted with gingerbreak I tried to reroot but no go don't think i need too and superuser app is there and works since i use TB and bloat freeze
I just get permission denied thanks for any help. I have googled this but can't find anything.
could you maybe have a problem with ADB itself? Maybe try reinstalling your SDK and setting up ADB again? You said you already tried to re-root and that didnt fix the issue. Maybe someone with more knowledge of ADB could provide more assistance...
I managed to get it working. I noticed when I had my screen set to not turn off i received a message to all access and I granted SU now it works fine.
Related
ok so on most roms this happens. i need a SU request but my phone freezes obn a black screen and on the top in gray it says SU request. i wait paciently and maybe 1-2 mins later is asks to FC because its not responding. is there a fix or what am i doing wrong. usb debugging is on and so is install nonmarket apps idk wtf im doing wrong or if somthing is just not working. any input??
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Marisa said:
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Click to expand...
Click to collapse
yes same thing happens to me
plug in your phone
goto your android sdk tools
and input adb shell
now go back to your phone and try it while still plugged
thats what i have been doing...
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
WalkingTaco said:
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
Click to expand...
Click to collapse
Are you getting the same crshes and things, but when you do the adb shell # pops up instead of $?
whenever i do adb shell I get #, so that means SU is already activated, but it's actually not on my phone, so i have no idea what's going on and no one seems to know how to fix it.
no. my Su permissions always force close after a minute of black screen. there is a fix posted above but my nerd level is not high enough to.infer the rest
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know the exact command prompt setup, I'm running linux. However, when you originally rooted your phone you used the Android SDK correct?
With your phone plugged in, and USB Debugging enabled on your phone (Settings -> Applications -> Development -> USB Debugging) Open command prompt and get to the tools directory you used during rooting, I don't know where you installed it, so I cannot guide you through that part. If you used Ivan's guide http://forum.xda-developers.com/showthread.php?t=647707 it's probably best to refresh yourself there.
Once you've found your SDK /tools/ in command prompt, it should be as easy as running the code I mentioned earlier
Code:
adb shell
$su
in the command prompt.
The superuser prompt should show up on your phone, tell it to allow it and it should work without fail until you flash a new ROM that has the bug.
thanks very much. I used Ivans guide. I rooted it yesterday when o got my replacement from Verizon in store. I had been using the 2.1 leak on my old one and complained in store for thirty seconds. they didn't even look at it gave me a replacement in ten minutes
Sent from my Eris using the XDA mobile application powered by Tapatalk
Rock out thanks for the Super Help
Okay, my Atrix is rooted and USB Debugging is on, but when I try to remount adb, it says "remount failed: Operation not permitted". Since I can't get adb shell to the # to come up, I type "adb shell su" and I get a Permission denied. I originally rooted with SuperOneClick and enabled sideloading with it and today I rerooted, unrooted, then used DesignGears' new root script to reroot and clean up SuperOneClick's root. Still no adb root access. I have TitaniumBackup, Superuser, and RootExplorer installed and even downloaded Root Checker to check if i really had root. I've spent almost all day looking this up and the closest I've found is the thread that talks about adb showing the device offline with the fix of copying over another adbd to the sbin folder(which I also tried) and adb still doesn't seem to recognize my root. The only time I can get the # prompt is when I do a shell root with SuperOneClick, but that is just a temporary root. Is anyone else experiencing this?
Edit: forgot to mention that adb works fine when I connect my NexusOne, so it's probably not the computer.
So I don't use adb push/install all that often but since I deleted mobile hotspot on my phone (I thought I had it frozen but apparently I didn't) I cannot upgrade my system.
I am rooted, and have tried installing from an emulator on the phone (and shell) as well as installing from and adb on the PC.
When I try to adb remount I get the following error:
remount failed: Operation not permitted
I have re-rooted thinking that an early version of root wasn't rooted for adb and also hoping that would let me install via shell. How can I get Mobile Hotspot back on?
Ok, so I was able to run a mount from terminal and copy the files and get the upgrade to go through.
So does anyone know why adb remount doesn't work? Is it because of the Moto Blur?
I have my phone connected to my laptop via the USB cable and the ADB is able to identify the device. When i run adb devices it returns the phone in the list of connected devices. Running the command adb shell now gives an error stating:
reloc_library cannot locate 'fdatasync'
Infact running any command on the terminal emulator installed on my phone also returns me the same error.
Has anyone faced the same problem or has any pointers to a solution to it?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
anuj142003 said:
I have my phone connected to my laptop via the USB cable and the ADB is able to identify the device. When i run adb devices it returns the phone in the list of connected devices. Running the command adb shell now gives an error stating:
reloc_library cannot locate 'fdatasync'
Infact running any command on the terminal emulator installed on my phone also returns me the same error.
Has anyone faced the same problem or has any pointers to a solution to it?
Click to expand...
Click to collapse
Do you have busybox installed? It seems as if the /bin directory doesnt exist or contain the proper files. Thats about all i got as of now
I have not been able to install busybox on my system. I have tried all possible versions and all possible ways of getting it installed but nothing works.
whats meant by "nothing works"? in fact you clearly installed something on your phone so it cannot start a shell anymore, did you reboot after you played around?
I have not been able to install busybox on my system. I have tried all possible versions and all possible ways of getting it installed but nothing works.
Click to expand...
Click to collapse
Well that is more than likely the issue, are you rooted? And you've tried the busybox installer from the market?
Sent from my GT-I9100 using Tapatalk
When i say "nothing works" what i mean is i have tried various busybox installers on the market and none of them seemed to work. Everytime i get the error stating that BusyBox could not be installed.
I have tried rebooting multiple times as well.
elesbb said:
Well that is more than likely the issue, are you rooted? And you've tried the busybox installer from the market?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yes, my phone is rooted and yes i have tried the busybox installers from the market.
I have searched through lot of posts on xda; able rooted device copied su binary and make root work by sdb shell.
Able to get #prompt on adb shell. But when i install superuser.apk; try to run from UI, i see an error.
"There was an error installing superuser"
What am i missing here. Sorry if a repost. quick help would be appreciated
TIA