Develop Bugs

Cracked Zenfone 2 Screen, Want to Wipe NO ADB

I cracked the screen on my Zenfone 2 and before I send for RMA, I would like to wipe passwords and sensitive content. I've installed the Intel Android driver as explained in this forum, and attempted to connect via ABD to no avail. I'm not sure if I enabled USB debugging before the drop.
It still shows as a MTP in the device manager, whereas my rooted HTC M7vzw lists as an android device and is able to be seen by ABD. So, I'm trying to tshoot if it's an issue with the driver, or simply that I didn't enable the USB debugging.
I've searched the forum and found similar threads, but haven't found anything the directly addresses this problem. If there has been a link would be appreciated or any suggestions.
I'm running win8.1 and have the latest stock firmware installed on the phone. I've also tried multiple USB ports and cables.
Please help me not to buy another phone,
- Thanks

If the screen is still visible, I would use a USB mouse (using the OTG adapter) to enable USB debugging just in case it wasn't enabled. And if a popups appears when plugging in debugging mode, I guess your only choice is to use a bluetooth mouse to be able to check whatever dialog may appear at the same time you use the USB port to plug it to your PC

rambn said:
I cracked the screen on my Zenfone 2 and before I send for RMA, I would like to wipe passwords and sensitive content. I've installed the Intel Android driver as explained in this forum, and attempted to connect via ABD to no avail. I'm not sure if I enabled USB debugging before the drop.
It still shows as a MTP in the device manager, whereas my rooted HTC M7vzw lists as an android device and is able to be seen by ABD. So, I'm trying to tshoot if it's an issue with the driver, or simply that I didn't enable the USB debugging.
I've searched the forum and found similar threads, but haven't found anything the directly addresses this problem. If there has been a link would be appreciated or any suggestions.
I'm running win8.1 and have the latest stock firmware installed on the phone. I've also tried multiple USB ports and cables.
Please help me not to buy another phone,
- Thanks
Click to expand...
Click to collapse
there are lot of ways,[if u get the 1st way below]
1. get an usb or wireless mouse,connect and do a factory reset
2. directly goto droidboot and use recovery,factory reset
3. connect to PC with fastboot mode and open cmd ,type
Code:
fastboot erase userdata
think these 3 ways are easiest

[Help] Problem connecting OP3 to computer in MTP mode

Hello everybody,
I received my OP3 yesterday and I'm quite happy with my phone, but I'm having an worrying problem with the USB connection. Indeed, I cannot seem to get the USB connection working in MTP mode. In fact, I cannot get anything else working than charging mode.
Things I already tried :
- Enabling USB debugging
- 3 different cables (OP2, OP3, no brand)
- Manually choosing MTP mode in developper options
- 2 different computers
Maybe the most worrying thing is that the Windows device manager doesn't see any device when I connect the phone, not even a device with an error...
I'm really starting to think this is a hardware problem
Please, HELP ! :crying:

Isayaa said:
Hello everybody,
I received my OP3 yesterday and I'm quite happy with my phone, but I'm having an worrying problem with the USB connection. Indeed, I cannot seem to get the USB connection working in MTP mode. In fact, I cannot get anything else working than charging mode.
Things I already tried :
- Enabling USB debugging
- 3 different cables (OP2, OP3, no brand)
- Manually choosing MTP mode in developper options
- 2 different computers
Maybe the most worrying thing is that the Windows device manager doesn't see any device when I connect the phone, not even a device with an error...
I'm really starting to think this is a hardware problem
Please, HELP ! :crying:
Click to expand...
Click to collapse
I had the same issue with my MXP and still have it with my OP. Just can't seem to get my pc to recognize them as storage devices.
A workaround I have found is to boot into twrp, then their recognized immediately and can be used as an external storage device.

I also got 'charging only' mode when I first connected OP3 to my laptop but after changing the settings at developer options I could do the file transfers and all.
I hope some of your privacy setting isn't messing up with it because AFAIK it shouldn't be a hardware problem.

I have the same issue.
---------- Post added at 05:22 AM ---------- Previous post was at 05:15 AM ----------
bruciebabie1963 said:
I have the same issue.
Click to expand...
Click to collapse
I turned off usb debugging and now my computer recognizes my device.

