Database Users

Change device name?

Is there a way to change a device's name, such that a carrier can't tell what kind of device it is?
I'm a bit concerned that Cingular is showing which of my phones I'm using when I login to their site. I'd rather not have them know I'm using an 8125 most of the time, instead of the 2125 I purchased with a data plan and such.
I'm running one of molski's roms now, so if there's something that could be changed and reflashed, I'd do that too...
Ideas? Or is it all IMEI based, and is being determined from that?

Miwa said:
Is there a way to change a device's name, such that a carrier can't tell what kind of device it is?
I'm a bit concerned that Cingular is showing which of my phones I'm using when I login to their site. I'd rather not have them know I'm using an 8125 most of the time, instead of the 2125 I purchased with a data plan and such.
I'm running one of molski's roms now, so if there's something that could be changed and reflashed, I'd do that too...
Ideas? Or is it all IMEI based, and is being determined from that?
Click to expand...
Click to collapse
Hush and don't fret about the website, it's in the User-Agent portion of the HTTP call to the server. It intelligently pulls the name of the device from it and then displays information relevant to you. Kind of like if you go to Google.com while in japan, it redirects you to google.co.jp, they traced the IP back and found it was based/located out of Japan and forwarded the client accordingly.
It's all IMEI based for device authentication, and unless they bothered to write down the IMEI number from your 2125, they won't be able to tell. I had a SideKick2, an NGage, and SE K750i all at the same time on my account. They couldn't tell what was what, but knew I was a phone fanatic, most carriers aren't alarmed when you have 2 or 3 IMEI number associated with your SIM card, it's not weird, however they will start to wonder when your SIM is tied to say, 10 IMEI numbers, all recently.
The only other way they might be able to tell, is if the device has a "heartbeat" where it connects to the network to pull data down for one reason or another, and is very specific about where it gets the data from. Then they might be able to track what device you have, but that level of scrutiny into your packets, is illegal for any provider, and only obtainable by FBI or other such agency, and only if you're a bad bad evil person.
So now the question comes down to, do you have 10 phones you plug your SIM into, OR, are you a bad bad person who deserves to be in jail? If the answer is 'no' to both. Breathe a sigh of relief just as much as we all do, because we know then we don't have a criminal in our midsts.

I'n not terribly worried about legality, more them bumping my plan to the $40 PDA connect, instead of the $20 Smartphone connect. Or even worse, disabling the data plan, and setting it pay-as-you-go. That'd be a nasty suprise.
It's just a bit weird to have the 8125 show up, when they shouldn't know I have one.

[Q] NFC compatibility: ISIS, Google Wallet, and embedded SE

I know there are several other threads that deal with the titular separate topics...I even started one myself before the phone was released. However, I wanted to make this thread to pool all the relevant questions about the general topic of NFC on this phone under one roof, as it were, since almost none of the following questions have been answered very thoroughly.
1) What is the status of ISIS compatibility on this phone? Version 1.09, I can personally confirm, works fine with the Verizon variant, but the app has recently been marked as incompatible on Google Play. The ISIS webpage only lists the AT&T variant of the Note 3 as compatible with the service, which seems inconsistent. Verizon also doesn't seem to have updated their branded version of ISIS to 1.9 alongside T-Mobile and AT&T, so it's extremely confusing, and I want to know whether the app will continue to be supported on the Verizon Note 3 or not?
2) What is the status of Google Wallet tap-to-pay? It's fairly obvious that the normal, non-NFC version of Google Wallet works properly, but I haven't heard anything definitive on the status of bringing the tap-to-pay version to the Verizon variant. One thread suggested that it may be more difficult to do than simply changing the build.prop to the Sprint version and adding the required SE authorization keys, so what's the status?
3) Related to question 2: Does the Verizon variant of the Note 3 even include an embedded secure element? It's fairly easy to acquire an SE-enabled SIM card from Verizon, but one thread awhile back suggested that the phone may not even include an embedded SE, and also suggested that that was what was holding up (or, rather, making impossible) this phone's Google Wallet port. Can anyone with authority on this phone's hardware answer this question?
Again, sorry if this seems redundant--these are just loose ends, and I thought it would be useful to bring them into one thread for coherence.

