Develop Bugs

Device not recognized on ADB?

I don't want to bother you with stupid threads and things like that, but I've used the search function on XDA and I'm still lost on this really small problem - my Kindle Fire is not being recognized anymore in ADB.
See, a long time ago (few weeks) I rooted my KF and installed Android Market, whatever. Never installed a recovery or custom ROM. Everything was ok until I tried to install TWRP using Kindle Fire Utility.
While trying to install, I got the famous "adbd cannot run as root in production builds". So I thought it was something with my drivers. Ok, then I installed the drivers that come with KFU - just to screw with everything. My Kindle Fire stopped being recognized by ADB.
I tried: (1) uninstall the drivers and install from KFU again. (2) uninstall the drivers and install the drivers I got from the video-tutorial (the famous one). (3) factory reset the kindle fire and do all the drivers install again. (4) hold the power button 900 seconds to reset the kindle fire and install the drivers again. (5) finally install the drivers on ANOTHER computer (running WinXP instead of Win7) and plug my factory reseted KF.
I gave up.
I don't know why my Kindle Fire isn't recognized by ADB on any computer at all. I thought it was my laptop, but then I tried the same steps I did at the first time using a Windows XP and no good. I don't know.
Can someone help me? Thanks a lot.

i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
or you can try this solution:
http://forum.xda-developers.com/showthread.php?t=1430038

b63 said:
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
Click to expand...
Click to collapse
Tried that and didn't work.
I'm going to wait a little more before using Linux, I really wanted to do this using Windows only.

in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu

b63 said:
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
Click to expand...
Click to collapse
Right now my KF is normally booting into stock ROM and stock everything.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Thanks for your support.

I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
Click to expand...
Click to collapse
xp will be the better choice cause you don't have to hassle with 32/64 bit drivers and the uac (user access control)
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Click to expand...
Click to collapse
add it in another line
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Click to expand...
Click to collapse
seems that the patched version (the whole thread) is deleted - you will have to do it by yourself - take the original from the dev section and:
http://forum.xda-developers.com/showthread.php?t=1454913

The issue persists. I've seen that other people are having the same issue. The device got "unrooted" by unknown reasons and then it's invisible to any adb. As I'm writing to you right now, I'm trying the adb on my brother's Ubuntu. I've tried other solutions using linux but without success.
I'm running out of options here.
I'll admit that I haven't tested the last link you sent, but I can't see how that can change the way adb works on my device. Anyway I'll try that tomorrow.

in the meantime br3 is out - if you use kfu you will have to use an updated run.bat: http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
but you'r right - that will not change the communication
firekit http://forum.xda-developers.com/showthread.php?t=1430038
is worth a try cause linux don't use drivers to communicate
only needs some entries which are included in firekit
maybe try an other cable ?
really running out of ideas at this point ...

I got the same problem.
If you can fix it, please show me how, thank you.
c:\KindleADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
c:\KindleADB>

Just a quick idea. Have you tried the attach the kindle to a different USB port? I had the same issue until I used a different port. The front ports on my desktop are totally fubar, but the port where my mouse was worked when 4 out of 6 ports did not. This for me is probably a hardware problem, but it may help someone.
Sent from my Kindle Fire using Tapatalk

I am having the same exact problem as the OP and I truer everyway to root it and install the drivers but its still not recognized by adb

Its seems i should give up

Similar problem with cm9, and fixed
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.

Push push push it

tried all the steps. and still nothing. dont know what im doing wrong. starting to get pissed. any help would be great, thanks

Save my KF
sudogeek said:
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Click to expand...
Click to collapse
Could you help me to fix same problem with window. My PC alway, automatic recognize my KF as normal disk driver. I try to make a factory cab but not success .
Thanks.

Edit android-path.sh
1. On my Mac I opened System Profiler, then checked Hardware > USB > and 'MyDeviceName' (for me its: LePan Tablet PC)
2. Opened this file with a text editor: /Users/MyName/.android/android-path.sh
3. Added a new line in this file with the tablet Vendor Id, for example:
0x22a4
4. Executed: adb kill-server
5. Executed: adb start-server
6. Finally adb devices is showing:
List of devices attached
0163AE9D0801F02C0C280002 device