numbere said:
I had the same issue with my MXP and still have it with my OP. Just can't seem to get my pc to recognize them as storage devices.
A workaround I have found is to boot into twrp, then their recognized immediately and can be used as an external storage device.
Click to expand...
Click to collapse
Thing is I cannot unlock bootloader and install TWRP because the USB connection is needed for that
Beside, this is a 2 days old phone, I'm expecting it to work flawlessly...

Isayaa said:
Hello everybody,
I received my OP3 yesterday and I'm quite happy with my phone, but I'm having an worrying problem with the USB connection. Indeed, I cannot seem to get the USB connection working in MTP mode. In fact, I cannot get anything else working than charging mode.
Things I already tried :
- Enabling USB debugging
- 3 different cables (OP2, OP3, no brand)
- Manually choosing MTP mode in developper options
- 2 different computers
Maybe the most worrying thing is that the Windows device manager doesn't see any device when I connect the phone, not even a device with an error...
I'm really starting to think this is a hardware problem
Please, HELP ! :crying:
Click to expand...
Click to collapse
When you connect the phone, Marshmallow by default connects in charging mode.
- Swipe down and you will see USB for charging "Touch for more options"
- Select 'File Transfers'
Transfer files.

white43 said:
When you connect the phone, Marshmallow by default connects in charging mode.
- Swipe down and you will see USB for charging "Touch for more options"
- Select 'File Transfers'
Transfer files.
Click to expand...
Click to collapse
I don't get the pop-up, the phone really does not detect that it's connected to a computer.

Isayaa said:
I don't get the pop-up, the phone really does not detect that it's connected to a computer.
Click to expand...
Click to collapse
That sounds like a hardware problem.
I don't have developer USB debugging mode on or anything.

I have this issue with my op3. Just got it in the post today. My windows 10 pc bleeps when pugged in but does not load a drive. In device manager it shows up as the d drive but not in file explorer. Annoying!

My windows 7 (company laptop) recognised my phone first time and installed the drivers no problem. I had problems with my USB flash drive earlier today until I discovered the hidden enable OTG toggle.
Sent from my ONEPLUS A3003 using Tapatalk

Isayaa said:
Hello everybody,
I received my OP3 yesterday and I'm quite happy with my phone, but I'm having an worrying problem with the USB connection. Indeed, I cannot seem to get the USB connection working in MTP mode. In fact, I cannot get anything else working than charging mode.
Things I already tried :
- Enabling USB debugging
- 3 different cables (OP2, OP3, no brand)
- Manually choosing MTP mode in developper options
- 2 different computers
Maybe the most worrying thing is that the Windows device manager doesn't see any device when I connect the phone, not even a device with an error...
I'm really starting to think this is a hardware problem
Please, HELP ! :crying:
Click to expand...
Click to collapse
I had the same problem.
What I did to fix it was the following steps:
- Disable USB debugging in developer options
- Choose PTP mode in developer options
- Choose MTP mode in developer options
- And Done, my PC now recognize the phone in MTP mode

what i do to fix this
- disable OEM unlocking
- disable developer options
- plug USB (wait for drivers install)
- enable developer options
- enable USB debuging

Gah, having similar problems!
Have tried all the workarounds suggested here, but whenever I plug it in on MTP mode it just shows me the OnePlus Drivers CD Drive.
I have installed the drivers (multiple times) but Windows 10 just won't see the phone when I plug it on MTP mode, just shows me the Drivers CD Drive every single time.
It's recognised as PTP no problems, but no luck on MTP!
Any ideas?
(Unlocked, not yet rooted, on stock firmware)

op3
Hi, i have the same problem, has anyone found any solution for this? It's starting to get pretty irritating... :/

Are you sure youre choosing file transfer mode from the notification area where by default its selected as charging only.

Try this
Hi Guys,
Try halfway inserting the USB cable into your PC, I was having the same frustrating problem and noticed that did the trick for me.
Still trying to figure out why the connectors are not responding when the USB cable is fully inserted, I admit that this is my first device using USB Type-C.

strange
The problem is not getting any better, i simply cannot get windows to even recognise my phone in device manager. Tried it in adb and fastboot, also tried a hard reset but no solution.. I requested a repair from oneplus because i think it cannot be anything else than a hardware problem.

