Unlock 6.0 Bootlader - Moto G 2015 Q&A, Help & Troubleshooting

I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows

MrTooPhone said:
I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows
Click to expand...
Click to collapse
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.

In addition to the above, by not prepending './' to your command, you were calling a(n apparently available) system-wide installation that might have been too old to detect the device. It would also help if you would post an lspci so we could see if the device is at least in the correct mode.

acejavelin said:
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.
Click to expand...
Click to collapse
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.

MrTooPhone said:
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.
Click to expand...
Click to collapse
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk

acejavelin said:
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Tried again with Linux. SU did the trick. Thanks.

Related

[Q] Installing Cyanogenmod, Fastboot wont work.

So, trying to root and install cyanogenmod on my friends Evo **** 4g 2.3.3.
Following instructions per the cyanogenmod install wiki and a few other places.
I am using linux for everything and have adb setup correctly. I downloaded the fastboot from htc's dev website. [Everyone links you to the website but forgets to mention that you have to create an account and click on 'unlock bootloader' and scroll through a few pages]
Anywho, I did that and extracted the file to my android sdk directory. {for me it's [androidsdk/platform-tools]}
Now, when I try to run the fastboot command after running the adb reboot command to get into the bootloader, it returns with an error. "Fastboot command not found"
Now, I double checked and I marked the permissions for the fastboot file to be allowed to execute as a program.
What else am I doing wrong? If someone that has done this before, could help me out, that would be fantastic!
Again, I am running on ubuntu 11.04 linux with adb set up properly. Thanks.
cehck to see if you are in the same directory as fastboot. If you are in the platform-tools/ directory, do cd ../tools
fastboot *command here
Indirect said:
cehck to see if you are in the same directory as fastboot. If you are in the platform-tools/ directory, do cd ../tools
fastboot *command here
Click to expand...
Click to collapse
I was indeed in the same directory as fastboot, but fastboot would not recognize as a command. Even when I tried it with my atrix.
Try chmod 777 fastboot
Sent from my PC36100 using XDA Premium App
Trying this now. Will let you know in a sec.
Edit:
Still getting fastboot: Command not found

Problem locking bootloader.

Adb is saying that it doesn't recognize "fastboot" as a command. I haven't really use ADB since I got the phone in February, has there been changes to the commands needed?
I did a simple search and found this: http://www.nexusoneforum.net/forum/...-fastboot-devices-command-not-recognized.html
GL Hope it helps.
Problem is not it recognizing cause Adb reboot-bootloader works.
This used to work
Cd\
Cd androidsdk/tools/
Fastboot oem lock
Has something been moved? And if so what is the new path?
sarge363 said:
This used to work
Cd\
Cd androidsdk/tools/
Fastboot oem lock
Has something been moved? And if so what is the new path?
Click to expand...
Click to collapse
Make sure fastboot is still in your tools folder. With some of the updated sdk fastboot gets removed. If it's not there you can get it from the cm wiki and just put it in the tools folder.
Sent from my PG06100 using Tapatalk
The problem is that you think you need to run adb to get fastboot to work.
adb and fastboot are 2 separate programs. ADB is the Android Device Bridge where fastboot is another standalone command line program s used to directly flash the filesystem etc.
If you download the Android SDK now, it won't have fastboot included, so you need to get it from somewhere else, like the old CM wiki as crump suggested.
Once you have the compiled fastboot file, you can navigate to it from a command prompt and execute the fastboot commands
Greetz
Thanks for the clarification. I really only used it once or twice when I first got the phone. And I just looked and I am missing the fastboot. I'll give it a shot.
In cm wiki there is only fastboot 32bit. I have 64bit, will it still work?
sarge363 said:
In cm wiki there is only fastboot 32bit. I have 64bit, will it still work?
Click to expand...
Click to collapse
Yes, 64 bit computers are backwards compatible for the most part
Sent from my illuminated black thing

[TOOL] Android ADB and Fastboot MSI installer with PATH variable

Description
After always having to search for the latest versions of Android's ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.
You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.
This installer is 32-bit and 64-bit compatible.
Usage
The default installation path is C:\ADB so you can easily add your flashable files in there.
After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don't need to change paths. Keep in mind that you need admin privileges, though.
To open a command prompt with administrator rights on Windows 8, just right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Command Prompt (Admin).
Click to expand...
Click to collapse
If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.
Click to expand...
Click to collapse
Requisites
You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.
You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.
Click to expand...
Click to collapse
Download
I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.
The download link and screenshots are on my website.
http://rubenalamina.mx/custom-installers/android-adb-fastboot/
Latest version of the installer: 1.5 (ADB 1.0.36) updated on 2016.09.21
Thanks mate, it really help people with lacks internet connection like mine
Sent from my WT19i using xda app-developers app
Installer updated to version 1.2 with the new ADB and Fastboot included in Android SDK 23.0.2.
Installer updated to version 1.3 based on the Android SDK 24.0.2.
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Nightmare-Rex420 said:
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Click to expand...
Click to collapse
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
ajua said:
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
Click to expand...
Click to collapse
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Nightmare-Rex420 said:
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Click to expand...
Click to collapse
Try using PowerShell. Also, see if you are able to run the ADB that comes with the SDK but run it from the folder where it is located.

ADB not recognized

So I finally undated my PC from Ubuntu 12.04 to 16.04. The good new is I have full MTP access to my G3 now. However, ADB is no longer recognized. ADB and Fastboot are located on a separate drive from the OS, so I am trying to run the same file from the same HD. Any suggestions?
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Tel864 said:
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
I did try that without success even though I successfully ran ADB without root with 12.04. Only Fastboot needed root.
For some reason the file is not recognized as an executable file. Below is a screen copy:
Code:
$ ls
adb fastboot twrp-osprey-3.0.0-r2.img
commands.txt twrp-osprey-2.8.7-r5.img twrp-osprey-3.0.2-r1.img
$ adb
The program 'adb' can be found in the following packages:
* adb
* android-tools-adb
Try: sudo apt install <selected package>
$
Henriquefeira said:
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Click to expand...
Click to collapse
I have not even got that far. See post above, "adb" is not recognized. I would rather not install the adb development package if I can avoid it.
Its fastboot flash recovery not adb flash
Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
The commands is not my issue. I have a list of commands I have run successfully many times. My issue is with the new OS (in the same PC) not recognizing adb. When I boot to the old OS, no issue, back to the new OS, command is not recognized..
My list of commands is as follows:
Code:
adb devices
adb reboot bootloader
sudo fastboot devices
sudo fastboot boot twrp-osprey-3.0.2-r1.img
Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
Re-reading your reply, I think you mis-read my code box. Next to the dollar sign my command "ls". Below is the OS response. Next $, command is "adb", and below the OS response.
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
MrTooPhone said:
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
Click to expand...
Click to collapse
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
acejavelin said:
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Pretty sure I had multiple 'adb' executables in 12.04.
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
steffano said:
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
Click to expand...
Click to collapse
adb doesn't work in bootloader mode, that is when you use fastboot... I think you should review the process involved in installing recovery.
Sent from my MotoG3 using Tapatalk

Waiting for Device Error

i want to root https://www.xda-developers.com/root/
when i try
Code:
fastboot flash boot /path/to/magisk_patched.img
im stuck at
< waiting for device >
when i try
adb devies
it show my device
but when i boot to fastboot in my phone
i try
fastboot devices
didn't show fastboot devices
i use
15 seconds ADB Installer​https://www.droidthunder.com/adb-drivers/#Method_1_Using_15_seconds_ADB_Installer
what should i do ??
if youre on windows, have you installed the driver provided by your manufacturer? Or did you run command prompt as administrator?
if youre on linux, did you execute adb/fastboot with root permissions?
Also make sure you use the official plaform tools: https://developer.android.com/studio/releases/platform-tools
MLPIR said:
if youre on windows, have you installed the driver provided by your manufacturer? Or did you run command prompt as administrator?
if youre on linux, did you execute adb/fastboot with root permissions?
Also make sure you use the official plaform tools: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
im on windows i have already install mtp driver also run cmd as admin in the platform-tools folder still not show the devices.
chatofking said:
im on windows i have already install mtp driver also run cmd as admin in the platform-tools folder still not show the devices.
Click to expand...
Click to collapse
Is your usb properly plugged in and working? (Both on the computer and phone)
yes as you can see
it work on adb devices but not fastboot devices.
Code:
D:\platform-tools>adb devices
List of devices attached
WGWWINQGT8NBJVB6 device
Code:
D:\platform-tools>fastboot devices
what should i do ??
Run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot devices
xXx yYy said:
Run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot devices
Click to expand...
Click to collapse
did you mean
Code:
adb reboot bootloader
xXx yYy said:
Run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot devices
Click to expand...
Click to collapse
thank it worked now
it show fastboot mode instead fastboot in my phone
D:\platform-tools>fastboot devices
WGWWINQGT8NBJVB6 fastboot
can i ask one more question i got this message
when i
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
what should i do ??

Categories

Resources