i have just flashed a new recovery, and everything is just fine until i typed this:
fastboot reboot
and it does not reboot fastboot,stucks on first screen but!
pull out battery and entering by hardware key works, all fastboot, bootloader, my ROM, the new recovery.
so that confuses me, i can enter manually, but by adb i cant?
ADB works at the Bootloader and Recovery.
Fastboot works at the Fastboot mode.
Fastboot != ADB
Different commands, different purpose.
If you need reboot to fastboot command is:
"fastboot reboot-bootloader"
"fastboot reboot" just reboots your phone.
I have a problem. I rooted my Kindle fire (6.2.2) with BurritoRoot 2 and then tried to use Kindle fire Utility 0.9.2 to install TWRP and FireFireFire on my device. Everything was going fine until it told my kindle to go into fastboot and now its stuck in there. ive tried adding new vendor IDs, fastboot bootmode 4000, draining out the battery, uninstalling the drivers, rebooting my computer, everything. Can someone please help before I decide to use up my warranty?
Using Windows XP 32-bit
Install the kfu driver go into tools folder in kfu hold shift right click run command... this should boot adb then type
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Sent from my Amazon Kindle Fire using Tapatalk
The exact same thing happened to me on the first try. Different drivers are needed when using KFU than when just using ADB. Run the install drivers batch file provided with KFU and run the commands listed above. That should get it out of bootloop.
Sent from my Kindle Fire using Tapatalk
interceptor_1972 said:
Run the install drivers batch file provided with KFU
Click to expand...
Click to collapse
I tried that, but it failed, saying the drivers were unsigned :/
alternativeaura said:
I tried that, but it failed, saying the drivers were unsigned :/
Click to expand...
Click to collapse
Follow these steps to set driver verification levels:
1.Press [Windows]Break to display the System Properties dialog box.
2.Select the Hardware tab and click the Driver Signing button in the Drivers panel.
3.Select the Block-Never Install Unsigned Driver Software button. (Verify that the Make This Action The System Default check box is selected.)
4.Click OK twice.
Still didnt work :\
"Errors were encountered while installing the software for your devices.. See the Status column for more details."
Driver name Google, Inc (WinUSB) AndroidUsbDeviceClass (12/06/2010 4.0.0000.00000)
Status
Install failed (unsigned)
did you do it with install_drivers.bat or did you update it manually ?
have you put kfu to c:\ and renamed to "kfu" that it is c:\kfu ? - it don't like spaces in pathname
are you on an english xp ? - since the xml of the driver installer has to be edited
b63 said:
did you do it with install_drivers.bat or did you update it manually ?
have you put kfu to c:\ and renamed to "kfu" that it is c:\kfu ? - it don't like spaces in pathname
are you on an english xp ? - since the xml of the driver installer has to be edited
Click to expand...
Click to collapse
1. I tried both
2. it's c:\KindleFireUtility
3. yes im on english, but how do i edit the xml?
alternativeaura said:
1. I tried both
2. it's c:\KindleFireUtility
3. yes im on english, but how do i edit the xml?
Click to expand...
Click to collapse
if your on english the installer should be ok
what does it tell you in device manager ?
in fastboot mode it should be "android adb interface" under "android phone"
b63 said:
in fastboot mode it should be "android adb interface" under "android phone"
Click to expand...
Click to collapse
Thats what i have, but adb does not recognize it
alternativeaura said:
Thats what i have, but adb does not recognize it
Click to expand...
Click to collapse
very fine - if the kf is in fastboot it don't recognize adb commands
an other little trick is to issue the fastboot command "fastboot -i 0x1949 oem idme bootmode 4000" and when it says <waiting for device> power down the kf by holding the pwr button for ~20sec - then unplug and replug - don't turn it on - it should do it by itself - at some point the command is recognized and finished - then power off and on again
here a little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible the commands:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
or
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
b63 said:
very fine - if the kf is in fastboot it don't recognize adb commands
an other little trick is to issue the fastboot command "fastboot -i 0x1949 oem idme bootmode 4000" and when it says <waiting for device> power down the kf by holding the pwr button for ~20sec - then unplug and replug - don't turn it on - it should do it by itself - at some point the command is recognized and finished - then power off and on again
here a little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible the commands:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
or
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!!!!!!!!!
I have been searching for DAYS over the Internet, and lets just say when it comes to kindle fires, you are my SAVIOR. thank you
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
b63 said:
very fine - if the kf is in fastboot it don't recognize adb commands
an other little trick is to issue the fastboot command "fastboot -i 0x1949 oem idme bootmode 4000" and when it says <waiting for device> power down the kf by holding the pwr button for ~20sec - then unplug and replug - don't turn it on - it should do it by itself - at some point the command is recognized and finished - then power off and on again
here a little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible the commands:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
or
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
i had the same problem, this worked !
but after i did everything and restart system, it went straight to the TWRP menu not the kindle fire system.
how can i fix this?
adb shell idme bootmode 4000
adb reboot
KFU v0.9.1 fixed this for me thankgod
Nice! And my KF's good to go again! Thanks b63! One air high-five for you bro!
This forum helps a lot of people! Hahaha! Thanks and more power!
HELP!
Hey guys! Back again. So noob me here has a new problem.
I CAN'T GET OUT OF NORMAL BOOT MODE! (Plain "Kindle Fire" logo but with dim backlight.)
These are what I did but to no avail:
- I tried switching it to fastboot mode, but everytime I do it, it becomes unrecognized by the device manager.
- And when I switch it back to normal boot mode, it just gets stuck there. (I HAVE NOT INSTALLED TWRP OR FFF OR ANYTHING ELSE FOR THAT MATTER BECAUSE THESE RECOVERY TOOLS NEED THE KF TO BE IN FASTBOOT MODE TO BE INSTALLED, BUT AS I SAID EARLIER, MY DEVICE GETS STUCK ON FASTBOOT MODE AND GOES UNRECOGNIZED, THAT'S WHY I DON'T HAVE TWRP AND FFF.)
Here is probably the most important info I can give.
I HAVE INSTALLED "GO LAUNCHER EX" ON MY KF AND AFTER THAT, I REBOOTED MY KF AND IT ASKED IF IT WANTED TO BE STARTED WITH THE KINDLE FIRE LAUNCHER OR GO LAUNCHER EX, I CHOSE GO LAUNCHER AND THEN IT GOT STUCK, I REBOOTED BY PRESSING THE POWER BUTTON FOR 10 SECS., TURNED IT ON AGAIN AND IT JUST GETS STUCK AT THE PLAIN KINDLE FIRE LOGO.
- I have watched some videos and read some articles saying that Go Launcher Ex can be installed for the KF without the device needing to be rooted, so when I tried it, everything mentioned above happened.
I hope somebody here can help me! This KF was a gift from my aunt and I don't want to be on the receiving end of a harsh scolding if she finds out I busted her gift. Thanks in advance and cheers!
brickboi said:
Hey guys! Back again. So noob me here has a new problem.
I CAN'T GET OUT OF NORMAL BOOT MODE! (Plain "Kindle Fire" logo but with dim backlight.)
These are what I did but to no avail:
- I tried switching it to fastboot mode, but everytime I do it, it becomes unrecognized by the device manager.
- And when I switch it back to normal boot mode, it just gets stuck there. (I HAVE NOT INSTALLED TWRP OR FFF OR ANYTHING ELSE FOR THAT MATTER BECAUSE THESE RECOVERY TOOLS NEED THE KF TO BE IN FASTBOOT MODE TO BE INSTALLED, BUT AS I SAID EARLIER, MY DEVICE GETS STUCK ON FASTBOOT MODE AND GOES UNRECOGNIZED, THAT'S WHY I DON'T HAVE TWRP AND FFF.)
Here is probably the most important info I can give.
I HAVE INSTALLED "GO LAUNCHER EX" ON MY KF AND AFTER THAT, I REBOOTED MY KF AND IT ASKED IF IT WANTED TO BE STARTED WITH THE KINDLE FIRE LAUNCHER OR GO LAUNCHER EX, I CHOSE GO LAUNCHER AND THEN IT GOT STUCK, I REBOOTED BY PRESSING THE POWER BUTTON FOR 10 SECS., TURNED IT ON AGAIN AND IT JUST GETS STUCK AT THE PLAIN KINDLE FIRE LOGO.
- I have watched some videos and read some articles saying that Go Launcher Ex can be installed for the KF without the device needing to be rooted, so when I tried it, everything mentioned above happened.
I hope somebody here can help me! This KF was a gift from my aunt and I don't want to be on the receiving end of a harsh scolding if she finds out I busted her gift. Thanks in advance and cheers!
Click to expand...
Click to collapse
Your only chance at fixing the device is with fastboot by installing TWRP and performing a factory reset. Work on getting your drivers working.
brickboi said:
Hey guys! Back again. So noob me here has a new problem.
I CAN'T GET OUT OF NORMAL BOOT MODE! (Plain "Kindle Fire" logo but with dim backlight.)
These are what I did but to no avail:
- I tried switching it to fastboot mode, but everytime I do it, it becomes unrecognized by the device manager.
- And when I switch it back to normal boot mode, it just gets stuck there. (I HAVE NOT INSTALLED TWRP OR FFF OR ANYTHING ELSE FOR THAT MATTER BECAUSE THESE RECOVERY TOOLS NEED THE KF TO BE IN FASTBOOT MODE TO BE INSTALLED, BUT AS I SAID EARLIER, MY DEVICE GETS STUCK ON FASTBOOT MODE AND GOES UNRECOGNIZED, THAT'S WHY I DON'T HAVE TWRP AND FFF.)
Here is probably the most important info I can give.
I HAVE INSTALLED "GO LAUNCHER EX" ON MY KF AND AFTER THAT, I REBOOTED MY KF AND IT ASKED IF IT WANTED TO BE STARTED WITH THE KINDLE FIRE LAUNCHER OR GO LAUNCHER EX, I CHOSE GO LAUNCHER AND THEN IT GOT STUCK, I REBOOTED BY PRESSING THE POWER BUTTON FOR 10 SECS., TURNED IT ON AGAIN AND IT JUST GETS STUCK AT THE PLAIN KINDLE FIRE LOGO.
- I have watched some videos and read some articles saying that Go Launcher Ex can be installed for the KF without the device needing to be rooted, so when I tried it, everything mentioned above happened.
I hope somebody here can help me! This KF was a gift from my aunt and I don't want to be on the receiving end of a harsh scolding if she finds out I busted her gift. Thanks in advance and cheers!
Click to expand...
Click to collapse
did yuo figure it out eventually?
i cant get my fire (stuck on logo, unknown device in windows) to connect to the utility tool or adb.
been trying different solutions for hours now.
thanks.
This should work:
If you have fff installed:
Copy the tools folder from KFU to your local disk.
Now power off your Kindle Fire all the way.(all doing)
Then open command prompt and type:
cd c:\tools
fastboot
fastboot getvar store
(now you should see <waiting for device>)
Now power on your Kindle. Now in cmd it should say finished and the time it took.(wating for device..... naver finishe)
Now copy TWRP to your local disk
Then type:
fastboot flash recovery c:\openrecovery-twrp-blaze-2.2.0.img(openrecovery-twrp-blaze certainly in to tool,)
fastboot oem idme bootmode 4000
fastboot reboot
Now as it boots up use your power button to boot into recovery and it should boot into TWRP.
naver ending wating for device~~~~~~~~~~~
cd c:\tools(recovery certainly into c
fastboot
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
(driver re-installing many times ,certainly driver install,well showing driver numbers)
don`t end ,naver ending~~~~~~~~~~wating for device
i wanna be korean keyboard,not needs markeet
You just said something that might be your problem because of how different korean characters are in your alphabet maybe just simply changing your computers language to english to complete the process will help
I was on CM 11. I wanted to restart fresh to I flashed
to KF 8.4.6 which worked fine. I then (this starts the
trouble) tried to reset device (remove personal data) from within kindle screens
1) rebooted to red screen
2) finally got into fastboot
3) tried this:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.3.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.6.0.0-recovery.img
fastboot -i 0x1949 reboot
4) it reboots and stays at yellow kindle fire logo
5) then I tried just this but same result:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
Any Ideas?? Please? I am not upset that I cant use it...I'm upset that I cant fix it!
Fixed it
Used SRT tool and finally realised also had to flash boot.img and recovery.img
Sent from my HTC One X using xda app-developers app
Haven't used my kindle for 6 months. Noticed today it just sits at the blue & white kindle fire logo.
If I hold the volume button down the Teamwin logo displays sitting there, nothing happens.
Hardware devices shows "Kindle" @ the Teamwin logo. I believe this is ADB.
If I just plug it in it shows Jem-PVT-Prod-04 with an exclamation.
edit: After about 5 hours I've determined the windows driver support is just ****. Using FWUL I can put the device into fastboot and send images. I sent a working copy of TWRP and now I cant enter TWRP at all, it just sits at the 2nd bootloader, ie. white and blue logo.
Code:
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
even erased cache and userdata, nothing. sits at the blue white logo and cant get into TWRP when pressing the down button.
edit: about 10 hours I finally figured out how to get it stuck in fastboot mode using linux and forced it to install the driver in windows. Even tried SRT 2.1, it flashes everything but upon reboot it shows a red swipe and automatically stays in fastboot mode.
I suspect something may be wrong with the device because issuing a fastboot oem idme bootmode 5001 after flashing twrp and freedom just locks up the device and fastboot will hang only displaying "..." unless I pull out the cable.
I'm over it.
Have you tried "oem idme bootmode 1" instead of 5001 ?