Develop Bugs

[Q] Fastboot issues

Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?

BonzTM said:
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
Click to expand...
Click to collapse
No, there should not be any issue. I suggest to re-install the fastboot driver. Use 1wayjonny's drivers here.

I've seriously never had any issues whatsoever in any way with the drivers I'm using, and I got them from the knives & forks package. Check my sig.

Well I don't know what's your case but as I do stuff with Nexus, Galaxy tab and lg o2x on my computer sometimes one of the drivers gets messed for randoms reasons.. So I re install drivers and that's it... Try that suggestions
Sent from my Galaxy Nexus using xda premium

No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked 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"
}

I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.

rmagruder said:
I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
Click to expand...
Click to collapse
I must've done this a million times. Where are the newest drivers? I've downloaded 1.4.6.0 from Samsung's website. If you or somebody has these "newest" drivers, could I please get a link?
I've used the ones from Samsung's website, the Universal Naked drivers, Google's drivers from SDK, Drivers from Galaxy Nexus Toolkit v7, drivers from Galaxy Nexus Root Toolkit 1.4 by WugFresh. I get the same issue with all of them.

BonzTM said:
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
Click to expand...
Click to collapse
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.

Theshawty said:
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Click to expand...
Click to collapse
Did one even better. Went to a brand new machine that had never seen an Android phone to be sure I was getting a clean experience.
Firstly, when I plugged the phone in (Android on), immediately said that the device could perform faster if I plugged it into a USB 2.0 port. Problem is, it was a 2.0 port. Got all the drivers installed etc. MTP, PTP, ADB works; granted very slowly because it's only going at 1.1 instead of 2.0.
Rebooted into Fastboot, same problem as before. Device failed to start (error code 10).
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.

BonzTM said:
[snip]
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
Click to expand...
Click to collapse
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.

efrant said:
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
Click to expand...
Click to collapse
It seems to be fine. :crying:

BonzTM said:
It seems to be fine. :crying:
Click to expand...
Click to collapse
Try using a different cable. I just went through the exact same experience. Hours of not being able to get fastboot drivers to work (ADB would though!).
I have a small desk dock that I got off of E-Bay, and I too was getting the USB 1.1 speed warnings when using it. Never really thought much about it until this particular problem.
I've un-installed, re-installed drivers and done everything short of standing on my head in a corner
Unplugged it from the 'Dock' and used a regular USB2.0 compatible cable, and fastboot fired right up.

No OS, OTG not recognized. Am I bricked?

Accidental full wipe of my Nexus 7 has left me with a no OS paper weight.
Fastboot indicates it's locked but I can boot into TWRP, but can't get it to be recognized by any PC and it won't recognize my OTG-USB (which has been recognized by others).
Any ideas as to how to get her up and running would be greatly appreciated.
{
"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"
}

Did you mount the OTG usb in TWRP or just looked for it to auto detect?
Btw, this belongs in the Q & A section, so ask a mod to move it

I am unable to select/check mount the OTG while in TWRP. The OTG is formatted correctly as the OTG is readable on other devices, but it seems like it just isn't being found by the N7. I'm baffled.

Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562

Tried it on a full battery, still no luck.

tried to get it to work, any suggestions fellow XDAers? I'm in a real jam here

Check this thread: http://forum.xda-developers.com/show....php?t=3064562
Click to expand...
Click to collapse
Thanks, but I can't get the tablet to be recognized. I've tried it in multiple windows computers with both USB 2 and 3.

Have you tried adb/fastboot?

Have you tried adb/fastboot?
Click to expand...
Click to collapse
I am able to fastboot, but still can't get the pc to recognize that it's connected. The tablet takes a charge, but the pc never acknowledges that a device is connected, device manager never indicates a device is connected.

-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.

CrazyJ36 said:
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
Click to expand...
Click to collapse
Thanks. Everything hinges on the PC being able to recognize that I'm attempting to connect the tablet (or for the tablet to recognize that I've attached the OTG).
I have tried multiple USB cables and ensured that the drivers are installed on the multiple PCs I've attached to.
I have tried to ADB sideload in TWRP, but since none of the PCs recognize that the tablet is connected to the PC, ADB won't work.
Again, it's not that the drivers are not installed, but rather the PC not recognizing that I have attached a device through the USB (no sound, no pop-up, nothing in the device manager). It is extremely frustrating, especially since the device charges via the USB from the PC.

DorianX said:
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Click to expand...
Click to collapse
CrazyJ36 said:
Have you tried adb/fastboot?
Click to expand...
Click to collapse
Still no luck, any other recommendations?

Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.

I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1

CrazyJ36 said:
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
Click to expand...
Click to collapse
Nothing shows in the device manager. I was using KitKat on the tablet.
Turns on without an issue, opens TWRP with no issue.
when connected to the PC nothing occurs, not when it's on the Google screen, not when it's in TWRP, not in Fastboot, not when it's restarting. Nothing.
if it was the driver being missing, I'd at least see the device attached, just not communicating properly
sorry to hear about your GS4

