Develop Bugs

[solved] attempted root, possibly bricked kindle, computer wont detect at all

i live in australia, and got a kindle fire for my b'day, and wanted to access the features that arnt allowed outside the US. my first search i came across rooting it, and it seemed straight forward, the instructions, which was for kindle fire utility. i installed the drivers, then did run.bat, that worked and detected the kindle. then it said to go to bootmode menu, then install permanent root with superuser. it lasted about 2 seconds then it rebooted the kindle. thats it. unless i misread something. it looked exactly the same as before, i didnt know what to expect, but some hint that something had changed, so i figured it didnt work. then i saw the bootmode menu, and selected normal, and that just reset it, then chose fastboot, not knowing what it did. so i tried that. now my kindle isnt detected by the pc at all, it just says kindlefire on the screen, and the power light is orange.
most of the fixes i have come across all start with "we assume you have this or this installed on the kindle, and that it is detected in some way by the computer". but it isnt being detected at all. i saw the fireusb thing, with ubuntu, i attempted that, but it didnt seem to recognise the fk file, which was only 9mb, it was the only file the instructions said to take, and that its supposed to unpack to more tools to manage it and get it to register that the device is plugged in.
then the only thing else i could try was opening the back of it, and doing the shorting out thing, then plugging it in, but KFU didnt detect it and not sure what else to try. i am a complete noob at this i know, so i dont know where to go from here.
edit: turns out the kindle doesnt like being detected in 3.0 usb, or usb hubs. so if you are trying to get it to detect, use the ones in the back of the pc lol... soo much wasted time on this over such a simple thing, but im glad it was a simple mistake, and not a major problem. though now i have the issue of having small sratched and stuff on the side when i opened the case, but oh well, learn from my mistakes!

have you tryed holding the power button for like 20 seconds and completely powering it off then powering it back on? Chances are your stuck in fastboot many people lately have had this happen so your not alone. Some say to power it off have the kindle fire utility window open plug your kindle in it should power back on then recheck status. Look in device manager and see how it appears there windows is terrible with drivers when this happens it will try to install what it thinks best even if the device is unknown rendering adb useless until the driver is reinstalled correctly. Most the time this is not enough to set the bootmode back to normal because it cannot detect your device correctly. http://forum.xda-developers.com/showthread.php?t=1670405 this may help but its not the only thing that can be done. If some of the files actually did get pushed to your device such as fff the bootmode can be changed via the bootloader. Try the power down thing see what you get and post back.
---------- Post added at 01:03 AM ---------- Previous post was at 12:12 AM ----------
also look at this thread http://forum.xda-developers.com/showthread.php?t=1670300
Another thing simply just rooting your device does not change how it appears its not until you install twrp and fff that it changes there are simple ways to do that first we need to get your boot mode corrected and ensure you are rooted then the rest can get sorted out. Check how your device is listed in device manager first.

sorry for the delay. spent all day just trying to install ubuntu, then connecting to the internet wirelessly, seems to have a lot of issues. anyway, in the end i got it all set up, followed that guide, then ran firekit, but still not detected. in windows and ubuntu, when its plugged in by usb, nothing at all shows up in device manager, or lsusb. ive tried doing the short trick, then plugging it in, still doesnt get detected. and honestly i think when i thought i rooted it, i may have misclicked and instead of selecting instant permanent root or whatever that command was, i just did a normal boot, so im pretty sure i selected fastboot for a stock kindle. i know the usb cord works cause i use it for my phone.
adb devices doesnt detect it either. i got all the doesnloads from the link you posted, would they all be up to date? also the adb_usb.ini file, had to get online, but not sure if that matters.

In Linux, type
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
...and make sure you have the following:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Reboot to save any changes you've made and check "lsusb" again.

i added both those rules, one of which was already in there, but it still isnt being detected. typing lsusb, then up and enter repeatedly as i plug it in doesnt show any changes at all, its not being detected.

While unplugged, type
Code:
udevadm monitor --environment
Plug it back in and see if you get a result.

