Has anybody gotten their computer to recognize their phone in fastboot yet? When I hook it up it comes up with adb interface device yet neither fastboot or adb commands work. Please don't point me to Android SDK or PDANet as I have tried those both. Pointing manually to the inf. I have even tried Moto drivers from their website still nothing. Working on bootloader **** and can't do anything at all without getting into fastboot and fastboot commands.
I can't even get to my standard recovery as I have been trying to do some mods my self and work around the boot loader. I am not able to get the adb interface to work in fastboot either. Even though I have the driver installed and shows it is working in device manager properly. I think there is definetley a driver issue with the adb for this phone.
The motor drivers worked for me adb wise not sure about fastboot are you referring to the recovery menu?
Sent from my DROID X2 using Tapatalk
wdenker said:
I can't even get to my standard recovery as I have been trying to do some mods my self and work around the boot loader. I am not able to get the adb interface to work in fastboot either. Even though I have the driver installed and shows it is working in device manager properly. I think there is definetley a driver issue with the adb for this phone.
Click to expand...
Click to collapse
Power off the phone then hold volume down while powering it on. when it says fastboot keep hitting volume down till you get to the option android recovery then hit volume up. When you get the triangle and the android push both volume up and down. You are now in recovery. Adb won't work with fastboot mode.
from what i can tell you need a newer version of fastboot.exe
chevyowner said:
from what i can tell you need a newer version of fastboot.exe
Click to expand...
Click to collapse
fastboot.exe doesn't mean anything if the device isn't recognized as a fastboot device
taylorhome11 said:
fastboot.exe doesn't mean anything if the device isn't recognized as a fastboot device
Click to expand...
Click to collapse
my droid x2 shows up in fastboot mode in device manager as "mot single ADB Interface"
i said that because i have been there
now goodluck getting me to give you a fastboot.exe that works with the x2
chevyowner said:
my droid x2 shows up in fastboot mode in device manager as "mot single ADB Interface"
i said that because i have been there
now goodluck getting me to give you a fastboot.exe that works with the x2
Click to expand...
Click to collapse
Then if you aren't going to share why post? piss off
i never said i would not share, nice wrong assumption
here you go, now you "piss off"
chevyowner said:
i never said i would not share, nice wrong assumption
here you go, now you "piss off"
Click to expand...
Click to collapse
im pretty sure "now goodluck getting me to give you a fastboot.exe that works with the x2" means im not giving it....but now you changed your mind
Related
On my Atrix 4G, I can't get the fastboot to work. I have installed the latest drivers for windows and created the rules files in linux and for both operating systems when I try to run fastboot I just get a <waiting for device>. Can anyone help me with this problem?
enderx1 said:
On my Atrix 4G, I can't get the fastboot to work. I have installed the latest drivers for windows and created the rules files in linux and for both operating systems when I try to run fastboot I just get a <waiting for device>. Can anyone help me with this problem?
Click to expand...
Click to collapse
That happen to me. All i did was put the phone in fastboot mode and it connect right away. Press volumn down button while powering on the phone. When the screen said Fastboot, then you press up on the volumn button.
I'd suggest trying to run "fastboot devices" before any other commands, just to verify that you have connected to the phone successfully. If you don't get any response from the "fastboot devices" command, you've still got an issue. For my money, the probable sources are lack of drivers, or phone isn't in fastboot mode.
the piont is how to do?
I have the phone in fastboot mode, and fastboot devices returns nothing. Where would I get the correct drivers? I believe I have the correct ones, for windows that is. For linux I have configured the rules.d files as well.
Hi,
Use moto-fastboot, you can find links in the dev section from -eval and others, it will detect the device, also it supports large partitions, unlike the regular fast boot binary you might find via Google. If you do a lsusb and it shows an nvidia entry, you are good to go on the phone side.
Cheers!
Hi,
I have been searching the forums for it, and I have not been able to find the moto-fastboot binary. Could you link to it?
http://forum.xda-developers.com/showthread.php?t=1138092
I've already unlocked the bootloader and am about to flash cwd but my computer won't recognize the phone in the bootloader while plugged into USB. So when I try to enter the command "fastboot flash recovery <recovery.img>", the command prompt comes back with an error. I bet I'm missing something simple here, but it's getting pretty frustrating.
I have the HTC drivers installed and I'm using bootcamp, if that matters.
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
jonesin said:
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
Click to expand...
Click to collapse
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
feperlman51 said:
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
Click to expand...
Click to collapse
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
jonesin said:
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
Click to expand...
Click to collapse
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
feperlman51 said:
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
Click to expand...
Click to collapse
"just ran the "fastboot flash recovery" command again"
Lol thats what I said man! Glad it worked! CWM and TWRP should both work, I bet a nickel to a dime you werent actually in fastboot mode the first time! anyway happy flashing! Get comfortable with ADB and Fastboot because they will be our primary utilities for the foreseeable future!
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Esploded said:
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Click to expand...
Click to collapse
Do you have adb? If you do the command is adb reboot recovery. Need to know more it just cycles? If so then try to push both power button and and both volumes until it has lights flashing at the bottom and reboots dont let go until it reboots. Other then that I am not sure. I tried to boot to recovery the manual way and it doesnt work. Which is why i Always use that to reboot recovery. Wait, I figured it out. Hold down volume power dont let go until bootloader comes up then let go of both. use volume down and select recovery and bam!
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
jhr5474 said:
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
Click to expand...
Click to collapse
I'll give the fastboot utility a shot, hopefully it works. Thank you
Esploded said:
I'll give the fastboot utility a shot, hopefully it works. Thank you
Click to expand...
Click to collapse
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
jhr5474 said:
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
Click to expand...
Click to collapse
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Esploded said:
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Click to expand...
Click to collapse
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
jhr5474 said:
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
Click to expand...
Click to collapse
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Esploded said:
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Click to expand...
Click to collapse
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
sdamark said:
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
Click to expand...
Click to collapse
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Esploded said:
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Click to expand...
Click to collapse
No, If you have twrp use adb push and push a rom to your phone and then flash it and your fine.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
If you can get into your rom, go to settings..power and at the bottom disable fastboot
Esploded said:
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
Click to expand...
Click to collapse
1. Charge your phone (about 24 hours).
2. Let him rest (about 24 hours) without turning on.
3. Connect device to PC with original wire (Win7 preferred).
There is possibility that your BB will recognize phone.
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
eriknors said:
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
Click to expand...
Click to collapse
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
dottat said:
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
Click to expand...
Click to collapse
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
eriknors said:
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
Click to expand...
Click to collapse
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
dottat said:
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
Click to expand...
Click to collapse
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
eriknors said:
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
Click to expand...
Click to collapse
Not an install. Unzip and run cmd prompt from there. Note that your fastboot commands will start HTC_fastboot
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
eriknors said:
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
Click to expand...
Click to collapse
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Got it
dottat said:
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Click to expand...
Click to collapse
No dice. ADB worked just fine but still no fastboot
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Uzephi said:
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Acoustichayes said:
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Click to expand...
Click to collapse
Well tbh I've been trying on both just to see if anything works.
eriknors said:
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Click to expand...
Click to collapse
He asked that because if you use mine you need to use htc_fastboot devices
Otherwise you will be using the fastboot from sdk install.
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Had the same issue tried every thing, but eventually end up installing uBuntu that solved every thing.
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
Its due to the missing device descriptor.
Royal PITA, I have yet to get it working. I just keep a win7 laptop around.
The only way this could be "fixed", would be if we had a newer eng-hboot that had the descriptors set.
I have the tmobile lg v10 h901. I'm trying to unlock the boot loader. I have adb and fastboot files installed and the lg drivers. I have the oem. Unlock and usb debugging checked in the setting. I can open the command prompt and use adb devices and it sees my device. I can use adb reboot bootloader and it will take me to the fastboot bootloader unlock screen. From here the command prompt no longer sees my device. I type fastboot oem Unlock and it says waiting on device... Any one have a idea what's going on. Am I missing something?
Try booting into fastboot manually by turning off the phone and holding vol down while plugging it in,then try it but make sure you fastboot devices first to make sure its even detecting it
No that didn't work. When the phone is on adb devices it sees the phone I type fastboot devices and it does nothing. But when the phone goes to fastboot even volume down then plug the phone In it won't recognize the phone just says <waiting on device>
Yeah I keep uninstalling everything and reinstall everything fast boot threw cmd fastboot with the volume button and always get waiting on device when I get to the "fastboot oem Unlock"
So sad ...
Use nexus toolkit for it all. I did. Works great.
Exconvict said:
Use nexus toolkit for it all. I did. Works great.
Click to expand...
Click to collapse
Wugs nexus toolkit ? That will work with the v10?
cwalton4077 said:
Wugs nexus toolkit ? That will work with the v10?
Click to expand...
Click to collapse
I used Mfastboot and it worked like a champ. Could not get nexus toolkit to see my device.
Yes. It boots temp recovery,flashes recovery and root. Also used it to relock the boot loader for sh*ts and giggles. To get it to see my phone I had to download LG bridge on my computer and run it.
I have tried mfastboot and the nexus toolkit and both stop working when it gets to the fastboot oem Unlock. Waiting on device. I have not installed lg bridge so I will try that later and see if that helps.
If you run Windows, you may be missing the USB driver for fastboot. If possible, use Linux where all the USB drivers are included from the start.
I'm having the same problem as well.
cwalton4077 said:
I have tried mfastboot and the nexus toolkit and both stop working when it gets to the fastboot oem Unlock. Waiting on device. I have not installed lg bridge so I will try that later and see if that helps.
Click to expand...
Click to collapse
When starting all of this (essentially becoming addicted to learning rooting) I noticed that no one mentioned to make sure to enable the "usb tethering" option on their device!! Once I did that, an entire plethora of additional options opened up. That being said, this option won't necessarily make rooting possible, but I think it may help out in this particular situation.
? I really hope this works for you.
1500 years ago, everybody "knew" that the earth was the center of the universe. 500 years ago, everybody "knew" that the earth was flat. And 15 minutes ago, you "knew" that humans were alone on this planet. Imagine what you'll "know" tomorrow.
-Kay
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
cwalton4077 said:
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
Click to expand...
Click to collapse
Glad you got it rooted
Great!
cwalton4077 said:
I got it working I had to go to device manager on the pc then put the phone in boot loader. Then on device manager the phone changed to Android unknown so I set the drivers to Android adb services and it worked fastboot would see the phone and I got root on the v10
Click to expand...
Click to collapse
Now can you post a YouTube vid for us who are still having this issue! ?