i got this error when unlock it
FAILED (remote: 'Command not supported in default implementation')
oem unlock enabled,im in Fastboot mode
(my english is super bad so i dont understand what it means)
try this... it's probably an adb driver issue, it was for me, when my phone was on it worked for adb but in bootloader mode the device manager on my pc showed an error on the usb device that was connected to the bootloader, so i updated that device driver to anotheer version by using the manual option when updating and then it worked
themrgoats said:
try this... it's probably an adb driver issue, it was for me, when my phone was on it worked for adb but in bootloader mode the device manager on my pc showed an error on the usb device that was connected to the bootloader, so i updated that device driver to anotheer version by using the manual option when updating and then it worked
Click to expand...
Click to collapse
i fixed it... not fastboot mode is bootloader mode i remember.
Related
I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....
I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....
adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.
I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
FAILED (command write failed (No such device or address))
Click to expand...
Click to collapse
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?
_Raziel666 said:
I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?
Click to expand...
Click to collapse
I'm assuming that since you were able to "successfully" unlock the bootloader that you can do this to check and see if your PC still recognizes your device. So, while you have you're Pixel C in fastboot and have it connected to your PC, open a command prompt and type the words fastboot devices and see if it returns your device serial number. Normally the command prompt will show that message when your device is not properly connected with the correct drivers installed. Also, if you have the correct drivers installed your ADB should work if you have enabled USB Debugging in developer options.
Sent from my Nexus 6 using XDA-Developers mobile app
Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.
_Raziel666 said:
Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.
Click to expand...
Click to collapse
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the very descriptive post. The thing is that I have already done all that, with the exception of using ADB, the pop-up never appeared and my Pixel C appears as unauthorized in adb devices.
I know for a fact that the bootloader is unlocked, because everything got wiped afterwards, and I also get the message saying that the bootloader is unlocked in every boot.
The thing is I cannot flash neither the developer preview nor the TWRP image. I read somewhere about a similar thing some users had on Pixel C, but the solution was to either do something via TWRP or use fwtool that needs root. And I can do neither.
So that's why I started this topic to see if anyone can think of anything else.
Sent from my A0001 using Tapatalk
On thing to try is to go into the settings Developer Options and "revoke USB debugging authorization". Connect to PC and you should then be asked to allow the "fingerprint". Hopefully that will fix it. I assume you've tried changing the connection type - charging, File transfer etc. If you are using W10 Pro then you may have driver issues. There are many posts on the net about that os and Google's driver but I've yet to find a definitive answer, I now use a USB C card see http://forum.xda-developers.com/pixel-c/help/windows-10-pixel-c-type-c-ports-t3414423
"""""""""""""""""""""""""''Help Help Help Help"""""""""""""""""'''''''''’'''''
I am having Moto M XT1663 phone I bought was already boot unlocked so i decided to Install recovery and Root so that I can enjoy rooted things.
The problem is that the phone not detectable in Fastboot mode phone can only be detected in ADB mode. When I write command "ADB devices" it shows my device.
If I want to reboot into boat loader and use fastboot devices after hitting enter it shows nothing and no error appears.
I google about my phone's drivers that should be installed in order to use fastboot mode. So I installed them but no success.
One thing I notice that In fast boot mode my laptop giveys USB detection error and also tells me ADB interface failed.
Tried below mentioned things in order to get my phone detected in fastboot mode:
1) tried 3 different laptops(my Nexus 6p is detectable on all three laptops).
2) changed USB cable.
3) FDR using recovery.
EDIT: Problem solve by install Mediatek driver from windows update
Hello,
I have tried installing the google drivers and the drivers from the Razer support site, but I keep getting the error message 'This device cannot start. (Code 10)'.
I would like to lock the bootloader.
I have tried running adb reboot bootloader into command prompt, then running fastboot oem lock but it just comes up with < waiting for device > and nothing I have done has resolved this.
Any help on this matter would be greatly appreciated .
try these ones: https://adb.clockworkmod.com/
those are the only drivers working with my newer PC, AMD x470 Chipset
If you still have problems you can try using an older Windows 7 like Laptop
sanicwowguy said:
Hello,
I have tried installing the google drivers and the drivers from the Razer support site, but I keep getting the error message 'This device cannot start. (Code 10)'.
I would like to lock the bootloader.
I have tried running adb reboot bootloader into command prompt, then running fastboot oem lock but it just comes up with < waiting for device > and nothing I have done has resolved this.
Any help on this matter would be greatly appreciated .
Click to expand...
Click to collapse
Just forget about it. This phone cannot be rooted
Hey there,
so fastboot does not recognize my phone in bootloader mode.
USB Debugging is enabled.
- ADB Commands work
- Fastbootd Mode and Fastbootd Commands work (adb reboot fastboot)
However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)
Drivers are Installed.
- I have an AMD Processor and i am aware of the issues. I tried the USB controller fix.bat without any changes.
- I have disabled Driver Signature in Windows 10, still nothing
Please help :/
Abrucci said:
Hey there,
so fastboot does not recognize my phone in bootloader mode.
USB Debugging is enabled.
- ADB Commands work
- Fastbootd Mode and Fastbootd Commands work (adb reboot fastboot)
However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)
Drivers are Installed.
- I have an AMD Processor and i am aware of the issues. I tried the USB controller fix.bat without any changes.
- I have disabled Driver Signature in Windows 10, still nothing
Please help :/
Click to expand...
Click to collapse
How does it show in Device manager?
sd_shadow said:
How does it show in Device manager?
Click to expand...
Click to collapse
*However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)*
Abrucci said:
*However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)*
Click to expand...
Click to collapse
Try a different usb cable