[help] widows, ubuntu, cannot recognise OP 3 fastboot. - OnePlus 3 Questions & Answers

Problem
When I plug my phone into usb 2.0 ,usb 3.0 doesn't have any popup and I can't see it in inside device manger, windows shows "The last USB device you connected to this computer malfunctioned and Windows does not recognise it. " error message and I can't see my phone through fastboot.
Side Problems
I updated to cm14 which made my recovery, (twrp) just black screen and when i went back to cm13 it made my normal boot black screen too.
Note
Have tried multiple Cables. standard OP 3 cable and off brand white one.
Have tried many usb ports.
Have tried three computers. two Win 10, one ubuntu 16.04
Have got the Media Feature Pack for windows 10
Have got latest ADB (on all computers)
Have got latest Fastboot (on all computers)
Have got latest OnePlus 3 drivers
Thank you for reading, any suggestions or links to other threads would be very much appreciated.

laal75 said:
Problem
When I plug my phone into usb 2.0 ,usb 3.0 doesn't have any popup and I can't see it in inside device manger, windows shows "The last USB device you connected to this computer malfunctioned and Windows does not recognise it. " error message and I can't see my phone through fastboot.
Side Problems
I updated to cm14 which made my recovery, (twrp) just black screen and when i went back to cm13 it made my normal boot black screen too.
Note
Have tried multiple Cables. standard OP 3 cable and off brand white one.
Have tried many usb ports.
Have tried three computers. two Win 10, one ubuntu 16.04
Have got the Media Feature Pack for windows 10
Have got latest ADB (on all computers)
Have got latest Fastboot (on all computers)
Have got latest OnePlus 3 drivers
Thank you for reading, any suggestions or links to other threads would be very much appreciated.
Click to expand...
Click to collapse
Normally when your phone is not recognised, it indicates a driver problem. On Win10, it happens invariably. So search and find ways of properly installing OP3 drivers on Win10. There are umpteen threads in OP3 sub forum.
On black screen, are you using TWRP 3.0.2-23? If not search for it and install it. If nothing works, go to the Mega Unbrick Guide.

Hm thats odd, but its recognized in MTP mode?
I would suggest to only use ubuntu for that cause you don't have that struggle with drivers.. I will flash TWRP on my OP3t now and report back if its working

Black screen on recovery is because of the firmware compatibility with the recovery. Use eng.stk's modded twrp.
If "fastboot devices" doesn't return you anything, try typing the device id after fastboot. Like if you want to flash a recovery, type fastboot -i 0x2a70 flash recovery ---.img
If that doesn't work out, I don't know of any other workaround. If you find a fix, do let us know.

*Mod, please delete this.*
Unwanted post.

How did you go about installing fastboot drivers for Ubuntu? If your device isn't recognised in fastboot I'm sure it's a driver issue.

Needed to reinstall drivers, by disabling device and installing drivers then plugging my phone in.
Phones fine now.
Thanks for the help.

Related

[Q] Craziest thing: can't get USB drivers to install in recovery or booted OS mode

I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.

HTC One m8 (Android 6.0) not connecting to computer

Hi,
So I got fairly sick of HTC's Android 6 update (Crazy amount of bugs) and decided to install CM-13.
A problem arose then when I tried to unlock my bootloader, the computer wouldn't detect my the one m8 in fastboot mode even with android studio and usb drivers installed or standard mode.
I installed HTC sync manager and still no good.
I tried different cables and different computers (one win 10 the other win 7).
When the phone is in standard mode and connected to the computer the usb symbol comes up and says charging only,
if i click on this and select file transfer mode the screen just greys out and stays like that until i click home/back.
This option comes up only once (I need to reboot to get it again).
I found another thread that says to install "AndroidHtcsync2.apk" I tried this and it didn't work.
Thanks
Maybe, like me, you have a broken USB port that will still allow charging but no data connection
assetttt said:
Maybe, like me, you have a broken USB port that will still allow charging but no data connection
Click to expand...
Click to collapse
That might be it, only thing is i was able to send files no problem a month or two ago before the update.
You need to be in bootloader-fastboot mode for fastboot commands; they won't work booted in OS or in bootloader (I think one of those is what you mean by "standard mode"?).
Other than that, Win7 is more reliable. And USB 3.0 is known to cause issues with USB connectivity on this phone, as well.
Sorry that wasn't clear. I was actually in fastboot mode when sending the commands.
The windows 7 computer I tried it in had USB 3.0 ports as well so that might be it.
However I wiped the phone after failing to flash CM and it fixed most of the bugs I was having trouble with so I might just leave it this way.
Thanks for the help

