Develop Bugs

Possibly bricked Kindle Fire....help needed, and appreciated!

A few of you know me already from my thread where I asked a million questions before attempting to install a custom ROM on my new KF. Well, it still went completely south somehow, so here I am.
So, I'm stuck with the stock Kindle Fire logo on the screen, and and can't get it to go anywhere.
Here's what I did:
Downloaded KFU, installed the drivers, plugged in the Kindle,and ran KFU. ADB status online, boot status 4000.....so everything seemed good, from what I've learned. Also looked in Device manager, and it showed up as Android phone, or whatever it's supposed to say. I figure I'm good to go.
My plan is to install TWRP,FFF, and root it, then boot into TWRP, and flash the ROM. The first thing I did(and it seems wrong now) was try to install FFF, instead of TWRP. I think that's the wrong order, but not totally sure if it matters, but it's my assumption that it does.
So, as soon as I sent the command, for some reason, my computer got this blue screen with some message that I didn't have time to read, because it restarted right after. It still said everything looked good, so I tried again to install FFF. I think the "crash" was just coincidental, because it didn't act like that the second time, but whatever.
Anyway.......said it was installing FFF, and then it went to <waiting for device>
I figured ...ok...need to wait.
After about 10 minutes of waiting, I held the power button down until it turned off, then turned it back on, because someone said that's what you should do if this happens. Well, essentially.....since then, I've not seen anything but the Kindle Fire logo on the screen, and it feels like I've tried everything. A forum member spent some time on the phone with me, and we tried everything he knew.....no luck.
At one point, someone told me to uninstall the drivers and reinstall them, which I did, but upon reinstalling them, nothing changed, and the computer no longer even recognizes it being plugged in as a USB device, the drivers don't show now in device manager, even though I told KFU to reinstall them. To me that's weird, and seems like a major problem, because the computer isn't "seeing" the device, but that's mu humble opinion. I'm at a total loss, and would sure appreciate some help bringing this thing back.
Thanks....immensely, in advance!

Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
If nothing you do results in any change, it's time to give up on Windows and create a Linux LiveUSB. Linux is extremely stable and pretty easy to set up and send adb/fastboot commands with. If you do decide to take that route, Ubuntu is pretty much the standard and version10.4 generally works better than later versions.

soupmagnet said:
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
Click to expand...
Click to collapse
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.

soulweeper51 said:
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
Click to expand...
Click to collapse
Use the KFU on the laptop to install the drivers and see if that makes a difference.

soupmagnet said:
Use the KFU on the laptop to install the drivers and see if that makes a difference.
Click to expand...
Click to collapse
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?

soulweeper51 said:
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
Click to expand...
Click to collapse
Yeah, that's what I meant.

Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.

kinfauns said:
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
Click to expand...
Click to collapse
I just did exactly what you said......plugged it in, turned it off. Turned volume all the way up, turned it on....no sound of any kind.
The weird part is when I first installed the drivers, I checked it by plugging the device in, and had adb status online, staus 4000, plus I went to the device manager, and I remember two things that said android phone. One said android phone, and the other said android something or other. And, it was seeing the device and everything seemed hunky dory, and I guess at that time it was???
I did uninstall and reinstall the drivers via KFU, and it says it's installing them, but never again have I seen anything in device manger that says Android anything. That is just wrong to me.

Personally I think you're spinning your wheels with Windows and causing yourself more headache than needed.
Create a bootable Linux LiveUSB on a thumb drive with Ubuntu 10.4 and get Android-SDK installed on it.
[Edit:]fixed spell check fail

I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.

kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first.
Click to expand...
Click to collapse
Trust me.....I realized not too long after that I had done the wrong order. I even had a note to myself right here that said:
TWRP
FFF
Root
For the life of me, I don't know why I did FFF first.
All the questions I asked, and as anal retentive as I am, I totally screwed that part up, which may be the entire problem. Trust me.......I'm pissed.

You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.

kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
Click to expand...
Click to collapse
Can I ask what Firekit is?

Firekit is a tool used to fix major problems easily. I would use it as a last resort because there isn't a command for just installing TWRP without the bootloader.. Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.

soupmagnet said:
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
Click to expand...
Click to collapse
I'll just be honest and tell you that I have no idea what you're talking about. I don't mean that in a bad way.......I'm not some computer whiz that speaks the same language as a lot of you. Right now I wish I had left the freakin thing alone with Go Launcher Ex and called it a day. I'm really pissed off right now....that's not your fault.
I don't suppose that Factory Cable will do anything for this situation, correct? The guy said he will send it ASAP FWIW.
Had to ask.

