Related
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
maatsby said:
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
Click to expand...
Click to collapse
I bought the phone and it came with 1 cord (with HTC label) that can be connected to the charger, I guess there are only 1 cord for charging and connect to PC? This is the cord that I use. In addition to that I have also tried Motorola, Sony Ericsson (both also for Android phone) and Nokia cord but all can't.
The ROM is actually older version stock ROM from RUU.exe. I saw from few Desire thread they were using this method to restore the ROM to before the USB Brick condition so I thought to try it.
BUMP!
Anyone know what should I do to resolve this problem?
Are you running the very latest HTC Sync on your PC? I'm using 3.0.5606. You can get it here: http://www.htc.com/www/help/
Also, connect your phone and go into Device Manager on your PC. Check to see if you have an entry for Android USB Devices and that the phone shows up. See attached screenshot for how mine looks. This is the best place to check to see if your PC has installed the drivers correctly.
In answer to your question about the cable, yes it's the same cable that attaches to the PC or to the mains charger. I've sometimes had connection problems caused by a dodgy cable, but I've used others apart from the HTC one without issues.
Edit: Also, when you install HTC Sync it should warn you to disable Antivirus software during the installation. This can be really important! I ignored it the first time around, thinking it was just a silly precaution, and had loads of problems with the phone not being recognised. Had to uninstall, temporarily disable AV, and re-install HTC Sync. Once it has finished installing, you can turn your AV back on.
Thank you for your reply preacher6.
Yes, I'm using the latest HTC Sync, v3.0.5606, just downloaded yesterday and reinstall everything.
When my phone connected to the PC it didn't appear as Android USB Device on my Device Manager, it only appear as Unknown Device in USB Controller:
So I guess I can rule out the cable as I have tried about 4 cables already.
For the installation part, I have disable the anti virus and also running the setup program as administrator. When installing there is no problem whatsoever that crop out.
Another point is, even on Fastboot it appear as Unknown Device in the PC.
I would try to update the driver manually - right click on the Unknown device, go to "install driver" or "update driver", then browse to the "Program Files\HTC\HTC Driver" folder. See if it picks up and installs the correct driver.
I've tried manually update the driver as per your advise but it says there is no compatible driver in that folder even though androidusb.inf is in that folder.
I'm running Win 7 64bit. does the driver also work for 64bit OS?
Should do, yes, I'm on Win7 64 bit myself. There is this folder on my PC:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64
Is the unknown device present when the phone isn't connected? Just to make sure that is actually the phone - if it's still there when the phone isn't connected, it's some other device.
Otherwise try uninstalling the unknown device and then rebooting the PC, then forcing the installation of the drivers again.
The folder is same as yours.
The unknown device does not present when my DHD is not connected, so I'm certain it is the phone that appear as unknown device.
I have tried uninstalling the unknown device > reboot PC > installing the driver but it still won't install.
Another thing is, I check on the Device Manager > Unknown Device properties > Details" for it's Hardware Ids and it shows as USB\UNKNOWN. I think it should show a strings of the device id? Correct me if I'm wrong.
Yep, there should be a proper device ID string, on charge mode mine shows a hardware ID of USB\VID_0BB4&PID_0CA2&REV_0226&MI_01.
At this point the best thing I can suggest is to try on another PC. If it works, your drivers are screwed up and you'll need to strip them and reinstall. But if it doesn't work on another PC, it's possible you have a hardware problem with the phone.
xb360 said:
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
Click to expand...
Click to collapse
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
dmastman83 said:
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
Click to expand...
Click to collapse
Yes. Holla if you still need help
marknoll said:
Yes. Holla if you still need help
Click to expand...
Click to collapse
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
FossaFX said:
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
Click to expand...
Click to collapse
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
marknoll said:
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
Click to expand...
Click to collapse
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Install the SDK on PC and update all android versions.
Well guys it was just my PC, i made a system backup for four days and that was all the problem(the USB port of my PC)
FossaFX said:
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Click to expand...
Click to collapse
After installing and updating SDK...go into platform folder and open it. Hold mouse in field and hold shift and right click mouse. Chose "open cmd here"..that will open a cmd prompt window. In regular mode on phone,type "adb devices" should return numbers (ex: hta3829g)..if in bootloader mode,type "fastboot devices" should return numbers.
This SDK helps PC see your phone when its plugged in. Especially handy when a PC won't install drivers for your phone
Sent from my ATRIX HD
Are you also stating that your device will no longer charge when plugged in?
Sent from my ATRIX HD
Hi guys,
i wanted flash some new kernel, i have currently Rush kernel. So i opened freshly installed FlashTool (0.90.10.1) with installed drivers from /drivers folder, take out battery and press "menu" and connect cabel....just like million times before. But now the LED just blinked blue and phone bootloops until i pull the cable out. And just the same happens when i want to go into flashmode (green LED) it just blinks and get bootloop. Can someone give me some advise? I am using original SE cable that comes with it.
edit: i am not using USB controller, i am using USB that comes right from motherboard
edit 2: even if i try "reboot into fastboot mode (via ADB)" in flashtool, it reboots into CWM...
Lord5619
And what happens when you try an older version or manual fastboot?
XperienceD said:
And what happens when you try an older version or manual fastboot?
Click to expand...
Click to collapse
just the same...
hmmm, but now the weird part, when i put the cable, just the cable without phone connected to it, windows told me, that "some of devices was not recognized" and drivers was not installed for unknown device. What the hell does this mean? drivers for cable?! btw: the cable is barely used i flashed with it two Arc S just week ago.
lord5619 said:
just the same...
hmmm, but now the weird part, when i put the cable, just the cable without phone connected to it, windows told me, that "some of devices was not recognized" and drivers was not installed for unknown device. What the hell does this mean? drivers for cable?! btw: the cable is barely used i flashed with it two Arc S just week ago.
Click to expand...
Click to collapse
Sounds like a PC issue to me.
nope it was that cable...i don´t get it, but with another one, it just works. I am using sometimes that "non-working" cable for file transfer or charge battery and it works normally. Strange...
I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.
Mikeonic said:
I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.
Click to expand...
Click to collapse
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus
Ive tried
mixtapes08 said:
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I have tried installing drivers...still nothing..
I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
iLeopard said:
I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
Click to expand...
Click to collapse
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.
Mikeonic said:
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.
Click to expand...
Click to collapse
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?
iLeopard said:
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?
Click to expand...
Click to collapse
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,
Mikeonic said:
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,
Click to expand...
Click to collapse
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.
iLeopard said:
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.
Click to expand...
Click to collapse
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .
Mikeonic said:
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .
Click to expand...
Click to collapse
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers
iLeopard said:
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers
Click to expand...
Click to collapse
Been trying and it wont let me push those files and when I do, I get Code Error 10
Mikeonic said:
Been trying and it wont let me push those files and when I do, I get Code Error 10
Click to expand...
Click to collapse
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)
iLeopard said:
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)
Click to expand...
Click to collapse
It says there are no files in the folder...
UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43
Mikeonic said:
UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43
Click to expand...
Click to collapse
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.
iLeopard said:
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.
Click to expand...
Click to collapse
It was through the Settings SubMenu, I'll try a Fast boot
Mikeonic said:
It was through the Settings SubMenu, I'll try a Fast boot
Click to expand...
Click to collapse
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu
iLeopard said:
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu
Click to expand...
Click to collapse
Still nothing....this is hopeless
Mikeonic said:
Still nothing....this is hopeless
Click to expand...
Click to collapse
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?
iLeopard said:
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?
Click to expand...
Click to collapse
I will try getting a new USB, maybe a stock if I can find and see if that works. Wish I could root without a USB...Thank You for your help. I will update if anything.
Sorry for noob question. Searched Searched xda and can't find anything. Pixel3 xl. Stock Android 10. Rooted. Windows 10 with correct drivers so it sees device. Can transfer files easily. USB debugging enabled. ADB and Fastboot do not see device. Used to work but not now. Tried kill-server and start-server in ADB. Tried different cables, restarting phone and computer. No luck. In fastboot mode (on phone) fastboot devices returns nothing. Totally stumped. Can anyone help. Again apologize for noob question but this has always worked before and I've flashed roms as well as stock numerous times with no issues till now. Help!
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
sliding_billy said:
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
Click to expand...
Click to collapse
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Daisymae said:
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Click to expand...
Click to collapse
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
jd1639 said:
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Thanks. Did that. Same thing. Blank list.
Daisymae said:
Thanks. Did that. Same thing. Blank list.
Click to expand...
Click to collapse
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Have you recently updated and not re-authorized your phone?
sliding_billy said:
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Click to expand...
Click to collapse
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
spotmark said:
Have you recently updated and not re-authorized your phone?
Click to expand...
Click to collapse
Turned usb debugging off then back on again. When I plug in a cable I reauthorize usb debugging but get the same results.
Daisymae said:
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
Click to expand...
Click to collapse
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
sliding_billy said:
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
Click to expand...
Click to collapse
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
ktmom said:
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Click to expand...
Click to collapse
No. Tried that first thing. Fastboot devices turns up nothing.
sliding_billy said:
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
Click to expand...
Click to collapse
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Daisymae said:
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Click to expand...
Click to collapse
just for the heck of it, do you have other cables. Stranger things have happened that made a difference, and the next suggestion involves reinstalling computer and/or phone. Maybe a live USB Ubuntu disk to see what is working and what is not.
Daisymae said:
No. Tried that first thing. Fastboot devices turns up nothing.
Click to expand...
Click to collapse
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
ktmom said:
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
Click to expand...
Click to collapse
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Daisymae said:
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Click to expand...
Click to collapse
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Homeboy76 said:
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Click to expand...
Click to collapse
Only one instance of fastboot. Not sure what you mean execute
permissions. You mean on Windows or on the device? Windows has execute permissions. I don't have adb or fastboot on the device.
My first Poco F3 is completely unlocked and running a custom rom, still able to connect to PC even now.
I have a second Poco F3 that I was able to originally connect to my PC to debloat, hadn't needed to connect it to a PC till now. Today was the day I could unlock it but when I connect it via USB cable, original or otherwise, no usb options appear on phone and nothing shows on PC. I can use the same cable on my first Poco F3 and everything works fine. I've tried multiple cables, reinstalling drivers, restarting phone and PC, trying a different PC, enabling debugging tools, etc.
Nothing shows in "My Computer"
Nothing shows in Device Manager
No usb options on phone (default is set to File Transfer)
Nothing shows in CMD with "adb devices"
Charging still works
Is there anything I can do to at the very least unlock the bootloader? Or is this not fixable?
long shot... check the usb C port for dirt/dust/fluff blocking connection...
Most probably u debloated an app responsable for media transfer. If u can, revert what u debloated.
Alin45 said:
Most probably u debloated an app responsable for media transfer. If u can, revert what u debloated.
Click to expand...
Click to collapse
Did a factory reset thinking that may have been the case, still no good.
Tried cleaning out the port and still no good either
I still think it's Windows. Please can you try putting Ubuntu (or another Linux distro) on a USB, booting from that, installing platform tools (ADB/fastboot etc) and then running ADB devices. Windows is very finiky sometimes.
Edit: when you plug in your phone to the PC do you get a notification saying charging? Or is there no notification? Also does it start charging the phone?
There is a delay before it begins charging and the charging animation plays but yes it does. But then there is no usb notification. Will try ubuntu and report back
Booting into Ubuntu, before installing platform tools the first phone that I knew worked showed up and showed up in adb devices when platform tools was used. The second still didn't show up, exactly the same as on windows
Try downloading the installed stock miui rom from the update menu in the miui update menu and re-install it on the phone
Unfortunately reinstalling latest package didn't help
Can't think of anything else to suggest. Sorry
If the usb connection continues to be nonexistent, is there any way to at least unlock the bootloader without using the Xiaomi Unlock tool on the PC?
Are you sure the USB cable you're using support transfert file?
Cjayy said:
If the usb connection continues to be nonexistent, is there any way to at least unlock the bootloader without using the Xiaomi Unlock tool on the PC?
Click to expand...
Click to collapse
Nope
Hmmmmm.....strange! I'm running out of ideas....try different USB ports on PC. Maybe it's a faulty USB-C port on phone after all.
do you have a type c usb-otg?
If yes then see if it is detected by the phone
X0PIRAT3 said:
Are you sure the USB cable you're using support transfert file?
Click to expand...
Click to collapse
Yes. Used 4 different cables, 1 of which is the cable that comes with the phone. None work on this phone but do on the first phone.
Alin45 said:
Hmmmmm.....strange! I'm running out of ideas....try different USB ports on PC. Maybe it's a faulty USB-C port on phone after all.
Click to expand...
Click to collapse
Tried different ports across 2 PCs. I'm starting to think it is a faulty port, though it worked fine a week ago.
arifqur said:
do you have a type c usb-otg?
If yes then see if it is detected by the phone
Click to expand...
Click to collapse
I honestly don't know if any of my cables are usb-otg, how would I check?
Try to use this version of Mi FLash Tool (only for drivers) : https://xiaomiflashtool.com/download/xiaomi-flash-tool-20210226
Extract and launch the executable then drivers install
Something like this. You can plug in any usb stick and see if it is detected. Another way to check whether the port on the phone is working for data as well
X0PIRAT3 said:
Try to use this version of Mi FLash Tool (only for drivers) : https://xiaomiflashtool.com/download/xiaomi-flash-tool-20210226
Extract and launch the executable then drivers install
Click to expand...
Click to collapse
Tried this and still no good.
arifqur said:
Something like this. You can plug in any usb stick and see if it is detected. Another way to check whether the port on the phone is working for data as well
Click to expand...
Click to collapse
I don't have anything like this but that reminded me of the usb-c to headphone adapter and that also doesn't work. Sound just plays out of the speakers.
Trying with Android Auto in the car, the car doesn't register a device connecting at all either.
Either the data transfer portion is somehow disabled on the device itself (which I would love to know how to enable it again if that's the case) or it's a damaged usb port. Just strange that it worked a week ago.
Something I forgot to mention, when I went to unlock the bootloader yesterday the phone did not show up anywhere except for in the ADBFastbootTools to debloat the software as a OnePlus device but then never showed up again.
Cjayy said:
Tried this and still no good.
I don't have anything like this but that reminded me of the usb-c to headphone adapter and that also doesn't work. Sound just plays out of the speakers.
Trying with Android Auto in the car, the car doesn't register a device connecting at all either.
Either the data transfer portion is somehow disabled on the device itself (which I would love to know how to enable it again if that's the case) or it's a damaged usb port. Just strange that it worked a week ago.
Something I forgot to mention, when I went to unlock the bootloader yesterday the phone did not show up anywhere except for in the ADBFastbootTools to debloat the software as a OnePlus device but then never showed up again.
Click to expand...
Click to collapse
I have the same problem, did you solve it ? I replaced the usb board of the phone, still not working.