Develop Bugs

ADB not seeing Evo

Sorry if this is a repost. But hopefully someone can help me out. I'm fully rooted, full nandroid unlock.full 100 yeards. Now this morning I was going to do the process for "Permanently replacing your recovery with ClockworkMod Recovery Image"
But for some strange reason, ADB doesn't see my Evo. I tried running "Command prompt" as administrator also and it wasa no go. I typed "adb devices" and my device wasn't listed like it was yesterday before I did a full nandroid Unlock.
Do anyone have any tips on how I can resolve this issue?
If this helps, I running the Bugless Beast Rom.
Thanks

You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.

thanks. I'll give that a try and reply back

Strange thing....before I rooted/flashed a rom I created a Nandroid backup (I think it was stock. It doesn't have Superuser Permission in my list of Apps). Well I reverted back to that nandroid backup and now ADB sees my Evo.
I will flash back to my previous rom and trywhat you posted. Hopefully tat'll work

phatalboom said:
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
Click to expand...
Click to collapse
Yeah, I tried what you suggested and itstill didn't see my Evo. I guess my only option is to revert back, then do the process.

Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.

I'm having same issues and it's not working. My device is not being seen. Do you I have to have the Evo in charging mode or Disk Mode?

chuckhriczko said:
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
Click to expand...
Click to collapse
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.

Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc

timothydonohue said:
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Click to expand...
Click to collapse
Thanks for trying to help me out. But it still didn't work.
toastcfh said:
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
Click to expand...
Click to collapse
What do you mean that I must run adb as root on my pc, i don't know what that mean. Do you mean run it by using the "Command prompt" program?
Also this only happens to me on the Bugless Beast Roms. When I revert back to my 1st nandroid backup that I was using before I flashed any rom, everything worked fine.

Is USB debugging enabled?

CentroniX said:
Is USB debugging enabled?
Click to expand...
Click to collapse
Thanks ...that fixed it! I enabled it typed "adb devices" and it showed up. thanks again!

No problem, glad you got it working! When I first started out I ran in to that trap over-and-over. Now I just make it a rule of thumb to turn it on after flashing and leave it on.
Have fun!

I would have started another thread, but this is basically a similar problem to the one I had at first with adb.
Ok...I was trying to install a rosie.apk that was in a zip format. Long story short, the OP informed me that he made a mistake and provided me the wrong information as to reinstalling the rosie.apk. He was giving me steps to "push it" via adb, instead of flashing it.
No problem to Poster and thanks for help if you reading this . But anyways after all that, When I open up "Cmd" and type anything with adb in front of it...adb devices, adb shell..., i get the message that adb is not recognized as a internal or external command. Before this incident happened i was able to just type "adb devices" and my Evo would show.
Do anyone know how to fix this?
By the way I also tried typing all the commands in the previous posts...and I get the same error message.
**Update** I got it working I had to redo the path. All is good now.
Thanks much!

You need to be in the tools directory of the sdk so cmd can find the adb command.

Having problems rooting

ADB is not friendly to me. I was able to root my g1 with pure ease. I cant get started with adb, I dont know why I cant get $, I've read several guides and I'm just about to give up. I'm running 2.2 on my g2.
I do have a couple of questions:
Are rooting with rage or visionary 14 the only way to root?
Are there any root guides out there that dont require ADB?
ADB is a ****ing pain in the ass to me, especially since I've tried everything and cant get it to work. Also, the drivers that go on Win7 64bit just dont work.
Also when I do have root, can I get android updates?
Any help would be thankfully appreciated. Sorry if I'm a pain in the ass, but I'd like to know if there is an easier way.

I think you need the q&a section
Sent from my HTC Vision using XDA App

This will help u get adb working...
http://forum.xda-developers.com/showthread.php?t=865685

If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.

dictionary said:
If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.
Click to expand...
Click to collapse
while my knowledge of adb isnt stellar, I have run into problems using it. I'm going to try this new link to the guide and see if it works.
Still if anyone knows other solutions, chime in.

Try the guide linked above. The drivers in the HTC Sync package (see the guide) definitely do work on Win 7 64-bit.

Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?

sorry about the ****ty pics

cwis said:
Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?
Click to expand...
Click to collapse
Did you definitely add it to your path as it is suggesting in that window ? If so, I think you may need to reboot to pick that change up.

I did that just in case.
Actually, that path field was empty. So, I added it as is.

look up droid explorer

I made some leeway:
C:\Program Files (x86)\android-sdk-windows\tools>adb shell
$
$ adb push su /sdcard/su
$ adb push su /sdcard/su
$ adb: permission denied
good grief!!!!!!!

I've completely removed visionary before starting this procedure. Did I need temproot before attempting this?
Downloading and installing Droid Explorer. Thanks!
Also, I'm using this guide: http://forum.xda-developers.com/showthread.php?t=834228

No matter what I've done, permission denied.

The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.

ianmcquinn said:
The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.
Click to expand...
Click to collapse
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).

