Related
I just got my data cable in an accessory bundle from hong kong(ebay). Installed htc sync and when I plug in my phone to the PC I get a usb not recognized error. I tried on a different laptop and same problem. Could it be the generic usb cable?...or did I miss something somewhere?
which os are you using. I believe if you are using win 7 64 there is an additional driver you have to install. I know i did.
windows 7 64 bit. Is the additional driver a separate download or is it in the sense folder??
when you plug it in...does it start charging? do you get the USB connection sound?
if the PC has no response to the phone being plugged in, then try swapping the cable.
if the PC does respond (in any way..lights, sounds, etc) then it's prolly a software issue.
did you actually try doing a google search on this?
something like: evo windows 7 64 "usb not recognized error"
http://forum.androidcentral.com/htc-evo-4g/22285-usb-device-not-recognized.html
http://www.htc.com/us/support/evo-sprint/downloads/
... updated version of HTC Sync
http://community.htc.com/na/htc-forums/android/f/94/tags/Windows+7/default.aspx
http://community.htc.com/na/htc-forums/android/f/94/p/5082/23208.aspx
... a problem with the USB hub.
it was a seperate download i cant find it on my pc but i got it off the guide for adb in development forum. hopefully that works for you.
Thanks for the links magic, but I found those when I actually did search before making this post. None of them worked. I did find a more detailed tut on how to root, so maybe something I missed is in it.
Still havent been able to figure it out. When I connect the device and open device manager I get an !unknown device. I click it and "view drivers" and says none are loaded. SHould I boot into safe mood and try all of this?...or disable driver signature or something??
i've had this issue in the past...in my situation is was a bad port...
you may want to reload everything on the phone though... i've ran into situations in the past were i flash a rom and the usb stops working i am able get the usb to work again by reloading the rom
skuzzie said:
Still havent been able to figure it out. When I connect the device and open device manager I get an !unknown device. I click it and "view drivers" and says none are loaded. SHould I boot into safe mood and try all of this?...or disable driver signature or something??
Click to expand...
Click to collapse
sounds like you just don't have the drivers. they're around here, or, you could update the sdk and the drivers are included in the package. you'd have to do the devmgmt.msc command w7, right click on the device, search for drivers, they're in the sdk usb driver folder.
or, someone around here posted them up somewhere. search.
Thanks for the help guys, I did all of the updates and what not, removed all the associated devices to all usb ports and none of that worked.
I decided to just go the easy route and rule of my generic cable, went to best buy and picked up a new one (data pilot) and it recognized it asap.
Thanks for the help though.
thanks for the update. TBH...the cable was lowest on my list of possible issues.
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
rjsmer said:
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
Click to expand...
Click to collapse
As stated, I have tried to use two other USB cables aside from just the one that came in the package.
Since all cables work on the laptop, but not this computer, I have pretty much singled it out to be a windows or a driver issue. :\
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
scott14719 said:
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
Click to expand...
Click to collapse
PC is i7 920, 12GB DDR3, Intel x58
Laptop is i5 2430M, 6GB DDR3, Sandy Bridge
Both are Win7 Pro, neither have Kies (I always just downloaded the drivers themselves) but I'm downloading it now to give it a try. As of now, nothing recognizes the phone on PC.
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Shuurei said:
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Click to expand...
Click to collapse
Samsung Kies isn't yet compatible with the sgh-m919. Samsung rep told me soon last night
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
SBERG117 said:
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
Click to expand...
Click to collapse
Enabling dev options and USB debugging was the first thing I did once I turned on the phone. Tried it both with and without, still not recognized either way. Still recognized on laptop.
I've also reinstalled windows altogether, since that fixed my issue last time around, but it's no good this time still. Clean install, formatted. No good. Previous steps from first post also taken, still no good. Tried the PDAnet method as well, no good.
At this point I am wondering if it might be an x58 issue, which would really suck, but it's the only thing I can think of given all the steps I have taken.
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
x58 issue
luckyduck69 said:
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
Click to expand...
Click to collapse
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Confirmed x58 and S4/general USB connectivity issues
Shuurei said:
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Click to expand...
Click to collapse
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Shuurei said:
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Click to expand...
Click to collapse
Here's my craziness.
USB connection was working yesterday. Today, it is not.
I have uninstalled/reinstalled the Samsung Windows drivers/Kies
I have even adjusted my southbridge voltage to 1.2V in my BIOS
Still, no joy.
Curiously, when I boot the phone into download/ODIN mode and connect it, ODIN recognizes the connection. Reboot back into normal mode, and no USB connection is recognized. It is not showing up in my Device Manager as an unrecognized device. It just doesn't know it is there (unless phone is in download mode).
UPDATE: Solved. I had installed this ROM (http://forum.xda-developers.com/showthread.php?t=2261013). Reading back over the thread, it provided instructions for re-enabling the USB recognition of the phone. Had to re-enable the developer options and reset USB debugging. Makes sense now.
HI
I'm facing this issue today, I've tried two different laptops, both have Windows 7 x64 installed. I've tried every USB port on the two machines, I've tried with three different cables, I've downloaded and installed every USB driver there is. no use!
I'm out of options here and I can't think where to look further.
any help please?
shuurei said:
the device acts as if it is being charged.
Steps i have taken so far:
-uninstalled t-mo samsung mobile drivers and reinstalled
-deleted (uninstalled) all recognized usb devices via usb deview
-tried to connect without samsung drivers installed and all usb devices uninstalled
-tried to connect with samsung drivers installed and all usb devices uninstalled
-tried to connect without samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on samsung's site (1.5.14.0) and with the one found here on xda from 25apr2013 (1.5.23.0)
-tried to connect using different usb ports
-tried to connect using a different usb port on a different usb controller altogether
the kicker:
Device is recognized instantly... On my laptop.
This means:
-it is not the usb cable i am using (even though i have tried 3 different cables altogether regardless, including the one that came with the phone)
-it is not the device itself
possible: Windows issue? Last time this happened was long ago when i had gotten a mytouch 3g slide. I eventually just reinstalled windows since i had been meaning to then. I don't want to do it now though because i have too many things installed on here to start a fresh install... But i suppose if nothing else works, that's what i'll have to do.
Before that though, i would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
很想帮你啊 可是英文水平比较拙计
ok so now I'm guessing it is not windows, I tried on another machine with Windows Vista and got the same error.
any thoughts, anyone?
Did a factory reset for the phone
no it works!
don't know why
I just picked up this phone a couple days ago and last night tried to get the USB to work with no luck. I've tried everything I can think of. It does work in PTP mode but not MTP mode. I was able to use odin to on it though, so I was able to root it.
I've tried both in linux and on windows xp. I've never had an issue with any phone on linux and have installed/removed drivers numerous times on XP.
Tried 3 different cables, Factory reset with and without USB installed, tried pretty much everything I could find while googling similar problems (removing old registry entries, installed media player, etc)
I have adb installed on my linux box and even with debugging enabled I can't even get adb to connect to the phone.
Definitely something strange going on. Maybe I'll switch to cm10.1 to see if that makes a difference
I cant get my computer (windows 7) to connect with the phone when the phone is on, and was hoping some one might have found a fix.
This might fix it...
Shuurei said:
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
Here's a link with a list of things to try what you may not have tried to fix your problems.
A small number of devices I have worked on have a weird thing, that the first time I plug the cable into the computer, it connects but won't show up on the screen. unplugging the USB cable from the machine for maybe 3 seconds, and reinserting makes the connection work... go figure! :>)
Aloha and Good Luck!
http://forum.xda-developers.com/showthread.php?p=32906335#post32906335
I have a brand new Nexus 5X, a brand new high-end laptop with a USB 3 port with a fresh installation of Windows 7 Professional onboard.
I CANNOT get any of the drivers I have tried (all fresh downloads - Google, universal, etc.) to work with my phone. When plugging in the cable, phone to PC, I get an error Code 10 - "Cannot start the device".
I see in Heisenberg's guide for unlocking and rooting the 5X this post from user AquilaDroid - http://forum.xda-developers.com/showpost.php?p=63080921&postcount=9
Saying "Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)"
Does this mean the cable included with the phone is not sufficient for data transmission?? Does this correspond to my Code 10 error?
I bought an iOrange and it works great for my charging, data transfer, and app development
Sent from my Nexus 5X using Tapatalk
Code 10 is not a cable problem but rather a driver installation issue. Did you install try to install unsigned drivers without disabling signature verification?
Install the ones from Google or the full SDK. Also try to change the more to MTP on the phone.
Alferboy said:
Code 10 is not a cable problem but rather a driver installation issue. Did you install try to install unsigned drivers without disabling signature verification?
Install the ones from Google or the full SDK. Also try to change the more to MTP on the phone.
Click to expand...
Click to collapse
I did try the drivers from Google and from the SDK; still got the Code 10. I said OK to the unsigned driver message and still got the error. Is there something else I must do for the unsigned driver verification?
If you get code 10 the device is seen. Can you check with which hardware ids?
Also you can try uninstalling all drivers. Try usbview.
Sent from my Nexus 7 using Tapatalk
If you pull down the notifications on the N5X it should say USB Charging, click on it and change it to MTP.
Sent from my Nexus 5X using Tapatalk
are you using a USB C to USB A cable? Or does your laptop actually have a USB C port on it?
Thanks for the responses, but I have been thorough to the extent of my knowledge. To outline my situation:
- brand new laptop with USB 3 port and fresh Win7 Pro
- brand new Nexus 5X with included USB 3 cable
- Developer options - OEM locking and USB debugging ticked
- USB configuration as MTP, also tried PTP - this is also in Developer options; I get no pull-down or choice when plugging in
- Tried drivers from Google, from the Extras folder in SDK, Universal - uninstalled and removed driver files between each attempt
- Turned off Unsigned driver verification in BIOS
I get Code 10 error every time.
In USBview nothing indicates that anything is connected when plugging in phone.
I don't know what to make of the hardware ids.
I'm still curious about this cable, the one that came with the phone from Google, and AquilaDroid's comment indicating that it is not the one required to connect to a PC....
Any other ideas, given all this info???
sordup said:
Thanks for the responses, but I have been thorough to the extent of my knowledge. To outline my situation:
- brand new laptop with USB 3 port and fresh Win7 Pro
- brand new Nexus 5X with included USB 3 cable
- Developer options - OEM locking and USB debugging ticked
- USB configuration as MTP, also tried PTP - this is also in Developer options; I get no pull-down or choice when plugging in
- Tried drivers from Google, from the Extras folder in SDK, Universal - uninstalled and removed driver files between each attempt
- Turned off Unsigned driver verification in BIOS
I get Code 10 error every time.
In USBview nothing indicates that anything is connected when plugging in phone.
I don't know what to make of the hardware ids.
I'm still curious about this cable, the one that came with the phone from Google, and AquilaDroid's comment indicating that it is not the one required to connect to a PC....
Any other ideas, given all this info???
Click to expand...
Click to collapse
Please help.
Included cable IS only for charging
Well, since my questions seemed to have stumped folks here - no doubt the newness of these phones have people a little in the dark still - and for the benefit of others with the same problem, I have discovered a solution here.
The included USB 3 type C cable that comes with the Nexus 5X apparently is only for charging. As my issue outlined above showed, I could get no connectivity to my computer for file transmission with it. Upon getting a USB C to USB A cable, however, plugging into my computer worked as it should: device recognized, choice offered in the phone's pull-down menu for USB connection type (charging, MTP, or PTP), and flawless connection and file transmission.
There you have it.
metpage said:
are you using a USB C to USB A cable? Or does your laptop actually have a USB C port on it?
Click to expand...
Click to collapse
The OP has not responded to this question...
Inviato dal mio Nexus 5X utilizzando Tapatalk
I think there is a problem with USB 3 type A - type C cable. I have one ( my N5X is from LG distribution, we don't have gplay for devices) and he is works only as charging cable. I tried USB 2.0 , USB 3 even USB 3.1 and still only charging. According to my knowledge N5X have USB 2.0 with type C connector.
Odesláno z mého Nexus 5X pomocí Tapatalk
I had the same issue as you. I have a method for you to try, as it worked for me!
Hook your Nexus 5X to your computer
Go into your System / Device Manager
You should now see a device listed with an ! or something (will be your 5X)
Ok, now right click the unknown device (5X) and update driver. Click the select file manually option. Direct it to your android-sdk\Extras\Google. No further. It should now install your USB driver. This is what I had to do to get mine to work. First I tried pointing it further and closer in the SDK file but it didn't work. When I pointed it to the google folder, it installed an boom.
My computer reads a device connected, but then immediately freaks out and shuts the USB3.1 port off. I'm thinking it's expecting a 3.1 device, but it's getting a 2.0 device. Or even possibly that the USB3.1 card doesn't supply enough current to satisfy the N5X's thirst. I dunno, maybe it's just a Windows 10 bug. A USB-C to USB-A (A Host USB2.0) works just fine.
Hi there. Sorry if I sound dumb. I'm new to this whole thing and this was supposed to be my first experience with flashing custom ROMs and stuff like that. I was planning to get ready to install LineageOS on my Nexus 7 using a Windows 10 PC. Unfortunately, things quickly went south.
My first roadblock was the tablet not being recognised by fastboot. I checked online for a bit and from what I could gather, the solution was to install the Google USB drivers using device manager. I went into device manager, right clicked my Nexus 7 in "portable devices", selected "update driver" and chose the Google USB driver I downloaded from the official Android developers website. I'm not sure if this is relevant but the tablet was in fastboot mode when I did this. From that point on, my tablet is no longer recognised and it just keeps saying "device descriptor request failed" whether it's in fastboot or normal mode, and regardless of which USB mode I choose.
I tried uninstalling the driver, factory resetting, WugFresh NRT, and using different cables and USB ports. I checked for all sorts of solutions but they either didn't help or they require an unlocked bootloader (which was the very first thing I tried to do before finding out I needed to install the driver for fastboot to recognise the Nexus 7). Does anyone here know of a solution to get this working again? I'm completely stumped on what to do.
EDIT: I tested with a Chromebook and an old Windows 7 PC I had lying around. Neither could detect my Nexus 7 and the W7 PC even said it failed to install the driver as soon as I plugged it in. It seems that the driver update screwed up my tablet somehow and I have no idea how to fix it. I really don't understand how this could have happened considering I followed Google's own instructions for updating the driver.
Does anyone perhaps have a copy of the OEM driver for the 2013 N7 Wi-Fi (flo) model? ASUS don't distribute the driver on their website anymore and I'm out of ideas.
BenSkylake said:
my tablet is no longer recognised and it just keeps saying "device descriptor request failed" whether it's in fastboot or normal mode
Click to expand...
Click to collapse
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
k23m said:
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
Click to expand...
Click to collapse
Thanks for the response. I don't think I'll have enough time to try this today but I might as well ask. Do any of these fixes work without needing a USB connection to a PC, or if they do, do they require adb and fastboot to work? Because if so, I won't be able to use them since my USB data connectivity is completely busted no matter what I plug my Nexus into.
k23m said:
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
Click to expand...
Click to collapse
I just ran the RESTOCK 1 script and it worked wonders! My tablet's USB connectivity has been fixed and as an added bonus, my bootloader is now unlocked. I'll be continuing the process in Linux on my Pixelbook since it doesn't require any driver installations as far as I know. Thank you so much! You're a life saver!
To provide you with some context, I messed up a custom ROM install on my Redmi Note 5 Pro/Whyred Global version/ where the phone starts up and get stuck on the Orangefox Recover logo screen.
I thought I could just reinstall Orangefox via fastboot and format the phone to start fresh but the phone is refusing to be recognized by Windows in fastboot. It's the same Windows 10 PC that I used to unlock the bootloader on this phone and flash a custom recovery a year ago, and now it refuses to recognize my phone altogether.
Its giving me the USB Device Descriptor Request Failed error.
The drivers are not the issue here on my PC, I recently used this PC to unlock my Poco F3 and the procedure on that went flawlessly. But now it's refusing to recognize this phone. To rule out the little stuff, i changed cables, changed and tried different PCs, decided to use a USB 2.0 port on my PC thinking that might be the problem but still no luck.
I was planning to try this guide, but for that, I would need the hardware ids for the phone when its in fastboot mode. So if anyone has the phone, please I beg you give me the hardware Ids. I really want to fix this phone and give it another life.
Just in cast this fails, my last option would be to get the micro USB port replaced. I have gotten the USB port on this phone replaced twice as it used to cause problem when charging, so my final doubts are going to this.
My only evidence against a borked USB port is that the phone used to fast charge fine with this port. And since fast charging utilizes the data cables to negotiate with the fast charger, but I might be wrong about this.
So if anyone can help me regarding this issue, I would highly appreciate it.
https://forum.xda-developers.com/t/fastboot-not-detecting-my-phone.4544585/post-88035749
aIecxs said:
https://forum.xda-developers.com/t/fastboot-not-detecting-my-phone.4544585/post-88035749
Click to expand...
Click to collapse
I tried that , but I am still getting that error. Do you think this might because of faulty USB port?
probably Windows issue. use linux
https://gist.github.com/smac89/251368c8df2ccd645baedc3e1238fdb4
abeel_siddiqui said:
Its giving me the USB Device Descriptor Request Failed error.
Click to expand...
Click to collapse
That's an indication of basic USB enumeration failing.
It could be bad cable, bad port or your device has failed initializing USB.
It's not an indication of anything to do with Windows drivers (at this point).
Renate said:
That's an indication of basic USB enumeration failing.
It could be bad cable, bad port or your device has failed initializing USB.
It's not an indication of anything to do with Windows drivers (at this point).
Click to expand...
Click to collapse
I have also tried swapping cables, the micro USB fault might just be faulty on the phone.
aIecxs said:
probably Windows issue. use linux
https://gist.github.com/smac89/251368c8df2ccd645baedc3e1238fdb4
Click to expand...
Click to collapse
That could be possible, I will try booting into a live Linux environment and try it there.