[Q] Wrong bootloader used -looks dead -is it a true brick? - 7" Kindle Fire HD Q&A, Help & Troubleshooting

I used a fastbook cable and followed the instructions for jem not tate (which I do have) e.g. (URL removed )which uses:
kfhd8-u-boot-prod-8.1.4.bin, kfhd8-twrp-2.7.0.0-recovery.img & kfhd8-freedom-boot-8.4.6.img
I found the text a bit misleading (ok I missed the very beginning) as it talks about tate in the tutorial. So I should have used:
kfhd7-u-boot-prod-7.2.3.bin, kfhd7-twrp-2.7.0.0-recovery.img & kfhd7-freedom-boot-7.4.6.img
So I get nothing from the device screen and no devices on PC. It get warm but no fastboot mode and nothing with std cable either.
Just checking there's nothing else to do. The 1st gen had a short pin option but that's not the case for HD. Can I hook up a USB reader somehow and boot of an SD card?
Ta.

Related

[Q] Can't get fastboot on Mac to see droid a855's.

I am using a MacBook (OS 10.6.8) with fastboot installed. It works when I use it with a Kindle Fire. I have not one, but three, factory cables, all of which (1) work with the Kindle Fire and (2) seem to work with my two broken-touchscreen a855 droids. I'm pretty sure that I've been able to get the droids into fastboot mode with the factory cable (and, in one case, without it) since (a) the info shown for the droids by System Profiler on the MacBook is very different when I boot with the factory cable (or boot holding down the volume down button) than what it is when I boot normally and connect with a normal cable and (b) I can boot with the factory cable without the battery installed.
But when I run fastboot the way I successfully run it to access the Kindle Fire, it doesn't recognize that the Droid is there. I've tried:
Code:
fastboot devices
fastboot -i 0x22b8 reboot
fastboot -i 0x22b8 reboot-bootloader
fastboot -i 0x22b8 getvar product
and all of the last three without '-i 0x22b8' as well.
It hangs either with no message or with the line:
< waiting for device >
until I press ^c, and sometimes I actually have to close the Terminal window to get out of it.
Is there something different I need to do to get fastboot on the Mac to recognize the Droids?
BTW, I can't use adb yet on these Droids because, without touch, I can't get to the setting to 'allow USB debugging'. Or is there a way to navigate the settings using the keyboard? (I would also need a way to get past the locked startup screen.)
CORRECTION noted on 2012/10/03: My point (a) above is only true in a certain situation. At times, perhaps depending on the battery status, and not when using a factory cable, System Profiler will show one of my Droids as SE Flash OMAP3430 MI rather than as Motorola A855, and the screen of the Droid will show, in plain white text on black:
Code:
Bootloader
2C.7C
[farther down:]
Battery OK
OK to Program
Transfer Mode:
USB
[With cable disconnected, the last two lines become:]
Connect USB
Data Cable
The A855 Droid does not support fastboot. If you're trying to flash a new image it either has to be done through a custom recovery or by using RSD Lite.
Isn't the A855 the same as the 'Droid 1'?
Dave Lister said:
The A855 Droid does not support fastboot. If you're trying to flash a new image it either has to be done through a custom recovery or by using RSD Lite.
Click to expand...
Click to collapse
Isn't the A855 the same thing as the Droid 1? If it is, then it is included in user SkOrPn's list of devices for which his factory cable works. Since he has probably sold hundreds of such cables, he would almost certainly know by now if he's wrong about that.
It's possible that I'm wrong about the identity of the A855 with the Droid 1. But if I'm not, my next guess is that you are wrong about the A855 not supporting fastboot. What are your sources for that assertion?
aarons510 said:
Isn't the A855 the same thing as the Droid 1? If it is, then it is included in user SkOrPn's list of devices for which his factory cable works. Since he has probably sold hundreds of such cables, he would almost certainly know by now if he's wrong about that.
It's possible that I'm wrong about the identity of the A855 with the Droid 1. But if I'm not, my next guess is that you are wrong about the A855 not supporting fastboot. What are your sources for that assertion?
Click to expand...
Click to collapse
The A855 is the Droid 1. What a factory cable allows you to do w/ an A855 is power the device even when the battery is dead due to the device only charging when the phone is fully booted, not in recovery or bootloader modes. I am my own source for this, as I have owned an A855 since it was released in November 2009 and was on the DroidMod ROM team for a time. The phone simply does not support fastboot.
Thanks for the clarification. I have downloaded RSD Lite 5.7 from tucows, but I have no idea what to do with it! (It's a zip file, but the contents is a single file with the .msi extension, which probably means I'll have to borrow access to a windoze machine to run it. I have and use a Mac.) Can you point me to a guide or the most compact compendium of info on using RSD Lite (or not having to use it!) that you know about that I can refer to without getting lost in hundreds or thousands of posts?
BTW, can I do these things without having a functioning touch screen? I already have one new digitizer ready to install, but I'd rather not install it until I have a good idea that the Droid will work reasonably well with it.
Finding an RSD Lite alternative for Linux/Mac took about 2 seconds of googling: http://www.atrixforums.com/forum/mo...h-any-sbf-file-without-rsdlite-mac-linux.html
And you don't need a working touchscreen for flashing RSDs or Custom Roms.
I had forgotten about the Linux/Mac alternative to RSD Lite. To put the phone into bootloader mode, press and hold "up" on the D-pad and then turn on the phone. You can then flash any .sbf file intended for the A855. I believe there are still some floating around that only flash a custom recovery image, which you can then use to install a new ROM off the SD card. Navigation in recovery is done w/ the power and volume buttons.
I've had some limited success. I downloaded sbf_flash, added .sh to the name and made it executable, then downloaded "VZW_A855_FRG01B_QSC6085BP_C_01.43.01P_SW_UPDATE_01.sbf" (a.k.a. 'FRG83G') from Peter Alfonso's site. I managed to get each of my two broken-touch droids (ignoring a third one I have with a broken USB/charge port!) into the mode with 'OK to Program' on the screen, and ran 'sudo ./sbf_flash.sh *.sbf' from the directory containing the two downloads. This got both of them into a state where I was supposed to 'touch' a green android, but couldn't, so I don't even know what ROM I have installed and whether it is rooted or not.
Any suggestions as to what further testing I can do on these Droids before deciding which to take apart and install the new digitizer on? Any way to get into USB Debugging mode without navigating with a touch screen?
BTW, one of the Droids also has a very unreliable (i.e., nearly useless) power button, so I got that one into the bootloader mode by (1) removing the battery, (2) connecting a factory cable to the Droid and then to the computer while holding down the 'up' button on the D-Pad, and (3) replacing the battery. Then I removed the factory cable and replaced it with a standard one before running sbf_flash. (Maybe I could have done it with the factory cable left in, but I didn't try.)

[Q] Unbrick Kindle Fire HD 8.9 without a factory cable?

I made some changes to the build.prop and rebooted, and now it gets stuck at the Kindle Fire boot animation. I can't get it to boot into safe mode either. Is there a way to unbrick or restore it without a factory cable? I can't get it to show up with adb.
If there's no way, I could probably make a factory cable, but it would be nice to fix it without having to do that.
FroyoShark said:
I made some changes to the build.prop and rebooted, and now it gets stuck at the Kindle Fire boot animation. I can't get it to boot into safe mode either. Is there a way to unbrick or restore it without a factory cable? I can't get it to show up with adb.
If there's no way, I could probably make a factory cable, but it would be nice to fix it without having to do that.
Click to expand...
Click to collapse
Yes there is a way to get the 8.9 into fastboot so you can restore it without a factory cable, as a factory cable does not work on this device.
Power down the device and unplug
Open a cmd prompt where you have access to the fastboot script from SDK
Enter this command (or any fastboot cmd as long as you include [-i 0x1949]:
Code:
fastboot -i 0x1949 getvar product
It will say "waiting for device"
Plug in the device and it will automatically boot into fastboot.
I have confirmed this works works when the device is in a loop and adb is not recognized. This does not work on the other models, a factory cable is required. Once in fastboot you can flash a backup image. I will be posting an update to the KFHD SRTool in the development section this morning to include 8.9" version
onemeila said:
Yes there is a way to get the 8.9 into fastboot so it can you can restore it without a factory cable.
Power down the device and unplug the device.
Open a cmd prompt where you have access to the fastboot script from SDK
Enter this command:
Code:
fastboot -i 0x1949 getvar product
Actually any fastboot command works
It will say "waiting for device"
Plug in the device and it will automatically boot into fastboot.
I have confirmed this works works when the device is in a loop and adb is not recognized. This does not work on the other models, a factory cable is required. Once in fastboot you can flash a backup image. I will be posting an update to the KFHD SRTool in the development section this morning to include 8.9" version
Click to expand...
Click to collapse
Tried that... The command you said just shows the help list, if I do a different fastboot command it says waiting for device and then the Kindle boots normally and gets stuck at boot animation like usual.
FroyoShark said:
Tried that... The command you said just shows the help list, if I do a different fastboot command it says waiting for device and then the Kindle boots normally and gets stuck at boot animation like usual.
Click to expand...
Click to collapse
Are you sure you typed that command correctly because the help menu comes up if a command is entered wrong, I just did it and it worked fine. When you enter a fastboot command for this device it has to have the- [-i 0x1949] after fastboot, that is a zero not an O. If that is not done it will boot normally
ie:
fastboot -i 0x1949 [command]
I've posted the update for the 8.9 restore tool in development section
It could be because I have an older version of fastboot. Any chance you could upload the newest version for me?
FroyoShark said:
It could be because I have an older version of fastboot. Any chance you could upload the newest version for me?
Click to expand...
Click to collapse
Here you go:
https://docs.google.com/folder/d/0B4lZEJI5lYeMdzJobG5jSk9QSEk/edit
If you need to restore the system image though, you should just download the KFHD_SRTool from development section for 8.9 and follow the instructions. It has fastboot included in the tool.
I've done the same thing with my kindle fire hd 7 (7.2.2 rooted, no TWRP), now its just stuck on the boot animation.
adb does not recognize the device. I tried using fastboot, (with the normal usb cable), it gets stuck with the '<waiting for device>' message.
The device manager does show the Kindle, but earlier it used to show 2 devices, a kindle and an adb composite
Were you ultimately able to solve this issue?
rogue07 said:
I've done the same thing with my kindle fire hd 7 (7.2.2 rooted, no TWRP), now its just stuck on the boot animation.
adb does not recognize the device. I tried using fastboot, (with the normal usb cable), it gets stuck with the '<waiting for device>' message.
The device manager does show the Kindle, but earlier it used to show 2 devices, a kindle and an adb composite
Were you ultimately able to solve this issue?
Click to expand...
Click to collapse
Turns out, it was a driver issue. Installed the proper Amazon driver, then it was detected by the adb. From there on, I was able to replace the bad build.prop with my backup
onemeila said:
Yes there is a way to get the 8.9 into fastboot so you can restore it without a factory cable, as a factory cable does not work on this device. <snip>
Click to expand...
Click to collapse
My Kindle Fire 8.9" SW v.8.1.4 is completely dark and unresponsive as the result of an unsuccessful attempt to root using KF utility 0.9.6. I suspect results would have been different if I'd had the sense to locate your tool and use it instead. Having downloaded KFHD for v8.1.4, I have tried to get the tool talking with the brick, and see only < waiting for device > eternally. I have charged overnight, held the power button down for >20 sec. to make sure the device was off, then bumped the power button. This should assure that the device is on, but in Amazon's wisdom there are no LEDs to confirm this. Do you have any suggestions for getting the device in a communicative state? I am perfectly willing to open the case. Please forgive the post if this is not the right thread for it, and point me to the right spot if you can.
Same problem: KF 8.9" completely dead
jimbobboy said:
My Kindle Fire 8.9" SW v.8.1.4 is completely dark and unresponsive as the result of an unsuccessful attempt to root using KF utility 0.9.6. .
Click to expand...
Click to collapse
I have exactly the same problem. This KFU-version seems to be a real KF 8.9"-killer.
My device does not respond to anything, regardless what I tried. Connecting to a PC does not trigger any response. The device is not recognized by the PC in any way. I believe that there is no USB-communication at all. I tried a factory-mode cable and this didn't work, too.
Any help would be appreciated, really!
Thanks and regards
Conny
onemeila said:
Yes there is a way to get the 8.9 into fastboot so you can restore it without a factory cable, as a factory cable does not work on this device.
Power down the device and unplug
Open a cmd prompt where you have access to the fastboot script from SDK
Enter this command (or any fastboot cmd as long as you include [-i 0x1949]:
Code:
fastboot -i 0x1949 getvar product
It will say "waiting for device"
Plug in the device and it will automatically boot into fastboot.
I have confirmed this works works when the device is in a loop and adb is not recognized. This does not work on the other models, a factory cable is required. Once in fastboot you can flash a backup image. I will be posting an update to the KFHD SRTool in the development section this morning to include 8.9" version
Click to expand...
Click to collapse
OMG, man. You just saved my ass. Thank you SO MUCH for that info. I threw a "thanks" your way for that one. If I had some ebay money in my paypal I would've even donated I'm so happy. Thanks again. you made my day!
jimbobboy said:
My Kindle Fire 8.9" SW v.8.1.4 is completely dark and unresponsive as the result of an unsuccessful attempt to root using KF utility 0.9.6. I suspect results would have been different if I'd had the sense to locate your tool and use it instead. Having downloaded KFHD for v8.1.4, I have tried to get the tool talking with the brick, and see only < waiting for device > eternally. I have charged overnight, held the power button down for >20 sec. to make sure the device was off, then bumped the power button. This should assure that the device is on, but in Amazon's wisdom there are no LEDs to confirm this. Do you have any suggestions for getting the device in a communicative state? I am perfectly willing to open the case. Please forgive the post if this is not the right thread for it, and point me to the right spot if you can.
Click to expand...
Click to collapse
Add another brick to the pile. Fire HD 8.9. Already rooted, OTA defeated, and Google App'd, but wanted the security of FFF just in case. Planned to used KFU 0.9.6 to set fastboot and then push FFF 1.4a once in fastboot. Instead, used KFU 0.9.6 to automatically install FFF. It appeared that KFU pushed FFF and then sent a reboot. The machine never came back to life after that shutdown.
Attempting to get into fastboot results in eternally <waiting for device>
I removed the back - there are no obvious 'fastboot' pads on any of the boards as there is for the HD 7".
Does anyone think that a factory cable would get this thing's attention? edit...apparently not. http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
edit 2...built a factory cable and tried fastboot, KFHD Recovery tool, KFFirstAide, KFU, and Linux Fire Kit. Nothing can see the device on the other end of the USB cable.
Well...there's always a 'motherboard' swap. Sigh.
Another one bites the dust...but hopefully not
Hi guys,
I tried the KFFirstAide tool to root my Fire 8.9, but after it ran, it just wipes red and then goes to the fastboot screen after powering up. I've used the KFHD SRT tool to replaced the system.img file, but still the same thing happens. Is it possibly because I need to restore the boot.img and recovery.img (which KFFirstAide overwrites) as well? And if so, does someone have a clean copy of those that will work with 8.1.4? Thanks!
George
KFHD_SRT
anyone have a working link for KFHD_SRT? i can get into TWRP and into fastboot mode, but simply trying to boot results in a black screen after the blue kindlefire logo
Wait don't do it!
Slimepuppy said:
Add another brick to the pile. Fire HD 8.9. Already rooted, OTA defeated, and Google App'd, but wanted the security of FFF just in case. Planned to used KFU 0.9.6 to set fastboot and then push FFF 1.4a once in fastboot. Instead, used KFU 0.9.6 to automatically install FFF. It appeared that KFU pushed FFF and then sent a reboot. The machine never came back to life after that shutdown.
Attempting to get into fastboot results in eternally <waiting for device>
I removed the back - there are no obvious 'fastboot' pads on any of the boards as there is for the HD 7".
Does anyone think that a factory cable would get this thing's attention? edit...apparently not. http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
edit 2...built a factory cable and tried fastboot, KFHD Recovery tool, KFFirstAide, KFU, and Linux Fire Kit. Nothing can see the device on the other end of the USB cable.
Well...there's always a 'motherboard' swap. Sigh.
Click to expand...
Click to collapse
I hope you didn't swap motherboards... Like user onemeila stated, you do not need a fastboot cable on the Kindle Fire HD 8.9. Just make sure that before you enter the command "fastboot -i 0x1949 getvar product" that your Kindle is off and plug into the factory cable. Enter the command and wait for the message <wating for device>. Then turn on your kindle and you should boot into fastboot mode. If you see the fastboot screen on your kindle and Jem-PVT-Prod-04 in the command terminal, there is hope. The only problem I encountered is after each command, sometime it won't respond. So you might have to do one command, let it finish it's process. If the next one doesn't work, turn off the kindle enter "fastboot -i 0x1949 getvar product" command. Turn on the kindle and proceed with the next command to restore your kindle.
The way the device is setup, it's very hard to completely ruin the device.
Also read this page for reference by hashcode http://forum.xda-developers.com/showthread.php?t=2128175 and make sure to thank him. He helped me get my device going no problem. The top and bottom of the page should apply to you. If you need additional help let me know.
Slimepuppy said:
Add another brick to the pile. Fire HD 8.9. Already rooted, OTA defeated, and Google App'd, but wanted the security of FFF just in case. Planned to used KFU 0.9.6 to set fastboot and then push FFF 1.4a once in fastboot. Instead, used KFU 0.9.6 to automatically install FFF. It appeared that KFU pushed FFF and then sent a reboot. The machine never came back to life after that shutdown.
Attempting to get into fastboot results in eternally <waiting for device>
I removed the back - there are no obvious 'fastboot' pads on any of the boards as there is for the HD 7".
Does anyone think that a factory cable would get this thing's attention? edit...apparently not. http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
edit 2...built a factory cable and tried fastboot, KFHD Recovery tool, KFFirstAide, KFU, and Linux Fire Kit. Nothing can see the device on the other end of the USB cable.
Well...there's always a 'motherboard' swap. Sigh.
Click to expand...
Click to collapse
You are pretty much screwed. Sorry to tell you. You've flashed over the bootloader, the problem is with one that doesn't work. So your device won't even boot into fastboot no matter what you do. There was a way to do it on the original KF by removing the back and grounding the usb boot pad, then you could usbboot cmds to install the bootloader. But I'm not sure if it will work or ever been tested on this device. Good Luck, look on the bright side you can turn it into an extremely thin planter box, that still serves no purpose
well
I didnt read everything carefully but succeded in rooting my KHFD 8.9"
then i tried to install FFF using KFU and then it restarted and i couldnt power it on
well i have tried using FireKit .. but it says waiting for OMAP device..
then i wanted to do the shorting trick !!
i have searched for two days and couldnt find any where the how to USB shorting of KHFD 8.9
please help I am getting frustrated..
Sent from my GT-N7100 using xda app-developers app
In total desperation I had opened my KHFD 8.9
But sadly I couldnt do anything to unbrick it
If anybody knows about hardware I can share photos of hardware
And may someone can be able to tell how to unbrick it or do fastboot
Sent from my GT-N7100 using xda app-developers app
onemeila said:
You are pretty much screwed. Sorry to tell you. You've flashed over the bootloader, the problem is with one that doesn't work. So your device won't even boot into fastboot no matter what you do. There was a way to do it on the original KF by removing the back and grounding the usb boot pad, then you could usbboot cmds to install the bootloader. But I'm not sure if it will work or ever been tested on this device. Good Luck, look on the bright side you can turn it into an extremely thin planter box, that still serves no purpose
Click to expand...
Click to collapse
Thanks onemeila - confirmation is good. Unfortunately, this is not a tax deductible education expense... :laugh:
Thanks for your KFHD SRT, by the way - I'm using it nearly weekly.
Andy
Kindle turn of eterny
Slimepuppy said:
Add another brick to the pile. Fire HD 8.9. Already rooted, OTA defeated, and Google App'd, but wanted the security of FFF just in case. Planned to used KFU 0.9.6 to set fastboot and then push FFF 1.4a once in fastboot. Instead, used KFU 0.9.6 to automatically install FFF. It appeared that KFU pushed FFF and then sent a reboot. The machine never came back to life after that shutdown.
Attempting to get into fastboot results in eternally <waiting for device>
I removed the back - there are no obvious 'fastboot' pads on any of the boards as there is for the HD 7".
Does anyone think that a factory cable would get this thing's attention? edit...apparently not. http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
edit 2...built a factory cable and tried fastboot, KFHD Recovery tool, KFFirstAide, KFU, and Linux Fire Kit. Nothing can see the device on the other end of the USB cable.
Well...there's always a 'motherboard' swap. Sigh.
Click to expand...
Click to collapse
I have the same usse and i don0t know what to do. I made my own factory usb but nothing happens. I don't find the way to fix it... some can help me?

I Think I Hard-Bricked my Kindle Fire HD 7"

Help! I successfully rooted my Kindle Fire HD 7" following your tutorial "[ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version", and then installed Google Plays etc. following "[ROOT][HOW TO] Install Google Play Store Noob (Simple) Version". I then got to the "[How to] Install Go Launcher EX and HD Noob (Simple) Version" tutorial, and everything went down hill from here.
After following the instructions of tutorial 3, and error message popped on my screen saying that "October has Stopped" and my device froze. I held down the power button, but my device wouldn't boot up - instead it went to a screen with a "Red Warning Triangle". I tried everything from this screen to reboot/reboot my device, all to no avail. Eventually the battery died.
I was able to my Kindle Charged again using the wall charger. However, when plugging into my computer via USB, it doesn't appear on my list of devices. Thus, tools such as KF First Aide are of no help; they cant't communicate with my device, and get stuck on the "<waiting for device>" message.
Any advice?
Can I fix this? How Is my Kindle Fird HD 7" dead forever?
dim_opoulos said:
Help! I successfully rooted my Kindle Fire HD 7" following your tutorial "[ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version", and then installed Google Plays etc. following "[ROOT][HOW TO] Install Google Play Store Noob (Simple) Version". I then got to the "[How to] Install Go Launcher EX and HD Noob (Simple) Version" tutorial, and everything went down hill from here.
After following the instructions of tutorial 3, and error message popped on my screen saying that "October has Stopped" and my device froze. I held down the power button, but my device wouldn't boot up - instead it went to a screen with a "Red Warning Triangle". I tried everything from this screen to reboot/reboot my device, all to no avail. Eventually the battery died.
I was able to my Kindle Charged again using the wall charger. However, when plugging into my computer via USB, it doesn't appear on my list of devices. Thus, tools such as KF First Aide are of no help; they cant't communicate with my device, and get stuck on the "<waiting for device>" message.
Any advice?
Can I fix this? How Is my Kindle Fird HD 7" dead forever?
Click to expand...
Click to collapse
Yes you can fix it,In Fact, You need to have done a lot worse than that to completely fry your kindle, Don't worry, But you will need a factory cable now, Do you have one?
If you don't you can either
A) Order one from SkOrPn
B)Make one yourself, It's easy if you know how to solder
Once you acquire i'll tell you how to completely restore your kindle!
Yes he is right. You can order a factory cable from prokennexusa by PM.
Sent from my KFTT using xda app-developers app
AmrBanawan said:
Yes you can fix it,In Fact, You need to have done a lot worse than that to completely fry your kindle, Don't worry, But you will need a factory cable now, Do you have one?
If you don't you can either
A) Order one from SkOrPn
B)Make one yourself, It's easy if you know how to solder
Once you acquire i'll tell you how to completely restore your kindle!
Click to expand...
Click to collapse
Thanks. I am ordering a factory cable asap. Once it arrives, however, what do I so then?
If u got any Samsung chargers laying around its very easy to make one without solder
Sent from my KFTT using xda premium
dim_opoulos said:
Thanks. I am ordering a factory cable asap. Once it arrives, however, what do I so then?
Click to expand...
Click to collapse
The simplest tool that can restore your kindle would be
KFHD System.img Restore Tool KFHD SRT
All you need to do is download this tool
KFHD_SRT_v1.2.3- 7.2.3
This is a large download, System images are ~600Mb
Originial Thread
http://forum.xda-developers.com/showthread.php?t=1951254
Open SR Tool.bat
choose option 1
Or option 2 if you would like to have Go launcher or Apex launcher installed along with it, And google play store!
The tool will send the system image to your kindle, This will take about 7 minutes
Next, you should choose option 3 to wipe cache and userdata, This is recommended but not required, You will lose any files you transferred to your kindle, You don't need to do this if you want to keep your files!
If you need help just ask
:good::good:Good Luck:good::good:
UPDATE
I wanted to update everyone on my situation. I followed the threads advice - and it worked!
Specifically:
1. I ordered a factory cable from SkOrPn - got it in 3 days after placing order (shibby!).
2. I charged my device by plugging it into wall charger.
3. I installed the Kindle Fire ADB drivers on my compter - directions and links can be found on the thread [ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version
4. I installed the toolbox KFHD_SRT_v1.2.3- 7.2.3 - from the thread KFHD System.img Restore Tool KFHD SRT
5. I plugged my device into PC USB port using the factory cable - it immediately went into fastboot.
6. I used KFHD_SRT_v1.2.3- 7.2.3 from my pc (SR Tool.bat), followed the instructions, and presto.
dim_opoulos said:
I wanted to update everyone on my situation. I followed the threads advice - and it worked!
Specifically:
1. I ordered a factory cable from SkOrPn - got it in 3 days after placing order (shibby!).
2. I charged my device by plugging it into wall charger.
3. I installed the Kindle Fire ADB drivers on my compter - directions and links can be found on the thread [ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version
4. I installed the toolbox KFHD_SRT_v1.2.3- 7.2.3 - from the thread KFHD System.img Restore Tool KFHD SRT
5. I plugged my device into PC USB port using the factory cable - it immediately went into fastboot.
6. I used KFHD_SRT_v1.2.3- 7.2.3 from my pc (SR Tool.bat), followed the instructions, and presto.
Click to expand...
Click to collapse
How long did it take your kindle to charge? When I plug mine in the wall charger it only turns on for like 5 seconds and that's about it? Also did you use the factory cable to charge or the usb cable that came with the Kindle?
bricked .. red screen
I was able to root my KFHD7 with Root_with_Restore and then Qemu .. rooting seemed to work fine.
I then tried to use Fire Flash app to load Hashcode's freedom boot image and TWRP recovery image.. clicked the flash button, it rebooted to a red screen.
I made myself a fastboot cable, when I plug it in, I see the Fastboot logo on the kindle, but my PC never detects the device.
Not sure where to go from here.
I've downloaded and tried KF2_SRT tool and no go. Also downloaded and tried KFFirstAide .. same deal.
All tools stay on <waiting for device>
remove factory cable after it is in fastboot
compmd said:
I was able to root my KFHD7 with Root_with_Restore and then Qemu .. rooting seemed to work fine.
I then tried to use Fire Flash app to load Hashcode's freedom boot image and TWRP recovery image.. clicked the flash button, it rebooted to a red screen.
I made myself a fastboot cable, when I plug it in, I see the Fastboot logo on the kindle, but my PC never detects the device.
Not sure where to go from here.
I've downloaded and tried KF2_SRT tool and no go. Also downloaded and tried KFFirstAide .. same deal.
All tools stay on <waiting for device>
Click to expand...
Click to collapse
remove factory cable after it is in fastboot mode then plug normal usb cable in it then into pc.
My Kindle Fire is basically like this one mentioned above and I'm in fastboot with the factory cable, but i'm stuck with , <waiting for device> on the tool. It seems as though my drivers can't be installed. Any fix to this.
wj3pic said:
...It seems as though my drivers can't be installed...
Click to expand...
Click to collapse
Can you elaborate on this?
soupmagnet said:
Can you elaborate on this?
Click to expand...
Click to collapse
So, basically.
1) I rooted
2) got google play
3) tried to get twrp with fire flash, and this is where i screwed up
Insted of using hashcode's twrp img i used the actualy twrp (blaze) img. so im in this constant reboot loop thing.
So i got a factory cable and I am in flashboot. I got KFHD recovery tool 1.3.5 and when i click option 1, it says <waiting for device>.
I think this is due to the fact that my drivers are not installed correctly, so i tried to reinstall drivers but it just doesnt seem to be working. My thoughts are, If i can just get my computer to recognize the device we might be ok. but i cant seem to make it do that.
wj3pic said:
So, basically.
1) I rooted
2) got google play
3) tried to get twrp with fire flash, and this is where i screwed up
Insted of using hashcode's twrp img i used the actualy twrp (blaze) img. so im in this constant reboot loop thing.
So i got a factory cable and I am in flashboot. I got KFHD recovery tool 1.3.5 and when i click option 1, it says .
I think this is due to the fact that my drivers are not installed correctly, so i tried to reinstall drivers but it just doesnt seem to be working. My thoughts are, If i can just get my computer to recognize the device we might be ok. but i cant seem to make it do that.
Click to expand...
Click to collapse
Watch this video here to learn how to set up your drivers http://m.youtube.com/watch?v=oaNM-lt_aHw&desktop_uri=/watch?v=oaNM-lt_aHw
You're bootlooping and need to use Kindle Fire First Aide to get your KFHD back to normal. http://forum.xda-developers.com/showthread.php?t=2096888
I used KFFA to get back to 7.2.3 bootloader and used Hashcode's 7.2.3 bootimg and the 2.6.1 TWRP file he lists. This worked great using Fire flash.
Sent from my Amazon Kindle Fire HD using xda app-developers app
KFHD7 turns off after 5 seconds
So I've basically followed all steps here and in numerous other threads, but one problem still persists: the Kindle Fire HD 7 turns off after 5 seconds. If I press the power button, nothing happens. If I plug it into a charger, it'll turn on and display the "Kindle Fire" logo on the screen then turn off after 5 seconds. If I plug it into a USB port, it'll turn on and display the "Kindle Fire" logo on the screen then turn off after 5 seconds. If I plug in the factory cable, it'll turn on and display the "Kindle Fire" logo, then display the "Fastboot Kindle Fire" logo then turn off after 5 seconds. I've left the unit on the charger for hours on end, then attempt to turn it on using the power button or plugging in a normal or factory USB cable and it'll do the same thing, turn off after 5 seconds.
OK you may have a 50/50 shot if its doing this because of a bad boot loader, but it could make things worse and end up in a hard brick if it shuts off mid flash, but if it happened to be something wrong with the battery then you would risk this for nothing, but I'm more inclined to think its the bootloader since it doesn't warn u of a low battery. If the fastboot device needs its drivers still, try installing the ones in my signature in that small time frame. If u can manage that, get a copy of the boot loader for your device and check the md5sum of the file( very important) and make sure it matches. Once you have that setup, you need to flash the boot loader onto the device, so I would suggest putting the boot loader in the same folder as fastboot.exe and running "fastboot -i 0x1949 flash bootloader bootloaderfile.bin" and let it say waiting for device, then plug you fastboot cable in and see if it will successfully flash within 5 seconds. If things go south it will hard brick though from an incomplete flash so just warning you ahead of time its up to you.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

