Develop Bugs

[Q] no adb after firefirefire - SOLVED

my computer won't recognize the kindle fire in adb. I have the kf rooted. have firefirefire installed. after firefirefire was installed is when I lost adb. I have tried reinstalling the drivers numerous times to no avail. Any suggestions?
I have deleted all previous sdk, usb drivers or anything android related from computer to start from scatch. I did a factory reset on the kf. I currently have KFU v0.9.3 setup from instructions i followed on a youtube video titled (How to Root - Kindle Fire 6.2.2 BurritoRoot3) by Nat3Mil. sorry I would post a link but apparently I can't until I have 8 posts.
kf v6.2.2
win7
thanks

maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
and check "adb_usb.ini" in the ".android" folder in your personal folder
it should include 0x1949 - i use to add 0x18d1 also in a new line

Sound like your Fire is in Fastboot. This happened to me last week. If you are able to load the drivers in manually, then you should be able to use the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot

b63 said:
maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
and check "adb_usb.ini" in the ".android" folder in your personal folder
it should include 0x1949 - i use to add 0x18d1 also in a new line
Click to expand...
Click to collapse
I have followed those steps in the link before and did it again but no difference. I don't have the adb_usb.ini file or the .android folder. only "Kindle ADB" and "kfu" folders both on the root of the c drive.
vwpower44 said:
Sound like your Fire is in Fastboot. This happened to me last week. If you are able to load the drivers in manually, then you should be able to use the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot
Click to expand...
Click to collapse
load the drivers manually and it acts like everything is good but adb still won't recognize the kindle under adb devices

zachjen said:
I have followed those steps in the link before and did it again but no difference. I don't have the adb_usb.ini file or the .android folder. only "Kindle ADB" and "kfu" folders both on the root of the c drive.
Click to expand...
Click to collapse
without the .android folder in your personal folder and the correct adb_usb.ini adb will never work !
create the .android folder and copy the file from c:\kfu\drivers\kindle to the .android folder

Thank you a million times! All is well again.
I had that folder and usb file before when it couldn't be recognized and forgot to put them back I guess.

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

b63 said:
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Click to expand...
Click to collapse
I can't get this to work.
I've been trying to root/install jb on my kindle fire hd I bought today. I downlaoded the android sdk, installed the proper pacakges. Ran cmd and did "adb devices" no devices found. Enabled ADB on kindle fire, no devices found still. I've now downloaded the kfu and copied the file over just like you said (as well as installed the driver) and still to no avail.
I'm running Win7 64bit.
Any ideas?!?