Reading up on some of the other threads the non Sprint variants do not (by default) have the required libraries flashed (Google wallet fix for SGS3 US variants AT&T, T-MOBILE, US Cellular, VERIZON, etc), although since the hardware is the same, flashing the required libraries (properly) should not bork the phone. From this question 3 could be answered as "There should be a hardware based secure element in the phone".
For question 1) it is quite possible that ISIS may be on the downslope. From September 20, 2013, PC Mag was reporting that Capital One was dropping supporting for ISIS Capital One Drops Support for Isis Mobile Wallet with a zdnet report on a CTIA panel discussion Mobile payments: Are we there yet? CTIA panel talks up Isis.
For question 2) it's hard to tell at the current moment. The reason being is obviously about the physical secure element required. With the latest version of android (4.4 'KitKat'), Google collaborated with Doug Yeager and Ted Fifelski (of SimplyTapp) to bring Host Card Emulation to the official builds of Android (Google gets around the carriers with Host Card Emulation for NFC payments).
Back in 2012 SimplyTapp proposes secure elements in the cloud/ both of these gentlemen approached the problem of the inaccessible secure element by 'using the cloud' (or more technically accurate, an active data connection) to emulate the secure element. The only caveat was because the official builds of android didn't include the libraries required for HCE (ie ISOPcdA, ISOPcdB, etc) that was built from starch via Doug Yeager (GitHub Repo for the NFC libaries) could only be included in forked, unofficial builds of Android, most notably the CyanogenMod Roms (Emulating a PKI smart card with CyanogenMod 9.1).
With Google taking the cloud approach it is possible that Wallet may eventually work on all NFC phones running 4.4 (and hopefully on unofficial builds including the CyanogenMod Roms.
Hope this helps
Joe

Does the Note 2 google wallet hack to enable Tap to Pay work on the N3?

deputydog95 said:
Does the Note 2 google wallet hack to enable Tap to Pay work on the N3?
Click to expand...
Click to collapse
No, unfortunately. If you have a Sprint Note 3 then it already works, and if you have an AT&T/Verizon/T-Mobile model then Host Card Emulation isn't supported at all by the NFC chip. Kind of seriously aggravating that they went with a different NFC chip in those models, if you ask me. I really love the Note 3, but I absolutely will not be getting a Note 4 unless HCE is supported by the hardware AND the software; if it's available on some carriers, but not on the AT&T models, then I'll almost certainly change carriers.

[Q] Verizon apps + Root + Move to TMo

I upgraded my unrooted Galaxy S5 to lollipop and it was bad, slow, freezing a lot. I disabled many Verizon-bloatware apps and lollipop is now a buttery smooth beautiful thing!
What pros & cons would rooting a phone generally give me for an average user's experience?
Most importantly, I'm looking to take & convert this S5 phone (and my daughter's Galaxy S3) to T-Mobile this weekend and want to make it all T-Mobile ready. Any insight, thoughts, suggestions, especially if I wanted to root or factory reset my phone but keep app data (such as Kung Fu Pets )?
I've been told by friends and cell providers these phones are already unlocked and can easily switch networks, no worries of voice or data settings on my part, TMo's WiFi calling will work as if I bought the phone from TMo, etc.
Thanks all!

KCSamerica said:
I upgraded my unrooted Galaxy S5 to lollipop and it was bad, slow, freezing a lot. I disabled many Verizon-bloatware apps and lollipop is now a buttery smooth beautiful thing!
What pros & cons would rooting a phone generally give me for an average user's experience?
Most importantly, I'm looking to take & convert this S5 phone (and my daughter's Galaxy S3) to T-Mobile this weekend and want to make it all T-Mobile ready. Any insight, thoughts, suggestions, especially if I wanted to root or factory reset my phone but keep app data (such as Kung Fu Pets )?
I've been told by friends and cell providers these phones are already unlocked and can easily switch networks, no worries of voice or data settings on my part, TMo's WiFi calling will work as if I bought the phone from TMo, etc.
Thanks all!
Click to expand...
Click to collapse
This is my opinion only, with that being said for the average user there is no advantage to being rooted. The average user is not interested in flashing new roms or freezing apps beyond what Verizon allows. The average user wants to turn on their phone and go on their merry way. If something goes wrong they want to call Verizon and have they fix it for them. They would never touch Odin.
With that being said, because your in this forum your more than the average user. If you wan to freeze or uninstall more Verizon/Samsung bloat you need to be rooted.
As for moving to a different carrier I'll let some one who has done that chime in.

jrv331 said:
This is my opinion only, with that being said for the average user there is no advantage to being rooted. The average user is not interested in flashing new roms or freezing apps beyond what Verizon allows. The average user wants to turn on their phone and go on their merry way. If something goes wrong they want to call Verizon and have they fix it for them. They would never touch Odin.
With that being said, because your in this forum your more than the average user. If you wan to freeze or uninstall more Verizon/Samsung bloat you need to be rooted.
As for moving to a different carrier I'll let some one who has done that chime in.
Click to expand...
Click to collapse
Thanks! It won't be a Verizon phone for long, so I guess with rooting it and installing a known stable release be a good idea to get rid of Verizon's bloatware (and maybe some of Samsung's) while keeping a good, hard-working phone? I noticed a big difference disabling what I'm allowed to with Verizon's apps and maybe that's enough, I don't know - any place to research which Verizon and/or Samsung apps are safe to disable (if rooting it & installing a stable release doesn't already remove them)?
Oh, also, is there where I'll go to get future updates since I'll no longer be part of Verizon, and T-Mobile will probably not update my phone since I didn't buy it from them?
Thanks again!

Through a couple phone calls, T-Mobile reassured me both my S3 and S5 would work just fine, everything just the same except I'll have to make sure the phone is unlocked. They also said on both calls that their WiFi calling would most definitely work. Verizon, though a half dozen calls, gave me a different "unlock" story each time. So much for trying to be prepared...
Neither the S3 or the S5 work as expected. The S3 uses the far inferior network speeds and takes about 3 minutes just to send a pic text, and that's only if we're using Hangouts - stock Messages or Verizon's Messages+ don't work on the S3. The S5, I get a lot of "Data (Network) connection lost", setting the time errors, I can't access my voicemail or change my voicemail phone number (not sure if that is a new issue).
So with all this in mind:
1) is the S3 using an inferior data speed network due to hardware limitations or settings I can change?
2) would rooting my S3 and S5 alleviate a lot or all of these issues?
3) any way to get TMo WiFi calling to work on a Verizon phone? Would rooting it allow me to install a TMo version Android?
4) how do I go about updating Android on these phones now that they're off Verizon and not officially TMo phones?
5) any suggestions to fix any or all of these other issues?

