Database Develop

[Q] Struggling to unlock Bootloader using Mac OS 10.9

I just got my Verizon Dev Edition and am having trouble unlocking the bootloader using my MacBook Pro running OS X 10.9. I am following the instructions from the Moto website.
- I downloaded the SDK and unzipped it.
- I downloaded the USB drivers (though they only show it for up to 10.8 Mountain Lion) and installed them.
- I put the phone in Fastboot mode, connected to my computer, opened up the terminal and went to the directory where I installed the tools, and typed in the command per instructions:
​$ fastboot oem get_unlock_data
Here is what I input in Terminal and the result:
Macintosh:~ zenrubble$ cd /Users/zenrubble/Developer/adt-bundle-mac-x86_64-20131030/sdk
Macintosh:sdk zenrubble$ $ fastboot oem get_unlock_data
-bash: $: command not found​
Any Mac users out there able to clue me in on what I might be doing wrong?
Any help appreciated.

zenrubble said:
I just got my Verizon Dev Edition and am having trouble unlocking the bootloader using my MacBook Pro running OS X 10.9. I am following the instructions from the Moto website.
- I downloaded the SDK and unzipped it.
- I downloaded the USB drivers (though they only show it for up to 10.8 Mountain Lion) and installed them.
- I put the phone in Fastboot mode, connected to my computer, opened up the terminal and went to the directory where I installed the tools, and typed in the command per instructions:
​$ fastboot oem get_unlock_data
Here is what I input in Terminal and the result:
Macintosh:~ zenrubble$ cd /Users/zenrubble/Developer/adt-bundle-mac-x86_64-20131030/sdk
Macintosh:sdk zenrubble$ $ fastboot oem get_unlock_data
-bash: $: command not found​
Any Mac users out there able to clue me in on what I might be doing wrong?
Any help appreciated.
Click to expand...
Click to collapse
On mac you have to use "./" in front of fastboot or adb:
./fastboot oem get_unlock_data
Hope this helps.

zenrubble said:
I just got my Verizon Dev Edition and am having trouble unlocking the bootloader using my MacBook Pro running OS X 10.9. I am following the instructions from the Moto website.
- I downloaded the SDK and unzipped it.
- I downloaded the USB drivers (though they only show it for up to 10.8 Mountain Lion) and installed them.
- I put the phone in Fastboot mode, connected to my computer, opened up the terminal and went to the directory where I installed the tools, and typed in the command per instructions:
​$ fastboot oem get_unlock_data
Here is what I input in Terminal and the result:
Macintosh:~ zenrubble$ cd /Users/zenrubble/Developer/adt-bundle-mac-x86_64-20131030/sdk
Macintosh:sdk zenrubble$ $ fastboot oem get_unlock_data
-bash: $: command not found​
Any Mac users out there able to clue me in on what I might be doing wrong?
Any help appreciated.
Click to expand...
Click to collapse
I'm a windows user but I had to drop the $ as I too got teh command not found error. The command that worked for me was:
fastboot oem get_unlock_data

zenrubble said:
I just got my Verizon Dev Edition and am having trouble unlocking the bootloader using my MacBook Pro running OS X 10.9. I am following the instructions from the Moto website.
- I downloaded the SDK and unzipped it.
- I downloaded the USB drivers (though they only show it for up to 10.8 Mountain Lion) and installed them.
- I put the phone in Fastboot mode, connected to my computer, opened up the terminal and went to the directory where I installed the tools, and typed in the command per instructions:
​$ fastboot oem get_unlock_data
Here is what I input in Terminal and the result:
Macintosh:~ zenrubble$ cd /Users/zenrubble/Developer/adt-bundle-mac-x86_64-20131030/sdk
Macintosh:sdk zenrubble$ $ fastboot oem get_unlock_data
-bash: $: command not found​
Any Mac users out there able to clue me in on what I might be doing wrong?
Any help appreciated.
Click to expand...
Click to collapse
The command to type in is "fastboot oem get_unlock_data" do not type the "$"

That worked
fuego3048 said:
On mac you have to use "./" in front of fastboot or adb:
./fastboot oem get_unlock_data
Hope this helps.
Click to expand...
Click to collapse
That was the problem. I used the ./ and it worked like a charm.
Thanks to all for your help.

fuego3048 said:
On mac you have to use "./" in front of fastboot or adb:
./fastboot oem get_unlock_data
Hope this helps.
Click to expand...
Click to collapse
I've been trying to run this command for hours, and this finally worked. Thank you so much!

luckychrysler said:
I've been trying to run this command for hours, and this finally worked. Thank you so much!
Click to expand...
Click to collapse
Glad you got it working. It can be a frustrating world for us Mac users sometimes

