QUESTION: anyone successfully hacked MSO5000 series using macOS and Python3? - Page 1
Forum section: electronics / testgear

author: 6SN7WGTB
author_rank: Regular Contributor
timestamp: September 26, 2024, 02:32:30 pm
content: Have Python3 and pip installed.'Scope communicating with macOS fine. Have done the interrogation:python3 XXXXXXX Rigol_MSO_LicensingUtility_2.10b.py -i 10.n.n.nAnd satisfactorily get returned the 'scope option list, which correctly shows I have bundled options but not memory depth and 350MHz BW.Needless to say, slightly nervous about doing the -r to read FRAM and activate.Only because first time I've used Python and would like to know that someone else has done this on macOS, and that, e.g. the PRIV.PEM gets written back to the Mac OK and that the -a does indeed occurr automatically and correctly.Anyone?Thank you.(BTW Martin has been brilliant and generously checked I am on right track so far).

author: BTO
author_rank: Frequent Contributor
timestamp: September 28, 2024, 11:03:29 am
content: Quote from: 6SN7WGTB on September 26, 2024, 02:32:30 pmHi mate, For the benefit of anyone else who is paranoid as you are allow me to say this1. The reason why no one else has responded and probably won't is because most of them have already activated and licensed their scopes2. There already exists several posts for this topic so i wouldn't be suprised if you get pulled up for posting duplicate posts.(Don't worry, i'll link the other posts in here os it all meshes together)3. Now we have been doing this now for approx 2 years , maybe a little longer on the MSO5000 AND Maybe 6 months on the MSO8000.in that time i personally have helped approx 300 people license the scopes successfully.Briefly stated, we started with the script by DrMefisto and later TV84 got involved , Now after the initial patching Method we wereable to license the scopes so they survive future firmware updates.Along the way we encountered a few speed bumps, some were not able to activate for various reasons , then we had the Exception ErrorAnd a few other things.ALL OF THOSE ISSUES HAVE BEEN FIXED.IN ALL 300 ODD (that only account for my effort in this) NOT 1 HAS BRICKED THEIR SCOPE4. We are way way way beyond beyond paranoid about whether this will work or not......... IT WILL ABSOLUTELY WORK.The fact that you're on a Mac makes no difference at all, and along the way i have had around 4 or 5 people who were on a macand they activated as wellBEING ON MAC JUST MEANS...- Instead of using cmd.exe or PowerShell You're going to be using Terminal- As for the directory location that priv.pem file gets stored in , which is c:/ Users/User Fact is.. You can put it in most any location you want so long as......THE LOCATION THAT PYTHON IS WORKING IS THE LOCATION WHERE YOU WANT TO PUT THE SCRIPT, this will be the locationwhere the priv.pem file is located and createdNow... Python works on both Windows , Linux and Mac (so that part is irrelevant)The file structure is different from Windows to Mac, but.. You can adjust for that easilyTerminal or Powershell or Command Shell......... Whatever .... it's all doing the same thing in this situationLastly, the networking part of it is the sameSO THERE REALLY IS NOTHING FOR YOU TO WORRY ABOUT5. Now you said you haven't run the -r switch to regenerate the Priv.pem BECAUSE YOU WERE CONCERNED.Well there's nothing to be concerned about- When you run the script with the -r switch it will generate the priv.pem file- then it will automatically go (After reboot) into activation and licensing mode- Now let's say the priv.pem doesn't get generated successfully because you are on mac, for some weird reason.well then... Nothing will happen, ... Activation will be attempted and it will fail. Your scope will be fine,- Let's say the priv.pem is generated but let's say because of mac security it doesn't activate.well then it'll just fail and your sope will be fineBut the chances of any of that happening at this point is miniscule .6. Now if you need actual proof, Feel free to read the past posts , We have several posts that have contributed to thisPost 1This post has around 60 Pages , i would start from around Page 45 onwards to see people who started activating successfullyCode:https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopesPost 2 (i created this one to attempt to minimize the first post)Code:https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-dr-mefisto-licensing-methodPost 3 (This was created by ASP to help people activating with the MSO8000 and 7000 although no one (to my knowledge) has had a 7000)Code:https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso8204-mso8000Then we have the credits.....In reality a lot of people contributed to this and we could not have gotten to where we are if forum members didn't help by provingmemory dumps and other scope data to me as well as some of them sacrificing our scopes when no one else wanted to take the plungewhen it was a reality that the scope MIGHT HAVE realistically been brickedThe credits are as follows****************************** CREDITS ******************************ORIGINAL VERSION BY DrMefistO\n"---------------------------------------------------------------------LOTS OF THANKS TO :tv84 - Paving the path from the startResponsible for rigol_kg2.pySMAS - Laying out the path to activation in anEasy to understand way.Seppletronics - For working out the edited version of the fileBTO - Assisting with Assertion Error- Minor script modifications resulting in- rigol_kg2_3_000.py- Rigol_MSO_LicensingUtility_2.09b- Cosmetic changes to scriptstraxpalicaru (TrAx) - Donated his MSO8000 for testingasp - HUGE Effort in script progression- Opened the door to MSO7000 and MSO8000- Continued to work on ongoing Assertion Error- Optimized the script for faster activation- Responsible for...- rigol_mso_util_2.02a.py- rigol_mso_util_2.03a.py- rigol_mso_util_2.04a.py- rigol_mso_util_2.05b.py- rigol_mso_util_2.06b.py- rigol_mso_util_2.07b.py- rigol_mso_util_2.08b.py- rigol_mso_util_2.09b.py- rigol_mso_util_2.10b.py- rigol_mso_util_2.11b.py- rigol_mso_util_2.12b.pyKyr - Pointing out offest issue 0x001DALL OTHER MEMBERS - That supplied feedback when neededDAVE JONES(EEVBLOG) - For doing all that he does"*********************************************************************SO IN A NUTSHELLthere are mountains of instances of evidence why you have no need to worryand i can say this as well,If we go back to the Rigol DS1052E (where it all started) then proceed through to the DS2000A Series then to the 1054Z seriesand then through MSO5000 and Now MSO8000THE MAIN THING I HAVE NOTICED WHY PEOPLE DON'T HAVE THEIR SCOPES ACTIVATED.............................. THEY ARE SCARED AND PARANOIDI literally know forum users that still1. On their DS2000A have upgraded their version of scope since they initially upgraded the scope.2. Same on DS1054z3. Same on MSO5000Even though we have HUNDREDS of people that have succesfully done this. I still get people saying "I don't want to risk it"Truth is, there's nothing to risk anymore, it's all done and dusted and it's likely Python Script Version 2.13b will be the last oneand the reason is... There are no more problems to fix hereSo mate, my advice.... Go ahead and run the -r switch , Have a bit of faith.Hope this helps

