Develop Bugs

[Q] Cant get ADB to work!!!

Ok so i used adb to root my phone when i first got it. set up the sdk tools file and all of that, however im having trouble trying to push a framework-res file back to my phone. actually no adb commands will work. i keep getting this message "/sbin/sh: adb: not found" can someone pleaseeee help me figure this out

chingy51o said:
Ok so i used adb to root my phone when i first got it. set up the sdk tools file and all of that, however im having trouble trying to push a framework-res file back to my phone. actually no adb commands will work. i keep getting this message "/sbin/sh: adb: not found" can someone pleaseeee help me figure this out
Click to expand...
Click to collapse
What exactly are you doing? You're not in the shell are you? If so, exit the shell and do it at the dos command prompt.

chingy51o said:
Ok so i used adb to root my phone when i first got it. set up the sdk tools file and all of that, however im having trouble trying to push a framework-res file back to my phone. actually no adb commands will work. i keep getting this message "/sbin/sh: adb: not found" can someone pleaseeee help me figure this out
Click to expand...
Click to collapse
wrong section. did you cd to the tools folder inside sdk folder

Make sure you have the SDK installed and when you open up Command Prompt type in "cd C:\Program Files (x86)\android-sdk-windows\tools" Obviously programs folder would be wherever you have your SDK located. After you type that in, type ADB Shell and you should be in.

Blindlabel said:
Make sure you have the SDK installed and when you open up Command Prompt type in "cd C:\Program Files (x86)\android-sdk-windows\tools" Obviously programs folder would be wherever you have your SDK located. After you type that in, type ADB Shell and you should be in.
Click to expand...
Click to collapse
it sounds like he's already in shell which he souldn't be. he needs to just be in a command prompt. you can't use the adb push command when in shell

This result from the command "adb" not being found.
Two ways to fix, either go to the folder with the adb executable in it, right-click, "Open terminal here." And then "adb" will work.
Second way is to copy the adb executable to /usr/bin. (I think xD) (One of the */bins.)
Good luck!

so im not supposed to run the whole cd\ cd sdk cd tools... all that stuff?

chingy51o said:
so im not supposed to run the whole cd\ cd sdk cd tools... all that stuff?
Click to expand...
Click to collapse
Oops, that's my bad. I assumed you were in Linux. If you are windows, then follow that other guy's instruction. (cd to blah blah) but if Linux thenfollow mine.

Moved to Q&A. Please do not post questions in the Development thread.

[Q] Help rooting with Mac OS X

The guides/walkthroughs seem to cover windows but I use OS X...are there any guides/walkthroughs to root a G2 using OS X?
I'm getting frustrated

Which guide are you trying to follow? Most of them require/mention adb, but the android SDK is available for Mac, so you should be able to get adb.

It should all work the same on a Mac. All you're doing on the PC/Mac end is using adb to send stuff over to your phone. The adb guide at http://forum.xda-developers.com/showthread.php?t=865685 has some stuff in there (which I still need to work on) about getting adb working on the Mac (see later replies).

dadewy said:
Which guide are you trying to follow? Most of them require/mention adb, but the android SDK is available for Mac, so you should be able to get adb.
Click to expand...
Click to collapse
I am following this guide
steviewevie said:
It should all work the same on a Mac. All you're doing on the PC/Mac end is using adb to send stuff over to your phone. The adb guide at http://forum.xda-developers.com/showthread.php?t=865685 has some stuff in there (which I still need to work on) about getting adb working on the Mac (see later replies).
Click to expand...
Click to collapse
I have got got adb working, I put the android_sdk folder at the root of my macs hard drive. I figured out I have to put "./" infront of adb to execute commands, and I have gotten it to recognise my device.
But where I am stumped is, where do I unzip the temp and perm root folders to, onto the desktop or into somewhere in the android sdk folder?
Also do need to have two terminals running, 1 navigated to adb and the other to the unzipped folders?
Or do I do something completely different?

bobbytomorow said:
I am following this guide
I have got got adb working, I put the android_sdk folder at the root of my macs hard drive. I figured out I have to put "./" infront of adb to execute commands, and I have gotten it to recognise my device.
But where I am stumped is, where do I unzip the temp and perm root folders to, onto the desktop or into somewhere in the android sdk folder?
Also do need to have two terminals running, 1 navigated to adb and the other to the unzipped folders?
Or do I do something completely different?
Click to expand...
Click to collapse
I think the common way is to unzip or move the files to your Android_sdk/tools folder so that adb and the files are in the same directory.
Another way would be to use the full path in the adb command:
adb push /users/bobby/desktop/gfree_unzipped/gfree /data/local/
you should change it to match your actual directory structure
The slick way is to add android_sdk/tools to your path so that it will work at any direectory level.
Either way, you should only need 1 terminal window (Unless you are trying to verify you have radio s-off- the last bit that starts with "stop ril-daemon")

