[Q] XT862 no data on Page Plus - Motorola Droid 3

I accidentally hijacked a thread over in the Epic forum when I came across someone with my exact symptom. I figured I should move my conversation over here so my apologies if it appears that I've "double posted".
I've been searching, reading and trying various 'fixes' for a couple of weeks now with no luck, so I'm hoping someone here might be able to help me out. A little background:
I have a Droid 3 with:
Stock GB 2.3.4
System version is 5.7.906.XT862.Verizon.en.US
Baseband version: N_03.18.29P
Build number: 5.5.1_84_D3G-66_M2-10
The only modifications I made was to root the system and remove some bloatware. I was able to activate the phone on Page Plus for voice and text but no data or mms (of course since mms relies on data). Interestingly, the OTA programming *22890 fails - I had to use the Verizon programming *228 to get it to work. I'm thinking that this might be related to my problem.
After a lot of attempts to resolve, including factory reset, I realized that when I tried to write to the evdo settings the passwords were not being written. After reviewing the cdma workstation output (licensed copy of cdma ws so all functions should work) I found that it was logging "access denied" errors on those particular fields. I also can't modify the HA / AAA shared secret codes in the m.ip profile. I even tried creating a new profile and those fields were protected in the new profile as well. So something is locking those fields - which I assume is the root of my problem. The SPC is the standard 000000.
I also tried using DFS cdma tool with no luck. Something else I noticed using this tool is that there is a section for Lock Codes on the General Tab. When I read these codes from the phone, the Lock extd: field was 11111111. So far I haven't been able to find out what this field is for or how it is used. I don't know if it's related in anyway to blocking access to the data password fields, just thought it was worth mentioning.
Sorry for the long post. Hopefully there's something in my ramblings that will trigger a solution. Any and all suggestions are welcome. Thanks.....

activating and using Droid 3 on page plus should not require any programming
problem could be hardware or software
check
menu>system settings>battery & data manager>
data saver should be uncheck, unless you are trying to limit data usage
and
menu>system settings>battery & data manager>data delivery
check 'data enabled'
check 'background data'
if those are correct
I would just flash the 906 sbf and wipe data, if that does not fix problem is likely hardware
Flash xml recovery files (Stock Rom) with RSD Lite

sd_shadow said:
activating and using Droid 3 on page plus should not require any programming
problem could be hardware or software
check
menu>system settings>battery & data manager>
data saver should be uncheck, unless you are trying to limit data usage
and
menu>system settings>battery & data manager>data delivery
check 'data enabled'
check 'background data'
if those are correct
I would just flash the 906 sbf and wipe data, if that does not fix problem is likely hardware
Flash xml recovery files (Stock Rom) with RSD Lite
Click to expand...
Click to collapse
Thanks for the input. Already did all that. Kinda doubt that it's hardware though. There's always the remote possibility, but my money is on software at possibly the microcode level that's holding those fields in read-only mode.

Maybe SBF the Verizon 862 or 906 ROM?

Ya. Same as everyone else, sbf. BUT also master reset after sbf. Use the latest full sbf that I link to in my thread.
If you know all then proper settings for Ppc then Check a cricket forum for a how to flash and you'll be able to program them and then *22890 to get 3g keys.
Tldr: sbf from my thread + master reset after sbf
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
---------- Post added at 04:35 AM ---------- Previous post was at 04:34 AM ----------
Your baseband may be gsm unlocked variant, I definitely recommend sbf
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

afextwin said:
Ya. Same as everyone else, sbf. BUT also master reset after sbf. Use the latest full sbf that I link to in my thread.
If you know all then proper settings for Ppc then Check a cricket forum for a how to flash and you'll be able to program them and then *22890 to get 3g keys.
Tldr: sbf from my thread + master reset after sbf
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
---------- Post added at 04:35 AM ---------- Previous post was at 04:34 AM ----------
Your baseband may be gsm unlocked variant, I definitely recommend sbf
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've already tried to flash the sbf at the 906 level (I happened to have used the same file you referenced in your thread) but didn't do any kind of reset after I installed it. When you say 'master reset' do you mean factory reset? I've done a factory reset a couple of times but not immediately following sbf. What would the reset do that the sbf didn't already cover? Or is there another 'master reset' that I've missed? It'll be a bit of work to redo the sbf since that means reloading apps, resetting screens, etc.. Since this is the Mrs.' phone I'll need to make sure I've covered any and all other bases before I go this route.
Also, I've tried manually programming and inputting all of the programming info via cdma ws, dfs, radiocomm, and qpts all to no avail. Tried auto programming via *22890 which fails. Auto programming via *228 works but only gives me talk and text.
Thanks for all of the feedback and suggestions. Much appreciated......

do you have baseband N_03.18.29P or N_03.18.32p or other

sd_shadow said:
do you have baseband N_03.18.29P or N_03.18.32p or other
Click to expand...
Click to collapse
N_03.18.29P

so you're not on a complete 906 version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
I would retry VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip
verify the md5:8C33C373BD309AA40C8EBDB458E426F1
flash with rsdlite

sd_shadow said:
so you're not on a complete 906 version.
(Images removed)
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
[/COLOR]I would retry VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip
verify the md5:8C33C373BD309AA40C8EBDB458E426F1
flash with rsdlite
Click to expand...
Click to collapse
I was also playing around with swapping radios so that's probably why there's the baseband discrepecy. Although it's a pain it's probably prudent to spf again to ensure that everything is at a base level.

nvrpayretail said:
I was also playing around with swapping radios so that's probably why there's the baseband discrepecy. Although it's a pain it's probably prudent to spf again to ensure that everything is at a base level.
Click to expand...
Click to collapse
The 890 radio works fine on 906. You can try an esn reset on PagePlus then redo the ota programming to generate and grab new auth keys. I had to do this before on a Droid X on PagePlus.
A free reset tool can be found here. Basically it refreshes your meid in the system like a new device for new auth keys.

Skreelink said:
The 890 radio works fine on 906. You can try an esn reset on PagePlus then redo the ota programming to generate and grab new auth keys. I had to do this before on a Droid X on PagePlus.
A free reset tool can be found here. Basically it refreshes your meid in the system like a new device for new auth keys.
Click to expand...
Click to collapse
this was to be my next suggestion, if after sbf to 906 you still had no data. Basically what happened was, your previous device held the 3g signal when you swapped esn's so new key's could not be generated when otap was performed (oddly enough, the old device may still have a working data connection...)
edit: post #100, hopefully it contain's some sort of factual useful information for someone.

Skreelink said:
The 890 radio works fine on 906. You can try an esn reset on PagePlus then redo the ota programming to generate and grab new auth keys. I had to do this before on a Droid X on PagePlus.
A free reset tool can be found here. Basically it refreshes your meid in the system like a new device for new auth keys.
Click to expand...
Click to collapse
Thanks for the suggestion. Something I hadn't heard of before. Gave it a shot but no joy...... *22890 still fails and have to use *228. Programming took a long time so I was hopeful but alas still no data. arghhhhhhhhhhhhhhhh.......

