Database Develop

[Q] ADB Device Not Recognized

Any help with my problem would be greatly appreciated!
Recently I managed to soft brick my Kindle Fire HD 7", and hoped to use the "KFHD System.img Restore Tool" to fix. I bought a factory cable and was able to put my Kindle into fastboot mode. Prior to this I had ADB installed so I could root my KFHD (which I did).
Now obviously when I rooted my KFHD, ADB recognized my device then. Unfortunately, now I have no such luck. While in fastboot I tried to use the command ---> adb shell su -c "reboot bootloader" <--- but I kept getting error messages that stated there was no recognized device.
I re-installed the AndroidSDK file to ensure there were no errors there and tested ADB with successful results. I also re-installed the Device Drivers and made sure that in my device manager under Kindle Fire it said "Android ADB composite interface" (or similar, I don't remember off of the top of my head). I went back and tested again, and ADB still does not recognize my device while in fastboot. I then left my Kindle on until it ran out of battery to test to see if ADB would recognize when out of fastboot.
After turning on my Kindle when not in fastboot, I typed in the command prompt "adb devices" and no device showed up. Also, now under my device manager "Android ADB composite interface" or whatever doesn't even show up. I have searched over and over again on many forums with no luck. Does anyone know what I am doing wrong? Or what I should try doing?
Sorry for that ^huge story^ but thanks in advance for any feedback!

ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
"That's a special kind of stupid. The kind that makes me laugh."

I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan

bryanchapman9999 said:
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
Click to expand...
Click to collapse
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."

soupmagnet said:
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ive been using the android drivers on windows 8 without an issue. They have to be manually installed and driver signing needs to be turned off.
Sent from my KFOT using Tapatalk 2

soupmagnet said:
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
Click to expand...
Click to collapse
I see, well the program seemed to work fine without it apparently (the line of code). My Kindle is working perfectly again! Thank you for the reply.

[Q] Kindle Fire half Brick Help (shows life and boots)

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'm stuck! Is a factory cable required?

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

[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

Amazon Fire 7" - Which ROM to install?

Hi,
I have the Amazon Fire 7" (not the Fire HD "7!). I did not find any Android ROM for this model, only for the Fire HD 7". Is it possible that such ROM does not exist?
If I'm mistaken, would appreciate if someone could refer me to the proper thread.

moralshixch said:
Hi,
I have the Amazon Fire 7" (not the Fire HD "7!). I did not find any Android ROM for this model, only for the Fire HD 7". Is it possible that such ROM does not exist?
If I'm mistaken, would appreciate if someone could refer me to the proper thread.
Click to expand...
Click to collapse
You need to identify the version of your Kindle. If its the otter2 try these threads over here:
http://forum.xda-developers.com/kindle-fire-hd/fire-2-development
another helpful discussion for you:
http://forum.cyanogenmod.org/topic/90173-otter-or-otter2/
---------- Post added at 02:43 AM ---------- Previous post was at 02:27 AM ----------
If it helps I can attach all the recovery/rom/and gapps that I'm using that seem to work well. I was using pac-rom but switched to slimkat a while ago. I only use this for a bedside alarm clock right now, but I'm thinking of putting it side mounted in my car into my stereo auxiliary running Kodi with the Car Skin they got going on in a thread. I'm not using the latest slimkat rom either I'm using an old version because it works well for me.

How do I identify the version of my Kindle? If it helps, it's the 5th generation that was sold during last December in Amazon for $35

moralshixch said:
How do I identify the version of my Kindle? If it helps, it's the 5th generation that was sold during last December in Amazon for $35
Click to expand...
Click to collapse
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.

monster1612 said:
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.
Click to expand...
Click to collapse
I realize this thread is a little old, but I too am trying to get something else on my Kindle Fire other than Fire OS if possible (LineageOS more than likely). Where might I find all of these drivers and utilities, as I have no idea what my Kindle's codename is.
Thanks!

MZGSZM said:
I realize this thread is a little old, but I too am trying to get something else on my Kindle Fire other than Fire OS if possible (LineageOS more than likely). Where might I find all of these drivers and utilities, as I have no idea what my Kindle's codename is.
Thanks!
Click to expand...
Click to collapse
The driver is available on Amazon's developer site, under the "Installing the USB Driver" section. This is assuming you're using Windows, of course.
The ADB binaries can also be downloaded directly from Google as a single .zip file. Once you have both of those downloaded, you should be able to extract the ADB package to an easily accessible directory, right-click on an empty space within the folder view of said directory while holding the shift key down, click "Open command prompt here", and then type the fastboot command I mentioned in the previous reply to identify your kindle.
(Apologies for the late reply!)

Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Code:
< waiting for any device >
Nothing else happens, it just keeps waiting.

