I was trying to unlock my device's boot loader, so I had to get into fastboot.
I was able to put the device in fastboot mode (the LED turned blue), but whenever I run the command "fastboot devices", it just does not find it.
When I connected, I installed the Android ADB Interface driver, is that correct?
I'm kinda lost here, any help would be appreciated.
Thanks!
-----EDIT-----
Figured that the fastboot I was using was not working properly. Downloaded another one and it worked fine.
Sorry, thread can be closed.
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 used "adb fastboot bootloader" command, installed Nexus Google Galaxy fastboot drivers and got into fastboot mode today--maybe (See screenshot. Installed FB drivers after yellow arrow).
I know very little about fastboot mode. When I've used it with FB cable I first see a logo on tablet screen, and fastboot output appears on tablet. This didn't happen with adb fastboot command, the screen stayed black. Also, adb devices and fastboot devices commands both returned the same device number. I've always seen different numbers from those two commands.
Still, the fastboot commands I ran seemed to work. So my questions:
Is adb fastboot different from "real" fastboot?
Why no output on tablet screen?
Do we know for sure the bootloader is locked? Is there any possibility that "fastboot oem unlock" would actually work?
Has anyone here tried it?
(Sorry, no, I'm not gonna test ) Thanks for any info.
Fastboot Cable doesn't work: Maybe everyone already knows. I knew my old one wouldn't work so got a brand new one--and nothing.
.
I'm trying to test a twrp recovery I ported to my phone, but fastboot isn't working correctly. Adb works fine, adb devices shows my phone. Windows device manager shows adb composite device, all is well. Adb reboot bootloader puts the phone into fastboot as it should. Device manager then shows android boot loader interface. It should be working since it seems like the appropriate drivers are loaded, but fastboot devices gives me a blank line. Fastboot reboot just shows waiting for device and never gets any further. What am I missing?
Jesseb342 said:
I'm trying to test a twrp recovery I ported to my phone, but fastboot isn't working correctly. Adb works fine, adb devices shows my phone. Windows device manager shows adb composite device, all is well. Adb reboot bootloader puts the phone into fastboot as it should. Device manager then shows android boot loader interface. It should be working since it seems like the appropriate drivers are loaded, but fastboot devices gives me a blank line. Fastboot reboot just shows waiting for device and never gets any further. What am I missing?
Click to expand...
Click to collapse
Hello men.
Did you get the fastboot to work?
I'm in the same situation here.
Thanks :fingers-crossed:
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
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!