Database Develop

[Q] I can't get in to fastboot

I have the Kindle Fire HD 7" and I was able to get into fastboot before without any issue but now I can't get into it no matter what I try. I had my kindle rooted and decided to unroot it since I was going to pass it on to a friend. The plan was to remove everything I put on the kindle, remove all traces of superuser, do a factory settings restore and then to top it off restore a system image I had, just to make sure it was back to stock. Well somewhere in this something must've gone sideways because now I can't get into fastboot. The factory cable doesn't work, trying to launch the bootloader from command line doesn't work. I am at a loss. I don't know where to go from here.. So any and all help would be most appreciated. Help!

jouninred said:
I have the Kindle Fire HD 7" and I was able to get into fastboot before without any issue but now I can't get into it no matter what I try. I had my kindle rooted and decided to unroot it since I was going to pass it on to a friend. The plan was to remove everything I put on the kindle, remove all traces of superuser, do a factory settings restore and then to top it off restore a system image I had, just to make sure it was back to stock. Well somewhere in this something must've gone sideways because now I can't get into fastboot. The factory cable doesn't work, trying to launch the bootloader from command line doesn't work. I am at a loss. I don't know where to go from here.. So any and all help would be most appreciated. Help!
Click to expand...
Click to collapse
First off restoring a system image after you've removed everything else is just going backwards. In order to make the backup image you have the device would have been rooted. So by doing an image restore you are just putting su binary back on the device. To get back to stock- http://forum.xda-developers.com/showthread.php?p=36088426#post36088426.
As for fastboot, in order to reboot into fastboot using adb you have to be rooted, so if you had removed root then that is why that won't work.
The factory cable not working.?, I couldn't say, did you make yourself or purchase it from somewhere?

kindle fire hd 7 adb will not see fastboot
wondering if someone can answer this cmd on windows 8 computer sees kindle as an adb device but when i try to reboot to fastboot it just says waiting for devices can anyone help

Be sure to have ADB drivers for kindle installed on your computer. Be sure ADB is enabled when you swipe down from the top go to More > Security > ADB and be sure it is on.
Sent from my Amazon Kindle Fire HD using xda app-developers app

[Q] Problem with KFHD 7" after factory restore.

Hello,
Let me start by saying I have looked a searched through several other threads but cannot seem to find anything that mimics my problem 100%. I had rooted the Kindle Fire HD 7" a few weeks ago and have been going along with no problem. One day (cannot remember what I installed) the KFHD crashed on me and wanted me to Restore the device in a "download mode" type of screen (used the volume buttons to select restore and power to confirm selection.) The device restarted just fine and was working normally. I went through the KFFirstAide root process again, root checker told me it was rooted. Starting using the options in KFFA to diable OTA, install play store, install google apps, installed Holo Launcher.. Some of the programs did not seem to install properly and didn't like the way things were behaving so I went to the Settings/Device/Restore to Factory Defaults...
After that process finished I am not at an Android setup screen. It has a blue Welcome at the top, select Language below that, Start below that, and a green outlined Android guy below that. When I hit start it says Just a sec.... and eventually get the message Setup Wizard has Stopped.. I can no longer see Kindle Fire ADB in the Device Manger.. Nothing seems to work on KFFA.. I have tried using the fastboot command in a command prompt (says waiting for device) and never does anything..
Basically I would like to know, what steps I may have to take to get the device to load properly again, and hopefully root the device again. IIRC the software version I last saw was 7.3.1...
Thank you for your time and assistance and appologize if it has been discussed before, but I just couldn't seem to find it and not sure what this problem is called to be able to properly search for it..

Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7

Krsmqn said:
Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7
Click to expand...
Click to collapse
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >

When I hold one of the volume buttons and press power on it says Safe Mode at the bottom of the screen. Might there be something I can work with in that? Is there another boot method similar to "download" mode on the GalaxySIII?

jhutch825 said:
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >
Click to expand...
Click to collapse
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".

Is there a way to make on or do I have to order it?

Just ordered a factory cable ... what should I do when I get it?

onemeila said:
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".
Click to expand...
Click to collapse
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken

codepoet82 said:
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken
Click to expand...
Click to collapse
Ok. I will try that forum when it arrives.. To the best of my knowledge, I had not created a backup at any time so I will search out something from the Recovery Thread.
Thank you
-Joe

