Alright to start I had some previous issues with this phone unable to charge. Which I am hoping the case isn't I destroyed USB input. But for starters I have a EVO Revolutionary Supersonic S-Off. Recently rooted very fresh noob. And I installed my first ROM MIUI with an iPhone theme I was unable to connect to my computer I quickly realized. I restored my phone and tried to connect as such but no good. I even went into recovery and mounted my USB storage under my Clockwork Mod Recovery. Still no change. Before I rooted my phone I had some minor difficulties with mount my phone via USB just to even charge, But as I plugged my phone in today I am not able to mount storage however I am able to charge my phone with no problems whatsoever. I am current installing CyanogenMod I believe 7.2.0 to see a if there is a change. So am I able to install a missing driver or anything of that sort on my phone or am I facing a physical issue?
Try using a different USB Cable. Alos try to make sure it's a real HTC USB Cable. The knock-offs sometimes cause issues like this. The other thing you should do is Update your HTC Sync Drivers. You can download them HERE. Make sure you read before you download, so that you do not download the wrong thing . Also go into Menu - Settings - Applications - Development. Make sure USB debugging is checked.
I used 2 USB cables that I had laying around. One is a cable that originally came with the phone the other is Samsung. And I'd have to revert back to stock in order to get those updates? And if I do would I be able to go back to my Cyanogen Mod 7.1 I installed 7.2 and it had major flaws in its ability to access the playstore.
just as a side note the usb port is known to break on the evo. it did on mine
Ive also had a broken USB port on my Samsung intercept I believe it was.
Related
Hey there.
Ok I have a problem. I have had my touch pro 2 for about 6 months now and i am really happy with it, but recently i have ran into a problem.
My phone won't connect to my computer anymore! Not just my computer... no computer at all. Not just activesync, no, it doesn't recognise it at all, not even as a disk drive.
I doubt its the cable because it does charge, and i have tried another cable (not a htc cable but its a cable with the same plug, its from my external harddrive) and it still didn't work.
I also tried a hard-reset on my phone, but still... nothing.
Ive read somewhere that you should push the usb connector a bit up, i did that, but nothing (now the usb connector seems wiggly... glad it still charges though) i have no idea what it could be and i thought i'd post here first before going back to the dealer with it. Because without usb connection i can't install costum roms and that we wouldn't want that, do we?
Well, hope one of you guys can help!
That's very strange I have had it once, but that was due to the rom I used. I flashed another rom and it worked again.
What you could try is to download a new rom and put it on your sd car using this:
http://www.julien-manici.com/windows_mobile_wifi_remote_access/
This let's you put stuff on your mobile using wifi. It's worth a try.
But you have to install roms directly from your pc to your phone, while being connected to USB right? The standards htc roms for example can only be installed that way i think... or can you also copy the .exe to your device and run that?
i'll give it a go when i get home. Thanks =]
I am having the same issue here. All of a sudden my PC or Laptop doesn't see the phone at all but it does charge with no issues. When I plug it in I don't even get the sound that the PC knows something was jut plugged into it.
go to settings - connection - usb to pc - untick the enable faster synchronization box
that should do it
As long as you have Hard SPLed your Rhodium you should be able to use the sd card method to install a rom instead of using the PC and usb connection.
You copy the rhodium.nbh file to the root directory of an sd card formatted FAT32 and then boot into bootloader - volume down and power button when off.
Follow the onscreen prompts...
Cheers...
This sounds familiar - http://forum.xda-developers.com/showthread.php?t=741406
Lennyz1988 said:
That's very strange I have had it once, but that was due to the rom I used. I flashed another rom and it worked again.
Click to expand...
Click to collapse
What's interesting with my Tilt2 (not the OP) was that I wanted to flash my ROM with the new AT&T "unofficial" ROM and that's when I found out I couldn't tether. I basically just wanted to tether my phone so I could put that new ROM onto the phone to see if I could make it more reliable and faster. Sigh.
it actually might be the cord...
The same exact thing happened to me... my phone charged with the cord but no computer recognized it...
I bought a new usb cable from radio shack and viola it worked again... so I advise u just trying a new one and if it doesn't work take it back... but try the unchecking the "check for faster sync" box first like someone said bc that do stop it from being recognized sometimes...
mr_sheen said:
go to settings - connection - usb to pc - untick the enable faster synchronization box
Click to expand...
Click to collapse
Yes, this has (almost) always fixed the issue for me. Somehow WDC becomes blind to new device inserts after you plug-unplug them several times.
Slow but stable is better.
I have installed and reinstalled the samsung windows drivers about four times.
My phone has not yet been activated and I'm not sure I'm going to attach it to service for the foreseeable future instead of possibly using it as an ipod touch with a keyboard.
I have connected the phone to my laptop one time. I feel asleep with the phone searching for drivers (the drivers had already been installed but the status bar message said it was searching anyway) and when I woke up it seemed fully connected. I was able to cwm3 root the phone but bricked it I think by putting an ext4 filesystem on without moving immediately to an ext4 rom.
I've restored it to stock and through wifi updated it over the air to ec05
Ever since then I have never been able to connect using any of the usb ports, trying two different usb cables, the oem and a generic micro-usb cable and using either windows vista or ubuntu on this computer.
Clockworkmod reports that the phone is not connected and I am not able to see the phone as a hard drive when I set it to mass transfer mode.
In download mode, odin is able to communicate with the phone reliably.
I've repeatedly tried all ##8778# settings and I've set debugging mode off and on. Device manager shows that the phone is connected to port COM7.
Is it possible that the activation program is preventing the USB connection? I would think not because the activation status has not changed since the one time it did connect, but I'm at a total loss for any explanation.
My next step is to try another computer but I don't have one handy.
Is it possible to root a phone only through odin, or to put a file onto the sd card that can root without the use of the computer?
garyf said:
I have installed and reinstalled the samsung windows drivers about four times.
My phone has not yet been activated and I'm not sure I'm going to attach it to service for the foreseeable future instead of possibly using it as an ipod touch with a keyboard.
I have connected the phone to my laptop one time. I feel asleep with the phone searching for drivers (the drivers had already been installed but the status bar message said it was searching anyway) and when I woke up it seemed fully connected. I was able to cwm3 root the phone but bricked it I think by putting an ext4 filesystem on without moving immediately to an ext4 rom.
I've restored it to stock and through wifi updated it over the air to ec05
Ever since then I have never been able to connect using any of the usb ports, trying two different usb cables, the oem and a generic micro-usb cable and using either windows vista or ubuntu on this computer.
Clockworkmod reports that the phone is not connected and I am not able to see the phone as a hard drive when I set it to mass transfer mode.
In download mode, odin is able to communicate with the phone reliably.
I've repeatedly tried all ##8778# settings and I've set debugging mode off and on. Device manager shows that the phone is connected to port COM7.
Is it possible that the activation program is preventing the USB connection? I would think not because the activation status has not changed since the one time it did connect, but I'm at a total loss for any explanation.
My next step is to try another computer but I don't have one handy.
Is it possible to root a phone only through odin, or to put a file onto the sd card that can root without the use of the computer?
Click to expand...
Click to collapse
This thread had a pre-rooted EC05 that you can flash through Odin
http://forum.xda-developers.com/showthread.php?t=1021305
budderocks said:
This thread had a pre-rooted EC05 that you can flash through Odin
http://forum.xda-developers.com/showthread.php?t=1021305
Click to expand...
Click to collapse
Thanks. I'm on ec05 now, so I'm OK with that. I'd like to root either with or without resolving the usb connection issue.
Is that possible at all?
garyf said:
Is it possible to root a phone only through odin, or to put a file onto the sd card that can root without the use of the computer?
Click to expand...
Click to collapse
budderocks said:
This thread had a pre-rooted EC05 that you can flash through Odin
http://forum.xda-developers.com/showthread.php?t=1021305
Click to expand...
Click to collapse
garyf said:
Thanks. I'm on ec05 now, so I'm OK with that. I'd like to root either with or without resolving the usb connection issue.
Is that possible at all?
Click to expand...
Click to collapse
While it isn't JUST a root that you are doing, as stated by budderocks, you can flash the pre-rooted EC05 tar file through Odin, although it will require you to reinstall any apps you currently have. This will start you out with either a stock(ish) setup, with root already included (not sure about Clockwork though), or you can use the one modified for the ext4 filesystem with CWM 3.0.0.6 included which will convert it to ext4 the first time you boot into recovery.
garyf said:
I have installed and reinstalled the samsung windows drivers about four times.
My phone has not yet been activated and I'm not sure I'm going to attach it to service for the foreseeable future instead of possibly using it as an ipod touch with a keyboard.
I have connected the phone to my laptop one time. I feel asleep with the phone searching for drivers (the drivers had already been installed but the status bar message said it was searching anyway) and when I woke up it seemed fully connected. I was able to cwm3 root the phone but bricked it I think by putting an ext4 filesystem on without moving immediately to an ext4 rom.
I've restored it to stock and through wifi updated it over the air to ec05
Ever since then I have never been able to connect using any of the usb ports, trying two different usb cables, the oem and a generic micro-usb cable and using either windows vista or ubuntu on this computer.
Clockworkmod reports that the phone is not connected and I am not able to see the phone as a hard drive when I set it to mass transfer mode.
In download mode, odin is able to communicate with the phone reliably.
I've repeatedly tried all ##8778# settings and I've set debugging mode off and on. Device manager shows that the phone is connected to port COM7.
Is it possible that the activation program is preventing the USB connection? I would think not because the activation status has not changed since the one time it did connect, but I'm at a total loss for any explanation.
My next step is to try another computer but I don't have one handy.
Is it possible to root a phone only through odin, or to put a file onto the sd card that can root without the use of the computer?
Click to expand...
Click to collapse
I have been through this myself and came short of beating my head against a wall before reading that it "may" be a cable issue.
Well, after tyring everything else, (because it couldn't be something as simple as changing to a different cable, right??!!) I pulled out an old cable from my Blackberry days and BAM - my laptop searched for and loaded the needed drivers and sees my phone everytime I plug it in now. I have also used a cable from a friends phone (not a Blackberry) and my laptop still sees the phone so I'm not advocating for Blackberry cables specifically.
Bottom line is - the Samsung cable is a piece of crap. It may work for a day or a month, but it will soon (for 98% of Epic owners) become nothing more than a charging cable before long.
Try using a different cable (not a Samsung model ) and see if that works. If so, then ODIN/one-clicks become your best friend(s)!!
Hope this helps!
-J
I used to be able to plug my phone into my PC and slide down the notifications to enable a USB connection but I'm unable to anymore.
I checked that debug is on. I've even tried via the Wifi Settings USB Connection method. The phone will charge but is not seen by the PC. I've tried other PCs and other cables. It doesn;t show up in Device manager and I've also tried the windows drivers for the phone.
The only thing that has changed in the past month or so is that I replaced my Clockwork Recovery module with the stock recovery module and my phone is no longer rooted. Any ideas anyone?
ingrouille said:
I used to be able to plug my phone into my PC and slide down the notifications to enable a USB connection but I'm unable to anymore.
I checked that debug is on. I've even tried via the Wifi Settings USB Connection method. The phone will charge but is not seen by the PC. I've tried other PCs and other cables. It doesn;t show up in Device manager and I've also tried the windows drivers for the phone.
The only thing that has changed in the past month or so is that I replaced my Clockwork Recovery module with the stock recovery module and my phone is no longer rooted. Any ideas anyone?
Click to expand...
Click to collapse
Just enable USB storage before plugging in
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Like I said I tried the Mass Storage connection method via the menu in Wifi Settings. The onscreen instructions say to enable then to plug in. Still get nothing.
Try reinstalling the driver that might do the trick. I am having the same issue but I am running the unofficial cm9.. good luck to us both and is it the same cable u always been using cause I bought 2$ cable off eBay it only charges no USB connection
Sent From Galaxy Bigger Than Yours.
I tried to re-install drivers and I'm using a known working cable - the one that came with the phone.
It really is strange. The only thing that has happened recently is my phone was rooted with Clockwork Recovery and then I reverted back to stock.
I'll see what happens after the ICS update comes from Telus next month, I guess.
Not a big deal as I can use AirDroid to transfer stuff over wifi.
Since rebooted a couple times now everything is working. I also had a problem with the lock screen rotating and phone defaulting to speakerphone. everything is back to normal now but i wish i knew what caused it.
I've been running CyanogenMod 10.2 on my rooted HTC One for a good long while now. Since the ROM worked so well, I never had the need to connect the phone to a computer via USB in quite some time. A few months ago, when I attempted to transfer some photos, I ran into a weird and frustrating road block; my phone is simply not being recognized by any computer <see here>
I have updated all drivers
I have enabled debugging in Developer Options
I have tried rebooting Fastboot in bootloader
I have tried using the toolkits
I have tried everything I think I know
The weird part is that the phone charges via USB connected to the computer.
Since it didn't effect much, I just figured it was a glitch and I never ran into a problem again--that is, until today. I hadn't used my MHL adapter with the HTC One (only my GNexus), but after reviewing an intended installation of a Pioneer Appradio, I wanted to ensure that my One would work with the MHL. Hooking up my One to the Samsung MHL adapter (and power supply of course), I get no display on my television.
I am now beginning to wonder if the USB port is damaged. Visual inspection doesn't reveal anything, but I am curious if anyone has had this problem and would appreciate any help. Is there any way to test if I've fouled up the port?
Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?
cmlusco said:
Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?
Click to expand...
Click to collapse
No and no
I installed Flashify and did install CWM 6.0.4.7 to see if it would help, but to no avail
Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.
cmlusco said:
Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.
Click to expand...
Click to collapse
I have tried adb, but the device never is recognized.
I'm currenty transferring my TWRP backup via WiFi.
I planned on switching to CM11 and see if I can't get it to work after that.
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.