KCSamerica said:
Through a couple phone calls, T-Mobile reassured me both my S3 and S5 would work just fine, everything just the same except I'll have to make sure the phone is unlocked. They also said on both calls that their WiFi calling would most definitely work. Verizon, though a half dozen calls, gave me a different "unlock" story each time. So much for trying to be prepared...
Neither the S3 or the S5 work as expected. The S3 uses the far inferior network speeds and takes about 3 minutes just to send a pic text, and that's only if we're using Hangouts - stock Messages or Verizon's Messages+ don't work on the S3. The S5, I get a lot of "Data (Network) connection lost", setting the time errors, I can't access my voicemail or change my voicemail phone number (not sure if that is a new issue).
So with all this in mind:
1) is the S3 using an inferior data speed network due to hardware limitations or settings I can change?
2) would rooting my S3 and S5 alleviate a lot or all of these issues?
3) any way to get TMo WiFi calling to work on a Verizon phone? Would rooting it allow me to install a TMo version Android?
4) how do I go about updating Android on these phones now that they're off Verizon and not officially TMo phones?
5) any suggestions to fix any or all of these other issues?
Click to expand...
Click to collapse
1) probably, but I haven't checked the specs.
2) probably not. The APN in your phone needs to be changed to the right settings for your mobile carrier. It's under Settings/More Networks/Mobile Networks. You should be able to google the settings for TMo.
3) The APN may resolve the issue, if the phone allows for it.
4) If you root, you can do it. You may be able to get OTAs with the new sim, but I can't for Consumer Cellular.
5)Again, the APN will solve a lot of issues. The voicemail number needs to be changed to your carrier's voicemail number under Phone Settings.
5)

Rapunzl said:
1) probably, but I haven't checked the specs.
2) probably not. The APN in your phone needs to be changed to the right settings for your mobile carrier. It's under Settings/More Networks/Mobile Networks. You should be able to google the settings for TMo.
3) The APN may resolve the issue, if the phone allows for it.
4) If you root, you can do it. You may be able to get OTAs with the new sim, but I can't for Consumer Cellular.
5)Again, the APN will solve a lot of issues. The voicemail number needs to be changed to your carrier's voicemail number under Phone Settings.
5)
Click to expand...
Click to collapse
1) probably hardware limitations or probably settings I can change?
2 & 3) the APN was already set by the TMo in-store rep, and google search confirms it's the correct setting.
5) voicemail number just won't change! Ug, I've google searched this issue too, no luck, and it seems many Android 5.0 users have this issue unless they factory reset - an option I'm hoping to avoid for a last resort.
I have noticed by disabling Verizon apps, much is working better, but I'm wondering if Verizon made these apps imperative for the system to run properly...?

KCSamerica said:
1) probably hardware limitations or probably settings I can change?
2 & 3) the APN was already set by the TMo in-store rep, and google search confirms it's the correct setting.
5) voicemail number just won't change! Ug, I've google searched this issue too, no luck, and it seems many Android 5.0 users have this issue unless they factory reset - an option I'm hoping to avoid for a last resort.
I have noticed by disabling Verizon apps, much is working better, but I'm wondering if Verizon made these apps imperative for the system to run properly...?
Click to expand...
Click to collapse
How did you disable the apps? If you used TiBU, there have been discussion of issues in some threads.

Rapunzl said:
How did you disable the apps? If you used TiBU, there have been discussion of issues in some threads.
Click to expand...
Click to collapse
I used the Android's built-in disable feature (since it won't let me uninstall it).

KCSamerica said:
I used the Android's built-in disable feature (since it won't let me uninstall it).
Click to expand...
Click to collapse
The only thing I can think of then, is that one or more of the disabled features are required to make things work properly. I would unfreeze the apps and then freeze them, one-by-one to find out which are causing the issues. Other than that, Kies may be able to repair the install if you don't have luck with unfreezing the apps.

Rapunzl said:
The only thing I can think of then, is that one or more of the disabled features are required to make things work properly. I would unfreeze the apps and then freeze them, one-by-one to find out which are causing the issues. Other than that, Kies may be able to repair the install if you don't have luck with unfreezing the apps.
Click to expand...
Click to collapse
Easiest step is to try the enable/disable apps as you suggested. Have you, or anyone out there, tried loading another's stock software onto a phone before doing a factory reset?
See this page: http://www.andromods.com/download-files/tmobile-galaxy-s5-stock-firmware-sm-g900t.html
It gives me the impression all S5's are the same hardware. If that's true, then why can't I install TMo's stock software in the recovery partition, then do a factory reset? (Another worse case scenario, but possibly more of a thorough cure)

