• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] [OLD]Sprint to Virgin Mobile LTE/MMS FIX [OLD]

Rate how the mods worked for you

  • Universal CM-AOSP worked (LTE / 3G / MMS / Internet)

    Votes: 4 20.0%

  • Universal CM-AOSP partially worked

    Votes: 3 15.0%

  • CM ROM Version 1 Worked (LTE / 3G / MMS / Internet)

    Votes: 2 10.0%

  • CM ROM Version 1 partially worked

    Votes: 2 10.0%

  • AOSP Version 1 worked (LTE / 3G / MMS / Internet)

    Votes: 0 0.0%

  • AOSP Version 1 partially worked

    Votes: 0 0.0%

  • AOSP Version 2 worked (LTE / 3G / MMS / Internet)

    Votes: 3 15.0%

  • AOSP Version 2 partially worked

    Votes: 0 0.0%

  • TW Version 1 worked (LTE / 3G / MMS / Internet)

    Votes: 2 10.0%

  • TW Version 1 partially worked

    Votes: 0 0.0%

  • TW Version 2 worked (LTE / 3G / MMS / Internet)

    Votes: 1 5.0%

  • TW Version 2 partially worked

    Votes: 4 20.0%
  • Total voters
    20
I have tried several different installs of Blackbean but I have not successfully gotten LTE working. If I put the phone into EVDO only mode I do get data and can send MMS messages. Because the camera doesn't work I have personally stopped trying and I'm going to try a different ROM.
 
MopedRyder said:
Unfortunately I cannot reproduce. Because I have a newer GS3 I cant flash anything over 4.2.1 ROMS. CM10.1 no workie.

Do me a favor. Do a full nandroid backup.

Wipe data / Factory reset
Flash CM 10.1
Boot
Flash my patch
Boot
Check it and update me.

Then restore to your nandroid
Click to expand...

