Hacking the Rigol MSO5000 - Dr Mefisto Licensing Method

[BTO]

HACKING THE RIGOL MSO5000 - Dr Mefisto's Fully Automatic License Activator

BACKGROUND :
This post exists because of the main rigol MSO5000 Post and specifically because of the python scripting method reverse engineered by Dr Mefisto (This is the VERSION 2 of the script)
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/2671/

Also because SMAS laid out their path to activation in a very easy to understand way.
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/2840/

But also because a few members have stated that there should be one simple place to come to instead of having to dig though almost 60 pages of discussion and then it's a matter of finding the files.
The unavoidable fact of these posts is that they will be long and will have many pages.

THE PROBLEM SUMMARIZED :
- As always it starts with us wanting to unlock all the features of the MSO5000 (or whatever scope it is at the time)

- as the method progressed it was quickly realized that rigol (Unlike the DS2000A) were not using "Symmetrical Encryption" but instead "Asymmetrical Encryption" which meant that since we didn't have Rigol's encryption key, we were not able to approach the solution in the same way. At this stage the "PATCH METHOD" was put into place. And it worked, but it had 1 problem... It would not survive a firmware upgrade. So in the future when the next upgrade came out and you installed it you would lose all your unlocked options.
 Same thing if you downgraded. But don't get me wrong... If you stayed on the same version you were totally fine and everything worked.

- Then in Post #2671 Dr Mefisto had a eureka moment and worked out a python script that would CORRECTLY LICENSE THE SCOPE. (Actually the original script was in an earlier post and Post 2671 is the version 2 / aka The Automated Script.

- However a lot of people found this challenging and difficult to perform. it became the case that faced with "Patch Method" vs "Python Licensing Method" it was seen much easier to do the former.

WE NOW HAVE A FULLY WORKING SOLUTION...

FIRST LET ME THROW SOME FEARS OUT OF THE WAY
It has become obvious also that even though everyone should upgrade to this method as it means.... when further upgrades come out you will have nothing to worry about and you'll just download the official upgrade from the Rigol website (No further hack or patching required). But even though everyone SHOULD, They are not doing it.

Why not ?

- one reason may be you're afraid of change and what may happen, because if it's working now with the patch why change ?
Answer : Because you'll have to anyway

- You've heard rumours of the scope being bricked

- You've heard people having problems with it

- You've heard that the script can damage your scope

LET ME PUT ALL THAT TO REST

- My scope started on V 1.3.0.3  (00.01.03.00.03) , i used the patch method and went up to 1.3.3.0 (Latest Version). All Options Unlocked
  I then Downgraded to 1.3.2.2 (During the downgrade all options are lost). I then used Dr Mefisto's script to license the scope and All Options were unlocked successfully.
  I then upgraded to version 1.3.3.0 ALL OPTIONS SURVIVED,  I then downgraded just to push my luck , to 1.3.0.3 ALL OPTIONS SURVIVED,  i even went as low as 1.1.4.4  ALL OPTIONS SURVIVED.

So Upgrading and downgrading is not a problem , But there's a catch, You can't downgrade via the operating system you have to do it in the Pre Boot Menu

- A Note on the Pre Boot Menu.  There are 2 Options   "Firmware Upgrade", "Restore Defaults" .  FIRMWARE UPGRADE both upgrades and downgrades your scope in a Pre O/S Environment.
  However RESTORE DEFAULTS Just restores your defaults,
IT DOES NOT Lower you to a lower version of firmware
IT DOES NOT take your scope back to it's original version (After you upgraded)
All it does is.. if you changed the settings in your scope, it restores them to stock settings.  This step is NOT necessary in order to upgrading, Nor does it avoid you bricking your scope if you don't do it.
it is a good step to do, but let there be no illusion, it's not a necessary step.

- I have , at the time of writing this post upgraded and downgraded my scope over 30 times just to see if i could brick it and around 3 of those times i used restore defaults, the rest i didn't. Nothing happened.  I have gone between the patch and back to the script method over and over.  THIS METHOD IS A VERY RELIABLE METHOD

