Related
[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.
I've tried to flash MIUI9 over LineageOS 14 with full formating.
After flashing I'm stuck at boot logo MI. Even if I try to boot into recovery.
Fastboot works, but I'm unable to change anything
Code:
$ fastboot boot recovery.img
> FAILED (remote: unlock device to use this command)
$ fastboot oem unlock
> FAILED (remote: Token verification failed, reboot the device)
The thing is, I remember unlocking bootloader when flashing original ROM with LOS. How is it locked again?
How to get out of this situation? I don't care about any data on the phone.
Thank you.
xda-lukasik said:
How to get out of this situation? I don't care about any data on the phone.
Thank you.
Click to expand...
Click to collapse
In this situation only EDL-mode flashing is possible, but no worries, you can unlock it and get MIUI again at the same time...
https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
xda-lukasik said:
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
Click to expand...
Click to collapse
You aren't reading the guide correctly, but for a Linux user I will clarify a few things.
- look, in the guide "Command: fastboot oem edl (this brings your device in a kind of emergency recovery state) -> the device does only show a black screen" - it means fastboot and "fastboot devices" do not exist anymore and your device enters QUALCOMM HS-USB QDLOADER 9008 mode
- run lsusb on Linux in fastboot and then in EDL/9008 mode - the IDs will be different and there is no Linux driver for 9008
- the Linux tool you mentioned is just a script to automate some trivial tasks which can be done manually in fastboot mode. I checked the source code and note "sudo apt-get install android-tools-fastboot", it pulls the fastboot app from a repo and works on it. The tool is completely useless for this job.
- your only option is MiFlash which runs on Windows
- you can get Windows 10 evaluation ISO from Microsoft and get rid of it later
- you can get Windows running in a much easier way but we are forbidden to talk about it on this forum
:good:
Good luck!
Tried and failed.
After oem edl there is no device listed in miflash and "flash" does nothing.
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
cybercruizer said:
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
Click to expand...
Click to collapse
I'm unable to flash anything
Ugh, when you enter edl mode it becomes different device in virtual box and you need to add it again.
But I tried it several times with real windows machine and it didnt show up either (??)
It still didnt worked, I got errors such as:
Failed to hello message
Ping failed
Solution was to use older MiFlash tool (2015).
Thanks all for your help.
Hello everyone,
after unlocking my bootloader (on a Realme 5 Pro) to install TWRP and custom ROM, I am now stuck at trying to make fastboot do anything.
No matter which fastboot command I try, the phone won't execute it. I instantly get a "FAILED" and "(No error)" returned and the phone exits fastboot, showing some logo with a chinese message, as well as "press any key to shutdown" in the top left corner.
The only excpetions to that behaviour:
1. "fastboot devices" works as expected and recognizes the phone.
2. "fastboot boot [path to TWRP .img file]" sometimes gets stuck at "downloading boot.img..." indefinitely, sometimes it fails like all the other commands
3. "fastboot flash recovery [path to TWRP .img file]" gives an instant "FAILED", but the error message is "requested download size is more than max allowed"
I've tried re-locking and unlocking the bootloader, when unlocked both colorOS and fastboot recognize the bootloader as being unlocked.
I have no clue what to try at this point, hopefully someone can help me out?
Same problem here.
Mine is Realme 3 pro with the new version of realme UI, RMX1851, C.04, I have unlocked bootloader without downgrading it to color os 6, but now I cannot flash twrp in my device. After going into fastboot mode, after applying the commands, it says "FAILED" (remote: GetVar variable not found) and sometimes directly "ERROR"
The fix was an incredibly easy one, but I only found it/got the idea through a lot of googling... simply used a different PC (that I never used adb and fastboot with before), let windows search for drivers online, and BAM, it works!
Hopefully this will help someone in the future.
If you don't have more than one PC, I guess the best bet would be uninstalling all adb and fastboot related drivers.
Hello wonderful xda peeps,
My
-
Mi A2
Running Android 10
xiaomi/jasmine/jasmine_sprout
10/QKQ1.190910.002/V11.0.5.0.QDIMIXM
is stuck in bootloop, how can I fix it or at least how do extract my files?
Thank you kind regards!
Micklo said:
Hello wonderful xda peeps,
My
-
Mi A2
Running Android 10
xiaomi/jasmine/jasmine_sprout
10/QKQ1.190910.002/V11.0.5.0.QDIMIXM
is stuck in bootloop, how can I fix it or at least how do extract my files?
Thank you kind regards!
Click to expand...
Click to collapse
What did you do before this happened? Is it your bootloader locked? Can you enter to recovery and/or fastboot?
SubwayChamp said:
What did you do before this happened? Is it your bootloader locked? Can you enter to recovery and/or fastboot?
Click to expand...
Click to collapse
Yes, I can enter Android Recovery and Fastboot.
Yes, the bootloader is locked.
I mistakenly clicked on "Run Graphics Test" in android recovery and it installed some update and my phone has been stuck eversince
Update
I've wiped my phone to factory reset and it is still stuck in bootloop
Micklo said:
Update
I've wiped my phone to factory reset and it is still stuck in bootloop
Click to expand...
Click to collapse
If you have enabled USB debugging and OEM unlock then you can unlock bootloader to get an easy way to send it to EDL mode and you can flash the stock ROM using MiFlash tool.
For future reference this is the first that any user have to do before to "play" with the device so you have more ways to recover it.
There is some probability that your device is trying to boot to the wrong slot, first update your platform-tools if needed https://developer.android.com/studio/releases/platform-tools then see if these commands work:
To identify your current slot type
Code:
fastboot getvar current-slot
then set as active the opposite slot with
Code:
fastboot --set-active=a
changing a for b as opposite slot
Also it exists this tool that can help you but you would need to previously enable USB debugging: https://www.xiaomitool.com/V2/ this tool allows adb (disabled by Xiaomi) to work through recovery stock.
In the case you can't unlock bootloader cause your USB debugging and OEM unlock were not previously toggled then you should have to use MiFlash tool through EDL mode using test point, also there is other tool called QFlash/Qfil.
SubwayChamp said:
If you have enabled USB debugging and OEM unlock then you can unlock bootloader to get an easy way to send it to EDL mode and you can flash the stock ROM using MiFlash tool.
For future reference this is the first that any user have to do before to "play" with the device so you have more ways to recover it.
There is some probability that your device is trying to boot to the wrong slot, first update your platform-tools if needed https://developer.android.com/studio/releases/platform-tools then see if these commands work:
To identify your current slot type
Code:
fastboot getvar current-slot
then set as active the opposite slot with
Code:
fastboot --set-active=a
changing a for b as opposite slot
Also it exists this tool that can help you but you would need to previously enable USB debugging: https://www.xiaomitool.com/V2/ this tool allows adb (disabled by Xiaomi) to work through recovery stock.
In the case you can't unlock bootloader cause your USB debugging and OEM unlock were not previously toggled then you should have to use MiFlash tool through EDL mode using test point, also there is other tool called QFlash/Qfil.
Click to expand...
Click to collapse
Thank you for your kind assistance.
Before it was stuck in boot loop:
- I enabled USB Debugging
- I did not enable OEM Unlocking
Using:
Code:
fastboot getvar current-slot
returned
Code:
current-slot: a
Now running
Code:
./fastboot --set-active=b
i got the following:
Code:
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Micklo said:
Thank you for your kind assistance.
Before it was stuck in boot loop:
- I enabled USB Debugging
- I did not enable OEM Unlocking
Using:
Code:
fastboot getvar current-slot
returned
Code:
current-slot: a
Now running
Code:
./fastboot --set-active=b
i got the following:
Code:
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are using PowerShell, try to switch firstly to CMD and then type the commands but open it as admin, and check if you have the latest platform-tools.
Also check if the tool provided with link works for you and report back.
SubwayChamp said:
You are using PowerShell, try to switch firstly to CMD and then type the commands but open it as admin, and check if you have the latest platform-tools.
Also, check if the tool provided with link works for you and report back.
Click to expand...
Click to collapse
I am using the correct code because that's how you run the command on Linux or Mac. I'm on a Mac.
The tool did not work for me.
I can't upload an image here
Micklo said:
I am using the correct code because that's how you run the command on Linux or Mac. I'm on a Mac.
The tool did not work for me.
I can't upload an image here
Click to expand...
Click to collapse
I know this is the correct command just I thought you used PowerShell from a Windows some times give errors.
The tool by Francesco Tescari works either through recovery or fastboot so you can try flashing a ROM.
But if for some reason the tool doesn't work your last chance it's either MiFlash tool or Qfil using a Windows machine.
SubwayChamp said:
I know this is the correct command just I thought you used PowerShell from a Windows some times give errors.
The tool by Francesco Tescari works either through recovery or fastboot so you can try flashing a ROM.
But if for some reason the tool doesn't work your last chance it's either MiFlash tool or Qfil using a Windows machine.
Click to expand...
Click to collapse
Thank you for your time and assistance, I eventually got a windows laptop to try it out, I got the Same Error.
I have tried MiFlash tool and I keep getting
Code:
error:"Flash bluetooth_a_error"
or
Code:
error:FAILED (remote: Flashing is not allowed in a Lock State)
I have tried XiaoMiTool V2 and it straight up didn't work.
Let me look up Qfil.
Micklo said:
Thank you for your time and assistance, I eventually got a windows laptop to try it out, I got the Same Error.
I have tried MiFlash tool and I keep getting
Code:
error:"Flash bluetooth_a_error"
or
Code:
error:FAILED (remote: Flashing is not allowed in a Lock State)
I have tried XiaoMiTool V2 and it straight up didn't work.
Let me look up Qfil.
Click to expand...
Click to collapse
It seems you are trying MiFlash tool in fastboot mode but while your device is locked fastboot mode won't work, you have to open the back cover and try test point method to send device to EDL (Emergency Download mode).
SubwayChamp said:
It seems you are trying MiFlash tool in fastboot mode but while your device is locked fastboot mode won't work, you have to open the back cover and try test point method to send device to EDL (Emergency Download mode).
Click to expand...
Click to collapse
Thank you very much, for still staying put.
I just did.
I downloaded the official Mi A2 fast boot ROM from https://bigota.d.miui.com/V11.0.14.....QDIMIXM_20200928.0000.00_10.0_62d0264480.tgz
I entered EDL mode following this guide: youtube.com/watch?v=34Zoevm-Wxc
I flashed it successfully but my phone is still stuck in the boot loop
Micklo said:
Thank you very much, for still staying put.
I just did.
I downloaded the official Mi A2 fast boot ROM from https://bigota.d.miui.com/V11.0.14.....QDIMIXM_20200928.0000.00_10.0_62d0264480.tgz
I entered EDL mode following this guide: youtube.com/watch?v=34Zoevm-Wxc
I flashed it successfully but my phone is still stuck in the boot loop
Click to expand...
Click to collapse
Use this link, there are other ways to unbrick it https://youtu.be/-B_YseC5kLk
Download from the official site linked in the video guide the recovery stock ROM, you can put it in some place in your PC and use the ADB sideload option through recovery to flash it or also you can use an USB OTG. Additionally try with other firmware, taking care to not downgrading it.
And if this doesn't work you should use other Windows version, some users report better results on Windows 7. And keep trying to switch slot.
Edit: before all try if this command work on fastboot mode: https://forum.xda-developers.com/showpost.php?p=75963934&postcount=25
Hey guys, I need help flashing my Google pixel 2. It was off for a couple of months and now when I am trying to start it, its not booting without putting it on charge and even then it only shows the battery icon then the google icon and restarts (So a bootloop). But when I press and hold the power button and volume down key, it goes in the fastboot mode ( the one where all device information is shown with an Android Logo) (Pic att).
If I select Download mode, it just shows operation denied and if I select recovery mode then it goes to bootloop again. Also as far as I remember when I last used the phone, the usb debugging was turned off so please suggest what to do from here.
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Alekos said:
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Click to expand...
Click to collapse
Hey thanks for the update man. I know I should have kept atleast oem unlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
mayankggrwl said:
Hey thanks for the update man. I know I should have nlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
Click to expand...
Click to collapse
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Alekos said:
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Click to expand...
Click to collapse
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
mayankggrwl said:
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
Click to expand...
Click to collapse
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Alekos said:
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Click to expand...
Click to collapse
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
mayankggrwl said:
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
Click to expand...
Click to collapse
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how the op in that thread above fixed his Pixel 2 with Skipsoft tool. His Device state said Locked in his screenshot on his post.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
edit--try these commands
fastboot erase system
fastboot erase data
fastboot erase cache
Alekos said:
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how those users in the thread flashed the bootloader image since I didn't think you could if the device state is locked, but worth a try.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
Click to expand...
Click to collapse
Okay great !! Thanks for these. Ill go through that thread and will see if any of the listed methods work. Will also try that software. In a rush so will try these later on and then ill update you.