Related
I have a very strange issue going on with my fascinate right now. Before I go into too much description, here is my setup, to see the big picture. Rooted, stock vzw with geekniks stupidfast for DI01 (thought original kernel was original issue). I've tried to force the ota to DL09 and I get "IP_PREVIOUS_UPDATE_FAILED" as it fails to verify the dl signature.
Ok, on to my true issue. When I plug my SF into my pc, I get unrecognized usb device. I have the drivers installed properly and have previously been able to use odin via usb. My pc doesn't see the sd card mounted or anything. I'm debating unistalling the usb hub and restarting the pc so it will pick it back up as a new device. I have debug mode and unsigned checked, however, the little red triangle is no longer present like it used to be. I also every once in a while have issues with my battery level being accurate, as in it shows 100% when its really at 36% etc. It still charges, and recognizes being plugged in (haptic and audible confirmation).
Anyone have a clue or suggestion? I'm new to android, but well versed in the pc world. I just installed the android sdk in hopes of maybe doing a wireless adb push eventually. I'm A) trying to correct the issue and update my os/rom, or B) somehow get me back to stock and unrooted without being able to usb odin, so I can swap out for a new phone.
Thanks in advance for any help, whether it works or not.
Sent from my SCH-I500 using XDA App
Oh yeah, I'm running Win7 64bit.
Sent from my SCH-I500 using XDA App
so you are on stock vzw but you have used odin before. Did you use it to get clockworkmod on the phone?
did you return to stock from dj05 or dl09 OR have you always been on stock rom
I used odin to flash cwm. I'm on DI01 upadate-1. Had done the first update ota, then rooted and flashed cwm. I have been running that since until today. Thought kernel may have been issue, so flashed geekniks kernel for DI01 and have seen no change, except better performance as was expected. That is where I am now. Thinking about going back to previous kernel, but this seems better until I decide what I can do. Original nandroid and other in betweens to date still manifest the issues, which are only recent, like last few weeks.
Thanks again.
Sent from my SCH-I500 using XDA App
Does not see the Samsung SD Card
I have had similiar issues since DL09.
Try turning off your phone then reconnect USB after it reboots.
Seems to want to see it as a CD Rom.
norm883
I've rebooted my phone and pc, multiple times, no luck. Oh, one other thing, I tried popping the sd card into a card reader and I was able to see the files briefly, and upon trying to select anything, it totally disappears from view, as in pc doesn't see card anymore. Now I can't get the pc to see it at all. So I can't read/write it that way. My phone still sees it and can mount and unmount for removal on phone itself, but not with the pc.
Sent from my SCH-I500 using XDA App
I'm non-voodoo as well.
Sent from my SCH-I500 using XDA App
Try flashing a different kernel. My first fascinate was picky with which kernels wanted to work right with the.usb connection.
Sent from my SCH-I500 using XDA App
In my experience, you can still use ADB to push and pull things from your device even when your pc doesn't recognize your device. I know this doesn't help with flashing DL09, but it could help you push a different kernel to your device (or you could download one from xda forums via the xda app). A different kernel might clear up the issue for you. Good luck!
This fixes it....
http://forum.xda-developers.com/showthread.php?t=915709
For your first issue it is because you are rooted you will not get ota updates. You should use odin and flash DJ05 imo it is much better and there are more ROMs and kernels
Sent from my SCH-I500 using XDA App
Thanks for all the help, I'm going to give it a whirl later and see if it works. I'll let you know.
Sent from my SCH-I500 using XDA App
Before I get too far deep in, could I just unroot via a terminalapp and then force the OTA to get me up to speed? Would at least like to see if I can deal with the minor malfunction while still being current.
nunyazz said:
This fixes it....
http://forum.xda-developers.com/showthread.php?t=915709
Click to expand...
Click to collapse
This won't fix the problem because he is not on DL09. It will likely make his problem worse. You might want to read the entire post b4 you give suggestion.
To answer your question sir: if you can't get your pc to read your sd card with a card reader, the problem most likely has nothing to do with your phone. It probably is a corrupted|damaged card. It could also be a problem with your computer (this can be ruled out by successfully connecting another usb device to your computer).
Most likely, you will have to buy another micro usb card.
Sent from my Vanilla Froyo Fascinate
Ok, been trying a few things, and I'm starting to lean towards the sd card being corrupt (as one of the issues), sending my important pics and backups of my contacts, sms, etc to dropbox as we speak. I actually tried the SV kernel from adryn, and my phone has seen no ill effects (possibly no haptic, but didn't care at this point), everything seems to be working just like nothing changed. I actually briefly got the USB debug icon up for a second and it said usb connected, however I was not connected to anything, lol. It had done this on the stock kernel as well. I've booted my phone without the sd card in and it starts up normally, but the USB debug icon is still not present, even though the option is ticked on.
I can still force my phone into download mode, however my computer still doesn't recognize the COM port, so odin is out of the question right now. If I were to get my hands on the stock kernel again, could I factory reset the phone, remove root, and potentially force the OTA and then reroot? I've seen some options for terminal apps where I could ru superuser and busybox. Any thoughts on that route? I may give my roomie's pc a try, when he's out, as well to widen my test field.
Well, I got my pc reading the card via a card reader, but not while inserted in my phone. I'm going to try to uninstall the usb hub on my computer and restart my pc with no usb periphs connected. I read somewhere that someone was able to get the phone recognized again, but I have a feeling that it isn't going to work, since I never see the USB debug icon anymore.
On a side note, I get a com.android.settings force close message somewhat frequently, on stock, geeknik and adryn's kernel. I've started unloading apps left and right, but no avail. Thinking I need to get back to full stock somehow without odin. Suggestions?
I had similar issues. No usb, battery flashing to 100%. Tried everything as you have. Couldn't figure out how to get back to stock without odin. I'm running DJ05 superdark with geeknik 1.54 kernel.
This went on for a week and I was ready to give up and go buy another phone when one day the usb icon flashed momentarily when I plugged it in to charge.
In the end, it turned out to be a dirty usb connector on the phone. Cleaned it with a paper swab dampened with alcohol. I still have no idea why it was so sensitive to the small amount of dirt that came off it.
Hope this helps.
Well, I tried the alcohol swabbing, and it mildly worked. I get the usb debugging icon more often, but it also shows that the usb is connected, even though it isn't. My pc briefly recognized it once. Would I be able to disassemble it and clean or replace the usb port myself?
I've even blasted it with compressed air.
Sent from my SCH-I500 using Tapatalk
You've gone farther than I had to. I didn't need to resort to compressed air.
Do you have more than one usb cable available? I had bought an aftermarket one in addition to the one that came with the phone.
The original cable is still wonky on connection. It charges ok (no more battery jumping to 100%), but usb recognition is a fifty-fifty proposition. The aftermarket cable does charging and usb correctly.
I have had to reset my PC's usb drivers once by rebooting the phone while connected (the PC recognized it as a CD-ROM drive). This may be coincidental or an indication of a chronic connection problem.
I speculate in my case that the aftermarket cable distorted the phone connector somehow so that it doesn't like the original cable any more. Pure speculation.
Anyhow, glad to see that you're making progress. I know how frustrating it was for me. Keep us posted.
I had the same problem at one point. I found out that if your turn the phone off, plug in the usb cord from the computer, then turn the phone on while the phone is still plugged in. once the phone reboots, unplug the phone, then replug the phone in to the computer and then the computer should recognize it. This works for me every time that i have this problem
Hey guys,
So I loaded RubiX a while back and after getting everything all fancied up the way I wanted it my phone decided that it doesn't like when I touch it (touch-screen stopped responding, the hard keys still worked fine, but I have to serious hold screen-keys down to make anything happen).
I thought this problem was just something in the ROM that my phone didn't like, or a bad setting I changed, so I tried out Liberty ROM (which, by the way, is AWESOME). After getting everything completely made for the Liberty ROM, the exact same thing happened.
In a fit of frustration I decided to start from scratch, root and deodex, then load all my fun settings (like the de-throttle and imoseyon's memory changes) and it all started doing it again. Is there something I don't know about the way the screen works?
Another interesting fact: While I was trying to figure this problem out with my phone (stock with root/deodex and imoseyon's changes) I unplugged it from charging on my comp and now it's running pretty smoothly again... I've been having this problem all day, restarting and clearing cache / loading different ROMs and running restores didn't do anything... this is really strange!
Any idea what this is / has anyone experienced it before. I was just about to call Verizon and reset my phone to stock to get an exchange.
Try running a ROM stock and see what happens. Could be an app...
zehk,
I've tried every combination, including running to stock...
What I know now is that it only happens when phone is charging from a computer... The touchscreen goes completely brain-dead...
Any ideas?
I've had a problem when charging my phone from USB before. Someone said it was the drivers on my PC... might try a newer or older version depending on what you have.
That's an odd problem. Seeing how you have tried to troubleshoot your issue, trying the PC Drivers might indeed help as suggested by zehkaiser.
I would recommend downloading Motorola'as MotoConnect. It's the only driver I use for any Motorola device I hookup to my computer. You can download it here. Hope that helps and if not, sounds like you will have to do a .340 SBF with RSD Lite or the maderstcok zip 340 and return your phone for a new one.
nope
It's not the drivers either, I've now realized that it's happening when I plug into the wall too. I thought that might be due to using an old palm charger, since it's slighty higher amperage, but it turns out the standard moto charger still causes this problem...
My DX does exactly the same thing after unplugging. Any ideas?
I am now having an issue with my usb connection, it keeps dropping off and randomly coming back. I installed cm7.0.3 over top cm7.1 to see if it was the newer cm7 build but i have the same problem. This is frustrating. My battery life is horrible and the usb being flaky at best and i just can not get this thing to work like everyone else has. Anyone able to tell my what i might be doing wrong??
Ended up being my usb cord was crap, got it replaced, Mods can delete this thread.
Do these have a crash log anywhere? It has been crashing daily on me. Trying to debug this thing, before blaming it on hardware
troubleshot said:
Do these have a crash log anywhere? It has been crashing daily on me. Trying to debug this thing, before blaming it on hardware
Click to expand...
Click to collapse
I'd rma it
Sent from my Rooted, LazyPanda, White "Destroy Mode" Evo
troubleshot said:
Do these have a crash log anywhere? It has been crashing daily on me. Trying to debug this thing, before blaming it on hardware
Click to expand...
Click to collapse
Dunno about a crash log, but are you rooted? If so did you root with the awesome root kit available at this forum? The only reason I ask is cause I was having a daily crash as well- I'd turn it on for the first time in the morning and find it was booting up. Anyway, just by chance, I noticed my N7 was still in USB debugging mode when I plugged it into my Macbook to charge (IIRC, the rook kit requires you to turn on USB debugging during some part of the process). I've noticed that since turning off USB Debugging I haven't had a single daily crash, though I've had the unit freeze up once.
I don't know for sure that this is what fixed things, but I didn't do anything else to my N7 aside from the usual updating of apps and the unit is purring along again.
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
BigDig said:
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
Click to expand...
Click to collapse
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Ankst said:
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Click to expand...
Click to collapse
Try a different cable and see what happens! It won`t hurt...
BigDig said:
Try a different cable and see what happens! It won`t hurt...
Click to expand...
Click to collapse
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Ankst said:
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Click to expand...
Click to collapse
I would have tried to flash another kernel if I were you to see if the problem persists
When I connect my N4 to my PC, it shows up in device manager as as a portable device and mtp works fine. Checking the driver version shows that it is using WMP drivers. When I turn on usb debugging, that connection gets added as other devices in device manager with a yellow exclamation point. My device is detected since it will pull the serial number in a command prompt. I haven't tried anything thru adb yet, but for accessing your folders on storage, that would be the mtp as portable device connection anyways. The key thing is making sure that you are getting that connection and using the WMP drivers, not the Android usb drivers.
Sent from my Nexus 4 using Tapatalk 4 Beta
Ankst said:
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
Click to expand...
Click to collapse
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
tyea said:
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Ankst said:
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Click to expand...
Click to collapse
Ok, so here's my progress, and ultimately my conclusion. I just wiped and tried another stock rooted rom by teshxx, it wouldn't even boot. So, CM was my last hope. Again, wiped and installed CM 10.1 RC3 , flashed gapps, and it booted up. There was still some issue with some of the google services, but fixed easily enough by uninstalling them and reinstalling them from the play store. When I plug it into a computer, I *still* have the "usb device not recognized" error in windows. And usb debugging still doesn't activate even though it definitely sees usb as the connection by looking at the battery settings. I realize that charging through usb is a different voltage etc. and why it knows has no relation to usb debugging reacting to the usb cable. That being said, I have to conclude that by some freak of nature, the data path through the usb port on the phone has stopped working. Perhaps a power spike? Maybe there is a god and he hates me? I don't know, but seeing as CM would have rewritten the kernel as well, this is about as far as I'm willing to go to try to diagnose this. Now since I can't use a computer to re-lock the bootloader, I'm stuck with a busted usb port. The phone is clearly within a warranty time frame, with the exception that I unlocked the bootloader and voided that upon purchase. I guess my advice to anyone reading this, wait one year and one day before you bother, so should a hardware failure like this happen to you, you can have it replaced.
Out.
tyea said:
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
Same here, see final post