Related
Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
WINDOWS XP x86 / 32-Bit Only
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys !!!! (Be Careful Deleting this File, I Say First try Without Deleting this file !)
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....
All I can say is THANK YOU.
THANK YOU THANK YOU THANK YOU.
This post deserves a sticky..
you are great
LOL
-- well after this I couldn't use FASTBOOT anymore hahahahaha
well, I worked around that, had to reinstall drivers for Haykuro's SPL too. So now both ADB and FASTBOOT work.
Thanks helped with my Win NT at work. lol
lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.
SolemnWishing said:
lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.
Click to expand...
Click to collapse
So Is that you are sayin is we do not need to remove the wdf file, did the drivers work without removing & again installing that wdf file?
or u did not put the new file again before rebooting ?
I am not really sure. It can possibly just be my computer. Once removing all the drivers you listed, the ADB then successfully worked, and continued to work as long as the computer was not rebooted. Once rebooted, I drivers for many pieces of hardware became corrupt and unreadable. By simply replacing the wdf driver and rebooting, it fixed the issue. So, I really am not sure. My computer... is strange. I believe it likely could just be my computer thats all.
next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks
The key points are:
To choose ADB interface\HTC Dream Composite ADB Interface to install
--DIYism
sangeet.003 said:
next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks
Click to expand...
Click to collapse
I will be performing another system recovery install soon, so I will post the results. My computer got screwed up again, so backing everything up now...
I still have a problem...
thanks for your tutorial.
I followed as you say, but I can't find my phone in cmd mode in my computer.
I succeed to install driver also it's shown in device manager as like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but something wrong in cmd mode as like this.
I'v tried whatever I can do..reinstall driver, adb, swipe my phone..
what shall I do now?
adb problem
Hi,
Same problem here, tried everything but CMD just is not showing any device...
I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.
pluplus said:
I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.
Click to expand...
Click to collapse
I followed this completely, I have the phone installed correctly now, not a mass storage device, device manager reads:
ADB Interface > HTC Dream Composite ADB Interface
However, I have usb debugging enabled, and still get the same *error: device not found*
Took a decent amount of time to get done right too, thanks to "trustedinstaller" being the only "user" that can delete drivers on my laptop..yay for changing ownerships! You'd think administrator would suffice, but nay.
Anywho..wtf am I missing here?
edit: win 7 x64, however the same rules for this how-to should still apply, as all the drivers and install options/processes are identical
ive found that trying to use the adb driver the driver gave me error code 10 (within the device manager)
ive got rc win7 64 bit
what i used to get rid of this problem is the program called USBdeview ( google for it)
and uninstalled everything related to htc/android
after connecting the phone the correct driver installed and i could use the adb device
I didn't want to make another topic on this, but I have a problem. Whenever I uninstall the drivers from device manager, then search for new devices, it installs the drivers automatically. I have mass storage and adb dream interface, but no devices are found when I execute the adb command. I cleaned out what I could from the system32 and /drivers folder. Any clues? Just to add, it did work about a week ago, didn't need to use it, now it doesn't work.
Edit: Oops, I forgot the check the uninstall driver box. I have the drivers, they install correctly, but I still can't use adb.
PS: vista x64, installing from the amd64 subfolder.
sangeet.003 said:
Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....
Click to expand...
Click to collapse
nothing happeneds...
after doing that after reboot my laptop,i'm loosing harware keyboard and have some other problems too..
i just change the drivers again and reboot and all ok but there isn't any way to my laptop(toshiba xqosmio x300 with vista 32bit)read my hero in fastboot usb condition...
i tried it and in 2 pc's with xp (service pack 2) but the same again and there....
adb shell and adb devices aren't reade the phone in fastboot usb ....
in my cmd i'm taking allways the same error message when i try to load the cm-hero-recovery.img ""canot load cm-hero-recovery.img""
anybody who can help??
i have the windows usb drivers. and when i go into device manager on my 32bit vista machine, it shows "Android Phone" under portable devices. i click update drivers and select the usb drivers. problem is, it tries to install them, then i get a message saying like 'unable to install "da da what ever driver its called" then it just closes.
why wont this work help is appreciated
THANKS, i was keen to install linux
Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you.
You save my life. I've been having this problem for MONTHS!!! and no way im gonna restore my windows xp again. Thanks so much.
Since I can't respond to threads in Developer and I think that this might belong here to answer some folks questions. I have read that a lot of people are having issues with ADB access under Windows x64 using the latest CM10 by h8rift. I found a solution that worked for me and I wish to share it with everyone in case it will work for them. A few critiria:
- Your device is connected via USB cable to your computer
- Your device is listed as "HTC MTP Device" in Windows Device Manager
- When you open a CMD prompt under your Android Directory and type "adb devices", nothing is listed
This is because you have the wrong device drivers installed on your system and it needs to be corrected. This is how I accomplished it.
1. Uninstall the driver completely from your system. This has to be done under the device properties. Under "Action", select "Scan for New Hardware Changes". Your system will see the new device and identify it under "Other Devices" as "One". If Windows tries to install the wrong drivers, you will have to restart all over until the HTC MTP Device driver is completely removed from your system.
2. Install HTC Sync from their website. Once installed, it has to update to the latest version. This is needed to install all additional drivers for SD Card access.
3. HTC One X Drivers will be listed under C:\Program Files (x86)\HTC\HTC Driver\Driver Files (default install location).
4. For ADB access, you will need the drivers located here; download appropriate drivers for your Windows flavor. These are the ADB drivers.
5. Download the zip, and extract. Remember the location of the files. Go into Device Manger, find "One" under "Other Devices" and Update Driver Software. Point to the new directory you made and install. The One X will now be listed in Device Manager as "My HTC" under "Android USB Devices"
6. To verify ADB, open a CMD prompt, point to Android directory and type in "adb devices". Your beautiful HTC One X should be listed.
I am not the maintainer of any of these webpages nor can I guarantee that these pages will exist to the end of time. Those of you wishing to have ADB access under Windows for CM10, this worked well for me. I gathered up this information just by doing a quick search in Google and through the forums.
Thank you to h8rift for CM10 and all the hard work he puts into it.
Will try this when I get home! Thanks.
This worked perfectly for me. Thanks man!
------------------------------------------------------------
HTC One X, CM10-Evita JellyBean, Win7-x64
Not working for me, evertime I scan for hardware changes it tried to install HTC MTP DEVICE, and when I try to update that driver with the new ADB driver, it says it's already installed. Then when I uninstall that driver, I don't see the One devices anywhere, until I scan for hardware changes again, which then repeats the above. What am I doing wrong?
Chrysis said:
Not working for me, evertime I scan for hardware changes it tried to install HTC MTP DEVICE, and when I try to update that driver with the new ADB driver, it says it's already installed. Then when I uninstall that driver, I don't see the One devices anywhere, until I scan for hardware changes again, which then repeats the above. What am I doing wrong?
Click to expand...
Click to collapse
I think I found a fix for that. Let me restart my computer and verify
edit: nope.. nothing so far. mine doesn't even show HTC MTP DEVICE anymore >.>
same i see one when i look for new hardware but it always just auto sets to mtp.
Delete old drivers
The reason for this is that you cannot completely delete existing drivers using device manager. They still exist in the driver store, and are loaded as soon as you scan for hardware changes.
There might be a better way to do this, but here's how I did it:
- uninstall driver in device manager. Don't scan for hardware changes.
- Run a CMD prompt as administrator (right click "Run as Administrator")
- navigate to C:/Windows/system32 which is the location of the driver store
- type pnputil.exe /e
- this will list the drivers that exist in the driver store. They are denoted as oem##.inf
- find the driver that has "HTC Corporation" in the description. Write down the oem##.inf number (ex. oem81.inf)
- type pnputil.exe /d oem##.inf (where ## corresponds to the number of the HTC driver).
This will remove the old driver from the driver store. Now when you scan for hardware changes, it should fail to find a driver and prompt you for a location.
NOTE: I actually had several HTC drivers in the driver store. Its because I've had a few HTC devices over the years. I deleted them all. This may break HTC Sync, I dunno. I don't use it.
Fixed. See post below
For anyone having problems. I finally got it working.
THIS SHOULD BE NO LONGER NEEDED. ROHAN'S NEW AOKP VERSION 2 SHOULD WORK WITH STOCK DRIVERS. IM ASSUMING THIS WILL BE MERGED WITH ANY OTHER AOSP ROMS. IF YOU STILL NEED THIS INFORMATION HOWEVER, I WILL LEAVE IT UP.
1. Uninstall HTC Sync and any HTC sync drivers listed in your "Add/Remove Programs"
2. Delete EVERY driver pertaining to HTC when you run CMD as admin and type "pnputil -e" and then type "pnputil -d oem##.inf" (such as oem13.inf ONLY IF it says HTC or HTC Corporation)
3. Download Deview - 32 bit OR 64 bit, and run as administrator and uninstall ALL disconnected drivers (it won't matter if you uninstall the wrong thing, because it will just reinstall again when you plug in the hardware. make sure your phone IS NOT plugged in)
4. Download ADB drivers 32 bit OR 64 bit. (windows)
**Restart Computer**? (I did just to be safe)
5. Plug in your phone. Go into device manager, and find your device. It should be listed as "One" with a yellow question mark.
6. Right click and update driver software
7. find your USB drivers you downloaded and choose to install those.
your device should now be listed under "Android USB Devices" as "My HTC"
When I did this, my phone skipped being labelled as "HTC MTP Device" all together
If it is not detected in ADB after installing drivers...
1. UNPLUG PHONE
2. Run USBDeview as administrator
3. Uninstall any unplugged devices
4. Restart computer
5. Plug in phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and after verifying adb reboot bootloader worked. I thought, well heck. I'm sick of installing a file manager to install a file manager that's already stored on my sdcard.
and to verify it installed (no restart)
I hope this helps someone
done everything, nothing work. sees my HOX only while being ON and thus can't get the cid :/
pet3rs said:
done everything, nothing work. sees my HOX only while being ON and thus can't get the cid :/
Click to expand...
Click to collapse
What exactly are you trying to do? Did you install HTC Sync drivers? This is for using ADB on the old CM10/AOKP, not for rooting your phone
device is already rooted, I need to get adb working because I can't get my cid from fastboot command.
pet3rs said:
device is already rooted, I need to get adb working because I can't get my cid from fastboot command.
Click to expand...
Click to collapse
Boot your phone into fastboot from your bootloader
Sent from my HTC One XL using xda-developers app
i'm in fastboot and type adb shell getprop ro.cid, message says error: device not found. fastboot getvar cid returns CID: none
Found a great way that fixed it for me on Windows 8:
use this tool: http://www.nirsoft.net/utils/usb_devices_view.html to remove all instances of anything that has to do with HTC. Then, follow steps above to scan for new devices, and set the driver accordingly (with USB debugging on on the phone). It should register as "My HTC" and then you will be able to see the device in "adb devices" list.
pet3rs said:
i'm in fastboot and type adb shell getprop ro.cid, message says error: device not found. fastboot getvar cid returns CID: none
Click to expand...
Click to collapse
you can't use adb from fastboot. you use fastboot.exe e.g.
fastboot oem getvar cid
no adb needed.
Guys can u pls help me? I've done the above procedure for installing the drivers on my htc explorer, it all worked, in the device manager panel i can see My htc when i'm in fastboot, and i can see Android bootloader Interface when i'm in the bootloader, but nevertheless I can't run adb shell because it doesn't find the device, and when I run adb device it gives me an embty list, i must use adb in order to attemp to recover the nand that it's probably burned.
Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Java is needed to Run SDK Manager - Install JAVA
The Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\sdk\platform-tools
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
Reserve if needed
Thanks! Good stuff.. I just installed Windows 8 and totally forgot that I had to reinstall this... ( which originally took me 8 hours to figure out the first time! Lol ) this will definitely help future HTC people out...
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
x70xchallengerx said:
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
Click to expand...
Click to collapse
USB 3.0 gets a bad rep. I do a lot of my adb with a USB 3.0 with few issues
Sent from my HTC6525LVW using Tapatalk
OP Updated
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
x70xchallengerx said:
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
Click to expand...
Click to collapse
wtoj34 said:
USB 3.0 gets a bad rep. I do a lot of my adb with a USB 3.0 with few issues
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I am aware that USB 3.0 does cause issues with adb, mostly the longer running ones it hangs sometimes, I don't have an answer for that right now, I am running with 2.0 still and I have zero issues.
This is something that I came across that seemed to resolve a lot of adb issues
USB 3.0 Help with ADB
also
XDA Thread I found that in
cant launch sdk manager
After installing abd on Windows8.1 64 is there a trick to launch so that i can add and update?
Fixed issue. New pc and forgot to install java...?
bdorr1105 said:
Android SDK - Powerful tool and easy to set up for use with your HTC One M8
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
Part 2. Verifying ADB is set up properly and Working
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
Click to expand...
Click to collapse
davidmatt34 said:
After installing abd on Windows8.1 64 is there a trick to launch so that i can add and update?
Fixed issue. New pc and forgot to install java...?
Click to expand...
Click to collapse
Thanks for sharing that, I added that as note in the OP...Glad you are setup and good to go
I feel like such an idiot, but I want to be sure I'm getting the latest HTC Sync... I follow the link in the OP and it takes me to support.. I Google and the same thing happens.. They move it over at HTC?
I found it here... http://www.htc.com/us/support/software/htc-sync-manager.aspx
And this worked flawlessly!! I was always afraid of going back to Windows 8.1 because of ADB/Fastboot being broken.. so far so good!! Side loading soon!!
jbarcus81 said:
I feel like such an idiot, but I want to be sure I'm getting the latest HTC Sync... I follow the link in the OP and it takes me to support.. I Google and the same thing happens.. They move it over at HTC?
I found it here... http://www.htc.com/us/support/software/htc-sync-manager.aspx
And this worked flawlessly!! I was always afraid of going back to Windows 8.1 because of ADB/Fastboot being broken.. so far so good!! Side loading soon!!
Click to expand...
Click to collapse
Glad everything is working, the link in my OP went to the same exact HTC Sync Manager yours did, pull yours you posted and mine side by side its the same, not sure what happened, either way glad you are up and running
bdorr1105 said:
Glad everything is working, the link in my OP went to the same exact HTC Sync Manager yours did, pull yours you posted and mine side by side its the same, not sure what happened, either way glad you are up and running
Click to expand...
Click to collapse
Yeah.. the link just wasn't working at the time.. weird..
jbarcus81 said:
Yeah.. the link just wasn't working at the time.. weird..
Click to expand...
Click to collapse
Thanks for the update
Sent from my HTC6525LVW using Tapatalk
Also make sure you don't have drivers installed for another phone.. ADB couldn't find my M8 until I uninstalled my lg spectrums drivers on Win 8.1
Sent from my HTC6525LVW using XDA Free mobile app
Nice job.. Thanks for this. My first W8.1 machine.
Guys can someone help ,,
everything is installed and still getting the following error :
C:\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH44FWM09049 device
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
< waiting for device >
i've been trying to fix this for the past 4 hours but no luck ,, anyone ??
I$ device in fastboot mode?
nvmd
without changing environment variable we can even hold shift+right click the folder containing the adb and open command window from the menu isn't it?
technochatter said:
without changing environment variable we can even hold shift+right click the folder containing the adb and open command window from the menu isn't it?
Click to expand...
Click to collapse
Yes.
Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!
do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)
CSquared4290 said:
Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!
Click to expand...
Click to collapse
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Thanks Mr. Hoax! I will give that a try and report back.
Interestingly in an attempt to use ADB Sideload to install the latest ROM update from scratch, I took a gamble and did a full format/wipe and was able to install the OS using ADB SideLoad. But afterwards, it still didn't come up under ADB Devices...But will try your recommendations and see what happens.
Elkhantar said:
do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)
Click to expand...
Click to collapse
Yessir, Debugging was enabled through the OS (I don't know of any other way to enable debugging?)
Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Wug's tookit for bacon hv step by step procedure to install adb n fastboot drivers...gv it a try...i did it myself n it works nice
1+1
CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
After drivers installation is done, you need to reboot your OPO in bootloader(fastboot) mode and type
fastboot devices
And check out if the prompt shows your device serial number.
I see you're using the nexus driver. Perhaps try a Samsung ADB driver. It works with my phone without problems.
I get the same problem with my work PC, while everything works fine at home.
What CSquared4290 says, applies here:
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
- All my drivers are up to date
- My Android SDK is up to date
The phone is recognised normally under command > fastboot devices.
Symantec Endpoint Protection is running at my work PC. Could this be a reason?
CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
100% agree with the other posters, really delete all of your old USB ADB drivers, including the Google USB driver. Here's a tool I use for that: http://www.nirsoft.net/utils/usb_devices_view.html
Install Samsung ADB drivers, then when you plug your OPO in you should be able to see it in Device Manager as "Android Device" don't let Windows pick the driver. Right click and pick the browse my computer for drivers, then find the Samsung Android ADB Interface, install that. Unplug your phone, then plug it back in...profit? Good luck!
From my OnePlus X rooting guide. It looks like you need to install the universal adb driver linked in #2 and follow the steps in #3.
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
Click to expand...
Click to collapse
I made this installer as a kind of "update" the old driver package I had made for Ainol and Actions before.
While at it I added those two tools usually used, that is adb and fastboot.
Based on batch scripts, so it's open source.
Self Signed, not need to do annoying reboots and other tricks.
Tested working using VirtualBox, from XP to Win10, both 32 and 64 bit. Edit: Tested working on Win11.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(five seconds wasted)
Download: https://yadi.sk/d/Xwt9cfb73HFhgA
The Readme.txt included is below.
-------------------------------------------------------
Yet Another Universal ADB Driver Package (+adbupdate)
-------------------------------------------------------
By CXZ (Slatedroid,Freaktab) / CXZa (XDA,4pda)
http://cxzstuff.blogspot.com
DISCLAIMER: No guarantee of any kind. Use at your own risk!
-------------------------------------------------------
Yet Another Universal Android Debug Bridge USB Driver
-------------------------------------------------------
Uses universal adb trick used in some (unsigned) packages before.
It works but fails in inf2cat signability test. Maybe there are reasons for that?
Signability test failed. Errors:
All Universal Serial Bus (USB) devices must have VID and PID sections in the PnP Device ID string.
Third-party USB function drivers must not install through a compatible ID match.
The following formats are not acceptable:
USB\Class_ii, USB\Class_ii&SubClass_jj, USB\Class_ii&SubClass_jj&Prot_kk
Can be uninstalled through the Control Panel.
Other choices: https://www.google.com/search?q=adbdriver
-----------------------------------------------------------
Leave YAUADBdriver certificate to the cert stores
-----------------------------------------------------------
Instead of deleting the YAUADBdriver certificate after
installing the driver, it's left into the certificate stores.
This is maybe needed in the newer Win10 versions. --> http://
www.anandtech.com/show/10747/examining-win10au-driver-signing-policy
Should be safe as certificates cannot be used without the
private key and I deleted the self signed certificate used
immediately after signing the driver. Certificate will
be added to Root and TrustedPublisher stores having
"___YAUADB-driver" as its name so it's easy to find.
-----------------------------------------------------------
ADB-Prompt (bat), ADB (version 1.0.32) and Fastboot
-----------------------------------------------------------
Installer just extracts the files to the chosen folder
and creates shortcuts to the SendTo subfolder.
Read the Readme.txt in SendTo subfolder for more info.
To uninstall just delete the folder (and shortcuts created).
There are newer versions than 1.0.32, but it was selected
on purpose because it's the last version that remembers
the previous shell commands used.
If a newer is needed use my "Yet Another ADB + Fastboot Updater"
which is now included in the package. For more info --> https://
https://forum.xda-developers.com/an...er-package-t3595277/post74097138#post74097138
ADB-Prompt (bat) allows one to avoid typing that darn
"adb" before every single adb command...
-------------------------------------------------------
ADB Prompt - h=open adb help in notepad, q=quit, c=cmd /k
v=add vendor IDs to adb_usb.ini, r=root+remount
-------------------------------------------------------
Remove the old ADB OEM Driver installations
-------------------------------------------------------
Uninstalls all the oem*.inf ADB Driver installations
including the YAUADBdriver (if it's installed).
(use the Control Panel for uninstalling the YAUADBdriver)
-------------------------------------------------------
Remove the old ADB Driver registry entries
-------------------------------------------------------
Removes the old ADB Driver registry entries.
Reboot possibly needed before ADB can be used.
-------------------------------------------------------
Looking for adbupdater or adbupdate? See the eighth post.
https://forum.xda-developers.com/an...er-package-t3595277/post74097138#post74097138
Changed but not updated.
Just minor adjustment done so that the version number is the same everywhere.
So, no need to re-download.
Suddenly like a hundred downloads more at the Yandex.
Either this has been praised elsewhere by someone, or that
someone has problems downloading from the Yandex link.
That many download problems? Probably not - but
here is a local download link - just in case.
edit: This local package doesn't include Yet Another ADB + Fastboot Updater - yet.
You can download it from here: https://forum.xda-developers.com/an...er-package-t3595277/post74097203#post74097203
PS: Please, do NOT share this elsewhere (Yandex link or this ok).
I want to be able to update if necessary.
edit: attachment removed. Use Yandex link instead. A bit easier if less places.
Download: https://yadi.sk/d/Xwt9cfb73HFhgA
Over 300 downloads, but no comments (nor thanks) what so ever.
Did I manage to do it too good at the first time?
(AFAIK, this installer is the only one - at the moment - being truly universal and in the same time
correctly signed. Checked some like a year ago, but I don't think they have changed much.)
(snip)
Hi, just checked your tool... i m in bootloop of death, can your tools unlock my Bootloader in fastboot command ? i m not able to access Recovery (Stoct or TWRP) .. only fastboot i can access
vijaygogawale said:
Hi, just checked your tool... i m in bootloop of death, can your tools unlock my Bootloader in fastboot command ? i m not able to access Recovery (Stoct or TWRP) .. only fastboot i can access
Click to expand...
Click to collapse
I believe it depends on what kind of bootloader and tablet you have there.
I have fastboot in one MTK tablet only. I don't think its bootloader was locked.
And with it it's easier to use their flashing tool. So I haven't used fastboot much myself.
The adb (and also fastboot) in this installer is a bit older - on purpose.
I think that it might be better that you use the latest versions instead.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
CXZa said:
Over 300 downloads, but no comments (nor thanks) what so ever.
Did I manage to do it too good at the first time?
(AFAIK, this installer is the only one - at the moment - being truly universal and in the same time
correctly signed. Checked some like a year ago, but I don't think they have changed much.)
(snip)
Click to expand...
Click to collapse
Thank you for "YAUADP" it worked flawless on my Windows 8.1 x64.
Don't worry about having huge download counts but no thanks or replys.
This forum has grown so big. There are alot of passive users. Who download but don't comment or click thanks.
Simply count your downloads as "thanks"
Yet Another ADB + Fastboot Updater
I was about to add this ADB + Fastboot Updater tool into the YAUADBdriver package,
but decided to publish it is as separate download instead.
Just put it to the ADB-Prompt folder and run to update the programs if needed.
This stand alone program can also be used without the YAUADBdriver .
Just put it any folder (preferably to an empty one) and run...
Download the exe: https://yadi.sk/d/UWsvoEsV3ReyeJ
Download zipped: https://yadi.sk/d/nZTi7Eqx3NcBwW
Tested working using Win7, Win8 and Win10.
DISCLAIMER: No guarantee of any kind. Use at your own risk!
The Readme included is below. (It, ini and bat files will be extracted on the first run.)
----------------------------------------------------------------------------
Yet Another ADB + Fastboot Updater
(companion for Yet Another Universal ADB Driver Package)
----------------------------------------------------------------------------
by cxz (slatedroid,freaktab) / cxza (4pda.ru,xda) /
http://cxzstuff.blogspot.com/
-------------------------------
Key names used in adbupdate.ini (extracted on the first run)
-------------------------------
adburl - from where to download the zip archive (platform-tools-latest-windows.zip)
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
http://dl-ssl.google.com/android/repository/platform-tools-latest-windows.zip
adbolddate - previous file time at the server.
adboldsize - previous file size at the server.
daysbetweenchecks - check updates every X days. if 0 (zero) startup check is not done.
to enable startup check, define the value and run the program once.
program's shortcut is then created to "Start Menu/Startup" folder.
to disable startup check, change value to 0 and run the program once.
lastcheck - when the latest check was done
adbupdateerror - if more than 0 and startup check is on, checking is done on the next startup.
startupdelayminutes - delay checking X minutes at the startup.
targetfolder - define where to extract ADB + Fastboot files. Run program as Admin and
use for example C:\windows as the target folder to run them system-wide.
addtothepath - if "a", add current exe dir or the target dir to the path and use adb system-wide.
removing: change to "r", and re-run to remove targetfolder/current dir from the path.
(do not change the targetfolder value if any, or removing it from the path will fail)
(value "ok" means that the folder is now in the path variable)
useragent - define the user-agent used. max 256 characters.
makebackups - backup the files to be replaced to the adbupdate.exe\~backup folder. 1=yes.
keepthezip - the platform-tools zip is saved to the adbupdate.exe\~platform-tools folder. 1=yes.
extractfile1 - files to be extracted. 1, 2, 3 and so on. Use full paths inside the zip.
the files are extracted to the targetfolder/adbupdate.exe folder
without using the paths inside the zip.
Both ADB and Fastboot are terminated if running before updating
(or installing if the ADB is not in the target folder).
Yet Another ADB + Fastboot Updater
Local copy. Removed. See the previous post.
Added it also to the Yet Another Universal ADB Driver Package zip but not into the installer yet.
PS: Please, do NOT share this elsewhere (Yandex link or this ok).
I want to be able to update if necessary.
Yet Another ADB + Fastboot Updater
Update. The download addresses are the same.
Now ADB + Fastboot are only terminated if they are updated/installed.
Also added a batch file for automatically checking updates and updating
ADB + Fastboot if they are installed system-wide (e.g. c:\windows folder,
keep adbupdate.exe in another folder so windows update doesn't remove it)
(if previously downloaded just the exe, delete the readme file to get its last version.)
edit:
adbupdate_scheduled-task batch file removed. It works, but I forgot that
(after xp?) windows does not allow user interface on system tasks. Sorry.
Yet Another ADB + Fastboot Updater
CXZa said:
adbupdate_scheduled-task batch file removed. It works, but...
Click to expand...
Click to collapse
A version in which above works, or a such that adds the target folder to the path
thus allowing system-wide usage might come some day in the near future.
In the meanwhile system-wide ADB can be updated "semi-automatically" like this .
Use two folders. One that checks updates, and another that has c:\windows as the target folder.
Then when a new update is found, let it update the first one and then run another as admin.
Disabled commenting at Yandex downloads.
Someone has been posting there a download link of a small
executable telling (in Russian) that it would be an updated version.
It is not. It could be a virus, so do NOT execute it!
Комментирование отключено в Яндекс.
Кто-то отправил ссылку, чтобы загрузить небольшую
исполняемый файл, говорящий, что это будет обновленная версия.
Не является. Это может быть вирус, поэтому НЕ запускайте его!
Hi, I wanted to try your installer but I got a little bit confused by all the packages and updates
Which one is the right one to install?
provolinoo said:
Hi, I wanted to try your installer but I got a little bit confused by all the packages and updates
Which one is the right one to install?
Click to expand...
Click to collapse
The one that is mentioned in the 1st post is always the latest.
This one: https://yadi.sk/d/Xwt9cfb73HFhgA
Now it has "Yet Another ADB + Fastboot Updater" included, but as separate installation - one doesn't have install it.
Latest "Yet Another ADB + Fastboot Updater" as separate installer program:
https://forum.xda-developers.com/an...er-package-t3595277/post74097138#post74097138
(the yadi.sk download addresses always stays the same )
provolinoo said:
Hi, I wanted to try your installer but I got a little bit confused by all the packages and updates
Which one is the right one to install?
Click to expand...
Click to collapse
So, what was the result? YAUADBdriver should work with any device.
Universal adb driver packages are a good option when one doesn't have
a driver package meant for your device. But obviously it's always best to
use a driver package by the manufacturer...
Yet Another ADB + Fastboot Updater
CXZa said:
A version in which above works, or a such that adds the target folder to the path
thus allowing system-wide usage might come some day in the near future.
Click to expand...
Click to collapse
Okay, I now updated the Yet Another ADB + Fastboot Updater.
It now has option to add target or the exe path to the path variable
thus enabling using adb system-wide without big windows updates
messing it by removing exe from the win subdirs.
(It wasn't really a big problem, easily fixed by re-running the program. Then again,
adding dir to the PATH has that advantage that admin rights aren't needed anymore
thus enabling that automatic adb update to work better when adb is used system-wide...)
Anyway, now are all the files at Yandex(yadi.sk) updated.
(The Yet Another Universal ADB Driver Package has still adbupdate as separate exe in its own folder.)
Here are the download links again for those lazy ones:
Yet Another Universal ADB Driver Package: https://yadi.sk/d/Xwt9cfb73HFhgA
Yet Another ADB + Fastboot Updater as exe: https://yadi.sk/d/UWsvoEsV3ReyeJ
Yet Another ADB + Fastboot Updater zip-file: https://yadi.sk/d/nZTi7Eqx3NcBwW
PS: If you have used an older adbupdate before, remove/rename the old ini and readme files in its folder
in order to get them updated as well.
Yet Another ADB + Fastboot Updater
Nice round number of downloads after this last update.
Altogether four and half thousand or more. That is if these two
program DLs are put together. Any feedback/suggestions of any kind?
There was some asking in "15 second installer" thread about device not showing.
The reason probably is that it, at least when I previously checked, uses Google's
vendor ID. If your device manufacturer use its own, you have to install driver
package provided by them, or use some universal one - like this YAUADBDriver...
CXZa said:
Nice round number of downloads after this last update.
Click to expand...
Click to collapse
Was 666. Not that round really. But now it is, the last update has exactly one
thousand downloads altogether...
To my knowledge these two packages of mine work as expected.
So they are not updated anymore - unless the users give some good reasons for it...
CXZa said:
To my knowledge these two packages of mine work as expected.
So they are not updated anymore - unless the users give some good reasons for it...
Click to expand...
Click to collapse
In another thread I came to think that some beautiful day the adbUpdater might not work anymore. But no worry, an update is coming soon before that. Then you can decide what files to extract, etc...
At the moment it doesn't extract for example the libwinpthread-1.dll as it was only used like one fastboot version. I don't know why it's still in the zip. Maybe it's used for something else?? Please tell if you know more, or if your device needs it, etc...
So, what to download from this a bit messy thread of mine? Here are the links again:
Yet Another Universal ADB Driver Package: https://yadi.sk/d/Xwt9cfb73HFhgA
Yet Another ADB + Fastboot Updater as exe: https://yadi.sk/d/UWsvoEsV3ReyeJ
Yet Another ADB + Fastboot Updater zip-file: https://yadi.sk/d/nZTi7Eqx3NcBwW
@kk131
There is one my friends again giving me thanks. Thanks buddy for your support!
(BTW, if you all would say something it would easier for me to thank you back... )