Here is my apns-conf.xml file is there something wrong with it? My MMS will not work unless I'm on stock ROM hope this helps.. As I'm out of ideas also to clarify I have the virgin mobile galaxy s2 d710
<?xml version="1.0" encoding="utf-8"?>
<!--
/*
** Copyright 2012, Cyanogenmod
**
** Licensed under the Apache License, Version 2.0 (the "License");
** you may not use this file except in compliance with the License.
** You may obtain a copy of the License at
**
** http://www.apache.org/licenses/LICENSE-2.0
**
** Unless required by applicable law or agreed to in writing, software
** distributed under the License is distributed on an "AS IS" BASIS,
** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
** See the License for the specific language governing permissions and
** limitations under the License.
*/
-->
<!-- use empty string to specify no proxy or port -->
<!-- This version must agree with that in apps/common/res/apns.xml -->
<apns version="7">
<apn carrier="MobiPCS" mcc="310" mnc="00" apn="MobiPCS" user="@mobipcs.com" password="mobipcs" mmsc="http://mms.mobipcs.com" authtype="3" type="*" />
<apn carrier="Verizon" mcc="310" mnc="004" apn="internet" user="*" password="*" server="*" mmsc="http://mms.vtext.com/servlets/mms" type="default,supl,mms" />
<apn carrier="Cricket" mcc="310" mnc="16" apn="wap.mycricket.com" user="@mycricket.com" password="cricket" mmsc="http://mms.mycricket.com/servlets/mms" mmsproxy="" mmsport="" proxy="wap.mycricket.com" port="8080" authtype="2" type="*" />
<apn carrier="MetroPCS" mcc="310" mnc="027" apn="wap.metropcs.net" user="[email protected]" password="metropcs" server="http://mms.metropcs.net/servlets/mmsc" mmsc="http://mms.metropcs.net/mmsc" mmsport="3128" type="default,supl,mms" />
<apn carrier="Sprint" mcc="310" mnc="120" apn="Sprint" user="Sprint" server="*" password="*" mmsc="http://mms.sprintpcs.com" authtype="3"/>
<apn carrier="Virgin Mobile US" mcc="311" mnc="490" apn="0" mmsproxy="205.239.233.136" mmsport="81" mmsc="http://mmsc.vmobl.com:8088/mms?" port="" type="mms" />
<apn carrier="Boost MMS" mcc="505" mnc="02" apn="mms" user="" password="" server="" proxy="61.88.190.10" port="8070" mmsc="http://mmsc.optus.com.au:8002/" mmsproxy="61.88.190.10" mmsport="8070" type="mms" authtype="3"/>
<apn carrier="Boost Mobile" mcc="505" mnc="02" apn="yesinternet" user="" password="" server="" proxy="" port="" mmsc="" mmsproxy="" mmsport="" type="default,supl" authtype="3"/>
</apns>
Sent from my SPH-D710 using xda premium
Edit: I flashed the vmmmsfix and now I can get the message to show up as "downloading" but never shows up
Sent from my SPH-D710 using xda premium
Try APN Backup and Restore from the play store. Backup your apn from the stock Rom, flash the new Rom, then restore your apn.
riggerman0421 said:
Try APN Backup and Restore from the play store. Backup your apn from the stock Rom, flash the new Rom, then restore your apn.
Click to expand...
Click to collapse
Depending on the Android version. APN backup/restore apps will not work. I know they block it in JB
Sent from my SPH-D710 using xda premium
This is correct, I ended up fixing it by editing my APN confg XML all I did was delete all of it besides the VM one. Booted into recovery wiped delvic cache waited about 15 minutes and I was able to send MMS once again
Sent from my SPH-D710 using xda premium
Related
Ok heres a good one that the search does not return a good thread so here goes.
My DINC is running a pretty much stock 2.2 ROM, rooted, Clockwork, Flash fixed to run HULU and does a great job with everything else too. I have been running this ROM for quite a while and have done nothing really to it for months except for hanging the numbers in build.prop to make it stop nagging me for the update, which I did not want nor did I install. I have always been able to receive and send test messages with or without attachments, until about a week ago when someone sent me a text with a picture attached and all I got was "message failed to download" error that keeps popping up and dinging every few minutes. Today I got on this and starting trying thiongs to see what gives and found that if I try to send a text with a picture or attachment I get "message failed to send" and retry messages now every few minutes. Since I can send and receive from my other unit (TP2) I know that the servers are working. As long as I do not try to send or receive a text with anything attached all works well, but now this thing is dinging a dozen times every few minutes and like I said I have not changed anything or loaded up anything new lately, it just crapped out. Any ideas ????? Grazi ;-)
Still working on this, no luck yet
I just tried removing the stock Mms.apk and installing the vanilla and the results are the same except that when trying to send or receive a message with attachment it force closes. Help please .
Still working on it, latest
Ok I have put the stock MS back in and still get the same problems, but I started thinking and looked in settings and under the MMS connection settings the fields were all blank. i bet somthing goes there, anyone have those settings ??????/
FIXED
Ok have a look at the fix. I do not know how the APN got the [disabled] entries in there but it did.
APN Before Editing
bolded entries will be removed
==============
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns>
<apn name="Production" numeric="00000" mcc="000" mnc="00" apn="1[disabled]" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="2.0" mmsc="http://mms.vtext.com/servlets/mms" type="mms[disabled]" />
</apns>
APN After Editing
==============
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns>
<apn name="Production" numeric="00000" mcc="000" mnc="00" apn="1" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="2.0" mmsc="http://mms.vtext.com/servlets/mms" type="mms" />
</apns>
HTC desire CDMA after convert cellsouth to Reliance India Internet not working plz help me
there is no APN setting under wifi/network .. mobileNetwork
plz help me how to work my Reliance cdma Internet
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="2">
<apn name="Production" numeric="00000" mcc="000" mnc="00" apn="1" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="2.0" mmsc="http://pix.cellularsouth.com:80" type="mms" />
<apn name="Reliance" numeric="00000" mcc="404" mnc="00" apn="Internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="2.0" mmsc="http://pix.cellularsouth.com:80" type="mms" />
</apns>
no idea anybuddy .......
harry_01 said:
HTC desire CDMA after convert cellsouth to Reliance India Internet not working plz help me
there is no APN setting under wifi/network .. mobileNetwork
plz help me how to work my Reliance cdma Internet
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="2">
<apn name="Production" numeric="00000" mcc="000" mnc="00" apn="1" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="2.0" mmsc="http://pix.cellularsouth.com:80" type="mms" />
<apn name="Reliance" numeric="00000" mcc="404" mnc="00" apn="Internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="2.0" mmsc="http://pix.cellularsouth.com:80" type="mms" />
</apns>
Click to expand...
Click to collapse
Dear Customer,
We regret the inconvenience caused to you. This is to inform you that your concern has been noted. Please provide us your contact details such as Full name, mobile no., and the type of Inconvenience you are facing, so that we are able reach you. Our team is eager to help you.
Regards,
RCOMcare
RCOMcare said:
Dear Customer,
We regret the inconvenience caused to you. This is to inform you that your concern has been noted. Please provide us your contact details such as Full name, mobile no., and the type of Inconvenience you are facing, so that we are able reach you. Our team is eager to help you.
Regards,
RCOMcare
Click to expand...
Click to collapse
where u send you contact no or details and how 2 solved this problem
need to talk you in some issues
harry_01 said:
where u send you contact no or details and how 2 solved this problem
Click to expand...
Click to collapse
hello bro,
can you whatsapp me at +919371266944. when you are free.
jitu jain said:
hello bro,
can you whatsapp me at +919371266944. when you are free.
Click to expand...
Click to collapse
Shouldn't be posting your number?
Sent from my HTC Desire S using XDA Free mobile app
Hello,
This thread just to share two roms I made from original kdz D80220G.
I've tested each, installed from TWRP 2.8.0.1, after wipe system,data,cache and dalvick.
Both can be flashed on 16Go or 32 Go device.
---
The first one is a pure stock rom without root and with the stock recovery,that can be flashed from a custom recovery.
Root and custom recovery will be lost after the flash of this one .
For the root, for my part, I let TWRP 2.8.0.1 do so by following, by accepting the proposal he made to me at my request to reboot system after the flash. I was so easily rooted again.
For the custom recovery, the patched kernel does not yet exist for this version, installing a custom recovery you would lose the benefit of the news that may contain the kernel of this new firmware version.
Download link of this pure stock rom D80220G open eur, without root and with the stock recovery:
https://www.androidfilehost.com/?fid=95747613655046456
---
And the second is the same, but prerooted (SuperSu preinstalled) and allowing to keep the custom recovery.
Custom recovery will be kept after the flash of this one .
It's prerooted and with 20D Knock code Cloudyfa kernel integrated (simple stock KC kernel, just patched).
This pure stock rom D80220G open eur, prerooted and friendly custom recovery can be downloaded here:
https://www.androidfilehost.com/?fid=95784891001602117
---
Thank's to:
@thecubed for his [python][Tool] LG Compressed KDZ Extractor
@cybojenix for his tool (system merger)
@bullghost for his windows GUI version [TOOL] KDZ and TOT Extractor
and for the one prerooted, friendly custom recovery:
@Cloudyfa for the kernel and permission to integrate it, @bender_007 and @citytrader for their advice for the integration of patched kernel, @autoprime for his ioroot25 that inspired the way I proceeded to preroot, @Chainfire for his SuperSu
Can you check if it has Danish language inside for me, please?
And thanks!
Sent from my LG-D802
natalya said:
Can you check if it has Danish language inside for me, please?
And thanks!
Sent from my LG-D802
Click to expand...
Click to collapse
Yep, Dansk language is present and apns.xml includes all Danish operators:
<!--23 Denmark - Telenor 2-->
<apn carrier="Telenor MMS" mcc="238" mnc="02" apn="telenor" user="" server="" password="" proxy="" port="" mmsproxy="212.088.064.008" mmsport="8080" mmsc="http://mms.telenor.dk" type="mms" authtype="0" />
<apn carrier="Telenor Internet" mcc="238" mnc="02" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<!--24 Denmark - TDC 2-->
<apn carrier="TDC MMS" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380101xxxxxxxx" apn="mms" user="" server="" password="" proxy="" port="" mmsproxy="194.182.251.015" mmsport="8080" mmsc="http://mmsc.tdc.dk:8002" type="mms" authtype="0" />
<apn carrier="TDC Internet" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380101xxxxxxxx" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<apn carrier="TDC MMS" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380171xxxxxxxx" apn="mms" user="" server="" password="" proxy="" port="" mmsproxy="194.182.251.015" mmsport="8080" mmsc="http://mmsc.tdc.dk:8002" type="mms" authtype="0" />
<apn carrier="TDC Internet" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380171xxxxxxxx" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<apn carrier="TDC MMS" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380172xxxxxxxx" apn="mms" user="" server="" password="" proxy="" port="" mmsproxy="194.182.251.015" mmsport="8080" mmsc="http://mmsc.tdc.dk:8002" type="mms" authtype="0" />
<apn carrier="TDC Internet" mcc="238" mnc="01" mvno_type="imsi" mvno_match_data="2380172xxxxxxxx" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<!--25 Denmark - Telia 3-->
<apn carrier="Telia MMS" mcc="238" mnc="20" mvno_type="imsi" mvno_match_data="2382010x" apn="www.mms.mtelia.dk" user="" server="" password="" proxy="" port="" mmsproxy="193.209.134.131" mmsport="8080" mmsc="http://mms.telia.dk" type="mms" defaultflag="0" authtype="0" />
<apn carrier="Telia SurfPort" mcc="238" mnc="20" mvno_type="imsi" mvno_match_data="2382010x" apn="www.internet.mtelia.dk" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<apn carrier="Telia MMS" mcc="238" mnc="20" mvno_type="imsi" mvno_match_data="2382030x" apn="www.mms.mtelia.dk" user="" server="" password="" proxy="" port="" mmsproxy="193.209.134.131" mmsport="8080" mmsc="http://mms.telia.dk" type="mms" defaultflag="0" authtype="0" />
<apn carrier="Telia SurfPort" mcc="238" mnc="20" mvno_type="imsi" mvno_match_data="2382030x" apn="www.internet.mtelia.dk" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<!--119 Denmark - 3DK 2-->
<apn carrier="3" mcc="238" mnc="06" apn="data.tre.dk" user="" server="" password="" proxy="" port="" mmsproxy="mmsproxy.3.dk" mmsport="8799" mmsc="http://mms.3.dk" type="default,mms,dun,supl" defaultflag="0" authtype="0" />
<!--143 Denmark - CBB_Mobil 2-->
<apn carrier="CBB MMS" mcc="238" mnc="02" mvno_type="spn" mvno_match_data="CBB Mobil" apn="telenor" user="" server="" password="" proxy="" port="" mmsproxy="212.088.064.008" mmsport="8080" mmsc="http://mms.telenor.dk" type="mms" authtype="0" />
<apn carrier="CBB Internet" mcc="238" mnc="02" mvno_type="spn" mvno_match_data="CBB Mobil" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" authtype="0" />
<!--144 Denmark - Telmore 2-->
<apn carrier="Telmore MMS" mcc="238" mnc="01" mvno_type="spn" mvno_match_data="TELMORE" apn="mms" user="" server="" password="" proxy="" port="" mmsproxy="194.182.251.015" mmsport="8080" mmsc="http://192.168.241.114:8002" type="mms" defaultflag="0" authtype="0" />
<apn carrier="Telmore Internet" mcc="238" mnc="01" mvno_type="spn" mvno_match_data="TELMORE" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<!--145 Denmark - Call_me 2-->
<apn carrier="Call me MMS" mcc="238" mnc="20" mvno_type="spn" mvno_match_data="Call me" apn="mmsSP" user="" server="" password="" proxy="" port="" mmsproxy="193.209.134.131" mmsport="8080" mmsc="http://mms.telia.dk" type="mms" defaultflag="0" authtype="0" />
<apn carrier="Call me Internet" mcc="238" mnc="20" mvno_type="spn" mvno_match_data="Call me" apn="webSP" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<!--177 Denmark - DLG_Tele 2-->
<apn carrier="DLG Tele MMS" mcc="238" mnc="20" mvno_type="spn" mvno_match_data="DLG Tele" apn="mmsSP" user="" server="" password="" proxy="" port="" mmsproxy="193.209.134.131" mmsport="8080" mmsc="http://mms.telia.dk" type="mms" defaultflag="0" authtype="2" />
<apn carrier="DLG Tele GPRS" mcc="238" mnc="20" mvno_type="spn" mvno_match_data="DLG Tele" apn="webSP" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
<!--224 Denmark - BiBoB 1-->
<apn carrier="BiBoB" mcc="238" mnc="02" mvno_type="spn" mvno_match_data="BiBoB" apn="telenor" user="" server="" password="" proxy="" port="" mmsproxy="212.088.064.008" mmsport="8080" mmsc="http://mms.telenor.dk" type="mms" defaultflag="0" authtype="0" />
<apn carrier="BiBoB Internet profil" mcc="238" mnc="02" mvno_type="spn" mvno_match_data="BiBoB" apn="internet" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsc="" type="default" defaultflag="0" authtype="0" />
6ril1 said:
Hello,
This thread just to share this rom I made from original kdz D80220G.
it is a pure stock rom without root and with the stock recovery, that can be flashed from a custom recovery.
Root and custom recovery will be lost after the flash.
For the root, for my part, I let TWRP 2.8.0.1 do so by following, by accepting the proposal he made to me at my request to reboot system after the flash. I was so easily rooted again.
For the custom recovery, the patched kernel does not yet exist for this version, installing a custom recovery you would lose the benefit of the news that may contain the kernel of this new firmware version.
I've installed this rom from TWRP 2.8.0.1, after wipe system,data,cache and dalvick
Download link:
https://www.androidfilehost.com/?fid=95747613655046456
Thank's to:
@thecubed for his [python][Tool] LG Compressed KDZ Extractor
@cybojenix for his tool (system merger)
@bullghost for his windows GUI version [TOOL] KDZ and TOT Extractor
@somboons for his thread [GUIDE-VDO] How to make your own KitKat ROM with Root+TWRP from KDZ
Click to expand...
Click to collapse
This can be flashed via Custom Recovery on D802 ??
i wonder whats new and impoved in this version of stock rom
whats new??
-iNCEPTiON- said:
This can be flashed via Custom Recovery on D802 ??
Click to expand...
Click to collapse
Yes (wipes recommended), and you will lose your custom recovery and root after the flash.
You can then root after with ioroot, but for the custom recovery, if you want to install it again, you will lose the potential benefit of the new kernel of 20G.
If you have TWRP 2.8.0.1, it will propose you to root when you'll ask the reboot after flashing. If you accept, you'll be invited to install supersu after the boot.
It's a pure stock rom, without root, and without patched kernel for keeping recovery.
shriom_manerker said:
i wonder whats new and impoved in this version of stock rom
Click to expand...
Click to collapse
No idea. The vulnerability exploited by Towelroot seems to be patched (i 've not tried, but it's said in this thread http://forum.xda-developers.com/lg-g2/general/d80220g-update-t2904346), stock recovery is accessible, so ioroot works.
This post links a binary comparaison http://forum.xda-developers.com/showpost.php?p=56019091&postcount=45.
In France many people complained of a bug on the 20f, about inadvertent switch between silent mode and normal mode. Those high expectations of an update, but I have not read back on this 20G, if it solved the problem. Probably too early.
For my part, I was in 20f and have not found the bug in question.
For now I have not encountered any problem with this 20g
6ril1 said:
you will lose the potential benefit of the new kernel of 20G.
Click to expand...
Click to collapse
What you meant with that?
Enviado desde un lugar muy muy lejano con mi D806
For having custom recovery with kitkat d802, you must downgrade bootloader and have a patched kernel for booting behind downgraded bootloader.
And patched 80220G kernel doesn't exist yet.
So if you put a custom recovery on this 20G, you have to use older patched kernel.
6ril1 said:
For having custom recovery with kitkat d802, you must downgrade bootloader and have a patched kernel for booting behind downgraded bootloader.
And patched 80220G kernel doesn't exist yet.
So if you put a custom recovery on this 20G, you have to use older patched kernel.
Click to expand...
Click to collapse
Does this mean I cannot install recovery on v20g with autorec (errors, fail, brick device...)? Or it means I can however use autorec to install recovery and it will work, even if loosing benefits of v20g?
has anybody tried Auto Rec by Cloudyfa with this 20G rom?
zekurosu said:
has anybody tried Auto Rec by Cloudyfa with this 20G rom?
Click to expand...
Click to collapse
I tried it and it worked without problem.
titomax82 said:
Does this mean I cannot install recovery on v20g with autorec (errors, fail, brick device...)? Or it means I can however use autorec to install recovery and it will work, even if loosing benefits of v20g?
Click to expand...
Click to collapse
I think he means that autorec will flash a kernel with that patched, but it won't be the g version it will be an old version, so we are not gonna have all improves from g version
Enviado desde un lugar muy muy lejano con mi D806
titomax82 said:
Does this mean I cannot install recovery on v20g with autorec (errors, fail, brick device...)? Or it means I can however use autorec to install recovery and it will work, even if loosing benefits of v20g?
Click to expand...
Click to collapse
Tinchoska said:
I think he means that autorec will flash a kernel with that patched, but it won't be the g version it will be an old version, so we are not gonna have all improves from g version
Click to expand...
Click to collapse
That's exactly what I mean, yes.
The patched kernel can only be produced if the sources were published, and it is not the case for 20G. The latest version released back to the 20D.
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=d802
However the latest patched kernel available (the one containing knock code) should work fine.
But if changes (improvements) were made on the 20G (I do not know if this is the case), the benefit of these innovations would be lost with the installation of an older kernel (20D).
Note: It was the same situation with the 20f.
Brief ...
Yes AUTOREC should work fine, but it will install an older kernel
then it should not be an issue because we can always flash latest twrp & dorimanx kernel :good:
as of now im enjoying stock 20G thanks to you mate :good:
If I backup my current v20g stock kernel with flashify,
then use autorec to install recovery,
then I restore my previous saved stock kernel with flashify,
will work? Or do I need necessarily a patched v20g?
Thanks for this rom. It would have been great to have removed some of Google apps and added xdabbeb camera. But so far so good.
titomax82 said:
If I backup my current v20g stock kernel with flashify,
then use autorec to install recovery,
then I restore my previous saved stock kernel with flashify,
will work? Or do I need necessarily a patched v20g?
Click to expand...
Click to collapse
Don't do that !
You must have a patched kernel for booting behind downgraded bootloader (downgraded bootloader is required for having custom recovery, because LG have patch loki exploit with 4.4.2 bootloader).
You don't need a patched kernel in a 20G version, just a patched kernel.
On another subject, I edited OP for giving a link to a post, where I give links to LG server for originals 20G kdz
Thanks for the advise, I was already thinking that, but someone on other thread said it was good... but I had my doubts and you confirm them. I'm a little confused by this statment:
6ril1 said:
You don't need a patched kernel in a 20G version, just a patched kernel.
Click to expand...
Click to collapse
I'm not sure that I understood...
titomax82 said:
I'm not sure that I understood...
Click to expand...
Click to collapse
20G patched kernel doesn't exist, so when you ask
Or do I need necessarily a patched v20g?
Click to expand...
Click to collapse
I answer: no, you need just a patched kernel, not in a 20G version (not a 20G patched kernel).
I'm going back to using a Sprint Note 2. I remember probably a year ago that TWRP would not work right and I had to use Philz Touch recovery. I saw that it is still currently maintained by TWRP so I'm wondering if the latest 3.0.2-0 works right? IIRC the older versions wouldn't boot after flashing anything.
The latest works great.
Sent from my SPH-L900 using XDA-Developers mobile app
skryte said:
The latest works great.
Sent from my SPH-L900 using XDA-Developers mobile app
Click to expand...
Click to collapse
I decided to try it out and it didn't work great for me. I made a full backup of my stock OH3 before messing with anything. I flashed Mokee 6.0.1 and it worked for that. But I couldn't change my APNs- so I did a full wipe and restored my nandroid backup made in TWRP. At first it booted and got a bunch of force closing apps, then after rebooting it just hung at "Android is starting" with a spinny thing for forever. I rebooted into TWRP and wiped cache/dalvik cache but it still didn't work. So I'm back to using Philz Touch which appears to be working fine. Just sucks because I like the interface on TWRP a million times better than Philz Touch.
I had issues with oh3. I'm on rwilcos ne2. I also had troubles with restoring a back up with any recovery. In anything above 5 your not going to be able to change the apn manually. You'll have to flash a fix for your carrier.
Sent from my SPH-L900 using XDA-Developers mobile app
skryte said:
I had issues with oh3. I'm on rwilcos ne2. I also had troubles with restoring a back up with any recovery. In anything above 5 your not going to be able to change the apn manually. You'll have to flash a fix for your carrier.
Sent from my SPH-L900 using XDA-Developers mobile app
Click to expand...
Click to collapse
How do I flash a fix? I have the APN info that I need but how does one make a flashable zip?
Code:
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="5">
<apn name="Global Roaming - SPRINT" numeric="310120" mcc="310" mnc="120" apn="cinet.spcs" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mms.sprintpcs.com" type="default,supl,mms,dun,fota" />
<apn name="APN0 LTE ota" numeric="310120" mcc="310" mnc="120" apn="otasn" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="null" mmsc="" type="fota" />
<apn name="APN0 EHRPD ota" numeric="310120" mcc="310" mnc="120" apn="otasn" user="" server="" password="" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="null" mmsc="" type="fota" />
<apn name="APN2 LTE internet" numeric="310120" mcc="310" mnc="120" apn="n.boost.ispsn" user="" server="" password="" proxy="" port="" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mms.sprintpcs.com" type="default,mms" />
<apn name="APN2 EHRPD internet" numeric="310120" mcc="310" mnc="120" apn="n.boost.ispsn" user="" server="" password="" proxy="" port="" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mms.sprintpcs.com" type="default,mms" />
</apns>
Depends on what carrier you have. I have boost and their are a few flash ables for it.
Sent from my SPH-L900 using XDA-Developers mobile app
---------- Post added at 09:43 AM ---------- Previous post was at 09:38 AM ----------
If you are just having truble sending mms then I would suggest using go sms. They have an option to add apn settings in advanced and that's what I do as data usually works fine.
Sent from my SPH-L900 using XDA-Developers mobile app
History:
Boostmobile S6
CODENAME: zerofltespr (same as for sprint)
Baseband: G920PVPS4CPI3
Software: G920PVPS4CPI3
Bootloader: G920PVPS4CPI3
*** BACKUP EVERYTHING FROM YOUR PHONE ON TO YOUR COMPUTER OR SOMETHING (Google Drive,Flash Drives,Email) ***Always read the DISCLAIMER file before committing to the use of this flashable mod.
These are points to note:
1. you better install the latest TWRP first. Most of the ROMs after KK required that.
2. KK was the most stable and usable from reports.
3. LP is memory hunger and not friendly to our device
4. MM is the latest I tried.
5. The main issue would be the growth of Gapps service. From 20M to over 100M now.
-Daniel_HK
Click to expand...
Click to collapse
1)A ROOT YOUR PHONE: PingPongRoot, or any other, as there are more now
My phone was rooted, only with the stock samsung recovery.
Using: PingPong Root
By idler1984
This was before TWRP was officially out for our s6.
1)B: Download TWRP from their site: LINK
Or Download directly here: Download twrp-3.1.0-0-zerofltespr.img
by BigBif
{
"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"
}
Like any other flash, put that img file onto your internal card, i did and made a new folder, new files, and just stuck everything in there, doesnt matter, just know where you put yours
1)C:[OPTIONAL] From this point, i personally installed [ROM] [SM-G920P] [DEBLOAT/DEODEX] TDH-JR (Just enough ROM) [v3.0]
By tdhite
Mainly because i wanted to make sure it would take a basic rom, hardly modded, and not cause any issues, before i moved on.
- Issues: No LTE (no MMS)
APN settings were most likely not right, if you want to download and install APNs: apns-Boost.xml
Or visit this xda Post with more information and options: Boost Mobile APN fix for any ROM
I installed the BoostMobile Fix for Sprint Roms
-By mholloway In case i would have issues, i could use this to fix it (i didnt need it after all w/bigdaddy)
So, the Roms thus far, were taking, just not 100%, no mms, no apn, little stuff that could modified to work.
2) Now, i felt confident that our boost s6 could take a full custom rom:
- Sprint Samsung Galaxy S6 Biggdaddy Rom 6.0.1
-Byamieldl143
-DOWNLOAD THE IMG HERE: LINK Flash it using TWRP
-Grace UX apps
Note 7 Camera
Weather widget
Clock
Highlight player
Keyboard
Sbrowser
Secmemo
Slowmotion
Splanner
Videoeditor
VideoTrimmer
Galaxyapps
Incallui
Photostudio
Samsung Account
Videoplayer
SecCalculator
SecContacts
Secgallery
Secmms
Secmyfiles
SmartManager
Storyservice
TouchwizHome
Voicenote
Wallpaper Cropper
Wallpaper Cropper2
Wallpaperpicker
Video
Download: LINK
(Dont worry if you flashed this WITH or RIGHT after the ROM was flashed, then rebooted...its still ok)
Optional: Links
Tdhite Enable Hotspot : LINK
Tdhite Skyhigh Kernel: LINK
Installation instructions:
1 Make sure on PL3 firmware(preferred)
2 Make backup just incase
3 Place Rom in internal storage
4 Suggest you delete android file and download cleaner in app store and run to clean your system.
5 boot into recovery do full wipe and flash rom
takes about 15 to 20 mins.
6 Let Rom settle in for 3 to 7 days -(it settled in pretty quickly for me)
Click to expand...
Click to collapse
AFTER ROM INSTALL:
Software: G920PVPS4CPL3
HARDWARE: G920P.02
MODEL: SM-G920P
Baseband: G920PVPS4CPL3
Kernel:
-3.10.61-8847946
[email protected] #1
-Sep 20 2016
Buildnumber: BiggdadyCPl3GraceUX
Overall status: Pleased, everything is working, no lag, no Force Closes.
The FIRST bootup did take about 5-8min
it asked to connect to wifi for the setup, this is where i said no on that, so i could make sure the lte/4g was actually working (it was) then i later continued to use wifi to restore my apps/settings via samsung and/or Google Sync
*** BACKUP EVERYTHING FROM YOUR PHONE ON TO YOUR COMPUTER OR SOMETHING (Google Drive,Flash Drives,Email) ***
For advanced users or more detailed info on boost mms,apns (All others ignore below this line)---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
MISC INFO:
MMSC Settings: http://mm.myboostmobile.com
MMS Proxy: 68.28.31.7
MMS Port: 88
APNS: These are from the XML file, do not need to worry about this, unless you come here later looking for particular info, otherwise ignore
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="15">
<apn name="LTE - SPRINT OTA" numeric="310120" mcc="310" mnc="120" apn="otasn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="fota" />
<apn name="LTE - SPRINT test ISP" numeric="00101" mcc="001" mnc="01" apn="n.ispsn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mm.myboostmobile.com" type="default,mms" />
<apn name="LTE - SPRINT test OTA" numeric="00101" mcc="001" mnc="01" apn="otasn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="fota" />
<apn name="LTE - SPRINT test PAM" numeric="00101" mcc="001" mnc="01" apn="pamsn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="dun" />
<apn name="LTE - SPRINT test ISP" numeric="001010" mcc="001" mnc="010" apn="n.ispsn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mm.myboostmobile.com" type="default,mms" />
<apn name="LTE - SPRINT test OTA" numeric="001010" mcc="001" mnc="010" apn="otasn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="fota" />
<apn name="LTE - SPRINT test PAM" numeric="001010" mcc="001" mnc="010" apn="pamsn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="dun" />
<apn name="EHRPD - SPRINT OTA" numeric="310120" mcc="310" mnc="120" apn="otasn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="fota" />
<apn name="EHRPD - SPRINT test ISP" numeric="00101" mcc="001" mnc="01" apn="n.ispsn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mm.myboostmobile.com" type="default,mms" />
<apn name="EHRPD - SPRINT test OTA" numeric="00101" mcc="001" mnc="01" apn="otasn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="fota" />
<apn name="EHRPD - SPRINT test PAM" numeric="00101" mcc="001" mnc="01" apn="pamsn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="dun" />
<apn name="EHRPD - SPRINT test ISP" numeric="001010" mcc="001" mnc="010" apn="n.ispsn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mm.myboostmobile.com" type="default,mms" />
<apn name="EHRPD - SPRINT test OTA" numeric="001010" mcc="001" mnc="010" apn="otasn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="fota" />
<apn name="EHRPD - SPRINT test PAM" numeric="001010" mcc="001" mnc="010" apn="pamsn" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="null" type="dun" />
<apn name="Global Roaming - SPRINT" numeric="310120" mcc="310" mnc="120" apn="cinet.spcs" user="null" server="null" password="null" proxy="null" port="null" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mm.myboostmobile.com" type="default,supl,mms,dun,fota" />
</apns>
Click to expand...
Click to collapse
ODIN METHOD
- installing TWRP
Run odin, Click AP, choose the file twrp-3.3.1-0-zerofltespr.img.tar
press start... phone does it thing.
It will auto-boot, at that time, unplug, and hold down VOLUME UP+HOME KEY+POWER Until you see TEAMWIN Logo.
From there, you can install ROMs, kernels.
Through the install process it will ask what kernel you want, i chose skyhigh 3.60
No SD card Slot?
Go buy a micro-c To USB: HERE
Then attach a usb Stick, the one that works that i used is: HERE
Then just put the rom and anything else in there, on the 64GB flash drive, mentioned above, and plug it into the extension cable, mentioned above, and plug into phone, in TWRP you can chose USB storage as a option to load file from.
If theres a new ROM with latest android OS, please comment below.