HOW TO: Motorola Triumph PRL Swap

[Godbilla]

Does anyone have an alternative way to get the msl code? cdma trial doesn't work with the motorola method. And the link isn't working right now. I also tried calling cs and 3 people couldn't figure out how to find the code or what it even was.

Sent from my MOTWX435KT using Tapatalk

[Zaius42]

I found a strange way of getting my msl since that page was broken. I'm working on a method.

I'm rooted but I don't know if you have to be root or anything.. I'll edit this post when i have something

Edit:

Alright, so this is a quick and dirty for those familiar with adb and can get their triumph working with adb. I'm far too lazy to write out a tutorial on installing adb, obtaining the foxconn usb drivers and using anycut shortcut to put the usb in diag mode (although that itself should set you on the right path)

One thing this method needs to make super easy is grep, which if memory serves is part of busybox and that will require root. However if you are quick enough and know what you are looking for you don't really need it.

1.) Start up adb
(ie: C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell)

2.) From anywhere input:

logcat | grep sec_code

basically the " | grep sec_code" is going to just return any line that has that string in it, so you don't have to sift through a bunch of crap. Beaware that command will probably display nothing yet, but leave it running in the adb shell

3.) From your phone's dialpad input ##DEBUG# or ##33284#

If entered properly your triumph will ask you for the MSL. This is normal, what you want to do is input anything, six zeros, your guess what you think it is for a luck test, whatever.

4.) when you continue on, your running logcat in adb should spit out a single line of stuff, at the end it will have sec_code:XXXXXX that's your MSL.

This is all it looks like for those confused.

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ logcat | grep sec_code
logcat | grep sec_code
V/QC_NV_ITEMS( 1703): sec_code:147268

if you don't have busybox for grep and don't want to root you can just run logcat by itself, and follow the same process and scroll up and read the sec_code: line and jot it down quickly. (trust me once you start up logcat you'll understand)

its just going to look a lot more like this:

D/wpa_supplicant( 1539):  len = 13, 13
D/wpa_supplicant( 1539): RSP:LinkSpeed 52
V/QC_NV_ITEMS( 1703): QcNvItems instance created.
I/QC_RIL_OEM_HOOK( 1703): QcRilOemHook Service Created Successfully
V/QC_NV_ITEMS( 1703): getSecCode()
V/QC_RIL_OEM_HOOK( 1703): sendQcRilOemHookMsg: Outgoing Data is 5155414c434f4d4
010008000400000055000000
V/QC_NV_ITEMS( 1703): Received: 313437323638
V/QC_NV_ITEMS( 1703): sec_code:147268
D/wpa_supplicant( 1539): CMD:DRIVER RSSI-APPROX
D/wpa_supplicant( 1539): wpa_driver_priv_driver_cmd RSSI-APPROX len = 4096
D/wpa_supplicant( 1539): wpa_driver_priv_driver_cmd FULTONHOUSE rssi -65
D/wpa_supplicant( 1539):  len = 21, 21

you can then test your MSL by re-inputting the MSL in the ##DEBUG# screen, if all's well you should now be looking at your debug stats.

Enjoy

[realdreams]

I just flashed Sprint 11114 (http://forum.xda-developers.com/show...&postcount=192)
some discussion about 11114
(http://forum.xda-developers.com/show....php?t=1175032)

Latest QPST ans QXDM I can find
QPST_2.7_366
QXDM_3.12.714

I suggest to compare the Station IDs before and after u flash the PRL, it might be more persuasive than speed test or signal strength, I forgot to do it...

Sprint PRL information with human readable explanations

[MarkMcCoskey]

The link to find the MSL code worked great for me. Just had to go back to the original post on page 1 to get it. https://www1.virginmobileusa.com/myaccount/login.dofsdf

[MarkMcCoskey]

I'm seeing various post mentioning 01115.prl, 01119.prl, and 01120.prl. Are all three of these suitable to use in the Triumph?

[prech]

I found a strange way of getting my msl since that page was broken. I'm working on a method.

I'm rooted but I don't know if you have to be root or anything.. I'll edit this post when i have something

Edit:

Alright, so this is a quick and dirty for those familiar with adb and can get their triumph working with adb. I'm far too lazy to write out a tutorial on installing adb, obtaining the foxconn usb drivers and using anycut shortcut to put the usb in diag mode (although that itself should set you on the right path)

One thing this method needs to make super easy is grep, which if memory serves is part of busybox and that will require root. However if you are quick enough and know what you are looking for you don't really need it.

1.) Start up adb
(ie: C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell)

2.) From anywhere input:

logcat | grep sec_code

basically the " | grep sec_code" is going to just return any line that has that string in it, so you don't have to sift through a bunch of crap. Beaware that command will probably display nothing yet, but leave it running in the adb shell

3.) From your phone's dialpad input ##DEBUG# or ##33284#

If entered properly your triumph will ask you for the MSL. This is normal, what you want to do is input anything, six zeros, your guess what you think it is for a luck test, whatever.

4.) when you continue on, your running logcat in adb should spit out a single line of stuff, at the end it will have sec_code:XXXXXX that's your MSL.

This is all it looks like for those confused.

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ logcat | grep sec_code
logcat | grep sec_code
V/QC_NV_ITEMS( 1703): sec_code:147268

Wow this is so easy! Much easier than with OV having to use CDMA Workshop. Thanks for sharing your discocery

[Zaius42]

Wow this is so easy! Much easier than with OV having to use CDMA Workshop. Thanks for sharing your discocery

My pleasure. Like I said I practically came by it on accident. I'm curious if this would work on any android or just a few

Sent from my MOTWX435KT using HowardForums

[ppan76]

Installed 01115. Very easy to do with EasyCut. 5 minutes top if you have all the software.

Dont see any improvements with 01115

[idbl_fanatic]

I also added ro.product.rat=EvDo only to the build.prop file, as suggested on another forum, and it also seems to help battery life, I now have 0% Time Without Signal.

I am using the 0119 PRL

[Whey Cooler]

....so....all this prl swapping is basically doing...nothing? results are pretty much inconclusive or equal to what you had before?

[mixedguy]

I also added ro.product.rat=EvDo only to the build.prop file, as suggested on another forum, and it also seems to help battery life, I now have 0% Time Without Signal.

I am using the 0119 PRL

I'm trying to save ro.product.rat=EvDo in the build.prop through through ES file editor but it wont save and gives me a error.. Is there anything I need to do in order to save my Edit?


Edit - Never mind I figured it out..

[juuvvy]

damn. seems complicated. i don't want to mess my phone up lol

[MarkMcCoskey]

No, not that complicated. Just read the instructions a few times, then go about it slowly. You'll be surprised after the fact.

I've been using 01115 for several days. It was quite a sound/clarity improvement over the stock PRL, which translates to: my girlfriend in NYC was happy I got a different phone.

I just swapped to 01120 today. Will give this a couple days.

Anyone using 11114? I hear this allows roaming on VZW.

[prech]

Have the folks who've performed the EVDO patch/change and PRL update noticed any increased performance (voice or data quality)?

The earliest posters on page one say no, but a few more recent folks suggest they make a dramatic improvement: http://androidforums.com/triumph-all...ta-speeds.html

[idbl_fanatic]

Can someone post up the stock PRL?