I've unlocked successfully my Mi 9 Lite and installed TWRP and then Lineage 16.0. It worked well for some weeks, but now I cannot get any connection via USB to a computer. I've tried Windows and Linux machines, tried different cables and connected the phone directly to the PC without any USB-Hub. The phone only shows that it is charging, but doesn't display the message to select the connection-type.
First I thought it was only a setting, which I changed, but one thing worries me. Even when booted into fastboot, "fastboot devices" didn't show anything.
did you try a different cable?
Did USB work at any time after you flashed TWRP? It's possible you somehow did something wrong and messed up the USB driver.
As a last resort, you can try flashing stock ROM and start over fresh.
I don't know what I did, but USB is working again.
I think that the problem was the silicone-case. It prevents that some USB-C-plugs will not have full contact. The original USB-plug is small enough to fit in the cutout of the silicone case.
Related
Hi guys, hoping someone can help ?
As you see from the title, my HTC One fails to connect to the computer, Here's what ive done to try and remedie the problem.
Removed and clean installed latest HTC Sync and drivers
removed SDK and ADB, updated
rebooted phone
switched on and off
tried several roms
tried 3 different usb cables
tried 5 different usb ports
tried 2 different PC's
My phone sounds like it tries to connect to the pc - with the typical windows noise, then disconnects almost immediaetly, then reconnects then just keeps doing that, my pc comes up with installing drivers, then fails to instal drivers, saying phone not connected, once ive tried this once the phone need to be rebooted before it will attemp to connect to the pc again ---- but fails again
software wise the phone runs perfectly , other than the usb connection problem and charge problem with pc.
The phone charges first time, every time with all my usb cables and htc chargers
im trying to downgrade or reflash hboot 1.55000, just incase this has somehow went corrupt on the usb commands side, but without adb ect it seems almost impossible,
have any of you guys experienced anything like this or could offer solid ideas on how to re-flash hboot from the file located on my phone ???
all help appreciated
running ardh 13.4/22.0, hboot 1.55, cid = supercid, unlocked, s-off
I would simply go back to stock and return via shop in uk - to see if i could get a replacement, but getting there seems impossible - if i can simply get the pc usb problem sorted - all will be fine
dayze0 said:
Hi guys, hoping someone can help ?
As you see from the title, my HTC One fails to connect to the computer, Here's what ive done to try and remedie the problem.
Removed and clean installed latest HTC Sync and drivers
removed SDK and ADB, updated
rebooted phone
switched on and off
tried several roms
tried 3 different usb cables
tried 5 different usb ports
tried 2 different PC's
My phone sounds like it tries to connect to the pc - with the typical windows noise, then disconnects almost immediaetly, then reconnects then just keeps doing that, my pc comes up with installing drivers, then fails to instal drivers, saying phone not connected, once ive tried this once the phone need to be rebooted before it will attemp to connect to the pc again ---- but fails again
software wise the phone runs perfectly , other than the usb connection problem and charge problem with pc.
The phone charges first time, every time with all my usb cables and htc chargers
im trying to downgrade or reflash hboot 1.55000, just incase this has somehow went corrupt on the usb commands side, but without adb ect it seems almost impossible,
have any of you guys experienced anything like this or could offer solid ideas on how to re-flash hboot from the file located on my phone ???
all help appreciated
running ardh 13.4/22.0, hboot 1.55, cid = supercid, unlocked, s-off
I would simply go back to stock and return via shop in uk - to see if i could get a replacement, but getting there seems impossible - if i can simply get the pc usb problem sorted - all will be fine
Click to expand...
Click to collapse
Are the chargers working fine? or are they giving you intermittent charge/no-charge cycles as well? in which case it could be your USB socket is damaged or dirty, try cleaning it with a compressed air tank (or whatever it's called )
Are you also facing the problem in bootloader mode (ie fastboot)?
hmm, will give the usb socket on my phone a clean. Im charging completley fine with chargers and usb cables from mains, when i install htc sync(latest) it installs no problems, then i plug phone into pc, the usb connected appears on phone and then disappears almost imediaetly, the pc sees ive plugged something in and straight away tries to instal drivers - but then comes up with drivers were no installed correctly, also then the phone fails to charge from pc, if i reboot phone - and plug in it will run through the same install cycle again , as described above., basically all drivers fail to install when i plug phone in, its like the phone connects then instantly disconnects.
I ll clean port and post back, could make a difference if a pin has a high resistance contact , thx for info will give it a go
I recently tried to install PureNexus 7.1.2 along with the latest version of GApps 20170610. There seems to be some sort of conflict with that version of Google Play Services that prevents my device from completing setup. Without completing setup, I'm not able to do anything with the phone.
In an attempt to save myself, I want to go back to the older version of the ROM and GApps that worked, but first they need downloaded. In the past, I could go into TWRP and mount my device to my PC and transfer the files I needed to install. Now, Windows is showing my device as Unknown USB Device (Device Descriptor Request Failed). Going through every thread I could find about updating drivers, etc, it still does not work. This used to work just fine in the past on the same PC (Windows 10).
Both adb and fastboot don't seem to work either. There is no device found. When I boot the phone into Bootloader mode and plug in the USB cable, it shows Transfer Mode: USB Connected but running fastboot on the PC still can't find anything.
I am not sure how else to go about getting the necessary files on the device to flash them.
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
tristanlee85 said:
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
Click to expand...
Click to collapse
It could be just a dirty usb port.
Where's answers
ktmom said:
It could be just a dirty usb port.
Click to expand...
Click to collapse
Unfortunately I do not think that is the case. I have used a number of different means to clean the connection with rubbing alcohol and electrical terminal cleaner, small utensils to get in there and clean the contacts, but no luck. I am to the point now where the phone won't boot up the OS. I can get into TWRP and the Bootloader, but from there I have no way to transfer files to the device.
Bluetooth was my option before, but that is when the device would boot. There's no way to enable BT from recovery right? I am trying to reset the phone back to stock to trade it in to Google, but I am afraid I am going to be out $100 since it seems to be as good as dead now.
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
No big deal right? I mean sure, I didn't make a back up first (Mistake #2) but it shouldn't matter because I can just go into twrp and factory reset and reflash everything.
So off I went to copy over the zips to my phone -- went ahead and wiped everything (mistake #3) and then opened up windows explorer to copy over the zips. Turned out my computer couldn't see my phone.
I tried mounting and unmounting and installing and uninstalling drivers. Moving over to my other computer (linux mint) messing around with adb sideloads, and lastly tried using OTG. Turned out my computer just couldn't register my phone at all with adb.
So then I switched to fastboot -- at the very least I should be able to reflash stock and then root and then install custom stuf, right? But I couldn't get my phone to even register on windows or linux with driver changes using fastboot!
I was pretty upset at this point (still am, admittedly).
In fastboot mode whenever I plug in my phone my computer doesn't even bat an eye, and my phone just says it's waiting for a data cable connection. Windows will register it after a while as a "code 43: Windows has stopped this device because it has reported problems" after a while but I still wasn't able to get the right drivers to register the device. Doesn't even show up in lsusb in linux.
Wondering now if maybe when the device was alive I forgot to enable adb debugging first or maybe it doesn't register because it was set to charge only in the usb mode setting. Is there a way to change those settings in recovery like through the terminal? I would love to hear any possible solutions, I've been googling and search xda all over the place so any insight would be really appreciated.
Fortunately I had an extra shamu (with a very cracked screen) left over that I switched to in the mean time, but I'd like to get my old phone back in working order if possible! Any help or insight is appreciated!
gunha said:
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
Click to expand...
Click to collapse
You even made more errors. You don't seem to read properly. Franco does only support shamu up to nougat.
- Did you install the latest USB drivers and latest platform tools (adb, fastboot ...)
- Did you boot you phone into bootloader when you tried to connect?
Yup! I installed drivers from Google when I downloaded the platform-tools. I put my phone in bootloader mode when using fastboot, and my phone never indicated 'USB transfer cable connected' it just said 'connect usb.' also fastboot just said waiting for devices when I tried doing a getvar all....
try it on another laptop, try a new usb cable...you seem to have done everything right
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
gunha said:
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
Click to expand...
Click to collapse
Could be the cable. But the USB port could also be the cause. The simplest solution could be that the port is just full of dust. In that case, cleaning will help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
IF you still have access to TWRP, you can move your zips on an usb drive and connect it via otg and mount in TWRP and flash from the USB drive. Might help.
I have a very weird issue with my S10: it wont connect via usb to pc. Once connected a notification should display and the option "file transfer" should be there, but no such menu appears. When i plug it in to a pc it just starts charging, the pc also does not see a (bad) usb connection or whatever. I have been reading fora and watching youtube for over 1,5 hours. I feel now is the time to ask for help.
What might be usefull context: i have had the "moisture detected" error many times, it started showing up 2 weeks after i bought the device. Gladly i mainly use wireless charging so effectively it hasnt bothered me much, but it was weird since even after waiting for hours for the phone to dry (i dont think it was wet but whatever) the error was still there. One week ago the problem got quite severe, lasted for more than 24 hours and it just refused to charge, tried rebooting, turning it off, going into safe mode... to no avail. I had no wireless charger then, it was nasty.
I am using the usb cable provided by samsung (but used two others as well).
What i tried:
wiping cache and data from usb settings
wiping cache via recovery
reinstalling samsung drivers to pc
looking for a yellow exclamation mark in device manager on pc (not there)
different usb cables
different pc's
different ports on pc
rebooting the phone
booting in safe mode
installed dex on pc
via developper mode select file transfer as standard
via developper mode select any of the other modes to see if that helps
via developper mode revoked usb debugging authorizations
via developper mode enable usb debugging
The next logical step seems a factory reset. I am unwilling to do that however, since there are many gigs of photo's on the device that i want to backup first (the whole point of trying to connect it via usb heheh).
Your advice please!
Your could try to reflash your present OS via Odin but when doing so remember to use HOME_CSC. This way your data will be present when done flashing and phone reboots.
Norup58 said:
Your could try to reflash your present OS via Odin but when doing so remember to use HOME_CSC. This way your data will be present when done flashing and phone reboots.
Click to expand...
Click to collapse
How he can do the flash with odin when phone is not recognized by the computer !
Clean the charging port with a clean toothbrush and try again ... Also make sure that the charging cable supports data transfer ... If you tried all of these things and did not work, then most likely the charging port has a problem that may be oxidized or cut in the tracks..Try the solution that I gave it to you, and if it doesn't work, take it to a technician
charge from the wall.
I too have a similar predicament. Tried all the cables and USB ports I could get my hands on... I have a custom ROM also, so it could be that. I have done a full format and reflashed ROM (from SD card) - but it made no difference, the phone refuses to communicate via USB.
SO, if you have any solutions, please let me know!
I can however communicate via ADB over network. So, if you know some adb commands you can pull over an entire folder with the "adb pull" command.
I was trying to upgrade from A9 to A10 and phone booted into bootloader. probably because i didn't clear internal memory. but it didn't even let me boot back into twrp recovery, which i upgraded to be compatible with android 10.
i have done all that before and never had problems that my pc didn't recognise the phone. tried on linux, not just windows - same story. tried on different windows machine - again the same. doesn't even show it as unrecognised device under device manager. tried cleaning usb ports, still no difference. even cahnged the battery as i've read somewhere that low battery can cause phone not being recognised.
now i don't know what else to try. could be loose data pins at side usb c port that would cause this?
any help is appreciated
edit: i disassembled the phone and checked all the pins from side port. now i can't say for sure, but it seems like few pins are be shorted to ground. i'm not sure if i accidentally poked with multimeter shielding instead of pin, but i tested few times on continuity and last three pins all beeped on ground. can't really see inside the port that good, but it looks all untouched. could it be that damage is already done when they shorted for the first time or is there any hope?
Did you use side usb when trying to access fastboot? Also in my opinion its a simple matter of switching active slot, like from A to B or viceversa. Also, did you update with an ota file, thru TWRP or how?
VarDes said:
Did you use side usb when trying to access fastboot? Also in my opinion its a simple matter of switching active slot, like from A to B or viceversa. Also, did you update with an ota file, thru TWRP or how?
Click to expand...
Click to collapse
ofcourse i used side port. how to switch active slot if i can't access recovery nor connect phone to the pc to boot up twrp?
i updated through twrp with full android 10 zip downloaded from asus