Develop Bugs

[GUIDE] Quick install firefirefire + twrp20. Important update!

pyrostic said:
It appears via @agrabren on twitter just changed to a new build. download the new one at
http://teamw.in/project/twrp2/79
you have to use fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
this custom image installs FIREFIREFIRE u-boot and TWRP 2.0
---------- Post added at 09:50 AM ---------- Previous post was at 09:41 AM ----------
If you flash the latest .img file using this method it will completely screw things up. The latest image installs FIREFIREFIRE u-boot as well as TWRP.
Please be kind enough to remove this thread as it could render Kindle Fires useless. You cannot flash the current twrp-blaze-2.0.0RC0.img via the following. It will make your devices stick at the Kindle Fire screen.
This wont work with the new image:
Code:
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
You NEED fastboot and you need to run the following with the new image from http://teamw.in/project/twrp2/79:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Click to expand...
Click to collapse
---------------------------------------------------------------------
BUT, if you still do no wanna use fastboot and wanna use dd to flash, you can download my attachments in this post and use the follow method.
It's the old version twrp2.0 that can be used dd to flash.
---------------------------------------------------------------------
Unpack rar file,
get u-boot.bin and twrp-blaze-2.0.0RC0.img
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
Ctrl+C (quit adb shell)
adb reboot
That's all.
They're holy perfect.

Thanks! Works great.

Unheard said:
Thanks for this. One question you might be able to help with. After doing the original method, and then doing this, my fire will only boot into recovery. I'm guessing something to do with 'idme bootmode 0x5001'. Is there and idme command to have the fire boot to the OS as opposed to recovery? Thanks!
Click to expand...
Click to collapse
Yea once in recover open up adb shell window and do "idme bootmode 4000" then "reboot" don't press anything and you'll boot to your rom.
Sent from my SPH-D710 using xda premium

pyrostic said:
Yea once in recover open up adb shell window and do "idme bootmode 4000" then "reboot" don't press anything and you'll boot to your rom.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Ya figured it out shortly after typing the question. Thanks for the reply.
EDIT: If you choose Recovery in the reboot menu of CM7, it will reboot you to Recovery. Problem is you have to idme 4000 to get it to reboot to your OS after doing that.

riverzhou said:
Unpack firefirefire, get u-boot.bin
Get twrp-blaze-2.0.0RC0.img from office site
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
Ctrl+D (quit adb shell)
adb reboot
That's all.
They're holy perfect.
Click to expand...
Click to collapse
Coming from a rooted Stock 1.0 ROM, this worked perfectly with no problems. Launched TWRP and did an immediate backup of /boot /data and /system to retain that stock feel in case of a need to RESTORE.
Thanks for this quickie!

Unheard said:
Ya figured it out shortly after typing the question. Thanks for the reply.
EDIT: If you choose Recovery in the reboot menu of CM7, it will reboot you to Recovery. Problem is you have to idme 4000 to get it to reboot to your OS after doing that.
Click to expand...
Click to collapse
Good to know, mind if I post this in the CM7 thread? It would be good for everyone to know.

pyrostic said:
Good to know, mind if I post this in the CM7 thread? It would be good for everyone to know.
Click to expand...
Click to collapse
Wont hurt my feelings.

I followed the guide but when it booted up it is stuck at the firefirefire screen. I have not been able to boot into recovery or into android, any help would be greatly appreciated.
Edit: Also adb is not detecting device.
Fix: Follow the instructions here will fix the issue. http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222

fleton said:
I followed the guide but when it booted up it is stuck at the firefirefire screen. I have not been able to boot into recovery or into android, any help would be greatly appreciated.
Edit: Also adb is not detecting device.
Click to expand...
Click to collapse
It appears via @agrabren on twitter just changed to a new build. download the new one at
http://teamw.in/project/twrp2/79
you have to use fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
this custom image installs FIREFIREFIRE u-boot and TWRP 2.0
---------- Post added at 09:50 AM ---------- Previous post was at 09:41 AM ----------
If you flash the latest .img file using this method it will completely screw things up. The latest image installs FIREFIREFIRE u-boot as well as TWRP.
Please be kind enough to remove this thread as it could render Kindle Fires useless. You cannot flash the current twrp-blaze-2.0.0RC0.img via the following. It will make your devices stick at the Kindle Fire screen.
This wont work with the new image:
Code:
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
You NEED fastboot and you need to run the following with the new image from http://teamw.in/project/twrp2/79:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img