soupmagnet said:
Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
Click to expand...
Click to collapse
Can you kindly tell me how I get to the point you're speaking of?
Sorry....this stuff is foreign language to me.
Do I have to install ubuntu on my computer?

Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.

soupmagnet said:
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
Click to expand...
Click to collapse
Should I trust this method?
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
I know NOTHING about this.
EDIT: Never mind.......that's another OS......damnit!
Can't I just play dumb, and send it back? I hate to say that, but.....

I guess this is it
http://www.linuxliveusb.com/en/download
^See.......trying as hard as I can to keep a good attitude.

That will work. Download Ubuntu 10.4

Brick?

So guys I feel so very stupid right now because I completely did this to myself and I realized what I did after the fact and now I am stuck with a KF that is booting up and then crashing and rebooting after about 20-30 seconds.... I decided that I wanted to have a stock ROM on the fire backup up if for some reason I wanted to go back to that UI. I made a nandroid and then flashed the 6.3.1.zip file that i downloaded from amazon's website. Have you spotted the mistake already? that's right, i forgot to wipe the cache and system and now I have a broken KF.... does anyone know what I can do to recover from this horrific boot loop? perhaps a hard reset of some sort that will erase everything so I can start from scratch? or at least have a stock fire?? thanks in advance for any help, such a n00b mistake....
If you think it helps, I CAN access the "SD" memory but I haven't had success with ADB

If you can reach the sdcard then you should have adb..... AFTER reinstalling the drivers.. try that..

fiddlefaddle said:
If you can reach the sdcard then you should have adb..... AFTER reinstalling the drivers.. try that..
Click to expand...
Click to collapse
Disconnect KF, shut it off, reinstall driver and finally connect the KF to the computer.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2

fiddlefaddle said:
If you can reach the sdcard then you should have adb..... AFTER reinstalling the drivers.. try that..
Click to expand...
Click to collapse
Two odd things: I rooted the kindle using this computer, so you would think that the drivers would be fine but for some reason it is not working. I ran the install_drivers.bat from KFU and it installs fine but then if i go back to device manager it says that these drivers "WPD FileSystem Volume Driver" is installed and when I try to install the adb drivers it says that the best driver for the device is already installed which is the WPD FileSystem Volume Driver and if I try to uninstall the drivers, it seems like it doesn't do anything at all. I will uninstall the drivers, disconnect and then reconnect the kindle and then it shows up with the same drivers again! any suggestions? I would really like to be able to use my kindle again...

nschiwy said:
Two odd things: I rooted the kindle using this computer, so you would think that the drivers would be fine but for some reason it is not working. I ran the install_drivers.bat from KFU and it installs fine but then if i go back to device manager it says that these drivers "WPD FileSystem Volume Driver" is installed and when I try to install the adb drivers it says that the best driver for the device is already installed which is the WPD FileSystem Volume Driver and if I try to uninstall the drivers, it seems like it doesn't do anything at all. I will uninstall the drivers, disconnect and then reconnect the kindle and then it shows up with the same drivers again! any suggestions? I would really like to be able to use my kindle again...
Click to expand...
Click to collapse
Uninstall the drivers from device manager first, then run install_drivers.bat
sent from my Nokia 5110

Thought I saw someone else with this problem a bit ago. Found this link. Maybe it will help a bit.
http://forum.soft32.com/windows/Microsoft-WPD-FileSystem-Volume-Driver-bootup-ftopict347023.html

pbailey212 said:
Uninstall the drivers from device manager first, then run install_drivers.bat
Click to expand...
Click to collapse
It's very strange, the install_drivers.bat seems to be installing drivers for a device that it is not associating with my kindle so every time I try to uninstall, it just comes back. It's really strange too because ALL of my computers are doing this... would I be better off if i tried from a linux machine rather than windows? from what I've gathered this default driver is a windows/microsoft substitute for mass storage that it doesn't know what else to do with. Is it possible that even though android is clearly running (even though it is only for a little while) that it is unable to communicate with the computer at all?

this is mostly a bump, not sure if it will work but I still haven't had any luck. I was grounded on my XP machine when it wouldn't install the drivers because they were unsigned... saw a tutorial on how to fix that but it was very confusing and unclear. But if anyone has had this problem or has ANY suggestions I am all ears. The kindle was a christmas gift from my parents and I really wish I had just left it alone now. ("if it ain't broke, don't fix it")

