Database Info

Google Ion Developer's Edition

I need some help installing amon_ra's recovery. In adb it states I don't have permission to push files. If I try to run a fastboot it states I don't have permission. How can I get the above mentioned recovery on this phone ?

timal said:
I need some help installing amon_ra's recovery. In adb it states I don't have permission to push files. If I try to run a fastboot it states I don't have permission. How can I get the above mentioned recovery on this phone ?
Click to expand...
Click to collapse
You should ask this in the thread that already exists.
If you follow every step listed, that won't happen. Do not skip any steps.
Do not skip any steps
1. Boot the device in fastboot mode, hold down the back button while powering on.
2. Connect via USB.
3. "fastboot boot recovery-RAv1.1.1H.img"
It will reboot into the custom fastboot with a black background. Then you'll be set to do these commands:
adb shell mount -a
Ignore the the errors...
adb push recovery-RAv1.1.1H.img /system/recovery.img
adb push recovery-RAv1.1.1H.img /sdcard/recovery-RAv1.1.1H.img
adb shell flash_image recovery /sdcard/recovery-RAv1.1.1H.img
adb shell reboot

I would have tried all that except the adb drivers are not working with the magic on windows vista. Device manager only shows Android 1.0

timal said:
I would have tried all that except the adb drivers are not working with the magic on windows vista.
Click to expand...
Click to collapse
they work fine, you just need to properly install them.

k4r1m said:
they work fine, you just need to properly install them.
Click to expand...
Click to collapse
Device manager only shows Android 1.0 Which I installed from the most recent sdk. Adb only will show 'waiting for device' even when I try to boot the recovery before flashing.

