Related
Im trying to root my kindle fire hd (version 7.4.8)
Every time i use Kindle Fire First Aide on the command prompt it says that i have a system path not specified error.
My laptop operating system is windows 8 ( I have not upgraded yet to latest version so I don't know if that's the problem)
Any Help would be appreciated
Steps I Used
1. Download KFFA
2. Opened KFFA using cmd
3. Used option 21 : Alternative root: newer devices
4. Says system path is not specified
5. It starts a daemon but thats all it does
P.S Im not sure but it also looks like i have a adb problem
I turned on the ADB with usb and used the adb drivers in KFFA but it never works
I'm having a similar problem.
I've had my kindle rooted for several months now, and I'm sure that I had turned auto updating off...however, this update (7.4.8) was forced on me a couple of weeks ago, and now I've lost the ability to usefully run Google Play (it keeps giving me a 'no connection' error). I also cannot update any programs that were obtained through google play.
A few things that I have noticed:
BusyBox Installer says that my Kindle is rooted, but cannot install BusyBox, or run any of the scripts.
KFFA cannot access my Kindle. I have tried several proceedures on the forums to rectify this problem, to no avail. I have tried with several cables including the original, and the cable that I previously successfully rooted my kindle with.
My kindle has started showing ads on the lock screen at times, which was something I disabled with KFFA when I first rooted my kindle.
I do have momentary adb access while booting, but it gets disconnected as soon as the lock screen appears and I cannot reconnect
same problem here, can't manage to root kindle with 7.4.8
RE:
Well then i guess it will only work if you brick your kindle to reboot over and over then root and use kffa to root it then unbrick it using it and i think it will work let me try
Successfully rooted Kindle Fire HD 7.4.8
Hi,
So this morning I reset to factory my KFHD 7.4.8. Clean start...
1/ install KFFirstAid from geekappz.blogspot.com/2013/02/root-kindle-fire-hd-and-2-with-windows.html
I did install the 64bit version on my windows 7.
2/ execute all installation steps of KFFA as explained in the link above until reaching C-1 root step 10 (do that step 10).
3/ connect your kindle to your computer via USB
4/ the runme.bat in KFFA depends on another system package called busybox. Great package but... you cannot install from amazon store on a fresh kindle, and the installation via the runme.bat does not work. I decided to do without busybox... So replace the original runme.bat in C:/KFFirstAid by the one attached. I edited the sections 18 and 21 (i "rem"ed some lines, and put the corrected code just below). I edited only these two options. (means do not ask about the others...)
(site did not upload the file, so here is a link to it... drive.google.com/file/d/0ByEA1ADGX9vNS2RKUEdKYnN6Uk0/edit?usp=sharing)
5/ launch "my" runme.bat.
6/ select option 21. This will root the kindle. Follow the instructions (including the full restore at the beginning). It will reboot quite a few times, just be patient... (very). Your kindle may seem up and running, but the adb communication may take a few more minutes to go through...
At the end, superuser.apk is installed, look for it in the command window log. When done, on your kindle, start supersu and let it update itself. Verify root access with root check basic.
7/ return to the main menu of runme.bat,
8/ select option 18. This will install google play. Follow the instructions, including the registration to google on the kindle, in the middle of the installation. During this registration i experienced a few "application stopped working", but it went through anyway... so do not panic...
Again, a lot of reboots...
That's all folks... (takes about two hours...)
Successfully Rooted KFHD 7.4.9
Still works for KFHD 7.4.9
Replaced some "mv" commands by "dd" commands to workaround a cross device link error, in the runme.bat file.
fabienwahl said:
Hi,
So this morning I reset to factory my KFHD 7.4.8. Clean start...
1/ install KFFirstAid from geekappz.blogspot.com/2013/02/root-kindle-fire-hd-and-2-with-windows.html
I did install the 64bit version on my windows 7.
2/ execute all installation steps of KFFA as explained in the link above until reaching C-1 root step 10 (do that step 10).
3/ connect your kindle to your computer via USB
4/ the runme.bat in KFFA depends on another system package called busybox. Great package but... you cannot install from amazon store on a fresh kindle, and the installation via the runme.bat does not work. I decided to do without busybox... So replace the original runme.bat in C:/KFFirstAid by the one attached. I edited the sections 18 and 21 (i "rem"ed some lines, and put the corrected code just below). I edited only these two options. (means do not ask about the others...)
(site did not upload the file, so here is a link to it... drive.google.com/file/d/0ByEA1ADGX9vNS2RKUEdKYnN6Uk0/edit?usp=sharing)
5/ launch "my" runme.bat.
6/ select option 21. This will root the kindle. Follow the instructions (including the full restore at the beginning). It will reboot quite a few times, just be patient... (very). Your kindle may seem up and running, but the adb communication may take a few more minutes to go through...
At the end, superuser.apk is installed, look for it in the command window log. When done, on your kindle, start supersu and let it update itself. Verify root access with root check basic.
7/ return to the main menu of runme.bat,
8/ select option 18. This will install google play. Follow the instructions, including the registration to google on the kindle, in the middle of the installation. During this registration i experienced a few "application stopped working", but it went through anyway... so do not panic...
Again, a lot of reboots...
That's all folks... (takes about two hours...)
Click to expand...
Click to collapse
Root Kindle Fire HD 7.5.1
Still works for KFHD 7.5.1
Option 18, to remove Amazon adds has been recoded in "my" runme.bat
Use also post below to remove an additional file (the kso file is now removed by the option 18 above)
http://forum.xda-developers.com/showpost.php?p=52046640&postcount=73
fabienwahl said:
Still works for KFHD 7.4.9
Replaced some "mv" commands by "dd" commands to workaround a cross device link error, in the runme.bat file.
Click to expand...
Click to collapse
[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 am completely confused, I have no os on the HDX but do have safestrapv4.1. I am trying to sideload a rom.zip to the HDX from my windows7 laptop, but after trying loads of command lines I'm still trying to understand I don't think I'm any closer. I have Android studio, minimal ADB and Fastboot installed.
My Laptop see's the HDX as 'unspecified' device, allows to eject but not open so I can copy a rom to the HDX. Recovery shows files but for the life of me I have no idea how I get a file from my desktop to the HDX.
edit:the thread title is more confusing than my objective. @unsoft brick this broken b1tch.
Hello,
I am new to the Kindle HDX platform. I read that FireOS 4.5.5.1 is still rootable with Kingroot, but here's my issue:
I just received a Kindle HDX which is not registered yet, and has 4.5.5.1 currently. But, if I understand it correctly, once I register the device via Amazon, it will get OTA immediately (Device Options says an update 4.5.5.2 is available) and ruin any chances to root the device. At the moment, its not connected to any Wifi, and I would like to ensure OTA does not get to my device.
So, how do I get around this? I can't sideload apps because it's still a stock device.
Thanks for any advice or any pointers to a step-wise procedure around this.
me4tux said:
Hello,
I am new to the Kindle HDX platform. I read that FireOS 4.5.5.1 is still rootable with Kingroot, but here's my issue:
I just received a Kindle HDX which is not registered yet, and has 4.5.5.1 currently. But, if I understand it correctly, once I register the device via Amazon, it will get OTA immediately (Device Options says an update 4.5.5.2 is available) and ruin any chances to root the device. At the moment, its not connected to any Wifi, and I would like to ensure OTA does not get to my device.
So, how do I get around this? I can't sideload apps because it's still a stock device.
Thanks for any advice or any pointers to a step-wise procedure around this.
Click to expand...
Click to collapse
First order of business is to verify if you have a 3rd or 4th gen HDX. All 7" models along with most older 8.9" models are 3rd gen. If purchased from Amazon the receipt should clearly indicate which gen.
Assuming 3rd gen you can try rooting with the desktop version of [url="https://kingroot.net/Ã?¢?Ã?Â]Kingroot[/url] which is done via USB tether. If successful you can then block OTA updates, enable WiFi and then proceed in the direction of your choosing. Those options can be laid out once you are rooted.
Downside to desktop app is the interface is in Chinese. Not hard to figure out but a bit discouraging for new comers.
If your device does update to 4.5.5.2 there is still a path to root. Cover that as needed.
Hi Davey126,
Thanks for your reply. To answer your questions:
1. My Kindle Fire HDX 7" is 3rd Gen.
2. I also found a youtube describing Kingroot desktop (maybe old version of Kingroot) but one of steps is selecting which Android OS. So, for FireOS 4.5.5.1, which Android OS should I select from Kingroot?
https://www.youtube.com/watch?v=D4CC5svnoW4
Lastly, somewhat unrelated, I also have a Kindle HDX 8.9 (4th Gen) with FireOS 4.5.4, can I use Kingroot Desktop and do the same to root it?
Cheers!
Davey126 said:
First order of business is to verify if you have a 3rd or 4th gen HDX. All 7" models along with most older 8.9" models are 3rd gen. If purchased from Amazon the receipt should clearly indicate which gen.
Assuming 3rd gen you can try rooting with the desktop version of [url="https://kingroot.net/Ã?¢?Ã?Â]Kingroot[/url] which is done via USB tether. If successful you can then block OTA updates, enable WiFi and then proceed in the direction of your choosing. Those options can be laid out once you are rooted.
Downside to desktop app is the interface is in Chinese. Not hard to figure out but a bit discouraging for new comers.
If your device does update to 4.5.5.2 there is still a path to root. Cover that as needed.
Click to expand...
Click to collapse
me4tux said:
Hi Davey126,
Thanks for your reply. To answer your questions:
1. My Kindle Fire HDX 7" is 3rd Gen.
2. I also found a youtube describing Kingroot desktop (maybe old version of Kingroot) but one of steps is selecting which Android OS. So, for FireOS 4.5.5.1, which Android OS should I select from Kingroot?
Lastly, somewhat unrelated, I also have a Kindle HDX 8.9 (4th Gen) with FireOS 4.5.4, can I use Kingroot Desktop and do the same to root it?
Cheers!
Click to expand...
Click to collapse
Q) which Android OS should I select from Kingroot?
A) FireOS v4 is based on KitKat 4.4; you will want to go with the option that corresponds most closely with that version
As for your 4th gen HDX you can root it as-is but you will not be able to install a custom ROM or Google Play Services/Store under FireOS v4. Best option is to manually update to FireOS v5.1.2, root and block OTA updates. From there you can install the Google Play Store which runs reasonably well under FireOS v5. Still no custom ROMs; you are stuck with FireOS on that pup.
Hi Davey126,
Unfortunately, it didn't work. Not sure what I did wrong.
Here's what I did:
Environment: Windows XP PC
1. I downloaded the ADB USB drivers for the Fire here: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing
2. Download and install Kingroot for Desktop: https://kingroot.net/
The current Desktop version is V2.2.2 and it auto-detected the HDX as Android 4.4.3
3. Clicked on Root and waited. Then, a red circle with a X showed up. I can only assume, the message says Root Failed.
Is there an older Kingroot Desktop I could use from xda? Or could it be, the USB driver which used?
Any help is appreciated.
Davey126 said:
Q) which Android OS should I select from Kingroot?
A) FireOS v4 is based on KitKat 4.4; you will want to go with the option that corresponds most closely with that version
As for your 4th gen HDX you can root it as-is but you will not be able to install a custom ROM or Google Play Services/Store under FireOS v4. Best option is to manually update to FireOS v5.1.2, root and block OTA updates. From there you can install the Google Play Store which runs reasonably well under FireOS v5. Still no custom ROMs; you are stuck with FireOS on that pup.
Click to expand...
Click to collapse
me4tux said:
Hi Davey126,
Unfortunately, it didn't work. Not sure what I did wrong.
Here's what I did:
Environment: Windows XP PC
1. I downloaded the ADB USB drivers for the Fire here: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing
2. Download and install Kingroot for Desktop: https://kingroot.net/
The current Desktop version is V2.2.2 and it auto-detected the HDX as Android 4.4.3
3. Clicked on Root and waited. Then, a red circle with a X showed up. I can only assume, the message says Root Failed.
Is there an older Kingroot Desktop I could use from xda? Or could it be, the USB driver which used?
Any help is appreciated.
Click to expand...
Click to collapse
You could probably fiddle with different KingRoot desktop builds but not sure it is worth the effort.
Suggested path forward (same process 4.5.2 users had to follow when 4.5.5.0 was out which was not rootable):
- tether device and look for a large file ending in '.bin' under "Internal Storage" (just the root folder; don't traverse any folder trees)
- if located it is likely the 4.5.5.2 update; simply change the extension to .bak for now
- perform a 'factory reset' either from the FireOS settings menu or stock recovery menu accessible via <power>+<vol-up> when fully powered down
>> WARNING: you will loose ALL personal apps and data. This step is optional but reduces the chance of receiving an unwanted OTA update
- when device reboots do NOT enable WiFi and do NOT register device with Amazon
- enable ADB/USB and sideload (unknown sources) options in FireOS settings menu (they will now be 'off' even if previously enabled)
- download latest Kingroot app to your desktop and install it to your device via 'adb install <apk>
>> (google or ask for additional detail if unfamiliar with adb commands) <<
- if your local ISP is relatively fast (download speed 10+ Mbps) identify a location that has a slower open Internet connection (eg: local coffee shop)
- with WiFi still off launch KingRoot; take a look around to become familiar with the UI features
- enable WiFi and connect to preferred (slow) AP just before hitting the 'root' button
- KingRoot will attempt to go about it's business; it's possible Amazon will attempt to download FireOS 4.5.5.2; a slow network connection will prolong the download
- device many reboot several times during rooting process; if 4.5.5.2 managed to full download it will install during the reboot (bummer)
- once root is obtained immediately disable WiFi
- retether device and repeat first two steps in above procedure; if a partial download is found delete (do not rename) the file
Keep WiFi off and post back when above is complete. Next step is to permanently block OTA updates which can only be done once rooted. If 4.5.5.2 does download/install there is a way to rollback and retry. As with all rollbacks there are significant risks involved so it's better to try the above method first.
Sorry for the long post with 8,000 steps ...
Hi Davey126,
It seems I have some very basic issues: Under Windows XP file explorer, I cannot see my HDX device internal storage.
The hardware device shown when I click on "Safely remove Hardware" lists my device as an "Android Composite ADB interface" icon.
So I wonder if I actually installed the correct USB driver for the HDX in the very place?
Davey126 said:
You could probably fiddle with different KingRoot desktop builds but not sure it is worth the effort.
Suggested path forward (same process 4.5.2 users had to follow when 4.5.5.0 was out which was not rootable):
- tether device and look for a large file ending in '.bin' under "Internal Storage" (just the root folder; don't traverse any folder trees)
- if located it is likely the 4.5.5.2 update; simply change the extension to .bak for now
< cut >
Click to expand...
Click to collapse
me4tux said:
Hi Davey126,
It seems I have some very basic issues: Under Windows XP file explorer, I cannot see my HDX device internal storage.
The hardware device shown when I click on "Safely remove Hardware" lists my device as an "Android Composite ADB interface" icon.
So I wonder if I actually installed the correct USB driver for the HDX in the very place?
Click to expand...
Click to collapse
Windows driver issues are a PiTA with this device. Probably the #1 USB connectivity issue.
Been awhile since I worked with XP. Take a look at the following articles from Amazon for general guidance:
https://www.amazon.com/gp/help/customer/display.html?nodeId=201735880
https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing
Be sure to connect and remove (uninstall) any existing drivers first. Reboot between attempts if problems persist.
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