Develop Bugs

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] Trouble Sending Fastboot Commands

Hey All!
I had a nice post written up, but XDA decided that it didn't like me and signed me out while I was writing so it's gone now... in any case....
My problem is this: I have set up my linux machine to do adb/fastboot and I'm fairly certain that there's nothing wrong with it on that front. I have no problem with adb, I use shell and then change the bootmode to 4002 and then quickly send a fastboot command to attempt to catch it before it loads FFF. I have FFFv.1.4a which I believe is still the newest version but I want to flash a newer version of TWRP (currently on 2.1.1). I tried using the flashable zip on HashCode's CM11 thread, but it doesn't seem to be making any change (if there's a special way to flash a recovery via recovery I would appreciate any advice) but at this point I'm stuck because I don't remember needing the factory cable to get to the point that I'm at but I don't know of any other way to enable fastboot mode. Is there a way that I can do this without the factory cable? I have one at home, but not with me at school
Thanks in advance,
Sparkplug

In twrp hit reboot then hit boot loader, or use and adb shell or mobile terminal and run "su -c 'reboot bootloader'", those are some of the alternate ways to enter fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
In twrp hit reboot then hit boot loader, or use and adb shell or mobile terminal and run "su -c 'reboot bootloader'", those are some of the alternate ways to enter fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
It appears that even though I'm running MoDaCo, I'm no longer rooted. Very odd.... Perhaps that has something to do with my weird situation. I'll try rooting and report back!

stunts513 said:
In twrp hit reboot then hit boot loader, or use and adb shell or mobile terminal and run "su -c 'reboot bootloader'", those are some of the alternate ways to enter fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I should have been more clear. I have no trouble getting to FFF and having it stay there as though it is waiting for commands, but my computer just continues to say <waiting for device>
Does that mean that I'm doing something wrong or do I just need to use the factory cable and that's the beginning and the end of it?

I'm mainly from the 2nd gen kindles and was a little bored so I ventured into the 1st gen forums... But if you are saying that its going into fastboot mode, but you PC can't issue commands then I would guess it's a driver problem, last I checked my drivers in my signature also work with 1st gen kindles. I thought fastboot had its own screen outside of FFF, but if it doesn't then check your device manager for a device with a triangle next to it, I'm guessing it will say otter, like I said though 1st gen kindles aren't my forte but they are similar in certain aspects.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
I'm mainly from the 2nd gen kindles and was a little bored so I ventured into the 1st gen forums... But if you are saying that its going into fastboot mode, but you PC can't issue commands then I would guess it's a driver problem, last I checked my drivers in my signature also work with 1st gen kindles. I thought fastboot had its own screen outside of FFF, but if it doesn't then check your device manager for a device with a triangle next to it, I'm guessing it will say otter, like I said though 1st gen kindles aren't my forte but they are similar in certain aspects.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I think that it is supposed to have a separate screen but I wound up doing what I forgot existed because I'm so used to doing everything manually; using ROM Installer by JRummy to flash the image after I had rerooted. I appreciate the help either way!

[HELP] Bricked kindle

Hey guys, so my story:
I have a Kindle fire hd 7
I tried to install cyanogenmod on it, i bricked it. When i turn on the kindle, appears the logo and restarting, again and again and again....
I bought fastboot cable, works well, appears the Fastboot text on kindle, when i plug in the usb to laptop.
Downloaded Android SDK, installed the adb driver. U see in the picture, works well.
When i write adb devices, shows nothing device.
And when i write adb kill-server, write nothing.
If i write adb start-server.
Check attachments.
What should i do?

Adb commands don't work with fastboot mode, you need to run fastboot commands. Try "fastboot -i 0x1949 getvar product" and it should report back something if it works. BTW this is the wrong section, I only mention this because I have been seeing a lot of misplaced threads in here lately.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Adb commands don't work with fastboot mode, you need to run fastboot commands. Try "fastboot -i 0x1949 getvar product" and it should report back something if it works. BTW this is the wrong section, I only mention this because I have been seeing a lot of misplaced threads in here lately.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
I attached the pic.

OK good its working fine then, restore the device with kindle fire first aid or srt and it should boot into amazon os. From there you can start the 2nd bootloader procedure again.
Sent from my Amazon Kindle Fire HD using Tapatalk

Thanks for the reply!
I downloaded the first aide. When i choose the Display the fastboot status.
In the next step i see that: the system can not find the path specified

I'm not one to use kffa since I just do all the stuff it does manually so my knowledge of it is fairly limited, but did you follow its instructions, only thing I could guess at is I think the instructions mention setting up its paths. I'm guessing it couldn't find the fastboot binary so it displayed that but I'm not sure.
Sent from my Amazon Kindle Fire HD using Tapatalk

i don't know what to do :/ But i read now, i not follow'd the steps i hope it will be the problem, i not made to desktop the icon, run as administrator, etc etc... if yes, facepalm...

When i start to restore my kindle, just waiting at daemon progress, and nothing happen, i checked the task manager and i see the adb.exe.
Why? why i need to wait more?

That's probably be cause you answered a question wrong, i know that it asks a question when you goto restore it, something like "is it in fastboot mode" or "would you like to put it in fastboot mode", but since it is already in fastboot mode there is no need to tell it to because adb commands don't work with fastboot.
Sent from my Amazon Kindle Fire HD using Tapatalk

i know, but when i try to restore my kindle with first aid, that stops in daemon process and nothing happen.
Check the attached pics.

Kill the adb process then, if the script doesn't check for error codes it should just continue to the flashing process.
Sent from my Amazon Kindle Fire HD using Tapatalk

I did, i got the first message on the 1. pic.
after that i got second picture, and the window closes :/

byAPEX said:
I did, i got the first message on the 1. pic.
after that i got second picture, and the window closes :/
Click to expand...
Click to collapse
well that's just great... try it again, md5sum if you didn't know is basically a way of verifying a files integrity, to make sure it is exactly like the original, if we didn't do these kinda checks and flashed a bad image like for instance the bootloader it would hard brick. Anyways it means it just had a bad download. It could have been a random packet drop, maybe something to do with admin rights, or perhaps the file was down on the site it was hosted on, you will just have to try again and see if you can get it to work. I don't have a copy of kffa handy or i'd check the url it downloads form for you.

Okay thank you

I am unsure how to install launchers read below

I have a second gen kindle fire (rooted) and looked and looked all over and have not seen any way to use custom launchers on my kindle fire. It downloads and installs but does not show up in the carousel or application list. i go into lucky patcher and it cannot open the launcher. Please give reason and or fix

illusion_insanity said:
I have a second gen kindle fire (rooted) and looked and looked all over and have not seen any way to use custom launchers on my kindle fire. It downloads and installs but does not show up in the carousel or application list. i go into lucky patcher and it cannot open the launcher. Please give reason and or fix
Click to expand...
Click to collapse
Try rebooting. It could also be intentional behavior on Amazon's side (they won't let you change the default launcher, and they might prevent you from even opening another one).
Sent from my Amazon Jem using XDA Labs

