Database Users

I'm stumped

I just got the NS, coming from the Vibrant. I installed the sdk and drivers. Adb see's my device because I get a serial # when I "adb devices" but when I go to fastboot oem unlock I get "waiting on device".

Do you have the phone in fastboot mode? Turn phone off hold volume up and power on...
Sent from my Nexus S using XDA App

make sure you have the fastboot file in your tools directory and that you are in the tools directory while trying to give the command. that is all I know to try.

I do have a fastboot file in the tools and I do have the phone in fastboot mode. Could the "path" have anything to do with it? For some reason I didnt have a path file under variables so I just created one. I'm assuming since I get a serial # that the drivers and path are correct.

Yeah not sure since it recognized device...
Sent from my Nexus S using XDA App

debug mode?

I'm on windows 7, not sure if that has anything to do with it or not. For the life of me I cant figure out what is going on. I've used adb extensively only g1, never needed it on my vibrant but it has something to do with the drivers I think.

I'm in debug mode

did you update your SDK?
and is your enviorment variable PATH along the lines of
C:\...\...\AndroidSDK\platform-tools
Click to expand...
Click to collapse

If you think you may be having trouble with your path, just cd to the folder where you have fastboot and try it there.
EDIT: I just ran into the same problem when trying to flash the cm7 boot image with ext4 hack. I had booted into bootloader using quick boot. I rebooted, powered off, and powered on with volume up button and everything worked fine. Not sure why this happened but I got the same "waiting" issue you had.

I got it to work. I uninstalled the drivers, put the device in download mode then plugged it in THEN installed the drivers. All is well, root, superuser and 2.3.1. Thanks to everyone who posted to help out.

If your phone is in fastboot mode, you will NOT get your serial number when you do a "adb devices".
So there you go, you're not in fastboot mode.
Turn the phone off.
HOLD volume up and then HOLD power.
You'll get to the bootloader. THAT is fastboot mode.
Now type "fastboot devices" and you'll see your serial number come up, then you can do "fastboot oem unlock".
FYI: adb command ONLY works when your phone is on and booted up OR in recovery.
fastboot command ONLY works in Bootloader.

fastboot mode adb

I downloaded minimal adb and fastboot from another thread
I had to disable "enforce driver signature" to install drivers for the device. Now I have an item in my device manager called "Samsung Android Phone" with "Android ADB interface"
I have tried command "adb devices" and it recognises my device
When I try "fastboot devices" nothing happens.
Maybe I don't know how to put the device into fastboot, but i thought all i needed to do was press and hold : power vol+ vol- and the device would reboot into fastboot.
Ultimately I am trying to unlock the bootloader and root, but the toolkit I am using get stuck as "waiting for device"
Any help would be appreciated

Tjisana said:
I downloaded minimal adb and fastboot from another thread
I had to disable "enforce driver signature" to install drivers for the device. Now I have an item in my device manager called "Samsung Android Phone" with "Android ADB interface"
I have tried command "adb devices" and it recognises my device
When I try "fastboot devices" nothing happens.
Maybe I don't know how to put the device into fastboot, but i thought all i needed to do was press and hold : power vol+ vol- and the device would reboot into fastboot.
Ultimately I am trying to unlock the bootloader and root, but the toolkit I am using get stuck as "waiting for device"
Any help would be appreciated
Click to expand...
Click to collapse
You probably did this but just to check:
1. Start cmd.
2. Navigate to your adb/fastboot folder.
3. Check if USB debugging is enabled.
4. Type "adb reboot bootloader" in the cmd window.
5. Type "fastboot devices".
6. Type "fastboot oem unlock" (THIS WILL WIPE ALL YOUR DATA, data+internal storage).
7. Type "fastboot flash recovery /path/to/recovery.img".
8. Navigate to recovery option in the bootloader. And boot into recovery by pressing the power button.
9. Flash the latest supersu and wipe cache and dalvik cache.
10. Reboot.
11. Profit.
If it doesnt work at the step "adb reboot booloader" or "fastboot devices" you prabably are having a driver issue.
Sent from my Galaxy Nexus using XDA Premium HD app

