When I'm trying to enter fastboot I just got : Starting fastboot protocol support.
I've tryed to wait for 15 or 20 minutes, but nothing happens
What to do?
Sent from my Xoom using XDA App
once you see the fastboot protocol at the top of the screen type your next ADB command. such as "fastboot reboot bootloader"
Related
I'm supposedly on fastboot mode. on the One x, I can run a command to confirm I'm connected but unsure what to do using the infinity since the fastboot commands is a different.
I ran this command "fastboot -i 0x0b05 flash staging ebtblob.bin" (part of nvflash steps) and it's stuck at "waiting for device".
When connected to my windows laptop, it says "ASUS Android composite ADB interface" in device manager when booted normally. And it says "AsUS Android bootloader interface" when I'm supposedly in fastboot.
thanks
mrjayviper said:
I'm supposedly on fastboot mode. on the One x, I can run a command to confirm I'm connected but unsure what to do using the infinity since the fastboot commands is a different.
I ran this command "fastboot -i 0x0b05 flash staging ebtblob.bin" (part of nvflash steps) and it's stuck at "waiting for device".
thanks
Click to expand...
Click to collapse
"fastboot devices" should show something. With the old bootloader, maybe just "???????? - device" - with a newer one, an actual serial number.
"fastboot continue" should continue booting Android, that would be a sign that the protocol basically works.
_that said:
"fastboot devices" should show something. With the old bootloader, maybe just "???????? - device" - with a newer one, an actual serial number.
"fastboot continue" should continue booting Android, that would be a sign that the protocol basically works.
Click to expand...
Click to collapse
just says waiting for device.
tried:
1. fastboot continue
2. fastboot -i 0x0b05 continue
3. the nvflash command above
4. fasboot reboot
5. fastboot -i 0x0b05 reboot
I was on 4.0.3 ICS before unlocking and I suppose still on 4.0.3 just unlocked. thanks!
when i connect my motorola xoom that is stuck on m logo, i enter on motorola xoom in fastboot mode then in my computer i go to command prompt where there is fastboot, i type "fastboot flash boot boot.img" but i received the following message:"error:cannot load boot.img".
Do you have the image file in the adb folder?
Sent from my Xoom using Tapatalk 2
i had to sbf my phoe and now its stuck in the boot loader on each power up i can enter the boot menu and get to lock screen, but the bootloader msg is very annoying i used the rsd script generator and used unerversal i tried others by taking out the gpt and tz but same results
A quick search will get you the answer on how to clear the sticky bit error.
Sent from my HTC6525LVW using Tapatalk
i have the same problem and i didnt find anyway to fixit
Sticky Bit Fastboot
and here is the fix
First you want to download this zip file extract the file to your computer so it should read C:\Android
Next click on it once so it's selected hold left shift and right click and click on "open command window here"
Now plug in you phone and boot it up normally, then make sure usb debugging is enabled.
now in the command window type "adb devices" (this makes sure your device is hooked up and ready to be fixed)
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
download all the files from here
http://www.2shared.com/file/M1n_-B0-/all.html
use the first 3 command only like what i did so you wont lose your data
my phone is stuck on the boot loop. i think i cant follow this fix. do you have any other fix? thanks
While Unlocking Bootloader, Fastboot Commands are stuck on "waiting for device"
I have a 6045I version Idol 3 and I've installed the 15 second adb fastboot setup. When I type the command "adb devices" I get the id number and rebooting to bootloader works fine. Once I reboot, the command fastboot -i 0x1bbb devices shows the id number. The problem is when I try either fastboot flashing unlock or fastboot oem unlock both result in the cmd saying "waiting for device". I don't know how to fix this but I've done some research and I think it might have something to do with drivers or maybe alcatel blocked fastboot after a certain update? All I want to do is flash the lineage rom to get android 7.1 nougat so I would really appreciate any help.
So, Iwas using Havoc Os 3.8 on my realme 5i, but I wanted to lock bootloader again, then I entered fastboot mode and locked bootloader, but I stucked in fastboot mode, It looped. Could not enter recovery or system. Only fastboot mode, because bootloader is locked I couldnt flash anything. I tried fastboot flashing unlock command but it did not work.
But solution was very easy, fastboot was not actually fastboot, everytime I power off device and power up there was not fastboot writing and robot icon, just directly fastboot itself. So actually it is fake fastboot, you just need to use volume buttons and select reboot to bootloader option, once device reboot you will see now fastboot- robot icon then fastboot itself, now you can unlock device with "fastboot flashing unlock_critical" command.
First, power off. Then wait for couple of minutes then start fastboot again.