gee one said:
I think the common way is to unzip or move the files to your Android_sdk/tools folder so that adb and the files are in the same directory.
Another way would be to use the full path in the adb command:
adb push /users/bobby/desktop/gfree_unzipped/gfree /data/local/
you should change it to match your actual directory structure
The slick way is to add android_sdk/tools to your path so that it will work at any direectory level.
Either way, you should only need 1 terminal window (Unless you are trying to verify you have radio s-off- the last bit that starts with "stop ril-daemon")
Click to expand...
Click to collapse
That helped me out perfectly, I just rooted my G2, YAY!
Thank you everyone for your help

[Q] ADB help!!

So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?

HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?

DressedUpPanda said:
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
Click to expand...
Click to collapse
The PATH issue, relates to ADB, if you are running into errors like:
'adb' is not recognized as an internal or external command
Click to expand...
Click to collapse
When executing ADB commands that is your issue, it can be resolved by adding the path where ADB lives to either your user or system PATH in Windows. The PATH is irrelevant if you are running ADB from the folder where the ADB files live.
The other (common) issue is drivers, where ADB is working but won't see your device. Do you see an "ADB Device" or similar with a yellow icon in your device manager when your phone is connected to your PC? If so you don't have the correct driver loaded. The only reason you install HTC Sync is to load this driver but the driver can also be loaded separately.

Sorry to hi-jack this thread, and since I'm new to adb I might as well use this.
I have adb running, did the file paths and everything. I'm just trying to test it out, since I'm already rooted using visionaryr13 as well as s-off. Went back and gfree over that, and I've also verified through terminal emulator on my phone, but I'm just testing my skills with adb and failing miserably. I Have d/l the verify file, and unzipped in a folder inside my downloads folder I might add.
When it says:
"
VERIFY (using "gfree_verify")
Now you can try using a new SIM card to verify that it worked.
In addition you can use gfree_verify to verify the state of your locks.
Download gfree_verify.zip from gfree_verify_v01.zip
ON YOUR PC:
Unzip gfree_verify_v01.zip to a place on your computer. Navigate to where the file is on your computer, and type:
$ adb push gfree_verify /data/local
"
I'm having a problem with the navigate to where the file is on your computer and type. I have cmd open, and have tried everyway but the right way to push this through. This is the error I'm getting.
cannont stat 'gfree_verify': no file or directory
EDIT: I got it and I'm sure everyone is laughing at this idiot. So in the cmd prompt you have to navigate to where you put the folder, then push the file to your phone, DUH!

OK, stupid question number two, since I answered number 1.
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?

mrbmg said:
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
Click to expand...
Click to collapse
Type "exit".

ty ty.
Ok so I updated something in adb and it's not working. LOL, well restarted, and now the sdk manager is updating some more stuff so hopefully that is the reason I was not getting in.
EDIT: everything is working now.
Ty stevie, really appreciate all your hard work helping us noobies man!

steviewevie said:
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
Click to expand...
Click to collapse
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'

DressedUpPanda said:
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
Click to expand...
Click to collapse
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.

steviewevie said:
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
Click to expand...
Click to collapse
Ok well here is the path that i have set up.
- C:\AndroidSDK\tools;C:\AndroidSDK\platform-tools
I saved the file right to my "C" drive so thats why i didn't go to the program files. I also changed the name of the folder so it was easier to type.
Edit: I got it to finally recognize my device. I went back to my path and found that i had spaced in between my ';' and 'C:/' so thank you very much Stevie on making me double check it!!!

Android-SDK?

Ok, long story short... I had to completely wipe/format my hard drive on my computer so I lost ever single thing I had.
I completely forgot everything I needed to install for my phone as far as things like ADB. I think it was Android-SDK but I really can't remember.
Can someone help get me going in the right direction again? Many [email protected]@!!

Yeah, you need the android sdk. If all you're after is adb, then I'm sure someone around here has posted a download link to just those files. If you can't find them, then download the sdk and use the sdk manager to download and install the platform tools. For a full install of the sdk with Eclipse and ADT, you'll need to consult Google's install docs on the android developer site.

