it all started two days ago and i thought it maybe a new gb flash issue.... when I slide the face to answer I can answer the call but it stays stuck on that screen for 15 - 30 sec and or i get android process not responding. same when I would hit the call, the phone on the other end would start to ring but there was a lag in going to the next screen....
I have wiped reflashed restored re odined and now I am on stock ec05 and it is always the same.....
I am waiting for a replacement to come in 2 days but wonder what this is being caused by? hardware? i have tried it in different areas and same results...
thanks
Turns out the ribbon cable was bad between the two parts of the phone.....
have you changed modems?
did you try to odin stock ec05 and not restoring any data or apps, then try making a call?
also make a call without the sd card in.
good luck
thanks for reply, just tried the sd thing. am now on stock ec05, i hope.... replacement phone should arrive tommorow... thanks sprint.... btw build froyo.eco5 stock?
Related
Ok my Evo stopped vibrating at all on everything. Even when I first boot it, the vibrate doesn't work.
I dont have the insurance, but can I still go to like a Sprint Repair Center and swap it or can they fix it?
Or do I have to send it to HTC?
First determine if it is hardware or software. What happens when you hold down the volume down button... Do you ever feel it vibrate then?
Nope its defiantly hardware
Seems like that would be a manufacturing defect covered under warranty.
nick8197 said:
Ok my Evo stopped vibrating at all on everything. Even when I first boot it, the vibrate doesn't work.
I dont have the insurance, but can I still go to like a Sprint Repair Center and swap it or can they fix it?
Or do I have to send it to HTC?
Click to expand...
Click to collapse
Download an app called sound manager. After it's installed hit menu and vibrate settings and make sure they're turned on. (just to make sure, it doesnt hurt) Good luck.
Try dildroid.
Sent from my PC36100 using XDA App
lol tried all those trust me im not a noob i would know if its software def hardware HTC said it would take 2 weeks wtf!!
I had the same problem with my evo....it stopped vibrating at all and i actually found out it was a result of dropping the phone. i have to be extra carefull now with mine because if it falls it will stop vibrating again and i will be forced to drop it again purposely untill it vibrates again...lol
give it a good shake, mines done that once before and that was all it needed to start working again
edit: just noticed this thread is three months old...
Hey xHausx
xHausx... thanks!!! it worked like a charm, vibration is now working again on my 2 months old EVO.
Thanks again!
Having the same issue here. Could someone link me to the RUU that would correct this?
Original post:
Hi All,
I've recently realized that none of my notifications will cause my EVO to vibrate.
I rooted my phone using unrevoked about 4 months ago, and up until about a month ago everything was working fine, when the vibration notifications suddenly stopped.
I have tried checking all settings (which are set correctly), downloading the Sound Manager application, and most recently (today), flashing to the Fresh 4.1 ROM, all to no avail.
I have also attempted (unsuccessfully) flashing back to the original EVO ROM (3.2 i think), after setting S-chip back to "On", but was receiving an error message stating that the main version I was trying to flash is older than the current one.
Attempts to revert back to factory defaults also did not correct this problem.
I have been searching different sites for about 3 days now hoping to find some information on how to correct this or perhaps someone who has has a similair issue.
Any assistance would be appreciated.
Thanks in advance.
Need some help. My wife's Tmobile S2 locks up and freezes when she takes pictures. Only a battery pull will get it going again and once it restarts, the picture is no where to be found. Its not 100% of the time, but it does happen too often. We have a 17 month old boy and she is constantly frustrated when trying to capture random acts of funniness.
This originally happened on a rooted phone. Tried switching where the pictures were being stored from phone to sd back to phone with no luck. Tried a factory reset and went back to the stock rom. Still no dice. Did all the stock updates. No luck. Sent the phone in for a warranty exchange and had the same problem with the replacement. She is now on her third S2 (completely stock, latest firmware) and she is still having the same problem. I don't know what else to try. Hoping someone out there has had this issue and found a fix. Thanks in advance everyone!
My s3 was running on Wicked Sensation and it was working perfectly. All of a sudden, my power button kept screwing up and then the phone randomly turned off. It was stuck in a boot loop but it turned off at random points in the boot process. It got as far as the wicked sensation loading screen a couple times but it didn't make it pass that. Next, I tried to clear cache and do a complete reset and that got the same result. I decided to restore my nandroid of CM10. Oh it takes a couple attempts to get to recovery. Most of the time it doesn't make it past the Galaxy s3 screen and turns back off. But eventually it made it to recovery and I was able to clear everything again and restore my nandroid back up. Now when booting, it occasionally makes it to the set up process and shuts back down. I was eventually able to complete it and the phone worked for 5 minutes but then it reset. I then decided to retry the nandroid back up and I eventually got back to the set up. Since that, I have not been able to complete it but I got to the gmail screen multiple times. I'm not exactly sure what the problem is.
At first I thought maybe it was the power button being pressed down by something but comparing it to my dad's S3, it looks the same so as far as I can tell it's not that. I'm not at home but I will try to unroot and use Odin to flash back to stock. I'll update this then but until then, does anyone else have an idea what I should do? It doesn't seem like going back to stock will work but I've got my fingers crossed.
UPDATE #1: Well this is strange, if I keep the back door cover off just a bit it seems to work. Hmm.. I'm not sure if that's just a coincidence but I'm not willing to completely put it back on til I get home. Oh and if the screen times out it takes a while to turn it back on. I hope this isn't the symptoms of a pre-motherboard failure that some people are reporting... JK it turned off again
UPDATE #2: Okay so now I have another problem. The phone doesn't stay on long enough for me to unroot.. Damn.
porshce2 said:
My s3 was running on Wicked Sensation and it was working perfectly. All of a sudden, my power button kept screwing up and then the phone randomly turned off. It was stuck in a boot loop but it turned off at random points in the boot process. It got as far as the wicked sensation loading screen a couple times but it didn't make it pass that. Next, I tried to clear cache and do a complete reset and that got the same result. I decided to restore my nandroid of CM10. Oh it takes a couple attempts to get to recovery. Most of the time it doesn't make it past the Galaxy s3 screen and turns back off. But eventually it made it to recovery and I was able to clear everything again and restore my nandroid back up. Now when booting, it occasionally makes it to the set up process and shuts back down. I was eventually able to complete it and the phone worked for 5 minutes but then it reset. I then decided to retry the nandroid back up and I eventually got back to the set up. Since that, I have not been able to complete it but I got to the gmail screen multiple times. I'm not exactly sure what the problem is.
At first I thought maybe it was the power button being pressed down by something but comparing it to my dad's S3, it looks the same so as far as I can tell it's not that. I'm not at home but I will try to unroot and use Odin to flash back to stock. I'll update this then but until then, does anyone else have an idea what I should do? It doesn't seem like going back to stock will work but I've got my fingers crossed.
UPDATE #1: Well this is strange, if I keep the back door cover off just a bit it seems to work. Hmm.. I'm not sure if that's just a coincidence but I'm not willing to completely put it back on til I get home. Oh and if the screen times out it takes a while to turn it back on. I hope this isn't the symptoms of a pre-motherboard failure that some people are reporting... JK it turned off again
UPDATE #2: Okay so now I have another problem. The phone doesn't stay on long enough for me to unroot.. Damn.
Click to expand...
Click to collapse
Sounds like something went wrong with whatever you flashed...can you get into download mode and stay there without the phone powering down? If so, Odin back to stock: if not, u have a defective power button and you should see Sprint.
Sent from my SPH-L710 using xda app-developers app
dante32278 said:
Sounds like something went wrong with whatever you flashed...can you get into download mode and stay there without the phone powering down? If so, Odin back to stock: if not, u have a defective power button and you should see Sprint.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yeah I think it might be the power button as well. I'm taking it in to Sprint today. Hopefully they don't notice it's on custom.. :fingers-crossed:
Okay, I've had my S3 since July of 2012. It has worked perfectly up until about 3 weeks ago. It has just started rebooting randomly and it says it's not sending texts, but the people I'm texting say they receive the message that supposedly fails to send like 5 or 6 times. I've spent the last 2 weeks trying to find a solution online and couldn't find anything. I have flashed probably 15 different roms, including stock rooted. Now I am on complete stock unrooted with stock recovery and I'm having the same issues. I used odin to return to stock. I only have 4 apps installed aside from the bloatware that comes with the phone. I'm sure the texting issue is with T-mobile's service, but the rebooting can't be. It's random, but I can always tell when it's about to do it because the screen will come back on right after I lock it and a few seconds later it will reboot. I have also taken the phone apart to see if the power button is jammed and it wasn't. I removed the actual power button and put it back in just to be sure. The phone still reboots randomly. Is anyone else having this issue and if so have you found a way to stop it? Any suggestions will be appreciated. Thank you for looking.
I guess nobody has had these issues.
Sounds like a defective phone.
Sent from my SGH-T999 using Tapatalk 2
It would of been easier if you had warranty on to just return it instead of going through all that hassle.
Sent from my SGH-T999 using xda app-developers app
I have the same issue, pretty sure its the power button sticking. I'm using the home button to wake it up and a widget on the lock screen to lock it for now until I send it in.
Sent from my Nexus 7 using Tapatalk 2
It stopped. I don't know what it was, but I ran stock for a few days and it just quit. Didn't do anything, but flash it back to stock, It did it for a couple of more days after I flashed it back to stock and then it just randomly quit. It's been almost a full week now and no random reboots. If it starts happening again then I will probably just get a replacement. I do have the insurance through T-mobile, but I don't want to pay the deductible.
Could some dust etc. making power button stuck causing reboots? It could also be unstable rom. If you are oc/uv 'ing the phone that could also do that
Sent from S♣ with XDA App
I had a similar problem with my Amaze, turns out one of the connector pins to the battery was miss aligned and would on occasion cross the line and short. Luckily nothing catastrophic but the phone would just reboot, sometimes continuously. After I straightened it out, problem solved.
Evo4eva said:
Okay, I've had my S3 since July of 2012. It has worked perfectly up until about 3 weeks ago. It has just started rebooting randomly and it says it's not sending texts, but the people I'm texting say they receive the message that supposedly fails to send like 5 or 6 times. I've spent the last 2 weeks trying to find a solution online and couldn't find anything. I have flashed probably 15 different roms, including stock rooted. Now I am on complete stock unrooted with stock recovery and I'm having the same issues. I used odin to return to stock. I only have 4 apps installed aside from the bloatware that comes with the phone. I'm sure the texting issue is with T-mobile's service, but the rebooting can't be. It's random, but I can always tell when it's about to do it because the screen will come back on right after I lock it and a few seconds later it will reboot. I have also taken the phone apart to see if the power button is jammed and it wasn't. I removed the actual power button and put it back in just to be sure. The phone still reboots randomly. Is anyone else having this issue and if so have you found a way to stop it? Any suggestions will be appreciated. Thank you for looking.
Click to expand...
Click to collapse
I'm actually having this exact same issue, as well as crashes which seem to happen when copy/pasting text. Reboots, spamming people supposedly failed messages, the works....
And I'm with Sprint.
This is the SECOND S3 that has done this to me. I returned my first one after being fed up with it, guessing it must have been a hardware problem since I couldn't find anyone else that had this issue.. but this one has done it too, so I just figured I had to accept it....
phsh I wouldn't accept a piece of hardware that acts like that... bug 'em til they fix it or get you something else like the s4
Sent from my EVO using Tapatalk 4 Beta
Interesting to read this. I got my S3 in October, and it just started doing this. Twice it has simply rebooted, both times have been after I uninstalled an app. My phone is completely stock, unrooted. Never been rooted. I took it out of the box and updated it to JB and haven't done anything else. I'm not getting any messaging issues, just the reboots. I'm using Nova Prime, and uninstalling by dragging the icon to the trash can.
I'm not sure what caused mine to stop, but it did. It hasn't done it again since it stopped either. I flashed back to complete stock, unrooted and used triangle away. It was still doing it for maybe a week or two after that, but then it just stopped. It has been working fine ever since. That includes trying 4 or 5 different roms after it stopped just to see if it would do it again. Been running wicked on the same phone for months now without any of the issues I previously had. If your phone is doing this then I suggest either waiting to see if it stops on it's own like mine or get it replaced.
Hey Guys, I have been beating my head against a brick wall trying to fix my phone.
Yesterday I was on a call with someone and suddenly I lost service (not uncommon for where I was since I have weak service there), but this time the phone was frozen. The dialer screen was on but was frozen. My phone would not react to anything. So naturally I pulled the battery and rebooted the phone. The phone started up as normally it would but then after 5 minutes of the phone running it froze again. During those five minutes I never received any cell signal.
The most recent "work" I had done on my phone was change the kernel to the AK Kernel on the guide here. This was done 3 days before anything started happening. I tried a new kernel because ever since upgrading to Paranoid 3.0 my phone was acting slow and occasionally I would get a screen of death typically about once a day. The 3 days that I had the new kernel, everything was working great (phone was faster, responsive and no SOD).
I tried restoring a nandroid before upgrading the kernel and it made no difference. Ever since the first time my phone down freezes after 3-5 mins after booting up. Nothing that I have tried has fixed the issue.
I have done a clean install, tried locking and re-rooting, tried a different kernel. All to no avail. Please help I am thinking there is something seriously wrong and may need to take it back to verizon. I am trying to restore my device to stock but am unable to do so. I have been using this guide: Restore to Stock. Any suggestions to make it "clean" enough to get verizon to replace it?
I'm going through withdrawals, please help!
Could not fix it, so I contacted tech support and explained everything that I did to try to fix and they just sent me a warranty replacement. I hope that it was a device error and not something that was caused by other ROMs or Kernels.