- A WORD ON BRICKING YOUR SCOPE
1. You're probably not going to
2. IF YOU LOSE POWER during the FRAM copy process YES.. YOU'LL BRICK YOUR SCOPE
3. IF YOUR LOSE ETHERNET CONNECTION during the FRAM copy process... YES, YOU'LL BRICK YOUR SCOPE
Because the data stream cannot be interrupted until it gets to 100%  (this only applies to the .. maybe 2mins that the FRAM is actually being written to)

If this method doesn't work for you you can always revert back to the Patch Method if you wish.

- I have observed that most of the problems arise either from fear or lack of knowledge how to do this method  so......

HERE IS WHAT YOU NEED TO DO
(This post has been put up so that if you can get through it you won't need to watch the video) but i have included a video that will take you through it step by step.
and you can also ask me for help and i'll be happy to help you


STEP 1.
DOWNLOAD THE FOLLOWING
Rufus
https://rufus.ie/en/

Python
https://www.python.org/downloads/

THEN. GO TO MY MEGA CLOUD SERVER
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ

Here you will find a few things that you'll need

1. Scope Firmware Version 1.3.2.2
2. Scope Firmware Version 1.3.3.0

3. Rigol_kg2.py   (Dr Mefisto's Script Version 2) ------ NOW OBSOLETE
3. Rigol_MSO_LicensingUtility_2.10b  -- CURRENT SCRIPT (as of 20th July 2024)

4. STEP BY STEP INSTRUCTIONAL PDF FILE (MSO5000 DrMefisto Licensing Method) (Also Attached)

OPTIONAL
- Downgrading to 1.3.2.2  Video (this video shows you how to get into the Pre Boot Menu)


THE ACTUAL UPGRADE PROCESS

I'm going to give you 2 options

OPTION 1 - I will BRIEFLY detail the steps in this post , You can take a crack at it if you feel competent, However i personally feel if you are competent enough you wouldn't be here in the first place.

OPTION 2 - There will be a DETAILED pdf of the steps at my MEGA cloud location , Download the pdf and follow that

NOW...
HERE ARE THE BRIEFLY OUTLINED STEPS that you'll have to do

(THESE STEPS ASSUME THAT YOU HAVE A DECENT DEGREE OF NETWORKING EXPERIENCE AND BASIC PROGRAMMING EXPERIENCE - Python is preferred but not necessary, But you MUST have had some experience actually programming from scratch, not just uploading sketches into arduino for example. you must be familiar with C.L.I. if you don't know what C.L.I. is then don't do this method. you must be familiar with flashing EEPROM Basics.)

Now, i'm not saying Dr Mefisto's method is hard, i'm just saying, if you want to take the quick road and just read this post and jump in the deep end, IT DOES REQUIRE TECHNICAL KNOWLEDGE.
The other option is the PDF walkthrough. But the method is easy, it's just very particular.

so...
- Get a USB Stick (up to 16GB)
- Download Rufus and format the USB stick to FAT32 File System (or... You can just use windows format if you like, but SOMETIMES this causes problems) Rufus is more reliable.
- Establish which firmware version your scope is on.

To do this upgrade you will need to start on Version 1.3.2.2 
The latest version as of today is 1.3.3.0
if your scope is not on the latest version, You will be upgrading to  1.3.3.0
But you must first do your backups. 

(NOTE : I AM ASSUMING A WINDOWS 10 PRO ENVIRONMENT - If you have Linux of Mac Make the appropriate Adjustments.

- if you are on 1.3.3.0 and patched , Put the 1.3.2.2 software version on your USB stick
(First use Step 1 and do your backups) , Then Use the STEP 2 GEL file and put it on your USB stick.

- if you are on 1.3.2.2 with no options installed (You're fine), You just need to download the 1.3.3.0 firmware, Use Step 1, Do your backups , Then use STEP 2 GEL file and put it on USB Stick  (Min. 2GB)

- Now you need to turn off your scope, Insert the USB stick into the scope, and Enter the PRE Boot menu and do the firmware ugprade
 (You can feel free to select RESTORE DEFAULTS if you want, it doesn't hurt anything )

- After that , Regardless of what version you started on, you will now be on Ver. 1.3.2.2
- If at this point you are on 1.3.2.2 and completed your Backups. NOW UPGRADE TO 1.3.3.0

- Now download the rigol_kg2.py script
THE CURRENT SCRIPT IS Rigol_MSO_LicensingUtility_2.10b.py

- Open your command shell  YOU HAVE THE CHOICE TO USE WINDOWS cmd.exe OR  WINDOWS POWERSHELL  (Powershell is recommended), it has had a higher success rate.
Start in Powershell though if not sure.

- now whatever directory your command prompt or Powershell is starting in, Copy your script to that location .

- NOW SET UP YOUR NETWORK
You need a router (Internet is not required) (But the downloaded files are)
You need a PC
The PC needs to be connected to a LAN Port in the back of your router
You need an MSO5000
the MSO5000 needs to be connected to a LAN Port in the back of your router
(This is a basic Star Toplogy Configuration)

MAKE SURE THE POWER IS RELIABLE
MAKE SURE THE ETHERNET CABLES ARE PLUGGED IN PROPERLY
Make sure you don't have a lightning storm going on or power outtages
Make sure you don't have shit power boards and that everything is securely plugged in and can't fall out
 (YOU'VE BEEN WARNED... IF YOU BRICK YOUR SCOPE IT'S BECAUSE YOU IGNORED THIS)

Now that everything is connected

- Download Python
_ Install Python (this is the part where ... if you're not sure... Read the PDF or watch the video)
If you install python and run it and you can't connect to the scope (Uninstall Python and do not proceed with this method, but instead do the PDF or Video method). i'm assuming here you know
how to install python correctly and run it and have basic programming experience.

- Now take that USB stick out of your scope

- Obtain the scopes IP Address and Use Command prompt or powershell to run a ping command to see if your PC is communicating with it.
IF YES... Proceed
IF NO... Troubleshoot the network
Stay on AUTO and DHCP (Try to avoid using STATIC IP)

- TYPE   

Code: [Select]

pythonInto the command shell or powershell to see if it connects to the python interpreter
if it does
- TYPE 

Code: [Select]

exit()  and press enter   (do not enter the commands directly from the python interpreter) Use cmd or Powershell only to interface with the interpreter
Now you want to see what options you have before you proceed  (ASSUME MY RIGOL SCOPE IP ADDRESS IS 10.1.1.666) 
TYPE

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -h 10.1.1.666Press ENTER
this will bring up the help menu (you can do no harm to your scope by doing this)
The options we are interested in  the SWITCHES that we are interested in are
-h HELP   --------------------------------- (THIS CANNOT HARM YOUR SCOPE)
-i INFORMATION ------------------------ (THIS CANNOT HARM YOUR SCOPE)
-r REGENERATE PRIVATE KEY--------- (THIS GENERATE THE PRIVATE KEY (Priv Prem) needed before activation)
-u UNINSTALL THE OPTIONS--------- (THIS Uninstalls all options and bundles) so if you are on 1.3.2.2 with installed patched options, you use this option to uninstall them
--reboot -------------------------------(Reboots the scope without having to press the OFF button)

Note the version of the scope
Note if the options are FOREVER or -
if you are on 1.3.2.2 and it says FOREVER because you used the patched version  do this now
if you are on the patched version

TYPE

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -u 10.1.1.666Press ENTER
Make sure to restart your scope after this
Restart now happens Automatically


NOW LET'S PULL UP THE SCOPE INFORMATION
TYPE

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -i 10.1.1.666Press ENTER

If you now have
- All Options Uninstalled
(if you don't restart your scope )

WE ARE NOW READY TO GENERATE THE PRIVATE KEY.... 
(Ensure you do not lose network or power connection at this stage)

TYPE

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -r 10.1.1.666Press ENTER

EXPECT THIS...

- the information table will appear
- A progress bar will appear that says "READING CFRAM"  ... Let it get to 100%
- Then "APPLYING NEW CFRAM"  Let it get to 100%
(if it seems to stall for longer than 1 min, it means you clicked on the screen,   RIGHT CLICK to un pause, then leave it alone)

- Then you will see multiple lines of ACTIVATING
- at the end of it you'll get an information window.   The options will still NOT BE ACTIVATED (that's normal)

-------------------------EDIT : THIS STEP IS OBSOLETE-----------------------------------------------
NOW WE RUN THE SCRIPT
TYPE
python rigol_kg2.py 10.1.1.666
Press ENTER
------------------------------------------------------------------------------------------------------------
After this you will expect all options to be activated (They won't be), That's also normal

UPDATE :
- The scope will reboot on it's own if needed
- After REGENERATE the scope will AUTOMATICALLY go into activation, which is this command

Code: [Select]

python Rigol_MSO_LicensingUtility_2.10b.py -a 10.1.1.666BUT YOU WON'T NEED TO ENTER THIS
The scope will then restart again on it's own.

-------------------------EDIT : THIS STEP IS OBSOLETE-----------------------------------------------
Now REINSTALL 1.3.2.2  even though the current version is 1.3.2.2  DO IT AGAIN,  put the USB in the scope with that firmware version on it and run Firmware upgrade again.
(Sounds stupid.. Just do it)

- Then follow the steps again
Get the python INFORMATION up again
NO NEED TO REGENERATE THE KEY THIS TIME
Then just run the script again
TYPE
python rigol_kg2.py 10.1.1.666
Press ENTER
-------------------------------------------------------------------------------------------------------------
THIS TIME YOU WILL BE ACTIVATED

BUT WAIT , YOU'RE NOT DONE JUST YET

- Now erase the USB stick and load 1.3.3.0 onto it

do the Pre Boot Menu UPGRADE FIRMWARE to 1.3.3.0
or you can do this straight from the operating system

NOW YOU WILL NOTICE A FEW THINGS

YOU WILL NOW BE CORRECTLY LICENSED

1. You're now on 1.3.3.0
2. ALL YOUR OPTIONS HAVE SURVIVED A FIRMWARE UPGRADE
3. You're now good to go

REMEMBER THOUGH

1. Do a self check (3 tests)
2. Do a self calibration
3. RUN YOUR BACKUPS AGAIN (Always remember to backup)

NOW YOU'RE ALL DONE , that's it


Lastly, if you have any further concerns, Let me know and i'll test it and post the results.
My goal here is to get everyone comfortable with Dr Mefisto's script, and to upgrade their scopes confidently.



EDIT : New pdf uploaded to include the step that shows you how to install the modules.
EDIT : This Method also supports Activation of  MSO5000, MSO7000, DSO7000, MSO8000  up to their Max. Respective settings.

[BTO]

UPDATE : The Step by Step Instructional PDF is now available (it's detailed)

Also if possible (Because i'm interested to know) could you please leave comments if this worked for you or if it didn't , i think this will start working for everyone.

[Sergey_21]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?

[BTO]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?
(Attachment Link)

Definitely.....

DO THIS FIRST

Code: [Select]

python d:/rigol_kg2.py -i 192.168.1.37
THEN THIS..

Code: [Select]

python d:/rigol_kg2.py -u 192.168.1.37RESTART YOUR SCOPE.

THEN THIS...
DELETE THE PRIV PREM FILE from it's current location
(it should be on the d Drive where you put your python script
then

Code: [Select]

python d:/rigol_kg2.py -r 192.168.1.37RESTART YOUR SCOPE.

then..

Code: [Select]

python d:/rigol_kg2.py 192.168.1.37RESTART YOUR SCOPE

Do you now have all options unlocked "FOREVER" ?
You might, but i don't think so..
IF NOT
DO THIS

 - Put the 1.3.2.2  Firmware GEL File on the USB Stick and even though you are already on 1.3.2.2 ...... DO THE UPGRADE AGAIN
- Go into the PRE BOOT menu by pressing Power button then repeatedly the SINGLE button and Select  FIRMWARE UPGRADE
(Whether you select Defaults, is completely up to you,  some people feel more comfortable doing this... Your call)

After the upgrade

Code: [Select]

python d:/rigol_kg2.py -i 192.168.1.37
then..  You don't need to do -r anymore, Just jump straight into

Code: [Select]

python d:/rigol_kg2.py 192.168.1.37
AND VOILA... 
RESTART YOUR SCOPE

THEN YOU NEED TO UPGRADE TO 1.3.3.0
Grab the GEL file for 1.3.3.0  and you can now do this from the PRE Boot Menu or from the scope in Local Upgrade, it's up to you.

then Restart your scope
Check if it's all good,  IF IT IS...

GET THE 1.3.3.0 BACKUP FILES AND DO YOUR BACKUPS
Do a Self Check
Do Self Cal
and there you go

If you need help, i'm still up, Let me know

[BTO]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?
(Attachment Link)

NOTE TO EVERYONE RE THE UPGRADE PATH

Code: [Select]

python d:/rigol_kg2.py -i 192.168.1.37
Notice the d:/

LET'S TRY TO AVOID USING USB STICKS WHEN DOING THE UPGRADE

WARNING : if the USB Stick fails (as they tend to do ) and it happens during the write process of

Code: [Select]

python d:/rigol_kg2.py 192.168.1.37YOU.... WILL...... BRICK YOUR SCOPE

I only advised you to go ahead with it because you already had the python path installed and i didn't want to mess with it (to keep things simple)
but in the future, i do not advise that you keep your python scripts on a USB, I WOULD ADVISE

1. Open your shell   Probably go for Powershell first
2. Whatever directory location it starts with..   
3. Copy your script to that location  (IT'S MUCH EASIER THAT WAY)

[BTO]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?
(Attachment Link)

Also, Re The Assertion Error, 
if it fails to do it again

TAKE YOUR SCRIPT OFF D DRIVE AND PUT IT IN YOUR C DRIVE AT THE LOCATION THAT THE COMMAND SHELL OPENS IN
Usually it will be
C:\Users\User
and retry all the steps

[BTO]

Hello!
I ran into a problem, perhaps this is due to the fact that some of the options are already activated (I bought it together with the oscilloscope). Is it possible to do anything?
(Attachment Link)

So.. How did you go ?

[Sergey_21]

So:
1) command python d:/rigol_kg2.py -u 192.168.1.37 worked and reset all options and then the oscilloscope rebooted;
2) the PRIV PREM file could not be deleted, because there is nothing to delete (there is no file);
3) the command python d:/rigol_kg2.py -r 192.168.1.37did not give anything, the result is the same;
4) then, following your advice, I reset the settings and updated the firmware, but this did not solve the problem;
5) drive "D" is a local drive;
6) moving the file to C:\Users\User did not bring any results;

[BTO]

So:
1) command python d:/rigol_kg2.py -u 192.168.1.37 worked and reset all options and then the oscilloscope rebooted;
2) the PRIV.PEM file could not be deleted, because there is nothing to delete (there is no file);
3) the command python d:/rigol_kg2.py -r 192.168.1.37did not give anything, the result is the same;
4) then, following your advice, I reset the settings and updated the firmware, but this did not solve the problem;
5) drive "D" is a local drive;
6) moving the file to C:\Users\User did not bring any results;