author: 6SN7WGTB
author_rank: Regular Contributor
timestamp: September 28, 2024, 11:13:33 am
content: I don’t doubt that the process works at all, but forgive my slight reluctance as I’m doing this on a different platform to that most common!Mods by all means close thread if considered duplicate or unnecessary.

author: BTO
author_rank: Frequent Contributor
timestamp: September 28, 2024, 11:23:29 am
content: Quote from: 6SN7WGTB on September 28, 2024, 11:13:33 amNo No, i'ts ok, I absolutely understand, You are BY NO MEANSthe first to be paranoid, off the few hundred that i've helped, i would saypossibly 40% were paranoid, but when this was a new concept, it was more like 90% were paranoid.So.. Nothing to forgive.. You are who you are , that's fine.As for Platforms, don't make the assumption that only windows users have done this.I've helped people on Mac, Windows and Various Linux Distro'sthere are 3 basic things to consider here in terms of Platform1. Python to run the script (Well, Python works on all the platforms os it's not a problem)2. The networking of the scope to the computer (this is a hardware thing and won't affect the platform)3. The directory location, The working Directory. This will changeI have (let's say) Coerced forum members to only use C:/Users/User and i did this just for the sake of simplicityand so that everyone can follow the PDF i created as a standard.The truth is, You can place the priv.pem in any location you likeAs long as the script and .pem file are in the same folder and your C.L.I. (whichever you are using) has access to itso again, i wouldn't worry about your cross platform issue, in this case, i'ts not highly relevant , it's just python and networkingand running a script, and if it fails , nothing happens to your scope.

author: 6SN7WGTB
author_rank: Regular Contributor
timestamp: September 29, 2024, 01:36:11 pm
content: Let me add finally, for the benefit of anyone else.NOW DONE. ALL OK.It all worked perfectly, and as explained.Post unlock to 350MHz BW, the -3dB point as measured is around 510MHz, starting from 10MHz with a 100mV RMS signal from an IFR2025.

author: BTO
author_rank: Frequent Contributor
timestamp: September 29, 2024, 05:09:08 pm
content: Quote from: 6SN7WGTB on September 29, 2024, 01:36:11 pmTHERE YOU GO MATE... WELL DONEYou broke your virginityEnjoy your scopeDon't forget- Do a Self Test- De a Self CalAlso if you want to get deep into your scope i have a bunch of tutorial videos herehttps://www.eevblog.com/forum/testgear/post-hacking-rigol-mso5000-post-hacking-tutorial-deep-dive/