When I connect my OP2 it it does nothing... but when I connect OnePlus 1 it works. Adb and fast boot tools installed.
I can not even see the files noting pops up when I connect it, nothing...
Related
I just picked up a Nexus 7 1st Gen WiFi 16GB running 4.1.1 and all was working well on it. I configured it, played with it a bit,even rebooted it once and then left it to charge for a while. I then decided to unlock the bootloader and root it. I enabled usb debugging, connected it to my laptop and issued adb reboot bootloader from my platform-tools in my Android sdk folder. The tablet rebooted, but instead of booting into the bootloader I got a message saying No USB Cable Connected with a question mark and an unknown device in Windows 7 Pro x64. Using NRT I found the correct driver and now I have an android with a hard hat on it with a message saying Wait for Download. Power + Down doesn't get me anywhere except the same messages. Power + Down + Up doesn't work either. Now I'm stumped. 'ADB devices' doesn't see it nor does fastboot. Anyone have any pointers?
Kage_
I am trying to connect my Note 3 to my computer and it will not mount as a device that is visible under windows. It was taken for service and when it came back it only connects to the PC as an ADB device, but not MTP when it is fully booted. I can flash firmware while in Odin, I can connect in bootloader mode, I just can not make it visible to transfer files from the computer directly to the phone via cable. Under device manager it says 'SAMSUNG Android ADB Interface'. USB debugging changes nothing either. My S3 shows ADB and MTP but the Note does not. I have attempted with multiple cables on 2 computers and get the same result. If anyone has a suggestion of a way to fix this without having to wipe again, I'd love to hear it. Thanks in advance.
The other day I was trying to flash my 6p back to stock so I can sell it, and I was flashing everything through cmd, until all of a sudden cmd stopped working towards the end for some reason. Now my phone only boots into fastboot mode and is NOT being detected by my pc. When it's plugged in, the fastboot menu says to connect the data cable. I've tried restarting my computer and reinstalling the drivers, but nothing seems to work. When I go into cmd and type adb devices, nothing shows up when it's plugged in, and device manager doesn't show any changes whether it's plugged in or not.
I've called local cellphone repair shops, but apparently if it's not Samsung or iPhone they can't help
Btw I've searched the forums and haven't found a solution to this problem.
Robertdudeman said:
The other day I was trying to flash my 6p back to stock so I can sell it, and I was flashing everything through cmd, until all of a sudden cmd stopped working towards the end for some reason. Now my phone only boots into fastboot mode and is NOT being detected by my pc. When it's plugged in, the fastboot menu says to connect the data cable. I've tried restarting my computer and reinstalling the drivers, but nothing seems to work. When I go into cmd and type adb devices, nothing shows up when it's plugged in, and device manager doesn't show any changes whether it's plugged in or not.
I've called local cellphone repair shops, but apparently if it's not Samsung or iPhone they can't help
Btw I've searched the forums and haven't found a solution to this problem.
Click to expand...
Click to collapse
Can you enter recovery?
No I can't enter recovery
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p.
this situation is the same when I connect the phone when it is alive.
I have installed adb and fastboot with this software
https://forum.xda-developers.com/showthread.php?t=2588979
with the 1.4.3 version it shows in the end of the process "0 files copied" and then I tried the 1.3 version and it showed that 4 files were copied but it also showed an error.
I have also downloaded ADB from google site but it does not work either.
When I try to open the powershell in a folder where I have downloaded an img and type in a fastboot command the computer doens't recognize any type of command.
So if anyone can help me ill be glad.
Thanks in advance,
Matan.
matan4442 said:
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p. Matan.
Click to expand...
Click to collapse
What is the new device identified as....Qualcomm HS-USB QDLoader 9008? Your phone may be stuck in EDL mode. If that is the case you need to search XDA and attempt solutions for that problem first.
Did you previously have your PC setup properly with the correct USB drivers and it was working OK, or just now trying to get your dead phone to communicate? If the former it may be the EDL issue above. If it was the latter, the communication problem may just be the drivers were never set up in the first place. Have you tried a different cable or port on your PC, or another PC?
With no access to the OS you will be unable unlock the bootloader or access to ADB because those have to be enabled FIRST in the OS, so there's no helping you here until you can actually boot into the OS. Do you have access to Recovery mode? Tried a factory reset? If you don't have recovery, that was a major omission.
Yesterday I managed to unbrick my x722 from QFIL, but the windows doesn't recognize it, i've tried different USB ports, different cables, different PCs, but nothing happens, the phone doesn't show on Device Manager, i even installed windows from zero, but the phone is still not recognized, he only connected the first time, then was no longer recognized, I let the battery die and turn on, but nothing, i don't know what to do anymore
EDIT 1: ok, I was able to connect after leaving it away from USB for a while, but it only connects once and then windows no longer recognizes
EDIT 2: By doing the same thing of keeping the phone away from the cable for a while, I was able to make the computer recognize, but not yet recognize fastboot, but the windows recognize as ADB Interface with a yellow triangle
EDIT 3: I was able to install TWRP by the all in one tool, I was connecting the phone to the computer until it recognized, I rebooted straight to the bootloader, unlocked my bootloader and then installed the TWRP, however, I couldn't get to TWRP yet, another 2 or 3 hours I'll try again
EDIT 4: i finally got it, computer recognized it, i used the all in one tool, i flashed twrp, i installed the rom via adb sideload and here we are, the phone is alive
I had a problem similar but it was the USB port was dirty I turned it off and cleaned the port carefully with a needle to get the lint out and then with a old toothbrush that had a drop of 90% rubbing alcohol on it...