ok

LET'S DO THIS STEP BY STEP

1) command python d:/rigol_kg2.py -u 192.168.1.37 worked and reset all options and then the oscilloscope rebooted;

The Command -u doesn't RESET all Options, it UNINSTALLS All options , Please confirm it uninstalled all options.

2) the PRIV PREM file could not be deleted, because there is nothing to delete (there is no file);

EXCELLENT, So in the location where you have the rigol_kg2.py script there is no PRIV.PEM file.......GREAT !!!

3) the command python d:/rigol_kg2.py -r 192.168.1.37did not give anything, the result is the same;

OK, SO THIS IS WHERE YOU ARE STUCK

Before you can run

Code: [Select]

python d:/rigol_kg2.py 192.168.1.37and expect it to work, The PRIV.PEM file with the key needs to be generated.  Your attempts are failing because that file is not there

WATCH....
After -r  To REGENERATE the key
You do this (To Run the Script)

Code: [Select]

python d:/rigol_kg2.py -u 192.168.1.37IT FAILS - Because there is no PRIV.PEM File to read from (The Script requires the PRIV.PEM File)

then..

4) then, following your advice, I reset the settings and updated the firmware, but this did not solve the problem;

EXCELLENT - But this will still lead you to a point where NO PRIV.PEM file is generated thus resulting in a fail to upgrade  (DON'T WORRY, I'LL GET YOU THERE)  Just follow me on this . Don't stress

