Trying to unroot kindle, ADB not working - 7" Kindle Fire HD Q&A, Help & Troubleshooting

I bought a rooted kindle off of craigslist knowing it was rooted with what the guy called "CM10" I bought it thinking unrooting it would be easy; boy was I wrong.
I tried a guide that I can apparently not link to since I'm new, but
It worked up till the point of typing 'adb shell', where I got the error message "device not found".
I have the developer options on and USB debugging enabled on the kindle fire, but ADB will not work. I've tried putting
HTML:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_6860
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&MI_01
in my android_winusb.inf file, and I've also tried install the kindle fire hd USB drivers, but NOTHING works. It just says the device cannot be found. I'm about to just toss the $120 POS out the window.
What else is there to even do? I just want it to be on its stock software. I dont want it to be rooted

invadermoose said:
I bought a rooted kindle off of craigslist knowing it was rooted with what the guy called "CM10" I bought it thinking unrooting it would be easy; boy was I wrong.
I tried a guide that I can apparently not link to since I'm new, but
It worked up till the point of typing 'adb shell', where I got the error message "device not found".
I have the developer options on and USB debugging enabled on the kindle fire, but ADB will not work. I've tried putting
HTML:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_6860
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&MI_01
in my android_winusb.inf file, and I've also tried install the kindle fire hd USB drivers, but NOTHING works. It just says the device cannot be found. I'm about to just toss the $120 POS out the window.
What else is there to even do? I just want it to be on its stock software. I dont want it to be rooted
Click to expand...
Click to collapse
Using the device, go to the Amazon Kindle Fire software update page and download the software update for your particular device. Make absolutely certain that you have the right one or it will brick your device. If you aren't sure, check your device in settings under "About Tablet" for the version number and post it here for help. The original Kindle Fire and Kindle Fire 2 are identical in every way except for the software so don't jump the gun and just assume you have the right one without checking.
Once you have the right software update on your device, use the file manager that comes with the device to locate the software update you downloaded, most likely located in the Download folder of the sdcard, and change the file extension from ".bin" to ".zip". (This step is very important)
Reboot the device and repeatedly press the power button during startup to access custom recovery.
In the custom recovery, locate the "Wipe" option and perform a "Factory Reset" (This step is also very important). It probably wouldn't hurt to wipe System as well, but be sure you DO NOT wipe external storage or sdcard.
With the necessary wipes having been done, go back to the main menu, and select "Install".
Use the panes on the right and left to navigate to and select the software update.
Make sure you have selected the correct file then swipe to install.
Reboot and enjoy your 100% stock, unrooted Kindle Fire.

This worked magnificently!! THANK YOU SO MUCH
soupmagnet said:
Using the device, go to the Amazon Kindle Fire software update page and download the software update for your particular device. Make absolutely certain that you have the right one or it will brick your device. If you aren't sure, check your device in settings under "About Tablet" for the version number and post it here for help. The original Kindle Fire and Kindle Fire 2 are identical in every way except for the software so don't jump the gun and just assume you have the right one without checking.
Once you have the right software update on your device, use the file manager that comes with the device to locate the software update you downloaded, most likely located in the Download folder of the sdcard, and change the file extension from ".bin" to ".zip". (This step is very important)
Reboot the device and repeatedly press the power button during startup to access custom recovery.
In the custom recovery, locate the "Wipe" option and perform a "Factory Reset" (This step is also very important). It probably wouldn't hurt to wipe System as well, but be sure you DO NOT wipe external storage or sdcard.
With the necessary wipes having been done, go back to the main menu, and select "Install".
Use the panes on the right and left to navigate to and select the software update.
Make sure you have selected the correct file then swipe to install.
Reboot and enjoy your 100% stock, unrooted Kindle Fire.
Click to expand...
Click to collapse

Related

[Q] Help ADB & rooting KF HD: no device in ADB

