Develop Bugs

[Q] KFU - No success - Kindle not found or Path not found

Hi, noob here. Searched but could not find answer...
Running Windows 7 x64. Attaching KF via USB and tapping "disconnect" after it installs it as USB drive.
Trying to root kindle fire for first time using KFU 0.9.5. Put KFU files/folders into new directory called KFU on root of C: drive. Device drivers seem to install ok and device manager indicate "ADB device" (not "kindle").
when i run kfu normally, it cannot find my kindle. (and "ADB Status offline")
when i run kfu as "administrator" ADB Status shows Online but I get "windows cannot find tools\wget", then many "system cannot find the path specified" errors and i get stuck at the "read me" saying "do NOT unplug kindle if we are stuck here..."
(in both of above, KFU shows boot status as "unknown")
Anything else i can try?
TIA

http://www.youtube.com/watch?v=mwMHIkX20YI
try to follow this steps to steps video from nat3mil.It should be helpful.
But always make sure that you know what you are doing for every single steps you take.even if its a small one.
if not,ask here and wait until you get a reply.
i don't want people to follow my footsteps causing myself trouble.Hope this helps.
And if you patient enough.try to root and flash recovery manually.its safer since you know what you are doing.

Help! Bricked my Kindle Fire

I attempted to root my Kindle Fire (which was running 6.2.2) using the Kindle Fire Utility v0.9.5. KFU appeared to run successfully and my Kindle was fine (started up OK). But, when I ran Root Check Pro, it showed KFU didn't succeed with rooting. I thought maybe KFU was unsuccessful because KFU v0.9.5 works on Fire firmware 6.3 and up (and not on 6.2.2).
Then, I tried to update the Fire firmware to 6.3.1 from the Amazon site, thinking I'd run KFU v0.9.5 again after the firmware update. I didn't think to uninstall any of the KFU installed rooting software (like superuser or TWRP) before trying the update because the root was unsuccessful.
My Fire started the update but stopped almost immediately and got stuck at the TWRP yellow-triangle logo. Also, my laptop (running Window 7) won't recognize the Fire when I plug it in with a USB cable.
When I set my laptop Device Manager to show hidden devices, "Android Phone" appears as a device. When I expand it, I see "Android ABD Interface". The Android Phone device displays for a few seconds and then disappears. If I shutdown my Kindle Fire and power it on again, the device manager does the same thing.
[FYI - I successfully rooted another Fire (though it was running 6.3) using KFU v9.0.5 on this same laptop so the Kindle Fire drivers for Windows were installed.]
Because of this behavior, none of the unbricking, KFU, or ABD utilities/commands are getting through to the my Fire. The Kindle Fire Unbricking utility, for example, will start but almost immediatley close the Windows Command window.
I don't know what to do when your laptop won't recoginize the Fire as a connected device. Is there any thing else I can try? I'd appreciate any help with this I can get!!

Go here
...and download FFF1.4
Mount your sdcard in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"

If you get things working and decide you want to root again I would highly suggest side loading the superuser.apk. Root Check Pro might have discovered no root because the su.apk was missing (just a thought). This is an issue with KFU. I've rooted 4 kindles and not once has it installed the su.apk.

I also had to side load superuser and Google Play. Here is a great link on this forum to help with that:
http://forum.xda-developers.com/showpost.php?p=24312196&postcount=17

Soupmagnet - thanks so much for the reply!
One question >> how do I 'mount the SD card in recovery'?
Long press on the Fire power button does nothing - doesn't launch TWRP in recovery mode. Entering commands in a Command window from my laptop isn't getting through to my Fire. And, as I mention above, the Kindle Fire device won't stay available in my laptop Device Manager for more than a split second.

morgan4k said:
Soupmagnet - thanks so much for the reply!
One question >> how do I 'mount the SD card in recovery'?
Long press on the Fire power button does nothing - doesn't launch TWRP in recovery mode. Entering commands in a Command window from my laptop isn't getting through to my Fire. And, as I mention above, the Kindle Fire device won't stay available in my laptop Device Manager for more than a split second.
Click to expand...
Click to collapse
This is a tricky situation because you need to replace your device drivers, but you can't replace your drivers if you don't have access to them. I haven't come across a situation like this before last night so I wouldn't know how to fix your device manager issues.
You could however, try a different computer (easiest), OR create a bootable Linux LiveUSB thumb drive to boot from your laptop and set up the environment for issuing adb/fastboot commands. IMO, that would probably be the best route considering Linux's overall stability but it would definitely be the trickiest.
There are tutorials here for setting up Linux to use adb and fastboot and I'll add them as soon as I find them.
Setting Linux up for adb and fastboot can be tricky but there are plenty of Linux users here that can help with that.
Once you get everything set up, (re)install TWRP and continue wth the previously posted tutorial.
[Edit:] Actually, I have a better idea if you're using the LiveUSB and you wouldn't need to set up adb and fastboot.

