Related
I see that there are other threads for this and I have read through them but they don't seem to be helping. I was in the middle of using the Nexus Toolkit to install a Rom when the program temporarily booted TWRP after it removed old os and then it stopped working and I went to reboot from the temporary boot when it told me I had no OS. Because I do not have a ROM my computer does not detect ADB status so I cannot seem to get anytging on the device. I also can seem to get the sideload to work. I am not quite sure how to use the CMD for this and I have used other threads suggestions like starting cmd in the folder that has the rom i want to flash and the typing the adb commands but it doesn't seem to work. Can someone help please?
STOP USING TOOLKITS!
If you can't get adb to work, I suggest following this thread to get it working: http://forum.xda-developers.com/showthread.php?t=2588979
Thank you, but my adb drivers are installed. my device can only enter fastboot and recovery so even now with that tool I dont know how to install an os back on my device.
Just flash the images from fastboot. There are a thousand posts on how to do this here.
"fastboot flash system system.img"
Hey guys,
I seriously need help with my M4. I think I might have soft-bricked it :crying:
Here's what I have done:
I unlocked it and installed TWRP 2.7.1.1 to install a custom ROM. The thing is, I didn't know it was branded (as I found out too late, the CID is VODAP102), so the ROM wouldn't install. Now, I tried to change the CID to a SuperCID (11111111) but ran out of luck. So I thought I'd simply revert to Stock. So far, so good. Yesterday I got an update notification for a Sense 6.0 update but it wouldn't install. So I successfully flashed the stock recovery but the installation of the update halted (red exclamation mark). I then went back to flashing the boot.img too (from an UL rom, unfortunately) and relocked the bootloader. Still the same error. Then I read I should factory reset in the bootloader. So I did and the result was I got stuck on the bootscreen!! So I unlocked it again, re-installed the TWRP recovery to at least get back to the backup I made before, but the thing is: My storage got wiped and TWRP won't mount OTG-USB!!! I guess it's that some partitions/files are now messed up. Now I cannot do anything anymore. I don't have the stock ROM as a flashable zip, only the TWRP backup.
Here's what still works:
Fastboot & Recovery
What doesn't work:
ADB (because phone won't boot), ExtSDcard (naturally!) and flashing ROMs via fastboot because I need one that matches that damn Vodafone CID
I think if someone could upload their Vodafone Germany M4 ROM as a zip or exe, I could manage it. If someone has it, PLEASE give it to me!
If someone has any other idea how to get this phone to work, or at least get TWRP to mount the USB-stick, please HELP!!! I'm totally at a loss :crying:
You can ADP from TWRP so all is not lost
apjashley said:
You can ADP from TWRP so all is not lost
Click to expand...
Click to collapse
Well, if I start ADB sideload in TWRP, it says it is starting but then nothing happens. Or does it take more than 5 minutes? Because cmd says no devices found :/
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
apjashley said:
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
Click to expand...
Click to collapse
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
kumpelfred said:
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
Click to expand...
Click to collapse
What does your Windows device manager show when you're in TWRP but not sideload mode?
I've been wrong before but I believe from sideload mode "adb push firmware.zip /sdcard/" should work as normal.
Hi, thanks for your reply.
The device manager lists it as HTC One Mini but with a yellow question mark. When I plug it in, it recognizes it and installs all the drivers with the exception of the MTP driver, and it won't let me manually install it. In fastboot, it is listed as "MyHTC".
When I go into adb sideload mode in TWRP it gets stuck on telling me it starts the service but nothing happens. "adb devices" remains empty in the cmd console.
As I said, I DO have a backup, only I cannot restore it as TWRP is unable to mount the USB-OTG. I simply cannot check the box (all other partitions data, system etc. work)! I tried 3 different sticks and TWRP versions 2.6.3, 2.7.1.0 & 2.7.1.1. On a friend's M7 TWRP loads that stick in a few seconds. ADB is not working as I said, otherwise I could simply push the file to the internal SD and see if I can restore it from there :/ I think it may have something to do with TWRP not being able to fix permissions, too (it tells me to boot the system once after factory reset, which I cannot do of course!) but I'm not sure....
What I have also tried is setting back the phone (relocked, stock recovery, cache erased) via rebootRUU and a Vodafone DE firmware zip but it tells me "read zipped android info fail" and aborts. Probably because I'm on a higher hboot version than the one in the firmware zip and I cannot go S-OFF without ADB working -.-
I'm struggling with this for 3 days now... Is there nothing I can do to get it booted into anything???
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
kumpelfred said:
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
Click to expand...
Click to collapse
could u share that drivers pls. i have same problem ((
[email protected] said:
could u share that drivers pls. i have same problem ((
Click to expand...
Click to collapse
Hey, I was wrong about the HTC drivers, this was not the issue. The issue was that the latest TWRP recovery (2.7.1.1) did not work in adb mode for whatever reasons. The solution was not older drivers (as they update anyway) but to install an older TWRP version (2.6.3.0 worked for me).
This is only when you cannot boot into your system and have to adb push something to your sdcard. If the phone is not recognized when connected with a booted system running, the only fix is to remove drivers and programs that could interfere (Samsung Kies, HTC Sync, e.g.), reboot, reinstall the drivers, plug your phone into a different USB port and just hope 'adb devices' gets a result, otherwise try all over again.
Hi there,
I had my HTC One S rooted, S-OFF, unlocked, with SuperCID running MaximusHD and I wanted to reinstall a fresh version of it to give it to my father. However, I went too fast and wiped absolutely everything. So now, I'm stuck on the startup screen (with the warning message in red) with no OS and I can't reboot into recovery (wether using hard keys or fastboot) as I can't switch off my phone. What do I need to do in this case? It's plugged to my computer but, of course, as it's stuck on the startup screen, it doesn't recognize it.
Thanks in advance.
Small update: I managed to turn it off but I still can't get it recognized by my computer. I will try to uninstall all drivers for now, I'll get back here as soon as I have time to do that. Hopefully someone will have an idea by then
Flash the recovery from my signature. It will enable USB mounting in recovery mode for hboot 2.16. Just be sure to flash the dm version.
The thing is I can't flash anything since I can't transfer anything to my phone.
Right now, what I've done is reinstalling drivers properly (I get the mention "FASTBOOT USB" in bootloader) but I can't do anything with One S toolkit v4 for example. I managed to get adb commands working and tried to push Maximus ROM through ADB but I got a protocol failure message
Edit: oh wait, it's been transferred anyway.
Do you still have the folder from the install package archive? If yes, open the cmd console and go to the package folder. If it's like in my case "D:\Root" you got to type
Code:
d:
and press enter. Then you got to type
Code:
cd
hit space, repeat pressing tab until it says
Code:
cd Root
and hit enter, again. Then plug in your phone, put it into fastboot usb mode and type
Code:
fastboot devices
into the cmd console and hit enter, once more. If everything is working you should get a list with attached devices which shows your phone.
If your phone isn't listed try another usb port or another cable or if nothing else works another computer.
Next download the TWRP version from my signature, rename it to recovery.img an put it into the install package folder. Then enter
Code:
fastboot flash recovery recovery.img
into the cmd console and press enter for one last time.
TWRP 2.8.0.1-dm should be installed now and you should be able to mount your phone as mtp in recovery mode.
It's all good now! I could get ADB/Fastboot working and could reinstall a fresh Maximus on my One S. I can now safely give it to my father and enjoy my new Z3 Compact. I'll probably install your TWRP anyway though.
Thanks for your help!
Your welcome. Actually it's not my work so it's not "my" TWRP. I've found some mistakes in my last answer cause I'm in a little hurry right now. Going to correct it later for the case that someone else has a similiar problem...
Edit: My previous answer is corrected now.
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
emmpii said:
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
Click to expand...
Click to collapse
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
sdembiske said:
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
Click to expand...
Click to collapse
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
ive managed to get the latest twrp on.. now I cant seem to adb sideload the rom nor does it show via otg.. ADB sideload disconnects and says invalid zip file
emmpii said:
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
Click to expand...
Click to collapse
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
sdembiske said:
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
Click to expand...
Click to collapse
shows up in device manager as android usb device, Still not showing on adb
I managed to get the device to finally track on with adb. It tracks fine now. However I can't seem to flash a rom on regardless of whether its OTG or sideload...
emmpii said:
shows up in device manager as android usb device, Still not showing on adb
Click to expand...
Click to collapse
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
sdembiske said:
Try this command: fastboot boot recovery.img or fastboot boot twrp.img
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
Click to expand...
Click to collapse
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
emmpii said:
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
Click to expand...
Click to collapse
The problem with CM roms is they're not really being updated anymore - just one of the problems I have with a lot of custom roms besides the bugs, etc., etc.
If you're hell bent on a custom rom, I would check out this one: [ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1 at https://forum.xda-developers.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103
Lineage is the new go-to from CM. I personally would go back to stock first, however, to ensure everything is restored properly before installing it.
It's being updated regularly currently.
I just had a old CM rom downloaded from before hence I went to that lol. I'm trying lineage for now but I've also downloads the stock ROM. Whatever will keep the phone going
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
jwoegerbauer said:
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
Click to expand...
Click to collapse
As it turns out, I had already stumbled upon your your "ADB-FASTBOOT-Installer" during a trip down one of the many rabbit holes trying to get this tablet working again.
adb devices returns:
List of devices attached0123456789ABCDEF recovery
adb reboot restarts the tablet, which I assume means the ASUS tablet driver is working.
I can't seem to do anything else with adb, however, such as push a new TWRP version, etc. This may be a key point, as it seems likely the version I have of TWRP may be too old to support upgrade using something like Chrombi-KK.
Is this a likely theory?
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
NotTheLips said:
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
Click to expand...
Click to collapse
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
jwoegerbauer said:
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
Click to expand...
Click to collapse
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
[email protected] said:
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
Click to expand...
Click to collapse
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
NotTheLips said:
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
Click to expand...
Click to collapse
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
NotTheLips said:
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
Click to expand...
Click to collapse
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
jwoegerbauer said:
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
Click to expand...
Click to collapse
As I mentioned before, "2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine."
[email protected] said:
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
Click to expand...
Click to collapse
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
NotTheLips said:
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
Click to expand...
Click to collapse
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
[email protected] said:
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
Click to expand...
Click to collapse
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
the problem is your pc does not have adb and fastboot properly installed
try this one https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
also, use this official driver https://www.asus.com/SupportOnly/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
if your pc is 64 bit use win764bit version
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
This "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in Fastboot mode, so you can easily have permission to it in ADB but not in Fastboot.
Each manufacturer implements Fastboot differently. So, if not already done yet, download and install the suitable "Android USB Driver" provided by ASUS. Then Fastboot should work.
BTW: Your device actually stucks in recovery mode.
Is OEM Unlock got enabled in Android settings? If not, Fastboot never will work.