Database Info

[Q] Stuck in "Starting Fastboot Protocol Support" when trying to flash stock images

[Q] Stuck in "Starting Fastboot Protocol Support" when trying to flash stock images
When i punch in adb reboot bootloader i get starting fastboot protocol support, i used the rootmyxoom procedure which does unlock my bootloader.
im using this method:
http://forum.xda-developers.com/showthread.php?t=1075260
Please Email me with responses, [email protected]

philski421 said:
When i punch in adb reboot bootloader i get starting fastboot protocol support, i used the rootmyxoom procedure which does unlock my bootloader.
im using this method:
http://forum.xda-developers.com/showthread.php?t=1075260
Please Email me with responses, [email protected]
Click to expand...
Click to collapse
I don't understand, when you type in adb reboot bootloader you should get fastboot...whats the problem.

bwcorvus said:
I don't understand, when you type in adb reboot bootloader you should get fastboot...whats the problem.
Click to expand...
Click to collapse
thats where I have no clue what hell is going on, if I type in flash blah blah it says waiting for device

i have the same issue, I'm I reboot via adb and then my xoom reboots and says starting fasboot protocol support and just sits there. Any help or idea why?
answered my own question. This is because my device has not been unlocked yet.
I had to do the fastboot oem unlock found here.
http://forum.xda-developers.com/showthread.php?t=967065

Only thing I can suggest is to check to make sure you have your drivers installed and ready for fastboot. I think one of the commands you can throw at it is fastboot devices which should do the samething as adb devices but use for fastboot (but can't remember, been awhile since I've had to do anything with fastboot). If that is an acceptible command then you should see your device listed, if not then your computer isn't seeing the device which is why it's saying waiting for device.
You might also want to try throwing the fastboot oem unlock command again and see what happens (it's possible that you've never actually unlocked the xoom).
This is only a few suggestions I can give you for now as I'm not at home to try throwing some of those commands myself to confirm they're valid commands or not, sorry.

drivers are installed that's how I did the original unlock. and I'm sure I hit accept. I went through the whole process of losing everything when doing so. no dice on being able to flash . and the weird thing is this. when I type in adb reboot bootloader it reboots to the fast boot protocol screen but when I type in the info to flash the recovery I get the error of can't load

I'm having the same problem, I simply can't boot into FASTBOOT. I've got the latest USB drivers, I've updated ADB, but it just won't work. It just sits there telling me "Starting fastboot protocol support".
Very frustrating, nothing I do seems to fix it - I've even done a factory reset.
Edit: Now it won't even respond to "fastboot oem unlock", it just sits there saying "<waiting for device>" even though the device shows fine when I do "adb devices" and the device also shows in Windows. (Is this simply because the device is already unlocked)

Are you sure USB debugging is enabled?
Sent from my GT-I9000 using XDA Premium App

Yep, it is
Edit: By the way, if I do "fastboot devices" nothing is listed. If I do "adb devices" it lists the XOOM just fine.
Edit again: Just noticed that the OP also used the "rootmyxoom" process, which is exactly what I used and I'm having the same issues he's having... hmm.

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.

looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM

Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!

nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.

leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...

leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.

Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......

Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.

You need the drivers.

albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.

Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?

leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782

ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.

leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?

nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".

Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?

kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.

the same issue for me. is there any working solution for that?

I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147

GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing

[Q] Unable to Flash Custom Recovery, ADB not detecting device, etc.

First problem: when I do "adb devices" in command prompt, there are no devices listed. I am pretty sure I have installed all the proper drivers.
Second problem: I don't know if my boot loader is unlocked. The reason I think this is because when I used the manudroid19 toolkit to unlock the boot loader, it restores my system, but when I try to flash a custom ROM, nothing happens. People I've talked to say that its supposed to stay in fast boot mode for about a minute before it actually boots into TWRP, but nothing actually happens.
Third problem: when I press the root button in manudroid19, nothing happens. The cmd prompt just pops up for a split second then nothing. Plain out nothing happens. Root Checker says my phone is not rooted.
How would I resolve all of this?

cm recovery
WunderWuffle said:
First problem: when I do "adb devices" in command prompt, there are no devices listed. I am pretty sure I have installed all the proper drivers.
Second problem: I don't know if my boot loader is unlocked. The reason I think this is because when I used the manudroid19 toolkit to unlock the boot loader, it restores my system, but when I try to flash a custom ROM, nothing happens. People I've talked to say that its supposed to stay in fast boot mode for about a minute before it actually boots into TWRP, but nothing actually happens.
Third problem: when I press the root button in manudroid19, nothing happens. The cmd prompt just pops up for a split second then nothing. Plain out nothing happens. Root Checker says my phone is not rooted.
How would I resolve all of this?
Click to expand...
Click to collapse
uncheck update cm recovery under settings..developer option..

