ok so adb is installed and working however when I do "adb shell" I get $ not # and permission denied on everything I do. Phone is rooted via VISIONary, debug on, adb recognizes device and "ls" command gives proper read/ logcat works, any help would be AWESOME!
please don't be asses I would have posted this in the [SOLVED][ADB] Won't install correctly for my G2 thread but it's locked....
thanks in advance
Did you type "su" after adb_shell?
Yes and it just hangs...
Sent from my T-Mobile G2 using XDA App
Ok so I guess this one falls under the age old "have you tried turning it off and on again" method of dealing with windows... root access achieved.
Thanks for help KShatzkes....
Sent from my T-Mobile G2 using XDA App
Related
Hy,
i try to get the 'adb root' working but i get this msg 'adbd cannot run as root in production builds'
My desire is rooted by Unrecovered 3 and i installed the new Superuser app. I am S-OFF, lates busybox is running and su in adb shell works. but i don't know why adb root didn't and what to do...
asked google, tried some of the 'answeres' -> nop
Its my first post but i am not a totaly newby
If someone knows what i have missed or have an idea, you are wellcome
Edit:
Ok, my fault - dont understut what "adb cannot run as root in production builds" means...
Have to be in the recovery, not booted up to Android (production build),
in recovery adb starts automaticly as root...
could be closed, thx
Have you got USB debugging enabled?
Mike
Sent from my HTC Desire using XDA App
Yepp is on
I'm not sure what the command 'adb root' does, but have you mounted system, data etc....
Sent from my HTC Desire using XDA App
Is mounted, and everythink i whant to do works exept root for adb.
I like to try out the Android Commander, but it wont get root.
Superuser App asked me and I gave it the root permission but i have checkt out that i have no root for adb. I dont undersant why. Dont noticed it till yet cause did everything with Terminal Emu on my desire, su - remound ops ... everything works. As i understand 'adb root' should restard adb with root permision so you can use the privileged adb commands and that seams to be necesary for android commander to do his job.
Any Ideas why it dont work?
So I 'm getting brave and decided I want to learn more about modding so that means I need to know at least the most basic of ADB commands.
Well I set up the Android SDK several weeks ago and to my best knowledge it was/is working i.e. from the command window (I'm using Win 7 so I use Shift-Right click to access in the Android sdk tools folder) I can type
adb devices
and my phone shows up.
From there I can type
adb shell
Now here is where it gets wonky
I can't use any adb commands or else I'll get an
"adb: not found" error
I can use the -ls command and a2sdcheck commands without any issues. I can even use the reboot and reboot recovery commands ONCE I don't use ADB in front of it.
So simple commands such as adb push/pull is off limits.
I have also tried in recovery mode but the same thing happens.
I'm sure I'm just missing something small but this is turning out to be really frustrating
And yes I do connect with Charge Only and USB debugging is checked.
Thanks in advance for any help
Sent from my PC36100 using XDA App
I could be wrong, but once you type adb shell I think you have to grant it Super user permission from the phone.
I just read the the SU log and didn't see a request resembling anything from adb or my computer. I also didn't notice a prompt to do so but wasn't really paying attention. I need to check on that but if someone else can clarify or tell me how to grant access that would be great. Thx for the response
Sent from my PC36100 using XDA App
Reconnected my phone and typed adb shell and there was no prompt for SU permissions. I'm thinking this may not be applicable or else you wouldn't be able to connect adb in recovery mode right?
Sent from my PC36100 using XDA App
Here is a tut on using adb. ADB Basics
I clicked on your link and it's taking me to a scanning app. Is that correct?
Nvm got it now
Sent from my PC36100 using XDA App
No it should take you to a thread here in XDA about ADB basics. That's where it takes me. Here try this: http://forum.xda-developers.com/showthread.php?t=694250
I found it in the development section in one of the stickies called
HTC EVO helpful/popular threads (Look here First!)
Babysitting my daughter right now so can't really read that link. I'm pretty sure I've read it before though.
Sent from my PC36100 using XDA App
Ok sorry I couldn't be more help. I am sure you are missing something very small because it sounds to me like it should be working. Make sure you have the right adb driver installed.
Moved to Q&A. This isn't development
Thx pulsar for the move. Sorry about that.
Housry thx for all your input.
I did read that link before and there was a link that confirmed that my ADB is set up correctly.
At the very first cmd prompt I can do adb devices and see my phone.
Then I can type adb shell and I get the # prompt
From there I can't issue anymore adb commands or else I get "adb: not found" error
I can issue reboot or reboot recovery commands BUT without adb in front of it and my phone will respond accordingly.
I can use the ls commands and search the subdirectories. Pushboot even works when I need to change my bootanimations. All this leads me to believe that adb is indeed set up correctly including the drivers so why doesn't the other adb commands work?!
This is really frustrating because I can't even begin to experiment with ADB if I can't get the most basic commands to function.
I know it's probably something small I'm missing and I hope someone will be able to point me in the right directions. Thanks again
Who knows, maybe this is a good thing. I might be able to get in all kind of trouble with my phone otherwise.
Wow on a whim I switched out the USB cable and now everything is working great. Geez.
Sent from my PC36100 using XDA App
ok, you are making a simple yet solvable mistake:
once you type adb shell, you are inside the phone's linux terminal. of course, your phone doesnt have adb in it. a shell is a great tool, and is used very, very often to diagnose problems, make stuff, incorperate stuff, test stuff. if you are in a shell, just type
exit
to get back out. then your adb commands should work.
I apologize if this is already answered somewhere. I searched everywhere and could not find anything, but I might be using the wrong wording.
Anyways I am attempting to root my G2. I have managed to get adb onto the computer and it recognizes my phone. However, the next step in the wiki says to:
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*​
However, it gives me error messages such as 'adb' is not recognized. I'm sure I am missing stupid but I cannot figure it out. Thanks in advance.
Just use visionary, it is much easier. Click temp root and when it is done perm root
http://android.modaco.com/content/h...m/320722/19-nov-r14-visionary-one-click-root/
Sent from my HTC Desire using XDA Premium App
I don't trust visionary. I want to go about this the safest way which is the gfree method.
Sent from my T-Mobile G2 using XDA App
Make sure that the adb (and other stuff tha got installed) is in your PATH environment, or cd to that diectory and work from there.
Sent from my HTC Vision using XDA Premium App
o0olove said:
I don't trust visionary. I want to go about this the safest way which is the gfree method.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I used visionary and it worked just fine, but you do what you feel best with
Sent from my HTC Desire using XDA Premium App
bradley_e_smith said:
Make sure that the adb (and other stuff tha got installed) is in your PATH environment, or cd to that diectory and work from there.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I checked the path a few times because I thought that was the problem. However, it all looks good. I'm going to try on another computer tonight and see if that helps.
Did you make sure that all the necessary drivers were installed?
When you type 'ADB Devices' does it show your phone?
I used visionary and terminal emulator and haven't had any problems at all.
_________________________________
Sent from my CM7 T-Mobile G2 using XDA app
tazz9690 said:
Did you make sure that all the necessary drivers were installed?
When you type 'ADB Devices' does it show your phone?
Click to expand...
Click to collapse
Yes it shows my phone when I type 'ADB Devices' That's what's causing my confusion. I've reinstalled all the drivers that are needed. From what I am seeing it SHOULD work.
So I just set up ADB (I THINK) can someone tell me if I did it correctly or not? When I typed in "adb devices" on the cmd thing a bunch of stuff popped up. After watching a video the guy said type "adb shell" for to test to see if it works and I got a msg saying "adb server is out of date. killing... *daemon started successfully"
So is my ADB set up properly so I can now begin rooting??
I dont recommend ADB try using this method.
http://forum.xda-developers.com/showthread.php?t=928160
Sent from my HTC Vision using XDA Premium App
what's wrong with ADB??
I would at least have it set up in case you need it before you root. It might save you from bricking (it has for me).
It doesn't sound set up correctly. When I run adb devices, it says the serial number, nothing else.
Sinistah_ said:
what's wrong with ADB??
Click to expand...
Click to collapse
ADB isn't required to root, and if you're having troubles and have no other need for the SDK or ADB, it can be a lot of unnecessary work.
for awhile it said it was incorrect or sumthin when I'd type "adb devices" into the cmd. Then when I messed with the path a bit and when I typed "adb devices" again, all this stuff popped up. Then I did the "adb shell" and that last thing popped up. What should I do??
martonikaj said:
ADB isn't required to root, and if you're having troubles and have no other need for the SDK or ADB, it can be a lot of unnecessary work.
Click to expand...
Click to collapse
so with this said, can I still use the method shown on wiki to root or do I have to do it the way with Visionary/Gfree??
Sinistah_ said:
so with this said, can I still use the method shown on wiki to root or do I have to do it the way with Visionary/Gfree??
Click to expand...
Click to collapse
I rooted my MyTouch4G with visionary/gfree/terminal emulator. No adb required but its a lifesaver if your phone can't boot!
well now I'm confused on what to do... Do I continue trying to fix this ADB problem or do I just do this other method everyones mentioning.
Sinistah_ said:
well now I'm confused on what to do... Do I continue trying to fix this ADB problem or do I just do this other method everyones mentioning.
Click to expand...
Click to collapse
They really aren't as separate of methods as you think. Every command you enter in ADB can be done by manually moving files into the proper locations, and executing commands via the Terminal Emulator app in the Market instead of the command window (via ADB) on your computer.
So when using the wiki instructions, instead of using cmd commands I use terminal emulator instead??
Sent from my T-Mobile G2 using XDA App
How am I supposed to do the first step on the wiki guide without abd??? I don't get it.
Sent from my T-Mobile G2 using XDA App
I am currently in the process of rooting my G2 and when i have to enter this command, (adb shell chmod 755 /data/local/tmp/* and adb shell /data/local/tmp/psneuter) i get no such file or directory everytime. All other commands enter in without a problem. What is chmod 775 anyway. it is the only thing not previously included in the rooting process. Can anyone please give me some feedback on what is going wrong here
thanks
What ever you are doing stop now.
You're doing that the hard way. Here's what u do goto theunlockr.com and then click how to's, then goto the g2 picture then u want to do the how to get temp root first then once that is completed do the permanent root tutotrial. Everything on theunlockr has a video and text so u can't f up.
My best wishes and if u need help like asap jus send a pm or email me [email protected] gmail
gamestar21 said:
I am currently in the process of rooting my G2 and when i have to enter this command, (adb shell chmod 755 /data/local/tmp/* and adb shell /data/local/tmp/psneuter) i get no such file or directory everytime. All other commands enter in without a problem. What is chmod 775 anyway. it is the only thing not previously included in the rooting process. Can anyone please give me some feedback on what is going wrong here
thanks
Click to expand...
Click to collapse
What guide are you following?
Sent from my T-Mobile G2 using XDA App
I'm stuck in the same place. I get operation denied every time...
Please help
A lot of people say its because you haven't set up the path correctly to the abd folder or haven't put the root files in the right abd folder.
Sent from my HTC Vision using XDA Premium App
Where to find 'chmod' answers
I had to exchange my G2. The one T-Mo sent is running Gingerbread(?) ver 2.3.4
I've been to theunlocker.com and in the procedure to downgrade so that I can root, http://theunlockr.com/2011/07/22/how-to-downgrade-a-gingerbread-t-mobile-g2-so-it-can-be-rooted/ two of the steps are to enter in terminal:
chmod 777 /data/local/tmp/fre3vo
and
chmod 777 /data/local/tmp/misc_version
When I do this I get 'chmod' is not recognized as an internal or external command, operable program or batch file
I have spent several hours in the forums and can't find where I've gone wrong or where to find 'chmod'
Someone please help me
SOLVED, use this link http://forum.xda-developers.com/showthread.php?t=1178912 and also (from one noob to another) it helps to type 'adb shell chmod....' if that is one of the issues you're having
You don't seem to be in the directory that you have adb installed. Change directory to there and you should be good
Sent from my Bulletproof G2
I've searched my entire hard drive, both mac & xp. It's not there. I've downloaded the SDK twice, I can't find it anywhere.
Sent from my T-Mobile G2 using XDA App
noflopscott said:
I've searched my entire hard drive, both mac & xp. It's not there. I've downloaded the SDK twice, I can't find it anywhere.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
On my xp it installed to c:/program files/android/android-sdk/platform-tools/ automatically, maybe try there. If you can't find it try downloading just the adb program and putting it in your adk platform-tools folder. You did also download the android development package right?
Sent from my Bulletproof G2
I went ahead and downloaded the ENTIRE sdk, from 1.5 to 3.3, did a hard drive search, still nowhere to be found :-c. Any other ideas?
Sent from my T-Mobile G2 using XDA App
noflopscott said:
I went ahead and downloaded the ENTIRE sdk, from 1.5 to 3.3, did a hard drive search, still nowhere to be found :-c. Any other ideas?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Are you even installing the SDK? Follow this guide to get ADB up and running: http://forum.xda-developers.com/showthread.php?t=865685
Sent from my HTC Vision using XDA App
This method worked http://forum.xda-developers.com/showthread.php?t=1178912
Followed it letter by letter and I was downgraded from 2.3.4 to 2.2 in just a few minutes :-D