please help with fastboot/bootloader mode
mrgnex said:
You probably did this but just to check:
1. Start cmd.
2. Navigate to your adb/fastboot folder.
3. Check if USB debugging is enabled.
4. Type "adb reboot bootloader" in the cmd window.
5. Type "fastboot devices".
6. Type "fastboot oem unlock" (THIS WILL WIPE ALL YOUR DATA, data+internal storage).
7. Type "fastboot flash recovery /path/to/recovery.img".
8. Navigate to recovery option in the bootloader. And boot into recovery by pressing the power button.
9. Flash the latest supersu and wipe cache and dalvik cache.
10. Reboot.
Click to expand...
Click to collapse
I tried this, but all my device does at step 4 is a normal reboot. I am able to fully use adb without any issues...
My device is a Titan Allwinner A20 Softwiner sun7i Tablet...
Does this mean that it does not have a fastboot/bootloader mode?
Thanks for your help...

I only know this for the Nexus 10. Maybe look up the thread for your device and see whats there. Or use google
Sent from my Galaxy Nexus using xda app-developers app

silentarts said:
I tried this, but all my device does at step 4 is a normal reboot. I am able to fully use adb without any issues...
My device is a Titan Allwinner A20 Softwiner sun7i Tablet...
Does this mean that it does not have a fastboot/bootloader mode?
Thanks for your help...
Click to expand...
Click to collapse
Hi,
This forum is dedicated to Nexus 10 only, I don't believe that we can be of wide help for you .
The fastboot commands only work for Nexus devices, so as you don't own one and can't even get boot loader mode, then I'm sorry but here is not the place that you may seek advice.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1

True this isn't the place for the question, and the answer is you probably do not have a bootloader that is capable of interacting with the fastboot binary.
However fastboot is not only for nexus devices, virtually all HTC android devices are able to use fastboot, same with many Motorola, Sony and lg devices.
But again, more than likely your device will not work with fastboot
Best of luck!
Sent from my Nexus 7 using XDA Premium 4 mobile app

[SOLVED] Z1 not showing up in Linux ADB devices

hi,
trying to flash the breadcrust recovery using my linux pc, but the Z1 doesn't appear in the list of devices when running adb devices. Image attached. Normally I would get a request to accept the RSA key for a trusted pc when enabling usb debug. But I don't get this option.
- Adb tools are loaded and working on my linux laptop
- My nexus 7 responds to ADB devices and shows up ok
- tried on wifes windows laptop with adb/sdk tools loaded and no joy there too
- i have developer USB debug options enabled, i've tripple checked this
could it be the cable? I'm using the one which came with the phone, so that should be ok?!!
cheers
SOLUTION - I ran this One Plus Two script modified with the Z1 device ID and now I can see my device in adb devices and interact with it. I get the SHA screen to allow access and can run commands from linux terminal. YAY!
See the attachments for script.

I think it´s a driver fault. Did u install them in windows?

im using linux, i dont get any rsa pop up confirmation either!

EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
and that was the reason, why i installed windows last night. as long you dont get rsa pop up, the device will not listed (i think so)

EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
But u said, that u tried ur wifes Windows notebook. Did u install the drivers there?

ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.

MKKLR21 said:
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
Click to expand...
Click to collapse
Good tip - I'll give it a go.
My nexus 7 works as expected on all PCs and laptops Linux/windows so it must be the phone
Sent from my Nexus 7 using Tapatalk

Maybe sudo or check this:
http://1.bp.blogspot.com/-rDdBnJTh870/U-hxVzxMf3I/AAAAAAAAKwQ/WrZkaMjaReo/s1600/Unlock-Bootloader-linux-terminal-xperia-z.png[img/]
Source: [url]http://linuxwelt.blogspot.de/2014/08/cyanogenmod-unter-linux-installieren.html[/url]

ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader, but the device doesn't boot into fastboot, just reboots as normal!
I could also hold down up/down volume buttons and get into the bootloader, but again the device isn't picked by any fastboot oem checks for unlocking!!
arrrgh!!!

You'll have to add -i switch followed by the device ID to your fastboot command. I don't have it at hand, so just read the TWRP thread.

