Database Info

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

I need help with ADB/Fastboot commands from a powers shell window

i am very new so please speak to me like i have 50 IQ points (im actually not far off). i can get the powershell to open on my pc then when i try
PS C:\platform-tools> adb devices
List of devices attached
R9WN113HXVJ device
it works, but when i try any commands that start with fastboot, the window just hangs. Do i need to be in the bootloader for fastboot? does TWRP need to be installed first?
#2. I am trying to get an image off of my tablet and the tutorial says i need to enter....
" adb pull /sdcard/Download/magisk_patched.img " I am assuming its supposed to mean....
"adb pull /sdcard/Download/NAME OF FILE ON TABLET.tar"... which is "magisk_patched_ZRwve.tar"
if i am trying to "pull" from the tablet, where does it put this file on my PC?

scampo77 said:
i am very new so please speak to me like i have 50 IQ points (im actually not far off). i can get the powershell to open on my pc then when i try
PS C:\platform-tools> adb devices
List of devices attached
R9WN113HXVJ device
it works, but when i try any commands that start with fastboot, the window just hangs. Do i need to be in the bootloader for fastboot? does TWRP need to be installed first?
#2. I am trying to get an image off of my tablet and the tutorial says i need to enter....
" adb pull /sdcard/Download/magisk_patched.img " I am assuming its supposed to mean....
"adb pull /sdcard/Download/NAME OF FILE ON TABLET.tar"... which is "magisk_patched_ZRwve.tar"
if i am trying to "pull" from the tablet, where does it put this file on my PC?
Click to expand...
Click to collapse
No worries friend, everyone starts somewhere and IQ is not a real scientific measurement. Now let's clear some things:
You're not in fastboot mode if you didn't recognize it immediately. To enter fastboot from adb, use:
Code:
adb reboot fastboot
and no you don't need twrp to access fastboot mode.
The correct way to use pull looks like this:
Code:
adb pull <path of file to pull> <path of destination on pc>
for example:
Code:
adb pull /sdcard/Download/YOURFILENAME C:\platform-tools\
Also from context of your question, i assume you want to root your phone. Something helpful to remember, you don't need to flash TWRP to root, you can just boot into it without permanently changing your recovery by using this command in fastboot:
Code:
fastboot boot nameoftwrp.img
from there flash magisk and you're done

Slim K said:
No worries friend, everyone starts somewhere and IQ is not a real scientific measurement. Now let's clear some things:
You're not in fastboot mode if you didn't recognize it immediately. To enter fastboot from adb, use:
Code:
adb reboot fastboot
and no you don't need twrp to access fastboot mode.
The correct way to use pull looks like this:
Code:
adb pull <path of file to pull> <path of destination on pc>
for example:
Code:
adb pull /sdcard/Download/YOURFILENAME C:\platform-tools\
Also from context of your question, i assume you want to root your phone. Something helpful to remember, you don't need to flash TWRP to root, you can just boot into it without permanently changing your recovery by using this command in fastboot:
Code:
fastboot boot nameoftwrp.img
from there flash magisk and you're done
Click to expand...
Click to collapse
i am being told that there is no fastboot for Samsung devices, however your commands within powershell all worked, i managed to drag my file over. thank you!
you said "now flash magisk" like its something everyone knows. I have magisk manager on my tablet now and I have a magisk.zip on my PC. I am using a program called ODIN for flashing Samsung devices but i cant seem to put all of these pieces together to root or flash my phone.
any advice?

Adb fails to recognise device only when in fastboot

Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.

herkio1 said:
Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.
Click to expand...
Click to collapse
Adb use Adb.exe and fastboot fasboot.exe (differente programs)
For Twrp you must use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.
download sdk Platform tools https://developer.android.com/studio/releases/platform-tools.
extract platform-tools folder.
Put this twrp https://androidfilehost.com/?fid=17248734326145679747 into platform tools folder
Phone in fastboot mode power and volume - (Obviously the phone must be detected on the pc)
use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.

Solved thanks, I used fastboot for fastboot mode and adb for in twrp/booted in system. I must have mistyped because I could flash the twrp.img file but it then gave me an error when trying to boot into it.

Question All kinds of errors when flashing a rom

I use the command fastboot -w update insert rom.zip or fastboot -w also fastboot update rom name.zip does not work. I use minimal adb fastboot I can't seem to sideload any roms even with the current build. What is going on? I get invalid sparse then failed within 20 seconds. Yes, I am in the bootloader screen and my phone is bootloader unlocked. Ones like StagOS for example or the more recent roms. I have no problem with Graphene OS or Caylx OS though.

UltimateGamer83 said:
I use the command fastboot -w update insert rom.zip or fastboot -w also fastboot update rom name.zip does not work. I use minimal adb fastboot I can't seem to sideload any roms even with the current build. What is going on? I get invalid sparse then failed within 20 seconds. Yes, I am in the bootloader screen and my phone is bootloader unlocked. Ones like StagOS for example or the more recent roms. I have no problem with Graphene OS or Caylx OS though.
Click to expand...
Click to collapse
Because you're not supposed to use "Minimal ADB and Fastboot". The binaries inside that package are years old. No wonder you're getting all those errors and have issues while trying to flash a ROM that is straightforward.
Download the latest platform-tools from Android's website (google).
Also, make sure that you're not using Windows PowerShell, but the actual CMD.

ekin_strops said:
Also, make sure that you're not using Windows PowerShell, but the actual CMD.
Click to expand...
Click to collapse
What is the reasoning behind this? I pretty much always use PS, guess I'll have to stop?

It being PowerShell or cmdline is irrelevant. Anyways..
Well, you should be using the latest platform-tools and have it added to PATH. A lot of unofficial drivers floating around on the internet install outdated adb/fastboot along with the drivers. Please refrain from installing these as well as minimal adb & fastboot; Use the official google driver and official platform-tools instead.
Alternatively you can prefix each adb/fastboot cmd with ./ while in the platform-tools folder via powershell or bash, etc.
For example:
./adb sideload ./rom.zip
Or
./fastboot -w update ./rom.zip
This tells the shell "Hey, I want to execute this local file, not the one in PATH".