KCSamerica said:
Easiest step is to try the enable/disable apps as you suggested. Have you, or anyone out there, tried loading another's stock software onto a phone before doing a factory reset?
See this page: http://www.andromods.com/download-files/tmobile-galaxy-s5-stock-firmware-sm-g900t.html
It gives me the impression all S5's are the same hardware. If that's true, then why can't I install TMo's stock software in the recovery partition, then do a factory reset? (Another worse case scenario, but possibly more of a thorough cure)
Click to expand...
Click to collapse
If you read toward the end of that post, it says:
Before download check your model number and software version, head to Settings -> About. Confirm that you get the correct firmware that match with the model number of your device, and never use a firmware that isn’t built for your S5, downgrade is also not recommended.
Click to expand...
Click to collapse
I've also seen a thread talking about doing this for a TMo user on the Verizon S5, but I'm on Consumer Cellular, so I'm not sure if it would really work. Even if it does, I'm not sure if that would solve your issues, and I hear you're risking bricking your phone attempting it.

Not sure if I already mentioned, but sadly a couple T-Mobile reps assured me everything would work great. Not. A factory reset did help a lot, but I keep getting these oddities that TMo is now saying I just have to live with, now that my trial period is over. So any ideas and help would be great!
"Data network unavailable" often appears after a phone call and lasts for a few seconds or longer. In that time, I can't get Maps to find anything, among other issues. This error appears at random times otherwise, but most consistently after a phone call.
"SIM error" happens periodically. I'm not sure the pattern yet, but maybe after a couple phone calls in a row, or call swapping. The only way to fix this is to reboot the phone.
The top status bar bounces between "H+" and "3G". I haven't found a pattern as to when or why, but often can't do much with the phone until it settles down, if it settles down.
Everything I've read and originally heard lead me to believe this S5 should work much better than it is, as if some APN or data setting is wrong. I've triple checked and they seem to be set properly, but I don't know anymore...

Motorola G3 2015 [TextNOW]

https://www.textnow.com/wireless/ is selling an unlocked Moto G 3rd generation.
I have received the phone and can confirm it's BL unlocked with their stock ROM; I'll be pulling resources related to this device now.
Research notes
TextNOW is really Sprint.
The number they assign to you exists in the cloud and is probably making and getting calls over LTE, I had this feeling when I noticed the quality scale and special stuff in the .prop of stock ROM.
Stock ROM
http://droid.textnow.com/textnow-motog3-4281.zip
-------------------------------------
TextNOW unofficial Q&A
-------------------------------------
Q: How are you making calls and SMS normally?
A: Through TextNOW app which works off LTE.
Q: Is the actual RIL (radio) being used?
A: No, not by default but this can be enabled forcefully**
Q: What phone number does the radio use?
A: One unrelated to where you are, you have no choice in this number.
Q: Can the radio # send SMS?
A: No, but kind of via Allo but NOT directly from itself, ever.
Q: Is there any way to remove the SMS lock?
A: I imagine by social-engineering Sprint, as *3 will show you the Sprint plan TextNOW is using.
Q: Bootloader on arrival check...
A: Unlocked
Q: Recovery check
A: None found, purged with fastboot clearly
Q: Compatible with TWRP for 'Osprey' generically?
A: Yes
Q: Compatible with all Osprey ROMs?
A: Yes, by flashing a carrier zip for TextNOW
Q: Can radio phone make and recieve calls?
A: Yes
Q: Is phone carrier unlocked?
A: It seems to not be in terms of function, but I suspect carrier lock was re-enabled by the folks at TextNOW using CDMA workshop or something.
**
---------------------------------
Best way to utilize radio
(Google Voice!)
---------------------------------
Ok, TextNOW is annoying in that it wants all traffic through LTE.
I can't be screwed over by not having a data connection; and missing a call.
Instead create a Google Voice account, have it verify your radio number by CALLING it. SMS verification will NOT work.
After verifying your number have Google Voice forward all calls to it from the number you choose in voice.
After install Hangouts and you can receive and make calls over the phones native Radio using Google Voice with your custom picked number.
Allo will have the same number as your Radio, I would highly suggest Hangouts to send SMS as it will use your Google Voice number.
Likewise, you can port your old phone number to Google voice for $20 and use it forever on the multitude of cheap phones like this that are going to begin emerging.

LOL! I see! What a company!
1- Install TWRP
2- Install SuperSU to obtain Root
3- Backup the OS in TWRP for safety
4- Install CyanogenMod and flash for TextNOW via Moto_LTE.zip
5- Install Google Voice
6- In the Phones dialer *#*#4636#*#*
7- Write down your true number in 'About Phone'
8- Make Google voice forward all calls to this number
9- Install Hangouts to obtain a more native SMS
10- Use Google Voice number natively
11- Profit, bypass the need to make voice calls via data.
WOW! Why would anyone want to use LTE to make voice calls, my way is better it utilizes the actual RIL how can you beat that.
Maybe TextNOW should hire me I could do a way better job
But this is truly poverty-level ****, but I noticed the RIL wasn't being used in stock ROM right away; that all calls were being forwarded to the TextNOW app LOL
WE WANT RIL, WE WANT RIL.
Plus the native number is cool; it can be used as a "landline" in classification and that's important when verifying some things.

