OK so I've searched all over the forums and couldn't find a solution for this.
Most people seem to have the problem where ad works but not fastboot. For me though running "adb devices" and "fastboot devices" both work (I.e. showing a list of connected devices) but the phone stays in " starting fastboot protocol support" and doesn't change to "fastboot reboot" when connected.
If it helps I'm running Ubuntu 10.04 and my phone is on Jokers cm9 2.0 beta.
Sent from my Atrix 4g using xda app
Phone wont change to 'fastboot reboot'. That's a command entered from cmd prompt on your computer. Its normal for phone to stay at 'starting fastboot protocol support'.
Sent from my MB860 using xda premium
+1
"fastboot reboot" is a command as @CaelanT states. Try typing in "fastboot devices" while the phone says "Starting fastboot protocol" to see if it shows the serial number.
CaelanT said:
Phone wont change to 'fastboot reboot'. That's a command entered from cmd prompt on your computer. Its normal for phone to stay at 'starting fastboot protocol support'.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Davidrd91 said:
OK so I've searched all over the forums and couldn't find a solution for this.
Most people seem to have the problem where ad works but not fastboot. For me though running "adb devices" and "fastboot devices" both work (I.e. showing a list of connected devices) but the phone stays in " starting fastboot protocol support" and doesn't change to "fastboot reboot" when connected.
If it helps I'm running Ubuntu 10.04 and my phone is on Jokers cm9 2.0 beta.
Sent from my Atrix 4g using xda app
Click to expand...
Click to collapse
A serial number does show up when I type fastboot devices. But the phone still does not recognize that fastboot has started on the computer. Like if the USB wasn't connected.
Edit: also I'm sorry I didn't mean to say fastboot reboot. I know its a command. What the text doesn't change to is "fastboot USB". Or whatever its supposed to say when connected.
The Atrix usually doesn't say anything about a computer recognizing that it's there. If the serial shows up under devices command, then you're good to go!
At least you should be. It says fastboot next to the serial, right?
Yes it does, just none of the commands will work.
Edit: Turns out it will register the commands if connected to a specific USB port. Is this normal? Either way at least it works .
Sent from my MB860
Sometimes the USB port you use makes a difference. Most of the time on a PC you use the rear ports, but I myself have not found any problems using any ports on my PC or laptop.
Also remember that depending on if you have fastboot or moto-fastboot your commands will differ, e.g. "fastboot erase webtop" vs "moto-fastboot erase webtop".
The reason for the difference in which USB ports work is the way they are connected on the motherboard. The OS will only be able to send certain USB commands to the devices if that device is on a port connected directly to the chip set, from what I understand. My guess is that fastboot relies on some of those commands. This is true for me when I am doing Arduino development and want to use USB reset after flashing a new program.
Thanks guys. I got it working . Back to trying to compile a ROM now. This is taking me forever to get down right xD lol
Sent from my MB860
Davidrd91 said:
Thanks guys. I got it working . Back to trying to compile a ROM now. This is taking me forever to get down right xD lol
Sent from my MB860
Click to expand...
Click to collapse
I'm just curious on how you got it working. Some may want to know, if they are having the same problem.
I didn't pay attention that you were using Ubuntu. Don't you have to point fastboot to the device node using some Linux distros?
Edit: oh, missed your post saying how you fixed it. NVM. lol.
Related
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
I was trying to unlock the bootloader in my Atrix but I can't seem to get the fastboot to work.
I'm running Ubuntu 10.10. The adb works perfectly and when I run the fastboot command it gives me the list of syntax for it but when I try "./fastboot devices" it doesn't return anything. If I use sudo then it goes down to a new line and freezes. I'm assuming I need to edit something in rules.d but I don’t know how to get the proper information.
Any help would be great.
Sent from my MB860 using Tapatalk
LifelessRaptor said:
I was trying to unlock the bootloader in my Atrix but I can't seem to get the fastboot to work.
I'm running Ubuntu 10.10. The adb works perfectly and when I run the fastboot command it gives me the list of syntax for it but when I try "./fastboot devices" it doesn't return anything. If I use sudo then it goes down to a new line and freezes. I'm assuming I need to edit something in rules.d but I don’t know how to get the proper information.
Any help would be great.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
is your phone in fastboot mode? adb reboot fastboot
If it freezes at devices it can't see you phone. Make sure your phone says it started fastboot. Hold volume down while booting. When it says fastboot on the phone press volume up.
Sent from my MB860 using Tapatalk
Well I tried running the unlock in fastboot mode last night.
./fastboot oem unlock
Waiting for devices.
That was as far as I got. My phone was in fastboot mode but it just wouldn't recognize it. I saw some other posts about it saying things about adding to rules.d but I need the right information for my phone.
Sent from my MB860 using Tapatalk
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!
So i've been trying to get back to my stock settings on my DNA and i've hit a myriad of problems. Right now, I can get my phone to communicate when it's just plugged in. But whenever i boot into bootloader and plug it in, it tries to install the "Android 1.0 driver" but to no avail. The phone will then not be recognized by the computer and I can't do the "fastboot oem lock" command. Is there a download or something that i can grab that will solve this?
HosstaLaVista said:
So i've been trying to get back to my stock settings on my DNA and i've hit a myriad of problems. Right now, I can get my phone to communicate when it's just plugged in. But whenever i boot into bootloader and plug it in, it tries to install the "Android 1.0 driver" but to no avail. The phone will then not be recognized by the computer and I can't do the "fastboot oem lock" command. Is there a download or something that i can grab that will solve this?
Click to expand...
Click to collapse
Do you have the latest SDK version installed, sounds a bit like the drivers are outdated. Might be worth downloading the latest version and installing it...
Try the drivers in this zip file and see if this helps.. these are drivers I am using and have never had an issue
http://db.tt/kr11CT4d
Sent from my HTC6435LVW using xda app-developers app
lazarus2297 said:
Try the drivers in this zip file and see if this helps.. these are drivers I am using and have never had an issue
http://db.tt/kr11CT4d
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Okay, i downloaded that zip and attempted to relock the bootloader. When i type in "fastboot oem lock", the command prompt just shows <waiting for device>
HosstaLaVista said:
Okay, i downloaded that zip and attempted to relock the bootloader. When i type in "fastboot oem lock", the command prompt just shows <waiting for device>
Click to expand...
Click to collapse
Do you have debug turned on in developer options? Of so might try toggling on and off
Sent from my HTC6435LVW using xda premium
HosstaLaVista said:
Okay, i downloaded that zip and attempted to relock the bootloader. When i type in "fastboot oem lock", the command prompt just shows <waiting for device>
Click to expand...
Click to collapse
Are you in bootloader mode when you try this? You have to put phone in bootloader mode either thru adb command or manually. If communication is occuring, you will see fastboot usb in a red box, Then if your adb is working correctly it should go.
we need more info.. first did you uninstall the old drivers first.. then after installing the zip did you confirm that the drivers are the ones that were installed.. and also like someone mentioned is your phone in bootloader/fastboot mode and showing fastboot usb in red on the screen
Sent from my HTC6435LVW using XDA Premium HD app
Also make sure it's not a USB 3.0 spot, you need to use a 2.0. Windows 8 or 7? 8 has been causing issues connecting in fastboot for some.
madzozs said:
Also make sure it's not a USB 3.0 spot, you need to use a 2.0. Windows 8 or 7? 8 has been causing issues connecting in fastboot for some.
Click to expand...
Click to collapse
On my machine (win7) I can use either port usb 2.0 and 3.0..
Sent from my HTC6435LVW using XDA Premium HD app
lazarus2297 said:
On my machine (win7) I can use either port usb 2.0 and 3.0..
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
Win 8 has been having issues with 3.0 for some people.
Reply
HosstaLaVista said:
Okay, i downloaded that zip and attempted to relock the bootloader. When i type in "fastboot oem lock", the command prompt just shows <waiting for device>
Click to expand...
Click to collapse
Have you tried launching command prompt as an administrator?
I ran as root in Ubuntu to get it to re-lock.
Sounds like drivers to me. After you boot into the bootloader are you going into device manager selecting the android whatever and changing the driver to bootloader. Sorry not at a pc so don't know exactly what it says but that sounds like the case.
Sent from my HTC6435LVW using xda premium
One thing that worked for me was installing pdanet, for some reason it installed the correct drivers for HTC. Once I did that it saw my phone in adb, and I could get the device waiting prompt to go away and it would show my model and serial number...hope it helps. Just Google pdanet...and install it.
Sent from my HTC6435LVW using xda app-developers app
Hi,
I'm trying to unlock my Huawei Ascend Y300 but I'm stuck in fastboot.
I followed this guide: (not allowed to post outside links but you can find the guide by looking for "Free Huawei bootloader unlock tutorial"), but got my unlock code sent from Huawei by mail since the dc-unlocker tool didn't work as well (probably the same problem as with fastboot).
When the phone is turned on I can see it with "adb devices" but once I'm in fastboot mode (pink screen) no device can be found with "fastboot devices".
When the phone is in fastboot mode and being plugged into the computer it is recognized by Windows.
I tried two kinds of Huawei Drivers: "Huawei_U8680_U8730_U8800_U8860" and "Huawei_Android_driver" (for the last one: see the guide stated above). I also tried three different computers.
I'm using Windows 7 64bit if that helps.
Edit:
Same problem in Ubuntu, found in "adb devices" but not in fastboot mode.
Any idea anyone?
Thanks,
Patrick
Anybody?
SirBelial said:
Anybody?
Click to expand...
Click to collapse
both those drivers are most likely conflicting with each other. Uninstall them, and install the usb drivers for your device.
Another issue is that your using 64bit, those drivers may only support 32bit OS. Try doing it on a 32bit computer
Thanks for the reply. Only one of the drivers seems to be removable. I tried it on a different, 32bit Windows computer with first the one and then the second driver.
Same problem as above. I can find the booted phone via "adb devices" but can't find the phone in fastboot mode with "fastboot devices".
Maurice5813 said:
both those drivers are most likely conflicting with each other. Uninstall them, and install the usb drivers for your device.
Another issue is that your using 64bit, those drivers may only support 32bit OS. Try doing it on a 32bit computer
Click to expand...
Click to collapse
SirBelial said:
Thanks for the reply. Only one of the drivers seems to be removable. I tried it on a different, 32bit Windows computer with first the one and then the second driver.
Same problem as above. I can find the booted phone via "adb devices" but can't find the phone in fastboot mode with "fastboot devices".
Click to expand...
Click to collapse
does you phone have a bootloader?
Maurice5813 said:
does you phone have a bootloader?
Click to expand...
Click to collapse
With bootloader you probably mean a custom bootloader like ClockworkMod right?
If so: no, the phone has been untouched so far.
My old HTC phone had a bootloader to start with but as far as I know the Huawei phone doesn't and I can only boot normally or into fastboot.
SirBelial said:
With bootloader you probably mean a custom bootloader like ClockworkMod right?
If so: no, the phone has been untouched so far.
My old HTC phone had a bootloader to start with but as far as I know the Huawei phone doesn't and I can only boot normally or into fastboot.
Click to expand...
Click to collapse
I think your problem is your using the wrong commands, when you go into fastboot mode, your using "adb devices" which doesn't work with fastboot. Type "fastboot devices"
Maurice5813 said:
I think your problem is your using the wrong commands, when you go into fastboot mode, your using "adb devices" which doesn't work with fastboot. Type "fastboot devices"
Click to expand...
Click to collapse
I know, "adb devices" only works when the phone is booted normally. "fastboot devices" doesn't give a reply as can be seen in the image of the first post.
SirBelial said:
I know, "adb devices" only works when the phone is booted normally. "fastboot devices" doesn't give a reply as can be seen in the image of the first post.
Click to expand...
Click to collapse
because the daemon didn't start, you should have looked up how to use fastboot. I can tell fastboot hasn't started because it would have replied with "no devices found"
Uninstall everything (the android sdk, not drivers) and use this guide:
http://forum.xda-developers.com/showthread.php?t=2277112
Good luck!
Maurice5813 said:
because the daemon didn't start, you should have looked up how to use fastboot. I can tell fastboot hasn't started because it would have replied with "no devices found"
Uninstall everything (the android sdk, not drivers) and use this guide:
http://forum.xda-developers.com/showthread.php?t=2277112
Good luck!
Click to expand...
Click to collapse
I really hoped that you were right and I just used it wrong BUT:
I installed android sdk exactly the same way as stated in the guide.
Are you sure that "fastboot devices" should give a "daemon starting" and "no devices found" reply? I haven't found any screenshot of "fastboot devices" with one of the two replies. Just screenshots that looked like this:
Plus the guide you sent me states:
Code:
fastboot devices
...and nothing will happen, Why? because there isn't a device attached.
To me it looks like I'm not supposed to get any of the two replies you mentioned.
Enable USB Debugging
SirBelial said:
I really hoped that you were right and I just used it wrong BUT:
I installed android sdk exactly the same way as stated in the guide.
Are you sure that "fastboot devices" should give a "daemon starting" and "no devices found" reply? I haven't found any screenshot of "fastboot devices" with one of the two replies. Just screenshots that looked like this:
Plus the guide you sent me states:
Code:
fastboot devices
...and nothing will happen, Why? because there isn't a device attached.
To me it looks like I'm not supposed to get any of the two replies you mentioned.
Click to expand...
Click to collapse
I encountered this but then started the phone and enabled USB debugging and it then found the phone.
did u get this going? im having exactly the same issue. cannot get the phone detected in fastboot, either in Linux or windows
I had the same issue. Took my hours, different Systems, Cables... Try the following:
Code:
adb reboot-bootloader
.
Hope this helps! Your phone should stay at the Huawei Logo (no pink screen!)