Hi there,
I`ve got the following Problem:
My One is not detected properly in fastboot mode, adb works like a charm (all cmds working)
In fastboot mode windows says that the device cannot be started (code 10) and cmd cannot find the device and it`s also not charging in fastboot...
I`m using Windows 8 and I know that there are problems with driver signatures, so I disabled the checks through advanced boot, uninstalled all drivers and reinstalled them (the strange thing is, it worked like a charm with my HOX)
After that still the same issues... Then I uninnstalled the HTC drivers and tried the drivers from Google SDK and after that the drivers from PDAnet but nothing helped...
Then I read that there are Problems with USB3.0 and fastboot but I only got USB3.0. So I tried different USB ports and reconnected many times (about 30 times) and maybe the phone says "fastboot USB" but in cmd it`s still not detected...
As I said before with my HOX it worked like a charm... (also Win8 and USB3.0)
Any ideas?
Thanks for your help!
togx
Try disabling Fastboot in the Power Settings.
I tried it again with fastboot disabled but it still doesn`t work... :/
same problem here....
envoy_467 said:
same problem here....
Click to expand...
Click to collapse
hey envoy_467,
I found a solution for this issue:
It seems that microsoft´s own driver for the Intel USB3.0-Host breaks the support for several devices. You can install the Intel drivers for Win7 on Win8 (search google: Windows 8 and Intel USB3.0 host controller there should be a link to plugable. I´m not able to post links cause I don´t have enough posts...) but it only works with the Intel host.
Hope it will help you too!
greetz,
togx
usb device not recognized
I'm having a similar problem using windows 8, but I tried both my usb 2.0 and 3.0 ports but results in same problem. I have a t-mobile HTC One S (JB 4.1.1). Everytime I try to do the fastboot to get my token id my pc tells me my usb device is not recognized. Does anyone have any suggestions? Thanks in advance!
Try THIS
Sorry to bump this thread, but it's better than creating a new one.
Anyway, I have the same issue as the others here: fastboot won't work at all.
Btw, I've tried all possible solutions but installing the intel driver isn't possible due to a limitation on Windows + Intel 8 Series.
Windows 8, Intel 4th generation processor (8 Series/220) on a Gigabyte GA-Z87N-WIFI.
USB eXtensible Host Controller driver by Microsoft can't be modified to work with the Intel 8 Series driver. When trying to install it it says that my PC doesn't have the requirements to install the program (driver can be found here -- 8 Series ONLY!!) probably because I'm on Windows 8 (no, setting the app to run with Win7 compatibility mode doesn't work either).
Using Naked Driver 0.72..
Has anyone tried with a virtual machine? Maybe I could install Ubuntu on a VM to test it when I get the time.
Any other ideas?
VM doesn't work.. Since Windows won't recognize the phone while on fastboot that means that the VM Linux won't find the devide either.
LiveUSB won't install the android SDK either.. I'm stuck..
FIXED, kinda.. Workaround on Linux.
More info:
Just did it..
But not on Windows..
I've created a LiveUSB from Ubuntu 12.04 using the "Universal USB Installer" from: http://www.pendrivelinux.com/downloads/
When creating the LiveUSB I've created with 4gb (4096mb) of free space on a 16gb flash drive just in case, but you can make it work with a 4gb flash drive.
Then I installed the Android SDK.
Then I was able to use fastboot to change the CID to 11111111.. Working great.. Now let's download the developer ruu..
Tutorial used to install the SDK: http://askubuntu.com/questions/318246/complete-installation-guide-for-android-sdk-on-ubuntu
To run all commands faster, just type "sudo su" before starting. After that type "apt-get -f install" to clean everything.
Remember: To install anything the tutorial asks you have to use the command "apt-get install name-of-package", where the name is the item the tutorial says.
Go up to Step 4.
Download and Unzip/extract the AndroidSDK to the desktop (just the SDK, you don't need the full bundle).
Go to the unzipped folder, go to the Tools folder, double click "android", run in terminal, install the SDK and the TOOLS.
When finished, open a terminal window, navigate to your unzipped folder, than navigate to platform-tools and use the command "./adb" and "./fastboot" to work your magic..
Edit: Still not able to install the RUU..
At least now I have the phone ready.. Just have to find a new PC to install the RUU..
Related
When I tried to install it, it failed and now when I try again it says
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
you dont install anything. you extract the android sdk into the c:\. then you copy the two files mention in the thread to c:\windows\system32. you then go to start>run>cmd(enter). type adb devices. ADB is ALL COMMAND LINE. THERE IS NO PROGRAM YOU INSTALL
what two files?
blackfire1 said:
what two files?
Click to expand...
Click to collapse
~sigh~ are you sure you read how to do this at all?
adb.exe and AdbWinApi.dll are the two files that need to go to system32
and then install the drivers from your usb_driver folder from the SDK. Use the AMD one if you're using a 64bit OS or the Intel one for 32bit OS.
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
blackfire1 said:
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
Click to expand...
Click to collapse
System Restore and try it again.
that has nothing to do with adb. that means your driver installer that is resident in windows is corrupted. unless you can system restore to a point at which it was working, the only real fix is going to be a new windows install. not entirely sure how one breaks the library for installing device drivers, but hey, thats what you've got.
Ok the problem was solved when I used my other computer.
Hey, i have had this problem for a bit now, but it is really starting to bug me.
I have a dual boot computer, one is fedora, the other windows 7. When i decided to root my nexus one, i did it through windows, so i got the SDK, installed the drivers and rooted the phone.
Some time later (after flashing and restoring from desire rom back to CM 5) my computer can no longer recognise the device properly Windows will say it fails to recognise the device (code 43), and will not let me re-install the drivers. Saying they are up to date even after i uninstall the drivers then re-install them.
I have given up on fedora too, since no command ever seems to work on fedora beyond yum install xxx. Trying to get "fastboot devices" in fedora brings up "command not found" or something to that effect.
I wouldn't be too worried, but not everything comes as an update.zip, and i would like to try out the undervolted kernel some time.
Note: i can still mount the SD card fine.
EDIT: i can Mount the SD on Fedora, but not windows.
Things you can try out:
1. Completely uninstall and remove the driver from the system and connect the phone and install the drive when prompted. (try in safe mode as well)
2. Try other USB ports.
3. Try turning off USB debug, connect the phone and then turn on USB debug.
4. Try on another PC and rule out any problem with ur phone.
5. Reinstall Windows!!!
Thanks for the suggestions, i tried everything there short of re-installing windows.
As soon as i plug in the device windows will bring up the error message, it will not call it a nexus one, an unknown device. Any attempt to install the new drivers and windows will say that better drivers are already installed.
I also figured out that it will not work on fedora because it is not configured, but the only guide to fastboot and linux i have found is for ubuntu, and some of the commands wont work on fedora.
I tried it on another computer, an XP, it would not install on there either, i tried to use my mums N1 afterwards to see if it would install, it didn't but there are a number of reasons why it may not.
Any other suggestions? or could someone point me to a fedora guide for fastboot?
I've searched and searched for a solution to this, nothing is working. Really need help guys.
Phone is on stock ICS rom, PC is Win8 Pro x64. All three files are in the folder, SDK is installed (x64 version), Google USB driver installed, Java for windows installed, and HTC Sync installed but not running.
When in FASTBOOT and USB connected it shows FASTBOOT USB. Device manager shows Android Phone - Android ADB Interface. Is this correct or should it show something else in device manager?
No matter what I've tried when running fastboot oem get_identifier_token in command prompt I get waiting for device. Also running fastboot devices returns nothing.
Don't know what else to try... Seems it doesn't recognize the device but it's in device manager.
Edit: have also tried different usb ports and I know the cable works.
Edite 2: I fixed it. Took me hours to get this working but for any one struggling like I was here is what I did.
Got rid of all the drivers and started back at Android 1.0 in device manager. Manually installed the official SDK google usb driver and selected Android Bootloader Interface for Android 1.0. Also boot the phone and manually install again and select Android ADB Interface.
Here is what really caused me problems. The HTC tutorial I looked at said to take adb.exe, fastboot.exe, and adbWinApi.dll and put them in their own folder. This absolutely does not work for me even now. I used the directory straight from the SDK (sdk\platform-tools) and added fastboot.exe from a previous sdk revision into that folder. Now everything works!!! Finally!
Hi everyone!! I have the same issue as brother bassvoykevlar but the solution here expresed is not all clear to me. Can anyone please give me a hand on this, i am really mad with it . Thanks in advance.
The Best Solution
this problem has also happened with me and i found a solution to this,
this usually happens if your system lacks fastboot drivers.
ADB drivers can only Run ADB shell so that is why you need to have fastboot drivers as well to use fastboot commands.
i think you must have tried this code:
"fastboot oem unlock"
then cmd may have got stuck on "waiting for device"
don't worry install drivers for fastboot then it should work.
google it then get it.
there is 15seconds ADB,fasdtboot installer available try that.
then give it another try.
Hey guys,
Wonder if you can all help me,
Im not new to Rooting, but i have never come across this error before, ive searched accross XDA and Google, but cannot for the life of me find a fix, found a couple of things about deleting a registry file, and installed the One drivers which i had downloaded from here. I Do not have HTC Sync installed.
When device is powered up normally and connected to USB it as fine. When i reboot the Device into fastboot and connect it, i get a Error saying USB Device not recognised.
When i goto device manager, its shows up as My One under HTC, but has a Yellow '!' in a triangle, when i click on properties it states a code 10 Device Fails To Start error.
Please help as this is really frustrating me... Ive tried everything! And i really dont want to re-set my whole laptop as i will lose ALOT of data!
Like i said, im not new to this, as been doing this since the days of the HTC HD2...Am i missing something? Having a thick moment?
Running Windows 8.1.
If anyone really knows what this could be and could possibly fix, let me know as have team viewer and would gladly let you connect to me to help me out (Donation for your time aswell)
Thanks in Advance!
Really simple mate, windows 8.1 isnt compatible with fastboot drivers for now. Only adb is working atm. So dont be scared, your phone have no problem, its only because you updated to 8.1
Sent from my HTC One using xda app-developers app
Edit: there is a possible fix if your computer is based on intel chipset usb 3.0. Just google something like Windows 8.1 fastboot fix. Otherwise I think you will need to wait or simply use another computer with win7 or 8.0 or maybe dual boot win7 or even boot win7 with a vm?
Edit 2: search the forum, there is a "how to" force win7 fastboot drivers installation on win8.
Perfect buddy worked a Treat! Thankyou so much! I was getting so frustrated haha!
Didnt know it was a problem with Windows, so just needed to change the search terms, do'h!
For all those that has the problem in the future, a link for the fix!
Clicky!
Mods, this can now be closed, fixed!
fastboot for windows 8.1 over linux and this is my option to work fastboot on win 8.1
load wubi (windows ubuntu installer) over the link http://wiki.ubuntuusers.de/Wubi
than install ubuntu, on harddrive C:// and reboot your Pc
Now you have a linux in your current system, you can remove ubuntu (linux) in Programms & feautures list in windows.
now reboot reboot the system and isntall in ubuntu fastboot.
you musst give in the terminal sudo apt-get fastboot
and now you can flash your bootloader in linux.
but you musst sudo bevor you type fastboot flash type sudo fastboot flash boot boot.img
adb is working to on linux
i love wubi <3
you say it is easy
gooogle wubi (windows ubuntu installer)
tried running ubuntu in a virtual machine still no go guess the vm needs the windows driver to see the damn usb ports ffs
anyone know if for sure it will work if i actually install ubuntu to a partition?
Sony vaio 13 i7-4500u so only got usb3 ports and small hard drive didnt wanna dual boot really
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
ambitiousButRubbish said:
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
Click to expand...
Click to collapse
Does it work with
Different cable
Different port
Different pc
Different OS like linux
?
If I remember correctly I had issues with windows drivers.
Tried different ports, same issue, not tried a different cable, but I know this cable works as I use it for fastboot on my mi mix 3.
I'll try Linux though, a few posts seem to say it works
ambitiousButRubbish said:
Tried different ports, same issue, not tried a different cable, but I know this cable works as I use it for fastboot on my mi mix 3.
I'll try Linux though, a few posts seem to say it works
Click to expand...
Click to collapse
I use Linux Mint Cinnamon for development
I am still happy with it
ambitiousButRubbish said:
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
Click to expand...
Click to collapse
my same issue adb working but not fastboot on windows 10.
i solved using ubuntu on virtual machine. on windows i can't use fastboot but with ubuntu on oracle virtualbox all is work perfectly
yep, worked with linux, well, i just connected it to my mi mix 3, installed the adb/fastboot binaries in magisk and ran the commands from the terminal, looks like all my fastboot work is being done from another android device
ambitiousButRubbish said:
yep, worked with linux, well, i just connected it to my mi mix 3, installed the adb/fastboot binaries in magisk and ran the commands from the terminal, looks like all my fastboot work is being done from another android device
Click to expand...
Click to collapse
is it possible to install adb and fastboot from magisk and do it from another android device?
is it possible to do it with a 32 bit device? i have a galaxy note 4 as a second phone with snapdragon 805 32 bit
MartinX3 said:
I use Linux Mint Cinnamon for development
I am still happy with it
Click to expand...
Click to collapse
Arch linux only ?
Don't see why not, the binaries are just compiled for ARM, don't think they are architecture specific.
My mi mix 3 is ARMv8 (64 bit) sd845, and it worked fine, not sure about ARMv7, but as I say, I think the binaries are ARMv7 anyway.
So long as the device can host a USB connection it will work.
For anyone having problems with the,"Waiting for Device" in windows,
USB debugging enabled on the phone.
Connected to PC through USB data cable and Phone screen unlocked and File Transfers enabled.
In windows> Device Manager> Android device(or your device/phone) >ADB driver or similar > Properties> Driver> Update Driver > Browse Computer > Let me pick from a list of devices and Un-tick the show compatible devices and find one that works.
I've had to keep this general as there are quite a few variables with different phones makes/models but the problem is caused by Window's Device Mangler not getting the correct ADB driver installed/chosen and or too many varied ADB driver packages installed
HTH
First hit in google... so let me explain it again. (Yeah... fresh windows install ****ed me over... )
You need ADB/Fastboot.
Sony Drivers?: https://developer.sony.com/file/download/xperia-xz2-driver/
Google USB Drivers: https://developer.android.com/studio/run/win-usb
If you can't install it. Disable Driver signature enforcement (Hold Shift while you press the restart button with the mouse)
When ADB works but fastboot isn't recognized reboot into bootloader "ADB reboot bootloader" and then in Device Manager find the "Android!" device and manually select the Android Bootloader as driver.