Hello everyone. I am new to this site as well as rooting devices, so I apologize in advance for my newness.
I have a Kindle Fire HD
I'm trying to root it, mostly to add the google play store to it.
I've been following this http://forum.xda-developers.com/showthread.php?t=1893838
and have everything downloaded.
As far as ADB; I have it enabled on the kindle; it shows up under device manager as Android ADB Interface, but when I use the cmd “adb devices”, nothing shows up.
I have the google driver installed, I've added 0x1949 to the adb_usb.ini and added
“;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01”
to the proper spaces in the android_winusb as suggested in other threads... no luck.
I've spent the better part of my day trying to figure this out, browsing the forum and google; but now I'm just frustrated and have decided to give up and ask for help.
MrsDoom said:
Hello everyone. I am new to this site as well as rooting devices, so I apologize in advance for my newness.
I have a Kindle Fire HD
I'm trying to root it, mostly to add the google play store to it.
I've been following this http://forum.xda-developers.com/showthread.php?t=1893838
and have everything downloaded.
As far as ADB; I have it enabled on the kindle; it shows up under device manager as Android ADB Interface, but when I use the cmd “adb devices”, nothing shows up.
I have the google driver installed, I've added 0x1949 to the adb_usb.ini and added
“;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01”
to the proper spaces in the android_winusb as suggested in other threads... no luck.
I've spent the better part of my day trying to figure this out, browsing the forum and google; but now I'm just frustrated and have decided to give up and ask for help.
Click to expand...
Click to collapse
Hi, I have been having the exact same issue and like you have resorted to coming on here, been doing everything you have and still can't get anywhere, when I delete the drivers and then point it to the location of the edited driver file with
“;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01”
added it doesn't even find the driver. seems it can't use this android_winusb.inf file
solution in my case
MrsDoom said:
Hello everyone. I am new to this site as well as rooting devices, so I apologize in advance for my newness.
I have a Kindle Fire HD
I'm trying to root it, mostly to add the google play store to it.
I've been following this http://forum.xda-developers.com/showthread.php?t=1893838
and have everything downloaded.
As far as ADB; I have it enabled on the kindle; it shows up under device manager as Android ADB Interface, but when I use the cmd “adb devices”, nothing shows up.
I have the google driver installed, I've added 0x1949 to the adb_usb.ini and added
“;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01”
to the proper spaces in the android_winusb as suggested in other threads... no luck.
I've spent the better part of my day trying to figure this out, browsing the forum and google; but now I'm just frustrated and have decided to give up and ask for help.
Click to expand...
Click to collapse
Try to uninstall it and plug your device, or uninstall it and reinstall it, i plugged my device after uninstalling and it worked because it started to install, that is in my case
Sent From My Rooted Kindle Fire HD
---------- Post added at 10:43 AM ---------- Previous post was at 10:37 AM ----------
Try to update it too, i had a old adb, so i uninstalled, conected my device and waited that draivers installed, then i updated them. Old drivers are a problem too
persano said:
Try to uninstall it and plug your device, or uninstall it and reinstall it, i plugged my device after uninstalling and it worked because it started to install, that is in my case
Sent From My Rooted Kindle Fire HD
---------- Post added at 10:43 AM ---------- Previous post was at 10:37 AM ----------
Try to update it too, i had a old adb, so i uninstalled, conected my device and waited that draivers installed, then i updated them. Old drivers are a problem too
Click to expand...
Click to collapse
I uninstalled and set it up again. Made sure I updated the drivers and still nothing. It shows in the device manager but still nothing coming up in the cmd prompt when I do "adb devices".
ADB Server
slugger09 said:
Hi, I have been having the exact same issue and like you have resorted to coming on here, been doing everything you have and still can't get anywhere, when I delete the drivers and then point it to the location of the edited driver file with
“;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01”
added it doesn't even find the driver. seems it can't use this android_winusb.inf file
Click to expand...
Click to collapse
I have seen this a lot over the last 3 weeks, so far every case has been solved by updating the ADB Server. Are you trying to Root the device or are you looking to do software development on the Kindle? If Rooting is all you are looking for, I have put together a small tutorial with updated ADB daemons.
http://forum.xda-developers.com/showthread.php?t=2045999&page=5
prokennexusa said:
I have seen this a lot over the last 3 weeks, so far every case has been solved by updating the ADB Server. Are you trying to Root the device or are you looking to do software development on the Kindle? If Rooting is all you are looking for, I have put together a small tutorial with updated ADB daemons.
http://forum.xda-developers.com/showthread.php?t=2045999&page=5
Click to expand...
Click to collapse
How do you update the ADB Server? I tried entering 'android update adb' into cmd but it comes up as 'android is not a recognizable command'.
I haven't used cmd much since I was a kid so I could be entering it entirely wrong.
ADB Server
MrsDoom said:
How do you update the ADB Server? I tried entering 'android update adb' into cmd but it comes up as 'android is not a recognizable command'.
I haven't used cmd much since I was a kid so I could be entering it entirely wrong.
Click to expand...
Click to collapse
When the utilities to Root the Kindle were developed, most of them used old adb daemons (Let's face it, anything that is more than 4 weeks old is 'outdated'). Since most of us are using the adb daemon to Root the Kindle, I decided to focus on just that: Rooting the Kindle. If you are going to do Software Development around the Kindle than installing the Android SDK will be invaluable and necessary. Your error is usually the cause of a missing or erroneous PATH statement. Adding the correct PATH statement can cause QEMU and Root many Android to fail when each program calls to it's own embedded adb daemon.
Updating the adb daemon and API's are fairly easy, go to your favorite Android SDK vendor and download the needed updates and then replace the files. I use http://developer.android.com/sdk/index.html
Rooting the Kindle should take you 10 minutes. Getting every aspect of the Android SDK to function can take 2 - 3 hours depending on your environment, software packages (like Eclipse IDE) to be used with the SDK, etc
I have the same problem. I followed amazon's instruction in setting up the development environment, and it worked after. "adb devices" command now recognize my fire HD.
https://developer.amazon.com/sdk/fire/setup.html
1) Download Kindle Fire ADB drivers from here, after that install it on your PC.
2) Activate ADB on your kindle, from notification area choose more > security and then turn on ADB.
3) Since this root tutorial utilizing ADB, you are advised to install Android SDK on your computer.
4) After that you have to connect your Kindle with ADB using USB cable, go to “platform-tools” folder on Android SDK installation, press and hold Shift key and then right-click and choose “Open command window here”.
5) To check whether the connection between the device and adb is correct, run the following command:
adb devices
6) In case the command shows nothing, you can try to run this command:
android update adb
adb kill-server
adb start-server
adb devices
prokennexusa said:
1) Download Kindle Fire ADB drivers from (link), after that install it on your PC.
2) Activate ADB on your kindle, from notification area choose more > security and then turn on ADB.
3) Since this root tutorial utilizing ADB, you are advised to install Android SDK on your computer.
4) After that you have to connect your Kindle with ADB using USB cable, go to “platform-tools” folder on Android SDK installation, press and hold Shift key and then right-click and choose “Open command window here”.
5) To check whether the connection between the device and adb is correct, run the following command:
adb devices
6) In case the command shows nothing, you can try to run this command:
android update adb
adb kill-server
adb start-server
adb devices
Click to expand...
Click to collapse
I tried replacing the files with the sdk adb files, no luck. I think I'm going to just retry again tomorrow as it's getting late. I've got the day off tomorrow so I'm thinking of starting from scratch using your directions. There has to be something I'm doing wrong. Thank you for your help, I'll update tomorrow after I've tried again. Is there anything I should know about completely starting over, other than uninstall SDK, delete drivers, reset kindle?
Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
MrsDoom said:
I tried replacing the files with the sdk adb files, no luck. I think I'm going to just retry again tomorrow as it's getting late. I've got the day off tomorrow so I'm thinking of starting from scratch using your directions. There has to be something I'm doing wrong. Thank you for your help, I'll update tomorrow after I've tried again. Is there anything I should know about completely starting over, other than uninstall SDK, delete drivers, reset kindle?
Click to expand...
Click to collapse
1) Uninstall SDK
2) Remove any ADB Drivers installed
3) Reset the Kindle to Factory Default
The problem "Device not Found" is usually driver related or ADB Security issue. On the Kindle 7" HD go to Security - Enable ADB. Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/show....php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", you may download this package here: Kindle_Fire_HD_ADB_Drivers then install the ADB driver package. Reboot the PC and then reboot the Kindle.
If you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Download Root MANY ANDROID! to your desktop. Extract to your desktop.
Download Qemu automated root to your desktop. Extract to your desktop.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the batch files RunMe.bat and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Root Step 1: Run RunMe.bat from Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Choose option 1 Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it will react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run RootQemu.bat from Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Follow the instructions Step-by-Step allowing Windows to re-detect the Kindle between reboots (about 2 minutes). The first two 'steps' are just dialog boxes, just press Enter, Enter. Following the instructions, complete all steps to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Using the Amazon App Market, search for "Root Explorer", it should be free. Download and install Root Explorer, once done open Root Explorer and "Allow" Root to initialize.
Also, I have organized a few Google Apps & Services then zipped them into a folder you may download here: Google Apps. I have used all these Apps on my Kindle 7" HD successfully.
Extract google_apps to the folder named "Download" on the Kindle drive in My Computer.
Play Step 1 Open Root Explorer, navigate to /system/app/ Mount RW (Press upper RH box that says Mount RW). Now move GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk from /sdcard/download to /system/app. Using Root explorer app on the Kindle (be sure it has Superuser Permissions). Change permissions on all 3 packages to Owner: Read-Write, Group: Read and Others: Read. Install both GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk
Play Step 2 Reboot the Kindle
Play Step 3 Move Vending.apk from /sdcard/download to /system/app.
Play Step 4 Using Root explorer app on the Kindle (be sure it has Superuser Permissions) modify the Vending.apk permissions to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Install the Gplay3.8.17.apk in /sdcard/download to upgrade the the android market to the current Google Play market.
Play Step 8 Install final Google Apps as needed. There is no need to move any of the apps to /system/app, just perform a normal apk install by using Root Explorer to install these apps.
I have also attached copies of the above noted files to this thread.
If you would like to disable the Amazon OTA Updates, delete or move /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle. You will not loose any functionality by moving this file.
Finally, to eliminate Amazon from intercepting any Market requests, thus allowing Google Play to be the default Market move /system/app/MarketIntentProxy.apk to /sdcard/download - Reboot the Kindle
Enjoy.
Follow Up
MrsDoom,
How is the progress going on the Kindle? If you follow the steps closely, you should have success. If you are still having trouble PM me.

