Develop Bugs

[Solution]Windows 8 - ADB/fastboot driver problem solved!!

Hello!!​
Well, hey guys. I thought I tell you the story, on why I posted this thread.
It started as I was installing Windows 8, on my laptop, and had the same problem, as some others. I just could not install the drivers, for my Droid, so I had a looksee and found that Windows 8 didn't yet have the capability, to download unsigned drivers, unlike Windows 7. So, I found a way of "tricking" Windows, into thinking, that these drivers are legit and it isn't forbidden to use, which is exactly what this tutorial tells Windows, in a way.
So, get going and use the full potential of your Android device!
Tutorial:​
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... : devmgmt.msc
Now, the dive manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here/
To prevent confusion: When I say install, it can mean unpack, or instal... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has poped up, choose "Browse my computer" and goto your dsktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\adb reboot-bootloader
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick, from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices.
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your SAMUNG GALAXY NEXUS!"!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Addition: You can only reboot into bootloader, if you are using a motorola, Google or HTC branded Android device! This will NOT work with Samsung models (i.e. Galaxy S II/III) due to the fact, that they use Odin mode. Should the drivers need updating, for some devices, please let me know!

Motorola Razr
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.

thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Click to expand...
Click to collapse
Download MotoHelper. Right click the file and run in compatibility mode. It should install the drivers. I used this to run fastboot with my xoom.

It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.

thejakenixon said:
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
Click to expand...
Click to collapse
Bummer, I just remembered there was a setting to skip os version check in compatibility mode. Did you try that? If that won't work unfortunately I don't know what else to try. Sorry.
Sent from my Xoom using XDA Premium HD app

thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
First of all, thanks, for letting me know about the link It's uploading again ^^
Yes, you can do the same for your Motorola. But only with the ADB drivers. Just do the same as with the Samsung. Select your device, form the devman. and right click. Update device drivers -> Browse -> Let me choose from a list... -> Samsnung ADB interface.
They are all provided by Google, inc. so, they are compatible, with every Android device. I've even used my Samsung ADB drivers, for a Sony Ericsson Xperia X8. So I can actually say, for myself, that they work. You then can work, using fastboot... ^^
Have fun fastbooting!
LG familyguy59/Beatsleigher

Well, I'm definitly glad, to see I'm actually helping some people, and they're appreciating it!!
I don't remember mentioning it, but if you Need help, PM me. I'll help you via Team Viewer ^^

will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?

iconicpaul said:
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
Click to expand...
Click to collapse
Yes, it works on both x86 and x64 bit architectures of Windows 8, works withRC and with pre-release...
Sent from my GT-I9300 using xda app-developers app

confirmed, it works, thank you...very fast and easy

thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
To your edit. You have extracted the files. This is also called "installing" because you have extracted NEEDED files. Even when you extract a .zip/.rar/.tar/.tar.gz and so on, because you need files out of them, you are installing, but not to the system, but to yourself

Sorry for bringing up an old post, but this method is not working for me on Windows 8 Consumer Preview. When I'm trying to install the ADB drivers, it says the drivers cannot be installed because it's not digitally signed.
UPDATE: I got it to work by disabling the Digital Signature Enforcement on Windows 8. Steps: Restart Windows > Boot loader Menu > Other Options > Advance Options > *Computer Automatically Restarts* > Press F7 to Disable Digital Signature Enforcement

I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app

2phonejones said:
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...

iconicpaul said:
confirmed, it works, thank you...very fast and easy
Click to expand...
Click to collapse
No worries, dude That's what I posted this thread for.

familyguy59 said:
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
Click to expand...
Click to collapse
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:

Could someone pls. create a video tutorial, nad post this on Youtube, for me?
My laptop broke a couple of days ago, and my PC is only capable of running 98 - Vista, so, running on XP with 1GB of RAM.
I would appreciate this very much!
If you could do so and send me the link, via PM, I would be glad to pay 5€, via PayPal!

2phonejones said:
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Click to expand...
Click to collapse
Ok, dude! Have fun!

Didn't work for me.

