Related
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
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
kindlestuck said:
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
Click to expand...
Click to collapse
[HOW-TO] Before asking for troubleshooting help...
Frequently Asked Questions - Amazon Kindle Fire
[GUIDE] Kindle Fire For Beginners
[HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)
He has all of the drivers installed, but KFU seems to have an issue with file paths. I have redownloaded it for him and I also updated his copy of the SDK with Kindle Fire drivers and a newer ADB. The KFU returns an error "System cannot find the path specified for everything, even though it is extracted straight out of the zip it came in. All he did was choose install TWRP and it didn't even make it to fastboot mode before it bricked.
Zeklandia said:
He has all of the drivers installed, but KFU seems to have an issue with file paths. I have redownloaded it for him and I also updated his copy of the SDK with Kindle Fire drivers and a newer ADB. The KFU returns an error "System cannot find the path specified for everything, even though it is extracted straight out of the zip it came in. All he did was choose install TWRP and it didn't even make it to fastboot mode before it bricked.
Click to expand...
Click to collapse
Thank you for your insight, but all the information needed to fix what is a very common problem can be found in the threads to which links have been provided. The device IS in fastboot. Simply changing the bootmode is the key to resolving the problem. That being said, the KFU is not the end all/be all to changing the bootmode or installing TWRP.
soupmagnet said:
Thank you for your insight, but all the information needed to fix what is a very common problem can be found in the threads to which links have been provided. The device IS in fastboot. Simply changing the bootmode is the key to resolving the problem. That being said, the KFU is not the end all/be all to changing the bootmode or installing TWRP.
Click to expand...
Click to collapse
It is not in fact in fastboot, it is not even listed in adb devices or fastboot devices.
---------- Post added at 12:52 PM ---------- Previous post was at 12:29 PM ----------
I have a feeling it is trying to boot into stock recovery, as KFU was trying to reboot into TWRP (which never installed because KFU was broken).
---------- Post added at 12:55 PM ---------- Previous post was at 12:52 PM ----------
If we can get out of stock recovery, that would be useful. Do you have any idea how to bring up the menu in stock recovery? Does he need to hold the power button down or press it in a pattern?
Zeklandia said:
It is not in fact in fastboot, it is not even listed in adb devices or fastboot devices.
Click to expand...
Click to collapse
While some who know me better may be prepared to see me respond in my usual manner at this point, I have instead, decided to play nice
I have been a member of this forum for quite some time and have seen hundreds of different problems in just as many scenarios for each, and I can assure you, without even a shred of doubt, that the device is in fact in fastboot mode (unless, of course, the information provided in the OP is inaccurate).
You can find information for properly identifying fastboot mode in the "Frequently Asked Questions" thread and the "Fastboot Guide" linked to within it, so please feel free to prove me wrong.
With that,
Just because the device itself doesn't respond to fastboot commands from the computer, doesn't mean the device isn't in fastboot mode. It simply means (in this case) that the drivers are not properly installed or configured, despite the steps taken to do so. Windows is very tricky when it comes to installing drivers for Android and there are hundreds of posts within these forums that should be able to convince you of that. If you want to eliminate all doubt and ensure that driver problems aren't just compounding the issue, set up a Linux LiveUSB and either install SoupKit, or configure it manually to communicate with the device via USB so that adb and fastboot commands will work properly.
Good luck
I appreciate you trying to help, but his device is 100% stock. KFU has set it to boot into recovery, and it will continue to boot into the stock recovery until we can find a way to change that idme bootmode. Tomorrow, I will attempt to use my factory cable on it, but for now all fastboot does is wait for device. I use Linux, so if it truly is in fastboot mode, then it should have no problem, especially with the factory cable.
Zeklandia said:
I appreciate you trying to help, but his device is 100% stock. KFU has set it to boot into recovery, and it will continue to boot into the stock recovery until we can find a way to change that idme bootmode. Tomorrow, I will attempt to use my factory cable on it, but for now all fastboot does is wait for device. I use Linux, so if it truly is in fastboot mode, then it should have no problem, especially with the factory cable.
Sent from my Battle Droid
Click to expand...
Click to collapse
Looking at your signature, I see that you are technically competent enough to take a look at the KFU 'run.bat' and see how it works. When the option to install TWRP is selected, the script uses Pokey9000's 'fbmode' to boot into fastboot mode. Once KFU is able to detect the device in fastboot, it then uses fastboot commands to flash TWRP to the recovery partition and then reboot to recovery. If the KFU were able to detect the device in fastboot mode and TWRP was not installed due to file paths, then the device would still boot into the stock recovery, normally, and you would see plenty of error messages giving you a clue as to what went wrong. Messages in the KFU window compared to those found in the script itself can also show you where things went wrong.
What happens (more times than I care to try and estimate) is, due to the way Windows handles Android drivers, when the device is put into fastboot mode (even though adb commands were working at the time), the fastboot drivers aren't working properly, the script cannot move forward and the device gets stuck in fastboot mode.
As I mentioned earlier, the "Fastboot Guide" linked to in the FAQ, tells you how to recognize fastboot mode beyond all uncertainty. With all due respect, I'd suggest you look into it before deciding that you know best in this particular situation.
And not to make assumptions about your level of proficiency with Linux, but don't forget that you have to either set up udev rules for the device, or run your fastboot commands as root for it to work properly.
same issue...
yes perhaps you should be a little more sympathic to the OP as 1. he probably has a valid issue (im having the same problem...neither windows nor Soupkit is recognizing my KF thats stuck in the white and orange logo fastboot and 2. none of the above links help this problem in any manner. I have been researching this issue for days now and have tried a few different distros (just my luck Mint's persistance didnt work...sigh) and no matter what, my computer will not communicate with the KF.
it seems my KF is now bricked because I ran the KFU and selected install "FireFireFire" before rooting...it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem.
if you have any other suggestions it sure would be appreciated...thanks.
menriquez said:
yes perhaps you should be a little more sympathic to the OP as 1. he probably has a valid issue (im having the same problem...neither windows nor Soupkit is recognizing my KF thats stuck in the white and orange logo fastboot and 2. none of the above links help this problem in any manner. I have been researching this issue for days now and have tried a few different distros (just my luck Mint's persistance didnt work...sigh) and no matter what, my computer will not communicate with the KF.
it seems my KF is now bricked because I ran the KFU and selected install "FireFireFire" before rooting...it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem.
if you have any other suggestions it sure would be appreciated...thanks.
Click to expand...
Click to collapse
Make no mistake about it...I am sympathetic to every single person who "bricks" their device. However, I find it very hard to be sympathetic to those who fail to take personal responsibility for a problem they created due to not having done the appropriate amount of research before getting involved in something they didn't understand.
First off, your device does not have to be rooted to install FireFireFire. As a matter of fact, it's better that you install FireFireFire before trying to root...but your drivers have to be in working order from the start. And you have absolutely NO RIGHT to push blame on someone else just because you don't have the knowledge necessary to modify your device without tools made by other people. It is your device and your responsibility...so own up to it.
Second, I can say beyond all uncertainty that the information needed to understand and resolve yours and 90% of all other situations in this forum, can be found in those 4 links posted earlier. But since no one seems to want to believe that, I guess I'll just have to prove it to you.
1) Being stuck at the Kindle Fire logo means your device is in one of two states; in fastboot mode, or in normal mode but without a working system to boot to. This is explained in both the Frequently Asked Questions thread and the Fastboot Guide thread linked to within it. FAQ #16, Fastboot Guide
2) Also explained in the threads mentioned previously, is information on determining what state the device is in by paying attention to the behavior of the Kindle Fire logo as the device starts up. If the Kindle Fire is displayed brightly and stays brightly lit indefinitely, the device is in fastboot mode. If the Kindle Fire logo is brightly lit for a few seconds then flashes and/or goes dim, then it is trying to boot normally to a non-working system. With that knowledge, you can easily determine your next course of action...also based on the information found in the links provided. FAQ #16, Fastboot Guide
3) The key to fixing 99% of all Kindle Fire problems is getting access to custom recovery. There are two ways to access custom recovery when your device is malfunctioning, through FireFireFire, or through fastboot. If you don't have FireFireFire installed, the only option you have left is fastboot. If the device is trying to boot normally to a non-working system, then your only option for accessing fastboot is with a factory cable. FAQ #16, 17, 26, 29, 32, 33, Fastboot Guide
4) If your device is already in fastboot mode, and you are unable to change your bootmodes with the command line in Windows, it is because your drivers aren't properly installed. There is no other possible scenario. FAQ #14, KFFB - post #3
5) If you are using Windows, and you are unable to fix your drivers despite the wealth of information available to you for getting the drivers to work properly, then you use use Linux. FAQ #15
Your situation is no different. If I were to make an educated guess, I would say device is stuck in fastboot mode because your drivers weren't working properly...and you only have Microsoft to blame for that. As for Linux, it will not communicate your device using ADB or fastboot automatically. You have to either run the commands as the root user, or set up udev rules for your device. If you used the SoupKit to set up your udev rules using a LiveUSB, you have to have working persistence. The way it's configured now is to reboot in order for the udev rules to be loaded. If you don't have working persistence, everything you did prior to the reboot will be lost (This is also explained to you in the SoupKit thread).
With that being said, you have NO RIGHT to get offended if I would rather post a few links and expect the user to do the appropriate amount of research on their own to fix a problem THEY CREATED, than spend my personal time to tell every single user that comes to this forum with the exact same problems, everything that I have told you just now.
I wish you the best of luck in getting your device fixed, and I have no qualms about providing you support for the things in the aforementioned threads that you don't understand. But I WILL NOT hold your hand and tell you every single little thing that you need to know in order for you to fix your own device.
soupmagnet said:
Make no mistake about it...I am sympathetic to every single person who "bricks" their device. However, I find it very hard to be sympathetic to those who fail to take personal responsibility for a problem they created due to not having done the appropriate amount of research before getting involved in something they didn't understand.
First off, your device does not have to be rooted to install FireFireFire. As a matter of fact, it's better that you install FireFireFire before trying to root...but your drivers have to be in working order from the start. And you have absolutely NO RIGHT to push blame on someone else just because you don't have the knowledge necessary to modify your device without tools made by other people. It is your device and your responsibility...so own up to it.
Click to expand...
Click to collapse
wow...sigh...listen the last thing my post tried to do is shift blame...i CLEARLY stated *I* made a BIG MISTAKE didn't I?? i dont need a flame war here sheesh im just trying to fix this ****ty kindle for a buddy.
Second, I can say beyond all uncertainty that the information needed to understand and resolve yours and 90% of all other situations in this forum, can be found in those 4 links posted earlier. But since no one seems to want to believe that, I guess I'll just have to prove it to you.
1) Being stuck at the Kindle Fire logo means your device is in one of two states; in fastboot mode, or in normal mode but without a working system to boot to. This is explained in both the Frequently Asked Questions thread and the Fastboot Guide thread linked to within it.
2) Also explained in the threads mentioned previously, is information on determining what state the device is in by paying attention to the behavior of the Kindle Fire logo as the device starts up. If the Kindle Fire is displayed brightly and stays brightly lit indefinitely, the device is in fastboot mode. If the Kindle Fire logo is brightly lit for a few seconds then flashes and/or goes dim, then it is trying to boot normally to a non-working system. With that knowledge, you can easily determine your next course of action...also based on the information found in the links provided.
3) The key to fixing 99% of all Kindle Fire problems is getting access to custom recovery. There are two ways to access custom recovery when your device is malfunctioning, through FireFireFire, or through fastboot. If you don't have FireFireFire installed, the only option you have left is fastboot. If the device is trying to boot normally to a non-working system, then your only option for accessing fastboot is with a factory cable.
4) If your device is already in fastboot mode, and you are unable to change your bootmodes with the command line, it is because your drivers aren't properly installed. There is no other possible scenario.
5) If you are using Windows, and you are unable to fix your drivers despite the wealth of information available to you for getting the drivers to work properly, then you use Linux.
Click to expand...
Click to collapse
lol i read and did ALL of that my chippy friend...the logo starts and stays bright so im sure im in fastboot mode. i got the latest ubuntu on a pen, like i said after i tried Mint 15 and discovered that persistence on a pen doesn't work well with that distro currently. ubuntu did, and in fact recognizes all my other android devices no problem...but nothing at all when i plug the kindle
Your situation is no different. If I were to make an educated guess, I would say device is stuck in fastboot mode because your drivers weren't working properly...and you only have Microsoft to blame for that. As for Linux, it will not communicate your device using ADB or fastboot automatically. You have to either run the commands as the root user, or set up udev rules for your device. If you used the SoupKit to set up your udev rules using a LiveUSB, you have to have working persistence. The way it's configured now, is to reboot in order for the udev rules to be loaded. If you don't have working persistence, everything you did prior to the reboot will be lost (This is also explained to you in the SoupKit thread).
Click to expand...
Click to collapse
like i said both in my original post and above, i figured out the persistence issue its working now. the reboot loaded the rules but when the script runs im getting two errors which, due to my deep frustration at the time i didn't write down the exact wording. i figured i'd chill for a while and then try again later.
With that being said, you have NO RIGHT to get offended if I would rather post a few links and expect the user to do the appropriate amount of research on their own to fix a problem THEY CREATED, than spend my personal time to tell every single user that comes to this forum with the exact same problems, everything that I have told you just now.
I wish you the best of luck in getting your device fixed, and I have no qualms about providing you support for the things in the aforementioned threads that you don't understand. But I WILL NOT hold your hand and tell you every single little thing that you need to know in order for you to fix your own device.
Click to expand...
Click to collapse
hey i totally appreciate your help and your wish of luck lord knows ill take anything right now this stupid "project" has caused me more grief then i could have ever imagined it could. btw, i didnt get "offended" i just thought maybe you were being kinda hard on the OP due to my experience dealing with the exact same issues he posted he was dealing with...
...believe it or not not everyone who doesn't have the same experiences with this stuff as you do aren't necessary idiots or unskilled at using complex systems. thanks again for your continued help and do have a great day!
menriquez said:
wow...sigh...listen the last thing my post tried to do is shift blame...i CLEARLY stated *I* made a BIG MISTAKE didn't I?? i dont need a flame war here sheesh im just trying to fix this ****ty kindle for a buddy....!
Click to expand...
Click to collapse
The last thing I want to do is to get into a flame war with anyone, but when someone comes to the forum and says something like...
it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem
Click to expand...
Click to collapse
...which, by the way, is entirely based on misinformation...it is very easy for someone to assume the author is, whether directly or indirectly, speaking poorly about a developer's work and assigning blame by presuming that the mistake would not have been made if the tool in question had been made differently. Based on the limited information from your original post, one can only assume that your situation is no different from the hundreds of other users with the same exact problem that also swore the information available did not pertain to their situation and that they were somehow unique, only to find out 50 posts later that it was not the case.
But rather than letting this discussion escalate any further, lets try a different approach. I will give you the benefit of the doubt and entertain the thought that your situation is in fact unique and that there is possibly some other solution for your problem. But, in order for me to do that, I'm going to need some information...very detailed information.
From what I gather so far, based on the information you've provided in your second post is...
1) Your device is in fastboot, confirmed by the fact that the Kindle Fire logo stays brightly lit.
2) You are currently using a LiveUSB with Ubuntu installed and working persistence.
3) When you ran the SoupKit install script, you received errors of some sort, but don't you remember what they were.
4) You are unable to send any fastboot commands at all.
The things I would like to know are...
1) What version of Ubuntu are you running?
2) What brand of pendrive are you using?
3) What is the exact error you received when trying to install the SoupKit?
4) With your device connected, enter the following commands (in Linux) and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
Code:
cat ~/.android/adb_usb.ini
Code:
sudo cat /etc/udev/rules.d/51-android.rules
soupmagnet said:
...
But rather than letting this discussion escalate any further, lets try a different approach. I will give you the benefit of the doubt and entertain the thought that your situation is in fact unique and that there is possibly some other solution for your problem. But, in order for me to do that, I'm going to need some information...very detailed information.
From what I gather so far, based on the information you've provided in your second post is...
1) Your device is in fastboot, confirmed by the fact that the Kindle Fire logo stays brightly lit.
2) You are currently using a LiveUSB with Ubuntu installed and working persistence.
3) When you ran the SoupKit install script, you received errors of some sort, but don't you remember what they were.
4) You are unable to send any fastboot commands at all.
The things I would like to know are...
1) What version of Ubuntu are you running?
2) What brand of pendrive are you using?
3) What is the exact error you received when trying to install the SoupKit?
4) With your device connected, enter the following commands (in Linux) and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
Code:
cat ~/.android/adb_usb.ini
Code:
sudo cat /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
firstly i'm very appreciative of your decision to get this back on a positive track and even more thankful that you are still trying to help...
1. ubuntu 13.04 32-bit
2 16gb sandisk with 1024m persistance
3. i reinstalled everything and double checked it...i am no longer getting any errors running soupkit it just says "device offline"
4 lsusb -vd 1949: | grep 'bcdDevice' - nothing just the prompt
5. cat ~/.android/adb_usb.ini - 0x1949
6 . sudo cat /etc/udev/rules.d/51-android.rules -
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
well thats it...i plug my nexus 7 and GS3 and even an ultra cheapo zte warp sequent and it connects right up to all of those...
menriquez said:
firstly i'm very appreciative of your decision to get this back on a positive track and even more thankful that you are still trying to help...
1. ubuntu 13.04 32-bit
2 16gb sandisk with 1024m persistance
3. i reinstalled everything and double checked it...i am no longer getting any errors running soupkit it just says "device offline"
4 lsusb -vd 1949: | grep 'bcdDevice' - nothing just the prompt
5. cat ~/.android/adb_usb.ini - 0x1949
6 . sudo cat /etc/udev/rules.d/51-android.rules -
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
well thats it...i plug my nexus 7 and GS3 and even an ultra cheapo zte warp sequent and it connects right up to all of those...
Click to expand...
Click to collapse
Oh........this again....
For reasons I have yet to figure out, there are rare (and I do mean rare) situations where Linux just will not detect the device whatsoever. When you enter the 'lsusb' command, whether the udev rules are configured properly or not, Linux should still detect your device when plugged into the USB. I can probably count on one hand the number of times I've seen this happen, and I've never been able to recreate the problem on my own.
It could be caused by using the wrong USB port (i.e. USB3.0 instead of USB2.0), it could be caused by the USB pendrive itself, you could have a faulty cable, it may even be the Linux install itself, but those are just wild guesses because I have really don't know. My best estimate is that there is a bug in the stock bootloader that sometimes causes it to malfunction when put into fastboot because (in the few instances I've seen), users that were able to resolve their situation did so by using usbboot to install a custom bootloader. This of course requires opening the device and performing the "shorting trick" to drop the device into usbboot mode.
If I were you, considering you probably haven't attempted to usbboot before, you should try a different USB port, a different USB cable, and a different pendrive to see if you have any luck. Otherwise, you may have no other choice but to usbboot.
The unfortunate thing usbbooting is, it's just one of those things you have to somehow figure out on your own, even with the instructions given in the Firekit/usbboot thread (it's really about technique more than anything else). I've done it several times myself, mostly for testing and various other reasons, but the first time (when I really needed it), took practically forever to get it right.
If you do take the usbboot route, you can launch Firekit from the SoupKit utility script (option #4, I think) and follow the instructions in the Firekit thread. Be very careful opening the device, use a safety pin for creating the short (the reason will become apparent when you get the device opened), and most of all...good luck.
[Edit:] And yes, crow is very tasty
kindlestuck said:
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
Click to expand...
Click to collapse
Charge kindle, boot into the frozen logo screen with no animation, plug into computer, and reboot computer, i want to share this with everyone because it worked for my kindle
I'm pretty frustrated because I've spent more than 4 hours trying to boot into fastboot, googling, searching XDA, ...
- OS: Windows 8
- Kindle Fire HD 8.9, Software 8.4.6, rooted, ADB activated in the security settings
- Amazon ADB drivers installed, device manager says "Kindle Fire" -> "Android Composite ADB Interface"
- when trying to boot into fastboot with "fastboot -i 0x1949 getvar product", I'm stuck at waiting for device. Device manager blinks ("Jem-PVT-Prod-04") and the Kindle boots up normally
- when using KFFirstAide64 I can boot into fastboot, device manager says "Jem-PVT-Prod-04" with a yellow triangle (obviously no driver)
- when trying to send any fastboot commands to the Kindle, (like fastboot devices), nothing happens
- pressing and holding the power button shuts the Kindle down, powers on normally
Please help!
I need to get rid of this Kindle ROM. Tried it for a day but this crap really hurts once you're used to CM-ROMs
Cheers,
Carsten
Try putting it into fastboot again and use these drivers for the device that comes up and see if it will install them:
http://forum.xda-developers.com/showthread.php?p=44446906
Ha, for a minute I thought I saw my name at the end of this post... For the sake of privacy I don't really intend on giving my name out openly to explain why, but if you look at my skype profile it would make sense.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
STRIKE!
It worked!
Had to reboot windows in order to deactivate the enforcement of driver signatures (your usb driver failed with "The hash for the file is not present in the specified catalog file"), but it finally boots into fastboot and back.
If you could spare a few seconds to explain why your driver files work and others don't? (too old?)
And what's this fuzz about driver signatures?
Anyway, thank you so much!
kasek said:
STRIKE!
It worked!
Had to reboot windows in order to deactivate the enforcement of driver signatures (your usb driver failed with "The hash for the file is not present in the specified catalog file"), but it finally boots into fastboot and back.
If you could spare a few seconds to explain why your driver files work and others don't? (too old?)
And what's this fuzz about driver signatures?
Anyway, thank you so much!
Click to expand...
Click to collapse
I am not sure why the ones you already had didn't work with fastboot. Those drivers were just a compilation of device vendors id and product id's off of various kindles i have had to help with or deal with myself. As to the other part i will say this, I find windows 8 to be a total pain. The problems u were having is thanks to Microsoft deciding to enable that driver signature enforcement, see once I modify the drivers it kinda unsigns them so that's why you had issues. I don't know why they enabled that feature on windows 8, it was on vista too if I remember correctly, and then on 7 it was gone and it just gave u a warning while trying to install. I got sick of windows myself and stick to Linux unless I'm gaming. Driver problems are a lot easier because it comes with tons of drivers, never has to install the device, it just initializes automatically, unless under a few rare occasions u have to compile the drivers that it doesn't have. Yay Linux!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Yeah, you're right about Windows 8, it's really a pain in the a**.
I'm gonna switch to Ubuntu once they'll publish my beloved shooters (CoD, Battlefield, ...) on Linux. Fortunately, I'm using Linux since my college time ('94) so I guess the only one having problems will be my wife
stunts513 said:
I am not sure why the ones you already had didn't work with fastboot. Those drivers were just a compilation of device vendors id and product id's off of various kindles i have had to help with or deal with myself. As to the other part i will say this, I find windows 8 to be a total pain. The problems u were having is thanks to Microsoft deciding to enable that driver signature enforcement, see once I modify the drivers it kinda unsigns them so that's why you had issues. I don't know why they enabled that feature on windows 8, it was on vista too if I remember correctly, and then on 7 it was gone and it just gave u a warning while trying to install. I got sick of windows myself and stick to Linux unless I'm gaming. Driver problems are a lot easier because it comes with tons of drivers, never has to install the device, it just initializes automatically, unless under a few rare occasions u have to compile the drivers that it doesn't have. Yay Linux!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
confirm rooted in ver 8.4.6
Could you give me a course link about rooting KFHD8.9 on Ver8.4.6 ?Thank you~
Zukii said:
Could you give me a course link about rooting KFHD8.9 on Ver8.4.6 ?Thank you~
Click to expand...
Click to collapse
Shure.
This one worked perfectly for me:
http://forum.xda-developers.com/showthread.php?t=2337634
hi guys, i'm stuck in the very same point as the OP and i am getting the "hash for the file is not present......" error when installing the pointed drivers,
how do i install them?
kasek said:
I'm pretty frustrated because I've spent more than 4 hours trying to boot into fastboot, googling, searching XDA, ...
- OS: Windows 8
- Kindle Fire HD 8.9, Software 8.4.6, rooted, ADB activated in the security settings
- Amazon ADB drivers installed, device manager says "Kindle Fire" -> "Android Composite ADB Interface"
- when trying to boot into fastboot with "fastboot -i 0x1949 getvar product", I'm stuck at waiting for device. Device manager blinks ("Jem-PVT-Prod-04") and the Kindle boots up normally
- when using KFFirstAide64 I can boot into fastboot, device manager says "Jem-PVT-Prod-04" with a yellow triangle (obviously no driver)
- when trying to send any fastboot commands to the Kindle, (like fastboot devices), nothing happens
- pressing and holding the power button shuts the Kindle down, powers on normally
Please help!
I need to get rid of this Kindle ROM. Tried it for a day but this crap really hurts once you're used to CM-ROMs
Cheers,
Carsten
Click to expand...
Click to collapse
I'm like you (8.4.6) somehow I getinto fastboot quite succesfully, I dont know if this is your problem, you seems to try to "fastboot" before you poweroff your device.
don_ernesto said:
hi guys, i'm stuck in the very same point as the OP and i am getting the "hash for the file is not present......" error when installing the pointed drivers,
how do i install them?
Click to expand...
Click to collapse
Maybe this link could be helpful:
http://www.fotoclubinc.com/blog/how-to-disable-driver-signature-enforcement-to-allow-installation-of-windows-7-printer-drivers-on-windows-8/
This was exactly what I did.
Good luck!
Hey guys my name is Vito, even though this is my first post I have been reading Xda developers forums for a while. More than a year ago I bricked my first generation Kindle Fire and ever since been trying to unbrick it. These days i have a new version of kindle fire but from time to time i get back into trying to fix the old tablet without succeeding. I've read many threads on this forum in regards to Kindle Fire trouble shooting and used the search button dozens of times so i hope i don't repeat an existing threads. I am posting here as my last resort to try to trouble shoot the problem and get some experienced advice to hopefully fix the tablet because i failed trying to fix it on my own.
My kindle fire 1st gen has been rooted, it has FireFireFire bootloader v1.4a and working TWRP v2.2.2.1 also I got factory cable and otg cable, and USB debugging Disabled, No ROM,
How I bricked it: One day i was playing with an operating system tuning application and after pressing auto tune kindle fire either froze or shut down and when i power it back on it would just freeze on "booting, with blue kindle fire logo". That's where i made a few mistakes i believe, instead of researching xda developers forum thoroughly i went into TWRP and wiped cache, dalvik cache, factory reset, and unfortunately system (ROM) however i did not wiped the external storage so that still there. Also USB debugging was disabled on my kindle fire at the time i bricked the device.
What I tried to fix it: I tried to install and re install many different kindle fire drivers for windows on at least 4 different computers and operating systems ( XP, WIN7, WIN8 ) but my kindle fire would not be detected and adb would not work, also tried going trough guides on installing Android SDK and getting ADB working but now i know that i wont be able to get ADB working without having USB debugging enabled.
So i ended up with only one option Fastboot. I tried installing Ubuntu on one of the computers with soupkit but linux would not recognize kindle fire being connected, it would always say waiting for device, same thing would be if i log on to ubuntu from flash drive boot.
Also when i type # lsusb command in ubuntu command prompt it gives me all usb ports and connected devices but kindle fire does not get detected in any mode while my new kindle fire does get detected in ubuntu once connected.
When i get into fastboot mode and i type # fastboot getvar product every time i get < waiting for device >.
So that's about it, all the above i tried and re tried hoping to get it going but im either doomed or im just doing something wrong or missing something all the way which is possible. I would really appreciate anyone's help and feedback on this post and would really love to just try to figure this thing out.
Thank you.
Vito,
I am new and far from an expert, however, I just discovered if you have TWRP, there is an option to mount the sdcard space and copy files. Not sure about the version you have but give it a try:
- Connect USB to PC
- Boot on TWRP
- Mount sdcard
- copy ROM (make sure you use one that works with your TWRP version and whatever other software is there)
- install ROM
Like I said, far from expert, but I believe all you need is a ROM.
pokeys fire kit should sort it. im back in 2 hours. i can help you then
Sent from my Nexus 5 using Tapatalk
pm me when your online
shabuboy said:
Vito,
I am new and far from an expert, however, I just discovered if you have TWRP, there is an option to mount the sdcard space and copy files. Not sure about the version you have but give it a try:
- Connect USB to PC
- Boot on TWRP
- Mount sdcard
- copy ROM (make sure you use one that works with your TWRP version and whatever other software is there)
- install ROM
Like I said, far from expert, but I believe all you need is a ROM.
Click to expand...
Click to collapse
Thanks for replying, my TWRP version has that option to mount sdcard but unfortunately it does not work, if only it did
lovejoy777 said:
pokeys fire kit should sort it. im back in 2 hours. i can help you then
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey Lovejoy777, thanks for the help, I will send you PM.
it does not mount it? Or it does not show on Windows? If it is the Windows part, you probably need the drivers. I used Kindle Fire Utility v0.9.9.zip.
This also helped me after rooting my device.
http://forum.xda-developers.com/showthread.php?t=2308295
and sorry, this is where my expertise ends
Hi All,
Today I should be picking up a KF2 (Kindle Fire 2nd Gen) today from a friend. And although I have experience with this device in the past, as I rooted one a while ago, and installed Google PlayStore bits and bobs for another friend... This was a while back.
A few months back, I read somewhere although cannot find it now... That Amazon have rolled out a serious Update to most Kindles (KF2, KF-HD, and possibally KF-HDX) that has updated the baseband/kernel to a certain version. Which prevents Unlocking, and tampering with it could cause the device to Hard Brick...
So was wondering, what is the best procedure to tackle this? Easy method to Root / Recovery??
And what does this 2nd BootLoader actually do?? Does it allow you to DualBoot both original stock Kindle firmware as well as second partition for Custom Roms??
Thanks, Lister
OK first off which kindle do you have, because a kf2 is. Of a 2nd gen kfhd. If its a 2013 kindle fire HD, don't bother with second bootloader because it will just brick it. If it is in fact a kf2 then here's what second d bootloader does. Basically we can't unlock our devices bootloader so 2nd bootloader is a workaround. It allows us to run our own unsigned kernels and custom recovery. Once we have that we can flash a custom ROM like cm. And no no dual booting, Amazon's os is too different from cm to be able to.
To install 2nd bootloader + twrp you must be rooted, suggest kindle fire first aid for that, there's a tutorial in the dev section for kf2 for installing second bootloader + twrp here.
Make sure you check the md5sum of the bootloader before flashing it so you don't risk hard bricking, also I suggest putting the ROM and its gapps on the kindle ahead of time if your are running 10.4.8 because it will boot loop into recovery after the process until you flash a different rom, so its easier to have the ROM o. Ahead of time rather than "adb push" it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hi @stunts513,
Sorry for the delay getting back to you, my friend didnt bring the device in until yesterday...
I can confirm that it is a Kindle Fire 2nd Gen (Otter2), and it is running 10.4.6 firmware/baseband...
I tried to root it in work, on my Windows 8.1 and Windows 7 based PCs, and unfortunately it wasn't detecting it, or working with the ADB drivers....
I tried at home on my Windows XP and Vista setup, and again wasn't detecting it. However it did detect on my Windows 7 setup at home (triple boot). This must of been the partition I used for my friends one many months ago... (although I found various Kindle related files on each partition).
Anyway, I got the damn thing rooted now, thankfully... and shall move onto the 2nd Bootloader thing... However, is there any other way, or easy way of doing this other than whats in that post?? I don't mind doing it, and will follow it again. However late last night I was losing the will to live as it was hard work getting to do things... (compared to other Android devices that are a breeze to do...).
I tried to backup my partitions on the Kindle what it says to do at the start, and it kept saying it couldnt find these on the Kindle... I read in the guide that it said I could download them from a website, but all I could see was scripts and not backup partitions... Is it really important to backup my own ones, or could I just download someone else's Kindle Fire 2nd (8Gb) model??
And yeah, is there any other way to get custom recovery / rom on, other than the original guide...?? - not gonna give up, just last night kept falling asleep trying to follow it... when things werent working and patiently waiting for things to happen/work... lol
Anyway, thanks so much for replying to my question, and for all the help you have given me to get me started... much appreciated!!
Thanks, Lister
Lister Of Smeg said:
Hi @stunts513,
Sorry for the delay getting back to you, my friend didnt bring the device in until yesterday...
I can confirm that it is a Kindle Fire 2nd Gen (Otter2), and it is running 10.4.6 firmware/baseband...
I tried to root it in work, on my Windows 8.1 and Windows 7 based PCs, and unfortunately it wasn't detecting it, or working with the ADB drivers....
I tried at home on my Windows XP and Vista setup, and again wasn't detecting it. However it did detect on my Windows 7 setup at home (triple boot). This must of been the partition I used for my friends one many months ago... (although I found various Kindle related files on each partition).
Anyway, I got the damn thing rooted now, thankfully... and shall move onto the 2nd Bootloader thing... However, is there any other way, or easy way of doing this other than whats in that post?? I don't mind doing it, and will follow it again. However late last night I was losing the will to live as it was hard work getting to do things... (compared to other Android devices that are a breeze to do...).
I tried to backup my partitions on the Kindle what it says to do at the start, and it kept saying it couldnt find these on the Kindle... I read in the guide that it said I could download them from a website, but all I could see was scripts and not backup partitions... Is it really important to backup my own ones, or could I just download someone else's Kindle Fire 2nd (8Gb) model??
And yeah, is there any other way to get custom recovery / rom on, other than the original guide...?? - not gonna give up, just last night kept falling asleep trying to follow it... when things werent working and patiently waiting for things to happen/work... lol
Anyway, thanks so much for replying to my question, and for all the help you have given me to get me started... much appreciated!!
Thanks, Lister
Click to expand...
Click to collapse
As far as i know offhand that method for the kf2 is the only method, which is kinda sad because its the same manual method as the other hd's, and the hd's have fireflash, but fireflash never had the support added in for the kf2 for some reason last i checked. I wouldn't worry too much about the backups, once you run the dd command on the partitions to store them on the sdcard folder, then even if adb pull doesn't work you can always copy them over mtp. i don't like how adb pull works on windows. Only image i would be concerned with storing is the boot0block.
If i made some incorrect references its probably because i vaguely remember it maybe having a different command than the hd model, but the hd's backup command would work on a kf2 as well.
Hi @stunts513,
Just wanted to say THANK YOU SO MUCH!!!
With your help, you have helped me accomplish what seemed like a scary trip to KindleFire Bricks'ville...
But thanks to you, I am all rooted, TWRP'd and ready to go... Shall flash a rom, and sort dads Birthday Pressie now...
Really appreciated, top guy!! thank you... Lister
stunts513 said:
As far as i know offhand that method for the kf2 is the only method, which is kinda sad because its the same manual method as the other hd's, and the hd's have fireflash, but fireflash never had the support added in for the kf2 for some reason last i checked. I wouldn't worry too much about the backups, once you run the dd command on the partitions to store them on the sdcard folder, then even if adb pull doesn't work you can always copy them over mtp. i don't like how adb pull works on windows. Only image i would be concerned with storing is the boot0block.
If i made some incorrect references its probably because i vaguely remember it maybe having a different command than the hd model, but the hd's backup command would work on a kf2 as well.
Click to expand...
Click to collapse
Rooting KF2
Can you give a list of the links that you used to root you KF2?
I've tried to connect to my with ADB but I can't get it to see my device. I can connect my KF2 to my WINXP machine, and transfer files, but I can't get ADB to recognize the device, and I can't get any root options to work. Any help would be appreciated. Ultimately I would like to install a new ROM like CM, but until I can do the basics, I can't get that done.
You should check to see if it has the driver installed for adb in the device manager, if it doesn't even show up as a adb device in device manager you probably haven't turned USB debugging on on the kindle itself.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You should check to see if it has the driver installed for adb in the device manager, if it doesn't even show up as a adb device in device manager you probably haven't turned USB debugging on on the kindle itself.
Click to expand...
Click to collapse
Checked and verified that USB debugging is in fact turned on on my kindle.
Settings>>Security>>Enable ADB is ON.
Settings>>Device>>Allow Installation of Applications is ON
I still can't get adb to recognize my device.
I installed ADB from adt-bundle-windows-x86-20140321.zip if that makes any difference.
I had read in the forums that I might need a special cable for fastboot. Is that what I'll need to get?
For what it's worth, I just found and followed this tutorial:
EDIT: Well crap, this forum won't let me post the outside url. I guess if you search for "Setting up ADB driver for Kindle Devices" by David Isbitski" on developer dot amazon dot com, you will be able to find the tutorial
It was very helpful, and it was the first tutorial I've found that actually showed how to install adb windows drivers for the kindle fire.
In windows Device Manager >> Portable Devices >> Kindle is installed, then uninstall Kindle, as they are the wrong drivers.
In the SDK Manager
Go to TOOLS >> Manage Add On Sites
Go to the User Defined Sites tab
add the url found in the tutorial listed above, save and quit that window.
Back at the manager, do "Packages >> Reload" to update the list.
For the kindle fire 2nd generation, I had to expand "Android 4.0.3 (API 15) to find and install:
"Kindle Fire 2nd Generation"
Under Extras, install:
Amazon AVD Launcher (Windows)
Kindle Fire Device Deffinitions
Kindle Fire USB Driver
Once installed go to \extras\amazon\kindle_fire_usb_driver and run "KindleDrivers.exe"
You should then find "Device Manager >> Kindle Fire >> Android Cmposite ADB Interface"
You can then stop/start adb, then do a adb devices.
That is what worked for me!
New to the forum and trying to recognize what you are doing here......
I have a Kindle Fire 2nd Gen with 10.4.8 SW installed. Would like to dump a much newer Android version on it and looking for the correct path.
Any help is greatly appreciated.
Thanks