Thanks for a great summary! Unfortunately even after sideloading superuser.apk, I still have read-only rights on / and the system directories under it that (would) allow me to copy over vending.apk. Yes, I am superuser when I try.
I have no problems becoming superuser, and OTA Rootkeeper works to switch back and forth.
The three things that do not work are write access to /system/app in order to switch out vendor.apk, mounting a drive as read/write, and from my PC am unable to use the adb remount command. All see outcomes of the same permissions issues.
Anyone seen this, and found the cause?
Thanks.

Are you positive your rooted download root checker verify root if you get red writing your not rooted

[Q] Why is kfu not recognizing my kf as being online?

Hey everybody, sorry for not introducing myself properly, but I really do need some help with rooting my kf. Basically I've installed the drivers properly and my device manager does show my device as "Android Composite ADB Interface", but when I run kfu, ADB status is "offline" and Boot status is "unknown". Even if I do try to install the permanent root with superuser, I get a notice saying "Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on." I find this maddening since it obviously is.
Please help!
P.S. kfu does say twrp.img and fff.bin have been found and it does try to install FFF, but I just get the message <waiting for device>.

First of all make sure you are using a proper cord . Only use 2.0 usb port. If when you start kfu the you get online boot status 4000 then your good. If not there is still something to work out. If all is good when starting make sure you have allowed installation from unknown sources under device and you have disconnected the mass storage application. Recheck device status. In device manager there should not be an exclamation mark next to android adb composite interface or the driver is incorrect. Having all the things correct kfu should indicate your device online. Its pointless to do anything until it is.

How do I disconnect the mass storage application?

[Q] Another nOOb got his Kindle Fire stuck in fastboot mode.

Good evening all. Here I am, another nOOb who ended up getting his Kindle Fire stuck in fastboot mode. I've read through the forums for about a week and a half and tried to apply some of the suggestions with no luck. I'm using a 32bit Windows 7 Home Premium desk top computer and am using the KFU 0.9.6. The Kindle fire is in stock mode stuck at the white and yellow boot logo. My computer recognizes the Kindle Fire as an Andriod Phone>Android ADB Interface but I have the yellow exclamation and in the properties it reports a code 10 error. (see attachment 1.) I tried uninstalling and re-installing the driver's by the cut and paste below. post #2 again with no luck.
If the Kindle Fire comes up as a different device or you get a "Code 10" error, you'll have to explicitly tell Windows what driver you expect to see for the device. The steps below are for Windows 7, but they should be very similar for earlier versions of Windows as well. The following may have to be performed twice, once for normal mode and again for fastboot mode. The steps below are listed for normal mode (and the fastboot equivalent in parentheses). Be sure to have tried installing the drivers using the batch file at least once or you will not be able to complete the process.
*Connect the Kindle Fire in normal mode (fastboot mode) to the computer
*In the Device Manager, right click on the device and select "Uninstall"
*Check the "Delete the driver software for this device." box and press "OK"
*Disconnect the Kindle Fire, reconnect and reboot in normal mode (fastboot mode)
*The Device Manager should show "Other devices -> Kindle" ("Other devices -> kindle")
*Right click on "Kindle" ("kindle") and select "Update Driver Software..."
*Select "Browse my computer for driver software"
*Do not click the "Next" button, but select "Let me pick from a list of device drivers on my computer"
*Select "Android Phone" and then press the "Next" button
*Press the "Have Disk..." button
*Click the "Browse..." button, point it to the "C:\kfu\drivers\kindle" directory and press "Open"
*Press the "OK" button
*Uncheck the "Show compatible hardware" checkbox
*Select "Android Composite ADB Interface" ("Android ADB Interface") and press the "Next" button
*Select "Install this driver software anyway"
*Press the "Close" button
The device should now appear in the Device Manager.
I tried this suggestion post #4 thinking it was the closest to my current situation again with no luck. The command prompt window hangs up at the waiting for device.. forever. I tried the suggestion with a regular USB cable and a factory cable (Thank you SkOrPn) with same results. KFU shows the device ADB Status as offline and Boot status as unknown (see attachment 2.)
If anyone has any suggestions I'm all ears. If any further information is needed just ask and I'll do my best to supply it.
Thank you in advance for any and all help
Mike Shipman
sabres032

Okay try this method. Plug your kindle in, use kfu to set the bootmode to normal, when it hangs <waiting for device> hold the power button down while connected till it powers off, then simply power it back on and wait bootmode change doesn't happen immediately. Rinse and repeat till you're successful. If your trouble persists due to driver issues consider trying soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .

Thepooch said:
Okay try this method. Plug your kindle in, use kfu to set the bootmode to normal, when it hangs <waiting for device> hold the power button down while connected till it powers off, then simply power it back on and wait bootmode change doesn't happen immediately. Rinse and repeat till you're successful. If your trouble persists due to driver issues consider trying soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .
Click to expand...
Click to collapse
Thank you for the suggestion. Should I use a normal USB cable or the Factory Cable?

A normal one. A factory cable is intended to stick you in fastboot you're already there

Thepooch said:
Okay try this method. Plug your kindle in, use kfu to set the bootmode to normal, when it hangs <waiting for device> hold the power button down while connected till it powers off, then simply power it back on and wait bootmode change doesn't happen immediately. Rinse and repeat till you're successful. If your trouble persists due to driver issues consider trying soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .
Click to expand...
Click to collapse
OK So I've tried your suggestion of using KFU to set boot mode to normal, and rebooting the Kindle (after sufficient time, like 30 minutes) and still nothing. I've also tried to uninstall and re-install the drivers as noted in the OP, and every time the driver's install I still get the code 10 error. Would a broke bootloader or not being in fastboot be the cause of this? I'm sure there is an easy way to get the driver's to install properly but, so far it's escaping me. YEs I have spent more than two weeks searching the forums and trying others suggestions.
I know Window's can be very temperamental but I'd like to avoid using soup kit since it's Linux based and I know nothing of Linux. I only have one computer and if I screw it up I will have to waste even more time reloading windows and configuring.
I'm open to just about any other suggestion right now.
**EDIT** Also not sure if this means anything the C:\User\.android folder is empty. ISn't there supposed to be an .inf or configuration file in there?

**EDIT** Also not sure if this means anything the C:\User\.android folder is empty. ISn't there supposed to be an .inf or configuration file in there?
Click to expand...
Click to collapse
yep you can get it from the drivers folder in kfu and put it in there it`ts the adb_usb.ini if you open it with notepad it has this inside 0x1949. When your having driver issues soupkit is the way to go unless adding that file does it for you.

Thepooch said:
yep you can get it from the drivers folder in kfu and put it in there it`ts the adb_usb.ini if you open it with notepad it has this inside 0x1949. When your having driver issues soupkit is the way to go unless adding that file does it for you.
Click to expand...
Click to collapse
I would definitely need some major hand holding if I have to use soupkit as I have zero knowledge of Linux. Let me see if adding the .ini file works.

You could try the iso I made post 7 http://forum.xda-developers.com/showthread.php?t=1413358 . I`ll hold your hand if you need it.

I know it's been a while (a looooong while) since I have posted here but life sort of got in the way. I would like to share an update on my predicament. After months of leaving the Kindle Fire sitting on my bookshelf collecting dust I tried again to unbrick it. I spent a great deal of time studying up on Linux and reading and re-reading soupmagnets soupkit and decided to give it a try. I mean why not I'm not going to make things worse, right? . Well let me tell you it worked like a charm. I was able to restore my Kindle Fire to factory settings and to take it a step further I was able to install CROT recovery, the latest FFF bootloader and install CM10.1 and it's like a have a new device. I would like to give a huge thank you to everyone who tried to help me fix my device, you rock.
Mike

Eror update Amazon Fire Phone

Hi. Today i get new update for my phone Fire OS 4.6.3 (463001420) for Unlocked Fire Phone. But when i tried intall it, phone catchs "Eror". Now, when i try turn on mobile, opened recovery. I tried "Factory reset", but again opened recovery.
I downloaded 4.6.3 (463001420) bin and try install it use adb. I opened my terminal and wrote "adb sideload <name>" but got error "cannot read <name>".
So, i checked adb connection - pc do not found it: List of devices attached - none.
I deleted SDK, install it again and tried this steps:
"
1. In the Android SDK Manager window, from the Tools menu, click Manage Add-on Sites.
2. In the Add-on Sites dialog box, click the User Defined Sites tab, and then click New.
3. In the Add Add-on Site URLdialog box, enter the following URL:
4. https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml
5. Click OK and then Close. Wait for the Android SDK Manager to refresh, as indicated by the progress bar.
6. Expand Extras and click Amazon Kindle Fire USB Driver.
7. Click Install n Packages.
8, In the Choose Packages to Install dialog box, accept the license agreements for the packages, and then click Install.
9. In your Android SDK directory, at \extras\amazon\kindle_fire_usb_driver, run KindleDrivers.exe, and then follow the instructions on the screen."
After 8 step i opened SDK directory and did not find KindleDrivers.exe,.
So, i do not understand, how i can adb, how i can update fire phone. Need helps, pls!
P.S. Sry, my english is very bad, i am from Russian.

..

