Database Users

Failed ROM update - power failure

Apologies if this has already been dealt with elsewhere. Tried to update ROM - was in cradle with power and connectivity with XP pc. Update started and was working fine until I got an RPC service failure message informing me that PC would shut down in a minute!! After this I have the update screen saying it will take about 5 mins to complete and do not turn power off, etc. Cannot get rid of this - have I created a fancy paperweight or is there a way out of this?

If yor XDA can not power on, try the Bootlader method:
http://www.xda-developers.com/forum/viewtopic.php?t=1717

And check your system for viruses. You have at least one: http://vil.nai.com/vil/content/v_100547.htm
Chris
P.S. The reason for the RPC stuff and the shutdown....

Yippee
Thanks all for advice. O2 xda up and running again! Now I can try xda-developers rom again without viruses!!
Got hit by w32.blast.worm!! What are the odds of that happening when upgrading ROM!
Thanks again.

Hi guys
Just to let you know that the blasted virus is quite prevalent. After reading this thread, I checked my computer and found the msblast.exe in the winnit 32 directory. Didn't even realised it was there till I read this forum !
Just to warn anyone out there to check out the site and clean your system.
Cheers
Vic

I have found the most comprehensive virus scanner that I have seen, it gives free online automatic or manual updates, allows you to have your email scanned before reaching you and also does its thing in real time in the background, all that and its FREE, go to www.avast.com and download the home edition, you will never regret the couple of minutes filling in your details, it even speaks to you. I dont have any connection with this company, I just think they are brilliant.

Hi
I am using AVG anti virus which is free as well; go to http://www.grisoft.com/us/us_dwnl_free.php if you want to try using this.
I will try that site you recommended as well.
I know this is not the proper forum for this but wonder if anyone has any idea how to disable all those irritating messages from Messenger Service that pops up on your screen now and then when you are on the internet? There are ads directing you to download some softwares to "cure" this problem but costs money. Also I don't seem to have this problem with Windows 98 and only when I use Windows 2000 that this irritating messaging service is present.
Hope if someone is able to give some advice.
Thanks
Vic

Ms Balster
Sorry this is slightly off topic but it may be helpful to somone.
There are two ways to beign infected by blaster.
1 Run the pacth that fixes the vunrability in RPC.
2 Use a firewall that blocks the RPC ports the windows xp one does this by default.
If you have blsat most of the big virus checker developers have free removal tools. I used the one at http://www.symantec.com. As far as I know it does little dmage to the vistim pc, although the 16th of every month it produces a distributed dinal of service attack on windowsupdate.com.
I also recived blast on monday lunch time. I removed it by the end of the day. Luckly my rom update had not fisnished downloading so I had got round to installing it. (Perghaps there is something to be said for a slow connection . )

Sound Problems

I am running the stock ROM from Sprint (WM 6.1). To my knowledge I do not have anything really wacky installed...and have not installed any new programs...but the following problem has developed...
Periodically my sound will jsut stop working. If I turn the phone off and back on, the sound seems to come back (by phone I mean the screen using the power button on a short press -- not actually causing the phone to power off). Sometimes that works and sometimes if doesn;t the first time...
Sometimes the sound will simply come back on it's own.
I have not done a hard reset yet, becuase I do not want to spend another three hours rebuilding my phone....
Any ideas?

Try installing a new radio. Some radios don't work well with ROMs, therefore giving intermittent sound.
(Also, for the sake of making a hard reset easier, use Sashimi to preload your cabs )

First, as a side note, if you spend 3 hours rebuilding your phone, sounds like you don't backup, I highly suggest doing that.
Anyways, there could be a number of reason why the sound is out. Since you say you hve installed nothing, I would guess a hardware issue. I would go pickup a new device.

TheChampJT said:
First, as a side note, if you spend 3 hours rebuilding your phone, sounds like you don't backup, I highly suggest doing that.
Anyways, there could be a number of reason why the sound is out. Since you say you hve installed nothing, I would guess a hardware issue. I would go pickup a new device.
Click to expand...
Click to collapse
I have backups....I back up several times a week...but since I do not know what is causing my problem...will restoring the backup help...
I did not say I did not install anything ... I said I did not think I installed anything wacky...and have not installed any new programs for a while...

Hopefully by restoring, it will work properly, then you can narrow down the problem.

HTC touch HD stops working