steviewevie said:
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).
Click to expand...
Click to collapse
I did run the commands from my pc. But still permission denied.

cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
"permission denied" is a message from your phone, not your PC.
The $ prompt that you copied and pasted up shows that you were running the commands on your phone. As soon as you do "adb shell", then any commands you are entering after that are going on your phone, even though they're physically being typed on your PC - because your PC has started a command prompt on your phone, as shown by the $ prompt.

cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
Basically, don't start by typing adb shell. The instructions you are trying to follow don't even say to do that anywhere. I highly recommend you reread the instructions very carefully and follow them exactly. Rooting this phone is actually pretty simple if you just do exactly as the guide states. If you don't know what you are doing and mistype something in some of the later steps though, you can seriously screw up your phone...

I think part of the confusion is that the commands listed on the guide all have "$" at the beginning of them, probably because whoever wrote that was using a Linux PC or maybe a Mac. You are actually executing these commands from your Windows command shell so they will look more like:
D:\Android SDK\platform-tools>adb push su /sdcard/su
Click to expand...
Click to collapse
(depending on where you have the SDK installed)
instead of:
$ adb push su /sdcard/su
Click to expand...
Click to collapse
but of course you only need to type:
adb push su /sdcard/su
Click to expand...
Click to collapse
Again these are typed from your windows command shell.

T-mobile g2 root problems, other threads checked.

In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.

Did you do "adb shell" and then you tried more adb commands and got "permission denied" ?
If so, then that's because "adb shell" starts a command prompt session on your phone, and the adb commands need to be run on your PC, not your phone. So don't do the "adb shell" first.

So wait a second, you're saying that the wonderful wiki, either is in the wrong order, or requires me to follow the pc, and phone steps simultaneously? Because im running them from my pc. Which would be implied by my saying im following the wiki. Fyi, i meant the one on the g2, involving rooting the g2, on the xda-dev site. I've done this before, i know how to use adb. this is the first time i have rooted a g2. Don't mean to sound like a ****, but you basically didnt read anything i wrote.

The Wiki isn't in the wrong order. But IMHO it's very confusing that it shows a $ prompt when it shows "adb push" etc, because that makes it looks like it is run on the phone. But it's assuming you're running from Linux/Mac. On a PC the prompt for your adb commands would be C:\ or similar.
The Wiki doesn't tell you to run "adb shell"

So the answer to my question was yes, it works, but i had to wait 5 minutes to post this. I dont understand why there cant be a note that, unless you put adb into your path, cmd isnt going to recognize it unless its in the folder you're using. I feel no need to put a tool that i will use maybe once a year at most into path. also, when i just checked the wiki now, i noticed how the dollar signs had changed to c:/ ha ha. and sorry about the rudeness, at first it just seemed like you were making fun of me.

