Develop Bugs

[Q] Problems with rooting Kindle fire

Hi,
sorry in advance for my English - I am from Germany...
Maybe this is a stupid one but I am struggeling with rooting my kindle fire. Before running the installing_drivers.bat the Kindle was shown as 'Kindle' in the device manager after installing the drivers as 'Android Composite ADB Interface' which seems to be correct.
After starting run.bat I always get the following messages:
ooops... something went wrong
We are unable to locate your Kindle Fire.
Make sure it is plugged in and powered on.
trwp.img has been found.
fff.bin has been found.
Fastboot uses a different device than ADB
you should check device manager for Kindle or Amazon
if you see it rerun the driver installer that came packaged with KFU
installing FFF
#waiting for device#
now - nothing happens any more. Any idea what went wrong or what kind of mistake I made? (The kindle is plugged in an powered on )
Thanks for your support
Kerstin

Does your device enter fastboot? Does kfu indicate your device online boot status 4000. http://forum.xda-developers.com/showthread.php?t=1923010

Thepooch said:
Does your device enter fastboot? Does kfu indicate your device online boot status 4000. http://forum.xda-developers.com/showthread.php?t=1923010
Click to expand...
Click to collapse
All I can see it the message I mentioned before.

When you start kfu with your device plugged in it should indicate the status of the device, whether its online or offline and the boot status. This is a first gen kindle fire isn`t it?

Thepooch said:
When you start kfu with your device plugged in it should indicate the status of the device, whether its online or offline and the boot status. This is a first gen kindle fire isn`t it?
Click to expand...
Click to collapse
And exactly that is the problem, it showed the device online the very first time I tried it but also showed this 'oooops.... something went wrong, we are unable to locate your kindle fire' in the beginning. It stuck with the message 'waiting for device'. after an hour or so I disconnected the device and gave it another try since that time I always get the above described message and do not get any more to the info if device is on or offline. Attached a screenshot of the failure message. :crying:
And yes it is a first gen.

[email protected] said:
And exactly that is the problem, it showed the device online the very first time I tried it but also showed this 'oooops.... something went wrong, we are unable to locate your kindle fire' in the beginning. It stuck with the message 'waiting for device'. after an hour or so I disconnected the device and gave it another try since that time I always get the above described message and do not get any more to the info if device is on or offline. Attached a screenshot of the failure message. :crying:
And yes it is a first gen.
Click to expand...
Click to collapse
Yeah I cant open that file you attached but if it says waiting for device simply try powering it off then back on again as well did you read my tutorial?

[Q] KF 1st stuck at logo after return to rom stock

My KF using TWRP and CM7. Recently, I returned to rom stock but it failed. Now, it stuck at logo "kindle fire" and I can't find how to boot it. When connect KF to computer, in Computer Magement, it shows android phone and F driver in portable device. About sdcard, whenever I click to F driver, it always request "please insert a disk". When using KFU, the status of ADB is offline, boot status is unknown, any method of boot using cmd, it alway said "waiting for device..."
Please help me to resolve it!!!!!

If it's a kindle fire 1, I think you need to either reflash the boot loader and twrp, or use fastboot to clear the data partition, but that may wipe the contents of the sdcard. At least i think this is what needs to be done, I have a kf1 lying around, but this is the second generation kindle fire forum, so I think a mod should move this... You will probably get better answers there. If you are having a driver issue try updating uninstalling and updating with the drivers in my SIG, they have some basic support for kf1's I believe since I occasionally mess with my moms kf1.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
If it's a kindle fire 1, I think you need to either reflash the boot loader and twrp, or use fastboot to clear the data partition, but that may wipe the contents of the sdcard. At least i think this is what needs to be done, I have a kf1 lying around, but this is the second generation kindle fire forum, so I think a mod should move this... You will probably get better answers there. If you are having a driver issue try updating uninstalling and updating with the drivers in my SIG, they have some basic support for kf1's I believe since I occasionally mess with my moms kf1.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks so much for your advice. But I don't know how to fastboot or reflash if my computer not recognized the kindle, all of the command in cmd has the same error "waiting for device.." or "device not found.." even i push the on/off button several time

