Database Info

Found Answer To Windows XP 32 Bit Driver install Error

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.

[Tutorial] How to install Android SDK/ADB tool & HTC's drivers [BEGINNER FRIENDLY]

[Tutorial] How to install Android SDK/ADB tool & HTC's drivers [BEGINNER FRIENDLY]
[SIZE="+1"]-- Android SDK/ADB tool Tutorial --[/SIZE]​
I decided to create this Beginner Friendly tutorial on how to install SDK tool mainly because recent phones such as the i.e. HTC One X / One X+ are requiring many basic usage of adb command line, and lots of members are having difficulities to have basics adb command to work because their SDK tool is not correctly installed. I won't show you how to make usage of it, there is plenty of How-to's for that purpose all around xda and on the Web.
This is all safe to install on your Windows based computer, and if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device. From now on, I or anyone else on the Internet can not be held responsible if something really bad is happening to you because you didn't read and followed any given instructions letters by letters and you ended with a screwed, pricey and valuable paperweight device. That being said, let's get started.​
Let's GO!
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
{
"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"
}
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
This is it, I hope this tutorial was helpful, if you have some sort of problems let me know, I will try to help you at the best of my knowledge. Have fun hacking your Android!!

Lucky Thirteen said:
...if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device.
Click to expand...
Click to collapse
Excellent tutorial... but I disagree with this line. No process is bulletproof and there is no way a tutorial can account for all the variables with Windows.
Which explains why I am now asking for help!
This is my third Android phone and fifth Android device. I've rooted all five and installed multiple ROMs and for the most part have not had too many problems.
I'm currently running Elegancia 5.3.0 on my AT&T One X+ and have a few issues that I'm tired of dealing with. I decided to flash the RUU to go back to stock and also to update to hboot 1.4 which is required for the Blackout ROM I was thinking about trying. The RUU cannot find my phone unless I connect while in the bootloader. Even then though, the RUU flash still fails. Since it cannot see my phone while it's running, I decided to check if ADB can see it. Nope. No luck at all. I have connected with ADB to my device many, many times... but it has been close to a year since the last time I did. I removed all HTC drivers and Sync from Add/Remove Programs, deleted my old version of the SDK and Java and followed your tutorial step-by-step.
My phone still shows up in Device Manager under PORTABLE DEVICES and I can't seem to make it connect any other way.
Please tell me you have a suggestion to help me fix this. I've tried using every combination of search terms I can think of and have had no luck for the past 36 hours.

Finally fixed my ADB problem using these steps in case anyone else runs into it.

This worked great for me after two days of trying to get my phone to connect. I had to uninstall everything related to java, android, and htc, and the link for the htc drivers was dead so I just reinstalled sync manager, but it all works now, much thanks. All this effort was just so I could put my music on the phone, and so that I could do a full backup to my pc without rooting.

Yet Another Universal ADB Driver Package and adbupdater for Windows

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... )

[TOOL] MobyDroid (Android Device Manager for Linux, Windows and MacOS)