It is really much harder on xp to sort out the driver issue acesss to a machine running at least windows 7 would help you out alot. Otherwise go through the process of downloading the Java development kit and using sdk manager to acquire the platform tools for android 2.3 make sure you grab the Google driver this one is signed .

I have no problem putting the jdk and sdk on my personal computers but the xp machine is my mom's so I'm not going to put those on. I thought there would be no problem if i could have used the install_drivers.bat but that turned out to be a bust. Besides that, I wasn't able to find the kindle in the device manager...

nschiwy said:
I have no problem putting the jdk and sdk on my personal computers but the xp machine is my mom's so I'm not going to put those on. I thought there would be no problem if i could have used the install_drivers.bat but that turned out to be a bust. Besides that, I wasn't able to find the kindle in the device manager...
Click to expand...
Click to collapse
Your last sentence tells me that you might not be sure what you are looking for in the device manager.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

kinfauns said:
Your last sentence tells me that you might not be sure what you are looking for in the device manager.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
I really appreciate your help. I've actually been trying to use your guide to see if there was anything I missed. Unfortunately I've not had very much luck. Honestly I've gotten to the point that I would be willing to pay someone if they were confident that they could fix it and I would even pay the shipping both ways. I just want to try to use a linux box to fix it and if I am still unable to communicate with the device through ADB I would be willing to employ anyone from these forums with enough knowledge that they are confident that they could fix it to do it for me. As long as the price was reasonable, of course, keeping in mind that I could buy a refurbished one from amazon for $160 so paying 70-100 would be outlandish... I bought a new HDD for my pc so I could boot linux (I hate dual boots) and after that comes and I still have no luck I will be seeing if anyone would be interested. It's probably a great learning opportunity as well and would be a great addition to the forums if we know what to do when something like this happens.
What OS were you basing this guide from out of curiosity?

http://forum.xda-developers.com/showthread.php?p=26491884

soupmagnet said:
http://forum.xda-developers.com/showthread.php?p=26491884
Click to expand...
Click to collapse
Thank you so much, this will certainly come in handy! I've actually used Ubuntu 11.04 before and I really liked it aside from a few bugs that I didn't feel like dealing with that eventually led me to switch back to windows. So, hopefully this will be the end all in terms of android/kindle fire issues.

okay so, I finally got a hard drive today for my laptop. Booted up Ubuntu 12.04 and used andadb.sh to install all of the necessary software. However, I am not able to connect to my kindle through adb, even on linux. Is there something I may have done wrong somehow? I used the adb_usb.ini from KFU, I don't know for sure that was correct but soup didn't put a link up on his guide so I made an educated guess. I am amazed that nobody has had this problem before, it seems like a very easy mistake to make, at least it was for me! as always, any suggestions will be greatly appreciated!

Try sudo fastboot devices

I'm sorry is this a command? I'm not very familiar with linux you might need to hold my hand on this one. and I tried to adb devices and nothing was listed, will using sudo fastboot devices make a difference? again, sorry for the ignorance, I will try it, I am just addressing concerns.

What bootloader are you using just give me a refresh of your situation so I don't have to read I'm at work but I can still help ya.

okay so basically I don't have a bootloader or recovery because I was planning on rerooting after reinstalling the stock amazon android, only problem is that I forgot to wipe before installing the OS and now I have a Frankenstein amazon gingerbread which is competing with the ICS i had previously installed on the device and continues to crash after about 20 seconds being on and reboots. I am able to access the sd memory, even when it is rebooting but I haven't had any successful connection using adb. If I had, I would imagine I could just reflash twrp and fff and I would then wipe and install a ROM and be good to go but as of now I just have a constantly bootcycling KF that for some reason has no precedent for repairing.

Shutdown and reboot the phone

[Q] Beyond frustrated, would like to hire some help