5) drive "D" is a local drive;

WHY IS D DRIVE THE LOCAL DRIVE ?
I have installed and repaired computers for 35 years or more, I have NEVER seen a Primary Hard drive with Operating system on it (Assuming no Dual Boot configuration) that did not call
the Main Hard drive C:\
Ever since computers started,   A and B Are for floppy drives, C is the first primary Drive, D was used for Optical drives. Now  OF COURSE we can re assign them, But
C IS ALWAYS THE PRIMARY DRIVE
the point being (For many reasons)  DO NOT USE OTHER VOLUMES AND DRIVES WHEN DOING THIS, Use the Primary C Hard drive

6) moving the file to C:\Users\User did not bring any results;

OK, I WANT YOU TO DO THIS

1. Go in your computer to windows Explorer and select  THIS PC and give me a screenshot of the window

2. Open Powershell and give me a screenshot of Powershell (Close enough so i can see the directory in use)

3. Give me a screenshot of the location where you have the rigol_kg2.py script

do that ...

[Sergey_21]

The Command -u doesn't RESET all Options, it UNINSTALLS All options , Please confirm it uninstalled all options. - Yes it is, I confirm.

After the last attempt, the file priv.pem appeared, but the result remained the same.

[BTO]

The Command -u doesn't RESET all Options, it UNINSTALLS All options , Please confirm it uninstalled all options. - Yes it is, I confirm.

