Recently just bricked my zenfone 5 and have been trying to flash it ever since then. I installed the Android Intel driver and all the necessary files for the flash. But when I type the commands in command prompt, it just shows <waiting for device>. I've been searching the whole internet just to find the answer and still can't :crying:
Update the Intel USB Driver
Related
As it says. I've used this cable to unlock/root my HTC M9, and the Win10 machine I have shows the Shield's storage when connected. However, neither ADB nor Fastboot are connecting. Error message says 'Error: device not found" or something like that. What am I doing wrong?
Disregard. Had to install the device drivers for Win10 from Nvidia.
adb reboot bootloader works but not fastboot oem unlock
I can reboot bootloader and get to the fastboot menu, but the fastboot oem unlock command does nothing, the command window simply says "waiting for device".
When I go to device manager on my PC to change to the Nvidia drivers, windows says I already have the best driver installed.
Any ideas what to do to get this working properly? Is the "hardware method" better somehow?
Thanks.
BillTheCat said:
As it says. I've used this cable to unlock/root my HTC M9, and the Win10 machine I have shows the Shield's storage when connected. However, neither ADB nor Fastboot are connecting. Error message says 'Error: device not found" or something like that. What am I doing wrong?
Click to expand...
Click to collapse
Hello. I bought this tablet and I`m trying to root it. My problem is that in fast boot after entering an adb command I get "error: device '(null)' not found". After a tablet reboot adb reboot bootloader goes into bootloader but again I got same error, tried adb devices (blank return), adb reboot (null error). USB debugging and OEM Unlock are enabled, I have tried lenovo usb drivers, google usb drivers but I`m getting same errors in fastboot. In windows 10 device manager device is recognised.
And a question about rooting, should I try Dashi or Genius Root ? My last android device was a HTC Desire S many many years ago and went with apple devices after. I`m a little rust with new android root methods.
Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!
Hi all does anyone know the reason why the 2nd gen phone doesn't connect to fastboot command ? It connects to adb command but just hangs saying waiting for device when prompted with fastboot command, I have all Nokia drivers installed any ideas thanks
OK found out that operating system needs to be x64 not x32 my bad
Hello. My Asus Zenfone Max Pro M1 ZB602KL (3GB/32GB version) just arrived, and one of the first things I tried to do with is is enabling GCam. I installed the drivers correctly, I enabled USB Debugging, I switched it to MTP over USB and tried to do it. ADB works fine, I even wrote some commands, but when I try to run "fastboot oem enable_camera_hal3 true" or "fastboot devices" (after rebooting it to fastboot), I get this error message on my computer: FAILED (command write failed (No such file or directory)). Also, my "fastboot screen" gets replaced by an error message that says "Press Any key to Shutdown". I have tried every single video, followed each pass, installed every driver I found, but the result is always the same. My phone is not rooted, the bootloader isn't unlocked and it is running august 1 security patch, Build No. : 15.2016.1808.326. Thanks.
adb version
what version of adb are you using?
type "adb version" to find out.
For e.g. the latest version of the "sdk platform tools" on the android website has adb version 1.0.40
pankym24 said:
what version of adb are you using?
type "adb version" to find out.
For e.g. the latest version of the "sdk platform tools" on the android website has adb version 1.0.40
Click to expand...
Click to collapse
I guess it was my PC, I just tried the exact same way I did it before on another computer and I got it the first time.