Develop Bugs

[Q] USB connection

Ok so I am trying to plug my phone into pc using usb cable so i can use odin. But my computer doesn't recognize my device. I've tried everything from uninstalling the drivers and reinstalling them restarted pc and phone. nothing works i did get it to read one time and was able to access my sd storage and then i tried to go into download mode and i plugged in usb cable and it didn't recognize so i got out of download mode and it didn't recognize the phone again. Then i plugged in my girls evo and it reads the phone all the time. Is there something wrong with my epic then? how can i fix that problem. seriously getting frustrated!!

Try not to double post. We will get to your issue eventually. Refer to the other case, as it has potential solutions available for your issue.
(I've dealt with this as well.)

USB problem

I'm running cyanogenmod 7 on my evo 4g and when I plug it into a computer it only charges and never prompts me if I want to connect as a disk drive. It used to but now it just stopped. I had a backup of my rom so I put it on my girlfriends evo and hers still connected to the pc like normal but mine will not give me the option to hook up through USB. My computer says unknown device. Any help would be great. I can provide more info if you need.

More info. It gives me code 43 in windows 7. I was able to hook it up in xp but when I tried doing anything it no longer was able to detect the phone. I did a factory reset and it still doesn't work. I'm at a complete loss. I feel the only thing left to do is revert completely back to stock losing root and starting from scratch.

perhaps try completely uninstalling the device from windows in Device Manager. Then plug it in again and let it re-install the drivers

sitlet said:
perhaps try completely uninstalling the device from windows in Device Manager. Then plug it in again and let it re-install the drivers
Click to expand...
Click to collapse
I've tried that on two different computers with windows 7. My gfs fone reads fine with the exact same rom but mine wont.

It seems like the drivers on the phone are corrupted or something. At one point I found a forum that suggested to turn off bluetooth and a few other things. I decided to see if turning off my wifi would do anything and finally my phone showed the usb debugging notification and the mount as usb notification but it wouldn't mount so I restarted my phone and now it's back to doing nothing but charge the phone.

The only difference between the two phones is the rom then? Perhaps make a backup and flash a different rom or re-flash your current rom to see if that helps

sitlet said:
The only difference between the two phones is the rom then? Perhaps make a backup and flash a different rom or re-flash your current rom to see if that helps
Click to expand...
Click to collapse
I actually took a backup of my rom and put it on my gfs phone and hers worked. we had the exact same rom. I will try installing a different rom however and i'll let you know what happens.

Okay so I had a back up of sinister rom so I restored it and now it asks me if I want to connect as a usb device and so I do and my computer still says usb device not recognized or whatever.

Wow so I tried a backup of sinister rom that I had and suddenly it asked if i wanted to connect as a disk drive but windows was still saying usb device not recognized. I reverted all the way back to stock losing root privileges and it still doesn't work. It appears to me that it is a hardware problem. I don't know what else to do.

ok, so I hooked my phone up to a computer with ubuntu on it and my phone showed up but then when I went to explore the sd card it said permission denied. Then I hooked it up in windows 7 and it showed unknown device under universal serial bus controllers(as usual) but it also had it under modem, which is what I want.

Okay, got it working on this computer. After plugging the phone in several times it still said device not recognized. I have also been pushing ##data# and it was saying the same thing. I decided to shut my phone off one last time and when I hooked it up i pushed ##diag# and now it works. ****ing stupid. Glad it's working now.
UPDATE: Now all of the drivers install when I plug the phone in except the HTC DIAG doesn't appear even when i enter diag mode on the phone. this is the only driver i need installed but i can't install it because the computer isn't picking up that part of the device....This is getting irritating.

Turns out my port is ****ed up. I'm gonna have to order a new one and replace it.

[Q] hosed usb

I've been searching the web, but cannot find help. Have i9250, but cannot get it to be detected by a PC. I can't even get a device with no drivers installed to show up. Not in fastboot, not in download mode, nothing. I had a working, barely, phone, but the battery was draining and I couldn't detect the phone with any PC/USB cable combination. I replaced the USB daughterboard and still had the same issues. After that, I tried flashing stock recovery and stock rom, so I could maybe get Google to fix it, but it's stuck on boot loops. Also, no Omap 4440 detected, if I plug in without battery, like in this thread http://forum.xda-developers.com/showthread.php?p=28038226
Thanks in advance for any advice.

sgtkwol said:
I've been searching the web, but cannot find help. Have i9250, but cannot get it to be detected by a PC. I can't even get a device with no drivers installed to show up. Not in fastboot, not in download mode, nothing. I had a working, barely, phone, but the battery was draining and I couldn't detect the phone with any PC/USB cable combination. I replaced the USB daughterboard and still had the same issues. After that, I tried flashing stock recovery and stock rom, so I could maybe get Google to fix it, but it's stuck on boot loops. Also, no Omap 4440 detected, if I plug in without battery, like in this thread http://forum.xda-developers.com/showthread.php?p=28038226
Thanks in advance for any advice.
Click to expand...
Click to collapse
after my usb port started restarting my phone due to a short circuit i got by with a usb cable that i cut and attached the wires to the pogo pin connectors and charge it that way. Really not a good way, buy yourself a pogo pin charger dock if possible, sounds like a usb replacement is needed (same for me, but getting an extra couple of batteries, just got an external charger)

I was able to charge, but now I'm stuck with bootloops and can't get a data connection to a computer with fasboot or odin.

sgtkwol said:
I was able to charge, but now I'm stuck with bootloops and can't get a data connection to a computer with fasboot or odin.
Click to expand...
Click to collapse
cant boot into recovery? i've managed to get by with adb over wifi where it was needed, thankfully nothing that has required an actual usb connection.
at what point is the reboot occurring? would safe mode possibly help?

Recovery just shows the android open with red exclamation.
OS bootloops on Nexus logo.
Neither Odin nor bootloader are recognized by any PC/usb cable combination. Even after changing the USB daughterboard http://phonepartsusa.com/samsung-ga...onnector-flex-cable-0000824?filter_name=i9250

Lost transfer via USB

When I plug in my USB cable, it only charges, it no loner allows me to transfer files to my Desktop/Laptop. Nothing shows up on my computer.
When I start my LG PC software it never connects.
How can I set it so when my USB cable is plugged it allows me to transfer files and browse the drive.
I have looked everywhere and the options given does not work on this phone. Is there a setting I may have accidentally disabled??

have you ever connect via USB successful
duckfart said:
When I plug in my USB cable, it only charges, it no loner allows me to transfer files to my Desktop/Laptop. Nothing shows up on my computer.
When I start my LG PC software it never connects.
How can I set it so when my USB cable is plugged it allows me to transfer files and browse the drive.
I have looked everywhere and the options given does not work on this phone. Is there a setting I may have accidentally disabled??
Click to expand...
Click to collapse
Have you ever connect via USB successful?
Remove all LG Software, TOOLS, USB Drivers, and Install latest LG USB driver 3.11
Go device manager to check if all LG device is installed properly, You should find mtp device in the device manager.

asialove2013 said:
Have you ever connect via USB successful?
Remove all LG Software, TOOLS, USB Drivers, and Install latest LG USB driver 3.11
Go device manager to check if all LG device is installed properly, You should find mtp device in the device manager.
Click to expand...
Click to collapse
yes.
everything was going well until today.
nothing worked, I ended up de -rooting and going back to stock to fix it.

Thanks
duckfart said:
yes.
everything was going well until today.
nothing worked, I ended up de -rooting and going back to stock to fix it.
Click to expand...
Click to collapse
Thanks for your information.
Unroot and back to stock do fix the issues?

duckfart said:
yes.
everything was going well until today.
nothing worked, I ended up de -rooting and going back to stock to fix it.
Click to expand...
Click to collapse
How did u go back to stock if u couldnt connect through usb i have the same problem thanx for any help i was able to load a different rom that i had on my flash card thats all bust still no luck

someone help please id like to go back to stock any rom I install I cannot connect through use just charge

I've had this happen on my old phone occasionally, and found I had to turn the phone completely off (not just reboot) and back on to get the computer to recognize the phone again.

I can power off, take out battery, flash new rom ,factory reset ,wipe cache ,dalvic everything and no matter what computer I connect it to it just charges its not a matter of having driver its like the computer doesn't even know I plugged something in. happened after I flashed I think it was dragon rom not even sure or maybe after I updated the ota while rooted or is it you cant ota with cwm/twrp installed

lost transfer via usb
can you tellme what you have done to be able to flash a new rom without having the ability to transfer files via usb thanx still haven't figured anything out. just saw a post about it being enable through the kernel can anyone help with this

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.