Heya~ Ive recently upgraded to CM5, since then manually & Automatically updating the drivers to use fastboot have failed on Vista Home Premium (32bit)
I've also tested it on Win7 64BIT, in win7 it does appear on device manager as "HTC Bootloader", under ADB Interfaces. But does not appear when I do "fastboot devices" therefor it endlessly stays at <Waiting for Device> when trying to flash a file, It wasnt like this on Vista before upgrading from hardSPL to dangerSPL. Under windows vista it continuasly picks the device up as "Android 1.0" and cannot find drivers on the internet, and the drivers from the SDK arent working.
Is there a command to flash the splash1/2 via terminal or recovery prompt...because My computers dont want to cooperate.
Related
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
Ok, I get into Fastboot on my DELL S7 it just keeps on saying "Starting Fastboot USB download protocol" and other stuff in red text above, besides that I need to install the driver on my computer for Fastboot but Windows 7 says "Windows was unable to install your Fastboot" I guided windows to the driver folder in Fastboot+ADB which I got from the Clockwork Mod 5.0 RECOVERY Flash thread.
I really want to flash this clockwork mod http://forum.xda-developers.com/showthread.php?t=1334487
EDIT: Fastboot working, ok I have another problem I flashed the CWM 5.0 IMG file thru fastboot, but how to go into CW recovery? isn't it Power + Up Volume, but that takes me to the Dell update system.
EDIT 2 : I got everything working, used my brain instead of working blindly. Thanks anyways.
ikutoisahobo said:
Ok, I get into Fastboot on my DELL S7 it just keeps on saying "Starting Fastboot USB download protocol" and other stuff in red text above, besides that I need to install the driver on my computer for Fastboot but Windows 7 says "Windows was unable to install your Fastboot" I guided windows to the driver folder in Fastboot+ADB which I got from the Clockwork Mod 5.0 RECOVERY Flash thread.
I really want to flash this clockwork mod http://forum.xda-developers.com/showthread.php?t=1334487
EDIT: Fastboot working, ok I have another problem I flashed the CWM 5.0 IMG file thru fastboot, but how to go into CW recovery? isn't it Power + Up Volume, but that takes me to the Dell update system.
EDIT 2 : I got everything working, used my brain instead of working blindly. Thanks anyways.
Click to expand...
Click to collapse
Where did you find the driver during the fastboot screen? I'm having the same problem and any help would be definitely appreciated. What stock android did you have before installing CWR?
Ok, I had ADB drivers for a Motorola CLIQ and it worked, just select choose from list of installed drivers and selct Android Interface or ADB interface or whatever wityh ADB or android in it. Tyhen run cmd and ttpe fastboot.exe or fastboot
I see a few posts where folks cant get their computer to install the fastboot driver from the FASTBOOT+ADB.ZIP but then they say they got it working, but nobody has said how! I have XP sp3 and cant get the computer to install a fastboot driver. The ANDROID PHONE device is empty as well as the ANDROID USB DEVICE. I get adb interface when I plug in my Epic but I even tried uninstalling it and seeing if the steak would install but no go. Any suggestions?
PfcKirk said:
I see a few posts where folks cant get their computer to install the fastboot driver from the FASTBOOT+ADB.ZIP but then they say they got it working, but nobody has said how! I have XP sp3 and cant get the computer to install a fastboot driver. The ANDROID PHONE device is empty as well as the ANDROID USB DEVICE. I get adb interface when I plug in my Epic but I even tried uninstalling it and seeing if the steak would install but no go. Any suggestions?
Click to expand...
Click to collapse
Yeah, that's right.
This is how it is download ADB which is basically downloading the SDK.
And if you have an Android phone or something just install the drivers for it, usually downloads adb drivers for it too, or if that doesn't work try downloading MOTOROLA CLIQ USB or ADB drivers....as I had them installed when I plugged in the phone.
Put device in fastboot mode
Connect device
Open up Device Manager
Click on "Fastboot" or whatever it says
Click on "Update driver"
Click on "Browse my computer for driver"
Click on "Let me pick from a list of device drivers on my computer"
Click on "Have Disk"
Find your fastboot drivers
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..
im on w10 and im having trouble using fastboot commands through cmd (in a folder with the files)
my device is not showing up when i type "fastboot devices" when i go into fastboot mode or flash mode
when i open cmd and type in "fastboot boot twrp.img" or "fastboot flash recovery twrp.img", it gets stuck saying "< waiting for device >"
but when i use flashtool, it recognizes that im in fastboot mode or flash mode
i have installed:
adb drivers
fastboot drivers
flashtool
platform tools
android sdk
google usb driver
i have tried uninstalling the drivers and reinstalling them through device manager
my device shows up as "S1Boot Fastboot"
my main objective is to get twrp in order to flash oreo carbon rom with magisk
Did you install the fastboot drivers through the file in the Flashtool folder, with the installation of unsigned drivers allowed in Windows (driver signature enforcement disabled)? Suppose that's often a problem.
I had the same problem as you, and I noticed that some [automatic] Windows update had apparently uninstalled those drivers. Installing them again did the trick for me. Good luck.
LaRazón said:
Did you install the fastboot drivers through the file in the Flashtool folder, with the installation of unsigned drivers allowed in Windows (driver signature enforcement disabled)? Suppose that's often a problem.
I had the same problem as you, and I noticed that some [automatic] Windows update had apparently uninstalled those drivers. Installing them again did the trick for me. Good luck.
Click to expand...
Click to collapse
sucha simple fix lol
thanks
'fastboot devices' does not return anything
win10 says that driver isn't installed, manually tried to feed 'Google USB driver' from SDK package - no luck, Android sits with yellow warning in Device Manager
but it detects the device from recovery, adb sideload works and win10 correctly shows Android Composite ADB interface
tried on 3 different PCs, no luck with fastboot driver
any ideas?
You can try finding a machine with windows 7, it will probably find drivers right away