takieuanh said:
Thanks so much for your advice. But I don't know how to fastboot or reflash if my computer not recognized the kindle, all of the command in cmd has the same error "waiting for device.." or "device not found.." even i push the on/off button several time
Click to expand...
Click to collapse
I also try to use the command "fastboot -i 0x1949 oem idme bootmode4000" but it respond "waiting for device..." then I turn the button on and off several times but it didn't work.
When using adb shell "idme bootmode4002" in windows safe mode it responded
"* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon"
Anyway, I donn't know how to place the thread in a suitable postion in the Forum. (Thanks mod if you could help to not delete it or move to a suitable position)

I've reported the thread, so it should be in the right position soon.

takieuanh said:
I also try to use the command "fastboot -i 0x1949 oem idme bootmode4000" but it respond "waiting for device..." then I turn the button on and off several times but it didn't work.
When using adb shell "idme bootmode4002" in windows safe mode it responded
"* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon"
Anyway, I donn't know how to place the thread in a suitable postion in the Forum. (Thanks mod if you could help to not delete it or move to a suitable position)
Click to expand...
Click to collapse
Thanks so much Mod for move thread.
Is there anyone could help me please. Thanks so much

First Gen Kindle Fire Stuck in Kindle Fire logo bootloop

I have a first gen Kindle that I am trying to unbrick. I've followed many instructions and I eventually get stuck. The problem is, I've followed these directions:
http://forum.xda-developers.com/showthread.php?t=1602560
Now, when I get to the last part, where you have to type in adb in command prompt to list the devices, my device won't show. When I go into to the device manager, i see the kindle icon with a yellow triangle, i try to manually install it, and I direct the path, it starts to install and gives me the following error:
"Windows found driver software for your device but encountered an error while trying to install it
Android ADB Interface
The hash is not present in the specified catalog file. The file is likely corrupt of the victim of tampering."
How do I fix this? Can anyone please direct me to any way I can resolve this issue and get my Kindle to boot normally? Thanks.

[Q] Kindle Fire Root Gone Wrong No ADB Status

Like many here I'm a bit of a noob. I have rooted my LG Optimus Q quite successfully and it was far more complicated than the Kindle Fire Utility. When I first ran it it did install superuser (which got uninstalled by my daughter...) but I was never able to boot into TWRP. I've tried re running KFU many times & even tried it on a spare XP machine with the exact same results.
I can get the kindle to display ADB status of Online but boot status always remains Unknown. The bootmode commands will reboot but KFU never updates the boot status. It always remains unknown. When attempting to run "Install permanent root with superuser" I get this:
1 [main] cat 3900 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointe
r. Please report this problem to
the public mailing list [email protected]
1 [main] cat 4596 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointe
r. Please report this problem to
the public mailing list [email protected]
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
< waiting for device >
Then the Kindle reboots back to the slide screen.
Using KFU 0.9.9 (tried some previous versions also)
I'm running an Intel Gateway laptop with Win 8.1
I believe the USB is 3.0
The other machine I tried to use is an AMD 950 with XP
USB 1.1
The drivers on both machines are listed in device manager as Android Composite ADB Interface.
I'm assuming the root of the problem is ADB and/or not using USB 2.0 but honestly I'm lost at this point. Any help would be so greatly appreciated.
*EDIT*
Never thought to check my sw version and it's in fact 6.3.3 so unless there's some other method I guess it's off to make a moto factory cable.

[Q] Rooting Kindle Fire Using Saferoot and KFU 0.9.9

