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!
Related
Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
mdky said:
Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
Click to expand...
Click to collapse
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
For more info, you should check Android's page on ADB if you would like. http://developer.android.com/tools/help/adb.html
I'm not sure if any of this is actually directly related to your issue, but it is nice to start with the basics.
wildstang83 said:
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
Click to expand...
Click to collapse
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
mdky said:
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
wildstang83 said:
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
Click to expand...
Click to collapse
I will try these command when I get home, thank u!:good:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
mdky said:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
Click to expand...
Click to collapse
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
wildstang83 said:
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
Click to expand...
Click to collapse
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
mdky said:
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
Click to expand...
Click to collapse
Oh wow, that is quite the ordeal, but atleast its something huh, lol
I wonder if you could run adb and fastboot commands in xp mode on your win7 pc?
I know there is a way to run programs in XP mode, its just been awhile since I've done it.
And its no problem to keep trying to help, even if I don't know the device and all that. Maybe I can learn to while we are at it, and maybe make a new friend along the way
Hello everyone, I'm using Redmi Note 3 and I have tried rooting it several times.
I have unlocked the bootloader. I have also installed the adb drivers.
When I connect phone in fastboot mode and write 'fastboot devices' in cmd it doesn't return anything. But when I connect when its on, adb devices returns the device code.
Please help.
Same, happens to mine too. Used to work with a previous install of windows, but now, nope.
Had this issue too.
Try going to Device Manager and check to see if Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Install minimalist ADB and fastboot and right click Android Bootloader Interface. Click Update Driver Software, browse computer, and then click the option to list driver files already present on your drive. It should pull up a fastboot driver that's an older version than the one you currently have. Install that and fastboot will work again.
Doesn't work
Can you please link the files for download when we're updating the driver software.
Downloaded and installed ADB. Following tutorial here:
https://www.xda-developers.com/nexus-6p-bootloop-fix/
Specifically:
- Connect your smartphone or tablet to your computer with a USB cable. Change the USB mode to “file transfer (MTP)” mode. Some OEMs may or may not require this, but it’s best to just leave it in this mode for general compatibility.
- In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices
- On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).install adb
- Finally, re-enter the command from step #6. If everything was successful, you should now see your device’s serial number in the command prompt. Yay! You can now run any ADB command on your device! Now go forth and start modding your phone by following our extensive list of tutorials!
https://www.xda-developers.com/install-adb-windows-macos-linux/
I did all the above. But don't see anything from:
C:\ADB>fastboot devices
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
Nexus 6P was plugged into the USB cable on Win10 machine. Am in MTP mode. Most recent Google USB drivers installed.
I have done OEM Unlock in setup|Developer options. I have also turned on USB debugging in same options.
I am [obviously] lost. Anyone know what else I might try?
OK, I have made a little progress messing around on my own. It seems that running from the CMD line in Win 10, ADB command works but Fastboot does not. WHY? Bith are in the same directory.
If I type Fastboot by itself, then I get a list of the associated parameters, which means that the CMD system DOES recognize the Fastboot command.
Now, if I run CMD====> "ADB devices", it looks like my device is recognized and attached (that is my serial# below).
But if I try CMD=====> "Fastboot devices", as the instructions require, I get nothing. And if I try to run the flash job via Fastboot, that does not work either.
==================
C:\ADB>adb devices
List of devices attached
8XV5Txxxxxxxxxxx device
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
===================
Wondering if I need to install the Android SDK on Windows for this process to work?
I Think You need to Redo The process from Step One.
I Heard about This and Never Did An OTA.
If it Persists Try Using A Different PC and If After That It doesn't work Then Yes Android SDK is The last Option.
Sent from my Nexus 6P using Tapatalk
Solved. I needed to add the ADB install directory to the environmental path. Don't quite understand why, but doing so allowed me to get the problem fixed.
Once I reboot to bootloader and connect to PC, the command "fastboot devices" does not recognize the device, so when I try to unlock it. it says "waiting for device". I've enabled both OEM unlocking and USB debugging.
The phone shows "fastboot_unlock_verify ok"
"The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously. "
EDIT: Solved it by using the correct platform-tools
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
7tyjupiter said:
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
Click to expand...
Click to collapse
I used the ones from here - https://www.getdroidtips.com/download-adb/#How-to-Install-Android-SDK-and-Platform-Tools
Solved.
I downloaded the platform tools 30.0.5 and reinstall it. Then i reinstall the adb bootloader driver right at the moment when the Nord2 is in the fastboot mode.
cheers
I have no developer options for reboot, bootloader, recovery.
platform tools 30.0.5, where?
Try after reboot into bootloader "fastboot devices". Is the Nord 2 recognized?
For me the correct command was "fastboot flashing unlock".
Hier is the link for the Platform tools 30.0.5
adb - platform tools v30.0.5.zip | by abdyasar for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
F4t16u3 said:
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
Click to expand...
Click to collapse
Mine does not show up.... -.-
Hey all, I just got a G90 Pro that I want to put a ROM on, but something is up with the fastboot. I have the drivers installed according to what I found online, but when I go to fastboot there is no response from the cmd inputs. Nothing even shows up when I check fastboot devices. Has anyone had luck with these phones? I can't even unlock the bootloader!
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
jwoegerbauer said:
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
Click to expand...
Click to collapse
I have done this, but did it again just to be sure, and device manager recognizes the G90 Pro under USB devices, and ADB finds it, but when I do the 'adb reboot bootloader' the fastboot mode text is on the bottom, yet fastboot commands don't do anything, not even 'fastboot devices'.
Edit: Fastboot devices is recognized in fastbootd, but not regular fastboot, yet the other commands don't work.
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
jwoegerbauer said:
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
Click to expand...
Click to collapse
Fastboot reboot fastboot just brings up the fastboot command list. Assuming it's expecting me to try reboot bootloader.
That's really weird because your phone is running Android 10.
My info in settings definitely confirms that. Nothing seems to be working as expected though.
jwoegerbauer said:
That's really weird because your phone is running Android 10.
Click to expand...
Click to collapse
Is there any other possible solution? I still can't get fastboot commands to work after rebooting to fastboot mode from fastbootd.