jorgefcbastos said:
Didn't work for me.
Click to expand...
Click to collapse
Did you follow the tutorial COMPLETELY, or did you leave stuff out? If you left something out, it's obviously not going to work
You may have to disable device driver signing, I've had quite a few people notify me about this.
But I'll sign the drivers, ASAP, so you won't have this problem
LG familyguy59/Beatsleigher
Edit: I forgot to mention, you need to tell me what exactly didn't work, otherwise I can't really help you

[Q] Waiting for device...

So I rooted my KF a day or so ago and didn't follow the directions entirely. I ended up bricking my KF. Eventually I was able to unbrick it and got it back to stock.
I would like to try rooting it again using the KFU (which is what I used the first time), but the KFU won't find my KF.
I installed the drivers and after I plug in my KF, it shows up in my Device Manager under 'Disk Drives' and it is named 'Amazon Kindle USB Device.' Is this correct?
I have removed the drivers and reboot both my computer and KF, re-installed the drivers and the same thing happens.
Something to note... when I uninstall the drivers and plug the KF back into my computer, the drivers install by themselves. I remember the first time I plugged my KF in, the drivers were not found and would obviously not install. I had to manually install the drivers included in this utility in order for my computer to 'find' my KF.

car_lost said:
So I rooted my KF a day or so ago and didn't follow the directions entirely. I ended up bricking my KF. Eventually I was able to unbrick it and got it back to stock.
I would like to try rooting it again using the KFU (which is what I used the first time), but the KFU won't find my KF.
I installed the drivers and after I plug in my KF, it shows up in my Device Manager under 'Disk Drives' and it is named 'Amazon Kindle USB Device.' Is this correct?
I have removed the drivers and reboot both my computer and KF, re-installed the drivers and the same thing happens.
Something to note... when I uninstall the drivers and plug the KF back into my computer, the drivers install by themselves. I remember the first time I plugged my KF in, the drivers were not found and would obviously not install. I had to manually install the drivers included in this utility in order for my computer to 'find' my KF.
Click to expand...
Click to collapse
I'm having the same problem.
In the device manager, you should see Android phone or some such near the top, as well as the drive you mentioned.
I tried to root my KF yesterday on 4 different Windows machines using 4 different OS's: Windows 7 Professional, XP Professional, XP and Vista. (Yes, I stil have a Vista machine)
No joy. <Waiting For Device> _
Matt

This might help both of you...
http://forum.xda-developers.com/showthread.php?t=1552547
Post #2 deals with driver installation, but it might not hurt to read #1 before you get to that.
Good luck.

kinfauns said:
This might help both of you...
http://forum.xda-developers.com/showthread.php?t=1552547
Post #2 deals with driver installation, but it might not hurt to read #1 before you get to that.
Good luck.
Click to expand...
Click to collapse
Yup, I've done all that.
One thing that doesn't happen for me anymore is this step when I remove/uninstall the drivers:
Check the "Delete the driver software for this device." box and press "OK"

car_lost said:
Yup, I've done all that.
One thing that doesn't happen for me anymore is this step when I remove/uninstall the drivers:
Check the "Delete the driver software for this device." box and press "OK"
Click to expand...
Click to collapse
Is this on Windows XP?
"Disk drives - Amazon Kindle USB Device" is not what you should be worried about. That just lets you mount the sdcard on Windows.
You should be seeing something under "Android Phone" or "Other devices" in the Device Manager. That's the device that needs the ADB drivers.

kinfauns said:
Is this on Windows XP?
"Disk drives - Amazon Kindle USB Device" is not what you should be worried about. That just lets you mount the sdcard on Windows.
You should be seeing something under "Android Phone" or "Other devices" in the Device Manager. That's the device that needs the ADB drivers.
Click to expand...
Click to collapse
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'

car_lost said:
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'
Click to expand...
Click to collapse
On a stock device, booted up to the OS... some device in a category other than Disk drives or Portable Devices should come up when you connect it to your computer. I've never seen a situation where that did not happen. If you have another computer, I would suggest trying that.

car_lost said:
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'
Click to expand...
Click to collapse
is there a device named "kindle" ? - if yes delete it and try to unplug/replug
if this don't help try to use this method to show devices that are not connected atm:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
disconnect the kf and remove everything with adb or kindle
take care that you uninstall the driver too where you get the option to do this
now reconnect the kf - it should ask for the drivers like at the first connection

I'm formatting my computer and starting from fresh. Fresh copy of Windows 7 and a stock KF.
I'll report back.

