Develop Bugs

[FIX] Regarding TWRP 2.0 for Kindle Fire

Hello, I'm Pyrostic and I alpha tested the Kindle Fire build of TWRP 2.0.
The build that was posted last night was that of an older version. The build has since been fixed and re-uploaded at: http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
See @agrabren on twitter for the latest details on TWRP 2.0
For Kindle Fire TWRP 2.0 support please see the Kindle Fire RootzWiki forum. Team Win will not be providing support here.
During install when your device gets to the "Reboot" screen run
Code:
adb shell
idme bootmode 4000
If you did flash the old version and you find yourself stuck at the Kindle Fire screen you simply need to replace your twrp-blaze-2.0.0RC0.img and run the following snippet of code.
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
if you haven't flashed yet. Please DO NOT FORCE install this new image using a dd command such as this:
Code:
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
Simply follow the following instructions after downloading the image at http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img in an ADB prompt:
Code:
adb shell
su
idme bootmode 4002
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
This will install both the FIREFIREFIRE U-boot and TWRP 2.0 .
FURTHERMORE if you did use the DD commands stated above you may not be able to get into ADB, and I hope fastboot still works for you. If it does, try :
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
If you are having problems please try the following. It has been reported that it is helpful to others.
If you LOVE TWRP 2.0 on your Kindle Fire. I suggest donating to @agrabren (<--- donation link) for his hard work and thanking me here for my testing .
I will not be replying to this thread. If you have issues please join us on RootzWiki for follow up support. I merely posted this here because I do care for my community in general.

There are so many different guides floating around and I've decided to simply follow this one. However, I get 'fastboot: not found' after the 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' command. All I've done is put the twrp-blaze-2.0.0RC0.img on my sdcard and run the following commands..
adb shell
su
idme bootmode 4002
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Did I miss a step? Thanks.

Is there anything I can do since I used the dd command and am now stuck at the firefirefire screen?
Edit: Tried the "fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img" and all I got was < waiting for device >
Fix: I followed http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222 worked like a charm

i did the dd install... not having any adb issues though. are there any other problems with installing it that way?

I also used dd with no issues and can boot in and out of TWRP with no issues.
Sent from my Kindle Fire using xda premium

ags29 said:
There are so many different guides floating around and I've decided to simply follow this one. However, I get 'fastboot: not found' after the 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' command. All I've done is put the twrp-blaze-2.0.0RC0.img on my sdcard and run the following commands..
adb shell
su
idme bootmode 4002
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Did I miss a step? Thanks.
Click to expand...
Click to collapse
Yes a couple things, put the twrp-blaze-2.0.0RC0.img file in the folder where you have fastboot installed. and It doesn't sound like you have fastboot on your computer. Please look around.

borborpa said:
I also used dd with no issues and can boot in and out of TWRP with no issues.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
The new file was uploaded around 9:30am this morning. Anything from before then will not harm you using the DD method.

I also use dd method to install FIREFIREFIRE and twrp. After that I lost the ADB connection. Try to issue the comand:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
But it shows < waiting for device >...
My Solution:
Change the VID to 0x18D1 and issue the command:
fastboot -i 0x18D1 boot twrp-blaze-2.0.0RC0.img
The < waiting for device > msg will still be showed. Don't worry. Reboot you KF. During the reboot period, the twrp-blaze-2.0.0RC0.img will flash to your KF. After the twrp installation process is completed, you ADB will BACK~~~

my problem is that it booted into fastboot, installed, and now simply sits at the firefirefire screen. I do not have fastboot, nor will it go into recovery when the power button is pressed....I am running the new combo install, following the instruction posted above.
Is there a driver change in FIREFIREFIRE? Do we need to add it to the driver settings?
HELP!

pyrostic said:
The new file was uploaded around 9:30am this morning. Anything from before then will not harm you using the DD method.
Click to expand...
Click to collapse
i downloaded it about 2 hours ago (dunno what 9:30 am is for you.. its 8:51 for me right now so... yea) and it didn't cause any problems that I can notice. if I did flash the newer version what problems could I expect to see? fastboot works, firefirefire works, and adb works.
if it matters any I'm running CM7 not stock rom. Maybe that's why I haven't been having these issues.

