Related
So I was hoping some of you guys could help me out.
Recently my Vibrant started to give me trouble with my computer. But it's only my vibrant with my computer. I can connect to any other computer no problem. Any other device is easily recognized by my computer except the vibrant.
It started after using PDANET's tethering app. I was at one point tethering all the time putting my phone in usb debugging mode and running pdanet on my computer. Then I also started using the bluetooth tethering. Once I finally got internet at my new place i stopped using the tethering option. But then I realized when i tried to get files off my phone my computer wouldnt recognized my phone anymore.
The error I get is
USB Device Not Recognized.
One of the usb devices on this computer has malfunctioned and windows does not recognized it.
Usb Root Hub Unknown device.
Try Reconnecting the device if windows still does not recognized it replace the device.
In the device manager the properties of the "unknown device" says
Status: Windows has stopped this device because it has reported problems. (Code 43)
I've tried the solution posted under here
USB Fix - Win7 x64 - USB Device not Recognized
and I've used both drivers from Samsung Kies and here
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S
(Sorry can't post links apparently)
When I try to update the driver manually for the unknown device it says that it has already selected the best driver for the device. So i don't know if it really updated it.
Any Suggestions would be really helpful. Thanks!
espy1988 said:
So I was hoping some of you guys could help me out.
Recently my Vibrant started to give me trouble with my computer. But it's only my vibrant with my computer. I can connect to any other computer no problem. Any other device is easily recognized by my computer except the vibrant.
It started after using PDANET's tethering app. I was at one point tethering all the time putting my phone in usb debugging mode and running pdanet on my computer. Then I also started using the bluetooth tethering. Once I finally got internet at my new place i stopped using the tethering option. But then I realized when i tried to get files off my phone my computer wouldnt recognized my phone anymore.
The error I get is
USB Device Not Recognized.
One of the usb devices on this computer has malfunctioned and windows does not recognized it.
Usb Root Hub Unknown device.
Try Reconnecting the device if windows still does not recognized it replace the device.
In the device manager the properties of the "unknown device" says
Status: Windows has stopped this device because it has reported problems. (Code 43)
I've tried the solution posted under here
USB Fix - Win7 x64 - USB Device not Recognized
and I've used both drivers from Samsung Kies and here
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S
(Sorry can't post links apparently)
When I try to update the driver manually for the unknown device it says that it has already selected the best driver for the device. So i don't know if it really updated it.
Any Suggestions would be really helpful. Thanks!
Click to expand...
Click to collapse
I have the same problem on my PC. I would plug in the phone and my mouse would stop working. No tethering app installed or anything.
Anyway, I just tried the ports on the back of the PC and those worked. Try a port closer to the MB
I've tried all my ports. It's still not recognized.
Check the cable and power source. Be sure cable is with good quality. I hade the same issue. I fixed it with original HTC cable and back panel USB from my deskop computer. Front USB of desktop computers often are not enough to power that consumption.
After updating to Froyo it started working again. Thanks though. I still have no clue what caused it.
Bumping to confirm, I found this thread after getting the same error. I had tried several of the USB ports on my computer but after reading this tried the 2 I hadn't yet, they both worked. Not sure why only those work now, but they do work.
Hope this helps someone.
I have a bricked galaxy s which doesn't do anything. Windows 7 reconizes an unknown device and it's not possible to install the samsung driver. Windows says that it allready has the right driver.
I can't seems to reincarnate my galaxy s. Only this small sign of live in windows 7.
It happened when I was flashing 2.3.5 and the connection went down just seconds after the start of flashing so I guess the bootloaders are corrupt.
Anyone any idea how to solve this one?
Vibrant UnBrickable Mod
The same thing is happening to my Vibrant. Tried Rooting and installing various ROMs and it is still "Not Recognized". Tried all ports on all PCs (4) and Laptops (1) and non of them work. espy1988, how did you upgrade to Froyo 2.2 if you could not connect to PC and Kies? This used to work without an issue.
Thanks
Tombias said:
I have a bricked galaxy s which doesn't do anything. Windows 7 reconizes an unknown device and it's not possible to install the samsung driver. Windows says that it allready has the right driver.
I can't seems to reincarnate my galaxy s. Only this small sign of live in windows 7.
It happened when I was flashing 2.3.5 and the connection went down just seconds after the start of flashing so I guess the bootloaders are corrupt.
Anyone any idea how to solve this one?
Click to expand...
Click to collapse
Like said above u might need to be debricked.
seems like ur phone is hard bricked.
---------- Post added at 04:33 AM ---------- Previous post was at 04:26 AM ----------
have u tried Odin back to stock using Odin or hemidal ?
I have the same problem now. I have had my Vibrant for over a year never with an issue. I have Odined it back to JFD dozens of times but now it will not recognize the usb device.
I have GB bootloaders, but never a problem before. When changing Roms I usually Odin back to JFD first and start clean.
My problem started with the phone getting stuck in landscape mode. I was running a 2.3.4 GB rom Sensation. I reflashed a few times but whenever a restored anything from Titanium it would revert back to landscape only. I decided to go back to a 2.2 rom and plugged in the phone to Odin and it was not recognized, also not as a mass storage device, no go. I used Samba to copy a 2.2 rom, Trigger, to the phone and flashed from there. The phone is good now except the computer still won't recognize it. I can use Samba to access the SDCard but I hate not being able to use Odin if things go south. Tried all usb ports and a new cable, no go. Really wierd.
Looking for suggestions......
If you're still under warranty claim it & send it.
Had same problem. There is no fix short of replacing USB port.
I found my problem. It was dirty/corroded usb port. I carefully cleaned it out (took a few times) and it's all functioning again. I also cleaned the contacts on my original usb cord and it is working again also.
I'm just now having this problem for the first time. I've tried all USB ports and cleaning the port on the phone with no luck so far. Can someone point me to the unbrickable mod mentioned early in this thread?
jnusz said:
I'm just now having this problem for the first time. I've tried all USB ports and cleaning the port on the phone with no luck so far. Can someone point me to the unbrickable mod mentioned early in this thread?
Click to expand...
Click to collapse
Have you tried installing the installing/re-installing the Samsung drivers (LINK), using another USB cable, or even another computer? I just want to make sure you've tried it all before attempting to do a hardware mod.
Anyhow, you can find a link to the unbrickable mod and other hardware mods in the "Official XDA Vibrant Bible Thread", under the "MODS/SCRIPTS" section (LINK).
Mine is the cable btw. My wife has a GSII and I was able to use her cable.
Ok so I was previously running Hydr0g3n ICS ROM an older version and I had mount problems where only internal sd would mount, but it mounted at least. Occasionally I'd have to reboot my laptop because of no detection but that'd fix it.
Fast forward to a couple of days ago and I installed Resurrection Remix 04/05 but got really weird issues when connecting to my laptop e.g. installing device drivers, failing, usb sounds coming and going, device being recognised then disappearing again. Eventually no response. I reflashed, fully wiped, everything, experimented with drivers. Then plugged it into a mates (newer) laptop and it worked?
Back to mine, didn't work, installed Hydr0g3n ICS 05/05 which ran a lot smoother but still same issues, I repeated the steps above and even after device drivers actually successfully installed, it'd work and then next day no response or detection when plugging in USB. Since then I've gone through the drivers route again, trying all sorts of windows fixes, it still works fine when plugged into a newer laptop.
So after all my research etc I've realised that it seems to be some sort of power issue with the phone/ROM, perhaps the newer laptops have more USB hubs which aren't shared between many devices and so it works but mine is very intermittent if not non-existent. Oh, all other USB devices work, flash drives, external hard drives, I have never had any issues with any USB devices. Just this.
Also, I've tried toggling USB Debugging, and MTP UMS PTP, nothing. Read something about fast charge but have no notification that it's enabled on boot and no option to disable it in Kernel tweaks since I'm not on a supported kernel.
Hydr0g3n ICS ROM 2012 05 05 SGS2
3.0.29 Siyah v3.1.2
Any help would be much appreciated.
UPDATE:
I ordered a powered USB hub off eBay, it arrived today and did not work with the phone.
UPDATE 2:
So I recently stole my dads TouchPad and installed AOKP on it, my laptop detected it absolutely fine in MTP mode.
It uses the same cable so I figured, why not?
I plugged it in and hey presto, it popped up -_-
It's so strange the stock cable works on everyone elses laptops but mine, I don't know if it'll still work tomorrow though, I suppose if I don't re-comment then it still is working.
Bump?
FatPhysicsBoy said:
Ok so I was previously running Hydr0g3n ICS ROM an older version and I had mount problems where only internal sd would mount, but it mounted at least. Occasionally I'd have to reboot my laptop because of no detection but that'd fix it.
Fast forward to a couple of days ago and I installed Resurrection Remix 04/05 but got really weird issues when connecting to my laptop e.g. installing device drivers, failing, usb sounds coming and going, device being recognised then disappearing again. Eventually no response. I reflashed, fully wiped, everything, experimented with drivers. Then plugged it into a mates (newer) laptop and it worked?
Back to mine, didn't work, installed Hydr0g3n ICS 05/05 which ran a lot smoother but still same issues, I repeated the steps above and even after device drivers actually successfully installed, it'd work and then next day no response or detection when plugging in USB. Since then I've gone through the drivers route again, trying all sorts of windows fixes, it still works fine when plugged into a newer laptop.
So after all my research etc I've realised that it seems to be some sort of power issue with the phone/ROM, perhaps the newer laptops have more USB hubs which aren't shared between many devices and so it works but mine is very intermittent if not non-existent. Oh, all other USB devices work, flash drives, external hard drives, I have never had any issues with any USB devices. Just this.
Also, I've tried toggling USB Debugging, and MTP UMS PTP, nothing. Read something about fast charge but have no notification that it's enabled on boot and no option to disable it in Kernel tweaks since I'm not on a supported kernel.
Hydr0g3n ICS ROM 2012 05 05 SGS2
3.0.29 Siyah v3.1.2
Any help would be much appreciated.
Click to expand...
Click to collapse
just try 2 flash the latest siyah kernel and check
On Windows 7, after several USB connect-disconnect, I would experience Windows not responding to connection any more on that very USB port.
I usually have adb server running in background, so "Safely remove" feature is blocked, and I would simply remove after file operations are over.
I made a .bat file on desktop, that simply performs "adb kill-server", so that I can safely remove it, and have not experienced this problem since then.
Sun90 said:
just try 2 flash the latest siyah kernel and check
Click to expand...
Click to collapse
I've tried all of the kernels, Siyah, Thoravukk, NEAK, and multiple versions of Siyah too, including the latest one.
Also my powered USB hub arrived today and it did not remedy the issue.
mirbeksm said:
On Windows 7, after several USB connect-disconnect, I would experience Windows not responding to connection any more on that very USB port.
I usually have adb server running in background, so "Safely remove" feature is blocked, and I would simply remove after file operations are over.
I made a .bat file on desktop, that simply performs "adb kill-server", so that I can safely remove it, and have not experienced this problem since then.
Click to expand...
Click to collapse
Could you perhaps explain this a little more to me?
I plug it in and literally it charges but absolutely nothing else happens. Anything else works in the same port, just not the phone for some reason.
USB problems basics .
USB port should be mainboard port .
Usb Port on phone multiple USB problem posts say clean port .
Kies or Samsung USB drivers should be installed with Kies not running .
USB cable try Samsung cable or another .
Try USB debugging off and or on .
jje
JJEgan said:
USB problems basics .
USB port should be mainboard port .
Usb Port on phone multiple USB problem posts say clean port .
Kies or Samsung USB drivers should be installed with Kies not running .
USB cable try Samsung cable or another .
Try USB debugging off and or on .
jje
Click to expand...
Click to collapse
1) Yes they are all mainboard ports - No response.
2) Have cleaned USB ports on mainboard many times. This seems irrelevant too since all other devices are recognized.
3) Have also experimented with combinations of this. (All combinations) Nothing.
4) I have only tried the Samsung cable since it's all I have, and it works on all of my friends laptops.
Also, I plug it in, and it draws power (aka it charges) but nothing else. Not even a windows 'bong'. Even with the powered USB hub, it still only charges.
However the minute I plug it into a friends laptop it seems to work just fine.
@ op
goto device manager and uninstall the android devices you see there with the option "delete device drivers completely" and make a reboot.
now install the usb drivers and plug in the device.
FatPhysicsBoy said:
1) Yes they are all mainboard ports - No response.
2) Have cleaned USB ports on mainboard many times. This seems irrelevant too since all other devices are recognized.
3) Have also experimented with combinations of this. (All combinations) Nothing.
4) I have only tried the Samsung cable since it's all I have, and it works on all of my friends laptops.
Also, I plug it in, and it draws power (aka it charges) but nothing else. Not even a windows 'bong'. Even with the powered USB hub, it still only charges.
However the minute I plug it into a friends laptop it seems to work just fine.
Click to expand...
Click to collapse
This last point tells me there are possibly some registry settings on your computer that are keeping the drivers from loading properly.
I've never had to do this, so I don't know what to look for EXACTLY, but you may need to get a registry cleaner and try to eradicate all traces of Kies and Samsung drivers from your computer, then re-install either Kies (to get the drivers) or the stand-alone USB drivers.
I remember reading another post some time back about some other guy who actually totally re-installed Windows... which is a bit like using explosives to kill a mosquito, if you ask me.
However, try bala_gamer's suggestion first. That may be all that is needed.
FatPhysicsBoy said:
1)
2) Have cleaned USB ports on mainboard many times. This seems irrelevant too since all other devices are recognized.
NO its the phone USB port .
Agree that if all fails try reinstall of Kies and drivers after a delete .
Delete registry kies .
[HKEY_CURRENT_USER\Software\Samsung]
[HKEY_LOCAL_MACHINE\SOFTWARE\SAMSUNG]
jje
Click to expand...
Click to collapse
bala_gamer said:
@ op
goto device manager and uninstall the android devices you see there with the option "delete device drivers completely" and make a reboot.
now install the usb drivers and plug in the device.
Click to expand...
Click to collapse
So believe it or not I didn't actually go into detail in the op! But a few more things to note are that the device does not show up in device manager at all. Even with shadow device detection enabled. I have used all manner of driver software available to clear out all old usb drivers/any drivers which may be conflicting etc. I have also removed and reinstalled the usb host controllers and root hubs many times
ctomgee said:
This last point tells me there are possibly some registry settings on your computer that are keeping the drivers from loading properly.
I've never had to do this, so I don't know what to look for EXACTLY, but you may need to get a registry cleaner and try to eradicate all traces of Kies and Samsung drivers from your computer, then re-install either Kies (to get the drivers) or the stand-alone USB drivers.
I remember reading another post some time back about some other guy who actually totally re-installed Windows... which is a bit like using explosives to kill a mosquito, if you ask me.
However, try bala_gamer's suggestion first. That may be all that is needed.
Click to expand...
Click to collapse
Yes, indeed I also believed it to be some sort of registry problem, I have also used tune up utlities, registry mechanic and ccleaner (I think thats all there was!) and run registry scans/cleans/fixes/defrags. To no avail. I was actually considering reinstalling windows or something.
JJEgan said:
FatPhysicsBoy said:
1)
2) Have cleaned USB ports on mainboard many times. This seems irrelevant too since all other devices are recognized.
NO its the phone USB port .
Agree that if all fails try reinstall of Kies and drivers after a delete .
Delete registry kies .
[HKEY_CURRENT_USER\Software\Samsung]
[HKEY_LOCAL_MACHINE\SOFTWARE\SAMSUNG]
jje
Click to expand...
Click to collapse
Yes, my bad, I have also cleaned that too. Also I didn't think it could be that since it seems to work on everyone elses laptop.
Just deleted those registry entries, rebooted. Nothing. Deleted a few more from old software which seemed to still be floating around, rebooted. Nothing.
:'(
Click to expand...
Click to collapse
I had the same problem with AOKP ROMs
I had the same problem with AOKP ROMs and then I installed MIUI and it worked again, I guess you can try any other ROM (not AOKP) and check if it solves your problem.
So I recently stole my dads TouchPad and installed AOKP on it, my laptop detected it absolutely fine in MTP mode.
It uses the same cable so I figured, why not?
I plugged it in and hey presto, it popped up -_-
It's so strange the stock cable works on everyone elses laptops but mine, I don't know if it'll still work tomorrow though, I suppose if I don't re-comment then it still is working.
Hi guys!
I have a rooted international Galaxy S3 (i9300) phone with a custom rom: UltimaRom (version 8.x), and using XXELLA kernel (?) and XXELLA Modem version.
Since a while, I'm trying to manage the files in it (phone memory or sd card) from my computer, simply by using an USB cable (the one given with the phone or even other cables, it doesn't matter) and the standard MTP protocol, which is used by Google since Android 3.0. And, whatever I try to do, Windows doesn't seem to notice anything. In my device manager, nothing appears. Nothing either in the "My Computer" window, it just doesn't "exist". No reaction at all from Windows. The Phone's charging, but this is all it is.
And I have the same problem using another computer (like my own laptop, or my brother's one). All computers are running Windows 8 x64 Pro.
I tried to install, re install, delete, etc. all the phone drivers I have on this computer, tried to install Samsung Kies, tried some "mounting" apps on the Play Store, nothing's working.
What should I do to make it work?
Thanks a lot!
Might be stating the obvious but is your phone set at usb debugging? I have the same issue from time to time but when I unplug and plug back it fixes itself.
Hope you get your stuff fixed soon.
Sent from my GT-I9300 using xda app-developers app
Thanks for your response.
Yes, USB Debugging is enabled.
Jiraiya-08 said:
Hi guys!
I have a rooted international Galaxy S3 (i9300) phone with a custom rom: UltimaRom (version 8.x), and using XXELLA kernel (?) and XXELLA Modem version.
Since a while, I'm trying to manage the files in it (phone memory or sd card) from my computer, simply by using an USB cable (the one given with the phone or even other cables, it doesn't matter) and the standard MTP protocol, which is used by Google since Android 3.0. And, whatever I try to do, Windows doesn't seem to notice anything. In my device manager, nothing appears. Nothing either in the "My Computer" window, it just doesn't "exist". No reaction at all from Windows. The Phone's charging, but this is all it is.
And I have the same problem using another computer (like my own laptop, or my brother's one). All computers are running Windows 8 x64 Pro.
I tried to install, re install, delete, etc. all the phone drivers I have on this computer, tried to install Samsung Kies, tried some "mounting" apps on the Play Store, nothing's working.
What should I do to make it work?
Thanks a lot!
Click to expand...
Click to collapse
That's odd.. I use Ultima ROM and have updated to 8.1.1. I just checked just to make sure (my last update was done OTA) and yeah, computer recognized phone right away.. heard a little computer sound and everything. I am also running Windows 8
The base changed in v8. If you haven't done a fac reset since then you should try that.
Ok I just tried to make a factory reset, nothing changes...
Oh, and if that can help: when the phone's booting, Windows says "Unrecognized device". When it's booted up, it disapears.
Anyone ?
Drivers...
I used these drivers.
It worked for me...
http://forum.xda-developers.com/showthread.php?t=1564104
Work for me too! THX
Thanks for your help !
Unfortunately it didn't work for me.... :/
Any other ideas ?
Sorry to keep rising this thread but this issue is really annoying... :/
Up
I still have the same problem. No other ideas please ?
? :/
Does Easy UMS work?
Can you connect via adb?
Does Odin recognize the phone?
If no to all of the above, try a different cable / port
Glebun said:
Does Easy UMS work?
Can you connect via adb?
Does Odin recognize the phone?
If no to all of the above, try a different cable / port
Click to expand...
Click to collapse
Thank you for your response !
- Easy UMS doesn't seem to work, even if the app doesn't show any error on the phone
- How do I connect via ADB ? I tried to connect the phone while it is in Download Mode, nothing appears on Windows or Odin
- As I said, in Download Mode, Odin doesn't seems to recognize anything...
And of course, I already tried to change the cable, the USB port, or even the computer i'm connecting the phone to...
Thanks again for your help
Starting to sound like a damaged micro USB port on the phone possibly, or a driver's problem
Oh, and there's a thing: when I reboot the phone, while the Samsung logo appears on the screen with the short jingle, the PC makes 3 or 4 times a sound like something has been plugged, and showes a "Unrecognized device" warning window. When the boot is finished, and the rom is loaded, everything just disappears and no sound is any longer made by the PC.
Also, please note that when I connect the phone to the PC (using the same PC, cable and USB port of course), the phone charges up just like before, without any problem.
have you tried the old drivers?
search Google for " Samsung USB drivers 1.4.6.0 "
disconnect your computer from the internet
Install the drivers.
don't reconnect to the internet.
connect your phone and let windows find the drivers
Hey,
I have been using CM12.1 Nightlies since January, and I've been experiencing bugs related to USB recognition. Yesterday I've updated to CM13 thinking that it would solve this issue, but it haven't.
What happens is that I can't use USB storage/MTP/Odin/direct plug adb because my phone doesn't get recognized by the OS. I think that the USB port is not damaged because I can charge it when connected to my PC . I used to have CM11 and it worked fine, I think that maybe it is something related to the build itself..?
I have already tried a lot of methods, USB debug on/off, different cords, OSes (Tried on Windows, Mac, Linux), multiple adb/samsung drivers, apps.. nothing has worked so far.
I can only access the internal data using an external SD card or through network adb.
I think that the USB module was overwritten, because it looks undentified in every device that I've tested.
Has anyone experienced something like that? any tips, tests, or patches that I've missed?
Thanks.
Did you install Google USB Driver? I had to install this one to get my device on CM 13 recognized. It should work "out-of-the-box" on Linux distros though if you've got libmtp installed (for MTP browsing).
matee89 said:
Did you install Google USB Driver? I had to install this one to get my device on CM 13 recognized. It should work "out-of-the-box" on Linux distros though if you've got libmtp installed (for MTP browsing).
Click to expand...
Click to collapse
The device doesn't get recognized by Windows, it doesn't even show up on the connected devices list. The funny thing is that the phone actually charges, so it is not a dead usb connection...
I think that I'll have to replace the USB PCB...
Hello,
i tried to flash twrp to my i9100.
I had cm12.1 with cyanogen recovery and tried to apply update for :
"recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab)"
and
"kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100"
but know my phone is not starting anymore.
I already know that i used 13 kernel for 12.1 system and that was wrong.
I can access ODIN Mode but my pc (win10) and Odin v.3.10 don´t recognize my S2.
Can you tell me how to solve my problem?
i9100cm said:
Hello,
I can access ODIN Mode but my pc (win10) and Odin v.3.10 don´t recognize my S2.
Can you tell me how to solve my problem?
Click to expand...
Click to collapse
Try reinstalling Samsung USB drivers. If that didn't work then try it on another computer.
Now my S2 is getting recognized again.
But i geht the error code 43.
The device description is failured.
Kevin3014 said:
Try reinstalling Samsung USB drivers. If that didn't work then try it on another computer.
Click to expand...
Click to collapse
Kevin, how to flash lanchon kernel without recovery?
because my recovery is cyanogenmod recovery cm13 it cannot update from sdcard..
Abdullah Yusoff said:
Kevin, how to flash lanchon kernel without recovery?
because my recovery is cyanogenmod recovery cm13 it cannot update from sdcard..
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
Read this thread, it has the answer to your question.
Hey, OP here.
So just updating my status, I bought and replaced the Micro-USB connector and everything is working now, the device is recognized by the OS and I'm able to use use Odin/ADB normally.
If anyone out there is having the same issue, I recommend buying a new Micro-USB PCB. This phone is from 2011, batteries and connectors might stop working...
Thanks everyone for helping me out!
Thyrr said:
Hey,
I have been using CM12.1 Nightlies since January, and I've been experiencing bugs related to USB recognition. Yesterday I've updated to CM13 thinking that it would solve this issue, but it haven't.
What happens is that I can't use USB storage/MTP/Odin/direct plug adb because my phone doesn't get recognized by the OS. I think that the USB port is not damaged because I can charge it when connected to my PC . I used to have CM11 and it worked fine, I think that maybe it is something related to the build itself..?
I have already tried a lot of methods, USB debug on/off, different cords, OSes (Tried on Windows, Mac, Linux), multiple adb/samsung drivers, apps.. nothing has worked so far.
I can only access the internal data using an external SD card or through network adb.
I think that the USB module was overwritten, because it looks undentified in every device that I've tested.
Has anyone experienced something like that? any tips, tests, or patches that I've missed?
Thanks.
Click to expand...
Click to collapse
hey..if no method works for you i have simple way..to turn on usb debugging and for odin (means from this way odin will recognose your mobile)...just flash the new simple custom rom with lower android versions and then turn on usb debuging mode....thats all ...i also strucked in this problem but i did this and all works fine...sry for my bad english and typing
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