Develop Bugs

Upgrading your rom on Windows Vista And Windows 7

Follow these instructions and your vista and 7 problems is over...
I used this guide and it works on my phone..
Originally Posted by pvdhelm
To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here to install it first - http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
One problem with windows VISTA and 7 is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.
For this guide firstly you need to download the new drivers:
Drivers for Windows Vista/7 x32 - http://forum.xda-developers.com/attachment.php?attachmentid=33662&d=1169888879
Drivers for Windows Vista/7 x64 - http://forum.xda-developers.com/attachment.php?attachmentid=33892&d=1170385335
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.
Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA/7 PC.
Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon
In the connection settings menu untick "allow USB connections" then press OK.
Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.
Scroll down the list and make sure these services are present:
Windows Mobile-based connectivity
Windows Mobile 2003-based connectivity
If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.
Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync".
This will bring up the properties of the currently connected device (the hermes in bootloader).
Go to the "Driver" tab and click "Update Driver".
Click "Browse My Computer for Driver Software".
Select "Let me pick from a list...."
Click the "Have Disk" button.
Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
Vista x32 users select the file "wceusbsh.inf"
Vista x64 users select the file "wceusbshx64.inf"
Then click Open.
click next and the driver will be installed (wait a moment).
Press close and escape back to the desktop now.
Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.
click the WMDC line and click "End Process". In the confirmation window, again press End Process.
Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").
Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which vista uses when the device is in bootloader mode.
Can this be made a Sticky please..??

Followed your Steps on Win7 x64 but WMDC doesnt connect do my device although I re-enabled USB connections. Digital Driver signing is disbaled.
No it did work, I just didnt get it
Write this into the wiki plx, really helpful.

All done till the driver installation.
But start from task manager and so on, it's failed to connect.
Am i doing wrong?

Just try to flash, at my side WMDC shows no connections either but flashing is possible.

DasEtwas said:
Just try to flash, at my side WMDC shows no connections either but flashing is possible.
Click to expand...
Click to collapse
After i installed the drivers then i started WMCD and re-enable USB connections and then took out my cable out of the phone then put it back in and it connected..

Method with no install
What I have been doing with Win7 without installing any drivers is
- Put phone in bootloader mode (press power and left OK button while pressing the reset button on bottom)
- Start the RUUWrapper
This of course assumes that you have hardSPLed the phone and select the right options, no autodetect
This is what I have been doing for a while now, I dont recall updating any drivers or activesync/mobile center

coolsva said:
What I have been doing with Win7 without installing any drivers is
- Put phone in bootloader mode (press power and left OK button while pressing the reset button on bottom)
- Start the RUUWrapper
This of course assumes that you have hardSPLed the phone and select the right options, no autodetect
This is what I have been doing for a while now, I dont recall updating any drivers or activesync/mobile center
Click to expand...
Click to collapse
Well this is another option you can do then...should i add this to my post..?

[GUIDE] adb in Win7 (x64, maybe others)