regrouping
I'm going to regroup and try again as well and try again this evening. I've tried all of the above with no success.

Mattb4rd said:
I'm going to regroup and try again as well and try again this evening. I've tried all of the above with no success.
Click to expand...
Click to collapse
maybe this one can help:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

b63 said:
maybe this one can help:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
Already had tried that but did again for good measure. The driver installs as before but the KFU still hangs on "oops, something went wrong" and <waiting for device>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
Out of time right now and have to leave for a meeting. Will give it one more shot later.

you need two drivers:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
according to your screenshot the kf is not recognized by adb
what are the status lines if you start kfu ?
should look like:
ADB Status: Online
Boot Status: 4000

So I did a fresh install of Windows 7, plugged in the KF and the same damn thing is happening. I'm gonna throw this thing against the wall.

This is what I get...

previous pic doesnt seem to be working..

car_lost said:
So I did a fresh install of Windows 7, plugged in the KF and the same damn thing is happening. I'm gonna throw this thing against the wall.
Click to expand...
Click to collapse
You're in an unusual spot... I figured a new Windows install would get it to work. In my opinion, if you can rule out Windows 7 as the problem, you're going to have to start looking at the KF as the possible cause. I haven't had stock on my device in a while, but if I was in your shoes... I would try a factory reset. Maybe even try to get it to reflash the stock software. I think you can download the KF software from Amazon, rename it update.zip and put it at the root of /sdcard or /sdcard/kindleupdates and reboot to initiate a flash.
If none of that works, you might want to build/buy/borrow a factory cable. Then you can flash a new bootloader/recovery and try a ROM to see if you can get adb working with that.

kinfauns said:
you're in an unusual spot... I figured a new windows install would get it to work. In my opinion, if you can rule out windows 7 as the problem, you're going to have to start looking at the kf as the possible cause. I haven't had stock on my device in a while, but if i was in your shoes... I would try a factory reset. Maybe even try to get it to reflash the stock software. I think you can download the kf software from amazon, rename it update.zip and put it at the root of /sdcard or /sdcard/kindleupdates and reboot to initiate a flash.
If none of that works, you might want to build/buy/borrow a factory cable. Then you can flash a new bootloader/recovery and try a rom to see if you can get adb working with that.
Click to expand...
Click to collapse
this worked! This worked! This worked! This worked! Thank you a million times!!

b63 said:
you need two drivers:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
according to your screenshot the kf is not recognized by adb
what are the status lines if you start kfu ?
should look like:
ADB Status: Online
Boot Status: 4000
Click to expand...
Click to collapse
ok .. I'm taking it with me to the office. That's a Win7 Pro machine, but I'm thinking about trying a restoration to factory defaults like Carlos.

Mattb4rd said:
ok .. I'm taking it with me to the office. That's a Win7 Pro machine, but I'm thinking about trying a restoration to factory defaults like Carlos.
Click to expand...
Click to collapse
A factory reset isn't going to hurt, but you are in a different boat than Carlos. Based on your screenshot of the Device Manager, it looks to me like your computer is recognizing the device correctly and loading the right drivers since it says "Android Phone -> Android Composite ADB Interface" when it's hooked up. For whatever reason, KFU is not able to push the required files onto your device and get it into fastboot mode. I suggest taking KFU the middleman out of the picture and seeing what adb tells you when you try to use it directly. Try something simple like "adb devices" on the command line and see what you get. You'll have to use the command line to run the adb program located in the tools directory of KFU.

[GUIDE]Enable USB Debugging and setup Android SDK for Fire Phone

