for anyone looking to boost the eris internet speed (every so subtly) you may want to try changing the default DNS servers on the phone similare to stated here:
Found this one in the Fascinate forms (i've recently switch phones). Thought this might be a tad helpful for the eris too.
http://forum.xda-developers.com/showthread.php?p=9735607#post9735607
http://forum.xda-developers.com/showpost.php?p=9735607&postcount=6
and for those asking. whats the point:
http://forum.xda-developers.com/showpost.php?p=9733302&postcount=4
Please note I have not tested this on the Eris, so I wouldn't advise flashing the files, BUT the location of the files is the same as on the Eris. I just dont know if the settings within the file being flash are all identical, so someone smarter than me may want to mess around with this and "port" it over to work on the eris.
good luck!
Nice, I've had to do that with my computer out here I wasn't sure how to do it on the phone. Hopefully it is trivial to get setup right.
to bad this wouldn't work with cricket flashed phones, as i hear cricket blocks any dns server other than theres
Hi everyone, I am a old ERIS user who is a NEW ERIS abuser. I am running xtrSENSE 5.0.1 and I noticed that the only file in "/system/etc/ppp" is [if-up-vpn] So my question is how would I modify or edit the DNS servers? I have tired pushing a modified ip-up. I had no luck, hopefully someone can shed some light. Thank you
Download SETDNS from market.
Zuckstone said:
Download SETDNS from market.
Click to expand...
Click to collapse
Is there any other way besides using an app? But I will try out the app, and thank you.
Ideally, you want to pick DNS addresses that are "close" to you, as in the # of hops. Geographically close doesn't always mean it will be 3-4 hops away either. For me, the (3) listed are 9-11 hops away.
Going to try SetDNS and see where my current VZW DNS are or how many hops away they are...
***I'm going to soon grab a Samsung Galaxy Nexus! Look out for my guide on how to flash THAT to MetroPCS, soon!***
This is my first write up of a really detailed tutorial on HowardForums. I spent as much as a hour writing this whole thing out, seriously! I figured I might as well get it up on XDA here as well. o: Leave me with your feedback and how things work out for you.
==How to Flash the Nexus S 4G to MetroPCS==
This is just a very detailed write up on how to get the Nexus S 4G flashed to MetroPCS. I get really in-depth with this tutorial. I don't know how much easier I can make it. This will get you working talk, text, web, mms, and all that good cellphone stuff.
This tutorial is made up of bits and pieces of Bloodykiller's HTC EVO 4G flashing how-to, just re-written with proper MetroPCS settings and all other things specifically for the Nexus S 4G.
==BEFORE WE BEGIN==
Couple of things we'll need before we can begin. Here's the checklist for your grand journey.
- CDMA Workshop 2.7 OR 3.5 (Google it.)
1- QPST build 323 (Google it.)
2- Experience with QPST and CDMA Workshop...
3- These Samsung drivers: https://www.dropbox.com/s/mthba0oaizzo6t0/samsung_driver.zip
4- This PRL (Enables 3G data, if available): https://www.dropbox.com/s/z8ecqcg76gw44wg/3029.prl
5- *MMS is being fixed, ignore it*
6- A ROOTED Nexus S 4G running on STOCK Android 4.0.x, OR Android 2.3.x, with A CUSTOM RECOVERY (This is now a requirement to get working MMS!)
7- Some MiniUSB cables
8- Your Nexus S 4G's MEID added into MetroPCS's database. Look it up, or PM me for help on the matter. I don't do it, but I can help.
Disclaimer: Follow these instructions CAREFULLY. Mess up, and things can go bad, and I'm not responsible for whatever happens. Okay, lets begin.
==1. TALK/TEXT==
1. This is the most crucial part. Your MEID needs to be added into the MetroPCS database. No MEID = No phone. (Or to get smart about it, no talk, or text.)
2. We're going to need to use CDMA Workshop for this part of the tutorial. You need to either download it from somewhere on the interwebs, or be a cool guy and actually buy it, up to you.
Before we can start, you will need to download the Samsung drivers (https://www.dropbox.com/s/mthba0oaizzo6t0/samsung_driver.zip), unzip it, and install the .msi file inside. Thats it for the drivers part.
3. Now that you've gotten the drivers, make your way to your Nexus S 4G, and open up the dialer. Dial *#*#8778#*#*, and you should be pulled into a menu called PhoneUtil. (If you didn't get into PhoneUtil after dialing the code, you need to be on STOCK Android 2.3.x, or 4.0.x!) Next, tap the modem bullets on both UART and USB.
{
"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"
}
4. Connect your Nexus S 4G to your PC. You should be getting a message about a new device being installed. Once that finished, go to the Start Menu, and right click on "Computer" and choose "Properties". On the left side, click on Device Manager. Once you're in, expand "Ports (COM & LPT) and look for "SAMSUNG Mobile Modem Diagnotic Serial Port (WDM) (COMx)"
The x in (COMx) is the number of the port you'll be using in QPST and CDMA Workshop. It'll be 1,2,3,4,5 and so forth, whatever.
5. Open up CDMA Workshop. Under the Main tab, find COM Settings, and change the Port to whatever the SAMSUNG Mobile Model Diag Port told us earlier. I got COM6, so I would open up the drop down menu and choose COM6. Don't touch the baud rate. Go down and click "Connect", and then click "Read".
**If the phone does not answer, wake up your Nexus S 4G.**
You should then see a bunch of number and stuff on the left under Phone Information, awesome! Next, make your way to the Security tab. We need to unlock the phone before we can do anything. Under SPC, in the blank field, enter in "000000" (without quotations), then click on SPC and then click send. You should get the message saying "SPC is correct. Phone unlocked", opossum-grade awesome!
6. Go to the NAM tab, and click Read at the bottom. You should see a bunch of numbers and other things, but what we want to look at is "MIN" and "Dir_Number". You need to change these numbers accordingly. Dir_Number is your actual phone number, and MIN is your Mobile Identification Number. Your MIN can be found from one of your older phones. Once you put those in, click on Write at the bottom.
**If the phone does not answer, wake up your Nexus S 4G.**
7. Next, make your way to the "Other" tab. Find PRL, and make sure the boxes read "Universal, and NAM1". Click the Write button, and find the PRL file that you downloaded earlier. (3029.prl) Once you find it, double click it, and wait for it to finish.
Sometimes you will get an error about failing to write to NAM1, no worries. Go back to the main tab, disconnect, and reconnect and at the same time, read again. Go back to security, enter the SPC, and try to rewrite the PRL.
**If the phone does not answer, wake up your Nexus S 4G.**
8. Almost done with CDMA Workshop! Also, be VERY careful with this part because a simple mistake CAN brick your phone. Finally, head over to this website here: http://www.whiterabbit.org/android/
We need to get our NV items, as well as our MetroPCS MSL. In the field where it says "Enter your login string", type in [email protected]. (So if your phone number were 555-555-5555, you'd put in [email protected]) Before clicking generate, make sure you have the correct version of CDMA Workshop on the bubbles selected! Okay, so you should have gotten a .txt file after clicking generate. Save it to somewhere you can find it.
Go back to CDMA Workshop, and go into the "Memory" tab. Find "NV Items" and click Write. You'll get a warning message, click OK. Find the .txt file you got from whiterabbit, and open it in CDMA Workshop. *Make sure that this process does NOT get interrupted!* Once that's done, not only have you just taken the first steps into getting WEB working, but you've gotten Talk and Text working on your Nexus! Give yourself a pat on the back.
Also, you will need to get your MetroPCS MSL Code. To get this, on the whiterabbit page, near the field that says "Enter 1 MEID/ESN per line in the text area to your left, then click the calculate button.", enter your ESN/MEID in the field, and click generate. Under MetroPCS MSL, write that down, we'll need it later.
Close CDMA Workshop, and reboot your phone.
==2. DATA/WEB==
Time to work with QPST! This stuff is going to really require your attention to "spot the differences". I say that because I'm going to use pictures. on this part to make life simple.
1. Open up QPST Configuration, and while you're doing that connect your Nexus S 4G to your PC, again.
2. Remember that port we used for CDMA Workshop? It might be the same as last time. Mainly, look for the Phone "FFA-6550-ZRF6500". Do you see it? If not, go to Add New Port. Uncheck "Show Serial and USB/QC Diagnotic ports only". Select the ports that showed up and click OK. Wait and see if it finds your phone now. It should.
(If the ports are enabled, but you still don't see your phone, on your Nexus S 4G, go to the dialer, and enter in *#*#8778#*#* and make sure those fields are still on MODEM.
3. With your phone highlighted, go to "Start Clients" at the top, and choose Service Programming.
4. On the new window that showed up, click on your Nexus, and click OK.
5. Another window should come up. Click "Read from Phone" at the bottom, and with the window asking for your SPC, just press OK. Let it read, and make sure that some stuff popped up on Settings. If it did, awesome.
6. Click the right arrow at the top of the window to move the tabs over until you find M.IP, open it. Remember the matching I was talking about earlier? Well, match up the values down here in QPST.
7. When you've matched up those values, under User Profile, you want to click on Profile #0 and click the Edit button. Match up what you see here.
Those red boxes are where your phone number would be. So if your phone number was again, 555-555-5555, you'd need to put in [email protected] in those NAI and Tethered NAI fields.
Once you're done with the matching, click OK, and then, we're going to be doing the same under Profile #1, so click it, and go click Edit, again. You're going to do the EXACT same thing. Match up Profile #1's values with what you did in Profile #0. (Hint: Look at the picture above, and just match it inside of Profile #1)
8. After that, time for more matching! Go to the "PPP Config" tab on the top. We're going to first start off in the "Rm" tab. Copy everything exactly as you see here.
Okay, now we go to the "Um" tab. The only difference here is that you will need to check the "Req PW enc" option, and enter the MetroPCS MSL code that we got earlier.
Make sure you copy those settings, and get that MSL in there. Also, the red blocked off area in the picture above should be your phone number.
Finally, we're going to the "AN" tab. Copy the settings, and make sure you get the MSL code we got earlier in there as well.
Again, the red blocked off area in the picture above is where your phone number would be, and you need to get the MSL code in there.
9. At last, you can finally hit the "Write to phone" button in QPST. Your phone should now be rebooting.
==3. Configuring Web/MMS==
Really simple steps here, if you know what I'll be talking about here. Simple. If you do not know what a build.prop is, it's a sign that you should read this section carefully.
1. When your phone comes back on, go back into the dialer, and dial *#*#8778#*#*, and put your phone back into PDA mode on both UART, and USB.
**If you ever need to use CDMA Workshop or QPST again, you just go back into here, and re-enable MODEM. You need to go back into PDA mode in order to utilize your Nexus's NAND storage.**
2. Connect to a Wi-Fi network, and go into the Google Play Store.
3. Search for the application called "AnyCut", download and install it.
4. Go back. You need to also search for ES File Explorer in the Google Play Store. Download and install it as well.
5. Have that MMS Fix.zip file downloaded and ready to go as well, we're going to need to use it.
6. Let's save us some time for later on, first. Open up AnyCut, and tap on New Shortcut.
7. Tap on Activity.
8. Wait for the list to load, and look for "APNs", tap it, just press Ok, on the following pop-up.
SKIP EVERYTHING IN HERE. I'm trying to fix MMS
9. Mount your device in USB Mass Storage mode with your computer.
10. Copy the MMS Fix.zip file to the root of your Nexus S 4G's NAND storage.
11. Unmount properly, and power off your device.
12. Boot into recovery (You need a custom recovery, like ClockworkMod Recovery!). (While your device is off, hold the volume down and power buttons. On the boot loader screen, select Recovery, using the volume keys and the power button.)
13. When you are in your recovery, flash the MMS Fix.zip file, and reboot your device.
14. We're back into the Android OS now? Good. PROCEED.
Click to expand...
Click to collapse
15. Go back to your homescreen and tap on the newly created APNs shortcut.
16. Open up the Sprint APN and match up the settings to the following below as EXACTLY as it's shown. Don't type in Not Set into the fields, just tap on a field, and empty it. Then press OK.
Name: metropcs
APN: internet
Proxy: Not set
Port: Not set
Username: Not set
Password: Not set
Server: Not set
MMSC: http://mms.metropcs.net:3128/mmsc
MMS Proxy: wap.metropcs.net
MMS port: 3128
MCC: Don't touch.
MNC: 120
Authentication type: None
APN type: mms
===ICS users may have the settings below==
APN protocol: IPv4
APN roaming protocol: IPv4
APN enable/disable: Its greyed out. If its not, check it.
Bearer: Unspecified
You're done with APNs, press MENU, and SAVE.
17. When you save your APN, the MetroPCS APN should be missing. That's great, we're making some nice progress. c:
18. Go back to your home screen, and open up ES File Manager.
THIS IS THE PART WHERE YOU NEED SUPERUSER PERMISSIONS! (ROOT!)
19. When ES File Manager has fully loaded, press the menu key, and tap on Settings.
20. Scroll to the very bottom. Check ROOT EXPLORER, when you get the warning message, press yes. You MUST grant ES File Manager superuser permissions. Next, check Mount File System, and also check Backup System App.
21. Press the back key once.
22. At the top, press the Favorites button, and choose /
23. Open up the "system" folder.
24. Find build.prop, and open it by taping it and then tapping on ES Note Editor on the following popup.
25. Scroll down the file until you locate "ro.cdma.home.operator.numeric="
26. There should be a 5 or 6 digit number after the = symbol, change that number to 310120. Do NOT make any spaces after the = symbol.
27. When you're done, press menu, and tap Save.
28. When you saved the build.prop file, reboot your phone.
(KEEP IN MIND, MMS cannot be recieved or sent while Wi-Fi is on. Sending MMS while your Wi-Fi is on will break your MMS until you reboot your phone.)
===
Congratulations! You are DONE! You should now have working Talk, Text, Web, and MMS! (Depending on your plan.) If there's any problems, you can PM me, or attempt to post it here. I don't browse the forums that often but, its worth a try. To really get my attention, go to my website. http://HaxConnect24.com, and use the Contact Us form on my site.
I may wind up doing this after my Sprint contract ends, metroPCS is so incredibly cheap.
Thanks for a fantastic post, great detail and you even included screens!
i found qpst over in the ppcgeeks forums. someone posted several versions, some much newer than build 323 listed in the instructions above. i wonder if that is a good thing to use or not. no luck on finding cdma workshop 3.5+ though
mercado79 said:
i found qpst over in the ppcgeeks forums. someone posted several versions, some much newer than build 323 listed in the instructions above. i wonder if that is a good thing to use or not. no luck on finding cdma workshop 3.5+ though
Click to expand...
Click to collapse
It's a specific build that needs to be used, and you also don't have to just use CDMA Workshop 3.5. You can also use 2.7. I used 2.7 to get my Nexus up and going.
wow
Much respect bro thanks for your time and effort writing this ....
do you need a metro phone that already has services???
bongrun said:
do you need a metro phone that already has services???
Click to expand...
Click to collapse
Not really. You can still flash your Nexus over to MetroPCS by following this tutorial, having your ESN added into the MetroPCS database, and changing the phone on your account.
okie dokie imma give it a try wish me luck...and thanks...
bongrun said:
okie dokie imma give it a try wish me luck...and thanks...
Click to expand...
Click to collapse
And also, for testing purposes, what version of Android does your Nexus S run?
i'm running IMM76D ICS 4.0.4...
bongrun said:
i'm running IMM76D ICS 4.0.4...
Click to expand...
Click to collapse
Okie. Thanks for the response.
Sent from my Nexus S 4G using XDA
Great tutorial. Quick question, would you be able to get metro's 4G working on the phone or can you only receive their 3G data?
Metro is LTE. NS4G uses Wimax... so not a chance
Sent from my Nexus S 4G using Tapatalk 2
pimp8426 said:
Great tutorial. Quick question, would you be able to get metro's 4G working on the phone or can you only receive their 3G data?
Click to expand...
Click to collapse
MetroPCS uses LTE. The Nexus has WiMAX. Two different technologies.
3G doesnt seem to work on 4.0.4 i get 1x instead... is seems to work with 2.3.x just fine
Anyway to get 3G back?
Uzi5 said:
3G doesnt seem to work on 4.0.4 i get 1x instead... is seems to work with 2.3.x just fine
Anyway to get 3G back?
Click to expand...
Click to collapse
3g should work on 4.0.4. Go back and check your settings and that your prl is the correct one. Metro may have pushed prl 2004 to your phone.
Uzi5 said:
3G doesnt seem to work on 4.0.4 i get 1x instead... is seems to work with 2.3.x just fine
Anyway to get 3G back?
Click to expand...
Click to collapse
As chainsaw said, yes, metroPCS is always going to periodically push out the 2004 PRL to your phone to rid of your 3G data. Just try to re-write the 3029.prl file to your device again. Weird though, the firmware of the device shouldn't be affecting your network data connection either.
Sent from my Nexus S 4G using XDA
Metro is no longer accepting flashed phones.
Sent from my Nexus S 4G using Tapatalk 2
BananaOG said:
Metro is LTE. NS4G uses Wimax... so not a chance
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Wrong. You can use wimax with metro. Go to clear.com sign up for service and enter your Mac address of the wimax and as long as you are in a wimax area... good to go.
Sent from my Nexus S 4G using Tapatalk 2
Google_Nexus said:
Wrong. You can use wimax with metro. Go to clear.com sign up for service and enter your Mac address of the wimax and as long as you are in a wimax area... good to go.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I honestly never knew that. But I live in Florida, so there's no 4G service here. I'll surely give this a try when it comes.
Google_Nexus said:
Metro is no longer accepting flashed phones.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I'm aware. ESN's can't be added by MetroPCS themselves anymore. However, it can still be done with services like eBay or so, but I won't mention who exactly to get it done with.
So I have read through at least 50 threads and 10 PDFs to get this far. I also realized that I had to do everything on a 32bit machine since that is the only driver available for the Rant.
So here is a little background on what I have done so far. I rooted the Evo shift easily since it came with the stock 2.2 and installed the newest clockwork and Cyanogen Mod 7 R2. I also updated to the lastest radio (found it here in a thread and it came with an updated WiMax and touchscreen).
I managed to successfully transfer the ESN/MEID. I tried searching and realized it was futile when a new radio that no one knew the locations were. FINALLY, I found someone mentioned a method using EFS and got it to work. After the code 16 error, reactivating on boost mobile, my phone now accepts calls and messages no problem, however 3G is another story.
So some questions:
1. I noticed that my home address is not 0.0.0.0 like most of the guides out there but actually 0.0.0.1 for both profile 1 and 0. Is that okay?
2. My SPI for both profile 1 and 0 were blank and NOT 4D2. Is that okay?
3. My "Rev tunnel preferred" for both profile 1 and 0 were not checked. Is that okay?
4. Should the password for profile 0 and 1 (both HA and AAA) be the same or different? Something I thought I should ask.
Right now, I am going to find a Rom that comes with sense since it has been a pain to use the terminal in order to turn diag on in CM7. Also I am going to try rewriting the 465 and 466 files to the Evo again (I had a rant so 1192 and 1194 were useless essentially BUT I did transfer them over).
Thanks for all the views and help,
Alan
Have you tried THIS thread.
this guy apparently helps people switch their phones over too, i havent done it myself but worth a look:
https://www.facebook.com/groups/294474680575872/
So it seems that my new issue is that my HA and AAA passwords for both profiles refuse to save in QPST.
I downloaded the 465 and 466. 1192 and 1194 refused to write (I have a Rant but not sure if that makes a difference)
I also loaded a sense rom so I could get access to the regular commands.
Is there something I am missing? I entered the MPL password and then enter all the information in the MIP tab and set profile to 0. I click write and get this error
nv_ue_imei_i nv_read only's error
and when I go back to reading the phone when it reboots, nothing has changed.
alansupra94 said:
So it seems that my new issue is that my HA and AAA passwords for both profiles refuse to save in QPST.
I downloaded the 465 and 466. 1192 and 1194 refused to write (I have a Rant but not sure if that makes a difference)
I also loaded a sense rom so I could get access to the regular commands.
Is there something I am missing? I entered the MPL password and then enter all the information in the MIP tab and set profile to 0. I click write and get this error
nv_ue_imei_i nv_read only's error
and when I go back to reading the phone when it reboots, nothing has changed.
Click to expand...
Click to collapse
Just to let everyone know, I finally got the phone to work. 3G is REALLY slow but works. So does the phone and messages.
I actually got it to work using DFS 3.3.0.7 which can be found with searching (cough 4shared cough).
I pretty much swapped the ESN, flashed a completely stock 2.2 rom and then did a reset (##rsn#). After that it started working. Granted, I changed all the settings in DFS 3.3.0.7 before.
Hey alansupra94 can u give me a little bit more help on what to do with dfs? If u could pm me that would be great! I have been trying to get this for a day or so no luck! Thanks
Sent from my PG06100 using XDA
jerebediah said:
Hey alansupra94 can u give me a little bit more help on what to do with dfs? If u could pm me that would be great! I have been trying to get this for a day or so no luck! Thanks
Sent from my PG06100 using XDA
Click to expand...
Click to collapse
Sent you a pm.
Just to let everyone know, I figured out the problem. The Rant was never provisioned to get 3G and refused to on Boost Mobile. Got an Incognito and problem solved.
alansupra94 can you write a guide on this please?
If so, how did you fix MMS for our phone? It something that I still have problems with.
I was able to find a solution to my problem. Although I'm still having trouble with TW ROMs, AOSP ROMs work great with this.
eduncan911 said:
Ok, I had the same MMS issues after flashing June 29th's nightly in that I couldn't receive MMS.
DISCLAIMER: My service provider is Ting - which is a Sprint MVNO (a hell of a lot cheaper, see sig). There are known problems of running custom firmwares on Ting because the provisioning doesn't get set right from Sprint. Because of this, we custom-ROMers have to edit our APNs to make MMS work.
With that that said, I had to edit the APN file and select the correct one in the APN settings. Once i did that, BAM, I could send and receive MMS from other Ting users as well as verified from Verizon and AT&T. The only thing I haven't verified is MMS from other Sprint users, since I have changed the APNs (will do that later today).
NOTE: The instructions below is to get MMS working on the Galaxy S4 with CM10.1 Nightly build June 29th. You may ignore the mms.plspictures.com settings, and it may work for normal Sprint users. Or hell, try to use the mms.plspictures.com anyways to see if it works on Sprint. mms.plspictures.com seems to be an open gateway for any carrier, as it is specified as the Roaming option in stock ROMs.
Step 1: The apn.conf.xml file...
First thing I noticed when starting to flux with my APNs is that CM10.1 includes a butt-load in their drops - that every variant gets (Verizon, AT&T, T-Mobile, Boost, Sprint, etc etc). Nothing about Ting in here. It seems to be a one-size fits all.
Someone that has the time to research what each specific setting is, and the codes, might be able to clean up CM10.1's APN file to match/get updated to match the Samsung oem one for Sprint variants. But I don't have that time.
At first, I tried to edit the CM10.1 file for Ting-specific requirements: replace all instances of mms.sprintpcs.com with mms.plspictures.com. This did not work, though I forgot about Step 2 below so it may have worked.
What I did was to copy the Sprint Samsung Galaxy S4's stock/oem apns-conf.xml file off before I threw CM10.1 onto the phone. This file is attached as:
Code:
// original Sprint Galaxy S4's APN file attached
//
apns-conf.xml.gs4-oem.zip
// rename it to apns-conf.xml if you plan to use it.
//
// this file exists in /system/etc/
// you must mount as read/write to copy the file
// (or use root explorer, es file explorer, etc).
//
You'll notice it is a hell of a lot smaller than the CM10.1 version. Again, I think the CM10.1 version is a one-size-fits-all approach. How about we just use the Spring version, since that is our variant? See attached gs4-oem file.
Now, this still did not work on the S4 with CM10.1 6/29/2013 nightly. So I edited the file to match the Ting specifics outlined above, with mms.plspictures.com. Still didn't work.
Finally, I forgot one last step...
Step 2: Specify which "APN to use", whatever that means...
There is one last step you must do when editing this APN file: you have to "edit and select it" elsewhere in the UI. For some reason, while this does list the the APNs in your config file, the settings are still wrong. You have to change them as well.
With CM10.1, there is a "Voice Dialer" app. You must use this app to access the APNs to edit and select as I have no idea how to get to this edit screen without that Voie Dialer app. On Samsung's S4 stock ROM, there is a ##....# combination to enter to get to a similar menu - but still different.
1) Open Voice Dialer and say, "Open A P Ns", just like that.
2) Once open, you'll have to go into each APN and see if it lists mms.sprintpcs.com. If it does, change it to mms.plspictures.com. Change each and every one you see.
2b) If you edit, REMEMBER TO SAVE IT! This is so cumbersome, but after you edit a field, make sure to click the Menu button, and there is the hidden option to "Save" it. If you just click back, you'll loose your changes.
3) lastly, you'll need to select/click on the bullet-point to select the one you edited. If you are using the CM10.1 apn-conf.xml file, it's your best guess as to which one to select - I can't help you there. Using the attached apn-conf.xml.gs4-oem.zip, you only have 1 to select that had mms.sprintpcs.com.
4) Reboot.
A note on step 2 above, I was using the oem Sprint Samsung Galaxy S4 apn-conf.xml that I attached to this post. So I only had 3 listed, and only 1 had the mms.sprintpcs.com. If you don't use the oem Sprint apn.conf.xml and want to try using the CM10.1 version, you'll be editing 4 or 6 of them! Yes, there's a lot more to edit. Make sure to edit each and every one though, because that's the only way I got my Galaxy Nexus to work on Ting as well. But now my Galaxy Nexus is using this same apn-conf.xml.gs4-oem.zip that I attached, only 1 to edit now.
OT: MMS over WIFI: the holy grail for us Ting users is getting MMS working over WIFI with AOSP-based ROMs (so we can limit our data usage). I've tried dozens of combinations and have come to the conclusion that the stock Messaging app in AOSP (and any AOSP-based ROM across several devices) is somehow hardcoded to use only a specific mobile-specific APN for sending and receiving MMS. If I ever get the time, among my dozens of other projects (building a house, by hand!), I would grab a dump of the AOSP, looking for how a text message is received and determined to be an MMS message, and see how it accesses which APN/network device to send/receive with. I would then compare it by decompiling the oem Samsung Galaxy S4's Messenger APK (if it is not obfuscated) - because the stock Samsung Galaxy S4 DOES SEND OVER WIFI! I verified this with Ting billing, as well as leaving Mobile Data off all of the time as well as with BetterBatteryStats (after I rooted the stock S4) and looked at what was using network bandwidth. Samsung's stock (and really sh1tty / non-Emoji-compatible / non-Japanese friendly / compresses images too small - all compared to AOSP's original Messaging app) Messaging app was listed as using Wifi for the size of the pictures I was sending!
Such a PITA...
Click to expand...
Click to collapse
Like they tittle Say anyway to bypass T-Mobile tether?
If rooted...
Then theres various ways to bypass and if used together chances are good you won't have to pay 2x for data: modifying your apn to allow dun type, adding the line: net.tethering.noprovisioning=true
to your build.prop and finally using adb from a PC (u can try this even if not rooted) type the following from cmd or powershell: "adb shell" followed by "settings put global tether_dun_required 0" without the " "s and restart your phone n hopefully that should do the trick.
If still throttled by TMo go into Magisk and install tethering_enabler or TTL tethering modules. These modules weren't specifically made for the 6T but they should still be effective. If still unsuccessful then modifying the TTL from the device your trying to tether to will help hide the source of data aim for TTL of 65 to confuse tmo.
If your not rooted then use PDANet USB tether to a PC and hide tether options then create a hotspot from the PC your USB tethered to or use the WiFi Sharing option in PDANet PC Menu. At least thats what works the best for me and I've tried many many things... One other possibility if your on stock no root is to add a new apn with all the same info as normal fast.tmobile.net lte apn only enable MVNO type to GIO for apn type leave it blank and save it. This should hide the default TMobile apn (and make the editor think your using a 3rd party like Mint) now go back and edit the new apn and under apn type put: dun,default,mms,supl try and save it. It should error n say dun not supported... Press Home and force close settings-reboot phone. The dun sometimes will stick if this method isn't patched yet I'm sure it will be soon.
Your final options are to use an app from playstore like VPN Hotspot or VPN Tether they might slow your speed a bit but they should tunnel all your data thru a VPN confusing TMo as to the origin of data. Probably the best and easiest way is by using a custom ROM as most haven't been tainted by Google's latest CarrierConfigManager commits or carrier apn restrictions. If anyone knows how to reverse these commits easily or any other methods not listed please let me know.
I'm currently looking for a clean TMo only dun enabled apns-config.xml so I can overwrite the default n modify the build.prop for a quick fix on any new ROM or update...
As you can probably tell being throttled or having to pay 2x for the same data is a pet peeve of mine and I've spent some time researching the topic. I'd love to hear what ended up working for you or if anyone knows a solid method I missed. Or has a recommendation for a good ROM with unlimited hotspot features built in for the 6t let me know.
I installed the app from this thread, https://www.xda-developers.com/vpn-hotspot-share-vpn-connection/. You can also download the app in the Playstore. I also subscribe to Private Internet Access (https://privateinternetaccess.com) and they have an app that you can download from the playstore.
My phone contract has overseas roaming for a number of days but it restricts tethering and hotspot when roaming. The way I bypass this limitation is to run the PIA VPN, then run the VPN Hotspot app, and use the "Repeater" function. This has worked flawlessly sharing my internet connection with other devices..
gigilie said:
Then theres various ways to bypass and if used together chances are good you won't have to pay 2x for data: modifying your apn to allow dun type, adding the line: net.tethering.noprovisioning=true
to your build.prop and finally using adb from a PC (u can try this even if not rooted) type the following from cmd or powershell: "adb shell" followed by "settings put global tether_dun_required 0" without the " "s and restart your phone n hopefully that should do the trick.
If still throttled by TMo go into Magisk and install tethering_enabler or TTL tethering modules. These modules weren't specifically made for the 6T but they should still be effective. If still unsuccessful then modifying the TTL from the device your trying to tether to will help hide the source of data aim for TTL of 65 to confuse tmo.
If your not rooted then use PDANet USB tether to a PC and hide tether options then create a hotspot from the PC your USB tethered to or use the WiFi Sharing option in PDANet PC Menu. At least thats what works the best for me and I've tried many many things... One other possibility if your on stock no root is to add a new apn with all the same info as normal fast.tmobile.net lte apn only enable MVNO type to GIO for apn type leave it blank and save it. This should hide the default TMobile apn (and make the editor think your using a 3rd party like Mint) now go back and edit the new apn and under apn type put: dun,default,mms,supl try and save it. It should error n say dun not supported... Press Home and force close settings-reboot phone. The dun sometimes will stick if this method isn't patched yet I'm sure it will be soon.
Your final options are to use an app from playstore like VPN Hotspot or VPN Tether they might slow your speed a bit but they should tunnel all your data thru a VPN confusing TMo as to the origin of data. Probably the best and easiest way is by using a custom ROM as most haven't been tainted by Google's latest CarrierConfigManager commits or carrier apn restrictions. If anyone knows how to reverse these commits easily or any other methods not listed please let me know.
I'm currently looking for a clean TMo only dun enabled apns-config.xml so I can overwrite the default n modify the build.prop for a quick fix on any new ROM or update...
As you can probably tell being throttled or having to pay 2x for the same data is a pet peeve of mine and I've spent some time researching the topic. I'd love to hear what ended up working for you or if anyone knows a solid method I missed. Or has a recommendation for a good ROM with unlimited hotspot features built in for the 6t let me know.
Click to expand...
Click to collapse
Be sure you reset APN to default values after you install this new file....
Thanks bro I'll test it out...if it works care if I add it to the main post? Yeah I mentioned the VPN app along with a VPN my only issue with that method is the decrease in speed and some apps/devices don't like the VPN way much. Wish google would stop letting carriers dictate Android or itd b nice if the US would put their foot down and not allow companies to bend us over lock our bootloader's, phone's, devices we pay for or try and swindle us by charging 2x for data or throttle us...
gigilie said:
Thanks bro I'll test it out...if it works care if I add it to the main post? Yeah I mentioned the VPN app along with a VPN my only issue with that method is the decrease in speed and some apps/devices don't like the VPN way much. Wish google would stop letting carriers dictate Android or itd b nice if the US would put their foot down and not allow companies to bend us over lock our bootloader's, phone's, devices we pay for or try and swindle us by charging 2x for data or throttle us...
Click to expand...
Click to collapse
seems to work for me. let me know if it works for you....
dustintinsley said:
seems to work for me. let me know if it works for you....
Click to expand...
Click to collapse
Where do I install the files?
LuCkyCn said:
Where do I install the files?
Click to expand...
Click to collapse
replace the file in /etc/
backup your old file first....
dustintinsley said:
replace the file in /etc/
backup your old file first....
Click to expand...
Click to collapse
Not sure what I did wrong, but it's not loading for me. All my APNs disappeared. I reset to default after replacing with the one provided.
Well, I know this post is rather old, but I made a Magisk module that does everything for you...
L
oloyin