Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
First verify drivers are working. For whatever reason legacy composite drivers from Motorola seem to work best with this device regardless of platform or host OS. Install the Motorola Device Manager from this page and then switch drivers. No need to launch the utility.
TWRP must be at v2.7 or above for ADB support. If below 2.8.6.0 you should consider updating via fastboot assuming bootloader has been unlocked. See: https://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547
If still no joy you will have to erase/replace aboot and rebuild the device from scratch. Data loss is likely.
hmm yeah, the main problem seems to be the tablet never shows up in device manager as any device... thanks for the hints though, will try the motorola device manager drivers...
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
fufu508 said:
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
Click to expand...
Click to collapse
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
fufu508 said:
In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled?
Click to expand...
Click to collapse
Oh snap, this is a good idea - will try when I get home.
TWRP 3.1.1-1, Win 10 64bit - yeah tested several usb ports on my computer - I originally rooted the HDX with this computer and windows 10 install about 2 years ago [side note do you guys remember reformatting every 6 months because windows was such a pos, I'm really glad those days are long gone!]
LOL yep Windows 10 nowadays does seem a lot more stable than the earlier stuff.
---------- Post added at 06:14 PM ---------- Previous post was at 05:50 PM ----------
Davey126 said:
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
Click to expand...
Click to collapse
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
fufu508 said:
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
Click to expand...
Click to collapse
Fair enough; I may have been a bit harsh in my response. I now see the passing reference to an Apple rig and appreciate the unfiltered perspective often obtained via Linux. That said, there is new info on the table that suggests the OP has access to a Win10x64 box which should connect effortlessly/reliably with Moto drivers and a quality USB cable. Mucking with drivers can be a PiTA on Windows; the Moto variants remove much of the pain - although you still have to select the proper driver after tethering in the target mode (adb or fastboot) as Windows will typically default to Microsoft/stock variants which rarely work with HDX devices.
Related
First, let me say that I've searched and searched and looked for all the info I can find about people having similar problems. I've yet to find anything that works for me, and I'm at my wit's end on this...
A few days ago I tried [unsuccessfully] to update CWM on a GTab. I can't get into recovery at all now (it just hangs), but this problem predates that.
The problem I have is that I cannot get any PC to recognize the GTab - in any mode - and I've tried 4 computers with various operating systems. I've tried Fedora, Ubuntu, Windows XP and Windows 7 and none of them will see the GTab at all. They won't see it with debugging on, with it off, in APX mode or anything.
I have gone through half a dozen cables and tried every USB port I've got. It just simply will not recognize the tablet in any way.
I'm toying with the possibility that the port might be damaged, but I can't think of a good reason why that would be the case. The tablet has been well taken care of, and all the other ports work just fine (audio, USB storage, SD).
So, has anybody else run into this issue and found a fix for it?
N0ctrnl said:
I'm toying with the possibility that the port might be damaged, but I can't think of a good reason why that would be the case. The tablet has been well taken care of, and all the other ports work just fine (audio, USB storage, SD).
So, has anybody else run into this issue and found a fix for it?
Click to expand...
Click to collapse
Read: Only ClockWork recovery on boot
Check dmesg to see if tablet is detected: A self inflicted wound
Also: [Q] (really) bricked g-tab.
If you can't boot the tablet at all--into either ROM or recovery--, then there's nothing you can do if your USB isn't working. If you can boot into one of them, then there's hope.
I managed to get CWM installed (was my bad on trying to flash the wrong one to upgrade it anyway). It's always booted just fine into the ROM, and everything works but the USB connection to PC.
I am actually a Linux admin by trade, so I kept an eye on all pertinent system logs and outputs when I tried it on the Linux box. No dice.
N0ctrnl said:
I am actually a Linux admin by trade, so I kept an eye on all pertinent system logs and outputs when I tried it on the Linux box. No dice.
Click to expand...
Click to collapse
Well, you have to be careful about these things. APX mode, for instance, only "connects" to the host PC once, so if you unplug and replug hoping to see USB device recognition messages from the Linux kernel, then you will be disappointed.
What about on the gTablet? Does the kernel print anything pertinent when the cable is connected to the host PC (enable USB debugging first)? Are there any other error messages or diagnostics?
That's the troubling part. I'm finding absolutely nothing. Nothing at all to indicate there's any kind of issue. My guess at this point is that the USB port must be physically broken. I can't see any other way to make sense of it.
Here's one final suggestion: Open the gtab up and disconnect the battery. Wait 1 minute then reconnect the cable.
See if it helps. (It's for people who can't even boot the tablet into APX mode, but, try it before concluding that it is a HW problem).
I just got a new laptop with Windows 8.1 64 bit. When I plug in my Evo LTE, nothing happens. It does not show up as new hardware and there is no trace of it in the device manager. The charge light is on, but that's it.
I've tried installing HTC sync & drivers only but I get the same results. I've dug around on this site and on the web for a couple of days before starting this thread just in case I could find something. No luck.
My phone:
Evo LTE S-Off
CM 10.2
My laptop:
Acer V5 122P
1 USB 3.0, 1 USB 2.0
I've tried plugging it into both ports with the same above results. I'm stuck.
Seems to be a common issue with 8.1. The consensus seems to be either downgrade to 8 or find a Windows 7 machine to use.
Nice avatar
Sent from my HTC EVO 4G LTE
oops. Double post.
Thanks. She's my baby.
I was afraid of that.. My Windows 7 machine has been retired. I've been reading about downgrading to 8.0 and it looks like it's a PITA as far as having to completely reset the machine.
So far everything but my phone works through the USB ports. I guess I'll just have to wait for a fix.
I spent countless hours trying to get ADB/Fastboot drivers to work on 8.1 and there was no fix.
I was able to find a fix for it!
Using a Live CD of Ubuntu and boot that. ADB/Fastboot work from there.
If you need help with that, I can guide you
Try a different USB cable - some will do charge only, others will give full access to communicate with phone.
If using an Intel chipset, go to Intel's webpage and download their USB 3.0 drivers and use those instead of Microsoft's - these are a must if trying to flash/root phone when using windows 8/USB3 drivers.
CapedCrusader said:
I spent countless hours trying to get ADB/Fastboot drivers to work on 8.1 and there was no fix.
I was able to find a fix for it!
Using a Live CD of Ubuntu and boot that. ADB/Fastboot work from there.
If you need help with that, I can guide you
Click to expand...
Click to collapse
This is my favorite solution. Ubuntu (Linux) is the bets when handling Android. Sometimes, ADB on Windows tends not to recognize devices that are booted into recovery, for example. Never a problem with Ubuntu.
I have a 32gb flash drive which I installed the complete Ubuntu package onto. So I simply boot from my USB whenever I want to use it. And this method is better than a Live CD because all of my files/settings are saved. Live CDs require setting up ADB and fastboot each time, to my knowledge. If I'm wrong, please inform me.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
aarsyl said:
This is my favorite solution. Ubuntu (Linux) is the bets when handling Android. Sometimes, ADB on Windows tends not to recognize devices that are booted into recovery, for example. Never a problem with Ubuntu.
I have a 32gb flash drive which I installed the complete Ubuntu package onto. So I simply boot from my USB whenever I want to use it. And this method is better than a Live CD because all of my files/settings are saved. Live CDs require setting up ADB and fastboot each time, to my knowledge. If I'm wrong, please inform me.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
Click to expand...
Click to collapse
How did you do this? I can't use 8.1 with fastboot. Would love to use one of my old thumb drives and try.
Download Ubuntu here:
http://www.ubuntu.com/download/desktop
Download the Live USB creator here (instructions included):
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
Some might find my method to be a bit cumbersome, but it got the job done. I experienced a lot of problems trying to dual-boot Windows 7 & Ubuntu, so I used 2 flash drives. I used the 2gb drive as the Live USB install, rebooted using my new Ubuntu Live USB, then I installed Ubuntu onto my 32gb drive. In Windows, you might be able to run the installer, and install Ubuntu to the flash drive that way, but for some reason that I don't know, it would force me to try or install Ubuntu as my only option.
I will continue to edit this post as I find more tips, and clearer instructions.
If your win8 system only has USB 3.0 ports, try installing the intel usb3.0 drivers instead of the Microsoft ones. This is what I did to get around adb and htc sync connection issues - I have no problem connecting my win8.1 system w/intel usb3.0 drivers to communicate and flash rom's to my evo since I made the switch over. do a search and you will find all the information about intel vs. Microsoft usb drivers on this and other sites.
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
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