Im getting an issue with my phone saying that usb is connected and usb debugging when im not connected to computer. I took out battery and replaced to see if it would fix it. But my phone thought it was charging and wouldn't get into recovery mode or boot up.. so I had to odin back to stock. Once I flashed my rom again it started saying it again. Im running trigger, so I figured it would ask birgertime about it. He said to plug into usb and unplug as soon as sound was heard. Said it was common froyo problem.. didn't work. Any other answers? Rather annoying cuz I can't see my notification bar
Sent from my SGH-T959 using XDA Premium App
you have to unplug the phone from usb while the phone is unlocked and screen is on. Ive noticed this with all froyo roms going back as far as i can remember.
Ya thays what I did.. sorry didn't specify
Sent from my SGH-T959 using XDA Premium App
I don't have any good news for you, just similar circumstances. Now, I can't connect to any computer. No adb, no Odin, just charging. I can flash cwm'able stuff, but can't be too risky.
Back to topic...I tried everything to get rid of USB connected/USB debugging...format every partition, but no luck. I've heard its a cwm bug. Can't get real answers from anybody. I just started (re)researching this again. I will pm you if I find info...good luck
So my USB port is somehow not working with data on my vibrant. It worked intermittently but now I cannot connect to my pc or other pcs at all. I think I may have bent something, not sure. But the real question is, can I flash GB bootloaders via another method then ODIN. something like SGS kernal flasher? or am I SOL. I read on the Simply Honey 3.8 rom thread that people were going from simply honey 3.3 to 3.8 without loading the GB bootloaders.
Thanks!
Do you have USB debugging enabled?
Yes, the reason why I think my usb port is broken because sometimes I can get a connection if I hold the cable a certain way when connecting to the pc but when I let go the pc reverts to usb device not functioning. Not good, and hard to reproduce.
Sent from my SGH-T959 using XDA App
you dont need to bootloaders to do it, i dont trust odin so i dont have them
i flashed 3.3 from 2.8 then 3.8 in the cwm app then any addons with rom manager, everything seems to work fine for me
thaydengeo said:
Yes, the reason why I think my usb port is broken because sometimes I can get a connection if I hold the cable a certain way when connecting to the pc but when I let go the pc reverts to usb device not functioning. Not good, and hard to reproduce.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Have you tried with different USB cables?
I have tried different cables, just that it used to work and now no longer does
Sent from my SGH-T959 using XDA App
When your phone is plugged in, does it indicate it's connected to the PC or both of them don't acknowledge it?
Sometimes the phone acknowledges it, sometimes it doesn't. This is what makes me think it may be a problem with the port.
Sent from my SGH-T959 using XDA App
Use a different computer and see if that fixes it. If it doesn't, let me know so we can try to figure out what's wrong.
My vibrant usb no longer works, Phone charges and detects usb cable (option to mount) but my PC doesn't show phone in device manager...
I've tried cleaning usb, multiple usb cables, and different PC's!
Has anyone had problems like this before? I find it hard to believe out of the blue my usb hw failed... Hoping this is some how fixable... because I need odin access to the phone
any help would be appreciated, thanks
make sure you have drivers?
http://forum.xda-developers.com/showthread.php?t=728929
Yes, I've tried new and old drivers making sure to properly remove them before trying the other... Problem is even if drivers weren't installed Device manager would indicate a unusable or unrecognized device? all PC's i've tried don't indicate any device connected.
My other vibrant works fine on all PC's only my Gf's is having a problem...
Could be usb failing I had to send mines in 2 weeks ago and they replaced the usb at no cost. Just make sure you call the galaxy s support if you plan on sending it in to fix. I got ny phone back within 4 days.
Sent from my SGH-T959 using Tapatalk
Going to call Monday thanks for the info
Sent from my T959 using xda premium
Was on Bonsai rom and was running fine. Noticed the phone acting kind of weird the last couple days and thought it may be related to Xposed or some of it's modules so I deleted all of them. That didn't fix the problem. The problem being that the battery icon in the the notification bar would randomly flicker and with it so would the touch keys. I'm pretty sure this only happened when I was attempting to charge my phone (in my car.)
Instead of getting the usual phone charging indication in the status bar I either got nothing or it would say that the phone was connected to the dock (WTF?) I ended up restoring a nandroid of an older Bonsai rom and for a few hours there were no problems but then it started happening again. At times I would get a reboot from just plugging in the USB cable to charge the phone (car or wall) Other times the phone would just freeze up.
I then did a full wipe and tried MAXIMUS rom. I plugged in the USB cable and attempted to sync the phone to my PC as I have done countless times just days ago but I was now getting a message that my USB device is not recognized. I did another clean flash and tried Steve's Odexed rom. Same story more or less. If I attempt to sync the phone to the PC I get the same not recognized message.
Here are the steps I have taken:
- tried numerous USB cables
- tried numerous charging ports (wall/car/PC)
- tried numerous roms (none will let my PC see the phone)
- reinstalled the Samsung USB drivers
I'm at the point where I'm thinking this is a hardware issue and I probably have to return this phone. However, before I jump the gun I wanted to see if anyone has input on this. I appreciate any advice u guys may have.
My initial thought s maybe a cheap car charger, then a bad USB cable, but you've already eliminated those options. When you backup /restore your backups, are you including the efs.? I also remember the option in Wanam to keep old efs, was that option checked while it was installed?
Sent from my SM-N900P using Tapatalk
blackcanopy said:
My initial thought s maybe a cheap car charger, then a bad USB cable, but you've already eliminated those options. When you backup /restore your backups, are you including the efs.? I also remember the option in Wanam to keep old efs, was that option checked while it was installed?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure that when I backup and restore I have all the boxes check off. However, I not only used backups. I did clean flashes on two separate roms but both had the same issue. I'm still on the fence as to whether this is software or hardware
SantinoInc said:
I'm pretty sure that when I backup and restore I have all the boxes check off. However, I not only used backups. I did clean flashes on two separate roms but both had the same issue. I'm still on the fence as to whether this is software or hardware
Click to expand...
Click to collapse
Have you tried flashing the MJ4 firmware to see if that straightens things out?
I would suggest to odin the stock rom found here if you can get your computer to recognize your device in download mode..
[ROM][TAR][ODIN] Full Restore (Return To Stock) N900PVPUBMJ4 TAR
http://forum.xda-developers.com/showthread.php?t=2549035
[ROM][TAR][ODIN] Full Restore (Return To Stock) N900PVPUBMJ4 TAR
Sent from my SM-N900P using Tapatalk
I may try that as a last resort. My fear is that I won't even be able to access Odin mode because the PC won't recognize my phone. We'll see...
Sent from my SM-N900P using XDA Premium 4 mobile app
SantinoInc said:
I may try that as a last resort. My fear is that I won't even be able to access Odin mode because the PC won't recognize my phone. We'll see...
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hopefully somebody can come up with a solution for you.
If it fails to recognize your device in Odin mode, you should be able to remove the battery, reinsert it and reboot to your system. No harm, no fowl.
Sent from my SM-N900P using Tapatalk
---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------
One more thing before I resign for the night... Maybe try those things you have already tried with your SD card removed. I'm hearing here and there about sd cards going bad causing issues you wouldn't normally think were related.
Sent from my SM-N900P using Tapatalk
SantinoInc said:
I may try that as a last resort. My fear is that I won't even be able to access Odin mode because the PC won't recognize my phone. We'll see...
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like a Windows driver issue. Could be unrelated to your phone.
What Version of Windows are you running? What do you see when you plug in your device when you go into Windows device manager?
Have you installed any new Android devices of the Nexus variety on your computer?
Alright, I'll assume that you're asleep. I agree, you may not want to do PC Odin if your computer isn't recognizing your device.
Go into device manager (right click on My Computer, select Manage, go to device manager from there). Do you see your device? Do you see any Android device? If so, do either have a yellow question mark adjacent the device name? Either way, delete the device if present, then reboot your PC.
Now plug your phone into your computer using a different USB port on the machine (cable we'll assume is fine). Your computer should automatically recognize the phone. If yes, profit.
Also check that USB debugging is set to on. If recognized and the phone is plugged in, deselect MTP device and choose the photo option. Then select MTP again.
If the above doesn't work, you can try rolling back drivers and reinstalling.
Let me know if this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Sounds like a Windows driver issue. Could be unrelated to your phone.
What Version of Windows are you running? What do you see when you plug in your device when you go into Windows device manager?
Have you installed any new Android devices of the Nexus variety on your computer?
Alright, I'll assume that you're asleep. I agree, you may not want to do PC Odin if your computer isn't recognizing your device.
Go into device manager (right click on My Computer, select Manage, go to device manager from there). Do you see your device? Do you see any Android device? If so, do either have a yellow question mark adjacent the device name? Either way, delete the device if present, then reboot your PC.
Now plug your phone into your computer using a different USB port on the machine (cable we'll assume is fine). Your computer should automatically recognize the phone. If yes, profit.
Also check that USB debugging is set to on. If recognized and the phone is plugged in, deselect MTP device and choose the photo option. Then select MTP again.
If the above doesn't work, you can try rolling back drivers and reinstalling.
Let me know if this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Mic, thanks for taking the time for taking a look at this Q&A. I'm on Windows 7. Under DEVICE MANAGER it says UNKNOWN DEVICE with a yellow triangle with a exclamation point inside. When I click on that icon this is what I get for device status: Windows has stopped this device because it has reported problems. (Code 43)
I went through all your steps but it hasn't worked. I get the same message in DEVICE MANAGER before and after doing your steps.
As far as the phone is concerned (running Steve's Odexed) it indicates that the phone is charging but it doesn't have the usual MTP message in the status bar. Simply indicates that it's charging.
Is it safe to assume this is a hardware problem with the phone? The only thing I can think of that could have caused this is the other day my car charger (part that goes in the phone) fell in some water that accumulated on the rubber car mat. I dried it off with a napkin and plugged it back into my phone. These problems happened a day or two after this incident. Not sure if it's the reason. I was leaning towards blaming it on Xposed modules that got updated.
Nope, Not Safe to Assume...
SantinoInc said:
Mic, thanks for taking the time for taking a look at this Q&A. I'm on Windows 7. Under DEVICE MANAGER it says UNKNOWN DEVICE with a yellow triangle with a exclamation point inside. When I click on that icon this is what I get for device status: Windows has stopped this device because it has reported problems. (Code 43)
I went through all your steps but it hasn't worked. I get the same message in DEVICE MANAGER before and after doing your steps.
As far as the phone is concerned (running Steve's Odexed) it indicates that the phone is charging but it doesn't have the usual MTP message in the status bar. Simply indicates that it's charging.
Is it safe to assume this is a hardware problem with the phone? The only thing I can think of that could have caused this is the other day my car charger (part that goes in the phone) fell in some water that accumulated on the rubber car mat. I dried it off with a napkin and plugged it back into my phone. These problems happened a day or two after this incident. Not sure if it's the reason. I was leaning towards blaming it on Xposed modules that got updated.
Click to expand...
Click to collapse
Hi, SantinoInc, let us hope that the car charger issue and your Code 43 is a cum hoc ergo propter hoc (with this, therefore because of this) fallacy, or a non-correlated set of phenomena that, though happening contemporaneously, does not mean (though one is enticed to infer) causality.
The Code 43 error is a Windows issue, and if you are using a laptop (I hope), turn off the computer, take out the battery, let it discharge for 10 minutes, slap your laptop battery back in, boot up, plug in the phone, it's alive (I'm hoping). The USB controller on your computer actually holds a small amount of charge for rapid use when the computer is started, which can corrupt the port and driver. Draining the charge and pulling the battery is required to get rid of the problem.
Report back and let us know if this works for you.
unfortunately my computer I've been using is a desktop. However, I do have an old laptop laying around somewhere and will try that. This is driving me nuts already. I wish I knew for sure what the issue is.
Sent from my SM-N900P using XDA Premium 4 mobile app
Google...
SantinoInc said:
unfortunately my computer I've been using is a desktop. However, I do have an old laptop laying around somewhere and will try that. This is driving me nuts already. I wish I knew for sure what the issue is.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Google the error code you flipped me. You'll find that it most certainly looks like a USB controller issue. Tom's Hardware and Microsoft look to have the info you need, bro.
SantinoInc said:
unfortunately my computer I've been using is a desktop. However, I do have an old laptop laying around somewhere and will try that. This is driving me nuts already. I wish I knew for sure what the issue is.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had this issue as well, not with the same phone symptoms, but in windows.
Remove the driver, go to samsung's site, download and re-install the latest driver. Also make sure you are connecting directly to the ports on your motherboard and not on the front of the PC or a USB hub on something like your monitor. Also make sure you are using the cable provided by samsung if possible. 3rd party cables for some reason can cause issues. (Thank god for standards to specifications
If you are still on MI5, use the thread I created here for help in getting to MJ4:
http://forum.xda-developers.com/showthread.php?t=2580731
I have tried all of your suggestions (including Windows error code 43 in Google and trying those recommendations) nothing has worked. Of course I can't find either of the two laptops I own to test this POS phone out. If I get the same error another PC I'm going to take the phone to Sprint to get it replaced. I'm really feeling that this is hardware related considering I have not installed any new phone drivers to my PC at all and have made no significant changes to the PC.
Agreed...
SantinoInc said:
I have tried all of your suggestions (including Windows error code 43 in Google and trying those recommendations) nothing has worked. Of course I can't find either of the two laptops I own to test this POS phone out. If I get the same error another PC I'm going to take the phone to Sprint to get it replaced. I'm really feeling that this is hardware related considering I have not installed any new phone drivers to my PC at all and have made no significant changes to the PC.
Click to expand...
Click to collapse
Agreed; any PC would be suffice to determine if it is phone related. I'd almost be inclined to hop in the car and hit a Best Buy store and be done with it, like now....
Best of luck.
So all of a sudden I can't connect to my pc. When I plug in in it charges but can't view the internal memory. I've tried different cables , different computers yes it's in developing mode with usb on.
Like i said it worked last week using pdanet but now it stopped. I've even reset the phone. Wtf.
I've read a bunch of threads here but can't get it to work. Oh Ya I'm running 4.4 stock Rom Unmodded unrooted.
turbosporsche said:
So all of a sudden I can't connect to my pc. When I plug in in it charges but can't view the internal memory. I've tried different cables , different computers yes it's in developing mode with usb on.
Like i said it worked last week using pdanet but now it stopped. I've even reset the phone. Wtf.
I've read a bunch of threads here but can't get it to work. Oh Ya I'm running 4.4 stock Rom Unmodded unrooted.
Click to expand...
Click to collapse
Reinstall your drivers.
Sent from my HTC6435LVW using XDA Premium 4 mobile app