adb fastboot flashing lock < waiting for any device > Does not function !

[Dave.037 3]

Hi I'm having a problem performing the lock in adb

Everything works as per the Pro1-X OEM Lock - User Manual

Until I perform the actual lock command then nothing further happens ,

I don't get the screen on my Pro1 to confirm the lock, it remains in the boot loader screen

The USB connection is disconnected on entering the lock command in adb

I have a Dell Precision running Windows 10

See below PowerShell text:-

I'm guessing something still needs to be installed for this process to work ?

Can some one advise what I'm missing or need to do to get the Lock to work

Thanks David

===================================================================

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\Windows\system32> adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
c8fd29a2        device

PS C:\Windows\system32> adb reboot bootloader
PS C:\Windows\system32> fastboot flashing lock
< waiting for any device >
 

[FlyingAntero 871]

Most likely you are missing fastboot drivers. When you are in fastboot mode what does it say when you type "fastboot devices"? Is the phone recognized like in ADB mode?

[EskeRahn 5,460]

Apart from driver, It COULD also be a connection issue, as fastboot is more picky than ADB...

You could try to connect through a hub, as direct connection to newer pc's USB 3 ports have caused me problems with fastboot.

I do not know why a hub helps here, but my guess is that it adds som lag in the connection, that makes fastboot more happy.

I had issues with a Lenovo laptop, but using a USB 3 port on Lenovo 'docking' connected via Thunderbolt 4, make it work. I also experimented with an ancient cheap (usb 1?) hub, and it worked, but things got extremely slow, so flashing took sort of forever - but it did work.

[Dave.037 3]

Hi FlyingAntero,

After entering:-

PS C:\Users\Fxtec> adb reboot bootloader
PS C:\Users\Fxtec> fastboot devices
PS C:\Users\Fxtec>

It returns immediately to the command prompt, not reporting any information.

So where from & how do I install the fastboot drivers you mentioned ?

Thanks EskeRahn,

There is no differance connecting by a hub or with shorter or longer USB cables,

I'm using the supplied Pro1 USB cable

[EskeRahn 5,460]

That "fastboot devices" returns without even waiting is the expected behaviour if it does not see any device in fastboot mode.

It only shows a result if the device is in fastboot mode (shows the bootloader menu).

Is the hub USB 3? If so try something inferior(!)

Try from an old PC, a linux PC or with an old usb 2 hub. From other threads this seems to hit 'newer' pc's with windows andd usb 3.0. So an old pc with usb 2.0 is likely to do the trick.

[EskeRahn 5,460]

PS I assume that you await the boot of "adb reboot bootloader" to finish, ending in the bootloader menu, right?

[Dave.037 3]

It is an older PC originally on Win 7 no USB 3 ports.

It looks like a driver problem , I've now identified from the open USP devices & printers,

The phone when initially plugged in to the USB port reports as BENGAL-IDP with no errors reported

after entering adb reboot bootloader

it changes and reports as ANDROID with status of Driver is unavailable

Running the trouble fixer has not fixed the missing driver......

[Dave.037 3]

Yes waited for the phone to respond with the boot loader menu

then entered the fastboot flashing lock

then nothing else happens no phone menu change

[EskeRahn 5,460]

I see it like this in adb

And like this in fastboot

 

I have never heard of "Kedacom" BTW

[EskeRahn 5,460]

....The driver is ancient:

 

[Dave.037 3]

Thanks all for your replies,

I have now fixed the problem and the fastboot flashing lock is now working.

From the devices page selecting the trouble shouter from the device properties,

then going to the device driver tab selecting update and forcing a windows update to start,

then selecting the optional drivers in windows update found the Google android driver,

installed and now its working 🙂

Regards David

[FlyingAntero 871]

3 minutes ago, Dave.037 said:

Thanks all for your replies,

I have now fixed the problem and the fastboot flashing lock is now working.

From the devices page selecting the trouble shouter from the device properties,

then going to the device driver tab selecting update and forcing a windows update to start,

then selecting the optional drivers in windows update found the Google android driver,

installed and now its working 🙂

Regards David

Getting the drivers working is always pain in the ass. Once that is resolved everything else is easier. Great that you were able get it working!

Here is a video of the installation of fastboot drivers. It is for Xperia XA2 when I flashed Sailfish X to it but same idea works for other devices on Windows 10. Unfortunately, it is in Finnish but maybe someone can find it helpful.