thanks
i am no a pro at this but i think someone said its because it has a locked bootloader.

illusion_insanity said:
i am no a pro at this but i think someone said its because it has a locked bootloader.
Click to expand...
Click to collapse
The issue isn't caused by a locked bootloader; however, unlocking or replacing the bootloader will allow you to use a custom ROM and sidestep the stock OS's restrictions.

Thanks
monster1612 said:
The issue isn't caused by a locked bootloader; however, unlocking or replacing the bootloader will allow you to use a custom ROM and sidestep the stock OS's restrictions.
Click to expand...
Click to collapse
I guess I can trial and error my way until it works! do you think I should just get cyanogem mod on it if I can't get a launcher?

illusion_insanity said:
I guess I can trial and error my way until it works! do you think I should just get cyanogem mod on it if I can't get a launcher?
Click to expand...
Click to collapse
Yep - it'd be more up to date than Amazon's stock OS, too.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Yep - it'd be more up to date than Amazon's stock OS, too.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
the thing is, I don't have the adb drivers to use kindle fire utility

illusion_insanity said:
the thing is, I don't have the adb drivers to use kindle fire utility
Click to expand...
Click to collapse
What OS are you using on your PC? If you're running Linux (Ubuntu, etc.), no drivers are needed.

windows
monster1612 said:
What OS are you using on your PC? If you're running Linux (Ubuntu, etc.), no drivers are needed.
Click to expand...
Click to collapse
I am using windows seven. but it wants me to have android sdk in the majority of the tutorials I've read

illusion_insanity said:
I am using windows seven. but it wants me to have android sdk in the majority of the tutorials I've read
Click to expand...
Click to collapse
The tutorials recommend you install the Android SDK, but unless you're planning on doing Android app development, most of the SDK will be useless. Instead of using the SDK (which is quite bulky), I'd recommend that you run the 15 second ADB installer, which can be downloaded here. Run the program as administrator, and when you're asked the questions, answer Yes/Y for the "install ADB and fastboot" and "install ADB system wide" questions, and No/N to the "Install device drivers" question. The reason we're not installing the drivers bundled with the installer is because the drivers are for Google devices, which will clearly not work with the Kindle.
Because of this, we're going to install the Kindle drivers separately. Go ahead and download the zip file in this thread, which contains installers for the Kindle drivers. Unzip the folder, run one of the executables as administrator, and install the drivers as prompted. You may get errors about installing unsigned drivers - continue anyway. Once the drivers successfully install, reboot your machine. Once you're rebooted, plug in your kindle (make sure it's booted into either recovery or a ROM). (NOTE: If you're booted into a ROM, you may get a prompt asking if you want to allow USB debugging. If you get this message, check the "Always allow from this computer" checkbox, and then OK.) Open a command prompt window and type adb devices. Below "list of devices attached", you should get a random string back (this is your device's ID) and either "unauthorized", "offline", or "device" next to it. If you don't see any text below "List of devices attached", then check to make sure ADB is enabled on your kindle (which it probably is if you rooted it ).

AWESOME
Have see it tried it yet but I will I gave ed up with sdk I have crap internet so it takes forever to download. I needed this thanks alot