So, I've unlocked my T-Mobile MDA G3 phone both CID and otherwise using loki. I've tried the T-Mobile update off their own site, and here is what happens. I suspect I need a different data cable, but I might be wrong there, so I figured I'd bring the issue to you all because you are the gurus of all gurus...type peoples.
So, here's what goes on. I download the software. I sync my MDA and my notebook. I ensure both machines are on and set to stay on. I check the connection and all is good. Heck, I've even backed up my MDA system using one of those backup utilities for Smartphones available online for trial download(which worked great, btw). So I run the software and click next and check everything it says the check and then it begins. This is where my problem begins and the goodness ends...
The MDA shuts off and just sits there. I don't touch it for fear of what might happen by being impatient, but every time, no matter which ROM I've tried to use for update purposes, the notebook pops up saying that it encountered a "communications error". It doesn't brick the phone, thank God. It simply just requires removal of the battery for 5-10 seconds after disconnecting the USB, then turning it on. It boots fine and all is good, except, no new ROM, same old 1.0.8.something version and bah!
I want to update my ROM and am stuck. I've tried at least 5 DIFFERENT ROMs and loaders and still the same thing.
I'm running the original T-Mobile ROM 1.0.8.something, IPL 1.X, and SPL 1.X. The phone says it's unlocked using the CheckLock program you can download from the forums, or elsewhere, I forget which. I've run the cidunlock with the loki tool multiple times and it finishes no issues.
If anyone has ANY ideas or thoughts, or even if they've run into this I'd like to know.
I'm pretty sure my phone right now won't do the whole A2DP via bluetooth bit, and that's what I'm REALLY wanting. I just got those Motorola HT820's and am anxious to play around with them more.
Anywho. You all rock and I've only been here like a day, but your information, walkthroughs, and just general geekiness(oh yeah, I work for the Geek Squad and we ALL use either the Verizon or Sprint version of the MDA, heh heh) have been most appreciated!
nabibakhur said:
So, I've unlocked my T-Mobile MDA G3 phone both CID and otherwise using loki. I've tried the T-Mobile update off their own site, and here is what happens. I suspect I need a different data cable, but I might be wrong there, so I figured I'd bring the issue to you all because you are the gurus of all gurus...type peoples.
So, here's what goes on. I download the software. I sync my MDA and my notebook. I ensure both machines are on and set to stay on. I check the connection and all is good. Heck, I've even backed up my MDA system using one of those backup utilities for Smartphones available online for trial download(which worked great, btw). So I run the software and click next and check everything it says the check and then it begins. This is where my problem begins and the goodness ends...
The MDA shuts off and just sits there. I don't touch it for fear of what might happen by being impatient, but every time, no matter which ROM I've tried to use for update purposes, the notebook pops up saying that it encountered a "communications error". It doesn't brick the phone, thank God. It simply just requires removal of the battery for 5-10 seconds after disconnecting the USB, then turning it on. It boots fine and all is good, except, no new ROM, same old 1.0.8.something version and bah!
I want to update my ROM and am stuck. I've tried at least 5 DIFFERENT ROMs and loaders and still the same thing.
I'm running the original T-Mobile ROM 1.0.8.something, IPL 1.X, and SPL 1.X. The phone says it's unlocked using the CheckLock program you can download from the forums, or elsewhere, I forget which. I've run the cidunlock with the loki tool multiple times and it finishes no issues.
If anyone has ANY ideas or thoughts, or even if they've run into this I'd like to know.
I'm pretty sure my phone right now won't do the whole A2DP via bluetooth bit, and that's what I'm REALLY wanting. I just got those Motorola HT820's and am anxious to play around with them more.
Anywho. You all rock and I've only been here like a day, but your information, walkthroughs, and just general geekiness(oh yeah, I work for the Geek Squad and we ALL use either the Verizon or Sprint version of the MDA, heh heh) have been most appreciated!
Click to expand...
Click to collapse
Try this sub-forum http://forum.xda-developers.com/forumdisplay.php?f=289
--M
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 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
Hey guys, really need help here. Honest noob here so please try to understand my situation. I updated to Windows 8.1 to see what were the changes but unfortunately I realised I didn't have my activation key, so I decided to use a program called Windows 8.1 Key Finder Ultimate just to see all the features before buying the key ( I don't have money, I'm just a poor student)
So I installed it, and clicked on it. Then it prompted me to install again, which I found peculiar. So I scanned the exe and nothing was wrong. I installed the thing and tried to run it, but it did the same thing so I tried KMS activators instead. From KMSAuto Pro to KMSPico, nothing worked. Something I did along the way triggered a sound driver to install, and it definitely wasn't a Realtek driver, which is my soundcard manufacturer. I didn't really pay much attention as it was 2-3am, and I assumed it would just stop installing due to conflicts with the real driver.
Decided to sleep, went to school at 7, came back home and decided to turn on my laptop to listen to my new CD. No sound. I assumed its just WMP having issues with the CD, so I tried my other players. Nothing! Decided I should try to see the speaker settings and check vol. etc but I can't play any test tone, with the computer telling me "Failed to play test tone". I panicked for awhile but went on a solution hunt. I tried everything from a clean boot to driver update to uninstall then install, disabling audio and re-enabling, so many and nothing works. Five hours later I'm here desparate to find answers from the gurus. (I realised I have no restore points, which is really idiotic of me...)
I remembered the sound driver that installed itself, so I intended to find it and murder it. But being the noob I am, I don't know how to find the right thing in event logs and all the mumbo jumbo. Is there a way to see what changed recently, or installed recently (not only programs) or even what was running a certain periods of time (don't say task manager because I'm not looking for what's running but rather what RAN). Also, are there any ways to see all drivers installed apart from device manager and isolate them to diagnose the issue at hand?
Any solutions provided to me is greatly appreciated, and should be free is possible. I don't have any money on me and I can't find a job to support myself due to school, so please understand that this laptop is really valuable to me and I need all the help I can find here. If any other detail is needed I'd gladly provide them. And please don't condone me for my mistake and stuff, I'm still learning as I go along...
syngamer96 said:
Hey guys, really need help here. Honest noob here so please try to understand my situation. I updated to Windows 8.1 to see what were the changes but unfortunately I realised I didn't have my activation key, so I decided to use a program called Windows 8.1 Key Finder Ultimate just to see all the features before buying the key ( I don't have money, I'm just a poor student)
So I installed it, and clicked on it. Then it prompted me to install again, which I found peculiar. So I scanned the exe and nothing was wrong. I installed the thing and tried to run it, but it did the same thing so I tried KMS activators instead. From KMSAuto Pro to KMSPico, nothing worked. Something I did along the way triggered a sound driver to install, and it definitely wasn't a Realtek driver, which is my soundcard manufacturer. I didn't really pay much attention as it was 2-3am, and I assumed it would just stop installing due to conflicts with the real driver.
Decided to sleep, went to school at 7, came back home and decided to turn on my laptop to listen to my new CD. No sound. I assumed its just WMP having issues with the CD, so I tried my other players. Nothing! Decided I should try to see the speaker settings and check vol. etc but I can't play any test tone, with the computer telling me "Failed to play test tone". I panicked for awhile but went on a solution hunt. I tried everything from a clean boot to driver update to uninstall then install, disabling audio and re-enabling, so many and nothing works. Five hours later I'm here desparate to find answers from the gurus. (I realised I have no restore points, which is really idiotic of me...)
I remembered the sound driver that installed itself, so I intended to find it and murder it. But being the noob I am, I don't know how to find the right thing in event logs and all the mumbo jumbo. Is there a way to see what changed recently, or installed recently (not only programs) or even what was running a certain periods of time (don't say task manager because I'm not looking for what's running but rather what RAN). Also, are there any ways to see all drivers installed apart from device manager and isolate them to diagnose the issue at hand?
Any solutions provided to me is greatly appreciated, and should be free is possible. I don't have any money on me and I can't find a job to support myself due to school, so please understand that this laptop is really valuable to me and I need all the help I can find here. If any other detail is needed I'd gladly provide them. And please don't condone me for my mistake and stuff, I'm still learning as I go along...
Click to expand...
Click to collapse
You can use the reliability monitor under control panel >system and security>action center >maintenance to see a nice time line of events.
If you have a key for windows 8, you can easily and freely update to windows 8.1 using the store (you have to install all windows 8 updates first).
It is best to avoid using fishy .exes because they can damage your windows install and even install mallware.