WunderWuffle said:
First problem: when I do "adb devices" in command prompt, there are no devices listed. I am pretty sure I have installed all the proper drivers.
Second problem: I don't know if my boot loader is unlocked. The reason I think this is because when I used the manudroid19 toolkit to unlock the boot loader, it restores my system, but when I try to flash a custom ROM, nothing happens. People I've talked to say that its supposed to stay in fast boot mode for about a minute before it actually boots into TWRP, but nothing actually happens.
Third problem: when I press the root button in manudroid19, nothing happens. The cmd prompt just pops up for a split second then nothing. Plain out nothing happens. Root Checker says my phone is not rooted.
How would I resolve all of this?
Click to expand...
Click to collapse
My first piece of advice: stop using a toolkit, it's clearly creating more confusion than it's actually helping.
When you're issuing the 'adb devices' command are you booted into Android? What happens when you issue 'fastboot devices' when you're in fastboot mode?
Transmitted via Bacon

paztine said:
uncheck update cm recovery under settings..developer option..
Click to expand...
Click to collapse
Its always been unchecked.
timmaaa said:
My first piece of advice: stop using a toolkit, it's clearly creating more confusion than it's actually helping.
When you're issuing the 'adb devices' command are you booted into Android? What happens when you issue 'fastboot devices' when you're in fastboot mode?
Transmitted via Bacon
Click to expand...
Click to collapse
When I did adb devices, I was in Android iirc. I can't remember since the last time I did it was a day or two ago. Sorry. I am not very knowledgeable in this area. I have not done the fastboot device command.

WunderWuffle said:
Its always been unchecked.
When I did adb devices, I was in Android iirc. I can't remember since the last time I did it was a day or two ago. Sorry. I am not very knowledgeable in this area. I have not done the fastboot device command.
Click to expand...
Click to collapse
Ok, adb commands will only work while you're booted into Android or booted into recovery. Similarly, fastboot commands will only work while in fastboot mode. Let us know how you go, and if you get your serial number turned from the 'fastboot devices' command, issue this one:
Code:
fastboot oem device-info
And post the results.
Transmitted via Bacon

I would start by reading up on fastboot, this phone is as easy to root as they come so as mentioned earlier a toolkit just ads to the hassle
http://forum.xda-developers.com/showthread.php?t=2277112
Here you will find information on how to get adb and fastboot working properly, my guess is its a driver issue right now. So check device manager and manually update to the appropriate drivers if needed
And here you will find the steps to manually root
http://forum.xda-developers.com/showthread.php?t=2788632
Best of luck!

timmaaa said:
Ok, adb commands will only work while you're booted into Android or booted into recovery. Similarly, fastboot commands will only work while in fastboot mode. Let us know how you go, and if you get your serial number turned from the 'fastboot devices' command, issue this one:
Code:
fastboot oem device-info
And post the results.
Transmitted via Bacon
Click to expand...
Click to collapse
I just did that. Here are my results. It says that my device has been tampered with, and my boot loader is unlocked. And now, for some odd reason (I guess I was in fastboot while I was doing adb commands), it not detects my One. Thank you!
demkantor said:
I would start by reading up on fastboot, this phone is as easy to root as they come so as mentioned earlier a toolkit just ads to the hassle
http://forum.xda-developers.com/showthread.php?t=2277112
Here you will find information on how to get adb and fastboot working properly, my guess is its a driver issue right now. So check device manager and manually update to the appropriate drivers if needed
And here you will find the steps to manually root
http://forum.xda-developers.com/showthread.php?t=2788632
Best of luck!
Click to expand...
Click to collapse
Since I am not on my computer anymore, I will check these out and I will get back to both of you in a bit. Thanks!

timmaaa said:
Ok, adb commands will only work while you're booted into Android or booted into recovery. Similarly, fastboot commands will only work while in fastboot mode. Let us know how you go, and if you get your serial number turned from the 'fastboot devices' command, issue this one:
Code:
fastboot oem device-info
And post the results.
Transmitted via Bacon
Click to expand...
Click to collapse
demkantor said:
I would start by reading up on fastboot, this phone is as easy to root as they come so as mentioned earlier a toolkit just ads to the hassle
http://forum.xda-developers.com/showthread.php?t=2277112
Here you will find information on how to get adb and fastboot working properly, my guess is its a driver issue right now. So check device manager and manually update to the appropriate drivers if needed
And here you will find the steps to manually root
http://forum.xda-developers.com/showthread.php?t=2788632
Best of luck!
Click to expand...
Click to collapse
I rooted the phone manually using command prompt and everything worked! I got TWRP recovery, and Root Checker says I'm rooted! Thank you very much! Doing it this way took my less than 7 minutes while using the toolkit took me more than three hours, and that didn't even work!

Reinstall Pixel OS

Hi
I have a Pixel that currently has no OS on it at all. I can only get into the bootloader with no way of factory restoring the phone. Usually I would use ADB to reinstall the factory image from the Pixel image Google provides but with no way of activating USB Debugging, I'm unable to do this.
How can i get the normal factory image back onto the phone?
Thanks