ok! Some progress...ish.
running "adb reboot bootloader"command in windows worked when I switched Cyanogen recovery updates off in developer options. The Z1 reboots into bootloader.
Running "fastboot -i 0x2b4c oem get-device-info" returns nothing just "....."
So I tried "fastboot -i 0x2b4c oem unlock" an error returns cannot unlock use command "fastboot -i 0x2b4c oem unlock-go" which works. The phone wipes data and reboots back into OS.
I re-enable the developer options and adb debug. and reboot into bootloader
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
weird!

Your commands are simply wrong, thats why they don´t work.
It is:
fastboot -i 0x2b4c oem device-info
fastboot -i 0x2b4c oem unlock-go
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
Click to expand...
Click to collapse
Flashing does NOT work on the international version, you have to boot into it directly from fastboot.
fastboot -i 0x2b4c boot z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
Should be correct instead of the flash command.

EggZenBeanz said:
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader...
...
Click to expand...
Click to collapse
What made the change? I was able to see the RSA screen only once, but after device restored to defaults I can't get it back. same drivers installed, and it appears in the device manager.

I honestly don't know, it just worked after many attempts. I read somewhere about USB 3 ports with Linux so might be the same for windows?
Sent from my Z1 using Tapatalk

It's an USB 3.0 issue. Plug the phone into an USB 2.0 port, or an USB 2.0 hub plugged into an USB 3.0 port and it will magically start working. God knows why this is the case...
Ironically, fastboot works fine even on USB 3.0...

For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?

Planet X said:
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Click to expand...
Click to collapse
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.

MrColdbird said:
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
Click to expand...
Click to collapse
Okay, I have found out that it is impossible to boot from TWRP as log as the bootloader is locked. It just took me 2 hours to setup my phone again after unlock.

Have a look at this thread, I am going to give it a try later.
http://forum.xda-developers.com/showthread.php?t=2408802

This did the trick on Linux (Ubuntu):
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in
- run on terminal "adb kill-server" and "adb start-server"
And run the fastboot commands with "sudo".

Stuck in Bootloop

US996 Unlocked, stock rom. I was in XDA Forums and saw there were app updates, one being Play Store. I updated. When I tried to get into Play Store, the message "this version of play store is incompatible with your device, go to settings and disable app update (or something like that). I tried but the app was not listed in settings. I tried to reboot and now the phone bootloops. All I can get is the warning that the software cannot be checked for corruption and then a quick display of the LG logo, then screen off, and then LG logo again and then warning screen, etc. If I try to reboot into recovery I get the Factory data reset screens and I answer both "yes" and the phone goes into adb mode.. From adb mode I can fastboot reboot, which puts me back into the above loop, or fastboot bootloader, which merely returns me to the adb screen. What can I do now?

Maybe try relocking the bootloader. I am pretty sure (someone correct me if I am wrong) that that pop-up of the "cannot check for corruption" usually only shows when the bootloader is unlocked.

XP_1 said:
Maybe try relocking the bootloader. I am pretty sure (someone correct me if I am wrong) that that pop-up of the "cannot check for corruption" usually only shows when the bootloader is unlocked.
Click to expand...
Click to collapse
Is that even possible? Don't know how to do it.

PhoneBull said:
Is that even possible? Don't know how to do it.
Click to expand...
Click to collapse
Try entering
Code:
fastboot oem device-info
into Fastboot on your computer to see if it says it is unlocked when in fastboot mode.

XP_1 said:
Try entering
Code:
fastboot oem device-info
into Fastboot on your computer to see if it says it is unlocked when in fastboot mode.
Click to expand...
Click to collapse
I get "FAILED (remote: unknown command)"

Do you have fastboot installed on your computer? (Something you would have had to have intentionally installed) If not google Minimal Fastboot /ADB and install it, enter the supposed ADB screen you are talking about and see if it makes contact with your phone.

XP_1 said:
Do you have fastboot installed on your computer? (Something you would have had to have intentionally installed) If not google Minimal Fastboot /ADB and install it, enter the supposed ADB screen you are talking about and see if it makes contact with your phone.
Click to expand...
Click to collapse
I have the fastboot on the PC that I used to unlock the bootloader.. I enter fastboot on the PC via the administrative command prompt. With the phone in the fastboot mode, I type "fastboot devices" on the PC and get a proper response (LGUS996ab**** fastboot). If I enter ""fastboot reboot" I get the bootloop. If I enter "fastboot bootloader" I wind up in Fastboot Mode on the phone again. I was hoping there was a "fastboot recovery" command but there doesn't seem to be. I don't know what to do next. I am not all that familiar with what can be done from fastboot. My only experience with it was when I unlocked the phone. I am desperate!