I'm not a stupid person, but I am a slightly distracted widowed father of a three-year-old, and I've become so frustrated that I can't think straight!
I'm not a developer, but I've always easily rooted my devices by following the instructions. Until the Kindle came along.
I had all kind of trouble, wrong drivers, general mistakes, etc. Finally, everything appeared to be working, and then I had a hard drive crash during the root process. TWRP was installed, but, apparently, nothing else.
Took it to a second computer, downloaded KFU, installed drivers, ran. Partial success. TWRP appeared to be running smoothly. Downloaded ROM (Don't even remember which, Kindle has been thrown in drawer for weeks!) ROM appeared to install, but wouldn't boot. Here's where I got extra-stupid:
Obviously, something is already wrong with my Kindle, but at least I can see it in device manager. At least I can access it through KFU. For some insane reason, I began trying everything I could think to do, and eventually got TWRP into a recovery bootloop. Yay, me!
Now, I've screwed around on multiple computers, in Windows and Ubuntu. I'm completely confused as to which drivers are loaded where, Kindle shows up in Device Manager as a phone, but does not show up as a drive in Windows Explorer, and KFU, while it runs just fine, alternates between between telling me that it's "waiting for device," or "the system cannot find the drive specified."
Help on the Forums has been wonderful, but I am beyond that. My last post was answered with "Which drivers have you installed?" Well, crap! I don't know. I probably knew a month ago when the problem started, but I can't think rationally (where the Kindle is concerned, I seem to do OK in real life) anymore!
Now, I know that I've got so much crap going on, that most of you don't want to trash up the forum by trying to address my multiple issues. Please do not post "Have you tried the search tool?" Re-read my far too long post. I don't even know what the crap to search for anymore!
So, finally, here's my question? Anybody want to try their hand at fixing my F-'d up Kindle? It's not doing me a bit of good as is so, even if I mail it to someone and they just keep it I haven't really lost much!
All I want is a nice, stable (STABLE!) Gingerbread or ICS ROM that my little boy can watch Netflix on. I'll gladly pay anyone a reasonable amount to anyone willing to take this problem off my hands...

If you have TWRP installed can you mount the USB drive in it and then flash what you want?

When I mount usb storage in twrp, it does allow me to access the device on the computer, which is much better than I was getting. When I run KFU it still stated that it cannot find the device. If I run Kindle Unbrick, it open the command line, then just hangs up.

RobWoodall said:
When I mount usb storage in twrp, it does allow me to access the device on the computer, which is much better than I was getting. When I run KFU it still stated that it cannot find the device. If I run Kindle Unbrick, it open the command line, then just hangs up.
Click to expand...
Click to collapse
No need to run KFU... Just copy FFF to the Kindle and flash from TWRP. Then copy what rom you want and Flash from TWRP.

And, make sure you flash the FFF version (1.4a) in this thread:
http://forum.xda-developers.com/showthread.php?t=1632375
Your download should be named: fff-u-boot_v1.4a.zip.
You will see some notes in that thread about NOT flashing this file, but those are for an older zip. This is a flashable .zip ... I just installed (flashed) it last week from TWRP.
(P.S.) Your KF is not in as bad of shape as you might think. This is a quick fix with the right setup.

I had a similar problem. First you should download Kindle Fire Drivers(the one that came with KFU didn't work...) and install it. Then in TWRP mount the SD card. Update the drivers using that Kindle Fire Driver folder(I will upload it and give you the link). Then with KFU press 1(bootmode) and then 1 again(normal). I think this should get you out of bootloop. If that doesn't work, just flash the Kindle Fire Stock Rom.
Sent from my Kindle Fire using xda premium

When I said install Kindle Fire Drivers I meant download. Then manually install the drivers(My Computer, right click,
properties, hardware, and open up device manager. If you get android device or something, click on it. If you see Kindle with a ! then click on update drivers and select the kindle fire driver folder. If you don't see kindle, or if you see Android device, then uninstall. Then go to disk drives and find your kindle fire and uninstall. Close and re-open, and you should see Kindle! Then update the drivers. Open up KFU and change bootmode to normal. Do a 20 sec. hard reset and see if it boots. If your trying to install a Custom ROM(ICS or honeycomb) put the .zip file on you kindle fire. Then open up TWRP and choose Wipe, and Factory Reset. Then wipe Cache and Dalvik Cache. Then go to install and select the ROM. After install the boot may take awhile. You said you tried this but you got stuck in bootmode, so make sure you follow these instructions. Make a backup if you ever want to go back. Move the backup to your computer as it takes up almost 1.5gb of space. Please inform me if this doesn't help. Sorry if I'm not good at giving instructions,but I'm only 14.
Sent from my Kindle Fire using xda premium
Here is the Link for the folder. Just unzip and update your Kindle Fire with it: http://www.mediafire.com/download.php?lnx766ac84o7q1i

RobWoodall - hang in there, because a lot of us were exactly in your shoes. For the life of me I can't get most of the ubuntu stuff to work, and windows was a bit of a nightmare for drivers until sorted out. I bootlooped, thought I bricked, etc etc but all sorted out in the end.
The fact you can see it in device manager is good. What you need to do is to replace the drivers with the 'Android Composite ADB Interface' - this video may help you out
I'm sure folks here will try to help you out without taking your money

Thanks, but I don't seem to be able to find a current version of FFF. Probably because I'm not thinking clearly.

tedr108,
Thanks, but the link appears to be unavailable at this time. I'm not hopeful, as I have been quite able to install ROMs. For all I know they are running perfectly. My most immediate problem seems to be that I'm trapped in a bootloop, and no matter what I do, the Kindle always boots into TWRP. Apparently I'm in boot mode 5001, and I should be in mode 4000 or some such. KFU should be able to change the boot mode, but it only gives me "waiting for device."

RobWoodall said:
Thanks, but I don't seem to be able to find a current version of FFF. Probably because I'm not thinking clearly.
Click to expand...
Click to collapse
Here is the latest copy of FFF 1.4A that I have.

Dropbox link (while Rombot is down):
https://dl.dropbox.com/u/41149741/KFire-Android/fff-u-boot_v1.4a.zip
md5sum: 419c53b922c963082454b14b7de75a90
Edit: Tera Tike is on the ball! (Thanks I almost never ready this forum)

josepho1997,
Thanks. Downloaded and installed perfectly. Unfortunately, the Kindle will still only boot into TWRP recovery. Apparently I'm in boot mode 5001, and should be in 4000 or 4001 or something. It's really getting frustrating!

Use sudo command in ubuntu power it off type sudo fastboot getvar product plug your kindle in it should return kindle as a response your kindle then your kindle will be in fastboot then type sudo fastboot oem idme bootmode 4000 hit enter then type sudo fastboot reboot it should boot in normal mode

Nevermind, someone beat me to it...

RobWoodall said:
josepho1997,
Thanks. Downloaded and installed perfectly. Unfortunately, the Kindle will still only boot into TWRP recovery. Apparently I'm in boot mode 5001, and should be in 4000 or 4001 or something. It's really getting frustrating!
Click to expand...
Click to collapse
It seems that your system is bad.

Tera Tike,
Thanks! I think I love you! Worked perfectly. I'm now running CM7 Barebones, because that's the last ROM I had tried to flash. Now that I understand the process, I'll certainly experiment with other ROMs, but Bare Bones looks pretty darn good after staring at the TWRP menu for a month and a half!
P.S. Nope! My system wasn't bad, the operator was!!! LOL!

Thanks, Hashcode! I got the file from Tara Tike. Fantastic work! That simple option to reset bootmenu on the first page was all I needed all this time!

RobWoodall said:
Tera Tike,
Thanks! I think I love you! Worked perfectly. I'm now running CM7 Barebones, because that's the last ROM I had tried to flash. Now that I understand the process, I'll certainly experiment with other ROMs, but Bare Bones looks pretty darn good after staring at the TWRP menu for a month and a half!
P.S. Nope! My system wasn't bad, the operator was!!! LOL!
Click to expand...
Click to collapse
Great!!! Hashcode FFF is the best!! Now enjoy your hard work!
Thanks, Hashcode for all you have done for us Fire users!!

I really appreciate everyone's help! I've been sharing the nook with my three-year-old. He's a pretty smart kid but, once he learned how to change icons and wallpaper, install and uninstall apps, it's a completely different experience every time I turned it on. I bought the Kindle so I could have MY OWN tablet!
If anyone is still reading this thread, please give me some recommendations for ROMs. I typically only use Google Play Books, Contacts and Calendar, Aldiko Reader and Netflix. I'm not in the market for fastest or fanciest, but most stable. I don't care if it's Gingerbread or ICS (Heck, even Honeycomb if it's stopped sucking!) So what do you all say?
What's the most stable ROM out there for a person who needs Google compatibility on the Kindle Fire?

[Q] Bricked ... tried most things ... need some guidance

Hi,
Some background - I've been tinkering with android roms on phones for a while, and thought i'd give it a go on my Kindle, which I hardly ever use with the stock rom. I have a very low level of understanding regarding rooting, etc., but generally I'm good at following instructions (until now!)
So everything was going along nicely. Because I hardly ever use the device, I decided to do a full wipe before installing the new rom. Then, when I went to flash it, it turns out that I had forgotten to copy the new rom onto the SD card. In a moment of temporary insanity, I turned the device off (don't ask me why, I can't explain it).
On restart, the device now gets stuck on the logo screen. KFU tells me that the device is online, but boot status is unkown, and it can't change the status (although it does reboot the device when I try to put it into fast boot mode- but it doesn't actually 'fastboot').
If I try to reinstall TWRP or anything else, I get the 'exec system\bin\sh failed' error. The Kindle unbrick utility is unable to help.
I did some research and it kept pointing me to a factory cable, which I duly bought off eBay. When I use the factory cable, the only difference is that the boot sequence is slightly different (different levels of backlight) and KFU can't recognise the device at all - it says its offline.
I have no idea if the factory cable I have bought is any good - it might be complete rubbish.
Can any tell me if there is a simple option I have missed? Is trying fixes through Linux the only option? Will I have to open my kindle to fix it? I've already spent a heap of time on it, and I'm just about ready to call it a paperweight. Any help would be greatly appreciated.

I`m a little confused so file me in. Do you have access to recovery? with your type of error "exec system\bin\sh failed" a factory cable is indeed needed to reinstall twrp and the bootloader, unless you can access TWRP and mount your sdcard and transfer a rom. If that is not possible then you have some kind of mounting issue. So I still wonder what happened to your recovery and your bootloader? For me yet not everything is meshing to well. No bootloader, no acces to recovery, kindle just boots to logo and no further. Does the logo flicker and brighten and dim at boot? Yes very likely you will need to run linux on a live usb then run soupkit on it. Still you may still need a real factory cable not one half **s one from ebay you can find that here http://forum.xda-developers.com/showthread.php?t=1392693 from user @SkOrPn no one can beat what he does I`m sorry. As for linux and soupkit the where and how is here http://forum.xda-developers.com/showthread.php?t=1850038 . Unless you get easily confused then try the iso I created with some fairly easy instructions soupkit is ran already simple create boot and use you can find that here http://forum.xda-developers.com/showthread.php?t=1413358 post # 7 make no mistake that this is only for the kindle like the last person I helped with this setup. This is your best route to get your kindle fixed sounds like it could still be a combined effort cable and soupkit .You will know when you hook your kindle up and run some of the features in soupkit if your device is truly online or if a cable is needed. If you run my iso teamviewer is also installed so it provides a nice edition for assistance if you want someone to see what you see. If you choose to run soupkit then the par for instructions differ from those of my iso.

Thepooch said:
I`m a little confused so file me in. Do you have access to recovery? with your type of error "exec system\bin\sh failed" a factory cable is indeed needed to reinstall twrp and the bootloader, unless you can access TWRP and mount your sdcard and transfer a rom. If that is not possible then you have some kind of mounting issue. So I still wonder what happened to your recovery and your bootloader? For me yet not everything is meshing to well. No bootloader, no acces to recovery, kindle just boots to logo and no further. Does the logo flicker and brighten and dim at boot? Yes very likely you will need to run linux on a live usb then run soupkit on it. Still you may still need a real factory cable not one half **s one from ebay you can find that here http://forum.xda-developers.com/showthread.php?t=1392693 from user @SkOrPn no one can beat what he does I`m sorry. As for linux and soupkit the where and how is here http://forum.xda-developers.com/showthread.php?t=1850038 . Unless you get easily confused then try the iso I created with some fairly easy instructions soupkit is ran already simple create boot and use you can find that here http://forum.xda-developers.com/showthread.php?t=1413358 post # 7 make no mistake that this is only for the kindle like the last person I helped with this setup. This is your best route to get your kindle fixed sounds like it could still be a combined effort cable and soupkit .You will know when you hook your kindle up and run some of the features in soupkit if your device is truly online or if a cable is needed. If you run my iso teamviewer is also installed so it provides a nice edition for assistance if you want someone to see what you see. If you choose to run soupkit then the par for instructions differ from those of my iso.
Click to expand...
Click to collapse
No, I can't access recovery at all. When I use the factory cable, there is no flicker, but all other ways (standard cable, no cable) there is a flicker and it brightens. Either way, it just hangs on the logo.
I suspect that the factory cable is not all it should be ... I will probably try the @SkOrPn option first, then work my way through the other options you mention. I had kind of figured from reading other posts that this would be the case ...
Thanks for taking the tiime to help.

There is no flicker because your likely in fastboot the lack of recognition is drivers which can easily be solved using linux and soupkit. Otherwise straighten out your drivers in windows by running the driver bat packaged with kfu. If your on XP it`s a fight to the death to try to sort out unsigned drivers on that os. Sometimes I can get it fast other times it`s pointlessbut a huge hassle nonetheless. Attempt to fix your drivers while using the factory cable you have maybe you will get lucky.

Fixed! Thanks so much!
I used your pre-installed ISO and it was a piece of cake. Initially, I had the device connected over the factory cable and it wasn't recognising it, but when I swapped to a standard cable, suddenly I was able to reboot into recovery straight away. Rom mounted and installed, and I have a new tablet!
Definitely appreciate all your hard work!

That`s great I`m happy you had good success!!

[Q] Another Possibly Bricked Kindle Fire 1st Gen.

Okay, so I've searched this entire day, literally like the past 13 hours has been spent searching xda kindle fire forums, and googling the hell out of the internet searching for a fix to a situation like mine but have gotten no where! So, if I have somehow missed another thread that has this figured out I am apologizing now, but like I stated before I have tried and tried searching before deciding to post this. Now, moving on to the issue.
My Kindle Fire is stuck at the boot logo. It seems to be in fastboot mode, (4002), but will not go any further. If it is hooked up to the pc, which I'm running Windows 7 64 it will sound as though it connects, the screen will show the kindle fire logo (orange) really brightly btw, then go black with a disconnect sound on the pc then quickly show the logo again, this time dimmer and the reconnect sound on the pc sounds again.
What I did to cause this. I had a Custom CM7 rom on this (I don't remember which), and had this rooted and customized since last January. I remember that TWRP never would come up right (I don't know which version again) unless I reinstalled TWRP everytime I wanted to install a new rom on it using KFU. This time was no different, except I made a stupid mistake. I was trying to reinstall the stock rom 6.3.1 which I downloaded directly from Amazon, put it in the sdcard directory using TWRP and didn't rename it completely, instead only chaning the end to .zip, and not renaming the whole thing as update.zip (not sure if that makes a dif). Anyway, I did a delvik/cache wipe (not a factory reset) and attempted to run the install of the factory rom. Everything seemed fine until it came to the boot logo, and nothing else.
What I've tried so far. I have tried all of this on two seperate pc's using windows 7 64. I have tried the unbrick utility making sure I had the latest and greatest, making sure I tried every which way it has to unbrick it to no avail. I have tried the KFU, again the latest and greatest trying everything IT has to see if any of it would make a difference to no avail, even chaning the bootmode but no matter which mode I try, the Kindle will reboot but stay stuck regardless of whatever I tried after the reboot. I have tried using command prompts to bring up ADB Shell but again, when I run ADB devices it will show up, and the drivers hardware ID's are correct according to all the forums with the drivers listing the Kindle as an ADB android device but when I try to run a shell command it says that no such directory is found or something of the sort. If it doesn't say that than it will simply state that it is waiting for the device, and I do try to disconnect then reconnect the cable at this time, even rebooting the Kindle but it never moves past "waiting for the device". I have tried shorting it by opening the case and putting something metal to the one point and the metal border but the most that did was turn the device off! When I try to turn it on again it simply stays on the boot logo. I have tried the factory cable, and still nothing works! I have changed the script for the driver to make sure it recognized the Kindle but that didn't work either.
I am at the end of my rope here, and I am begging for someone to simply help me who may know exactly what I am going through that knows what to do! I am sorry for the lenghty post, but I figure certain questions will be asked if not for my detailed accounts of what's happened and what I have done to this point. Thank you to anyone reading this and thanks to anyone who replies, you have my gratitude!

Try Soupkit http://forum.xda-developers.com/showthread.php?t=1850038 it will rule out all the formalities of drivers. My guess is that your shell is missing or broken so that factory cable will come in handy. If you want to do without the whole setup try my iso post 7 http://forum.xda-developers.com/showthread.php?t=1413358 if you desire assistance I would be happy to help.

So friendly!!!
Thepooch said:
Try Soupkit http://forum.xda-developers.com/showthread.php?t=1850038 it will rule out all the formalities of drivers. My guess is that your shell is missing or broken so that factory cable will come in handy. If you want to do without the whole setup try my iso post 7 http://forum.xda-developers.com/showthread.php?t=1413358 if you desire assistance I would be happy to help.
Click to expand...
Click to collapse
Thank you so much for replying so quickly! I have seen you reply to others, and I was actually dreading posting due to some unruly replies I have witnessed to people like me. But you are always helpful and I appreciate that! I'll try setting up ubuntu (I'm assuming that soupkit only works with that, correct?) and I'll read your post and let you know what happens. Thanks again!

