I can't seem to get through with Odin. I've tried multiple different versions of Odin and two firmware version and running as admin with no luck.
The issue I keep seeing is this:
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I have Samsung driver version 1.5.51.0, phone model is a Verizon(VZW) SM-G960U, android 9 of course, baseband G960USQS3CSAG.
I'm trying to G960USQS3BRK2 provided by SamMobile.
Happy to provide more info as needed
MEGAtheguy said:
I can't seem to get through with Odin. I've tried multiple different versions of Odin and two firmware version and running as admin with no luck.
The issue I keep seeing is this:
I have Samsung driver version 1.5.51.0, phone model is a Verizon(VZW) SM-G960U, android 9 of course, baseband G960USQS3CSAG.
I'm trying to G960USQS3BRK2 provided by SamMobile.
Happy to provide more info as needed
Click to expand...
Click to collapse
Assuming you're using Windows, have you made sure you're actually using the Samsung driver? My computer has a tendency to switch to the generic MTP driver whenever I try to do something with ADB.
sonic65101 said:
Assuming you're using Windows, have you made sure you're actually using the Samsung driver? My computer has a tendency to switch to the generic MTP driver whenever I try to do something with ADB.
Click to expand...
Click to collapse
How would I go about making sure I am using the correct driver? From what I know, it wouldn't show up in Odin until I installed the driver
MEGAtheguy said:
How would I go about making sure I am using the correct driver? From what I know, it wouldn't show up in Odin until I installed the driver
Click to expand...
Click to collapse
Try a different USB port on the PC, different USB lead, and try a different PC
Driver "Should" install automatically when you connect the phone
Try these too
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
*Detection* said:
Try a different USB port on the PC, different USB lead, and try a different PC
Driver "Should" install automatically when you connect the phone
Try these too
Click to expand...
Click to collapse
Tried different cables and ports on my computer. Trying with another computer at the moment but it seems to stall out on SetupConnection with more than one port on that system
MEGAtheguy said:
Tried different cables and ports on my computer. Trying with another computer at the moment but it seems to stall out on SetupConnection with more than one port on that system
Click to expand...
Click to collapse
Does the USB data connection work for file transfer on a PC?
Which version of Windows?
It is a PC and not a Mac running Windows ?
*Detection* said:
Does the USB data connection work for file transfer on a PC?
Which version of Windows?
It is a PC and not a Mac running Windows ?
Click to expand...
Click to collapse
All 20 pins in the type C connector, Windows 10 (1809), neither are Macs as I built both of them
MEGAtheguy said:
All 20 pins in the type C connector, Windows 10 (1809), neither are Macs as I built both of them
Click to expand...
Click to collapse
Yea sorry I mean can you transfer files from phone to PC via USB?
Try enabling USB debugging in Developer Options too
*Detection* said:
Yea sorry I mean can you transfer files from phone to PC via USB?
Try enabling USB debugging in Developer Options too
Click to expand...
Click to collapse
I've enabled USB debugging, the cable allows for file transfers, I can access whatever directories on the phone and mSD card in the phone. Yet I still get the same result.
{
"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"
}
MEGAtheguy said:
I've enabled USB debugging, the cable allows for file transfers, I can access whatever directories on the phone and mSD card in the phone. Yet I still get the same result.
Click to expand...
Click to collapse
What are you adding in "USERDATA" in ODIN ?
Should only have the first 4 sections added
Make sure you're using the normal ODIN too, not the patched one
*Detection* said:
What are you adding in "USERDATA" in ODIN ?
Should only have the first 4 sections added
Make sure you're using the normal ODIN too, not the patched one
Click to expand...
Click to collapse
I'm not sure since it was from SamMobile, but I guess it doesn't matter either way. It is a normal Odin from what I know, too.
MEGAtheguy said:
I'm not sure since it was from SamMobile, but I guess it doesn't matter either way. It is a normal Odin from what I know, too.
Click to expand...
Click to collapse
And you are putting the phone in Download Mode right?
Firmware comes with
AP
BL
CP
CSC and HOME_CSC
You only choose either HOME_CSC or CSC, not both, and nothing is added to USERDATA
Other than that I am out of ideas
*Detection* said:
And you are putting the phone in Download Mode right?
Firmware comes with
AP
BL
CP
CSC and HOME_CSC
You only choose either HOME_CSC or CSC, not both, and nothing is added to USERDATA
Other than that I am out of ideas
Click to expand...
Click to collapse
Yeah my phone is in that weird teal screen that says "Downloading... Do not turn off target"
In the top right I have this
RPMB fuse blown
RPMB PROVISIONED
CURRENT BINARY : Samsung Official
FRP LOCK : OFF
KG STATUS : Checking
QUALCOMM SECUREBOOT : ENABLE
RP SWREV : B3(2,2,2,3,2) K3 S3
SECURE DOWNLOAD : ENABLE
DID : 20208B1D87858711
Otherwise, same here. Followed all instructions like people have listed so I'm just as confused as you.
MEGAtheguy said:
Yeah my phone is in that weird teal screen that says "Downloading... Do not turn off target"
In the top right I have this
RPMB fuse blown
RPMB PROVISIONED
CURRENT BINARY : Samsung Official
FRP LOCK : OFF
KG STATUS : Checking
QUALCOMM SECUREBOOT : ENABLE
RP SWREV : B3(2,2,2,3,2) K3 S3
SECURE DOWNLOAD : ENABLE
DID : 20208B1D87858711
Otherwise, same here. Followed all instructions like people have listed so I'm just as confused as you.
Click to expand...
Click to collapse
Maybe someone with that model S9 will know more than me, you could try the patched Odin I suppose
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
*Detection* said:
Maybe someone with that model S9 will know more than me, you could try the patched Odin I suppose
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Click to expand...
Click to collapse
Stalls :/
Device Manager.
sonic65101 said:
Device Manager.
Click to expand...
Click to collapse
What about it
MEGAtheguy said:
What about it
Click to expand...
Click to collapse
You can check what driver your phone is using.
MEGAtheguy said:
Stalls :/
Click to expand...
Click to collapse
I don't know if this is any help at all but generally failing/stopping on setup connection can mean there is another program or process on your PC which is conflicting with Odin. This can happen irrespective of the type of phone model or Odin version used.
Eg: Samsung's smart switch and Odin do not play nice with each other.
Since from your screen shots Odin is seeing your phone ( therefore windows is ) you would have to see what is causing the conflict.
Some other things to try ( been mentioned in previous posts)
Plug directly into a USB 2 port on pc
Different PC ( still need Samsung drivers )
Some people have mentioned booting up in download mode then rebooting phone straight back into download mode again.
spawnlives said:
I don't know if this is any help at all but generally failing/stopping on setup connection can mean there is another program or process on your PC which is conflicting with Odin. This can happen irrespective of the type of phone model or Odin version used.
Eg: Samsung's smart switch and Odin do not play nice with each other.
Since from your screen shots Odin is seeing your phone ( therefore windows is ) you would have to see what is causing the conflict.
Some other things to try ( been mentioned in previous posts)
Plug directly into a USB 2 port on pc
Different PC ( still need Samsung drivers )
Some people have mentioned booting up in download mode then rebooting phone straight back into download mode again.
Click to expand...
Click to collapse
I've done all of that aside from trying a USB 2.0 port. I'll give it another shot tomorrow
Related
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.
Yesterday I plugged my phone with usb to the pc but it didn't recognize it, When I tried with another cable , One of the devices you connected was not recognized" this message popped, the phone was recognized day before yesterday and before that but suddenly it's unrecognized by the system. How do I fix this? I tried plugging my phone to my friend's pc but still it gives the same error,
Jexbox said:
Yesterday I plugged my phone with usb to the pc but it didn't recognize it, When I tried with another cable , One of the devices you connected was not recognized" this message popped, the phone was recognized day before yesterday and before that but suddenly it's unrecognized by the system. How do I fix this? I tried plugging my phone to my friend's pc but still it gives the same error,
Click to expand...
Click to collapse
Do you have HTC sync installed? Or have you ever had the right drivers installed on this PC? If so you can try go into device manager on windows, select the malfunction device and manually change its driver to the HTC drivers and see if that works
Sent from my HTC Desire S using Tapatalk
heavy_metal_man said:
Do you have HTC sync installed? Or have you ever had the right drivers installed on this PC? If so you can try go into device manager on windows, select the malfunction device and manually change its driver to the HTC drivers and see if that works
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Yea It used to detect my phone earlier but suddenly it has stopped, with the stock usb cable nothing gets detected, and when I try with others it pops the message that it is unrecognized.
Jexbox said:
Yea It used to detect my phone earlier but suddenly it has stopped, with the stock usb cable nothing gets detected, and when I try with others it pops the message that it is unrecognized.
Click to expand...
Click to collapse
Have you tried
Code:
adb devices
?
What does it say?
mcgi5sr2 said:
Have you tried
Code:
adb devices
?
What does it say?
Click to expand...
Click to collapse
It returns nothing
{
"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"
}
even tried to run fastboot in bootloader, It doesn't detect the phone which it used to detect previously, the phone is still in warranty but I can't give it because I can't even restore my stock backup as I won't be able to flash the stock kernel again is there any other way to return to stock?
Jexbox said:
It returns nothing
even tried to run fastboot in bootloader, It doesn't detect the phone which it used to detect previously, the phone is still in warranty but I can't give it because I can't even restore my stock backup as I won't be able to flash the stock kernel again is there any other way to return to stock?
Click to expand...
Click to collapse
OK panic not.
First see if you can test it on another computer. The HOV doesn't agree with USB3.0 so if you have any usb ports that aren't that, then try it there. Is the phone S-OFF? If so you could try and flash by putting the rom.zips on your sd-card then rebooting into recovery.
Also can you check adb with the other cables as well?
mcgi5sr2 said:
OK panic not.
First see if you can test it on another computer. The HOV doesn't agree with USB3.0 so if you have any usb ports that aren't that, then try it there. Is the phone S-OFF? If so you could try and flash by putting the rom.zips on your sd-card then rebooting into recovery.
Also can you check adb with the other cables as well?
Click to expand...
Click to collapse
I tested it on other 2 computers with 3 different cables, Adb doesn't detect my phone, The phone is S-ON, I tested it on all ports still no recognition, The phone charges through the USB but it is not recognized, I also looked at the HTC Dumlock method as I have TWRP installed, should I try that ?
Jexbox said:
I tested it on other 2 computers with 3 different cables, Adb doesn't detect my phone, The phone is S-ON, I tested it on all ports still no recognition, The phone charges through the USB but it is not recognized, I also looked at the HTC Dumlock method as I have TWRP installed, should I try that ?
Click to expand...
Click to collapse
That is very strange indeed, if it charges then it should be recognised by ADB. Are you sure your running adb from a folder it works from, are the drivers installed on the computers you tested it on?
I don't know anything about the Dumlock method so really can't advise
mcgi5sr2 said:
That is very strange indeed, if it charges then it should be recognised by ADB. Are you sure your running adb from a folder it works from, are the drivers installed on the computers you tested it on?
I don't know anything about the Dumlock method so really can't advise
Click to expand...
Click to collapse
Yea, it is strange, I was running adb for a long time on my pc and it was working and this thing has just started recently, I've read many similar posts with this strange problem but none of them give an solution to it.
Jexbox said:
Yea, it is strange, I was running adb for a long time on my pc and it was working and this thing has just started recently, I've read many similar posts with this strange problem but none of them give an solution to it.
Click to expand...
Click to collapse
Could you try it without your SD card in?
mcgi5sr2 said:
Could you try it without your SD card in?
Click to expand...
Click to collapse
Tried. still not working
Jexbox said:
Tried. still not working
Click to expand...
Click to collapse
It might be worth trying with different usb cables. If this wont help the hOV micro usb socket could be physically broken. :\
kvestas said:
It might be worth trying with different usb cables. If this wont help the hOV micro usb socket could be physically broken. :\
Click to expand...
Click to collapse
Can't tell cause the phone gets charged but it's not detected, tried at least 5-6 wires on different computers still the same
Ok another idea you could try is flashing a different rom. I am plucking at straws here though, as all our 4.2.2 roms are currently based on 1ceb0xs one anyway. Have you tried re-installing the rom from recovery?
mcgi5sr2 said:
Ok another idea you could try is flashing a different rom. I am plucking at straws here though, as all our 4.2.2 roms are currently based on 1ceb0xs one anyway. Have you tried re-installing the rom from recovery?
Click to expand...
Click to collapse
Will give it a try and report back.
Hi all,
I have a Oneplus 3 with the last update (OxygenOS 5.0.4) and I can't access to my files with an USB cable.
I try on 3 computers with differents cables, and the OTG parameter on ON but nothing works.
Drivers are normally ok.
Do you have a solution?
Best regards,
Jckbrtn
jckbrtn said:
Do you have a solution?
Click to expand...
Click to collapse
Try to turn on usb debugging in developer options
mar.ur said:
Try to turn on usb debugging in developer options
Click to expand...
Click to collapse
Hi,
Thanks but it doesn't work and I never need to do that before.
I don't understand why it doesn't work anymore.
I hadn't try nothing new on my phone.
I think I will try to reset it...
Best regards,
Jckbrtn
@jckbrtn is there connecting with pc in recovery mode ? I mean adb commands
mar.ur said:
@jckbrtn is there connecting with pc in recovery mode ? I mean adb commands
Click to expand...
Click to collapse
I just try to connect my Oneplus with USB cable like I always use to do.
ADB drivers are installed on my PC and I only have the original recovery.
I never try to root this smartphone.
With a OneplusX on LineageOS, no problem. See screenshot:
{
"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"
}
Looking at your photo, have your tried to tap the second option...?
150208 said:
Looking at your photo, have your tried to tap the second option...?
Click to expand...
Click to collapse
Picture is for my OneplusX. It works for the OneplusX on the same computer but not for the Oneplus 3.
I don't have this menu in notification.
jckbrtn said:
Picture is for my OneplusX. It works for the OneplusX on the same computer but not for the Oneplus 3.
I don't have this menu in notification.
Click to expand...
Click to collapse
Oh i see
Try developer options, if i remember it right, i believe there is a setting about USB access in OOS.
Other than that i don't know except factory reset, re-install the PC, or bad usb port (in either of phone/pc).
I have this issue once, but it because my bad usb port on my PC motherboard.
jckbrtn said:
Picture is for my OneplusX. It works for the OneplusX on the same computer but not for the Oneplus 3.
I don't have this menu in notification.
Click to expand...
Click to collapse
Go through and remove the drivers for all the one plus device then connect the 3. The drivers for the two are corrupting each other. It is a known issue with the drivers for this device. I have to reinstall the drivers on every connect and disconnect from USB.
zelendel said:
Go through and remove the drivers for all the one plus device then connect the 3. The drivers for the two are corrupting each other. It is a known issue with the drivers for this device. I have to reinstall the drivers on every connect and disconnect from USB.
Click to expand...
Click to collapse
I only have drivers for the 3. For th OneplusX with the usb, no problem.
Drivers removed but it doesn't works. I think I'll try a reset of my device in a few days to see...
I try on 3 windows computers with differents cables (also the Oneplus one), drivers, no drivers... don't know....
jckbrtn said:
I only have drivers for the 3. For th OneplusX with the usb, no problem.
Drivers removed but it doesn't works. I think I'll try a reset of my device in a few days to see...
I try on 3 windows computers with differents cables (also the Oneplus one), drivers, no drivers... don't know....
Click to expand...
Click to collapse
With the one plus devices you can never tell. It could be anything from software to hardware. Next time you connect pull a log cat this might help.
So I try a factory reset: don't work
I downgrade to oxygen 5.0.3 and 5.0.1: don't work
I try on an other laptop where I never plug my oneplus or install drivers/adb: don't work
I also try with different cables (original from oneplus include): don' work
With otg option on, usb debugging on, ... or without, don't work!
And best is I can't install LineageOS as I have no access on my PC
zelendel said:
With the one plus devices you can never tell. It could be anything from software to hardware. Next time you connect pull a log cat this might help.
Click to expand...
Click to collapse
Yes, I think it's hardware. USB-C don't work with OTG adapter (USB-C to USB and USB key).
Log cat? How to?
I just bought an used 3T and have the same problem. I have tried every possible software solution I guess I have to try to replace USB port but if it doesn't help I don't know what I'll do...
I had the same issue but a fix I found to work was when my Oneplus 3 was plugged into my computer, the dropdown notification that says "Android System" - USB charging this device can be changed to transfer files and after that option is picked, my phone is detected by my computer. Maybe this will help some of you
stingerbs said:
I had the same issue but a fix I found to work was when my Oneplus 3 was plugged into my computer, the dropdown notification that says "Android System" - USB charging this device can be changed to transfer files and after that option is picked, my phone is detected by my computer. Maybe this will help some of you
Click to expand...
Click to collapse
Problem is I don't have this menu anymore since my usbc port is not working
stingerbs said:
I had the same issue but a fix I found to work was when my Oneplus 3 was plugged into my computer, the dropdown notification that says "Android System" - USB charging this device can be changed to transfer files and after that option is picked, my phone is detected by my computer. Maybe this will help some of you
Click to expand...
Click to collapse
I'm waiting for a response of the oneplus support. My smartphone is still under warranty so I asked for a RMA.
I had to make a video of me connecting the phone to my computer to show the issue.
I also made a video with an other usbc smartphone to show that all is working.
jckbrtn said:
I'm waiting for a response of the oneplus support. My smartphone is still under warranty so I asked for a RMA.
I had to make a video of me connecting the phone to my computer to show the issue.
I also made a video with an other usbc smartphone to show that all is working.
Click to expand...
Click to collapse
So after 2 weeks of mail contact, my smartphone was sent from Belgium to Poland monday.
I received my repaired smartphone on wednesday.
Technical support very good! Mail support very complicated...
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
Okay, this is getting kind of ridiculous. I cannot get any computer to see the 9 pro via ADB devices.
This is my 4th Oneplus phone I currently own. So I know what I'm doing. All my other phones have bootloaders unlocked and rooted. No issues, until now. I just bought this one. Been waiting for the unlock bin file because it's the T-Mobile variant, but found out that I don't need the bin file to unlock the bootloader, but need ADB to see it !
Fastboot devices will see the phone but not ADB. I even just reformatted my laptop and started from scratch. Followed all of the guides I could find, and I STILL cannot get ADB to see this phone. Why is this phone different ?
Anyways. Anyone have any ideas cause I'm out of them.
Install all the proper drivers. How are you connecting the OnePlus 9 pro to your PC?
Are you using windows or linux?
If you are using linux, I can't help you out.
Enable USB debugging via developer options and go to USB configuration:
Select usb debugging as the default.
When you want to transfer files, select file transfer.
Also, do you have access to another usb cable?
rogerrulez said:
Okay, this is getting kind of ridiculous. I cannot get any computer to see the 9 pro via ADB devices.
This is my 4th Oneplus phone I currently own. So I know what I'm doing. All my other phones have bootloaders unlocked and rooted. No issues, until now. I just bought this one. Been waiting for the unlock bin file because it's the T-Mobile variant, but found out that I don't need the bin file to unlock the bootloader, but need ADB to see it !
Fastboot devices will see the phone but not ADB. I even just reformatted my laptop and started from scratch. Followed all of the guides I could find, and I STILL cannot get ADB to see this phone. Why is this phone different ?
Anyways. Anyone have any ideas cause I'm out of them.
Click to expand...
Click to collapse
Fix: ADB Devices Not Found
With smartphones being present everywhere, the need for transferring files from your personal computer to your smartphone and vice versa arises. Not only
appuals.com
luarpc said:
Fix: ADB Devices Not Found
With smartphones being present everywhere, the need for transferring files from your personal computer to your smartphone and vice versa arises. Not only
appuals.com
Click to expand...
Click to collapse
Hi and thanks for the link. I have tried all of that except the universal drivers which I just installed. No difference. When the phone is booted it shows up as USB composite device. And when I try to update the driver, even after disabling driver verification, it will accept the driver but will show a small yellow icon over the newly installed driver.
In bootloader mode ADB does not see the phone but fastboot does. It looks like this could be a driver issue but the only Oneplus drivers I've found are from 2012.
rogerrulez said:
Hi and thanks for the link. I have tried all of that except the universal drivers which I just installed. No difference. When the phone is booted it shows up as USB composite device. And when I try to update the driver, even after disabling driver verification, it will accept the driver but will show a small yellow icon over the newly installed driver.
In bootloader mode ADB does not see the phone but fastboot does. It looks like this could be a driver issue but the only Oneplus drivers I've found are from 2012.
Click to expand...
Click to collapse
Disable Driver Signature Enforcement in windows - google this
then reinstall oneplus 9 drivers from manufacturer
OnePlus messed up the signature of their drivers for the Oneplus 9 pro and windows doesn't install it properly.
immortalwon said:
Disable Driver Signature Enforcement in windows - google this
then reinstall oneplus 9 drivers from manufacturer
OnePlus messed up the signature of their drivers for the Oneplus 9 pro and windows doesn't install it properly.
Click to expand...
Click to collapse
Yes I did that. It's currently in that state of driver verification is currently disabled. I can change the driver right now with no problem. But it's still the same result. Are there newer drivers than from what I found ?
Thanks
rogerrulez said:
Yes I did that. It's currently in that state of driver verification is currently disabled. I can change the driver right now with no problem. But it's still the same result. Are there newer drivers than from what I found ?
Thanks
Click to expand...
Click to collapse
Hi,
Try this drivers.
OnePlus USB Drivers | Official
Download the latest version of OnePlus USB Driver for your OnePlus smartphone. OnePlus USB Drivers helps your OnePlus smartphone to communicate properly with your computer.
oneplususbdrivers.com
{
"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"
}
rogerrulez said:
Yes I did that. It's currently in that state of driver verification is currently disabled. I can change the driver right now with no problem. But it's still the same result. Are there newer drivers than from what I found ?
Thanks
Click to expand...
Click to collapse
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb-c connector port.
immortalwon said:
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb connector port.
Click to expand...
Click to collapse
I have always used a regular USB a to c charge/sync cable. No USB c port on laptop.
immortalwon said:
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb-c connector port.
Click to expand...
Click to collapse
It's connected with a USB A - C cable. In device manager it says kedacom USB device. After installing the drivers from the link @TheGhost1951 sent me. It now set itself up as a Universal Serial Bus Device - ADB interface.
In bootloader mode it shows up in device manager with whatever driver I had chosen from before. ADB still can't see the device on either my desktop or newly formatted laptop.
So a pic of the device manager will show basically that. Whatever driver I have chosen. But any driver I chose, ADB still won't find the phone. Regardless what I do on either computer.
luarpc said:
Hi,
Try this drivers.
OnePlus USB Drivers | Official
Download the latest version of OnePlus USB Driver for your OnePlus smartphone. OnePlus USB Drivers helps your OnePlus smartphone to communicate properly with your computer.
oneplususbdrivers.com
Click to expand...
Click to collapse
Thanks for the link. That was perfect. I had seen that website during a search yesterday, but I didn't think at the time if it was real and could be trusted.
TheGhost1951 said:
I have always used a regular USB a to c charge/sync cable. No USB c port on laptop.
Click to expand...
Click to collapse
And that's what I'm using. I've tried 3 different cables. Even just opened a brand new one. A quality cable.
immortalwon said:
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb-c connector port.
Click to expand...
Click to collapse
Oh. And after installing the new drivers. When the phone is booted ADB can see the phone. But not in bootloader mode. Or down mode.
rogerrulez said:
Oh. And after installing the new drivers. When the phone is booted ADB can see the phone. But not in bootloader mode. Or down mode.
Click to expand...
Click to collapse
I don't have any free slots for an additional card in my computer. But is that what it's needing you think ?
rogerrulez said:
I don't have any free slots for an additional card in my computer. But is that what it's needing you think ?
Click to expand...
Click to collapse
Nah, it is a matter of getting the right cable and drivers....it has never been that completed for me even with a Qualcomm crashdump!
TheGhost1951 said:
Nah, it is a matter of getting the right cable and drivers....it has never been that completed for me even with a Qualcomm crashdump!
Click to expand...
Click to collapse
Can you tell me what should be the proper name of the driver that should be installed ?
And do you think that this might be a hardware issue ?
Also, I've noticed that debugging is randomly getting turned off.
rogerrulez said:
Can you tell me what should be the proper name of the driver that should be installed ?
And do you think that this might be a hardware issue ?
Also, I've noticed that debugging is randomly getting turned off.
Click to expand...
Click to collapse
If driver is correct, your device should show up in device manager on PC as a port with description as 9008.....ex:Qualcomm USB hub 9008 or something similar. Google latest Qualcomm USB drivers... Make sure driver signing is turned off on PC, there should be a watermark in bottom right hand corner stating test mode. One the correct drivers are installed, reboot PC and then you are ready to start the MSM tool process.
immortalwon said:
Can you show me a picture of your device manager? Also how is your device connected to pc - Direct usb-c to usb-c slot or adapter? If so, I recommend using a pci-slot based usb-c connector port.
Click to expand...
Click to collapse
It's connected with a USB A - C cable.
TheGhost1951 said:
If driver is correct, your device should show up in device manager on PC as a port with description as 9008.....ex:Qualcomm USB hub 9008 or something similar. Google latest Qualcomm USB drivers... Make sure driver signing is turned off on PC, there should be a watermark in bottom right hand corner stating test mode. One the correct drivers are installed, reboot PC and then you are ready to start the MSM tool process.
Click to expand...
Click to collapse
Okay thanks for that info. But I have yet to see that qualcomm port yet on either of my computers. No matter what I do it doesn't seem to change anything. Certainly nothing near having a qualcomm port in device manager.
I would be willing to completely reformat my laptop and install the recommended drivers from this post if I knew it would definitely work.
But I'm starting to think at this point that this might be a hardware issue.