Database Info

[Q] Legend 2 ICS Edition GPS Problem for Infuse

Hey guys, so I just finished up changing my infuse over to Legend 2 ICS edition and I've been playing with it for about a week and I'm having a rather large issue. Whenever I leave the gps ability enabled so that my apps can find where I am the phone has a tendency to dump battery life like there is no tomorrow but worse than that it stops sending and accepting text messages randomly while the rest of the phone continues to operate. There are no warning signs so that I know this is happening and I have to reboot the phone to get it to work again. If I leave the gps feature off this is not an issue however, this is rather useful to have running so that my apps all work. Any idea how to fix this problem?? Thanks for your time.

I've been running legend 2 for almost a couple weeks and legend before that, my gps was buggy at first-it wouldn't lock on to my location. I did a complete wipe and reinstall, then let the phone boot up and let it settle for a while before I did anything else. Haven't had any problems since
---------- Post added at 03:13 AM ---------- Previous post was at 03:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=1318160
http://forum.xda-developers.com/showthread.php?t=1561463
use clean wipe, I run that a few times just before I flash a rom now, haven't had any problems since I started using that.

Thanks a bunch I'll try that out and get back to you on if it works or not in the next couple of days.

Thanks
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.

Klevin2011 said:
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.
Click to expand...
Click to collapse
Hmmm, the phone shouldn't be overheating at all, do you do any tibu system restores? I've had an app cause an overheating problem before. One thing I've learned is when you do allot of flashing, checking out different roms or themes, its good to just do an odin or hemdall flash back to stock that has repartitioning.
It gives you a fresh start.

TiBu
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.

Klevin2011 said:
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.
Click to expand...
Click to collapse
Have you tried the new version 3 to see if maybe that helps? This is first Ive heard anything like this. I guess it works fine using another rom?
Sent from my SAMSUNG-SGH-I897 using xda premium

I didn't even know there was a version 3. I'll have to go take a look at that and see what happens. Thanks for the help.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Still having issues
Ok so I'm still having an over heating issue and my phone refuses to send or recieve texts for periods of time. I'm going to delete a couple of apps to see if they're causing the problem. If that doesn't work any chance that I'm having a hardware issue with the phone, it wouldn't be the first time I've had issues this would be my 5th replacement due to hardware issues in the phone.

Display issues, wierd colorful pixel-noise AND phone unresponsive

Sometimes, after I wake up my phone from sleep the screen shows a wierd colorful pixely noise as shown in the picture, and it doesn't respond to anything besides the power button turning off the screen.
cannot post link, i(dot)imgur(dot)com/TrI3w(dot)jpg
Replace (dot) with . but I hope you understood that
(Sorry for the bad quality, only camara besides my phone was this crappy old digital cam, but it gets the point across)
Sometimes it gets back to my normal lock screen after leaving it to be for a few seconds, but more often than not does it kinda 'lock up' in this mode with me unable to do anything with my phone. Sometimes pulling the battery and starting my phone works and will allow me to continue work/browsing as usual. Other times (right now) it goes back into the 'lock up' right away. Aand it just popped back to normal, this took around 5 minutes, give or take.
I know that when the screen locks up my music continues, for I have listened to music with the screen locked up. I am not sure if my alarm will continue to work as I have not tested it. I can also turn the ringtone volume up/down.
It seems to 'lock up' after long periods of inactivity as I have previously put my phone to sleep and woke it without the issue arising. This was whilst I was chatting. I have not been able to recreate the 'lock up' on demand, aside for just leaving it asleep for extended periods of time.
I hope there is a solution to this problem, and I'd preferably not wipe my contacts etc. I have no idea how I can keep my data through a reinstall, so if I'd have to reinstall then if someone could link me to a thread that explains how to keep data would be awesome.
The phone is a HTC Sensation, 8 years old. This is what it says in the 'about phone' tab.
Code:
Model number
HTC Sensation Z710e
Android version
4.0.3
Baseband version
11.65.3504.00U_11.19.3504.29_2
Kernel version
3.0.16-v1.30.2
SebastianFM#1
Build number
HyperNonSense v1.5 (3.32.401.5)
As you can tell, the ROM isn't the regular HTC Sense ROM, so that might cause issues. I am currently unsure whether the kernel is custom or not.
Any and all help is greatly appreciated! I hope I can fix this problem.
PS I'm sorry if this topic is a repost of any kinds, I've done a quick search for some terms that came to mind but couldn't find a thread that fit my problem.

