Develop Bugs

[Q] Power, but no sync? Is a USB a USB cable?

Folks....
I have a question about the pin out of a USB cable. I have a cable that has a micro USB connector at one end (it plugs into my HTC EVO) and the other end is a standard USB connector.
This cable works just fine when I charge my HTC EVO. However, my computers can not see my htc evo. So I installed software from Sprint called "HTC Sync" version 3 something. Nothing.
So here is my question. Are USB cables that are sold as "Sync" cables have a different pin out than a USB cable that is used for power?
Maybe I need to change a setting in my phone to make it sync?
In settings, under Connect to PC, I have it set up as:
Default Connect Type = HTC Sync
Ask me is checked
I also tried:
Default Connect type = Disk drive
Ask me is checked
Can some of you give me some advice?
Thanks
jack
Portland Oregon

I can't speak on usb pins but I do know that there are some shoddy low quality usb cables out there (the ones that come with epic 4g) and some good high quality ones (the ones that come with the palm pre). with the low quality ones I can't copy files to my card.

In general, unless it's sold as a power cable, it should have the normal connections. Some cables have the data lines cut and shorted together, which tells the phone it can draw more power than a normal USB port provides. These should only be used with chargers due to the risk of burning out a PC's USB port.
A good way to test is to plug it in, open Spare Parts and go to Battery Information, then see if it says it's charging on AC.

Not all usb cables are created equally.
Sent from my PC36100 using XDA App

Noxious Ninja said:
In general, unless it's sold as a power cable, it should have the normal connections. Some cables have the data lines cut and shorted together, which tells the phone it can draw more power than a normal USB port provides.
Click to expand...
Click to collapse
Ahhh. OK. Thank you.
jack

USB Cable Charging but not Sync
Some cables do not have hooks and they are loose in phone. This also prevent to connect it with PC for sync.

Noxious Ninja said:
In general, unless it's sold as a power cable, it should have the normal connections. Some cables have the data lines cut and shorted together, which tells the phone it can draw more power than a normal USB port provides. These should only be used with chargers due to the risk of burning out a PC's USB port.
A good way to test is to plug it in, open Spare Parts and go to Battery Information, then see if it says it's charging on AC.
Click to expand...
Click to collapse
Excellent info.
RTC88 said:
Not all usb cables are created equally.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not so much.
---
These
Code:
[URL="http://www.amazon.com/gp/product/B004W3LKZ0/ref=cm_cr_rev_prod_title"]cables[/URL]
Look sturdy but break too easily. Not as cheap as most chinese made but these cables usually break in about 2 months for me. Dont even think about folding it and putting it in a bag for those frail,dying HTC phones.
I wonder if these are easy to fix...
-Can anyone recommend a simple way to handle these wires or a more durable wire? I dont want to buy one every month. I'm thinking about http://www.amazon.com/Micro-Retractable-Cable-Samsung-Vibrant/dp/B004SK35M8/ref=sr_1_19?s=wireless&ie=UTF8&qid=1328931599&sr=1-19.

I herd with root and some roms
I herd with root and some roms sync wont work .. make sure u have all the right drivers and ..Ive had a cavle that would work for mass storage for one phone and not another...

KF2 does not go into fastboot

I have a KF2 that is stuck onthe orange/white "Kindle Fire" boot logo. The logo displays on the screen and stays static - it doesn't flash/disappear/"shimmer". It doesn't reboot/bootloop, it just stays there.
The device doesn't power on when connected to a PC. Using a factory/bootloader cable, a standard microUSB cable - the device stays completely dark. Pushing/holding the power button does nothing when the USB cable is plugged in, it shows no signs of life. Removing USB, the device boots to the "Kindle Fire" screen and stays there indefinitely. Plugging it into an AC adapter but not a computer, the unit boots to that same "Kindle Fire" screen.
The device was rooted a long time ago by somebody else and I'm not sure what has been done since then. My plan is to fastboot and flash boot/recovery/system/uboot to get it back to stock, but with the unit not even turning on I can't get to that stage. Windows or Linux doesn't pick up any sort of USB device when plugged in (lspci/lsusb/dmesg on Linux returns nothing at all). The fastboot cable works, as I've used it on an identical KF2 with success.
Any thoughts on how to progress would be great!