I am just 100% confused now.. I have searched and searched and everything I am reading is just making me more confused.
The cable will put the device into fast boot and will show up in Device Manager as an ADB Device.. I ran option 3 on KFFA and I don't believe the entire system image downloaded as now I am stuck on a screen with a red triangle asking to reboot or restore the device. Neither option does anything.
I have looked in recovery threads for fresh stock images but only find links and directions to TWRP.. Which, if I understand correctly, needs a 2nd bootloader.. And still will need a fresh stock image from amazon. Also, in KFFA it says to connect the device with a normal cable, not fastboot cable, in ADB mode for TWRP and the second bootloader.. I cannot get into the KF to enable ADB like it asks because I cannot get anything to load..
I have downloaded kfhd7-amazon-os-7.3.1 from goo.im and it comes in a zip file. I am not really sure of what to do..
I looked in the Android Development section of this forum and there are only 18 threads that don't talk about fastboot either. Do I need to go to a general Android Development section, not in the Kindle Fire Forum Sections?
I just want to go back to 100% factory original and start over from there..
Also, the KindleFireFirstAide dropbox seems to be overloaded and suspended, so I cannot get the images from there at the moment through their tool.

jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app

-a- said:
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.

Solved
Found a link, finally, to onemeila's KFHD System.img Restore tool... Used the fastboot cabled and got it installed and everything seems to be running flawlessly.

Same Story Here...
jhutch825 said:
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.
Click to expand...
Click to collapse
Hello, after looking through many, many threads..I have finally found this one. Same story here..I have not order the factory cable. I have the original cable that came with my kindlehd. Before I go and buy the cable I wanted to see if this question can be addressed?

Dnoob, it's been a while don't remember the solution but I did get a factory cable and worked everything out through fast boot
Sent from my Amazon Kindle Fire HD using Tapatalk now Free

[Q] 7.4.6 - two questions

Hello.
After hours of struggling and Googling (and reading mostly from this forum) I managed to root my KFHD 7.4.6 using bin4ry method. I have two questions about where I'm at right now.
Question 1: While struggling to get adb to recognize my KF, I realized that the problem was quite simple: after installing the special adb drivers, I would plug the Kindle back in and Windows would recognize the device and install the Microsoft drivers - completely ignoring the driver I had just installed. The only way I managed to get around this was to quickly interrupt Windows 7's driver installation and tell it to NOT install drivers from Windows Update.
However, I'm sure there must have been a more elegant way of accomplishing this. What would have been the correct way to do this?
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Thanks! :good:

SpidaFly said:
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Click to expand...
Click to collapse
I just found this:
http://forum.xda-developers.com/showthread.php?t=2271909
So the answer to my question appears to be "YES", correct? It appears that I need to flash back to 7.2.3?
Question 1 still remains unsolved.

Well you could downgrade it, I don't know if the latest update causes problems, but the thing that needs downgrading isn't the os, its the bootloader. I suggest the fireflash method in seokhuns tutorial, the one you linked. Just make sure to check the first box at the top in fire flash or you will have a red screen brick, which requires a fastboot cable to fix. Also I have never heard of windows update having drivers for the kindle, I mean I usually hit skip anyways, I believe the more elegant solution may have come with kindle fire first aid, not positive though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Thanks!
I'm having another little inconsistency now.
I disconnect and power off my KF.
I run in cmd: fastboot -i 0x1949 getvar product
It says < waiting for device >
I then plug in my (powered off) KF, and it boots up NORMALLY, and fastboot doesn't return the expected tate-xxx.
Any ideas why?
My ADB is seeing the device. (ie. adb devices is returning one device).

Your fastboot drivers aren't working.

soupmagnet said:
Your fastboot drivers aren't working.
Click to expand...
Click to collapse
Indeed. Can this be solved by wiping existing drivers and reinstalling Amazon's USB drivers from sdk/extras/amazon ?
EDIT: I've attempted reinstall twice with no improvement. ADB works, fastboot won't.

Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?

SpidaFly said:
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?
Click to expand...
Click to collapse
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.

soupmagnet said:
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.
Click to expand...
Click to collapse
Sounds good, thanks. I'm following that tutorial even though it's for 7.4.3, and I'm on 7.4.6. I hope that doesn't cause any issues - but 7.4.6 looks like it's pretty new, so I don't see other options.

