Database Info

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

[Q] Root Xoom with linux ?

i ditched windows ages ago and i will never look back i am sick and tierd of waiting on moto uk to push ics. i use to have the dell streak and i rooted that but i was on windows then how do i root my xoom with linux mint is it possible and can any point me in the right direction please

Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk

Thank you megabiteg Still learning linux but i Love it
megabiteg said:
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse

well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see

Cheers for the info just by any chance do you know the commands still learning Linux
llama-power said:
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Click to expand...
Click to collapse

elsworth1983 said:
Cheers for the info just by any chance do you know the commands still learning Linux
Click to expand...
Click to collapse
thought you ditched windows ages ago?
anyhow... don't have linux set up atm, so this will from memory and might contain some errors... Also, never tried mint, I always stuck to debian or debian-derivates...
anyhow, lets try this:
first, use your package management-system to install a jre (java runtime environment.
If that is set up, install the android sdk:
Code:
$ cd ~
$ wget http://dl.google.com/android/android-sdk_r17-linux.tgz
$ sudo su
[enter your su-password]
# cd /usr/local
# tar xfzv ~[yourusername]/android-sdk_r17-linux.tgz
# ./android-sdk-linux/tools/android
a window should open up and list some files available for download. Just select "Android SDK Platform-tools" and hit "Install 1 package...".
once that's finished (might take a while), close the Android SDK Manager and you should get back to your shell.
Code:
# ln -s /usr/local/android-sdk-linux/platform-tools/adb /usr/local/bin/adb
# ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot
# exit
$ rm android-sdk_r17-linux.tgz
now, connect your xoom to your computer and enable usb debugging in the settings of your xoom. If you issue adb devices, you should get something like
Code:
List of devices attached
043c12343456476547 device
if you receive something like bash: adb: command not found, something went wrong somewhere. Try the same using sudo: sudo adb devices if that doesn't fix it please write another post.
Also, if you encounter an error after entering any of the comments above, please do not continue until you resolved that error. (For example ask for a solution here)
And, since you are still learning to use linux: whenever instructions contain a $ or # at the beginning of a line, DO NOT ENTER THESE. They are just there to tell you to issue that command as normal user ($) or superuser (#)
/EDIT: btw: there may be an easier way to do this if you just want to use adb/fastboot this once: you could try to simply download the adb and fastboot- binaries and put these into the folder with your recovery.img-file. Might work, not sure about that, though. Also, since I don't have linux installed on my machine atm, I can't provide you with a link to these binaries.

cheers for all your help will give this a go "Dont want to back to windows

Android SDK manger log
Error Stopping ADB server failed (code-1)
Connected the xoom and did adb devices and it listed the xoom with no errors in the terminal Thank you again ? Were do i go from here now

glad to read it's working
just follow the instructions in this thread That will help you to install a custom recovery and root your xoom. It will not, however, install a custom rom. To do that, you'd also need to download a custom rom (usually comes in a flashable .zip-file), place that on an acutal sd-card which you're gonna put into your xoom, and install that file from within the custom recovery. Just make sure you grab a rom that works with your xoom (for example, you shouldn't put a us-4g-rom onto a wifi-only-xoom and vice versa)

have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?

elsworth1983 said:
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
Click to expand...
Click to collapse
have you done the # ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot? The error you're getting seems to suggest that it can't find the fastboot application? What happens if you type /usr/local/android-sdk-linux/platform-tools/fastboot oem unlock?
elsworth1983 said:
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
Click to expand...
Click to collapse
that is expected. adb is only available while android is booted up, fastboot is the protocol to use while in bootloader mode. As indicated before, I suspect that your computer can't find the fastboot application (on the computer).

Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working

elsworth1983 said:
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
Click to expand...
Click to collapse
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.

all i can say is thank you for all the information every 1 is giving me my head is mashed lol so if i put recovery-Tiamat-R4c-100611-1150-cwm.img on the desktop what would the terminal code be
kofrad said:
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
Click to expand...
Click to collapse

depends on where your desktop is If it is in ~/Desktop/, then the correct command should be
Code:
fastboot flash recovery ~/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img

error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)

What am doing so wrong its lucky am not bold yet been trying this all day

elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
if the graphical interface, where do you see the file located?

elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
Sounds to me like you are running the commands as root. You likely have also downloaded the recovery image as a normal user. This means the '~' shortcut for the home directory is pointing you to someplace where the file is not.
Try using "fastboot flash /home/Your username/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img"

I have put the file on the desktop ? is that what u mean

Unlock 6.0 Bootlader

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.

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

Can't boot or flash TWRP from MacOS ADB. Can't find file...

Hi,
I successfully unlocked my bootloader and the MacOS ADB can still see my device.
However, I have the TWRP files and Magisk downloaded and ready to go on the Mac (and on my phone) but the ADB commands won't work. Fastboot boot or Fastboot flash...
It's my girlfriends Mac and I'm not familiar with MacOS at all. Am I doing something obvious wrong..??? Any ideas please??

the.Great.Skua said:
Hi,
I successfully unlocked my bootloader and the MacOS ADB can still see my device.
However, I have the TWRP files and Magisk downloaded and ready to go on the Mac (and on my phone) but the ADB commands won't work. Fastboot boot or Fastboot flash...
It's my girlfriends Mac and I'm not familiar with MacOS at all. Am I doing something obvious wrong..??? Any ideas please??
Click to expand...
Click to collapse
cant find file?
Seems like youre in the wrong folder. Try to navigate to your download folder with the command cd
You can also send pictures in here

You have to open a Terminal window in the same folder where you have adb and fastboot.
Also, on OSX, the commands have to be preceded by ./
For example:
./adb devices
./fastboot boot twrp.img

Done it thank you.
I did the 'cd' command.
Then dragged the img. file from Finder to the terminal window. Then put the 'fastboot boot' command in front of that. It worked obviously.
I was unfamiliar with the file location name. This seems an easy way for someone that doesn't have a clue like me. ??