timal said:
Device manager only shows Android 1.0 Which I installed from the most recent sdk. Adb only will show 'waiting for device' even when I try to boot the recovery before flashing.
Click to expand...
Click to collapse
Switch to Linux ... nah just kidding... you obviously have a driver "issue", it happens to many people using Micro$oft Vi$ta...
Perform the following steps (do not skip any steps) on Vista :
1. Make sure your phone is not connected via usb
2. Download USBdeview and run it as admin (it's very important to run it as admin otherwise you will be unable to uninstall!).
3. Uninstall all drivers that mention Android in the device name or description.
4. Make sure that USB debugging is enabled in your phone (Settings - Applications - Development - USB debugging).
5. Connect your phone via usb.
6. Vista will now look for drivers, point it to the sdk drivers and make sure it uses those.
7. Check with "adb devices" to see if your phone listed.

Amon_RA said:
Switch to Linux ... nah just kidding... you obviously have a driver "issue", it happens to many people using Micro$oft Vi$ta...
Perform the following steps (do not skip any steps) on Vista :
1. Make sure your phone is not connected via usb
2. Download USBdeview and run it as admin (it's very important to run it as admin otherwise you will be unable to uninstall!).
3. Uninstall all drivers that mention Android in the device name or description.
4. Make sure that USB debugging is enabled in your phone (Settings - Applications - Development - USB debugging).
5. Connect your phone via usb.
6. Vista will now look for drivers, point it to the sdk drivers and make sure it uses those.
7. Check with "adb devices" to see if your phone listed.
Click to expand...
Click to collapse
Thank you I tried all the above. Long story short brick, no power dead . This hobbie is getting expensive.

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

Un/Official (Windows) USB Drivers/ADB/Fastboot [Essential PH-1/Mata]

Warning if your intent is to Unlock the Bootloader.
At this time 24 Sept 2017
There are no Stock Firmware Images, No Custom Recovery, No Root Method.
Without any of those available Unlocking Bootloader has little Value, and lots of risks.
Official PH-1 windows drivers are up, with Official builds.
https://essential-live.herokuapp.com/developer/current-builds thanks for update @bmg1001 -14 Nov 2017
I haven't seen any Official Windows USB drivers (adb/fastboot) posted any where so i just used Google Pixel Drivers.
Official Google Drivers
Selecting correct drivers in Device manager
Adb seems to work with Windows default drivers, but i had to update ADB.exe version
SDK Platform-Tools for Windows ~3MB
If you have never used ADB
[Index] Setting up and Using ADB/Fastboot
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
Enabling Dev Options
See post #2
ADB Setup/ Troubleshooting
See post #3

Enable Dev Options..
Settings/About phone
Tap on Build number, until you see "You are now Developer"
Back up one screen (Main Settings Page)
tap Developer options
Optional
Toggle on Stay Awake (if you are new to this)
If you are plan on Unlocking Bootloader
Toggle On OEM unlocking
Select Enable (on popup window)
Required
Toggle On USB debugging
Watch for Allow USB debugging popup on Phone
recommended
check box Always allow from this computer
then OK

Testing ADB setup by booting to bootloader
Code:
adb reboot-bootloader
If that code doesn't work you may need to update adb

Fastboot setup
Fastboot commands only work with the device in Fastboot/Bootloader Mode
Boot the Device to Bootloader Options
Code:
adb reboot-bootloader
Power off, Hold Volume Down Button, Power On
Connect To PC via USB
Open PC Device Manager (Settings/Devices/Device Manager)
Look For Mata
Update Driver (Right Click on Mata)
Browse My Computer for Driver Software
Let Me Pick from a List of Available Drivers
Select your Device's Type: ADB
Select the Driver ypu want to Install
Manufacture: Google
Model: ADB Testing (there may be a better one)
Select: Next
PH-1/Mata should look like this
If You don't see adb drivers in available drivers
Try installing l Google Drivers in post #1

I'm using the minimal adb&fastboot, do you think that's the problem?
edit: see attached thumnail, I looked at your photos and followed the instructions. On my windows I get the following options. I tried the two "ADB testing interface" options and neither seem to allow me to perform fastboot commands. If I type fastboot devices nothing happens while the device is in fastboot mode. The ADB commands while the device is powered on do work though.

elsamuraiguapo said:
I'm using the minimal adb&fastboot, do you think that's the problem?
Click to expand...
Click to collapse
no, you need to select the correct driver in Device Manager

Looks like Minimal ADB and Fastboot hasn't been updated since 6th January 2017
So that could be an issue

Updated post #4
to explain images in post #1

sd_shadow said:
no, you need to select the correct driver in Device Manager
Click to expand...
Click to collapse
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Is yours the Sprint variant?

elsamuraiguapo said:
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Click to expand...
Click to collapse
Doesn't look like that has been updated since October 2016
i would use the ADB files direct from Google, link in post #1
Is yours the Sprint variant?
Click to expand...
Click to collapse
No, but if bootloader wasn't Unlockable, the OEM unlocking option in Settings should be Greyed out and unselectable

[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05
adb-setup-1.4.3.exe
has adb version Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android
and fastboot commands didn't work for me with Mata

ADB version working for me is
Code:
adb version
adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android

[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng

sd_shadow said:
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng
Click to expand...
Click to collapse
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.

elsamuraiguapo said:
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.
Click to expand...
Click to collapse
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date

sd_shadow said:
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date
Click to expand...
Click to collapse
Well I uninstalled all the drivers I could find on my computer to start from scratch. Which should I install? I can't figure out how to install the google usb drivers referenced above

Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again

sd_shadow said:
Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again
Click to expand...
Click to collapse
Okay awesome, I think we're almost done. When I type in fastboot devices I can see the device now. Starts with PM1. What command did you use to unlock the bootloader? I tried fastboot oem unlock and "fastboot flashing unlock" and it failed. (remote: unknown command)
Edit: Never mind it worked now after a few attempts. Weird cause I typed the same command over and over and it kept failing. Anyway looks like it rebooted successfully after the factory reset. Thanks for your help mate. Now I can set up the device to my liking and just wait until we get customer recovery and root.

Hi guys, same issue here with OPENUS version of the MATA PH-1.
I have installed 15 seconds ADB driver 1.43 clean on laptop and can access the phone with ADB and reboot it into bootloader.
However, 'fastboot devices' gives me nothing. I've updated the Mata in device manager first with the options from the 15 seconds ADB, with are 'Android ADB Interface', 'Android Bootloader Interface' and 'Android Composite ADB Interface'. None of them give me any luck when trying 'fastboot devices', nothing found.
Then, uninstalled the ADB driver from device manager so that it showed Mata again, installed Google driver from 1st post, but same thing: version 11.0 of Google drivers (28/08/2014) with same choices, but none of them work.
Does this have to do with the USB A 3.0 --> USB C cable maybe? Or is it just a driver thing?
BTW reason for unlocking is so that I can root later without wiping the device, once root becomes available..

updated post 1 a bit

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.

Can't connect to Pixel 3a in fastboot mode

Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.

You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day

Chrisp3 said:
Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.
Click to expand...
Click to collapse
On Windows, make sure your phone is connected and you can run ADB commands. Enter Device Manager in Windows and verify that there is a listing for Android ADB Interface.
I just connected to a new computer and I could do ADB but not Fastboot. Discovered that instead of ADB Interface in Device Manager, it just said "Pixel 3a."
If this is the same for you, go install the Android USB drivers.

KaptinBoxxi said:
You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day
Click to expand...
Click to collapse
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!

Chrisp3 said:
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!
Click to expand...
Click to collapse
The issue with the fastboot method (realized this when I upgraded to Win11 Beta) is the ADB Quick Installs are missing some stuff, and cause certain flash methods to not work via flash-all.bat's from Google or Graphene or others.
When I install ADB System Wide, I also download the platform-tools from Google, and over-write everything in the c:\adb folder, also adding the stuff missing. Idk why the adb quick installers don't just download from google directly, would save a lot of headaches