MayfairDROID said:
my problem is that it booted into fastboot, installed, and now simply sits at the firefirefire screen. I do not have fastboot, nor will it go into recovery when the power button is pressed....I am running the new combo install, following the instruction posted above.
Is there a driver change in FIREFIREFIRE? Do we need to add it to the driver settings?
HELP!
Click to expand...
Click to collapse
This post saved my kindle when that happened to me

What's the advantage of using this one over the old one? Old one works fine for me.

Ok I've tried everything to get out of the yellow triangle screen and it won't budge lol.. O If I just reboot it just goes back to the same screen and with the fastboot commands it just stays on 'waiting for device'.
Edit: Trying solution in link by brian112.. annnnd it worked (but not before adding the 18D1 line to the .inf file and reinstalling the kindle drivers through Device Manager).

pyrostic said:
The new file was uploaded around 9:30am this morning. Anything from before then will not harm you using the DD method.
Click to expand...
Click to collapse
Now I'm totally confused. I dled it after 10. It worked just fine, I rebooted multiple times into it, did a backup and everything. Now I just rebooted, and I'm stuck at the FIREFIREFIRE screen, and can't see the device in adb. Windows won't even recognize the driver.
[FIXED] brian112358's post above fixed the problem.

Thanks..that worked
Now next time i need to get into the TWRP 2.0, I just hit the power button during reboot correct?
Thanks again!
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
ags29 said:
Ok I've tried everything to get out of the yellow triangle screen and it won't budge lol.. O
If I just reboot it just goes back to the same screen and with the fastboot commands it just stays on 'waiting for device'.
Edit: Trying solution in link by brian112..
Click to expand...
Click to collapse
Works like a champ...give it a shot

what is the 18D1 line? I'm trying sl0ttedpig's fix but it's not working, driver wont install

ckong1 said:
what is the 18D1 line? I'm trying sl0ttedpig's fix but it's not working, driver wont install
Click to expand...
Click to collapse
My fix unfortunately doesn't fix everything! There may some extra steps depending on what state you are in and how you got there. Did the device driver install, and can you see it listed in Device Manager as "Android Phone" > "Android Composite ADB Interface"? That is the most important step for this to work for you.
If you can see that try just doing the following:
Code:
fastboot oem idme bootmode 4000
fastboot reboot

i can't seem to get driver to install, kindle comes up as unknown device

ckong1 said:
i can't seem to get driver to install, kindle comes up as unknown device
Click to expand...
Click to collapse
So what happens if you follow the same instructions. I just updated my OP to include it saying either kindle or unknown, as it could work in either state (as posted by other people)
"In device manager, you'll see a device just called "kindle" or "unknown" with an exclamation point by it. At this point, you'll need to install drivers for it again. Pick "Browse my computer for driver software" BUT don't browse, just click on "Let me pick from a list...", and select "Android Phone" and then pick the newest "Android Composite ADB Interface" from the list. I think you may have 4.0.0.0 or something similar (you may have only a 2.x version possibly depending on which drivers you loaded to root your phone)."
Click to expand...
Click to collapse

when i select "Let me pick from a list..." "Android Phone" is not an option, only "Unknown Devices" is shown. I try clicking that and i get:
windows has stopped this devices because it has reported problems. (Code 43)
Tried updating vendor list and adding 18d1 to winusb, still cannot install driver
Update:
After restarting the kindle and connecting it, it comes up as "kindle" in devices manager. driver will install but it still is not recognized by adb...

