I tried to install CM9 to my kindle, but I didn't realize I was supposed to install TWRP first. I am stuck at the yellow triangle, can't get into recovery (of any sort).
When I plug in the USB cable I type in
Code:
fastboot getvar product
which returns: kindle.
I tried to push TWRP using
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
and it returns: sending 'recovery' (5568 KB) but nothing ever happens.
I have tried draining the battery and recharging it completely. I have been able to get into recovery before by tapping the power button but don't seem to be able to do it anymore.
adb doesn't work at all. I should mention I am on a mac so KFU didn't work for me either.
I promise to be more careful in the future, can someone please help me save my kindle?
Try omitting the "-i 0x1949" from your command and flash it again.
EDIT: While you're at it, download TWRP again and confirm its md5 checksum before flashing it again.
md5 is ok, I tried without the switch as well still nothing
whtmgcwmn said:
md5 is ok, I tried without the switch as well still nothing
Click to expand...
Click to collapse
What recovery did you use to flash CM9 in the first place? What happens when you try to boot into the system?
I'm starting to recall some people having problems with the mac version of fastboot. Do you have another OS available just to compare things?
in my case the commands only return "is <waiting device>"
I had CWM I believe it's still in there somewhere. But I can't get to it anymore. Sometimes I think CM9 is going to start up because I do get the splash screen but it just goes on for like 15 minutes then the kindle restarts and goes back to the yellow triangle of doom.
EDIT: No unfortunately all I have is the mac
nailanb13 said:
in my case the commands only return "is <waiting device>"
Click to expand...
Click to collapse
If you're using Windows, read the first three posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
and make sure your drivers are working properly.
whtmgcwmn said:
I had CWM I believe it's still in there somewhere. But I can't get to it anymore. Sometimes I think CM9 is going to start up because I do get the splash screen but it just goes on for like 15 minutes then the kindle restarts and goes back to the yellow triangle of doom.
EDIT: No unfortunately all I have is the mac
Click to expand...
Click to collapse
I hope you weren't using Hashcode's CWMR...
In any case, I believe I've seen another user struggle with fastboot on the mac. You might be having the same problem, but I can't find that thread. You might want to look into building Ubuntu Linux on a USB stick and try running that on your mac. Otherwise, you'll have to wait for someone who's used those tools on the mac to chime in here. I've never played around with it.
kinfauns said:
I hope you weren't using Hashcode's CWMR...
In any case, I believe I've seen another user struggle with fastboot on the mac. You might be having the same problem, but I can't find that thread. You might want to look into building Ubuntu Linux on a USB stick and try running that on your mac. Otherwise, you'll have to wait for someone who's used those tools on the mac to chime in here. I've never played around with it.
Click to expand...
Click to collapse
I have no idea which CWM I have. I couldn't find the mac fastboot thread either, I guess I will just put it away for now until I get access to a pc.
Looking above there is a good chance twrp sent I'm pretty sure now all you need to do is reset your bootmode
fastboot oem idme bootmode 4000
fastboot reboot
Do you try use factory cable? If not, let factory cable and run command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
chamnv said:
Do you try use factory cable? If not, let factory cable and run command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Click to expand...
Click to collapse
Not to just sit here and tromp on your toes chamnv but the title of this thread is "kindle stuck in fastboot mode but wont accept commands" my impression of a factory cable is that it puts you in fastboot and secondly above he has attempted to send a new recovery why would he then send an old one?
Thepooch said:
Not to just sit here and tromp on your toes chamnv but the title of this thread is "kindle stuck in fastboot mode but wont accept commands" my impression of a factory cable is that it puts you in fastboot and secondly above he has attempted to send a new recovery why would he then send an old one?
Click to expand...
Click to collapse
sorry to laugh but hehehe
whtmgcwmn said:
I tried to install CM9 to my kindle, but I didn't realize I was supposed to install TWRP first. I am stuck at the yellow triangle, can't get into recovery (of any sort).
When I plug in the USB cable I type in
Code:
fastboot getvar product
which returns: kindle.
I tried to push TWRP using
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
and it returns: sending 'recovery' (5568 KB) but nothing ever happens.
I have tried draining the battery and recharging it completely. I have been able to get into recovery before by tapping the power button but don't seem to be able to do it anymore.
adb doesn't work at all. I should mention I am on a mac so KFU didn't work for me either.
I promise to be more careful in the future, can someone please help me save my kindle?
Click to expand...
Click to collapse
Just unplug the KF from the USB, hold the power button and turn it back on. Repeat the process.
fastboot -i 0x1949 flash bootloader <name of firefirefire image here>
fastboot -i 0x1949 flash recovery <name of recovery image here>
Related
I've looked everywhere for an answer to my question and have yet to find an answer. Probably because my Kindle Fire is truly bricked for good. But here is the series of events that lead to my current predicament.
1. I used Kindle Fire Utility 0.9.1 to root and install TWRP.
2. I was ignorant of the uses of TWRP so when I wanted to restore the Kindle to factory settings I did it within the kindle.
3. I ended up in TWRP so I looked up how to force the amazon update to the kindle. I cleared both caches and factory restore and then installed update.zip.
4. When I rebooted I am now stuck on the boot up screen with no access to TWRP. My computer still recognizes the kindle fire, but I can't access the directory of the kindle.
5. I've tried to use fastboot, Kindle Fire Utility, and anything else to knock it out of the boot logo, but I always am stopped by the error: exec "system/bin/sh": No such file or directory
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
b63 said:
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
Click to expand...
Click to collapse
I´m in the same situation. We can´t use kfu because everyrthing it does needs adb shell, wich isn´t working.
I´d love to be wrong, but the only solution we have is getting a factory cable.
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
b63 said:
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
Click to expand...
Click to collapse
The problem is we are not in fastboot mode. We have normal boot enabled.
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
b63 said:
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
Click to expand...
Click to collapse
Thanks, but it doesn´t work. Factory cable is the last hope.
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
qv775219 said:
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
Click to expand...
Click to collapse
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
osozraz said:
It reboots the device but not to recovery.
Click to expand...
Click to collapse
It looks like flashing the stock rom erases FireFireFire and recovery
osozraz said:
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
It looks like flashing the stock rom erases FireFireFire and recovery
Click to expand...
Click to collapse
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
(Recovery image needs to be named recovery.img)
After flash is done
./fastboot reboot recovery
If have issues from fastboot, reboot the device and from bootloop screen
./adb reboot recovery
qv775219 said:
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, thank you very much for your help.
I type
adb reboot bootloader
and the device reboots, but
fastboot flash recovery recovery.img
gives the same result as before
< waiting for device >
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
b63 said:
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
Click to expand...
Click to collapse
If I am not mistaken, to execute fastboot you have to boot in fastboot mode. My fire is always booting in Normal mode so all fastboot commands i execute have the same result:
< waiting for device >
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
edit2: just for info: kfu uses this to switch to fastboot:
adb shell "idme bootmode 4002"
adb shell "reboot"
don't think that this works
b63 said:
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
Click to expand...
Click to collapse
Adb works. If I type adb devices it shows my Kindle is connected. BUT when executing adb shell or commands that use the sh like adb logcat it fails with the message from the topic title.
If adb shell were working i could use pokey9000´s program to boot in fastboot.
would need a command like "adb reboot bootloader" but never saw such one
could be creative and try "adb reboot fastboot" but it's a shot in the blue ...
sorry
I think we have the same problem
I think we have the same problem @osozraz. I'll share my experience and add more information that I feel is relevant.
1. I also used Kindle Fire Utility to root my Kindle and install TWRP 2.0.
2. I tried installing CM7, it worked, but figured I'd like to get back to stock firmware.
3. In TWRP, I too cleared both caches, factory restored and then proceeded to install update.zip.
4. When the Kindle rebooted it was stuck on the Kindle Fire boot screen.
Now, I researched and tried a couple of unbricking/debricking methods and failed. Here is what I've observed:
a. My device drivers are fine. If I do 'adb devices' it's recognized by the PC. However if I try 'fastboot devices' it returns nothing at all. I assume
b. I also tried the Kindle Fire Utility. Any command I try to do gets stuck on <waiting for device>. I figured that while KFU commands work on the PC's end, it doesn't work on the Kindle Fire. It's basically as if the Kindle is not connected to the computer (try running some of the commands in KFU with the Kindle disconnected, such as changing the bootmode. It'll still say <waiting for device>).
c. I can't to 'adb root' as it will say I don't have permission. Same with adb 'remount' or even 'adb shell', which from what I've gathered is crucial to this process. I can do 'adb reboot' though. I haven't tried rebooting into restore mode but I will try when I get a new MicroUSB B cable.
d. I can't change the bootmode, it gets stuck on <waiting for device> as I've said in point b. Is there a way to actually know what bootmode your device is in? I'm just assuming it's in normal bootmode because I can get fastboot.exe to detect it on the PC. In addition, KFU returns 'unknown'.
Factory Cable
Of course, there's the method of using a factory cable. I'm trying to create one and from what I've gathered there are two ways to do so: 1) use a breakout board (this one I think is the safest way to go) or 2) hack together one using your existing cable: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html. I'm also still scouring the forums for additional information that may help debrick/unbrick my device without the use of the cable. I'm afraid that I might end up damaging my PC or Kindle if I create the cable incorrectly. I've been following this thread though http://forum.xda-developers.com/showthread.php?t=1392693 because I'm thinking of actually just buying one.
Hopes these all help.
You are probably out of luck and need a factory cable at the moment.
You wiped /system/ or killed its permissions, and thus it is unable to load shell.
@osozraz and @jkspn looks like we all have the same problem. Thanks for all the suggestions. I've tried everything. Looks like the only option left is the factory wire. Only problem is that I have 0 skills with smoldering. I guess I could buy one but the site doesn't look like it will be restocking anytime soon. I'll see if I can't return it to Best Buy.
shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
When it says waiting for device, what happens when you unplug and plug in the device?
Yesterday, I got the Update 6.3.1 and because I have CMW installed, it blocked the update and I get the yellow triangle. Then I changed the recovery from CMW to TWRP and my kindle update successfully with stock bootloader and recovery back. And I can get in the system.
I want to root it again but on my Mac, I cannot use the KFU, so I use the method here (http://forum.xda-developers.com/showthread.php?p=24129239).
After I issued these commands:
"
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
fastboot -i 0x1949 flash bootloader <name of firefirefire image here>
fastboot -i 0x1949 flash recovery <name of recovery image here>
"
the terminal returns something like "Could not get PIPE properties" and it stucks here. And later, I typed ctrl+c to stop the command and "fastboot oem idme bootmode 5002
fastboot reboot"
Then the screen is black and blank. I do not know what to do. I have tried fastboot but always get "< waiting for device >". Even I hit the power button for 1 minutes, the light is not on and the screen is still black. But it seems that the battery is stll a little bit hot, which may indicate that it is using the battery. What should I do now?
You could just keep holding the power button down for a long time maybe you will get it to boot but otherwise I believe you need a factory cable. http://forum.xda-developers.com/showthread.php?t=1550999
Thanks for your reply!
Thepooch said:
You could just keep holding the power button down for a long time maybe you will get it to boot but otherwise I believe you need a factory cable. http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
Thank you so much! I ordered a factory cable and it is on the way. No matter how long I push the power button, nothing happens, no power light, no backlight....When I charge it, the charger get hot, which may indicate it is being charged. Can a factory cable save it? I guess I may flash the wrong bootloader. I should unzip the u-boot-firefirefire-1.2.zip file and then flash it. But I flash it directly without unzipping. Such a silly mistake!
You don't unzip it just flash it in recovery but look at this post too http://forum.xda-developers.com/showthread.php?t=1392693 there is a new bootloader here http://forum.xda-developers.com/showthread.php?t=1632375 follow the instructions you most likely corrupted the bootloader partition flashing a new one will fix that but you need to get to a state where you can until then your in limbo with a draining battery factory cable is maybe your only rescue. I'm not familiar with Mac so I can't really help ya there http://forum.xda-developers.com/showthread.php?t=1430038 good luck
Thepooch said:
You don't unzip it just flash it in recovery but look at this post too http://forum.xda-developers.com/showthread.php?t=1392693 there is a new bootloader here http://forum.xda-developers.com/showthread.php?t=1632375 follow the instructions you most likely corrupted the bootloader partition flashing a new one will fix that but you need to get to a state where you can until then your in limbo with a draining battery factory cable is maybe your only rescue. I'm not familiar with Mac so I can't really help ya there http://forum.xda-developers.com/showthread.php?t=1430038 good luck
Click to expand...
Click to collapse
I use the command "fastboot -i 0x1949 flash bootloader <name of firefirefire image here>". Does the "<name of firefirefire image here>" is like "u-boot-firefirefire-1.2.zip" or "u-boot.bin"? Sorry, but I am quite confused.
g0og1e said:
I use the command "fastboot -i 0x1949 flash bootloader <name of firefirefire image here>". Does the "<name of firefirefire image here>" is like "u-boot-firefirefire-1.2.zip" or "u-boot.bin"? Sorry, but I am quite confused.
Click to expand...
Click to collapse
When flash with fastboot you need to flash the u-boot.bin file
The zip file is for flashing by TWRP
they are used for two different method.
Problem Solved!
Problem solved here and I posted here.
Bricked Kindle Fire HD 7
Hi, so i bricked my kindle fire hd completely. i got a factory cable it it shows as fastboot kindle fire on the screen. But when i run the kfhd recovery tool, and try to restore it, all it says on the command prompt is, waiting for device. Help please!!
hii
wj3pic said:
Hi, so i bricked my kindle fire hd completely. i got a factory cable it it shows as fastboot kindle fire on the screen. But when i run the kfhd recovery tool, and try to restore it, all it says on the command prompt is, waiting for device. Help please!!
Click to expand...
Click to collapse
........
same problem , no solution l feel unlucky...
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
androidschima said:
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
Click to expand...
Click to collapse
I'm in a similar situation. TWRP will not mount anything, If i try to wipe cashe, ect it says failed. If i try adb push it does not work. At this point I would be fine with just going back to stock. Hopefully someone can find a solution to our problem.
androidschima said:
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
Click to expand...
Click to collapse
What is the exact command you are running? Also uninstall any kindle drivers that are installed and let it reinstall the device, I always have to do that when I switch from adb recovery to fastboot, sometimes it will be part of a component device you have to uninstall, but in that case you have to check the components vid so you don't uninstall something else by accident. All fastboot commands should be prefixed with ”-I 0x1949” so for ex: fastboot -i 0x1949 getvar product
Hope this helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
What is the exact command you are running? Also uninstall any kindle drivers that are installed and let it reinstall the device, I always have to do that when I switch from adb recovery to fastboot, sometimes it will be part of a component device you have to uninstall, but in that case you have to check the components vid so you don't uninstall something else by accident. All fastboot commands should be prefixed with ”-I 0x1949” so for ex: fastboot -i 0x1949 getvar product
Hope this helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
hi there. thank you. when i type the command you said i get the following:
product otter2-prod-04
finished. total time: 0.016s
does this mean, that fastboot is actually working and i get a connection to the device?
androidschima said:
hi there. thank you. when i type the command you said i get the following:
product otter2-prod-04
finished. total time: 0.016s
does this mean, that fastboot is actually working and i get a connection to the device?
Click to expand...
Click to collapse
ok i get in and out of fastboot fine. i looked through the commands here for fastboot.
http://forum.xda-developers.com/showpost.php?p=23747804
so far so good.
However whenever i flash something onto the kindle in cannot find it. also when i am in twrp it tell me unable to mount data.
fastboot wont let me format the userdata. did i break the filesystem? this must have been done by twrp when accidently formatting it... right?
androidschima said:
ok i get in and out of fastboot fine. i looked through the commands here for fastboot.
http://forum.xda-developers.com/showpost.php?p=23747804
so far so good.
However whenever i flash something onto the kindle in cannot find it. also when i am in twrp it tell me unable to mount data.
fastboot wont let me format the userdata. did i break the filesystem? this must have been done by twrp when accidently formatting it... right?
Click to expand...
Click to collapse
im stuck....
i flashed new recovery through fastboot because this was supposed to get the twrp 2.3.3.0 bug out of the system formatting the data partition in a way i could flash a rom onto it. so new twrp 2.7 flashed through fastboot. according to the cmd it worked all fine...
now i come into white blue boot loade choose recovery and kindle wont boot from there.
this is just f***d up. Next time i jsut keep my hands of jailbreaking hardware.
anychance anyone out there could give me a hand and get this fixed? I am
I thought 2.7 hadn't been release for kf2. You sure you flashed the right version for your device? If it is a kf2 then flash this one: http://forum.xda-developers.com/showthread.php?t=2218868
Once you flash it from fastboot, recovery should work again.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I thought 2.7 hadn't been release for kf2. You sure you flashed the right version for your device? If it is a kf2 then flash this one: http://forum.xda-developers.com/showthread.php?t=2218868
Once you flash it from fastboot, recovery should work again.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
ok got a factory cable and flashed the recovery as you said like that:
fastboot i- 0x1949 flash recovery d:\.android\recovery\twrpnew.img
target reportet max downlaod size of 486539264 bytes
sending 'recovery* (6768 KB)...
OKAY [ 0.438s}
writing 'recovery'...
OKAY [0.719s]
finished. total time 1.156s
so i reboot and select recovery but I get stuck on the blue white logo... what do I do wrong?
androidschima said:
ok got a factory cable and flashed the recovery as you said like that:
fastboot i- 0x1949 flash recovery d:\.android\recovery\twrpnew.img
target reportet max downlaod size of 486539264 bytes
sending 'recovery* (6768 KB)...
OKAY [ 0.438s}
writing 'recovery'...
OKAY [0.719s]
finished. total time 1.156s
so i reboot and select recovery but I get stuck on the blue white logo... what do I do wrong?
Click to expand...
Click to collapse
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
androidschima said:
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
Click to expand...
Click to collapse
kindle fire first aid has them. But it downloads them off the net last i heard so you wont find the images directly in there unless i am mistaken.
androidschima said:
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=43569633
This should be all u need
-》Sent from my mind to your screen.
Thank you! I will look into it!
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
kas782000 said:
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
Click to expand...
Click to collapse
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
sd_shadow said:
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
Click to expand...
Click to collapse
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
kas782000 said:
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Should be able to do it either way but I press enter, before the power button
This will not work if drivers are not correct
could try
Code:
fastboot devices
as a test should get something like
Code:
123456789 bootloader
back in command prompt
I finally got it to work and I can't thank you enough. You were right. I knew my computer recognized the device with adb in normal boot but my computer wouldn't recognize the device in fastboot mode until i reinstalled the android driver while it was in fastboot mode. Now I have a custom ROM running Google Play apps! Again, thank you!
Hey, I don't know if this will help others, but I had a hell of a time trying to get my kindle to recognize while in the bootloader/fastboot mode... It frustrated me so much that I had to write about it.
I recently switched to Windows 10, so it seems like my computer is relearning drivers and stuff...
My kindle was fine when on, and I could issue adb commands from the main screen, but when in fastboot mode, I couldn't get it detected. I knew the drivers were an issue, but I couldn't figure out how to do it. I looked at Amazon's support pages, went through the SDK route, tinkered with the adb.ini and so forth... to no avail.
Post after post said that the easiest way to install the drivers was through the Kindle Fire Utility, but for some reason, the drivers in the .bat file kept failing and would not load. It took a good few hours to figure out the solution.
When I asked the Web why the drivers kept failing, I came across a post that said Windows was actually blocking unknown drivers from loading onto my system. I really wish Windows had told me that instead of just saying "Fail"...
I had to hold down the shift button and click restart on the start menu, and when the computer restarted, I when through: troubleshoot -> advanced options -> startup settings and clicked on Restart. It eventually gave me the option to disable that signature verification [F7]
My explanation is crude, because I want you to look it up properly. Just search for "disable driver signature enforcement" and you should be fine.
Hope this helps others out. I may have to revisit my own post just to see how to do this again.
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
piffdaddy420 said:
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
Click to expand...
Click to collapse
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
monster1612 said:
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, actually i am using windows 10. My thinkpad has windows 7, so i will try to do this using windows 7. i will post back with results. its funny, out of everywhere i looked nobody mentioned windows 8+ having to disable enforcement. actually it will probably just be easier just to disable the enforcement. ill give it a try and report back.
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
piffdaddy420 said:
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
Click to expand...
Click to collapse
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
ok so im in fastboot mode now. i checked out that thread that you sent. but i have another problem, how am i supposed to get cm and gapps onto the kindle? is there a command i can use to put the files on the internal sd card? and i cant do the adb commands to push the stack, and do the other commands adb since i couldnt get it loaded to begin with, i am not able to enable developer mode. it would be nice if i could do those commands in fastboot mode. there has to be a way to do this....
maybe if someone can send me the stock partitions that they backed up stock boot partititons when they did it. maybe if i flashed them onto my kindle it will allow me to get it to atleast boot up so i can get into adb.
right now this is completely bricked.
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
piffdaddy420 said:
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
Click to expand...
Click to collapse
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
piffdaddy420 said:
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
Click to expand...
Click to collapse
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
yes it does
piffdaddy420 said:
yes it does
Click to expand...
Click to collapse
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
monster1612 said:
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
piffdaddy420 said:
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
Click to expand...
Click to collapse
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
piffdaddy420 said:
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
Click to expand...
Click to collapse
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
monster1612 said:
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
Click to expand...
Click to collapse
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
piffdaddy420 said:
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
Click to expand...
Click to collapse
anyone have any suggestions or can help me with my situation?? i am wondering if maybe someone could just send me the original backed up bootloader, boot, and recovery. i tried the original ones that were posted with that srt file. but it included everything but the bootloader. which is what i need. i know that in original thread they recommended to back up your original files (i was unable to do so because my kindle woulnt boot so i couldnt use adb to back up these files).
so if someone on here can send me the original files so i can try to get my kindle booted back up. that so far is my only theory because i tried everything else. i know people with advance knowledge would be able to help me in a heartbeat. any devs out there wanna help me out? i would greatly appreciate it!
anyone?