Good, Well done

so your primary drive is C and the D Drive is a secondary drive.
so LET'S USE THE  C Drive

You've obviously copied the script to the C:\User\Admin Location   
that's good

Now

to check you have communication with the scope

Code: [Select]

python rigol_kg2.py -i 192.168.1.37
followed by

REGENERATE THE PRIV.PEM file

Code: [Select]

python rigol_kg2.py -r 192.168.1.37
CONFIRM THAT YOU NOW HAVE AN ADDITIONAL FILE IN THE C:\Users\Admin   folder  called priv.pem
IF YOU DO

then..

Code: [Select]

python rigol_kg2.py 192.168.1.37
RESTART THE SCOPE
at this point it's normal to not have it activated.... no problem

then
Relaod the 1.3.2.2 GEL FILE and do the FIRMWARE UPGARDE process via PRE BOOT menu

After that's done

again

Code: [Select]

python rigol_kg2.py -i 192.168.1.37
then RUN THE SCRIPT

Code: [Select]

python rigol_kg2.py 192.168.1.37
and now you should be activated with all options unlocked

then
Update to 1.3.3.0

LET ME KNOW IF THAT WORKS

You're almost there, once that priv.pem file generates , it's gonna work

[BTO]

The Command -u doesn't RESET all Options, it UNINSTALLS All options , Please confirm it uninstalled all options. - Yes it is, I confirm.

