Related
My laptop won't recognize my nexus 7. It's running Windows 7. I looked up possible solutions on Google and none really worked. Help?
Sent from my Nexus 7 using Tapatalk HD
Which ones did you try?
danvee said:
Which ones did you try?
Click to expand...
Click to collapse
I tried using a different cord, plugging the cord into different USB ports, rebooting the device as well as reinstalling the drivers.
Then you haven't tried everything yet
A different computer? (will verify if it's the computer)
Uninstalling all USB drivers then reinstalling them?
Watching what happens in Device Manager when you plug in?
Switching debugging mode on or off on N7?
danvee said:
Then you haven't tried everything yet
A different computer? (will verify if it's the computer)
Uninstalling all USB drivers then reinstalling them?
Watching what happens in Device Manager when you plug in?
Switching debugging mode on or off on N7?
Click to expand...
Click to collapse
One of those options, I held off on since I was confused on how to exactly do it.
I can't really use a different computer because I'm trying to move around 15 GB of music located on the laptop I'm trying to get to recognize the Nexus 7 ..and the other computer is damaged lol.
The second option is what I was confused on. How would I go about doing this?
I'll try the third and fourth now.
I switched to USB debugging and it installed some drivers again. "Google Nexus 7 ADB Interface Installed" It said this when before I turned on USB Debugging. Still doesn't show up as a drive if it's supposed to.
You need the other computer long enough to verify if the N7 is Ok.
You're not going to be transferring stuff.
Just a diagnostic step. Any computer running XP-8 will do.
I'd do that before playing with the drivers. You've got to have access to another computer somewhere for 3-4 minutes.
USB Driver Uninstall :
http://www.faqforge.com/windows/uninstall-usb-drivers-on-windows-7/
http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
Google will turn up others, but these should get you there.
---------- Post added at 05:05 PM ---------- Previous post was at 05:01 PM ----------
It should show up as an MTP device.... http://android-ios-video-tips.com/how-to-transfer-files-to-your-google-nexus-10-nexus-7-from-pc/
I tried uninstalling drivers through device manager before and installing them by connecting the tablet back into the computer and still nothing.
Should the Nexus 7 ADB thing be showing up under SAMSUNG Android Phone? (edit)
*Edit again*
I got it to work by checking "Delete Driver Software" when uninstalling the drivers from Device Manager. It's not showing up under SAMSUNG Android Phone anymore but I think that's because I havent connected my s4 yet. Thanks for the help!
Not unusual.
Another interesting link.... http://forum.xda-developers.com/showthread.php?t=2213688
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
Idkwts said:
I tried uninstalling drivers through device manager before and installing them by connecting the tablet back into the computer and still nothing.
Should the Nexus 7 ADB thing be showing up under SAMSUNG Android Phone? (edit)
*Edit again*
I got it to work by checking "Delete Driver Software" when uninstalling the drivers from Device Manager. It's not showing up under SAMSUNG Android Phone anymore but I think that's because I havent connected my s4 yet. Thanks for the help!
Click to expand...
Click to collapse
I was just going to add that sometimes 'delete' is preferable to uninstalling.
---------- Post added at 05:19 PM ---------- Previous post was at 05:18 PM ----------
Glad it all worked out. :thumbup:
Idkwts said:
I tried uninstalling drivers through device manager before and installing them by connecting the tablet back into the computer and still nothing.
Should the Nexus 7 ADB thing be showing up under SAMSUNG Android Phone? (edit)
*Edit again*
I got it to work by checking "Delete Driver Software" when uninstalling the drivers from Device Manager. It's not showing up under SAMSUNG Android Phone anymore but I think that's because I havent connected my s4 yet. Thanks for the help!
Click to expand...
Click to collapse
Have you tried looking under my computer and seeing if it shows up there? On my friends laptop it doesn't show on bottom but shows up under my computer.....idk this would help but danvee listed everything I could think
Idkwts said:
I tried uninstalling drivers through device manager before and installing them by connecting the tablet back into the computer and still nothing.
Should the Nexus 7 ADB thing be showing up under SAMSUNG Android Phone? (edit)
*Edit again*
I got it to work by checking "Delete Driver Software" when uninstalling the drivers from Device Manager. It's not showing up under SAMSUNG Android Phone anymore but I think that's because I havent connected my s4 yet. Thanks for the help!
Click to expand...
Click to collapse
I had a similar problem.
My Nexus 2013 LTE model was connecting perfectly but using the same port the 16 GB version was not able to show up.
Checked the device manager and it did appear under Samsung Android device. Deleted the drivers and got them to install again after connecting.
Now the Nexus 7 appears under portable device and works perfectly.
Thanks for the idea
I have the same problem
idkwts said:
my laptop won't recognize my nexus 7. It's running windows 7. I looked up possible solutions on google and none really worked. Help?
Sent from my nexus 7 using tapatalk hd
Click to expand...
Click to collapse
can someone help me, i have try everything in different laptops different usb, but nothing seems to work, please someone help me
I used the OTA update and it went (as far as I can tell) without any problems. I tried to install TWRP, but when I use Wug's toolkit, or N-Cry, they cannot detect the phone in ADB. I tried removing and re-installing the drivers, but no luck. It worked fine before the update to 4.3, but obviously something has changed.
It will see the phone if I'm in fastboot, just not when the phone is up and running normally. Is this normal with the 4.3 update (I know not being able to get root at the moment is)?
Have you enabled USB debugging?
Sent using xda-developers app
chromium96 said:
Have you enabled USB debugging?
Click to expand...
Click to collapse
Yes, sorry, should have mentioned that...it is.
I tried un-checking the USB debugging box and re-checking it, un-plugging and pluggin the USB back in, rebooted computer and phone several times as well.
Did you update adb and fastboot as well?
Try updating your sdk or at least the platform-tools
I just updated the drivers using Wug's toolkit, is did that update adb and fastboot at the same time?
I'll try and update sdk and see if that helps.
I just tried installing Wug's toolkit on another computer running W7 (previous one on XP), and it seems to work great now It did ask me about alowing the RSK (I think), but then it seems to work fine. I was also able to use N-cry and get root back
Now I have to figure out how to install TWRP. I tried Wug's, but it didn't stick, when i try to boot into recovery it just give the android on his back with a red exclamation mark.
Same problem here. Followed the steps in the toolkit to install drivers, and the test always fails. The phone is seen by windows as a nexus 4, and no adb device nowhere to be seen.
I'm on Windows 8 BTW.
---------- Post added at 07:03 PM ---------- Previous post was at 06:49 PM ----------
Additionnal information : when i connect the phone, it appears as "Google Nexus ADB Interface" in the device manager. I seriously don't get it.
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
Another : while messing aroung with the toolkit, i ended up on a tutorial about how to activate USB debug on my phone.
USB Debug is activated, but there is this step : 4.) You will see a prompt with your computer fingerprints [...]
I never get prompted for anything, would be on my computer or on the phone. Am i missing anything ?
---------- Post added at 07:25 PM ---------- Previous post was at 07:08 PM ----------
Alright sorry for spamming but finally found a solution : the phone has to be connected to the computer in camera mode -_-
Hello!
My problem
My problem is that when I connect my Mako to my PC, it repeatedly connects, disconnect and reconnects every 2-3 seconds. The hardware icon flashes in the taskbar and I hear the connect/disconnect sound played. This is a very weird behavior I have never seen in any other device. It also means that any ADB operations are rendered impossible because the connection is severed constantly.
My phone
Stock Mako
Also tried after having installed CM12
My computer
Windows 10 (dev preview)
What have I tried?
The problem only appears when the phone is powered on fully or in recovery mode. In bootloader mode, it is stable (but here, obviously, I have no ADB connection). This lead me to believe it was a problem with my ADB drivers, so I tried the following:
Different USB ports on the computer
Reinstalling Google's ADB drivers
Installing custom ADB drivers
Removing all ADB drivers (this prevents the phone from connecting to ADB entirely)
Troubleshooting using http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396 and other guides
Additional question
I could technically do without ADB, but the reason I want it is so that I can clear my phone and install ROMs cleanly with sideloading (without having to boot into the phone, download the zip and then reboot). I'm quite new to flashing -- is it usually a bad idea to boot the phone and download the zip and then install? Am I right in saying it would be better to sideload or push the zip onto the device after a complete format? Or is that just an incorrect thing to assume.
I will be trying with a new USB cable in the next few days, hopefully that should solve it.
Doggie52 said:
I will be trying with a new USB cable in the next few days, hopefully that should solve it.
Click to expand...
Click to collapse
What happens when you fastboot devices in the bootloader?
For sure try a new cable, if it does not help, you are likely facing a hardware failure like in the following post:
http://forum.xda-developers.com/nexus-4/help/nexus-4-computer-t3048983
---------- Post added at 08:53 AM ---------- Previous post was at 08:39 AM ----------
and here
http://forum.xda-developers.com/google-nexus-5/help/usb-fastboot-adb-driver-issue-t3055262/page2
joegestes said:
What happens when you fastboot devices in the bootloader?
For sure try a new cable, if it does not help, you are likely facing a hardware failure like in the following post:
http://forum.xda-developers.com/nexus-4/help/nexus-4-computer-t3048983
---------- Post added at 08:53 AM ---------- Previous post was at 08:39 AM ----------
and here
http://forum.xda-developers.com/google-nexus-5/help/usb-fastboot-adb-driver-issue-t3055262/page2
Click to expand...
Click to collapse
Fastboot works fine -- when in the bootloader, my phone appears to be working just as normal. The connection is stable and fastboot can detect the device and flash to it as well.
I will try the cable and report back. Thank you for the tip!
Kind of late but if you are still experiencing the problem, try using USB 3.0 or 2.0 because I experience the problem too when I use the dedicated charging port on my laptop.
sent from Le Nexus 4
It turned out to be the cable that I had which was not good! I bought a stock Nokia cable, actually, which worked flawlessly (and charges at 820mA!!).
Good to know you've rectify the problem
from Le Nexus 4
Doggie52 said:
It turned out to be the cable that I had which was not good! I bought a stock Nokia cable, actually, which worked flawlessly (and charges at 820mA!!).
Click to expand...
Click to collapse
Excellent :good:
So if you been messing around with your fire and got to the point that it wont want to get past the loading screen or something or you may have messed up during the root process you can use these steps to restore your Fire
MOD EDIT: THE FIRMWARE LINKED HERE IS NOT SAFE AT THIS TIME, LINK REMOVED AND THREAD CLOSED.
Steps.
1. MAKE SURE YOU HAVE ALL YOUR ADB DRIVERS INSTALLED!! and if you dont know how to check this thread
2. Download the amazon frimware above and keep it where you can flash it.
3. Boot into recovery (Volume Down + Power at the same time)
4. Select "adb sideload" or whatever it says using your volume keys and press the power to select
5. Now adb sideload <frimware>.bin
6. Its probably gonna take 5- 10 minutes so be patient and then once the recovery options come up make sure you wipe every thing and cache as well
7. Reboot gonna take another few minutes BE PATIENT!!
8. Now your back to your stock frimware.
I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:
Darkside1984 said:
I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:
Click to expand...
Click to collapse
Try installing ADB drivers in Device Manager while the Fire is in recovery. If you do it correctly, when you do ADB Devices, it should come up as Sideload.
Sent from my KFFOWI using Tapatalk
Troubleshooting
Device may not connect to PC until you select apply update from ADB,
check device manager, Fire should be listed ADB sideload or adb composite interface, when in recovery mode
If device is in adb sideload mode
Code:
adb devices
should return
Code:
G000HXXXXXXXXXXX.........sideload
if not drivers are not correct
Manually Fix Drivers
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Error
cannot read 'adb sideload update-kindle-37.5.2.2_user_522053820.bin'
Make sure Firmware.bin file is in same location, that is listed in command prompt
(ex: C:\Program Files (x86)\Minimal ADB and Fastboot>)
sd_shadow said:
recheck device manager, drivers are not correct, Fire should be listed adb composite interface, when in recovery mode
Click to expand...
Click to collapse
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Looking for a miracolous hard factory reset...
EDIT: I see that the battery is low. Does this have something to do with Recovery troubles?
i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
Darkside1984 said:
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Click to expand...
Click to collapse
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
Darkside1984 said:
I see that the battery is low. Does this have something to do with Recovery troubles?
Click to expand...
Click to collapse
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.
sd_shadow said:
i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.
Click to expand...
Click to collapse
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...
Darkside1984 said:
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...
Click to expand...
Click to collapse
try
Code:
adb version
---------- Post added at 12:38 PM ---------- Previous post was at 12:38 PM ----------
should get
Code:
Android Debug Bridge version 1.0.32
Revision d15680a64678-android
sd_shadow said:
try
Code:
adb version
Click to expand...
Click to collapse
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?
Darkside1984 said:
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?
Click to expand...
Click to collapse
try link in my Using adb post
Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!
Darkside1984 said:
Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!
Click to expand...
Click to collapse
great
care to post some details about what worked?
Drivers version?
adb method?
Sent from my KFFOWI using Tapatalk
after side loading I needed to switch off the device and restart in order to start the final "Installing the latest software"-sequence
sd_shadow said:
great
care to post some details about what worked?
Drivers version?
adb method?
Click to expand...
Click to collapse
Sure!
I deleted my adb folder and follow the steps in your thread here. So it got the right adb version (1.0.32) and I finally could sideload properly the bin file. I think that the point is that PC just recognizes the Fire (as ADB composite) when you are into 'adb sideload' option, not in the recovery main menu.
5th Gen Kindle Fire - MT65xx Preloader problems
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3238740
[HOWTO] How to restore firmware on your device + Amazon Firmware
hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
Following your comment, I ran the .BAT while watching Device Mgr. Prior to running it, I had the Android device apparently successfully installed. It had its own folder in Dev Mgr without any [!]. Running the .BAT, that disappeared and Android migrated down to Other Devices. It's now next to the same Unknown Device that I haven't been able to update drivers for.
I tried pointing both to the latest_USB_drivers zip from Shadow's recommended thread. According to Win7, it's 'unable to install' from that unzipped folder or any of the others I've pulled from various threads.
fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
With the Fire disconnected, I booted to recovery (Volume Down + Power) and got a list. Not knowing what to pick, I chose the Bootloader option. It started to boot in FASTBOOT mode. Plugged it in, went to Dev Mgr. Both Android Device and Unknown Device showing in Other Devices. Pointed the Android Device driver to the latest_USB drivers from your other thread. Windows says unable to install your Android. Tried same thing with Unknown Device. Unable to install.
So I recently booted my Oneplus 5 into fastboot, just because.
And for some reason my device name is QC Reference Phone.... what the heck!
Has the factory QC phone somehow ended up being packed up and shipped out to me?
Can anyone else check their device and see if it says anything similar.
Got a pic?
I have same thing
Same for me.
same here and cant get fastboot working also can flash twrp
Same here and it is also strange that I can't connect with my windows.
- the cmd: Fastboot devices
doesn't return the serial number.
---------- Post added at 03:10 PM ---------- Previous post was at 03:00 PM ----------
hounter17 said:
same here and cant get fastboot working also can flash twrp
Click to expand...
Click to collapse
Did you already got an solution for your fastboot?
hmm wierd mine said the same
i can boot into fastboot
so i have allready unlocked oem an rooted
Unable to connect OnePlus 5 to windows 10, Fastboot reads phone as QC Reference Phone
I am having the same issue. Oneplus 5 is not being recognized as a valid USB device in windows 10.
In fast boot the device shows as a QC REFERENCE PHONE.
Please Help.....do i need a replacement ?
hounter17 said:
same here and cant get fastboot working also can flash twrp
Click to expand...
Click to collapse
didt u enable debug an oem in developer before u enter fastboot
Jonnyn93 said:
So I recently booted my Oneplus 5 into fastboot, just because.
And for some reason my device name is QC Reference Phone.... what the heck!
Has the factory QC phone somehow ended up being packed up and shipped out to me?
Can anyone else check their device and see if it says anything similar.
Click to expand...
Click to collapse
I am having the exact same issue...
Got the same problem. After some reboots and USB Debugging on/off the device was shown as a drive in Windows. Then there was a driver in this Drive. Installed. Problem solved. My Phone is shown as QC Reference Phone but Everything working great yet. (Fastboot, Sideload, USB Debugging, File Transfer)
When i connect my phone with te pc I hear te tone from recognizing or making contact ,but there is no drive visible as a folder in explorer. Ofcourse In die all settings in the developer options.
I'm missing the right driver. But I tried several.
Oneplus 5 showing up as Qualcomm HS-USB Diagnostics 900E
I got my OP5 today in the mail and the phone itself is working fine.
Although when connected to PC(Windows 10 64bit) it says "USB device not recognized". - Have already tried to set USB to MTP in developer Options.
And the device connected Reads "Qualcomm HS-USB Diagnostics 900E", did i receive a bricked Phone from the company ?
PLEASE HELP.
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Spider1996 said:
Got the same problem. After some reboots and USB Debugging on/off the device was shown as a drive in Windows. Then there was a driver in this Drive. Installed. Problem solved. My Phone is shown as QC Reference Phone but Everything working great yet. (Fastboot, Sideload, USB Debugging, File Transfer)
Click to expand...
Click to collapse
@Spider1996 :
This is my issue, any thoughts on that.
I got my OP5 today in the mail and the phone itself is working fine.
Although when connected to PC(Windows 10 64bit) it says "USB device not recognized". - Have already tried to set USB to MTP in developer Options.
And the device connected Reads "Qualcomm HS-USB Diagnostics 900E", did i receive a bricked Phone from the company ?
PLEASE HELP.
This was my Problem too. The normal USB Drivers from other devices are not working. Try to delete the driver in the device Manager from Windows and replug (with usb Debugging enabled and disabled) until a new drive is shown in Windows. After that install one of the .exe from this Drive. This helped me
---------- Post added at 04:45 PM ---------- Previous post was at 04:34 PM ----------
There are the Drivers from my Device Folder (Windows, Mac and Linux)
https://www.dropbox.com/s/nc7mgnj1k8kli92/OP5 Drivers.rar?dl=0
Try to use them for your OP5 in the device manager.
I think your device is not bricked/corrupted whatever
-fluffy- said:
didt u enable debug an oem in developer before u enter fastboot
Click to expand...
Click to collapse
yes i did it
I have the same thing. QC reference phone, no BL version or baseband version shown in fastboot mode. I also could not flash TWRP. I could fastboot reboot and see the device's serial # in fastboot but it wouldnt report the target size and errored out saying the file was too big for the target or something along those lines. I updated my ADB and fastboot EXEs just in case. What ended up working was switching USB ports on my laptop, despite the fact I use that one all the time and it was still recognized by fastboot. Hope this helps.
hibby50 said:
I have the same thing. QC reference phone, no BL version or baseband version shown in fastboot mode. I also could not flash TWRP. I could fastboot reboot and see the device's serial # in fastboot but it wouldnt report the target size and errored out saying the file was too big for the target or something along those lines. I updated my ADB and fastboot EXEs just in case. What ended up working was switching USB ports on my laptop, despite the fact I use that one all the time and it was still recognized by fastboot. Hope this helps.
Click to expand...
Click to collapse
just the same happend to me, so u finally flash the recovery and root or nay??
y try all the usb ports and nothing...
hounter17 said:
just the same happend to me, so u finally flash the recovery and root or nay??
y try all the usb ports and nothing...
Click to expand...
Click to collapse
I got the recovery to flash yes. It took me a while. It didn't stick because I didn't delete that file you have to delete but it flashed and booted into TWRP eventually.
hibby50 said:
I got the recovery to flash yes. It took me a while. It didn't stick because I didn't delete that file you have to delete but it flashed and booted into TWRP eventually.
Click to expand...
Click to collapse
so the only solution is to try in different usb plugs till it goes on someone?
wich file i must delete?
pritamk88 said:
I am having the exact same issue...
Click to expand...
Click to collapse
So maybe it isn't an issue, I'm not sure.
Oneplus replied "QC means qualcomm". So does this mean the phone is based off of a qualcomm reference board, and they just slapped it into a oneplus shell....