I know I am probably the millionth person to say this, but I can't for the life of me get my device recognized in ADB when it's in Bootloader.
What I have tried so far:
- Activated OEM Unlock, USB debugging and set my computer to always be allowed for usb debugging
- Manually installed latest google usb drivers through device manager
- started up adb in cmd, made sure the device was recognized, rebooted in bootloader to check device list again
- Same thing, but with the drivers from the Mi A1 Tool)
The results:
- in Bootloader: Not recognized in ADB, but windows device manager shows "Android Bootloader Interface" as properly installed with google's driver 11.0.0.0.
- booted up: Recognized in ADB as " d59.... device" and in device manager as "ADB Interface"
This is not my first android rooting experience, but I have never had such problems installing drivers before. Is there anything special about the MI A1 I don't know? Anything I am forgetting maybe? All other Threads I found weren't helpful.
Thank you in advance for just taking the time to read until this point Any pointers even just links will be much appreciated!
Did you type 'su' after opening ADB/command prompt?
No I did not. Will try it out at home, but isn't that just for superuser meaning root access? The command to list devices should be "adb devices" not matter what mode the device is in, no?
Thank you for the tip!
Use "fastboot devices" "fastboot oem unlock".
Related
Hello,
First of all, the problem started when Android Kitkat update ota came to my device. After downloading it, my device was not able to verify it, as a result of which, it started downloading the update all over again. It downloaded the update more than 10 times without any success.
So finally I decided to sideload it. I set up everything properly, double checked everything. As I was going to send the update.zip to my tablet through command, the cmd prompt showed me "error: device not found".
I restarted the device, checked the drivers in my computer, even checked whether adb recognized it by commanding "adb devices". It did.
So again I turned it off, entered fastboot mode, But this time before entering recovery, I connected the device (it gave the connecting sound as on Win7). I ran the command "adb devices" and it showed no device at all!
My device is complete stock, unrooted. Usb debugging is turned on and MTP is selected.
Use a toolkit to install\test adb drivers then slide load using it. Some times windows install some crap adb drivers u have to remove them and install the naked drivers.
Toolkit is in development section.
I tested with wugfresh toolkit.
Please ignore my spelling mistakes. English is not my native language.
Hi xda community,
I have always sideloaded the OTA in recovery using a Windows machine. Yesterday, I tried to use my Chromebook running Ubuntu. I can see my device when Android is up and running (meaning Android is running and not in recovery or bootloader) by typing "adb device" using the terminal within Ubuntu. The problem I'm having is not being able to see my device when in Recovery mode and selecting the sideload adb mode.
$adb devices
List of devices attached
<---------this line is blank
$adb sideload update.zip
error: device not found
I've made sure /etc/udev/rules.d/51-android.rules are configured. I also checked the post regarding .android/adb_usb.ini but this is only for the Nook and should not apply to the Nexus 6P.
I also tried adb kill-server and adb start-server with no luck.
I've read post about being able to see the device in fastboot. I tried this as well and can't see the device either. My device does not have an unlocked bootloader but this should not matter. The device doesn't need to be for a sideload. This worked in Windows with no issues. You might ask, what is the problem then? I just want it to work in Ubuntu.
Does anyone have any suggestions on how I can fix this?
Thank you in advance for just reading.
After some more searching I found a suggestion to run the following command and it fixed my problem:
/etc/init.d/udev restart
http://android.stackexchange.com/questions/58187/adb-can-discover-devices-but-not-fastboot
My Acer Chromebook 11 only has two ports: 2.0 and 3.0 USB. I noticed the device would not show up after typing in "lsusb" which would normally show the Google device. I unpluged the USB cord from the 2.0 and plugged it into the 3.0. I read another post online stating this sometimes causes the problem.
When in fastboot I can type "fastboot devices" and "adb devices" in recovery and my device now shows up.
I hope this helps someone. Thank you all.
Mods feel free to close out this thread.
I'm trying to unlock the bootloader on my XT1622.
I can transfer files etc and backup when connected to PC and in Windows
I have installed the drivers and fastboot and adb and opened a cmd window in Admin mode in the directory where fastboot.exe and adb.exe are installed.
I have restarted the phone in fastboot mode (power up plus Vol Down) and connected by USB cable to my PC but when I type adb devices I get no information coming back.
Does anyone have any idea, please, where I may be going wrong?
Anyone able to help, please?
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.
actomox said:
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.
Click to expand...
Click to collapse
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?
Still no show
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
pastorbob62 said:
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?
Click to expand...
Click to collapse
actomox said:
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
Click to expand...
Click to collapse
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.
Still no joy
negusp said:
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.
Click to expand...
Click to collapse
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.
actomox said:
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.
Click to expand...
Click to collapse
Did an RSA key dialogue ever pop up when you plugged it into your PC?
If fastboot shows no devices when your phone is in fastboot mode (voldown+power hold), then something is seriously off. Have you tried multiple USB cables?
On your wife's PC did you make sure to install adb/fastboot and drivers: https://forum.xda-developers.com/showthread.php?t=2588979
And make sure to run the cmd shell as administrator/root? (right click cmd, click run as admin)
Will double check everything
Will double check all of those pointers over the weekend and report back. Thanks
Success at last
Went onto my wife's computer and deleted all that I could find relating to SDK and Motorola. Re-installed adb tools and the Motorola drivers and now adb devices return the details of the connected phone. Onto the next stage of unlocking the bootloader and then rooting. Thanks for the help.
Hi!
So I've just received my Oreo 8.1 update. but before updating, I decided to backup my EFS/persist after some reading in this forum.
Turns out ADB works fine, "adb devices" shows my phone ID but when I reboot to booloader, fastboot doesn't work, it doesn't show my phone ID.
While on ADB mode:
On Windows 10 Device Manager, Moto G5 Plus is listed under Android Devive > Motorola ADB Interface. (Everything ok here, no exclamation mark, working as it should)
-While on fastboot mode:
Phone gets listed under "Other Devices" as "Fastboot Potter S" (exclamation mark inside a triangle)
Tried uninstalling/reinstalling motorola drivers but I always get: Windows found drivers for your device but encountered an error while attempting to install it."
-Moto G5 Plus (XT1683) - Stock, Nougat 7.0 ( NPNS25.137-92-14 )
-Debugging mode is enabled.
-When connected to the PC, If I change from Charging to Transfer Files, my phone doesn't show up as another drive where I can transfer files and also gets listed as MTP (Exclamation mark/Triangle) under "Other Devices"
-Windows 10. Updated.
Anyone has been through that? Any ideas, tips, solutions or workaround would be appreciated.
Use "Fastboot Reboot Bootloader" device will go to bootloader automatically without the need of switching off.
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
might be a long shot but i read somewhere else that a person had to type
fastboot -i 0x2e17 < zip/file here >
sorry ; all i know to try.
good luck
maybe @IronRoo can help.
I had the same issue but installed the driver from here and it worked.
https://essentialsupport1493251565....015490828-Windows-Drivers-for-Essential-Phone
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
Connect in fastboot mode and then restart phone with plugged in condition, see if it gives any driver notification.. if dosent then connect the pbone as media device it would show driver disk, you may install driver from there.
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
If non of the above work uninstall all phone drivers & or any other phone connection software that installs phone drivers also eg Samsung Kies/Connect then reinstall Essential drivers, though haven't read about conflicts in recent years ....(Also try different USB ports pref on direct to mother board, people have suggested in the past)