monster1612 said:
The driver is available on Amazon's developer site, under the "Installing the USB Driver" section. This is assuming you're using Windows, of course.
The ADB binaries can also be downloaded directly from Google as a single .zip file. Once you have both of those downloaded, you should be able to extract the ADB package to an easily accessible directory, right-click on an empty space within the folder view of said directory while holding the shift key down, click "Open command prompt here", and then type the fastboot command I mentioned in the previous reply to identify your kindle.
(Apologies for the late reply!)
Click to expand...
Click to collapse
I realized I never quoted you in my last reply (forums didn't like me quoting links since my account is so new), so you probably wouldn't see my previous reply. Thanks again for your help, I quoted my last post below.
MZGSZM said:
Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Code:
< waiting for any device >
Nothing else happens, it just keeps waiting.
Click to expand...
Click to collapse

MZGSZM said:
I realized I never quoted you in my last reply (forums didn't like me quoting links since my account is so new), so you probably wouldn't see my previous reply. Thanks again for your help, I quoted my last post below.
Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Click to expand...
Click to collapse
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.

monster1612 said:
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.
Click to expand...
Click to collapse
The device does show up in its own category:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Assuming this is the correct one, I'm not sure why I still can't get a readout.

monster1612 said:
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.
Click to expand...
Click to collapse
Hate to sound like a nag, but hoping you saw my last post. Any thoughts on why I'm not getting a readout? Thanks again!

MZGSZM said:
The device does show up in its own category:
Assuming this is the correct one, I'm not sure why I still can't get a readout.
Click to expand...
Click to collapse
That's the right category. Theoretically, the device should be recognized in ADB if you already have it enabled on the Kindle. Try going to the device properties and "updating" the driver by selecting a different one from the list of Fire-specific drivers installed.
My apologies for the extreme lapse in response time - I went through finals earlier this month, and totally forgot about XDA for a while. Anyhow, I haven't worked with the Kindle on Windows in a while - drivers are notoriously finicky, so I tend to use Ubuntu and other Linux OSs for adb and whatnot, seeing as though everything seems to just work without the need for device-specific drivers on that platform.

monster1612 said:
That's the right category. Theoretically, the device should be recognized in ADB if you already have it enabled on the Kindle. Try going to the device properties and "updating" the driver by selecting a different one from the list of Fire-specific drivers installed.
My apologies for the extreme lapse in response time - I went through finals earlier this month, and totally forgot about XDA for a while. Anyhow, I haven't worked with the Kindle on Windows in a while - drivers are notoriously finicky, so I tend to use Ubuntu and other Linux OSs for adb and whatnot, seeing as though everything seems to just work without the need for device-specific drivers on that platform.
Click to expand...
Click to collapse
Hey, no worries. I know how crazy life can get sometimes.
I tried using the different driver versions available without any luck. My laptop currently has a copy of Ubuntu installed, so I could definitely try it on there (with some guidance from you). I'm pretty familiar with how to use the terminal, and would've tried it under Linux had I known it might've been easier.
Thanks again for all of your assistance!

MZGSZM said:
Hey, no worries. I know how crazy life can get sometimes.
I tried using the different driver versions available without any luck. My laptop currently has a copy of Ubuntu installed, so I could definitely try it on there (with some guidance from you). I'm pretty familiar with how to use the terminal, and would've tried it under Linux had I known it might've been easier.
Thanks again for all of your assistance!
Click to expand...
Click to collapse
Nice! I don't know if you need to enable the universe software repo within Ubuntu before you can install the adb programs, but you should be able to type sudo apt-get install android-tools-adb android-tools-fastboot to have them install. After that, you can use the fastboot commands exactly the way you would on Windows, and thus should be able to get the Kindle to boot into fastboot directly from a powered off state. Let me know if you need any other advice or help.

monster1612 said:
Nice! I don't know if you need to enable the universe software repo within Ubuntu before you can install the adb programs, but you should be able to type sudo apt-get install android-tools-adb android-tools-fastboot to have them install. After that, you can use the fastboot commands exactly the way you would on Windows, and thus should be able to get the Kindle to boot into fastboot directly from a powered off state. Let me know if you need any other advice or help.
Click to expand...
Click to collapse
So, I'm still not having any luck. I'm not entirely sure why, I'm guessing maybe I'm missing something?
I've tried getting fastboot to work on three different devices now, two of which were running a Linux OS, the third Windows 7.
I'm running the mentioned fastboot command and then connecting the kindle over USB while it is powered off. ADB is enabled in developer settings.
I've tried running the command with or without the ADB daemon started and with or without the computer in question being authorized as I wasn't sure if that was necessary.
I tried it on my laptop (which is now running Kubuntu) without success but, also read somewhere that fastboot doesn't like USB 3.0. For that reason I tried it also on one of my Raspberry Pi 3s with a fresh install of Raspbian Lite. I didn't have anything else available at the moment running Linux.
I'm guessing I'm probably just missing something small or did one of the steps incorrectly maybe.

MZGSZM said:
So, I'm still not having any luck. I'm not entirely sure why, I'm guessing maybe I'm missing something?
I've tried getting fastboot to work on three different devices now, two of which were running a Linux OS, the third Windows 7.
I'm running the mentioned fastboot command and then connecting the kindle over USB while it is powered off. ADB is enabled in developer settings.
I've tried running the command with or without the ADB daemon started and with or without the computer in question being authorized as I wasn't sure if that was necessary.
I tried it on my laptop (which is now running Kubuntu) without success but, also read somewhere that fastboot doesn't like USB 3.0. For that reason I tried it also on one of my Raspberry Pi 3s with a fresh install of Raspbian Lite. I didn't have anything else available at the moment running Linux.
I'm guessing I'm probably just missing something small or did one of the steps incorrectly maybe.
Click to expand...
Click to collapse
Does your Linux distro recognize the device if you have it plugged in while you're in the Kindle's main OS and you type adb devices? It should work if you have ADB enabled in developer settings.

monster1612 said:
Does your Linux distro recognize the device if you have it plugged in while you're in the Kindle's main OS and you type adb devices? It should work if you have ADB enabled in developer settings.
Click to expand...
Click to collapse
Yep, if I type that a message pops up on screen saying it's unauthorized. The kindle then asks me if it should be authorized.

Try running fastboot as root.

basenjidad said:
Try running fastboot as root.
Click to expand...
Click to collapse
Thanks for the suggestion. I gave that a shot, still no luck getting this Kindle to fastboot.

monster1612 said:
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.
Click to expand...
Click to collapse
After installing LineageOS on another device, I learned of a command that should force the Kindle to fastboot, and it seemed to work. When I ran the suggested fastboot command I got this output:
Code:
product: AUSTIN
finished. total time: 0.004s
Where might be my next step in finding a compatible ROM?
Many thanks again!