After the last attempt, the file priv.pem appeared, but the result remained the same.

sorry didn't see that last photo

NO.. THIS IS OK

Now you just need to get that 1.3.2.2 GEL file
wipe the USB, 
put the GEL file in the root of the USB
and run it again VIA Pre Boot menu

after that restart your scope

run the INFORMATION  -i  command

then run the script

Code: [Select]

python rigol_kg2.py 192.168.1.37
and it'll be activated
then.. Give me the good news

[Sergey_21]

I did everything according to your advice, but the options remained unactivated.

[BTO]

I did everything according to your advice, but the options remained unactivated.

ok and
- After you did the upgrade of 1.3.2.2  FOR THE 2ND TIME
1. Did you make sure it was the correct GEL file

2. When you ran the Script,  did you get 2 progress Bars ? 
or was it just the READING CFRAM

also did you get that error from before again ?

[BTO]

hi mate, how are you going with it , if you need me to do a zoom with you , let me know, Glad to help.
You're really close we just need to figure out what's going on. I'm happy to do a 1 on 1 with you if you like.

EDIT :
I'm free this evening, if you want to jump on

[Sergey_21]

1. Did you make sure it was the correct GEL file

I used the file from the folder "Step 2. GEL File - Scope Firmware - 00.01.03.02.02"