fleton said:
I followed the guide but when it booted up it is stuck at the firefirefire screen. I have not been able to boot into recovery or into android, any help would be greatly appreciated.
Edit: Also adb is not detecting device.
Click to expand...
Click to collapse
I have the same problem, I used the new build and the "fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img" command. All went well, got the TEAMWIN screen and pushed the reboot button, rebooted to the triangle fire screen with "press power button for recovery" at the bottom. I press power and nothing, if I hold for 20 sec.s it powers off but on reboot, back to the same triangle screen.. What is wrong.. Thanks..

Same thing happened to me, this post solved the problem.

To load twrp, at triangle seen, press power button a bunch until the light turns orange, then it will reboot into twrp

Something is up with this install method of the twrp img (which includes firefirefire). It leaves the device at the yellow triangle and (in windows at least) you lose adb and fastboot (in fact, in windows the device is no longer recognized and you cannot install the modded driver). I'm thinking the factory cable might be an option to force it into fastboot. Any thoughts on that?

rwphwp said:
Something is up with this install method of the twrp img (which includes firefirefire). It leaves the device at the yellow triangle and (in windows at least) you lose adb and fastboot (in fact, in windows the device is no longer recognized and you cannot install the modded driver). I'm thinking the factory cable might be an option to force it into fastboot. Any thoughts on that?
Click to expand...
Click to collapse
I had same issue. I followed the instructions on this link http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222 which fixed it.

brian112358 said:
Same thing happened to me, this post solved the problem.
Click to expand...
Click to collapse
Took a couple of tries but this did work and got back to normal boot..

Well, in following OP's instruction's I bricked my Kindle(I followed them verbatim, so it must have been something I did on my Kindle).
Brian's post helped unbrick it.

Just to confirm, we SHOULDNT be following this guide now?

correct.. this is the old method.... use the new method...

alchemyst said:
Just to confirm, we SHOULDNT be following this guide now?
Click to expand...
Click to collapse
Yes. Should NOT.
I think I can post old twrp20 file and then you can use this method.

riverzhou said:
Yes. Should NOT.
I think I can post old twrp20 file and then you can use this method.
Click to expand...
Click to collapse
I renewed the origin post and uploaded image files that can be flash by dd.

[Q] Kindle Fire Bricked: exec "system/bin/sh": No such file or directory

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?

[Q] Bricked Kindle. I use fastboot, but always get < waiting for 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...

[Q] kindle stuck in fastboot mode but won't accept commands

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>

Soft Bricked Nexus....other threads not helping...

My CDMA Nexus froze....battery pull, boot looped. Recovery restore backup....."error while restoring /data"
Been trying to get back to stock ever since and I can't get the fricken ADB command prompt stuff to work.
I have installed drivers like 10 times, and it shows "Android phone" in device manager when the phone is plugged in with fastboot on.
Everytime I try and do the fastboot commands it just says "error: device not found"

Does it let you mount usb so you can stick a new rom file on it?
Sent from my Galaxy Nexus using Tapatalk 2

edit/disregard
does "fastboot devices" reveal your phone?

eqjunkie829 said:
Does it let you mount usb so you can stick a new rom file on it?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It doesn't show up as a drive, just in the device manager as Android ADB Interface.
I just restarted my computer to see if the drivers needed that....this time I ran the 'adb reboot bootloader' and I got daemon not running. Now starting on port 5037. Daemon started successfully. Then it still said error: device not found

animal24 said:
Hold both volume rockers down and start your phone ... then in your command prompt
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
then just to be sure boot into recovery and wipe.
Click to expand...
Click to collapse
This

Does it show as fastboot devices?
Click to expand...
Click to collapse
Yeah.....it returns the phone serial number....
So I dunno what the deal is.

biscuitownz said:
This
Click to expand...
Click to collapse
yeah...I know....that has been my goal for the past 4 hours.
The command prompt wont push to a device it doesn't find...

Cadillac Kid said:
yeah...I know....that has been my goal for the past 4 hours.
The command prompt wont push to a device it doesn't find...
Click to expand...
Click to collapse
if the serial number comes up then it should be able to push the factory images back into it.
try fastboot erase userdata

IINexusII said:
if the serial number comes up then it should be able to push the factory images back into it.
try fastboot erase userdata
Click to expand...
Click to collapse
that did it.........weird. THANKS!!!!