Galaxy Nexus working in Ting (Brio donor)

Hi everyone, I just wanted to report on my findings porting the Galaxy Nexus (sprint version) over to Ting. So far I have talk, text, and at least 1x data working, using the Brio as a Donor phone. I can't say whether 3G data is working or not since I'm out in the middle of nowhere and can only get 1x out here--at least I'm fairly sure. I'm getting speeds of around 200-300 Kbps right now. That being said, I'm waiting to worry about data speeds until I'm in a location where I can properly test for 3G access.

Step 1: Install Brio drivers from  here.

Step 2: Install QPST from  here.

Step 3: Using your MSL code obtained from Ting, or using the method detailed in this thread, obtain your MEID and related information.

Step 4:  The steps in  this thread for modifying the data on the GNex are reproduced below with some of my own insights. Please note that your GNex should be unlocked **and **rooted, and a backup made before proceeding on onto the next steps. I take no responsibility if your device stops working, explodes, or starts talking like Sean Connery.

Step 5: Install the drivers contained in this package. If you are running a 64 bit system, you will not be able to install the VIA drivers inside--don't worry, it shouldn't affect getting your device working (at least for talk, text, and 1x).

Step 6: Prepare your phone. Dial *#*#DIAG#*#*  on your Nexus and set USB to "CDMA MODEM," _then dial *#*#DATA#*#* and select _Edit > Enter MSL > Others/More > ETS Channel and set it to USB. Please Note: These instructions are for the Sprint version only, and I cannot say whether the same commands and steps work on the Verizon version. Please refer to XDA Dev forums thread for more details on the Verizon version. ALSO: if you've installed the ACS forums version of Jelly Bean developed by Shabby Penguin, setting your USB to CDMA MODEM will not work. I recommend downgrading back to ICS before proceeding.

Step 7: Install ETS from here.  Choose USB as the communication protocol during installation. 

Step 8: Plug in your phone and start ETS. It should display an output like this when you select Debug -> Send Startup Commands. Now you're connected.

Step 9: Select CP -> PS -> Database -> CP Set Mobile ID. Enter your MSL under SPC Code, 7268324842763108 for the security code, set ID Type to MEID, and finally enter your MEID after the "0x" in the text box. Press send, and you should receive a confirmation. Your MEID is now repaired. If you make a mistake entering your code, the MEID stored in the device will be zeroed out, along with your IMEI, so write these down if you think you'll ever want them again.

Step 10:  Select CP -> VAL -> PRI -> NAM -> CP VAL PSW Parm Set Mdn, and enter your MDN in the box labeled Mdn_Digits. Press Send. Your MDN should now be repaired. 

Step 11: Reboot your phone. You should now update your profile information, and make a test call and text to get everything squared away on your device.

Please keep in mind that most of what I wrote here is from memory, and my own exact steps included some experimentation that I've left out for the sake of clarity. If you encounter a problem whilst flashing your phone, I'll do my best to help out, **but it's your responsibility to do research before assaulting your phone.

**Cheers everyone! 

 

P.S.** Please back up your phone before doing things to it!**

P.P.S. If you're looking for a simple and very effective tool for unlocking, rooting, flashing and messing with your Galaxy Nexus, go get the Nexus Root Toolkit. It's pretty fantastic. 

4

Comments

