Database Users

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

Can't get HD8-6G ADB working properly on my Win7x64 PC

It's weird.
I had my HD8-6G on v5.3.1.0 (now, v5.3.1.1).
I installed the Amazon Fire Drivers that were on the Amazon developer website. But, my Win7x64 PC complained that it still didn't recognize the HD8 device while it was in ADB mode. So, I manually selected the Amazon.com ADB Composite Device for my updated driver. This works ... partially
If I booted the HD8 into "adb sideload" mode, the HD8 was properly recognized, and I was able to install the v5.3.1.1 update. However, the tablet is still not visible when I did an adb devices command. in my ADB / Fastboot shell. I tried running KingoRoot, and the tablet wasn't discovered.
How can I get ADB working properly on Win7x64?

¿GotJazz? said:
It's weird.
I had my HD8-6G on v5.3.1.0 (now, v5.3.1.1).
I installed the Amazon Fire Drivers that were on the Amazon developer website. But, my Win7x64 PC complained that it still didn't recognize the HD8 device while it was in ADB mode. So, I manually selected the Amazon.com ADB Composite Device for my updated driver. This works ... partially
If I booted the HD8 into "adb sideload" mode, the HD8 was properly recognized, and I was able to install the v5.3.1.1 update. However, the tablet is still not visible when I did an adb devices command. in my ADB / Fastboot shell. I tried running KingoRoot, and the tablet wasn't discovered.
How can I get ADB working properly on Win7x64?
Click to expand...
Click to collapse
this might be silly, but make sure you have developer mode enabled/adb enabled. also enable unknown sources in security. I would think it should show up when you issue adb devices..how strange.
* also I like to check stay awake.
Those are the very same drivers (fire usb for everything except recovery, and the android ones for the adb composite for recovery) I used and I'm on Windows 7 64 Bit.
* I just put my device in recovery mode and yeah it says android composite adb interface 10/27/2014 1.4.0.0 Amazon Services
hmm..actually it says the same when i reboot

smokejumper76 said:
this might be silly, but make sure you have developer mode enabled/adb enabled. also enable unknown sources in security. I would think it should show up when you issue adb devices..how strange.
* also I like to check stay awake.
Those are the very same drivers (fire usb for everything except recovery, and the android ones for the adb composite for recovery) I used and I'm on Windows 7 64 Bit.
* I just put my device in recovery mode and yeah it says android composite adb interface 10/27/2014 1.4.0.0 Amazon Services
hmm..actually it says the same when i reboot
Click to expand...
Click to collapse
I have all the same settings you list above, but the ADB device isn't being found.
I also don't get prompted for an RSA key. Could that be related? I may have been prompted previously, but I don't think so. This is the first time I think I did any ADB stuff on this tablet.

¿GotJazz? said:
I have all the same settings you list above, but the ADB device isn't being found.
I also don't get prompted for an RSA key. Could that be related? I may have been prompted previously, but I don't think so. This is the first time I think I did any ADB stuff on this tablet.
Click to expand...
Click to collapse
yes, you must get prompted for RSA key. If you disable usb debugging, then reenable it (with tablet still connected) you should get a prompt and check remember. That definitely is an issue if that never was applied.
* also I like to make sure stay awake is on. In addition, whenever you reboot the tablet, upon rebooting, I like to make sure the screen is unlocked and sometimes you need to quickly unplug it, then replug it back it once it's rebooted for the device to show up in my computer.

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?

Big Big problem - No fastboot with Controller method and pc!!

I try update my nvidia shield tv 2017 but now the System bootloop on Android circles animation (dont start box).
- I try fastboot with Controller but dont work (many, many times)
- I try conect to pc but dont connect device with fastboot
bricked bootloader??
I dont have solutions.... please help.
Sorry my english

Try un plugging the power then plug a USB keyboard in and hold the A and B key and then plug the power back in.

same problem for 3 days, can not enter fastboot mode. my shield is in bootloop

Shot in the dark, but have you tried different USB ports on the computer? I know in my case, some otherwise working ports will not work with the shield. Seems to be very fussy when it comes to which ports I choose. None of my front ports work on this desktop, I have to plug into rear ports in order for my computer and shield to see each other.
Also be sure to use the original cable that came with the shield.

Also make sure USB debugging is on.

Any fix ? Same problem

Have you tried "adb reboot bootloader" in command prompt when the android logo is looping?

I have no Android logo i have no os just twrp and twrp with no access adb and fastboot command dont work on NVIDIA logo

If you put lineage os on a usb stick can twrp read the usb stick? If so, you can install the zip file of lineage with gapps...once that's installed and booted up, you can enable usb debugging in the developers options and fastboot and adb should work again.