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.
.
Related
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.
Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
DadSteveo said:
Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
Click to expand...
Click to collapse
Unfortunately, there is no known recovery from this type of failure. I don't say that casually and wish there was a solution. The symptoms you report are both common and tell tale. The device is bricked.
I just replaced the motherboard on my hdx 8.9
It worked, I had to order a daughterboard also.
Total cost around $50 from where I got them.
Worth looking into. Watch teardown videos on YouTube and get the right tools.
Sent from my SM-N920T using Tapatalk
Too late?
DadSteveo said:
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Click to expand...
Click to collapse
Since fastboot appears to respond as expected on your device,
I'd be **very** interested in testing my long-standing theory
that 'fastboot update' __might__ work even on locked devices.
The "gotcha" is that we'd need to prepare the right package for
your Kindle. So, I gather it's an HDX 7" (3rd Gen?), i.e. "thor" model.
Do you remember what version of Fire OS you had installed?
Hi guys,
In the past days i've been troubling my head with trying to unlock the bootloader on my lenovo tb-x103f, but cant seem to enter fastboot mode
I've been using this guide as reference, among other searches from all around, trying to work around this, but cant really seem to come to the bottom of this.
from cmd
adb recognizes my device
"adb reboot bootloader" tablet just boots into the startupscreen
"fastboot devices" somehow "confirms" that im in fastboot, even tho Im acctually not (right?)
"fastboot oem unlock-go" finishes, and says its successfull, but nothing happens (obviusly, since its not acctually in fastboot mode)
from there it just sits there, and nothing happens. have to reboot it myself, either via cmd or the button
why is it not entering fastboot mode? is there any fix for this?
This is getting really frustrating as I just wanna root the tablet and most likely install lineageOS, or some other custom ROM..
thanks in advance
If you can reboot it with a command than you are connected in fastboot mode. It sounds like you have unlocked you tablet. Enter fastboot mode through adb again and try "fastboot oem device-info"
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!
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.