Been through a bunch of threads here and elsewhere trying to figure this out. My daughter brought her 1st gen KF to me last night with it stuck on the logo screen. Here's the things I've tried so far:
Hard reset (with power button): Held down for 20 seconds to a minute. Doesn't work.
Installed adb and fastboot on my Mac OS X system. I can get adb responses, "adb devices" returns <device ID> device. The KF will also reboot with the "adb reboot" command. I followed the suggestion at noelarlante.com/kindle-fire-stuck-at-boot-logo-solved (can't post link, new user), but when I ran the "adb shell /data/local/tmp/fbmode" command, it returned "couldn't write bp1, panic!"
Also tried running "adb shell idme bootmode 4000" and "adb shell idme bootmode 4002", but get permission denied as the response
Fastboot commands don't work, I just get <waiting for device>
On the Windows 7 side, I installed the Amazon drivers and the KF is recognized without any problems.
I then tried the Kindle Unbrick Utility (v1.1). If I run the "Stuck at logo" option, I get error: device not found, even though Device Manager lists the Kindle Fire without any issues (shows up as Android Composite USB Interface). "Recovery Loop" option leaves me at <waiting for device>.
Turning now to the Kindle Fire Utility (v0.9.9), the KF is listed as ADB Status: Online, but Boot Status: Unknown. Using the options on the bootmode menu, the KF will reboot, but I get the "couldn't write bp1, panic!" message and Boot Status stays unknown. If I try to install TWRP, "couldn't write bp1, panic!" comes up again, then <waiting for device>. Nothing more happens.
Any suggestions beyond what I've tried so far? The key step seems to be getting past the "couldn't write bp1, panic!" issue.
May need a fastboot cable.
How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Sent from my XT912 using Tapatalk
sd_shadow said:
May need a fastboot cable.
How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Click to expand...
Click to collapse
Yeah, I was wondering if the cable might be necessary. I'll give that a try and check back in when I've got it.
typ993 said:
Yeah, I was wondering if the cable might be necessary. I'll give that a try and check back in when I've got it.
Click to expand...
Click to collapse
Try the fastboot commands without cable first.
I meant to add that in first post.
Sent from my XT912 using Tapatalk
sd_shadow said:
Try the fastboot commands without cable first.
I meant to add that in first post.
Click to expand...
Click to collapse
See OP, fastboot commands just give me the <waiting for device> prompt, only the adb commands work. Hoping the cable gets around that.
typ993 said:
Been through a bunch of threads here and elsewhere trying to figure this out. My daughter brought her 1st gen KF to me last night with it stuck on the logo screen. Here's the things I've tried so far:
Hard reset (with power button): Held down for 20 seconds to a minute. Doesn't work.
Installed adb and fastboot on my Mac OS X system. I can get adb responses, "adb devices" returns <device ID> device. The KF will also reboot with the "adb reboot" command. I followed the suggestion at noelarlante.com/kindle-fire-stuck-at-boot-logo-solved (can't post link, new user), but when I ran the "adb shell /data/local/tmp/fbmode" command, it returned "couldn't write bp1, panic!"
Also tried running "adb shell idme bootmode 4000" and "adb shell idme bootmode 4002", but get permission denied as the response
Fastboot commands don't work, I just get <waiting for device>
On the Windows 7 side, I installed the Amazon drivers and the KF is recognized without any problems.
I then tried the Kindle Unbrick Utility (v1.1). If I run the "Stuck at logo" option, I get error: device not found, even though Device Manager lists the Kindle Fire without any issues (shows up as Android Composite USB Interface). "Recovery Loop" option leaves me at <waiting for device>.
Turning now to the Kindle Fire Utility (v0.9.9), the KF is listed as ADB Status: Online, but Boot Status: Unknown. Using the options on the bootmode menu, the KF will reboot, but I get the "couldn't write bp1, panic!" message and Boot Status stays unknown. If I try to install TWRP, "couldn't write bp1, panic!" comes up again, then <waiting for device>. Nothing more happens.
Any suggestions beyond what I've tried so far? The key step seems to be getting past the "couldn't write bp1, panic!" issue.
Click to expand...
Click to collapse
OP says nothing about fastboot commands.
See fourth bullet point in list above.
Will the fastboot cable override whatever has failed to keep the KF stuck in the boot loop? If the KF is accepting (some) adb commands, does that imply it is in normal bootmode?
Thanks again, got the cable ordered.
typ993 said:
See fourth bullet point in list above.
Will the fastboot cable override whatever has failed to keep the KF stuck in the boot loop? If the KF is accepting (some) adb commands, does that imply it is in normal bootmode?
Thanks again, got the cable ordered.
Click to expand...
Click to collapse
Fastboot cable forces Kindle into fastboot mode.
Sent from my XT912 using Tapatalk
Problem is solved. Here's what I did:
As sd_shadow suggested, I got a fastboot cable. This worked to get the KF into fastboot mode.
Once in fastboot mode, I was able to use Kindle Fire Utility to load FireFireFire and TWRP onto the Kindle.
TWRP from KFU was kind of an old version, so I got the latest version and did a fastboot flash recovery to load up that newer version.
Also downloaded the stock Kindle ROM. For some reason, the sdcard partition wouldn't mount in my Win7 VM, but did mount on my Mac, so copied update.zip from there.
TWRP (2.8.5.0 otter) then wouldn't install the ROM. Tried loading in the 2.8.5.0 blaze version, same deal.
Some Googling on this same problem turned up the fact that TWRP 2.2.2.1 would correctly install the Amazon ROM, which in fact it did. Later builds must have some kind of bug, but if this only affects 1st gen KF's, probably not an urgent one.
Rebooted and back in business. :good:
Fastboot cable is the key ingredient in this situation.
Twrp versions 2.8.X.X have issues for some people, use 2.7.1.0 for custom Roms, 2.2.2.1 for stock.zips
Sent from my XT907 using Tapatalk
Related
I have just bought Kindle. So i try to root and install TWRP recovery for my Kindle. After installing TWRP, because don't look Super User icon in Kindle; I took hard-reset my device in Settings. And Now My Kindle boot Logo Kinder Fire stuck on here.
What problem ???? Please help me....... i don't know i had just done nothing. Thanks guys !
I try to text in command dos: "add shell" but it show may Laptop Screen:
- exec '/system/bin/sh' failed: No such file or directory (2) -
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
I'm having this same problem. It's apparently stuck in fastboot. I can't even figure out how to type in adb commands or fastboot commands (meaning I could before and now when I tried it says command not found, but I didn't change anything. It won't recognize my device and when I try installing the android-winusb.inf it says it won't let me. I don't know what else to do. Any help would be appreciated. My Kindle is listed as unspecified device.
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
g1no23 said:
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
But Boot Status show: Unknow, so when i type this text comandos show: waiting device
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
lovejoy777 said:
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
thanks guy much. But i tried all, i used KFU to try installing Recovery ( CMW, or TWRP), try to plug in USB Kinlde, press power button, etc. But It'S seem not working, all show: " exec- system/bin/sh failed ; not such file orr folder "
i also use tool KF Unbrick on XDA, but it's too. Reply show: " -exec- "system/bin/sh"...
Can U know that what problem in "system/bin/sh" of Kindle Fire ???????
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
works perfectly for me too! awesome!
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
thanks but my kindle don't have TWPR recovery after i've just flashing office room 6.2.1 from Amazon. Now it stuck in my logo Kindle
tunglx1988 said:
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Serinety said:
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
thanks for repl. But My Kindle Logo is Stuck in here. open KFU then show : Boolloader: UnKnow. So i don't know it bootmod ??? ( recovery, Normal, or fastboot).
b63 said:
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
he is absolutely right, this happened to me and nothing would work until I got a factory cable
This is a typical problem with KFU.
You need to go to your device manager and uninstall both the adb and android drivers then reinstall them manually. Sometimes it helps to restart your computer and Kindle afterwards. Make sure your device manager says both "Android Phone" and "Android ADB Interface" NOT "Other Device" and "Kindle".
When you are stuck at the boot screen it means you are in fastboot mode. In fastboot mode your device will only recognize fastboot commands. If your device doesn't recognize fastboot commands (KFU uses fastboot commands to change boot modes), 99 times out of 100, it's a driver issue.
A factory programming cable, while nice to have, is not usually necessary. A factory programming cable does two things. It provides power directly to the device instead of the battery AND forces the device into fastboot mode (stuck at boot logo). Since most of you with this problem are ALREADY in fastboot mode, a factory cable would be pointless.
Make sure you are 100% certain that you have the correct drivers installed and configured properly and then use the command prompt to change your bootmode to 4000.
In command prompt, navigate to the folder that contains fastboot.exe and enter the following commands...
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Sent from my Amazon Kindle Fire using xda premium
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
soupmagnet said:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Click to expand...
Click to collapse
jingcleovil said:
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
Click to expand...
Click to collapse
i have the same problem as you it fills good to not be the only one
First off, thanks to everyone on here who's posted numerous help guides that have helped me in the past. I've rooted several phones in the past and figuered I'd try to root and install Jelly Bean on a Kindle Fire I won at a work event (woohoo!).
The problem right now is the kindle is stuck in fastboot (no root, twrp installed) it boot into the non-animated white and orange "kindle fire" logo screen and stays there.
What I did to put it there:
On a Windows 7 machine, I used KFU 0.96. After reading instructions, I installed TWRP.
Since then, it is not repsonding to adb commands. It will mount the drive to the computer, and the drivers show it's using the correct one from Google Composite device.
After researching, I found someone who mentioned that after several restarts, and smashing "normal boot" commands thru adb while the kindle was starting up (and before it went unresponsive) he was able to move along. When I did this (with KFU), Kindle went into TWRP. From there I followed instructions on flashing pre-rooted 6.2.2 (as the guide indicated, doing wipes) but the flash always failed.
Assuming something wasn't working with Windows, I've gone home to my macbook running Ubuntu 12.04, and while installing SDK from Google, I can not figure out how to get the google sdk running. I followed this guide http://forum.xda-developers.com/showthread.php?t=1550414 but I can't get to step 5, I cannot get the Android SDK Manager to run!!
I have access to dozens of Windows computers, I'm fine with going back to them, but everything I've read makes me think I've got a better shot with Linux due to driver problems on windows.
Also, when I had TWRP loaded on the Kindle, and connected it to KFU 0.96 it said my boot mode was 0x5003.
fastboot commands will not execute. I'm sending them like this:
(Devices list)
[email protected]:~/Android/KR$ ./adb-linux devices
List of devices attached
???????????? no permissions
fastboot:
[email protected]:~/Android/KR$ fastboot getvar product
fastboot: command not found
Someone had a similar problem here- http://forum.xda-developers.com/showthread.php?t=1765546 but I want to see if I should follow that thread or try something else instead, before I go making more changes.
Thanks for reading! Will gladly send pizza to someone who can help
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
veeman said:
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
Click to expand...
Click to collapse
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Josepho1997 said:
Try uninstalling and reinstalling the drivers. If your in fastboot mode, adb wont work. After reinstalling the drivers, type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If the drivers installed correctly, these commands should work and get you out of fastboot(which it seems your stuck in)
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
drivers installed. command input. no response. Id like to install screenshots, but I'm new user.
hardware driver reads Google ADB interface 4.0.0
c:\KFU\tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
.....nothing?!
wheelzr said:
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Click to expand...
Click to collapse
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
kinfauns said:
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
Click to expand...
Click to collapse
So, witout popping the cover and screwing with the mobo this thing is bricked?
wheelzr said:
So, witout popping the cover and screwing with the mobo this thing is bricked?
Click to expand...
Click to collapse
</thread>
Just sold the kindle on craigslist for $40 as a bricked device.
wheelzr said:
Just sold the kindle on craigslist for $40 as a bricked device.
Click to expand...
Click to collapse
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
kinfauns said:
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
Click to expand...
Click to collapse
for real, I probably would have paid $50-60 too, it should be an easy fix with a factory cable. (which I already have one of after I bricked my kindle once)
Also, as a side note - Amazon will replace it for $100 "not under warranty" because you bricked it through the tinkering process.
Actually, it turned out better than I could have planned. I told the company whom gifted to me t did not work, they sent a bike ,messenger to exchange it for me! Naturally the first thing I did with the new one was fire up kfu .96 and it worked perfectly this time. Stoked on this hashtaag jelly bean ROM. Hate the keyboard tho. And Google cards are fc'ng.
Love life.
Sent from my Amazon Kindle Fire using xda app-developers app
my kindle is stuck on the boot screen (not fastboot) and when i plugged it into my computer it would show as an android phone, please help me get the unbricking utility to recognize my device. when i run command and i type "cd computer/users/etc." then type in "adb kill-server" then "adb devices" and nothing shows. yes i am a noob so please help.
jbQsad said:
my kindle is stuck on the boot screen (not fastboot) and when i plugged it into my computer it would show as an android phone, please help me get the unbricking utility to recognize my device. when i run command and i type "cd computer/users/etc." then type in "adb kill-server" then "adb devices" and nothing shows. yes i am a noob so please help.
Click to expand...
Click to collapse
What were you doing when it got stuck at the bootlogo? Have you tried some fastboot commands to see how it responds?
Even if it's not in fastboot mode, see if you can get it there...
http://forum.xda-developers.com/showthread.php?t=1668159
If you can get it into fastboot mode and issue fastboot commands to it, you can change bootmodes, flash a recovery, or whatever else to get the device booting again. There's also a part in the above post to figure out what hardware ID is getting sent to Windows. That will be important in determining what your KF is doing.
kinfauns said:
What were you doing when it got stuck at the bootlogo? Have you tried some fastboot commands to see how it responds?
Even if it's not in fastboot mode, see if you can get it there...
http://forum.xda-developers.com/showthread.php?t=1668159
If you can get it into fastboot mode and issue fastboot commands to it, you can change bootmodes, flash a recovery, or whatever else to get the device booting again. There's also a part in the above post to figure out what hardware ID is getting sent to Windows. That will be important in determining what your KF is doing.
Click to expand...
Click to collapse
i was rooting and ran out of battery. and i would fast boot it but my kfu wont recognize my kindle even when its in adbinterface
Is it charging?
im not sure
Thepooch said:
Is it charging?
Click to expand...
Click to collapse
its plugged into the computer but since its at the boot logo i cant tell. the light is green on the bottom if that means anything
Maybe try another machine and attempt to reset the bootmode
Ok, I am attempting to root my Kindle Fire running 6.3.1, I am new to rooting so bear with me. I have downloaded the latest KFU and can't seem to get the ADB status to show as online. So I downloaded SDK and zergRush when I use the SDK platform tools in the windows cmd and use "adb devices" it shows that it is connected, attempt to push zergRush get the hellions with blue flames error. zergRush not working. How can the device be connected when I'm running SDK but the KFU won't recognize that it is connected. I have tried to push fbmode to it and it says access is denied. Is there something I'm missing here? I want to root and install jellybean. Please help.
would recommend to read this first to understand how it works:
http://forum.xda-developers.com/showthread.php?t=1552547
then:
http://forum.xda-developers.com/showthread.php?t=1638452
in fastboot mode cant flash twrp
ok, now i think i have a problem for real. sorry for being so retarted about this, when i started to reboot into recovery to install FFF i missed part of the command in fastboot -i 0x1949 reboot now it just says waiting for device.....
could you try "fastboot -i 0x1949 getvar product" and "fastboot getvar product" - one should return "kindle" to test if fastboot is working.
i use to put the .img file in the same directory where the fastboot.exe is located.
furthermore i use c:\adb or something like this to avoid long path names and special characters.
do you still have the original bootloader or fff ?
device not connected...
it still says waiting for device, the kindle is at the stock kindle boot screen, but my computer made the device disconnect and reconnect noises so i checked the device manager and now it says unknown device under USB controllers.... i think i messed up.
what do you mean with stock kindle boot screen ?
the orange "kindle fire" or the unlock screen of the system ?
if you have the unlock screen simply plug the kf off and power it down.
reinstall the drivers (install_drivers.bat) and then plug it in again - it should power on by itself.
boot screen
silver and orange kindle fire screen
nevertheless you have a driver issue and have to reinstall the drivers.
the kf seems to be in fastboot mode ...
unknown device
I tried re-installing the drivers manually and it says drivers are up to date for "unknown device" when I use the driver installer that came with KFU it says the drivers are installed properly.
gave you a pm ...
So, I know not supposed to post questions that are lame, but I can't seem to figure this out. I will state my specs/situation:
I am stuck on the first step of installing FFF on my first Kindle Fire 1st gen.
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
The kindle fire is in fastboot mode (I'm pretty sure, at least).
It is stuck on the stock Kindle fire boot-up logo.
install_Drivers was run successfully after enabling unsigned driver installs.
Run.bat was executed
selected Option 5 first, to install FFF
FFF was downloaded by KFU, the Fire rebooted and then got stuck.
As it rebooted, I had forgotten to automatically have my Fire connect to the Virtual Machine, so VMWare prompted my with what system I wanted the fire connected to. I'm not sure if that delay has something to do with the stall and failure of KFU to install FFF or get out of fastboot.
KFU doesn't recognize the Kindle ("waiting for device" message; ADB: Offline; Boot Status:Unknown).
In my "other devices" on Windows Device Manager I see "Base System Device" and "Unknown Device"
My questions are:
1. How do I go about getting it out of fastboot mode even though KFU can't see the device.
2. What was I doing wrong in the first place?
Before you tell me:
I have read through the Guide
I have read through and searched much of the KFU dev thread
I have searched the forums, without a clear solution.
Thank you very much for your help!!!
escoloader said:
2. What was I doing wrong in the first place?
Click to expand...
Click to collapse
This:
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
Click to expand...
Click to collapse
Use breakdroid instead
Sent from my Amazon Kindle Fire HD using Tapatalk 2
soupmagnet said:
This:
Use breakdroid instead
Click to expand...
Click to collapse
How do I get it back to normal booting first?
Thanks for your help!
escoloader said:
How do I get it back to normal booting first?
Thanks for your help!
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thank you for the help, but could you please explain how I use that code, step by step if possible?
Thanks a lot
EDIT: I guess I should specify, I do NOT have a fastboot factory cable. Do I need one?
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Thepooch said:
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Click to expand...
Click to collapse
Did the first one, but still says "waiting for device" and nothing is happening. :/ (EDIT: for clarity's sake, nothing happening means its still stuck on the kindle fire white/orange stock boot logo)
btw, thank you for your help.
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
soupmagnet said:
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
Click to expand...
Click to collapse
still says "waiting for device" in the terminal.
also, windows still comes up with "usb unrecognized" message at the bottom right of my screen.
What's next?
Thanks for joining to help, soupmagnet
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Thepooch said:
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Click to expand...
Click to collapse
Still doesn't show up. (It also occasionally crashes my mac system when I plug the kindle in now :/ )
If I get a factory cable, will that likely solve this easily?
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thepooch said:
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Click to expand...
Click to collapse
Got it! Using Breakdroid, I was able to capture the Kindle as it powered on. I believe my main problem was that there was a significant enough delay in connecting the Kindle via USB to the Windows Virtual Machine, that the ADB couldn't access it in time to capture it. Or whatever.
Solution: I used BreakDroid on my Mac. Turned the kindle off, then back on while Breakdroid was waiting for my device to perform Step 1 on Breakdroid's Kindle Tools. Then it immediately captured the Kindle when I powered it on. Went through the steps on Breakdroid, and it's working with bootloader and recovery
Works great! Have all my stuff back. And...it's rooted
THANKS FOR ALL YOUR HELP, GUYS!
EDIT: Now how do I install Google Play?