afextwin said:
this was to be my next suggestion, if after sbf to 906 you still had no data. Basically what happened was, your previous device held the 3g signal when you swapped esn's so new key's could not be generated when otap was performed (oddly enough, the old device may still have a working data connection...)
edit: post #100, hopefully it contain's some sort of factual useful information for someone.
Click to expand...
Click to collapse
Interesting. Although the reset that Skreelink suggested didn't work, you and Skreelink might be onto something.
A little more background. This phone # was ported over from VZW. When on VZW we were using a Samsung SGH-U960. Since I didn't have a data plan, VZW disabled data. When I did the port to PP I activated the Droid 3 at the same time.
For grins, I just turned on the Samsung and it shows a data connection. When I try to access the web I can see the data connection active trying to access Verizon Mobile Web. Of course since I'm not on VZW, it doesn't actually work and I get a message to dial *611. I then turned on an LG phone that was used previously on VZW and it too shows a data connection but when I try to access the web from there it immediately gives me a 'network unavailable' message. So I'm wondering if somehow the data is indeed still linked to the last phone used on VZW. One more fly to throw into the ointment is that for a brief time while I was working on the Droid 3 I switched the PP service to the Samsung so the wife wouldn't be without a phone. When I was done I switched PP service back to the Droid 3 so you'd think that any crossed records would have gotten straightened out during that exchange. But who knows. Any suggestions which way to go from here?

I suggest contacting page plus
Sent from my XT862 using Tapatalk 2

sd_shadow said:
I suggest contacting page plus
Sent from my XT862 using Tapatalk 2
Click to expand...
Click to collapse
@nvrpayretail definitely contact page plus or PM me, I can swap your number to a phone here and see if it works (cust svc can do same thing).
the data block should not stick for your line after you ported, the data block is an account setting and technically you don't have an account with vzw anymore.

afextwin said:
@nvrpayretail definitely contact page plus or PM me, I can swap your number to a phone here and see if it works (cust svc can do same thing).
the data block should not stick for your line after you ported, the data block is an account setting and technically you don't have an account with vzw anymore.
Click to expand...
Click to collapse
I'll try PP but they generally take a hands off approach if you don't have one of their 'supported' phones. I can understand their position. I have a couple of retired old phones here so I can have PP swap to one of them to see if I have the same problem. Thanks anyway for the offer.

nvrpayretail said:
I'll try PP but they generally take a hands off approach if you don't have one of their 'supported' phones. I can understand their position. I have a couple of retired old phones here so I can have PP swap to one of them to see if I have the same problem. Thanks anyway for the offer.
Click to expand...
Click to collapse
Yes, thats why I suggest calling me, I work for a page plus master. Trust me, I know how hard it is to get general cust svc to do ANYTHING on a non-native device, but it's not their fault, if they did then call hold times would be outrageous or plan prices would go up to pay for all the additional csr's. I suggest that if they tell you it's not supported, then ask them for ITCC support. Or it may be ITTC support, I'm not sure what the acronym stands for but basically if the phone is not in their supported devices list but is a verizon branded 2g or 3g phone it may be in their ITTC list and they can conference chat with you and a verizon rep to further troubleshoot. Sadly, if the line is bad because of the data block being "stuck" you may have to lose the line...Porting out and back in may be an option if this is the case, but I've never tested the theory, it probably won't work - i'm sure Verizon keeps previous customer's accounts in a "dormant" state for an infinite amount of time.

afextwin said:
Yes, thats why I suggest calling me, I work for a page plus master. Trust me, I know how hard it is to get general cust svc to do ANYTHING on a non-native device. I suggest that if they tell you it's not supported, then ask them for ITCC support. Or it may be ITTC support, I'm not sure what the acronym stands for but basically if the phone is not in their supported devices list but is a verizon branded 2g or 3g phone it is in their ITTC list and they can conference call with you and a verizon rep to further troubleshoot.
edit: As explained to me by Lisa about 2 years ago...
Click to expand...
Click to collapse
Thanks again for the additional info and suggestion. I generally do every thing I possibly can before contacting vendor support since it's usually a rather frustrating experience. That's a general support comment - not targeted at PP. I've gotta be in the right mood to deal with the poor level 1 support folks (definitely not on a Friday the 13th evening ) before I call them.
I opened a trouble ticket online and will wait to see what they come back with before getting on the phone with them. Who knows, maybe a miracle will happen and some research will actually be done before they try to say 'it's not our problem'
Am I having fun yet???
edit: Alas, I received canned response #103.6 back from level 1 support. Attempting to escalate to ITT(C)C support as afextwin suggests. I don't have much confidence that it will go anywhere. Assuming things stay status quo I guess I'll see if one of my older, retired phones will work and go from there.