mikeydjs said:
Thank you so much for replying so quickly! I have seen you reply to others, and I was actually dreading posting due to some unruly replies I have witnessed to people like me. But you are always helpful and I appreciate that! I'll try setting up ubuntu (I'm assuming that soupkit only works with that, correct?) and I'll read your post and let you know what happens. Thanks again!
Click to expand...
Click to collapse
If you use my iso Soupkit has already been ran just follow my instructions for creating it . If you choose to do the setup on your own use linux mint mate 13 32 bit or precise pangolin ubuntu 12.04 or 12.10 32 bit. 32 bit works on both 32 and 64 bit machines.

Trying Ubuntu 11.10
Thepooch said:
If you use my iso Soupkit has already been ran just follow my instructions for creating it . If you choose to do the setup on your own use linux mint mate 13 32 bit or precise pangolin ubuntu 12.04 or 12.10 32 bit. 32 bit works on both 32 and 64 bit machines.
Click to expand...
Click to collapse
I tried using ubuntu 12.04, but the live usb application wouldn't recognize the .iso I got from pbay. It did see the 11.10 version so I went with that instead. Man! Why did I ever not use Ubuntu before!!! Really nice os. Anyway, with that being said, I downloaded SoupKit while on ubuntu like you instruct in your post, but when I click on install.sh I am seeing that it says Soupkit is already installed. So I don't see the prompt to run in terminal. Do I have to uninstall or delete the current occurrence of soupkit on this ubuntu install? Or do I continue on with the setup.sh file located in the soupkit folder? Also, I plugged my fire in while on ubuntu and I don't see a prompt for it to install any drivers, nor do i know how to located usb connected devices (Too used to Windows I guess, lol). Thanks again for you help, and hopefully I'm not sounding like a total noob!

