Related
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.
Hello, This is my first ever post on this site. I'm a beginner so take it easy,"if you can"
i have searched all the post i could find both google and xda. i seem to be stuck in twrp mode every time it boots it goes directly to the
twrp menu. i found i have no os installed and no files at all even the twrp.zip file which i had it saved on the /sdcard/downloads. im not to familiar with fastboot but i think i can get it into it by using the factory cable but i can see it on my comp as kindle but missing drivers. i tried installing drivers but to no avail. what can i do... please help if you can and ask for more info if you need it. Thank you
You shouldn't nessasrily need fastboot to fix this, I'm assuming the drivers you don't have installed for twrp is the adb device, so try updating Ur drivers with this version of the drivers: http://forum.xda-developers.com/showthread.php?p=44446906
Once the adb driver work you should be able to go I to twrp, hit advanced, then hit side load, and swipe to start side load, and with it plugged I to your PC put either a cm ROM or the stock rooted amazon ROM from android development into the same folder as your adb command, and run a line with this syntax in a command prompt: adb sideload myrom.zip
If that doesn't work you might be able to use adb push when not in side load mode but I haven't tinkered to much with twrp. If you must resort to using fastboot you shouldn't even need a factory cable in this case, as u can just go into twrp and hit reboot and tap bootloader, that should put you in fastboot. Hope this helps.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Code:
adb shell idme bootmode 1
Solution
Am3nd said:
Hello, This is my first ever post on this site. I'm a beginner so take it easy,"if you can"
i have searched all the post i could find both google and xda. i seem to be stuck in twrp mode every time it boots it goes directly to the
twrp menu. i found i have no os installed and no files at all even the twrp.zip file which i had it saved on the /sdcard/downloads. im not to familiar with fastboot but i think i can get it into it by using the factory cable but i can see it on my comp as kindle but missing drivers. i tried installing drivers but to no avail. what can i do... please help if you can and ask for more info if you need it. Thank you
Click to expand...
Click to collapse
Ok guys thanks a lot to stunts513 i have got it fixed. i will explain it to all the noobs out there what i did.
Like stunts513 said download the drivers from the link he provided, ok once you download it you will see a whole bunch of files but no exe files
like i said i was a noob and i was stuck on how to install the drivers, what you do, is you go to the device manager and click update drivers on the unknown or kindle with the yellow sign (assuming you have one) the click "let me pick from a list....." next if you see "have a disk" click that if you dont see it, hit next you will see it then. now point it toward the "usb drivers file" you just downloaded there should be a .inf file there click it and say open (next-next-next) your done on that part then follow his instructions
when you reach the part of the adb command this is what i did, i moved the file to where my adb was right next to adb.exe. i named it com10.zip to make it short and easy to type. you then start the adb by typing cd (wherever you placed your adb setup, mine was in C:\Users\MN\Desktop\adt-bundle-windows-x86-20130717\sdk\platform-tools) then type adb devices to see if your kindle is under there it should, mine at the time said something like "12312if8923823f recovery" before you type adb sideload make sure you are in the twrp menu and your in the sideload option. you then type adb sideload yourfilename.zip ....... "yourfilename meaning the file you wanted to transfer which should be in the adb tool section" it will start to transfer, when it was finished go and flash it your done.
One other thing that i had a problem with was, i couldn't get the kindle to connect to my computer, what you do is while it is connected uninstall the driver first in the devicemanager, then go to program files and the amazon folder keep going until you get to a folder with a uninstall .exe click it and uninstall it, then disconnect and then install the kindle drivers the reconnect there you go.
I hope i helped anyone had a similar problem cause i was up since 3 am in the morning working on this lol " i had hard bricked a kindle before, i was determined not to let it happen again"
~second post~
Am3nd said:
Ok guys thanks a lot to stunts513 i have got it fixed. i will explain it to all the noobs out there what i did.
Like stunts513 said download the drivers from the link he provided, ok once you download it you will see a whole bunch of files but no exe files
like i said i was a noob and i was stuck on how to install the drivers, what you do, is you go to the device manager and click update drivers on the unknown or kindle with the yellow sign (assuming you have one) the click "let me pick from a list....." next if you see "have a disk" click that if you dont see it, hit next you will see it then. now point it toward the "usb drivers file" you just downloaded there should be a .inf file there click it and say open (next-next-next) your done on that part then follow his instructions
when you reach the part of the adb command this is what i did, i moved the file to where my adb was right next to adb.exe. i named it com10.zip to make it short and easy to type. you then start the adb by typing cd (wherever you placed your adb setup, mine was in C:\Users\MN\Desktop\adt-bundle-windows-x86-20130717\sdk\platform-tools) then type adb devices to see if your kindle is under there it should, mine at the time said something like "12312if8923823f recovery" before you type adb sideload make sure you are in the twrp menu and your in the sideload option. you then type adb sideload yourfilename.zip ....... "yourfilename meaning the file you wanted to transfer which should be in the adb tool section" it will start to transfer, when it was finished go and flash it your done.
One other thing that i had a problem with was, i couldn't get the kindle to connect to my computer, what you do is while it is connected uninstall the driver first in the devicemanager, then go to program files and the amazon folder keep going until you get to a folder with a uninstall .exe click it and uninstall it, then disconnect and then install the kindle drivers the reconnect there you go.
I hope i helped anyone had a similar problem cause i was up since 3 am in the morning working on this lol " i had hard bricked a kindle before, i was determined not to let it happen again"
~second post~
Click to expand...
Click to collapse
Thanks, this helped.
Another noob here, first post. Firstly, thanks very much, this was also a great help to me. Just wanted to say i had a little trouble with the sideload command. Kept returning the error * cannot read 'com10.zip' *. Despite being in the same directory as the adb, to fix you must give the directory in the command like so:
adb sideload C:\pathToAdb\com10.zip
Just in case anyone is having the same issue. Cheers again
Hi, my device (tate) cannot connect to any of my computers in adb or fastboot modes, rendering me unable to transfer any files onto my device. However, I am able to perfectly boot into TWRP recovery. The ROM I previously flashed didn't work, and I had already factory reset the device without making a backup. How can I now transfer a working ROM given my problems in adb?
OS: Windows 8 x64 (failed to install the KFHD adb drivers)
Upon command 'adb devices' or 'adb usb': 'no device found'
Upon command 'fastboot -i 0x1949 getvar product': nothing happens
You need to install the drivers while in twrp/fastboot. I would recommend just using adb to push the ROM onto the sdcard from twrp. You will need to fix your drivers first though, to do that you need to disable windows driver signature enforcement, look it up on Google. Then download the drivers in my signature and update the drivers for the device with a triangle in the device manager and point then to where you extracted the drivers. Then try adb again while in twrp.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Disable device driver signature enforcement.
Both must be done from the administrator profile to work right.
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue.
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit /set testsigning on
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1, 2 and 3 in part B of tutorial enter these commands
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/
---------- Post added at 10:18 PM ---------- Previous post was at 09:55 PM ----------
chemicalrubber said:
Hi, my device (tate) cannot connect to any of my computers in adb or fastboot modes, rendering me unable to transfer any files onto my device. However, I am able to perfectly boot into TWRP recovery. The ROM I previously flashed didn't work, and I had already factory reset the device without making a backup. How can I now transfer a working ROM given my problems in adb?
OS: Windows 8 x64 (failed to install the KFHD adb drivers)
Upon command 'adb devices' or 'adb usb': 'no device found'
Upon command 'fastboot -i 0x1949 getvar product': nothing happens
Click to expand...
Click to collapse
You need to push a ROM onto TWRP using this tutorial http://forum.xda-developers.com/showthread.php?t=2459498 Also disable drivers via my post above this post. Lastly, make sure to use Hashcodes crackflasher mirro as TWRP is still messed up making goo.img zip file downloads a mere shell that fail to flash. Make sure to have the most up to date TWRP as well http://forum.xda-developers.com/showthread.php?t=2128848
Thanks stunts and Linearequation! Disabling driver signature enforcement was the crucial step. Adb now works perfectly in recovery!
chemicalrubber said:
Thanks stunts and Linearequation! Disabling driver signature enforcement was the crucial step. Adb now works perfectly in recovery!
Click to expand...
Click to collapse
You're welcome. To clarify my post, TWRP works fine, goo,.img is causing some corrupted downloads yet.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
I bricked my Fire HD 7" a while back and decided to start working on it again.
I was doing some mods before I bricked it. The device, once it boots into Kindle's OS is EXTREMEMELEY slow. All the icons are blank, and it is extremely slow to do anything on but it kinda works. The menu to reset the device doesn't work, and the keyboard and other stuff barely works if at all as well.
I believe the unit used to be rooted, but somewhere along my bad fixing process I believe it is 'locked' again.
I am currently working on making a factory cable from the droid website in where you solder a cable from 1 to 4.
Following that guide. Any tips?
Thank you very much
Edit:
I can boot the KF HD second gen into fastboot mode but no idea what to do next. I have tried almost everything. I can't instal adb or even get the drivers to work. The device shows up with Windows giving me an error message. Yes, I have Android sdk and Java installed with proper Google usb drivers and api in there modified to add Kindle Fire HD in there. And yes, I have tried to manually add drivers. It just won't work, and or show life.
This sounds like a bad qemu root... look in the /data folder for a ".prop" file and delete it if you can. I would check the device manager for a usb composite device with a hardware id vid of 1949 and uninstall it if I were you. Also try the drivers in my signature, they should work with all modes but you tend to have to uninstall the driver between going from normal os to fastboot and recovery.
Sent from my LG-P769 using xda app-developers app
stunts513 said:
This sounds like a bad qemu root... look in the /data folder for a ".prop" file and delete it if you can. I would check the device manager for a usb composite device with a hardware id vid of 1949 and uninstall it if I were you. Also try the drivers in my signature, they should work with all modes but you tend to have to uninstall the driver between going from normal os to fastboot and recovery.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Can you go into detail on what it is that you mean pleasE?
kingbowness said:
Can you go into detail on what it is that you mean pleasE?
Click to expand...
Click to collapse
ok lemme reply now that i'm on my pc so i can type better, the kindle drivers are a bit finicky, between switching between fastboot, recovery, and the normal os it tends to make you have to uninstall the device to reinstall the drivers, and if adb was enabled in the os typically it shows up as a composite device that you don't tend to notice, so if you goto the device manager, look under usb devices, and see some composite devices right click them and hit properties and goto the details tab, look for one with a hardware id with something like "USB\VID_1949" it will have other stuff after that but i don't feel the need to put it. If you find one of those then uninstall the composite device and search for new hardware or just unplug and plug the kindle back in, it should be able to install the drivers now. Otherwise just uninstall any previous kindle devices when switching between boot modes.
As for the other part i was saying, you could probably just fix this if adb is enabled in the main os, just connect to the kindle from an adb shell and cd into the /data folder and look for a ".prop" file(run the command ls if you don't know that much about linux it will list the contents of the directory you are in.), i don't remember the name, but part of the qemu root process sometimes leaves that file there and causes the symtoms you mentioned, deleting the file fixes it but i don't remeber its name offhand. so if you see a .prop file in the /data folder then run "rm whatevername.prop"
stunts513 said:
ok lemme reply now that i'm on my pc so i can type better, the kindle drivers are a bit finicky, between switching between fastboot, recovery, and the normal os it tends to make you have to uninstall the device to reinstall the drivers, and if adb was enabled in the os typically it shows up as a composite device that you don't tend to notice, so if you goto the device manager, look under usb devices, and see some composite devices right click them and hit properties and goto the details tab, look for one with a hardware id with something like "USB\VID_1949" it will have other stuff after that but i don't feel the need to put it. If you find one of those then uninstall the composite device and search for new hardware or just unplug and plug the kindle back in, it should be able to install the drivers now. Otherwise just uninstall any previous kindle devices when switching between boot modes.
As for the other part i was saying, you could probably just fix this if adb is enabled in the main os, just connect to the kindle from an adb shell and cd into the /data folder and look for a ".prop" file(run the command ls if you don't know that much about linux it will list the contents of the directory you are in.), i don't remember the name, but part of the qemu root process sometimes leaves that file there and causes the symtoms you mentioned, deleting the file fixes it but i don't remeber its name offhand. so if you see a .prop file in the /data folder then run "rm whatevername.prop"
Click to expand...
Click to collapse
Nope, nothing shows up in device manager in those areas. The Kindle shows up under portable devices. NOTHING works in uninstalling or changing it's drivers.
I can't get ADB no matter what it seems.
So what about when its in fastboot mode? If it goes into fastboot, uninstall the portable device and try searching for new hardware, if it cant find a driver then point it to mine. If you can get fastboot working you can just use kindle fire first aid to restore the device.
stunts513 said:
So what about when its in fastboot mode? If it goes into fastboot, uninstall the portable device and try searching for new hardware, if it cant find a driver then point it to mine. If you can get fastboot working you can just use kindle fire first aid to restore the device.
Click to expand...
Click to collapse
Drivers don't work in fastboot. I keep getting This Device cannot start code 10.I got the drivers to work in normal mode now and have ADB installed, but I can't find the ADB devices even with kill-server and adb devices.
Thank you everyone for your help, I got the issue fixed.
I used FFFirstAide.
That didn't work for me for a while because my fastboot cable had a disconnected data lined.
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
It is doable without a factory cable, the known rooting utilities people typically use are kindle fire first aid or binary's root. If you still can't get it to root, you can technically use a fastboot cable and kffa to restore it to a earlier is that os pre-rooted.
Sent from my Amazon Kindle Fire HD using Tapatalk
pastorbob62 said:
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
Click to expand...
Click to collapse
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
pastorbob62 said:
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
Click to expand...
Click to collapse
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
LinearEquation said:
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
Click to expand...
Click to collapse
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
pastorbob62 said:
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
Click to expand...
Click to collapse
Its kinda just a precautionary measure, to put it plainly, your kindle will bootloop into recovery if you do the process on 7.4.8, so unless you know how to use "Adb push" its suggested to put the rom and gapps onto the kindle ahead of time so it will be there when you start to bootloop into recovery. On another note, you do need to downgrade the bootloader though, if you use hashcodes method, please check the md5sum on the bootloader file before flashing it to avoid a hardbrick. If you used the fireflash method i wouldnt worry about it, just make sure you check off the downgrade bootloader button above or beside the red warning text.
I had these same issues. The device wouldn't boot into fastboot while it was <waiting for device>.
I did this.
1. Used Many Root Tool to gain root. http://forum.xda-developers.com/showthread.php?t=1886460
2. Placed the Rom and Gapps file on my sd card to be safe.
3. Used Anonymous.123's Tool up until the fastboot <waiting for device> malfunction. http://forum.xda-developers.com/showthread.php?t=2685414
4. Opened the Batch File for the Flasher Tool and copied and pasted the fastboot commands into a terminal with the Kindle in Fastboot. The only way I could get it in fastboot was "adb shell su -c reboot bootloader"
This will install the 4.2 bootloader so you don't have to flash back.
5. Profit 2nd Bootloader and TWRP
Good luck. You'll get it.
Sorry I Keep using the quote reply wrong. Havn't been on XDA in a while.
Okay, following Hashcode's procedure, I have successfully completed all steps up to flashing CM 10.2. TWRP works great and I made a backup from it. Not really necessary since I had backed up my Kindle three different ways and also copied all of my data to my PC as well.
But when I went to copy the TWRP backup to my PC for safekeeping I discovered that now I no longer have access to my Kindle from my PC's file explorer when I am booted into my Kindle. Prior to doing any of the steps here I could swap files back and forth without any problem. So how do I get that feature back??
I am running WIndows 8.1. This worked before I followed the procedures here. Also, when I pull files in adb where do they get stored??? Can't seem to find them.
Check the storage settings in CM you have to turn MTP storage in.
Sent from my Galaxy Nexus using xda app-developers app