fuego3048 said:
Glad you got it working. It can be a frustrating world for us Mac users sometimes
Click to expand...
Click to collapse
Hello. I'm having the same problem. Unfortunately I'm still having the problem. This is what it shows
Last login: Sat Sep 16 14:27:42 on ttys000
lllllllllls-MacBook-Pro:~ new$ cd /Users/new/Library/Android/sdk
lllllllllls-MacBook-Pro:sdk new$ ./fastboot oem get_unlock_data
-bash: ./fastboot: No such file or directory
lllllllllls-MacBook-Pro:sdk new$

GuestK0040 said:
On mac you have to use "./" in front of fastboot or adb:
./fastboot oem get_unlock_data
Hope this helps.
Click to expand...
Click to collapse
Dude you saved my live I have been struggling with this for days why dont they explain this on the F**ING motorola website!!!! OMG DUMB!!!

[Q] Unable to use fastboot

After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.

I've been trying other things with no success.
I've installed windows on a VM and rebooted the phone into fastboot mode. When I try to list devices in fastboot I get the '?' answer as if the phone wasn't recognised.
Device drivers seem to be installed as no missing drivers appear in the device manager.
How can I fix this?
Thanks in advance!
UPDATE: Added some more info
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.017s

antoniovazquezblanco said:
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
Click to expand...
Click to collapse
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.

g4b3rm4n said:
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
Click to expand...
Click to collapse
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!

antoniovazquezblanco said:
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
Click to expand...
Click to collapse
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too

g4b3rm4n said:
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
Click to expand...
Click to collapse
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!

antoniovazquezblanco said:
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
Click to expand...
Click to collapse
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?

g4b3rm4n said:
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
Click to expand...
Click to collapse
Is this also happening to you?
I would like to be able to use fastboot boot for some kernel testing... It seems there's source code for kernel building both from Huawei and the comunity and it would be nice to have a free kernel as a base for cm devel...
It is also 00:50 here (Spain)... Tomorrow will be another day, no hurry

1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.

Kostyan_nsk said:
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Click to expand...
Click to collapse
Thank you Kostyan_nsk! I really appreciate you sharing your knowledge .
About 2 I thought the same but I was not sure... so why not trying...
About 3 do you know what are the supported commands or where to find that information? It would be nice to have a post in the developers section with some documentation for those who want to perform tests with the device .

[fastboot] problem with booting boot.img

When i use the command "fastboot boot boot.img" to boot twrp it loads endlessly until i interrupt it,
where it then gives me the error : FAILED (Status read failed (Too many links)).
My device is detected by "fastbood devices" and "adb devices".
I already tried to set the current slot to a with this: fastboot.exe --set-active=a
but it failed: FAILED (remote: 'unknown command').
My device is unlocked but when i check device status via "fastboot oem device-info" it tells me: (bootloader) 'device-info' is not a supported oem command.
Same goes for "fastboot oem help" which results in a : "FAILED (remote: 'unknown command')".
Right now i am using Havoc-OS which means it did work before.
Anyone else got any tips how i might get twrp to run again?

are you trying to boot fastboot boot boot.img ? or fastboot boot twrp.img ?

You need USB 2.0 hub.

Hello.Dear said:
You need USB 2.0 hub.
Click to expand...
Click to collapse
I've heard that before but I use a USB3.0 .

KrisM22 said:
I've heard that before but I use a USB3.0 .
Click to expand...
Click to collapse
Fastboot has a problem with USB 3.0. Same thing happened to me then i use usb 2.0 hub and everything works.

Unlocking Bootloader Issue

Hello guys!
I have an XT1929-4 on android pie and I am having issues with unlocking my bootloader.
I am using the fastboot unlock method and I am always getting stuck with the "fastboot oem get_unlock_data" command. "fastboot devices" shows my device serial number. OEM unlock and USB debugging is also turned on in the devices settings. The tool I am using is the minimal ADB and Fastboot software. Tools mode config is enabled when I do the fastboot commands, If 'fastboot oem help' should work, then maybe all 'fastboot oem' commands are not working for me.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY2268BV45 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.002s
^I did the fastboot oem get_unlock data twice here.
I was planning to flash pixelexperience rom when I saw the thread here. Thank you in advance and I hope somebody can help.

FIXED: i used all three usb A ports of my laptop. I tried using the usb c port of the laptop by using a usb c to usb a adapter. fastboot oem get_unlock_data worked.

Question 'fastboot oem unlock' failing with remote: 'unknown command'

I just got my OnePlus 10 Pro, and am trying to unlock the bootloader. I've enabled USB debugging, and enabled the option to allow the bootloader to be unlocked in the Developer Settings.
I ran `adb reboot bootloader`, then ran `fastboot devices` to confirm the phone was connected and visible.
When I try to run `fastboot oem unlock`, I get this response:
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Fastboot version if necessary:
Code:
C:\Windows\system32>fastboot --version
fastboot version 33.0.2-8557947
Installed as C:\Program Files\Android Platform Tools\fastboot.exe
Thanks!

Fastboot flashing unlock

Awesome, thank you very much!