ToonBoon said:
Sometimes, after I wake up my phone from sleep the screen shows a wierd colorful pixely noise as shown in the picture, and it doesn't respond to anything besides the power button turning off the screen.
cannot post link, i(dot)imgur(dot)com/TrI3w(dot)jpg
Replace (dot) with . but I hope you understood that
(Sorry for the bad quality, only camara besides my phone was this crappy old digital cam, but it gets the point across)
Sometimes it gets back to my normal lock screen after leaving it to be for a few seconds, but more often than not does it kinda 'lock up' in this mode with me unable to do anything with my phone. Sometimes pulling the battery and starting my phone works and will allow me to continue work/browsing as usual. Other times (right now) it goes back into the 'lock up' right away. Aand it just popped back to normal, this took around 5 minutes, give or take.
I know that when the screen locks up my music continues, for I have listened to music with the screen locked up. I am not sure if my alarm will continue to work as I have not tested it. I can also turn the ringtone volume up/down.
It seems to 'lock up' after long periods of inactivity as I have previously put my phone to sleep and woke it without the issue arising. This was whilst I was chatting. I have not been able to recreate the 'lock up' on demand, aside for just leaving it asleep for extended periods of time.
I hope there is a solution to this problem, and I'd preferably not wipe my contacts etc. I have no idea how I can keep my data through a reinstall, so if I'd have to reinstall then if someone could link me to a thread that explains how to keep data would be awesome.
The phone is a HTC Sensation, 8 years old. This is what it says in the 'about phone' tab.
Code:
Model number
HTC Sensation Z710e
Android version
4.0.3
Baseband version
11.65.3504.00U_11.19.3504.29_2
Kernel version
3.0.16-v1.30.2
SebastianFM#1
Build number
HyperNonSense v1.5 (3.32.401.5)
As you can tell, the ROM isn't the regular HTC Sense ROM, so that might cause issues. I am currently unsure whether the kernel is custom or not.
Any and all help is greatly appreciated! I hope I can fix this problem.
PS I'm sorry if this topic is a repost of any kinds, I've done a quick search for some terms that came to mind but couldn't find a thread that fit my problem.
Click to expand...
Click to collapse
Well for starters, Google syncs all your contacts online so once you restore your phone you'll get your contacts back. To me, it reminds me of the same issue I used to have with my Motorola Cliq: systematic hardware failure. The touch screen is starting to go. Which is why only your power button works.
But before we announce the end of your phone, why don't you do this so I can try to help:
Download "GO Backup" and back everything up.
Reboot into recovery and create a backup from there.
Wipe data, cache, and system
Install Virtuous Inquisition (I'm familiar with the ROM and it can help eliminate the possibility that it's the ROM doing the damage)
Set up your phone and restore using go backup. Then Try to induce the problem one you reload all your things
After that, let me know what the end result is
Sent from my HTC Sensation using xda app-developers app

monkor said:
Well for starters, Google syncs all your contacts online so once you restore your phone you'll get your contacts back. To me, it reminds me of the same issue I used to have with my Motorola Cliq: systematic hardware failure. The touch screen is starting to go. Which is why only your power button works.
But before we announce the end of your phone, why don't you do this so I can try to help:
Download "GO Backup" and back everything up.
Reboot into recovery and create a backup from there.
Wipe data, cache, and system
Install Virtuous Inquisition (I'm familiar with the ROM and it can help eliminate the possibility that it's the ROM doing the damage)
Set up your phone and restore using go backup. Then Try to induce the problem one you reload all your things
After that, let me know what the end result is
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I will do this as soon as I regain control over my phone. It has been stuck on this screen for 10 minutes straight now. It really feels like standard electronics failure, starting off small and only on minor occasion and ending in a big endless failure. ****.

There is no wipe system option in my recovery ?
EDIT: Found it, got the ROM working. Screen issue still arises.

ToonBoon said:
There is no wipe system option in my recovery ?
Click to expand...
Click to collapse
Haha is okay is not entirely necessary
Sent from my HTC Sensation using xda app-developers app

monkor said:
Haha is okay is not entirely necessary
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Replying since I'm not sure you'd read my EDIT
Display issue still arises, which means it's an internal hardware issue isn't it?
Does anyone have any experience with opening it up and seeing whether there's a connector loose or something? As I think installing a custom ROM kinda voids the warranty so I wouldn't be able to send it to HTC for repairs right?

Any Updates?
My phone started doing this this week and is now in what seems to be a permanent state of evil pixel screen. Have you had any luck fixing yours? If so, how? Thanks

argcdm said:
My phone started doing this this week and is now in what seems to be a permanent state of evil pixel screen. Have you had any luck fixing yours? If so, how? Thanks
Click to expand...
Click to collapse
It was a hardware issue, contact HTC support and they'll hook you up with a pickup and return service. If your warranty still covers that at least.

ToonBoon said:
It was a hardware issue, contact HTC support and they'll hook you up with a pickup and return service. If your warranty still covers that at least.
Click to expand...
Click to collapse
Thanks for the update, unfortunately I am out of warranty. Glad you got yours replaced.

