Related
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
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.
my a2 lite does not connet to my pc, I have installed drivers, put it on usb debug, but my pc does not recognize de phone, I have tried different usb ports and cables with no success, it does charge eventually with some cables, but I don't know if this is hardware problem or there is any setting I am missing, it does not give me any choice of chosing the usb kind of conection
it is a new phone just prepped for everyday use, not hacked or modded in any way
USB OTG is working but only reading, I cannot write in external usb drive with es file explorer, or the includer file aplication, it says unsupported operation
any help?
Set hardware id in the adb_usb.ini file perhaps
cpu004 said:
Set hardware id in the adb_usb.ini file perhaps
Click to expand...
Click to collapse
thank you, but I cannot acces from adb as there is absolutely no conection from my computer, it only starts charging but as if it were just a charger, there is no usb mode options avalaible y my phone, and the pc does not recognize anything conected
I have tried to connect with another computer with the same results, it only gets power, but no data comunication whatsoever
as nobody gives any clue or info about some hidden setting, I must assume this is another case of bad quality control in xiaomi products, I will check with the seller
Did you specifically set file transfer mode via the notification drawer or left it on charge only?
cpu004 said:
Did you specifically set file transfer mode via the notification drawer or left it on charge only?
Click to expand...
Click to collapse
the phone does not detect either that it is connected to a computer, so the notification to select the mode of connection does not even show
I have tried usb otg and I can read fine but I cannot write at all in a pendrive
I have installed also an sd card as internal memory and have storage errors all the time so I have removed it
I have tried also conection in fastboot mode but the computer still does not recognize anything connected
I have uses several cables, usb ports and even 2 different pc with same results
My only guess is that there were some hidden config setting that is messing with the phone, that's the reason I am asking before going to the seller.
Seems like a broken USB pin then
cpu004 said:
Seems like a broken USB pin then
Click to expand...
Click to collapse
an usb pin should not affect internal sd memory, and usb does not work like water pipes, one pin data in one pin data out, they need both data pins for reading also, so as it can read from pendrive the problem is somewhere else, not in the connector.
This could be a hardware problem. Have you tried to connect it to another computer?
I have already tried on 3 diferent computers with same results. The only diference so far is that it actually does not read either the content of a pendrive connected through OTG, the first day it read it, now it only detects but reads nothing.
Also when sd is configured as internal memory, instead of reading internal memory, that seems to be the normal result, I can read only the sd card with android file explorers
I have the same problem.
No connection data with pc/mac, it only charges.
I'm italian and like many other italians, I've also the problem with Sim slot 2 with no connect..
robiox said:
I have the same problem.
No connection data with pc/mac, it only charges.
I'm italian and like many other italians, I've also the problem with Sim slot 2 with no connect..
Click to expand...
Click to collapse
It is good to know I am not the only one.
F**k, this phone starts to look like a piece of garbage I dont connect to USB, I dont use SD not 2nd sim, so I did not experience these issues, but, f**k again..
Have you tried rebooting? Press the power button for 15secs. to power it off. Use another cable, use another PC, make sure the cable is plugged in properly... bla bla bla. Oh, have you tried placing the phone into a dry rice bowl? Haha (sorry, I had to). I'm sure you've tried it all.
So, I have not much to say. Only that I had a similar problem with a Moto G after I flashed a LineageOS ROM. It worked fine before, but with the new ROM, the USB didn't work at all (it could only read OTG). It was stuck in the "charging" mode. No notification nor option to turn it to file transfer. The PC didn't recognise it at all, either.
Solution? Initially, I turned on USB debuging option and the PC saw the phone (on windows device manager, it was there, but not on MyPc). It was some advance. I can't remember if adb detected it.
Final solution? Luckily my phone was rooted and had a custom recovery, so I could easily flash the same ROM from the TWRP recovery and everything works fine now.
You might try using Xiaomi's flash tool to try to flash the orginal ROM again IF the phone is recognised by the tool (try if it can see the phone) http://en.miui.com/download-354.html
And I suggest contacting Xiaomi for a warranty claim if needed, 'cause it looks like a harware problem (a pin the the microUSB port issue). But be ready to answer the questions posted above several times haha.
Good luck!
adriakus said:
Have you tried rebooting? Press the power button for 15secs. to power it off. Use another cable, use another PC, make sure the cable is plugged in properly... bla bla bla. Oh, have you tried placing the phone into a dry rice bowl? Haha (sorry, I had to). I'm sure you've tried it all.
So, I have not much to say. Only that I had a similar problem with a Moto G after I flashed a LineageOS ROM. It worked fine before, but with the new ROM, the USB didn't work at all (it could only read OTG). It was stuck in the "charging" mode. No notification nor option to turn it to file transfer. The PC didn't recognise it at all, either.
Solution? Initially, I turned on USB debuging option and the PC saw the phone (on windows device manager, it was there, but not on MyPc). It was some advance. I can't remember if adb detected it.
Final solution? Luckily my phone was rooted and had a custom recovery, so I could easily flash the same ROM from the TWRP recovery and everything works fine now.
You might try using Xiaomi's flash tool to try to flash the orginal ROM again IF the phone is recognised by the tool (try if it can see the phone) http://en.miui.com/download-354.html
And I suggest contacting Xiaomi for a warranty claim if needed, 'cause it looks like a harware problem (a pin the the microUSB port issue). But be ready to answer the questions posted above several times haha.
Good luck!
Click to expand...
Click to collapse
I have done all your sugestions previously, even reseting phone with a new gmail account so no config setting from other phone could interfere, I have also tried fastboot, but although phones goes to fast boot mode the pc does not recognize connection either
it is not an usb pin issue, tried 6 cables, 4 computers, 10 or more usb 2 an 3 ports, I am negotianting in aliexpress a refund, we'll see
If I go into recovery mode with power vol+ a broken android appears.
elsita said:
I have done all your sugestions previously, even reseting phone with a new gmail account so no config setting from other phone could interfere, I have also tried fastboot, but although phones goes to fast boot mode the pc does not recognize connection either
it is not an usb pin issue, tried 6 cables, 4 computers, 10 or more usb 2 an 3 ports, I am negotianting in aliexpress a refund, we'll see
If I go into recovery mode with power vol+ a broken android appears.
Click to expand...
Click to collapse
I don't know if you already did this, but try using a PC with Linux (you can use Ubuntu without installing it on the PC, then install the fastboot package).
Hi,
I had no problem with fastboot and adb with Mac!
Phone recognized by the machine and do transfer boot.img for magisk...
Now I Win!
I can see the internal memory with Android File Transfer (Trasferimento File Android in italian!) - this is the link https://www.android.com/filetransfer/.
My version of Build is V.9.6.8.0.
Solution:
- Connect the phone to pc/mac;
- Go to: Settings -> System -> Developer Options -> Select USB Configuration -> select first "Charge" and then "MTP" (Media Transfer Protocol)
- The system recognize the phone!
[for italian, like me, andare su Impostazioni -> Opzioni Sviluppatore -> Seleziona Configurazione USB -> scegliere "Ricarica" e poi "MTP" (Media Transfer Protocol) ]
robiox said:
Hi,
I had no problem with fastboot and adb with Mac!
Phone recognized by the machine and do transfer boot.img for magisk...
Now I Win!
I can see the internal memory with Android File Transfer (Trasferimento File Android in italian!) - this is the link https://www.android.com/filetransfer/.
My version of Build is V.9.6.8.0.
Solution:
- Connect the phone to pc/mac;
- Go to: Settings -> System -> Developer Options -> Select USB Configuration -> select first "Charge" and then "MTP" (Media Transfer Protocol)
- The system recognize the phone!
[for italian, like me, andare su Impostazioni -> Opzioni Sviluppatore -> Seleziona Configurazione USB -> scegliere "Ricarica" e poi "MTP" (Media Transfer Protocol) ]
Click to expand...
Click to collapse
somehow i was able to connect through fastboot with the help os some advanced users, I unlocked boot and managed to flash original firmware using fastboot mode, the result: no usb connection, no pendrive otg, sd card as internal memory gives storage errors all the time ...
so the phone is faulty, now I am at aliexpress hands claiming for a refund and send back phone
elsita said:
somehow i was able to connect through fastboot with the help os some advanced users, I unlocked boot and managed to flash original firmware using fastboot mode, the result: no usb connection, no pendrive otg, sd card as internal memory gives storage errors all the time ...
so the phone is faulty, now I am at aliexpress hands claiming for a refund and send back phone
Click to expand...
Click to collapse
Where are you from? Where did did you purchase the phone (the actual store, is it in China)? Depending on where are you from and what country did you buy the phone from, by law, you'll get manufacturer warranty. So, any "official" distributor in your country will have to provide a warranty solution for you. If Ali Express is unable to provide you with a solution, look into that.
Let us know how it work out for you
adriakus said:
Where are you from? Where did did you purchase the phone (the actual store, is it in China)? Depending on where are you from and what country did you buy the phone from, by law, you'll get manufacturer warranty. So, any "official" distributor in your country will have to provide a warranty solution for you. If Ali Express is unable to provide you with a solution, look into that.
Let us know how it work out for you
Click to expand...
Click to collapse
I am from Spain, and the aliexpress seller has store in Spain, but you know how chinese vendors act ... no agreement so far, and now aliexpress decides, whenever they turn back to work, because China as you may know is a whole year vacation place for workers ...
Hi
I would appreciate any input/help on this issue.
I bought the Korean Note 10 + 5g exynos (SM-N976N), specifically for the purposes of being able to root it. I would prefer to use the Magisk approach, because I would like to be able to use Google Pay, amongst others
Try as I might, I cannot get my PC to "see" the android phone. I have engaged developer mode, checked USB debugging, checked the the USB connection as MTP mode, and gone through several cables, going by the advice of "experts" I consulted. I even went as far as returning my original phone and buying a new one, again, on the advice of an "expert" who determined that my original phone was faulty (unlikely, since I had literally taken it out of the box and attempted the rooting before trying to load my multiple software). I am using Windows 10, 64k, with all current Microsoft updates.
I have reloaded the Samsung USB drivers, rebooted both the phone and PC several times, to no avail. When I connect, in download mode, the USB cable between the two devices, I hear the "ping" on the PC, indicating that the two have made contact, but then - nothing. I have established that the cable works fine, by connecting my Note 8 to the PC, where it shows up as a device with two drives (int and SD card)
I have installed Magisk on the 10+, and modified the stock ROM with Magisk, and then copied that over to the PC, as advised by the rooting solution; the problem is that I cannot use Odin to flash that modified ROM because Odin does not recognize any phone attached to it!
Help, Please!!
Could be the Odin version your using
Perhaps, I hadn't thought of that. I am using 3.13.1. Do you have a suggestion about using a more stable/useful one? My only issue with your answer is that it's not just Odin that isn't responding- it's the entire computer - it's as if the phone doesn't exist when connected.
I'm guessing you are using a USB 3.0 port on pc? If you have access to USB 2.0 try that....
Next thing I'd suggest (with note plugged in while in download mode)....go into device manager (right click This PC)
Find device under Modem, open properties Ports tab, Advanced Settings and manually change the port setting to a lower port assignment (preferably between 1 & 5). Reboot pc and just for kicks reset the phone into Download Mode again....Give odin a try now.
Hope one or a combination of these methods help.
Sent from my [device_name] using XDA-Developers Legacy app
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.