I tried it. No workie. :( Thanks for your work though!

Now I just have to figure out why Epic's Root from Recovery doesn't seem to be working for me. No errors. I'll have to borrow a Windows box again to see if ODIN can help.
 
rickyx32 said:
CM 10.0.0 is a no go for me I'm just stuck on the S3 splash screen.

I got it from this link CyanogenMod Downloads from the Sprint http://androidforums.com/sprint-cricket-galaxy-s3-all-things-root/624450-rom-list.html Should we just go down the list, are there things to look out for?
Click to expand...

Ive only been able to get 4.2.1 ROMs to work on our phones - 4.2.2 = nogo / 4.1.x = nogo

Download the ROM:

I went to your link and downloaded "cm-10.1.0-d2spr.zip "

After downloading I need to check what version it is. So I right click and extract the ROM in place.

Double clicked: cm-10.1.0-d2spr then system

Inside the system folder is a file called build.prop. Open this file with a text editor. I suggest Notepad++

Look for the version number toward the top:

Code: 
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39E
ro.build.display.id=cm_d2spr-userdebug 4.2.2 JDQ39E eng.jenkins.20130624.150955 test-keys
ro.build.version.incremental=eng.jenkins.20130624.150955
ro.build.version.sdk=17
ro.build.version.codename=REL
[B][SIZE="4"]ro.build.version.release=4.2.2[/SIZE][/B]
ro.build.date=Mon Jun 24 15:10:45 PDT 2013

This is a 4.2.2 ROM. It will not work (at least with the newer GS3's)

Top left of the CM page I clicked "ALL" - this shows all SPR builds

I downloaded "cm-10.1.0-RC3-d2spr.zip " and the one below it called "cm-10.1-20130411-EXPERIMENTAL-d2spr-M3.zip ". Extracted both and checked the ro.build.version line

cm-10.1.0-RC3-d2spr = 4.2.2 = nogo

cm-10.1-20130411-EXPERIMENTAL-d2spr-M3 = 4.2.2 = nogo

cm-10.1-20130304-EXPERIMENTAL-d2spr-M2 = 4.2.2 = nogo

cm-10.1-20130121-EXPERIMENTAL-d2spr-M1 = 4.2.1 = WINNNAR

Most ROMs jumped from 4.2.1 to 4.2.2 very quickly so finding a 4.2.1 ROM is difficult. Since I cant find my Slim ROM that is 4.2.1 from his site Ill post it in OP too (camera borked)
 
It looks to me like your MOD fixes MMS only on 4.2.2. I tested a 4.2.2 version of cyanogen mod with this and MMS was broken before the flash. After the flash it worked.
 
comndrcody said:
I tried it. No workie. :( Thanks for your work though!

Now I just have to figure out why Epic's Root from Recovery doesn't seem to be working for me. No errors. I'll have to borrow a Windows box again to see if ODIN can help.
Click to expand...

Can you make a backup and try something else for me please?

Flash my MOD again but also flash the CM10.2 KT747 kernel:

http://forum.xda-developers.com/showthread.php?t=1800576
(For CM10.2 its the "AOSP JELLYBEAN 4.3 Linux 3.4 VERSIONS:" kernel)

I think my mod may need to be paired with the KT747 kernel.
 
This maybe already posted but this is what I discovered that in order to get MMS to work on 4.3 or 4.2.2 roms. I manually added the apns I used Sliding Messaging I'm sure that GO SMS Pro will work as well. The thing is my phone isn't a Virgin Mobile S3 it's a Sprint one flashed to Virgin Mobile so I can't test 4G LTE. I have also tired using this mod on MOAR rom using a sprint kernel but I could only send mms couldn't receive it. Flashed it on Avatar rom 4.2.2 for Sprint S3 with no build.prop changes and mms doesn't work but if I edit build.prop and use sliding messaging and going to system messaging app and disable mms auto receive and enable it in Sliding messaging.
Build prop changes:
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha= Virgin Mobile
Sliding Messaging mms config:
MMSC Url: http://mmsc.vmbol.com:8080/mms?type=null
MMS Proxy: 205.239.233.136
MMS Port: 81
Click to expand...
 
Did you say it "not working for newer gs3"? I remember one of post that I had to flash 4.2.2 but somewhere on Rom: cm10.1 forum
 
ok so 4g has been tested and working on sprint based roms using this patch? because if so i may have a solution for aosp based roms

youll need to remove specification of the virgin network in the buildprop first off, aosp doesnt like that, might be able to leave it out and just have it tower selected but i would say a safer bet is setting it to sprint 310120

also, i noticed youre using a larger apn than me and you have pamsn and n.ispsn which are sprint where as boost uses boost.pamsn and n.boost.ispsn so you might wanna check a backup of a stock apn pulled with an apn backup utility to verify accuracy. make sure to pull it from stock rom tho. and you will also want to check the duplicate lines and such but this should be the apn necessary for lte...

http://unleashedprepaids.com/upload/devs/junkie2100/apns-conf.xml

to install put it in /system/etc/ overwriting the old one then factory reset in cwm or twrp or clear the apn database using a 3rd party app. or you can manually replace the apns-conf.xml in the zip provided in the op using just about any archive manager and just install it as normal
 
EDIT: Reflashed MOAR ROM and the patch and everything seems to be working fine now, but MMS. I can send MMS fine but I can't download it. Keeps saying download failed.
 
Boot time is slow, if you first install it. Apn isn't working don't have any data if wifi is off. Wifi works though, at least keyboard is nice theme but it be slow for the first. Mms is able to work might get some bugs on the UI
Does anyone have md4 modem punk file non hlos.bin already installed because I have issue with that part putting virgin modem to md4. Want to try out cm10.1 :/
 
junkie2100 said:
ok so 4g has been tested and working on sprint based roms using this patch? because if so i may have a solution for aosp based roms

youll need to remove specification of the virgin network in the buildprop first off, aosp doesnt like that, might be able to leave it out and just have it tower selected but i would say a safer bet is setting it to sprint 310120

also, i noticed youre using a larger apn than me and you have pamsn and n.ispsn which are sprint where as boost uses boost.pamsn and n.boost.ispsn so you might wanna check a backup of a stock apn pulled with an apn backup utility to verify accuracy. make sure to pull it from stock rom tho. and you will also want to check the duplicate lines and such but this should be the apn necessary for lte...

http://unleashedprepaids.com/upload/devs/junkie2100/apns-conf.xml

to install put it in /system/etc/ overwriting the old one then factory reset in cwm or twrp or clear the apn database using a 3rd party app. or you can manually replace the apns-conf.xml in the zip provided in the op using just about any archive manager and just install it as normal
Click to expand...
the apns uses were copied with an apn backup utility on a stock tw rom. the apn is larger due to adding some info but ill pull a pure stock apn for comparison...

Stock apn https://www.dropbox.com/s/u7af2ufiposq7gy/apns-20130918124518.xml
 
junkie2100 said:
ok so 4g has been tested and working on sprint based roms using this patch? because if so i may have a solution for aosp based roms

youll need to remove specification of the virgin network in the buildprop first off, aosp doesnt like that, might be able to leave it out and just have it tower selected but i would say a safer bet is setting it to sprint 310120

also, i noticed youre using a larger apn than me and you have pamsn and n.ispsn which are sprint where as boost uses boost.pamsn and n.boost.ispsn so you might wanna check a backup of a stock apn pulled with an apn backup utility to verify accuracy. make sure to pull it from stock rom tho. and you will also want to check the duplicate lines and such but this should be the apn necessary for lte...

http://unleashedprepaids.com/upload/devs/junkie2100/apns-conf.xml

to install put it in /system/etc/ overwriting the old one then factory reset in cwm or twrp or clear the apn database using a 3rd party app. or you can manually replace the apns-conf.xml in the zip provided in the op using just about any archive manager and just install it as normal
Click to expand...

" i noticed youre using a larger apn than me and you have pamsn and n.ispsn which are sprint where as boost uses boost.pamsn and n.boost.ispsn so you might wanna check a backup of a stock apn pulled with an apn backup utility to verify accuracy."
Click to expand...

I saw that too. Ive looked at as many Virgin apns settings and found just about all as pamsn and n.ispsn. Ill try "n.vmu.ispsn" based on Lordmage.

Based off the apns-conf.xml you posted you changed the mnc="120" but in most Virgin mobile setting Ive seen its been mcc="311" mnc="490". That why I kept it to 311 and 490

Here is an entry pulled from a Stock Virgin Mobile Phone:
Code: 
    <apn carrier="EHRPD - Virgin OTA"
        mcc="311"
        mnc="490"
        apn="otasn"
        type="fota"
        protocol="IPV4V6"
        roaming_protocol="IPV4V6"
        bearer="13"
    />

Here is a Stock apns

I did find some things that need changing and Ill try to test the next version.
 
junkie2100 said:
ll need to remove specification of the virgin network in the buildprop first off, aosp doesnt like that, might be able to leave it out and just have it tower selected but i would say a safer bet is setting it to sprint 310120
Click to expand...

Can you explain this more please? Am I to remove all ro.cdma.home.* setting all together from the build.prop? The script file in the fix flash changes the Virgin settings to the Sprint if it's in there. The only place "Virgin Mobile" will be really is in a Virgin Mobile ROM. Since we download Sprint CM/AOSP ROMs Virgin Mobile is not there.

junkie2100 said:
oh yea and dont forget dwfault network mode 9. sounds wrong even to me, should be 8 but on the force its 9
Click to expand...

Yea I don't get that either. Ill edit my script to change it to 9 is there. CM/AOSP are the only ones that seem to have the network entry.
 
You must log in or register to reply here.
Back
Top Bottom