26 comments
  • Have you further investigate the performance of the phone in 3G/4G?  I'm just curious.  I can live with 200-300k download speeds if it means getting a nexus back as my main phone.  I miss it terribly.  It doesn't seem ting is having much luck getting the Nexus and I'd be willing to repeat what you have done and report my findings.

     

    When you say Using MSL code from Ting; I presume you mean I can call Ting and have them give me the code for my Brio?  Do I need to activate the brio before I flash it's information onto the Gnex?

     

    1x speed aside, have you found the phone to functioning flawlessly?  I presume I'm going to need to flash whatever rom I want to use on the phone prior to doing this; basically get the Gnex to the state I want it and then proceed with flashing the brio info onto the Gnex.  Thanks much for posting this, now to find a cheap gnex!

    0
    Comment actions Permalink
  • I might be willing to try this, I've done similar things in the past.  However - what do you mean by "unlocked" for a CDMA phone?  I understand what it means for GSM, but not for CDMA.

    0
    Comment actions Permalink
  • I'd like an update as well.  If this works and 3G is working well I will likely purchase a Galaxy Nexus myself and attempt this.

    0
    Comment actions Permalink
  • I have seen several people request the Galaxy Nexus on this network. It may be a worthy investment for Ting to get a few developer phones and find some of the Ting Army people to help in seeing how well this device adapts to the network.

    0
    Comment actions Permalink
  • I thought there was an issue with the capability of the donor phone being a limiting factor.  Since the Brio shows as a "CDMA2000 1xRTT" phone, I thought you'd be unable to get anything better than that on whatever it's codes were transferred to.  So in order to get 4G or LTE, you'd need one of those phones as a donor.  That is a rather pricey proposition, unless you had a phone that was broken anyway, and not likely to be executed.

    0
    Comment actions Permalink
  • @Sagi, I'm using the GNex as my primary device, and it seems to be working well at the moment. My average download speed when I'm in 3g areas is probably 300kbps. Strangely enough, I've actually gotten upload speeds of up to 600-700kbps. The only problem I've been having is MMS is not sending or receiving right now, but I can't say whether that's because of the Jelly Bean ROM I'm running right now, or something else. I'm having a blast with the phone right now though--posting from it right now! :) 

     

    @Iris, by unlock, I mean sending the unlock code (MSL) via QPST, then reading the data off that you need.

     

    I can't say anything about 4g speeds, unfortunately, since I don't live anywhere near 4g coverage. I am definitely getting both the 1x icon as well as the 3g icon at times though and I seem to be getting close to 3g speeds. More investigation into MMS coming after I get back next week!

    0
    Comment actions Permalink
  • Thanks Joey.  Some clarity please:  Since my Gnex won't be activated on Ting/Sprint, I guess it doesn't matter if the ESN is bad, correct?  Considering we're flashing the network info from the brio to the Gnex,; the Gnex would be reporting itself as the brio (ESN and all) and not as the Gnex with the bad ESN.  I ask because I found a good deal on a gnex in great shape but the ESN is bad.  I've no experience in the matter, so I can't be sure.  Ug, CDMA why were you born.

     

    I don't care about 4g and 300 kps is plenty for my needs.  I'm still considering going back to the tmo 100/unlimited plan but it's rather expansive in comparison to my usage and the tmobile customer support is terrible.  It's a pity Ting isn't allowed to get the Gnex officially.  Given Google's stance on CDMA, I doubt Ting ever will.

    0
    Comment actions Permalink
  • I forgot to ask:  The average 300kps download speed; are you getting that from the speedtest.net app?  Kyocera Brio is suppose to only be able to support 2g (CDMA2000 1xRTT) which tops out at 384 kps I think.  Maybe even less than that, so I would say that is pretty decent if you getting a consistent 300kps in 3g areas.

    0
    Comment actions Permalink
  • Now that I think of it further; why couldn't I flash something like the conquer since I already have on of those on the account?  That way I couldn't have to worry about the reduced speed, if it is even an issue at all.

    0
    Comment actions Permalink
  • Has anyone even tried changing the SIM data on the LTE sim card? I believe its identification is separate from CDMA, so it might not be so simple as just having an LTE-authorized donor phone, even if you find a cheap one.

    0
    Comment actions Permalink
  • Can we get any clarification on the 3g? We seem to have a disagreement of sorts in the Brio thread. :) 

    0
    Comment actions Permalink
  • I think of it as being EVDO. 1x is 1xRTT.

    0
    Comment actions Permalink
  • FYI, I'm not getting any where writing the data to the Gnex.  I've done the steps you indicated but when I reboot, I don't have voice or data.  It seems like you're missing steps.  What about the two profiles 0 and 1?  How did you set those?  Ug, of course it would be the case that because of the VIA chipset I can't use DFS, would have been so much easier.

    0
    Comment actions Permalink
  • Well, that does it for me.  I give up.  I've been at it all night and I don't see what else I can try or triple check.  Sprint Gnex with Donor phone M370 fails.  Note to others, you can only use ETS as noted above due to the VIA chipset drivers.

    0
    Comment actions Permalink
  • @Sagi:  Sorry to hear you give up.  Can you please clarify some things for me?

    Q-1:  The issue is NOT pulling the M370 donor info using ETS.  Correct?

    Q-2:  The issue IS pushing the donor info to the Sprint Google Nexus S?

    Q-3:  I assume that is what "Gnex" means "Sprint Samsung Google Nexus S".  Correct? 

    TIA for your responses. 

    I want to see if I can help and also because I recently used the M370 as a donor for my Sprint Evo 4G.

    I used CDMA Workshop to pull the "soul" from the M370 and push it to the Evo 4G.

    However, I am now planning on moving my wife's phone to Ting.  She has a Sprint Google Nexus S.

    I was planning on using CDMA to do the same as the Evo. . .  and want to see what issues I may hit.

    I will try to plug my wife's Nexus S to CDMA Workshop later today to see if I can read the settings with that software.

    I do not have an M370 donor phone for hers yet.  So, I will not try to write things to it yet.

    0
    Comment actions Permalink
  • @Sagi:

    Ok folks.  My spologies.  GNex is "Galaxy Nexus" which is in BIG letters at the top of this post.

    I realized that AFTER my first cup of coffee this morning.  :-)

    I am still interested in your response to Q-1 and Q-2.

    Thanks! 

    0
    Comment actions Permalink
  • Pulling the info from the M370 via DFS CDMA Tool is really easy.  Pusing it to the Gnex (galaxy nexus) would also be as easy as the nexus s if it weren't for the fact that the Gnex uses a VIA chipset and isn't supported by DFS or anything of the other tools like QPST, etc.  You have to use a tool called ETS and it sucks.  I'd really like to know, exactly, Joey Trishka did to get it working.  I can tell from further attempts and research that he left out a good bit of information.  I'm still trying.  I'm not going to spend anymore time on this past this weekend.  I'm not going to be able to do this without help, perhaps I"m just too dense.  The info in that thread seems to presume previous knowledge, I have none.

     

    You won't have issues using the Nexus S with CDMA workshop or DFS CDMA Tool.  The "Nexus S on Ting" Thread is very helpful, have a look and combine the M370 donor thread with that and you'll be set.    Just be sure you have the donor phone set-up and working as if it were you're main phone (MMS and all that) before you pull info.  I'm glad you'll be able to succeed; it sucks that samsung used such different hardware in the Gnex.  I feel like I'm wasting time messing with this thing any further. 

    0
    Comment actions Permalink
  • Holy shit:  I got voice/text (profile 1) working, I'm gonna cry.  Now I need to understand how to write the 3g data (profile 0).  If I succeed, I'll try to make a clear, one page instruction manual.  My main issue withe the data profile now is getting ETS to write the hex passwords I think.

    0
    Comment actions Permalink
  • @Sagi:  Excellent!  Please keep us posted!

    0
    Comment actions Permalink
  • Voice/Text have nothing to do with profile 0 and profile 1. They are strictly a function of having the correct ESN/MEID, MDN, PRL, etc.

    That said I know it can be a headache, but I'm sure you'll get everything going with some more time and effort! 

    0
    Comment actions Permalink
  • That is clear to me now.   I may not keep up my efforts.  After a day of use with voice/text and mostly wifi coverage I quickly came to realize that I used sprint's visual VM app with enough regularity to miss it.  I'll like go back to using my Ting S2 with my eye on the S3 later.  Hopefully, some one in the XDA thread will have some advice and I will be able to do it; at least for the education.

    0
    Comment actions Permalink
  • Joey Triska:  Using ETS, how did you write the 3G profile so you would get 3G data?  I'm only getting 1x?  Please be specific.  I though I had it, then double checked, everything seems fine.

    0
    Comment actions Permalink
  • I can confirm that the Sprint Galaxy Nexus works fine as a target phone. Talk+text and 3G data is confirmed working. Donor phone was a M370. It was all done through ETS. It's not a terrible application once you get used to it.

    0
    Comment actions Permalink
  • Ryan:  Please tell me what you did to get 3G data working and what download rates you get on 3G.  I got voice/text/data working; the 3G icon would show but the data speeds were only at 1x.

    What did you do in ETS to write the 3G profile?

    Email me at sagiquarion at gmail dot com if that is easier, please.  I'd really like to get this thing working; I feel dumb having not been able to get it myself. 

    0
    Comment actions Permalink
  • Anyone confirm official JB works on this?

    0
    Comment actions Permalink
  • I confirmed it by myself. It works. key of AAA is not a six-letter so a hex one would be the best choice.

    0
    Comment actions Permalink

Please sign in to leave a comment.