Develop Bugs

[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.

adb drivers in Win7 64

I have no problem connecting my Epic 4G Touch to a WinXP system with adb.
On Win7 64, I installed Kies, but when I plug the phone in, I am told that no drivers for CDC Serial and SAMSUNG_Android were found. And "adb devices" finds nothing.
I can mount the device just fine for transferring files. But I need adb for software development.

arpruss said:
I have no problem connecting my Epic 4G Touch to a WinXP system with adb.
On Win7 64, I installed Kies, but when I plug the phone in, I am told that no drivers for CDC Serial and SAMSUNG_Android were found. And "adb devices" finds nothing.
I can mount the device just fine for transferring files. But I need adb for software development.
Click to expand...
Click to collapse
Unless you're going to use it, I would uninstall KIES. Having it running in the background can mess up other functions like flashing with odin. I would just install the Samsung Drivers by themselves. It worked for my adb install in windows 7.
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe

tdunham said:
Unless you're going to use it, I would uninstall KIES. Having it running in the background can mess up other functions like flashing with odin. I would just install the Samsung Drivers by themselves. It worked for my adb install in windows 7.
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Click to expand...
Click to collapse
Just did that. Uninstalled KIES and tried to install the driver package. Driver installer says: "The MSS Installation for SAMSUNG USB Driver for Mobile Phones V1.3.2360.0 has failed."
Were you using 64-bit Win7?

arpruss said:
Just did that. Uninstalled KIES and tried to install the driver package. Driver installer says: "The MSS Installation for SAMSUNG USB Driver for Mobile Phones V1.3.2360.0 has failed."
Were you using 64-bit Win7?
Click to expand...
Click to collapse
Uninstall all your drivers from device manager and start fresh. Only install the driver.exe from samsungs support page. Once that is installed plug your phone in and let it run through the drivers before you try anything else.
If your computer isn't recognizing your phone in the first place then it's not a problem with adb, its the drivers, so start there.

OK, so I uninstalled KIES and the drivers.
I then tried to install the drivers. No go: The installer continues to fail, with the progress bar at around 80-90%. I experimented with running the installer as administrator, installing off of \Program Files (x86) and off of \SAMSUNG, instead of the default \Program Files, and still no go.
I then re-installed KIES, turned off debug in the phone, and plugged it in. Win7 installed a driver for the phone and all was well.
I then unplugged the phone, turned on debug, and plugged it back it. Now Win7 installed the following drivers:
Code:
USB Composite Device
USB Mass Storage Device
Android UMS Composite USB Device (two of these!)
and said they're ready to use. But it also tried to install:
Code:
CDC Serial
SAMSUNG_Android
and it gave "Driver not found" for these.
And "adb devices" lists nothing.
To make sure adb works fine I then plugged in a Kindle Fire. Windows set up the drivers for it and it showed up in "adb devices" just fine.

I still can't get it working.
I even tried using the advice I saw on some blog to use the Device Manager, and then update the non-working devices by directing Windows to look in the "\Program Files (x86)\SAMSUNG\USB Drivers" directory for drivers. No effect--Windows says it can't find an appropriate driver there.
The 25_escape\ssudadb.inf file seems to contain stuff with hardware IDs that match the device that Windows can't find a driver for. BUT there is no x64 section in the inf file. Is there supposed to be one?
I even tried turning off Windows' driver signature checks. Didn't help.
Does anybody have this working 64-bit Win7?

arpruss said:
I still can't get it working.
I even tried using the advice I saw on some blog to use the Device Manager, and then update the non-working devices by directing Windows to look in the "\Program Files (x86)\SAMSUNG\USB Drivers" directory for drivers. No effect--Windows says it can't find an appropriate driver there.
The 25_escape\ssudadb.inf file seems to contain stuff with hardware IDs that match the device that Windows can't find a driver for. BUT there is no x64 section in the inf file. Is there supposed to be one?
I even tried turning off Windows' driver signature checks. Didn't help.
Does anybody have this working 64-bit Win7?
Click to expand...
Click to collapse
Have it working - and did remember I have Kies installed.
Maybe I downloaded both the separate driver and Kies?
USB Driver Link:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Kies Link:
http://org.downloadcenter.samsung.c...0111012045653670/KiesPC_2.0.3.11082_152_4.exe
Know I have problem still with Kies... but I can use ODIN without issues.

Finally got it!
I can't really explain how I did it, as there was a lot of trial and error and I wasn't keeping notes. But the basic trick was to right click in device manager on the unknown SAMSUNG_Android device, choose Update Driver, choose "Let me pick", choose "Have disk", point to the "SAMSUNG\USB Drivers\25_escape" folder from the KIES installation, and then choose "Samsung Mobile USB Composite Device".
You may then get another unknown device, which using the same method you set to ADB. I did a bunch of stuff in different ways, trying to match different drivers from the 25_escape folder to different devices, until it finally worked.

Same issue, solved twice
I have had similar problems in win7 64bit twice now. I got it working once, then ended up reinstalling windows for other reasons. I then had the same problem when trying to install cm9alpha3.
Both times it took a strange combination of installing the drivers manually, plugging in the phone, etc. to get it working. The best advice I have for others is to keep trying.
Also, it seems that Kies almost never gets it right. I personally don't even keep it installed.

I posted a guide on how I got this working.
adb works, but I still can't connect to KIES.

arpruss said:
I posted a guide on how I got this working.
adb works, but I still can't connect to KIES.
Click to expand...
Click to collapse
What Rom are you on. I had same problem with phone running on Calks E4GT v. 3.0 GB Rom, Kies won't recognize Calks Rom, wifeys stock Epic is recognized no problem . Pc Asus G73 win7 64. PC recognizes my phone but Kies won't.
Pp.
Edit
It is rumoured that Kies w will only recognize stock roms.
Pp.
Sent from my tofu plasma converter.

PanchoPlanet said:
What Rom are you on. I had same problem with phone running on Calks E4GT v. 3.0 GB Rom, Kies won't recognize Calks Rom, wifeys stock Epic is recognized no problem . Pc Asus G73 win7 64. PC recognizes my phone but Kies won't.
Pp.
Edit
It is rumoured that Kies w will only recognize stock roms.
Click to expand...
Click to collapse
I am on stock EL29, no root.
It worked once on my WinXP system, but now it doesn't work on either the WinXP or Win7 system.

Oops. I misunderstood the KIES error message to mean that I'm supposed to have the phone in adb mode for KIES to work. But actually adb mode needs to be off for KIES to work. Now it works fine.

arpruss said:
Oops. I misunderstood the KIES error message to mean that I'm supposed to have the phone in adb mode for KIES to work. But actually adb mode needs to be off for KIES to work. Now it works fine.
Click to expand...
Click to collapse
hi, I have same issue with you now, can you teach me how to solve it? thanks.
WIN7 x64 with GT-I9300

Just turn off USB debugging and Kies will connect.
Sent from my SPH-D710 using Tapatalk 2

Chrome DevTools Inspect working again
{
"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"
}
I couldn't get Chrome Dev Tools to remote debug (chrome://inspect) until I installed the "Android Composite ADB Interface" (just picked the latest version). See screenshot attached (taken before I installed correct driver).
1. To install I right-clicked on the "SAMSUNG_Android" driver under "Other Devices" in the Device Manager.
2. "Update Driver Software..."
3. "Browse my computer for driver software"
4. "Let me pick from a list of device drivers on my computer"
5. Select "Samsung Android Phone"
6. Select "Android Composite ADB Interface Version" (latest one)
7. Ignore warning that Windows does not know if this driver is compatible.
At this point, I saw the "Trust this device" message come up on the Samsung phone
Thanks for the help. This was really killing me as I had tried everything including installing the official drivers from Samsung's site (developer.samsung.com/technical-doc/view.do?v=T000000117)
Note: I don't have Windows Kies installed and I am using Windows 7 x64 OS. Also note that this does not fix the "CDC Serial" error, however, this is not required for remote debugging over USB.

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

Moto G5 does not connect to the PC in any way!

So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.

Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.

Hyoretsu said:
Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.
Click to expand...
Click to collapse
it does not work in fastboot mode, in fact it is as if the cell phone was dead, it stopped working on the computer, it only loads, I already installed drivers, everything ... but no use, I already tried to use rsd lite but it does not recognize!

Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up

Hyoretsu said:
Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up
Click to expand...
Click to collapse
to recognize in fastboot mode, the cell phone does not need to be recognized on the pc first? I connect the USB cable and it's the same as nothing, besides that, debugging usb also does not work to proceed in fastboot

Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands

Hyoretsu said:
Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands
Click to expand...
Click to collapse
{
"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"
}
Does not recognize, neither in fastboot nor in normal mode

@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.

Chekm8Qc said:
@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.
Click to expand...
Click to collapse
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?

kolple said:
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?
Click to expand...
Click to collapse
This is odd for sure. I wish I could help more honestly. Trying USB 2.0 or 3.0 ports doesn't change anything right? Probably not.

kolple said:
Does not recognize, neither in fastboot nor in normal mode
Click to expand...
Click to collapse
I would say update your adb/fastboot
I never use minimal adb/fastboot but always the package that comes with the full android sdk
Also try a different USB cable
And you can try cmd as admin instead of the windows power shell not that it should make a difference

kolple said:
So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.
Click to expand...
Click to collapse
Try using Moto lenovo smart assistant it will flash the latest firmware.

riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
Really? I didn't even know that.

riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.

kolple said:
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.
Click to expand...
Click to collapse
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.

Chekm8Qc said:
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.
Click to expand...
Click to collapse
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging

kolple said:
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging
Click to expand...
Click to collapse
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.

Chekm8Qc said:
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.
Click to expand...
Click to collapse
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me

kolple said:
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me
Click to expand...
Click to collapse
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/

Chekm8Qc said:
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/
Click to expand...
Click to collapse
did not work, even changing the options MPT, PTP, loading, the device manager did not appear anything either!
@edit
USB HOST DIAGNOSTIC