sadly not. tried plugging other things in, they all appeared, also my phone with the same cord. but nothing at all when i tried the kindle, with it powered off when plugging it in, and with the shorting out thing, nothing at all. i dont understand how booting in fastboot by accident, with a stock kindle, could make it not be detected at all, ive read people causing worse things getting it to at least be picked up. im pretty sure thats all i did, i cant think of how i could of done anything worse.

That's interesting...I'm having the same problem with mine but I was led to believe it was my VM causing the problem.
So, just to make sure...
Are you using a VM Linux install or USB or other?
Have you tried multiple usb ports?
Do you have FireFireFire installed and if so, what version are you using? (If you're not sure, what does your boot logo look like?)
What Linux distro/version are you using?

this is the first time ive ventured outside windows, so not sure what you mean by vm, but i installed ubuntu with a disc, to a second hard drive that i had in my comp.
and nope, dont have firefirefire installed, im pretty sure its just a stock kindle still, just stuck in fastboot by mistake, and not being detected by any usb port.
also, would a factory cable work? if its makes it boot differently, you would think it would? i really suck at making things, but http://forum.xda-developers.com/showpost.php?p=23049902&postcount=254 is selling them. sure it would probably take 2 -3 weeks, but if it works then thats better then not using it forever lol. and if i get it fixed before it even arrives, well, cant complain about that.

A factory cable will only help if you can get Linux to detect your device. Considering you can't get Linux to detect any USB event when plugging your Kindle in, it most likely points to a problem with your Linux install.
It would be very helpful to know what version of Ubuntu you are using.

Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
though there is a few updates in theupdate manager. but last time i installed them, it completely disabled my wireless adapter and ened up reinstalling ubuntu to get it to work again cause i couldnt figure out how to get it detected again. but redownloading it all now to see if its any different. i hope it is just a problem with the install, at least thats something i can work on.

at soupmagnets suggestion, i made a liveUSB, which i had tried to do earlier, but didnt succeed, where as now it does work, im pretty sure i have the drivers now installed, but not sure where to go from here, with it still not being detected at all.

haaa... im an idiot. just putting that out there. ok, so i got the kindle detected. turns out it was the usb ports. one was usb 3.0, and the others were in a hub, which apparently the kindle doesnt like. i got frustrated and plugged it into the back of the pc, and it is now unknown device in device manager. thinking i should go back into ubuntu, see if its also detected there, and go from there

oh yeah the usb is a problem and use 2.0 and go back to ubuntu you will see its detected in a couple hours Im gonna retest soups script for udev rules but I think you will have success now
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
in fact I think using 3.0 usb is quite dangerous

i didnt go back to ubuntu, i just used KFU again, and just tried doing normal boot. and it worked. its back up and working. ill try rooting it again now, being more careful this time, sorry for the waste of time, but thanks to soupmagnet for helping. now that its back to stock, i do stil lwant to root it, and now with ubuntu installed, what is the best noob friendly guide to use to just get the basic things up and running.

yayyy Im glad you got it goin check allow installation from unknown sources under device and install twrp first then fff bootloader no need to root flash a rom and gapps once your familiar all roms are rooted
You can select these options in kfu watch the dialogue on the screen you can see the files downloading and getting pushed to your kindle just make sure your connected to the net I suggest running one of the options without your device plugged in first do a reboot on your computer plug your kindle in check for adb online boot status normal and go for it
---------- Post added at 11:38 PM ---------- Previous post was at 11:23 PM ----------
or go this route http://forum.xda-developers.com/showthread.php?p=24129239

[Q] Bricked Kindle

I was given a "bricked" kindle to take a look at last week. Here is the story I was given.
User installed a custom rom, but it was for a lower version (didnt fully understand this)
Afterwards it locks on the kindle fire logo during boot.
User made a factory cable to restore the unit, and now anytime ANY usb is plugged into the device it shuts off immediately.
I tried opening the device and shorting the required pins, but plugging in the usb doesnt do anything. It appears to be charged, but I have no way of knowing.
It doesnt show as anything in device manager (it looks to be fully off)
Pressing the power button still gets it to start and hang at the kindle logo.
My guess is the factory cable was made incorrectly and shorted the usb board but I figured I would see what others thought.
Thanks

Any opinions?

I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.

narume said:
I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.
Click to expand...
Click to collapse
Thanks for the thought, but nothing shows in device manager. I believe this is due to the kindle shutting off the second you plug any usb into it.

bump?

The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know

Thepooch said:
The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know
Click to expand...
Click to collapse
I'll definitely try the factory cable again (the user tried this, but who knows)
But as far as the device not being recognized... Like I said, the second you plug it into usb (either computer, or power plug) it shuts off.
Its not that I get a windows notification for "not recognized" windows doesnt see it period.

it should not turn your device off it should appear stuck at the logo like I said sounds like a bad build guess you misunderstood
---------- Post added at 06:45 PM ---------- Previous post was at 06:38 PM ----------
only use a 2.0 usb port and try it from the device in an off position

[Q] Nexus 7 (flo) not connecting to PC????

im not sure if ive been looking in the wrong places but i cant find an answer to my problem. so i rooted my nexus 7 about a week ago and installed twrp. everything was working fine until i accidentally pressed wipe data instead of factory reset. i deleted EVERYTHING on my tablet including my operating system, the only thing left was twrp :crying: today my otg usb cable came in and i installed that unofficial cyanogenmod build and now it wont connect to my pc. i have usb debugging on and everything. i go to device manager (on my pc) and it is listed as "Nexus 7" but when i try to install the usb drivers it says that they dont work for it. how can i get the usb drivers to work again?
Note: its not my pc cause my rooted s3 works just fine with my pc.
sorry for being a noob! and thanks for the help!

I actually have the same issue where my Windows won't let me navigate my N7 as a portable device. Tried a whackload of drivers and the like to no avail. To transfer files I just end up using ES Explorer. Funny enough, ADB in recovery works just fine.

If it is the same as PA and PAC, try Settings > Storage > Press Menu > USB > Check MTP
Sent from my Nexus 7 using Tapatalk 4

BigDaddySunshine said:
im not sure if ive been looking in the wrong places but i cant find an answer to my problem. so i rooted my nexus 7 about a week ago and installed twrp. everything was working fine until i accidentally pressed wipe data instead of factory reset. i deleted EVERYTHING on my tablet including my operating system, the only thing left was twrp :crying: today my otg usb cable came in and i installed that unofficial cyanogenmod build and now it wont connect to my pc. i have usb debugging on and everything. i go to device manager (on my pc) and it is listed as "Nexus 7" but when i try to install the usb drivers it says that they dont work for it. how can i get the usb drivers to work again?
Note: its not my pc cause my rooted s3 works just fine with my pc.
sorry for being a noob! and thanks for the help!
Click to expand...
Click to collapse
Were you on stock before you wiped? Trying going back to stock and see if you can get MTP working, then start introducing the parts until you figure out what broke.
The USB IDs for the MTP device change more often than you'd expect causing recognition problems.
For example, on stock, with USB debugging enabled, it advertises one USB ID and also sends out a MTP-compatible flag. When USB debugging is disabled, a different USB ID is sent, minus the MTP-compatible flag.
I helped someone on a different ROM force the MTP device drivers to associate, but then the drivers couldn't initialize the device. This might indicate there is a problem on the ROM side.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
verkion said:
I actually have the same issue where my Windows won't let me navigate my N7 as a portable device. Tried a whackload of drivers and the like to no avail. To transfer files I just end up using ES Explorer. Funny enough, ADB in recovery works just fine.
Click to expand...
Click to collapse
If your ADB works in recovery then you must have installed some other adb device driver, other than Google's, at some point.
If you want I can try helping you get things recognized on this thread
http://forum.xda-developers.com/showthread.php?t=2391236

swagstr said:
If it is the same as PA and PAC, try Settings > Storage > Press Menu > USB > Check MTP
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
this

HELP! Lumia 640 Device Not Recognized - Device Descriptor Request Failed

So lately I've been having more and more issues with my Lumia 640, such as random reboots, data switching, and slow downs. I decided that since I haven't preformed a hard reset since about 2 builds ago, it was time for it. I went ahead and reset, and everything appeared to be working better. It was when I plugged my phone into the laptop to dev unlock and deploy tools that I ran into trouble. As soon as I plug it in, I get the device connected sound followed by USB Device Not Recognized error, a Phone charging slowly message on the phone, and then a device unplugged sound from the laptop. I tried it on my desktop and get the exact same results. Both my computers are running Windows 10, and my 640 is on latest 10586 build.
I've tried everything I could think of/find online including
-Soft reset the device while plugged
-Using different Usb cable
-Uninstalling the device (read below)
-Rebooting the PC and letting it turn the phone on with it
-Uninstall all Usb Root Hubs
Unplug PC power cord/battery and Usb devices and wait 10-15min
-Developer Mode on/off
-Hard Reset phone again
I really don't know what else to do. When I plug it in and get the not recognized error, it's a Descriptor Request Failed, and then the device disconnects. In Device Manager it shows under Universal Serial Bus (as an Unknown device with the Descriptor Request Failed next to it) until it disconnects itself, then it disappears. Using Show Hidden Devices and a command to enable showing every device ever connected (plugged in or not), I see it show but it's greyed out and it's properties page says it's disconnected. While showing all hidden devices, I uninstalled the phone under Portable Devices as it used to work, along with my wife's phone.
Nothing I've done has gotten me anywhere. It just connects with the error and immediately disconnects. It used to work with both the laptop and desktop before I hard reset. The only thing i believe could be causing it was the fact that before the reset my phone was being faked as a Lumia 1520. But I've uninstalled that in the hidden devices of Device Manger.
Any help would be greatly appreciated. As it stands, I can't developer unlock, deploy tools, or even copy my pictures!
Edit- just tried plugging it into 2 other computers with WinXP (. I know it's not supported), and also get the device not recognized and charging slowly. So... Either the firmware/os git messed up, or the Usb jack is messed up.

I have also have same problem. If you find the solution. Pls let me know. problem is you cannot roll back to 8.1 without connection to PC
---------- Post added at 02:54 PM ---------- Previous post was at 01:56 PM ----------
probably this can help
http://mobifaq.com/why-can-t-i-connect-my-lumia-640xl-to-my-laptop/t9893/

Does device charge properly using AC? Based your trouble shooting so far it seems like it be the Usb port acting up.. I am assuming the Usb cables were 6ft and under? Did you flash any non stock rom to the phone? And what do you mean faked as a 1520? If the phone acts weird while charging it definitely could be the phones Usb port. If not you can put the phone in flash mode and use thor2 list device connection list to see if and how long the phone is being detected by windows.

OP, you have interopunlocked phone with FS acces?

augustinionut said:
OP, you have interopunlocked phone with FS acces?
Click to expand...
Click to collapse
as a matter of fact yes, to both!
anubis23 said:
Does device charge properly using AC? Based your trouble shooting so far it seems like it be the Usb port acting up.. I am assuming the Usb cables were 6ft and under? Did you flash any non stock rom to the phone? And what do you mean faked as a 1520? If the phone acts weird while charging it definitely could be the phones Usb port. If not you can put the phone in flash mode and use thor2 list device connection list to see if and how long the phone is being detected by windows.
Click to expand...
Click to collapse
charging is perfectly fine. I also suspected the Usb port, but after an online chat with Cricket Support, they assured me it was a software issue.
animesh_shah said:
I have also have same problem. If you find the solution. Pls let me know. problem is you cannot roll back to 8.1 without connection to PC
---------- Post added at 02:54 PM ---------- Previous post was at 01:56 PM ----------
probably this can help
http://mobifaq.com/why-can-t-i-connect-my-lumia-640xl-to-my-laptop/t9893/
Click to expand...
Click to collapse
the thing is, I couldn't even restore to 8.1 with my issue. The phone would not stay connected long enough to be identified by the OS let alone the Recovery Tool.
However, I have good news. I did finally solve the problem. When I had realized that connecting the phone while in the boot loader got it to detect and install as Lumia BootMgr, I opened up the Recovery Tool and sure enough it was detected. I let it start downloading the ROM, and about 1/2 way through I heard the device disconnected sound and thought oh great this isn't going to work either. However, the download kept going, and when it finished I clicked the start install button, but it gave an error saying the device was not detected. So with the phone still plugged in, I preformed a soft reset and continued holding Volume down to boot back into the boot loader. When I came to the ! screen and the phone was detected again as Lumia BootMgr, I clicked Retry in the Recovery Tool and it actually copied over the ROM, which thankfully is a very quick process.
Once 8.1 had finished setting up the phone was detected and installed perfectly on the computer. Last night I updated back to W10 and it's still detecting without an issue. I'm for sure not enabling the Full Filesystem Access hack again. Before this problem started I was already tired of waiting up to 30 minutes at a time for it to connect. Only reason I did it was to copy the custom HOSTS mod file to block ads, which I'd love to do again, but it's just not worth it.

So, if FS acces, enter device manager on pc, disable windows phone, enable windows phone.... wait a minute...voila

augustinionut said:
So, if FS acces, enter device manager on pc, disable windows phone, enable windows phone.... wait a minute...voila
Click to expand...
Click to collapse
Are you referring to the problem I was having? If you are, then reread my OP. You'll see that Device Manager would not even display the phone because the phone would immediately disconnect after the USB Device Not Recognized error popped up. There was simply nothing to disable, or enable for that matter.
If your saying to disable and enable AFTER applying the FS access hack to affect the detection time, then please, elaborate on that.

Erase driver, reinstall driver, try with another pc, sell the phone....

@x_orange90_x
http://forum.xda-developers.com/win...de-filesystem-access-sftp-windows-10-t3185766

augustinionut said:
Erase driver, reinstall driver, try with another pc, sell the phone....
Click to expand...
Click to collapse
you obviously did not reread the OP.. I tried all of those with the exception of the last with no sucess.
And I think you've missed my point entirely.. I solved the issue already. Hopefully the other member that posted in here with the same problem can fix it by following what I did.

You right.. disable full fs access....

You still active Mr. Orange

usb data not working after september update

USB cable only charges the phone when connected to computer. Tried the following
1. Using 2 different cables which previously worked for data but phone only shows charging.
2. Using pc and Mac and both does not see phone. Looked in device manager of windows but it nothing shows up. Both computer previously used for data transfer on this phone
3. Looking inside usb-c port but no lint or dirt. Although just before update to September security patch my phone has some water on the screen which I wiped off. And the phone does not show sign of problem other than no data transfer to computer
4. Factory reset phone and same thing
5. No notification shown for changing charging only to file transfer
6. Computer doesn't Bing when connected.
What else can I try? Anyone can help or confirm if their usb-c works after September update so I can narrow down to hard ware problem.
Anyone diagnosed this hardware problem before?

Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.

jd1639 said:
Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.
Click to expand...
Click to collapse
I tried changing the options to MTP, PTP, midi, charge only, etc but non of them make any difference to the computer, nothing pops up and does not show as new item connected in device manager

did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.

jd1639 said:
did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.
Click to expand...
Click to collapse
Tried changing when USB connected and when not. Doesn't seem to make a difference.

I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware

jd1639 said:
I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware
Click to expand...
Click to collapse
I don't know how I can flash a previous firmware if I don't have USB access.. it's really frustrating. Looking from ifixit. It does not seem there is any chip near usb-c other than voltage control.
Can't seem to find how I can look at logs to know if USB has been engaged or if there is any error message. It's all dead end and my phone seem to be the unique case.

Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4

jd1639 said:
Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
Click to expand...
Click to collapse
USB worked fine, I am using it for Android studio, and transfered music across as well. Looked at the post and it seemed that has to do with device manager. Problem is mine does not show up any changes to device manager. I.e . No ADB or other device. Seemed like no data is exchanged and windows treating it like a battery or something

Any fix for this?
I've hit the same issue and wondering if anybody has a fix for this yet?
I'm using linux and seeing no usb activity at all from my nexus 5x after sep 17 update.
I've tried multiple cables. Cleaned the usb port on the phone. Multiple PCs.
I've connected to the phone using adb over tcpip and seeing nothing in logcat except battery logs when the usb cable is plugged in and out.
Turned usb debugging off and on.
I've set usb mode in developer options to mtp (it was on 'charging') and restarted the phone. Then find the option is forced back to 'charging.'
Logcat entries during boot show no failures in regards to usb connectivity.
Charging works fine but no data connectivity via usb at all.
Anyone got any other ideas?

Hello world.
I had the same issue.
To solve the problem :
- unlock developer mode
- switch on debug usb
regards
J.

I had this problem too- did not have to enable USB debugging though, just enabling the developer options fixed it for me. Which is odd because I definitely had them enabled previously... I guess a recent update reset that and for some reason all the USB data options are tied to developer mode now.

I've got 790 (american, as i know). The same issue, no response from service, guarantee, doesn't help, pc shows it as unknown device. some other bugs, mobile data fails, no sim detected after a few seconds, violet camera with no focus, but nice when the distance ia ok, so matrix works ok, but no stabilisation.
Then, bad battery, it seems that the bank ia ok, but controller works bad. it charges enough time to think that the capacity is not degraded. I suppose that usb controller (pc connection and fsat discharging) are nearby problems.

None of the above posts worked for me on my N5x (8.1.0 March), but searched some more and found this to work for me:
https://productforums.google.com/forum/#!topic/phone-by-google/DfpqXN1UfWY

Hello everyone. I'm just resurrecting this old thread so I can provide the solutions I have found to this problem. It appears this symptom has multiple causes, and there are different solutions depending on the cause. I have seen this problem twice now on my Nexus 5x (stock, no custom ROM) and solved it both times.
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
2. SOLUTION #2 - ClockworldMod USB Driver was installed. Replace with Google driver
The second time I encountered this issue, the Solution #1 above did not work. Surprisingly, the adb devices command successfully detected the Nexus 5x. It's just that the phone wasn't showing up in the Windows 10 File Explorer interface.
The root cause of this problem was that I had installed the ClockWorldMod USB Driver because I was playing around with their Vysor App (on a different phone.)
BTW, I think the Vysor tool is really nifty for screen mirroring purposes!
To resolve the problem, I replaced the ClockWorldMod driver with the regular Google USB Driver.
(Sorry, XDA is not letting me post links because of my low post count. The link is:
h++ps://developer.android.com/studio/run/oem-usb.html )
The procedure is:
- Download the Google USB Driver from the link above and extract the ZIP.
- Enter the Windows Device manager
- Find 'Android ADB Composite Interface'
- Open the properties of 'Android ADB Composite Interface' and you will see it is from ClockWorldMod.
- Right click on this Interface and Select 'Update Driver'
- Click on 'Browse My Computer for Driver Software'
- Click on 'Let me pick from a list of available drivers on my computer'
- Click on 'Have Disk'
- Browse to the Google USB Driver you downloaded.
- Select that driver and load it on top of the ClockWorldMod driver. (Windows may claim that you've got the best driver already installed, but ignore that.)
After re-installing the Google driver, the Nexus 5x appeared immediately in the Windows 10 interface for file transfers.
Cheers, I hope this helps someone out!

I have the same problem with LineageOS 15.1, I am not sure since when, because I don't use USB that often, but I it must have been after the second update for 15.1. ADB and FASTBOOT don't work.
None of the suggested methods work. I am on Linux, but I also tested the USB driver solution on a windows PC.
The problem is, my phone does not trigger any response from the system I connect it to.
On Linux an lsusb/dmesg shows nothing, and on windows it doesn't make the classic "ding" when I connect something to the USB port.
It is like my phone isn't even there.
In the developer options under networking and USB, USB was set to charging only. I changed that to MTP, but it didn't help.
Now I can't change it back (not that I want to, but just saying). No matter what I press on this menu, it always stays on MTP.
I am here because of adb not connecting tho, MTP is not my concern anyways.
I am not sure what to do, format data, and wipe system etc. and go for a clean install? The problem is, when I boot into recovery, ADB and FASTBOOT don't work either, i.e. my computers don't see an USB connection. So will a wipe even help? I am scared I wipe my phone, and then I can't connect via ADB in TWRP.

Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?

tantalfr said:
Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?
Click to expand...
Click to collapse
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!

ufopaper said:
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!
Click to expand...
Click to collapse
Never underestimate the power of a toothbrush

Bamboo-Toolkit said:
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
Click to expand...
Click to collapse
Amazing, this solved my problem. Thanks!