guys i found solution on op3 forum... it worked 4 me with win 10 enterprise... download and install update from here... https://support.microsoft.com/en-us/kb/3099229

This worked fo me: (i'm using Win10)
Device manager, and find "MTP device" then driver update, find on computer, and select MTP USB Composit Device. It works with enabled Debugging, OEM unlock is on too. :good:

white43 said:
When you connect the phone, Marshmallow by default connects in charging mode.
- Swipe down and you will see USB for charging "Touch for more options"
- Select 'File Transfers'
Transfer files.
Click to expand...
Click to collapse
Solved my problem

USB not working

I am rooted with magisk and have had no issues until recently I cannot do any file transfers via USB. I also cannot use fastboot to Flash Android p. I want to unroot and remove magisk and Flash the latest OTA however I can't determine if I can remove magisk and unroot without being able to connect to fastboot. I'm also thinking that I may have to do an RMA. Any thoughts? Has anyone else had their USB data transfer stopped working. I've tried multiple cables, multiple computers and Chromebooks.

pbrian138 said:
I am rooted with magisk and have had no issues until recently I cannot do any file transfers via USB. I also cannot use fastboot to Flash Android p. I want to unroot and remove magisk and Flash the latest OTA however I can't determine if I can remove magisk and unroot without being able to connect to fastboot. I'm also thinking that I may have to do an RMA. Any thoughts? Has anyone else had their USB data transfer stopped working. I've tried multiple cables, multiple computers and Chromebooks.
Click to expand...
Click to collapse
Same here, happened out of the blue last week. No Android Auto and no computer would see it. Still charged but no data. I reset it but no go. I RMA'd and new one is perfect. The thing I knew it was messed up for sure is when I got new phone and you use cable from old one to new one to transfer data and it would not see old phone.

We're you rooted on the device you sent back? I'm worried Google will not approve my return

jawmail said:
Same here, happened out of the blue last week. No Android Auto and no computer would see it. Still charged but no data. I reset it but no go. I RMA'd and new one is perfect. The thing I knew it was messed up for sure is when I got new phone and you use cable from old one to new one to transfer data and it would not see old phone.
Click to expand...
Click to collapse
I flashed the new update yesterday and afterwards I had this exact same issue. the reason why I discovered was I never got the prompt to allow usb debugging I had to enable and disable usb debugging several times while plugging it into the pc and after a few tries I got the message and was able to enable it and then I could use the phone on the pc

I had the same problem but I eventually got it to work again. Heres how:
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 us know if this worked for you.

having the same issue. stock not rooted pixel 2 xl 128gb. is the usb port fried? kind of doesn't make any sense how can it just stop working?? anything else left to try? I spent an hour and half with google support and couldn't figure it out. I can't RMA for warranty b/c I don't have original Order ID. :-/ what do I do?

piotrus22 said:
having the same issue. stock not rooted pixel 2 xl 128gb. is the usb port fried? kind of doesn't make any sense how can it just stop working?? anything else left to try? I spent an hour and half with google support and couldn't figure it out. I can't RMA for warranty b/c I don't have original Order ID. :-/ what do I do?
Click to expand...
Click to collapse
Try cleaning up with a brush. I could be too much dust interfering with the connection.
I read on another thread that someone used post-it strips to do the cleaning.

To close the loop. Cleaning worked. Thank you.

Feb 2019 update kills PC usb connection

Strange issue. After applying the Feb 2019 security patch over air, my phone is no longer recognizing when it is plugged into a PC. I plug into my PC and I get a charge symbol on my battery but no pull down option to switch from charging to USB mode. Things I've tried:
1. New Cable although the wife has a Pixel 3 (standard) that works with this cable and computer just fine.
2. Different PC
3. Toggling USB debugging
4. Changing the USB setting in developer mode to transfer
5. When I plug a USB stick into the phone using the USB-C to USB-A adapter, the phone recognizes the stick and I can browse files
6. "Cleaning" the USB-C port
7. Also booted into safe mode (which I would assume should be like a factory reset) but no USB.
8. Switched between USB 3 and USB 2 ports on the PC.
It seems to me that there's a software issue with the Feb update that messed with the usb settings. I called google and they just want me to factory reset my device before they will transfer me to tech support. I'm avoiding that because I don't want to go back through the time/trouble of resetting up my phone. Any tips/tricks I've missed here?

If you have a Google variant with the BL unlocked, flash the factory image with the -w removed from the flash-all batch file. That way, you won't lose data. If you are on the Verizon variant or don't want to unlock you BL, sideload the OTA from stock recovery. See if it cleans up your issue. Also, sounds like you might have a driver issue on your PC. Easier to fix that first if it is the issue.

I have the February update over the air and I had no issues connecting to my Chromebook (crouton) via USB to pull an APK with ADB. I did have to turn USB debugging back on (not sure if I turned it off or if it was turned off from an update) and change the connection type, it was set to charging only.

More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.

copekyle said:
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
Click to expand...
Click to collapse
Try putting the phone into Fastboot mode and use the command "fastboot devices" to see if it is recognized. If it is, then the problem is on the ADB side, which is part of the Android system.
If it can connect via Fastboot, it's less likely to be a driver issue. You can try "adb devices" too with the phone booted to see if it is recognizing it all. May need to toggle through the various connection modes, I believe I used PTP the last time, but not certain.
As for sideloading, you will need the phone to be recognized by either ADB or Fastboot. You can sideload an OTA update from Recovery with a locked bootloader or as @sliding_billy said you can unlock the bootloader and flash the factory image which is done via Fastboot.
I would also verify that you have the latest version of the Android SDK installed just to cover that base.

copekyle said:
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
Click to expand...
Click to collapse
You don't need to be in file transfer mode to connect via fastboot. Check connection from there after using the combo keys to get into fastboot (power/vol down) for the factory image or one step further into recovery for sideload.

Neither Fastboot devices or ADB devices lists a device. When put in fastboot and recovery, my device manager on either computer does not register that there is a device connected.

copekyle said:
Neither Fastboot devices or ADB devices lists a device. When put in fastboot and recovery, my device manager on either computer does not register that there is a device connected.
Click to expand...
Click to collapse
Sounds like you have attempted everything... New cable (but rereading I don't see where you tried using a C>A cable instead of a C>C and that definitely needs tried). New computer/port/OS. Direct connect to fastboot. I think you are going to need to backup to the cloud (at least you have a functional device with internet) and factory reset the device.
P.S. I just thought about this, but do you have the current platform tools (ADB/Fastboot)? https://developer.android.com/studio/releases/platform-tools.html

sliding_billy said:
Sounds like you have attempted everything... New cable (but rereading I don't see where you tried using a C>A cable instead of a C>C and that definitely needs tried). New computer/port/OS. Direct connect to fastboot. I think you are going to need to backup to the cloud (at least you have a functional device with internet) and factory reset the device.
P.S. I just thought about this, but do you have the current platform tools (ADB/Fastboot)? https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Sadly I don't have a computer with a USB C port. I have been using only cables with C>A. I downloaded the latest platform tools yesterday before trying fastboot/adb. I'm waiting for a call back from Google tier 2 tech support within 72 hours. If anything comes of it, I will report back here.

copekyle said:
Sadly I don't have a computer with a USB C port. I have been using only cables with C>A. I downloaded the latest platform tools yesterday before trying fastboot/adb. I'm waiting for a call back from Google tier 2 tech support within 72 hours. If anything comes of it, I will report back here.
Click to expand...
Click to collapse
Good luck!

No data transfer possible (Pixel 2 XL - PC)

Today I tried to transfer some files from my Pixel to my PC.
After plugging in different cables into different PCs and Ports I only could get my phone to load.
There was no way to change it to transfer mode...
Windows didn't recognize the phone at all.
In the developer options it is already set to data transfer / Android Auto.
I am using the latest December (October) patch.
My final goal was to backup my data and install a different ROM now after there are no more official updates.
Anyone has an idea how to get my phone connected to a PC again? In the past it was working well - but I don't know how long it isn't working anymore.
PS: I already cleaned to USB port of my Pixel.
Thanks a lot!

I just bought a used Pixel 2 XL and have the same 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.
It's got to be a software problem on the phone. 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.