Disclaimer:I am not responsible if using anything I've made or provided suddenly deep-fries your device or causes thermonuclear war leading to alien abductions.
Hey guys!
It's been a while that I've been seeing people having problems to enable USB debugging and setting up the Android SDK to recognize the device. So,I've made a guide to help you enable USB debugging and set up the Android SDK accordingly. So let's begin!
What you'll need:
Windows/Linux/Mac OS X with the Android SDK installed
A Fire Phone
Click to expand...
Click to collapse
Setting up Android SDK and drivers:
At first,make sure you have the Android SDK installed,adb and fastboot working.
Open the SDK manager
Click on "Tools" and then click on "Manage add-on sites"
Click on the "User Defined Sites" tab,click "Add" and paste this URL:https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml
Click "Ok". Wait for it to finish. Then,from the repo of Android 4.2.2(API Level 17),select Fire Phone SDK and install it.
Remove any Fire Phone drivers using device manager
Go to the directory of the SDK and find this:
Code:
/add-ons/addon-fire_phone_sdk_addon-amazon-17/tools/KindleDrivers.exe
Run the driver setup and connect the phone having USB debugging enabled. If you don't know how to do this,it's explained below.
Done!
Click to expand...
Click to collapse
Enabling USB debugging:
Go to Settings
Scroll to the Device section and expand the section.
Tap Get info about your Fire.
Tap any item at least 7 times in 5 seconds
Developer options will appear. Set it to On.
Go to developer options and enable USB debugging.
Done!
Click to expand...
Click to collapse
Thanks a lot for reading my guide. If this was useful to you,please hit the thanks button. Feel free to comment,post or report anything. Thanks.

Excellent!! I can confirm this is working.
Bin4ry's root method was unsuccessful. Tried all options including the pwn binary. Very nice to have adb working though. :good:

I am M3 said:
Excellent!! I can confirm this is working.
Bin4ry's root method was unsuccessful. Tried all options including the pwn binary. Very nice to have adb working though. :good:
Click to expand...
Click to collapse
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.

I am M3 said:
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
Click to expand...
Click to collapse
Could you try in a Linux distro live CD? It should detect the device without a hitch
Sent from my device running CyanogenMod 11

I am M3 said:
@SafinWasi - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
Click to expand...
Click to collapse
If you're using Windows here's how I did it on Windows 7. Once you open ADB and reboot it into recovery mode remove it from Device Manager. Reboot you PC if asked. Never unplug or remove your phone through any of this. You may need to remove it a second time from Device Manager after a reboot. It'll eventually show up under Other Devices with the Model Number as the device name (at least mine did). Once it's there then go and update the driver. Tell Windows you want to pick from a list of all the devices. Scroll down until you see Amazon listed on the left side. You'll then see "Android Composite ADB Interface" listed on the right. Choose that. Then it should be recognized again and you can sideload to roll back. Once you roll back you'll probably get a lot of errors but it will work and it will root using the towelroot APK that's posted in the other forum here. I had to have my phone services so I had to do a factory reset on my phone because it broke my phone services. But the roll back process itself was very easy to do once I figured out how to get it recognized again while in recovery mode.

I did what the directions say, but I don't see the fire phone listed in the sdk.

mnknight said:
I did what the directions say, but I don't see the fire phone listed in the sdk.
Click to expand...
Click to collapse
You have to choose the correct driver in Device Manager
On Windows 8/8.1 you may have to activate unsigned drivers

Kindle drivers don't seem to be working for me!

In Windows 8 and newer you have to activate unsigned drivers.
And please choose driver in device manager!

Kindle driver not working for me on windows 7
Kindle driver not working for me on windows 7

Grizzly123 said:
Kindle driver not working for me on windows 7
Click to expand...
Click to collapse
Try using a Linux distro

hey, first sorry for my bad english. isnt my native language.
ich have installed all i need (Windows/Linux/Mac OS X with the Android SDK installed,Android SDK installed,adb and fastboot working[but i dont really know what fastboot working means.])
i have no problem with step 1-5 but i dont understand step 6. i google it but i dont understand. can you please update pictures? that would be very nice.
i have a sec question. my fire phone is netlocked(german). is where still a netlock after install andoid?
again, sry for my bad english :/
thanks for help
munir

Step 6.
In windows device manger, remove all the fire phone devices listed.
Then run the KindleDivers.exe listed in step 7.
When you plug the phone back in windows "should" find and use the right drivers.

Thank you

For reference, the drivers have now moved. The following is an extract from the latest release notes:
* Windows USB drivers have been removed from the tools directory. You may access them from the SDK Manager under Extras.
Click to expand...
Click to collapse
They're installed with the package Extras / Kindle Fire USB Driver and will be located at: android-sdk\extras\amazon\kindle_fire_usb_driver
Other than that, instructions work fine, thanks

hello op, i got as far as step 4, when you mention add the link, mine shows new, everything after step 4 is different. can you please help?

