Database Develop

[Q] Bionic won't activate Pageplus after JB upgrading

I'm a Pageplus user. After flashing 6.7.246 (ICS 4.0.4), I got OTA to 98.72.22 (JB 4.1.2) successfully.
But I'm stuck then when trying to activate Pageplus OTA by calling *22800:
I kept getting "Sorry, this SIM card is not recognized or registered..", no matter how many times I tried.
There's another notified error: "Unknown SIM card detected"
It's abnormal b/c it should fail only 2-3 times, then taking me to the activation screen.
The 4glteSIM card inside was activated before and used on the 6.7.246 stock build.
FYI, I also reflashed 6.7.246 one more time on top of 6.7.246 and didn't encounter the activation problem. So I'm superised to have this issue after upgraing.
Please advice me if you have any idea.
Thanks in advance.

Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app

Thx for your reminding. I'll try this way.
Did you install the cm10 with safestrap 3? I tried to install it on the JB but failed. Does it require a rooted JB?
I tried to search but cannot find an effective way to root Bionic JB.
I'll appreciate if u can give some detail abt: A. the JB rooting method, and B. How to install cm10 (or the justed released Blurry-JB_2.4.zip) while keeping the JB stock rom.
Thanks a lot!
Wilsono1050 said:
Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse

Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app

I managed to have the JB stock rom rooted anyway (by the virtual box approach).
Then I was allowed to install safestrap 3.1, then the newest Blurry JB 2.4.
I tried to "activate" from the step 2 ("2-Getting phone ready for OTA Activation") of the old instaruction:
http://www.howardforums.com/showthr...CS-OTA-Activation-TXT-MMS-3G-ROOT-on-PagePlus
But the CDMA Workshop didn't find the port. I assume the reason is that safestrap has blocked the normal bp-tools booting way.
So I can only start from "3-OTA Activation".
After changing "Network Selection" to "CDMA Only", I rebooted and dialed *22800. Still get the same error "sim card not recognized or registered".
Can you please detail how did you "activate" it under cm10?
Many thanks.
Wilsono1050 said:
Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse

Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app

I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Wilsono1050 said:
Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app
Click to expand...
Click to collapse

may thx. that work!
taller238 said:
I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Click to expand...
Click to collapse

taller238 said:
may thx. that work!
Click to expand...
Click to collapse
Did you get it to work?
Sent from my XT875 using xda app-developers app

did anyone get this to work?
Thinking of just saving myself the headache and getting a droidx2.
I'm running cm10.1 and safestrap 3.11 3. I'm going to try a dealer tomorrow to see if they can activate it on pageplus.
I haven't activated a phone on pageplus for a while. I've been using simple mobile, straight talk and h20

taller238 said:
Still get the same error "sim card not recognized or registered.
Click to expand...
Click to collapse
I had the same problem when I went from GB to ICS. I just ignored it and kept trying and trying (based on advice/steps I found elsewhere) and after a few times it worked. So I would suggest trying it about 10-12 times in a row to see if it works.
Also, here is the method I used for GB to ICS, I'd be interested to know if they help you move from ICS to JB:
Re-activating phone
1. Remove any old Motorola Droid Bionic drivers you may have on your computer and install the newest ones.
2. Turn phone off and turn back on in BPTools mode. Then plug the phone into your computer via USB.
3. Open DFS. Click "Ports" and select the COM port for your phone. Next, click the "SPC" button.
4. Click the "Programming" tab and then the "General" tab. Change the "Ruim Config" to NV_ONLY and click "Write".
5. Click the "Data" tab. Under the "Mode" section, change the "HDR SCP force AT config" option to "RevA_MFPA" and click "Write".
6. Close DFS and unplug phone from USB port.
7. Go to the dialer and dial ##7764726 (##PROGRAM). When prompted for an SPC password, enter "000000" and hit verify.
8. Go to "06 Test Mode". Hit "Next" twice. Then, change the Network mode to "CDMA Only".
9. Back out to the home screen; the phone will automatically restart.
10. After the phone has restarted, go to the dialer and dial *22800. Ignore any SIM card error messages you may see; just keep trying *22800 until you reach the activation screen.
11. Follow the instructions to activate the phone.

I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.

has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD

BuonaDomenica said:
has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD
Click to expand...
Click to collapse
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written

primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
well your links are not working as I want to check it out

primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
BuonaDomenica said:
well your links are not working as I want to check it out
Click to expand...
Click to collapse
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
http://www.howardforums.com/showthread.php/1794056-Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
http://www.howardforums.com/showthread.php/1795498-Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms!
they weren't links,,, google is your friend,,, they are at howardfourms enjoy these links though...
gonna be looking them over myself
.

