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.

Unlock NAND on MAC anyone?

tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks

nitty917 said:
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
Click to expand...
Click to collapse
I did it on my MBP. What problems are you having?

I did it on my macbook..

I also did it on my Mac. Like someone else said what specifically is the issue you're encountering?

there is a post in about using Terminal app from the market to do this and it works!

brianb7590 said:
I did it on my MBP. What problems are you having?
Click to expand...
Click to collapse
thanks, I cant get it to communicate in terminal,
i have no idea. i dloaded the sdk, dragged the adb from tools folder,
onto the terminal, it opens up all the adb commands but after that i cant type
nothing.

nitty917 said:
thanks, I cant get it to communicate in terminal,
i have no idea. i dloaded the sdk, dragged the adb from tools folder,
onto the terminal, it opens up all the adb commands but after that i cant type
nothing.
Click to expand...
Click to collapse
Don't drag it to the terminal.
I would navigate to the directory where you stored the SDK and go to the tools folder and run it that way or you search up how to set your PATH to include the tools folder.

nitty917 said:
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
Click to expand...
Click to collapse
Like the others who have already replied, I also did it on my mac and was a complete noob. It was only through much trial, error, YouTube, and 3 other sites that I figured it out. Needless to say I'm now fluent in adb and would be happy to answer any questions you have since I was in exactly the same shoes as you last weekend. Below are the biggest things you need to know when you start:
1. When you plug the phone into your computer make sure you select "Charge Only." If you select "Use Phone as Disk Drive" you won't be able to write to the phone, only read. I ran in circles for a long time getting "Read-Only File System" errors and it was all due to having the phone mounted as drive.
2. Make sure you have USB Debugging turned on. After that, you should be able to communicate with the phone fine.
3. ADB - The instructions are nearly identical regardless of operating system but on a mac you need to add "./" (without the quotes) before adb commands. For example, lets say I have a file on my desktop called "Test_File.img" that I want to push to the root of the sdcard. On my Mac I would type "./adb push /Users/Bryan/Desktop/Test_File.img /sdcard/" (without the quotes of course) & (Bryan is my Username)
4. To avoid any issues make sure none of the folders or file names you are working with have spaces in the name.
Hopefully all this helps and does no lead to more confusion than when you started. Again, if there are any specific errors you are seeing post them here and either I or someone else would be happy to answer them.
Bryan

okolowicz said:
Like the others who have already replied, I also did it on my mac and was a complete noob. It was only through much trial, error, YouTube, and 3 other sites that I figured it out. Needless to say I'm now fluent in adb and would be happy to answer any questions you have since I was in exactly the same shoes as you last weekend. Below are the biggest things you need to know when you start:
1. When you plug the phone into your computer make sure you select "Charge Only." If you select "Use Phone as Disk Drive" you won't be able to write to the phone, only read. I ran in circles for a long time getting "Read-Only File System" errors and it was all due to having the phone mounted as drive.
2. Make sure you have USB Debugging turned on. After that, you should be able to communicate with the phone fine.
3. ADB - The instructions are nearly identical regardless of operating system but on a mac you need to add "./" (without the quotes) before adb commands. For example, lets say I have a file on my desktop called "Test_File.img" that I want to push to the root of the sdcard. On my Mac I would type "./adb push /Users/Bryan/Desktop/Test_File.img /sdcard/" (without the quotes of course) & (Bryan is my Username)
4. To avoid any issues make sure none of the folders or file names you are working with have spaces in the name.
Hopefully all this helps and does no lead to more confusion than when you started. Again, if there are any specific errors you are seeing post them here and either I or someone else would be happy to answer them.
Bryan
Click to expand...
Click to collapse
If you're going to be using adb on a regular basis, and want to avoid typing "./" before each command, you can add the android sdk tools path to your .bash_profile file in your home directory. Something along the lines of:
export PATH=${PATH}:/path_for_ur_sdk_folder_location/android-sdk-mac_86/tools

mocalve said:
If you're going to be using adb on a regular basis, and want to avoid typing "./" before each command, you can add the android sdk tools path to your .bash_profile file in your home directory. Something along the lines of:
export PATH=${PATH}:/path_for_ur_sdk_folder_location/android-sdk-mac_86/tools
Click to expand...
Click to collapse
That wont be saved. It goes away after every reboot.

