Related
Please forgive me if I've missed a post somewhere, I've been searching for weeks for an answer to my problem and I still don't see one (similar cases, but either a-no answer or b-solution for another problem).
Computers:
A Windows 7 (32-bit) system and a Windows XP (32-bit) system.
Phone:
Samsung Vibrant SGH-T959
Firmware Version: 2.2
Baseband Version: T959UVJL5
Kernel Version: 2.6.32.9
Build Number: Nero.v3
Description of Problem:
When I plug my phone into either or my two computers the following occurs - My phone recognizes that it is plugged in and begins charging; my computers do nothing.
When I was on Android 2.1 I could plug my phone into either of my two systems and my PCs would respond appropriately (ie. show the drive letters and let me access the device once I mounted the device).
Since the very first Android 2.2 install my computers act like nothing is happening. ADB doesn't see my phone, Odin is silent, and Windows doesn't show any drive letters nor does it even show that I am plugging in a USB device.
I have tried to correct this by changing the USB settings on the phone (Kies, Media Player, Mass storage, Ask on connection) and even trying to connect while in debug mode. Sadly, I never made a nandroid backup to take me back to the Android 2.1 install (idiot me took the plunge before reading up on that section).
I don't understand what would cause my phone to be treated as if it wasn't there. I've tried different USB ports, different MicroUSB cables, and even uninstalling/reinstalling the various device drivers for the phone.
I can get into download mode just fine, but what's the point if Odin can't see the phone since Windows thinks that nothing is there? Before you ask, yes, I tried going into download mode before starting Odin as well as after starting Odin; debug mode on and debug mode off. I've been trying all the combinations.
If anybody has any information beyond what is in the stickies, I would greatly appreciate it!
Do you see "USB connected" in notification bar on the phone? You can also turn on USB debugging mode in USB settings. If you see "USB connect" in pull down notification bar..tap on that and it will mount on your computer.
I experienced similar problem with.axura tool...phone well charge but doesn't pop out the mount notification. I power off both my phone and computer and it work again. I'm sure this won't on your scenario but just wanna inform you that it's not all hopeless...good luck
Yes. I have seen the mount USB bar. Bad news: even after it says mounted, the PCs react as if nothing has happened.
Sent from my SGH-T959 using XDA App
First of all, read this forum (last post is mine) http://forum.xda-developers.com/showthread.php?t=925393 - make sure you have kies or kies mini installed so that you have the correct drivers on your computer for your vibrant.
secondly, team whiskey has developed a fix for the mount issue your experiencing: http://forum.xda-developers.com/showthread.php?t=846384&highlight=mount+fix
they also have the mount problem fixed in the later nero roms... should not be an issue. please let me know if this helps!
in_dmand said:
First of all, read this forum (last post is mine) http://forum.xda-developers.com/showthread.php?t=925393 - make sure you have kies or kies mini installed so that you have the correct drivers on your computer for your vibrant.
secondly, team whiskey has developed a fix for the mount issue your experiencing: http://forum.xda-developers.com/showthread.php?t=846384&highlight=mount+fix
they also have the mount problem fixed in the later nero roms... should not be an issue. please let me know if this helps!
Click to expand...
Click to collapse
Okay, so I've tried all of the above to no effect except for the latest Nero rom...
Looks like I'll be trying the latest Nero (thank goodness for Dropbox).
Nope. Updating to the latest Nero [v5] didn't work.
Anyone else?
Nvm... gl with fixing it.
All~G1 said:
Nvm... gl with fixing it.
Click to expand...
Click to collapse
I think I'm going to have to throw it under a bus...
This same thing happened to me and to fix this problem all I did was install the drivers I got online, PM me your email and ill send you the drivers
I am almost certain that it is drivers issue more than your phone or any rom. You need to completely uninstall current drivers..all traces of em, reboot and install drivers from samsung website or there are some here in vibrant section also. It happened to me couple of times where one set of drivers stopped working for no reason and i had to try couple of different ones.
I had the same problem. Phone would charge but not connect. I solved it by getting a new usb cable. I just use the bad one for charging now
Sent from my SGH-T959 using XDA App
This is a driver problem. Your computer does not have the phone drivers and is confused on what to make of your phone so it finally decides that it is a charging device more or less and will not mount it, EVEN if you select mount from your phone options.
Please look on this forum or ask the guy who posted before for the Samsung USB drivers. Install them on your computer and then mounting the phone from the notification bar will work.
Hope that helps and feel free to ask again if you are stuck on the process.
I thought it was a driver issue as well until last week.
My coworker has the same model phone and is currently running 2.2.
He has his laptop (Windows XP) setup to handle his phone.
When he plugs his equipment in, everything works. When he plugs my phone in, same old story...
Even when trying different MicroUSB cables.
This is why I'm considering loading up a different/modified kernel.
Sent from my SGH-T959 using XDA App
Please take the time to read this:I flashed and installed SkyRaider a couple days ago and I noticed when I connected to my PC that my PC started recognizing it as HTC Phone (or something of the like). This apparently really screwed up my drivers on my computer because I installed iKReaM and now I can't even get into disk drive mode...it doesn't ask what connection type I want anymore and my computer just says "USB Device Not Recognized". I tried uninstalling the HTC Driver Installer but that didn't do anything either. This is not good as I ran into the same problem when trying to root my friends Samsung Fascinate and never go the problem fixed. Anyways...my phone worked perfect before and SkyRaider evidently messed it up pretty good...to say I am pissed is an understatement. If you need any more info please let me know.
Please link me to the newest HTC Drivers as well, it would be much appreciated.
If no one can help I will have to do a clean install of windows 7, which is not an enjoyable experience
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Stratejaket said:
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Click to expand...
Click to collapse
I can't get into recovery anymore using usb mode, computer doesn't recognize the device so no way to use it...and I would use the Wifi app instead of using a usb cable? I see what you mean by easy but I don't wanna avoid the problem...I have a brand new $1600 Alienware so I would like to have it fixed lol...if need be I may just have to do a clean install
I know this isn't your actual problem but just for the record, AirDroid lets you control your phone and push files to it with a web browser and wifi for free.
(I tried linking it but I guess I haven't made enough posts to include links yet, easy to find by searching the Market tho)
You might check under Settings/ Connect to PC to make sure the Ask Me option is turned on.
Sent from my ADR6400L using Tapatalk
When you plug your phone into your computer does the phone start to charge?
If so restart the computer and plug the phone into a different usb port. Check device manager and see if you have it listed in your usb devices, or you have an ! over a usb. Most of the time this ends up being an issue with the computer it is being hooked to, not the phone. The computer isn't launching the driver correctly to show the phone that it is connected to a computer, and not just a wall outlet.
Even when I've had this issue, which is random I have still been able to use recovery usb to manage it. Make sure when your in recovery you mount the sdcard before enabling the usb.
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.
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
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