Bricked?
I think I'm having the same problem, or at least a very similar one.
Using windows XP. I got the drivers working, plugged my kindle into the Kindle Fire Utility, and ran option 2, which seemed like it was the option to create a backup in case you bricked your kindle. It ran, showed up on the Kindle screen, and did it's thing without a problem.
Then, when the kindle rebooted, I got the yellow-triangle-fire symbol. It says 'press power button for recovery', but pressing the power button does nothing. Holding it down for a long time shuts the kindle down, but pressing it again brings it right back to the yellow-triangle-fire symbol.
So I uninstalled the drivers from Windows XP (as another thread mentioned). I now have two ways that I can think of to install the drivers. Using the KFU, I get the "unsigned drivers" shutdown even after I went into the Driver Signing menu and chose "ignore and install regardless".
The other option I have is to install the drivers that I downloaded manually -- the same ones that worked in the first place. Problem with that is that I go through the entire process, selecting the directory the drivers are in and whatnot, and the only thing that happens is I get an error that says "These drivers aren't the drivers for your hardware" or something similar to that.
So neither of my options allow me to actually install drivers for my Kindle Fire, and my Fire itself is in a recovery loop. All of the tools that are supposed to address the recovery loop require drivers, so I seem to be up a creek without a Fire.
Any ideas?

Okay, to enter recovery...When you see the yellow triangle, hold the power button until it turns orange then release. It shouldn't take more than 10-15 seconds. If you still can't get into recovery, reinstall it.
For your drivers...uninstall completely and delete them if you're using Win7. Then reinstall using one of the previous methods.

The power button doesn't do anything when I push it. It stays bright green until the kindle fire shuts down. I'm not sure what "reinstall it" means, sorry, n00biness.
The drivers (winXP as mentioned) I've uninstalled, but I can't reinstall. One option says "unsigned drivers" and the other doesn't recognize the device as a Kindle and thus quits the install with a "this is not an appropriate driver for your device" message.
Thanks for trying, though! I appreciate your time and effort.

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] 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

Kindle Fire doesn't show up on ADB or device manager

I'm trying to put Cyanogenmod on my Kindle Fire, but haven't gotten anywhere with it, due to my computer not being able to recognize it. I have ADB installed (have used it with at least 4 other devices).
The issue is that when I connect the tablet to my computer (Windows 7, 64-bit), "adb devices" turns up with nothing. I've read that you have to uninstall the Windows installed Kindle drivers through the Device Manager (even with hidden devices shown). However, my issue is that I can't see the Kindle on the Device Manager. Also, the tablet shows up under "Devices and Printers", so it's not completely unrecognized.
I've also tried installing Kush's ADB drivers, because I thought that would work, but it didn't.

If it is in devices and printers it is in device manager.
Sent from my Amazon OtterX using Tapatalk

sd_shadow said:
If it is in devices and printers it is in device manager.
Click to expand...
Click to collapse
Well, then help me find it in device manager (pictures attached).

Quevvy said:
Well, then help me find it in device manager (pictures attached).
Click to expand...
Click to collapse
So I thought it was showing me hidden devices, but it wasn't. When I view hidden devices, it was listed under Portable Devices. I then right-clicked and then uninstalled the driver to try and install the ADB drivers for the Kindle (ADB setup). When I plug it back into the computer, then it really doesn't show up on Device Manager (but again still on Devices and Printers)

Quevvy said:
So I thought it was showing me hidden devices, but it wasn't. When I view hidden devices, it was listed under Portable Devices. I then right-clicked and then uninstalled the driver to try and install the ADB drivers for the Kindle (ADB setup). When I plug it back into the computer, then it really doesn't show up on Device Manager (but again still on Devices and Printers)
Click to expand...
Click to collapse
Mine show as an android phone.

sd_shadow said:
Mine show as an android phone.
Click to expand...
Click to collapse
While it does show up that way, adb devices returns nothing. I've even tried kill-server and start-server to try and restart it. This means that when I run the Kindle Fire Utility, it doesn't do anything because it can't detect the device.

Reboot pc
Sent from my Amazon OtterX using Tapatalk

sd_shadow said:
Reboot pc
Sent from my Amazon OtterX using Tapatalk
Click to expand...
Click to collapse
Had tried it before, but tried it again: ADB comes up with nothing.
I even tried it on another computer, with similar issues. I also tried resetting it to factory defaults, which didn't help either.

Quevvy said:
Had tried it before, but tried it again: ADB comes up with nothing.
I even tried it on another computer, with similar issues. I also tried resetting it to factory defaults, which didn't help either.
Click to expand...
Click to collapse
you unzipped KFU, and not running it still zipped?