Stuck on recovery
Solved it

Update: in the sdk manager, you must select 'kindle fire usb driver' under 'extras' now, and install that package. Then, you can find it in the sdk dir under sdk/extras/amazon/kindle_fire_usb_driver/KindleDrivers.exe

CM 11 back to Fire OS but have a question?

I love CM11 but I'm just not having great service anymore like I did with the Fire OS... Now here is the question... I have the At&t version with 464 installed... Then installed the CM11 now is it possible to install 463 OS from the unlocked version so that I can install the play store and Google services... Amazons app store lack a lot of apps I currently use... If so how do I go about doing that?

1. Download the "GSM unlocked" firmware image: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
Assuming you are using Windows 7 / 8 / 10, if not, don't bother reading the following wall of text:
2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. In Windows, run the "CMD": adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin
4. If you have trouble getting your device recognised after entering recovery / ADB sideloading mode:
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try this tool (& driver) ADB, Fastboot and Drivers
It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":

Bingo,
Thanks for the guide, but I cannot get my computers to recognize the Phone in recovery ADB mode. It shows the device description as SD4930UR. It only shows as unknown. The hardware IDs are VID_1949&PID_0800. I tried the linked tool (both the 1.4.2 and 1.3 version he had) and the google drivers.
What is the exact driver that works for you?

wats2u said:
What is the exact driver that works for you?
Click to expand...
Click to collapse
I used the "15 seconds ADB Installer" v. 1.3, so the OS used the drivers from there (on Win 7 x64). Use a USB 2.0 port, just to be sure.
The drivers that work on my system might not work for your configuration...
Are you using Win 10? If so, have you tried updating the drivers with the integrated update function?
g0tNoodles said:
It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one, which also needed updating which I have just done and appears to now let the CMD see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now.
Click to expand...
Click to collapse

I can't access my phone from my computer to run the .bin after rebooting it into recovery mode. The download links for that driver installer you linked to don't work. In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.

powerlocked said:
In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
Click to expand...
Click to collapse
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface​

powerlocked said:
I can't access my phone from my computer to run the .bin after rebooting it into recovery mode. The download links for that driver installer you linked to don't work. In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
Click to expand...
Click to collapse
DePingus said:
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface​
Click to expand...
Click to collapse
What DePingus said, regarding the 15 seconds ADB... It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Not the first time people struggling with it, Windows is just too darn complicated.

Bingo Bronson said:
What DePingus said, regarding the 15 seconds ADB... It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Not the first time people struggling with it, Windows is just too darn complicated.
Click to expand...
Click to collapse
Good lord...tried all of that and more and still not able to get my device to show up in ADB. The last installer gives me the message "[Error] Incompatible with Win8 x64". So two questions...anything else I can try for drivers, or, can I use a method other than ADB, such as Safestrap?
Thanks again for all your insight on this forum
EDIT: For anyone that struggled as much as me to finally get drivers to work, this method ultimately worked as posted by @hijax2001
4) I also grabbed the Kindle Fire ADB drivers from here for convenience in Step 7 (below) https://docs.google.com/file/d/0B1Z1J6LQic8PQjFjS0FpVGVia2M/edit
7) For me, ADB did not initially detect my phone. I ended up having to go into Control Panel in Windows, to Device Manager, find the Fire phone, choose Update Drivers, then Browse My Computer, Let Me Pick, Show All Devices, Have Disk, then find the folder from Step 4 (above) and add Android Composite ADB Interface by hand. Once I did that, I unplugged and replugged the USB to the phone and then typed "ADB devices" again at the ADB command prompt, like in Step 6. There it is! Ok, next step...

ElQuixote said:
Good lord...tried all of that and more and still not able to get my device to show up in ADB. The last installer gives me the message "[Error] Incompatible with Win8 x64". So two questions...anything else I can try for drivers, or, can I use a method other than ADB, such as Safestrap?
Thanks again for all your insight on this forum
Click to expand...
Click to collapse
I'm not familiar with adbdriverinstaller, but which ever you use, make sure you are running the installer as admin (right-click on the installer). Also, if you extract the 15 second installer exe with 7zip you get access to the drivers installers separately. Maybe try manually installing them.

