Develop Bugs

problems rooting

I have KFHD 8.9 v8.3. I am having problems getting fastboot working. I have read threads that there are specific "fastboot drivers" and then I have seen other threads where fastboot drivers are a part of the Kindle Fire drivers installed by ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe. No matter what I do I am unable to get "fastboot -i 0x1949 getvar product" to work. At one point I had it rooted with validation from suchecker, still couldnt get fastboot to work, but factory restored to 8.3 to validate steps and instructions and it is a nogo at the moment.
Any help would be appreciated.

So, is your device rooted or not? Your post in another forum seems to contradict what you are saying here.

Liek Soupmagnet said are you positive that your device has root access? If so, I would try wipe the drivers and start from scratch.
As far as I know and it worked for me, fastboot drivers are loaded when you install Android SDK on your PC. See picture bellow.
However in case you need the fastboot drivers you can download here: https://docs.google.com/folder/d/0B4lZEJI5lYeMdzJobG5jSk9QSEk/edit?pli=1 as referenced here: http://forum.xda-developers.com/showpost.php?p=34589184&postcount=6
These ADB drivers worked for me: http://forum.xda-developers.com/showthread.php?t=1890413
For Kindle drivers and Amazon drivers for Windows 8 (if the case),please take a look here: http://forum.xda-developers.com/showthread.php?t=2185402 however I did need not need them.
Is your Kindle showing up when you type the command ADB Devices cmd/terminal window?
I hope it helps.

soupmaget,
I responded to your PM and I said I would try the SoupKit tonight. Calling me out in forums doesn't help you or me and dont know why you keep doing that. I am trying many things but it boils down to the same specific commands. I have even tried the below downloads manually grabbing the commands and typing them in manually.
Last night I refreshed my env following the amazon tutorials step by step. I finally got root by running Root_with_Restore_by_Bin4ry_v25 twice and then Kindle_Fire_Utility_v0.9.6 rooting via recommended option twice. ADB does work, I can "adb reboot", "adb shell" push files, mv files, etc. SUCheck validates I have root.
When I continue to hashchodes TWRP and 2nd bootloader tutorial it states that "you should have working fastboot drivers" which to me means that there is a separate download/driver to install for it to work. I know fastboot.exe is included in the ADK and tried using the other tools for getting fastboot working but its not working.
I do run these with administrative rights....
D:\android\sdk\platform-tools>adb devices
List of devices attached
B0CA060424841KF0 device

So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...

rwideman said:
So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...
Click to expand...
Click to collapse
You are blowing my mind right now with your refusal to be helped. Why are you so hell bent on making this difficult for yourself? You have a $300 device that doesn't work and you're being resistant to someone who can most likely help you get it working again. Why? I don't get it...
From what I gather in your various posts, your device is rooted but you cannot access fastboot via the traditional method of entering "fastboot -i 0x1949 getvar product" in the terminal and powering the device up.
Assuming you have a usb/adb/fastboot connection problem with your Mac, you can use SoupKit, but only in certain VMs. But if you have had a previous connection with either fastboot or adb, that probably isn't the case.
Theres a good chance that you can install the Android Terminal Emulator, enter 'su' to gain root privileges and enter "reboot bootloader". That should boot your device into fastboot so you can enter fastboot commands. But, as I told you before, if there is a usb connection problem, and you cannot send fastboot commands to your device, you will be stuck in fastboot. If you have another non-Mac computer available to you, it would be best to boot it into Linux and install soupkit to make sure that doesn't happen. BTW, that is nearly verbatim to what I told you via the first PM.

Are you looking at the timestamps of my postings? Things change over time....
Did you read my PM response? I will try SoupKit tonight, I mentioned this after you told me to try it.
Thank you for your efforts.

My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
FYI #3, In the professional world it is better to stick to non-psychologist bashing, what someone is and is not doing/thinking/acting, and sticking to the issue at hand. I have been in the IT world for 15 years and troubleshooting is my day job (windows, vmware, SAP, *nix, .net, java, j2ee, storage, UCS, routers, switches, nexus, cloud automation, orchestration, etc). Professionalism frowns upon psychologist speak.