Ok - I've followed the aforementioned tutorial precisely up to step 4. When I try to boot the kindle up, it shows orange logo, then blue logo, then looks like it's trying to boot normally, then sends me into TWRP.
Is this what is called "boot loop"?
At this point my PC doesn't see the sdcard so I can't get CM/Gapp copied over.
Would it be safe to push CM & Gapp to the sdcard using adb, then resume with TWRP?
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?

SpidaFly said:
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?
Click to expand...
Click to collapse
This ended up working.
However, now with CM 10.1, my PC isn't recognizing the device for MTP. It still does recognize it as an ADB device, but ADB doesn't see it.

Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Got it working. Basically just uninstalled the existing drivers and reinstalled standard drivers. Works like a charm. I love CM, this is great! Thanks all, for the help!
I'll worry about getting adb going again later.

[Q] Please puh-leeze help me

I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.

Nikaroo said:
I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.
Click to expand...
Click to collapse
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.

soupmagnet said:
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.
Click to expand...
Click to collapse
Thanks for the pointer - I think it got me a tiny bit further. After finding the package and 'fixing' drivers - woo-hoo - my computer is saying that the device is working properly now, I can see it as 'Kindle Fire' in my device manager. However, it still is showing up as 'Tate-PVT-08' under Devices and Printers, and it cannot be found (isn't communicating) with ADB. I feel like I'm missing something so small to be able to move forward and reflash this thing - it's so incredibly frustrating to not be able to find it. :/
I also have tried editing the adb usb file to include the 0x1949, having gone through the adb kill/start-server commands several times, which hasn't changed anything. Is there anything I am missing to get windows and adb to communicate with it? Or is my only option at this point trying 'non-Windows based options'?

You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Click to expand...
Click to collapse
Sooo, I feel even stupider now. I do have KFFA, so I tried to reflash the system image. It went through and gave me a success, although it did have an issue with erasing user data and cache. It said to disconnect from the computer/usb and power down, then restart. I did that and was super hopeful - it went through the boot screen a few more times than normal... but then BAM. Right back to the Kindle Fire System Recovery screen that it can't get past. Ugh. I must have really screwed something up on it.

Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here. Going through that, I checked my hardware IDs, and one of the numbers are off, which according to the guide means that my Kindle isn't in fastboot mode (and this is while using the fastboot cable). If I use a regular USB cable, it doesn't show up at all anywhere. The more I research, the more confused I get. Everything seems geared towards fixing your device if it is stuck in a bootloop (mine goes through that and sticks at the recovery screen) or being able to get it into fastboot, which I cannot seem to do even with the cable. I guess I'm going to try to uninstall and reinstall the drivers for it again, but I'm starting to believe that whatever value I changed while in super user mode before my problems began are going to make it impossible to fix...

The hardware I'd should be 0x1949, and at this point I'm guessing maybe something is wrong with something in the data partition or you have a bad kernel. I don't know how to wipe the data partition from fastboot though. I don't know if kffa reflashes the boot partition, but you could always try that since a system reflash didn't work, or you could try reflashing the system image again, there's another tool in the android development section called kindle fire system restore tool, maybe it will work better for you. Here's the other tool: http://forum.xda-developers.com/showthread.php?t=1951254
Ignore the part about that adb command, that's only for of your kindle can actually boot up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Nikaroo said:
Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here.
Click to expand...
Click to collapse
Be very careful of what guides you use around here. Some of them (fastboot guide in particular) are made with the original Kindle Fires in mind, and can lead you to do irreversible damage.

I'll try that in the morning... I spent most of my day at this and need a break! Thank you so much for trying to help me out. I really appreciate any and all pointers.

kindle can't connect to computer

I flashed a rom not compatible with my device and it bricked it. I later got a fast boot cable and after some research tried to fix it but just made it worse. When I connect it to the the computer it gose to the kindle logo to the fast boot logo to a black screen on the fast boot logo it connects to the computer but then at the dark screen it deconnects. Can someone please help me fix this?

OK so it will briefly go into fastboot mode and is detected by the PC in fastboot mode but then keeps rebooting? I can only assume something is messed JP with either the boot.IMG or bootloader, the good news is it might be fixable, the bad news is if what I want to recommend doing fails you could be left with a hard brick depending on what you flash. I suggest using Ubuntu 13.10 since I thinks its got a faster response time and no issues like installing the fastboot driver when the device is only briefly showing up (as opposed to windows). Then after installing the android-tools-fastboot package from apt or w/e I would recommend attempting to just flash the bootimg of a ROM meant for your ROM, like the freedom boot image or a cm boot.IMG. if you can get it to say flash success full after plugging it in when it says waiting for device, you may have some good results. Since this occurred after a ROM flash attempt I'm thinking this is more likely the bootimg rather than the bootloader. As a test run you could try "fastboot -i 0x1949 getvar product" and see if you can get it to respond. Bootimg bricks are a bit foreign to me, I've heard people say they have hard bricked kindles with bad bootimg's, but that confused me all the note since the bootloader loads either fastboot or the boot.IMG, not to mention I built a ROM and in the testing stages had issues making a suitable bootimg for the kindle and it just made the kindle pop into fastboot mode.
Sent from my Amazon Kindle Fire HD using Tapatalk

kindle connection
stunts513 said:
OK so it will briefly go into fastboot mode and is detected by the PC in fastboot mode but then keeps rebooting? I can only assume something is messed JP with either the boot.IMG or bootloader, the good news is it might be fixable, the bad news is if what I want to recommend doing fails you could be left with a hard brick depending on what you flash. I suggest using Ubuntu 13.10 since I thinks its got a faster response time and no issues like installing the fastboot driver when the device is only briefly showing up (as opposed to windows). Then after installing the android-tools-fastboot package from apt or w/e I would recommend attempting to just flash the bootimg of a ROM meant for your ROM, like the freedom boot image or a cm boot.IMG. if you can get it to say flash success full after plugging it in when it says waiting for device, you may have some good results. Since this occurred after a ROM flash attempt I'm thinking this is more likely the bootimg rather than the bootloader. As a test run you could try "fastboot -i 0x1949 getvar product" and see if you can get it to respond. Bootimg bricks are a bit foreign to me, I've heard people say they have hard bricked kindles with bad bootimg's, but that confused me all the note since the bootloader loads either fastboot or the boot.IMG, not to mention I built a ROM and in the testing stages had issues making a suitable bootimg for the kindle and it just made the kindle pop into fastboot mode.
Sent from my Amazon Kindle
Can you list out a series of steps for me to follow so that I can try it out. If not my kindle doesn't work anyway so o well but please list out some steps and I will try that out.
Click to expand...
Click to collapse

OK I' assuming that at this point you never see the blue logo when you try to boot normally. Go grab copy of system restore tool for your kindle and stick it on a flash drive if you have one, we only need the bootimg it includes. Go grab a Ubuntu 13.10 live CD and either burn it to CD or make a bootable usb. Now boot into Ubuntu live os and copy the boot.img from SRT to the desktop. Now launch a terminal and run these commands:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
cd Desktop
fastboot -i 0x1949 flash boot boot.img
At this point you should be able to plug the kindle in with a fastboot cable when it says waiting for device and see if fastboot will successfully flash the boot partition.
I hope this will fix it, normally such behavior would make me think that the bootloader needs reflashing but a ROM flash shouldn't have touched the bootloader itself so I'm inclined to think its a bad boot image. Also not positive if that apt-get command has the correct package name, I don't have my laptop booted into Linux right now so I can't check, if it says something like "package not found" then tell me and I will look it up, might also be in a repo that's not defaultly enabled on Ubuntu.
Yay I retyped this post, if it doesn't post again I'm going to throw this kindle...
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
OK I' assuming that at this point you never see the blue logo when you try to boot normally. Go grab copy of system restore tool for your kindle and stick it on a flash drive if you have one, we only need the bootimg it includes. Go grab a Ubuntu 13.10 live CD and either burn it to CD or make a bootable usb. Now boot into Ubuntu live os and copy the boot.img from SRT to the desktop. Now launch a terminal and run these commands:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
cd Desktop
fastboot -i 0x1949 flash boot boot.img
At this point you should be able to plug the kindle in with a fastboot cable when it says waiting for device and see if fastboot will successfully flash the boot partition.
I hope this will fix it, normally such behavior would make me think that the bootloader needs reflashing but a ROM flash shouldn't have touched the bootloader itself so I'm inclined to think its a bad boot image. Also not positive if that apt-get command has the correct package name, I don't have my laptop booted into Linux right now so I can't check, if it says something like "package not found" then tell me and I will look it up, might also be in a repo that's not defaultly enabled on Ubuntu.
Yay I retyped this post, if it doesn't post again I'm going to throw this kindle...
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Can you link me to the system restore tool kit I can't find it . Also it said package not found, PLEASE HELP.

Checked on Ubuntu package list and the name was that, still haven't been in Linux to verify it.
Heres the tool, if your on a 7" then this should be what i was talking about: http://forum.xda-developers.com/showthread.php?t=1951254
I will have to check what repo that package is from, because I remember Ubuntu doesn't always have all the default repos enabled, might have to enable it in the manager, would be simpler if it came with synaptic still...
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Checked on Ubuntu package list and the name was that, still haven't been in Linux to verify it.
Heres the tool, if your on a 7" then this should be what i was talking about: http://forum.xda-developers.com/showthread.php?t=1951254
I will have to check what repo that package is from, because I remember Ubuntu doesn't always have all the default repos enabled, might have to enable it in the manager, would be simpler if it came with synaptic still...
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you soon much I will definitely try it out. What is a repo package though and how do I install it to read the command for the fast boot download.

OK put simply ubuntu uses a very nice package management system called apt, it basically connects to repositories set in a file that have tons of precompiled programs and such for that specific version of Ubuntu or more broadly Linux. It retrieves some manifest of all the packages in each repo, each package has a specific name. If you want to use a better interface try typing this, "sudo apt-get install synaptic" then run "sudo synaptic" and you can search for fastboot in the nice visual package manager. Sorry I haven't been in Linux, I have left Firefox running with a form for a job application up waiting for some info I need and I don't want to reboot and have to fill it out again. I will boot my desktop up into Linux tomorrow if I can, I may be going out to do something though.
Sent from my Amazon Kindle Fire HD using Tapatalk

ok i finally rebooted into linux, it turns out teh package is indeed called android-tools-fastboot, so that being the case open up the settings app and click software and updates and everything on the first tab under downloadable from internet should be checked with the slight exception of source code which for me has a line through it when you try to check it off, it should as k you to reload, you can do that or run "sudo apt-get update" again. As long as this is the 13.10 version of ubuntu then it should have that in the repos, i don't think it was in the repos before 13.10.

Thank you so much, what you said worked with my friends kindle who had kinda the same thing happen but the problem with mine is that it can't stay connected to the computer. It connects but then unconnected like 2 seconds after and it can't stay connected or I could fix it . Any suggestions?

Pray that what you did works on his, though I would ask what did he do that made his do that? Because if you can get it into fastboot even briefly, as long as the PC has the fastboot command already running so it says "waiting for device" it should attempt it. Depending on what he did is oukd recommend what I told you, its either the bootloader or the boot image, I don't go for bootloader unless I have to because an incomplete flash on that would be far worse, though the bootloader is quite a bit smaller than the bootimg last I checked so it would take less time to flash. Also is his also the 7” HD?
Sent from my Amazon Kindle Fire HD using Tapatalk

My friend booted into recovery and it bricked it to the logo but what you said worked. With mine my family's getting a new computer so when when we do I will definitely try it out and let you know how it works. And again thank you so o much.

Very good news, what you said worked, my kindle fully connected to the computer in fast boot mode. I was able to install the abd composite drivers to my kindle and it runs fast boot commands. IT is stuck on the fast boot symbol and was wondering if you had a way to reset the kindle, a factory reset that wipes it clean or anything that would make the device work again. Thank you for all your help so far, it is greatly appreciated.

Adam h said:
Very good news, what you said worked, my kindle fully connected to the computer in fast boot mode. I was able to install the abd composite drivers to my kindle and it runs fast boot commands. IT is stuck on the fast boot symbol and was wondering if you had a way to reset the kindle, a factory reset that wipes it clean or anything that would make the device work again. Thank you for all your help so far, it is greatly appreciated.
Click to expand...
Click to collapse
You want to flash factory images through fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
You want to flash factory images through fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you please link me to a website where I can download these images and list some steps for me to follow to flash those.

Kindle fire first aid does it for you as well as SRT, kffa is in the 7" general section. I think I should add links to this stuff in my signature... Maybe I will add them tomorrow.
Edit: here's the link
http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD using Tapatalk