2. When you ran the Script,  did you get 2 progress Bars ?

No, the script, as before, did not work to completion, I only had 1 progress bar and an error after that, but the PRIV.PEM file appeared


Probably the problem is that the script reads memory (this is done without errors) and tries to do something with it,
then an error occurs and the data that the script was supposed to generate/rewrite is not generated.

[BTO]

1. Did you make sure it was the correct GEL file

I used the file from the folder "Step 2. GEL File - Scope Firmware - 00.01.03.02.02"
(Attachment Link)

2. When you ran the Script,  did you get 2 progress Bars ?

No, the script, as before, did not work to completion, I only had 1 progress bar and an error after that, but the PRIV.PEM file appeared
[ Attachment Invalid Or Does Not Exist ]

Probably the problem is that the script reads memory (this is done without errors) and tries to do something with it,
then an error occurs and the data that the script was supposed to generate/rewrite is not generated.

Possibly...
TRY THIS

1. Delete the old script and download another one from the link i supplied in this topic
2. it's good that you used the 1.3.2.2 from the link in this topic

NOW... Just try this, ok

- Download 1.3.3.0  and Upgrade to it (don't worry about the options) Just do an upgrade.

-Then.. Go to PreBoot Menu and hist Restore Defaults

- Then.. Get that 1.3.2.2 and via Pre Boot Menu downgrade the scope to 1.3.2.2

- Then repeat the process
it's important to remember you need to do this TWICE

so....  After your back down on 1.3.2.2

put the script in the location of the command shell
run the -i command

run the -r command

then run the script without the switch

THEN.. (this is now 2nd Time Round)
Power down the scope

Load 1.3.2.2 into it again

Run the -i command

Then just run the script

and then you should be activated

I WOULD ALSO BE CHECKING AND DISABLING ANY ANTIVIRUS OR FIREWALL THAT MAY.. POSSIBLY BE MESSING WITH THIS

so try the upgrade then the downgrade and do it over again.
We are really close mate, we are almost there,

the script is supposed to read the Pri.pem file,  it's as simple as that .
so so far you have not done any damage to your scope, don't worry about that.
it's just about getting those 2 to talk to each other
Let me know how that goes

[Sergey_21]

I ran a little through the main forum thread and had a suspicion that this script does not support my oscilloscope model (MSO5074).
On the forum I found a mention only of MSO5072, but so far this is only an assumption.

[BTO]

I ran a little through the main forum thread and had a suspicion that this script does not support my oscilloscope model (MSO5074).
On the forum I found a mention only of MSO5072, but so far this is only an assumption.

No that's not correct. if anything the script supports Multiple scopes, my suspicion is that it even supports the MSO7000 and possibly the 8000
as the Option Bundle JITTER is there which is not available in the 5000 and 7000

Simply put
The Script Generates the Priv.pem
then uses that file to right to the CFRAM
but before doing so it searches for AVAILABLE OPTIONS
as well as INSTALLED Options
and then the one's that are not installed,.... it installs


it supports all MSO5000 Models,  it has nothing to do with that .  if it didn't support it it would even run and it would spit out an error.
I've seen that post as well

REMEMBER THIS...
A Large part of what i'm doing here is.. TO DISPELL THE MYTHS Because this is a good upgrade, and it does work.
but since the topic started , people have jumped to a lot of conclusions and we need to sort out a few of these incorrect assumptions

like one of them is.. the need to hit that Restore Defaults option
which then morphed to....  RESTORE DEFAULTS takes your scope off the current firmware and back to the firmware version that you bought it with.

As a result of all this a lot of people are scared and freaking out.
I have upgraded my scope over 30 times, i've tried to brick it (with the exception of pulling the power or network cable) i wasn't about to.

I tried to fault the script,  i couldn't,  I've had a look through it, it's a pretty straight forward script.

Mate, do what i requested before and let me know how it goes... Buti  YOUR SCOPE IS COMPATIBLE TO THE SCRIPT.  that's not the issue.

[Sergey_21]

Unfortunately, all these actions did not lead to a positive result.
I think we need to return to the old method of hacking.

Thanks for trying to help.

[BTO]

Unfortunately, all these actions did not lead to a positive result.
I think we need to return to the old method of hacking.

I Disagree,
Now we can always revert back to the patched method, There's no problem there.
and it's your scope so it is totally up to you .
But, we are really close to a permanent solution.

1. This is proving unusually difficult, which tells me we just need to find the issue and we'll be good
2. The first problem was that you had the file on a different directory
Sinc then we've made progress

3. Now the issue is that the script is not speaking to the Priv.Prem

Do you want to jump on a 1 on 1 support with you this evening ?
i'm confident we can work it out

Also @DrMeFistO
Mate do you have any ideas...

- He's trying to licence the scope
- He has the script in the same directory that Poweshell opens in
- He is able to regenerate Priv.Prem
- when whe runs the srcript it only get to the READING CFRAM but doesn't write to it

the is currently on 1.3.2.2 (the GEL is a known working file)
the script is a known working file

I'm thinking some software is blocking it or firewall, i see nothing in the script that would not allow his model MSO5000 to not write to FRAM.

we have also tried 2 times
running regenerate -r
running script
then running GEL 1.3.2.2 AGAIN
then ran the script again
should have licenced at this point, but didn't

for some reason the script doesn't seem to proceed to the writing of the CFRAM
in the code, i think he gets to line 127  but doesn't proceed past line 141

ANY IDEAS ...

[BTO]

Unfortunately, all these actions did not lead to a positive result.
I think we need to return to the old method of hacking.

Thanks for trying to help.

Try this for me
Do a SELF CAL

and Uninstall Python for me
then REINSTALL PYTHON  But make sure to do the following

STEP 1 . on the first screen
- SELECT..... CUSTOMIZE INSTALLATION    Not Install Now

- on the same screen CHECK THE BOXES 
- Use Admin Priviledges When Install Py.exe
- Add Python.exe to PATH

STEP 2 - Advanced Options
- Check the top 5 boxes  from Install Python for all users to Precompile Standard Library

STEP 3 -  Install it

STEP 4 - Open command shell  and enter the  -i command and see if it communicates with your scope, if it does
try the process again

[BTO]

I ran a little through the main forum thread and had a suspicion that this script does not support my oscilloscope model (MSO5074).
On the forum I found a mention only of MSO5072, but so far this is only an assumption.

What Model do you have anyway ?

[Sergey_21]

What Model do you have anyway ?

MSO5074

[Swap_File]

Directions and script worked perfectly on my MSO5074.  Thanks.

It might be useful to add a reminder to use a USB stick at least 2GB in size when doing the backups.  I have a little old 64MB stick I use for updates, and that was not big enough.