jenlow said:
Okay, so before i opened the adb shell from cmd, when i would type adb push, i would get adb is not recognized as an internal or external command. so, my solution of putting the adb tools into gfree, should work now once i cd to the gfree folder?
Click to expand...
Click to collapse
That's an issue with your path not being setup properly on your PC. You can adb adb's folder to the path to mean you can run it from anywhere. Otherwise you need to put the gfree tools etc in the same folder as adb, then cd to there and run the commands.
Or if the path is setup properly, cd to where the gfree tools are and start doing your "adb push" etc from there.
I have just edited the Wiki to show a "C:\" prompt for the stuff that's run on the PC, to try and avoid this confusion.

Did it work ?

jenlow said:
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Click to expand...
Click to collapse
the "permission denied" thing... from the phone? Or from the computer? You know you need to be root in order to access the hardware, or at least set the permissions on the hardware to be accessible to your user account....???
And... you DID enable adb on the phone side, didn't you?

I used the Wiki and am now perm rooted. A few tips that may help you since they helped me to get it done. I opened a command prompt and noted the default path that opened. For me it was C:\Users\Ed . I used windows explorer to navigate there and open up the Ed folder and created a new folder in Ed that I named pr. This is where I unzipped both of the gfree zip files...into that same folder. When temp rooting and perm rooting, I simply opened up the command prompt, it opened to C:\Users\Ed and then I typed cd pr then I hit enter. That set me up to input the commands in the right place both times and it worked out just fine.
Another thing that I noticed. After temp rooting, I had to ctrl alt del to open up task manager and close down adb.exe (as noted in the instructions that appeared in terminal emulator). I couldn't load adb again until I closed it down and let it restart itself. When I entered the first command in the perm root process adb started up again by itself and all went well.
Good Luck! It is well worth it. I now have Cyanogen's latest stable build loaded along with the Google apps package that I found online.
Ed

OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.

Root my phone!!! HELP
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!

mannær said:
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
Click to expand...
Click to collapse
None of those apps work with the G2 to perm root without extra steps. And in that case only Visionary. You need to check out the vision wiki page.

Ed thoroughly described how to make it work. I did the exact same thing he did and got it last night.

jenlow said:
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Click to expand...
Click to collapse
What method did you use to root your cliq, and did you still have 3G? I have stock motoblur 2.1 on it now, I have it for a backup phone (got a G2), but I would like to root it.

ADB Question

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.

Unlocking Xoom on a Mac (edit - solved!)

Hey guys, while I'm not exactly new to rooting, it has been quite some time since I rooted my N1 (and that was the only time I've ever rooted anything. I'm now a little lost with the unlock/rooting process. At this point,:
*I have the latest SDK, and I've updated the Platform Tools and added the contents to the Tools folder
*I've connected via USB and I've done the volume-down-power-up combination and have the "Starting Fastboot protocol support" screen.
However, that's all I've been able to do, and I honestly don't know what I'm missing. I can't get the the commands in Terminal to communicate with the tablet. Any assistance that anyone could provide would be greatly appreciated.
THANKS!

You have the Motorola v4.9 USB charging drivers installed?

When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.

Elysian893 said:
You have the Motorola v4.9 USB charging drivers installed?
Click to expand...
Click to collapse
Well I was looking for drivers initially, but then I read in the "how to unlock" thread that someone said drivers werent needed on a Mac. Plus I looked for Mac drivers and couldn't find any, just Windows.

bcgaynor82 said:
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Click to expand...
Click to collapse
Well I'm not sure I'm opening Terminal in the right location. Entering "adb devices" gives me "command not found.

Ah, Mac, I'm of no use to you then.

Well should anybody see this, I'm still trying to get this to work. I can now confirm that the xoom does not show up after entering "adb devices". Otherwise I think the SDK is set up properly...at least I think it is.

take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.

tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!

joeski27 said:
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
Click to expand...
Click to collapse
Set your path. Edit your .bash_profile and you can run commands from anywhere in the terminal. Example:
Code:
export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH

tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
That makes me a little sad. People should know how to use a command line
Sent from my PC36100 using XDA Premium App