Related
Hi!
I have LG G3 D855 Vodafone ESP with free ROM v10i
Have one problem:
When connect USB LG to PC, dissable (I don´t know like) USBs Mode, only charge,
How fix this optiom to change an other one, options to MTP?
Thanks
Giving this a bump, as I now have this problem as well. Just today is when this occurred. I've had the LG G3 for about two weeks now and always had the option of switching between full charge mode or MTP, but now I suddenly lost the feature all together. I rooted my phone about a week ago, and made all the changes then. Had the feature all the way up to yesterday and now today I am noticing it is no longer there.
Rebooting the phone doesn't bring it back either. Any ideas?
---------- Post added at 06:46 PM ---------- Previous post was at 06:34 PM ----------
Nevermind! Embarrassing but fixed it. Issue was the USB cable not being plugged all the way in the slot.
Lost USB connection mode Fix
Go to Settings and click on storage and then click on the 3 dots at the top right of your screen then click on USB PC connection click on Media device (MTP) or Send Images (PTP) and that's it you will be fixed
runesmtr said:
Go to Settings and click on storage and then click on the 3 dots at the top right of your screen then click on USB PC connection click on Media device (MTP) or Send Images (PTP) and that's it you will be fixed
Click to expand...
Click to collapse
Except I don't have any dots in that menu I upgraded to lollipop so I don't know if that could be the reason why. Any other suggestions? I'm desperate here
zach1791 said:
Except I don't have any dots in that menu I upgraded to lollipop so I don't know if that could be the reason why. Any other suggestions? I'm desperate here
Click to expand...
Click to collapse
Quick google search: http://support.bell.ca/Mobility/Sma...ow_to_change_the_usb_connection_options_on_my
The guy above gave you the solution, whether you are on kk or lollipop, it's still in your settings. Just gotta find it.
That would be an easy fix right? It's why I'm asking here. Once I made the mistake and press the charge only option and now it will not allow me to go back and choose any other option such as MTP or PTP. Know any workaround for this?
zach1791 said:
That would be an easy fix right? It's why I'm asking here. Once I made the mistake and press the charge only option and now it will not allow me to go back and choose any other option such as MTP or PTP. Know any workaround for this?
Click to expand...
Click to collapse
Go into Settings > Apps > Tap "Three Dots" top right > Reset Default Apps > Select Clear on App....
573v3 said:
Go into Settings > Apps > Tap "Three Dots" top right > Reset Default Apps > Select Clear on App....
Click to expand...
Click to collapse
Thanks for the reply man. Didn't work though. I cleared every single default setting and app preferences. The problem remains. Funny enough it still persists even after factory resetting.
help
zach1791 said:
Thanks for the reply man. Didn't work though. I cleared every single default setting and app preferences. The problem remains. Funny enough it still persists even after factory resetting.
Click to expand...
Click to collapse
hello you managed to solve the problem I also have the same problem just that to me even with charging usb charger
thewall76 said:
hello you managed to solve the problem I also have the same problem just that to me even with charging usb charger
Click to expand...
Click to collapse
Sorry no I haven't. It's really perplexing because I wiped the phone clean (which should have set all settings to default) and yet the problem remains.
I'm having this problem also.. Been a month I tried all above suggestions but still no fix
Me Too
I've been having this issue for around a week now after switching to USB Tethering. Now whenever I connect my phone via USB to a computer (any computer) it defaults to the USB Tethering mode.
On Android Lollipop there are no options to change in the storage menu.
I have noted that "plug and pop" fails when the usb cable is connected "unfortunately plug & pop has stopped" I suspect this maybe the root cause of the issue. I have run a task to correct permissions but this hasn't resolved this force close.
Any help suggestions apart from those already provided (that I have tried) would be appreciated.
I'm also having this issue for about two months. I've since given up. Also tried factory reset, multiple times. Would love to get this resolved. I have the D851 for T-Mo.
I should also add that I've tried multiple custom ROMs (Bliss, SkyDragon, CM, and one or two more) as well as the stock. Nothing works.
h3lman said:
I've been having this issue for around a week now after switching to USB Tethering. Now whenever I connect my phone via USB to a computer (any computer) it defaults to the USB Tethering mode.
On Android Lollipop there are no options to change in the storage menu.
I have noted that "plug and pop" fails when the usb cable is connected "unfortunately plug & pop has stopped" I suspect this maybe the root cause of the issue. I have run a task to correct permissions but this hasn't resolved this force close.
Any help suggestions apart from those already provided (that I have tried) would be appreciated.
Click to expand...
Click to collapse
I've uninstalled "plug and pop" which has stopped the force closes but not this issue. I've also booted into recovery and cleared cache. No joy after that either.
Broked
Also on lollipop, had MTP/PTP etc option until this week, no suggested fix in this thread works
In addition my PC is routinely telling me the SIM or SIM2 unlock is "required" to use the phone. It's, like, wigging out. It's vibrating when there are no messages as well, probably repeatedly telling me that it's charged and I should unplug it. Kinda stupid, like a lot of programming in this stock ROM (popups, volume messages, other s/w irritations that are just amateurish). The device is good but it seems to be time to replace the OS.
PC is an Ubuntu 17 rig with KDE; phone is rooted; logcat & shell still work. Odd.
—JDK
Having the same issue.. I've been using cm12 /12.1 for months and all of a sudden my PC won't recognize my G3 . it charges when connected to the PC but that is it. Just found and watched a video on YouTube with another person Having this exactbproblem and it was due to oxidation on the "gold teeth" within the phones charging port . He fixed the issue by lightly scraping/cleaning the gold teeth with a screwdriver. He was brave . im going to try the storage/3 dots/ USB connection suggestion tmw when I can access the computer and will share an update.
Heres The video mentioned above.....
https://youtu.be/pmpmH4NyG
I am also having this problem on my D852 running 4.4.2.. last time I used MTP was at least a couple months ago, and now there's no USB options at all. I have checked Storage settings, there is no More Options anymore. I have also tried Application defaults reset, still no change. On mine the USB tethering option connectivity is completely gone- the option is greyed out as though the phone no longer recognizes it has a USB connection at all.
It seems pretty obvious to me that this is a hardware failure somehow - everyone seems to be having this problem after several months of use, and across multiple G3 models and multiple version of Android. In mine the USB functionality is *gone* entirely yet the phone still charges. Does anyone have a *code to perform USB diagnostics?? *NOT* USB debugging- actual onboard hardware self-tests like the radio, touchscreen, etc. *#*#4636#*#* does nothing for USB.
Solved missing usb connection options missing
I got bored at work one night and reread these forum entries and noted the possibility of there being a hardware issue with the USB port. Rather than wait until I got home I decided to see if there was a diagnostic mode hidden somewhere that would check out the hardware... and there was. So I plugged in the codes appropriate for the international g3 and the diagnostics screen popped up. Woohoo. I thought I'd just run the full suite of tests and that was the last thing that worked after the phone rebooted. It then started coming up with a message "security error" and went into a boot loop. Wait it gets better. I booted into TWM recovery and did a restore to my previous backup. This resulted in the phone becoming soft bricked....arrrrghhhh.
My next step was to download the D85520H_0 kdz file and apply that to the phone with the kdz tool after putting the phone into download mode. When the phone rebooted it went into the diagnostics mode which I then exited and my phone rebooted into stock lollipop and was working fine. All USB connection modes were once again available. There still aren't three dots on the storage screen though. There was a firmware update to 20I available so I decided to let my phone upgrade before rerooting. However it seems that 20I has some "fix" in it to prevent both the LG 1 click root and purple drake from working on it. In the case of one click root it seems to root the phone but it actually doesn't. In the case of purple drake it just sits on the screen waiting for device even though my phone is connected correctly.
So short story is that I suggest you download the the 20H firmware kdz for your country and apply it with the kdz flashing tool after putting your phone into download mode and then rerooting but NOT upgrading to the 20I firmware unless there is an update to either of the rooting tools. If you're lucky you might get your usb connection options back.
---------- Post added at 08:31 AM ---------- Previous post was at 08:00 AM ----------
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
:angel:
problem persists
Friend and me both bought 2 G3s from the same shop. My friend doesnt have this problem while I do. I do not want to reset my device. Is there no solution yet?
Solved MTP options in G3
ankitmania said:
Friend and me both bought 2 G3s from the same shop. My friend doesnt have this problem while I do. I do not want to reset my device. Is there no solution yet?
Click to expand...
Click to collapse
Step1: Connect your G3 to the computer
Step2: Go to device manager in your computer
Step3: Search for LGE composite device and uninstall the driver
Step4: Install LG PC suite
Step5: Press on the 'Connect with USB' button
Step6: Search for the device. The software will say device not found and it will provide an option to reinstall the driver.
Step7: Keep your G3 connected to the computer and reinstall the driver and you are done. G3 will show options to connect via MTP.
USB cable only charges the phone when connected to computer. Tried the following
1. Using 2 different cables which previously worked for data but phone only shows charging.
2. Using pc and Mac and both does not see phone. Looked in device manager of windows but it nothing shows up. Both computer previously used for data transfer on this phone
3. Looking inside usb-c port but no lint or dirt. Although just before update to September security patch my phone has some water on the screen which I wiped off. And the phone does not show sign of problem other than no data transfer to computer
4. Factory reset phone and same thing
5. No notification shown for changing charging only to file transfer
6. Computer doesn't Bing when connected.
What else can I try? Anyone can help or confirm if their usb-c works after September update so I can narrow down to hard ware problem.
Anyone diagnosed this hardware problem before?
Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.
jd1639 said:
Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.
Click to expand...
Click to collapse
I tried changing the options to MTP, PTP, midi, charge only, etc but non of them make any difference to the computer, nothing pops up and does not show as new item connected in device manager
did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.
jd1639 said:
did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.
Click to expand...
Click to collapse
Tried changing when USB connected and when not. Doesn't seem to make a difference.
I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware
jd1639 said:
I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware
Click to expand...
Click to collapse
I don't know how I can flash a previous firmware if I don't have USB access.. it's really frustrating. Looking from ifixit. It does not seem there is any chip near usb-c other than voltage control.
Can't seem to find how I can look at logs to know if USB has been engaged or if there is any error message. It's all dead end and my phone seem to be the unique case.
Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
jd1639 said:
Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
Click to expand...
Click to collapse
USB worked fine, I am using it for Android studio, and transfered music across as well. Looked at the post and it seemed that has to do with device manager. Problem is mine does not show up any changes to device manager. I.e . No ADB or other device. Seemed like no data is exchanged and windows treating it like a battery or something
Any fix for this?
I've hit the same issue and wondering if anybody has a fix for this yet?
I'm using linux and seeing no usb activity at all from my nexus 5x after sep 17 update.
I've tried multiple cables. Cleaned the usb port on the phone. Multiple PCs.
I've connected to the phone using adb over tcpip and seeing nothing in logcat except battery logs when the usb cable is plugged in and out.
Turned usb debugging off and on.
I've set usb mode in developer options to mtp (it was on 'charging') and restarted the phone. Then find the option is forced back to 'charging.'
Logcat entries during boot show no failures in regards to usb connectivity.
Charging works fine but no data connectivity via usb at all.
Anyone got any other ideas?
Hello world.
I had the same issue.
To solve the problem :
- unlock developer mode
- switch on debug usb
regards
J.
I had this problem too- did not have to enable USB debugging though, just enabling the developer options fixed it for me. Which is odd because I definitely had them enabled previously... I guess a recent update reset that and for some reason all the USB data options are tied to developer mode now.
I've got 790 (american, as i know). The same issue, no response from service, guarantee, doesn't help, pc shows it as unknown device. some other bugs, mobile data fails, no sim detected after a few seconds, violet camera with no focus, but nice when the distance ia ok, so matrix works ok, but no stabilisation.
Then, bad battery, it seems that the bank ia ok, but controller works bad. it charges enough time to think that the capacity is not degraded. I suppose that usb controller (pc connection and fsat discharging) are nearby problems.
None of the above posts worked for me on my N5x (8.1.0 March), but searched some more and found this to work for me:
https://productforums.google.com/forum/#!topic/phone-by-google/DfpqXN1UfWY
Hello everyone. I'm just resurrecting this old thread so I can provide the solutions I have found to this problem. It appears this symptom has multiple causes, and there are different solutions depending on the cause. I have seen this problem twice now on my Nexus 5x (stock, no custom ROM) and solved it both times.
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
2. SOLUTION #2 - ClockworldMod USB Driver was installed. Replace with Google driver
The second time I encountered this issue, the Solution #1 above did not work. Surprisingly, the adb devices command successfully detected the Nexus 5x. It's just that the phone wasn't showing up in the Windows 10 File Explorer interface.
The root cause of this problem was that I had installed the ClockWorldMod USB Driver because I was playing around with their Vysor App (on a different phone.)
BTW, I think the Vysor tool is really nifty for screen mirroring purposes!
To resolve the problem, I replaced the ClockWorldMod driver with the regular Google USB Driver.
(Sorry, XDA is not letting me post links because of my low post count. The link is:
h++ps://developer.android.com/studio/run/oem-usb.html )
The procedure is:
- Download the Google USB Driver from the link above and extract the ZIP.
- Enter the Windows Device manager
- Find 'Android ADB Composite Interface'
- Open the properties of 'Android ADB Composite Interface' and you will see it is from ClockWorldMod.
- Right click on this Interface and Select 'Update Driver'
- Click on 'Browse My Computer for Driver Software'
- Click on 'Let me pick from a list of available drivers on my computer'
- Click on 'Have Disk'
- Browse to the Google USB Driver you downloaded.
- Select that driver and load it on top of the ClockWorldMod driver. (Windows may claim that you've got the best driver already installed, but ignore that.)
After re-installing the Google driver, the Nexus 5x appeared immediately in the Windows 10 interface for file transfers.
Cheers, I hope this helps someone out!
I have the same problem with LineageOS 15.1, I am not sure since when, because I don't use USB that often, but I it must have been after the second update for 15.1. ADB and FASTBOOT don't work.
None of the suggested methods work. I am on Linux, but I also tested the USB driver solution on a windows PC.
The problem is, my phone does not trigger any response from the system I connect it to.
On Linux an lsusb/dmesg shows nothing, and on windows it doesn't make the classic "ding" when I connect something to the USB port.
It is like my phone isn't even there.
In the developer options under networking and USB, USB was set to charging only. I changed that to MTP, but it didn't help.
Now I can't change it back (not that I want to, but just saying). No matter what I press on this menu, it always stays on MTP.
I am here because of adb not connecting tho, MTP is not my concern anyways.
I am not sure what to do, format data, and wipe system etc. and go for a clean install? The problem is, when I boot into recovery, ADB and FASTBOOT don't work either, i.e. my computers don't see an USB connection. So will a wipe even help? I am scared I wipe my phone, and then I can't connect via ADB in TWRP.
Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?
tantalfr said:
Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?
Click to expand...
Click to collapse
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!
ufopaper said:
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!
Click to expand...
Click to collapse
Never underestimate the power of a toothbrush
Bamboo-Toolkit said:
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
Click to expand...
Click to collapse
Amazing, this solved my problem. Thanks!
so im using a pixel 2 xl, and i cant seem to transfer files between my phone and any pc whatsoever, i used to do this easily before, ive tried everything, turned on usb debugging, use the notification drawer changed the cable, but nothing seems to be working, what coudl be the problem and how do i solve it ??????????????????
USB mode now always defaults to "charging". You have to change it manually to "MTP" each time. At least in my experience.
I had the same problem. With my Nexus 5x and USB-C to USB cable it works, but with my Pixel 2 XL it works not, so i had to buy a new USB-C to USB cable and now it works.
Not sure what cable you are using but do not use a USB C to USB C cable, make sure its a USB c to USB a.
Sent from my Pixel 2 XL using XDA Labs
Ive been having issues lately too. Doesnt matter which cable i use. It will connect then disconnect over and over again. IT may be my computer but not sure how to check why it would be doing that.
Are you doing gigabytes of data? If it's just in the hundreds of megabytes transfer to Google Drive. I do that when I have files on my computer I want over to my phone and vice versa.
Sent from my Pixel 2 XL using Tapatalk
Engineer
nasfayde said:
so im using a pixel 2 xl, and i cant seem to transfer files between my phone and any pc whatsoever, i used to do this easily before, ive tried everything, turned on usb debugging, use the notification drawer changed the cable, but nothing seems to be working, what coudl be the problem and how do i solve it ??????????????????
Click to expand...
Click to collapse
I had the same issue with my Pixel 2 as well and after reading through numerous forums, I figured out how to fix it. its been two days now and I am still able to transfer files via USB.
Here is what you need to do:
1) Enable developer mode by going into Settings > System About Phone > Build number and tapping a few times (5 I think!)
2) Click back and then select Advanced > Developer Options
3) Scoll down the menu until you see "Default USB configuration". Tap and then select the option you require (ie: File Transfer)
4) Click back, then scroll up the menu till you see "USB Debugging". Enable USB Debugging.
5) Connect your Pixel 2 to you laptop/PC. The phone should appear in the Devices list in 'Control Panel\Hardware and Sound\Devices and Printers. Leave it connected for another 5 or 10 minutes and it should become available in "This PC"
6) Disconnect the Pixel2 from your laptop/PC
7) Disable "USB Debugging" and disable "Developer Mode" on the phone.
8) Reconnect the Pixel2 to your PC/Laptop. It should now appear under "This PC" every time you connect and you should now be able to view and transfer files between you PC and Pixel2.
Let me know if it works for you or not.
equlizer said:
Ive been having issues lately too. Doesnt matter which cable i use. It will connect then disconnect over and over again. IT may be my computer but not sure how to check why it would be doing that.
Click to expand...
Click to collapse
I had the same issue on my notebook yesterday - the phone would connect, but once I transmitted a larger file the transmission was terminated after a few seconds.
In my case it wasn't the cable, it was the USB port on my notebook! I simply used a different one and then it worked flawlessly
Thank god my notebook has 4 USB ports, I pity people with notebooks with a single USB port :laugh:
IsaacFC said:
I had the same issue with my Pixel 2 as well and after reading through numerous forums, I figured out how to fix it. its been two days now and I am still able to transfer files via USB.
Here is what you need to do:
1) Enable developer mode by going into Settings > System About Phone > Build number and tapping a few times (5 I think!)
2) Click back and then select Advanced > Developer Options
3) Scoll down the menu until you see "Default USB configuration". Tap and then select the option you require (ie: File Transfer)
4) Click back, then scroll up the menu till you see "USB Debugging". Enable USB Debugging.
5) Connect your Pixel 2 to you laptop/PC. The phone should appear in the Devices list in 'Control Panel\Hardware and Sound\Devices and Printers. Leave it connected for another 5 or 10 minutes and it should become available in "This PC"
6) Disconnect the Pixel2 from your laptop/PC
7) Disable "USB Debugging" and disable "Developer Mode" on the phone.
8) Reconnect the Pixel2 to your PC/Laptop. It should now appear under "This PC" every time you connect and you should now be able to view and transfer files between you PC and Pixel2.
Let me know if it works for you or not.
Click to expand...
Click to collapse
Got the same problem. Since a few days device isn't recognized on any computer. Tried serveral usb cables (they were all working before) - no success. As soon as i am connecting device to a windows computer it says "device couldn't get regonized properly". So it isn't recognized as android phone. So your method didn't work (tried all the steps before). I also remarked before, thad my device sometimes restarts as i plug in an usb cable. Mainly when connected to a pc but also serveral times only when charging. So i resetted my device back to all stock (even formated data), flashed original boot whitout twrp, no root. It's starting nice but i even can't install the update (january patch) through device. Alway gives me install error. So it isn't recognized in adb... So i can't use fastboot mode to reinstall twrp.... Any advice? Think gonna claim for replacement.... Seems a hardware problem.
Had something similar a couple of months back.
Just do a quick check with usb dac and otg. If they are not working, the component is fried. RMA.
Else, faulty cable or friend port in laptop.
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.
As the written on the title section, my pc/mac can not detect my phone, it only charges it.
I re-flashed my phone to stock ( Oct update ).the problem is when it booted up. It can't detect anymore my phone. My pc gives me an error "USB can not be recognized". I think there's no problem with the pc driver since i just flashed the image. Any suggestions??
Method i tried.
Factory flash (since i cant go to bootloader and pc/mac cant detect it)
Safe Mode usb connection
ADB over wifi cannot be detected
RMA (not possible, bootloader unlocked)
kismetmookz said:
As the written on the title section, my pc/mac can not detect my phone, it only charges it.
I re-flashed my phone to stock ( Oct update ).the problem is when it booted up. It can't detect anymore my phone. My pc gives me an error "USB can not be recognized". I think there's no problem with the pc driver since i just flashed the image. Any suggestions??
Method i tried.
Factory flash (since i cant go to bootloader and pc/mac cant detect it)
Safe Mode usb connection
ADB over wifi cannot be detected
RMA (not possible, bootloader unlocked)
Click to expand...
Click to collapse
I've RMA'd a bootloader unlocked phone before. Just flash stock firmware and re-lock it before sending it back. Google's only requirement is that you factory reset from the settings menu in order to disable factory reset protection. If you fail to do this, there will be problems, but otherwise you should be fine.
TheSt33v said:
I've RMA'd a bootloader unlocked phone before. Just flash stock firmware and re-lock it before sending it back. Google's only requirement is that you factory reset from the settings menu in order to disable factory reset protection. If you fail to do this, there will be problems, but otherwise you should be fine.
Click to expand...
Click to collapse
I see, as i mentioned before, my pc/mac cannot detect my phone anymore. There's something wrong with the usb connection. I dont have access to any commands on adb platform since device cannot be seen.
kismetmookz said:
I see, as i mentioned before, my pc/mac cannot detect my phone anymore. There's something wrong with the usb connection. I dont have access to any commands on adb platform since device cannot be seen.
Click to expand...
Click to collapse
replace the USB cable.
parakleet said:
replace the USB cable.
Click to expand...
Click to collapse
I tried 3x usb2a to usb c without success
i tried usb2a to microUSB+ adapter. no success..
still usb not recognized, NO usb debugging notification/MTP/file transfer options. and only charging..
kismetmookz said:
I see, as i mentioned before, my pc/mac cannot detect my phone anymore. There's something wrong with the usb connection. I dont have access to any commands on adb platform since device cannot be seen.
Click to expand...
Click to collapse
If you explain that to them, it might still be okay. The important part is performing the factory reset from the settings menu.
Try clean the port with some tissue paper. Just push in some tissue paper with a pin, be gentle and don't damage the port. You will be surprised how dirty the port is
Be sure usb debugging is enabled in developer options?
kismetmookz said:
As the written on the title section, my pc/mac can not detect my phone, it only charges it....
Click to expand...
Click to collapse
When you flashed the full image, did you leave the flash-all script alone, allowing it to wipe data? Have you done a factory reset from recovery mode? Google doesn't care if your bootloader is unlocked, but they will make you factory reset the phone before authorizing an RMA. May as well get that out of the way now. Nothing to lose because the data transfer tool will not work anyway if your USB-C port is hosed. Just make sure you have a recent Google backup, and that Photos is sync'd up with all your pictures.
in my case, the phone will be only recognized on a USB 3.0 port.
I had this exact same issue.
Try this If you still have the UsbC to USB connector that came with your phone. Plug in an ordinary flash drive into that and into your phone. You should see a notification that you have a USB connected.
Then unplug that and try to connect to the PC. Worked for me twice when this happened.
Is your USB port clean? When I took my Pixel 2 XL into the sea, afterwards data cables weren't working but it would charge, due to salt water residue. After giving it a good clean it worked again.
Worth a shot just to ensure dirt isn't the issue!
TheSt33v said:
If you explain that to them, it might still be okay. The important part is performing the factory reset from the settings menu.
Click to expand...
Click to collapse
Hi Steeve. Thanks for suggestion. Yes they issued me for a standard RMA because the phone is bought from third party site. btw. i got it working without doing nothing after couple of days.
cescman said:
Try clean the port with some tissue paper. Just push in some tissue paper with a pin, be gentle and don't damage the port. You will be surprised how dirty the port is
Click to expand...
Click to collapse
I did that too in the first two days, and did nothing. I was using anti oxidant sprays.
Nergal di Cuthah said:
Be sure usb debugging is enabled in developer options?
Click to expand...
Click to collapse
It was and it is. But neither the usb mtp nor debugging is showing in the notification center and my pc/mac can't even recognize it.
v12xke said:
When you flashed the full image, did you leave the flash-all script alone, allowing it to wipe data? Have you done a factory reset from recovery mode? Google doesn't care if your bootloader is unlocked, but they will make you factory reset the phone before authorizing an RMA. May as well get that out of the way now. Nothing to lose because the data transfer tool will not work anyway if your USB-C port is hosed. Just make sure you have a recent Google backup, and that Photos is sync'd up with all your pictures.
Click to expand...
Click to collapse
Yes, I did and I didn't edit the BAT file with -w . Thanks for your time on replying on this thread.. The Phone is miraculously working again.. I did too much on the first two days and left it alone when I lost hope with it and it came back today..
tatico28 said:
in my case, the phone will be only recognized on a USB 3.0 port.
Click to expand...
Click to collapse
No mtp? no "Usb Debugging"?