[How To] Retrieve MSL CDMA Workshop Method

Search This thread

techwerkz

Senior Member
Mar 24, 2008
76
17
Fort Myers, FL
www.techwerkz.com
Try the "MSL Reader" from the market. I wrote that a few weeks ago to make MSL reading much easier.

chart

Good work man. Updated my first post.
 

cytherian

Senior Member
Oct 15, 2010
263
25
NJ
Google Pixel 5
For those who haven't rooted (thus MSL Reader isn't an option), you can easily use CDMA-Workshop. The main trick is getting the proper software installed (HTC Sync, drivers, etc) and then using it in various ways, depending upon your situation and operating system. I'm running Windows Vista x64.

First, you have to know what COM port the phone is on, when connected via USB. When you run CDMA-Workshop, there's a choice of 25 ports, so it would be major pain testing connectivity on all of them. Normally QPST can help you in this regard. It should show your active phone on one of the listed ports when you run QPST Configuration. However, it won't always see the phone as-is. Sometimes you have to put your phone into diagnostic mode, via ##3424#.

I'd had a slightly older version of QPST, so I uninstalled it and put the newer one on (b323). After that, QPST would not see my phone on the available ports. However, what I noticed when I plugged my phone in, was the "new device installed" dialog pop-up. If you click on it, it'll tell you what port the phone was installed on. In QPST, you can select to add additional ports. It'll show you a few in the list. If the port that the phone is on isn't listed, you can select one of the ports and modify it to match. In my case, it was port10. Upon adding it, QPST showed the phone active in the list.

CDMA-Workshop requires you to select the active port that the phone is on and then connect, in the Main tab. Make sure QPST is stopped, or else CDMA-Workshop will fail (only one program can access the port at any given time). Once connected, perform a read for the basic info. Then go to the security tab and perform a read with the default dropdownlist selection. If it fails, try restarting your phone. In my case, it didn't work the first time. Restarting the phone worked, but I also had to put it into diagnostic mode. Once that was done, I connected, performed a basic read, then did an SPC read from the security tab. I got the MSL ID with no problem. :)
 
Last edited:

techwerkz

Senior Member
Mar 24, 2008
76
17
Fort Myers, FL
www.techwerkz.com
For those who haven't rooted (thus MSL Reader isn't an option), you can easily use CDMA-Workshop. The main trick is getting the proper software installed (HTC Sync, drivers, etc) and then using it in various ways, depending upon your situation and operating system. I'm running Windows Vista x64.

First, you have to know what COM port the phone is on, when connected via USB. When you run CDMA-Workshop, there's a choice of 25 ports, so it would be major pain testing connectivity on all of them. Normally QPST can help you in this regard. It should show your active phone on one of the listed ports when you run QPST Configuration. However, it won't always see the phone as-is. Sometimes you have to put your phone into diagnostic mode, via ##3424#.

I'd had a slightly older version of QPST, so I uninstalled it and put the newer one on (b323). After that, QPST would not see my phone on the available ports. However, what I noticed when I plugged my phone in, was the "new device installed" dialog pop-up. If you click on it, it'll tell you what port the phone was installed on. In QPST, you can select to add additional ports. It'll show you a few in the list. If the port that the phone is on isn't listed, you can select one of the ports and modify it to match. In my case, it was port10. Upon adding it, QPST showed the phone active in the list.

CDMA-Workshop requires you to select the active port that the phone is on and then connect, in the Main tab. Make sure QPST is stopped, or else CDMA-Workshop will fail (only one program can access the port at any given time). Once connected, perform a read for the basic info. Then go to the security tab and perform a read with the default dropdownlist selection. If it fails, try restarting your phone. In my case, it didn't work the first time. Restarting the phone worked, but I also had to put it into diagnostic mode. Once that was done, I connected, performed a basic read, then did an SPC read from the security tab. I got the MSL ID with no problem. :)

There is an easier way to find the COM port, just look at device manager.

Windows Key + R -> devmgmt.msc -> expand Ports (COM + LPT). Look for the diagnostic driver and the port will be shown.

Taking this a step further ... Right click on it, go to properties, head to the Ports tab, and click advanced. You can change the COM port there.

I explained this in my first post that I wouldn't explain this lol. It is pretty easy information to find via Google, however I will just leave that here. I was just being lazy in the first post :D
 

wherestheanykey

Senior Member
Sep 1, 2009
205
7
Hi, I am using Windows 7 Home Premium 64bit and have downloaded the diag drivers from post 1, but when try to do the update driver from device manager, and browse out to the 64bit folder, I get the windows did not fine the right driver for your device. Is this working for others using WIN7, what am I missing?

Thanks,
 

m4f1050

