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?
So I was trying to install TWRP to my Kindle Fire HD7. I had successfully rooted and was using FireFlash to flash the bootloader.
When I pressed boot to recovery the device rebooted showed the kindle logo and then a red screen.
I tried making a fastboot cable but could not get the device to show up in ADB devices. Am I totally boned?
I have links to the directions I followed and a gif of the logo and red screen but I cannot post them since I'm new.
I had this issue also, I just made a fastboot cable, plugged it in and flashed stock files, I then rerooted, installed TWRP, 2ND bootloader, then CM11, finally with PAC-rom.
Sent from my Kindle Fire HD 7 running PAC-man
I can can agree with wire55. Have to have a fastboot cable to fix this. Reflashed stock then created my own personal port ROM.
Sent from my Kindle Fire HD running a Personal Ported Rom
I made a fastboot (by jumping pin 1 and 4 on a microusb) cable but it shows the device as disconnected in Device Manager.
Here is what it looks like when I turn it on i.imgur.com/TSUHsjW.gif
you dont use adb commands with fastboot mode, you use fastboot commands with fastboot mode. Try "fastboot -i 0x1949 getvar product" and see if it reports back. If it does all you will need to do is flash the older bootloader for your device first(check the md5sum plz so you don't hard brick), then restore with kffa or srt. Fireflash method should work fine now for sure once you have flashed the older bootloader.
concerning rdwidam
It says <waiting for device>
I will try again tomorrow, my friend is bringing over a fastboot cable that we know is working.
I'll report back if there is progress. Thanks.
stunts513 said:
you dont use adb commands with fastboot mode, you use fastboot commands with fastboot mode. Try "fastboot -i 0x1949 getvar product" and see if it reports back. If it does all you will need to do is flash the older bootloader for your device first(check the md5sum plz so you don't hard brick), then restore with kffa or srt. Fireflash method should work fine now for sure once you have flashed the older bootloader.
Click to expand...
Click to collapse
frakkingcylon said:
It says <waiting for device>
I will try again tomorrow, my friend is bringing over a fastboot cable that we know is working.
I'll report back if there is progress. Thanks.
Click to expand...
Click to collapse
ok that's good, if the command still doesn't respond after it says fastboot mode on the screen, then go to the device manager and look for a device with a yellow triangle next to it, once you find it download my drivers in my signature, extract them somewhere, and right click the device and hit update drivers, point it to where you extracted mine and let it install. If you are on windows 8 you will have to disable driver signature enforcement first.
OK, I got a fastboot cable but still no luck. Nothing shows up in device manager and no response to fastboot commands. I think I'm going to throw my self on the mercy of Amazon.
frakkingcylon said:
OK, I got a fastboot cable but still no luck. Nothing shows up in device manager and no response to fastboot commands. I think I'm going to throw my self on the mercy of Amazon.
Click to expand...
Click to collapse
So the fastboot cable isn't throwing it into fastboot mode, it is staying at a red screen? You are positive the fastboot cable is a fastboot cable? And i have to ask this even though its stupid but you are positive it was a kindle fire hd 7 and not an 8.9"? The fastboot cables don't work on 8.9" models is why i'm asking, those will go into fastboot with the command i mentioned but its slightly more complicated than that, the device would show up for a brief moment then disappear when turned on.
It is possible our fastboot cable is not working. I will try another one today. I measured the kindle and the view-able screen is 7 inches diagonally, while the whole body including the bezel is 9 inches.
stunts513 said:
So the fastboot cable isn't throwing it into fastboot mode, it is staying at a red screen? You are positive the fastboot cable is a fastboot cable? And i have to ask this even though its stupid but you are positive it was a kindle fire hd 7 and not an 8.9"? The fastboot cables don't work on 8.9" models is why i'm asking, those will go into fastboot with the command i mentioned but its slightly more complicated than that, the device would show up for a brief moment then disappear when turned on.
Click to expand...
Click to collapse
Ok, success! I got out my soldering iron and made a working fastboot cable. Now my kindle turns on and shows a fastboot logo on screen, and I have a device called Tate-PVT-08 in Device Manager. So I installed the android drivers to allow me to use fastboot commands. Then I used KFHD_SRT tools to restore the Recovery and Factory image.
Thank you everyone for all your help and knowledge. I was freaking out a bit, but all is well.
Kindle Fire HD 7 1st gen
The title says it all. I was following this - http://forum.xda-developers.com/showthread.php?t=2409435
Followed everything it said.
It stated "If not, wipe all above except for your internal storage (/sdcard) and flash the zip file you downloaded earlier then afterwards, wipe your Internal Storage (/sdcard)."
I asked "Just to be completely clear, if I download the zip to my device, I wipe EVERYTHING BUT the internal storage, then I can flash it, and then wipe JUST the internal storage?"
Instead of waiting for an answer, I just did it. As you can imagine, I have a brick now. No TWRP, no recovery mode, just the static orange "Kindle Fire" logo forever. Nothing happens at all when plugging it into my pc, doesn't even recognize any device being plugged in. Called Amazon, and since it's past the one year warranty mark they won't replace it.
So, I guess I just need someone else to tell me that all is completely lost and there is nothing more I can do so I can move on and stop worrying about it and get some sleep.
That's completely fixable, you just need a fastboot cable to kick it into fastboot mode so you can reflash it. I recommend the blackhat adapter that hashcode mentions in his twrp + second bootloader tutorial.
Sent from my LG-P769 using Tapatalk
stunts513 said:
That's completely fixable, you just need a fastboot cable to kick it into fastboot mode so you can reflash it. I recommend the blackhat adapter that hashcode mentions in his twrp + second bootloader tutorial.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Cool! Thanks for that. I was under the impression that since my pc didn't think anything was even being plugged in that a fastboot cable wouldn't work. I'll definitely try this out!
stunts513 said:
That's completely fixable, you just need a fastboot cable to kick it into fastboot mode so you can reflash it. I recommend the blackhat adapter that hashcode mentions in his twrp + second bootloader tutorial.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Well, got a fastboot cable. It origionally showed up in device manager as an unknown device "tate-pvt-08", so I installed the kindle hd adb drivers, and now it appears in the device manager as Kindle Fire - Android Composit ADB Interface, but when I use adb devices in the cmd window, it always returns "List of devices attached" followed by a blank line.
Tried adb kill-server, and android update adb, but so far no luck. almost seems like there's no device info left on my kindle. Any clue as to what I can do?
BTW, tried this on 2 pcs, first Windows 8, and then Vista
adb commands don't work with fastboot mode, only fastboot commands work with fastboot mode. Ex: fastboot -i 0x1949 getvar product
Sent from my LG-P769 using Tapatalk
stunts513 said:
adb commands don't work with fastboot mode, only fastboot commands work with fastboot mode. Ex: fastboot -i 0x1949 getvar product
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
That makes sense. Thanks for the help/patience.
Now at least I know what to do. I'm currently following this thread http://forum.xda-developers.com/showthread.php?t=1951254&highlight=network+error and at the end of the download, I had a "network error" Currently trying to not scream and destroy things. Trying again from IE instead of chrome, but man <200 KB/sec dl speeds are going to drive me insane.....
If I take anything away from this experience, it's have the right tools, and always make backups.
I'm back in business in factory w/root. now I can sleep again.
My Kindle Fire HD is in a TEMAMWIN ecovery loop. The fastboot cable wont recognize the device for me to reflash the recovey img. What should I do?
jackjohns said:
My Kindle Fire HD is in a TEMAMWIN ecovery loop. The fastboot cable wont recognize the device for me to reflash the recovey img. What should I do?
Click to expand...
Click to collapse
If you're running Windows, install the Kindle drivers from this post. Also run the 15 second ADB installer found here, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle when you see <waiting for device>. If you get a string beginning with "jem" or "tate", then fastboot is recognized. At this point, you should reflash the recovery image. Also type fastboot -i 0x1949 erase system and fastboot -i 0x1949 erase cache. Once those complete, type fastboot -i 0x1949 reboot and try booting into recovery.
monster1612 said:
If you're running Windows, install the Kindle drivers from this post. Also run the 15 second ADB installer found here, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle when you see <waiting for device>. If you get a string beginning with "jem" or "tate", then fastboot is recognized. At this point, you should reflash the recovery image. Also type fastboot -i 0x1949 erase system and fastboot -i 0x1949 erase cache. Once those complete, type fastboot -i 0x1949 reboot and try booting into recovery.
Click to expand...
Click to collapse
Thanks! It worked. Only problem is... It isn't flashing the firmware... And it bricked into a normal over and over "kindle fire" logo. ?
jackjohns said:
Thanks! It worked. Only problem is... It isn't flashing the firmware... And it bricked into a normal over and over "kindle fire" logo. ?
Click to expand...
Click to collapse
Try flashing the second bootloader, freedom-boot, and TWRP images again in fastboot. You should have fastboot access at some point, even if you have to completely turn it off, run fastboot -i 0x1949 getvar product, and plug in the kindle when you see <waiting for device> to get it to boot into the bootloader.
Sent from my Amazon Jem using XDA Labs
It won't flash the boot images, just <waiting for device>
I have no OS, should I flash one and see if it helps?
jackjohns said:
It won't flash the boot images, just <waiting for device>
I have no OS, should I flash one and see if it helps?
Click to expand...
Click to collapse
Sure, but make sure you flash the 2nd bootloader via fastboot immediately after, or you may end up with a bricked device.
Sent from my Amazon Jem using XDA Labs
@monster1612 it is not flashing anything ? what should I do
jackjohns said:
@monster1612 it is not flashing anything ? what should I do
Click to expand...
Click to collapse
First off, you need to disable driver signature enforcement in order to install the Kindle drivers on Windows 10. Here's a tutorial to do just that. After you reboot, install the kindle drivers again, and perform another reboot when prompted.
Also, you can't flash .zip files via fastboot - that would be part of the reason as to why it's stuck. I suggest flashing TWRP, the second bootloader, and the freedom-boot image via fastboot first. Once those are complete, type fastboot -i 0x1949 oem recovery to reboot into TWRP, and then flash the CM ROM zip within TWRP.
Finally, make sure you include the -i 0x1949 parameter in all of your fastboot commands. This will ensure fastboot knows what device you're flashing.
Sent from my Amazon Jem using XDA Labs
@monster1612 thank you I will try that
@monster1612 also, the 7.2.3 uboot is a .bin. Will that work with fastboot? Or will I need it?
jackjohns said:
@monster1612 also, the 7.2.3 uboot is a .bin. Will that work with fastboot? Or will I need it?
Click to expand...
Click to collapse
Yes, it should work with fastboot.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Yes, it should work with fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Now this
jackjohns said:
Now this
Click to expand...
Click to collapse
It looks like the fastboot flashing process isn't working because it's not being told where to flash each image. Go ahead and flash each of those files again as directed by Hashcode in this thread, under step 5. The flashing process should now succeed.
@monster1612 it flashed the uboot, freedomboot, and twrp ok, but the device is still in a bootloop. I even did it twice. What should I do?
@monster1612 now it wont even turn on. I tried fastboot 0x1949 erase system because i was just erasing everything and now it wont even turn on. Maybe it is just out of battery because Ive been at this for a couple of months....
jackjohns said:
@monster1612 now it wont even turn on. I tried fastboot 0x1949 erase system because i was just erasing everything and now it wont even turn on. Maybe it is just out of battery because Ive been at this for a couple of months....
Click to expand...
Click to collapse
I'd let it charge overnight. After that, try fastboot -i 0x1949 idme bootmode 4000 and then fastboot -i 0x1949 reboot. Does that quell the bootloop issue?
@monster1612 it has been plugged in for 45 minutes and isnt turning on. Could it be hard bricked?
jackjohns said:
@monster1612 it has been plugged in for 45 minutes and isnt turning on. Could it be hard bricked?
Click to expand...
Click to collapse
That's odd - try holding the power button down for 10 seconds, then turn it on and see if it boots.
Sent from my Amazon Jem using XDA Labs
Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.
Gospelalex said:
Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.
Click to expand...
Click to collapse
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."
vasolini said:
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."
Click to expand...
Click to collapse
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...
Gospelalex said:
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...
Click to expand...
Click to collapse
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413
vasolini said:
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413
Click to expand...
Click to collapse
Can`t install them - install failed.
Gospelalex said:
Can`t install them - install failed.
Click to expand...
Click to collapse
Got another cable. Was able to get to fastboot. But couldn`t get past it. Device was shown as tate unrecognized. Pushed to install driver and made it recognized by pc. Tried kindle fire utility v099 to run recovery. The kindle gone into reboot. So now it reboots into main loge, then changes into fastboot loge and then going into continuous reboot again. Windows in the same time stop recognize it. Shows it in usb unidentified for a second because it switches on and off again.
Update:
Managed to return it into fastboot. But in cmd when i run adb.exe devices there is nothing.
I know how to fix this problem. I ran into this 10 times before Android Studio suddenly went through my head.
In order to install the Kindle Fire ADB Drivers, you need to download and install the Android SDK Manager from Google Inc. Then when you install those drivers I mentioned earlier, you won't get errors. It's so weird.
You can try using the Ultimate Unbrick Tool, but I forgot the download link for it. There should be a thread about it here on XDA.
Lots of advanced technical stuff. I suck at explaining without making it a very long explanation because then people stop reading after 10 seconds.