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!
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 have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
I believe part of the instructions are to install the Platform Tools, which should include drivers. Try running the SDK Manager and updating or installing the drivers again. Also ensure you have USB Debugging ON in your Developer settings and OEM Unlocking enabled. Lastly, tap the notification in your shade about the USB connection (I think it defaults to Charging Only) and change it to various modes. Mine seems to only work on PTP mode. When you run the adb devices command you will need to authorize the connection on the phone end the first time by clicking OK so make sure the screen is on and unlocked so you can see it.
Hope this helps.
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
u enable OEM Unlock under developer settings?
You enable USB debugging?
Me personally do not get any strings of data returned when im on fastboot
i open CMD, run ADB DEVICES, get message saying the port is opening, and then listing devices... which is empty
but i am able to flash anything i want using fastboot....
try this command and see if it works after that... fastboot reboot-bootloader
it should reboot bootloader for u.. thats a easy way to know its responding to u
Is the device showing properly in the Device Manager when it's connected to your system?
hEaTLoE said:
Is the device showing properly in the Device Manager when it's connected to your system?
Click to expand...
Click to collapse
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
peckaldee said:
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
Click to expand...
Click to collapse
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
fury683 said:
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
Click to expand...
Click to collapse
Yeah I tried every option. Nothing.
The instructions say the fastboot devices command should return my serial number and it does not.
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
chaco81 said:
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
Click to expand...
Click to collapse
I'm using sdk manager revision 24.4.1
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
I had the same issue ,it was down to when I plugged the phone into the PC for the first time,it installed the Google.USB driver ,but it didn't install the driver for the adb interface,I had to download it from Google and install it manually
I also had the same issue, I had an old Clockworkmod generic driver that I was using for my Samsung Galaxy S5 installed.
Go to Device manager (either type it in the start menu, or: right click This PC, click manage, and click device manager), plug in your unlocked Nexus 6P phone and watch for a new item to pop up. If it says android something, uninstall it. I had to uninstall 3 times, then reinstall the drivers from the SDK before it would work.
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
This worked. Now my commands in terminal are working correctly. thanks all for the help
Got A device to pop up under the command adb devices, but nothing under fastboot devices. Any tips? Had to follow the skipsoft instructions to install adb/fastboot devices. Yes USB Debugging is on and the OEM unlocking is set to allow..
Christ I'm retarded. Sorry boys, thought my phone was in the bootloader when I was trying this command LOL
Same problem
peckaldee said:
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
Click to expand...
Click to collapse
I'm having the same problem. Did you ever figure out what was wrong?
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
Solved my problem as well. Thanks!
I am not being able to unlock my K4 Note no matter and I will have to admit it's so frustrating. I am not new to unlocking and modding party but i just cannot get to have this done!
I downgraded from S230 to s218 & now on s219. I am able to get adb to recognize my device but not fastboot. Thus I am unable to unlock bootloader!
When I type in " adb reboot bootloader" or click on the "unlock_recovery.bat" file provided, I get booted into a dark screen where "fastboot" is written at the bottom left & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
i have been seeking an answer to this since the last 3 days but am yet to find one
This is problem with the driver, I too had problem. Do enable usb debugging, connect to PC, it will ask permission in phone, give ok. Now a lenovo folder will appear on PC, click on usb driver installation, done.
Now try adb and fastboot device will detect.. Also i hope u enabled oem unlock in usb debugging
Hit Thanks if it helped!!!
Same problem
I am also facing the same problem
Please provide solution if you found one
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 finally managed to switch from (rooted) Nougat to Oreo (rooted) .
Now I'm facing an issue with fastboot command not working.
ADB works ("adb devices", "adb reboot..." commands are ok) but fastboot always fails.
The commad itself is ercognized by the system but it aways fails in executing the command ("waiting for the device...").
I've tried several ADB/Fastboot install methods, always the same result.
Is there something I am missing?
fastboot mode usually has nothing to do with the android flashed because its a mode triggered out from Any android.
however some days ago my PC suddenly stopped recognizing device ..
All I did changed port and cable! .. and it worked fine!
please try that (if you havent already )
YasuHamed said:
fastboot mode usually has nothing to do with the android flashed because its a mode triggered out from Any android.
however some days ago my PC suddenly stopped recognizing device ..
All I did changed port and cable! .. and it worked fine!
please try that (if you havent already )
Click to expand...
Click to collapse
Thanks for your seggestion but... ADB works, so cable and port are OK.
Anyway, I tested it the same to be sure :cyclops:
eresac said:
Thanks for your seggestion but... ADB works, so cable and port are OK.
Anyway, I tested it the same to be sure :cyclops:
Click to expand...
Click to collapse
can you reflash different android version and try? just making sure you don't have issues with device
Today I tried from another PC and fastboot is working, so it must be something related to the computer not to the phone.
eresac said:
Today I tried from another PC and fastboot is working, so it must be something related to the computer not to the phone.
Click to expand...
Click to collapse
Check the device manager on the pc if using Windows before anything else. It's likely the fastboot driver, select it press update and point it to the correct driver. It should be installed on the computer already so you can just choose the correct driver.
Just to share that the only way I found to get fastboot work is to install flashmode and fastboot drivers from the installer provided by flsahtool in the drivers folder.