Senior Member
Apr 20, 2007
1,994
208
Anybody have the Windows XP 64-bit version? This worked for me on Windows 7 64-bit but not my XP 64... :(
 

ljohnson1981

Senior Member
Jul 7, 2009
115
8
under ports (COM and LPT) i see HTC Diagnostic Interface (COM 12) and its working fine. no unknown icons anywhere to be found... i have htc sync and debugging on and running.... if you can tel me where i should go to update the drivers then perhaps i should do that...

thats all you need to see is the port show up, diagnostic interface is exactly what you want to see :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    Update 9/14/10 -- There is an app in the market called MSL Reader that successfully found my MSL. It does require root access, my method will still work for phones that are not rooted. Thanks flexgrip for pointing this out, and mmastrac for the hard work developing the app.
    chart


    Since the other method using aLogCat doesn't seem to work for everyone, this is a more consistent method.

    Please be very careful with CDMA Workshop. I am not responsible for your curiosity, or stupidity!

    I have included screenshots for installing the drivers on Windows 7 x64. This seems to be a little different for most users, so I hope this helps. Windows XP should be pretty similar to below. You can enter Device Manager the same way. Some of the prompts will be slightly different, but at the end most of the same dialogs will appear.

    Prerequisites:
    CDMA Workshop - http://www.cdma-ware.com/workshop.html
    The Demo version will be able to retrieve the MSL.

    HTC Diag Drivers - http://www.techwerkz.com/evo/HTCDiagDrivers.zip
    I have compiled this zip which includes both x86 (32 bit), and x64 (64 bit) drivers for HTC diagnostics. I have successfully tested the x64 drivers on Windows 7, and all works without issue.

    The Fun Part
    Step 1 - Dial ##DIAG# (##3424#) on your phone.

    Step 2 - Connect the phone to the computer via the USB cable. When prompted to install the drivers use the drivers from the ZIP provided above.

    Windows will probably not be able to find the drivers:
    1.jpg


    You will need to manually install the drivers from Device Manager. Quickest way to get there is to press the Windows Key + R to open the Run dialog. Type in devmgmt.msc:
    2.jpg


    Once Device Manager is open you will see it cannot find the HTC Diag driver :(:
    3.jpg


    Right click on HTC Diag, and go to Update Driver. You will be prompted with the following, choose Browse my Computer. Then choose Let me Pick. Click Next. Click Have Disk. Browse to the drivers you downloaded, and choose the proper INF file. Click Next. Then finally Yes, if prompted :eek::
    4.jpg

    5.jpg

    6.jpg

    7.jpg

    8.jpg

    9.jpg

    10.jpg


    If all went well you will see it installing the driver. Then finally let you know it was successfully installed!
    11.jpg

    12.jpg

    13.jpg



    Step 3 - Run CDMA Workshop you downloaded earlier.

    Once CDMA Workshop is open click the word Port found on the right:
    14.jpg


    You will be given the options to select the correct COM port (Please note the demo version will only go to COM6. If you have an issue with this please Google how to change the COM port to something not in use.):
    15.jpg


    Once the correct COM port is selected click Connect:
    16.jpg

    17.jpg


    Head over to the Security tab and click Read under the SPC / User Lock section:
    18.jpg


    If all has gone well you will be given your MSL code! It is the 6 digit number listed after pressing Read. Great Success! :D

    Testing
    The following sections should prompt for your MSL code. Enter what you have retrieved to find out if it is in fact the correct MSL code.

    ##data# (##3282#)
    ##debug#(##33284#)
    ##diag#(##3424#)
    ##svn#(##786#)
    ##prl#(##775#)
    ##prev#(##7738#)
    ##akey#(##2539#)
    ##vocoder# (##8626337#)

    If you followed the steps correctly, the code should work.

    Hope this helps everyone with finding their MSL when Sprint will not give it to you. Again, I am not responsible for what you do with this information. This is a use at your own risk method!
    6
    I figured out how to get this to work on the OTA updated devices. I just got a replacement, and tried the steps in the original post, and and I kept getting the same error that mikecore was getting a few posts up. Here is how to fix that.

    Before you go to the step in the original post where he has you click "read" on the security tab where it says SPC, head over to the terminal tab, and enter the following (exactly as I have it below with spaces and everything) on the line that says "DM Commands"

    41 74 64 77 61 6F 70

    Click "send"

    You should get some output below in the message box along the lines of:

    "Answer Length 5 bytes >
    0x0000: 41 01 70 41 7E .. .. .. .. .. .. .. .. .. .. .. .. | A.pA~............."

    Then go back over to the security tab and try reading you SPC / User Lock.

    After I did what I explained above, it worked perfectly for me. And all I was using was the Demo version of CDMA workshop.
    2
    Someone else try my post above and verify that it works for others.

    Sent from my PC36100 using XDA App
    2
    Try the method in the very first post in this thread, but use the extra step I mentioned a few posts up.

    Sent from my PC36100 using XDA App
    1
    the download link to CDMA workshop now is version 3.7 I was confused at first, when you said com port right, now its on the left, but still gives the MSL code. Thanks for the great tut. worked for me.