mazay2 said:
Hi. Today i get new update for my phone Fire OS 4.6.3 (463001420) for Unlocked Fire Phone. But when i tried intall it, phone catchs "Eror". Now, when i try turn on mobile, opened recovery. I tried "Factory reset", but again opened recovery.
I downloaded 4.6.3 (463001420) bin and try install it use adb. I opened my terminal and wrote "adb sideload <name>" but got error "cannot read <name>".
So, i checked adb connection - pc do not found it: List of devices attached - none.
I deleted SDK, install it again and tried this steps:
"
1. In the Android SDK Manager window, from the Tools menu, click Manage Add-on Sites.
2. In the Add-on Sites dialog box, click the User Defined Sites tab, and then click New.
3. In the Add Add-on Site URLdialog box, enter the following URL:
4. https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml
5. Click OK and then Close. Wait for the Android SDK Manager to refresh, as indicated by the progress bar.
6. Expand Extras and click Amazon Kindle Fire USB Driver.
7. Click Install n Packages.
8, In the Choose Packages to Install dialog box, accept the license agreements for the packages, and then click Install.
9. In your Android SDK directory, at \extras\amazon\kindle_fire_usb_driver, run KindleDrivers.exe, and then follow the instructions on the screen."
After 8 step i opened SDK directory and did not find KindleDrivers.exe,.
So, i do not understand, how i can adb, how i can update fire phone. Need helps, pls!
P.S. Sry, my english is very bad, i am from Russian.
Click to expand...
Click to collapse
Hi, I got the steps below from a post made by hijax2001. I modified the steps somewhat to cover the problem you are having. I don't know if they will work, but you can try them if you like.
1) Put update-fire-phone-35.4.6.3_user_463001420.bin in your ADB folder.
2) On your computer go to Device Manager and delete any SD4930UR and or Unknown device that appear when you plug your phone into the computer. Unplug your phone from the computer. Skip steps 3 and 4 if you see "Kindle Fire> Android Composite ADB Interface" when you plug in your phone into the computer.
3) If you need the Kindle Fire ADB drivers then download and install the Kindle Fire ADB drivers on your computer from here: Kindle Fire ADB drivers
4) Plug your phone back into the computer. The drivers for the phone should be installed and you should see "Kindle Fire> Android Composite ADB Interface" in Device Manager. Move on to the next step even if the drivers are not installed.
5) Power off the phone. Turn the phone back on by pressing and holding the Power and Volume Up buttons until the Fire System Recovery screen appear.
6) Use volume down to reach "Apply update from ADB" option, then press Power to select the option.
7) From ADB type ADB devices. If you see what looks like a serial number (letters and numbers), then ADB is seeing your phone and you can skip to Step 9. If nothing there, follow Step 8.
8) If ADB doesn't detect your phone go to Device Manager and right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer. Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>. Go back to ADB and type ADB devices. ADB should now detect your phone.
9) Type the command ADB sideload update-fire-phone-35.4.6.3_user_463001420.bin (Note: you can copy and paste the filename). When the phone display "install from adb complete", press the power button to select "reboot system now". The phone should update to Fire OS 4.6.3.

jack9955 said:
Hi, I got the steps below from a post made by hijax2001. I modified the steps somewhat to cover the problem you are having. I don't know if they will work, but you can try them if you like.
1) Put update-fire-phone-35.4.6.3_user_463001420.bin in your ADB folder.
2) On your computer go to Device Manager and delete any SD4930UR and or Unknown device that appear when you plug your phone into the computer. Unplug your phone from the computer. Skip steps 3 and 4 if you see "Kindle Fire> Android Composite ADB Interface" when you plug in your phone into the computer.
3) If you need the Kindle Fire ADB drivers then download and install the Kindle Fire ADB drivers on your computer from here: Kindle Fire ADB drivers
4) Plug your phone back into the computer. The drivers for the phone should be installed and you should see "Kindle Fire> Android Composite ADB Interface" in Device Manager. Move on to the next step even if the drivers are not installed.
5) Power off the phone. Turn the phone back on by pressing and holding the Power and Volume Up buttons until the Fire System Recovery screen appear.
6) Use volume down to reach "Apply update from ADB" option, then press Power to select the option.
7) From ADB type ADB devices. If you see what looks like a serial number (letters and numbers), then ADB is seeing your phone and you can skip to Step 9. If nothing there, follow Step 8.
8) If ADB doesn't detect your phone go to Device Manager and right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer. Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>. Go back to ADB and type ADB devices. ADB should now detect your phone.
9) Type the command ADB sideload update-fire-phone-35.4.6.3_user_463001420.bin (Note: you can copy and paste the filename). When the phone display "install from adb complete", press the power button to select "reboot system now". The phone should update to Fire OS 4.6.3.
Click to expand...
Click to collapse
Thank you very much! I am so silly(
I could update phone. No problem!
Moder, pls close this thread