Fixter said:
That wont be saved. It goes away after every reboot.
Click to expand...
Click to collapse
True, if you enter it from the command line. But if you add it to the .bash_profile file , it will stick... at least on my Mac Pro it does...

mocalve said:
True, if you enter it from the command line. But if you add it to the .bash_profile file , it will stick... at least on my Mac Pro it does...
Click to expand...
Click to collapse
If I add those entering nano .bash_profile and enter that command and the pressing Ctrl X and Yes it will stick?

Fixter said:
If I add those entering nano .bash_profile and enter that command and the pressing Ctrl X and Yes it will stick?
Click to expand...
Click to collapse
It should... although I use vi instead of nano. Regardless, after saving the .bash_profile, you'll have to fully exit the terminal application and restart for the path setting to take effect. After that, it'll be in effect every time you start terminal.

mocalve said:
It should... although I use vi instead of nano. Regardless, after saving the .bash_profile, you'll have to fully exit the terminal application and restart for the path setting to take effect. After that, it'll be in effect every time you start terminal.
Click to expand...
Click to collapse
Nano is way cleaner. And yeah. It got applied.

ADB commands not working

So i rooted my desire using the modaco r6 root.
I'm using defrost 1.0 atm and when I'm entering recovery i cant use any adb command, except for devices which show my desire in recovery mode.
all other commands return an error like:
su:
/sbin/sh: su: not found
logcat:
/sbin/sh: exec: line 1: logcat: not found
install
/sbin/sh: pm: not found
just to name a few.
i just got it so i don't know if they worked before.
however i did get one boot loop due to flashing the circle battery mode.
after which i recovered the nandroid backup.
If you need more info tell me what to do im clueless, im prolly just doing something very stupid.
Thanks in advance.

Go into partitions menu and mount /system then try.

No go doesn't even change the error.

so no ideas? i got no wifi or 3g connectivity atm so you guys are my last resort.
just some updates i flashed mcr 3.1 and it change in addition htc sync doesn't recognize my desire now.

you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?

Can you not boot into fastboot. Volume down and power. Then go to recovery. Then hold volume up and power. Select wipe data and wipe cache. Wouldn't that solve your wifi issues etc?

Wait...if you're using root r6 then your using fake flash aren't you? Try looking for r5 and use pauls recovery or look for amskghs recovery and use that. Pretty sure adb stuff doesn't work easily with fake-flash.

cgrec92 said:
you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?
Click to expand...
Click to collapse
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.

Hash = #
What exact commands are you doing and what are you trying to achieve?
I really want to help