So, of course things went as expected with support. Escalated to level 2 and their take was "sorry, ain't our phone". I finally bit the bullet and and did a complete wipe (at least as complete as I could figure out to do, and started from scratch flashing the VZW base flash. I went straight to activate before rooting or anything and surprise, surprise ABSOLUTELY NOTHING CHANGED!!!! In the process I lost my nand backup (of course!!) so it's back to manually reinstalling and setting up everything.
I think I'm at the point where I've fought the phone and the phone won
I sincerely thank all that tried to help.

Related

Potential Solution for Unlocking Bands on Droid 4 in US

Hi Everyone,
I'm not sure how to try this out, since I'm not in the US, and that RadioComm doesn't work for my Droid 4 (it's been upgraded to ICS)
1) Install latest Motorola drivers and RadioComm
2) Launch RadioComm
3) When it RadioComm launches, Click Main -> MA -> Common -> MDM 6x00
4) Click Settings -> USB -> PST USB
5) Click on FTM Common 1
6) Connect the phone to the PC and wait for it to go green
7) Under NVAccess, find the following values:
4870, NV_GSM_850_CARRIER_SUPPRESSION_I
4871, NV_GSM_DCS_CARRIER_SUPPRESSION_I
4872, NV_GSM_1900_CARRIER_SUPPRESSION_I
8) For each value, press Read, then replace all of the numbers with 0. Once done, press write. Repeat for all 3 values/
Let me know if this works!
Again, I mentioned a problem with RadioComm. I'm using Windows 8 x64, RadioComm worked fine with my Bionic on GB, maybe it's an ICS thing, maybe I need newer drivers, etc... Please let me know if this works!
I was able to get this going on my Droid Bionic (which also had a corrupted IMEI number) so if you want to see that post, view it here :
http://forum.xda-developers.com/showpost.php?p=32256347&postcount=780
danifunker said:
Hi Everyone,
I'm not sure how to try this out, since I'm not in the US, and that RadioComm doesn't work for my Droid 4 (it's been upgraded to ICS)
1) Install latest Motorola drivers and RadioComm
2) Launch RadioComm
3) When it RadioComm launches, Click Main -> MA -> Common -> MDM 6x00
4) Click Settings -> USB -> PST USB
5) Click on FTM Common 1
6) Connect the phone to the PC and wait for it to go green
7) Under NVAccess, find the following values:
4870, NV_GSM_850_CARRIER_SUPPRESSION_I
4871, NV_GSM_DCS_CARRIER_SUPPRESSION_I
4872, NV_GSM_1900_CARRIER_SUPPRESSION_I
8) For each value, press Read, then replace all of the numbers with 0. Once done, press write. Repeat for all 3 values/
Let me know if this works!
Again, I mentioned a problem with RadioComm. I'm using Windows 8 x64, RadioComm worked fine with my Bionic on GB, maybe it's an ICS thing, maybe I need newer drivers, etc... Please let me know if this works!
I was able to get this going on my Droid Bionic (which also had a corrupted IMEI number) so if you want to see that post, view it here :
http://forum.xda-developers.com/showpost.php?p=32256347&postcount=780
Click to expand...
Click to collapse
This looks awesome -- I saw your post in the Bionic forum. I was curious if this worked for anyone in the states on T-Mobile? I was looking to get a Droid 4 and use it on Straight Talk. Currently have an Epic, but loved my OG Droid. 3G is fine enough for me -- just curious if anyone is also able to get MMS working as well, along with APN settings?
What version of RadioComm do you recommend? I've tried 11.9.0 and I get the error when I try to open it:
"Error in getting the pointer to CommP2K and/or CommQC. Error number: Exception of type 'System.Exception' was thrown."
If you can help me get past this error, I'd love to try this out...
terinfire said:
What version of RadioComm do you recommend? I've tried 11.9.0 and I get the error when I try to open it:
"Error in getting the pointer to CommP2K and/or CommQC. Error number: Exception of type 'System.Exception' was thrown."
If you can help me get past this error, I'd love to try this out...
Click to expand...
Click to collapse
I'm using 11.12.2, and try to get the latest motorola phone drivers (different than the USB drivers) I think I'm running 5.9 of those.
Sent from my XT894 running ICS
danifunker said:
I'm using 11.12.2, and try to get the latest motorola phone drivers (different than the USB drivers) I think I'm running 5.9 of those.
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Awesome, I'll give it a shot when I get home. Out of curiosity -- I'm assuming this is similar to QPST. If I bork the modem, I should be able to go back to a prior group of settings, right?
SIM Card should be coming in on Saturday or Monday -- so should be able to get some news to everyone by then.
terinfire said:
Awesome, I'll give it a shot when I get home. Out of curiosity -- I'm assuming this is similar to QPST. If I bork the modem, I should be able to go back to a prior group of settings, right?
SIM Card should be coming in on Saturday or Monday -- so should be able to get some news to everyone by then.
Click to expand...
Click to collapse
Cool, just to give you a heads up, someone tried it in the RAZR forum without success....
Sent from my XT894 running ICS
Shoot. I've read that you can get 3G on AT&T without any problems across forums -- did I misread and this was for international use -- not inside the US? I just want to get 3G on AT&T if possible...
Any thoughts? Or can you point me in the right direction?
terinfire said:
Shoot. I've read that you can get 3G on AT&T without any problems across forums -- did I misread and this was for international use -- not inside the US? I just want to get 3G on AT&T if possible...
Any thoughts? Or can you point me in the right direction?
Click to expand...
Click to collapse
Still trying to figure it out... I don't think we have a solution just yet.
I'm a developer outside of all of this (C# primarily these days, but have an extensive background in C/C++) -- and I've flashed phones to cricket with QPST -- so maybe I can help you guys out with this. If you're up for discussing any background that might catch me up to speed on this (already have my phone), would be up for trying to help break into it and enable this. Just send me a PM if you're up for this. Thank you!
Hey all,
I've only used this program for a little bit but I was able to change the values to what the OP suggested however, I used the Motorola Factory USB cable. I couldn't get the program to recognize my phone w/o it.
I'm using stock rooted ICS too.
Sent from my DROID4 using Tapatalk 2
So, you updated it with that -- were you successful and does GSM now work in the US?
Did anything change?
Phone doesn't make calls now
I followed the steps above
Radio Comm v11.12.2
Motorola drivers 2.2.28
Whatever data card drivers came with radiocomm
This did not allow me to see t-mobile or at&t here in the states.
So, random question/thought... If we find another modem with similar chip in another phone -- say on AT&T -- would we be able to read some of these fields and stuff out -- and then push it into our modem?
it would be great if we can set the phone to just swap SIM cards very easily, especially in the US
terinfire said:
So, random question/thought... If we find another modem with similar chip in another phone -- say on AT&T -- would we be able to read some of these fields and stuff out -- and then push it into our modem?
Click to expand...
Click to collapse
Hmm, might be an idea. I don't think that there were many AT&T phones with this capability though. My idea is to compare an XT910 vs an XT912, since that was a worldwide release.
Best idea, get an XT910, put your SIM into it, grab a full radio dump, then put your SIM into the XT912 that doesn't work and grab another full radio dump and compare the two.
You'd need an internation XT910, since AT&T didn't ship them down there, but that would be a great starting place...
danifunker said:
Hmm, might be an idea. I don't think that there were many AT&T phones with this capability though. My idea is to compare an XT910 vs an XT912, since that was a worldwide release.
Best idea, get an XT910, put your SIM into it, grab a full radio dump, then put your SIM into the XT912 that doesn't work and grab another full radio dump and compare the two.
You'd need an internation XT910, since AT&T didn't ship them down there, but that would be a great starting place...
Click to expand...
Click to collapse
Only thing is that I'd have to go out of my way to do that and spend even more money. I just dropped some on the Droid 4 for an off-contract phone. I wonder if there's any way we could ping some of the other forums, i.e. the Razr and see if anyone can potentially get us full-reads, so that way we could compare/diff them?
In addition -- I wonder if it's possible (probably a long-shot) to potentially order a SIM card or something from another carrier in Europe or somewhere outside the US and get it into the phone, but then have it "added" or "roaming" on a US network or something -- if that might provide a workaround?
Just trying to take stabs at it. I figure I'll hold onto the D4 for another month and see if we have any exciting developments -- and if not -- just push it to Swappa.
So i could use this to unlock the radio for overseas teleco use?
remiqaine said:
So i could use this to unlock the radio for overseas teleco use?
Click to expand...
Click to collapse
D4 already has unlocked radio for most telecoms overseas.
terinfire said:
Only thing is that I'd have to go out of my way to do that and spend even more money. I just dropped some on the Droid 4 for an off-contract phone. I wonder if there's any way we could ping some of the other forums, i.e. the Razr and see if anyone can potentially get us full-reads, so that way we could compare/diff them?
In addition -- I wonder if it's possible (probably a long-shot) to potentially order a SIM card or something from another carrier in Europe or somewhere outside the US and get it into the phone, but then have it "added" or "roaming" on a US network or something -- if that might provide a workaround?
Just trying to take stabs at it. I figure I'll hold onto the D4 for another month and see if we have any exciting developments -- and if not -- just push it to Swappa.
Click to expand...
Click to collapse
Not sure what you a proposing in your second paragraph. I have a UK SIM card, and when I plug it in two other phones (Samsung Renown, a CMDA/GSM basic phone) and a Motorola quad-band GSM phone, it works fine in the US. When I move the SIM into my Droid 4, no signal, although it sometimes gives the Unrecognized SIM message. So it's not a matter of non-US sims.
silver6054 said:
Not sure what you a proposing in your second paragraph. I have a UK SIM card, and when I plug it in two other phones (Samsung Renown, a CMDA/GSM basic phone) and a Motorola quad-band GSM phone, it works fine in the US. When I move the SIM into my Droid 4, no signal, although it sometimes gives the Unrecognized SIM message. So it's not a matter of non-US sims.
Click to expand...
Click to collapse
I get the unrecognized SIM message also. That doesn't affect the phone one bit though, since I just press okay to the message and the phone connects to my carrier. Is your carrier one with a Verizon roaming agreement?
Sent from my XT894 running ICS

