June 30th, 2011, 03:05 PM
Join Date: Apr 2011
Carrier: Not Provided
Thanked 0 Times in 0 Posts
Something strange happened just now that may hold a key for some. Not sure how to explain this yet but the cable started working when the plastic cover around the jack fell off. Unplugged it, reassembled it, and plugged it back in "USB device not recognized". Unplugged it and pulled the cover back off (the two small pieces of black plastic that you grab when you're plugging the USB cable in your phone), plugged it back in and it recognizes my phone.
Now I see no obvious reason why this would be. Maybe in some of these cables the wires are too close with the cover on and a short exists that we don't notice. It still charges but Windows 7 doesn't like it.
Whatever the case (no pun intended), looks like I'm going to revisit rooting my phone, if for no other reason than to see what it will run. Rooted my 2.1 VM Intercept before and the 2.2 OTA update bricked it because I left the custom kernel on it. Yeah I know. Oooops.
Virgin Mobile Samsung Intercept with Android 2.2.2
Windows 7 Home Premium SP1
Devices and Drivers say:
Android ADB Interface Driver Date 8/11/2009 Version 18.104.22.168
Android UMS Composite USB Device Driver Date 6/21/2006 Version 6.1.7600.16385
Not sure where these drivers came from at this point. I tried rooting that 2.1 phone several times in Jan with the USB cable working then not working then working then not, going through each of the methods. Finally z4root worked. Wish that still worked on 2.2.2. Gonna have to look into what's behind that method.