My KFHD 7'' status bar disappeared!

Hello guys!
I just came on this awesome forum and I would like to stay active here
So, I got my Kindle Fire HD 7'' recently and yesterday I tried to root it but I failed ( some problems that said : Permission denied ) and I left it there. Today, I turned it on and the status bar and the sidebar with home etc has been disappeared. I tried a lot of things , but with no success. I have installed file manager but I can't find something that could be useful to restore my Kindle. I just want to get on the menu "Device" and press the button that format in factory settings my Kindle. Can someon help me, please?
If you're using gmail, turn off notifications. They interfere.
Sent from my DROID BIONIC using Tapatalk 2
No, I haven't any Google app. Can, someway, restore to the factory settings? I have installed,as I said, an file explorer.
Guys! Need some help here! Just tell me how to restore my Kindle is the basic settings ( factory )!
eliac7 said:
Guys! Need some help here! Just tell me how to restore my Kindle is the basic settings ( factory )!
Click to expand...
Click to collapse
Do you have a fastboot cable? Do you have root?
Sent From My Rooted Kindle HD 7"
No, I don't have a fastboot cable. What is that?
And no , I don't have root.
eliac7 said:
No, I don't have a fastboot cable. What is that?
And no , I don't have root.
Click to expand...
Click to collapse
Ok i would suggest buying a fastboot cable (factory cable) you can find one on amazon for like 3$ but first lets see if we can get that thing rooted maybe it will bring it back to where you need it. Follow these directions exactly and should get it rooted.
First things first lets get your sdk and drivers setup correctly.
1. Download the sdk package from here http://developer.android.com/sdk/index.html#download
2. Open the file you downloaded and take the sdk folder and the sdk manager file and copy it to you hard drive. C:/sdk** C Being the hard drive letter. Sdk being a new folder you created. Put files in sdk folder
3. Now you need to open up sdk manager and go to tools menu and select manager addon sites. Now select user defined sites tab and select new and enter this site. http://kindle-sdk.s3.amazonaws.com/addon.xml and click ok.
4. You need to click the following boxes to install the packages you need. TOOLS, ANDROID 4.0.3 (api 15), and EXTRAS. Then click install packages to install them.
5. Now you need to install JDK from here http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
6. Now you need to install your basic java from here http://www.java.com/en/download/index.jsp
7. Now you need to install kindle fire hd adb drivers from here http://forum.xda-developers.com/showthread.php?t=1890413
8. Now shut down your kindle and connect your kindle to your pc and let it boot all the way and unlock the lock screen.
9. Now you need to run this tool https://dl.dropbox.com/u/54456659/Root_with_Restore_by_Bin4ry_v18.5.1.zip
And select option 1 and on your kindle when the screen pops up asking to restore go ahead and tap on restore.
10. When your kindle restarts the lock screen should turn black and look funny ( if this does not happen then run the tool again untill it does) Now unlock the lock screen.
11. Now you need to run this tool https://dl.dropbox.com/u/54456659/Qmenu-v2.5.zip and select option 1
When it says press enter to proceed make sure you wait till it fully boots and you unlock the lock screen before continuing to next step. Once all steps are completed you should have root.
Open superuser to activate it and enjoy.
Sent From My Rooted Kindle HD 7"
Hinzman420 said:
Ok i would suggest buying a fastboot cable (factory cable) you can find one on amazon for like 3$ but first lets see if we can get that thing rooted maybe it will bring it back to where you need it. Follow these directions exactly and should get it rooted.
First things first lets get your sdk and drivers setup correctly.
1. Download the sdk package from here http://developer.android.com/sdk/index.html#download
2. Open the file you downloaded and take the sdk folder and the sdk manager file and copy it to you hard drive. C:/sdk** C Being the hard drive letter. Sdk being a new folder you created. Put files in sdk folder
3. Now you need to open up sdk manager and go to tools menu and select manager addon sites. Now select user defined sites tab and select new and enter this site. http://kindle-sdk.s3.amazonaws.com/addon.xml and click ok.
4. You need to click the following boxes to install the packages you need. TOOLS, ANDROID 4.0.3 (api 15), and EXTRAS. Then click install packages to install them.
5. Now you need to install JDK from here http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
6. Now you need to install your basic java from here http://www.java.com/en/download/index.jsp
7. Now you need to install kindle fire hd adb drivers from here http://forum.xda-developers.com/showthread.php?t=1890413
8. Now shut down your kindle and connect your kindle to your pc and let it boot all the way and unlock the lock screen.
9. Now you need to run this tool https://dl.dropbox.com/u/54456659/Root_with_Restore_by_Bin4ry_v18.5.1.zip
And select option 1 and on your kindle when the screen pops up asking to restore go ahead and tap on restore.
10. When your kindle restarts the lock screen should turn black and look funny ( if this does not happen then run the tool again untill it does) Now unlock the lock screen.
11. Now you need to run this tool https://dl.dropbox.com/u/54456659/Qmenu-v2.5.zip and select option 1
When it says press enter to proceed make sure you wait till it fully boots and you unlock the lock screen before continuing to next step. Once all steps are completed you should have root.
Open superuser to activate it and enjoy.
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
Thank you very much for the instructions. I will try and I will let you know.
Can you link with me a cable from Ebay?
eliac7 said:
Thank you very much for the instructions. I will try and I will let you know.
Can you link with me a cable from Ebay?
Click to expand...
Click to collapse
Just let me know even if you just get root and dont get the nav bar we still have some options.
Sent From My Rooted Kindle HD 7"
Hinzman420 said:
Just let me know even if you just get root and dont get the nav bar we still have some options.
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
So, okay, I installed all the things and I am going on the step to open the RunMe.bat and then I choose the option 1. Then, it scans to get my Kindle, but can't find it. Now, the thing is that I can't know if the Kindle has opened the ADB as I can't go in the Sytem etc.
I attached a picture of my Kindle ( to understand which things have been disappeared )
eliac7 said:
I attached a picture of my Kindle ( to understand which things have been disappeared )
Click to expand...
Click to collapse
Ok my next question is have you called amazon? They have an excellent return policy. Just tell them this happened after their update and play stupid about root or anything of that sort and you should have a brand new one in a few days. Or your gonna have to get a fastboot cable.
Sent From My Rooted Kindle HD 7"
Hinzman420 said:
Ok my next question is have you called amazon? They have an excellent return policy. Just tell them this happened after their update and play stupid about root or anything of that sort and you should have a brand new one in a few days. Or your gonna have to get a fastboot cable.
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
Can you help me with restoring my Kindle? C'mon! There will be a way to restore it from File Manager!
Without root or knowing if adb is enabled. There's not much i can do for you. The only other thing you can try is unplug your kindle ,reset your pc, wait till it boots, then plug kindle into pc this will power on your kindle. Then go into device manager and under kindle when you open that branch it should say android composite adb interface. If not you can try to update drive and choose the option that lets you choose what driver to install. Then search in program files/amazon and install drivers from there. But without knowing if this kindle has adb enabled its kinda hard to help you. But if these do install and it does shows up as android composite adb interface. Then try the rooting process again steps 9 - 11. If you cannot get steps 9 - 11 to work your only other choice is to get a fastboot cable ( factory cable ) and use the kindle restore tool from this thread http://forum.xda-developers.com/showthread.php?t=1951254KFHD System.img Restore Tool and follow downgrade to 7.2.1 section.
Hinzman420 said:
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
Υes, I had enabled it before get this.
P.S.: Do you have TeamViewer?
What is team viewer?
Edit: i just installed it on my kindle. If you cant get it to root send me your id and i can try to help.
Sent From My Rooted Kindle HD 7"
Hinzman420 said:
What is team viewer?
Edit: i just installed it on my kindle. If you cant get it to root send me your id and i can try to help.
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
You don't have PC to help me out?
Yes but i run my pc all time from my kindle my wife ussually ties up the pc. But i can still help i have team viewer on my kindle. If not ill put it on my pc.
Sent From My Rooted Kindle HD 7"
It can find it , so ADB is turned on on the Kindle! Next step?
Plug it into your pc and go to the device manager on your pc and tell me what it says when you open up the kindle branch of your devices
Sent From My Rooted Kindle HD 7"

[REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial

Disclaimer: By following this guide, you understand and accepts that I, and any developers mentioned in this guide, will NOT be held responsible in the event that your device stops functioning or dies. While I try my best to make everything as clear and concise as it can be, accidents will happen should you not follow everything like a hawk.
Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial​
I'm going to lead you through installing Hashcode's 2nd-Bootloader and TWRP in order to start flashing custom ROMs and make backups. First, let's go over the basics and why I'm doing this in the first place. I wrote this guide to be used on a Windows computer, but as long as you can do the same things on Mac/Linux, the whole guide applies. If there are any issues, please first refer to the troubleshooting portion at the end of the guide. The 8.9 version of the device does not need the factory cable to enter fastboot mode.
+Note: As of Amazon OS update 8.3.1+, there has been a lot of issues with rooting and flashing the 2nd-bootloader. Many users reported bootloops during the completion of the guide. Those with tablets running 8.3.1 or higher, please proceed with caution. I strongly recommend you make backups in Step 2.
===== 1. Why do we need a 2nd bootloader? =====
The stock Amazon bootloader doesn't play nice with Android even though it has Android at its core. We can still use fastboot commands with it, but other than that, it's quite locked-down. In other words, normal exploits used to unlock the bootloader on other Android devices, for example, like the Nexus series by Google or the handsets by HTC don't apply here. In order to use the same features, like a custom ROM, custom kernel, custom recovery, we must bypass Amazon's software by installing a 2nd bootloader.
===== 2. Why are you posting a tutorial? =====
I'm doing this because the lack of a guide means that people like myself, who are not proficient developers, keep running into issues and some ended up bricking their devices. This means that they end up with a heavy paperweight, with no chance of fixing, other than hoping that they're lucky with a fastboot cable (not the one that came with the device) and find their way back to the beginning. I'm sick of seeing so many questions about the exact same issues so I thought, why not just make a guide everyone can follow and thus make the world a better place.
===== 3. Do I need any special equipment/knowledge? =====
You don't need any special equipment, provided that you follow this guide word-for-word and be careful. I successfully installed the 2nd-Bootloader + TWRP and flashed CM10.1, within minutes. The key is make sure you don't miss anything, and if you're not sure, don't make any random guesses. As far as knowledge, yes, and no. Know what you're dealing with. Anything underneath the ROM has the chance to brick the device, so know what you're getting into.
===== 4. Can't I just use FireFireFire or another automatic tool to install the bootloader + TWRP? =====
Definitely not. This is the exact reason why there are so many threads in the Q&A section about bricked devices in the first place. Never use a tool that wasn't made for the version of your tablet. The Kindle Fire (1st gen), the Kindle Fire 2 (2nd gen), and the Kindle Fire HD 7" & 8.9" (3rd gen) are not the same devices, at all. Due to the way the bootloader behaves, flashing the files that are only compatible for the Kindle Fire 2 on a Kindle Fire HD 7" will definitely brick it. This is because the bootloader is so-named for a program that checks the booting process before the device actually boots, and if there are any bad sectors that don't match, the device won't boot.
How do you avoid this? By following guides like mine, and first knowing exactly what model you have. Yes, the Kindle Fire 2 and the Kindle Fire HD 7" look similar, and Amazon seriously have problems with their naming method, but a bit of research tells you that the Kindle Fire HD actually contains an HD resolution screen, 1280x800 for the 7" and 1920x1200 for the 8.9". Also, ONLY the Kindle Fire HD 7" and 8.9" models have a front-facing camera while the other models don't have one at all. If you want to be sophisticated about it, you can use working fastboot to identify the tablet.
+Note: if you know 100% that you have the right model, skip to Step 1 and begin the guide. This part is only for those with knowledge of fastboot and would like to confirm scientifically that they have the right model. You don't need to know how to use ADB or fastboot in order to successfullly complete the guide and install custom ROMs:
In CMD, type:
Code:
fastboot -i 0x1949 getvar product
Hitting enter will return with <waiting for device>. If you connect your powered-off Kindle Fire HD 7" or 8.9" at this point, it will reboot into fastboot mode, and on CMD, it will return with "tate-xxx-xxx" for the 7" and "jem-xxx-xxx" for the 8.9". I cannot stress this enough, please know your stuff before you end up crying about how you made a simple mistake that cost you $200, or however many in other currencies, but I do know that universally, it's quite a lot of money.
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
===== 6. How do I boot into fastboot mode? =====
This relies on you having a working device (as long as it can boot at all, you're good). If you wish to enter fastboot mode to flash system images like new versions of TWRP or restore Amazon OS 8.1.4 if you've got freezing or bootloops, then you need a regular USB cable that came with the device, or any other mini-USB cable that fits the device and the computer. Again, you need to have Android SDK installed before you can use fastboot. Turn the device off, and leave it unplugged. Go to your computer, open command prompt, and type this:
Code:
fastboot -i 0x1949 getvar product
Hit enter, and it should return with <waiting for device>. If it doesn't, your fastboot drivers aren't working. Install Android SDK and go from there. If it does, connect your turned-off Kindle to the computer. Two things will happen: one, the command prompt will show "jem-xxx-xxx" (something there), and two, your Kindle should reboot into fastboot mode. From here, you can begin using fastboot commands to flash to the device's partitions. To exit fastboot mode, after you finished flashing what you needed, type this:
Code:
fastboot -i 0x1949 reboot
And that's all for the basics! Let's move on to the actual process.
Step 1: Rooting​
+Note: Some users reported not being able to root on later software versions, so check for 8.1.4 in your Settings, if it's higher than that, you may have some trouble, which is why I provided 3 methods.
Before you can do anything else, you need to root the device first. Rooting is the process of acquiring superuser (administrator) access on a Linux system, allowing you to modify just about anything with regards to software. It is generally very safe to do, provided you follow the correct guides and you use the correct tools, and if there are no tools, the knowledge to manually root the device. On many other Android devices, rooting also installs a custom recovery, but the Kindle Fire HD 8.9" is different. You must root first before you do any modifications.
Go to this thread: QEMU Root by sparkym3, and download the necessary attachments. Use any decompressing software to unzip the files, and install the Kindle Fire HD 8.9" ADB drivers (this may fail, no need to worry). Then jump to your device, go to Settings and turn on ADB, then plug it into your computer. At this time, your computer should report that the ADB Composite Interface has been installed. What this means is that your ADB drivers work. Go ahead and use that thread's instructions to root the device.
Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry, same idea. Make sure your ADB drivers are working, and that ADB is turned on in Settings. Open the RunMe.bat file, choose option 1. Now it will ask for your Amazon account password to restore, go ahead and type in your password and proceed. After the device reboots, it will be sluggish, now run the first method again, and you'll be back to normal with root.
You can aso try this: Root Kindle Fire HD with Windows
To check if you're rooted, when the device is on, go to the Amazon Appstore, install "ES File Manager" or any other root application, you want to see the window asking for superuser permissions. Once it installs, open it, go to settings, and turn on root browsing. If it asks for superuser permissions, you have root access, and you can move on to the next step. If the root programs say you have root, but you don't see the window asking for the permission, remember to go to the app listing, and tap on superuser to initialize the daemon, then try to check for root again.
Recap:
1. Download the root tools from the threads
2. Proceed to root by using the provided tools
3. Check if you successfully have root access using any root application
Step 2: Grabbing Files and Backing Up​
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Step 3: Installation​
You might have noticed that Hashcode made a pretty extensive thread to help you flash the bootloader, but another coder has since developed an automatic app to do all the work for you: FireFlash. Go ahead and download the .apk file. Move that file to the sdcard, and on the device, install it using "ES File Manager" (tap on that file) or "Easy Installer" (after it finishes scanning, select it and install), both found on the Amazon Appstore. You will then find it in the applications listing, go ahead and open it.
The first thing you notice is that there are spots to plug in files for different partitions. This is where those files from Hashcode come into play. Plug the freedom-boot.img into the boot partition space, plug the TWRP recovery.img into the recovery partition, and make sure to hit "apply stack". If you are NOT on the 8.1.4 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 8.1.4 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on.
Check that "disable recovery auto update" box, leave everything else alone, unplug the cable, and hit flash (the first option). You will see a progress window, and just hit OK. Then, turn off the device. Now, when you turn it on, this is the way to enter recovery every time: the moment you turn it on, you'll see the yellow Kindle title. Immediately hold down the Volume Up button (leftmost from the power button) before it turns blue, and once it does, count to three in your head and let go and you'll see the TWRP splash logo. Once you're in TWRP, you're done. Just hit reboot, and everything's finished. Now you can browse the 8.9" Development forum for custom ROMs.
If you want to save space, you can now go ahead and delete all the files we just used; you no longer have a need for any of them. Keep FireFlash, though, because in the future you might want to update TWRP, then leave everything blank, plug the update image into the recovery partition and hit flash. Only use Hashcode's TWRP builds as of now, because he specifically altered those builds to work on the Kindle Fire HD 7" and 8.9" so the official ones on the TWRP site won't work. If you flash those (especially the "blaze" codename), you will brick the device, so don't do it!
Recap:
1. Download FireFlash and install on device using file manager or installer
2. Plug in the required files in the correct areas, and check the necessary checkboxes
3. Flash, and boot into TWRP to confirm successful installation of both 2nd-Bootloader and TWRP recovery
Step 4: Flashing Custom ROMs​
This is what you've been waiting for, the ability to load custom ROMs. You have a few choices at this point in time. This list contains (somewhat, if not) stable releases only:
1. CyanogenMod 11 by Hashcode (AOSP, Android 4.4 KitKat)
2. ParanoidAndroid Port by jb2kred (AOKP, Android 4.2.2 Jelly Bean)
3. PAC-man by goldflame09 (AOKP, hybrid of CM + PA, Android 4.3 Jelly Bean)
4. CM11/SGT7 by twa-priv (CM + Samsung Galaxy Tab 7 mods, Android 4.4 KitKat)
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
Now, in case your custom ROM doesn't automatically include GApps, and you would know if you boot up and you don't see Play Store or Google Maps in the app drawer, follow this. Go to this link. You will notice a table, and on the left side, you see the CM version that corresponds to the Android version number. All the custom ROMs should use the row that corresponds to the Android version. For example, CM10.1 runs 4.2.2, CM10.2 runs 4.3, so click on the one that corresponds. If your ROM runs 4.2.2, use the 4.2.2 row, etc. After you finish downloading that .zip file, move it to the sdcard, and boot into TWRP. From there, if you want to be fancy, wipe cache and Dalvik cache before flashing, but you don't have to unless there are problems after you restart. If there are problems, like freezing on boot, or crashing, then boot back into TWRP and wipe the two cache partitions.
Generally, you only need to flash the file and you're done, but you can never be too safe. This also applies to ROMs: if you're moving from ROM to ROM, say Ubuntu Touch to CM10.1, you MUST wipe EVERYTHING except the sdcard itself, and this includes the "Factory Reset" option. However, if you're moving from one update of a ROM to another, say a nightly of CM10.1 to a newer nightly of CM10.1, you can just simply flash the update over the old one, no wiping needed (this is called dirty-flashing). However, again, if you notice problems afterward, simply boot back in TWRP and wipe the two cache partitions. Remember to always make backups before you make changes to an otherwise stable build. If there are issues that you can't seem to resolve, you can always restore back to the previous build.
Recap:
1. Download .zip for ROM + GApps and move to sdcard
2. Boot into TWRP, make backups, and wipe the necessary partitions
3. Flash ROM, and wipe cache + Dalvik cache, then reboot
4. Wait for 5 minutes after successful reboot, then reboot again
5. If there's no GApps for your ROM, use the link to download the proper version.
6. Move the file to sdcard, then boot into TWRP and flash.
7. Reboot, and if there are problems, reboot back into TWRP and wipe cache partitions.
Credits: Hashcode, fattire, and verygreen for the work on the bootloader, stanga72 for the app FireFlash, sparkym3 & prokennexusa & Bin4ry for their rooting methods, and myself for the creation of this guide.​
This guide/tutorial was extremely helpful to me as a novice, just starting how to learn to modify my Fire HD 8.9". I'd like to suggest a few changes/enhancements to the guide:
1. In the NOTE paragraph just below the first paragraph you mention issues with 8.4.1. specifically you mention issues with this release but there is no indication if these issues will prohibit successful update if the guide is strictly followed. Also, a cable is mentioned. In other posts I have seen references that indicate that no cable is necessary with the Fire HD 8.9". In fact, one post mentions that using a cable may, in fact, possibly damage the Fire HD 8.9".
2. Because I'm so new at this I'm very paranoid about making a mistake. I've read the horror stories in many of the posts and I'd like to avoid these mistakes. And because I'm so new, my only experience is with the 8.4.1 release and unfortunately it is so new, I suspect, that the developers have not had time to verify that their applications are compatible. I am not complaining since I know that 99.9% of these good people do this out of the goodness of their heart, and not for monetary gain. However, I do wish this issue of software release version could be more fully addressed.
3. Just an example - The heading clearly states that this guide applies to the Fire HD 8.9". Very clear and difficult to misunderstand! In Step 3 Installation, FireFlash is mentioned with no reference to a Fire HD operating system release number. Can I safely assume then that this utility is compatible with 8.4.1? It may be that the answer would be obvious to a more experienced person but to someone like me(and from reading many, many posts there must be a bunch of folks out there just like me), with little experience in flashing, rooting, etc.,I'm at an impasse regarding should I proceed or not proceed Thank you..
There will have to be some changes to the method to install boot and recovery on both 8.4.1 and now people are receiving 8.4.3 all the present methods will break the system, unless you have a Rom waiting on your sdcard to flash afterwards.
rebelduke said:
This guide/tutorial was extremely helpful to me as a novice, just starting how to learn to modify my Fire HD 8.9". I'd like to suggest a few changes/enhancements to the guide:
1. In the NOTE paragraph just below the first paragraph you mention issues with 8.4.1. specifically you mention issues with this release but there is no indication if these issues will prohibit successful update if the guide is strictly followed. Also, a cable is mentioned. In other posts I have seen references that indicate that no cable is necessary with the Fire HD 8.9". In fact, one post mentions that using a cable may, in fact, possibly damage the Fire HD 8.9".
2. Because I'm so new at this I'm very paranoid about making a mistake. I've read the horror stories in many of the posts and I'd like to avoid these mistakes. And because I'm so new, my only experience is with the 8.4.1 release and unfortunately it is so new, I suspect, that the developers have not had time to verify that their applications are compatible. I am not complaining since I know that 99.9% of these good people do this out of the goodness of their heart, and not for monetary gain. However, I do wish this issue of software release version could be more fully addressed.
3. Just an example - The heading clearly states that this guide applies to the Fire HD 8.9". Very clear and difficult to misunderstand! In Step 3 Installation, FireFlash is mentioned with no reference to a Fire HD operating system release number. Can I safely assume then that this utility is compatible with 8.4.1? It may be that the answer would be obvious to a more experienced person but to someone like me(and from reading many, many posts there must be a bunch of folks out there just like me), with little experience in flashing, rooting, etc.,I'm at an impasse regarding should I proceed or not proceed Thank you..
Click to expand...
Click to collapse
Thepooch said:
There will have to be some changes to the method to install boot and recovery on both 8.4.1 and now people are receiving 8.4.3 all the present methods will break the system, unless you have a Rom waiting on your sdcard to flash afterwards.
Click to expand...
Click to collapse
I am aware of the changes, but I have not been caught up with the status of the methods and their effects on the tablets. I have placed warnings at the beginning of the guide.
I have two questions about Step 2 for backing up files.
1. Is boot0block.img ever needed? It looks like it is backed up, but it isn't referred to in the restore step (fastboot commands).
2. The "adb pull" commands don't work for me. For example, this error message displays: "remote object /sdcard/stock-boot.img' does not exist". But the files are definitely there.
Sorry about asking about 2! I was actually putting the brackets around the local folder, but I realize now that you only had them to indicate that parameter was optional. However, the error that was occurring before wasn't about the local file...it was about the .img file which did exist. I'm baffled because now if I put the brackets back, it only fails with an error about that, not about the .img file. I realize I'm not making much sense, but I can't reproduce it so that it says the same error that I first mentioned above in 2.
I'd still like to know about 1 though. Thanks.
EDIT: I did Step 3 - Installation. I booted into TWRP and did a backup. I assumed that I did not have to do any wipes or install of any other rom yet, i.e. I just wanted to boot the existing 8.1.4 rom that was already there. However, when I "reboot system" from TWRP, it goes into TWRP again instead of booting up the rom.
I tried doing a restore of what I just backed up, but the result is the same. So does this mean I was required to do the wipes and install of another rom, rather just booting up my existing one? Or is there some other step I'm missing to make it get out of TWRP?
sga999 said:
I have two questions about Step 2 for backing up files.
1. Is boot0block.img ever needed? It looks like it is backed up, but it isn't referred to in the restore step (fastboot commands).
2. The "adb pull" commands don't work for me. For example, this error message displays: "remote object /sdcard/stock-boot.img' does not exist". But the files are definitely there.
Click to expand...
Click to collapse
Boot0block is backed up in the event something happens to that particular partition somewhere along the way, you will know if it does no wifi ect. Shift plus right click inside the folder that adb is located, select open command window here. Run all your commands from that cmd prompt. It will pull all those files to that folder location. Since you will know what folder it is to be pulled to this portion of the command can be omitted [C:\KFHD8Backup].
Thepooch said:
Boot0block is backed up in the event something happens to that particular partition somewhere along the way, you will know if it does no wifi ect. Shift plus right click inside the folder that adb is located, select open command window here. Run all your commands from that cmd prompt. It will pull all those files to that folder location. Since you will know what folder it is to be pulled to this portion of the command can be omitted [C:\KFHD8Backup].
Click to expand...
Click to collapse
I realized more about the format of the 'adb pull' command and posted late last night. It's in my post above your response. Thank you for answering. Also, it's good to know about what boot0block is in case something fails later.
I also added another question there, wondering about why I can only boot into TWRP, not the stock rom I already had installed. I'm pointing that out again now, just because you(and others?) may not have seen it in my EDIT above.
Do a full wipe and flash a Rom.zip. Now you will need to
Code:
adb push Rom.zip /sdcard/
For obvious reasons just don`t wipe your sdcard .
Thepooch said:
Do a full wipe and flash a Rom.zip. Now you will need to
Code:
adb push Rom.zip /sdcard/
For obvious reasons just don`t wipe your sdcard .
Click to expand...
Click to collapse
I can do that. But I'm curious to know why you're recommending this. Is it because I had problems booting up the old 8.1.4 rom and you just want me to try some other rom? Or is it that you know that what I did will never work, i.e. using FireFlash with the boot and recovery images and two checkmarks will never allow me to boot into the original rom?
Just "for fun", here's what I see when I try to boot. Times are approximate:
orange 2 seconds, blue 8 seconds, orange 30 seconds, totally black screen 2 seconds, orange 1 second (kind of flickers), blue 3 seconds, TWRP comes up.
My reason for wanting to do this is to "prepare" for going to CM10 (or other) "soon" but not quite yet. I'd like to keep the original rom for now and not wipe any data. Maybe this goal is impossible?
Thanks for your help.
sga999 said:
I can do that. But I'm curious to know why you're recommending this. Is it because I had problems booting up the old 8.1.4 rom and you just want me to try some other rom? Or is it that you know that what I did will never work, i.e. using FireFlash with the boot and recovery images and two checkmarks will never allow me to boot into the original rom?
Just "for fun", here's what I see when I try to boot. Times are approximate:
orange 2 seconds, blue 8 seconds, orange 30 seconds, totally black screen 2 seconds, orange 1 second (kind of flickers), blue 3 seconds, TWRP comes up.
My reason for wanting to do this is to "prepare" for going to CM10 (or other) "soon" but not quite yet. I'd like to keep the original rom for now and not wipe any data. Maybe this goal is impossible?
Thanks for your help.
Click to expand...
Click to collapse
Your system is broken for some reason the present method just does that. Flash Hashcode`s 8.4.1 zip. Disable OTA`s with kindlefire FirstAide or Free your kindle http://forum.xda-developers.com/showthread.php?t=2072198 or even Soupkit http://forum.xda-developers.com/showthread.php?t=2162973 . YOU MUST WIPE. Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash Rom.zip disable OTA`s before enabling wifi or you will go in circles.
Thepooch said:
Your system is broken for some reason the present method just does that. Flash Hashcode`s 8.4.1 zip. Disable OTA`s with kindlefire FirstAide or Free your kindle http://forum.xda-developers.com/showthread.php?t=2072198 or even Soupkit http://forum.xda-developers.com/showthread.php?t=2162973 . YOU MUST WIPE. Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash Rom.zip disable OTA`s before enabling wifi or you will go in circles.
Click to expand...
Click to collapse
Thanks, Thepooch. If I have to wipe anyway, I may as well just go to CM10 now. The main thing I wanted to know was whether I had done something wrong or whether what I tried to do (i.e. not install a new rom and just boot into the original rom) cannot be accomplished by anyone. I think you are saying the latter, right?
I appreciate all the help you've given me!
sga999 said:
Thanks, Thepooch. If I have to wipe anyway, I may as well just go to CM10 now. The main thing I wanted to know was whether I had done something wrong or whether what I tried to do (i.e. not install a new rom and just boot into the original rom) cannot be accomplished by anyone. I think you are saying the latter, right?
I appreciate all the help you've given me!
Click to expand...
Click to collapse
Well you got a free thanks so make sure you hit mine as well. I don`t believe you did anything wrong but I really could not tell you for sure. I have been stuck just where you are a couple times and I know I did everything right. Others I have helped became stuck the same way because Amazon has been diddling around with the boot for the last three updates. I can only assume that some encrypted part of the framework is running a stack check resulting in the system appearing broken. So yes it would be best to have something to flash before starting this process.
Thepooch said:
Well you got a free thanks so make sure you hit mine as well. I don`t believe you did anything wrong but I really could not tell you for sure. I have been stuck just where you are a couple times and I know I did everything right. Others I have helped became stuck the same way because Amazon has been diddling around with the boot for the last three updates. I can only assume that some encrypted part of the framework is running a stack check resulting in the system appearing broken. So yes it would be best to have something to flash before starting this process.
Click to expand...
Click to collapse
Thepooch, it helps to know that you and others ran into this. I did read posts that were similar, but I never was sure if anyone found an answer or knew what went wrong. This is a friend's Kindle that she got in December. I got it rooted for her back then, and I did whatever was necessary to not get OTA's. So it's way back on release 8.1.4. So I don't think Amazon's last 3 updates would have any bearing on this. But who knows! Again, thanks.
sga999 said:
Thepooch, it helps to know that you and others ran into this. I did read posts that were similar, but I never was sure if anyone found an answer or knew what went wrong. This is a friend's Kindle that she got in December. I got it rooted for her back then, and I did whatever was necessary to not get OTA's. So it's way back on release 8.1.4. So I don't think Amazon's last 3 updates would have any bearing on this. But who knows! Again, thanks.
Click to expand...
Click to collapse
You will have issues rolling it back that far, just saying there are changes that likely if not done properly will leave you stuck again. My suggestion is to flash 8.4.1 then create a solid backup when booted normal giving yourself a safety net in the event of a mishap.
Thepooch said:
You will have issues rolling it back that far, just saying there are changes that likely if not done properly will leave you stuck again. My suggestion is to flash 8.4.1 then create a solid backup when booted normal giving yourself a safety net in the event of a mishap.
Click to expand...
Click to collapse
Thepooch, I'm not sure if this is interesting to you at all, but I experimented a little and learned something. As you suggested, I flashed 8.4.1 and decided to try an unusual step.
After I used Fire Flash yesterday and booted into TWRP, I immediately created a backup. But it turned out to be no good in the sense that restoring it did not help me fix the problem of not being able to boot into the 8.1.4 (old) rom (I could only boot into TWRP). But now that I was on 8.4.1, I did a restore of ONLY the data from that old 8.1.4 backup. It seems fine so far, except for Google Play app, which just exits as soon as I execute it.....it's not a big deal to fix that. (There may be other issues, but I haven't hit anything else yet).
So....it seems like something is bad in either the boot or the system portions of the backup. It's probably system since it has framework, which you had mentioned might be causing the problem. Again, this may not be interesting, but I thought I'd let you know.
Makes sense google play rarely works from my restored backups and your system was in good shape if you flashed the 8.4.1 zip prior to restoring data.
Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP with 8.4.3
Has anyone attempted Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP running 8.4.3? If so, were you successful? If you were successful did you follow the procedure defined here or did you have to deviate? If you had to deviate, what were the deviations? Thanks!
How to root kindle fire any version (including 8.4.3) ONE CLICK
Hi I need some help.
KFHD 8.9, non-us user, but bought at amazon, i am unsure of the exact version.
ADB worked ok, device showed there. BUT "fastboot devices" didnt really show anything at all. Still I went ahead with it. Rooted using bin4ry, qemu did not work at all, permission denied error.
I did everything up to the point of flashing the freedom-rom and twrp through fireflash. It did not have 8.1.4 bootloader, so I checked the box, checked the other one and left all else as is. It seemed to flash ok. Then I rebooted,,, and its stuck on orange kindlefire logo, forever. doesn't matter what volumes i hold. tried rebooting and everything.
Now I dont really know what to do... any ideas?
Getting errors trying to install the drivers from the QEMU zip file, so no device ( sdcard ) access from recovery and the Advanced...sideload option is not working either.
I'm on windows 8, when plugging in the KFHD89 to my laptop, I see the kindle show up, but I have the yellow explanation sign. When I try to update driver software, i get error it can't update Windows ADB.
Between windows 8 and ubuntu, I've been able to get fastboot working enough to get all the files loaded...but for the lift of me !!! my copy of CM10.1 and gapps.zip are not seen via recovery...AND...I get stuck at Blue boot logo...so I'm sort stuck in recovery and need to get drivers sorted between windows and/or ubuntu so I can copy the .zip files over.
EDIT: #6 from http://forum.xda-developers.com/showthread.php?t=2277105 helped me out. I was starting ADB Sideload and connecting USB out of sequence. Followed directions and it worked.

[Q] Kindle Fire HD Stuck Booting on TWRP Instead of Android

I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
GogoplataMMA said:
I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
Click to expand...
Click to collapse
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
stunts513 said:
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
Click to expand...
Click to collapse
Now I'm all screwed up. Before I saw this message, I restored my Kindle back to when it was still running the factory default OS with root, then I shut it down to enter TWRP, and it appeared on its own, but it was installing some sort of update... and when the Kindle's factory default OS appeared, my root was gone. Now I am stuck on the factory default Kindle HD 8.9" on System Version 8.4.8. Man, I should have never accepted that update and just left it as it was. Ugh. Well, for right now, there's an entry in my Device Manager that says "Kindle Fire" and when you click the arrow to bring down the submenu, it says "Android ADB Interface." The Kindle is now working when connected through USB. Now... how do I go about rooting this thing and getting TWRP on it again, because it seems the entire thing got erased. Not having my ROM installed on this thing makes it mostly useless to me.
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I can't find anything. Download links are dead for KFFA. You have a link to get it through another source?
They are up and running when I click em. You were on this thread right?: http://forum.xda-developers.com/showthread.php?t=2096888
If that doesn't work you can always use binary's root.
http://forum.xda-developers.com/showthread.php?t=1886460
Use the old normal method if I remember correctly.
Sent from my Amazon Kindle Fire HD using Tapatalk
Nah, the link is dead here. Says the file was removed. There are other members in the forum asking as well for a new link.
I managed to get ADB working, and in Device Manager, I have "Android Device -> Android Composite ADB Interface."
I open CMD and type "ADB" and it scrolls a bunch of stuff, but when I type "ADB Devices" I get a list with nothing there. It's just blank.
I tried using BIN4RY Revision 33, using Option #1, but it just keeps bringing me to a "Path not Found" error of some sort.
It looks like all I need to manage to do now is get ADB to list my Kindle device before attempting the ROOT, but how can I do that?
I still wanna give KFFA a try, but no downloads anywhere, and I don't trust random 4Share and the likes, not that it's gonna fix my problem.
I'm close... I just need this damn ADB to list my Kindle device and I think I'll be okay.
Also, I want to say thanks for the help you've given me so far. It's greatly appreciated. :highfive:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb kill-server
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
i.imgur.com/gZrrqXm.jpg
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
GogoplataMMA said:
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
Click to expand...
Click to collapse
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, that didn't work. I'm pretty sure one or more of my drivers are interfering with the connection to the Kindle, but this is such an old OS with so many drivers, it's hard to tell.
Right now, I have a Virtual Machine of Windows 7 up. I plugged my Kindle in and I can instantly see it. I can even enter the internal storage! I'm currently installing the Android SDK for the ADB after installing the Java SE x86 version. Once I get ADB on it, I'll see if it lists my device now. Seems promising since the VM sees and allows me to already enter the internal storage, unlike my original Win7 OS.
EDIT #1: Great news! ADB now lists my device! Thing is... Root with Bin4ry Revision 33 does not seem to want to work. This is what I get...
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (14.12.2013) v33 =
======================================================================
Device type:
0) Xperia Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Please connect Device with enabled USB-Debugging to your Computer
The system cannot find the path specified.
Doing a Backup first, please confirm this on your device!
The system cannot find the path specified.
Done!
Press any key to continue . . .
Click to expand...
Click to collapse
It doesn't give me a chance to do anything. All of that pops up as soon as I press enter. ADB and third party software is enabled on my Kindle. ADB even reads my device as:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9110232560198 device
Click to expand...
Click to collapse
I'm at a loss now. Any ideas?
EDIT #2: Success! The issue was I was using Root with Bin4ry Revision 33. I should have been using Root with Bin4ry Revision 30. That worked, and I am now ROOT. Mission accomplished. Now the next part of my mission... figuring out how to get TWRP on this thing.
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
Everything seemed to work until I get to Step 3. I'll enter the commands but it tells me that there is no such directory or something. Something about there not being any "stack." Can't recall. I wanted to ask on the thread there but the site isn't allowing me to post there.
adb push stack /sdcard/ is where the issue occurs. Everything else worked.
I'm at a loss, and the comments don't seem to help on that thread. Please tell me there is an easier method of getting TWRP on this thing.
ERROR:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push stack /sdcard
/
cannot stat 'stack': No such file or directory
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
GogoplataMMA said:
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
ERROR:
Click to expand...
Click to collapse
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He's on a 8.9", he just posted in the wrong section. Use the fireflash method from seokhuns tutorial, just don't forget to check the box with red text near it or you will get a nice redscreen brick. Lemme grab a link
Edit: link grabbed! http://forum.xda-developers.com/showthread.php?t=2277105
I used FireFlash, followed the instruction... now I cannot get passed the first "Kindle Fire" logo when I turn the Kindle on. It just freezes at "Kindle Fire" as soon as I turn it on. I can't seem to do anything at all, and it won't connect via USB. Any ideas?
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It's not working... it won't read at all. Device Manager doesn't see the Kindle at all. And yes it is 8.9". I think it may be bricked now. ;'(
And all because of that stupid update... ughhhh. Sucks!
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I switched over to my main Windows 7 OS and did what you said. I connected it and it showed for a brief moment in Device Manager, so I quickly loaded the driver and updated. But wen I type the command you gave me, it says <waiting for device>, so I plug it back in and... nothing. At all. Just sits there at <waiting for device>
I'd try Linux, I have several copies of different OS's, but I'm not very good at working with it or using Terminal... I can try that though, but no clue how I'd get ADB or the Kindle to read on it. :\
And yes, 100% it's the 8.9". The resolution is 1200p.
OK the command has to be run while the device is off and disconnected, once it says waiting for device, plug the kindle in and it should work if the drivers are working. Linux is really easy to use with a kindle, it has the fastboot and adb drivers built in natively, only thing you need is the fastboot command from the Ubuntu repos if you are using Ubuntu, believe they were added to the repo in 13.10.
Sent from my Amazon Kindle Fire HD using Tapatalk

what guide should I use

I have a kindle fire HD. About a year and half after we got it, it started to randomly reboot. Since the warranty was expired Amazon would not fix it without payment. The reboots started about once a month and increased to about daily. At that point we did a factory reset. This has continued to today.
At this point I want to completely remove the amazon firmware and replace with a full version of Android. I am hoping this fixes the random rebooting.
Before we can replace the firmware, we should root it in order to make the process easier. To root it, we need to determine which OS version you have. Swipe down from the top of the screen to open the notification bar, and then tap "More". Select "Device", and then "About". You should see a string that begins with 8.x.x or 7.x.x. Please comment back on this post with that string, as it's critical in determining how to replace the stock Amazon OS.
System version 7.5.1
Start here (http://forum.xda-developers.com/showpost.php?p=56678177&postcount=5) with the directions that @sd_shadow posted for rooting 7.5.1. Once you're done, verify your root access with an app such as this one (http://www.amazon.com/Free-Android-Tools-Root-Checker/dp/B00TSA0MWY).
Also, if you're running Windows on your PC, download and run the 15 second ADB installer (http://forum.xda-developers.com/showthread.php?t=2588979). Answer yes to the "install ADB and fastboot" and "install ADB system wide" questions, and no to the "Install device driver" question. Also install the kindle drivers linked in this thread (http://forum.xda-developers.com/showthread.php?t=1890413). If you're on Windows 8, 8.1, or 10, follow these instructions (www.howtogeek.com/167723/how-to-dis...8.1-so-that-you-can-install-unsigned-drivers/) to temporarily disable driver signature enforcement before you install the kindle drivers.
I am on Windows 7. I assume I should follow the windows 7 directions AFTER I verify root, correct?
Correct. Reboot after the kindle drivers are installed, and then follow @Hashcode's instructions here (http://forum.xda-developers.com/showthread.php?t=2128848) to replace the firmware.

Categories

Resources