While Unlocking Bootloader, Fastboot Commands are stuck on "waiting for device" - Onetouch Idol 3 Q&A, Help & Troubleshooting

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.

Related

[Q] how do I confirm I'm connected to my tablet using fastboot?

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!

Xt1033 Adb Can't find device in fastboot but finds it when booted

Odd thing really, When I type "adb Devices" when My Moto G is in fastboot, No devices are found.
How ever, When I Simply boot up my phone, adb can find it perfectly fine.
My drivers are up to date.
Can someone help me with this?
Do you have adb debugging enabled?
If your phone is in fastboot mode, type "fastboot devices" at the command prompt.
I don't believe ADB commands work in fastboot. ADB commands are used in debugging mode.
audit13 said:
If your phone is in fastboot mode, type "fastboot devices" at the command prompt.
I don't believe ADB commands work in fastboot. ADB commands are used in debugging mode.
Click to expand...
Click to collapse
oh Such a rookie mistake, Thanks.
Trying to fix my dumb error, I have a XT1034 but Resored it to A XT1033 Firmaware
Did the fastboot command find you phone when the phone was in fastboot mode?
We were all rookies at one point

unlocking bootloader

hey please help i am unable to unlock boot loader of my coolpad note 5 which has snapdragon 617 soc, no unlock code type help or instruction on official forum and no help there because all command returns as unknown command ,
i tried many command except these two command all return unknown command ,
fastboot devices works shows device no
fast getvar all works showing something
i checked all driver installed properly and pc showing it on device manager as fastboot device even fastboot recognized it as a fastboot devices, also i allow oem unlocking on developer setting and enabled usb debugging
after this all command like
fastboot oem unlock
fastboot oem unlock-go
fastboot boot
fastboot reboot
fastboot flashing unlock
fastboot oem device-info
fastboot flash
all and more i found i net returns unknown command remote
i tried with vendor id but no result
i checked fastboot getvar all returns its kernal as lk
so do little kernel has problem , i have its firmware package but not found aboot.c
please help its unrooted
attached error command screenshot in zip

getting error FAILED(remote:unknown command) on xt1721

i tried, every procedure for unlock bootloader on moto c pus. giving error "FAILED(remote:unknown commond)"in adb terminal commond "fastboot oem get_unlock_data"
adb &USB drivers are well, detecting the device fastboot serial number, "fastboot devices, fastboot reboot, adb devices, adb reboot bootloader" ....these commands are working but when i tried "fastboot oem get_unlock_data" for getting my device id , giving error "FAILED(remote:unknown commond)"......
please help me how to solve this!!!!

"unable to open fastboot HAL"

Hello,
I'm trying to unlock the bootloader on my Oppo A 15 with ColorOS 7.
The developper mode, debugger usb and oem unlock are enabled.
I use the last adb fastboot platform tools.
I reboot my phone on recovery mode (there's no fastboot, or download mode or whatever), I then have a very short menu on my phone.
On my computer, fastboot detect the fastboot device but then, unlocking bootloader doesn't work.
Fastboot fastboot flashing unlock return the message "unable to open fastboot HAL"
There's not much I can do as a matter of fact. I tried several of the command In Here and most don't work.
The command "fastboot getvar all" gave me a sh...load of informations, but I don't know what I can do with it.
Any help?

Categories

Resources