My dad has updated his evo to the 1.22.651.3 update. And now the phone randomly reboots and locks up all the time. He can't ever get the navigation to work for him either(its locks up and force closes). Is anybody else experiencing these issues too? Also whenever it locks up and unfreezes itself he has to reboot the phone to get data services back. If he gets a replacement will it have the same update? Could I just ruu back to the shipped rom?
Sent from my HTC Holiday using xda premium
I would say back everything up and do a hard reset. I've seen a lot of issues get cleared up like that. I would reccomend against getting a replacement unless you have to.
Yeah, if hard reset doesn't work, I would think it's a defective unit. I've had zero problems with update.
(I'm still stock)
Thanks for all of the advice I think I'm just going to try a hard reset. I really like his evo. Might be leaving att and my vivid for one of these soon. They're great phones.
Sent from my HTC Holiday using xda premium
Only issue I see Is the play store app freezes for me.
Sent from my EVO using xda app-developers app
Related
So a friend of mine just got a hold of a droid eris because her droid busted and it is having issues with constantly being in roaming on sprints network.
Is this a common issue, is there any fix for it? verizon rep had no idea and couldn't help.
Did you have her try *228?
Sent from my DROID2 using XDA App
yea that was the first thing i told her to try, it didn't work. From what she said it sounds like it didn't even go through as a working working.
I don't know what else to try... factory reset?
If you haven't rooted that phone for them you need to, and load the Xtsense ROM. It makes that phone rock pretty good.
I loaded it on for my wife (she wanted to keep the Sense options and look). It has yet to lag doing anything.
Good luck
Sent from my DROID2 using XDA App
Ok.. I flashed back to stock yesterday. I was returning the phone because of my GPS issues. I had to reboot to get GPS to lock every time.
After the stock flash, I got an OTA message. I figured "why not"
The GPS seems to work perfect. I can get locks consistently. It also seems a whole lot faster and more responsive. The lagginess is gone.
I highly suggest flashing stock (previous) with RSD lite then getting the update.
Same here. I have service again in my house!
Sent from my MB855
It seems Motorola (or google) is really fast on updates.
This phone is not even two months old and already 2 OTA's.
My son's Epic is still on 2.2!
TheShackSpecialist said:
Same here. I have service again in my house!
Sent from my MB855
Click to expand...
Click to collapse
All you had to do was tell Sprint and they will send you a free airave.
How do u return to stock? I can't install ota. I'm missing native apps?
Sent from my MB855 using xda premium
I agree with most the new OTA really did fix alot of things which I thought the 1st OTA mess up with my Photon.
Plus it also un-rooted the phone... so now I can try to sale it
Sent from my MB855 using xda premium
Im on 1.3 mean rom and havent updated anything.
I dont have overclock either.
If im in a call or something it juat randomly reboots. How would i solve this
Sent from my EVO using xda premium
bamp
This might sound crazy but I had the same issue. Mine was the otterbox commuter case was sticking to the power button a bit and powering off my phone and rebooting. Did you put a new case or something on it?
Sent from my EVO using xda app-developers app
Dont use a case. Updated to 1.7 hopefully it stops
Sent from my EVO using xda premium
i kno its a pain in the a$$ but sometimes running an ruu back to stock and then rerooting the phone helps... worst case.. i did that when my evo 3d kept acting up like that.. and it helped...
Happened again today. Super annoying. If it happens again im going to sprint and demanding a new one
Sent from my EVO using xda premium
Try wiping everything including factory reset then reflash rom.
I did do that. Idk what the problem could be
Sent from my EVO using xda premium
afgomar said:
I did do that. Idk what the problem could be
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Mine does this as well. I talked to HTC and they said if you don't LTE in your area, Sprint LTE that is but have Verizon LTE, your phone may be trying to latch on to the Verizon LTE, and since it can't quite connect it attempt to push more power to the LTE antenna to get it to connect, in doing so, it eventually pushes it pass a threshold and causes the phone to reboot. Apparently the issues seems to be popular in areas where there is no Sprint LTE and other LTE available. Sounds like a software issue on HTC's end, that will hopefully get fixed.
For now, you can try and go a *#*#4636#*#* and change your network to CDMA Only or EVDO Only and see if that keeps it from rebooting. (when you change to CDMA only, make a call right away otherwise you might not get incoming calls or texts)
I dont make many calls but the few calls i usually do make or receive are important and i would hate having to switch that. U think it will work if i turn off mobile network in the drop down settings???
Im in los angeles btw and i think verizon lte is live here
Sent from my EVO using xda premium
So I reset my phone to 1.22.651.3 and didn't take OTA yet because I need to re-lock bootloader and whatevs, but whenever I use my navigation via google, the thing crashes after a couple of minutes. Anyone else have this problem? anybody have a solution? did this get fixed for you via the update?
Yes, I'm having serious crashing problem s too. And I'm on a long trip, so this real ly sucks. Seems to happen when getting a poor signal. Like switching back-n-forth from Sprint and roaming
Sent from my EVO using xda app-developers app
Clear the cache for maps and reboot
That seems to have fixed it!
Sent from my EVO using xda app-developers app
Last night I decided to try to update my prl through the updater in Sense and I got an error code 1233. Called sprint tech support and spent an hour trying to get it fixed. The tech ended up just sending me a new phone, which a huge buzz kill because I've had hboot 1.12 since the beginning with s-off. Was running toasted-deck from irc, and I don't know if that had anything to do with my phone getting screwed up so I figured I'd ask if anyone else has had this problem? I want to unlock this new phone when I get it too, and I'm really going to miss TD if this is a common problem.
I got the same thing while trying to update my firmware.
Sent from my EVO using Tapatalk 2
malicenfz said:
I got the same thing while trying to update my firmware.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
OF wouldn't accept a new phone there's a method of fixing it with WiFi and checking HTC updates then rebooting
cm10ed 3VO
I was getting this too. I had to run an errand up to another major city north of where I live. While there, I figured I'd give it a shot again, and it worked there. If you get the opportunity, try running it in a different area from where you tried.
I'm surprised that they are sending you a new phone for this.
Sent from my EVO LTE using xda app
pbedard said:
OF wouldn't accept a new phone there's a method of fixing it with WiFi and checking HTC updates then rebooting
cm10ed 3VO
Click to expand...
Click to collapse
I searched high and low for a fix before I even called Sprint Tech. Any chance you can point me in the right direction? I'll just send them their locked down phone back if I can fix this one.
sslbaron said:
I was getting this too. I had to run an errand up to another major city north of where I live. While there, I figured I'd give it a shot again, and it worked there. If you get the opportunity, try running it in a different area from where you tried.
I'm surprised that they are sending you a new phone for this.
Sent from my EVO LTE using xda app
Click to expand...
Click to collapse
Unfortunately I did try in a few different areas. I live in Cincinnati and go to school in Dayton, but got the same error in both places. I really wonder how this even happened because I never had a problem running AOSP on my OG EVO so I don't think that could be it.
I had this happen on my 3D and when it did work it only connected to Verizon....weird I know and even the tech couldn't believe but I did a data reset on it and never had that problem again.
Sent from my EVO using Tapatalk 2
So I was on stock with goodies and just out of curiosity switched to mean rom to try and activate my phone. The activation went off without a hitch and now my phone is working perfectly again. So pumped.
if u were able to do it before then all of sudden u can't, it must be sprint
Sent from my EVO using xda app-developers app
I get the error code also, im on flex 2.18 I'm gonna try a different rom tomorrow to see if it still does it, another thing that's driving me crazy is when i call my wife's or my brothers phone it rings once then goes to a busy signal i have to force my phone to roam to call them and it only happens when i call one of them and all three phones are on my account
Sent from my EVO using xda premium
josh030181 said:
I get the error code also, im on flex 2.18 I'm gonna try a different rom tomorrow to see if it still does it, another thing that's driving me crazy is when i call my wife's or my brothers phone it rings once then goes to a busy signal i have to force my phone to roam to call them and it only happens when i call one of them and all three phones are on my account
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Are you using Google voice? I've found that GV messes things up like that.
Sent from my EVO using xda app-developers app
mmhama2 said:
Are you using Google voice? I've found that GV messes things up like that.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
OK i flashed to mean rom and now I'm able to update prl and profile without getting the error, as for the busy tone it was gv, i signed out of gv the calls went thru then i signed back in and get the busy signal again, which sucks because that's never happened before till now.
Sent from my EVO using xda premium
I had the same problem a few days ago. I was Running CM10 and switched over to Stock w/ Goodies to update my PRL and Profile so i can take advantage of LA's new LTE network but i kept getting that error. I ended up unrooting and relocking my phone and restored to complete stock after that it updated fine the first time. I doubt being rooted prevents you from updating either the PRL or Profile.
I was getting the same error code at work. I googled the code ansomeone said it was a connection problem. I believe this because I never get a good signal at work. When I got home my prl updated. I'm on meanrom.
Easy Fix
Turn off WiFi and LTE radio (CDMA only) and try it. You should be able to update the PRL and Profile.
As "zAcHcOmA" mentioned, I also gave them a Thanks for it.. I had the same issue with "Error Code 1233".
My problem started when I noticed every incoming call I tried to answer thru the Handset would basically act as if I missed the call. Seems I didn't have an issue answering through Blue Tooth though. Not exactly sure what is causing this. I'll keep an eye on it after updating my PRL & Profile. Anyways, I did the following and was able to update both PRL & Profile..
1. Make sure Wireless is off
2. Set network to by going to Settings - Mobile Data - Network Mode "CDMA only"
3. I was then able to update both PRL & Profile through System Updates and I then rebooted my phone.
I'll now find out if my issue is resolved or if I still have on going issues.