6 replies to this topic

[cranked]

This is my first Cyanogen Mod...I have JDK and the SDK installed, but I am unable to get the phone to be recognized.  Before I modded the phone, I could run "adb devices" and see my phone.  With this current mod, my PC recognizes it is plugged in - I see the "USB connected" prompt, and the "USB debugging connected" prompt - but no devices are listed...

I searched around, but I am sure I missed something again.  Would really appreciate any tips, so I can attempt to fix a maps issue I have.

C:\Users\cranked>adb devices
List of devices attached


C:\Users\cranked>adb devices
List of devices attached


C:\Users\cranked>

[ciwrl]

Make sure usb tethering is disabled. I dont think there is another setting that would affect this.

Also, there is an open bug about moving from the wallcharger to usb and it affecting adb connection/sd mounting.

Try giving the phone a quick reboot before trying to use adb

[marzib]

cranked, on 29 May 2010 - 05:39 AM, said:

This is my first Cyanogen Mod...I have JDK and the SDK installed, but I am unable to get the phone to be recognized.  Before I modded the phone, I could run "adb devices" and see my phone.  With this current mod, my PC recognizes it is plugged in - I see the "USB connected" prompt, and the "USB debugging connected" prompt - but no devices are listed...

I searched around, but I am sure I missed something again.  Would really appreciate any tips, so I can attempt to fix a maps issue I have.

C:\Users\cranked>adb devices
List of devices attached


C:\Users\cranked>adb devices
List of devices attached


C:\Users\cranked>

It happens to me sometimes on mac and unplugging usb/plugging back in works for me. Does it keep happening even then?

[cranked]

ciwrl, on 29 May 2010 - 05:43 AM, said:

Make sure usb tethering is disabled. I dont think there is another setting that would affect this.

Also, there is an open bug about moving from the wallcharger to usb and it affecting adb connection/sd mounting.

Try giving the phone a quick reboot before trying to use adb

Reboot, and not plugging into the wall works...thanks a ton.  I am low on battery so I kept plugging it in as I was rebooting...all is well now, thanks everyone.

[DroidGio]

Hey guys.. I think lots of people are having the same problem and I want to say is the adb.exe & AdbWinApi.dll files causing this. Today I downloaded and installed the latest of SDK from the Dev's site and after that there was no way i could do a comand on adb.. after a while i just played with it and took those two files from my old SDK i had before in replace the new ones for the old ones and haven't had problems yet.. hope it helps, i did almost go crazy asking what did i do wrong when i always follow step by step of everything posted. thanx

[bruslim]

DroidGio, on 29 May 2010 - 05:58 AM, said:

Hey guys.. I think lots of people are having the same problem and I want to say is the adb.exe & AdbWinApi.dll files causing this. Today I downloaded and installed the latest of SDK from the Dev's site and after that there was no way i could do a comand on adb.. after a while i just played with it and took those two files from my old SDK i had before in replace the new ones for the old ones and haven't had problems yet.. hope it helps, i did almost go crazy asking what did i do wrong when i always follow step by step of everything posted. thanx

When you upgrade the SDK with the provided Updater Program, you should also update the drivers.

Windows always has driver issues.

If it still doesn't work, COMPLETELY remove the OLD driver, and then install the new one.

there is also a program called usbdevview? (i think, go search), that may provide assistance in fixing your USB driver issues.

Also forcing windows to rescan your USB hub, by disabling and then enabling, or uninstalling and then reinstalling it all through the device manager is also another way.

[JMak]

Same problem on a Rogers HTC Dream (g1).  

I placed the Amon Ra recovery.img into the tools folder and ran fastboot (fastboot boot recovery.img) which went fine, but then the phone is just showing the Rogers splash screen and running "adb devices" gets me "list of devices attached".

I've got Android SDK and the device was listed when I ran adb devices before trying to run the recovery image.

Not sure how to proceed especially since I've noticed some discrepancies between the wiki for "HTC Magic (32A): Rooting (3.22.x radio)" and the posts by Haykuro and others on xda-developers.com.  Specifically, the wiki says that fastboot is achieved by holding Volume Down+power, but that just got me to a reboot screen while the instructions posted on xda (camera button + power) DID get me to the fastboot screen on the device.

Any suggestions as to how to proceed?  I have a sinking feeling I've bricked the phone.

Sorry if this is not clear, I need more sleep.

Thanks,
J.