Related
You can use the command "adb reboot-bootloader", I didn't see anyone else try this on here. Unfortunately, fastboot still doesn't recognize the device. I used the stock USB cable, I also tried doing it with my factory cable, but the device rebooted to a black screen and I got it recognized as "Qualcomm QH-USB QDloader"
epicfailol said:
You can use the command "adb reboot-bootloader", I didn't see anyone else try this on here. Unfortunately, fastboot still doesn't recognize the device. I used the stock USB cable, I also tried doing it with my factory cable, but the device rebooted to a black screen and I got it recognized as "Qualcomm QH-USB QDloader"
Click to expand...
Click to collapse
need use QPST (http://forum.xda-developers.com/showthread.php?t=2588608&page=5)
but this way not completed until the end of
I managed to send a command with fastboot under linux (Windows just didn't work, but in device manager I got it to show up as fastboot), did anyone else try this?
epicfailol said:
I managed to send a command with fastboot under linux (Windows just didn't work, but in device manager I got it to show up as fastboot), did anyone else try this?
Click to expand...
Click to collapse
Really? & just what command did you send using fastboot? Unless you have a magic kernel & bootloader, there is no fastboot access without passing the key. The way updates are performed on the KF HDX are fairly abnormal compared to other devices, which is why you see two kernel, stream writer & other such files & apps.
GSLEON3 said:
Really? & just what command did you send using fastboot? Unless you have a magic kernel & bootloader, there is no fastboot access without passing the key. The way updates are performed on the KF HDX are fairly abnormal compared to other devices, which is why you see two kernel, stream writer & other such files & apps.
Click to expand...
Click to collapse
I used getvar, and it worked fine (but most the of parameters don't), boot and idme don't work because it's locked, and oem unlock doesn't exist. But what your saying is that I shouldn't even be able to do any of this?
i look at the picture and the kindle is not hdx.
i've searching for fastboot cable on ebay but didn't found, the cable only work for kindle HD
so for there is no fix for bricked kindle fire hdx
You can turn HDX into fastboot mode by "adb reboot bootloader" if device is alive.
But you can not flash anything anyway - error "flash not allowed for locked hw".
Fastboot cable perfect fit to HDX too. But it turn device in Qloader for QPST.
epicfailol said:
You can use the command "adb reboot-bootloader", I didn't see anyone else try this on here. Unfortunately, fastboot still doesn't recognize the device. I used the stock USB cable, I also tried doing it with my factory cable, but the device rebooted to a black screen and I got it recognized as "Qualcomm QH-USB QDloader"
Click to expand...
Click to collapse
Try "fastboot -i 0x1949 yourcommandhere"
I'm trying to unlock the bootloader on my XT1622.
I can transfer files etc and backup when connected to PC and in Windows
I have installed the drivers and fastboot and adb and opened a cmd window in Admin mode in the directory where fastboot.exe and adb.exe are installed.
I have restarted the phone in fastboot mode (power up plus Vol Down) and connected by USB cable to my PC but when I type adb devices I get no information coming back.
Does anyone have any idea, please, where I may be going wrong?
Anyone able to help, please?
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.
actomox said:
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.
Click to expand...
Click to collapse
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?
Still no show
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
pastorbob62 said:
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?
Click to expand...
Click to collapse
actomox said:
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
Click to expand...
Click to collapse
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.
Still no joy
negusp said:
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.
Click to expand...
Click to collapse
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.
actomox said:
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.
Click to expand...
Click to collapse
Did an RSA key dialogue ever pop up when you plugged it into your PC?
If fastboot shows no devices when your phone is in fastboot mode (voldown+power hold), then something is seriously off. Have you tried multiple USB cables?
On your wife's PC did you make sure to install adb/fastboot and drivers: https://forum.xda-developers.com/showthread.php?t=2588979
And make sure to run the cmd shell as administrator/root? (right click cmd, click run as admin)
Will double check everything
Will double check all of those pointers over the weekend and report back. Thanks
Success at last
Went onto my wife's computer and deleted all that I could find relating to SDK and Motorola. Re-installed adb tools and the Motorola drivers and now adb devices return the details of the connected phone. Onto the next stage of unlocking the bootloader and then rooting. Thanks for the help.
I know I am probably the millionth person to say this, but I can't for the life of me get my device recognized in ADB when it's in Bootloader.
What I have tried so far:
- Activated OEM Unlock, USB debugging and set my computer to always be allowed for usb debugging
- Manually installed latest google usb drivers through device manager
- started up adb in cmd, made sure the device was recognized, rebooted in bootloader to check device list again
- Same thing, but with the drivers from the Mi A1 Tool)
The results:
- in Bootloader: Not recognized in ADB, but windows device manager shows "Android Bootloader Interface" as properly installed with google's driver 11.0.0.0.
- booted up: Recognized in ADB as " d59.... device" and in device manager as "ADB Interface"
This is not my first android rooting experience, but I have never had such problems installing drivers before. Is there anything special about the MI A1 I don't know? Anything I am forgetting maybe? All other Threads I found weren't helpful.
Thank you in advance for just taking the time to read until this point Any pointers even just links will be much appreciated!
Did you type 'su' after opening ADB/command prompt?
No I did not. Will try it out at home, but isn't that just for superuser meaning root access? The command to list devices should be "adb devices" not matter what mode the device is in, no?
Thank you for the tip!
Use "fastboot devices" "fastboot oem unlock".
Hi,
I am trying to unlock Google Camera using this guide. It needs me to use the fastboot mode in my ASUS Zenfone Max Pro M1. As far as I can see, I have followed the guide pretty well.
Enabled debugging mode on the phone
Downloaded the adb and fastboot files
Am using cmd with admin privileges
adb drivers are installed
checked connectivity with "adb devices" command and it is showing the serial number
However, none of the fastboot commands seems to be working for me.
As soon as I try to run the command from guide, mobile just goes dark with one line saying Press Any Key to shutdown. Also, if I try
Code:
fastboot devices
command at the CSC Fastboot Mode screen, it just shows
Code:
???????????? fastboot
and goes to the press any key to shutdown. When I try the command to enable the camera, it shows
Code:
fastboot oem enable_camera_hal3 true
...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
The build number is OPM1.WW_Phone-15.2016.1901.339-20190108.
Any help is greatly appreciated!
Regards,
pallups
The exact same happened with me. I tried everything but nothing worked, I even tried every single driver and ADB version out there. I only got it to work when I tried to do the same thing on another computer, and it was successful in the first try. Good luck, I hope you manage to get it working!
Use .\fastboot and remember to put whatever file in the same folder where fastboot files are located
farhanshaikh671 said:
Use .\fastboot and remember to put whatever file in the same folder where fastboot files are located
Click to expand...
Click to collapse
This has nothing to do with his problem, I had the same issues. It has to be a driver problem, because switching to another PC solved the issue.
VictorPLopes said:
This has nothing to do with his problem, I had the same issues. It has to be a driver problem, because switching to another PC solved the issue.
Click to expand...
Click to collapse
I agree. I'm using command prompt not PowerShell. So that shouldn't be an issue.
I don't have a second PC. Any idea on how to solve this on my existing one?
I also used CMD. You could try uninstalling every single android related driver, adb program, file, etc. If it doesn't work, probably, only another PC would do the trick. Also, try another USB ports, and make sure you are using the original USB cable that comes with the device.
If you uninstall everything, make sure you install "15 seconds ADB first", then, plug the device.
Go to your computer BIOS Setup and change the USB port to 2.0 and use the original USB cable.
Let me help you.
The problem is the driver.
Shut down your phone, and go to fastboot mode.
Connect to your PC.
Then, open device manager and see "other devices"
There must be an exclamation mark, update the driver and select manually (let me chose from your computer).
Select the fastboot driver, install.
Voila.
You now should be can use "adb devices" command on cmd or powershell.
Sorry for bad English
I found a workaround solution. Use a multi port USB hub regardless is USB 2.0 or 3.0, connect Android devices to USB hub and USB hub to PC. The problem shall solve regardless of how many times you run "fastboot devices"
pallups said:
Hi,
I am trying to unlock Google Camera using this guide. It needs me to use the fastboot mode in my ASUS Zenfone Max Pro M1. As far as I can see, I have followed the guide pretty well.
Enabled debugging mode on the phone
Downloaded the adb and fastboot files
Am using cmd with admin privileges
adb drivers are installed
checked connectivity with "adb devices" command and it is showing the serial number
However, none of the fastboot commands seems to be working for me.
As soon as I try to run the command from guide, mobile just goes dark with one line saying Press Any Key to shutdown. Also, if I try
Code:
fastboot devices
command at the CSC Fastboot Mode screen, it just shows
Code:
???????????? fastboot
and goes to the press any key to shutdown. When I try the command to enable the camera, it shows
Code:
fastboot oem enable_camera_hal3 true
...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
The build number is OPM1.WW_Phone-15.2016.1901.339-20190108.
Any help is greatly appreciated!
Click to expand...
Click to collapse
pallups said:
Hi,
I am trying to unlock Google Camera using this guide. It needs me to use the fastboot mode in my ASUS Zenfone Max Pro M1. As far as I can see, I have followed the guide pretty well.
Enabled debugging mode on the phone
Downloaded the adb and fastboot files
Am using cmd with admin privileges
adb drivers are installed
checked connectivity with "adb devices" command and it is showing the serial number
However, none of the fastboot commands seems to be working for me.
As soon as I try to run the command from guide, mobile just goes dark with one line saying Press Any Key to shutdown. Also, if I try
Code:
fastboot devices
command at the CSC Fastboot Mode screen, it just shows
Code:
???????????? fastboot
and goes to the press any key to shutdown. When I try the command to enable the camera, it shows
Code:
fastboot oem enable_camera_hal3 true
...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
The build number is OPM1.WW_Phone-15.2016.1901.339-20190108.
Any help is greatly appreciated!
Regards,
pallups
Click to expand...
Click to collapse
The exact same problem occuring with me... any fixes? Please tell me how to solve this
VictorPLopes said:
The exact same happened with me. I tried everything but nothing worked, I even tried every single driver and ADB version out there. I only got it to work when I tried to do the same thing on another computer, and it was successful in the first try. Good luck, I hope you manage to get it working!
Click to expand...
Click to collapse
I tried with everything for 2 days, nothing works. I faced the same issue, everything works, adb works, driver gets loaded, but "fastboot devices" shows "???????????? fastboot".
After applying this method, (using another PC), everything works within 1 minute.
Hope his help, who faced the same issue.
cychau said:
I found a workaround solution. Use a multi port USB hub regardless is USB 2.0 or 3.0, connect Android devices to USB hub and USB hub to PC. The problem shall solve regardless of how many times you run "fastboot devices"
Click to expand...
Click to collapse
Entirely different phone (Redmi Note 5 Pro) but this is the only solution I could find that worked for me. Thank you very much!
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
might be a long shot but i read somewhere else that a person had to type
fastboot -i 0x2e17 < zip/file here >
sorry ; all i know to try.
good luck
maybe @IronRoo can help.
I had the same issue but installed the driver from here and it worked.
https://essentialsupport1493251565....015490828-Windows-Drivers-for-Essential-Phone
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
Connect in fastboot mode and then restart phone with plugged in condition, see if it gives any driver notification.. if dosent then connect the pbone as media device it would show driver disk, you may install driver from there.
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
If non of the above work uninstall all phone drivers & or any other phone connection software that installs phone drivers also eg Samsung Kies/Connect then reinstall Essential drivers, though haven't read about conflicts in recent years ....(Also try different USB ports pref on direct to mother board, people have suggested in the past)