I recently bought an Alltel Touch Pro from alltel.com for CHEAP. Now the merger with Verizon and the peeps in the vzw store and on the 800# said my phone in not compatible and told me to buy another one.
I need new phones for the other lines on the plan but not willing to pay $350 for another Touch Pro when i already have the same phone.
I unlocked my Touch Pro and am running NFSFAN's rom (presumably compatible for any carrier). WHAT GIVES!
Please Help!
Are there any options beside Sprint or start all over and go AT&T (which i dont want to do)
if you're interested
I do have a vzw touch pro for trade if you want...I'd like to take that alltel touch pro
that's one other option
PM me or let's chat on msn a bit or whichever IM client you have
RE: Phone Trade
Thanks man but my point is, I dont want to get rid of the phone, I just want it to work!
Any one else have this problem?
The alltel phone should work they are lying to you. I have a sprint phone and it works. Did you try to set up all the epst settings first? You have to update the MSID, MDN, and something else but i cant remember right now. If you do a search you will be able to find it. Then flash update the pri, that way you dont get that annoying roaming triangle. After that just get them to add the ESN to there network and it will work.
Start at step 2 and then skip to step 9 and continue.
Getting your sprint phone on a vzw network
What you will need
you will need
* QPST (google this - seriously, because chances of you finding it here are slim)
* Baffles MSL Grabber (you can find it here: http://www.baf.cc/bafmsl you will need .net framework 3.5 installed on your phone)
* An unlocked Sprint Touch Pro (Raphael Unlocker here http://forum.ppcgeeks.com/showthread.php?t=42503)
* VZW leaked rom (that you can find here : ftp://ppcgeeks.com/Raphael/Stock R...51064_Ship.exe)
* The most current vzw PRL (Again you can find that here : http://www.corolada.com/prl/verizon/51056.prl)
* DMU Keys (Find that here : http://forum.ppcgeeks.com/attachment...2&d=1205773368)
* HTC modem drivers http://www.cinconet.org/gpsfix/WMode...rInstaller.exe
Step One
You can perform this step on your phone. Install Baffles MSL Grabber and write your MSL. My suggestion is to open up a text document and type it there because it will be necessary later on.
Step Two
Unlock your device using the Raphael team elite unlocker for sprint. I used the second link (I believe .37).
Step Three
Install the htc modem drivers on your computer (that's kind of important)
Step Four
Install QPST on your computer
Step Five
If you completed all the preliminary steps, you should be ready to fully begin. At this point, you can perform the steps on the vzw leaked rom or on your sprint touch pro rom. If you are performing this on the sprint touch pro rom, you will need DCD carriers cab. On the vzw rom, however, I have noted that MMS does work on the phone (and you know how much we love our mms). I think this is solely up to you whether or not you use either rom for operation. Remember though, if you are doing this on a sprint rom
DMR mode for sprint is
##3424#
Whereas DMR for vzw is
##3424 and press the send key (send key is below the home hardware button - you can also use the send key on the phone)
Also EPST for sprint is
##778#
whereas this for a vzw phone is
##778 and hit the send key
So how you will work is solely up to you
What you would need to do next is place your phone in DMR mode. Connect your phone to your computer via usb mode. If everything worked okay, the popup for drivers shouldn't come up at all. Start QPST config and select ports
Step Six
Now, in QPST, your phone should come up. If it doesn't, right click on my computer and select properties. Click hardware and then device manager. Click view and device by connection. Click on your USB controllers and don't stop until you see HTC. Notice the com port that the HTC device is on (mine on two different computers, running xp or vista was COM5, yours may be different). Take a note of this and return to QPST config. Now, click add COM port, and add the port you saw in the device manager. QPST will pick up the phone.
Step Seven
Now, click on services and go to services programming. Select your phone and begin. This will ask for your MSL. Type it in and continue. Click read from phone. You may have to retype that MSL code, if not good. but on some cases, it asked me for my MSL code twice (unfortunately) so I typed it in twice. The point of it all is this - to get the data from your phone to QPST
Step Eight - changing your MSL
Now that you are in QPST Service programming, you can change your MSL unlock code. Please change it to 000000. That is vzw's MSL code, and it is so easy to remember for later on. Once this is done, click write to phone. I caution, do not close out of QPST service programming until this is done! You will know when this is done if you can see that the buttons read from phone, write to phone, are not grayed out.
Step Nine (optional)
Okay so at this point, I installed the leaked vzw rom but it is not necessary to perform this step at all. Its just something I did to make things a lot easier on me. Individual results can vary though.
Step Ten
Now, its time to change our MIP settings. Go into EPST and select your MIP profile. On your phone you can edit the information to match the following:
MIP Profile
Number of profiles: 6
Active user profile index: 0
MIP_MODE: Mobile IP Prefered
MIP Reg Retries: 2
MIP Reg Retry: 1750 ms
MIP Pre-Reg Timeout: 0
Mobile Node-HA: Enable
Send A Reg: Disable
Dormant Handoff Opt: Enable
Step Eleven
Now in EPST, go to MIP default profile and edit the information on your phone to match these settings:
MIP Default Profile
Enable Profile: Enable
NAI: [email protected] ([email protected])
DUN NAI: (if entry is there enter [email protected] so you can tether without a tethering package or [email protected] if you want paid tethering))
MN HA SPI Set: Enable
MN HA SPI Value: 12C
MN AAA SPI Set: Enable
MN AAA SPI Value: 0 (requires a "2" here for 6800 and 6900)
Reverse Tunneling: Enable
Home Address: 0.0.0.0
HA Shared Secret: (erase whatever entry is here leave blank)
AAA Shared Secret: (erase whatever entry is here leave blank)
Primary HA Address: 255.255.255.255
Secondary HA Address: 255.255.255.255
DMU Pub Key: 10
MN Authenticator: 0
It is very important to erase the HA and AAA shared keys. We will return back to them momentarily
Step Eleven
Complete changes from EPST and the device will soft reset. Now place your phone in diag mode. Connect your phone to your computer and enter QPST EFS explorer. Unzip the DMU keys and notice you will see the file on your hard drive. In EFS explorer, you will see the DMU folder. Right click on the folder and you will be able to insert a DMU key via the file explorer on your computer. Select the DMU key file and press okay. The information will be written to the phone.
Step Twelve
Drag your PRL file you downloaded from your computer to your cell phone memory. Dial ##PRL and hit send if you are on vzw rom, if not ##PRL# if you are still on the sprint rom. This will lead to a dialog box on your phone that will allow you to locate the PRL file you loaded onto your phone. Make sure the PRL is in a directory where you can access it when you browse for it on your phone.
Step Thirteen
Place your phone back in diag mode. Connect to QPST service programming and go to the MIP default profile (AAA shared secret and HA shared secret is where you need to go in Service programming). If there is anything in those two areas, delete it, click enter hex values and leave it blank. Write to phone.
Step Fourteen
If you are still on a sprint phone, install DCD vzw carrier cab. If not, please dial *228. The menu has changed, so you will have to hear EVERY option before selecting. You will enter option number 3. Go through the prompts on vzw's end and the phone will program and soft reset.
Step Fifteen
Once your phone has soft reset, you're almost done! You should have text messaging and voice, but data not yet. So to get data, you have some options. If you can't get data to authenticate, follow step thirteen. Then force the phone into 1x mode (I don't care how you do it - what I did was go to a mall basement) and connect to the internet in 1x mode. EvDO won't work, but 1x does work. What is going to happen is the HA and AAA shared keys will be written. If all goes well, you should have your sprint touch pro phone 99.9% working on vzw network.
Now, the roaming triangle will stay there, I'm still working on how to remove that. But it will work everyday. Enjoy your new phone =)
Special thanks to Nex, Baffles, drellisdee, and KilgoreBA for the help. I haven't started my hand at a vzw rom, but I will eventually...
Any questions?
all original tutorial above was found here:
http://forum.ppcgeeks.com/showthread.php?t=44663
at this thread http://forum.ppcgeeks.com/showthread.php?t=75164&page=2
people have got their Alltel TP on the VZW network without having to go through the abouve steps
Solution! (I think)
Thanks for the posts. So, from what I gather all I need to do is spend an entire day on the phone to speak to someone with the authority and the will to add my esn to the database.
Now thats quality guest service!
if you quote the CSA to them after they said it can't be done then it shouldn't take all day. I would look at it as you just made them do something that they said they won't do, and at least you don't have to buy their crappy version of the phone. just one more way of sticking it to them.
I work at Verizon and I've seen this problem numerous times since the merger. Here's how it works:
Legacy Alltel customers will remain on their Alltel plans until they decide to switch over to a Verizon plan. Even when your Alltel plan is up for renewal, you can still renew it and remain on your Alltel plan. So in all honesty, the only thing that's Verizon about legacy Alltel customers is the letterhead on your most recent bill.
Another note, Verizon phones work on Alltel plans but Alltel phones will not work on Verizon plans. Even now, legacy Alltel customers that have made the switch over to Verizon plans and phones are having trouble with their service. We CSR's aren't sure why but it's happening. If it were a smartphone on an Alltel plan then it's your Alltel's plan and VZW's add on. This goes for all addons: texting, data, smartphone plans, etc. So if you wanted a Storm and wanted to keep your Alltel plan, we would add VZW's smartphone plan on top of your Alltel plan.
So to answer your question to the best of MY knowledge, as long as you're still on an Alltel plan with your Alltel TP, you should be fine, but if you're on a VZW plan with your Alltel phone, it won't work.. at least that's what I've been told through training.
derynhaze said:
I work at Verizon and I've seen this problem numerous times since the merger. Here's how it works:
Legacy Alltel customers will remain on their Alltel plans until they decide to switch over to a Verizon plan. Even when your Alltel plan is up for renewal, you can still renew it and remain on your Alltel plan. So in all honesty, the only thing that's Verizon about legacy Alltel customers is the letterhead on your most recent bill.
Another note, Verizon phones work on Alltel plans but Alltel phones will not work on Verizon plans. Even now, legacy Alltel customers that have made the switch over to Verizon plans and phones are having trouble with their service. We CSR's aren't sure why but it's happening. If it were a smartphone on an Alltel plan then it's your Alltel's plan and VZW's add on. This goes for all addons: texting, data, smartphone plans, etc. So if you wanted a Storm and wanted to keep your Alltel plan, we would add VZW's smartphone plan on top of your Alltel plan.
So to answer your question to the best of MY knowledge, as long as you're still on an Alltel plan with your Alltel TP, you should be fine, but if you're on a VZW plan with your Alltel phone, it won't work.. at least that's what I've been told through training.
Click to expand...
Click to collapse
so you are saying that everyone on verizon wireless can drop their service without a termination fee because the CSA clearly states that customers can use any CDMA phone on the network as long as it is compatible. here is a quote from the CSA
"Your wireless phone is any device you use to receive our wireless voice or data service. It must comply with Federal Communications Commission regulations and be compatible with our network and your Plan. Whether you buy your wireless phone from us or someone else is entirely your choice. At times we may change your wireless phone's software, applications or programming remotely and without notice. This could affect data you've stored on, the way you've programmed or the way you use your wireless phone. If you purchased a wireless phone (other than a "global phone") from Verizon Wireless for use with a plan with a minimum term and want to reprogram your phone for use with another wireless carrier network, the default service programming code is set to "000000" or "123456." Verizon Wireless in no way guarantees that your Verizon Wireless phone will be capable of being reprogrammed for use with another wireless carrier network after the service programming code is entered, or that another wireless carrier will accept your device for use on its network"
people here had the same problem but got verizon to add the phone http://forum.ppcgeeks.com/showthread.php?t=75164&page=2
It DOES Work!
Whoever said that it doesnt isnt telling you the truth. I have an Alltel Touch Pro and when Verizon bought alltel, I didnt have to do anything to my phone to have it work on Verizon. The only phones that dont work are a few very old phones on alltel because their technology is old
I agree it does work
I also had have a TP that was with Alltel and when the migration to VZW was completed it still worked. Now, what does suck, the PRL I have for VZW using my Alltel phone is different from the PRL that a VZW phone is using. I was informed this is due to my Alltel rate plan. All I can tell you is my signal bar in some areas where I had great service now is sub-par with signal strength.
The other thing I did was go ahead and flash my TP to NFSFANs ROM build, and it is a world of difference.
From what I've read, folks with Alltel TP's on Alltel Plans are being transferred almost seamlessly to the Verizon network. However, what I'm planning on doing is purchasing an Alltel TP to put on my existing VZW plan. After I flash the ROM to a VZW compatible one, does anyone know if I'll be able to just activate and go on my merry way or will I run into problems where I have to call up VZW customer support and get them to add my new ESN to their database?
Hate to say it...
I've had zero luck getting an Alltel Touch Pro activated with Verizon, post programming ala the old Sprint to Verizon guide. I hope you have better luck!
TGabriele said:
From what I've read, folks with Alltel TP's on Alltel Plans are being transferred almost seamlessly to the Verizon network. However, what I'm planning on doing is purchasing an Alltel TP to put on my existing VZW plan. After I flash the ROM to a VZW compatible one, does anyone know if I'll be able to just activate and go on my merry way or will I run into problems where I have to call up VZW customer support and get them to add my new ESN to their database?
Click to expand...
Click to collapse
SUCCESS... well almost...
I've received my Alltel TP yesterday and followed the tutorial at ppcgeeks (the one that shows you how to convert a Sprint TP to VZW). I then proceeded to talk to VZW Customer Service and they told me it was incompatible as I expected even after quoting them the CSA. I asked them to transfer my to tech support. I mentioned to them the trouble I was having and that I had read that it could be as simple as submitting a form to add the phone to the VZW database and asked it that was true. He confirmed that it was true, however, it would take 2-3 business days to complete the process after we submitted the form. So that's where I'm at now, waiting in anticipation! I set up an appointment for him to call me back this Wednesday to help me activate the phone. I will post back then to let you guys in on the rest of the story!
My advice thus far, save yourself the aggravation and skip CS and ask to be transferred to tech support. They are much nicer and more helpful over there about this subject.
what is the update here?
Interested in seeing a reply for this as well.
I currently have an Alltel TP and have sort of the same predicament. One of my lines is eligible for upgrade and wants to get a Droid. I have been told I could upgrade all phones and swap to a VZW plan, but would end up paying about 40$ more because of their DATA add on.
Fortunately I am on an Alltel plan and you can add Verizon smartphones to the alltel plan and only a couple of codes will change, but you stay on your plan - no cost difference.
But if I were to switch to a VZW plan or if you were on a VZW plan, you would lose your TP because of incompatibility which I know i'm not ready to throw out yet.
Update date Radio and PRL
Update the touch pro Radio to the Verizon 1.03.09v
Update the PRL, dial *228, then 2
periodically I also do a program update, *228, then 1
just in case they changed something.
Hi.
I just purchased an CDMA alltel touch pro phone from the states, and I wanted to get it to work on the bell network. The phone is unlocked and has the EnergyROM 'Aurora' (quoting from device information on the phone), rom date is 08/09/09. It was sold to me with this ROM on it.
There was a few ring tones and such on the phone, so as soon as I turned it on, I did a hard reset so that it would be a clean slate.
I then phoned bell tech support, they say to go into a bell store to activate it. I phone my local bell store and the guy was nice enough to try activating it over the phone. I gave him me MEID number, but he wanted me to type in a 'unlock code' and was also saying something about the serial number not being able to be registered.
I phoned back the bell tech support, spoke to a tech, and he said that the software on the phone might not be compatible with the bell network.
This phone, even after the hard reset, thinks it has an Idaho phone number. When I dial any number from the phone, I get a generic bell network message ('welcome to bell mobility, call this number to get help')
My questions are: Does it matter what ROM I use for the bell network?
What is the unlock code/ where can I find it for this phone?
And lastly, if the serial number (I assume by serial he meant MEID) cant 'take' on the network, am I screwed?
I believe the unlock code you are asking about is 000000
I would try flashing the phone NFSFAN's Rom, It is supposedly carrier free meaning it will work with all carriers.
One thing I have noticed though is that if you use any codes, like ##778, which is normal on a alltel phone, you have to do a ##778# if you are using NFSFANS Rom. Noting the trailing "#" which is like pressing the send key.
About the ESN not registering I do not know about this, maybe someone with more expierence can help.
Hope this is accurate and I hope it helps
Thank you for that unlock code! I phoned bell again and gave them the MEID, and they said that in his computer system, he had to specify what type of device the MEID was for. He tried all 5 and none of them would work. He then gave me a number for bell tech support, saying that I should ask them if they can 'force' the MEID onto the bell network.
ok put in the MEID with the tech support and they say it's an analog phone according to thier database. because they no longer support analog phones, it cant be activated. W-T-EFFING-F. its a touch pro phone! how is that possible??. What Should I do???
I did a quick google search and perhaps this thread can help you, if you have another "Bell" phone.
http://www.mobile-files.com/forum/showthread.php?t=111584&page=7
i personally did this follwing that exact same tutorial and its working 100% with my sprint tp on bell network !!!
I've been trying to read the MSL from a Verizon HTC Eris.
I followed all the directions here (http://forum.xda-developers.com/showthread.php?t=697487 ), but it gave me the same error as midnigh7 got, and restarting the phone didn't work. When I checked the box nearby, it did give me a 4 digit code.
So I tried using MSL reader, and that also failed.
I then tried putting in the terminal commands mentioned, and there was no entry containing "MSL"
I then recalled reading that verizon sometimes has all 0's.
So I 'called' ##PROGRAM# , and when it asked for a password, the previously mentioned 4 digit code was not correct, but 000000 was.
Is my MSL 000000 ?
Verizon apparently uses 000000 as a universal MSL for their devices.
SPC/MSL: Service Programing Code/Master Subsidy Lock- This is a 6 digit code used keep the average phone user from programing the phone. Some providers have codes that are specific to each phone based off of the ESN e.i. Sprint, USSC. Other providers use a universal code e.i. Verizon uses 000000, Cricket uses 333333.
Click to expand...
Click to collapse
Yes that's right all Verizon MSL codes are 000000
MongooseHelix said:
Verizon apparently uses 000000 as a universal MSL for their devices.
Click to expand...
Click to collapse
Mongoose, What does unlocking MSL allow one to do? What are the risks involved?
Thanks,
phone_cell said:
Mongoose, What does unlocking MSL allow one to do? What are the risks involved?
Click to expand...
Click to collapse
From my understanding, the MSL is a password of sorts needed to perform certain dialer code actions and such. I've never had occasion to do anything where I needed to use the MSL so I can't really say what all people use it for. I think one thing some Sprint customers use it for is to modify their phone to roam on Verizon.
I was provided a subsidy unlock code for my Atrix 4G (4.5.91.MB860.ATT.en.US, Android 2.3.4) by AT&T today. However, when I enter the code I get the message "Network unlock request unsuccessful." I called AT&T back to verify I had the correct code and double-checked that I was being given the code for my IMEI. Three people have now provided me the same unlock code, which results in the above error message. AT&T tech support sent me to Moto and Moto told me they have nothing to do with the subsidy codes as they are programmed by the carrier and that I need to go back to AT&T.
So, now I'm stuck in the middle with both companies pointing at the other. This is a really annoying situation to be in. Anyone have any suggestions as to how I can extricate myself from this situation?
P.S.: I've unlocked my Atrix 2 and Atrix HD w/o issues, both with codes from AT&T. I've also unlocked a Motorola RAZR V3. This last was interesting as I was given two different codes in two different emails spaced three days apart. I used the code from the most recent email and it unlocked the phone.
Bump
Come on....No one has any input or ideas?
Waaaaaaah! Nobody loves me....
Don't be surprised at the lack of responses. Unlock codes are a largely unknown territory. Mostly they either work or they don't. I for one have no idea what to make of that error message. I do however agree this most likely has nothing to do with Motorola, AT&T will have to solve this somehow.
Fixed!
While I was away on travel AT&T sent me a new subsidy unlock code for my Atrix 4G, and it is completely different than I was originally given. WTF? Anyway, it worked. No explanation, just a new set of email one giving me the code and the second stating that the case was closed.
Once I get home, with trepidation, I tried the new code, which didn't work. I had already anticipated this as AT&T had me enter my original unlock code several times even though I was told there was a limit of five tries before it was 'permanently' locked to AT&T's network. Hoping that the failure to unlock with the new code was due to the excessive attempts I followed the instructions I found on this http://www.amilkhanzada.com/2012/03/how-to-unlock-permanently-network.html web page to 'clear the unlock attempt count.' The instructions entail flashing your Atrix with radio firmware for Brazilian Atrixes (Atrixs Atrices?). The instructions worked as published except for step 17 detailing the entrance of the unlock code; the instructions state to type "#73887*" to open up the "SIM network unlock PIN" prompt, but this didn't work for me. To enter the unlock code I had to put a T-Mobile SIM into the phone. Once I did this I was able to successfully remove the subsidy lock on my phone.
I really don't know what the issue was; it certainly wasn't because of an incorrect IMEI as we checked that a million times. In any case, I got "Network subsidy unlock successful" and I am able to connect to the T-Mobile network as I get "T-Mobile" in the upper-left corner and an H+ icon along with four bars in the upper-right corner, so I'm happy.
So did you use the new or old code after resetting the counter?
Bump for later use.
I have an HTC Evo 3D phone. It is for Virgin Mobile. I had it attached to my phone number last year and it worked fine. I upgraded my phone and just had the HTC laying around. My son accidentally broke his phone and I gave the HTC to him. I activated it online and everything went fine. I turned on the HTC and it would not connect. It tries to activate but it is not connecting to the Virgin Mobile network. I have network on and WiFi off. I have tried it with WiFi on and neither is working. I tried resetting the phone. I tried factory resetting and taking the battery out. I tried updating Profile and PRN - not connecting to the Virgin Mobile network.
Have made a total of 4 calls to Virgin Mobile.
Call #1
Your phone is too old and it wont connect to our towers. Get a new phone.
Call #2
Use ##VIRGIN# - that doesnt work? Oh well get a new phone.
Call#3
Needs to be programmed - This one actually tried a few things before he told me I had to go to a Sprint store to get the MSL code so that I could program the MSID and MDN into the phone manually.
Call #4
Retrieved the MSL code *By the way - virgin mobile phones need to be on the virgin mobile network for over 10 months for them to give out the MSL code.
Tried ##(mslcode)# - did not enter into the edit mode - did nothing.
At this point he stated that I needed to upgrade my phone.
Tried ##3282# - was able to edit MSID # but not the MDN number (which is the phone number).
So my questions are - why is it not connecting to the network?
How to change the MDN number?
Anything else? Please?
entrailnu said:
...
So my questions are - why is it not connecting to the network?
How to change the MDN number?
Anything else? Please?
Click to expand...
Click to collapse
//edited to put the solution first and diatribe after.
HAHA!
since the log gave the the expiration date of the stale CA certificate, I turned off automatic time/date and set the date to April 29, 2019, right before the cert expired.... and the profile update ran and completed.
same for the PRL update, but the profile update corrected the time and I had to go back and "fix" it again to run the PRL update.
I'll have to try the date reversion gimmick on the Optimus V for fun later.
Just a heads-up, most HTTPS is going to have issues from the stale certificates. If you figure out which ones have gone south (settings>security>trusted credentials) you might be able to import new ones (settings>security>install from SD card)
but I have yet to find a current version of the Sprint branded CA cert anywhere, and somewhere around a third of the certs installed on the 3vo are expired.
Maybe good ones could be pulled from a newer ROM on some up-to-date Sprint HTC device. Since I'm not worried about using the stock rom on my 3vo I will likely not go to the trouble of fishing for current CA certs.
If it works for anyone else, great. I'm going to harass Sprint mercilessly about this one.
If it wasn't such a fight to get to tier 2 (or higher) tech support even WITH a sprint account, maybe I'd have been able to talk to someone who had a clue. Virgin tech support is no better... I feel I know that pretty well, considering that over the years since 2007 I have been such a ridiculous pain in the behind to both companies with overly deep technical issues that I once had direct phone numbers for tier 3 Sprint and tier 2 Virgin support, which they have of course since disconnected.
original reply follows:
I know this is stale, but, for anyone interested:
to edit MDN/MSID on a Sprint 3vo
##(your six digit MSL/SPC number)# in the dialer
this was on a fully updated sprint 3vo, on ICS.
it's weird yours wouldn't edit. will it view the numbers in that menu? You can also see them without editing in ##RTN# and ##SCRTN# menus, they both require the MSL to access.
##VIRGIN# was the way to edit MDN and MSID on my Virgin Optimus V. I'll have to burn a Virgin 3vo back to stock to verify if it's the same. Will do that at some point.
Since my most recent $7 3vo is a used sprint phone and I have no sprint account, sprint flat refused to give me the MSL, and I had to root the phone and use MSL reader from play store to get it. Even finding stale crusty downloads of everything I needed, it was still faster rooting and getting the MSL myself than all the time I wasted with Sprint between phone calls and the corporate store today.
f*** sprint.
the 3vo activation apps, including both virgin and the sprint one and the buried pieces of them in settings>system updates, are now broken due to expired root CA certificates, as far as I can tell from the system logs.
E/vDM ( 7403): VdmRawConnection#open: IOException: com.android.org.bouncycastle.jce.exception.ExtCertPathValidatorException: Could not validate certificate: current time: Sun Aug 23 22:48:30 CDT 2020, expiration time: Tue Apr 30 13:24:45 CDT 2019
I managed to get voice/text working on Hello Mobile (sprint MVNO) by setting the MDN(phone number) and MSID (looks like a phone number but is different than the actual phone number(MDN.))
But I have no data service whatsoever, and have not yet puzzled out why. It is still day 1 of hacking at this phone again, I guess.
It was like pulling teeth and took around a half hour to explain roughly what the MSID is and why it was needed to the tier 1 hello mobile rep before they eventually went through a manager or two and coughed up the information. I actually got that for testing a Virgin Mobile LG Optimus V.... again, voice/text/no data. Rather than fight through another call with them I reverted the V to aphrodite (stock mod) to get the MSID from ##RTN# menu to force it into the 3vo.
the activation tool does connect to data during its failed run, you can see it in logcat, but I haven't found a working APN for hello mobile yet or any other info to get data up and running.
//end of the beginning
Perhaps I'll post a "guide" of sorts later. But, I'm pretty lazy, and people don't usually like my crowded overly verbose text formatting anyway.
So to update my last post...
I dug up my Virgin 3vo, put it on my hello mobile account which works with my Sprint 3vo, and the VM version refuses to activate, even with the time/date set to 2018 before the SSL certs expired.
As far as I can tell from the logs, activation on the Virgin model is trying to run over 1xRTT (2G towers.) Those, as far as I know, have been obsoleted on Sprint service and will no longer connect.
The exact same thing happens on my Virgin Mobile LG Optimus V.
The Sprint 3vo has newer firmware than HTC ever released for the Virgin model, and runs activation over the 3G towers, which works.
I'm sorry to say that the older Virgin Mobile devices look to be dead ducks for activating data service unless they were already activated on a specific account.
My somewhat newer Virgin HTC Desire 816 (A5) also refuses to provision services with a different error, but it has hardware issues with the SIM slot which may be preventing activation from running properly.
You can still use ##(your MSL code)# to program the MDN/MSID manually for voice/sms service, but for data, I have never gone deep enough into debugging to see how the stock ROM obtains the new profile information and sets it in the NVRAM. It'd require some serious reverse engineering to figure that out.