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
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.
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)Code: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
its just going to look a lot more like this:
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.Code: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