Hi, I also bought this phone from TextNow but am interested in getting it into a GSM unlocked state. I have tried the steps in the following thread
http://forum.xda-developers.com/2015-moto-g/help/sim-unlock-xt1548-cdma-model-t3235281/page4
but haven't had any luck getting anything but invalid sim card even after flashing the roms and changin the radios, any advice?

I think I have found the solution for obtaining GSM unlock. I have followed the steps in the following thread and it looks like our NV codes are already matching the unlocked ones except the NV code for domestic unlock, our phones currently have NV 8322 set to 01 it needs changed to 00 for unlock. Unfortunately to do this we need a way of obtaining MSL/SPC code for our phone as the one in the thread does not work for our phone.
http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155

Zdog291 said:
I think I have found the solution for obtaining GSM unlock. I have followed the steps in the following thread and it looks like our NV codes are already matching the unlocked ones except the NV code for domestic unlock, our phones currently have NV 8322 set to 01 it needs changed to 00 for unlock. Unfortunately to do this we need a way of obtaining MSL/SPC code for our phone as the one in the thread does not work for our phone.
http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155
Click to expand...
Click to collapse
I'll look into this

http://forum.xda-developers.com/showthread.php?t=2166542
Edit: Although doing this is HIGHLY scary.

http://forum.xda-developers.com/showthread.php?t=2389740
Is also a feasible method, using CDMA workshop

Zdog291 said:
I think I have found the solution for obtaining GSM unlock. I have followed the steps in the following thread and it looks like our NV codes are already matching the unlocked ones except the NV code for domestic unlock, our phones currently have NV 8322 set to 01 it needs changed to 00 for unlock. Unfortunately to do this we need a way of obtaining MSL/SPC code for our phone as the one in the thread does not work for our phone.
http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155
Click to expand...
Click to collapse
Yeah, we can unlock our phone using QC-Tools or CDMA Workshop.

Stock files for Motorola G3:
http://droid.textnow.com/textnow-motog3-4281.zip
I don't know what it contains yet, It's 722 MB but as the situation unfolds I'll have more feedback about it

I wish you guys the greatest of luck. This would truly be groundbreaking, as it has been many many years since I've heard of a successful, verifiable DSU on a Sprint based Motorola Device. Motorola is notorious -- at the directives of Sprint and its MVNOs, of course -- for embedding DSU lock code in multiple partitions of a single device. So just when you think you've cracked it --- surprise, another lock. The Moto E LTE xt1526 for example, the /utags, /pds, /hob, and dhob partitions were found, upon inspection, to be embedded with domestic UICC network lock code. I am hopeful that you guys can crack the Moto G3. Perhaps TextNow hasn't resorted to sheer rocket science to GSM lock this great device. Thank you guys....and good luck.

MotoJunkie01 said:
I wish you guys the greatest of luck. This would truly be groundbreaking, as it has been many many years since I've heard of a successful, verifiable DSU on a Sprint based Motorola Device. Motorola is notorious -- at the directives of Sprint and its MVNOs, of course -- for embedding DSU lock code in multiple partitions of a single device. So just when you think you've cracked it --- surprise, another lock. The Moto E LTE xt1526 for example, the /utags, /pds, /hob, and dhob partitions were found, upon inspection, to be embedded with domestic UICC network lock code. I am hopeful that you guys can crack the Moto G3. Perhaps TextNow hasn't resorted to sheer rocket science to GSM lock this great device. Thank you guys....and good luck.
Click to expand...
Click to collapse
What I'm saying is that this model is already carrier-unlocked, but they have reverted that by changing a '00' to '01' probably.
When I got this phone I went through a battery of testing in order of Q&A, what was important for me:
Q: How are you making calls and SMS?
A: Through TextNOW app which works off LTE.
Q: Is the actual RIL (radio) being used?
A: No, not by default but this can be enabled forcefully
Q: What phone number does the radio use?
A: One unrelated to where you are, you have no choice in this number.
Q: Can the radio # send SMS?
A: No, but kind of via Allo but NOT directly from itself, ever.
Q: Is there any way to remove the SMS lock?
A: I imagine by social-engineering Sprint, as *3 will show you the Sprint plan TextNOW is using.
Q: Bootloader on arrival check...
A: Unlocked
Q: Recovery check
A: None found, purged with fastboot clearly
Q: Compatible with TWRP for 'Osprey' generically?
A: Yes
Q: Compatible with all Osprey ROMs?
A: Yes, by flashing a carrier zip for TextNOW
Q: Can radio phone make and recieve calls?
A: Yes
Q: Is phone carrier unlocked?
A: It seems to not be in terms of function, but I suspect carrier lock was re-enabled by the folks at TextNOW using CDMA workshop or something.
---------------------------------
Best way to utilize radio
---------------------------------
Ok, TextNOW is annoying in that it wants all traffic through LTE.
I can't be screwed over by not having a data connection; and missing a call.
Instead create a Google Voice account, have it verify your radio number by CALLING it. SMS verification will NOT work.
After verifying your number have Google Voice forward all calls to it from the number you choose in voice.
After install Hangouts and you can receive and make calls over the phones native Radio using Google Voice with your custom picked number.
Allo will have the same number as your Radio, I would highly suggest Hangouts to send SMS as it will use your Google Voice number.

