Related
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?
hi all
I have a question, I have a Kindle Fire HD 7 with TWRP Recovery everything worked but the application nova launcher disappeared could not delete it or reinstall it so I did a wipe, but lost the root when you try to do it again had problems with coomand SU, with wire factory try doing a factory recovery with my backup.
appered after to restore a red screen and my computer does not recognize any new device
micro usb cable = kindle fire logo and red screen after
factory cable = fasboot logo and not recognize any device
not a problem for drivers is a problem with the tab
any ideas to fix?
tnx
Have you tried everything available to you first? This includes: factory resetting by booting into recovery and doing a whole system wipe, SD card included; see if you're at luck and ADB or fastboot still works by flashing the stock Amazon OS, assuming CMD still recognizes your fastboot.
Other than that, I'm out of options. I'd try to return it and hope for a refund or an exchange. However, you're only dealing with a soft brick, because if it's a hard brick, the whole tablet won't turn on at all, so at least it's not a paperweight at this point. I'd try to reach out to Hashcode or Soupmagnet or Reverendkjr on this forum and ask for help.
Yes, all that and tried
It sounds like your kindle updated to 7.3.0 the boot loader hack doesn't get along with that...read the last few pages in the boot loader three I think you'll fix your problem
Sent from my GT-P3110 using xda app-developers app
SAME HERE PLEASE SOMEONE HELP ME!!! DONT USE KF First Aide tool!!!
Help the same thing has happened to me i need to get in to fastboot mode but i cant
any help would be great
is their a kindle fIre hd recovery tool from amazon as i cant boot up
this was the kf first aid tool that did this to me
There's actually a way I can think of, but I don't know if it will work. As long as you can find the bootloader files for the tablet, you can try to ask someone to JTAG your KFHD7. The process involves taking apart the tablet, using electricity to provide power while re-writing the bootloader so you can end up in fastboot mode. It's not very expensive, a regular Galaxy S3 takes 45-60 bucks and within a week. That's the only thing I have left for y'all.
seokhun said:
There's actually a way I can think of, but I don't know if it will work. As long as you can find the bootloader files for the tablet, you can try to ask someone to JTAG your KFHD7. The process involves taking apart the tablet, using electricity to provide power while re-writing the bootloader so you can end up in fastboot mode. It's not very expensive, a regular Galaxy S3 takes 45-60 bucks and within a week. That's the only thing I have left for y'all.
Click to expand...
Click to collapse
thanks for the reply buddy yeah i guess but i was hoping for a easier way to do it
yes, i searched the diagram but not luck
anyone know where to find it?
napstermisaki said:
yes, i searched the diagram but not luck
anyone know where to find it?
Click to expand...
Click to collapse
So when you plug in your factory cable and power it on it enters fastboot.... correct? But then the computer does not detect the fastboot drivers? I'm a bit confused lol
napstermisaki said:
hi all
I have a question, I have a Kindle Fire HD 7 with TWRP Recovery everything worked but the application nova launcher disappeared could not delete it or reinstall it so I did a wipe, but lost the root when you try to do it again had problems with coomand SU, with wire factory try doing a factory recovery with my backup.
appered after to restore a red screen and my computer does not recognize any new device
micro usb cable = kindle fire logo and red screen after
factory cable = fasboot logo and not recognize any device
not a problem for drivers is a problem with the tab
any ideas to fix?
tnx
Click to expand...
Click to collapse
Have you tried installing kindle first aide tool which can be found on a thread in this forum. I had the same problem with the red screen so I bought a factory cable, directed the computer to the KFF folder and installed the fastboot driver. After that the computer recognised my device and I was able to restore using option 3 of the first aide tool. Hope this helps. Good luck
Sent from my KFTT using xda premium
jmar8124 said:
So when you plug in your factory cable and power it on it enters fastboot.... correct? But then the computer does not detect the fastboot drivers? I'm a bit confused lol
Click to expand...
Click to collapse
jmar8124 is correct, my device enter fasboot mode but the computer no detect device.
Can you send fastboot commands to it? Try "fastboot -i 0x1949 reboot" and see if it reboots. As long as you can send fastboot commands to it, you're good to go.
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
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.
I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!
ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk
History of the issue at hand:
I was running a new rom that was marshmallow based. It was running fine but lost root privileges so I attempted to boot into recovery and install the stable version of SuperSU for the device. I wiped the dalvik and cache and rebooted through TWRP recovery and the system went into a bootloop. Solution: Read XDA forums to find a way to fix the device. Went on ebay and bought a fastboot cable, waited 3 weeks, cable comes in and gets me to fastboot mode, but I am running Windows 10, creating a new problem. Solution: Partition the HDD on my computer and install Windows 7 Professional. This now fixed the driver issue. Plugged in the cable, with the new drivers installed and voila - Fastboot mode.
Seems pretty easy right? Wrong. After trying several utilites, I still cannot seem to get the Kindle to get out of the current situation it is in.
The device was rooted with the 2nd bootloader added over 2 years ago. Every ROM I have ran has been successful. Every time a new ROM was used or tried a backup was done and the device wiped properly before install. I made sure that every ROM was for my specific device (Tate).
Here is what I can do:
If I power on the Kindle, it briefly shows the logo, then the fastboot logo and goes blank
If I power on the Kindle by plugging in the factory cable and quickly entering any command (it is already typed) like "fastboot erase cache" the system will remain in fastboot with the fastboot logo on the screen. My sdk does recognize the device and states it is in fastboot.
From here I have no idea where to go. I can type any command I like, such as erase cache, recovery, system or any multitude of things and the command prompt takes it time to show the device is working on the command. However, the device remains unresponsive and has the same issues when attempting to reboot. When flashing anything the target size of the device remains unchanged at 1006632960 bytes, which seems to tell me that device is receiving the command but not writing anything to the device. This probably also means that anything that is on the device causing it to continuously bootloop or fail is not being erased or properly formatted.
All I have is fastboot and time. Time to scratch my head and wonder if the device is truly and totally bricked. i am under the assumption that if I have a working fastboot that I should be able to at least accomplish something. Even if it means reverting it to bare bones stock and starting the whole process over. I will be happy to answer any questions you all have regarding the system via here or PM.
Please assist this old man and thank you in advance for your time.
Give it a try
While I wasn't in the same weird brick scenario as you. My device would show up on my pc as fastboot and or regular adb. But, I would get no video. The solution which I have no idea why worked was to pop the back cover off. Then disconnect the battery from the mobo. Wait a few seconds. Connect it back to the mobo. After that video showed back up. Then proceeded on my way.
Not sure if what I did will help you. But. Then again I didn't think simply disconnecting the battery and reconnecting it would solve video issues.
You definitely do have a weird brick scenario. Good Luck!