Database Users

Unable to flash anything with fastboot

Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.

pfederighi said:
Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.
Click to expand...
Click to collapse
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?

gee2012 said:
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?
Click to expand...
Click to collapse
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.

pfederighi said:
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.
Click to expand...
Click to collapse
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro

Solved
gee2012 said:
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro
Click to expand...
Click to collapse
So. I solved the problem. I now feel like an idiot.
I plugged my phone into a Windows system and a nice notice popped up saying that my device could run faster if it was plugged into a USB 2.0 port. Then it dawned on me that only a few of the ports on my computer are 2.0 and that I had tried one of them previously but with an extension cable (because it's in the back and hard to reach). I unplugged the extension cable and plugged the USB cable directly into the port and all was well.
I hope that others who have had this issue find this useful.
Thank you for your help.

Bricked Oneplus 2 Not Connecting To PC

- How My Phone Got Bricked?: (Chinese Version Oneplus 2) I Was On Oxygen OS 3.0 And TWRP 3.0 And I Decided To Flash The Resurrection Remix ROM, I Did A Full Wipe And I Installed The Rom And It Failed To Installed The ROM. Now My Phone Is In A Bootloop With No OS Installed. I Have The Chinese Version OP2
- Current State Of My Device: My Device Is In A Bootloop With No OS Installed, I Did Notice That My Phone Was Not Being Recognized VIA Fastboot & ADB On My PC. I Went Fastboot Mode And My Phone Is Not Being Recognized By PC, And I Went To TWRP, ADB Was Not Working And ADB Sideload Is Not Working. I Also Tried A USB OTG With A USB Drive And Still TWRP Recovery Is Not Recognizing It. How Ever When I Connect My Device To PC And Check Device Manager And Press Scan For Hard Ware Changes My Device Shows Up As "COM 1". I Also Did Try To Put My Phone Into Qualcomm Mode Trying Alot Of Key Combinations But My Phone Is Not Getting Into Qualcomm Mode Or It Just Might Be Me Since I Heard Its Tricky For The Phone To Get Into Qualcomm Mode. I Did Try One Click ADB And Fastboot Installed And Qualcomm USB Driver, Still No Luck. And I Did Try The MEGA Unbrick Guide. I Have Tried This With 3 Other Computers Which Are All Running Windows 10 And Turned Driver Signature Enforcement Off And Still No Luck, And Also A PC Running Linux Mint And Still No Luck. Please Help Me And I Will Put All Thanks On All Of Your Replies And I Really Appreciate Your Help!
- Whats Working:
- My Device Charges From The PC And Wall
- I Am Using The Official OP2 Cable
- Can Access Recovery + Fastboot
- Turns On But In A Bootloop

I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable

Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?

foomanjackel said:
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
Click to expand...
Click to collapse
Yeah I did try typing ADB devices and Fastboot devices in both twrp and fastboot. I think the issue might be the cable

evertking said:
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Click to expand...
Click to collapse
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week

fahad999 said:
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
Click to expand...
Click to collapse
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.

evertking said:
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
Click to expand...
Click to collapse
My cable did used to work with adb and fastboot before, and I did unlock the bootloader with it before. I think now the cable got broken

Same issue working cable
Same issue... but my cable is working fine. I have a 2nd OP2 and tried the qualcomm connect with my cable and volume up, and worked perfect. More over, I swapped motherboards and still didnt work. I have access to twrp on the phone and I can get into fastboot. But no way to connect to my pc

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.

Oneplus 5 adb sideload not recognize on stock recovery

I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.

extremeinside said:
I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.
Click to expand...
Click to collapse
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver

Pieter20 said:
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver
Click to expand...
Click to collapse
I am also facing same problem...please help me

Does the stock recovery even have adb capabilities?

Help getting ADB to work (solved)

Can anyone help me getting ADB to work for this device. I can get it with every other phone but this one. I have the OnePlus drivers installed but when I type the Command "ADB Devices" The phone isn't listed.

Have you made sure your adb is up to date? Have you tried a different cable or a different port? Also, did you try to see if fastboot detected the device while in the bootloader?
Just trying to get more information so people can help you troubleshoot.

Milly7 said:
Have you made sure your adb is up to date? Have you tried a different cable or a different port? Also, did you try to see if fastboot detected the device while in the bootloader?
Just trying to get more information so people can help you troubleshoot.
Click to expand...
Click to collapse
So I was able to unlock the bootloader while connected. And my ADB is up to date as far as I know. I got it to work with my other devices. I have tried all the ports that I could try and I tried using the stock OnePlus cable as well as a different one but neither worked.

Did you enable adb debugging in developers options?

DaOldMan said:
Did you enable adb debugging in developers options?
Click to expand...
Click to collapse
Yes, ADB Debugging is enabled. Other people have said that switching from File Transfer to PTP solved the issue for them but that didn't work for me.

I solved the issue. I just uninstalled everything then downloaded them again and it fixed the issue.