Develop Bugs

I Guess I Discovered a New Form of Hard Bricking on my Device???

I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.

jasonstackhouse said:
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
Click to expand...
Click to collapse
I would try a different cable as this device is very finicky; that solved my issue of the computer not recognizing the phone.

Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?

Az Biker said:
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Click to expand...
Click to collapse
That would be nice if that were the problem, but unfortunalty I do not think it is. For example, when the issues first began, before I did the factory reset on the device, windows would pop up a message that said unknown device, and failure to connect. After the factory reset in TWRP the computer gave up all together in recognizing the phone. Another sign it was likely not a hardware failure was when the device was on and i was attempting to connect the otg usb to the phone it would give me some weird options. With android P the options were, allow this device to control the usb, or allow the USB to control the USB. that made no sense to me since why would i want the the USB to have any control, it couldnt do anything its not a computer its only a storage device. However, even though I had file transfer selected in developer options, it would not allow this connection. The options were all greyed out and it would not allow the pixel to have control over the usb device.
As for USB cords I have used without fail the google issued USB cord that came with the Pixel 1 xl, It has never faile me or had any issues. It is still fully functional as I was able to use it to connect my girls note 8 to my computer for file transfers and all other things my phone is not doing anymore.
I reached out to google and explained the situation to them, after i told them I was on Dev preview beta and they verified this to be true they told me this is likely a hardware failure and offered to replace the device. I am now waiting on the new device to be sent to me, however still cant accept that i cant recover the current device with an unlocked bootloader, TWRP installed, and access to fastboot/bootloader screen. I have seriously bricked phones before as in they would not even turn on and I was able to get them back up and running, this would be my first ever device I could not recover and what makes it worse is that it actually has TWRP installed and powers on and off just fine.

Sorry for the obvious question: Do you have the latest drivers? I don't have the drivers set to the whole system (Windows), so if I don't CD into my fastboot folder, I can't do anything because the system wide drivers aren't current. Don't know if that could be your issue?
I'm too lazy to fix the PATH of my drivers ¯\_(ツ)_/¯

I had an issue similar to this. I was trying to hook up a USB c to Ethernet adapter. It worked fine on April's patch but after I flashed Mays the phone wouldn't recognize it. After I plugged it in my phone rebooted and I no longer had access to developer options and it wouldn't read any usb device. Luckily I had a TWRP backup on my device. Once I flashed the backup which was only about a week old everything worked again. I haven't tried using the adapter again. I think something in the data partition got corrupted. I tried just restoring the boot and system partition and that didn't fix it. Try doing an advance wipe and formatting the data partition. That might get you back up and going.

have we even seen a bricked device yet?

twiz0r said:
have we even seen a bricked device yet?
Click to expand...
Click to collapse
I didn't think it was possible, I still dont understand how this is happening. For the other responses above, I have all the drivers up to date, and I already formatted data, wiped everything. At this point I would like to see if there is anyway to delete TWRP recovery from the device, anything, I have no OS on the device, but for some reason still have TWRP on both A and B.
I almost dont want to give the phone back to Google because I want to figure out what happened and how to fix it, its definitely not broken/bricked like you see when someone flashes the wrong files to a device, it just has no USB connection capabilities which in-turn have rendered the device useless.
When I had Samsung phones if you bricked a device to the point it doesn't even turn on correctly you could always save it still using ODIN. Its weird that the google flagship device and software doesn't have its own proprietary flash software like Samsung, LG and HTC, we just have adb/fastboot, I feel like if we did, i may be able to get this thing started again.

have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image

Pyr0x64 said:
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Click to expand...
Click to collapse
I can't access the play store on the device in it's state. I do have access to fastboot. I can boot the phone to fastboot, and into TWRP, only problem is the phone doesn't communicate with the computer in either state. If the pixel had a SD card slot I would just load up a recovery but unfortunately we don't have that luxury

What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs

Triscuit said:
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
The cable is not the issue, I confirmed this by testing all my cables with the new device that I just received for my warranty exchange. I also tried my luck with Linux, after a complicated installation on my computer I was able to have Linux actually detect the device (partially) when the device was plugged in at splash screen I got nothing, at fastboot/bootloader screen nothing, but once the phone booted into TWRP it came up as AOSP device, when I attempted clicking on the AOSP device being detected by Linux an error message popped up telling me mtp or midi error, not sure for sure what one it said. Either way I couldn't connect for any transfer of information, I tried adb sideload and that failed as well.
This has been an experience for the memory books, glad that old device is gone and I'm back up and running on a working phone. No more beta testing for me, I'll be ready for Android P when they get it out of beta, I don't have the time or patience to deal with any more warranty exchanges.

USB device not recognized - not recognized by computer in fastboot or booted up

So it looks like my USB C port may be fried. Had recently flashed Resurrection Remix and had used a usb thumb drive connected through usb a to c adapter that comes with phone to restore apps from titanium backup and copy files over no problem. Went to use the thumb drive again a while later and noticed that the prompt only came up to charge the device and choosing file transfer option did nothing. Rebooted to TWRP to backup and flash a different rom and noticed that my thumb drive was no longer recognized there any more either. Now when I connect to my PC with same cord I have always used, it always comes up with the windows error message saying it's not recognized and has malfunctioned. Have tried fastboot mode and booted up and always same message. Fastboot will not see the phone. I really don't think it's a driver issue at this point. I actually already have a replacement device coming for different issue and I'm wondering if I should try to flash stock June image through TWRP so at least it's on stock software when I send it in even if it's unlocked. Oh yeah and the device does currently charge still. Thanks for any help or comments as I probably only have one shot at this.

Reechings said:
So it looks like my USB C port may be fried. Had recently flashed Resurrection Remix and had used a usb thumb drive connected through usb a to c adapter that comes with phone to restore apps from titanium backup and copy files over no problem. Went to use the thumb drive again a while later and noticed that the prompt only came up to charge the device and choosing file transfer option did nothing. Rebooted to TWRP to backup and flash a different rom and noticed that my thumb drive was no longer recognized there any more either. Now when I connect to my PC with same cord I have always used, it always comes up with the windows error message saying it's not recognized and has malfunctioned. Have tried fastboot mode and booted up and always same message. Fastboot will not see the phone. I really don't think it's a driver issue at this point. I actually already have a replacement device coming for different issue and I'm wondering if I should try to flash stock June image through TWRP so at least it's on stock software when I send it in even if it's unlocked. Oh yeah and the device does currently charge still. Thanks for any help or comments as I probably only have one shot at this.
Click to expand...
Click to collapse
Just a shot in the dark, but when you plug in the cord to the phone does it snap in fully? I work in a very dusty environment and have to clean my port out with a tiny wire bent like a hook every few weeks or the plug does not stay in. It may very well not be your problem but just a thought.

CyberpodS2 said:
Just a shot in the dark, but when you plug in the cord to the phone does it snap in fully? I work in a very dusty environment and have to clean my port out with a tiny wire bent like a hook every few weeks or the plug does not stay in. It may very well not be your problem but just a thought.
Click to expand...
Click to collapse
Thanks, I wish it was that simple but no luck.

Reechings said:
Thanks, I wish it was that simple but no luck.
Click to expand...
Click to collapse
RMA that thing if you've tried everything possible. Which, it sounds like you have ?

Badger50 said:
RMA that thing if you've tried everything possible. Which, it sounds like you have ?
Click to expand...
Click to collapse
RMA is en route and my USB just randomly started working again lol

Reechings said:
RMA is en route and my USB just randomly started working again lol
Click to expand...
Click to collapse
Doesn't surprise me a bit! Damn gremlins! ?
https://forum.xda-developers.com/pi...aimen-flash-kernel-1-00-t3702057/post76871322

Phone not recognized by any computer

Not sure exactly when this started, but went to try to sideload the P update and can't get any PC to recognize my phone. Tried different computers and different cables. Won't even pop up on the phone to transfer files. So not an adb/fastboot problem. Last time I remember plugging into a PC and working was when I ran an adb command to enable the Hide Nav Bar app. Possible my USB port crapped out? Charges and fast charges just fine.
Any insight is welcome.
edit: Phone reads flash drive connected through USB-C adapter