The Apostle said:
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
if you truly had the same exact problem, how were you able to use ADB if your device wasn't recognized on a PC or OTG?

Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1

The Apostle said:
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
it's alright, thanks for the thought.
I'm just hoping since I can get into TWRP someone has an idea of how I can get it to recognize the OTG or the PC to see it and I can get into ADB.

Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.

zandgreen said:
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
Click to expand...
Click to collapse
the port looks perfectly fine, I was thinking the same thing, but there doesn't seem to be any damage. I almost wish it was damaged so I could at least assume that's the problem and just trash the thing.

USB Data transfert not working

Hello everyone,
Since few days, I have a really enoying issue with my Pixel 2 XL.
Android Auto is not working anymore.
after differents diagnostic test, USB data is not working at all. I tried different USB cable, different Android Auto car and different Computer. I have only USB charge.. not data. Even if I enable USB debbug or if I try in safe mode
Does anyone have the same issue ?
What can I do ?
thank you for your help !
PS: https://productforums.google.com/forum/#!topic/nexus/PP_MDA4y0kU;context-place=forum/Nexus this issue looks like the same as me. but even if I enable or disable usb debbug. it doesn't work. and I am with 8.1 Oreo

MrMoi said:
Hello everyone, Since few days, I have a really enoying issue with my Pixel 2 XL. Android Auto is not working anymore. after differents diagnostic test, USB data is not working at all. I tried different USB cable, different Android Auto car and different Computer. I have only USB charge.. not data. Even if I enable USB debbug or if I try in safe mode Does anyone have the same issue ? What can I do ? thank you for your help ! PS: https://productforums.google.com/forum/#!topic/nexus/PP_MDA4y0kU;context-place=forum/Nexus this issue looks like the same as me. but even if I enable or disable usb debbug. it doesn't work. and I am with 8.1 Oreo
Click to expand...
Click to collapse
Have you tried revoking USB debugging authorizations and then re-enabling? It is the option just below the USB debugging toggle. Taking AA completely out of the equation, if after you have tried more than one USB-A to USB-C cables on more than one PC and cannot get MTP working you probably need to do a factory data reset. This will confirm whether you have a hardware issue or not. It is also the first step Google will require you to do prior to allowing an RMA.
Edit: You can also test if fastboot is working in bootloader mode, and if adb is working in recovery mode.

thank you for your help..
I've tried adb, fastboot and factory reset...:crying:

MrMoi said:
thank you for your help.. I've tried adb, fastboot and factory reset...:crying:
Click to expand...
Click to collapse
I'm not sure you understood... my suggestion was to test the phone in bootloader mode and send fastboot commands to it from your PC (eg. fastboot devices) -and- while in recovery mode (eg. adb devices). This is of course with adb debugging enabled. You also didn't answer my question about revoking adb in Developer Settings and then re-authorizing it? I still suspect you have a cable/pc driver issue.

Oups sorry my answer is not really clear.
Yes I revoke all ADB computer in developer setting . I try to boot in fastboot mode and recovery mode but ADB devices and fastboot device command doesn't work.
I can't see the device in my w10 computer in device manager

MrMoi said:
Oups sorry my answer is not really clear. Yes I revoke all ADB computer in developer setting . I try to boot in fastboot mode and recovery mode but ADB devices and fastboot device command doesn't work.I can't see the device in my w10 computer in device manager
Click to expand...
Click to collapse
Use THIS tool to view and remove any Google related USB drivers and try again. Don't worry about removing any drivers, they will re-install. Make sure you get them all out, REBOOT the PC and then plug your device back in. Are there any conflicts in your Device Manager in the USB section?

v12xke said:
Use THIS tool to view and remove any Google related USB drivers and try again. Don't worry about removing any drivers, they will re-install. Make sure you get them all out, REBOOT the PC and then plug your device back in. Are there any conflicts in your Device Manager in the USB section?
Click to expand...
Click to collapse
no conflicts in my device manager, nothing change after removing all my 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"
}

MrMoi said:
no conflicts in my device manager, nothing change after removing all my drivers
Click to expand...
Click to collapse
I had the same problem with my Nexus 5x (now dead) and recently pixel 2xl where there is no charging options or USB debugging mode in all different modes(recovery, fast boot) like yours.
What I did before it was installing Andromeda. Not sure if your case was the same.
Anyway, I fixed mine by going to safe mode. Plugging usbA to C, and connecting to mac. Tried changing usbc between the orientation while trying "adb devices" in the terminal on mac. After a while plugging in in each orientation. It came back to work. Not sure why..
Try it on your windows machine if it worked