I had a lot of trouble getting the adb drivers on my work Win7 x64 laptop working. Here's what seems to have done the trick.
1. Pull up a commandline, go to Documents and Settings\username\.android directory, and do
Code:
echo 0x04e8 >> adb_usb.ini
if you haven't done so already.
2. Install KIES. (Downloading the separate driver package didn't work--the driver package refused to install.)
3. Set device in adb mode (Settings | Applications | Development | USB debugging(x)).
4. Plug device into computer. You will get a tray icon with stuff spinning. Click on it. If things go fine, you'll eventually see a list of drivers with "Ready to use" and green checkmarks.
If all the drivers have checkmarks, you're done--you had it easy. This guide is for cases like mine where you find that two drivers, "CDC Serial" and "SAMSUNG_Android" are labeled "No driver found" and adb doesn't work.
5. Right-click on My Computer, choose Properties, then "Device Manager". Expand "Other devices".
6. Right-click on "SAMSUNG_Android".
7. Choose "Update driver software" | "Browse my computer for driver software" | "Let me pick from a list".
8. Make sure "Show All Devices" is selected and click on "Next".
9. Click on "Have Disk" and type in "C:\Program Files (x86)\Samsung\USB Drivers\25_escape" (auto complete made it easier to type; if you have 32-bit windows, the " (x86)" should be omitted).
10. You will get a two-pane selection of the drivers. Selecting one of the two "SAMSUNG Electronics Co., Ltd." listings (you may need to look through both) in the left pane gives an option list on the right that includes two "SAMSUNG Android ADB Interface".
11. Choose the first "SAMSUNG Android ADB Interface" and click on "Next". You will get a warning that Windows cannot verify compatibility. Accept this. Windows will install the driver and once it's done you'll click on "Close".
12. Windows installed the driver and ADB started working. (If it didn't start working, I would now have gone back to the Device Manager, right clicked on "SAMSUNG Android ADB Interface", and then redid steps 7-11, but this time with the other "SAMSUNG Android ADB Interface" driver.)
This is enough to get adb working. But it's still probably worth fixing the CDC Serial device.
13. Repeat steps 7-11 in the Device Manager with the "CDC Serial" device now, except that instead of the ADB driver you will look for and install "Samsung Mobile USB CDC Composite Device" in the right pane in steps 10-11.
If all goes well, you will get more spinning stuff in the task bar, and eventually Device Manager doesn't show any devices in "Other devices" with yellow triangles. But if things go for you like they did for me, you'll have "CDC Abstract Control Model (ACM) in "Other devices".
14. Repeat steps 7-9 in the Device Manager with the "CDC Abstract Control Model (ACM)" device now. (You may have some USB Modem options showing up in some places, but I ignored those, and did the same "Have Disk" move as before.)
15. I got a single-pane display showing only "SAMSUNG Mobile USB Modem". (Maybe you'll have two-pane display and you'll have to find it as in steps 10-11.) Select it and click "Next". I didn't get any warnings. Windows will install the driver and once it's done you'll click on "Close".
At this point, Device Manager showed all devices correctly functioning. And "adb shell" worked fine.
16. If you don't want KIES, just uninstall it, but make sure not to uninstall the drivers (the KIES uninstaller will ask).

Man, thank you so much. I was going crazy with this. Worked for my T-mobile SGS3. :cyclops:
One thing that's not mentioned, after I fixed the ADB and the CDC driver, it threw an error in the MTP device, I just let Winblows install that one automatically and it worked fine.

There is less steps needed,i got my ADB working in Windows 8 64bit RC1 developer preview flawlessly.
Just disable driver signature,install sdk,add sdk folder to windows environment and you are done.

nice. I didn't have any problems with mine, just sayin. Its always nice to see people help each other.
Sent from my SPH-D710 using xda premium

Worked perfectly on my PC and the Kies could see the phone as well (GT-I9100).
Thanks again !! :good:

Longest ADB guide I've ever seen.
Sent from my sph-d710 using xda premium

Thanks for this!

Great guide man! Helped solving some driver issues with Windows 8.1 and Note 3, particularly installing the SAMSUNG_android adb device manually!
Thank you very much!

I thought I would never find a tutorial like that, it saved my life lol. Thank you so much!

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 unlock bootloader, fastboot not detecting device

UPDATE: Got it working on a windows 7 machine.
I've been trying to unlock my bootloader but have been having issues. I have done the following:
- Enabled Developer Options
- Enabled USB Debugging
- Enabled the OEM Unlock in the Developer Options
- Installed drivers via android SDK
I have adb and fastboot installed from the android SDK. Using that, I have been able to see my device with 'adb devices'. I have also been able to reboot it using 'adb reboot bootloader'. However, once the phone is in fastboot, it does not seem to be detected by my machine. I have tried 'fastboot devices' to no avail. Using 'fastboot oem unlock' just stalls at '< waiting for device >'. Am I missing something?
I have also tried:
- Using a different computer
- Using different USB ports
- Using different ADB / fastboot package (the minimal one).
Please assist! I'd really like to unlock my bootloader now for future flexibility.

There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"

Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)

crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.

yourbuddypal said:
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.
Click to expand...
Click to collapse
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"

amitte said:
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"
Click to expand...
Click to collapse
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working

yourbuddypal said:
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working
Click to expand...
Click to collapse
Yes this is normal. For the bootloader part, do not let windows search automaticly. Do as i described earlier exept use the driver i uploaded for you or search any other nexus usb driver install guide since the process did not change
Same applies to the installation when you are in the system already. Exept do not override any driver that is under portable devices since its the file transfer protocoll driver.

I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!

yourbuddypal said:
I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!
Click to expand...
Click to collapse
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
{
"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"
}

Solution on Linux
I had a similar problem earlier today on one of my linux boxes. Turns out, in order to use fastboot (successfully) under linux, you need to run fastboot with sudo rights.
If I had to guess, I'd guess this is because unlike adb, fastboot doesn't run as a server, so fastboot always needs to get elevated permissions to communicate with a device on a USB port.
Maybe it's possible that Windows wants Administrator rights for similar reasons?

duckxtales said:
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
Click to expand...
Click to collapse
Sorry, I really don't have any more feedback to give you. It really did seem like voodoo when it worked. The only thing I can think to explain the "random" aspect is that perhaps it is related to the quality of cable used. I was using these (http://www.amazon.com/Orzly-Type-Cables-Assorted-Colours/dp/B013RMG5WY/ref=cm_rdp_product), which have now been taken down due to cable standards as described in the comments section for that product. I was thinking that maybe the different USB port on the desktop machine was somehow able to get sufficient voltage or something. Voodoo!

I am having the exact same issue with my 6P right now. However it shows when I do adb devices, just not fastboot devices. Weird...
I even uninstalled the Google USB driver and reinstalled it using Android Studio but Still did not work. Then I even went to Device Manager and uninstalled and deleted the driver. Then went manually to file path C:\Users\MyWindowsLoginName\AppData\Local\Android\sdk\extras\google\usb_driver and clicked next. It installed successfully, but displays as Android Composite ADB Interface. So I guess that is correct then?
Tried to just sideload the new 6.0.1 OTA update using adb since adb devices was recongizing it but still not found...
C:\Users\Matthew\AppData\Local\Android\sdk\platform-tools>adb sideload angler-MMB29M-from-MDB08L.zip
loading: 'angler-MMB29M-from-MDB08L.zip'
error: device '(null)' not found
EDIT: I got it after unplugging my phone, killing the adb.exe process in task manager, waiting until in bootloader before plugging phone in, then running fastboot devices shows the serial number now. I hope that helps others!

I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?

I had the same trouble on my 64 bit Windows system. I believe it was HTC sync software that threw the monkey wrench. But I uninstalled that software together with all the adb fastboot drivers for my other devices, removed all adb fastboot versions, then installed the 64 bit version of the Minimal adb fastboot tool.
All good now

Garvinr said:
I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?
Click to expand...
Click to collapse
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)

wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Thank you.
I follow this step. now I can use fastboot.

crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
Thanks man! Worked immediately after updating the drivers!

I too had this issue.
Manually installed drivers using this guide.
(pretty much the same instructions as wangxiangg, but with pics)

wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Man. That was it. Worked like a charm. Thank you.
To clarify, you do this while you are in Fastboot Mode and you right-click on "Android" in step 1.
You can go through the steps while you are in Fastboot Mode and with the cable still plugged in.

amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Someone give this man a cookie!
it worked!!!!!!!!

Fastboot mode Troubleshooting [windows users]

Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows​
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.

Nice... Thanks for the guide... Many people needed it... Was about to make one myself...

Great. Many many thanks bro

kickyvivi said:
troubleshoot guide for updating the adb and fastboot drivers manually in a pc running any version of windows​
first, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
pre-requisites:
* pc running windows 7/8/10
* internet connection (just 20mb)
* working usb cable
steps:
(1) download the [official][tool][windows] adb, fastboot and drivers - 15 seconds adb installer v1.4.3 from xda
link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) install it with "y" confirmation for all 3 options and reboot the pc
(3) disable the internet connection of your pc
(4) reboot your phone to fastboot mode and plug it to your pc's usb 2.0 port (important)
(5) open device manager on pc and scan for hardware changes from the option if your device is not listed already
(6) if it shows 'asus android device' -> "asus android bootloader interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) now scan for hardware changes (magnifying glass icon)
(8) it will show 'android' with an ! Symbol
(screenshot 3)
(9) right click -> update driver -> browse my computer for driver software
(10) choose "let me pick from a list of available drivers on my computer"
(11) choose "android device" or "asus android device" or similar option and confirm it with yes or next option
(screenshot 4)
(12) a warning will pop up, press 'yes'
done
(13) go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )

Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
I am having same problem... Did you find any solution for it?

kickyvivi said:
Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows​
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
Hello, I followed your mentioned steps but in my drivers its showing "Samsung Android Device" is that okay for my asus zenfone max pro m1 device? Or there is one portable device option, is that it?

Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!

kickyvivi said:
(12) A warning will pop up, press 'Yes'
Done
Click to expand...
Click to collapse
After I completed all the steps, my phone showed on screen "press any key to shutdown" and even in device manager it shows android ADB interface as hidden. Help please. Rebooting again to fastboot mode doesn't help because it shows the same screen "press any key to shutdown" on reconnecting with PC.

May Asus x01bd can't in to the mode fastboot..how to solved it?

Kajin660 said:
May Asus x01bd can't in to the mode fastboot..how to solved it?
Click to expand...
Click to collapse
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it

D0CT0RFATE said:
Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!
Click to expand...
Click to collapse
this same with me,, n i donk know how it is??
my phone asus x01bd

Nightmonkeyps said:
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it
Click to expand...
Click to collapse
can u explaining me?? sorry i dont understand what u mean??

Kajin660 said:
can u explaining me?? sorry i dont understand what u mean??
Click to expand...
Click to collapse
Well you know how there's a BIOS in your PC which contains the basic commands required to run a computer. There is a setting called secure boot inside your BIOS. You need to turn it off and then install fastboot tools. To open the BIOS, repeatedly press F10 or F8 on your computer while it is opening. This is how it worked for me atleast

Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
this happen to me,, and i have solved this,,
step:
1. U must flash ur Phone via qfil,(*)
,than u will lost ur IMEI and SN will Change to 111111,, but dont worry thats can be back again
2. next step is u must recover ur IMEI and SN back (in tele group u wil found the step) after that U just flash stock firmware modified (via TWRP/ORFOX)n then ur phne willl back normally
Note : (*) in firmware for flash via qfil replace the recovery.img with twrp/orfox (rename To "recovery.img") this will bring u a twrp/orfox recovery after flash via qvil
i hope this can help..