At first thanks for the programmer to contribute on THE HDX UTILITY ,I have a problem,after i running THE HDX UTILITY in Windows 7 64-bit,3 command line of Access denied with some file path code show up ,after the status bar reaches 100%,main menu is shown ,however code "error:device no found" is shown no matter which option i chose,except 5.Install HDX Adb Driver,and i have connected my HDX 8.9 to my computer,what have I done wrongly,please help
Oh Windows with your stupid drivers and topheavy system...
You need to remove your current drivers and install the HDX drivers from Amazon's website. I don't use Windows, so that's as far as I can help you.
Sent from my KFSOWI using Tapatalk
Mineturtle33 said:
Oh Windows with your stupid drivers and topheavy system...
You need to remove your current drivers and install the HDX drivers from Amazon's website. I don't use Windows, so that's as far as I can help you.
Sent from my KFSOWI using Tapatalk
Click to expand...
Click to collapse
Thanks let me have a try
Related
hi
i just began learning android. i tried to connect my kf hd to adb. i installed the jdk and eclipse. i also setup the sdk manager to install the kindle fire hd 7 and kindle fire USB driver. but i have two problems.
one is when i run my app, it always run in the android API 16 emulator even though i set the project property to KF hd 7.
the second thing is that when i connected my device to the usb port of my computer, and run the app from eclipse to debug, my device did not changed accordingly (to displays what is on eclipse. furthermore, when i clicked start->control panel->device manager i found the name of my device in it, but just "kindle" that all, not kindle fire. and i do not see "Android Composite ADB Interface". why is that? even though i installed and ran Kindle Fire ADB drivers.exe.
as i mentioned before, i am a complete noobs when it come to android and java.
thanks in advance.
Have you enabled usb debugging on the kindle?
Sent from my GT-N7000 using xda premium
from 3444:enabled usb debug
zacthespack said:
Have you enabled usb debugging on the kindle?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
thanks for the reply. i did. i even enabled the allow installation of app.
3444 said:
thanks for the reply. i did. i even enabled the allow installation of app.
Click to expand...
Click to collapse
Odd have you tried using adb via the sdk. Its likely a driver issue tbh
Sent from my GT-N7000 using xda premium
reply
3444 said:
thanks for the reply. i did. i even enabled the allow installation of app.
Click to expand...
Click to collapse
hi
i do not know what you meant "tried adb in sdk. i had not heard that before. can you elaborate?
one thing i should tell you is that when i go to the command line and execute "adb devices", the device list is two blank lines. that showed that it did not install the usb driver correctly, right?
I am trying to root a Kindle Fire HD 8.9" running version 7.4.6 using Qemu.
The Kindle is already recognized as an ADB device using the necessary drivers. The Issue occurs when I run Qemu.
Without admin privileges it starts the whole reboot cycle but does not have the necessary permissions and fails
With admin privileges it gives the error that "ADB is not a recognized internal, external command, executable program or batch file"
How can I get past this?
Thanks
Lboecken said:
I am trying to root a Kindle Fire HD 8.9" running version 7.4.6 using Qemu.
The Kindle is already recognized as an ADB device using the necessary drivers. The Issue occurs when I run Qemu.
Without admin privileges it starts the whole reboot cycle but does not have the necessary permissions and fails
With admin privileges it gives the error that "ADB is not a recognized internal, external command, executable program or batch file"
How can I get past this?
Thanks
Click to expand...
Click to collapse
You need to run Root by Restore first, I have never personally had to use Qemu, root by restore has worked for me everytime!
I think I've made a huge mistake.
I just wiped my device in TWRP because the last CM Nightly I installed was acting up.
I went into TWRP, wiped and factory reset. I then rebooted and went into TWRP again.
I wanted to install CM 9.1, which I copied onto my 64GB SanDisk Ultra, and I was thinking to just flash it from the external sd.
I read somewhere on xda that I needed to maybe use a smaller SD card and have the format in FAT32, which I did, but TWRP still does not recognize them.
I am currently stuck with TWRP v2.3.1.0, no way to flash a new rom from a blank internal memory or an external memory.
I tried updating SDK and the most updated drivers for the device through the Device Manager and use "adb push" or "adb sideload" but the device is not recognized.
Can someone give me some kind of suggestion to solve this situation.
I’d suggest using a linux install to do the adb stuff if you’re not doing so already, no need for crazy windows drivers to see a connected device.
Sent from my EPAD using xda app-developers app
squidlr said:
I’d suggest using a linux install to do the adb stuff if you’re not doing so already, no need for crazy windows drivers to see a connected device.
Sent from my EPAD using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
Can you elaborate a bit on what a linux install is? My PC has W8 on...
kgal said:
Thanks for the reply.
Can you elaborate a bit on what a linux install is? My PC has W8 on...
Click to expand...
Click to collapse
Windows 8 is a bugger to get drivers working properly.
Try and use a windows 7 machine or a friends laptop or try the following instructions.
Windows 8 Instructions
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Ubuntu is a linux based Operating System, and can be used to do most things Windows 8 does, sometimes worse, sometimes better. So in this case, it's less trouble to connect an android device to a linux OS such as Ubuntu, as it can recognize a telephone without having to install drivers.
If you want to give it a go, you can install Ubuntu alongside Windows 8.
http://www.makeuseof.com/tag/tired-of-windows-8-how-to-dual-boot-windows-ubuntu/
And then install Fastboot and ADB:
http://putokaz.wordpress.com/2012/08/29/install-adb-and-fastboot-android-tools-in-ubuntu-via-ppa/
But, I'd stick to Windows and follow the advice of Flumpster if you're not too confident installing a second operating system.
I can and have knowledge of installing another OS to run alongside Windows.
I use VirtualBox to run Mac OSX and Android. Can I run Linux on VirtualBox and do the process through that?
I am not quite sure what I should do after disabling Driver Signature Enforcement on Windows 8...
Yes, you can install Linux in a virtual machine - give it a try. If the device is still not recognized via OS running in the virtual machine, you can then always install to your hard disk and try that route.
The other option is to run Ubuntu as a live cd eg from the disk in memory (not install) and do it that way. I first unlocked and rooted my mobile this way. I can give more info on this if you like.
jamesthedisciple said:
The other option is to run Ubuntu as a live cd eg from the disk in memory (not install) and do it that way. I first unlocked and rooted my mobile this way. I can give more info on this if you like.
Click to expand...
Click to collapse
I think I'll give a multi-boot option a try. I've been wanting to install a different OS anyway since upgrading to Windows 8. Now I just have incentive.
kgal said:
I think I'll give a multi-boot option a try. I've been wanting to install a different OS anyway since upgrading to Windows 8. Now I just have incentive.
Click to expand...
Click to collapse
Just a quick thought after re-reading your first post, I'd try a smaller sd card (16 or 32GB). I have heard of the larger faster cards giving some people problems.
Solved!
After trying to install Linux using Ubuntu 13.04 and getting more errors (something with the UEFI vs Legacy Boot installation), I decided to retry and find the original Windows drivers for the TF201.
I found one through Softpedia, downloaded it, used the "Have Disk" option when installing the yielded "Transformer" device in the Device Manager and sideloading the new CM 10.1 Nightly onto it.
Works like a charm!
Thanks everyone for the support!
[FIXED]!
Hey guys, I am having some trouble working with ADB with my kindle fire HDX 7". I have dev options enabled and ADB Debugging. But when i connect my Kindle Fire HDX 7" it does no show the drive on my Mac but Android File Transfer reads it fine. So, thinking that it is fine I install ADB and Fastboot. But, anytime when I try to locate my device in ADB (adb devices) it doesn't show up. Thinking it might be a bug with my computer not showing it as a drive I try to use a command but it says: error: device not found. (Or something like that.) I hope someone could help me on why my device does not work with ADB. I am using Fire OS 4.5.2 (Un-Rooted.)
Make sure you have Amazon's drivers installed.
https://developer.amazon.com/post/T...p-the-ADB-driver-for-Kindle-Fire-Devices.html
Does this work for Mac? (I see the AVD thingy for Mac.)
Oh, nevermind I got it to work. Thanks alot for your help!
I have a rooted kindle and the past few days my Wi-Fi isn't working right. Some days it will switch right on and connect other says you switch it on and it does nothing and acts as if the wifi is still turned off. Please help. I did factory reset and it didn't help. I can post a video to YouTube to show you if you need.
Heatherb90 said:
I have a rooted kindle and the past few days my Wi-Fi isn't working right. Some days it will switch right on and connect other says you switch it on and it does nothing and acts as if the wifi is still turned off. Please help. I did factory reset and it didn't help. I can post a video to YouTube to show you if you need.
Click to expand...
Click to collapse
- known side effect of KingRoot
- toggling Airplane/Flight mode should work; give it a few seconds to connect
- consider a custom ROM if further relief is needed; Fire Nexus (KitKat based) works best if WiFi reliability/stability is a priority
worse issues lol
I tried that and now I have royally screwed it up lol. I was in the recovery menu which is team win recovery project v2.8.6.0 and I think it was the advanced wipe which I was thinking was basically a factory reset and it deleted the OS. I tried connecting it to my laptop and have been at it for over an hour and can't get it to connect to my windows 10 laptop. I installed the drivers from amazon. In device manager it shows as Android Phone > Google Nexus ADB Interface but I can't actually see it in my file manager area to try and put the stock kindle back on it. At my witts end and my daughter is so mad she cant use her tablet (she is 3 lol) any help is greatly appreciated.
heather90 said:
I tried that and now I have royally screwed it up lol. I was in the recovery menu which is team win recovery project v2.8.6.0 and I think it was the advanced wipe which I was thinking was basically a factory reset and it deleted the OS. I tried connecting it to my laptop and have been at it for over an hour and can't get it to connect to my windows 10 laptop. I installed the drivers from amazon. In device manager it shows as Android Phone > Google Nexus ADB Interface but I can't actually see it in my file manager area to try and put the stock kindle back on it. At my witts end and my daughter is so mad she cant use her tablet (she is 3 lol) any help is greatly appreciated.
Click to expand...
Click to collapse
I will respond to this in the next 24 hours - hang tight.
Thank you
I will keep checking for your response. I really appreciate your help.
heather90 said:
I tried that and now I have royally screwed it up lol. I was in the recovery menu which is team win recovery project v2.8.6.0 and I think it was the advanced wipe which I was thinking was basically a factory reset and it deleted the OS. I tried connecting it to my laptop and have been at it for over an hour and can't get it to connect to my windows 10 laptop. I installed the drivers from amazon. In device manager it shows as Android Phone > Google Nexus ADB Interface but I can't actually see it in my file manager area to try and put the stock kindle back on it. At my witts end and my daughter is so mad she cant use her tablet (she is 3 lol) any help is greatly appreciated.
Click to expand...
Click to collapse
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
LINK?
When I click the link to download package it shows up to a thread to download motorola package? Should I be downloading that? Thanks.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
Heatherb90 said:
When I click the link to download package it shows up to a thread to download motorola package? Should I be downloading that? Thanks.
Click to expand...
Click to collapse
Yes - Motorola drivers have proven to be highly compatible with HDX devices. The link will install some other stuff that is not needed but is otherwise benign (does not run in background, etc).
My other Kindle Tethers fine
I am not sure if this makes any difference but my other Kindle which is exactly the same except unrooted tethers just fine to my laptop. It immediately shows up in file manager as Fire when I plug in the cord.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
waiting
I am installing that motorola driver now. Seems it may take quite a while to install.
It didn't change anything. It still shows in device manager as Andriod Phone > Google Nexus ABD Interface and the only thing it does when I right click is open properties and in properties it has General, Drivers, Details, Events and under drivers my only option is Driver details and it also says Driver Provider: Clockwork Mod.
Heatherb90 said:
When I click the link to download package it shows up to a thread to download motorola package? Should I be downloading that? Thanks.
Click to expand...
Click to collapse
It didn't change anything when I got the motorola drivers. Still shows up in device manager are android phone and no options to uninstall anything.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
I got it to tether sucessfully. Now to try the next steps in recovering my kindle. Thanks so so so so much for your help. I had to go into TWRP menu and select mount usb storage.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
Got the computer to recognize my device but now I can't flash the kindle software. I tried just drag and dropping it into kindle and couldnt find it via twrp install so i found a thread about using adb commands and i get the issue that my device is unauthorized when i type ADB devices.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
Heatherb90 said:
Got the computer to recognize my device but now I can't flash the kindle software. I tried just drag and dropping it into kindle and couldnt find it via twrp install so i found a thread about using adb commands and i get the issue that my device is unauthorized when i type ADB devices.
Click to expand...
Click to collapse
Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there.
On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download".
Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats.
If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions.
When opening the kindle with file explorer I see internal devices then twrp and in that folder is a single file called twrp. I
I am going to try just dropping it in the twrp folder since that is the only folder I have and if that does not work I am not sure what to do. Could I possible create the Download folder within the internal storage folder?
Davey126 said:
Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there.
On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download".
Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats.
If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions.
Click to expand...
Click to collapse
OK so I got the file onto the kindle and when i try to flash the rom I get the error E: Error execturing updater binary in zip '/sdcard/downloads/kk-fire-nexus-rom-apollo-20161017.zip'
Davey126 said:
Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there.
On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download".
Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats.
If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions.
Click to expand...
Click to collapse
Finally got it thank god. The only rom that would work was Thor. The Apollo one would not work and kicked out that error but first try Thor went right on. Thank you so much for all your help and listening to my annoying posts lol.
Davey126 said:
Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there.
On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download".
Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats.
If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions.
Click to expand...
Click to collapse
Heatherb90 said:
Finally got it thank god. The only rom that would work was Thor. The Apollo one would not work and kicked out that error but first try Thor went right on. Thank you so much for all your help and listening to my annoying posts lol.
Click to expand...
Click to collapse
Glad you got it sorted. FWIW:
- Thor = 7" 3rd gen HDX (your device)
- Apollo = 8.9” 3rd gen HDX