Hello every one,
MobyDroid is a simple and cross-platform Android Devices Manager.
It runs on any operating system with Java support (Mac OS X, Windows, Linux, BSD, Solaris...).
THIS IS JUST A BETA RELEASE !
I have been running linux from while now. And what I noticed is there is no GUI Android Devices Manager until now (QtADB didn't work for me).
Basicly I kept using ADB command line and kept waiting for someone to make something or some alternatives.
Some day a friend of mine kept complaining about the same problem. After that, I decided to make a simple Apk installer with a graphical user interface. And something lead to another.
And I wanted to share it for any one having the same problem.
So here it is !
Prerequisites
Java Runtime Environment (JRE) 1.8 or later
ADB
BETA
THIS IS JUST A BETA RELEASE !
So you should expect a ton of bugs or crash issues.
if you encounter an issue or have a great ideas please file an issue.
Download
You can download from here.
Authors
Bilux ([email protected])
Link
MobyDroid
https://github.com/ibilux/MobyDroid
Screenshots
{
"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"
}

ibilux said:
Hello every one,
MobyDroid is a simple and cross-platform Android Devices Manager.
It runs on any operating system with Java support (Mac OS X, Windows, Linux, BSD, Solaris...).
THIS IS JUST A BETA RELEASE !
I have been running linux from while now. And what I noticed is there is no GUI Android Devices Manager until now (QtADB didn't work for me).
Basicly I kept using ADB command line and kept waiting for someone to make something or some alternatives.
Click to expand...
Click to collapse
this is kinda long term general issue, most of manufacturers had their own app, samsung, htc, lg, and there is no general solution android manager, so this could be a start of a big project. good luck
Sent from my ONE A2005 using Tapatalk

chxei said:
this is kinda long term general issue, most of manufacturers had their own app, samsung, htc, lg, and there is no general solution android manager, so this could be a start of a big project. good luck
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Thank you very much.
As a start, I'm just trying to give back to the XDA and open source community.

Nice work keep up ???

@ibilux
Hi, is this project discontinued?
Any plans for future development?
Thanks!

EuK_V said:
@ibilux
Hi, is this project discontinued?
Any plans for future development?
Thanks!
Click to expand...
Click to collapse
I just didn't have anything to add.
But, if you have an issue or feature, I'll look into it.

ibilux said:
I just didn't have anything to add.
But, if you have an issue or feature, I'll look into it.
Click to expand...
Click to collapse
Thank you, for your reply!
First of all I'd like to say that I am interested more in the "File manager" function of the app. And if you don't mind I have some suggestions:
I am faced with the following: when I start the app I don't have full root access, though "su root permissions" is checked in settings. I can browse the root directory, but cannot create or delete any file or folder. There is a workaround: if I start adb as root from my Ubuntu terminal executing:
adb root
after that I have full root access to my phone. It works this way, but I think since Mobydroid is a gui to adb, it should be able to start adb as root.
Also it would be great if the app could start adb via wifi (I don't know maybe add an option to choose how to connect via usb or network. Now if I start adb via network in terminal executing:
adb connect 192.168.0.101:5555
Mobydroid then works well. Again I need to make some actions outside the app before I start it. (BTW IP address of a device is just an example)
Another thing I'd like to say is that Mobydroid when viewing a device shows symlinks to folders as files and you cannot enter them. On the side of Ubuntu it works well, symlinks to folders work as folders and you can enter them. See my screenshot.
And it would be great to have sort options like "folders first" to sort folders before files and to sort dot folders (.folder) after regular folders and dot files after regular files. Like it works in most linux FMs.
Hope this wouldn't be too overwhelming...
Thanks!

EuK_V said:
Thank you, for your reply!
First of all I'd like to say that I am interested more in the "File manager" function of the app. And if you don't mind I have some suggestions:
I am faced with the following: when I start the app I don't have full root access, though "su root permissions" is checked in settings. I can browse the root directory, but cannot create or delete any file or folder. There is a workaround: if I start adb as root from my Ubuntu terminal executing:
adb root
after that I have full root access to my phone. It works this way, but I think since Mobydroid is a gui to adb, it should be able to start adb as root.
Also it would be great if the app could start adb via wifi (I don't know maybe add an option to choose how to connect via usb or network. Now if I start adb via network in terminal executing:
adb connect 192.168.0.101:5555
Mobydroid then works well. Again I need to make some actions outside the app before I start it. (BTW IP address of a device is just an example)
Another thing I'd like to say is that Mobydroid when viewing a device shows symlinks to folders as files and you cannot enter them. On the side of Ubuntu it works well, symlinks to folders work as folders and you can enter them. See my screenshot.
And it would be great to have sort options like "folders first" to sort folders before files and to sort dot folders (.folder) after regular folders and dot files after regular files. Like it works in most linux FMs.
Hope this wouldn't be too overwhelming...
Thanks!
Click to expand...
Click to collapse
Root and wireless connection features has been implemented in version v0.4.
I'll implement symbolic links and folders order in next release.

Thanks. Works good, but it can't sort dirs/files by name or date.

sorry but it doesn't work

@rifkican, enable adb in developer settings.

Is this still working? I tried to run it but i get this error:
[CheckBinaries] : I: couldn't create file: Read-only file system.

pabekam said:
Is this still working? I tried to run it but i get this error:
[CheckBinaries] : I: couldn't create file: Read-only file system.
Click to expand...
Click to collapse
What platform are u using ? and how did u install MobyDroid ?

ibilux said:
What platform are u using ? and how did u install MobyDroid ?
Click to expand...
Click to collapse
Windows. I downloaded the Standalone version, installed java and run the command over cmd. MobyDroid starts but in the cmd i get the error message. In MobyDroid when i go to the file manager, it doesnt show me any files/folders on my phone

pabekam said:
Windows. I downloaded the Standalone version, installed java and run the command over cmd. MobyDroid starts but in the cmd i get the error message. In MobyDroid when i go to the file manager, it doesnt show me any files/folders on my phone
Click to expand...
Click to collapse
can u provide full log errors.

ibilux said:
can u provide full log errors.
Click to expand...
Click to collapse
how do i do that?

ADB no longer works with devices I have used for years

I originally posted in the "Ask ANY Question. Noob Friendly" thread but got no replies so am trying again in its own thread. I just find it hard to believe no one has seen a similar problem anywhere....
ILikeOldStuff said:
I've been using ADB for some years on several devices but recently ran into a snag. On the same machine (an older desktop running XP) where it has always worked before, I recently tried to use it but got an odd error message:
E:\platform-tools> adb version​Android Debug Bridge version 1.0.32​Revision 57224c5cff69-android​​E:\platform-tools> adb devices -l​List of devices attached​* daemon not running. starting it now on port 5037 *​ADB server didn't ACK​*failed to start daemon *​error: cannot connect to daemon: No error​error: cannot connect to daemon: No error​​I tried to google it but everything I found either assumed there was a problem with eclipse, with wifi, with not using correct cables, not installing drivers, etc. But NOTHING about a case where it used to work but for some reason no longer does.
I do not (and never did have) have eclipse, nor even the android SDK installed, just the much smaller platform-tools thing. The desktop box does not have any wifi radio hardware so I can rule those out. It also is not a usb port or cable issue as I can still transfer files through MTP.
It is not really a device issue as it suddenly started happening on ALL android devices including ones I used it on before. And it isn't a case where the device updated to change anything as these are older devices running FroYo, IceCreamSandwich, Jellybean, and Oreo, where updates stopped many years ago.
I don't think it is a device driver issue as all devices I tried do show up properly in device manager.
The last time it worked was 25Sep2022 when I adjusted some permissions on the BetterBatteryStats app. I did not need it again until recently when it started doing the above error message.
Has anyone seen anything similar or have an idea how to fix it?
Click to expand...
Click to collapse
I will add that I have tried disabling AV and adding extra permissions to the firewall (which were never needed before as the process was always local) to no avail. I have never had genymotion installed (another common culprit according to various google hits). There does not seem to be anything useful in system event logs either. And Task Manager does show the adb process is indeed running.
One question I have , is how to get more clues for solving this problem. I thought firewall logs might show if that was blocking anything, so set it to log all connection activity attempts but it is not showing up in firewall logs, which makes me think the problem is elsewhere.
I see that some apps can write things to system event logs, but ADB seemingly has not done this. Is there some setting to make it write event log entries, or any other way it can be made to write some debug logging details somewhere?
Any other thoughts of how to solve this?

To start, I suggest using the latest version of platform-tools-latest-windows.zip.
or use mAid:
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com

Update ADB: dowmload latest version from here
Releases · K3V1991/ADB-and-FastbootPlusPlus
A small Application for Windows that allows you to install the latest Version of ADB and Fastboot Files on the Computer without installing the entire Android SDK Package + Toolkit & Commands - ...
github.com
{
"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"
}

ze7zez said:
To start, I suggest using the latest version of platform-tools-latest-windows.zip.
or use mAid:
Click to expand...
Click to collapse
Sadly I can't do either of these. Platform tools R23 (that I have been using) is the last one that is compatible with Windows XP. And this desktop box is running on an old P4 processor, which is 32bit only, with no hardware support for virtualization either, so mAid does not look compatible.
xXx yYy said:
Update ADB: dowmload latest version from here
Click to expand...
Click to collapse
Again, that looks like too new of a version of platform_tools to be compatible with XP.
But thank you both for at least trying to help!
What bugs me, is that debugging mode USED to work, until recently when it didn't.

ILikeOldStuff said:
...
Again, that looks like too new of a version of platform_tools to be compatible with XP.
...
Click to expand...
Click to collapse
The ADB driver ( has nothing to do with platform tools package ) since ever is 32-bit, hence it will work with Windows XP, too.

xXx yYy said:
The ADB driver ( has nothing to do with platform tools package ) since ever is 32-bit, hence it will work with Windows XP, too
Click to expand...
Click to collapse
While it may be still 32 bit, it does not work anymore with Windows XP since it uses functions that are only available in Vista & up. It gives an error message:
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.​

Time to change OS version or update WS2_32.DLL ( read: WinSock 2 DLL - the system file that contains the Windows Sockets API, an important software that is used to run most network and internet applications ) .

Right, v23 is latest version working for Windows XP (and still works). delete the %userprofile%\.android folder and try again (do backup if necessary)

alecxs said:
delete the %userprofile%\.android folder and try again
Click to expand...
Click to collapse
This took a little longer before it eventually gave a similar error message :
E:\platform-tools> adb devices -l​List of devices attached​* daemon not running. starting it now on port 5037 *​* daemon started sucessfully *​** daemon still not running​*failed to start daemon *​error: cannot connect to daemon: No error​error: cannot connect to daemon: No error​​but Task Manager shows adb.exe is indeed running, and my firewall log reports that adb.exe is listening on port 5037, and is not blocked.

what firewall? is that the cause? disable completely?

Comodo 3.14.130099.587
I don't really think it is the cause, it has been running on the machine since even before the first use of ADB and never caused an issue before, allowing ADB to work in the past. Also ADB has never showed up in the logs as having been blocked.
I might try disabling it later tonight when I get home.

do a search on whole disk for other adb.exe make sure you haven't running multiple instances.

ILikeOldStuff said:
...
​but Task Manager shows adb.exe is indeed running, and my firewall log reports that adb.exe is listening on port 5037, and is not blocked.
Click to expand...
Click to collapse
In a previous post you stated ADB.EXE doesn't work due to missing or invalid shared system library file named WS2_32.DLL file.
Why not fix this issue as 1st thing of all things?
ws2_32.dll free download | DLL‑files.com
Download ws2_32.dll free! Fix DLL missing error. Solve it yourself or get help using DLL‑files.com Client to fix DLL error automatically.
www.dll-files.com

xXx yYy said:
In a previous post you stated ADB.EXE doesn't work due to missing or invalid shared system library file named WS2_32.DLL file.
Why not fix this issue as 1st thing of all things?
Click to expand...
Click to collapse
It is neither missing nor invalid. There is Ws2_32.dll version 5.1.2600.7074 present in \Windows\system32. This is the latest version for XP, from installing MS16-077 KB3161949 ; it just does not have (and was never intended to have) the WSAPoll function that was introduced in Vista.
This error message only happens if I try to run the latest version of ADB, which is no longer compatible with XP. I do not see this when I stay with the r23 version that is the last one compatible with XP.
xXx yYy said:
Time to change OS version or update WS2_32.DLL
Click to expand...
Click to collapse
Installing a newer Windows OS is not really an option for this older hardware; it just does not have the RAM nor CPU horsepower for anything beyond XP. There is also the lack of device drivers for older hardware, and I am not willing to do without such "frills" as a working video card, ethernet adapter, parallel printer port, and other items which I use on a daily basis but are not supported by W10.

alecxs said:
what firewall? is that the cause? disable completely?
Click to expand...
Click to collapse
ILikeOldStuff said:
Comodo 3.14.130099.587
I don't really think it is the cause . . .
I might try disabling it later tonight when I get home.
Click to expand...
Click to collapse
I finally got around to trying this, and it turns out you were right and I thought incorrectly. So thanks for the reminder to re-check the obvious.
alecxs said:
do a search on whole disk for other adb.exe make sure you haven't running multiple instances.
Click to expand...
Click to collapse
The only other copies of adb.exe that I have are inside the .zip files for other newer (no longer XP compatible) versions of platform-tools. I left them inside the .zip files and unzipped only the r23 version to prevent accidentally running the wrong ones.
Task Manager mostly only showed the one instance. The only time I could see multiple was when I disabled the firewall, started one, re-enabled the firewall, then did another "adb devices -l"; repeating this sequence several times would produce one additional instance for each repeat. Using task manager to kill the extras allowed the remaining one to work properly provided the firewall was disabled.
So I can still run the r23 version of ADB after all, although the workaround of disabling first the ethernet and then the firewall is inconvenient to say the least, and hardly ideal.
I am still confused why Comodo FW clearly is blocking this while not logging that action. And also why it is blocked at all when I am using only a USB cable and neither ethernet nor wifi networks. Even moreso why it USED to work with no need to disable the firewall but no longer does.
Looks like getting these other questions sorted will need some visits to the Comodo forums.

adb client communicates with adb server via TCP. here is list of ports you must whitelist in firewall.
https://developer.android.com/tools/adb