I am attempting to diagnose some issues that I have been encountering. My phone was in the shop as the battery was being replaced. Before repair I did a data dump on e/os 3.5. Data connection was fine. On return of the device applied update to e/os 3.6 and data via USB has been unavailable (only charge)
Before I take the phone back to the shop I wanted to inquire if this might be a know hardware issue that has occurred with other users on upgrading the operating system recently.
The default situation is that you get a notification when you connect a live USB cable and you give permission for data to that PC. If you miss the notification is it found in Notification history?
Thanks for your reply aibd.
Sadly, this is a hardware error. There are no notifications in the history - USB data is not working. I get a charge from the PC that I plug into but that is all.
I have tried plugging the phone into three computers - a Linux mint laptop, a Linux mint desktop and a windows 7 computer. None of them display the phone even though it is set to allow USB connections.
I am becoming more convinced that the repair shop shorted the capacitors on the USB circuit when they changed the battery but wanted to ask the community in case this might have been a software issue first.
In case not all devices are the same. Perhaps open Developer options and change Default USB configuration to file transfer.
Ofc, contamination in the USB port could cause this sort of issue too.
I went to the shop yesterday and we did some testing. The first thing he did was clean the USB port. It did not work.
Another thing that was interesting was that when a device is connected via USB it is not possible to switch between control of the USB. He was surprised when each time it was attempted, the message came back âcouldnât switchâ.
This whole episode reminds me of my work as an IT professional over a decade ago. If there were hardware issues due to a replacement that we ordered, the entire system could go crazy. One part of the puzzle can cause driver instability. It can be incredibly frustrating.
One could search the forum for âcouldnât switchâ. It happens when the the âauthorisationâ is not given at the earlier mentioned Notification.
The reason for returning with a comment is that while your problem looks like hardware for sure ⌠many users still encounter this happening.
Did you already test the USB in Recovery?
Boot to e-recovery > Advanced > Enable ADB is expected to lift the same bar as âAuthoriseâ.
I booted to recovery. There was no change in the phoneâs behaviour. The USB is dead.
It has been malfunctioning more since then. âI/o errorâs and Bluetooth has stopped functioning. The phone is fried. Was thinking of buying a spares or repairs with a cracked screen and doing a swap to repair this phone but life is too short.
In the meantime I have bought another phone to use as my day-to-day device.
Thanks again for assisting me with my queries while I was troubleshooting my issues. This case is now closed.
A lesson that I have learned - when the battery fails, do not bother taking it to a shop. Itâs a waste of money. [EDIT - I have just purchased a pixel 5 with a broken screen for ÂŁ25. I will swap that phoneâs body with my working screen and attempt to reprogram the device. As with my experience working in computer repairs, if you want something doing properly, you have to do it yourself, it seems]