Yeah sorry 11.10 is funky with soupkit during testing I really had to cheat to get a proper install try going with my prefab iso its far more simple and stable enough. I know the download is large that is because of it's own prepacked casper r/w. Drivers do not install on linux rather it is setup as udev rules that configure for a specific device lets just say it's different to avoid going into to much detail. Yes setup.sh is the next run if it doesnt run in terminal but that's not the proper way to run soupkit stick with the distros I recommend. If it doesn't find the distro in the dropdown try unlisted iso if you can`t find the iso when attaching start to fill the name of the iso in it will begin to auto complete.

Ubuntu 12.10?
Thepooch said:
Yeah sorry 11.10 is funky with soupkit during testing I really had to cheat to get a proper install try going with my prefab iso its far more simple and stable enough. I know the download is large that is because of it's own prepacked casper r/w. Drivers do not install on linux rather it is setup as udev rules that configure for a specific device lets just say it's different to avoid going into to much detail. Yes setup.sh is the next run if it doesnt run in terminal but that's not the proper way to run soupkit stick with the distros I recommend. If it doesn't find the distro in the dropdown try unlisted iso if you can`t find the iso when attaching start to fill the name of the iso in it will begin to auto complete.
Click to expand...
Click to collapse
I'm downloading ubuntu 12.10. Not sure if this will make a difference, but I will try anything at this point! Will this make a difference?

