Database Users

Error: Device not found!!

Hi,
I installed ADB from here.
http://developer.android.com/sdk/index.html#download
I moved on to C:/adt-bundle-windows-x86_64-20130219/sdk/platform-tools
Then hold shift & right click "open command window here".
Now moving to my phone setting,
1. Developers Options-->checked on USB Debugging.
2. Security Option--> checked on Unknown Sources.
With all the options seems ok, when I tried to backup my sdcard content through ADB I got "Error: device not found" in the cmd.
Please help guys....

D_RiDeRs said:
Hi,
I installed ADB from here.
http://developer.android.com/sdk/index.html#download
I moved on to C:/adt-bundle-windows-x86_64-20130219/sdk/platform-tools
Then hold shift & right click "open command window here".
Now moving to my phone setting,
1. Developers Options-->checked on USB Debugging.
2. Security Option--> checked on Unknown Sources.
With all the options seems ok, when I tried to backup my sdcard content through ADB I got "Error: device not found" in the cmd.
Please help guys....
Click to expand...
Click to collapse
Do you have the correct drivers installed? Try the 0.72 naked drivers from here http://forum.xda-developers.com/showthread.php?t=1379875.

gee2012 said:
Do you have the correct drivers installed? Try the 0.72 naked drivers from here http://forum.xda-developers.com/showthread.php?t=1379875.
Click to expand...
Click to collapse
I have downloaded these naked drivers. But how to install it on my lappy??
It's in ".zip" file.
Secondly, in my device manager I got yellow icon on my Nexus 4(windows default colour of unavailability of drivers). Possibly due to this drivers I am not able to backup content from mako sdcard.

Why not just use the ones Google intended for you to use, they work perfectly. The flag is your problem, you need to point it to the drivers you want to use. This thread should be very helpful. Same drivers.... http://forum.xda-developers.com/showthread.php?t=1830108

When adb is open, type in
Code:
adb version
If it does not return "Android Debug Bridge version 1.0.31" (Or higher/newer), download the attachment (Works for my Nexus 4)
View attachment adb.zip
If it still doesn't work, download the Google ADK and install the Google USB driver through the SDK manager

[Q] USB Driver for Nexus Player?

I'm trying to do a bit of development for Android TV on my Nexus Player. I've got the player connected to my computer via USB, developer mode enabled, and USB debugging turned on. It shows up in device management but is unknown as there are no drivers installed for the device; and of course when I try and debug my app the player doesn't show up in the connected devices list. I have tried installing the Google USB Driver (Rev. 11) via the SDK manager; and unfortunately Asus's support is pretty useless. Anyone know where I can find the Windows drivers, or if there is some step I'm missing? Thanks!

Tried Koush ADB Drivers?
http://www.koushikdutta.com/post/universal-adb-driver
Cheers Rob.

halfluck said:
Tried Koush ADB Drivers?.
Click to expand...
Click to collapse
Unfortunately that didn't work.
I got it up and running by:
Selecting update driver
Browse my computer for driver software
Selecting let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting \android-sdk\extras\google\usb_driver\android_winusb.inf as the driver
Hope this helps anyone else who comes across this issue.

I just pasted the hardware ID's from device manager into the INF file of the normal ADB drivers and that worked fine.

Funkwheat said:
I just pasted the hardware ID's from device manager into the INF file of the normal ADB drivers and that worked fine.
Click to expand...
Click to collapse
How do you do that exactly?

Phoexyael16 said:
How do you do that exactly?
Click to expand...
Click to collapse
Goto the properties of the unknown device in your device manager, then goto Details and then Hardware ID's, then copy and paste those into the INF file in the same format the others are in.

Funkwheat said:
I just pasted the hardware ID's from device manager into the INF file of the normal ADB drivers and that worked fine.
Click to expand...
Click to collapse
How could you view the hardware ID's if you were not able to connect with the device?
DevinWatson said:
Unfortunately that didn't work.
I got it up and running by:
Selecting update driver
Browse my computer for driver software
Selecting let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting \-sdk\extras\google\usb_driver\_winusb.inf as the driver
Hope this helps anyone else who comes across this issue.
Click to expand...
Click to collapse
I get "error code 10" every time I try this.

Please help (need working unlock and root instructions)

I've been up and down the forums for two days trying every method and app and whatever else is recommended.
asus zenfone 2 laser
Z00TD (ZE551KL)
-i cannot unlock bootloader (Asus unlock tool does not work for any variant)
- cannot root with any one click app (assuming because bootloader is locked)
- cannot manually install drivers via any instructional method online. (They all seem to be 64 bit when I have a 32 bit machine) and there is no actual exe file to install anywhere that i can locate.
- cannot use windroid as it requires twrp (basically root) ....useless.
-cannot adb command unlock or root, does not recognize device (assuming because proper drivers are not installed)
I'm on the updated software version 1.16.40.763-20151201
Someone please give me a hint or some lead as to what I'm missing or where I'm going wrong.
Thanks in advance.

