Related
Hi,
My rooted KF started behaving, weirdly so I decided to start from scratch and unroot it using the ClockworkMod recovery utility interface that was automatically loaded when I rooted it using Breakdroid. It started life with 6.2.2 but then updated itself to 6.3, so I downloaded the following file to do the unroot, and converted it into a .zip file called update.zip.
//kindle-fire-updates.s3.amazon...1E_4019920.bin
and went into the ClockworkMod recovery utility mounted my KF, did a factory reset, then applies sdcard update.zip which appeared to perform sucessfully, however when I rebooted, it launched the Stock KF screen, no fire fire fire, and has since stayed there. Can anyone please help! Many thanks.
Does KFU recognize it? If it does you are good to go.
Hi,
Nope. I'm using a Mac, so I use Breakdroid, and it's not picking it up.
http://forum.xda-developers.com/showthread.php?t=1644970
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1644970
Click to expand...
Click to collapse
Keep up the good work soupmagnet!
Thanks soupmagnet,
I know it's the same question asked over and over again, I'll give it a shot and let you know if I sort it out. Appreciate your time.
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
nickvon said:
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
Click to expand...
Click to collapse
Actually a factory cable, while nice to have, doesn't seem necessary in your case. (Hint Read about the different bootmodes.
Hi again Soupmagnet,
So I eventually got hold of my factory cable which I ordered off Ebay from Hong Kong, so I plugged it in and hey presto, nothing happened. I'm still stuck on the Kindle Fire screen. I've been using a Mac and Breakdroid doesn't pick it up at all. I decided to see if a PC could pick it up using KFU, and it's still offline, although in My Computer I do see an external drive and device manager does call it Kindle. I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle. Could it perhaps be the cable not in fact being a factory cable at all? I'm getting pretty desperate with this situation. Can you offer me advise.
Nickvon
Oh and further to my last I was changing boot modes but as it couldn't recognize the device, it was pointless.
nickvon said:
I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle.
Click to expand...
Click to collapse
Take a breath, relax, and rest assured that you are more likely in the upper 90% range.
As I said before, the factory cable, while nice to have isn't usually required to fix most devices. All it does, is puts the device in fastboot mode and provides direct power to the device via usb in case of low or now power
Your problem is simply a matter of fixing your drivers so you can communicate with the device and change the bootmode.
[Edit:] It's been a while since this post was first started so I forgot you were using Mac instead of Windows.
Open your Terminal and enter the following:
Code:
cat ~/.android/adb_usb.ini
Your output should read:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
Anything other than would explain why you aren't able to change the bootmode normally.
Are you using Terminal commands to change the bootmode or are you using Breakdroid?
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?
I initially bricked my kindle with the KFU somehow so the static logo showed, but that was a relatively quick fix. I then got clockworkmod working, and flashed a ROM. Now it will show the standard kindle bootloader for a second, then the screen will flash white, and then I get a blank screen. ADB works, but neither KFU nor the Fire Unbrick Utility will recognize it, I just get waiting for device. This has left me really scratching my head. Any advice would be greatly appreciated.
Typically, this is caused by a bad download (failure to check MD5) or not " wiping" correctly. In your case, I'm willing to bet Clockwork is the culprit. Use fastboot to manually install TWRP to see if that fixes the problem, or try a different rom. Personally, and based on what I've seen in the recent past, I think Clockwork is not a safe bet in regards to custom recovery at the moment.
soupmagnet said:
Typically, this is caused by a bad download (failure to check MD5) or not " wiping" correctly. In your case, I'm willing to bet Clockwork is the culprit. Use fastboot to manually install TWRP to see if that fixes the problem, or try a different rom. Personally, and based on what I've seen in the recent past, I think Clockwork is not a safe bet in regards to custom recovery at the moment.
Click to expand...
Click to collapse
Thank you for replying. The problem is I can't get it into fastboot. When I turn on the KFU, it states that ADB is online but boot status is unknown. I can force it to reboot but I can't get it to fastboot. Whenever I try to install anything or repair it with the Kindle Fire Unbrick Utility, I either get waiting for device forever or exec '/system/bin/sh' failed. The default kindle bootloader is still installed, I think, and I can't get into clockworkmod at all.
daimyo777 said:
Thank you for replying. The problem is I can't get it into fastboot. When I turn on the KFU, it states that ADB is online but boot status is unknown. I can force it to reboot but I can't get it to fastboot. Whenever I try to install anything or repair it with the Kindle Fire Unbrick Utility, I either get waiting for device forever or exec '/system/bin/sh' failed. The default kindle bootloader is still installed, I think, and I can't get into clockworkmod at all.
Click to expand...
Click to collapse
See, this is why it's important to be extremely detailed with the issues you are experiencing, including all error messages.
Code:
exec '/system/bin/sh' failed
That indicates your shell has been damaged or corrupted. The only fix for this so far, is with a factory cable. Get a factory cable to put your device in fastboot.
heres where to find a cable http://forum.xda-developers.com/showthread.php?t=1392693
Thepooch said:
heres where to find a cable http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
Thank you. I just bought one. Just one question, when it arrives, how do I use it? Do I just use the KFU to install Firefirefire? Or do I have to use firekit? And do I just plug in the cable once to force fastboot then use a normal cable to flash a new recovery and bootloader? Sorry, I'm kind of new at this.
By plugging the cable into your usb port first, then to your device that has been powered off, the device will power on automatically into fastboot. After that it can be used to send commands and transfer data as a normal cable. Using it in a way other than I described will not enable fastboot automatically.
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
favaron88 said:
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
Click to expand...
Click to collapse
Do you have a bootloader installed? Can you boot into recovery?
Eaffon said:
Do you have a bootloader installed? Can you boot into recovery?
Click to expand...
Click to collapse
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
favaron88 said:
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
Click to expand...
Click to collapse
Hmm... Does it show up in device manager?
Dont throw it.. give it to me. Haha
After my sem I will have plenty of time to do all this stuff..
Sent from my SGH-T999 using xda premium
Eaffon said:
Hmm... Does it show up in device manager?
Click to expand...
Click to collapse
I've uploaded a screen shot of my device manager and in "devices and printers"
as you can see, it shows up as a kindle in devices and printers, and as an android phone in the device manager.
I also uploaded "My Computer" so you can see there is no access to it from there.
Okay.
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Eaffon said:
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Click to expand...
Click to collapse
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
favaron88 said:
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
Click to expand...
Click to collapse
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Eaffon said:
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Click to expand...
Click to collapse
alright, I found it and tried those commands and this is what I got.
favaron88 said:
alright, I found it and tried those commands and this is what I got.
Click to expand...
Click to collapse
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Eaffon said:
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Click to expand...
Click to collapse
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
You could try my prefab ISO soupkit is already ran on it and it has teamviewer installed for assistance measures you can find it here post 7 http://forum.xda-developers.com/showthread.php?t=1413358 but what I think you will need is a factory cable found here ultimately post 9 http://forum.xda-developers.com/showthread.php?t=1392693 . The system is trying to run that's why it comes up android composite adb interface, its busy trying to handle the data that you failed to wipe prior to flashing jelly bean and then stock. You could also see if if will allow you to send twrp and fff back to the device with kfu then enter recovery wipe and reflash another ROM.
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
It's totally fixable.
Thepooch is right. My brother had the same problem with his son's. Just get into fastboot and flash a bootloader and twrp and youre set
Sent from my Amazon Kindle Fire using xda app-developers app
Thepooch said:
It's totally fixable.
Click to expand...
Click to collapse
Awesome
Also I didn't want you to think I ignored your post. I just finished making the usb drive with ubuntu on it and was going to attempt your solution in the other thread if whatever we were trying here doesn't work.
I appreciate y'alls help very much.
Eaffon said:
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Ok I loaded KFU and told went and told it to boot in fastboot, it said that it told the device to do it, but it still says Boot Status: Unknown.
Is this a problem or do we know that it's booting in fastmode now? I'm just not sure how to tell if it was successful since it's not giving me the code.
(Ps - I originally posted this before my previous post thanking you guys, but then came back to this window to see that I had screwed up the Captcha, but it wouldn't let me post for 5 more minutes since I'm a new user. Sorry for the wait.)
Its very common for the boot mode to be unknown in fast boot. Try to send twrp with kfu if it says waiting for device for a long time simply power it off while connected then back on it should then pick up and send twrp. If need be do the same thing with the bootloader just wait longer a failed bootloader flash is far worse than the situation your in.
favaron88 said:
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
Click to expand...
Click to collapse
ADB is connected, therefore you are not in fastboot. The Kindle Fire logo you see is actually the stock boot animation. The difference is whether or not it changes in brightness at any point (obviously it does).
You need access to recovery to fix your problem and you need the ability to change bootmodes to get into recovery. Without a working shell you need access to fastboot to change bootmodes.
Unfortunately, in many situations like yours, there is no working shell to change the bootmode. To confirm this, try to launch the shell by entering "adb shell", respectively.
If you receive an error, your only options are to get a factory cable (recommended) or open the device so you can put it in USBboot via the shorting trick and the use of Firekit (not so recommended).
With access to fastboot, you can change your bootmode to recovery or reinstall a custom recovery if necessary. In recovery, the "fix" is as simple as reinstalling a ROM.
"That's a special kind of stupid. The kind that makes me laugh."
Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail
farkuldi said:
Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail
Click to expand...
Click to collapse
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.
Socially Uncensored said:
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.
Click to expand...
Click to collapse
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!
farkuldi said:
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!
Click to expand...
Click to collapse
The unbrick program didn't work. It just stayed there t <waiting for device>. How can I use the fastboot cable to fix it?
Thanks.
I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC
ezproxy said:
I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC
Click to expand...
Click to collapse
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.
farkuldi said:
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.
Click to expand...
Click to collapse
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159
ezproxy said:
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I'd say you didn't read the previous posts.
Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.
farkuldi said:
Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.
Click to expand...
Click to collapse
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.
Socially Uncensored said:
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.
Click to expand...
Click to collapse
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?
Gon Rouge said:
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?
Click to expand...
Click to collapse
post in correct forum
Fire Index: Which Amazon (Kindle) Fire Do I have?
"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.
jerry777888 said:
"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.
Click to expand...
Click to collapse
Repost what?
Sent from my ocean using XDA Labs