Database Users

Error 67 issue and how I resolved it

I recently had problems with my phone constantly giving me "Error 67" and I could not get data through the Sprint network at times, other times it would work fine. I searched on google and this forum a great deal, but could not find anything that fixed it. I performed the profile update, PRL update, contacted Sprint and did some thing in the dialer starting with ## (I do not remember the numbers) that did some kind of auto update, and even installed the official 2.1 patch. Everything seemed to work at first, but nothing sticked for very long before the issues continued. The issues first started when I had my phone overclocked and slightly unstable, I thought that I had maybe damaged the phone and needed a replacement.
After a week of all this, I had an idea. I had just recently sold my BlackBerry Pearl (8130) to a co-worker, he still had not had data turned on for the phone but could make calls with it. The next day at work I asked to see his phone. He could not pull up any internet data, but under connections data was still turned on. I turned it off (since he did not need it anyways) and tried it out. It has been 2 days now without any errors. The only thing I can figure is that even though I cleared out all my data on that phone, it still had my password to connect to data. Since it is a smart phone, it would try here and there, even though there is no need for data. The network would see my phone trying to connect after the BlackBerry and boot it since that password is already connected.
The only reason I made this post was because I could not find any solutions on the net that helped me at all. I hope with this post maybe I could save a few people the headache I went through.

Restricted access changed message after 4.2.2

Hello guys and gals
I'm trying to fix my issue and while doing some search I haven't found a fix or what's causing this issue.
Phone is rooted running stock rom and kernel
Manually updated to 4.2.2
After 24 hours on 4.2.2 I came home and turned on wifi like usual, placed the phone on the orb charger and noticed 2 notice on the screen.
Both of them said "Restricted access changed" one for calls and the other for data.
I cleared them and tried to make a phone all and a notice appeared on the dialer screen and the call didn't get thru. I asked my wife to call my phone and it send the call to vm.
Called Tmobile to see if it was something on their end and they said no and asked me to power cycle the phone , yeah like that;s going to help.
I have wipe back to factory, data, cache, dalvik and no luck.
It only happens when the wifi is on, it only started after 24 hours of manually flashing 4.2.2
Any help is appreciated in find the fix for this issue.

happened to me in 4.2.1.
but not that frequently in 4.2.2
I wonder the reason too
Sent from my Nexus 4 using xda premium

It seems that when you turn on "2G only" setting that seems to work but I'm not happy with this temp fix.

Sudden issues with wifi + LTE, MHC19Q (Solved)