Download the adb-fastboot tool from here...:- Moderator EDIT PPC links are not allowed
Install it.. it will ask you for installing drivers also.. install them... Visit Asus.com and download the drivers for your device. . Now search for Device manager in Windows start menu. Click on Device Manager and then you will see a device named as Android or something like that... Right click on it.. then select update drivers... Then you will see two options 1). Check online 2. Browse my Pc for updated drivers.. select the 2nd one now browse the downloaded file of drivers and select it.. select the folder of files .(After unzipping the folder)...
Click on update.. now drivers will get installed.. now
Use Ctrl+shift+right click..(in adb folder mainly located in local disk c) and select open command Windows here. Enable the USB debugging option in developer options of your device.. At first it will ask for permissions. Alow it.. Now you can flash anything.. for further information ,if needed you can contact me..

Njishi said:
Now you can flash anything.. for further information ,if needed you can contact me..
Click to expand...
Click to collapse
LOL

Njishi said:
Download the adb-fastboot tool from here...:- Moderator EDIT PPC links are not allowed
Install it.. it will ask you for installing drivers also.. install them... Visit Asus.com and download the drivers for your device. . Now search for Device manager in Windows start menu. Click on Device Manager and then you will see a device named as Android or something like that... Right click on it.. then select update drivers... Then you will see two options 1). Check online 2. Browse my Pc for updated drivers.. select the 2nd one now browse the downloaded file of drivers and select it.. select the folder of files .(After unzipping the folder)...
Click on update.. now drivers will get installed.. now
Use Ctrl+shift+right click..(in adb folder mainly located in local disk c) and select open command Windows here. Enable the USB debugging option in developer options of your device.. At first it will ask for permissions. Alow it.. Now you can flash anything.. for further information ,if needed you can contact me..
Click to expand...
Click to collapse
When uninstall those drivers I get the yellow triangle on them. They aren't functioning.
Sent from my A1R using XDA-Developers mobile app

nujaxx said:
When uninstall those drivers I get the yellow triangle on them. They aren't functioning.
Sent from my A1R using XDA-Developers mobile app
Click to expand...
Click to collapse
You don't need to uninstall them.. just update them..

Typo.... install
Sent from my A1R using XDA-Developers mobile app

I must be doing something wrong. Because I've done all of that. And the drivers don't install properly. I can get into fast boot and that's where it stops for me. The bootloader 20007.img code keeps failing.
I don't know. Something isn't right. I can't even unlock it with the Asus unlock tool. I've tried every one for every variant.
Sent from my A1R using XDA-Developers mobile app

this might sound stupid, but try a different, better, usb cable.
I had a similar issue years ago, trying to flash my first android phone, windows would also give me device manager error. i beat my head on the wall for two days using the motorola supplied data cable, until on a whim i tried a different USB cable and everything worked.

Yotaphone 2 drivers

Hi, where can I find the correct drivers for Yotaphone 2? I tried the driver that comes with the flasher tool, but somehow it does not install (yes, I right-clicked on the INF file and selected Install, but nothing happened after that)
Thanks in advance for the help!

Right clicking the INF file and selecting install most of the time doesn't yield any results on screen. It is a silent install. You can check if they are installed by comparing the size of the installed androidusb.sys in C:\Windows\System32\drivers with the size in the AMD64 and i386 folders in the yotaflasher folder. It is either 31kb (AMD64) or 26kb (i386).

Drivers
Thanks for the reply.
I checked the system folder on my PC, and the drivers were not installed. Somehow clicking on "Install" for the INF file does nothing
Is there some other way to install the drivers? Can I simply copy the driver files to the system folder

Drivers
Hi, does anyone have a suggestion to install the drivers? I am on Windows 10

peekeh said:
Hi, does anyone have a suggestion to install the drivers? I am on Windows 10
Click to expand...
Click to collapse
You can try installing the default Google drivers. You can find everything you need in this thread. http://forum.xda-developers.com/showthread.php?t=2588979

You use device manager to install " legacy drivers" and "have disk" , it is mentioned several times here including the one above.

Drivers
Hi, I really appreciate the replies and patience with this
I already tried that but I get the message:
The folder you specified doesn't contain a compatible software driver for your device. If the device contains a driver, make sure it is designed to work with Windows for x64-based systems
What do I need to do?

These worked for me:
http://adbdriver.com/downloads/

Thanks, sonof.
I tried the installer from the link you gave.
Somehow it is not showing any detected device at all.
How do I get it to detect my phone in order to install the driver?

Did you solve it? I have the same problem, can't see the device...

QPST driver install...

Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5

Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$

L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now

L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"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)"
msi laptop running windows 10 latest update

JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"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)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port

fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that

L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar

fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.

Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?

Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.