[Q] A few Q's about factory cable & un-soft-bricking.

Hey all,
So I have few questions about using the factory cable to fix my soft-bricked KFHD. If you want to read what I did to mess it up and what I've tried so far that's here in this thread but the TLDR is that I messed up my rooted kindle, won't boot, won't show up when plugged in (presumably ADB is off now) and so I ordered a factory cable from SkOpRn. I should get my cable today/tomorrow and I had a few questions before I start blundering about like a bull in a china shop. I've tried to read all the relevant threads here but some of the information seems conflicting/unclear. Here are my two clarification questions:
1) As I understand it, by plugging the device in with the factory cable I should be able to force it into a fastboot mode that allows me to issue commands. Assuming this works, do I continue to use the factory cable for the restore process or is the cable just a one-time "plug in" after which I use the standard cable to restore?
2) I was running 7.2.3 before things got messed up, so once I am able to get it to accept fastboot commands do I use kffirstaide to actually do the restore (Option 4: Completely Restore the KFHD 7.2.3)? I'm thinking along the lines of this guide here and using "Option 4" in "Step 16".
I'm probably over-complicating things but I hate to make things any worse by doing something wrong.
Thanks!
MightyBraeburn said:
As I understand it, by plugging the device in with the factory cable I should be able to force it into a fastboot mode that allows me to issue commands. Assuming this works, do I continue to use the factory cable for the restore process or is the cable just a one-time "plug in" after which I use the standard cable to restore?
Click to expand...
Click to collapse
The fastboot cable is just a trigger. It tells the device to start up differently by powering a pin that does not normally have power. Once you see the fastboot screen, I recommend changing back to a normal cable. You really don't want that extra power hanging out ready to wreak havoc if there's any unexpected fault in the cable (especially if you got one from a random person on eBay).
With standard cable.If the device is recognized by adb then you can use this command:
Code:
adb shell su -c "reboot bootloader"
See the status kfHD have fastboot and you can go from there .
psych0phobia said:
The fastboot cable is just a trigger. It tells the device to start up differently by powering a pin that does not normally have power. Once you see the fastboot screen, I recommend changing back to a normal cable. You really don't want that extra power hanging out ready to wreak havoc if there's any unexpected fault in the cable (especially if you got one from a random person on eBay).
Click to expand...
Click to collapse
Agreed once in fastboot u can user standard kindle micro USB cable also if your kindle is recognised in any way by your PC in device manger even if its an unions p unknown device u should be able to voice force install the drivers for it if u need help and this is the case pm me
Sent from my KFTT
I don't know about kffaide but the restore tool in the dev section claims it replaces the boot loader when you flash 7.2.3
Sent from my GT-P3110 using xda app-developers app
Thanks everyone all for the help! In case anyone else stumbles across this thread with a similar problem, let me summarize what I did to fix my KFHD7:
1. I used SkOrPn's factory cable to get the device into fastboot mode (I just plugged it in for a few seconds until fastboot came up and then switched to the standard USB cable).
2. Once in fastboot mode it was detected by my computer with no problems and I could issue fastboot commands.
3. As soon as I could issue commands I took no chances and used kffirstaide to flash 7.2.3. kffirstaide must provide the stock image because it installed and rebooted fine except without root. I do remember seeing somewhere in a dev forum an image of 7.2.3 that came pre-rooted but I couldn't find it easily. Since I had already rooted it once before it was no big deal to root again.
I can't believe I went from a soft-brick (not even being detected via usb) back to normal so easily! Thanks again for all the help and suggestions!

[Q] Damaged Recovery Partition

Heyo! I was looking to install TWRP and 2nd bootloader when i noticed the device wasnt taking any files. i hit option 9 on kffirst aide,(fastboot checker) and it told me to look for any warning triangles.
ht.tp://puu.sh/aUYZw/a3b809f36c.png ._.
It then told me to make a forum about it.... so hi!
could a factory reset fix a damaged recovery partition? or anything?
I'm not sure what you mean when you say your Kindoe isn't accepting any files. Is it in fastboot? If it isn't, you can use a factory cable (not the one out-of-the-box, a special one you can buy online). If you already have root, you can use an app such as ROM Toolbox to reboot into the "bootloader". KF First Aide probably has an option for this too. ("Reboot into fastboot" or something like that.)
If the Kindle is showing the Kindle Fire logo and the word "fastboot" I believe KF First Aide should recognise it. Try uninstalling the drivers from Device Manager and reboot the Kindle. (In fastboot, make sure you aren't uploading anything through fastboot then press and hold the power button.)

Categories

Resources