1. Make sure USB Debugging is enabled
2. Try all USB ports available on computer
3. Try all USB cables available (OEM cable is always the best choice)
3. Revoke USB permissions
4. Uninstall & reinstall adb drivers, then reboot computer
If you have access to another Android device, plug it in and see if the computer recognizes that one. If it does, then the problem is your device, not the adb environment.

My phone with thru that. I had to unroot, re-lock bootloader, and i sent the device back to google. Since it was still under warranty and the issue was that the hardware wasnt allowing the device to be read via andriod auto or any computer. Not even my headphone dongle worked.

TheKevinMaestre said:
My phone with thru that. I had to unroot, re-lock bootloader, and i sent the device back to google. Since it was still under warranty and the issue was that the hardware wasnt allowing the device to be read via andriod auto or any computer. Not even my headphone dongle worked.
Click to expand...
Click to collapse
Can you do this through terminal app?

i have the same problem but even my fastboot mode isn't reconized. i can't even boot the phone. Tried unistalling and reinstalling adb fastboot phone drivers but it didn't work. I even tried 4 different cable, usb c to c, usb c to a... nothing working)!!!! I don't know what to do... and it's the first time in 10 years of modding. My devices show the red triangle.... will google refurb it if they find out that's modded?

Balino said:
i have the same problem but even my fastboot mode isn't reconized. i can't even boot the phone. Tried unistalling and reinstalling adb fastboot phone drivers but it didn't work. I even tried 4 different cable, usb c to c, usb c to a... nothing working)!!!! I don't know what to do... and it's the first time in 10 years of modding. My devices show the red triangle.... will google refurb it if they find out that's modded?
Click to expand...
Click to collapse
if you are at the red triangle, you aren't in recovery, yet.
You'll need to hold the power button and tap the up volume key to get to recovery.

When my USB port recently crapped out, one of the symptoms was the inability to connect to a computer. Still not sure if it was hardware or something deep in the filesystem. A factory reset from recovery didn't fix it, but an RMA replacement under warranty from Google did.
Sent from my Pixel 2 XL using Tapatalk

Happened to my device too 3 weeks ago... the phone would sometimes charge, sometimes wouldn't at all, and wasn't detected anymore by my computers. Android Auto dead. USB-C -> minijack dead.
Had to RMA it, it was a problem with the USB controller or something

I had this issue as well I was able to fix by turning on and off USB debugging, still RMA'd it as I don't fully trust the port anymore. Not sure what happened, it was working fine on the way to work, on the way home I plugged in the USB for Android auto and got nothing.

This just happened to me too...think they are going to RMA but the phone is unlocked and I am not able to relock it anyway without connecting...
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
rajendra82 said:
When my USB port recently crapped out, one of the symptoms was the inability to connect to a computer. Still not sure if it was hardware or something deep in the filesystem. A factory reset from recovery didn't fix it, but an RMA replacement under warranty from Google did.
Click to expand...
Click to collapse
Was yours unlocked. I can't relock my phone cuz I can't connect to anything...I'm supposed to send in to Google but worried they won't honor warranty now...

My phone bootloader was not unlocked. I don't believe Google denies warranty coverage for unlocked phones, if the failure is not caused by it. They certainly never asked me any questions about it.
Sent from my Pixel 2 XL using Tapatalk

Help me recover OP3 data

Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you

manto02 said:
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
Click to expand...
Click to collapse
Most likely the connector has become loose (since you have not said anything about the screen being broken) and you can try to reconnect it by yourself.
Another alternative is to see if adb is working and your PC is authorised. If so, you can use the 'adb pull /sdcard' command to copy your data to the PC.
Alternately, search with Google since I remember reading about a method to mirror your screen and then using the mouse to enable whatever you want.

tnsmani said:
Most likely the connector has become loose (since you have not said anything about the screen being broken) and you can try to reconnect it by yourself.
Another alternative is to see if adb is working and your PC is authorised. If so, you can use the 'adb pull /sdcard' command to copy your data to the PC.
Alternately, search with Google since I remember reading about a method to mirror your screen and then using the mouse to enable whatever you want.
Click to expand...
Click to collapse
I'll check the connector but the screen has some cracks (tho i've seen screens in worse condition then mine work).
And i can't use the mouse because OTG is not on, on other phones you don't need to give permission to use OTG but on mine you have to,