[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...

forgot to wipe when installing stock update

i wanted to reset my device back to default rom. so i downloaded the zip file via KFU. then i flashed it. however, i forgot to wipe everything. now when i turn on my device and unlock it, it says that all these apps cannot open and i have to force close them. then after like 30 seconds, it closes and i see the kindle fire logo. then it boots up and the same thing happens again. I then tried to reinstall twrp and FFF but it cant because the location where evry thing recquired for fastboot doesnt exist. it could be because of a different reason so any help will be appreciated! :crying::crying::crying:

Why would you be confused you know what you did wrong here's the trick you need to be really fast ... get to factory reset and reset it try from a powered off position maybe you will get the few extra seconds it takes to get it done...
---------- Post added at 11:36 PM ---------- Previous post was at 11:27 PM ----------
Otherwise you need to somehow get into fastboot and fastboot flash twrp.img and fff.bin note that I did say .bin if you cannot the best way is to get a factory cable...

Thepooch said:
Why would you be confused you know what you did wrong here's the trick you need to be really fast ... get to factory reset and reset it try from a powered off position maybe you will get the few extra seconds it takes to get it done...
---------- Post added at 11:36 PM ---------- Previous post was at 11:27 PM ----------
Otherwise you need to somehow get into fastboot and fastboot flash twrp.img and fff.bin note that I did say .bin if you cannot the best way is to get a factory cable...
Click to expand...
Click to collapse
im sorry, what do you mean by try it from a "powered off position"?

I mean turn it off then power it on and race to reach factory reset in the settings
---------- Post added 11th August 2012 at 12:00 AM ---------- Previous post was 10th August 2012 at 11:56 PM ----------
Anything you can do to shave time

reboot into fastboot and open kfu. then install superuser and others
i have got the same trouble.

I'm sure he would if he knew how to achieve fastboot :
Shift+ right click on the tools folder in kfu ... select open command window here.. power your kindle off.. type fastboot -i 0x1949 getvar product ... plug your kindle in it will power on in fastboot and return product: kindle open kfu and commit send of twrp after reboot commit send of fff .... power off power back on select recovery in recovery factory reset , wipe cache, wipe dalvik select reboot then system if prompted. In theory it should work if fastboot can be initiated...
Edit: no need to root twrp and fff is all you need

Sounds like you have enough time to set the bootmode to fastboot before your KF reboots.
So what you need to do is download the fbmode binary (may be include in KFU, otherwise search the development forum), adb.exe, fastboot.exe, and the TWRP 2.2.0 fastboot image. All of which should be placed in a single folder.
I'm assuming your on Windows, and therefore you must open a command prompt in your working directory. You will need to run the following commands...
Code:
adb wait-for-device
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
It may be easier to make a batch file so you don't have to type all the commands.
Then you could boot TWRP without flashing it by issuing this command...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 boot openrecovery-twrp-2.2.0-blaze.img
From there, you should be able to delete the dalvik-cache, userdata, and cache.
Note: You must have the adb drivers installed and working properly. On the stock KF rom, adb is enabled by default so there's no reason this shouldn't work.
Edit: Actually, there's a possibility that this won't work if you disabled USB Debugging before switching back to the stock KF rom.

Thepooch said:
I'm sure he would if he knew how to achieve fastboot :
Shift+ right click on the tools folder in kfu ... select open command window here.. power your kindle off.. type fastboot -i 0x1949 getvar product ... plug your kindle in it will power on in fastboot and return product: kindle open kfu and commit send of twrp after reboot commit send of fff .... power off power back on select recovery in recovery factory reset , wipe cache, wipe dalvik select reboot then system if prompted. In theory it should work if fastboot can be initiated...
Edit: no need to root twrp and fff is all you need
Click to expand...
Click to collapse
thx! am going to try soon.... not at home atm....

lmntone said:
Sounds like you have enough time to set the bootmode to fastboot before your KF reboots.
So what you need to do is download the fbmode binary (may be include in KFU, otherwise search the development forum), adb.exe, fastboot.exe, and the TWRP 2.2.0 fastboot image. All of which should be placed in a single folder.
I'm assuming your on Windows, and therefore you must open a command prompt in your working directory. You will need to run the following commands...
Code:
adb wait-for-device
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
It may be easier to make a batch file so you don't have to type all the commands.
Then you could boot TWRP without flashing it by issuing this command...
Code:
fastboot oem idme bootmode 4000
fastboot boot openrecovery-twrp-2.2.0-blaze.img
From there, you should be able to delete the dalvik-cache, userdata, and cache.
Note: You must have the adb drivers installed and working properly. On the stock KF rom, adb is enabled by default so there's no reason this shouldn't work.
Edit: Actually, there's a possibility that this won't work if you disabled USB Debugging before switching back to the stock KF rom.
Click to expand...
Click to collapse
for some reason, i cant get the adb to work..... i hav the correct driver (i already did this before) but adb cannot find the device.

Then here is your best bet http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info+factory+cable unless you can reach factory reset in time to do it

n00byn00bface said:
for some reason, i cant get the adb to work..... i hav the correct driver (i already did this before) but adb cannot find the device.
Click to expand...
Click to collapse
If you had adb disabled in the old rom, the settings could have been carried over to the stock rom.
Using a factory cable seems to be the only solution.

Thepooch said:
Then here is your best bet http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info+factory+cable unless you can reach factory reset in time to do it
Click to expand...
Click to collapse
i was going to try to buy one from skorpn..... anyway, factory reset does nothing.

lmntone said:
If you had adb disabled in the old rom, the settings could have been carried over to the stock rom.
Using a factory cable seems to be the only solution.
Click to expand...
Click to collapse
i got it into fastboot mode, but now the command is stuck on fastboot oem idme bootmode 4000 <waiting for device>
also, its stuck on the kindle fire logo screen (that means its in fastboot right?)

thx everyone! i managed to fix my device! i followed imntones instructions and they worked.... sort of.... i used the first codes to get into fastboot, then i used twrp to install..... the last two codes dont work. thank you thank you thanmk you..... :highfive:

n00byn00bface said:
thx everyone! i managed to fix my device! i followed imntones instructions and they worked.... sort of.... i used the first codes to get into fastboot, then i used twrp to install..... the last two codes dont work. thank you thank you thanmk you..... :highfive:
Click to expand...
Click to collapse
I think that you just needed to specify the vendor id for fastboot. As in...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 boot openrecovery-twrp-2.2.0-blaze.img
Anyway, glad to see you got your device working.

[Q] Can I downgrade 10.3 with Windows?

Hello,
Still working on my kids KF2. I got root, yeah! However at some point it updated to 10.3. Can someone point me in the right direction for getting its bootloader downgraded from a Windows 7 x64 platform? I can use a RHEL box at work if I really need to, but rather not.
so I get CM on this thing
thanks!

http://forum.xda-developers.com/showthread.php?t=2100963

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2100963
Click to expand...
Click to collapse
Does that mean I need a fastboot cable? I can make one no problem... but better if I don't have to
I ran: fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin, device off, it said waiting for device, but then it just boot up to the lock screen.
Sorry im a little confused on this one.

Code:
adb shell su -c "reboot bootloader"

soupmagnet said:
Code:
adb shell su -c "reboot bootloader"
Click to expand...
Click to collapse
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?

s10010001 said:
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?
Click to expand...
Click to collapse
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.

soupmagnet said:
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.
Click to expand...
Click to collapse
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...

s10010001 said:
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...
Click to expand...
Click to collapse
Close
Make backups
Fastboot with that command
Install downgraded bootloader
Install 2nd bootloader
Install TWRP & kernel(boot.img)
Factory Reset in TWRP
Install rom
enjoy..
Enjoyment is relative, of course

Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?

s10010001 said:
Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?
Click to expand...
Click to collapse
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.

soupmagnet said:
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.
Click to expand...
Click to collapse
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?

s10010001 said:
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?
Click to expand...
Click to collapse
If your device is completely off, and you plug a working factory cable in, it will boot into fastboot.
Info on pin layout
You need a 5-pin usb cable BTW.

Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?

s10010001 said:
Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?
Click to expand...
Click to collapse
Were you able to successfully backup your boot, recovery, and system partitions before everything went wrong?

No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?

s10010001 said:
No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?
Click to expand...
Click to collapse
Possibly, but depending on where things went wrong, you may have to restore first. Do you know what the error was?

Something like this max-download-size: 486,539,264

s10010001 said:
Something like this max-download-size: 486,539,264
Click to expand...
Click to collapse
You are supposed to save your partition images with the 'dd' command using the shell:
Hashcode said:
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Take those files and put them somewhere safe.
Click to expand...
Click to collapse
You won't see a "max-download-size" message unless you are using fastboot to flash those images.

ohh ok.. so I dont have a backup
But the fastboot cable is working! Im in fastboot

keeps telling me no device found
do I want the "Android ADB Interface" or "Andriod Composite ADB Interface"?
Also once booted in to fastboot with the cable, do I just leave the cable or put the stock cable back in? Shouldnt matter... but just want to make sure.