argcdm said:
My phone started doing this this week and is now in what seems to be a permanent state of evil pixel screen. Have you had any luck fixing yours? If so, how? Thanks
Click to expand...
Click to collapse
I'm having the same problem here

Stock HTC One S got bricked sudenly?

so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.

Very strange!!!
Root the phone and make a nandroid backup. Stock Rom's sucks!!!
Sent from my HTC One S using xda app-developers app

Warmo said:
so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.
Click to expand...
Click to collapse
Did you let the phone die? the phone don't like to do that. Get Dropbox or Google+ that will sync your pictures online.

The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.

-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?

Warmo said:
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?
Click to expand...
Click to collapse
yes, I take care that I don't have more than 5-10 in my list. since that it didn't brick again. but a few days ago I had ~10 in my list and it suddenly restarted again while I was in the wifi list screen and I was like pleeeaassse no bootloop! but fortunately it was no bootloop but my whole wifi list was reset. it must be an error in htc's software.. so we can only wait for updates..

I've had this happen with other Android devices, it's generally some rogue app that screws up the device and only a factory reset will clear it. I've never had more than 3 or 4 wifi points saved so can't comment on that as a possible cause.
It's not 'bricked' by the way, just slightly fubar'd

-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
You are not the only one. I also encountered the same thing because of too much wlan connections and the only thing i could do is run into bootloader and restore factory settings, since i don't have a nandroid backup because i'm not rooted.. fortunately i synced my pictures thru dropbox, and a backup of sms in gmail.. but i don't know why it is happening to us, so this issue isn't an individual case..
Sent from my HTC One S4 using xda-developers app

Reboot issue with JB 4.1.2 vzw newest update on Razr HD

Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!

xgshortbus25 said:
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
Click to expand...
Click to collapse
Never had that issue with the new update. Try doing a factory reset or try the new fast boot files to start fresh. Not sure why chrome would be an issue.try the chrome beta version but I suspect chrome had nothing to do with the reboot just a bad initial update.
Sent from my DROID RAZR HD using Tapatalk 2

Fixed!! I hope!!!
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!

xgshortbus25 said:
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
Click to expand...
Click to collapse
My Wife's phone is doing the Random Reboot thing since the 4.1.2 update as well. I did a Factory Reset on it and it still does the same thing.
I suspect an application is doing it? Because I put the phone in Safe Mode and it never rebooted while in Safe Mode.
But I have No Idea of how to tell which app is doing it, other than to uninstall a random app after every reboot to find out which one it is.
But I would like to try this fast boot option? I know how to get the phone into fastboot, but which files are you redoing? What exactly are your doing ?

Have the same problem. I have done:
SBF 4.1.2
FDR
WIPE
Even tried running a parallel rom with safestrap (bakatang)
The chrome thing did not work
Keeps freezing. Seems the problem is way worse when having the phone play some music.
I am just about unlocking the thing and SBFing back to 4.1.1 but not really interested into unlocking the bootloader. That would be the last choice for me.
If someone knows of some way to fix this, please help, this used to be a great phone...

No problem here with the sfr rom... used for over 1 month now and no problem and my system is always fast...
Sent from my XT925 using xda premium

I've been running some tests for about a week now since I got my RAZR and the results are interesting... I've had lockups and reboots multiple times a day, most often while doing something involving sound i.e. listening to music or playing a game or video. I've tried stock and custom 4.1.2 ROMs and custom 4.2.2 ROMs and it persists so I'm inclined to say its either bad audio software or faulty audio chips. This is everything I've done:
1. turning off sounds (keeping phone on vibrate/silent) pretty much eliminates the random lockups/reboots I got from receiving multiple texts or calls at once. I noticed if I bombarded the phone and made it ring a lot it gave the same results as listening to music but if its just a text or email or call here and there during regular use it the phone works fine.
2. Listening to music, either streamed or local from phone/SD storage and through headphones or speaker, would cause skips and audio cutting out. After a few minutes of this the phone will lock up completely and reboot itself. Strangely enough it happened only rarely or not at all while streaming music via bluetooth to a stereo.
3. I don't think its anything kernel related or if it is its not causing visible errors or wake locks. My battery seems to be just fine through all this.
4. I have tried multiple music/video players, put my SD card with music in another phone and the music plays fine, stock ROMs with nothing disabled/removed still has the issue, custom ROMs debloated and modified also have the issue. I think I've just about covered every base I can as an end user to track down what's causing it but I'm open to suggestions.
I have a replacement scheduled so I will see if that fixes it, I have seen this problem reported quite a few times all over the interwebz but there are also a lot of people not having the issue either so idk. If there are any Devs or anyone skilled in android-fu that can read logcats I will be more than willing to get those for you. Sorry for the essay everyone lol
tl;dr Like others I have freezes and reboots from what seems to me to be an audio software/hardware problem, either built in or from the 4.1.2 update
Sent from my DROID RAZR HD using Tapatalk 2