Okay, so if you do not have TWRP installed on your phone, then I don't know if you can save your data. You can try to
Code:
fastboot erase cache
and see if it helps, or if not and just reset the device fastboot oem lock I think. Maybe ask around in the unlocking help threads or perhaps someone with more knowledge will chime in. If none of this works, then there are some instructions on how to get your phone back to stock in the News and Guides section.
EDIT: Maybe try the power+volume down. It may work? I have tried it and never got it to successfully work. But you can try it.

XP_1 said:
Okay, so if you do not have TWRP installed on your phone, then I don't know if you can save your data. You can try to
Code:
fastboot erase cache
and see if it helps, or if not and just reset the device fastboot oem lock I think. Maybe ask around in the unlocking help threads or perhaps someone with more knowledge will chime in. If none of this works, then there are some instructions on how to get your phone back to stock in the News and Guides section.
Click to expand...
Click to collapse
Thanks for your help. I DO have TWRP installed and have used it often for backups. But now the only way I know to TRY to get to it is by the power/vol down until LG logo, then release/repress power button sequence but this just gets me into fastboot mode. II have some recent backups saved on my micro SD card - is there any way to flash one of them through fastboot if I load one onto the PC?

Yeah. My bad. Okay, so how I get into TWRP is through the EasyRecowvery.
Go ahead and download it from Git-Hub (1.3b3).
Now extract it and run the cmd program. Enter 5. which is extras and stuff and then enter 5 again in the sub menu which will let you boot into recovery. When you are in recovery, and plugged into your computer, you should be able to either flash or drag and drop like a flash drive on the the phone. Hope that helps a little bit.

XP_1 said:
Yeah. My bad. Okay, so how I get into TWRP is through the EasyRecowvery.
Go ahead and download it from Git-Hub (1.3b3).
Now extract it and run the cmd program. Enter 5. which is extras and stuff and then enter 5 again in the sub menu which will let you boot into recovery. When you are in recovery, and plugged into your computer, you should be able to either flash or drag and drop like a flash drive on the the phone. Hope that helps a little bit.
Click to expand...
Click to collapse
I don't have T-Mobile. I have Verizon Wireless on the US996. Will that work?

PhoneBull said:
I don't have T-Mobile. I have Verizon Wireless on the US996. Will that work?
Click to expand...
Click to collapse
Since you are only rebooting into recovery and not flashing anything it might. If not, it will just fail and not harm anything. Last thing to try is the
Code:
adb reboot recovery
which is the only thing I can think of and I think you already tried it. Otherwise you will need to just go stock.

A1 stuck in bootloop

Let me know if this post belongs somewhere else.
My Mi A1 is stuck in a bootloop as a result of trying to install magisk 14.4. At the moment I can boot it into fastboot mode, but not into recovery mode. In fastboot I can execute the command
fastboot devices
that returns the hex number followed by "fastboot." However, it does not respond to any other fastboot commands, e.g.
fastboot reboot
fastboot oem device-info
I have been attempting to flash the stock rom without success as follows:
in win10 32-bit environment:
fastboot responds as above. I cannot install the MiFlash-2017-7-20 version. Windows complains. I conclude that version must be a w10 64-bit app, although it doesn't say so.
win10 64-bit
MiFlash-2017-7-20 installs and runs, but does not see the device. Apparently, the adb drivers are at fault. I have turned off signature enforcement and tried installing various versions of the adb drivers. The device manager shows them as installed, but reports that they cannot start.
Centos 7 linux
Adb drivers install. "Fastboot devices" reports correctly. All other fastboot commands fail, i.e. they hang. I tried installing the tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image using the linux shell script provided, but that just hung also.
Is this phone well and truly bricked at this point? Is there any other recovery available?

I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.

Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works

GalihBK said:
Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works
Click to expand...
Click to collapse
As he said, he can't execute fastboot commands so that isn't a option.

@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well

Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong

dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.

The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps

Edwin Hamal said:
I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.
Click to expand...
Click to collapse
1. I tried this method to boot into EDL with no luck. Is there any other way?
C:\Downloads\xiaomi mi a1 root>adb reboot edl
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
2. On my win10 32-bit installation I am able to run MiFlash-2017045. It reports the device. I attempted to flash this image:
tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794
It completed and reported "success" however it did so in only 7 seconds, so it must not actually have succeeded. In any case the phone still will not boot.
3. However, I distrust MiFlash 20170425 because it comes from an androidmtk.com site and the processor is Qualcomm, not Mediatek. So I attempted to install MiFlash2017-07-20. However, that program will not install on my win10 32-bit installation. There is a Windows msg saying it cannot be installed, but does not give a reason. I suspect it is a 64-bit program. So, I installed MiFlash2017-7-20 in a win 10 64-bit installation. The program does run, but it does not see the device. I suspect that the adb drivers do not install correctly. I did turn off signature enforcement and the drivers appear to install, but the device manager reports that the drive cannot start.
The tissot images include bourne shell scripts to install, so I installed the adb drivers on my Centos box. Fastboot reports the device, but just as in win10 no other fastboot commands work. So, even though I did try to execute the install_all.sh script, it just hung on the first "fastboot getvar product" command.
So, I do not have a way to flash the stock rom.

_mysiak_ said:
@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well
Click to expand...
Click to collapse
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.

dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Use fastboot commands manually. Mi flash tool is very buggy. Many time it doesn't work.

_mysiak_ said:
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.
Click to expand...
Click to collapse
Did the command:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
"Missmatching image and device"
So this is a little interesting. However, I don't think that the image is actually the wrong one, but that the script cannot get the device info since both "fastboot getvar product" and "fastboot oem device-info" fail on a timeout.

zazzy24 said:
The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps
Click to expand...
Click to collapse
When I do that it just keeps going back to the "no command" screen. I think the recovery image is either damaged or gone.

yuoip said:
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.
Click to expand...
Click to collapse
1. & 2. It sounds like you don't have installed fastboot drivers (install them manually via device manager) or phone isn't connected in fastboot mode (make sure there is a picture with fastboot written on the phone).
3. this IS the recovery mode, just press power + volume up again to show the menu
4. you won't see ADB devices in fastboot or recovery mode, unless you enable ADB sideload from recovery

Device Manager shows:
Android Phone

yuoip said:
Device Manager shows:
Android Phone
Click to expand...
Click to collapse
Wrong drivers then, it should say Android bootloader interface. Reinstall them correctly.

1. I did the manual install, but I don't see anything labeled "fastboot driver."
Device manager now reports:
Android Phone
Android ADB Interface
Android Bootloader Interface
Android Bootloader Interface
Android Composite ADB Interface
However, all these entries have a warning symbol on them. The Device status for each is:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Is one of these the fastboot driver? Apparently not, since the behavior of the fastboot command hasn't changed.
When I try using the fastboot command the A1 shows "Fastboot" with the rabbit character and the sick robot.
I should mention that in the Centos environment I have installed the android-tools package, which include adb and fastboot drivers and tools. The behavior of the fastboot command there is the same.
So, this leads me to believe that the problem is the A1, not the windows or linux environment, but I don't know enough to know for sure. Also, I would assume that if the fastboot drivers were not installed, the command "fastboot devices" would fail, but it doesn't.
3. At the "no command screen" if I do press and hold the power button and then the vol. up button it boots right back into the "no command" screen. There is no menu.
4. With no recovery menu I can't set any options.

Uninstall/remove everything with android name in it, disconnect phone, reconnect phone in fastboot mode. Make sure that there is only one item under Android Phone - Android Bootloader Interface. You should not see 4 devices - do you have Android emulator running or anything else connected?
When in recovery, do not hold power + volume up, just press it briefly. Sometimes it takes few tries to show the menu, but I can assure you that it's there.

Yes! You're right. The recovery menu is indeed there. I didn't know that it had to be a short press to bring it up. Thanks.
Device manager now shows only one "Android Bootloader Interface" entry. I am not running any emulator.
So now what do I do? Do I need to flash the tissot... image? The fastboot command still behaves as before.

Quick Google search suggests to avoid using USB 3.0 ports. So..maybe try another ports on your PC..?