Kralik said:
I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole[/URL] (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.
Click to expand...
Click to collapse
THANK YOU so much for making this post! I was finally able to activate my bionic after a week of reading the internet. lol. To update this post, yes, you need to do 4b. That step was what got me over the hump.

Anyone know the reason why no 3G? 1x works just fine. When toggle cdma/evdo, it still shows 1x.

I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.

ShadyDreamer said:
I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.
Click to expand...
Click to collapse
THIS! This so much! I had given up on flashing custom rom's after successfully switching my XT912 to page plus (3g/MMS working) and from there had just given up on custom roms after such a large headache. That was a year ago when the phone was coming from ICS to Jellybean (that was a rookies worst nightmare when google is your only quick resource: wrong versions, wrong tools, old information and didn't know a damn bit better. Ugh) anyways, I recently came back to try it out but found out yet again I was trying to use old information when getting through the activation process. This solved it though. I used Titanium Backup (trial version) to delete the system app/process and activation screen popped up on first try! If anyone else has the same issue that I had, where US Cellular answered my activation call, don't fret. I imagine it has to do with the SID (CDMA Network ID) but then I had let the phone sit for a minute and noticed at the bottom "a special number needs to be called to activate this phone" hit that button then the Verizon activation system answers and its good to go from there.
I'll now install safestrap and hopefully get a version of CM11 to run properly which caused this whole re-flashing process. I had a "working" stock rom that would constantly try to activate on phone startup, but 3g would work after skipping all those annoying screens, however when booting to CM11 it was not working with 3g.
Thank you again for that information, I can confirm com.motorola.setupwizard.phoneservice is the culprit to OTA activation problems when switching to PagePlus network.

[Q] New System Update

I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?

ace_case said:
I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
Click to expand...
Click to collapse
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.

skeevydude said:
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
Click to expand...
Click to collapse
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...

ace_case said:
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
Click to expand...
Click to collapse
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.

palmbeach05 said:
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
Click to expand...
Click to collapse
I'd say it's more like posting on Craigslist that you're going on vacation and then leaving all the doors open with your debit/credit card on the coffee table. It's a pretty serious bug, and according to wikipedia, 1.5% of the most popular 800,000 websites are still vulnerable to the bug, not to mention running a sideloaded app or connecting to a malicious website.

got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.

lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
Flashing back to completely stock may be the easiest way to get the update.

lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
If you flash the OTA update manually using something like Philz recovery, you can see the progress on the screen and where it stops updating. For me, it kept hanging on updating the smartactions.apk, which was because I had previously (long time ago) merged updates of the app to my System partition (along with a few other apps that were updated). This will mess up any attempt to do an OTA update, because your "stock" ROM is no longer stock.
I ended up having to flash back to the real stock with Mythtools, then install the OTA zip manually.
If you can't find the zip in your cache, you can download it directly from this post (thanks @skeevydude): http://forum.xda-developers.com/showpost.php?p=52657363&postcount=13

How to disable ota notifications? Or trick phone into thinking it's been updated?

How can I disable ota notifications here? I am rooted.
Or what could i edit in the build.prop that would show I'm up to date? The build info?

Hello? Is this thing on? Lol anyone know how and also avoid any wakelocks?

Or just update the phone?

You can press and hold on the notification, tap app info and tick hide notifications from this app. Alternatively, you can install an xposed module called notify clean if you have xposed. Incredibly useful.

lolcakes203 said:
You can press and hold on the notification, tap app info and tick hide notifications from this app. Alternatively, you can install an xposed module called notify clean if you have xposed. Incredibly useful.
Click to expand...
Click to collapse
xposed doesn't work with ART (the runtime in Android 5.0) so this isn't a solution

You are absolutely correct, that completely slipped my mind. Sorry!

Take take the easy and just upgrade

xxfwmxx said:
Take take the easy and just upgrade
Click to expand...
Click to collapse
Not so easy if you are rooted or anything modified.

Actually it is as I did so to go from 5 to 5.0.1 I was rooted, had twrp, elementalx kernel, and decrypted. Instead of flashing the entire factory image you just flash the needed images. That's what I did and didn't loose any data. There are a few posts here on how to do it. Here is one http://forum.xda-developers.com/nexus-6/help/5-0-1-wiping-t2975382

xxfwmxx said:
Actually it is as I did so to go from 5 to 5.0.1 I was rooted, had twrp, elementalx kernel, and decrypted. Instead of flashing the entire factory image you just flash the needed images. That's what I did and didn't loose any data. There are a few posts here on how to do it. Here is one http://forum.xda-developers.com/nexus-6/help/5-0-1-wiping-t2975382
Click to expand...
Click to collapse
I understand how to do it. I've done it many times before. But the op asked how to get rid of the notification. For whatever reason, some people may not want to take the update, or are modified & don't have time to restore stock, or will be away from their PC over the holidays. It would be useful to know how to disable the ota notification until we have time/ equipment to return to stock or flash images.
What I have done on my n5 is go to /etc/security & rename otacerts.zip to otacerts.zip.bak & reboot. Then try to take the ota & it will immediately fail verification. Voila, no more ota notification. I think this will last until a reboot & then it will try to verify again.
I'm not sure of a more permanent solution.

Thanks Stumpey. Yea haven't had the time yet. Still setting my phone up and haven't even backed up in Tb or Twrp yet. Plus this update is a relatively small one so not in a hurry to manually unroot-update-reroot.
Anyway just turned the notification off like another poster suggested and that's good enough for now. Didn't even realize you could do that.

