The install_drivers.bat from the Kindle Fire Utility is probably the most straight forward way to get them installed, but don't use anything in the KFU other than that. The KindleFireFirstAide tool has an option to install drivers also, I believe. Or you could just do as suggested and boot into a liveUSB and install SoupKit.
adb shell su -c "reboot bootloader"
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
and no device was detected in device manager when I disconnected and connected the USB cable.
OMG...don't do that.Hi, I can wait until the battery drains - but what then? Will I be able to charge the device then and try to redo this step and continue with the process?
Why on earth, if you have a Linux machine, are you trying to run a Windows VM? I think I just died a little inside.Can someone help me, please.
I was going to install CM10.1 on my KFHD8. I was doing it inside Win7 Virtualbox machine and everything went fine until I started this command:
Then I got kernel panic on my linux (host) machine and KFHD got stuck at "Start downloading" message in fastboot mode.Code:fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
OMG...don't do that.
Why on earth, if you have a Linux machine, are you trying to run a Windows VM? I think I just died a little inside.
If you don't want to go through the trouble of configuring your Linux environment to send ADB or fastboot commands, just install SoupKit. It already does all of that for you, and you won't have to run the VM (which is probably why you received the kernel panic in the first place).Well I was running the installer from this thread http://goo.gl/BMybF which only has a bat file and doesn't have bash variant; and I was to lazy to rewrite the thing; and I never had any problem with the VBox Win7 machine until today
But as I was on v8.3.1 (didn't disable automatic upgrade) and this post http://xdaforums.com/showpost.php?p=40453742&postcount=22 pointed me to do boot image from this thread I went ahead and did it - that is tried to do it - from inside VM.
If waiting for battery drai isn't the option, what is?
Or am I stuck with soon to be brick
If you don't want to go through the trouble of configuring your Linux environment to send ADB or fastboot commands, just install SoupKit. It already does all of that for you, and you won't have to run the VM (which is probably why you received the kernel panic in the first place).
To install the 2nd bootloader, you only need to copy and paste a handful of commands to the terminal, so running a script to do it for you is kind of pointless IMO.
You need to make sure your drivers are configured properly for fastboot .I have done everything up to step 5. It just doesn't go into fastboot.
This is what I have done:
1. Shut down the device.
2. Enter "fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0.img" into command prompt, I see "< waiting for device >"
3. Connect the device via USB.
4. Device still boots up normally into Android.
What did I do wrong? I have already installed the drivers successfully and ADB does detect the device.
You need to make sure your drivers are configured properly for fastboot .
The easiest thing to do would probably be to set up a Linux LiveUSB and install SoupKit.How do I do that?
I have followed your instructions here: http://xdaforums.com/showthread.php?t=2179748
Added the hardware ID of the KFHD8.9 to the android_winusb.inf file and installed the drivers that can with KFU. Still doesn't work.
I have done everything up to step 5. It just doesn't go into fastboot.
This is what I have done:
1. Shut down the device.
2. Enter "fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0.img" into command prompt, I see "< waiting for device >"
3. Connect the device via USB.
4. Device still boots up normally into Android.
What did I do wrong? I have already installed the drivers successfully and ADB does detect the device.
Thanks, it works! This should be included on the first post, it will save everyone a lot of time!
EDIT: I have completed all the steps, but now its stuck at the orange kindle fire logo. I have waited for more than 10 mins and I still don't see the blue logo.
I can still access the device via fastboot. Already tried repeating steps 4.5 and 5, but it just won't work. Any idea whats wrong now? :/
I never experienced this issue, but looks like there is some problem with the stack file installation. u can try to restore with your previous backup or KFHD SRT(http://xdaforums.com/showthread.php?t=2011126) and start over again.
After a lot of trial and error I claim success! Thank you for your help, on CM now, rockin and rollin
:good: The stack file was overwritten by an OTA update, doing that step again fixed the problem!
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
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
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"
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 reboot
fastboot -i 0x1949 flash boot [B]boot.img[/B]
fastboot -i 0x1949 flash recovery [B]recovery.img[/B]
fastboot -i 0x1949 flash system [B]system.img[/B] # This one will take a few minutes
fastboot -i 0x1949 reboot