myersn024 said:
Yeah, you need the android sdk. If all you're after is adb, then I'm sure someone around here has posted a download link to just those files. If you can't find them, then download the sdk and use the sdk manager to download and install the platform tools. For a full install of the sdk with Eclipse and ADT, you'll need to consult Google's install docs on the android developer site.
Click to expand...
Click to collapse
See, I can't remember what I had.
I know it was an android-sdk folder with a few sub-folders like tools in it. I had to browse to that directory when I pushed something via ADB.
So I guess I just need to find and install the android-sdk? I'm not even sure what Eclipse and ADT is..

http://developer.android.com/sdk/index.html
Download the sdk. Adb was moved to the platform-tools folder, so you can run your adb from there, or move it to the tools folder.

Thank you!
I appreciate the help guys

Rippley05 said:
Thank you!
I appreciate the help guys
Click to expand...
Click to collapse
You're welcome.

teh roxxorz said:
You're welcome.
Click to expand...
Click to collapse
I hope I'm doing it right. I unzipped the folder, clicked on tools and read where it said adb was moved. Then I clicked on the android guy (sdk and avd manager) and now it is installing a messload of stuff.
After it's done, I should be able to use ADB but instead of going to c:\android-sdk-windows\tools\ like I used to do, I'll have to change the "tools" to platform-tools correct?
EDIT: I feel liek it is downloading a lot of stuff I don't need =p

Rippley05 said:
I hope I'm doing it right. I unzipped the folder, clicked on tools and read where it said adb was moved. Then I clicked on the android guy (sdk and avd manager) and now it is installing a messload of stuff.
After it's done, I should be able to use ADB but instead of going to c:\android-sdk-windows\tools\ like I used to do, I'll have to change the "tools" to platform-tools correct?
EDIT: I feel liek it is downloading a lot of stuff I don't need =p
Click to expand...
Click to collapse
That is correct, and I also just rename the folder to android, cuz typing all that is a pain.
And you can do that, or copy the adb items from platform-tools into the tool folder itself; tis what I did.

Alright, Windows 7 is different and kinda irritating.
All the SDK stuff went into a folder "downloads" and I let everything install, but I can't seem to find it when I run the command prompt. It was much easier in Windows XP.

If anyone is using windows 7 , could you give me the commands you use to get to the directory. I get an invalid path no matter what I type.
Should I move the SDK folders out of my downloads folder and put them on my desktop?

I put it on the root of C. Then I run cd C:\android-sdk\platform-tools. I think you need HTC sync installed as well.

Rippley05 said:
If anyone is using windows 7 , could you give me the commands you use to get to the directory. I get an invalid path no matter what I type.
Should I move the SDK folders out of my downloads folder and put them on my desktop?
Click to expand...
Click to collapse
Its easier from the desktop

OK I'll install HTC sync. That should still be on my phones SDcard right?
The problem is, I don't know what commands to enter in the command prompt to get to the different directories on my computer. If I move it to the desktop, what commands will get me there?

dglowe343 said:
I put it on the root of C. Then I run cd C:\android-sdk\platform-tools. I think you need HTC sync installed as well.
Click to expand...
Click to collapse
You don't need htc sync, just the hboot drivers.

Rippley05 said:
OK I'll install HTC sync. That should still be on my phones SDcard right?
The problem is, I don't know what commands to enter in the command prompt to get to the different directories on my computer. If I move it to the desktop, what commands will get me there?
Click to expand...
Click to collapse
the commands would be:
cd desktop/android/tools
1. change android to whatever you named your sdk folder
2. change tools to wherever your adb is located.
Names are case sensitive

teh roxxorz said:
the commands would be:
cd desktop/android/tools
1. change android to whatever you named your sdk folder
2. change tools to wherever your adb is located.
Names are case sensitive
Click to expand...
Click to collapse
Sweet I got it!
I tried to do a ADB remount and got AdbWinApi.dll is missing from my computer. I don't have my phone hooked up tho so could that be it?

Rippley05 said:
Sweet I got it!
I tried to do a ADB remount and got AdbWinApi.dll is missing from my computer. I don't have my phone hooked up tho so could that be it?
Click to expand...
Click to collapse
No prob. If you got that error, you missed it from copying the files; just double check that its there in the folder.

teh roxxorz said:
No prob. If you got that error, you missed it from copying the files; just double check that its there in the folder.
Click to expand...
Click to collapse
Ahh ok, I just moved it and it started but said device not found. I assume that IS because my phone isn't connected.
One more quick question and I promise I'll leave u alone. Whenever I push something with adb I always close the box and just unhook my phone. Is that the right method? Because I see adb is still running on my pc until I end the process with my task manager.