manto02 said:
I'll check the connector but the screen has some cracks (tho i've seen screens in worse condition then mine work).
And i can't use the mouse because OTG is not on, on other phones you don't need to give permission to use OTG but on mine you have to,
Click to expand...
Click to collapse
What about adb? That is the easiest.
I am not talking about connecting the mouse to the phone through OTG. I am talking about using the PC's mouse to manipulate the cursor to the point where you want it on your PC's screen where your mobile screen is mirrored.

tnsmani said:
What about adb? That is the easiest.
I am not talking about connecting the mouse to the phone through OTG. I am talking about using the PC's mouse to manipulate the cursor to the point where you want it on your PC's screen where your mobile screen is mirrored.
Click to expand...
Click to collapse
I think you are referring to Vysor, but i can't use it with debugg off again. Edit: I see that there are other apps like that but for most of them you have to install them on the phone, i'll search a bit more tho.
As for ADB i tried before with another phone with debug off and adb doesn't see the phone, i'll try with my broken phone but i don't think it will be different.

manto02 said:
I think you are referring to Vysor, but i can't use it with debugg off again. Edit: I see that there are other apps like that but for most of them you have to install them on the phone, i'll search a bit more tho.
As for ADB i tried before with another phone with debug off and adb doesn't see the phone, i'll try with my broken phone but i don't think it will be different.
Click to expand...
Click to collapse
Just now, I switched off USB debugging in my OP3 and connected it to the Laptop. While the command 'adb devices' does not find the phone, as soon as it is connected, it shows up as a storage device and I can open it and copy data. I think that for this to work, you should have enabled MTP option for file transfer.
Check this on your phone.
EDIT: Check THIS as there seems to be a way though I am not sure that it works on current Android versions since the file locations may be different. Read till the end.

My phone goes in charging mode when connected to pc, and pc doesn't see it.
Did you do that through recovery mode?

manto02 said:
My phone goes in charging mode when connected to pc, and pc doesn't see it.
Did you do that through recovery mode?
Click to expand...
Click to collapse
No. Tried it while booted.
Now I tried on recovery mode. Still I get it as a storage device and I can copy data.
So most probably your phone is stuck on charging and not on MTP.

tnsmani said:
No. Tried it while booted.
Now I tried on recovery mode. Still I get it as a storage device and I can copy data.
So most probably your phone is stuck on charging and not on MTP.
Click to expand...
Click to collapse
I believe so, every time I connected it to pc i had to switch manually from charging to recovery.
I guess my best solution is to buy a screen replacement and repair it myself

manto02 said:
I believe so, every time I connected it to pc i had to switch manually from charging to recovery.
I guess my best solution is to buy a screen replacement and repair it myself
Click to expand...
Click to collapse
Have you tried fastboot flash twrp recovery and then fastboot reboot to recovery

You can try usb c to hdmi adapter , connect to a monitor or tv.
I am not sure but worth trying!!!

manto02 said:
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
Click to expand...
Click to collapse
From what i can remember, the recovery mode, accessible from the fastboot menu, has a usb access mode.
If worst comes to worst though, i personally have replaced the screen on my OP3, and its not as difficult as it seems or is made out to be. Took me max 4 hrs.

Question Phone not connecting via USB

My first Poco F3 is completely unlocked and running a custom rom, still able to connect to PC even now.
I have a second Poco F3 that I was able to originally connect to my PC to debloat, hadn't needed to connect it to a PC till now. Today was the day I could unlock it but when I connect it via USB cable, original or otherwise, no usb options appear on phone and nothing shows on PC. I can use the same cable on my first Poco F3 and everything works fine. I've tried multiple cables, reinstalling drivers, restarting phone and PC, trying a different PC, enabling debugging tools, etc.
Nothing shows in "My Computer"
Nothing shows in Device Manager
No usb options on phone (default is set to File Transfer)
Nothing shows in CMD with "adb devices"
Charging still works
Is there anything I can do to at the very least unlock the bootloader? Or is this not fixable?

long shot... check the usb C port for dirt/dust/fluff blocking connection...

Most probably u debloated an app responsable for media transfer. If u can, revert what u debloated.