bricked device

Hi Everyone,
I seem to have bricked a nexus 2013 wifi. At first, it was having movie playback issues so I restored it to lollipop using factory image on the google site. I decided to get OTA up to the latest MM. So far so good. But I though about putting a custom rom to it. So I installed TWRP 3.02 for flo and flashed PN MM with the recommended GAPPS. Kernel was what came with it. It worked fine until this morning when I realized that the touchscreen was not responding. I went to BL mode and into recovery. TWRP came up but touch was not responding as well.
So, I connected the device to my PC. It now shows unrecognized device. It still charges and all that but It is now stuck on the google logo. when I go to TWRP, touch wont work. I have tried another cable, still the same. My N6 is detected without issues using the same PC and cable. Since there are no drivers, I cannot reflash anything...
Any thoughts? Or am I just lucky to have bricked it? Appreciate any inputs that will be thrown in this direction. Cheers!
Hi, N7 motherboard gets touch, USB, accelerometer and compass data via the wide silver cable which often suffers from poor contact. Please try this first. If it is still not fixed, then in fastboot mode run and post the output of the following commands:
Code:
fastboot getvar all
fastboot oem gpt-info
fastboot format cache
Thanks for the help. hmm.. i pressed that part and it booted up to PN, touch is working as well. Not sure if that fixed it but if it happens again im gonna try to press that area. however, its still not detecting the device. I see it in Device manager, it says unknown device and will not take any driver, so fastboot is not an option for me atm.
so just an update. when I was able to boot up, it will not go landscape no matter what. I downloaded check my android and it the tests for compass and sensors were not responding. I decided to open the back cover, it was fairly easy. The thing is I have not the right tools to reseat the silver flex cable and I fear I might damage it, so I tried putting folded paper on to where it connects to on both ends. Now the thing works with landscape and so far, have not experienced touch issues or no boot issues.
I still do not have access to fastboot, though, as it still isnt detected by my computer. so I may have to stick to putting stuff to it over the air. Or should I just reseat that cable? Does it just slide out?
welxiii said:
I still do not have access to fastboot... should I just reseat that cable?
Click to expand...
Click to collapse
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
noahvt said:
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
Click to expand...
Click to collapse
The next step:
disconnect the ribbon cable from both the mobo AND daughterboard
spray the cable's and PCB connectors' contacts with Electronic Cleaner
reconnect and relock
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
Hi,
I really appreciate the assistance. Well, here's what I found.
[*]What's the VID/PID of the non-detected device? USB\VID_0000&PID_0002\6&688A3B8&0&2
[*]Does ADB work if you start TWRP? I don't think it does. In TWRP, I still get a message on my computer that the device has failed. DM shows the device as unknown usb device (device descriptor request failed)
[*]Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it? no it doesnt. same error as above.
[*]Is an OTG flash drive recognized? yes it does.
[*]Maybe Windows has a driver problem - does it work from live Linux? I'm still working on this. btw the same setup works on my phones and they are detected just fine.
update:
Suddenly its now detected by my pc. I connected my usb otg. At first,. It wasnt detected so I tried the usb on my nex6 and it worked. I connected it back to the 7 and voila! No error and DM now shows it as an android device. Whew!
But I have one question, is it safe to leave the folded papers i placed on both ends of the silver connector?
welxiii said:
Suddenly its now detected by my pc...
...is it safe to leave the folded papers i placed on both ends of the silver connector?
Click to expand...
Click to collapse
Yes.
As I mentioned earlier, the silver cable also connects USB data, so if you experience USB detection problems again, then do full re-seating with clean-up.
Cheers :highfive:
Thanks again for the assistance. Hopefully, it doesn't come to that.
unbricked my google nexus 7 tablet
if anyone has bricked there nexus 7 wifi tablet.....you can now unbrick it with the skipsoft toolkit. my tablet was bricked for awhile (it was stuck on the google logo and when I tried to boot into the twrp recovery it showed the android bot with an exclamation point so I was screwed big time) so I just brought another one (different version). after awhile I gave up hope, but today I decided to unbrick it (or atleast try to). at first I was using the nexus toolkit like I did before and I was having problems with it being recognized via adb and it wouldn't flash the stock recovery.img. than I remembered that I also had the skipsoft toolkit installed on my computer and the nexus 7 tablet was also supported on that toolkit so I decided to give it a try. at first, since I had it plugged in, it wouldn't recognize that it was plugged in not realizing that I had to download all the images and recoveries it needed to be able to root it and return it to stock if necessary so I did that and when I finished installing everything it detected that my device was in fastboot mode. I flashed the stock recovery image and it booted up like it was suppose to. I'm writing this just incase so one has bricked there device and has lost all hope in fixing there mistake. I love android and recently have a lg nexus 5x that's rooted with a custom rom on android 7.0 nougat. android is awesome
who ever developed the skipsoft toolkit....your awesome and thankyou for making this possible.