[Q] Just rooted & installed Xposed, can't receive calls or texts but can send them

[Q] Just rooted & installed Xposed, can't receive calls or texts but can send them
I rooted yesterday via towelroot:
I was on OA1 4.4.4 update, flashed kernel to ND3, rooted, flashed OA1 kernel back.... everything looked good (thread)
Only did a few style mods via xposed, nothing crazy but it then came to my attention that i wasn't receiving text messages.
I am able to send them but not receive.
I am able to make calls and I just noticed I can't receive them. It goes straight to my voicemail.
I reset my APN settings and cleared my application cache but nothing changed.
I'm not sure what else to try, searching has me going around in circles without getting much good information.

steelcity said:
I rooted yesterday via towelroot:
I was on OA1 4.4.4 update, flashed kernel to ND3, rooted, flashed OA1 kernel back.... everything looked good (thread)
Only did a few style mods via xposed, nothing crazy but it then came to my attention that i wasn't receiving text messages.
I am able to send them but not receive.
I am able to make calls and I just noticed I can't receive them. It goes straight to my voicemail.
I reset my APN settings and cleared my application cache but nothing changed.
I'm not sure what else to try, searching has me going around in circles without getting much good information.
Click to expand...
Click to collapse
Did you try disabling xposed then clearing cache?

nutt_case said:
Did you try disabling xposed then clearing cache?
Click to expand...
Click to collapse
i didn't. i'm not sure how i would disable it other than totally uninstalling the framework. I may try that, but honestly I don't think it is xposed, I think some sort of setting got messed up during the kernel flashing.
i am unable to get google voicemail to work either.
getting mmi error codes
i got one call to go thru earlier today and thought maybe it was fixed but that was the only one.
still can send but not receive.

steelcity said:
i didn't. i'm not sure how i would disable it other than totally uninstalling the framework. I may try that, but honestly I don't think it is xposed, I think some sort of setting got messed up during the kernel flashing.
i am unable to get google voicemail to work either.
getting mmi error codes
i got one call to go thru earlier today and thought maybe it was fixed but that was the only one.
still can send but not receive.
Click to expand...
Click to collapse
4.4.4 update was buggy as all get out I had all kinds of problems so I went back to NG3

I have been messing around with god knows what all morning and finally am able to accept calls. so there is some progress.
still can't receive text messages
can't activate google voicemail either
when i try to **004*1(voicemail number) code to activate google voice
i get "call forwarding connection problem or mmi code. conditionally for all basic services"
edit: i was able to get calls for about 5 minutes. now straight to voicemail again.

OPOfreak said:
4.4.4 update was buggy as all get out I had all kinds of problems so I went back to NG3
Click to expand...
Click to collapse
i might just end up doing that. the fact that virtually everything is working fine besides RECEIVING calls and texts (and now voicemail) makes me think it is just a matter of a network settings tweak and i dont need to factory reset.... but i have been at this for several hours and nothing seems to be working

I uninstalled xposed and the same issues are persisting. can rule that out

considering reflashing the oa1 kernel

steelcity said:
considering reflashing the oa1 kernel
Click to expand...
Click to collapse
Worth a shot...if that doesn't work might be best to reflashing back to stock and start fresh.

OPOfreak said:
4.4.4 update was buggy as all get out I had all kinds of problems so I went back to NG3
Click to expand...
Click to collapse
is there a thread you can point me to for this process?
is it as simple as flashing a ng3 rom and then running towelroot or do i have to go back to nce first?
edit: i suppose this thread is still relevant.
it sounds like i should go back to nce first then put the ng3 on my sd card and load it thru stock recovery

steelcity said:
is there a thread you can point me to for this process?
is it as simple as flashing a ng3 rom and then running towelroot or do i have to go back to nce first?
edit: i suppose this thread is still relevant.
it sounds like i should go back to nce first then put the ng3 on my sd card and load it thru stock recovery
Click to expand...
Click to collapse
The threads links are still active and yes that's the correct thread

if a mod sees this, you can close the thread
i spent hours trying to get my phone to receive calls and texts and never found a solution.
i ended up flashing the original stock rom and starting over and i am back rooted on 4.4.2 ng3 and so far all is well

steelcity said:
if a mod sees this, you can close the thread
i spent hours trying to get my phone to receive calls and texts and never found a solution.
i ended up flashing the original stock rom and starting over and i am back rooted on 4.4.2 ng3 and so far all is well
Click to expand...
Click to collapse
I would have been interested to know what the issue was, but I'm glad you finally got it sorted out. :thumbup:

"downgrading" from CM12.1 to stock 5.1

i'm pretty sure i did somethign wring when i downgraded my phone, and i'm not sure what steps to take now to fix it. i went from CM12.1 to the new 5.1 release, but my certain actions don't seem to want to work, although others do... i downloaded the firmware for my pure edition, and went through all the steps with mfastboot (flashign the image, recovery, some 14 odd steps)
problem is, i'm not revieving notifications, or phoen calls it seems. my phone also doesn't ring, and certain things like the twist to start camera dont' seem to want to work, or the double pull down notification bar.
how should i proceed from here?