Alin45 said:
Most probably u debloated an app responsable for media transfer. If u can, revert what u debloated.
Click to expand...
Click to collapse
Did a factory reset thinking that may have been the case, still no good.
Tried cleaning out the port and still no good either

I still think it's Windows. Please can you try putting Ubuntu (or another Linux distro) on a USB, booting from that, installing platform tools (ADB/fastboot etc) and then running ADB devices. Windows is very finiky sometimes.
Edit: when you plug in your phone to the PC do you get a notification saying charging? Or is there no notification? Also does it start charging the phone?

There is a delay before it begins charging and the charging animation plays but yes it does. But then there is no usb notification. Will try ubuntu and report back

Booting into Ubuntu, before installing platform tools the first phone that I knew worked showed up and showed up in adb devices when platform tools was used. The second still didn't show up, exactly the same as on windows

Try downloading the installed stock miui rom from the update menu in the miui update menu and re-install it on the phone

Unfortunately reinstalling latest package didn't help

Can't think of anything else to suggest. Sorry

If the usb connection continues to be nonexistent, is there any way to at least unlock the bootloader without using the Xiaomi Unlock tool on the PC?

Are you sure the USB cable you're using support transfert file?

Cjayy said:
If the usb connection continues to be nonexistent, is there any way to at least unlock the bootloader without using the Xiaomi Unlock tool on the PC?
Click to expand...
Click to collapse
Nope

Hmmmmm.....strange! I'm running out of ideas....try different USB ports on PC. Maybe it's a faulty USB-C port on phone after all.

do you have a type c usb-otg?
If yes then see if it is detected by the phone

X0PIRAT3 said:
Are you sure the USB cable you're using support transfert file?
Click to expand...
Click to collapse
Yes. Used 4 different cables, 1 of which is the cable that comes with the phone. None work on this phone but do on the first phone.
Alin45 said:
Hmmmmm.....strange! I'm running out of ideas....try different USB ports on PC. Maybe it's a faulty USB-C port on phone after all.
Click to expand...
Click to collapse
Tried different ports across 2 PCs. I'm starting to think it is a faulty port, though it worked fine a week ago.
arifqur said:
do you have a type c usb-otg?
If yes then see if it is detected by the phone
Click to expand...
Click to collapse
I honestly don't know if any of my cables are usb-otg, how would I check?

Try to use this version of Mi FLash Tool (only for drivers) : https://xiaomiflashtool.com/download/xiaomi-flash-tool-20210226
Extract and launch the executable then drivers install

Something like this. You can plug in any usb stick and see if it is detected. Another way to check whether the port on the phone is working for data as well

X0PIRAT3 said:
Try to use this version of Mi FLash Tool (only for drivers) : https://xiaomiflashtool.com/download/xiaomi-flash-tool-20210226
Extract and launch the executable then drivers install
Click to expand...
Click to collapse
Tried this and still no good.
arifqur said:
Something like this. You can plug in any usb stick and see if it is detected. Another way to check whether the port on the phone is working for data as well
Click to expand...
Click to collapse
I don't have anything like this but that reminded me of the usb-c to headphone adapter and that also doesn't work. Sound just plays out of the speakers.
Trying with Android Auto in the car, the car doesn't register a device connecting at all either.
Either the data transfer portion is somehow disabled on the device itself (which I would love to know how to enable it again if that's the case) or it's a damaged usb port. Just strange that it worked a week ago.
Something I forgot to mention, when I went to unlock the bootloader yesterday the phone did not show up anywhere except for in the ADBFastbootTools to debloat the software as a OnePlus device but then never showed up again.

Cjayy said:
Tried this and still no good.
I don't have anything like this but that reminded me of the usb-c to headphone adapter and that also doesn't work. Sound just plays out of the speakers.
Trying with Android Auto in the car, the car doesn't register a device connecting at all either.
Either the data transfer portion is somehow disabled on the device itself (which I would love to know how to enable it again if that's the case) or it's a damaged usb port. Just strange that it worked a week ago.
Something I forgot to mention, when I went to unlock the bootloader yesterday the phone did not show up anywhere except for in the ADBFastbootTools to debloat the software as a OnePlus device but then never showed up again.
Click to expand...
Click to collapse
I have the same problem, did you solve it ? I replaced the usb board of the phone, still not working.