MotoJunkie01 said:
I wish you guys the greatest of luck. This would truly be groundbreaking, as it has been many many years since I've heard of a successful, verifiable DSU on a Sprint based Motorola Device. Motorola is notorious -- at the directives of Sprint and its MVNOs, of course -- for embedding DSU lock code in multiple partitions of a single device. So just when you think you've cracked it --- surprise, another lock. The Moto E LTE xt1526 for example, the /utags, /pds, /hob, and dhob partitions were found, upon inspection, to be embedded with domestic UICC network lock code. I am hopeful that you guys can crack the Moto G3. Perhaps TextNow hasn't resorted to sheer rocket science to GSM lock this great device. Thank you guys....and good luck.
Click to expand...
Click to collapse
I suspect these are actually Global GSM models anyway lol
I think they were flashed with CDMA radios and then locked via CDMA workshop by the developers at TextNOW.
Well, I don't have the power to test because I don't have a GSM SIM card but I do have a second TextNOW phone so things are about to get real tonight either way; I should be able to see if I can forcefully carrier-unlock it via CDMA workshop.
Another amusing thing to note is before I had figured out what it needed to use TextNOW on other Osprey builds; It would sometimes be recognized as a Virgin Mobile device; I guess they are using Sprint towers too

InterfaceNode said:
I suspect these are actually Global GSM models anyway lol
I think they were flashed with CDMA radios and then locked via CDMA workshop by the developers at TextNOW.
Well, I don't have the power to test because I don't have a GSM SIM card but I do have a second TextNOW phone so things are about to get real tonight either way; I should be able to see if I can forcefully carrier-unlock it via CDMA workshop.
Another amusing thing to note is before I had figured out what it needed to use TextNOW on other Osprey builds; It would sometimes be recognized as a Virgin Mobile device; I guess they are using Sprint towers too
Click to expand...
Click to collapse
What is the actual model number of the TextNow variant?

MotoJunkie01 said:
What is the actual model number of the TextNow variant?
Click to expand...
Click to collapse
Can confirm it's XT1548

InterfaceNode said:
http://forum.xda-developers.com/showthread.php?t=2166542
Edit: Although doing this is HIGHLY scary.
Click to expand...
Click to collapse
InterfaceNode said:
http://forum.xda-developers.com/showthread.php?t=2389740
Is also a feasible method, using CDMA workshop
Click to expand...
Click to collapse
I tried both of these methods, I can't get the radio comm to detect the phone and unfortunately for any NV writer to work it needs an MSL code which we don't have.
Also TextNow model number is xt1548

Zdog291 said:
I tried both of these methods, I can't get the radio comm to detect the phone and unfortunately for any NV writer to work it needs an MSL code which we don't have.
Also TextNow model number is xt1548
Click to expand...
Click to collapse
OK. So its the same variant as the Sprint, Virgin & Boost variants. I'll look into Qualcomm's leaked programming tools. I have a copy on PC. And I can confirm that the MSL is readily available on the Boost & Virgin variants.

As a side note I flashed both the latest (Android 6.0) U. S. Cellular and Sprint roms from the below thread with fastboot and both seemed to work fine on first inspection. I then used the firmware posted earlier in this thread for TextNow and was able to flash back every step except for the partition command, however everything on the TextNow firmware seems to still be working.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750

Zdog291 said:
As a side note I flashed both the latest (Android 6.0) U. S. Cellular and Sprint roms from the below thread with fastboot and both seemed to work fine on first inspection. I then used the firmware posted earlier in this thread for TextNow and was able to flash back every step except for the partition command, however everything on the TextNow firmware seems to still be working.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Click to expand...
Click to collapse
Good information.

InterfaceNode said:
I suspect these are actually Global GSM models anyway lol
I think they were flashed with CDMA radios and then locked via CDMA workshop by the developers at TextNOW.
Well, I don't have the power to test because I don't have a GSM SIM card but I do have a second TextNOW phone so things are about to get real tonight either way; I should be able to see if I can forcefully carrier-unlock it via CDMA workshop.
Another amusing thing to note is before I had figured out what it needed to use TextNOW on other Osprey builds; It would sometimes be recognized as a Virgin Mobile device; I guess they are using Sprint towers too
Click to expand...
Click to collapse
I had this theory a while back that TextNow just simlicked the phones. I can confirm that the phone works with international sims (Like FreedomPop Global sim). Also when I disabled the Textnow app and make a call through the stock dialer, It called out to the number i called through the cell towers. The number on the device seems to be based in Virginia even though I'm the California. I'm willing to help with this and keep up the good work!

applepear123 said:
I had this theory a while back that TextNow just simlicked the phones. I can confirm that the phone works with international sims (Like FreedomPop Global sim). Also when I disabled the Textnow app and make a call through the stock dialer, It called out to the number i called through the cell towers. The number on the device seems to be based in Virginia even though I'm the California. I'm willing to help with this and keep up the good work!
Click to expand...
Click to collapse
I am literally probably the worst person ever to notice their service

Taking VZW S7 to VZW-based MVNO