[Q] Troubleshooting Mobile Data

Good night my fellow modders. Tonight i come with a particular query, mainly, how do i go about troubleshooting the 3G connection of the motorola razr i. Ever since i flashed Omar's Motorola 4.1.2 Rom from Jan-01-2014, i haven't been able to get internet access through my carrier (Not even through 2g) and ive already checked its not a carrier issue (Since i can use my simcard to browse the internet in another phone just fine), i even tried doing a nandroid restore from the stock firmware i had previous to starting this adventurous task to get things working again, but even then the mobile broadband service is a no-no.
I'm at a loss on what to do, since i've already tried reflashing the ROM, reset-ted the phones APN's, and i've also done the suggested file modification of the losialert timer to both, 1000 and 500 (as seen in the same thread). However those efforts have been to no avail and im quite at a loss on what to do.
Im sorry if my english isnt fully understandable (Its not my native languaje) and im also sorry if this isnt the righ section to post about it, but i cant post directly in the thread since I'm a new member. I thank you beforehand for any and all guidance or help you can offer me.
Don't worry, English is not native language for most of forum users.
First of all buy any pre-paid card from different carrier or borrow it sim-card from friend and test it.
I had similar situation with Virgin Mobile. We have quite few operators in my country and I tested all of them but for this I wasn't prepared. I had my new RAZR i and there was no option to use internet with Virgin Mobile.
After few days of fight with different ROM, modding system, installing apps to APN's I figured it was sim-card. Some carriers have old sim-cards which have something wrong with MCC and MNC code and all phones can work on it but not Android 4.1 and above caused APN automation.
I even called to Virgin to ask for changing sim-card but they said they don't have different version of sim-cards, so I asked "WHAT, so every people in Your network doesn't have internet on Android 4.1+??!!" and they said "Yes, it seems so".
And there was no other way but change carrier. Now I have fully working internet without any modifications.
Sorry for so long and boring reply but for my almost 10 years working with mobile phones it was first situation like this.
Chamelleon said:
Don't worry, English is not native language for most of forum users.
First of all buy any pre-paid card from different carrier or borrow it sim-card from friend and test it.
I had similar situation with Virgin Mobile. We have quite few operators in my country and I tested all of them but for this I wasn't prepared. I had my new RAZR i and there was no option to use internet with Virgin Mobile.
After few days of fight with different ROM, modding system, installing apps to APN's I figured it was sim-card. Some carriers have old sim-cards which have something wrong with MCC and MNC code and all phones can work on it but not Android 4.1 and above caused APN automation.
I even called to Virgin to ask for changing sim-card but they said they don't have different version of sim-cards, so I asked "WHAT, so every people in Your network doesn't have internet on Android 4.1+??!!" and they said "Yes, it seems so".
And there was no other way but change carrier. Now I have fully working internet without any modifications.
Sorry for so long and boring reply but for my almost 10 years working with mobile phones it was first situation like this.
Click to expand...
Click to collapse
Thank you for taking the time to answer my query. Unfortunately, i believe your case doesn't apply to me, since i had no issue using the internet with my operator (Telcel) before flashing the new ROM. I've also already called my operator and they made several procedures to try and reestablish my service, however none of them worked, but they assure me it's a problem with my device, since their service is working correctly.
I have no idea what to do now, but i hope can get the minimum required limit i need to ask for support directly on the thread ;(.
I don't know if this will help.
I had this problem with my brothers phone (galaxy s4 mini) last night. Data wouldn't turn on in anyway. Flash in new ROM from recovery didn't did the trick, nor a nandroid did. The only way I have got it to work was flashing a stock ROM through ODIN. In this case it would be RSD lite. Maybe it I'll work, but be aware of the flashing problems red lite can give. Read it a bit. Good luck!
Sent from my GT-P5110 using XDA Premium HD app
Do you have the correct APN entries?? You might need to add it manually...
That happens because it doesn't auto configure (correctly, or none at all) for some carriers because I don't have all the carriers in apn-config.xml -- while your specific carrier ROM might have had it already configured and a specific xml list for them.
If you reset APN's and see all the appropriate ones added it might be configuring a wrong ones by default according to the data from the apn-config.xml one in my ROM, just configure accordingly to your carrier information
Note 1: My ROM does not touch the radio, and since the radio images are international anyway it does not make sense to flash recovery images or anything ... the only problem (assuming you did not break anything in hardware during ROM flashing) comes from the android /system partition which is prone to have incorrect carrier settings for data configurations... any bad number or password updated on your carrier it would be configuring something else by doing "reset to default"...
Note 2: To save the APN entry don't exit ... press the options menu and hit save when done modifying -- else it won't remain saved!
The problem starts when You updated from 4.0.4 to 4.1.2??
Hazou said:
I don't know if this will help.
I had this problem with my brothers phone (galaxy s4 mini) last night. Data wouldn't turn on in anyway. Flash in new ROM from recovery didn't did the trick, nor a nandroid did. The only way I have got it to work was flashing a stock ROM through ODIN. In this case it would be RSD lite. Maybe it I'll work, but be aware of the flashing problems red lite can give. Read it a bit. Good luck!
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Did you try to change the APN settings before you tried this? I'm only asking because I'm considering this option, but i would like to rule it out as my final option, because since i started having this issue I've been reading a lot, and the way you fixed your problem sounds like the stock ROM corrected your issue by giving you the default APN's for your carrier.
Chamelleon said:
The problem starts when You updated from 4.0.4 to 4.1.2??
Click to expand...
Click to collapse
I'm afraid i was already on 4.1.2 by the time i installed Omar's custom ROM.
Omar-Avelar said:
Do you have the correct APN entries?? You might need to add it manually...
That happens because it doesn't auto configure (correctly, or none at all) for some carriers because I don't have all the carriers in apn-config.xml -- while your specific carrier ROM might have had it already configured and a specific xml list for them.
If you reset APN's and see all the appropriate ones added it might be configuring a wrong ones by default according to the data from the apn-config.xml one in my ROM, just configure accordingly to your carrier information
Note 1: My ROM does not touch the radio, and since the radio images are international anyway it does not make sense to flash recovery images or anything ... the only problem (assuming you did not break anything in hardware during ROM flashing) comes from the android /system partition which is prone to have incorrect carrier settings for data configurations... any bad number or password updated on your carrier it would be configuring something else by doing "reset to default"...
Note 2: To save the APN entry don't exit ... press the options menu and hit save when done modifying -- else it won't remain saved!
Click to expand...
Click to collapse
Thanks a lot for getting out of your way to help me Omar; After troubleshooting the device and several talks with my network carrier I've managed to get a so-so signal. I'm not sure if your ROM configures correctly or not the APN'S of my carrier (Telcel) because when i edited them everything was configured as it was supposed to be (I'm not sure about the password since i can't see it though), the only thing that was missing was the APN for GPRS, but I've been reading several forums and almost no android device needs this in addition to the 3G APN (I've added it nonetheless but the device isn't actively using it, my guess is that you've got to choose either 3g or GPRS); I also called my carrier, and the allegedly reset-ed my service.
I'm still not sure if the device is working properly, mainly because the internet access through the mobile network has become very unstable (Sometimes i get disconnected randomly, and turning on the Wi-Fi gets me disconnected automatically), and even though the radio almost always gets an H+ signal (Which is kinda funny, because i used to get 3G more consistently before) i don't think this is normal behavior. I think it may have to be with the los alert, because in my desperate attempts to get things working, i reflashed your ROM and it was set to 1000 once again and I also think that the hardware can't be broken because i wouldn't be able to connect to the data service otherwise.
Because of this i would like to ask two very specific queries, is there a way to flash this setting without flashing the entirety of the zip file?; And in case there isn't, if i flash the zip with the new configuration, and then proceed to perform a nandroid backup of my previous build, will i lose the new 00radio configuration?
I will be tinkering with the device this weekend and will report back if i can find whats wrong, just in case it's something else and somebody needs help troubleshooting this in the future. Thanks to everyone that has contributed so far, i wouldn't have learned so much in so little time without your help.
TemplarWithin said:
Did you try to change the APN settings before you tried this? I'm only asking because I'm considering this option, but i would like to rule it out as my final option, because since i started having this issue I've been reading a lot, and the way you fixed your problem sounds like the stock ROM corrected your issue by giving you the default APN's for your carrier.
Click to expand...
Click to collapse
Hmm, don't know for sure. I have made some changes within the APN list to get it working, didn't work. But the rare thing was that the cm11 one did have data and when he flashed his stock back with a nandroid or a stock zip file data wouldn't turn on anymore. So I can't rule out that it was the APN list that was making trouble, because even with stock it did not work. Only by flashing through Odin it worked. Radio hasn't been flashed in that process.
Sent from my GT-P5110 using XDA Premium HD app

XT883 on XT862 for straighttalk. Still not working

Ok, so I got everything done as per instruction on the bog thread about putting the XT883 radio on an XT862. Done. Every step done. exactly as stated. I have my straighttalk Sim in, and my phone doesn't do anything. got the red no smoking sign in the bars. no service. no phone calls.when I go to search networks. Networks unavailable.
When I go to *#*#4636#*#* set preferred network is set to unknown, and will not change and when I go to select radio band, USA in unsuccessful. well, they all are.
I flashed the radio, moved the build.prop and everything that is to be done. My phone reads as an 883 on my google play account, and all should be fine. Is there a reason the preferred network can't be set? I need to get my phone working because my job is an on call job, and if something happens to my work phone, my personal is kind of important. However, it currently does run N64 quite well, lol. Any help will be greatly appreciated. Thank you and thanks for all your guys' work om getting this whole Droid 3 on ST as smooth of a process as it is.
CPLSeraphim said:
Ok, so I got everything done as per instruction on the bog thread about putting the XT883 radio on an XT862. Done. Every step done. exactly as stated. I have my straighttalk Sim in, and my phone doesn't do anything. got the red no smoking sign in the bars. no service. no phone calls.when I go to search networks. Networks unavailable.
When I go to *#*#4636#*#* set preferred network is set to unknown, and will not change and when I go to select radio band, USA in unsuccessful. well, they all are.
I flashed the radio, moved the build.prop and everything that is to be done. My phone reads as an 883 on my google play account, and all should be fine. Is there a reason the preferred network can't be set? I need to get my phone working because my job is an on call job, and if something happens to my work phone, my personal is kind of important. However, it currently does run N64 quite well, lol. Any help will be greatly appreciated. Thank you and thanks for all your guys' work om getting this whole Droid 3 on ST as smooth of a process as it is.
Click to expand...
Click to collapse
did you get the unlock code and unlock it?
PassingThruLife said:
did you get the unlock code and unlock it?
Click to expand...
Click to collapse
Yes, phone is unlocked and everything should be right. I have it set to GSM/UMTS but I was a little confused on my unability to change it from unknown to GSM...
Redownload build prop, and replace, and/or fix permissions
Sent from my Amazon Kindle Fire using Tapatalk
I tried the build.prop again. nothing. same thing. However, something completely stupid just crossed my mind. We live in a basement Apt out of town a ways. I'm going to check if, when we go to town tonight, I get service. May just be something that silly. I'm going in to look at my radio to ensure the flash was succesful considering I am having an issue with it all together. However my phone reads as an 883 on Google Play, when I hook up to PC, it says something about XT862 drivers are working correctly
Motorola Phones can be sim card sensitive/picky may need a new sim card. even if it works in another phone.
Did you check build prop permissions?
---------- Post added at 02:50 PM ---------- Previous post was at 02:46 PM ----------
rw-r--r--
or
.......... Read Write Execute
Owner .....x ...... x
Group .....x
Others ....x
or
0644
I don't know how to do that, or what you mean. I am looking at the build prop now, but can you tel me where to look, SD Shadow?
Also, when hooked to PC, it reads as an XT883, just so it is known the radio was flashed.
Got permissions. However it just says
Owner, Group and Others, which I checked off the way you said. None of the other things. but the checks were way differant.Is there anything differant for the special permissions? none are checked.
I checked what was stated above. all is still the same. no service available.
which root explorer are you using?
I am using root explorer from Speed software. the one that cost 3.99
I also did a factory reset. kept the build.prop and all. Kind of debating to try the whole thing over. Or is there maybe a couple places to look to ensure everything is in its proper place?
CPLSeraphim said:
I am using root explorer from Speed software. the one that cost 3.99
Click to expand...
Click to collapse
long press on build prop>Permissions
sd_shadow said:
long press on build prop>Permissions
Click to expand...
Click to collapse
got that done. stilll the same.
I guess tomorrow I will buy another $60 kit from walmart with the straighttalk Sim and $45 monthly plan. A little discouraging since the last time I did, the $45 card didn't work because they checked it out wrong. What sucks is I got this new SIM from Straight talk CS because mine messed up, and now I get to blow more money and hope walmart doesn't mess it up this time. I guess I will see tomorrow if it was the Sim Card.
I am getting frustrated, moreso because this phone is pretty awesome, and does some amazing things. Never thought I could play N64 and PS1 on a phone. I just need to make calls. I'm not tech savvy, but these directions are right on the mark, and I know everything was done right, so it's gotta be the SIM. If it is not the SIM, I guess I will be back at square 1 tomorrow.
I did some testing, I think the radio is not getting changed.
Baseband should be n_16.18.16s with or without sim card
see Menu>settings>about phone>baseband
if it is saying unknown, reflash original .890 radio
copy to the fastboot folder from the unzipped unlock.zip file
then reboot phone to ap fastboot mode
and in command prompt
cd desktop
cd fastboot
moto-fastboot flash radio radio2.img
moto-fastboot reboot
baseband should be unknown
unless you still have 890/906 build prop, then it will be N_03.18.29P
then
reflash the XT883 radio
moto-fastboot flash radio radio.img
moto-fastboot reboot
you are getting
sending radio 14404 kb ... okay
writing .....okay
phone is rebooting, and it is showing a screen with a progress bar and it is taking a few to complete? before finishing booting?
Ok, I am going to try that. Baseband says unknown, even though model number says XT883
Ok, I flashed the old radio, thanks for that file, and it still said unknown. reflashed the new radio again
sending radio 14404 kb ... okay
writing .....okay
phone is rebooting, and it is showing a screen with a progress bar and it is taking a few to complete.
I'll be dammed. I got the roaming triangle and a box with a plus sign where the signal goes. says no sim as well... got the baseband number as well. must not have flashed right the first time...
UPDATE: Ok, so I reflashed the radio.. had some funky stuff go on... then remembered again the whole basement thing, so I went to a window. I am now able to make calls and revieve and txt either way. Now that it is all solved, I just have to do my APN.
Thanks you SD_Shadow. I never was going to figure out the radio did not flash... Thanks for your insights and patients, and the files to restore the other radio.
great, your welcome.
Sent from my XT894 using Tapatalk

Phone must reboot

Hello everyone,
I've noticed starting last week my G4 will have a old android style pop-up stating "Device must restart to allow service to continue. Device will restart in ## seconds." It has reboot and later as the options, and will continue to pop-up if i hit later and will even do this when the screen is locked randomly. It is starting to become more often.
I have:
Rebooted phone
checked for apps at cause
Wiped phone with factory reset
updated PRL and other update options (no updates available)
Seems some people here had the same issue on their S5's but with no answer to what was causing it fully
http://forum.xda-developers.com/gal...service-to-t3049657/post60225538#post60225538
Thanks!
Government monitoring you?
I had one pop-up yesterday, we'll see what happens today. If it does I'll post back here. Thanks for the reply back!
Just had one pop-up, requiring me to restart or click later. I'm starting to get frustrated at this. My wife and my co-worker have the same phones, and they have not received this message at all before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in-case the link above does not work here direct: http://imgur.com/xGjDQdU
Does it happen on both WIFI and Cell Network?
Are you using WIFI Calling?
mswlogo said:
Does it happen on both WIFI and Cell Network?
Are you using WIFI Calling?
Click to expand...
Click to collapse
It can happen on both WiFi and Cell network. I do use WiFi calling as my work area is prone to dead signal areas for any carrier. It is completely random as I can be at home on WiFi calling or at the mall on Cellular and it reboot itself due to that message.
Jessooca said:
Did you get your issue fixed? PM me if you need help still.
Click to expand...
Click to collapse
Hi Jessooca, I sent you a PM
I am having this issue now o.k. two phones.
Our problem started after rooting. I followed @rirozizo's video guide on the cubes post. I installed "root checker" that was mentioned on that video as well.
Now every few hours I have the pop up. One time, I was able to press the square key to bring up the multi window/tab view and the name of the tan with the restart message was called Network System Provider.
The window appears, as described in the OP, and states Device must restart. Device will restart in XX seconds.
I did just try clearing the cache for Network System Provider. Hopefully that helps....
Any and all help anyone can offer will be appreciated.
Thank you
Im a troll said:
Hi Jessooca, I sent you a PM
I am having this issue now o.k. two phones.
Our problem started after rooting. I followed @rirozizo's video guide on the cubes post. I installed "root checker" that was mentioned on that video as well.
Now every few hours I have the pop up. One time, I was able to press the square key to bring up the multi window/tab view and the name of the tan with the restart message was called Network System Provider.
Any and all help anyone can offer will be appreciated.
Thank you
Click to expand...
Click to collapse
I bet this is because of a bad SIM card or the pins are disconnecting then reconnecting to the SIM card resulting this reboot popup.
Check the tray, clean it up, and maybe even try a different SIM Card and see if that works.
BTW yes i got mentioned here so i want to help
Sent from my LG-H815 using Tapatalk
rirozizo said:
I bet this is because of a bad SIM card or the pins are disconnecting then reconnecting to the SIM card resulting this reboot popup.
Check the tray, clean it up, and maybe even try a different SIM Card and see if that works.
BTW yes i got mentioned here so i want to help
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Thank you so much.
I will check the SIM, although, I feel pretty confident that it's something else. My reasoning is that it's happening to both our phones and started within hours of being rooted ( I rooted them within minutes of eachother). The only new app installed after rooting on either phone was root checker. The months prior had no issue at all, and Now both are having the same issue at once...unless both SIM card trays got dirty at the same time which would be very coincidental.
I well try your suggestion though. Thank you.
Im a troll said:
Thank you so much.
I will check the SIM, although, I feel pretty confident that it's something else. My reasoning is that it's happening to both our phones and started within hours of being rooted ( I rooted them within minutes of eachother). The only new app installed after rooting on either phone was root checker. The months prior had no issue at all, and Now both are having the same issue at once...unless both SIM card trays got dirty at the same time which would be very coincidental.
I well try your suggestion though. Thank you.
Click to expand...
Click to collapse
Now i don't know anything about Sprint and "american services" but did you flash the right system image specifically for your device? maybe some Sprint service is lost and it's just bugging out? just a blind guess here
rirozizo said:
I bet this is because of a bad SIM card or the pins are disconnecting then reconnecting to the SIM card resulting this reboot popup.
Check the tray, clean it up, and maybe even try a different SIM Card and see if that works.
BTW yes i got mentioned here so i want to help
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
rirozizo said:
Now i don't know anything about Sprint and "american services" but did you flash the right system image specifically for your device? maybe some Sprint service is lost and it's just bugging out? just a blind guess here
Click to expand...
Click to collapse
I appreciate your guesses! I am stumped myself so I will gladly accept any and all help.
I double checked to be sure, and yes I did use the correct files and commands.
The problem presents itself every few hours, so I will see if it continues now that I have cleared the cache I mentioned before.
Thank you again and thank you much for the wonderful videos
I see so many posts in this forum with odd issues and later find they are running unlocked in another country.
Are you in USA on a Sprint Network and getting this error?
I doubt it's the SIM card too.
If on Sprint network you might try ##72768# Hands Free Activate.
Be sure you are near a solid Sprint Signal and WIFI for backup.
Also I find adblocking software gives Sprint phones fits now.
OP Chiming in here, my phone has never been rooted, and is experiencing this issue still. I have flashed the TOT file and also done a recovery factory restore with no luck.
I can clean the sim card real quick and see how it goes today, I am however heading to a Sprint repair tech this weekend to have a new sim card placed in to see if it works.
Get your service code and do an RTN reset. It will wipe your internal storage so just click and drag from your G4 to a place on your desktop. If an RTN doesn't fix it, call Sprint.
Jessooca said:
I replied to your PM hopefully if you go through all those steps, it will fix your issues.... For whatever reason the issues seem to arise if you have factory reset your device, after you have rooted it; theres no proof that's the cause but in most cases, not all, this seems to be a perpetrator. ROOT that is, this issue has happened on various other devices, from 4.4.2 all the way up to a friends Nexus 6 running Android 6.0....
If it fixes your issues; I will share the steps here for anyone else.
Click to expand...
Click to collapse
Hi Jessooca,
I just sent you a PM as well.
Just so everyone is clear, Jessooca is amazing!
Having said that, I am both happy and sad to report that the problem may be solved ( I am not sure and will wait and see). I noticed that twice in the multi-window view brought up by pressing square (forgive me for not knowing the correct term) that the window with the restart message was titled Network System Provider.. so I googled...and then I went through my apps looking for the matching icons. I then found that the error was part of an app by "Its on." Specifically two apps matched the icon; NetworkSystemProvider with an install date of 8/1/2008 (weird?) and NetworkSystemProvider UID with a install date of 5/7/15 ( the day I took the Sprint ZV5 OTA and then rooted).
What I then did was clear the cache of both apps and then of the phone via storage. I have not noticed nay pop-ups since then so I hope that my problem is fixed.
I am also unsure what those two apps are, if they were always there, and if I can safely delete them.
Best of luck OP. I will post again right away if my problem is not resolved, and clearing the cache did nothing more than fill me with false hope!
Im a troll said:
Hi Jessooca,
I just sent you a PM as well.
Just so everyone is clear, Jessooca is amazing!
Having said that, I am both happy and sad to report that the problem may be solved ( I am not sure and will wait and see). I noticed that twice in the multi-window view brought up by pressing square (forgive me for not knowing the correct term) that the window with the restart message was titled Network System Provider.. so I googled...and then I went through my apps looking for the matching icons. I then found that the error was part of an app by "Its on." Specifically two apps matched the icon; NetworkSystemProvider with an install date of 8/1/2008 (weird?) and NetworkSystemProvider UID with a install date of 5/7/15 ( the day I took the Sprint ZV5 OTA and then rooted).
What I then did was clear the cache of both apps and then of the phone via storage. I have not noticed nay pop-ups since then so I hope that my problem is fixed.
I am also unsure what those two apps are, if they were always there, and if I can safely delete them.
Best of luck OP. I will post again right away if my problem is not resolved, and clearing the cache did nothing more than fill me with false hope!
Click to expand...
Click to collapse
i dont have these two apps (i'm on international version, so no carrier stuff here)
I updated to ZV6 this morning and got this message for the first time this afternoon.
"Device must restart to allow service to continue"
After doing some reading, the problem seems to be related to ItsOn.
http://forum.xda-developers.com/spr...nt/zip-remove-itson-sprint-of7-based-t3154181
ItsOn is difficult to remove as it has service running even when the apk files are frozen or removed.

[GUIDE] Using Retail XT1607 With Verizon

UPDATE: Confirmed working on Squid's 11-08 build of Lineage 14.1 as well as various other Oreo/Pie ROMs
I've heard people making claims that the unlocked retail G4 Play (xt1607) doesn't actually work on Verizon's network--and this is true according to Verizon's own site even when you run the IMEI check. After a while I got everything to work just fine on mine, so I'll post here what I did and things I was told by the Verizon people. I apologize if it seems a bit unorganized, I just wanted to rush this out there ASAP since it seems like this is a known problem and I'd hate to see people returning their perfectly good G4 Plays for a supposed problem that got fixed
(Probably the most important thing here) They claim the activation process will take 5-10 minutes, but apparently this is a known problem with certain unlocked Motorola phones. Give it a few hours to see if it'll work eventually. This very well might be what eventually fixed it for me but I'll follow this up below with everything else we tried during this time anyway
Make sure you are running completely stock firmware so it can "provision" properly, at least initially. I remember with my friend's E4 Plus he had to be running on stock at first to get Verizon to recognize and accept his phone before he could flash Lineage on it and use it with that. Apparently this has something to do with outdated APNs that custom ROMs use, or perhaps Verizon just doesn't like custom ROMs at first and they detect/block it. Whatever the case may be, the TWRP Flashable Stock Nougat by Q9Nap will work just fine. What I did was a full wipe before flashing the stock firmware in TWRP. So not only did I do a factory reset, I wiped /system as well before flashing. To do this go to the Advanced Wipe menu in TWRP and check everything except Internal Storage and SD storage
When you're initially getting the SIM card for it, it seemed like they had to apparently tie it to an initial IMEI for it to work. Verizon's system of course said my G4 Play wasn't compatible but the rep said he'd put in another phone's IMEI that did work and then transfer it to my new phone once it was initialized initially. See if the Verizon rep can do this for you as well
If you give it a while running on stock firmware and it still doesn't fix the issue, proceed to the steps below
During the troubleshooting process the Verizon representative at the store took out my SIM card and put it in one of his Verizon phones to test as well. This was just to ensure the SIM itself is working properly which mine was. He made a couple of test calls and test texts with my SIM in his phone and it was all working fine. Obviously I'm no expert with Verizon's activation and provisioning process but perhaps this aided in the SIM being activated or whatever on their end. If you aren't at a Verizon store, find a friend or family member that has a Verizon smartphone and put your SIM in their device for a little while and do a test call or two
Go into the phone's hidden network menu (Dialer>*#*#4636#*#*>Phone Info) and set the Perferred Network Type to LTE/CDMA/UMTS Auto. Give it a minute or two and see if that changes anything
If none of the above is working, or if you're like me where you only had partial service (data/text is fine but cant make or receive calls because you're put in some weird restricted call mode on their network) go to TWRP and do another factory reset. Reboot afterwards and give it a few minutes to see if that fixed anything
If none of the above works or after factory resetting you lose ALL signal and its stuck in a Searching For Signal state (like mine was), go into fastboot and issue the following commands to wipe your phone's modem partitions/settings: "fastboot erase modemst1" and "fastboot erase modemst2". Reboot and give it a bit to see if that fixes it. This is what I believe finally fixed it for me
As of writing this I am running the TWRP flashable stock nougat and have full call/text/LTE capability on my G4 Play with the Preferred Network Type set to LTE/CDMA/UMTS auto. I couldn't get VoLTE working unfortunately, but the rest of the base functionality is all good (which is still better than others I've seen online that say their G4 Play flat out won't work at all)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you had VoLTE working? I can't remember if I had it working a couple of years ago when I got this phone. Moved the SIM from a Nokia 929, so already had a good SIM. But I've never had the original firmware back on the device - always some ROM or other.
jasonmerc said:
UPDATE: Confirmed working on Squid's 11-08 build of Lineage 14.1 as well as various other Oreo/Pie ROMs
I've heard people making claims that the unlocked retail G4 Play (xt1607) doesn't actually work on Verizon's network--and this is true according to Verizon's own site even when you run the IMEI check. After a while I got everything to work just fine on mine, so I'll post here what I did and things I was told by the Verizon people. I apologize if it seems a bit unorganized, I just wanted to rush this out there ASAP since it seems like this is a known problem and I'd hate to see people returning their perfectly good G4 Plays for a supposed problem that got fixed
(Probably the most important thing here) They claim the activation process will take 5-10 minutes, but apparently this is a known problem with certain unlocked Motorola phones. Give it a few hours to see if it'll work eventually. This very well might be what eventually fixed it for me but I'll follow this up below with everything else we tried during this time anyway
Make sure you are running completely stock firmware so it can "provision" properly, at least initially. I remember with my friend's E4 Plus he had to be running on stock at first to get Verizon to recognize and accept his phone before he could flash Lineage on it and use it with that. Apparently this has something to do with outdated APNs that custom ROMs use, or perhaps Verizon just doesn't like custom ROMs at first and they detect/block it. Whatever the case may be, the TWRP Flashable Stock Nougat by Q9Nap will work just fine. What I did was a full wipe before flashing the stock firmware in TWRP. So not only did I do a factory reset, I wiped /system as well before flashing. To do this go to the Advanced Wipe menu in TWRP and check everything except Internal Storage and SD storage
When you're initially getting the SIM card for it, it seemed like they had to apparently tie it to an initial IMEI for it to work. Verizon's system of course said my G4 Play wasn't compatible but the rep said he'd put in another phone's IMEI that did work and then transfer it to my new phone once it was initialized initially. See if the Verizon rep can do this for you as well
If you give it a while running on stock firmware and it still doesn't fix the issue, proceed to the steps below
During the troubleshooting process the Verizon representative at the store took out my SIM card and put it in one of his Verizon phones to test as well. This was just to ensure the SIM itself is working properly which mine was. He made a couple of test calls and test texts with my SIM in his phone and it was all working fine. Obviously I'm no expert with Verizon's activation and provisioning process but perhaps this aided in the SIM being activated or whatever on their end. If you aren't at a Verizon store, find a friend or family member that has a Verizon smartphone and put your SIM in their device for a little while and do a test call or two
Go into the phone's hidden network menu (Dialer>*#*#4636#*#*>Phone Info) and set the Perferred Network Type to LTE/CDMA/UMTS Auto. Give it a minute or two and see if that changes anything
If none of the above is working, or if you're like me where you only had partial service (data/text is fine but cant make or receive calls because you're put in some weird restricted call mode on their network) go to TWRP and do another factory reset. Reboot afterwards and give it a few minutes to see if that fixed anything
If none of the above works or after factory resetting you lose ALL signal and its stuck in a Searching For Signal state (like mine was), go into fastboot and issue the following commands to wipe your phone's modem partitions/settings: "fastboot erase modemst1" and "fastboot erase modemst2". Reboot and give it a bit to see if that fixes it. This is what I believe finally fixed it for me
As of writing this I am running the TWRP flashable stock nougat and have full call/text/LTE capability on my G4 Play with the Preferred Network Type set to LTE/CDMA/UMTS auto. Soon I will be flashing a Pie based custom ROM to see if it works on custom firmware too now that (hopefully) the initial provisioning is done. I will post back my results soon
Click to expand...
Click to collapse
RedCrane3 said:
Have you had VoLTE working? I can't remember if I had it working a couple of years ago when I got this phone. Moved the SIM from a Nokia 929, so already had a good SIM. But I've never had the original firmware back on the device - always some ROM or other.
Click to expand...
Click to collapse
That's something I shouldve mentioned, I did not get VoLTE working on this regardless of stock/custom firmware. So perhaps it's not FULLY working, but still much better than others I've seen online that say their G4 Play flat out doesn't work at all
Just updated the OP with that bit of info too
Interesting, ok. I guessed probably not... but you never know
I bought my 1607 from motorola, havan't had any issues with it on Verizon.
Thanks for the info!
jasonmerc said:
That's something I shouldve mentioned, I did not get VoLTE working on this regardless of stock/custom firmware. So perhaps it's not FULLY working, but still much better than others I've seen online that say their G4 Play flat out doesn't work at all
Just updated the OP with that bit of info too
Click to expand...
Click to collapse
RedCrane3 said:
Interesting, ok. I guessed probably not... but you never know
I bought my 1607 from motorola, havan't had any issues with it on Verizon.
Thanks for the info!
Click to expand...
Click to collapse
Funny thing is the G4 Play actually shows up as "not compatible" on Verizon's own IMEI checking tool. So if you go by what Verizon themselves say you're SOL. This strikes me as weird because Verizon themselves once sold their own G4 Play which is basically the same thing as the 1607 but minus an unlockable bootloader. According to the rep it has to do with Verizon "changing/upgrading their network" which for some apparent reason supposedly makes older phones like this mysteriously not work anymore. Regardless, the only reason I could even attempt at getting it to work was because I proved to the rep that Motorola themselves said this'll work with Verizon (which isn't simple to do since the G4 Play is no longer listed on their site) and I basically told the dude "Motorola says it works and I'm not gonna buy a new phone so do whatever you can to make it work" (and believe me, he sure as hell tried to sell me a new expensive phone during the process)
I figure this guide can also serve as a signal to onlookers that not only will this work with Verizon, it'll work even though they themselves want to assure you it wont
The real question is, has anyone ever figured out a way to get this phone to do VoLTE on Verizon/MVNOs? I'm testing it on Page Plus using AICP 16.1, and VoLTE is provisioned, but I only get 1xRTT for voice.

Categories

Resources