Hi all,
I've spent the last hour or so looking over posts, trying to solve my problem. Neither Saferoot nor KFU will root my device.
Step-by-step of my Saferoot attempt:
1. Install drivers (from KFU) and reboot PC
2. Run "install.bat"
3. Type "Y" for BusyBox
4. Prompted to plug in device... plugged in my KF
5. I am told:
"Watch your phone. If you see the "Allow USB debugging?" prompt. Tap on the "Always allow from this computer" checkbox then tap ok.
If this script appears to be stuck at "Waiting for your phone to appear", then you should tap on the USB icon in the notifications that says "Connected as a media device". On the "USB computer
connection" page, switch between "Camera" and "Media Device" to see if the device appears.
[*] Waiting for your phone to appear"
The thing is, there is no option to allow USB debugging (there is no prompt on the KF), and neither is there a USB icon in notifications. All I see on the screen is an image of a USB plug and a message stating "You can now transfer files from your computer to Kindle" and a button to Disconnect. Using Saferoot, I'm stuck here.
Step-by-step of my KFU attempt:
1. Ran "install_drivers.bat" and rebooted PC
2. Ran"run.bat"
3. ADB Status: Online
Boot Status: Unknown
4. Began to "Install Permanent Root with Superuser"
5. I was given this message:
5251 KB/s (510876 bytes in 0.095s) couldn't write bp1, panic!
The kindle has been told to reboot in Fastboot Mide.
twrp.img has been found
fff.bin has been found
***Notice***
Fastboot uses a different deice that ADB. You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF... (waiting for device)
6. I went to Device Manager and saw something labeled "Kindle Fire". I reran the install_drivers.bat
7. Now "Kindle Fire" has disappeared and "SAMSUNG Android Phone" has replaced it
8. Nothing happened either on the Kindle Fire or in KFU for the next 5 minutes
Am I doing something wrong? I'm not 100% sure I'm doing this right, even though I followed that guide. If anyone wants to help, I can Skype, thus helping to facilitate the process.

nativemaxican said:
Hi all,
I've spent the last hour or so looking over posts, trying to solve my problem. Neither Saferoot nor KFU will root my device.
Step-by-step of my Saferoot attempt:
1. Install drivers (from KFU) and reboot PC
2. Run "install.bat"
3. Type "Y" for BusyBox
4. Prompted to plug in device... plugged in my KF
5. I am told:
"Watch your phone. If you see the "Allow USB debugging?" prompt. Tap on the "Always allow from this computer" checkbox then tap ok.
If this script appears to be stuck at "Waiting for your phone to appear", then you should tap on the USB icon in the notifications that says "Connected as a media device". On the "USB computer
connection" page, switch between "Camera" and "Media Device" to see if the device appears.
[*] Waiting for your phone to appear"
The thing is, there is no option to allow USB debugging (there is no prompt on the KF), and neither is there a USB icon in notifications. All I see on the screen is an image of a USB plug and a message stating "You can now transfer files from your computer to Kindle" and a button to Disconnect. Using Saferoot, I'm stuck here.
Step-by-step of my KFU attempt:
1. Ran "install_drivers.bat" and rebooted PC
2. Ran"run.bat"
3. ADB Status: Online
Boot Status: Unknown
4. Began to "Install Permanent Root with Superuser"
5. I was given this message:
5251 KB/s (510876 bytes in 0.095s) couldn't write bp1, panic!
The kindle has been told to reboot in Fastboot Mide.
twrp.img has been found
fff.bin has been found
***Notice***
Fastboot uses a different deice that ADB. You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF... (waiting for device)
6. I went to Device Manager and saw something labeled "Kindle Fire". I reran the install_drivers.bat
7. Now "Kindle Fire" has disappeared and "SAMSUNG Android Phone" has replaced it
8. Nothing happened either on the Kindle Fire or in KFU for the next 5 minutes
Am I doing something wrong? I'm not 100% sure I'm doing this right, even though I followed that guide. If anyone wants to help, I can Skype, thus helping to facilitate the process.
Click to expand...
Click to collapse
System version on the kindle fire?
Sent from my XT907 using Tapatalk

sd_shadow said:
System version on the kindle fire?
Click to expand...
Click to collapse
6.3.4_user_4120220

I scrounged my house looking for the original Kindle Fire cable. Once I found it, I ran Saferoot using that, which caused it to work.
(Coincidentally, I was following your tutorial on YouTube @sd_shadow)