LByte said:
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.
Click to expand...
Click to collapse
I had your same problems and felt retarded too, but it might be something funky with the dos command prompt in windows. Follow these instructions to make adb commands universal so it doesn't matter what directory the dos command prompt thinks you're in (because obviously it didn't actually move you to the tools folder somehow even though you instructed it too):
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-1.1_r1\tools
This was found here: sorry can't post link to give proper credit, but do a google search for adb for dummies or adb commands, it's an xda forum post...

The thread looks dead, but im going to post the possible solution anyway.
PM commands like install and uninstall doesnt work in recovery mode, so if you want to use them, run the commands when the phone had booted normally.

i have same problem? anyone help me
adb error /sbin/sh: exec: line 1: logcat: not found

i need help!

help me root my phone i dont understand this im really f'd up this is like dsa adveture
ok here is the problklmemo
"Step 5: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now.
Once ready, type these commands in cmd prompt from your adb tools directory.
Code:
adb push unrevoked-forever.zip /sdcard/
adb push flash_image /data/local/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb push mtd-eng.img /sdcard/
adb push PC36IMG.zip /sdcard/"
oksssssss now..one person say i right click on tools and open cmd,,,so i dids that
then i type it in and its doesnt work..it says adb or abd waterver it is is not a command and its not reconixed...help me please!!!thanjs

Bank that nand up
Use the correct forum and answers may be provided.

Bielinsk said:
Bank that nand up
Use the correct forum and answers may be provided.
Click to expand...
Click to collapse
sorry im on anotheyhrfnd vci wikll try

you trying to root 2.1 or 2.2?

alextrox69 said:
then i type it in and its doesnt work..it says adb or abd waterver it is is not a command and its not reconixed...help me please!!!thanjs
Click to expand...
Click to collapse
You're getting this message because the tools folder in your Android SDK isn't in your path.
http://forum.xda-developers.com/showthread.php?t=500196

first off..if u need help ( im not gonna be that GUY to tell u SEARCH and post in the RIGHT forums) please post your stats and info...what type of root are you trying to do...what are your hardware specs...are you currently 2.1 or 2.2? not everyone rooted the same ways....and sometimes different hardware/software you gotta use different root steps

he is 2.2
If he was 2.1 he probably wont be using this method, there are easier ways for 2.1!!

lamboh said:
first off..if u need help ( im not gonna be that GUY to tell u SEARCH and post in the RIGHT forums) please post your stats and info...what type of root are you trying to do...what are your hardware specs...are you currently 2.1 or 2.2? not everyone rooted the same ways....and sometimes different hardware/software you gotta use different root steps
Click to expand...
Click to collapse
im on 2.2 officail..i want to get cm6 on my phone..thats my goal

illogic6 said:
You're getting this message because the tools folder in your Android SDK isn't in your path.
http://forum.xda-developers.com/showthread.php?t=500196
Click to expand...
Click to collapse
i did what that link told me to do and it still isnt working

htc desire gsm keeps restarting

hi my htc desire keeps restarting when i flash any gingerbread miui rom i have tired data2ext and a2sd and have wiped and also formated my sdcard and stil have same problem with both but it works fine with all other roms and the froyo version of miui. please help

What hboot are you using and how did you root your phone?
Sent from my HTC Desire using xda premium

hi im using normal hboot-0.93.0001 i used unrevoked to root my phone i am not really a noob i have flashed and rooted many phones but for some strange reason all other roms including miui froyo work on my phone but gingerbread miui wont it loads up to the home screen and then just reboots ive tried data2et version and a2sd version and same thing happens with both versions.i have also tried using diffrent recoverys amon-ra,clockwork etc and still get the same problem.

You need to understand what is going on under the hood.. Getting an adb logcat is the way to go..
Code:
Windows>Start>Run
echo "null" > log.txt
start log.txt
adb logcat > log.txt
Use Notepad++ to associate with the txt file and reload the file every couple of seconds while keeping the cmd shell in the background.. See what's happening just before it reboots. It could be anything from a bad script to a bad module

Have you tried gingerbread 2.8, its simple and a very plain ROM, I have had issues with miui roms with my desire, if that doesn't work I will keep looking my self, sorry I'm not very insightful, you have an odd problem.
Sent from my HTC Pyramid using xda premium

Nice one Droidzone, I will have to try that also.
Sent from my HTC Pyramid using xda premium

Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.

casanova786 said:
Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.
Click to expand...
Click to collapse
Once you open a command line prompt in the folder where adb is installed (or anywhere else, if the file adb.exe is in your Windows path variable-Dont worry about that if you dont know), you can directly type each line of the commands starting from step 2.
Before that, install Notepad+, and associate .txt file to open with it by default..
By the way, you have to start typing those commands directly after rebooting from recovery after installing the Rom..

hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.also i typed the commands u gave me once in adb and it says "the process cannot access the file because it is being used by another process."

casanova786 said:
hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.
Click to expand...
Click to collapse
Hmm.. I seem to be offering more Windows support than Android!
I meant Notepad+. Hold Shift, rightclick any text file, Choose Open with Notepad+ as default. You can go to your adb folder like you normally do and then type each line I posted and hit Enter after each time. You can also make a batch file with all those commands (search Google for that if you dont know how)

hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."

casanova786 said:
hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."
Click to expand...
Click to collapse
Hmm yes, that can happen if you have more than one adb.exe process running in the background because you exited it by closing the command shell with the close button instead of typing
Code:
exit
after done with it.
Use Ctrl+Alt+Del or Process Explorer to terminate the background adb.exe processes