I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.

barbaroja said:
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/t...roid-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
Click to expand...
Click to collapse
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2

anoninja118 said:
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!

barbaroja said:
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
Click to expand...
Click to collapse
one solution that has worked for me is silencing the phone or putting it on vibrate and I haven't had a freeze or reboot in almost 2 days... the problem seems to me to be related to audio/sound and not listening to music or watching videos along with silencing ringtones has put a stop to it which kind of confirms my suspicions... I will try and flash back when I can but it'll need a day or 2 of field testing to confirm if its a solution
Sent from my DROID RAZR HD using Tapatalk 2

I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.

barbaroja said:
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
Click to expand...
Click to collapse
looks like a negative on the SBF, tried to restore 4.1.1 and it failed halfway through the flash, now won't turn on... working on reviving it... I really need to replace this thing as its been nothing but a PITA since I got it
old school post from my Thunderbolt via Tapatalk

wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it

barbaroja said:
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
Click to expand...
Click to collapse
got it revived with Mattlgroff's new 1.2 utility, was able to force it to fastboot mode... the problem seemed to be some kind of partition error, I tried redownloading the sbf files thinking it was a bad file and got the same error so idk what it is since I'm on stock unrooted 4.1.2. My bootloader is already irreversibly unlocked so that won't be a problem lol but I am a n00b to RSD Lite and Moto devices so I'll tinker with it more when I get some free time
edit: I did have a Maxx HD way back at launch for a month or so running stock 4.1.1 and it ran perfectly, so my idea is its kernel/codec/software related. Hopefully a custom ROM (or hell even stock) with Hashcodes Qcom kernel will fix the issue we're having
Sent from my DROID RAZR HD using Tapatalk 2

I talked with vzw service, the assistant said that 2% of the phones were having this issue, wich for this kind of technology is a pretty big number of phones. Suuggested to send it to Motorola but since its rooted its almost sure not to be replaced by them. What is strange is that not everyone is having this issue. I would be almost sure Motorola is going to release a fix for this, but would not count days. Getting kind of frustrated with this phone I used to like so much. Thinking of going the htc route bc this is getting unbearable.

Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...

barbaroja said:
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
Click to expand...
Click to collapse
My wife & I both have this phone and still are constantly being rebooted. This is even after the software update. I have been wiped, factory reset, and everything possible, but I've not called for a replacement yet. Normally I havea worse luck with those.
Wife used to love this phone, now she hates it and hates we changed from AT&T to Verizon since we have no backup Verizon phones. At least we could take the sim out and go to the iPhone that's floating around the house when the phone went to pot before. Makes me really hate suggesting that we go back to Moto phones since that's all that I've used on Verizon.
Wonder if big red will get the new HTC One....

Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2

barbaroja said:
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
If an sbf didn't solve it then it's a hardware problem.you guys are definitely in the minority with this reboot issue.go get a warranty replacement.this phone and moto in general are solid phones.
sent from my xt926 RAZR maxx hd

Boost Mobile "Assisted Dialing Error"

For the past month or more my phone which is the xt1031 from Boost Mobile has been getting an "Assisted dialing error" and under that I guess is the reason which is "invalid mobile country code". I have had this phone for a few months now and at first it worked perfectly but now its getting this error, missing calls, and sometimes apps claim there is no data connection when there is. What I am wondering is if anyone else has had this issue and maybe fixed it.
My phone has the bootloader unlocked and is rooted so if that can help lead to finding the cause of my issues I am willing to try nearly anything. So far I have tried returning my phone to stock by removing root and relocking the bootloader then doing a full restore of the phone. That seems to work for a little while but I kind of think that when it updates a app on the phone the issue comes back. I think its one of the stock apps thats causing the issue because after the restore it worked fine and I left it stock for a while and I am thinking that one of the newer version of an app is the cause.
So what I am asking is if anyone has had this issue and/or a way for me to find out what is happening when the error occurs.

No one?
Has no one else had this issue or know of a way to figure out what is actually going on? On Republic Wireless people are reporting the same issue so I know its not just my phone. Is there no way to monitor everything happening on the phone so I can maybe see what's actually being done when the error starts.
Well I am getting a free replacement phone so this thread can be closed. I hate being a bad sport but seeing how no one even attempted to help me or give any sort of advice I will keep all the details of how I got the phone replaced after I had unlocked the bootloader (I did not hide this fact from them) and had done other software modifications (also did not hide this fact). I will also keep to myself the details about the 4.4.3 update for Boost Mobile phones.

I am getting that message too
It just randomly pops up, I've turned the feature off and on, results the same regardless off setting. I'm not rooted stock brand new boost moto g. I haven't encountered any issues because of it per say other than that message constantly popping up.