sd_shadow said:
you unzipped KFU, and not running it still zipped?
Click to expand...
Click to collapse
I have unzipped it, and am running it from the unzipped location.

check specific drivers do they match this?

Quevvy said:
I have unzipped it, and am running it from the unzipped location.
Click to expand...
Click to collapse
I was able to get the ADB working on a Windows 8 computer, but then when KFU tried to reboot into fastboot mode, it said "waiting for device" for a long time. I think it has frozen. I've tried resetting it by holding the power button for 20 seconds, but I haven't been able to get past the splash screen.

Quevvy said:
I was able to get the ADB working on a Windows 8 computer, but then when KFU tried to reboot into fastboot mode, it said "waiting for device" for a long time. I think it has frozen. I've tried resetting it by holding the power button for 20 seconds, but I haven't been able to get past the splash screen.
Click to expand...
Click to collapse
it maybe in fastboot mode, try restarting KFU a few times, or try command prompt
fastboot reboot-bootloader
if fastboot commands work you can flash Twrp manually

sd_shadow said:
it maybe in fastboot mode, try restarting KFU a few times, or try command prompt
fastboot reboot-bootloader
if fastboot commands work you can flash Twrp manually
Click to expand...
Click to collapse
I tried fastboot, to no avail. Then I ran KFU and during it, Windows said that the ADB device had been recognized, and then the installation of TWRP supposedly went through (have not been able to check it). Then I tried installing FFF, but got the < waiting for device > that was the original problem. This was back on the original computer (Windows 7), but will try on the Windows 8 computer now that the Kindle is back on.

FFF installs with Twrp now
---------- Post added at 11:42 AM ---------- Previous post was at 11:40 AM ----------
if twrp installed boot logo should have changed
do you see a press power for boot options?
---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------

sd_shadow said:
FFF installs with Twrp now
---------- Post added at 11:42 AM ---------- Previous post was at 11:40 AM ----------
if twrp installed boot logo should have changed
do you see a press power for boot options?
---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------
Click to expand...
Click to collapse
Hmm, the boot logo is still the same. I'm going to try and install TWRP again.

Quevvy said:
Hmm, the boot logo is still the same. I'm going to try and install TWRP again.
Click to expand...
Click to collapse
So this is what seems to work the best for me (even though it doesn't work). With the Windows 8 computer, the Kindle is recognized in the ADB devices. I can run KFU and it actually is able to communicate with the device, but then the Kindle stalls when trying to reboot in fastboot mode. I cannot do anything with it in Windows 8. So I connect it to the Windows 7 machine, where I cannot install TWRP, but I can reboot it into normal mode, so it is not bricked, and it is still usable.
As far as I can tell, it never even got to the point where it would have started installing TWRP.

Quevvy said:
So this is what seems to work the best for me (even though it doesn't work). With the Windows 8 computer, the Kindle is recognized in the ADB devices. I can run KFU and it actually is able to communicate with the device, but then the Kindle stalls when trying to reboot in fastboot mode. I cannot do anything with it in Windows 8. So I connect it to the Windows 7 machine, where I cannot install TWRP, but I can reboot it into normal mode, so it is not bricked, and it is still usable.
As far as I can tell, it never even got to the point where it would have started installing TWRP.
Click to expand...
Click to collapse
try manually reboot to bootloader with
[fastboot] stock 6.2.1 fastboot mode without rooting or cables
if that works manually flash TWRP with Fastboot.exe

sd_shadow said:
try manually reboot to bootloader with
[fastboot] stock 6.2.1 fastboot mode without rooting or cables
if that works manually flash TWRP with Fastboot.exe
Click to expand...
Click to collapse
I think my issue was the computer not recognizing the device once it was in fastboot mode. I reinstalled the drivers (which I had done before), but this time they worked on the Windows 8 computer, so I was able to get TWRP and FFF on the device. I am working on getting CM11 on it currently. Thanks for all the help so far!

Done!
Quevvy said:
I think my issue was the computer not recognizing the device once it was in fastboot mode. I reinstalled the drivers (which I had done before), but this time they worked on the Windows 8 computer, so I was able to get TWRP and FFF on the device. I am working on getting CM11 on it currently. Thanks for all the help so far!
Click to expand...
Click to collapse
I got it all working: TWRP, FFF, and CM11. As far as I can tell, there are no issues any more. I haven't tried ADB after putting CM11 on it, but I'm not going to worry about that since I already have the recovery and bootloader installed.

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