I have been trying to make this work for 2 days now and it still won't recognize my phone. I for sure have fastboot.exe, adb.exe, and AdbWinApi.dll in the C:\WINNT\system 32 folder on my computer. I am running windows 2000 SP4. I connect my g1 while its in the bootloader and displays fastboot in the middle of the screen, it asks to update drivers, and so i do. I use the "x86" driver found in the SDK because that is what i used to set up adb. It installs the driver, adds the "adb interface" category with "HTC Dream" under it, and asks me to reboot because hardware changes have been made. Oh and next to "HTC Dream" there is a little yellow exclamation point and when you double click on it it says "cannot start, code 10." I do a reset and whenver it starts up it doesn't ask me to install new drivers, but that little exclamation point is still there. Any help would be appreciated!
golferguy17 said:
I have been trying to make this work for 2 days now and it still won't recognize my phone. I for sure have fastboot.exe, adb.exe, and AdbWinApi.dll in the C:\WINNT\system 32 folder on my computer. I am running windows 2000 SP4. I connect my g1 while its in the bootloader and displays fastboot in the middle of the screen, it asks to update drivers, and so i do. I use the "x86" driver found in the SDK because that is what i used to set up adb. It installs the driver, adds the "adb interface" category with "HTC Dream" under it, and asks me to reboot because hardware changes have been made. Oh and next to "HTC Dream" there is a little yellow exclamation point and when you double click on it it says "cannot start, code 10." I do a reset and whenver it starts up it doesn't ask me to install new drivers, but that little exclamation point is still there. Any help would be appreciated!
Click to expand...
Click to collapse
What SPL do you have?
is there an issue with the new spl? because i cannot have my device recognized when its in fast boot anymore.
blakestimac said:
is there an issue with the new spl? because i cannot have my device recognized when its in fast boot anymore.
Click to expand...
Click to collapse
If you're using the new SPL (1.33.2005) or the Sapphire SPL, you need the updated USB driver.
Related
I have followed these steps..> http://forum.xda-developers.com/showthread.php?t=532719 <... ok correct me if im wrong i pluged in my phone pops up found new hardware and it give me three options...
1.Locate and install driver software
2.Ask me later
3.Dont show this message again for this device
I did option 1 then it gives me unidentified device installed and when i go into cmd and do the commands it show......
list of devices....
Nothing
when i click safley remove icon(bottom right) it show that my device is a USB mass storage device...I think this might be the problem idk im all confused...
WHAT NOW
Anyone help if can please THANKS...tear drop no adb for now
YES YES F***ing Yes ok sloved finally ok so this is what i did i went into device manager right click on unidentified driver then click update driver software, and then click browse my coputer for software update, then browse to C:\sdk\usb_driver\x86 then next and all done YES excited
jgu71424 said:
1.Locate and install driver software
2.Ask me later
3.Dont show this message again for this device
I did option 1 then it gives me unidentified device installed and when i go into cmd and do the commands it show......
list of devices....
Nothing
Click to expand...
Click to collapse
Did you follow these steps in the guide?
Installing Drivers
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
Click to expand...
Click to collapse
If you installed it properly, you should have "HTC Dream Composite ADB Interface" in your device manager.
jashsu said:
Did you follow these steps in the guide?
If you installed it properly, you should have "HTC Dream Composite ADB Interface" in your device manager.
Click to expand...
Click to collapse
Yes i did and it gave me a pop up with three options i chose option 1(read top for options) and it gave me what i said on top page...
Oh i have windows vista ultimate 32-bit
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder
SO recently got a nexus one and for some reason i cant get it to be recognized by adb, i have tried everything, updating drivers, reinstalling adb, trying diferent usb cables, different usb ports, but for some reason no matter what i try adb doesnt recognize any device. it recognizes my atrix just fine, but not the nexus. and the nexus is also rooted and has cwm but somehow the bootloader says ship s-on. it all seems prtty wierd. any ideas?
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
baseballfanz said:
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
already tried that driver and same thing
Theshawty said:
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
Click to expand...
Click to collapse
still nothing with reinstalling
gunna try restoring stock firmware and see what happens
not even going back and flashing stck firmware will let it connect to adb
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Aceyo said:
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Click to expand...
Click to collapse
as i told the other 2, it is not a driver issue, it turns out the guy i got it from had work done on it before it was shipped, thinking something internal is the issue
After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.
LuminousOne said:
After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.
Click to expand...
Click to collapse
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'
Didgesteve said:
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'
Click to expand...
Click to collapse
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I'm not sure what you're trying to do. If you want to flash a rom, you want flashmode, volume down (-) then plug in the USB. If you want fastboot it's volume up (+) then plug in the USB..
MTP driver is wrong, you need to uninstall it and re-install the sony driver. Windows chooses the wrong driver by default and you have to manually add it yourself to make it work.
Having said that you mentioned that you are getting ADB commands to work, so I'm confused, perhaps the google driver is in place, but the Sony one is not.
You need both, when the phone is in fastboot it's presented as a different device than when connected via ADB.
Hope that helps explain a bit.
But if you're having issues with the drivers, should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.
LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I had this problem before. My fault before was install drivers in usb-debugging mode, then a change to fastbook/flash, and then the phone is not recognized or connection properly - despite me thinking I had correctly installed the drivers.
Took me months to figure it out. Boot into windows, then connect your phone in all modes, flash mode, fastbook mode, standard, and usb debugging - and for each mode - install the Sony driver again.
The result will be, that for every mode - when you go to device manager - you won't see an exclamation mark. If you ever see an exclamation mark again - install the driver. You get the idea.
Regards,
I finally found the f**kin problem the invalid driver was hiding under "other devices" only when the phone was in fastboot mode. Basically I followed the instructions of user2021355 from here.
Start Windows in test mode (instructions)
download driver from https://developer.sony.com/develop/drivers/
in admin command prompt run adb reboot bootloader
if the above step failed, you have a problem with adb and the solution is something different
open device manager and carefully search for any errors. I found mine hidden under "other devices"
right click on the errored driver and choose update
choose browse my computer
select the driver you downloaded from step 2
verify if working by running fastboot devices and you should get a serial number
Didgesteve said:
should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.
Click to expand...
Click to collapse
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?
LuminousOne said:
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?
Click to expand...
Click to collapse
Some banking and games apps don't like rooted phones.
Not sure about android pay.
Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
same is when pointing to the drivers from here: https://developer.android.com/studio/run/win-usb
I ve the G8441
sheedy1900 said:
Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
I ve the G8441
Click to expand...
Click to collapse
Add the driver manually.
Didgesteve said:
Add the driver manually.
Click to expand...
Click to collapse
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.
OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement
LuminousOne said:
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.
Click to expand...
Click to collapse
I think we have different ideas of what adding the driver manually is
sheedy1900 said:
OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement
Click to expand...
Click to collapse
i have the problem as you and I'm also on win10. can you share how you installed the fastboot driver?
the adb and mtp drivers work fine for me, just fastboot is not working
unsigned driver under W10
try this one
https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Gesendet von meinem viennalte mit Tapatalk
I have the same problem with my Sony XZ1 Compact G8441.
'adb devices' shows my phone, after 'adb reboot bootloader' phone goes into fastboot mode (I think), the one with blue LED, but 'fastboot devices' does not show any connected devices. Same when pressing Volume Up or Volume Down while plugging the phone in.
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Tried installing through device manager, right-click on faulty 'Android' under 'Other Devices', update driver, browse to download location.
With 'Sony XZ1 Compact driver' it found no installable drivers.
With 'Sony Fastboot Driver' it found an installable driver but had an error. Error said something like 'Did not find "Android ADB Interface", installation failed'.
I tried figuring out what you guys meant by 'installing driver manually' but I don't understand. Is it what I tried above, or something else?
My goal is to be able to install TWRP, which needs an unlocked Bootloader first. I followed the instructions on the official Sony Website for that.
Sorry. Delete this.
Gnorv said:
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Click to expand...
Click to collapse
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.
Didgesteve said:
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.
Click to expand...
Click to collapse
No, that did not help. The same problem remains. Phone is recognized when powered on by 'adb devices' but not recognized after typing 'adb reboot bootloader' and 'fastboot devices'.
Thanks for your suggestion though.
I got the problem that no matter what i do i can't install the driver.
Booting windows 10 with driver check disabled does not solve my problem.
Once i selected the driver to install i end up with a questionmark in the device manager above the android device. Taking a closer look reveals that there seems to be no driver installed.....
Any advice?
I tried:
1. Booting with driver signature check disabled
2. Switching windows 10 into test Mode
I booted ubuntu from a live usb stick and went from there. That works like a charm without the need of installing any drivers
Both solutions do not work....
I load v35eng.img file into abl_a and remove laf_a, laf_b but restart booloader can not find adb device. I tried to update the driver but the computer shows android only in other devices but not android interface adb someone help me with
blackan1 said:
I load v35eng.img file into abl_a and remove laf_a, laf_b but restart booloader can not find adb device. I tried to update the driver but the computer shows android only in other devices but not android interface adb someone help me with
Click to expand...
Click to collapse
It sounds like you need to install the lg usb driver. when you see the exclamation mark in 'other devices' and it says android but it doesn't work, select that, select load driver from hard drive, then find the adb driver from the installed usb drivers.
good luck
AsItLies said:
It sounds like you need to install the lg usb driver. when you see the exclamation mark in 'other devices' and it says android but it doesn't work, select that, select load driver from hard drive, then find the adb driver from the installed usb drivers.
good luck
Click to expand...
Click to collapse
I tried many times but it not working. Still show "android"