[RESOLVED] No Device Attached to USB error message ...

[RonCam]

Hi, new user here. Much appreciated if someone could look at this and tell me why 'no attached device' is detected.

Hardware: M-Horse 9500mini
OS: v2.3.5
MyPhoneExplorer v1.8.5

Checked items on phone's Menu:

• Charge Only
  Unknown Sources
  USB debugging
  Allow mock locations
  Charge Only

Phone is rooted.


Safely Remove Hardware (in Notification Area) ... says

• Eject Spreadtrum phone

but this disappears whenever --
Charge Only is checked, and reappears when it's unchecked

Device Manager

• Android Device
  ROMaster Composite ADB Interface
  Other devices
  (!) Stpreadtrum phone
  (!) Stpreadtrum phone

Windows will not install new driver: when it is attempted (e.g. the Universal ADB driver from the directions), message says, the best choice is already installed.

A few days ago I was able to access ADB on the Command Line, but now that's gone. Is this essential to the success of having a connection??

Is it possible to tell what's missing, by reading the Log?

Code: Alles auswählen

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.5
Datum:   9/28/2013

23:36:44.68       Setting Port: 999
23:36:44.68       Setting Baud: 115200
23:36:44.68       Avaiable Ports: COM1=\Device\Serial0; COM3=Mtlmnt51; 
23:36:44.68       Main Load frmSplash
23:36:44.72       Load frmSplash...
23:36:44.72       Show splash...
23:36:44.77       frmSplash geladen
23:36:46.49       Hauptfenster wird geladen
23:36:46.83       Sidebar fertig geladen
23:36:47.07       UC SMS wird geladen
23:36:47.18       UC Phonebook wird geladen
23:36:47.26       UC Phonebook fertig geladen
23:36:47.26       UC Calls wird geladen
23:36:47.31       UC Organizer wird geladen
23:36:47.54       Organizer initiated
23:36:47.62       Startpage=1
23:36:47.68       UC Filebrowser wird geladen
23:36:47.91       UC Filebrowser fertig geladen
23:36:47.91       UC AppBrowser wird geladen
23:36:47.99       UC Notes wird geladen
23:36:48.03       UC Calls wird geladen
23:36:48.24       Setting Lastuser: 
23:36:48.26       Lade Userdatenbank: 
23:36:48.33       Kontakte geladen
23:36:48.34       ParseDialedCalls needed 0ms
23:36:48.45       Anrufe geladen
23:36:48.46       Organizer LoadUser DefaultTimeColWidth=112
23:36:48.46       Organizer geladen
23:36:48.46       Notizen geladen
23:36:48.46       SMS geladen
23:36:48.96       Hauptfenster fertig geladen
23:36:49.28       Downloader: RC=6 BytesMax=5 URL=http://www.fjsoft.at/myphoneexplorer/version.txt
23:38:50.63       Refresh ComDescriptions...
23:38:50.63       PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
23:38:50.64       MODEM: COM3 Enumerator=PCI Displayed=NetoDragon 56K Voice Modem FriendlyName=NetoDragon 56K Voice Modem InstanceID=PCI\VEN_2003&DEV_8800&SUBSYS_28001801&REV_02\3&267A616A&0&60
23:38:51.52       StickyNotesPath=C:\Windows\system32\StikyNot.exe FileExists=True
23:38:51.52       StickyNotesTitle=Sticky Notes
23:39:44.93       OK pressed in settingswindow
23:39:45.19       Set first swap of settings
23:39:45.25       Apply new holidays
23:39:45.26       Holidays applied
23:39:45.30       Second swap of settings set
23:39:45.30       Everything is done
23:39:49.59       RunADBCommand: start-server
23:39:53.77       ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
23:39:53.77       RunADBCommand: devices
23:39:53.85       ADB CommandResponse: List of devices attached 
23:39:53.85       Run DeviceTracker
23:39:53.87       Init Tracker
23:39:53.88       Device Tracker Message: OKAY0000
23:39:53.88       Connect to Android failed!
23:39:53.88       bOpened=False
23:39:53.88       No device attached to USB
23:39:53.88       Refresh ComDescriptions...
23:39:53.88       PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
23:39:53.89       MODEM: COM3 Enumerator=PCI Displayed=NetoDragon 56K Voice Modem FriendlyName=NetoDragon 56K Voice Modem InstanceID=PCI\VEN_2003&DEV_8800&SUBSYS_28001801&REV_02\3&267A616A&0&60
23:39:53.89       ErrMsg: Connection to phone could not be established:
No device attached to USB
23:40:41.97       RunADBCommand: start-server
23:40:42.08       ADB CommandResponse: 
23:40:42.08       RunADBCommand: devices
23:40:42.17       ADB CommandResponse: List of devices attached 
23:40:42.17       Connect to Android failed!
23:40:42.17       bOpened=False
23:40:42.17       No device attached to USB
23:40:42.17       Refresh ComDescriptions...
23:40:42.17       PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
23:40:42.18       MODEM: COM3 Enumerator=PCI Displayed=NetoDragon 56K Voice Modem FriendlyName=NetoDragon 56K Voice Modem InstanceID=PCI\VEN_2003&DEV_8800&SUBSYS_28001801&REV_02\3&267A616A&0&60
23:40:42.18       ErrMsg: Connection to phone could not be established:
No device attached to USB
23:46:35.81       Refresh ComDescriptions...
23:46:35.82       PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
23:46:35.82       MODEM: COM3 Enumerator=PCI Displayed=NetoDragon 56K Voice Modem FriendlyName=NetoDragon 56K Voice Modem InstanceID=PCI\VEN_2003&DEV_8800&SUBSYS_28001801&REV_02\3&267A616A&0&60