Okay - I have a question on whether I should even bother to attempt a migrate. I have an ex-VZW Galaxy Nexus on Tracfone (dual-carrier MVNO - currently on the VZW side). I also have a VZW Galaxy S7 inbound that is being replaced by the current owner (who is having issues with the phone itself) - the owner wants to GIVE me the phone in question (the frustration level is THAT high). I have worked on the phone (and used it as basically a tablet - I did not use the phone AS a phone) and am thus familiar with everything including factory-resets; however, how would I migrate it?
1. Issue #1 - it takes a different SIM style (from what I suspect) from the GNex I'd be leaving; if it didn't, it would be a straight migration that I could do.
2. Preferably, I'd like to be able to stick with VZW firmware (it's what I'm familiar with on the phone in question).
3. As far as SAMSUNG/Android Pay on an S7 (or any other phone), if you rooted the phone, it normally will NOT pass SafetyNet (this was an issue I faced with the GNex; therefore, it's not unique to the S7). You need a method to hide root - if done properly, that will fix the issue. Still, not a new issue (and it's one I know how to deal with).

PGHammer said:
Okay - I have a question on whether I should even bother to attempt a migrate. I have an ex-VZW Galaxy Nexus on Tracfone (dual-carrier MVNO - currently on the VZW side). I also have a VZW Galaxy S7 inbound that is being replaced by the current owner (who is having issues with the phone itself) - the owner wants to GIVE me the phone in question (the frustration level is THAT high). I have worked on the phone (and used it as basically a tablet - I did not use the phone AS a phone) and am thus familiar with everything including factory-resets; however, how would I migrate it?
1. Issue #1 - it takes a different SIM style (from what I suspect) from the GNex I'd be leaving; if it didn't, it would be a straight migration that I could do.
2. Preferably, I'd like to be able to stick with VZW firmware (it's what I'm familiar with on the phone in question).
3. As far as SAMSUNG/Android Pay on an S7 (or any other phone), if you rooted the phone, it normally will NOT pass SafetyNet (this was an issue I faced with the GNex; therefore, it's not unique to the S7). You need a method to hide root - if done properly, that will fix the issue. Still, not a new issue (and it's one I know how to deal with).
Click to expand...
Click to collapse
Number 3 is a no go, only 1 root option and it will not pass safetynet. The first 2 are fixable with 1. being get ST to mail you a sim and 2. Vzw firmware works fine on vzw ST.

gunz.jones said:
Number 3 is a no go, only 1 root option and it will not pass safetynet. The first 2 are fixable with 1. being get ST to mail you a sim and 2. Vzw firmware works fine on vzw ST.
Click to expand...
Click to collapse
That is what I was afraid of; actually, I can get Tracfone to send me a nano-SIM (they are my MVNO of record) or purchase one locally via any of their retail POPs (Dollar General, Wal-Mart, or Target - with DG being the closest and thus the easiest), since I'd be porting my existing number on my existing provider). Right now, I am updating the newly-arrived S7 with the Nougat firmware of the VZW sort (the original owner stayed with MM). What IS the one method that works for rooting? I'm used to either SuperSU and Magisk (Magisk was my SafetyNet compatible rooting solution - however, with MagiskManager booted out of the PlayStore, I need an alternative). I can set up everything else in the meanwhile.

PGHammer said:
That is what I was afraid of; actually, I can get Tracfone to send me a nano-SIM (they are my MVNO of record) or purchase one locally via any of their retail POPs (Dollar General, Wal-Mart, or Target - with DG being the closest and thus the easiest), since I'd be porting my existing number on my existing provider). Right now, I am updating the newly-arrived S7 with the Nougat firmware of the VZW sort (the original owner stayed with MM). What IS the one method that works for rooting? I'm used to either SuperSU and Magisk (Magisk was my SafetyNet compatible rooting solution - however, with MagiskManager booted out of the PlayStore, I need an alternative). I can set up everything else in the meanwhile.
Click to expand...
Click to collapse
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502

