Related
Alright this is gonna sound stupid, but I've done my looking around already. It's the same ol' Windows 7 USB issue that many people have had. I plug my phone in and I get an error message regarding it not being recognized etc...
The thing is...I've been using this computer for my dev'ing for like 6 months now without a single issue after the original driver work around. Haven't loaded any roms or anything for a couple months. ****, havent even plugged my phone into my computer at all. Nevertheless, it doesn't work anymore and I've done all the steps to try to fix it. Removed all drivers, downloaded latest driver (64 bit), updated, manually updated, etc... I've pretty much tried everything.
I saw a post regarding a bad power/date cord and that being an issue. My cord is sorta frayed at the usb connector, but seems to work fine so I really don't think that is it.
The only other thing I've seen is editing my registry. It's not that I'm worried about doing it, it just says it's a bit time consuming and I'm not positive it's the answer I'm looking for.
All I want to do is update to stupid CM 6 and sure enough my computer is laughing in my face. So annoying.
Any advice or help is much appreciated.
Try deleting all HTC drivers and reinstall them. I'm running Win7 Home Premium 64-bit and have never had this issue. Hope this helps!
Sent from my CricKet Hero using XDA App
Try other usb port or replace the usb cable
Sent from my HERO200 using XDA App
Why not just dl on your phone and flash via recovery? It's not the fastest option, but it is faster than a pc that won't recognize your hero.
Sent from my CDMA Hero. I got some hot Froyo on Hero action here!
I'd definitely cover the bases with the USB cord, I've had 3 of the stock cords, all have gotten "frayed" at the USB connector and have stopped working for me numerous times.
edIT: Also, try removing other USB devices or switching ports. It may not be receiving enough power.
Shots in the dark, but have proven to be the cause of the problem enough times to warrant an extra 5 minutes troubleshooting.
I had a hassle getting the Hero connected to Windows 7. I did so many things that I can't remember exactly what made it work in the end.
These are among the things I tried:
Switching USB ports. (Plug directly into machine.)
Installing and running sync (HTC provided Outlook sync).
Uninstalling android device (especially the unknowns) and updating drivers from Device Manager.
Googling the web for different versions of the USB driver.
On my system, when I plug the HERO to the computer, it shows up in three places under Device Manager:
Android USB Devices (HTC.Corp 6/10/2009 2.0.7.1 driver)
Disk Drives (microsoft driver)
Portable Devices (microsoft driver)
I hope some of this helps!
thesubliminaljuggalo said:
I'd definitely cover the bases with the USB cord, I've had 3 of the stock cords, all have gotten "frayed" at the USB connector and have stopped working for me numerous times.
edIT: Also, try removing other USB devices or switching ports. It may not be receiving enough power.
Shots in the dark, but have proven to be the cause of the problem enough times to warrant an extra 5 minutes troubleshooting.
Click to expand...
Click to collapse
dynamicpda said:
I had a hassle getting the Hero connected to Windows 7. I did so many things that I can't remember exactly what made it work in the end.
These are among the things I tried:
Switching USB ports. (Plug directly into machine.)
Installing and running sync (HTC provided Outlook sync).
Uninstalling android device and updating drives from Device Manager.
Googling the web for different versions of the USB driver.
Click to expand...
Click to collapse
That reminds me... When I first got Win7, I had trouble getting it to recognize my Hero as well. After some googling, I remember doing something like downloading both the Win7 and the WinVista drivers and replacing some of the Win7 drivers with a few of the WinVista drivers and then rebooting and that got my computer to recognize my Hero.
Not sure if you could find the same thing, but worth a shot.
Try the advice in this thread, the part about installing HTC Sync and getting it working:
http://forum.xda-developers.com/archive/index.php/t-659888.html
I hate to be the bad one but this is in the wrong section..belongs in Q&A section
Sent from my HERO200 using XDA App
Sorry!
I actually thought about that immediately after posting. Was browsing mulitple forums and just slipped my mind. If admin wants to move it, it's not a problem.
I'll investigate the usb ports. Shortly after discovering it was magically not recognizing my phone, a bunch of my usb peripherals stopped working. And upon reboot, actually reinstalled some of them.
I guess it could def still be the cord, too. Although, it charges fine.
And if it comes down to it, I'll just do it ota. Haven't really looked into it, but apparently it's possible. And at this point this usb crap is so annoying, it sounds like a great idea.
I've removed all drivers, all anything htc, and still can't even install the driver. Even if I point directly to it via "have disk", it gives some error about having the correct driver. I've downloaded mulitple drivers from multiple places, as well.
Thanks for the advice. I'll try a few more things and be in touch.
If you can, try it on another computer. It could definitely be the USB cable if it has been working and now isn't. It can still charge but not have data work because they use different parts of the cable
I am having issues with my Captivate's micro-USB port being loose. This is my second Captivate, and although it's still under warranty, the first one was RMA'd with the same issue. I never drop the phone while charging, etc, and I've tried multiple chargers so I really can't see why this would be happening. Both phones were 1008 versions, not sure if the 1008 is known to have this issue, or if I just have horrid luck. If anyone here can solder / fix the phone, I'm hesitant to go to AT&T again, as last time they made me go to the store and have the person working there verify that the USB port was not broken (luckily it still charged if you held it a certain way, and even more luckily I was able to flash stock before returning it!). Anyways, this phone is a refurb, and I did call and almost get it replaced as soon as I got it, as it had this issue slightly upon arrival, but decided it would be a hassle. It's only been about a month since the RMA, so I'm pretty sure that if I try now, they're going to get very mean about it, and possibly try and send me a bill for the phone, not to mention, the guy at the AT&T store will probably think something is up.
Any ideas are welcome, I love my Captivate, and I was just getting into develping on XDA :S
Sent from my Cappy using XDA Premium App
I actually found a fix to my issue. I actually was looking at it one day, and figured that in theory, it should be easy to fix, so I (CAREFULLY!!!) took a small knife I had and gently bent the inner part of the port up just a tad (it looked like it was too far down, and yes, I know it's supposed to be far down, but not that far), and it actually worked perfectly.
Thats weird... It kinda has to be what you're doing with it, since mine doesn't even have an irregular slight wiggle.
Obviously it could be just your luck but i doubt it.
edit: and who cares if the att dude thinks somethings up... its your $500..
Like I said, the second one actually had the issue upon arrival, but it was barely noticeable (the USB port would work, but if you moved the phone a lot, etc, it'd disconnect, then reconnect). I called in and talked to them, but decided not to RMA because it'd be a pain (in hindsight I should have...), and the problem just got worse.
Is the port internally lose? Or just when you plug a cable in it wiggles alot? Ive heard about people stretching the casing inside the port from alot of flashing (plugging in the usb). But if the hole port moves inside the phone thats no good lol. You should try to locate a nearby device service center and show them the problem and make sure you walk out with refurb thats fine. Dont worry about the people at atnt questioning it. Hell I use to walk in and just say "gps dosent work" and they would switch it out no questions.
What you said makes sense, the port looks like it's pretty sturdy, it's just that the cable wiggles a LOT, and it makes it hard to get it to even register.
I had the same issue but a new cable solved it
Sent from my samsung captivation
erraz said:
I had the same issue but a new cable solved it
Sent from my samsung captivation
Click to expand...
Click to collapse
I also had this issue, i opened up the stock Samsung Cable end to find that two of the four wires had insufficient strain relief and broke off at the solder joints
Oddly enough I had issues with the first cable as well, but I replaced it, and have tried others from my current.
So my USB port is being a little temparmental. It likes to charge only in a certain position. When playing music it does the same thing. Odin same thing. YOu get the idea. Obviously a loose connection inside the phone. Anyone every rip one of these things open and resolder this component? It's only a matter of time before it fails completely so I figure if no one else has done it I might as well give it try. Either that or get more batteries and a charger but that might hose me for Odin!
Have you verified it's not the cable? I had to replace one due to weird connectivity issues.
Sent from my SGH-T959V using XDA App
While your USB port still works, you should probably Odin a stock ROM and send it back to T-Mobile.
It would suck if your USB port completely died and T-Mobile won't replace your phone. It happened to one of the members on this forum. I forgot his name though.
Cables not the problem. It's the port itself. As far as TMOB goes no way to send it back to them. I got out of my contract a month and a half ago and switched to ATT. I like taking stuff apart and trying to fix it so worst case I try and kill the phone. Best case I fix it. Just looking to see if anyone here has ever ripped this thing open. Advice or tips would be great. Obviously I'm not to worried about voiding the warranty.
You could try the Vibrant and i9000 forums, I guess? The Vibrant community has opened their phone to install a FFC, and they might have come across the USB port. It might be similar to the SGS4G.
Just a suggestion. *shrug*
bkoon, that is a really good idea. i the vibrant and 4g have the same chasis, i think. you should be able to follow the video guides on how to add the ffc to the vibrant and be able to resolder the usb port. but you have to be careful with the soldering (im not sure how good you are with it), that could short circuit some things in the phone.
Thanks for the suggestion bkoon. And jager I know how to solder pretty well. Hopefully get around to it this weekend.
bkoon1218 said:
While your USB port still works, you should probably Odin a stock ROM and send it back to T-Mobile.
It would suck if your USB port completely died and T-Mobile won't replace your phone. It happened to one of the members on this forum. I forgot his name though.
Click to expand...
Click to collapse
That would be me. I managed to hold the plug just right long enough to stock get to KD1, and the second trip to T-Mo was successful. $20 processing fee, and the phone arrives tomorrow.
Back when I had a Blackberry Curve, I found a shop to replace the Mini-USB for about $65. That was my next step.
Please let us know how it goes! I'm sure we're curious as to how the insides will be like.
Good luck!
brutuspa said:
That would be me. I managed to hold the plug just right long enough to stock get to KD1, and the second trip to T-Mo was successful. $20 processing fee, and the phone arrives tomorrow.
Back when I had a Blackberry Curve, I found a shop to replace the Mini-USB for about $65. That was my next step.
Click to expand...
Click to collapse
Glad to know things worked out for you.
http://www.ifixit.com/Teardown/Samsung-Galaxy-S-4G-Teardown/4977/1
I know Google is tough to use sometimes so I thought I'd help
avrillapete said:
http://www.ifixit.com/Teardown/Samsung-Galaxy-S-4G-Teardown/4977/1
I know Google is tough to use sometimes so I thought I'd help
Click to expand...
Click to collapse
I've used ifixit numerous times. Fixed my laptop and my friends laptop. Thanks for the link though I would of never been able to find such a site on my own. Must be great to be that smart.
I was given an HTC Incredible the other day, and I quickly found out that the digitizer was non-functional, so I took it apart and found obvious liquid damage inside. Several areas of the board were crusted over with what I assume to be residue from the evaporated liquid. I remained hopeful that the only problem was a dead digitizer, but after carefully cleaning up the board, I noticed some scorched resistors near the digitizer's ribbon connector on the motherboard. On the off-chance that I misdiagnosed the cause of the dead touchscreen, I restored it to factory via recovery, but as I expected, still no go, of course.
It's frustrating, because the device is in beautiful shape in every other way. Screen looks great, not a single scratch on the phone itself, it boots into recovery perfectly as well as into Android.
I fully realize that I will never have this phone working as it was originally intended without swapping out the board, which I don't really plan on doing. I also have no interest in using this as a phone. I'd like to see this phone repurposed as a headless Linux box on my home WLAN. With its specs, it should be able to run Debian and Asterisk quite well (works great on my Seagate DockStar with 128MB RAM/700MHz ARM5-based SoC.) I just hate to see an otherwise perfectly good embedded computer go to waste because I can't enable debugging via the touchscreen.
Is it possible to use a breakout board attached to the microUSB connector to utilize any sort of external input so that I could jump into the phone and turn on debugging/root the device? Or would that require HID drivers to be installed on the device beforehand?
Another idea that I've considered is possibly reflashing it with a rooted ROM or maybe changing some settings on it via CDMA Workshop, I would still need to get into mode for that by pressing ##3424#, right? Argh. Is there another way?
Do either of these options sound viable? Any other suggestions? It should go without saying that I'm well aware that this could be a brick already, but it just seems as though there must be SOMETHING that can be done to at least give me rooted ADB access in the future.
Thanks in advance!
I'm guessing I'm out of luck? Either way, it's not a big deal. It's not as though it cost me anything, but it'd be nice to put it to work in some way. As a Linux geek, there's always a nagging feeling I get when I see a Linux-based device sitting in the corner being under- or non-utilized. Especially embedded.
I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!
rice923 said:
I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!
Click to expand...
Click to collapse
Root is still possible. Tethering *USED* to work on stock by using the FoxFi app. I haven't tested it in quite some time though. There's a limit for the free version, use it for testing though.
Sent from my SCH-I535 using XDA Free mobile app
I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too
rice923 said:
I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too
Click to expand...
Click to collapse
Do tell how. Especially if you did start with a Verizon galaxy s3 sgh-i535 that was not rooted and was running on stock Verizon Android 4.4.2
To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints
rice923 said:
To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints
Click to expand...
Click to collapse
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
I remember seeing you around MWs FML thread! 5.0 is looking decent over there, so I'm very happy for them.
If you get the chance, I'd definitely recommend CM11. It make me feel like I'm running a nexus device again, except significantly faster than the gnex with a better camera.
Regarding the charging speed, I don't think it's a kernel issue. With the phone plugged in, I keep getting notifications that it's being disconnectedAnd reconnected spontaneously. I've done some reading and and it seems there is a bit of oxidation or hardware issue within the charging port. The port also requires soldering of the mother board to change. I've resorted to ordering some qi chargers[emoji106]
As for the camera, this seems to be an old issue of cm11. I flashed a camera fix zip, but to no avail. The focus issue seems to be problematic only at macro distances though. I can't find a fix besides touching to focus prior to taking macro shots
Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3
ShapesBlue said:
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3
Click to expand...
Click to collapse
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.
Rushead said:
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.
Click to expand...
Click to collapse
Then yes there are several kernel options for fast charge. I know of lean kernel and ktoonsez off hand that are
From my CM11 S3
Don't want to start a new thread even though the title is irrelevant at this point, but was hoping someone could chime in regarding the camera auto focus issue. The camera focuses beautifully when I touch the screen, or when I allow it to autofocus. When I proceed to take the pic, it will try to focus again and take the pic right as it's completely blurry. This happens on both the stock CM11 camera and google camera.
I tried to flash the zip mentioned here http://forum.cyanogenmod.org/topic/85493-camera-wont-focus-cm11/ and nothing has improved.
Does anyone have any insight about this? These symptoms are identical to what many have mentioned in the thread above, so this is certainly not an isolated incident. Thoughts or input?
Who reads titles anyway?
I flashed Slim, and messed around with the camera a little, but I had wifi issues and am in the process of flashing cm11 11-09.
On Slim, the camera seemed to work fine. I took some "macro-esque" shots of text that came out pretty good (at least as good as the GNex, if not better).
I'll let you know how it fares with cm11...
So far, camera FCs on hitting the "No Thanks" button for location reporting.
OK, Camera is now functional (probably didn't wait long enough for the phone to settle on initial setup). The quality is mediocre. I'm still messing with it and will report back.
switching phones, want to keep/root the old Galaxy s3 as a lab/toy
Have an old Verizon Galaxy S3. Just got a new TMo Sony Xperia Z3 (which I am liking so far).
Will soon disconnect my Verizon service. Would like to root the S3 and use it wifi only as a experiment/toy thing, since there's no trade in value (cracked screen).
Possible? Cyanogenmod recommended?
I'm a total n00b at all this, and would steer totally clear of it for my main driver. But since I don't really NEED this phone anymore, thought this would be a safe way to dip my toes in. If I brick it in the process, no great loss.
Any advice or links would be much appreciated. Definitely want it to keep working as a wifi device and not brick once I cancel my Verizon service. Would be cool to be able to play with some of the fringier apps that require root. Those are my only requirements. Camera, cell service, etc all unnecessary. But do need wifi and don't want to create a big vulnerability to the rest of my home wifi network from this device once I'm done.
Thanks again!
evbb, depending on your current OS version, you might be able to root. If you are on the most current official OS, then you will likely just be staying with that.
Rushead, any update on how CM11 11-09 is going? If everything looks stable, I think I'll make the jump to that build.
Update about my charging times: The phone seems to charge at a normal rate if I use a 12V car charger made by Griffin (item does not specify amperage). I don't believe amperage has antying to do with my situation, as I've been yielding miserably slow charge times with the Nexus 7 (2.1 amp) charger. The phone is also very picky with cables. I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...
When my wife had the phone it was extremely loose as far as cables went. I could use virtually any cable whereas my GNex is super picky.
I haven't had much time to mess with the camera yet. I'm using it as a WiFi device, too, so I can't comment on data, signal, etc. But so far it seems pretty stable. The battery drain is excessive imo. On standby for most of the day, battery was dead by 10pm. That's factory kernel.
For those looking for a decent tethering app there's one on sale, free on the Amazon app store. Easy Tether is the name of the app. It's free 11/14 & 11/15
http://www.amazon.com/s/ref=amb_lin...d_t=101&pf_rd_p=1973721462&pf_rd_i=2350149011
From my CM11 S3
rice923 said:
I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...
Click to expand...
Click to collapse
You should try a very specific type of cable. The problem is the fact that you use a data cable at all. What I use is an aftermarket universal USB cable and it has the detachable tip for other phones. What this does is force the phone in "Charging (AC)" mode no matter what charger you use. Attached are 2 pictures to help identify exactly the kind of cable to solve your issue. I can charge my 7000 mah battery attached to my phone in 5 - 6 hours. A 2100 ah battery should be 1 - 2 hours with this.
Sent from my SCH-I535 using XDA Free mobile app
Some chargers identify as a USB hub rather than an AC adapter, and others do not. This is why on some chargers, it still charges slow. If ever the phone thinks it is on USB, it will not allow more than 650mah to pass through the cable. So even if you had a 10amp charger, it would not use that much if it identified as a hub.
Using the cable I mentioned removes the ability for any charger to send the identifier info to the phone. Reason? You are missing the data+/- cables that data is transmitted through. Only the +/-5v wires remain.
Sent from my SCH-I535 using XDA Free mobile app
But why would the phone have a constant disconnection and reconnection while being plugged in? That's the part that confuses me.
Regardless, I just received my qi charge in the mail! It's been pretty nice so far! I'm happy to answer any questions about it if anyone is interested
Rushead, wanted to give you a heads-up about the latest CM11 build I used. I clean flashed 11-15 and everything was great except for the camera, which consistently gave me a "cannot connect to camera" error. Otherwise, it seemed like a great build with some great options. I gave up and clean flashed 01-15. Camera is all great except for the autofocus issue mentioned before. GPS lock is great, and battery life is loads better than my GNex days.
Regarding my qi chargers, I am pulling a net positive charge of 315mA on my house charger (Nexus 7 2.1amp AC adapter). This is with the phone turned on, connected to Wi-Fi, screen off, and doing nothing.
My car qi charger is doing about the same. I ran the GPS with screen on (auto brightness) and the charger only charged the phone 3% in 2 hours with screen on and GPS running the whole time. I might switch the DC socket to the included one to see if I get better results.