Best I recall the HD had a bad habit of corrosion on the USB connector. Crack it open and check it..
This would explain a lot if it is corroded and shorting out the power pins. The instances I've seen of this was actually the device would only go into fastboot.

mrkhigh said:
Best I recall the HD had a bad habit of corrosion on the USB connector. Crack it open and check it..
This would explain a lot if it is corroded and shorting out the power pins. The instances I've seen of this was actually the device would only go into fastboot.
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately this isn't a HD, just a regular KF2. I did open it up and check the USB port itself and the pins on the motherboard and all look fine. The device will still startup when on AC over USB - just not with data from the computer.

R70 said:
Thanks for the reply. Unfortunately this isn't a HD, just a regular KF2. I did open it up and check the USB port itself and the pins on the motherboard and all look fine. The device will still startup when on AC over USB - just not with data from the computer.
Click to expand...
Click to collapse
sorry for reviving old bread
can you get into the system at all?
when plugged in with fastboot cable, does device manager show anything?
is there any missing drivers?
does windows react at all to kf2?

Computer can't see phone at all (no driver issue)

My phone isn't detected by my Winodws computers at all.
If I plug it into one of the USB ports directly, the phone starts charging, but that's it.
This is obviously not a driver issue as there's no unknown devices in Windows.
I tried different USB cables, USB-C and MicroUSB-to-USB-C adapters to no effect. Also tried this on two computers to no effect.
There's nothing in the phone's USB-C port (dust, dirt etc) and it's usually covered by the magnetic tip of my Volta charging cable (that's one of those "MagSafe-like" cables where the actual plug breaks off from the cable if you pull it)
If I connect the phone to a USB hub, the hub's ports usually light up when a device is connected. The phone does not trigger the port LED to light up.
Same behavior in System, Recovery and Download mode -> Computer doesn't even notice there's a new device, but device is charging (so apparently it notices there's something connected, just no data transfer)
Is my phone broken? Maybe a hardware problem with the USB-C port? Any advice on how to narrow down my problem?
Thanks in advance for any help or ideas you might have.

I had the same problem today but, in my case, it was the cable's connector.
Since you have multiple cables, it's unlikely they are the issue but it would be proof if you were able to check them with a different device. Also, ensure they aren't charge-only cables (I have a few of those; they lack data pins so devices don't slow-charge when they could rapid-charge instead).
You checked in download mode, so that eliminates configuration issues with Android.
That's all I got; it does appear to be the phone's connector or the USB interface.
A hail Mary would be to stick a 2PS6IMG.zip onto an SD card and RUU it in case firmware is the problem.

I'm pretty sure my cables could be used for data transfer as well. I'll try to find a colleague with USB c phone to try that as well. (family has all iPhones and most of my regular meet friends have phones from the stone age)
The firmware thing could be hard to do. Apparently you can't modify the Cid from within the phone anymore (setprop ro.cid doesn't do anything like it did on old HTC phones, despite having S-OFFed the phone) and T-MOB101 (T-mobile - the German parent of all those other clones) firmware is a rare sight.

onoz ! i have twrp and boootloader, but no system files... HELP !

due to my own stupidity, i had unlocked and installed twrp with a lot of effort, as the usb is decidedly iffy
i managed to use a file manager to import the requisite lineage rom and gapps, and then in my infinite wisdom stored them somewhere volatile - one mistake i won't make again
and so when i cleaned the device prior to a "new" install, i inadvertently lost the zip files, and now the computer refuses to recognise the device
no amount of forcing the right usb driver onit works, because i presume the computer does not know it's a flo
so, is there any way i can get it connected and push the roms to storage ?
my skills at the command line are limited, but i can follow scripts
this is sad, as i was soooooooo close to completing the install, after which the usb would have become redundant (i have a wireless charger and can wifi file across with a working system)
is this thus my very first brick ?
or can i trick the usb connection into working with the computer, or somehow wirelessly transfer to such a basic installation, or rig an otg connection (i have no cables that would seem to join micro-usb to any female plug to use a memory stick or sd card in adaptor)
thanks for any suggestions :fingers-crossed:

Get an image file from Google https://developers.google.com/android/images
Try going into TWRP and go into sideloading (can't remember exact menu - only used it once to get out of a similar problem), then try to connect USB lead to PC.
Run flash-all.bat on PC and that should at least get a system on the device.
Maybe...

thanks for the suggestion, but the sideload could place the lineage.zip instead if the computer would accept a usb connection - that's the problem: sideload can't work because the usb device is not recognised
my best bet would appear to be load the zip via otg - the twrp interface appears to allow that
i'll report back here if that works (once i procure a usb otg connector)

I was in a similar position once and couldn't get a normal USB ADB connection with PC until I tried TWRP sideloading which kicked in the PC connection.
Did you try it?
OTG was the next thing I was going to suggest

scruffy1 said:
the usb is decidedly iffy
no amount of forcing the right usb driver onit works, because i presume the computer does not know it's a flo
Click to expand...
Click to collapse
As the USB port is broken there is no hope that an OTG adapter would work because it can not function without the data connections, exactly like PC-USB. Have a look at the port's soldering, it may need some re-work. If the port's connectors are damaged then a replacement is very cheap.
:good:

k23m said:
As the USB port is broken there is no hope that an OTG adapter would work because it can not function without the data connections, exactly like PC-USB. Have a look at the port's soldering, it may need some re-work. If the port's connectors are damaged then a replacement is very cheap.
:good:
Click to expand...
Click to collapse
thanks for the suggestion
i sprung the back and was going to attempt to reflow the solder in case it had a dodgy connection - but i noted that the actual usb connector looked like it had been stretched, and took to it with my favourite pliers and performed some creative metalwork by squeezing it
lo and behold! the otg connection worked, at least for long enough to transfer the custom rom
thereafter when i reassembled the case, the otg connection failed but now the usb link seems to be happy enough even though that makes no great sense seeing it is the same connector port, and the otg works on my other android devices
still, gotta take what you can get, and i am now the proud owner of a nexus 7 "flo" with lineage doing nicely
thanks for all assistances

scruffy1 said:
thanks for the suggestion
i sprung the back and was going to attempt to reflow the solder in case it had a dodgy connection - but i noted that the actual usb connector looked like it had been stretched, and took to it with my favourite pliers and performed some creative metalwork by squeezing it....
Click to expand...
Click to collapse
Ahh this explains why my N7 - used daily - has never developed any USB port problems! I thought that this USB port's construction was rather 'weak' so preemptively I applied a simple reinforcement, have a look at the attachments.
It was 4 years ago....
:highfive:

Can't get file transfer/ADB/fastboot over USB

I just bought a used Pixel 2 XL and it has the file transfer/ADB/fastboot over USB problem. I've been through every solution here and on Google Pixel support with no luck (see below).
The phone connects via USB for a second and brings up ADB debugging auth, then disconnects. Every other thing I plug into the phone works fine (thumb drive, OTG camera, charger). Wireless ADB works fine, but I can't unlock the bootloader this way (that I know of). I can't get ADB or Fastboot access in bootloader or recovery mode.
I'm guessing software/kernel problem on the phone since everything else works with the USB port. I'm currently running build RP1A.201005.004.
On the factory image page, there's a new image, RP1A.201005.004.A1, Dec 2020, that I hope is a fix, but I've got no way to install it except if I get it OTA.
If anyone has any ideas on other things to try, please LMK! Thanks!
Solutions I've tried:
Cleaned port, dozens of cables, USB 1, 2, & 3 ports on four different machines and three different OS that work with ADB on other phones, every phone ADB/USB setting on/off in all combinations, cleared data for external storage, can't clear data for media storage because it's now grayed out in this build.
I've also tried the old tricks to try and get the OTA sent, but I'm guessing those tricks don't work with Android 11.
I may try replacing the internal USB port and cable since it's only $7, but I don't think it's the problem from what I've read in other posts here.

phineous said:
I just bought a used Pixel 2 XL and it has the file transfer/ADB/fastboot over USB problem. I've been through every solution here and on Google Pixel support with no luck (see below).
The phone connects via USB for a second and brings up ADB debugging auth, then disconnects. Every other thing I plug into the phone works fine (thumb drive, OTG camera, charger). Wireless ADB works fine, but I can't unlock the bootloader this way (that I know of). I can't get ADB or Fastboot access in bootloader or recovery mode.
I'm guessing software/kernel problem on the phone since everything else works with the USB port. I'm currently running build RP1A.201005.004.
On the factory image page, there's a new image, RP1A.201005.004.A1, Dec 2020, that I hope is a fix, but I've got no way to install it except if I get it OTA.
If anyone has any ideas on other things to try, please LMK! Thanks!
Solutions I've tried:
Cleaned port, dozens of cables, USB 1, 2, & 3 ports on four different machines and three different OS that work with ADB on other phones, every phone ADB/USB setting on/off in all combinations, cleared data for external storage, can't clear data for media storage because it's now grayed out in this build.
I've also tried the old tricks to try and get the OTA sent, but I'm guessing those tricks don't work with Android 11.
I may try replacing the internal USB port and cable since it's only $7, but I don't think it's the problem from what I've read in other posts here.
Click to expand...
Click to collapse
I just installed the update using ADB from my Chromebook via Crostini Linux. I had an issue at first due to the USB cable I was using. Switched to a USB 3 cable and it worked flawlessly. Kinda weird that after the update it still says October 2020. Looks like the .A1 on the end of the build is the only difference, other than whatever security updates they pushed.

robn30 said:
I just installed the update using ADB from my Chromebook via Crostini Linux. I had an issue at first due to the USB cable I was using. Switched to a USB 3 cable and it worked flawlessly. Kinda weird that after the update it still says October 2020. Looks like the .A1 on the end of the build is the only difference, other than whatever security updates they pushed.
Click to expand...
Click to collapse
I just got the update OTA today. I still can't get a USB connection to work for longer than a second or two. I've tried dozens of cables and several computers. I'm going a little crazy here.

phineous said:
I just got the update OTA today. I still can't get a USB connection to work for longer than a second or two. I've tried dozens of cables and several computers. I'm going a little crazy here.
Click to expand...
Click to collapse
I have noticed mine is a little finicky with ADB, especially when connected via USB 3.0. Connecting with USB 2.0 with a good cable seems to always be reliable and never disconnect. Also if you haven't tried using the stock cable that came with the Pixel, I would try that for sure.

I just replaced the internal USB assembly and nothing has changed. The old connector was definitely worn though.
I'll go back to trying more cables and ports. I ordered a cable that another poster claimed worked for them, but I had no luck with it.
For anyone wanting to replace their USB ass'y, here's what I learned from doing it. The service manual on ifixit is a good guide but leaves out a couple of important steps.
Heat is your friend. I used a clothes iron adjusted to 160F. The phone dissipates heat quickly so you may need to heat it several times. Place a towel over the screen and set the iron on it. I used guitar picks to pry up the screen and keep it separated while I heated the other sides.
The screen cable connection covers are hard to remove and you'll probably need a to use a metal spudger.
Heat the back of the phone to help remove the loudspeaker ass'y without damaging it, and again to remove the old cable ass'y.
The replacement ass'y I got had adhesive applied for the center of the cable, but not the adhesive foam pad under the antenna connector, so heat and scrape between the pad and phone body to remove it intact for reuse.
My old antenna connector partially came off in the white antenna connector and it was very hard to see what was wrong even under strong magnification.
You'll need a new screen adhesive sheet to reattach the screen securely.
Both parts came from a seller on ebay. Dougsgadgets was the only one that had both parts in stock. I think I paid $11 and they shipped quickly.
Good luck!