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.
I have a Kindle Fire 2 (I assume its Kindle 2nd Gen) / It has no camera its 7"s
It has 2nd Bootloader and TWRP (v2.3.3.0) on it
I had a Cyanogenmod ROM on it but decided it needed something new
I can boot into TWRP
I cannot get it to mount as USB
Windows 8 Device Manager shows it as Kindle Fire 2 -- but has no drivers installed
I cannot get a ROM onto this
I run ADB from the KFF Package
ADB kill-server
ADB start-server
ADB Device.......
Nothing....
Ive tried a million drivers, including the ones in the KFF package, nothing.
I have JDK and Dev Kit installed
I have the custom amazon repository added in the dev kit with suggested packages
Still no Amazon Kindle Fire2 drivers installed
I am in Windows Test Mode and do not require signatures in my OS.
Windows 8, not 8.1
Any suggestions?
Finally Progress!
C:\KFFirstAide>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\KFFirstAide>adb devices
List of devices attached
0123456789ABCDEF recovery
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Now I can sideload.
cnewman402 said:
Finally Progress!
http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Now I can sideload.
Click to expand...
Click to collapse
Did you get where you need to be then? Windows 8 driver enforcement has to be disabled as well http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/ Go Big Red
Sorry for probably posting something that's very common. Everything I try doesn't seem to work and I don't know what to do. I have 2 7" Kindle Fire HD's that I have previously rooted(quite some time ago). My PC HDD crashed and burned recently and I was attempting to sideload some stuff on to them, and I can't seem to figure out how I was able to get the ADB Drivers to install correctly when I first rooted these. ANy help would be greatly appreciated...
Wrong Forum
I've requested that this thread be moved to 7" Kindle Fire HD Q&A, Help & Troubleshooting
The Kindle Fire HD 7 First Aide Tool has drivers,
but you should also see Windows Device Drivers and the Device Manager
note: written for original kindle but steps are similar
install drivers with First Aide, reboot pc, connect Kindle, update drivers in Device manager.
if that doesn't work, when updating drivers select drivers folder from First aide files, may need to uninstall old drivers, and reboot pc to get it to work.
Ok, thanks. Sorry about posting in the wrong forum. I'll take a look at the links provided. :fingers-crossed:
sd_shadow said:
Wrong Forum
I've requested that this thread be moved to 7" Kindle Fire HD Q&A, Help & Troubleshooting
The Kindle Fire HD 7 First Aide Tool has drivers,
but you should also see Windows Device Drivers and the Device Manager
note: written for original kindle but steps are similar
install drivers with First Aide, reboot pc, connect Kindle, update drivers in Device manager.
if that doesn't work, when updating drivers select drivers folder from First aide files, may need to uninstall old drivers, and reboot pc to get it to work.
Click to expand...
Click to collapse
you can use the ones in my signature, if on windows 8 you will need to disable driver signature enforcement first.
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
Hello
I am having problems with my ADB Devices, first it read the my Amazon Fire as an ADB Device and I was able to root CM on to my Amazon Fire. But now it doesnt show up as an ADB Device at all but shows up as a Portable Devices. I have been trying to redirect the Drivers to the latest USB Driver Files that I had downloaded from your link but it says the drivers are fully update to date but I am still not able to see ADB Devices for my Amazon Fire in the ADB Device Section in my Device Manager.
I am in need to fix this so I can reboot my Amazon Fire into CM with Gapps for it did not install Gapps when I flashed the CM, Super SU, and Gapps the first time. And now it wont show up as ADB Devices.
Is this a problem with my SDK Manager where I would need to update it?
Any information in regards to this will be great.
Thank you
Hmm if you manually put the tablet into fastboot mode will fastboot work? Turn it off, then hold volume up button and power button. Then see if
fastboot devices
works