Related
Hi guys,
I've been experiencing this very consistently for the last couple of days now... every time I plug into USB - when I mount, the phone reboots... it's very quick, but has anyone else been experiencing this?
Thanks!
Hi keisuke_z,
which phone (X10i or X10a) and which Firmware do you make use of?
I had that Issue on my X10i UK Firmware R1FA016 too. Now, on Nordic R1FB001 everything is fine.
I'm not sure, if it was an Firmware or settings Issue.
On R1FA016 I couldn't determine any settings that could have caused that problem and resetting the device didn't help neither.
I am now getting this issue. Whenever I go to mount my phone, it crashes and then reboots. However it is always mounted when I plug it in. This leads me to believe it is somehow stuck in a mounted mode.
Anyone know a how I can see the logs for what the hell is going on?
EDIT: By the way my phone is X10a (R1FA014)
Same question here
Same here, I never bothered troubleshooting it as the reboot is fast and all is good again post reboot but ya, would be nice to find a fix. I have also noticed that the icons that show up in the notification bar are the explanation mark icons and not the standard usb icons.
element27 said:
Same here, I never bothered troubleshooting it as the reboot is fast and all is good again post reboot but ya, would be nice to find a fix. I have also noticed that the icons that show up in the notification bar are the explanation mark icons and not the standard usb icons.
Click to expand...
Click to collapse
Exact same problem bro...
j3yps said:
Exact same problem bro...
Click to expand...
Click to collapse
Happens for me too - found out that's it's an application(s), as I re-flashed the phone, and the problem didn't occur until I batch-installed some applications.
ToastyJustice said:
I am now getting this issue. Whenever I go to mount my phone, it crashes and then reboots. However it is always mounted when I plug it in. This leads me to believe it is somehow stuck in a mounted mode.
Anyone know a how I can see the logs for what the hell is going on?
EDIT: By the way my phone is X10a (R1FA014)
Click to expand...
Click to collapse
I can even copy files on my PC, and access files on the phone SD card at the same time - how is that possible?
HunteronX said:
I can even copy files on my PC, and access files on the phone SD card at the same time - how is that possible?
Click to expand...
Click to collapse
Me too!! Isn't this a SE bug?
Well, I reset my phone to factory state and it seems to have gone away. It bugged me just that much while developing. However, I seem to find that it will still disconnect if the cable is jiggled a bit in there. Perhaps something is loose on mine too. If it gets bad I may have to send er in or get it replaced.
Hi Guys,
This problem has just started happening with my x10a. I'm hoping that the only solution isn't to wipe the phone...
The only thing I can think of that might be causing it is a particular app that is using the SD card?
Maybe the R2BA020 firmware update will help things out. As soon as I get it I'll let y'all know!
Update: I've upgraded to R2BA020 and the problem has not happened again yet.
Hello Everyone,
I have noticed that the phone reboots everytime Spotify or any other media player is active and accessing files on the SD card.
Cheers
Marcus
Same here, and i have found that with one more reboot the triangle icon goes back to the normal usb one again. As Thurban says above, maybe something is running which is accessing the sd card at the point when we attempt to mount it?
One step that might help - perhaps if we were all to use ATK to kill everything immediately prior to whenever we plug into usb, and report back here if the issue still raises its head? That sound like a plan?
updating the phone would help resolve the issue..might be some application on the sd card thats causing this..so, you can also try formatting the sd card..
Has anyone else been having trouble with market today? I went to bed last night and the market was working perfectly. When I woke up today though, and its still going on, I will try to download a program and it will start the download for a second and then it just stops like I never even told it to try. I have tried on both the Verizon network and using Wifi.
Am I the only one with this problem? And if not, does anyone have any suggestions on how to remedy this problem?
Thanks in advance!
my market won't even start. it has a server error it says
Mine does everything normal except downloading. Rom manager wont download clockwork recovery either. All internet works fine tho...
I've been having the download problem too, but then again, I've always had serious problems downloading from the Market. It used to be that downloads would just hang on "Starting" without ever actually downloading. This start-and-disappear thing, however, is new to me.
The end result is the same though -- it's probably about 50/50 for me whether something will actually download and install or just hang or disappear. Honestly, the Market's dysfunctionality (yeah, I made up a word) is the single most annoying thing about Android to me, and the one thing that's legitimately made me consider switching to another OS and phone. It's unbelievably frustrating when you just can't download apps sometimes, no matter how many times you try. And no, I've never found a fix.
Well, I unrooted my phone and now everything works fine. I used Super One Click Root to do it and maybe that just doesnt work for this phone....
Edit, I used a different root method and now I have root and my market is working perfectly. Feel free to try this method if you want and see if it helps you out.
http://support.newagepcs.com/showthread.php?2813-How-to-Root-(1-Click-Root)-Samsung-Fascinate&p=2814
I had this issue also. I fixed it by using root explorer to set permissions. You can do this by opening root explorer-system-app-tap 'Mount R/W' at the top until it says 'Mount R/O' and find and long press vending.apk-permissions-check every box for User, and only check read for Group and Others. Then tap ok and reboot. Hope this works for you
Sent from my SCH-I500 using XDA App
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?
Ok so makes no sense ive not had any problems like this. Ive had my phone for months. All the sudden last night i plug it into my ps3 to move over a video file and Boom. the Ps3 freezes in such a way that all the controllers stop working and i cant do anything on it. Unplug the phone and after a few seconds things go back to normal. I plug it into my Usb hub (4 way splitter from Tmo) on the ps3 and it works (albeit very very slowly). Try to go back to just the ps3 and again it stalls and the pc wont even see it. Today trying to fix the problem ive changed to 4 different roms, tried mounting in recovery and tried to get my PC to recognize it every way i know and nothing is working. The charging light comes on but nothing else seems to happen on the ps3 or computer. Thanks in advance pros
Bump. Please help if u can guys. Thanks
ooo i had this issue earlier this week, installed like 3 different roms and it wouldnt see it, but all of a sudden it came back up.
what I did was wipe data/factory, cache, davlik, went into mount and storage formatted everything that gave me the option, mounted usb and installed Royal Panache rom. rebooted twice and it showed again.
hope this can help you.
srivers33 said:
Ok so makes no sense ive not had any problems like this. Ive had my phone for months. All the sudden last night i plug it into my ps3 to move over a video file and Boom. the Ps3 freezes in such a way that all the controllers stop working and i cant do anything on it. Unplug the phone and after a few seconds things go back to normal. I plug it into my Usb hub (4 way splitter from Tmo) on the ps3 and it works (albeit very very slowly). Try to go back to just the ps3 and again it stalls and the pc wont even see it. Today trying to fix the problem ive changed to 4 different roms, tried mounting in recovery and tried to get my PC to recognize it every way i know and nothing is working. The charging light comes on but nothing else seems to happen on the ps3 or computer. Thanks in advance pros
Click to expand...
Click to collapse
I had a similar issue with my nexus s and a dev told me to partition SD card or power down phone. Plug it in go to recovery and find mount SD card try that
Sent from my Nexus S 4G using Tapatalk
So i tried both ideas, interesting results. I had already tried getting it to work in recovery and no joy. Flashed the latest CWM 5.0.1.0 and still nothing.
Then tried Royal Panache and the phone seems to see the comp, lets me pick what kind of connection i want to use but then nothing else happens on the comp. A
Any new tips?
srivers33 said:
So i tried both ideas, interesting results. I had already tried getting it to work in recovery and no joy. Flashed the latest CWM 5.0.1.0 and still nothing.
Then tried Royal Panache and the phone seems to see the comp, lets me pick what kind of connection i want to use but then nothing else happens on the comp. A
Any new tips?
Click to expand...
Click to collapse
did it show up on the panache rom then? when you say it didnt show up on the computer, it didnt pop up and it didnt show in the "computer" section where it shows all drives?
Yes exactly.on panache only, it Shows in the phone but its as if the comp then can't see it. Still works fine with the hub but nothing else, have tried different computers, ROMs, cords, recovery images. The only way it works is through the hub. THIS MAKES NO SENSE.......could un rooting fix this? Could it maybe be the sdcard?
This happens to me...
Sent from my HTC Glacier using XDA App
This happened to me and flashing the latest unity kernal fixed it.
http://forum.xda-developers.com/showthread.php?t=1050106
ok, so virtuous didnt help. The rom didnt work alone neither did using the latest kernel. Unrooting now. will keep all posted.
no dice mates, all the way back to stock and no difference. Like the panache ROM, the notification shows up, but it doesnt seem to make any real difference. Doesnt show on the comp or ps3 and so im on the phone with TMO now.
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