Hey, I've looked around and searched some in the forums but haven't quite found what I'm looking for, sorry if this already been brought up.
Anyway, my Touch HD stops working while I run youtube application, this means, that the whole phone will lock/freeze itself and I can't even return by the "home" button and the phone won't even vibrate, it's just dead but the screen still shows. Same happens when I run TomTom and Media player at the same time, this really bothers me cause I'd like to be able to listen to music at the same time while I'm driving. The only way then to bring the phone back to life, is by using the restart button, and I really don't want to open my phone every 2 minutes just to restart it. Anyway, is there anyone who can help me with this? I have no idea what it can be...
Answers are really appreciated, thanks alot for reading and thanks in advance!

could be due to other installed programs... i would uninstall all programs except TomTom and YouTube and see if you have any problems. if not, then it could be due to one of more of the programs you removed. i would then add each program back to my device retest and if you have a problem you know its related to the program. if this process fails, then a hard-reset may be required to clear any issues.

Incoming Call Screen

So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.

Hmm...if it were me I'd definitely start with uninstalling that video driver and see if that changes the behavior.
Also, are you using the stock lockscreen or do you have CHT lockscreen enabled via CHTE? If you do have CHT's enabled, then next you might want to switch it off and see if it helps.
I don't know for sure that either of those will resolve that, but that's where I'd start troubleshooting.

After your new rom finished flashing, did you perform a manual hard reset (as recommended by most chefs)?
I've found that there is more chance of the rom being unstable if you dont.
(flashes dont always take first time, no clue why, but i'd estimate about 1 in 10 flashes just isn't stable, yet the next flash with the same rom is stable, , , I've also noted similar results when installing an OS on my PC, , , sometimes it just doesnt wanna take properly.)

theidealone said:
So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.
Click to expand...
Click to collapse
I read somewhere that the "unleaked official ROM" caused more problems than it was worth. I got the 2.13 ROM on the leaked version before it was made official and it has been working great since. I read that they made more changes and then made it official and that it was causing phones to be bricked and most phones ended up worse than they where before the the upgrade. The only "negative" thing i experienced was the screen sensitivity but it appears that the cab featured in the sticky at the top of the post fixed that!? Kinda strange If all else fails Factory Reset and try again. I always like to take a baseline reading. When my phone began acting screwy I would restore and run it stock for a few days to see if problems persisted...then after about three or four days slowly begin installing things...

Thanks for the responses! I will start with sirphunkee's suggestions. As I was typing, I started thinking the Driver Patch was a good possibility. Also, I have noticed that the phone doesnt just "sleep" the screen when I put the phone to my face, it locks. Im assuming this is something to do with CHTE's lock, because as sirphunkee mentioned, I am using the CHTE lock, instead of the stock.
Im going to start there, and see what happens.
Also, I did NOT do a manual hard reset. How would I go about doing so (yes, Im a HUGE noob. More of a car guy)? Im hoping I wont need to do this, as Im assuming I will need to restore all of my contacts, reorganize them, and reset everything else, as if the phone were new out of the box... Correct? But in case that is necessary, how do I do so?
As far as the leaked or official version... I couldnt find it on T-Mobile's site. I read a thread here, where it had been there then removed, due to people having issues with the download. I then was searching Swype or something, same forum, and found another thread, where someone had a link to the download through T-Mobile. Kinda hard to explain, but I will see if I can find the link, and the thread.
Thanks again guys! I really appreciate it. And thanks for taking it easy on me.

I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.

theidealone said:
I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.
Click to expand...
Click to collapse
Thanks for the effort though, you'll be able to put up links after just a few more posts (it's listed in the forum rules...hint, hint). Also, toreone already threw up a new thread in this section with that link for everybody, so don't sweat that
EDIT: oops, missed the rest of your questions there. The hard-reset is exactly what you said...resets the phone to factory-fresh condition. Yes, contacts will have to be reapplied, but sorting really shouldn't be an issue depending on your method of backing up and restoring them. I highly recommend using the built-in Microsoft Myphone utility for that (and it's wise to let it back them up regularly too, just in case, I just have mine set to do it each night while it's charging).
You can perform a hard-reset a couple of ways:
1. on your settings tab, hit "menu", then "all settings", then "system". You'll find an icon in there titled "clear storage". Run that, use 1234 as the code, and it will do its deed.
2. with the phone powered off, hold both the vol up and down buttons at the same time, and then press the end/power button to turn it back on, then it will take you into the same hard-reset process as the first method.

[Q] N4 USB stopped working yesterday

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