[RonCam]

Bump!

Sorry, I did search, but couldn't tell if the other similar problems duplicated mine.

If this has been answered, a link please?

[FJ]

Uninstall the current adb Driver and try the universal adb Driver: http://download.clockworkmod.com/test/U ... Setup6.msi

[RonCam]

I will try this. Your answer is most welcome as the problems remains unresolved. I may have been using the wrong driver.

[RonCam]

Uninstall the current adb Driver and try the universal adb Driver: http://download.clockworkmod.com/test/U ... Setup6.msi

I have installed the recommended driver.

MS Windows didn't automatically install the driver when plugging-in the phone, so I have been attempting a manual installation.

The Device Manager device list does not show an entry for 'Universal Adb Driver'. The previous driver's name was in the list, although it apparently was non-functional? (See the 'Code' section of my first post, above.)

There are three 'Spreadtrum phone' entries under 'Other devices.' All have a yellow [!] icon before them.

In Device Manager, now I am at the window, Update Driver Software - Spreadtrum phone. The content displayed is as follows:

• Browse for driver software on your computer
  Search for driver software in this location:
  D:\ClockwirkMod\Universal Adb Driver
  [x] Include subfolders

[Next]

• Windows was unable to install ...
  Windows could not find driver software for your device.

[Close]

Settings on the phone:

• USB storage [x]
  USB debugging [x]
  Allow mock locations [x]

This is how the phone is set now. I have tried various other combinations of the above, but perhaps not the correct ones?

Windows Explorer does show:

• 9500MINIS4

... and this does display a complete directory listing, including hidden files -- the phone is rooted.

Do you need more information?
Any additional suggestions on what to do next will be appreciated!

[climer97007]

I have the same USB non-detect message using my new Samsung Galaxy Note 3 phone. I would like someone who has solved this issue for these phones to post the solution. Thanks.

[RonCam]

OK, MyPhoneExplorer started to work, as soon as I could get adb devices to recognize the phone, as follows:

Code: Alles auswählen

C:\Users>adb devices
List of devices attached
19761202        device

The only 'box' on the phone I now have checked is 'USB debugging' -- seems the others weren't part of the problem.

I first usedAshraf's simplified method to install adb, but assumed something to be wrong with it, because 'devices' couldn't 'see' the phone.

Now I suspect it was failing because the file named adb_usb.ini was in the wrong location. Note, the importance of this file is described in the second reference and not in the first. Even so, I have seen it being mentioned in enough other references, that lets me suspect it's necessary to the proper functioning of adb.

But, do not put it alongside adb.exe. It should go in the directory named (on my system) .android, under Users, Username (your own, of course!). This should have been obvious, had I read the directions (blog reference given below) more carefully.

The drivers that worked for my phone were in the second download, headed 'Debug drivers' -- as given in Kiteplan's blog.

The user will know the drivers are 'working' as soon as all yellow [!] icons are gone, in Device Manager (MS Windows).

I should say, before I realized the ini file's location to be the problem, I went ahead and installed Oracle's SDK and JDK. I haven't yet uninstalled any of this, but may do so in the future to see if Ashraf's simplified installation continues to function. I think ... it may have been unnecessary, according a detailed reading of Ashraf's article. I can't rule out, however, that it may have been covered in one of his linked references.

Now, MyPhoneExplorer is able to 'synch' with everything on the phone.

[Underwater Mike]

I had the same issue with a Droid Bionic on 4.1. I never could find a fix...

[climer97007]

RonCam is right.

When I went into "Devices and Printer" in Window 7, there was no driver for my Samsung Galaxy Note 3 phone.

First, I had to install this driver on the PC: http://download.clockworkmod.com/test/U ... Setup6.msi

Then I went into "Devices and Printers" in Window 7 and updated the driver. I let Windows find the driver.

Then I used Windows Notebook to create a "adb_usb.ini" file:
C:\Users\MyName\.android\adb_usb.ini

After that, it took a couple tries, but, eventually the USB connection was made and the Calendar Sync'd with Thunderbird like magic. I did have to go back into MyPhoneExplorer "Settings" to select Thunderbird, and to force the Thunderbird calendar onto the phone.

But, now I am a happy camper. Tickled pink actually. I think I will send some money via PayPal now.