Oneplus 3 does not connect to pc

my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Evnul000 said:
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Click to expand...
Click to collapse
Windows drivers 100%.
null0seven said:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Click to expand...
Click to collapse
I have tried it on both my PC and laptop with both windows 10. Does not work. My PC also has windows 7 still seems to not work. Are there any other drivers i might be missing?
i have also done some research that you should update your drivers from device manager. I dont see anything related to my device. i went to portable devices nothing and i dont have a other devices section in device manager. Any help?
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
null0seven said:
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
Click to expand...
Click to collapse
i am on the latest twrp. will blu-spark help fix it?
ive also found out theres no kedcom driver when i go to fastboot. i even reinstalled adb drivers to insure its there but it does not pop up.
You'll need to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
I once have kind of youre problem connecting to my laptop (win.10). But, at work, on that laptop, connection was ok (win.7).
I reinstal windows 10 and connection works fine, since.
I allways use latest TWRP & version of rom. I can't tell for sure what it's goin on with youre phone.
If i was in youre situation i format my phone (this will erase ALL in youre phone). And if PC still does not see the phone reinstall windows.
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
dentman said:
You'll bed to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
Click to expand...
Click to collapse
What are the driver links if you have? I already installed the OnePlus drivers.
ninjeratu said:
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
Click to expand...
Click to collapse
I used the OnePlus cable and another cable.
Driver issues win 10
Find the excellent tutorial here on drivers.
For some reason my phone didn't show up but was able to receive commands. It was frustrating because I wanted to use the all in one XDA product but couldn't.
Even if you installed drivers they can be broken!
Do drivers from scratch per xda tutorial. Don't forget reboot!
Try different cables and usb ports! My front ones never seem to work!
Don't just try fastboot commands also try adb. Like I said mine wasn't seen properly yet it took the commands.
Unless your windows is a years old install it shouldn't require reinstall.
Factory phone reset might help.
Best of luck!

Stopped showing up on PC USB connection

Dug my old 2013 wifi 7 out to use on a project. Running a stock ROM, not sure of the version, rooted and unlocked bootloader. I screwed up something installing a new ROM and ended up wiping the system and data partitions. I'm trying to get a ROM onto the device so I can flash it. I can boot into fastboot and TWRP 2.8.6.0. Of course with no system it showed up as an unknown device. While doing the driver uninstall/install dance trying to get the naked driver set to work the tablet just stopped showing as connected to my windows 10 pc. Not like "unknown device" etc, no devices connected at all. Nothing shows on usbdview either. Tried plugging into a windows 7 pc, same thing, even tried a ubuntu live cd boot, nothing. Tried toggling MPT in TWRP on all these attempts. I can't mount USB OTG from TWRP I think its too old of a version. The tablet will charge so I don't think the usb port died. I'm out of ideas. Any suggestions before throwing in the towel?
Get the stable ROM for Flo. Stick Ubuntu on a decent laptop. Get a USB cable that's good for data and look at this instruction: https://itsfoss.com/restore-android-factory-nexus-7-2013-linux/
You want to Root look at this one and follow exactly: https://itsfoss.com/root-nexus-7-2013-ubuntu-linux/

Categories

Resources