bluepojo's post
For those who are having the same issue:
Turns out on Ubuntu, you need root permissions. Run the commands with sudo and all is well.
Click to expand...
Click to collapse
I'm using Windows cmd with adb and fastboot do my work. My device is an ideaUSA CT702 - MID A777 running a rooted 4.0.3 ICS. adb devices shows my device id under "List of Devices", but fastboot devices command shows nothing during normal boot. After booting into bootloader, which is a completely black screen (is this a problem, or is it ok because all devices are different. This forum post says it's ok to have a blank screen google this: I can't post links: forum.geeksphone.com/index.php?topic=1830.0). The forum also says it's ok to have this show up after typing fastboot devices in bootloader mode "? fastboot", which is exactly what I have.
However, the forum also says that there should be a string after this, and most other forums I've seen say that you should get your device ID. Did I do anything wrong?
Related
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
KrisM22 said:
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
Click to expand...
Click to collapse
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
kuisma said:
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
Click to expand...
Click to collapse
Thanks! Please pardon my ignorance... I did:
Code:
adb devices
pause
adb reboot-bootloader
pause
fastboot reboot
After adb reboot-bootloader my phone changed from the recovery screen to the white tmo logo screen and hung.
fastboot reboot still says waiting for device...
EDIT Okay, I think I've figured out that, from power off, volup+power=recovery screen , and voldn+power=fastboot screen(white with tmo logo).
But I can't do anything from that fastboot screen. The computer recognizes it when I USB plug it, but it still says waiting for device.
EDIT: It appears I have a driver for adb, but no driver for fastboot, or just plugging the powered off phone in to usb.
fixed.
<deleted>
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!)
Hello.
I own a Moto G (Global GSM) running CyanogenMod 11 rooted with TWRP recovery and the bootloader is unlocked. I have been trying to go back to the stock firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2542219 but I have a problem. The adb drivers for my device work fine when I am in the system or in the recovery, but don't work in the bootloader. I am able to type "adb reboot bootloader" when I'm in the system/recovery and it will follow the command, but once I get into the bootloader it stops. When I type "adb devices" a line saying "List of devices attached" comes up with nothing underneath it.
I am completely lost and would greatly appreciate any help. Also I am new to XDA.
Thank you
derekokelly said:
Hello.
I own a Moto G (GSM) running CyanogenMod 11 rooted with TWRP recovery and the bootloader is unlocked. I have been trying to go back to the stock firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2542219 but I have a problem. The adb drivers for my device work fine when I am in the system or in the recovery, but don't work in the bootloader. I am able to type "adb reboot bootloader" when I'm in the system/recovery and it will follow the command, but once I get into the bootloader it stops. When I type "adb devices" a line saying "List of devices attached" comes up with nothing underneath it.
I am completely lost and would greatly appreciate any help. Also I am new to XDA.
Thank you
Click to expand...
Click to collapse
When you are in bootloader you have to use fastboot. Type 'fastboot devices' and you'll see the connected device. Refer this guide "[Guide] How To Setup And Use Fastboot" for more info: http://forum.xda-developers.com/showthread.php?t=2277112
***********************************************************************************************************************************************************************
Hit the "Thanks" button if you think I helped!
Type 'fastboot devices' and you'll see the connected device.
Click to expand...
Click to collapse
When I do this, a blank line comes up underneath "List of devices attached". I don't know what I'm doing wrong.
derekokelly said:
When I do this, a blank line comes up underneath "List of devices attached". I don't know what I'm doing wrong.
Click to expand...
Click to collapse
Have you enabled 'USB Debugging' in Settings and allowed your computer to access it?
PhaseBeta said:
Have you enabled 'USB Debugging' in Settings and allowed your computer to access it?
Click to expand...
Click to collapse
Yes, I did. It has something to do with the ROM that I was on. For some reason, it won't recognise my device anymore, no matter what ROM I use. It doesn't really bother me though, there's plenty of ways to do things nowadays.
USB Debugging nor the rom have anything to do with fastboot.
Are you using a Windows PC? If so, when in bootloader mode, check your Device Manager and see if the driver is loading correctly. If it isn't, it'll have a yellow exclamation symbol next to it. If that's the case, you'll just need to manually load the driver from there.
I have a Zeki TBQC1063B Tablet with Android 4.1.1 on it. I am trying to see if I can unlock the bootloader so that I can try to put Ubuntu for mobile on it. This thing has been nothing but the bane of my existence all night tonight. I have made sure that while the device is on, the USB Debugger IS on, and I am using the correct USB drivers. In my SDK tools, I run the command adb devices and I get the following result:
List of devices attached
??????????????? device
For curiosity, I ran the command fastboot devices and nothing comes up. When I try to boot into "fastboot mode" it just comes up with a recovery screen with no mention of Fastboot. I am lost, confused, and very frustrated. Any thoughts?
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!