Hi all,
I have recently updated to the one and am having some trouble getting the fastboot commands working. Having been rooting/unlocking my phones for a few years now and have never really found the need to sign up and ask question as you can generally find what you need to solve most problems on here.
I have updated the driver using tutorials from here using the windows 7 ones. I have done this and everything works fine, the device is recognised. I can use the adb command to get the device connected information and adb reboot into bootloader, however when I get into the bootloader and into fastboot usb a windows notification pops up saying 'USB not recognised , the usb device connected to this computer malfunctioned and windows does not recognise it.'. As expected when I try any fastboot command it says it is waiting on device and is stuck there.
Hopefully it is something stupid I am missing out and not the device.
Any help would be good.
Thanks.
Related
I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?
my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one
I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.
Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...
That was a good idea, but I had no luck with that one either. Thanks though.
Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927
stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?
Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.
Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.
Hey guys!
In advance I'm sorry for asking something that has probably been asked many times before, but I'm unable to find the right answer.
Okay let's start at the beginning. My HTC one with an unlocked bootloader on stock started to display a very irritating bug in that sometimes the screen would not rotate and was stuck in landscape mode. Nothing would help nor rebooting, nor calibrating the sensor. Only booting into the bootloader would somehow help.
Until it did not.
I tried a factory reset, which did not help and then tried just wiping Dalvik and Cache, which did not help too.
Then I tried wiping Data and System, which I now know was very stupid.
The current problem is that I can't figure out how to send a new ROM to my HTC one using adb, when typing adb devices the device does not show up.
My computer does see the device, listed under Android USB devices ad My HTC. I think Fastboot too, recognized the device, because I am able to get the Identifier token.
I have installed the drivers and installed HTC Sync manager. I have restarted my Pc multiple times and changed the USB port the device is connected to.
I too, tried mounting the USB, but either I'm doing it wrong, or it does not work.
Hope one of you can help me! I've been at this all day long...
Adb commands only work when you're booted in the rom or recovery. Fastboot uses fastboot commands. Do you have a custom recovery? If so, you can adb sideload a rom. If not, you can fastboot flash a custom recovery assuming your bootloader is unlocked. You may have mentioned it in your post I just can't remember. Good luck!
Sent from my HTC One using xda app-developers app
Thanks for the help!
Yes, I unlocked my bootloader and have twrp installed.
I think I have narrowed down the problem: that my device is not recognized by the computer in twrp.
When in fastboot, My computer does recognize the device, listed as an HTC one, so the drivers are not the problem.
When booting into recovery, me computer only recognizes the phone for about 3 seconds, when it dissapears.
I have been able to see the device in Adb (using Adb devices).
What could I do? Adb sideload does not work because the computer does not recognize the device.
Hi,
You're on Windows? If yes which version?
Windows 7, but if needed I do have access to a win 8 PC as well.
All x64 by the way.
Ok, maybe take a look here if you use USB 3.0?: [FIX]Fastboot problems on Windows 8 x64 with USB 3.0? Solution inside.
It might work on Windows 7 too, there is a link for the drivers for x64.
Maybe using a toolkit to use ADB/fastboot? Take a look here:
[TOOL]HTC One (M7) All-In-One Toolkit V3.1
[TOOL]HTC One (M7) AIO Toolkit | v1.4
Okay, from now on I'll only use USB 2.0.
I tried these two toolkits, but they suffer the same problem as me in that in order for adb sideload to work the device has to be recognized for longer than 3s after booting into recovery.
I just bought a female-female USB adapter, hopefully installing a rom from a usb stick will work
Ofcourse help would still be greatly appreciated as i will have to wait for over a week till the USB adapter arrives.
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
pannic514 said:
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
Click to expand...
Click to collapse
Try it on Windows 7 or update your drivers.
http://androidxda.com/download-htc-usb-drivers
http://www.andromods.com/fix-troubleshoot/issue-fastboot-waiting-for-device-windows-81-fixed.html
Fastboot and adb don't work on Windows 10 yet. That's why I didn't upgrade from Windows 7 ?
Hello!
I am trying to root my phone, which requires and unlocked bootloader.
Here are the steps i have completed:
1. Got the unlock code.
2. Installed adb and fastboot drivers.
3. Installed HiSuite
4. Connected the phone to my desktop (windows 10).
Here i have to mention that the pc recognises my phone, and it is listed under devices. USB debugging and OEM unlock are enabled.
5. I opened cmd in the folder where abd is installed. Checked that abd devices finds my phone (which it does).
Here is where the problem comes in. After booting phone into fastboot (using adb reboot bootloader), i tried to find my phone using the command fastboot devices.
This doesn't find the phone. If i try to unlock anyways, it gets stuck on waiting for devices. I tried the same steps on a laptop (also running windows 10) and the problem stays the same.
Help is appreciated.
EDIT: solved the problem by using a windows 8 installed laptop.
Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.
monoxian said:
Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.
Click to expand...
Click to collapse
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.
Nastmi said:
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.
Click to expand...
Click to collapse
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone
monoxian said:
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone
Click to expand...
Click to collapse
Will try the tool when i get home from school, but fastboot devices doesn't detect my device.
EDIT: The tool didn't work. It is stuck on waiting for device.
Fixed the problem by unlocking on another laptop (has windows 8).
Nastmi said:
Fixed the problem by unlocking on another laptop (has windows 8).
Click to expand...
Click to collapse
Glad to hear that you got it working, I had windows 10 and that worked on mine =\
Sent from my iPhone using Tapatalk
Hi
I'm trying to flash TWRP on my CHe2-L11 via adb but it gets stuck at < Waiting for any device >.
I read somewhere that is because Windows lacks the necesary drivers (although Che2-L11 is listed as "MTP" in the devices connected to my computer).
Where can I find the necessary drivers for Win10?
Thanks a lot
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess? Windows can not automatically find drivers for this...
Then it make sense that I cannot flash the custom recovery until the phone is detected again.
What should I do to have my phone detected in Windows while it is in bootloader mode?
Thanks a lot
-a-
Running windows update found a driver for
Google Android Bootloader Interface
However, ADB still cannot detect it
EDIT: Actually it works! Even though
adb devices
would not list anything when the phone was in bootloader mode, I was able to flash twrp
Problem solved!