You might be able to root the hd but the 1st gen. methods will not work and you will not be installing jelly bean at this point it`s not even possible. The hd forum can be found here http://forum.xda-developers.com/forumdisplay.php?f=1782

Kindle Fire 6.3 Brick

I flashed the 6.3 update from TWRP and after reboot it gets stuck on kindle fire logo. I have tried Kindle Fire Unbrick Utility with no success. Whenever I choose an option on there, it says waiting for device. When I plug my kindle fire into my computer it makes the connecting noise. In kindle fire utility it shows that adb is online, but the boot status is shown as unknown. When i try to have it reboot into normal mode from kindle fire utility, I get exec '/system/bin/sh; failed : no such file or directory. Then the kindle fire resets itself and im back at square one.

I've uploaded a screenshot of what I get when I use kfu and try to get into fastboot

u were supposed to wipe data after flashing but before rebooting. what rom were you on before you flashed it? usbboot or factory cable.
Sent from my HTC Glacier using xda premium

I was rooted stock. Do you think I should order a factory cable?

yes. unless your comfortable removing the back cover.
Sent from my Kindle Fire using xda premium

If you type "adb devices do you see your kindle?
sent from my ever evolving kindle fire

when i type adb devices under command prompt I get that it's not a recognized command. I think that's because I never downloaded and installed the Android SDK. I've always just used kfu to root and install recovery.

chris_m128 said:
when i type adb devices under command prompt I get that it's not a recognized command. I think that's because I never downloaded and installed the Android SDK. I've always just used kfu to root and install recovery.
Click to expand...
Click to collapse
Personally I don't think it will show up in adb devices.but you don't need android sdk for adb.if you downloaded kfu then you have it.first look in kfu folder till you find adb.exe. then use the cd command and move into the folder with adb.then you can do adb devices.good luck bro.I've bricked 2 kindle fires and I still don't have enough money for a third.
Sent from my Droid using XDA

chris_m128 said:
when i type adb devices under command prompt I get that it's not a recognized command. I think that's because I never downloaded and installed the Android SDK. I've always just used kfu to root and install recovery.
Click to expand...
Click to collapse
like he said, but u can also navigate to the folder and do shift+control+right click and open cmd prompt. from there do adb devices
Sent from my Kindle Fire using xda premium

thank you!

when i type in adb devices after following your instructions I get a bunch of numbers, then they are followed by "device" I can post a screenshot if it will help

You said your computer makes a noise when u plug it in.. its not bricked. What does it show in device manager.
Sent from my Kindle Fire using Tapatalk

it shows android phone

chris_m128 said:
it shows android phone
Click to expand...
Click to collapse
Delete those drivers and run the driver pack from kfu. Then manually select the driver device manager. You have to choose adbcomposite device
You are not to bricked you only have the wrong driver
Sent from my ADR6425LVW using XDA

that's what's keeping my device from booting up?

chris_m128 said:
that's what's keeping my device from booting up?
Click to expand...
Click to collapse
No it is what is preventing you from fixing it
Sent from my ADR6425LVW using XDA

they are all wrong.
when u do adb devices and it shows numbers your golden.
do it again
then do
adb idme bootmode 4000
adb reboot
Sent from my HTC Glacier using xda premium

smirkis said:
they are all wrong.
when u do adb devices and it shows numbers your golden.
do it again
then do
adb idme bootmode 4000
adb reboot
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Well, I don't want to argue. I just know that for the 2 kindles that had the same problem as the OP, any adb command I sent just sat "waiting for device" It was not until I got the right driver (adb composite) that it started taking adb commands again.
if he can push a 4000 reboot without the driver, great. But if he is getting "waiting for device", as he stated in OP, then my suggestion is to get the right driver installed in there.
most soft bricks happen when the fire gets stuck in fastboot mode and loses connection via driver issues and fails to take adb commands.

chris_m128 said:
when i type in adb devices after following your instructions I get a bunch of numbers, then they are followed by "device" I can post a screenshot if it will help
Click to expand...
Click to collapse
but, this.
so, I don't wanna argue either. fastboot is one thing, but adb is another.
his waiting for devices in the op is from kfu, and if you know how it works, it chains a fastboot command and pings it at waiting for devices awaiting reboot. his adb works fine.
Sent from my Kindle Fire using xda premium

Sorry for hijacking your thread bro but im having the same problem. ADB is online but boot status is unknown. On top of that, its stuck at the kindle logo. Any help?

[Q] TWRP Doesnt show my backed up to restore!

TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?

DSH said:
TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?
Click to expand...
Click to collapse
i have figuerd out what must i do!
now i have ADB and ADB doesnt find my device to push the rom on it!
plz plz plz help me
i had Drivers installed but when in fastboot connected to pc windows cannt find JEM-Prod... (something like this)
i neeed your help im so confused

Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thanks for your help but adb doesnt recognize my kindle fire! when in CMD i type "ADB Devices" no devices showd up and when "ADB usb" error shows
i think this is the cuase why your tip doesnt work for me (
ive tried this but step 3 give an error
Had been searching on & off over 2 months & finally found the sol
This now lets you use the KFU util and others to root & install new OS etc
You need to have installed ANDROID SDK and extras-usb & JAVA se
1)
you will need to modify the following two files:
a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder
In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android
Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.
0×1949
2)
android_winusb.inf – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
d. type adb kill-server followed by enter
e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)
0000666665555 device
Click to expand...
Click to collapse

Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thank you very much, but how must i install that?
in device manager i select update driver and locate this folder and it says windows was unable to install you kindle fire HD
i put my kf in recovery mod and plug in the cable!
why have i these problems ?
but again i wanna say thank you bro:good:

So in the task manager is showing a device with an exclamation mark over it right? If so right click the device and hit properties, then goto the details tab, and choose hardware id's from the drop down menu and post them here, I'll see about modifying the driver if I can. Don't know why mine wouldn't work I had the old and new vendor id's for twrp in that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

When i connect to pc in fastboot, in device manager shows as Other devices "Jem-PVT-Prod-04" and the Hardware Ids is:
USB\VID_1949&PID_0008&REV0100
USB\VID_1949&PID_0008
and when just plug the usb cable in recovery mod task manager show it as Portable Device and "Amazon Kindle Fire HD" with a yellow mark! and the hardware Ids is:
USB\VID_1949&PID_0008&REV_0216
USB\VID_1949&PID_0008
thank you bro

ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,

stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
OMG OMG OMG you saved me and my KINDLE FIRE
i have best wishes for you bro best wishes :good::good::good::good::good::good:

Help!?!?!?
stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
i flashed recovery.img to my kindle using flashify and than i rebooted it than it came up saying kindle fire than the red screen slides across the screen. the app says that you may see a red screen.so im stuck now.

You probably just need to reflash the recovery partition from fastboot.

[Q] Kindle Fire; used Kindle Fire Utility v0.9.9, Browser & Terminal don't have root.

[Q] Kindle Fire; used Kindle Fire Utility v0.9.9, Browser & Terminal don't have root.
I've got a kindle fire that I rooted and installed android using the Kindle Fire Utility v0.9.9 (http://forum.xda-developers.com/showthread.php?t=1399889), and SuperSU is supposedly running correctly, but when I run root browser (by JRummy Apps Inc.), it cannot look into the /data/ folder, and trying to "su" on a terminal emulator gives an error. Any suggestions as to what might have gone wrong and/or how to fix it?
Thank you
Meriru

meriru said:
I've got a kindle fire that I rooted and installed android using the Kindle Fire Utility v0.9.9 (http://forum.xda-developers.com/showthread.php?t=1399889), and SuperSU is supposedly running correctly, but when I run root browser (by JRummy Apps Inc.), it cannot look into the /data/ folder, and trying to "su" on a terminal emulator gives an error. Any suggestions as to what might have gone wrong and/or how to fix it?
Thank you
Meriru
Click to expand...
Click to collapse
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]

How to unbrick kindle fire hdx 7?

Today I was thinking: "It would be great to install cm12.1 on mine KFHDX7"
So i downgraded my tablet, rooted it with tovelroot and than I found, what i need a twrp. So i tried this:
1. Root your Kindle Fire using SuperOneClick and make sure adb is enabled.
2. Download the latest version of FireFireFire, a custom recovery tool for the Kindle Fire.
3. Unzip the utility and copy the u-boot.bin file to the directory where you have adb installed. For instance, c:\androidsdk\
4. Download the twrp-blaze.2.0.0RC0.img, which is the version of TWRP 2.0 for the Kindle Fire.
5. Copy that file to the same directory (such as :\androidsdk\)
6. Open a command prompt by opening the Start Menu and typing “cmd” and pressing enter.
7. Navigate to c:\androidsdk\ or whatever directory you’ve placed your files in by entering “cd c:\androidsdk\” or the appropriate directory.
8a. Make sure your tablet is connected to your computer with a USB cable.
8b. Optional: type “adb devices” to make sure your Kindle Fire is connected and adb is functioning properly. If this works, you should see a listing for your device.
9. Copy the two files to your Kindle SD card by entering the following commands and pressing enter after each:
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
10. Open an ADB shell and then install the bootloader and recovery by entering the following commands one at a time. Note that if you get a message saying “permission denied,” it means that your tablet hasn’t been rooted properly. Try running SuperOneClick again.
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
11. Reboot your device with the following commands.
exit
adb reboot
I wasn't mentioned, what this tutorial is for Fire HD and I bricked my device.
What should I do?

Capitan_Veshdoki said:
Today I was thinking: "It would be great to install cm12.1 on mine KFHDX7"
So i downgraded my tablet, rooted it with tovelroot and than I found, what i need a twrp. So i tried this:
1. Root your Kindle Fire using SuperOneClick and make sure adb is enabled.
2. Download the latest version of FireFireFire, a custom recovery tool for the Kindle Fire.
3. Unzip the utility and copy the u-boot.bin file to the directory where you have adb installed. For instance, c:\androidsdk\
4. Download the twrp-blaze.2.0.0RC0.img, which is the version of TWRP 2.0 for the Kindle Fire.
5. Copy that file to the same directory (such as :\androidsdk\)
6. Open a command prompt by opening the Start Menu and typing â??cmdâ? and pressing enter.
7. Navigate to c:\androidsdk\ or whatever directory youâ??ve placed your files in by entering â??cd c:\androidsdk\â? or the appropriate directory.
8a. Make sure your tablet is connected to your computer with a USB cable.
8b. Optional: type â??adb devicesâ? to make sure your Kindle Fire is connected and adb is functioning properly. If this works, you should see a listing for your device.
9. Copy the two files to your Kindle SD card by entering the following commands and pressing enter after each:
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
10. Open an ADB shell and then install the bootloader and recovery by entering the following commands one at a time. Note that if you get a message saying â??permission denied,â? it means that your tablet hasnâ??t been rooted properly. Try running SuperOneClick again.
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
11. Reboot your device with the following commands.
exit
adb reboot
I wasn't mentioned, what this tutorial is for Fire HD and I bricked my device.
What should I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/kindle-fire-hdx
Sent from my KFFOWI using XDA Labs