jasperwells said:
Hi
I have a Pixel that currently has no OS on it at all. I can only get into the bootloader with no way of factory restoring the phone. Usually I would use ADB to reinstall the factory image from the Pixel image Google provides but with no way of activating USB Debugging, I'm unable to do this.
How can i get the normal factory image back onto the phone?
Thanks
Click to expand...
Click to collapse
You should use flash-all
Sent from my Pixel using Tapatalk

ansontyl96 said:
You should use flash-all
I can't, ADB doesn't recognise there's a phone plugged in when I'm in the bootloader
Usually I'd navigate to the platform tools folder, "adb devices" to check its there, then i'd unlock the bootloader using "fastboot flashing unlock", then i'd go on to "flash-all.sh"
But because there's no OS so USB debugging isn't on the terminal doesn't recognise the phone is plugged in
Click to expand...
Click to collapse

Sorry I am a mac user and I am not sure about windows, but as you can enter bootloader you should be able to use fastboot command
Sent from my Pixel using Tapatalk

jasperwells said:
ansontyl96 said:
You should use flash-all
I can't, ADB doesn't recognise there's a phone plugged in when I'm in the bootloader
Usually I'd navigate to the platform tools folder, "adb devices" to check its there, then i'd unlock the bootloader using "fastboot flashing unlock", then i'd go on to "flash-all.sh"
But because there's no OS so USB debugging isn't on the terminal doesn't recognize the phone is plugged in
Click to expand...
Click to collapse
adb devices only works when phone is booted into the OS. You need to use fastboot if the phone is in the bootloader. Try fastboot devices instead and see if it recognizes it.
Click to expand...
Click to collapse

robocuff said:
jasperwells said:
adb devices only works when phone is booted into the OS. You need to use fastboot if the phone is in the bootloader. Try fastboot devices instead and see if it recognizes it.
Click to expand...
Click to collapse
Ah ok I didn't realise they could do alot of the same stuff cos noob.
so "fastboot devices" - make sure its there
"fastboot flashing unlock" - unlock bootloader?
and then "fastboot flash OS.zip"?
Click to expand...
Click to collapse

Question [Solved] Re-locking bootloader - no fastboot commands working

Hi everyone.
I´ve decided today that I want to re-lock my bootloader on Lenovo P11 tablet and I discovered no fastboot commands work on that.
I installed clean version of ROM from Lenovo Rescue and Smart Assistant (TB_J606L_S120217_210805_ROW) but still nothing works.
Normally i reboot to Fastboot and try "fastboot flashing lock" but i recieve:
< waiting for any device >
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
When i try others like "fastboot oem lock" i recieve:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Does anyone has any advice what can I do to relock bootloader?

1. enable developer option
2. enable oem unlock in developer option
3. boot to fastboot mode and run
fastboot flashing lock

Thanks @ong14 for your reply but as you can see above I already tried that...

If you're on chinese firmware, try "fastboot oem unlock-go".

Sadly I get this response for this command:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Is it possibly because of version of my ADB and Fastboot tools? I downloaded many versions (lastly directly from Android Studio) but it didn´t fix anything. @ong14, could you possibly upload the tools you are using?

Sorry for my last reply, it should be "fastboot oem lock-go".
AFAIK, if you're on global rom, use this "fastboot flashing lock".
And if you're on chinese rom, use this "fastboot oem lock-go"
I'm using an old minimal adb and fastboot.

It is totally OK, I am grateful that you are trying to help me at all.
I will try your old adb and fastboot tools and see what happens.
Sadly I don´t have much hope. I am on global rom and command "fastboot flashing lock" resulted only in:
"
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
"
I will keep you posted about my progress and what else I tried.

Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!

kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
My guy, you are brilliant. I wonder why the change from oem to flashing was done and were you getting sent to that fastbootd menu too? This worked for my 2020 Moto Edge and I don't know how much longer I would have needed without you.
Thanks.

kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
Install RSA from Lenovo also works, and you can run rescue if you want to go back to 100% bone stock

kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
Where and how do you get the drivers for this tablet? For some reason I'm stuck in (what I think) is the exact same screen on my tablet. It says fastboot... in the lower left hand corner and you can hear the disconnect chime come from my laptop every few seconds. I punch in fastboot devices and it's stuck in limbo, no error codes or anything.

BakedinRC said:
Where and how do you get the drivers for this tablet? For some reason I'm stuck in (what I think) is the exact same screen on my tablet. It says fastboot... in the lower left hand corner and you can hear the disconnect chime come from my laptop every few seconds. I punch in fastboot devices and it's stuck in limbo, no error codes or anything.
Click to expand...
Click to collapse
Did you check device manager?

I didn't think I had to, when I plug in the tablet it pops up with the name and everything.

I'll try the Motorola drivers, is that going to solve the fastboot stuck screen?

Where do I go about getting the Motorola drivers?

hey mate. i had problem. now my Xiaoxin Tablet Pro 2021 having widevine L3 even i already lock the BootLoader and Stock Rom. how do i get Widevine L1 ?

kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
what did u do after installing the usb drivers?...can u pls explain in detail?....actually im facing the same problem again and again

me too can't figure it out, very sad