Just got a pixel 3a, it's running android 9. I want to unlock the bootloader. I'm following one of the popular root guides on this forum. I can't seem to get adb or fastboot to find my device.
Installed ADB applications from https://developer.android.com/studio/releases/platform-tools.html
Turned on developer options in phone, turned on USB debugging, plugged in phone.
Wasn't prompted for device authorization from phone.
Changed USB connection mode to PTP.
I have tried all USB connection modes, I verified the cable used to connect the pc to the pone is a data cable as I can transfer data when the phone usb mode is set to file transfer, ptp, or midiInstalled adb/phone device driver using https://developer.android.com/studio/run/win-usb
Still no debugging authorization prompt, but device manager lists the phone under 'Android Device' as 'Android Composite ADB Interface'.
'adb devices' doesn't list anything, tried 'adb kill-server', 'adb start-server', and 'adb usb'
'adb devices' doesn't list anything
reboot phone into fastboot by shutting down and holding power+volDown
'fastboot devices' doesn't list anything
Rebooted my pc, rebooted the phone, retried everything.
I'm at a loss, any suggestions?
Yea I've had some issues with adb/fastboot on windows as well. Sometimes it just won't detect the device, rebooting into my Linux install finds it instantly though. I haven't looked into how to fix it yet though as I can always just reboot to Linux. If you're on a version of windows that supports WSL, perhaps you should try that?
Sent from my Google Pixel 3a XL using XDA Labs
Related
adb devices doesn't show anything. I have tried it with linux and windows (with Motorola drivers installed), it doesn't work. I can access the phone when I have enabled MTP, but it just won't show in adb. I have killed and started adb server so many times, it's frustrating.
The thing is, the first time (yesterday) it worked! I could reboot into fastboot with adb but then nothing worked anymore.
Any ideas?
Maybe silly question, but: is USB debugging activated on the phone? If yes, try to switch between MTP and Camera (PTP) under "USB computer connection" option. You should get the authorization prompt on your phone when everything is fine.
Yes, USB debugging is activated. I already tried both MTP, PTP, and neither, but I don't get any authorzation prompts. I revoked all previos prompts, but still nothing. Thanks for the suggestion though!
Are you on bootloader or recovery or normally on os
I tried all three.
Try playing with the USB cable - change it, change the USB slot on the PC that it's connected to, etc.
I only have one USB cable, but I already tried it on several USB slots.
It worked! I had to put sudo in front of my adb commands! Yay! :victory:
When I first plugged my A9 into my computer I was immediately given a prompt to allow the computer to be used for adb, and proceeded to reboot to download to make sure everything worked before I attempted to unlock the bootloader using HTCdev. With the phone still plugged in the USB debugging symbol is no longer there and I've tried unplugging it, and plugging the cable back into the phone as well as the computer. Tried both ports on my computer, disabled USB debugging and re-enabled it but no dice ?. I'm not sure what to do now, adb devices shows up as empty.
Sent from my SCH-I545 using Tapatalk
65vdub said:
When I first plugged my A9 into my computer I was immediately given a prompt to allow the computer to be used for adb, and proceeded to reboot to download to make sure everything worked before I attempted to unlock the bootloader using HTCdev. With the phone still plugged in the USB debugging symbol is no longer there and I've tried unplugging it, and plugging the cable back into the phone as well as the computer. Tried both ports on my computer, disabled USB debugging and re-enabled it but no dice . I'm not sure what to do now, adb devices shows up as empty.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
This happens to me from time to time, especially when I'm swapping different devices out a lot.
Go to Device Manager
You should have Android USB Devices > My HTC (this is the ADB device) and Portable Devices > HTC One A9 (this is the MTP device).
You likely only see the MTP device. If so, right-click on it and select "Update Driver Software"
Click on Browse my computer for driver software
Navigate to your HTC device driver folder (in my case it's C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
Click Next
If you get a message that the best driver is already installed, then click the back button
Select "Let me pick from a list of device drivers on my computer"
If you have a device listed as My HTC select that
If you don't, you'll kind of have to play with different things from here. Try unchecking show compatible devices and see if it shows any Android USB devices. You might need to browse for your device drivers again.
Will try that when I get home, thank you very much ☺
Sent from my SCH-I545 using Tapatalk
Not sure what happened, but all of a sudden whenever I plug in my Blu Studio X+ into either one of my computers with USB Debugging enabled I get a pop up saying the USB device is not recognized, and it shows up in the Device Manager as an Unknown Device. I've tried updating the driver manually, but every time I navigate to an INF file in the driver installation dialog it tells me the specified file contains no information on the device. Doing an "adb devices" command returns nothing, and "adb shell" returns "error: device 'null' not found".
Sent from my STUDIO X PLUS using XDA-Developers mobile app
Already check your cable?maybe your cable does not support to transfer data beetween your phone and PC.
Make sure you have connect as a 'MTP' or Try to connect as a 'USB Mass Storage'
If you have tried all the ways,the last way is to backup your phone and do factory reset,or it will be BETTER if you bring your phone to serviceperson,because maybe there is an issues on your hardware.
jasonmerc said:
Not sure what happened, but all of a sudden whenever I plug in my Blu Studio X+ into either one of my computers with USB Debugging enabled I get a pop up saying the USB device is not recognized, and it shows up in the Device Manager as an Unknown Device. I've tried updating the driver manually, but every time I navigate to an INF file in the driver installation dialog it tells me the specified file contains no information on the device. Doing an "adb devices" command returns nothing, and "adb shell" returns "error: device 'null' not found".
Sent from my STUDIO X PLUS using XDA-Developers mobile app
Click to expand...
Click to collapse
You seem to have a lot of driver problems considering the number of threads you made
Go to device manager with your phone plugged in and uninstall every driver that has to do anything with your phone.
Unplug phone.
Reboot your PC.
Now plug phone back in and wait for the automatic driver installation to complete (doesn't matter if it succeeds or not).
Click here to download the latest driver (download it even if you have already).
Disable USB debugging and enable it again and wait for the automatic driver updater if it opens.
Open device manager and manually select the .inf file for your device.
If you don't know which device is your phone, unplug the phone and plug it back in and watch which devices disappear and then reappear again.
Also updating to Ubuntu, as your profile picture suggests, should ease the ADB driver installation and reduce ADB problems
Got it figured out. Wiped all ADB drivers and reinstalled, then downgraded my system-wide ADB from 1.4.2 to 1.3.
Sent from my LG-D415 using XDA-Developers mobile app
I have a new, unrooted, bootloader-locked F8332 Xperia XZ to which I am trying to connect via adb from my Windows 7 computer so that I can attempt an 'adb restore' of the applications and data from my current device. I already have the Android SDK installed and downloaded the XZ adb and fastboot drivers from the Sony developer site. However, I have not been able to install the drivers. When I connect the XZ (with USB Debugging enabled) and look in the Windows Device Manager, I get "Xperia XZ" listed under Portable Devices and nothing related to adb shows up. If I try to update the drivers and point Windows to the downloaded drivers for the XZ, it tells me that no drivers were found. With the XZ connected, I can run 'adb devices' and what I get is a blank list. I can connect the XZ set up for fastboot and it will show up in Device Manager as an Unknown Device. Attempting to install the drivers there also fails with a similar "no driver found" error.
My current device is a rooted Xperia TX. In order to get that device to show up with 'adb devices' I have to set its USB Storage Mode setting to Mass Storage, otherwise it will not work. The XZ, however, does not let me change the storage mode from MTP because whatever I choose (e.g. PTP) gets reverted to MTP immediately. So the questions is how do I get the XZ to be seen by adb or in a configuration that will allow me to install the relevant drivers? I am probably missing something simple because the threads in the forum relating to adb stop at "install the adb drivers" with no additional details. Any help would be appreciated.
Did some more playing around and figured out how to get the ADB interface to show up in Windows. As with my Xperia TX, the issue is related to the USB Configuration setting under Developer Options. For anyone who might run into this situation, it seems that USB Configuration has to be set to MIDI for ADB to work.
I had tried changing that setting to PTP, but it would not stick, it would always change back to Charging Only. Thinking that perhaps PTP would not stick because I did not have an SD card on the phone at the time, I put in an SD card and tried again, but the result was the same. Thinking that it would not actually work since what I was attempting had nothing to do with music, I set USB Configuration to MIDI and to my surprise the setting stuck. I plugged the phone into my computer and the Windows Device Manager showed a new "ADB Interface" entry with an exclamation mark. Right-clicking on ADB Interface and selecting Update Driver allowed me to choose the driver I downloaded from the Sony Developer Site. Windows accepted the drivers (with a prompt about the drivers being unsigned) and the Device Manager entry changed to "Sony sa0115 ADB Interface Driver." The XZ gave me a prompt about allowing the computer to have debug access, which I accepted. At this point I could go to a command prompt, run "adb devices" and the XZ showed up in the list, as expected.
The "adb restore" that I was attempting was (mostly) successful in transferring my applications and their data to the XZ. I still don't know why the PTP setting will not stick, or if that is normal.
Felix1701D said:
Did some more playing around and figured out how to get the ADB interface to show up in Windows. As with my Xperia TX, the issue is related to the USB Configuration setting under Developer Options. For anyone who might run into this situation, it seems that USB Configuration has to be set to MIDI for ADB to work.
I had tried changing that setting to PTP, but it would not stick, it would always change back to Charging Only. Thinking that perhaps PTP would not stick because I did not have an SD card on the phone at the time, I put in an SD card and tried again, but the result was the same. Thinking that it would not actually work since what I was attempting had nothing to do with music, I set USB Configuration to MIDI and to my surprise the setting stuck. I plugged the phone into my computer and the Windows Device Manager showed a new "ADB Interface" entry with an exclamation mark. Right-clicking on ADB Interface and selecting Update Driver allowed me to choose the driver I downloaded from the Sony Developer Site. Windows accepted the drivers (with a prompt about the drivers being unsigned) and the Device Manager entry changed to "Sony sa0115 ADB Interface Driver." The XZ gave me a prompt about allowing the computer to have debug access, which I accepted. At this point I could go to a command prompt, run "adb devices" and the XZ showed up in the list, as expected.
The "adb restore" that I was attempting was (mostly) successful in transferring my applications and their data to the XZ. I still don't know why the PTP setting will not stick, or if that is normal.
Click to expand...
Click to collapse
i tried what your mentioned and succeed,but i really want my 'mobile device' （a blue screen phone）show in my ‘file manager’。is there any method？
by the way,are all these mtp problem due to unlock bl?
Confirmed on my Xperia ZX F8331. I have to select MIDI interface to access to the ADB interface.
Btw, I'm rooted and the bootloader is unlocked.
Thanks for your report!
I have LE2110. In Settings I've enabled "OEM Unlocking" and also "USB Debugging".
I also instsalled the proper USB drivers but think they are unecessary regardless.
I boot into Fastboot & connect to laptop withofficial USB cable.
From the folder where I installed Android SDK Platform Tools I open command prompt.
Type in fastboot oem unlock and it says 'waiting for devices'.
I've rebooted everything, tried a few times over several days but always same result.
Phone works perfect, no issues otherwise.
Any tips what to try next or possibly what I'm doing wrong?
Thank you
I have a global unlocked 9. I had to use this to unlock bl. Open your command window from this after it installs,make sure to add shortcut to desktop when installing. Then run unlock command. Worked for me back in April when I bought device.
"minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities" https://androidfilehost.com?fid=746010030569952951
For me, I installed every driver while being in testsigning on ("bcdedit /set testsigning on" in cmd as administrator then reboot) and then I rebooted, turned testsigning off, rebooted again then it worked.
100 percent driver issue. Just reinstall the correct drivers and you'll be good to go.
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
dotuletz said:
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
Click to expand...
Click to collapse
Plus you can reboot edl through adb.