wkJason said:
I had the same problem with my Nexus 5x (now dead) and recently pixel 2xl where there is no charging options or USB debugging mode in all different modes(recovery, fast boot) like yours.
What I did before it was installing Andromeda. Not sure if your case was the same.
Anyway, I fixed mine by going to safe mode. Plugging usbA to C, and connecting to mac. Tried changing usbc between the orientation while trying "adb devices" in the terminal on mac. After a while plugging in in each orientation. It came back to work. Not sure why..
Try it on your windows machine if it worked
Click to expand...
Click to collapse
thank you, but still not working

Did you ever get this problem resolved? I am having the same issue on my XL 2

I experience this problm as well but I just try different USB ports then it magically works. Quite annoying.

Boiler_81 said:
Did you ever get this problem resolved? I am having the same issue on my XL 2
Click to expand...
Click to collapse
Hello,
I had to send it back to the Google store. I never knew what the problem was.

Thank You
MrMoi said:
Hello,
I had to send it back to the Google store. I never knew what the problem was.
Click to expand...
Click to collapse

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

HD1907 won't connect to PC (TRIED EVERYTHING)

Phone will only connect to adb in bootloader mode and shows as (unauthorized) despite USB debugging enabled. Tried revoking all but did not fix.
Won't prompt for file transfer or USB debugging. Nothing even shows up in device manager when phone is booted into Android.
Tried 4 cables and 4 computers. Tried changing default usb mode.
Bootloader is unlocked.
I used to transfer files all the time but not it randomly does not connect.

You have to click on the popup on phone to "authorize" adb connection. Otherwise, u need latest platform tools and drivers

HueyT said:
You have to click on the popup on phone to "authorize" adb connection. Otherwise, u need latest platform tools and drivers
Click to expand...
Click to collapse
I never get the popup. It is as if the phone is connected to the wall when I plug it into my computer. EXCEPT when I am in booted into recovery and it says it is unauthorized.
adb devices
{
"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"
}
Not detected in fastboot mode at all.
The only option I see is to try factory reset via recovery.
I see this in recovery

Now I literally can't get anything to show in device manager or adb/fastboot.
I have tried every driver and guide under the sun. Disabled driver signature enforcement. Ran the convert MSM and the regular 1907 MSM, didn't fix.
No matter how many times I install the OP drivers or Google nothing even shows in device manager even when "Show hidden devices" is checked. This picture I am in the system with USB debug and OEM unlock enabled set to file transfer (Although it never prompted me for anything, in fact USBDeview doesn't show anything when I plug in the phone):

So it recognized your hd1907 in EDL mode for msmtool? If so then it's a software prob and fixable with oos10:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com

HueyT said:
So it recognized your hd1907 in EDL mode for msmtool? If so then it's a software prob and fixable with oos10:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
I already ran this patched MSM like 10 times, I just get left in fastboot with no recovery or system and am forced to run the regular 1907 MSM to get back. Also tried Ubuntu just now and still not detected. I am very confident it is a software issue (on both phone and pc maybe) but I just can't figure it out for the life of me.
Now my bootloader is locked and I can't even connect to fastboot to unlock it again.
My sim is genuinely unlocked and I also have the genuine unlock_code.bin.
Currently spinning up a brand new install of Windows on my laptop to test with. Do you have exact recommendations for drivers? Some people recommend the Oneplus one and others the Google. What about the all in one tool driver install?
I currently have a network unlocked stock fully updated OOS 11.0.1.6.HD63CB system with locked bootloader. (I tried OTA updating to see if it would fix it)

Jonnyswboy said:
I already ran this patched MSM like 10 times, I just get left in fastboot with no recovery or system and am forced to run the regular 1907 MSM to get back. Also tried Ubuntu just now and still not detected. I am very confident it is a software issue (on both phone and pc maybe) but I just can't figure it out for the life of me.
Now my bootloader is locked and I can't even connect to fastboot to unlock it again.
My sim is genuinely unlocked and I also have the genuine unlock_code.bin.
Currently spinning up a brand new install of Windows on my laptop to test with. Do you have exact recommendations for drivers? Some people recommend the Oneplus one and others the Google. What about the all in one tool driver install?
I currently have a network unlocked stock fully updated OOS 11.0.1.6.HD63CB system with locked bootloader. (I tried OTA updating to see if it would fix it)
Click to expand...
Click to collapse
U need Qualcomm USB 9008 drivers

HueyT said:
U need Qualcomm USB 9008 drivers
Click to expand...
Click to collapse
I successfully ran the MSM several times.

After above patched MSMtool, Then can't u do "fastboot flashing unlock_critical" to unlock bootloader? Only then do u fastboot flash all oos10 files

HueyT said:
After above patched MSMtool, Then can't u do "fastboot flashing unlock_critical" to unlock bootloader? Only then do u fastboot flash all oos10 files
Click to expand...
Click to collapse
After above patched MSMtool I cannot connect to PC via fastboot. I just bought a Pixel 6, but thanks for the help.