DePingus said:
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface​
Click to expand...
Click to collapse
Ran 15s ADB. I right clicked SD4930UR in device manager. After selecting update driver, then 'Let me pick from a list..' there is no 'left' or Google listed. It loads a list int he center of the screen of generic hardware devices.. the only one that pertains to a phone is 'mobile' and after selecting that there are no driver options to be found. There is no 'android' to select from that list.
It's doing this on both windows 7 and windows 10.

Bingo Bronson said:
1. Download the "GSM unlocked" firmware image: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
Assuming you are using Windows 7 / 8 / 10, if not, don't bother reading the following wall of text:
2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. In Windows, run the "CMD": adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin
Click to expand...
Click to collapse
I tried this method, to install 4.6.3 unlocked over my ATT (now carrier unlocked) 4.6.4. After I sideloaded, I get the following lines in Recovery, indicating that this didn't work. Any thought? Is there something else I need to do to be able to install the GSM on the ATT version?
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted
EDIT: Determined that the file I originally downloaded may not have been complete and sure enough a second version is larger...

powerlocked said:
Ran 15s ADB. I right clicked SD4930UR in device manager. After selecting update driver, then 'Let me pick from a list..' there is no 'left' or Google listed. It loads a list int he center of the screen of generic hardware devices.. the only one that pertains to a phone is 'mobile' and after selecting that there are no driver options to be found. There is no 'android' to select from that list.
It's doing this on both windows 7 and windows 10.
Click to expand...
Click to collapse
I think those steps are for Windows XP. For Windows 7, 8, or 10 use the following steps to update the driver:
Those steps are for Google USB driver. For Amazon Kindle Fire USB driver, use the following steps:
1) Right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer.
2) 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>.

jack9955 said:
I think those steps are for Windows XP. For Windows 7, 8, or 10 use the following steps to update the driver:
1) Right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer.
2) 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>.
Click to expand...
Click to collapse
Ohhhh okay thank you for explaining this. After finding KindleFire down the list I was able to update my drivers. I've now installed the update to both of my ATT Fire phones, and both are now 4.6.3 and working great with working playstore options.
Thank you jack9955 and everyone else for the tutorials.. much appreciated!

How to Setup the Fire phone for ADB
An illustrated guide ... 2015-09-15​
Open open Device Manager. This is what my 4.6.3 Fire phone looks like when plugged in normally to my Windows 7 computer. Power it off and boot into the stock recovery using PWR + VOL UP (hold both buttons until recovery screen appears). The Fire device will disappear from Device Manager.
At the phone's recovery menu choose "Apply update from ADB". Back in Device Manager do a Scan for Hardware Changes and you should now see this. Right click on the Fire and choose uninstall.
Grab "15 Seconds ADB Installer" and install it as admin and hit yes for everything. http://forum.xda-developers.com/showthread.php?t=2588979
Now scan for hardware changes again and you will see this new device. Right Click this device and choose Update Driver Software.
From this window choose "Browse my computer for driver software."
From this window choose "Let me pick from a list of device drivers on my computer."
From this window choose "Show all devices."
In the section on the left that says Manufacturer find "Google Inc." Then, on the right, choose "Android Composite ADB Interface." Accept through any warnings.
The Device Manager should now show this.
Open up a cmd prompt and test that adb can see your phone with the "adb devices" command. Now you can sideload 4.6.3 or whatever.

DePingus said:
How to Setup the Fire phone for ADB
An illustrated guide ... 2015-09-15​
Open open Device Manager. This is what my 4.6.3 Fire phone looks like when plugged in normally to my Windows 7 computer. Power it off and boot into the stock recovery using PWR + VOL UP (hold both buttons until recovery screen appears). The Fire device will disappear from Device Manager.
At the phone's recovery menu choose "Apply update from ADB". Back in Device Manager do a Scan for Hardware Changes and you should now see this. Right click on the Fire and choose uninstall.
Grab "15 Seconds ADB Installer" and install it as admin and hit yes for everything. http://forum.xda-developers.com/showthread.php?t=2588979
Now scan for hardware changes again and you will see this new device. Right Click this device and choose Update Driver Software.
From this window choose "Browse my computer for driver software."
From this window choose "Let me pick from a list of device drivers on my computer."
From this window choose "Show all devices."
In the section on the left that says Manufacturer find "Google Inc." Then, on the right, choose "Android Composite ADB Interface." Accept through any warnings.
The Device Manager should now show this.
Open up a cmd prompt and test that adb can see your phone with the "adb devices" command. Now you can sideload 4.6.3 or whatever.
Click to expand...
Click to collapse
I see there are atleast two USB drivers you can use to set up ADB on the Fire Phone. Amazon Kindle Fire USB driver and Google USB driver. If Google USB driver is installed, you should select "Google, Inc." for Manufacturer. For Amazon USB driver, you should select "Amazon.com" for the Manufacturer, Device Manager will show the device as Kindle Fire> Android Composite ADB Interface.

