The touch pro 2 USB socket broke... (the 11 pin one)
and it is out of warranty.
They are demanding $300 to get it fixed.
Does anyone know of some other way I can get this phone fixed at a much cheaper price?!? Please!!
How exactly did it break? Did the whole socket come unsoldered or did the little tab thing just break off? The tab broke off on my old Mogul & I just superglued it back in. VERY carefully. It worked just fine afterward, the tab is just there to support the pins.
If the whole socket broke off, all I could suggest is finding a friend who's really good at taking stuff apart & soldering. I would do it(used to do micro-soldering for Hitachi) but I live in OK.
$300.00...?!?! That's insane...when the same happened to my mda, I purchased a battery charger from cellphoneshop.net, that charged the battery without the phone...I searched their site and was unable to locate one for the tp2
I don't know how big bellevue, wa is, or if its close to a larger metropolitan area. If so, I would look on craigslist and search for "cell phone repair". I had my mda screen repaired by a company I found on there, pretty cheap....
Alright, thanks guys... but is there like a place where I can mail-it in to get the phone repaired? Craigslist isn't really helping. The phone charges, but I can't connect it to the computer via USB or use any headphones. Also, there are other MAJOR problems caused by this broken socket (it won't boot unless I have a USB adapter plugged in, and that it remains in headphones mode). The black clip came off, but it's kinda impossible to glue it back in.
http://cnn.cn/shop/t7373-touch-pro2-rhodium-c-277_815.html
it isnt here right now but try calling them and see if you can get a new port, if the port isnt soldered to the board.
okay so my phone has been fine until yesterday. it keeps randomly opening car mode. its so annoying because i constantly have to close out of it and when i make cars it defaults to speaker phone.
i have looked into this problem and iv seen that this issue is cause by a faulty usb port and i have to get the phone replaced.
i DO NOT want to do that because i am rooted and the newer evos come with 2.3 and i wont be able to root.
any solutions for this?
anyone??????????????
clear the data. if it continues then uninstall and reinstall. but i really have no idea. mine used to do that also but i never used it so i just deleted it.
Your usb port is bad. The phone thinks a car dock is connected because your usb port is damaged.
ugh so i need to get a replacment evo?
i dont want to cause then i cant root the new one.
i had my friend spray air duster in his port and that did the trick for him cuz his was doing the same thing
So i just looked at the forum on this, My phone auto turns on speaker when making or receiving a call, it used to keep putting its self in car dock mode until i deleted the app, i thought it was the end of my problems, It said it was something wrong with the pin connectors, i have insurance, but would i have to pay to get this fixed? my sprint people are really cool, i normally dont have to unroot to get a hardware problem fixed, but never had this happen before, so would you recommend going back to stock for this fix?
Hello all, I have same problem with my SGS 2 after rooting with I9100 XXLPS. Not a great problem, but would be good if something helps us to solve it. Thanks in advance.
Sent from my GT-I9100 using XDA
This is a symptom if a broken usb port. Take it in, they should be able to replace it in store.. No un rooting should be necessary. I've had my digitizer replaced with cm7 on the phone and the guys were playing with it and showing it off
Sent from my PC36100 using xda premium
Its a damaged or dirty MicroUSB port. My Evo has been doing it for 2 years. It gets dusty inside the port, and the dust gets damp (in my situation), which fools the phone into thinking its plugged into a Car Dock, thus the dock mode and the speakerphone. Try blowing the port out with compressed air, or plug/unplug it a few times with a different cable/charger. If it doesn't go away, its the USB port, swap the phone.
Greetings,
My unlocked, rooted, and JB flashed GNEX suddenly will not be detected on any machine I connect it to. XP, vista, W7. It charges fine, and detects as charging when connected to a PC. Machine's will not detect it as even connected. No errors.
I recently had two developments to my device that leave me uncertain as to what might be the cause of this issue:
1. Device went for a short swim. Dried out in rice, but not working properly. Disassembled and bathed in alcohol, then dried again, and it seemed to be revived, with the exception of an extremely short wifi range, both when connecting to an AP, or running as a hotspot.
2. Before the swim, I had recently flashed the Ascent VZ JB rom. I can't recall if I attempted to connect to a PC after the flash.
I have insurance, but would prefer not to use it, if possible.
I have tried fastboot mode, debug on and off with no luck. I should think that on a totally foreign machine, that some sort of detection and driver installation should be intiated, but nothing.
Any ideas of more testing I can do, before writing off the unit and replacing it?
Gary
I've been having issues like this with mine too. Running Xenon HD. USB port seems to be hit or miss the last couple weeks. I'm also contemplating a warranty replacement.
http://forum.xda-developers.com/showthread.php?t=1856164 try that. I had a detection problem. Might not be related but you never know
teamgs said:
Greetings,
My unlocked, rooted, and JB flashed GNEX suddenly will not be detected on any machine I connect it to. XP, vista, W7. It charges fine, and detects as charging when connected to a PC. Machine's will not detect it as even connected. No errors.
I recently had two developments to my device that leave me uncertain as to what might be the cause of this issue:
1. Device went for a short swim. Dried out in rice, but not working properly. Disassembled and bathed in alcohol, then dried again, and it seemed to be revived, with the exception of an extremely short wifi range, both when connecting to an AP, or running as a hotspot.
2. Before the swim, I had recently flashed the Ascent VZ JB rom. I can't recall if I attempted to connect to a PC after the flash.
I have insurance, but would prefer not to use it, if possible.
I have tried fastboot mode, debug on and off with no luck. I should think that on a totally foreign machine, that some sort of detection and driver installation should be intiated, but nothing.
Any ideas of more testing I can do, before writing off the unit and replacing it?
Gary
Click to expand...
Click to collapse
If you haven't already tried this: open the device manager, then connect the phone. Monitor the device manager for newly detected devices. If the PC doesn't detect anything being connected, I doubt there's much you can do.
Thanks everyone, I appreciate the input.
Unfortunately, nothing is detected on any machine. Device manager is empty. Machines that used to detect it don't, and new machines don't either. I am in I.T.,...and have way to many PCs for my own good. Oh yes...not detected in Ubuntu either.
I disassembled my phone again today, and rechecked the wireless antenna, and the USB port, but still no luck. I think I may just have to pony up the $100 and use my insurance.
Thanks again,
Gary
teamgs said:
Thanks everyone, I appreciate the input.
Unfortunately, nothing is detected on any machine. Device manager is empty. Machines that used to detect it don't, and new machines don't either. I am in I.T.,...and have way to many PCs for my own good. Oh yes...not detected in Ubuntu either.
I disassembled my phone again today, and rechecked the wireless antenna, and the USB port, but still no luck. I think I may just have to pony up the $100 and use my insurance.
Thanks again,
Gary
Click to expand...
Click to collapse
This might be worth consideration, too:
http://www.ifixit.com/Device/Samsung_Galaxy_Nexus
Thanks strumcat, I found that link this morning. Great minds think alike! I am sourcing the part right now. I have disassembled my phone about 15 times since its bath.
Gary
Check and see if the device can be seen by adb, assuming you have the Android SDK and adb drivers set up.
If it's not detected, as stated above, there may not be a whole lot you can do.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the info. No luck with ADB.
If I purchase the micro USB board, I am out $40, with no guarantee it will resolve the issue. Then I still have the wifi range issue that may or may not be resolved by replacing another module for about $40.
Since that I will be most likely out $80 to possibly get it back to perfect, I think I am going to just shell out the $100 and get a replacement. Hopefully, it will be new one, not a refurb.
Gary
Sometimes when I have USB debugging enabled, my PC does not detect my phone. I have to disable USB debugging before connecting my phone, it detects it and then enable USB Debugging while the phone is connected. That usually works for me.
vG
teamgs said:
Thanks for the info. No luck with ADB.
If I purchase the micro USB board, I am out $40, with no guarantee it will resolve the issue. Then I still have the wifi range issue that may or may not be resolved by replacing another module for about $40.
Since that I will be most likely out $80 to possibly get it back to perfect, I think I am going to just shell out the $100 and get a replacement. Hopefully, it will be new one, not a refurb.
Gary
Click to expand...
Click to collapse
It will be a refurbished one. Why don't you just drop carrier insurance and pull a "stand alone" policy with whoever does your auto/home/renters insurance? Costs next to nothing really. Cheaper than carrier. Added bonus...? They send you a check. For actual replacement costs. After a year of premiums and the 150 deduct thru carrier its pretty much $300 for a repaired phone. You paid less for a new one. Yearly, the stand alone is half to 3/4 the price of carrier. Deduct varies, but its less also. And its actual price to get new phone. If comparable one is 800..check for 800. Ask your insurance guy about it. If no stand alone, get renters insurance for like 6$ a month. Still cheaper.
Tried Everything, Found the solution. (I will post this elsewhere, too)
So, I have spent two days with this problem. I've searched the entire godamn internet... only to find a surprising solution.
Regardless of what I had tried, my computer refused to detect my GNex. Toggled MTP, etc, Retoggled USB debugging, all that.
No matter what I would do, the PC would classify it an 'unknown device' !!!
What I had tried:
-Deleting all drivers, tried different driver sources (ex . Samsung's driver instead of Google's SDK, and even tried universal ADB drivers)
- Ensuring 'force fast charge' was disabled in both my kernel settings. (even disabled it in terminal emulator)
- Factory reset device (and quickly restored it back to the way it was, as this was not the problem)
-Three different PC's (Two Windows 7 PC's and 1 Ubuntu)
-Deleting all USB drivers on my computers and then attempting to connect via MTP or ADB, nothing.
-Even stepped through some drivers guides, including Nexus root toolkit (Even tried all 4 solutions, out of frustration).
My friend then suggested that maybe my USB internal port was dirty. I looked at it under a magnifying glass and to me, honestly it looked clean. I could clearly see the terminals,. Again, out of frustration, I tried this as a shot in the dark ------ I took a dry, new clean artists' brush and I brushed it out.
VOILA. I plug it in, and it installs the ADB interface first shot.
I really wasn't expecting this. I guess it should be expected , I carry this phone around in my pocket and it goes through hell, but one would expect charging problems as well. I guess a piece of pocket crud just so perfectly covered up the Data +/- in the middle of my USB port.
Try this, my friends. Having a non-functional USB port on a phone that screams "root me" is the most frustrating thing.
NOW IT'S TIME FOR PARANOID ANDROID 4.0
Jkolorz said:
So, I have spent two days with this problem. I've searched the entire godamn internet... only to find a surprising solution.
Regardless of what I had tried, my computer refused to detect my GNex. Toggled MTP, etc, Retoggled USB debugging, all that.
No matter what I would do, the PC would classify it an 'unknown device' !!!
What I had tried:
-Deleting all drivers, tried different driver sources (ex . Samsung's driver instead of Google's SDK, and even tried universal ADB drivers)
- Ensuring 'force fast charge' was disabled in both my kernel settings. (even disabled it in terminal emulator)
- Factory reset device (and quickly restored it back to the way it was, as this was not the problem)
-Three different PC's (Two Windows 7 PC's and 1 Ubuntu)
-Deleting all USB drivers on my computers and then attempting to connect via MTP or ADB, nothing.
-Even stepped through some drivers guides, including Nexus root toolkit (Even tried all 4 solutions, out of frustration).
My friend then suggested that maybe my USB internal port was dirty. I looked at it under a magnifying glass and to me, honestly it looked clean. I could clearly see the terminals,. Again, out of frustration, I tried this as a shot in the dark ------ I took a dry, new clean artists' brush and I brushed it out.
VOILA. I plug it in, and it installs the ADB interface first shot.
I really wasn't expecting this. I guess it should be expected , I carry this phone around in my pocket and it goes through hell, but one would expect charging problems as well. I guess a piece of pocket crud just so perfectly covered up the Data +/- in the middle of my USB port.
Try this, my friends. Having a non-functional USB port on a phone that screams "root me" is the most frustrating thing.
NOW IT'S TIME FOR PARANOID ANDROID 4.0
Click to expand...
Click to collapse
Wow thanks a lot man :good:
save my time from usb connecting problem :victory:
eventhough i'm using my own way: blown from the mouth
Thanks!!!!! Good!!
thanks! that helped a lot
So dropped my phone, screen cracked(The Plexiglas had enough and couldn't save it this time) at first the top half of phone was working but on the side whatever liquid solution was used started leaking under the screen, screen turned blue purplish then black and eventually covered 95% of the screen. spent hours trying to at least remote into it but with debugging not enabled and it seems impossible. Tried to cast it but the cast option is on the side of the phone that the touch screen is not working. Tried using data recovery to at least recover my data i can't find a legit one to use, they one that seems legit don't have oneplus device as an option. Can try and find a data recovery specialist but i know they will charge me out the a** for it and i have sensitive info and such and not really all that comfortable with living data with a random person. Can anyone help or have any suggestions? am running out of hope at this point and if i can't get anything here then will have to come to grips with it. if anyone can suggest a way to enable debugging am all ears....or eyes in this case.
If I were in your situation I would replace the broken parts and get my phone up and running. You can buy low quality replacements to make it work if your only aim is to get your data out. I couldn't read the whole thing with all my attention so there might be things that I missed. As I understood your screen is the only problem. You can find a cheap screen and plug that into your device. Another option might be (I don't know if this will work) buying a Type-C to HDMI adaptor to plug your phone to a display. With that you don't need to wirelessly cast you can just use a cable. Better yet you can buy a Type-C hub while you're at it and connect a mouse and a keyboard to do everything you need to do. But I don't know if the HDMI option will work.
EDIT: This guy makes it happen. I don't know if OP will support it. If you buy a Type-C hub with USB ports and HDMI port, you can use your phone as if it never broke, get whatever you need to get out of it.
Video doesn't wanna be on XDA for some reason
https://www.youtube.com/watch?v=3J10_VTU3bc