Hello
I made a thread on reddit in the subreddit of my ROM (/r/LineageOS/comments/cccbtu/pc_does_not_detect_xiaomi_redmi_note_4/) regarding my issue and they recommended that I come here (I hope that's the right place.)
In summary, the notification that usually shows when I plug in my phone, to change the USB configuration from charging to MTP, does not show.
I've tried everything I can think of (different ports, PCs, cables, etc.) and nothing seems to help.
"adb devices" shows no devices both on normal boot and TWRP. The only thing the cable does is charge.
I'd be very happy to fix it.
Thank you!
First it's a software issue so the hardware is fine
Second i suggest getting an sd card with the official stock rom on it (version 10.1.1.0) to fix the reading error since it can't be readed even on twrp
If the problem still presists
I suggest to change the cable or the phone socket
Try another cable then see
Related
My friend's got a Legend with a USB malfunction (which I'm supposed to repair ). I've gone through all the threads and posts, and I couldn't find anyone which had precisely my problem.
When the phone's switched on and connected to via a USB cable, it starts charging, and the pop-up to select Charging, Mount as disk drive, Sync etc comes up.
But on the computer, whether I try USB debugging, or Mount disk drive, or the others, it shows the error "USB Device not recognized". I've installed HTC Sync, and am able to connect other phones without any problem.
I tried connecting the USB in fastboot, but it doesn't detect it either (FASTBOOT doesn't change to FASTBOOT USB).
I just wanna confirm with experts if this' a problem with the hardware (Got a sample here :http://forum.xda-developers.com/showpost.php?p=18420923&postcount=11) before I go to the service center.
Thanks
U might be using the wrong data cable. There are 2 different types, there is the old type that only has 4 connectors in the mini USB plug (phone end), the new ones have 5 connectors.
Another possibility is that the cable is simply just damaged.
I had the exact same issue with an external HDD that worked, then stopped then worked again then stopped, tried a new cable and worked without issue.
Sent from my legend using XDA
I'm leaning less to the hardware side.
I have had this problem before (not entirely identical) and after fruitless attempts in fixing I decided to reflash my rom and USB worked again.
Sent from my Legend
Thanks for the reply guys Had to replace the USB port connector PCB.
Just for the info, I was not able to re-flash the ROM since the phone was S-ON and bootloader locked and couldn't get FASTBOOT USB to work.
USB Version...
Hey guys, long time reader thought I'd contribute my frustration to hopefully help someone in a similar situation.
I spent a few days wondering why I couldn't get any of this to work no matter what cable I tried. For some reason, my HTC One X didn't like dealing with fastboot through my computer's USB 3.0 slot. When I finally tried a 2.0 slot on the same machine, everything went through just fine...
Cheers!
http://forum.xda-developers.com/showthread.php?t=751265 This should do the trick.
This threat will indeed do the trick and your USB connection will be back
Hello! I know, I know. There are a lot of different threads according to this problem but I read almost everything and still cannot fix my problem.
A few weeks ago when I tried to charge my phone the message: Your cable is not compatible with your device. Please use the orginal HTC-cable or your phone get damaged. appeared.
until that moment I thought it doesnt matter if I use a htc cable or a cable from another brand. I mean they changed all the ports to a micro-usb-port. Just to give you the opportunity to use every cable.
Well, after that I tried to connect my phone with my computer and the HTC Car app appeared and bluetooth got switched on. WHY?
I did a factory reset and flashed my rom again. Now I can connect my HTC One with my computer and on the screen of my computer appears the message:
"Device not recognized "Windows has stopped this device because it has reported problems. (Code 43)"
(and its unable to mount otg-usb in recovery)
I tried different cables. I tried to (un)install and update the HTC drivers. I tried different computer. I tried turning usb debugging off and on! I tried to clean the USB-pins! nothing works! :crying:
(Unfortunately I have no old backup with my new TWRP v2.6.)
I just have been abroad for 6 months and dont wanna loose all my photos and videos. Any ideas?
I think its a software issue on my phones. Maybe something with my partitions. But I dunno what I can wipe without deleting all my photos and video.
THANKS
seven09 said:
Hello! I know, I know. There are a lot of different threads according to this problem but I read almost everything and still cannot fix my problem.
A few weeks ago when I tried to charge my phone the message: Your cable is not compatible with your device. Please use the orginal HTC-cable or your phone get damaged. appeared.
until that moment I thought it doesnt matter if I use a htc cable or a cable from another brand. I mean they changed all the ports to a micro-usb-port. Just to give you the opportunity to use every cable.
Well, after that I tried to connect my phone with my computer and the HTC Car app appeared and bluetooth got switched on. WHY?
I did a factory reset and flashed my rom again. Now I can connect my HTC One with my computer and on the screen of my computer appears the message:
"Device not recognized "Windows has stopped this device because it has reported problems. (Code 43)"
(and its unable to mount otg-usb in recovery)
I tried different cables. I tried to (un)install and update the HTC drivers. I tried different computer. I tried turning usb debugging off and on! I tried to clean the USB-pins! nothing works! :crying:
(Unfortunately I have no old backup with my new TWRP v2.6.)
I just have been abroad for 6 months and dont wanna loose all my photos and videos. Any ideas?
I think its a software issue on my phones. Maybe something with my partitions. But I dunno what I can wipe without deleting all my photos and video.
THANKS
Click to expand...
Click to collapse
use an app like airdroid to copy all your stuff to your pc via wifi
also dropbox can hold all your photo's
then try and RUU back to stock
Hi,
I'm struggling with my Samsung GT-I9300 for long six days and can't get bluetooth or "normal" USB connection.
Last week, after my battery deplet I made a full charge and when turn on the phone some weird error about encryptation appeared. The phone won't boot anymore.
I have done a standard ROM flash procedure and since that, no matter what ROM I put in, phone hangs or reboot when I try to turn on bluetooth.
Besides that, "normal" USB connection isn't possible anymore. The command "adb devices" show nothing. Strangely, I can put the phone on "download mode" and flash any ROM to it.
I already tried with different cables (all Samsung original), different computers (Windows and Mac), different USB ports on the computers and nothing seems to work...
Tried several Samsung stock ROMs for GT-I9300, ArchiDroid, Cyanogen, etc.
I done extense Google research and cannot get out of this situation by myself. Now I need to receive help from the pros.
I don't think that the problem is hardware related.
Anyone knows how to check if the bluetooth firmware is "in place"? I mean, how to verify using commands in adb shell (as root) what must be the correct bluetooth firmware, his location and etc.
Same thing for USB (MTP?) related function.
If it was hardware related, flash things using ODIN wouldn't be possible, right?
Hi Guys,
I'm unable to connect my v10 to my windows laptop or any other OS or laptop. I always get an error message saying, USB Device not recognized. However, the only thing I can do is Charge my phone with it. :crying:
About the device,
Android Version: 7.0
ROM: Stock
SW Version: V30a-HKG-XX
I've tried almost everything. The following are what I've tried
1. Rebooting the phone and connecting again,
2. Tried on different laptop/computers, with linux and mac too,
3. Replaced the micro usb port,
4. Fiddled with device manager on windows, uninstalled drivers, reinstalled,
5. Tested with different data cables,
6. Tried connecting OTG usb drives,
7. Booting into Fastboot to see if it gets recognized there,
8. Updated from MM to Nougat,
9. Enabled USB Debugging, under dev options,
10. Enabled MTP, under dev options
All of the above did nothing to solve the problem.
I believe the data cables on the microusb port are fine and there maybe something wrong with the motherboard. Please tell me if I'm correct with this inference. if yes, then what may be done to solve this.
Please guys, suggest what maybe wrong and what can be done to fix it. I'd really Love & Hope it if there is a simple fix to it
Thanks.
Same problem here. The problem started just after the upgrade to 7.0 (via ota). I spoke to lg but i have no warranty because my phone was bought on another country. Hope someone can help.
kitkitnaakar said:
Hi Guys,
I'm unable to connect my v10 to my windows laptop or any other OS or laptop. I always get an error message saying, USB Device not recognized. However, the only thing I can do is Charge my phone with it. :crying:
About the device,
Android Version: 7.0
ROM: Stock
SW Version: V30a-HKG-XX
I've tried almost everything. The following are what I've tried
1. Rebooting the phone and connecting again,
2. Tried on different laptop/computers, with linux and mac too,
3. Replaced the micro usb port,
4. Fiddled with device manager on windows, uninstalled drivers, reinstalled,
5. Tested with different data cables,
6. Tried connecting OTG usb drives,
7. Booting into Fastboot to see if it gets recognized there,
8. Updated from MM to Nougat,
9. Enabled USB Debugging, under dev options,
10. Enabled MTP, under dev options
All of the above did nothing to solve the problem.
I believe the data cables on the microusb port are fine and there maybe something wrong with the motherboard. Please tell me if I'm correct with this inference. if yes, then what may be done to solve this.
Please guys, suggest what maybe wrong and what can be done to fix it. I'd really Love & Hope it if there is a simple fix to it
Thanks.
Click to expand...
Click to collapse
I think it due to charging port. It may be broken/loose
My Kindle Fire HDX 7 (thor) is was rooted using kingroot on fire os 4.5.5.2, unlocked bootloader, twrp installed, and Lineage 13 installed. Everything is fine except that almost all usb protocols are screw up. The only one that does work is charging.
When I plug it into my pc (win10) it keeps appearing on the taskbar with the unrecognized usb device logo and then half a second to 2 seconds later it disappears and my pc makes the disconnected noise. Then .5 to 2 seconds later it will reappear with the unrecognized usb device logo and disconnect and repeat infinitely. Therefore, no mtp or adb. I've settled for wifi file transfer and haven't had to use adb yet, but I need mtp soon for larger files, and I need adb for other stuff soon too. Now. Fastboot, on the other hand, does sorta work. It shows up as an unrecognized usb device, but doesn't show up when I do "fastboot devices". I've done tons of research and tried so many solutions, and it's not a problem with my cables or pc. The problem is with the kindle. I hope very dearly that it's a software issue and not a hardware issue. One extra important detail: in developer options when I change the USB configuration to mtp it changes it but only shows the change when it I go out of developer options and back in. Then when I press any other option it automatically reverts it back to charging.
Uzerexample said:
My Kindle Fire HDX 7 (thor) is was rooted using kingroot on fire os 4.5.5.2, unlocked bootloader, twrp installed, and Lineage 13 installed. Everything is fine except that almost all usb protocols are screw up. The only one that does work is charging.
When I plug it into my pc (win10) it keeps appearing on the taskbar with the unrecognized usb device logo and then half a second to 2 seconds later it disappears and my pc makes the disconnected noise. Then .5 to 2 seconds later it will reappear with the unrecognized usb device logo and disconnect and repeat infinitely. Therefore, no mtp or adb. I've settled for wifi file transfer and haven't had to use adb yet, but I need mtp soon for larger files, and I need adb for other stuff soon too. Now. Fastboot, on the other hand, does sorta work. It shows up as an unrecognized usb device, but doesn't show up when I do "fastboot devices". I've done tons of research and tried so many solutions, and it's not a problem with my cables or pc. The problem is with the kindle. I hope very dearly that it's a software issue and not a hardware issue. One extra important detail: in developer options when I change the USB configuration to mtp it changes it but only shows the change when it I go out of developer options and back in. Then when I press any other option it automatically reverts it back to charging.
Click to expand...
Click to collapse
Well, first step is to try a Nougat based rom such as AEX, Lineage 14.1 or Resurrection Remix. Obviously backup your current config before flashing a new ROM. Good luck.
Help!
Davey126 said:
Well, first step is to try a Nougat based rom such as AEX, Lineage 14.1 or Resurrection Remix. Obviously backup your current config before flashing a new ROM. Good luck.
Click to expand...
Click to collapse
I'll try Resurrection Remix and AEX, but LN 14.1 definitely doesn't work. I just flashed a stock 4.5.5 rom via twrp and that's what I'm currently using. With stock rom it shows up as an unrecognized usb devices but now it at least stays and doesn't keep dis/reappearing. Still no adb or fastboot. I can't find I way to change it to an mtp device in device manager. PLEASE HELP!
Uzerexample said:
PLEASE HELP!
Click to expand...
Click to collapse
Exceptionally annoying.
Uzerexample said:
I'll try Resurrection Remix and AEX, but LN 14.1 definitely doesn't work. I just flashed a stock 4.5.5 rom via twrp and that's what I'm currently using. With stock rom it shows up as an unrecognized usb devices but now it at least stays and doesn't keep dis/reappearing. Still no adb or fastboot. I can't find I way to change it to an mtp device in device manager.
Click to expand...
Click to collapse
In most ROMs (can't speak to FireOS v4) ADB toggle is in Developer Options. Switching between modes is usually accomplished via notification toggle or separate setting. Unrecognized but otherwise functional device scenarios are almost always traceable to crappy cables, Windows drivers or direct/indirect use of a USB hub that doesn't carry the data signal. More exotic causes involve a bad port or other hardware fault. I am not aware of any firmware toggle that would persist across system partition wipes and installation of different ROMs from varying Android generations.
I have had consistent good luck using drivers installed with the following package (don't need to use/launch...just install). Look for Moto Composite variants with the device tethered.
https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
PC driver issue
Davey126 said:
In most ROMs (can't speak to FireOS v4) ADB toggle is in Developer Options. Switching between modes is usually accomplished via notification toggle or separate setting. Unrecognized but otherwise functional device scenarios are almost always traceable to crappy cables, Windows drivers or direct/indirect use of a USB hub that doesn't carry the data signal. More exotic causes involve a bad port or other hardware fault. I am not aware of any firmware toggle that would persist across system partition wipes and installation of different ROMs from varying Android generations.
I have had consistent good luck using drivers installed with the following package (don't need to use/launch...just install). Look for Moto Composite variants with the device tethered.
Click to expand...
Click to collapse
Next day. Went back to dis/reappearing on pc rapidly. Different cable isn't issue same cable works perfectly with NVIDIA K1 tablet, and I tried RR rom. While I tested it and loved the customization of RR, it didn't fix it. The PC driver side of it. In device manager it showed up as Unknown USB device (Device descriptor request failed) and it shows under Universal serial Bus Controllers. When I go to update the device as an android mtp or adb or anything, none of the mtp of adb driver options show.
Uzerexample said:
Next day. Went back to dis/reappearing on pc rapidly. Different cable isn't issue same cable works perfectly with NVIDIA K1 tablet, and I tried RR rom. While I tested it and loved the customization of RR, it didn't fix it. The PC driver side of it. In device manager it showed up as Unknown USB device (Device descriptor request failed) and it shows under Universal serial Bus Controllers. When I go to update the device as an android mtp or adb or anything, none of the mtp of adb driver options show.
Click to expand...
Click to collapse
Whether the cable works with another device is largely irrelevant. HDX devices are very picky/sensitive with tethered communications. Been working with these pups for 5+ years and heard many a forceful testimonial about how it can't be related to ports/cables/hosts. Amazing how many communication issues are fixed with a simple cable/port swap. Occasionally joy is found by connecting to a different host.
That said, your device may have a hardware problem. Not uncommon if you picked it up on auction at a bargain price. Keep trying different cable/port/host combinations.
Half way sucess
Davey126 said:
Whether the cable works with another device is largely irrelevant. HDX devices are very picky/sensitive with tethered communications. Been working with these pups for 5+ years and heard many a forceful testimonial about how it can't be related to ports/cables/hosts. Amazing how many communication issues are fixed with a simple cable/port swap. Occasionally joy is found by connecting to a different host.
That said, your device may have a hardware problem. Not uncommon if you picked it up on auction at a bargain price. Keep trying different cable/port/host combinations.
Click to expand...
Click to collapse
(Running a twrp flashable version of Fire os 4.5.5 https://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914) I used a different port and it stopped rapidly dis/reappearing! It stays connected... but as an unknown USB device (device descriptor request failed) I think I've isolated the problem on the kindle side. Something is making it think it's a different device. When I change the USB configuration in Dev settings, it does nothing. The computer doesn't see any changes, and when I turn off both MTP and PTP no changes were detected on pc and nothing happened on kindle. The MTP and PTP toggles are nothing more than cosmetic buttons. Is something wrong with the kernel or build.prop and/or system.prop?
If nothing, then please give me a guide on how to completely reset everything to 100% stock. (I don't have safe strap, but do have TWRP)
Uzerexample said:
(Running a twrp flashable version of Fire os 4.5.5 https://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914) I used a different port and it stopped rapidly dis/reappearing! It stays connected... but as an unknown USB device (device descriptor request failed) I think I've isolated the problem on the kindle side. Something is making it think it's a different device. When I change the USB configuration in Dev settings, it does nothing. The computer doesn't see any changes, and when I turn off both MTP and PTP no changes were detected on pc and nothing happened on kindle. The MTP and PTP toggles are nothing more than cosmetic buttons. Is something wrong with the kernel or build.prop and/or system.prop?
If nothing, then please give me a guide on how to completely reset everything to 100% stock. (I don't have safe strap, but do have TWRP)
Click to expand...
Click to collapse
Likely not carrying a proper data signal due to damaged usb interface or (wait for it...) crappy cables or other hardware issues previously identified. There is no easy path to 100% stock. Highly unlikely any *.prop is involved. Can device be 'seen' while booted into TWRP? Me thinks not which exonerates the .props.
Heck Yeah!
I have the same problem, everything was working fine, until i've managed to unlocked the bootloader, it was a disaster, it charges so very slow and it doesn't recognize my pc anymore, still searching for solutions, anyways this better than a bricked KFH.
ChickenKyrie said:
I have the same problem, everything was working fine, until i've managed to unlocked the bootloader, it was a disaster, it charges so very slow and it doesn't recognize my pc anymore, still searching for solutions, anyways this better than a bricked KFH.
Click to expand...
Click to collapse
https://forum.xda-developers.com/kindle-fire-hdx/help/thor-recognized-windows-t3812047/post77082565