Thanx for this
gunz.jones said:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Click to expand...
Click to collapse
Thanx for this; I'll check that out when I'm ready.
I have some other news on my testing; while I would have preferred to stick with Verizon-branded firmware, it commits two major sins - it lacks the latest security updates, and it's "cornflakey" in SIMless/tablet mode - however, there is an alternative firmware for the G930V (despite it being originally for its unlocked cousin, the G930U, it will install on the V as well - even in VZW trim; my own V is the gold exclusive-to-VZW model, and, atop that, this particular U firmware is for Tracfone's version of the U - hence absolutely none of the VZW shovelware that folks complain about). It is the May 16th (this year) U firmware for the G930U for the Tracfone S7 (yes - there is such a creature); it will also install on the VZW S7 (which means it will also install on the V from Big Red) via ODIN (use the four-file method - BL, AP, CP, and HOME_CSC) the file name is SM-G930U_1_20170516105039_fspus9jwu3_fac.zip, and is present on both SamMobile and updato.com (I used updato for speedier downloads). There are two good things about Tracfone's alternative firmware - it is pretty much designed for SIMless/tablet operations; while it has gotten easier to pick up SIM kits (you can grab them at any Wal-Mart or Dollar General anywhere in the country - in addition to having them mailed/shipped via Tracfone.com or StraightTalk.com), why should your new(er) phone be a paperweight in the meantime? Second, it is *vanilla* as firmware gets - and I don't mean French Vanilla, either - it reminds me of iOS or AOSP (specifically Unlegacy-Android); it may be burdened with TouchWiz; however, that is, literally, the only real ding against it. (And, from personal experience, the Snapdragon 820 bakes TouchWiz to a turn - more so on N than MM - and isn't N supposed to be heavier compared to MM?)

PGHammer said:
Thanx for this; I'll check that out when I'm ready.
I have some other news on my testing; while I would have preferred to stick with Verizon-branded firmware, it commits two major sins - it lacks the latest security updates, and it's "cornflakey" in SIMless/tablet mode - however, there is an alternative firmware for the G930V (despite it being originally for its unlocked cousin, the G930U, it will install on the V as well - even in VZW trim; my own V is the gold exclusive-to-VZW model, and, atop that, this particular U firmware is for Tracfone's version of the U - hence absolutely none of the VZW shovelware that folks complain about). It is the May 16th (this year) U firmware for the G930U for the Tracfone S7 (yes - there is such a creature); it will also install on the VZW S7 (which means it will also install on the V from Big Red) via ODIN (use the four-file method - BL, AP, CP, and HOME_CSC) the file name is SM-G930U_1_20170516105039_fspus9jwu3_fac.zip, and is present on both SamMobile and updato.com (I used updato for speedier downloads). There are two good things about Tracfone's alternative firmware - it is pretty much designed for SIMless/tablet operations; while it has gotten easier to pick up SIM kits (you can grab them at any Wal-Mart or Dollar General anywhere in the country - in addition to having them mailed/shipped via Tracfone.com or StraightTalk.com), why should your new(er) phone be a paperweight in the meantime? Second, it is *vanilla* as firmware gets - and I don't mean French Vanilla, either - it reminds me of iOS or AOSP (specifically Unlegacy-Android); it may be burdened with TouchWiz; however, that is, literally, the only real ding against it. (And, from personal experience, the Snapdragon 820 bakes TouchWiz to a turn - more so on N than MM - and isn't N supposed to be heavier compared to MM?)
Click to expand...
Click to collapse
The firm from any u or v/vl would work on the vzw and st/tf phones. I have a vl running v firmware. The v has updates to June security as far as I'm aware, but they ruin gps spoofing. Carrier fw gets updated more often than u as well from reading the forums

gunz.jones said:
The firm from any u or v/vl would work on the vzw and st/tf phones. I have a vl running v firmware. The v has updates to June security as far as I'm aware, but they ruin gps spoofing. Carrier fw gets updated more often than u as well from reading the forums
Click to expand...
Click to collapse
And why would you need GPS spoofage? (Yes - I'm serious.) The big reason for the hate on VZW firmware has to do with all the shovelware - I hate it because it is not as friendly to SIMless operation as Tracfone's more vanilla U-ware; some of VZW's shovelware I can actually use.

PGHammer said:
And why would you need GPS spoofage? (Yes - I'm serious.) The big reason for the hate on VZW firmware has to do with all the shovelware - I hate it because it is not as friendly to SIMless operation as Tracfone's more vanilla U-ware; some of VZW's shovelware I can actually use.
Click to expand...
Click to collapse
I use it for pogo and that's about it.

Advanced Calling Features on MVNOs
gunz.jones said:
I use it for pogo and that's about it.
Click to expand...
Click to collapse
Are you referring to EA's mobile-gaming service? I don't even use it for that.
I have a question for anyone that has a VZW-based MVNO (Tracfone, Straight Talk, etc.) - have you ever tried to use Wi-Fi calling? (This is actually a switch in the S7 settings menu which lets you use it when mobile data is unavailable - it's below the Advanced Calling switch.)

PGHammer said:
Are you referring to EA's mobile-gaming service? I don't even use it for that.
I have a question for anyone that has a VZW-based MVNO (Tracfone, Straight Talk, etc.) - have you ever tried to use Wi-Fi calling? (This is actually a switch in the S7 settings menu which lets you use it when mobile data is unavailable - it's below the Advanced Calling switch.)
Click to expand...
Click to collapse
Pokemon go. WiFi calling doesn't work on vzw mvno.

gunz.jones said:
Pokemon go. WiFi calling doesn't work on vzw mvno.
Click to expand...
Click to collapse
I wouldn't think so - such an advanced feature is what separates carriers from MVNOs; therefore, I certainly understand why a carrier would want to keep such a feature to itself.

PGHammer said:
I wouldn't think so - such an advanced feature is what separates carriers from MVNOs; therefore, I certainly understand why a carrier would want to keep such a feature to itself.
Click to expand...
Click to collapse
There is a possibility of it working with an att or tmo sim. I had it working on an st att sim and tmo note 4 as well as volte. Oh, volte also doesn't work on a vzw mvno.

gunz.jones said:
There is a possibility of it working with an att or tmo sim. I had it working on an st att sim and tmo note 4 as well as volte. Oh, volte also doesn't work on a vzw mvno.
Click to expand...
Click to collapse
Advanced feature, remember? I get that. Somehow, I got SIMless operations straightened out (V firmware). I'm right now waiting on two things - the latest security update (have any of you on a VZW MVNO but VZW firmware gotten it yet?) and to grab a Tracfone SIM (I'm going local retail for that - likely Dollar General, as they are the closest retailer that carries them).