Adb interface problem

[joedarkon]

I am trying to install a custom rom and I already rooted my Optimus S a while ago but now I am running into problems. I cant get ADB to work, in my devices on my computer (Windows7x64) the android sooner single adb interface has a yellow triangle with an exclamation point. I have been trying to fix this for a while but I cant seem to get it to work. I do see some issue with the driver not being signed but my attempts to address that have failed. Can anyone help?

 

[swg0101]

Have you tried deleting the drivers and reinstalling it?

 

[joedarkon]

several times

 

[DroidXcon]

I cant get ADB to work, in my devices on my computer (Windows7x64) the android sooner single adb interface has a yellow triangle with an exclamation point. ?

i dont understand this

 

[joedarkon]

It seems to me that there is some driver issue and I think thats what windows is saying with the yellow triangle. I have tried multiple drivers.

 

[DroidXcon]

have you tried this
http://forum.androidcentral.com/oth...8-how-install-usb-drivers-lg-optimus-one.html

 

[joedarkon]

Yup I tried that and it installs the drivers but the "Android platform sooner single ADB interface" fails

 

[pitmasterme]

What about Droid explorer? There's a thread saying how easy it is to use.

 

[DroidXcon]

or try this, sans the fascinate drivers
http://forum.androidcentral.com/general-help-how/56697-how-quick-adb.html

 

[joedarkon]

Quick ADB isnt working either it give the same "error: device not found"
And yes debugging mode is active

 

[joedarkon]

Droid explorer isnt working either. I think its some driver problem.

 

[DroidXcon]

uninstall any drivers that may have tried to install, reboot your computer and try that thread i gave you again

 

[sfhub]

Almost everything is based on adb even if it looks like the program is standalone. You really need to work on getting that working first.

When you right click on the android sooner device and select "properties" it should give you a reason why there is an error. What does it say?

 

[joedarkon]

The error for adb is "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
It has been like this even after uninstalling and installing multiple times.

 

[sfhub]

Have you tried pressing F8 during windows boot and choosing disable driver signing enforcement?

 

[joedarkon]

Thanks sfhub, I tried using a program to do the same thing but I guess I had to do it the windows way. Thanks so much, Ill pass this info on to another guy who has a similar problem.

 

[pitmasterme]

Have you tried pressing F8 during windows boot and choosing disable driver signing enforcement?

Would that work for trying to get cl14 to be able to find my wife's Moment? Had the f-ing thing for over a year and have tried all remidies I could find and still no luck......
(Sorry for bringing that retched phone into this forum!!)


Sent from my LS670 using Tapatalk

 

[mid3vil]

Hmm.. I was having this problem on my phone also.. I found a set of drivers that worked for the sooner single adb issue.. It worked for Windows 7 64 bit, I haven't tried it on my laptop running windows 7 32bit, but i was having same problem..

If anyone is interested i'll test on laptop and see if i can find a place to upload it later.. (Although i gotta find the file)

 

[sfhub]

Would that work for trying to get cl14 to be able to find my wife's Moment? Had the f-ing thing for over a year and have tried all remidies I could find and still no luck......
(Sorry for bringing that retched phone into this forum!!)

Have no idea about the moment. If it is a similar issue to what was described here, maybe it might help. Otherwise, probably not.

 

[Immersion]

Ive been having a hell of a time getting the drivers installed on Win7-64bit too....even had my friend who is an android pro help but could not get it working....any ideas?