mikeydjs said:
I'm downloading ubuntu 12.10. Not sure if this will make a difference, but I will try anything at this point! Will this make a difference?
Click to expand...
Click to collapse
It will make a difference in how soupkit setup runs if it doesn`t run correctly it causes issues you want it to be as stable as possible. Make sure you drag the slider to add at least 1300 mgs of persistent for saving data between reboots. Once you get this done I can assure you its one of the finest tools to ever grace your kindle Soupmagnet went all out on its creation make sure you stroke his thanks button.

ubuntu 12.10
Thepooch said:
It will make a difference in how soupkit setup runs if it doesn`t run correctly it causes issues you want it to be as stable as possible. Make sure you drag the slider to add at least 1300 mgs of persistent for saving data between reboots. Once you get this done I can assure you its one of the finest tools to ever grace your kindle Soupmagnet went all out on its creation make sure you stroke his thanks button.
Click to expand...
Click to collapse
Ok, so I'm currently running ubuntu 12.10 from the usb stick and I tried double clicking on the install.sh again with the same result! Do I have to install ubuntu in order for it to run properly? I keep getting the message when I open install.sh that soupkit is already installed and that I have no need to install it again. Am I doing something wrong here?

Try my iso post 7 http://forum.xda-developers.com/showthread.php?t=1413358.

mikeydjs said:
Ok, so I'm currently running ubuntu 12.10 from the usb stick and I tried double clicking on the install.sh again with the same result! Do I have to install ubuntu in order for it to run properly? I keep getting the message when I open install.sh that soupkit is already installed and that I have no need to install it again. Am I doing something wrong here?
Click to expand...
Click to collapse
Yeah, I need to fix that...delete your /bin/SoupKit folder and try again.
"That's a special kind of stupid. The kind that makes me laugh."

soupmagnet said:
Yeah, I need to fix that...delete your /bin/SoupKit folder and try again.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Lemme know when your ready for more testing .