Edit 5: Gonna go ahead and declared this solved, the problem hasn't come back since I factory reset and reflashed MHC19I (not Q) from scratch. No more issues with wifi not autoconnecting or taking excessively long to connect, no more battery drain (got nearly 48 hours this weekend including a good amount of time spent in a poor/oversaturated service area at the Grand Prix), etc. Probably going to wait until the May update before flashing any OTAs.
Edit 4: Two days later and still seems to be working fine. I'm seeing some other issues on the April update (significant battery drain, slow wifi connect, etc.), so this morning I tried rolling back first to January (wouldn't get LTE) and now to March (fine so far). With the exception of keeping my media, I'm setting this up completely new, i.e. redownloading everything from the Play Store, to avoid any weirdness from restoring backups.
Edit 3: A factory reset done via TWRP (which retained my media) seems to have solved it for now. At any rate it's been acting normal longer than anything I've done before. This includes restoring my apps + their data via TitaniumBackup (but not system backups), reflashing SuperSU and otherwise getting my phone back to where it started. I've tested things that were known to cause it before like having wifi active but leaving my signal area and having it revert to cell data. The only issue I've noticed now is that wifi no longer seems to autoconnect when it's in range of my router. Not a huge deal but kind of annoying, if anyone has a fix for this I'd appreciate that too.
Edit 2: This issue is NOT resolved. The problem came back after working for a little while. Once the LTE fails the wifi will never reconnect on its own. It seems like everything still works except loading images from anything (reddit, instagram, etc.) and loading bookmarks. I can make google searches, download apps, go into reddit comments, go to instagram profiles I've never been to before, and so on. Is my device defective?
Edit: It appears that going through the motions of flashing the latest update (save for recovery.img and formatting userdata) has fixed the issue. This includes reverting to the stock kernel and flashing the vendor.img, which I hadn't done before. Wifi can be flipped off and on and will reconnect and there are no "!"s anywhere in sight. Strange considering I essentially went through the whole process minus the stock kernel and vendor.img, just out of order, with no effect.
Can anyone offer insight as to what piece of that process might have fixed this? It's not clear to me which pieces of the update are responsible for wifi and cellular connectivity besides the radio and kernel. Leaving the original post below in case anyone has anything to add or is going through this same issue. I'll update this post if the issue returns.
---
As of just this afternoon I'm suddenly getting a strange new issue that I can reproduce pretty consistently. I first noticed that my wifi signal was claiming to be connected but with no internet, and showed a little exclamation point next to it. I disabled wifi, and noticed the exclamation point jumped over to LTE. In both cases, I can still essentially use the connection. I disabled cellular data with wifi connected and could still browse the web, and likewise if I disabled wifi and the exclamation point was back on the LTE symbol. However, I notice some apps like Instagram will refresh posts but no longer load images, and reddit will load posts but not follow any links or load any images either.
Things I've tried:
-Flashed the 2.50 radio (down from 3.61)
-Flashed the MHC19Q system.img and cache.img
-Installed ElementalX kernel (at first it looked like it fixed the LTE issues, but really it just made the "!" go away; still seeing the same issues when I connect to wifi and then disconnect)
-Deleted and readded the nxtgenphone APN (I'm on AT&T)
-Tried to get into *#*#4636*#*#; I get "Connection problem or invalid MMI code."
-Cleared cache/dalvik in recovery (hey, you never know)
-Rebooted my router to make sure it's not an issue there; all other wireless devices on my router are fine
-Removed and reseated the SIM card
In all cases I can still send and receive texts and certain apps will continue to function about halfway, such as Instagram mentioned above. Switching airplane mode on and off doesn't help. Furthermore, once the wifi connection first gets the "!", it will no longer automatically reconnect as it doesn't find a working internet connection.
After an initial reboot it will appear to be fine; wifi connects automatically, no "!"s anywhere in sight, and everything seems to work. As soon as I disconnect from wifi, this issue starts. As mentioned, it will no longer reconnect to wifi and cellular data doesn't seem to work.
Anyone have any thoughts or suggestions as to what the issue may be? This started out of the blue this afternoon, I haven't made any changes to my phone since flashing the April image. My bootloader is unlocked and I'm rooted, and save for the ElementalX experiment (going to go back to the stock kernel) everything else is stock.
Any help is appreciated. If you need any more info, let me know.

Did your problem get resolved or did it come back. I'm having a number of problems on t-mobile since upgradingj to mhc19q

acathrow said:
Did your problem get resolved or did it come back. I'm having a number of problems on t-mobile since upgradingj to mhc19q
Click to expand...
Click to collapse
So far so good, the issue hasn't returned, although I'm really not liking the latest update. I'm considering rolling back (is that something I can do? I don't see why I couldn't) to January or so.

I'm still in limbo. T-mobile have been helpful but it's in Google Nexus support's hands and they have been less than responsive to say the least.
Next step is likely replacement device but in the mean time I just finished flashing 19i and will see if that has the same issues, then I'll try the previous build.
I'm kicking myself that I didn't check the version numbers I was on before applying April update. Ah well, lesson learned,

acathrow said:
I'm still in limbo. T-mobile have been helpful but it's in Google Nexus support's hands and they have been less than responsive to say the least.
Next step is likely replacement device but in the mean time I just finished flashing 19i and will see if that has the same issues, then I'll try the previous build.
I'm kicking myself that I didn't check the version numbers I was on before applying April update. Ah well, lesson learned,
Click to expand...
Click to collapse
Out of curiosity are you doing a full wipe before flashing different builds? I noticed in my case the issue didn't go away until I did a factory reset, which I think suggests something was corrupt or otherwise affected in the system partition. Since doing a factory reset (and now after doing a couple more) the issue seems to have gone away and I'm no longer having wifi/LTE issues - well, except for not getting LTE at all on the January update, so now I'm back on MHC19i.

Current status: My issue appears to be with t-mobile band 12, the new band that t-mobile is rolling out now.
It appears that the phone "prefers" band 12 to the older bands (like 4).
Rolling back to an image before band 12 was added (eg MDB08K from October) gives me back reliable LTE on band 4.
Sent logs to t-mobile and Google and waiting.

Samsung S8 Glitch? .. I've got one for ya....

So.. Story begins..
I bought my S8 a few months back.. Worked flawlessly (Stateside).. Then I came overseas and the problems began.. I requested my service to be suspended by Verizon and after doing so my phone began to freak out.. I don't know for sure if this is the cause but having just received my replacement device and experiencing the exact same issue. Could it be possible?
Issue: No matter what I am doing on the phone it will freeze for a split second then appears to refresh.. For example.. If I am typing an email, as I am writing my keyboard locks up and the phone becomes unusable then it jumps to the top of the app and then I can continue .. It is SOOOO frustrating because for example.. SnapChat: While I am writing and the screen freezes and refreshes, I lose everything I wrote.. If I'm scrolling through Facebook .. It jumps back to the top..This became more frequent and even more annoying! Even if I am in the settings menu scrolled all the way to the bottom.. it freezes for a second and then jumps to the top of the app.. So.. I began removing apps I thought could be the cause of the problem.. I cleared the cache on the phone as well as the apps, reset settings, removed/re-added Google accounts, even tried some developer options to scale down the graphics, background processes etc.. No avail.. I finally caved in and contacted Verizon who put me in touch with TechCoach app to remote in a see the issue for themselves.. All the troubleshooting steps they walked me through, I had already done.. So they sent me a replacement.. I set the new phone up, installed the software updates, just a few apps to test and sure enough same issue! Then I wiped the phone again.. didn't install any software updates, I left it bare bones and even set the phone up as new (no restore from Google)... So as I am writing this TechCoach wants to send me yet another replacement device.. But I'm certain the "Certified Like-New" S8 they send me will end up doing the same thing.. What it appears to be to me (No expert here) is that once I came overseas and suspended my line.. There's some service/app that is trying to push/pull over network data and since it's unable to do so it's causing the phone to glitch? I mean I really can't think of any other reason this could be happening .. Furthermore, I tried different Wi-Fi connections, changed performance modes, disabled many "enhanced features" ... Any ideas/suggestions greatly appreciated while I wait for the replacement device.... Thanks XDA!
Update:
Verizon had to reactivate my line before they could send a replacement... So I asked the rep to keep my line active to see if the issue persists.. Would you believe it worked flawless as it did when I first bought it without issues.. So my theory was right!!! Some service running in the background is attempting to refresh without connectivity.. I'm now going through every system app to disable and test ... more to follow!

After upgrade, wifi connects, but all apps show off-line

After upgrading my phone from rooted stock 7.0 to 8.1 using this TWRP flashable stock image, it worked 100%. Not a single glitch. I did a dirty install and all of my apps and settings were exactly as before. I was so thrilled that I talked my father into doing the update (I coached him over the phone) in the same exact process I undertook.
Everything seemed to go perfectly, however, on his phone (which was configured exactly as mine was) the wifi doesn't allow data to transfer.
He is able to connect to his router/AP, and it pulls an IP/DNS from the router. I see his phone in the list of devices connected. Signal strength is perfect. There are no device restrictions on the router. Other wireless devices are able to use the web through the router w/o any issue.
Yet, any he opens says it's offline or fails to connect to the web. As soon as he turns off wifi and moves to LTE (T-Mobile), everything works.
It's almost as though there is some global setting that is acting like an out-bound firewall preventing the wifi from accessing the internet.
I've posted a request for help at the thread where I downloaded the rom, but have not had any replies. I'm hoping to reach a broader audience here, just in case this is not rom-specific problem.

This is a bug in the upgrade and is not fixed even in latest update. It is already being discussed in moto forums. Follow up the discussion here,

thank you for posting that link. I just read a number of the most recent pages, and I'm wondering if this really is the same problem. In my case the Wi-Fi is solidly connected. There are no disconnects and the signal strength is 100%. The problem is that the apps do not recognize an internet connection. I haven't found anyone over at the Lenovo forums mention similar symptoms. Only that they are having issues with Wi-Fi dropouts. What is even more confounding, is the fact that my phone had zero issues, and his phone has this bug. All things being equal, you would think that the problem would be on both phones. Or on neither.

Try this, reboot into recovery, wipe cache and reboot. This usually fixes most problems after a major system update. If not, try a full system wipe. You'll have sign in again and set up everything again. That should work as a last resort.
Sent from my Moto G (5) Plus using Tapatalk

Thanks for the recommendation. because the phone is 700 miles away, in my senior Father's hands. I'll have to walk him through that. But after doing the upgrade, we did do the wipe cache as part of the update. I'll try it again, but I am not optimistic. As a last resort, we will do a wipe, but I'm trying to avoid that at all costs because I know how challenging it is for him to set everything back up.and years gone by, I recall being able to fix permissions from the recovery. But now when I look under TWRP I see only fix contents, with a strong warning that it may cause bootlooping. So that's the last thing I want to do.

Well, I'm a bit embarrassed to admit clearing the dalvik cache/cache fixed the problem. We absolutely ran that routine immediately after applying the update, but apparently it did not do what it was supposed to do. I suppose that's because we wiped before booting for the first time? Either way, I had him do a nandroid full backup, and then using the advanced/wipe/(dalvik & cache), it worked. He is thrilled - an me, even more so as it means I don't have to hold his hand to get his phone set up from scratch.