Rippley05 said:
Ahh ok, I just moved it and it started but said device not found. I assume that IS because my phone isn't connected.
One more quick question and I promise I'll leave u alone. Whenever I push something with adb I always close the box and just unhook my phone. Is that the right method? Because I see adb is still running on my pc until I end the process with my task manager.
Click to expand...
Click to collapse
Naw you're fine; yea, it;ll show device not connected if you have nothing connected. I personally leave it open in the command prompt after opening it just in case I go back to it. It'll close once you close command prompt.

Sweet. Thanks again Rox.
I've has that stuff installed since I first got my Hero... been a long time since I had to mess with it..

Adb Problems? Read this.

--This thread is recommended to be viewed on a Pc/Linux (I included you guys too ), OR on your ANDROID-POWERED phone (with XDA or in browser now ).--
--This is for PC and LINUX problems.--
Hallo!
You may have adb errors such as: cannot connect to daemon. This is a common problem beginners commonly forget. Also MAKE SURE you have installed android sdk
If you get adb error like :
adb server is out of date * killing***
daemon still not running
error:cannot connect to daemon
Click to expand...
Click to collapse
That means your device can't be found in adb.
Simply:
1) Make sure USB debugging is on
Found in Settings>Applications>Development
Click to expand...
Click to collapse
2) Make sure you have YOUR PHONES DRIVERS INSTALLED.
They can be installed via HTC Sync.
Click to expand...
Click to collapse
3) Still not working? Instead of using the USB option Charge Only/Disk Drive.
Use HTC Sync USB option.
Click to expand...
Click to collapse
________________________
RUU Problem [May encounter in the future](Thanks miguelca)
--Not for RUU Setup exe.
Out of date daemon error
Click to expand...
Click to collapse
Step 1) Browser to your android sdk folder
Its probably in: C:\android-sdk-windows OR C:\Program Files (x86)\Android\android-sdk (In 64bit edition of windows) OR C:\Program Files\Android\android-sdk
Click to expand...
Click to collapse
Step 2) Enter the platform-tools folder
Its simple just press Platform-tools
Click to expand...
Click to collapse
Step 3) Copy all of the files except: Source.propties, NOTICE.txt, lib, renderscript folder.
Hold Ctrl-A then press the files, then when done right click and press copy.
Click to expand...
Click to collapse
Step 4) Browse to your RUU Folder, and paste the files there.
Enter the RUU folder, right click anywhere press paste (If asks to overwrite press yes.)
Click to expand...
Click to collapse
Step 5) Should be done now!
________________________
[Linux ADB Problems (Thanks Tectas)]
Hallo, now this part of the thread is about linux ADB Problems .
permission denied ?????????
Click to expand...
Click to collapse
If you use Linux and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
[B][I][U][COLOR="DarkOrange"][FONT="Lucida Sans Unicode"]adb kill-server
(be sure the path to the adb directory is inside the .Bashrc file or CD to the right directory)
adb start-server[/FONT][/COLOR][/U][/I][/B]
Afterwards you can exit to normal shell and use it like ever.
[End of thread. Please scroll up or down to read reply's, or to read on ]

One addidonal thing,
if you are an linux user and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
adb kill-server
(be sure the path to the adb directory is inside the .bashrc file or cd to the right directory)
adb start-server
to start the adbd in su context, afterwards you can exit to normal shell and use it like ever.

It's not as trivial as you say. I had the out of date daemon error while trying to update my phone with the 2.3.5 European RUU by football. The solution was to uncompress the RUU and replace the ADB executable and dll's with updated ones from the Android SDK I had installed. It had nothing to do with USB connections or settings. Probably the RUU wasn't prepared for Windows 7 x64 SP1... I guess.
Sent from my HTC Wildfire S A510e using XDA App

Thanks!
Updated the thread.

XDA_h3n said:
Updated the thread.
Click to expand...
Click to collapse
You're welcome!
Thank you for the nice thread, for updating it quickly and for crediting me too.
It's great when several experiences are compiled in a way that might help many other users.
That's what a community is all about.

My trick is Download Vroot on your Pc and it will install everything you need. (Might replace your current Root Manager if you don't cancel the process of it rooting.) Once you connect your phone to your pc with Vroot it's ask you to install a apk just click okay. Once you see the apk installed wait for it to get a green backrground with wire connected image. Then there you go. Sorry for my Bad English. Hope it Helps.