jack9955 said:
I see there are atleast two USB drivers you can use to set up ADB on the Fire Phone. Amazon Kindle Fire USB driver and Google USB driver. If Google USB driver is installed, you should select "Google, Inc." for Manufacturer. For Amazon USB driver, you should select "Amazon.com" for the Manufacturer, Device Manager will show the device as Kindle Fire> Android Composite ADB Interface.
Click to expand...
Click to collapse
I've also noticed some people using the Amazon drivers. But they're not included with "15 Seconds ADB".

Works seamlessly too on any linux terminal
Just, so you know, your method works very well too on any linux computer. I had the same issue and now it is fixed. I can write a tutorial complimenting this if needed.

hello lam from china english is very bad thanks for friephone cm l hope you will do cm12 cm12.1 don't abandon our china people have lot's of people hope and camera have better solution official camera and fire os5 Do you have any news thanks

csx21 said:
hello lam from china english is very bad thanks for friephone cm l hope you will do cm12 cm12.1 don't abandon our china people have lot's of people hope and camera have better solution official camera and fire os5 Do you have any news thanks
Click to expand...
Click to collapse
We can't do CM12 because the Fire Phone's bootloader is still locked and the current FireOS 4 is based on KitKat. Unless Amazon unlocks the bootloader or releases FireOS 5 for these phones, we are stuck in KitKat (CM11).

Will applying update from adb format the phone..hopefully it will

Can't enter fastboot + unusual screen - bricked?

Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.

MaRkuS_538 said:
Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?View attachment 3659595
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.
Click to expand...
Click to collapse
I have that same line running down mine, looks like twrp.
hope someone chimes in...

It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.

r3t3ch said:
It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.
Click to expand...
Click to collapse
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...

You have a driver problem. If it gets listed under anything, uninstall the drivers for it from device manager. It should show up as something like "jem-pvt-prod-04" under other devices with a yellow triangle. You can then try to install its driver as adb composite interface or try using the driver from this thread. If you don't see "Android Composite ADB Interface" when you try manually installing the driver, reinstall adb/fastboot.

MaRkuS_538 said:
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...
Click to expand...
Click to collapse
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry

sullytrny said:
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry
Click to expand...
Click to collapse
Hey hope all went well with the storm for you, now can u do a write up on how to fix the issue please.

Yeah, hopefully. But it would be very nice to tell what you've done exactly (especially driver setup)
Gesendet von meinem Nexus 6P mit Tapatalk

Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?

MaRkuS_538 said:
Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?
Click to expand...
Click to collapse
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs

It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk

monster1612 said:
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Can you tell me how you did this? I disabled driver signature enforcement (running windows 10), but I have no clue where to go from here.
---------- Post added at 02:30 PM ---------- Previous post was at 02:20 PM ----------
MaRkuS_538 said:
It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
Can you by chance explain what you did? I've got mine stuck at that screen (no recovery or anything) and can't go anywhere.

I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk

MaRkuS_538 said:
I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?

kslonkey said:
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?
Click to expand...
Click to collapse
YES, i can help.
you need EITHER:
KFHD_SRTv1.3.5.zip 1.13 gig from here @ X-DA
OR
Minimal ADB and Fastboot (a few megs) from here @ X-DA
launch the app, and when it says "waiting on device" plug the usb cable into the ALREADY OFF tablet.
this is the only way i could get fastboot to work (and be "installed" in windows) on my 32 gig model. i have the "red screen of death" and these 2 apps are the only ones i could get to work. i WANT to try "kindle fire first aid" but ALL the links here for that app are DEAD.