rwideman said:
My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
Click to expand...
Click to collapse
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?

I think I have the same problem. twrp installed on my device, but no OS running, and it can't be recognized on my computer, said driver incorrect, tried so many times, but can't get adb and fastboot work without driver supported. Don't know how to do.

soupmagnet said:
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?
Click to expand...
Click to collapse
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.

rwideman said:
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.
Click to expand...
Click to collapse
When it's in fastboot, do you see anything show up in the device manager?

soupmagnet said:
When it's in fastboot, do you see anything show up in the device manager?
Click to expand...
Click to collapse
Unfortunately no. I haven't had time doing linux with soupkit yet.

I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?

jonahy said:
I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?
Click to expand...
Click to collapse
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.

soupkit Folder Empty out
soupmagnet said:
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.
Click to expand...
Click to collapse
Hi Thank you for the direction.
I made a Ubuntu 12.10 usbkey booted
then copied ur soupkit folder on desktop Run install.sh ( have to go into permisions check the allow excute)
Run in terminal then terminal show 2 " closed then all the file in soupkit is gone..ha.
didnt see option 1 and 2.
Then i try in Ubuntu termal do abd and fastboot but same as in window 7 KFHD89 just boot into lock screen.
(adb devices it can see devices though
Setting up android-tools-adb (4.1.1+git20120801-1) ...
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9100425160LG8 device)
fastboot not
([email protected]:~$ sudo apt-get install android-tools-fastboot
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
android-tools-fastboot
0 upgraded, 1 newly installed, 0 to remove and 337 not upgraded.
Need to get 48.6 kB of archives.
After this operation, 129 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ quantal/universe android-tools-fastboot i386 4.1.1+git20120801-1 [48.6 kB]
Fetched 48.6 kB in 0s (105 kB/s)
Selecting previously unselected package android-tools-fastboot.
(Reading database ... 161214 files and directories currently installed.)
Unpacking android-tools-fastboot (from .../android-tools-fastboot_4.1.1+git20120801-1_i386.deb) ...
Setting up android-tools-fastboot (4.1.1+git20120801-1) ...
[email protected]:~$ fastboot -i 0x1949 getvar product
< waiting for device >
I was thinking maybe its the Root_with_Restore_by_Bin4ry_v26 mess up somthing? I know my KFHD is rooted it by, but if i load any app need root never show the window ask me if i allow this app in superuser massege.
anyway any tips abot that soupkit Folder Empty out issue?
(just got this tablet last friday, good device so far but put a recovery on it seems a bit harder then my other tablets...But hey I guess thats part of fun too right? )
Thank you in advance.

I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.

Installed 2ND-BOOTLOADER
soupmagnet said:
I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.
Click to expand...
Click to collapse
Great! Got Installed the 2nd bootloader and recovery .
adb shell su -c "reboot bootloader" boot device to fastboot mode.
thanks a lot! SoupMagnet.
Share steps:
D:\sdk\sdk\platform-tools>adb devices
List of devices attached
B0C9100425160LG8 device
D:\sdk\sdk\platform-tools>adb shell su -c "reboot bootloader"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 getvar product
product: Jem-PVT-Prod-04
finished. total time: 0.006s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/boot of=/sdcard/stock-boot.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.939 secs (8933554 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.937 secs (8952623 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/system of=/sdcard/stock-system.img"
1814528+0 records in
1814528+0 records out
929038336 bytes transferred in 116.782 secs (7955321 bytes/sec)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-boot.img
2794 KB/s (8388608 bytes in 2.931s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-recovery.img
3008 KB/s (8388608 bytes in 2.723s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-system.img
3004 KB/s (929038336 bytes in 301.978s)
D:\sdk\sdk\platform-tools>adb push stack /data/local/tmp/
571 KB/s (4096 bytes in 0.007s)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/data/local/tmp/stack of=/dev/b
lock/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,rw ext4 /system"
D:\sdk\sdk\platform-tools>adb shell su -c "mv /system/etc/install-recovery.sh /s
ystem/etc/install-recovery.sh.bak"
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,ro ext4 /system"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-
8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.026s]
writing 'bootloader'...
OKAY [ 0.045s]
finished. total time: 0.075s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0
.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.455s]
writing 'boot'...
OKAY [ 0.567s]
finished. total time: 1.030s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-r
ecovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.454s]
writing 'recovery'...
OKAY [ 0.567s]
finished. total time: 1.029s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.004s
D:\sdk\sdk\platform-tools>

FIXED
soupmagnet,
Finally had time to install ubuntu 12.10 on my laptop. I used soupkit for KFHD89 and root-plus from the same posting you had. This worked like a charm. rootplus' version of the play store actually worked compared to other versions I had installed, same for youtube and a few other google apps.
I will toy with TWRP tomorrow. Just glad I got normal google apps installed now.

[Q] Stuck at < waiting for device>

http://forum.xda-developers.com/showthread.php?t=2277105
I'm trying to follow above tutorial on how to install 2nd bootloader
I put "fastboot -i 0x1949 getvar product" in cmd, it showed "waiting for device" but when I turned it on, it doesn't change
I'm having a rooted 8.3.1 KF
Please help

tkien212 said:
http://forum.xda-developers.com/showthread.php?t=2277105
I'm trying to follow above tutorial on how to install 2nd bootloader
I put "fastboot -i 0x1949 getvar product" in cmd, it showed "waiting for device" but when I turned it on, it doesn't change
Please help
Click to expand...
Click to collapse
With the Kindle powered down, type the following command into a cmd/terminal window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect USB to the Kindle and it will boot. It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04 this has to be done in a command window opened where fastboot is located. Shift + right click in the folder where fastboot is located select open command window here, then run the command and follow above instructions to get it into fastboot.
Edit also to let you know if you are running system version 8.4.1 other thing will need to be done to install freedom boot and recovery just to send an air of caution if you use the present instructions for this you will become stuck at the blue kindle fire logo so I would wait till methods have been updated.

yes I did that, unplugged my kindle and powered down -> type the command in cmd < waiting for device> -> Plug my kindle in and automatically turn on
The cmd still show < waiting for device> even after it's fully boot, it doesn't show fastboot screen
I managed to go to Fastboot mode by using KF First Aide, but my computer couldn't recognize kindle while it's in fastboot mode. So I couldn't do anything
Edit 1st post: I'm using 8.3.1 rooted

Thepooch helped me through teamviewer on how to install Android and here I share my experience on how to do it.
Your kindle need to be rooted. I suggest to use KF First Aide and root. It's easier
You will need ADB enable by go to settings in Kindle.
Download this file (Amazon 8.4.1 OS): http://d-h.st/VnR and put it in sdcard for backup purpose.
You don't extract ZIP files.
1. Download and extract #1 on below link
http://forum.xda-developers.com/showthread.php?t=2191010
2. Go to Root_with_Restore_by_Bin4ry_v21\stuff -> Shift + Right Click on folder -> Open command window here
*Steps 3,4,5,6,7 are from http://forum.xda-developers.com/showthread.php?t=2128201
3. Use these command to backup your stock partitions, these *.img will be in the Root_with_Restore_by_Bin4ry_v21\stuff folder.
Take 4 of those *.img to somewhere else safe
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
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"
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img
4. Download these files (go to different topic above for latest version)
http://goo.im/devs/Hashcode/jem/stack
http://goo.im/devs/Hashcode/jem/kfhd8-freedom-boot-8.3.0.img
http://goo.im/devs/Hashcode/jem/kfhd8-twrp-2.4.4.0-recovery.img
5. Install stack:
Code:
adb push stack* /data/local/tmp/
adb shell su -c "dd if=/data/local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
*Replace stack with location to your stack file
Example: adb push C:\Users\Admin\Desktop\stack /data/local/tmp/
6. Stop the auto recovery update script (this file may or may not be present): Mine was not present, it will show file not sound after enter 2nd command
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "mount -o remount,ro ext4 /system"
6.5: APPLIES IF YOU ARE ON SOFTWARE VERSION 8.3.0 OR GREATER
Download this: http://goo.im/devs/Hashcode/jem/kfhd8-u-boot-prod-8.1.4.bin
Enter fastboot mode and flash:
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
*You will need a file called fastboot.exe, open command from there, KF First Aide have it
or you can download from here: http://d-h.st/ttL <- Do not use anything from this, just go to tools and open command from there
7. Continue with these command in fastboot mode:
Code:
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-recovery.img
fastboot -i 0x1949 reboot
***If everything is done correctly, when you booting up, the word Kindle Fire should switch from orange -> blue -> orange, then fully boot
***If you get orange screen, then you didn't do step 6.5
8. Download these and put them in sdcard:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130604-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130301-signed.zip
To enter recovery mode, unplug, shut the kindle down. Plug in (it should power on), when the word Kindle Fire is orange, hold the volume up button, it should switch to blue and then twrp recovery mode. If you failed, hold the power button until it shut down and try again.
8.5. Drivers problem: Kindle not recognized
When I get into recovery mode, my computer couldn't recognize Kindle. So this is what you have to do.
Download this and extract: http://d-h.st/9We
Open android_winusb.inf
Go to/Search for
Code:
;Kindle Fire HD
Now go to Device Manager -> Right Click on "couldn't recognize driver kindle" -> Details -> you will see there are two codes.
Edit android_winusb.inf (below your device, mine is Kindle Fire HD) to match with the two codes.
Then just right click, update driver
9. Now back to Kindle, you should be in TWRP Recovery Mode.
You should backup first: Go to backup -> backup everything and check compression
Next go to Wipe -> Wipe 4 of the thing on the first line (Caches, Dalvik Caches, Factory Reset, System)
Next go to Install, choose 2 of the files at step 8.
Code:
cm-10.1-20130604-UNOFFICIAL-jem.zip
gapps-jb-20130301-signed.zip
Then reboot system
10. Now you should see CyanogenMod (Android) loading
After you are in, don't let Google backup your things. It will somehow messed up your system and will crash when you try to run apps.
Next, go to settings, go to about, and tap the last line 8 times to enable developer mode
Next, check advanced boot and ADB
After that, when hold your power button for a little bit, you will see a boot button, tap it and there should be 3 options to boot in case something happens.

Nice job you make a helper proud.

[HOW-TO] FireFireFire and TWRP on 6.3.3 WITHOUT A FACTORY CABLE!

Disclammar: I TAKE NO RESPONSIBLITY FOR WHAT HAPPENS FOR YOUR DEVICE. YOU FACE THE CONSEQUENCES FOR WHAT YOU DO.
Another note: I took no part in developing any of these tools used, credit goes to their authors
Final note: This is for the ORIGINAL KINDLE FIRE ONLY!
These are instructions for installing FireFireFire bootloader and TWRP recovery
-- THIS GETS YOU INTO FASTBOOT --
Step 1: Root the kindle fire using this method: http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955
Step 2: Download fbmode from this: http://forum.xda-developers.com/showthread.php?t=1414832
Step 3: Install fbmode by using adb push fbmode /data/local/tmp
Step 4: Set fbmode permissions by using: adb shell chmod 755 /data/local/tmp/fbmode
Step 5: Run these commands here:
Code:
adb shell
su
cd /data/local/tmp
./fbmode
exit
exit
Step 6: From the command prompt: Run adb reboot
-- TO INSTALL FIREFIREFIRE AND TWRP FOLLOW THESE STEPS --
Step 1: Download SoupKit and install it from here: http://forum.xda-developers.com/showthread.php?t=1850038
Step 2: In soupkit's main menu go to the install menu by entering 2
Step 3: Enter 4 to install a bootloader and than enter 1.
Step 4 :If it says 'Make your selection now" enter 1 again
Step 5: Wait until SoupKit tells you to reboot your device and press enter.
Step 6: Follow the first set off steps to get into fastboot again
Step 7: Go back to the install menu and enter 1 to install TWRP, Than if it prompts you enter 1 again if it says "Make your selection now".
Step 8: Wait until it finishes flashing and prompts you to reboot. Reboot your device and press enter.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
You now have a rooted FireOS 6.3.3 session with FireFireFire bootloader and TWRP recovery with no factory cable!

Flashing FFF and TWRP without Fastboot Cable or SoupKit
Non SoupKit Method
Watch [Video] [How-To] Flash FFF/TWRP without Fastboot Cable
Step 1:
Root the kindle fire​Step 2:
Download fbmode and unzip.
Download ADB Files
Download fff-u-boot_v1.5.bin
Download a TWRP .img like openrecovery-twrp-2.2.2.1-blaze.img
or the One Zip Kindle.Fire.fastboot.Files.zip md5:5D68723E59AD5C1EFCCD3481C6D8E63B
Verify md5 checksums for files https://sites.google.com/site/sdshadowscollection/home/hash-checksums​Step 3:Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder.​Step 4change directory to adb
Code:
cd\adb
Install fbmode by using
Code:
adb push fbmode /data/local/tmp
Set fbmode permissions by using:
Code:
adb shell chmod 755 /data/local/tmp/fbmode
Step 5:Run these commands here:
Code:
adb shell
su
cd /data/local/tmp
./fbmode
exit
exit
Code:
adb reboot
Kindle reboots to fastboot mode
Note: Fastboot screen is just like the boot up screen, but it doesn't change or have animation.
Step 6Run these commands in command prompt
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Step 7Done​

Windows 8.1 users seems to be some driver issues, they are able to get drivers working in stock rom, but not Fastboot mode.
For those users, Soupkit maybe the only option.

Also died on me at step 6.... Nothing I've tried got it working...so caution if you're using this on windows 8.1
Sent from my Nexus 5 using XDA Free mobile app

so what do we do if its stuck at the boot screen? i set permissions on fbmode and rebooted and now im stuck at boot

Run the fastboot commands

sd_shadow said:
Non SoupKit Method
Watch [Video] [How-To] Flash FFF/TWRP without Fastboot Cable
Click to expand...
Click to collapse
This worked! I was skeptical about that saferoot utility that didn't say anything about supporting kindle fire, but figured I'd buy a factory cable if it didn't pan out. But it worked just like in the video. The saferoot utility did hang at "waiting for device" the first time I ran it and wouldn't stop even with control-c. I closed the command prompt window, left the KF connected, then restarted saferoot and it did its thing!
The other minor hitch was getting into fastboot. After rooting fbmode wouldn't execute in adb - I got the "couldn't write bp1, panic!" message. So I went into adb shell, did "su", and it worked. The rest was smooth sailing.
I just bought this KF on ebay for cheap because it had bad connection at the power jack. I'm pretty pleased with myself because I was able to reflow the solder this evening and get the microusb connector working again. Then I read that I couldn't root without a factory cable because it was on 6.3.3. I'm stoked that it worked without it. Next it's on to otterx! :good:
Thanks, sd_shadow!:

sd_shadow said:
Run the fastboot commands
Click to expand...
Click to collapse
Ah i never realized it was already in FB mode...maybe you could add that to your guide, works flawlessly but I believe most android users would believe a specific fastboot screen would pop up. I thought it was frozen
Thanks for your methods and help

jtj1825 said:
Ah i never realized it was already in FB mode...maybe you could add that to your guide, works flawlessly but I believe most android users would believe a specific fastboot screen would pop up. I thought it was frozen
Thanks for your methods and help
Click to expand...
Click to collapse
added Note: Fastboot screen is just like the boot up screen, but it doesn't change or have animation.

I have tried researching all day but when I type the "adb push fbmode /data/local/tmp" command, I get "error: device not found". I have tried all the drivers supplied in the various posts from xda to no avail. Any help would be appreciated!

mic81784 said:
I have tried researching all day but when I type the "adb push fbmode /data/local/tmp" command, I get "error: device not found". I have tried all the drivers supplied in the various posts from xda to no avail. Any help would be appreciated!
Click to expand...
Click to collapse
You need to check device manager, how is it listed?
Sent from my Amazon OtterX using Tapatalk

sd_shadow said:
You need to check device manager, how is it listed?
Sent from my Amazon OtterX using Tapatalk
Click to expand...
Click to collapse
Android ADB Interface

mic81784 said:
Android ADB Interface
Click to expand...
Click to collapse
should be in bootloader/fastboot if it says that.
When rom is running should say Android Composite ADB Interface.
If it is Fastboot mode you don't need fbmode command if in fb mode.
if it is running rom, could try rebooting pc and kindle, try a different usb cable or port

sd_shadow said:
Non SoupKit Method
Watch [Video] [How-To] Flash FFF/TWRP without Fastboot Cable
Step 1:
Root the kindle fire​Step 2:
Download fbmode and unzip.
Download ADB Files
Download fff-u-boot_v1.5.bin
Download a TWRP .img like openrecovery-twrp-2.2.2.1-blaze.img
or the One Zip Kindle.Fire.fastboot.Files.zip md5:5D68723E59AD5C1EFCCD3481C6D8E63B
Verify md5 checksums for files https://sites.google.com/site/sdshadowscollection/home/hash-checksums​Step 3:Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder.​Step 4change directory to adb
Code:
cd\adb
Install fbmode by using
Code:
adb push fbmode /data/local/tmp
Set fbmode permissions by using:
Code:
adb shell chmod 755 /data/local/tmp/fbmode
Step 5:Run these commands here:
Code:
adb shell
su
cd /data/local/tmp
./fbmode
exit
exit
Code:
adb reboot
Kindle reboots to fastboot mode
Note: Fastboot screen is just like the boot up screen, but it doesn't change or have animation.
Step 6Run these commands in command prompt
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Step 7Done​
Click to expand...
Click to collapse
after step 5 my the kindle is not recognized by the usb computer and it says on the command prompt waiting on device what can i do? im stuck on this boot screen plz help
what do i type to get it to at least boot back to normal?

mrdreamers said:
after step 5 my the kindle is not recognized by the usb computer and it says on the command prompt waiting on device what can i do? im stuck on this boot screen plz help
Click to expand...
Click to collapse
See my thread
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
Sent from my XT907 using Tapatalk

sd_shadow said:
See my thread
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
im not sure how this is going to help im stuck on boot screen on step 5 , can ya explain alittle plz?

mrdreamers said:
im not sure how this is going to help im stuck on boot screen on step 5 , can ya explain alittle plz?
Click to expand...
Click to collapse
Yes that is fastboot mode
Windows version?
Sent from my XT907 using Tapatalk
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
Read my thread watch my video
Sent from my XT907 using Tapatalk

sd_shadow said:
Yes that is fastboot mode
Windows version?
Sent from my XT907 using Tapatalk
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
Read my thread watch my video
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
im on windows 7 ultimate 64 bit

mrdreamers said:
im on windows 7 ultimate 64 bit
Click to expand...
Click to collapse
Used install.drivers.bat from Kindle Fire Utility v0.9.9?
Sent from my XT907 using Tapatalk

sd_shadow said:
Used install.drivers.bat from Kindle Fire Utility v0.9.9?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
i dont think so i used the exe one, why should i run it?

[Q] Need help to go back to stock OS

Hello friends,
I have Kindle Fire HD 8.9. I installed CM 11 on it six months ago using this method http://forum.xda-developers.com/showthread.php?t=2128175 and have been using it without any major problem since then. But I feel sluggishness in its performance so I want to switch back to stock Amazon OS. I had made a backup of stock OS using the method described in above mention thread, i.e.
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
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/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
Now I have those four files (bootblock.img, stock-boot.img, stock-recovery.img and stock-system.img) on my HDD.
If I want to go back to stock OS, I would do following steps, and I want to know if that is the proper way to proceed. and is there something I must do during the whole process in order to succeed or must be mindful of?
Plug in your fastboot cable and reboot so that you see the fastboot screen and enter the following commands:
Code:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
or should I follow instructions given here http://forum.xda-developers.com/showthread.php?t=2011126
some suggestions or instructions would be of great help. Thank you.

Both serve.
If you use your files you will return to the version that originally had in the tablet. If you use the link, you will return to the above versions (8.1.4, 8.1.3 or 8.1.2).
I do not recommend re-stock. CM11 is faster than any stock.

Yes, I did find CM11 much productive than stock Amazon OS but over time I witnessed deterioration in performance. I am in no way trying to say that it is because of CM,it could have been low hardware of Kindle.
Anyway, I used the backup made by TWRP and restored Kindle to its initial state(i.e. rooted and Google Play installed). At this moment I am on version 8.4.9. I have two questions, what if I install latest OTA? Would I loose TWRP and Root? and eventually ability to install a new ROM again? Or TWRP would be still there after OTA?

After latest OTA 8.5.1, TWRP and root permission is gone and Kindle is back to its original condition.

ADB help

By Hashcode, Senior Recognized Developer on 1st February 2013, 10:57 AM over 5 years ago
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/mmcblk0boot0 of=/sdcard/boot0block.img"
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/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
with that being said here is what happens, i can see adb is working
C:\adb>adb devices
List of devices attached
B0CC060324930545 device
C:\adb>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
/system/bin/sh: su: not found
C:\adb>
I could go on on but, that would be more gibberish.
So, what is wrong? Did the commands change? Is my path set wrong on my pc? Is there a updated thread i just have not come across yet? Anyone?
I'll thank you now for any help

Nothing changed. If you get the device to show up with the adb devices command, then everything's theoretically set up. The only reason you're getting an error with su not being found is that you aren't rooted. Here's a quick way to get root (like actually super simple, considering you already have ADB working):
1) download the attached 8.1.4 bootloader file (this is ripped straight from my Kindle before I "upgraded" to 8.5.1 to test this out). you may consider placing it in the same folder as the adb program. Also download SuperSU and the latest TWRP build for this device.
2) shut down the kindle and make sure it's plugged in.
3) run fastboot -i 0x1949 getvar product, then power the kindle on. when you see "fastboot mode" on the kindle, you should see something in the command prompt that begins with "Jem". if you do, then it's working.
4) type fastboot -i 0x1949 flash bootloader jem_8-1-4_bootloader.img to flash the 8.1.4 bootloader. this is ESSENTIAL because the kindle won't boot custom (unsigned) images otherwise. more explanation below...
5) next, type fastboot -i 0x1949 flash recovery twrp.img, where twrp.img is the file name of the TWRP image you downloaded earlier.
6) type fastboot -i 0x1949 oem recovery to kick the Kindle into recovery mode. if all goes well, you should see "TWRP" on your device after a few moments.
7) copy the SuperSU zip you downloaded to the kindle's internal storage. then on the kindle, tap Install. Next, on the side menu to the left, swipe up from the bottom and tap "sdcard" (referring to the internal storage that you see on the computer when the kindle's plugged in). Tap the SuperSU .zip, and then swipe where indicated. Feel free to reboot the system, and then voila, you're rooted. You should be able to run those backup commands. As a bonus, you won't have to download TWRP or the bootloader image from that virus-laden d-h.st site - avoid it like the plague.
8) Because TWRP's already flashed, you can type adb reboot recovery from the stock OS to begin flashing a new ROM right away.
A couple side notes...
1) Because you've flashed TWRP, a custom recovery, there is no need whatsoever to run the stock recovery backup command. It's already been overwritten, and if you really need it (which, again, is highly doubted because it only lets you run a factory reset), you can actually extract the recovery image from the system partition. Just run adb pull /system/recovery-prod.img stock-recovery.img instead of the adb shell su... stock-recovery.img one.
2) You have to flash the 8.1.4 bootloader because the one you currently have is more than likely a newer version. Custom ROMs (and even recoveries like TWRP) rely on an exploit in the 8.1.4 bootloader in order to trick the device into running the image (and newer bootloaders have this exploit patched already). So technically, because the exploit has to be run every time, the bootloader is never "unlocked" - merely tricked. Without the older bootloader in place, you get what is referred to as the "red screen of death". It's not pretty, but it's not permanent either. (Just power off the kindle, and then run the fastboot command involving "getvar product" to get it to the bootloader so you can flash the 8.1.4 bootloader and go forward.)
Hope this helps!