Database Users

Moto G4 seen by Windows but not by adb in fastboot mode

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.

Bootloop/ADB/Data Recovery - Phone Not Recognized With Correct Drivers

I am trying to recover the data from my old bootlooping LGV20. My drivers are updated. When I plug my current, working LGV20 into the computer, the phone is immediately recognized and the driver is listed as LG v4.2.0, the most current in Device Manager. The phone is labled as its model number in Devices and Printers. When I plug in my old V20 (which has full access to stock recovery and download mode but does not boot) the computer recognizes something is plugged in, but in Device Manager the device doesn't show up. In Devices and Printers the phone shows up, but as "LGE Android Phone".
Summary:
When a working LGV20 is plugged in, it is recognized and the latest 4.2.0 driver is used.
When the bootlooping phone is plugged in and completely off, it is only recognized as "LGE Android Phone"
Not recognized in Recovery mode
Because of this issue, I cannot use adb on the phone to recover my data.
The phone is stock, non-rooted, android 7, LG-VS995. I have the usb debugging option in the recovery menu though the phone bootloops when this is selected.
ADB installed via 15 second installer and SDK.
"ADB Devices" returns nothing.
When in Download mode, "Fastboot devices" returns nothing.
This issue was repeated on a second computer.
USB 2.0 and 3.0 tried.
The phone is recognized in LGMobileSupportTool
In Download mode the phone is recognized as "LGE AndroidNet" in Devices and Printers and as a COM41 port (changed from 7) in Devices and printers.
What do? I'm at a loss and it feels like I've tried everything.
Edit: I've successfully dumped the phone via LGUP, tried flashed a new image, phone is still bootlooping. Is there any way I can browse the userdata dump file?

Device not recognized in Bootloader

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".

Fastboot not finding device

Hey, I just bought an S7 Edge SM-G950U, the att&t version, SM-G950A. I heard some say that it's not possible to unlock its bootloader, but the OEM unlock option turned out to be available in developer options. However, I'm having a hard time properly installing its drivers, whichever adb driver I use, the driver still shows a yellow warning and the error is that the device can't be started. The device shows up with adb devices when the device is on, but it doesn't neither with fastboot devices nor adb devices when it's in download mode. I'm trying to install TWRP, the hero 2 version. Any help would be appreciated. Thanks in advance

If you in Windows Device Manager find any device with yellow mark right on the device, then the driver installed for it isn't suitable: uninstall it, get Samsung USB Driver and install it.
Samsung devices don't know of a Fastboot mode: there it's called Download mode. You can't run any Fastboot command in this mode.
ADB operates on Android OS, not on device's bootloader, hence it's not working when running the device in Download mode.

Thanks for the prompt reply. I used a different laptop and managed to install the drivers properly, no warnings. However, the result is the same. You mention how I can't run fastboot commands in Download mode, where can I run them? Only Odin is working in that mode now, but I gotta try to unlock the bootloader. A lot of people are saying that this model can't be unlocked, even though the OEM unlock checkbook in the Developer settings is there. Any advice is appreciated

Up

Gearninja said:
Up
Click to expand...
Click to collapse
Down

Question Nothing Phone 1 hard bricked (Edl Mode)

Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?

pogradecari said:
Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
Click to expand...
Click to collapse
Try holding power+volup+voldown with the phone unplugged from a computer.
If it doesn't work, let me know.

how to boot to edl mode ??

Try this :
Install ADB and Minimal Fastboot drivers through which Windows will recognize your Device.
Enable USB Debugging on your Android Device. You can do this simply by following the given direction:
Settings > About Phone > tap 7 times on the Build Number. This will enable Developer options on it.
Now, again go back to the main Settings > Developer options > USB Debugging and Enable it.
Connect your smartphone with your PC via a USB cable.
Open Command Window by the press and hold Shift Key + right-click of your Mouse.
Choose Open Command Window here.
Type the following command and press the Enter button to check whether the device is connected or not.
" adb devices "
You will see a device serial code on the screen. That means it is successfully connected. Then follow the next step.
Type the command from below and hit enter to Boot into Download Mode (EDL Mode):
" adb reboot edl " or "fastboot oem edl" or "fastboot reboot-edl" or "fastboot reboot edl"

muppetz said:
Try this :
Install ADB and Minimal Fastboot drivers through which Windows will recognize your Device.
Enable USB Debugging on your Android Device. You can do this simply by following the given direction:
Settings > About Phone > tap 7 times on the Build Number. This will enable Developer options on it.
Now, again go back to the main Settings > Developer options > USB Debugging and Enable it.
Connect your smartphone with your PC via a USB cable.
Open Command Window by the press and hold Shift Key + right-click of your Mouse.
Choose Open Command Window here.
Type the following command and press the Enter button to check whether the device is connected or not.
" adb devices "
You will see a device serial code on the screen. That means it is successfully connected. Then follow the next step.
Type the command from below and hit enter to Boot into Download Mode (EDL Mode):
" adb reboot edl "
Click to expand...
Click to collapse
my phone is bricked while flashing stock rom via fastboot
so unable to boot to recovery or bootloader

To begin with, power off your device. If you can’t do so, then you will have to wait until the battery completely drains out.
Now connect one end of the USB cable to your PC, but don’t attach the other end to the device.
Press and hold the Volume Up and Volume Down buttons together for a few seconds.
Now connect the other end of the device to the USB cable.
Your device will now be recognized as Qualcomm HS-USB QDLoader 9008. You may now flash the device-specific firmware to unbrick it.
Even you have a black screen , PC does recognize your phone . Use only a USB 2.0 port . Verify if Qualcomm USB Driver have been installed on Windows .

muppetz said:
To begin with, power off your device. If you can’t do so, then you will have to wait until the battery completely drains out.
Now connect one end of the USB cable to your PC, but don’t attach the other end to the device.
Press and hold the Volume Up and Volume Down buttons together for a few seconds.
Now connect the other end of the device to the USB cable.
Your device will now be recognized as Qualcomm HS-USB QDLoader 9008. You may now flash the device-specific firmware to unbrick it.
Even you have a black screen , PC does recognize your phone . Use only a USB 2.0 port . Verify if drivers have been installed on Windows .
Click to expand...
Click to collapse
tried these steps but phone goes in 900E mode

OK , look then at this :

muppetz said:
OK , look then at this :
Click to expand...
Click to collapse
it does not work as he just changed the drivers from diagnostic mode to qdloader mode

pogradecari said:
Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
Click to expand...
Click to collapse
Maybe it's too late already but you can unbrick the phone with this tool
Unbrick / Flash Stock Rom (1.1.7 global) QDLoader 9008 fix | EDL Mode fix
Hi everyone, If your phone (1) does not react on any of yours actions. You may have the same problem. This is an instruction how to fix it without Disassembly. ‼️ Do this at your own risk, I am not responsible for any damage that may occur to...
forum.xda-developers.com

none of these will work

pogradecari said:
none of these will work
Click to expand...
Click to collapse
Why? Have you tried?