Hacking the Rigol MSO5000 - Dr Mefisto Licensing Method

[BTO]

Did the post stuff as part of the process so I basically went from page 1 to the end and did it all. 

I'm fairly familiar with using an oscilloscope since I worked in electrical engineering but I'm not all that familiar with the capabilities of the MSO5000 so I'll be going to the thread you linked to and taking a look.

Did the post stuff as part of the process so I basically went from page 1 to the end and did it all. 

That's great, I always make a habit of reminding everyone because the checks, cal and backup are very important.
and peopole generally get caught up in the excitement of finally get all the options that they forget to backup

As for the rest, if you're familiar with scopes and you're an engineer, then you're probably ok.
I just did those videos mainly for the beginners and intermediate who want to understand their scopes and to help them
to understand how to test things properly with the scope

it has things like (if i remember)....    Calculating inductance with a scope by building a simple Tank Circuit , and explaining
how a square wave with a given duty cycle can be used on certain inductors to derive it's value
i think there's some transistor stuff in there . as well as some PWM stuff
there there's a tutorial on cursors',  Pass Fail mask , Etc etc
there's a lot there, chances are you'll find something interesting

Have fun with it

[Dorian_Kaf]

Good evening BTO,

first of all, amazing work you are doing! I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade. Is this constellation possible?

Best regards!

[BTO]

Good evening BTO,

first of all, amazing work you are doing! I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade. Is this constellation possible?

Best regards!

first of all, amazing work you are doing!

Thank you , i appreciate it,  Although i'm not the only one doing the work,  But , thank you in any case.

I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade.

OK, That's not a problem.

Is this constellation possible?

CONSTELLATION ??,  Not sure what you mean .

However if you're asking
"Martin, i have a MSO5104 With all options licensed EXCEPT Sampling Memory and Bandwidth to 350MHz,  is it possible to upgrade
the features that i don't have to licenced status ?"
YES IT IS

Go to Post #1
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-dr-mefisto-licensing-method/

USE THIS LINK to get to the cloud
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ

When you are there  YOU WANT TO DOWNLOAD THE FOLLOWING

- Downgrading to 1.3.2.2   Video  to show you how to get into the Pre Boot menu
- MSO5000 DrMefisto Licencing Method   PDF WITH DETAILED INSTRUCTIONS (Follow this step by step)
- rigol_kg2_3_000.py   This is the script you will use for MSO5100 SERIES
- Upgrading to 350MHz (1.3.2.2)  You will use this zip file for the 1.3.2.2  GEL FILE to downgrade to 1.3.2.2
- Upgrading to 350MHz (1.3.3.0)  You will use this zip file for the 1.3.3.0  GEL FILE and the backup files

download all that
1. Follow the PDF
2. Use the Script stated above for your particular scope
3. After you do all that, don't forget to backup the scope BEFORE and AFTER (this is all in the PDF)

and then you'll be fine

let me know if you have any issues.
Most people have said it's pretty easy to follow along

[BTO]

Good evening BTO,

first of all, amazing work you are doing! I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade. Is this constellation possible?

Best regards!

So.. How are you mate
How did you go with the licensing of your scope,   Any Drama's ?

[BTO]

And i already tried to hardcode the serial number and Model number in the code to get it to run.... It runs trough completely but no matter what i do, the outcome is never ... activated but either unavailable or not activated...

I would be so happy if you could help to get it to work...

Mate, it sounds like you're not doing something correctly Because...

LET'S GO THROUGH YOUR COMMENT STEP BY STEP

today i got my 5072 and right away i tried to upgrade it

OK with 5072 it's likely you'll need to use the script 

Code: [Select]

rigol_kg2.py

All the USB - Scripts ran fine and then i started with the Python script

ALL THE SCRIPTS ?  What do you mean "ALL" , There is only 1 script.

DID YOU FOLLOW THE INSTRUCTIONS IN THE PDF THAT I SUPPLIED AND DID YOU DOWNLOAD THE FILES FROM THE LINK THAT I SUPPLIED IN COMMNET 1 OF THIS THREAD ?

I installed all the modules ran the script with -i and then: (see picture).

the -i Switch DOES NOT INSTALL ANYTHING, the -i Switch just brings up the INFORMATION of the scope

And i already tried to hardcode the serial number and Model number in the code to get it to run

You did What   WHY ?   What exactly did you do ?


before you do this though , because i don't know what you've done, but it sounds really wrong.
I would DEFAULT THE SCOPE TO FACTORY SETTINGS

then..
Roughly stated the process is as follows
(You should really read the PDF as it is details everything)

- You connect your scope to power and network
- You install Python on your computer
- You download the content that you need from the link in Post 1
- You do your backups

- You get yourself on version 1.3.2.2

you run the INFORMATION script

You run the REGEN Script

You then run the script on it's own WITHOUT ANY SWITCH

then, You'll need to  run 1.3.2.2   again

You then run the INFORMATION SCRIPT AGAIN

This time NO NEED to run regen

You just then run the normal script again without the switch
and then it works


There's no need to hardcode or change anything


so..
HAVE YOU DOWNLOADED THE CONTENT FROM THE URL IN POST 1

HAVE YOU FOLLOWED THE INSTRUCTIONS IN THE PDF

[BTO]

And i already tried to hardcode the serial number and Model number in the code to get it to run.... It runs trough completely but no matter what i do, the outcome is never ... activated but either unavailable or not activated...

I would be so happy if you could help to get it to work...

I wouldn't worry too much, at this point it has worked for many people that there isn't much risk.

you should just need to follow the instructions in the pdf

if you can't get it, i'm happy to jump on a zoom with you or something and help you out. but .... it cirrently seems like you are doing some weird and incorrect stuff.
let me know how it goes

[BTO]

Hi BTO,
today i got my 5072 and right away i tried to upgrade it. All the USB - Scripts ran fine and then i started with the Python script. I installed all the modules ran the script with -i and then: (see picture).

It throws an error and terminates the script. Has it something to do with that the LA modules are limited time activated? I tried deactivating them with the script but it shows the same screen and terminates with same error and at the same point.

I really hope that you or somebody else can help me.

Thanks a lot already.

Best regards!

Sorry i had to run out there for a second.
I was going to say 
RE :
TYPE ERROR : CANNOT UNPLACK NON ITERABLE NON TYPE OBJECT

Basically the script was not able to unpack an object because it encountered incorrect values

CHECK THE FOLLOWING
- Download and read the PDF
- Ensure you have installed ALL THE MODULES
- Use your backup that you created (Please tell me you created a backup before you did this................right )  to restore the scope it's original settings

- See.. when you mentioned you hardcoded the serial and the model number,   this error may be happening because you did that .

we need to start your scope from a factory state
all those scripts you say you ran, whatever you did, you need to bring it back to factory again

then download the PDF and just follow it , No need to do anything fancy here, Just follow the PDF

[BTO]

Good evening BTO,

first of all, amazing work you are doing! I have an MSO5104 with all the options activated apart from the Memory and Bandwidth upgrade. Is this constellation possible?

Best regards!

Hi mate, what happened to your comments ? They disappeared, this you delete them ?

Look
WHAT OPERATING SYSTEM ARE YOU USING ?

so based on the message i got on my phone (that is no longer here on the forum)

- You're on 1.3.2.2 now    GOOD
- You've factory reset it    GOOD


- You said

I then tried the connection to the scope via pinging it

THEN.... NOTHING ?
so... What happened, When you send the ICMP Request (Communication Test) to the scope, What happened ?
Did the Scope ACK (Acknowledge) the request for more than 4 cycles or did it not ACK ?

then you said

Then i ran the script (rigol_kg2.py.) with -i

THAT'S INCORRECT !!

it's not

Code: [Select]

rigol_kg2.py.it's

Code: [Select]

rigol_kg2.py

it's very important that you followed PAGES 12 and 13 of the PDF and selected all those stated options during installation

also how are you running python ?
is it from Powershell
Windows Command Prompt
or
Python CLI

Now you're supposed to be doing this....

STEP 1.  (Assuming scope IP is 10.1.1.666)
Bring up INFORMATION

Code: [Select]

python rigol_kg2.py –i 10.1.1.666PRESS ENTER

STEP 2. REGENERATE THE PRIVATE KEY

Code: [Select]

python rigol_kg2.py –r 10.1.1.666PRESS ENTER

STEP 3. RUN THE SCRIPT

Code: [Select]

python rigol_kg2.py 10.1.1.666PRESS ENTER

now, Restart your scope
Reload 1.3.2.2 again via pre boot menu
Startup your scope

STEP 4.  (Assuming scope IP is 10.1.1.666)
Bring up INFORMATION

Code: [Select]

python rigol_kg2.py –i 10.1.1.666PRESS ENTER

STEP 5. RUN THE SCRIPT

Code: [Select]

python rigol_kg2.py 10.1.1.666PRESS ENTER

follow those steps and copy and paste my code in and see what happens

[Slats]

Please help.

I have Rigol MSO5074. I have followed the instructions exactly, but get an "AssertionError" when I do the -r step.

[BTO]

Please help.

I have Rigol MSO5074. I have followed the instructions exactly, but get an "AssertionError" when I do the -r step.

Sure no problem, it's not the first time it's happened. Usually it happens when it's an MSO5000 with BND Options.
or when it's MSO5100 series.
In any case, instead of using the following script

Code: [Select]

rigol_kg2.pydownload and use this one...

Code: [Select]

rigo_kg2_3_000.pyRun it again, As per the response in my previous comment to Dorian_kaf

Try it again and let me know if it works.

[Slats]

Hey BTO, thanks for the quick responce. No luck, still didn't work.

Hardware version: 1.01.000. If that is of any use.

[BTO]

Hey BTO, thanks for the quick responce. No luck, still didn't work.

Hardware version: 1.01.000. If that is of any use.

thanks for the quick responce.

No problem

HERE ARE MY THOUGHTS...
1. No, the hardware version isn't relevant,   You're on Version 1.3.2.2 According to the INFORMATION script.

2. Something fundamental isn't correct, Either
 - you got the wrong I.P. address for the scope
 - The Data stream is disconnecting
 - I doubt it's a python based issue
 - could be that there is an issue with your regen file

3. If you like and have some time we can jump on zoom now and sort this out a lot quicker than what it would be to go and forth with typing.
Would you like to do that ?

I feel, Just a few things need to be checked and i'm confident i'll find the issue and we'll have the scope licenced pretty quickly.

What are your thoughts ?

Also, Are you actually following the PDF or just the quick notes in the forum ?

[BTO]

Hey BTO, thanks for the quick responce. No luck, still didn't work.

Hardware version: 1.01.000. If that is of any use.

Here is a bit of a checklist

don't just skip through this and say   yeah yeah... Actually confirm each step, ok

- When you installed Python did you  do a CUSTOM INSTALLATION ?
- Did you also check the box that says  PATH ?
- then after installing python, did you open cmd.exe or  powershell and typed in

Code: [Select]

python
then press ENTER  to get the compiler screen,
Did you successfully get the screen ?
You can then type

Code: [Select]

exit()  and ENTER   to get out of it

- did you connect your scope to your PC Correctly and with Non Faulty Cables ?
- did you go into the scopes LAN settings and confirm DHCP is on and that the I.P. Address range, Matches the I.P. Address range in your router
when you open cmd.exe and type in

Code: [Select]

ipconfig  then ENTER

- then...   Open cmd.exe   or Powershell, (whichever you like)  DID YOU NOTE THE WORKING DIRECTORY ?
Meaning  if you open it and the path is

Code: [Select]

C:\Users\UserDid you place the script in that location ?   IF NOT.......... DO THAT !

- then when you created the regen file
-- was there another regen file or script in that location ?   if there was.. DELETE IT !

both the script and the regen file need to be in the same location as the working directory path that shows up in Python.
You must also use ONLY
cmd.exe    OR
Powershell

Do not use the Python CLI that comes with the installation.

- After that , You are supposed to ensure that you remove the patch method,  this is done by dropping from version 1.3.3.0  to 1.3.2.2 (you've done this)

- it's then just a question of

Load the -i command
Load the -r command
Load the script without any switch
then shutdown and reinstall 1.3.2.2
then restart and again
Load the -i command
DO NOT DO THE -r again
then load the script without any switch again

At this point it will activate

You seem to be falling over at the regen priv.pem stage
Check the folder locations
and also when redoing all this,  i would use the first script again  not the _3_000.py  one

Let me know if you want to jump on zoom
I'm off to bed now

[Slats]

Hey BTO, thank you for trying. However, I have given up and just used the patch method, which worked perfectly.

I went through your checklist again on my and my wifes computers.

- When you installed Python did you  do a CUSTOM INSTALLATION ?
- Did you also check the box that says  PATH ?

Yes, uninstalled and reinstalled Python.

- then after installing python, did you open cmd.exe or  powershell and typed in "python"
then press ENTER  to get the compiler screen,
Did you successfully get the screen ?

Yes, the Python interpretor loaded.

You can then type "Exit()"   and ENTER   to get out of it

Yes.

- did you connect your scope to your PC Correctly and with Non Faulty Cables ?

Yes. Validated cable was good by coping large files between devices.

- did you go into the scopes LAN settings and confirm DHCP is on and that the I.P. Address range, Matches the I.P. Address range in your router
when you open cmd.exe and type in "ipconfig" then ENTER

Yes, checked the IP and pinged successfully.

- then...   Open cmd.exe   or Powershell, (whichever you like)  DID YOU NOTE THE WORKING DIRECTORY ?
Meaning  if you open it and the path is "C:\Users\User"
Did you place the script in that location ?   IF NOT.......... DO THAT !

Yes.

- then when you created the regen file
-- was there another regen file or script in that location ?   if there was.. DELETE IT !

both the script and the regen file need to be in the same location as the working directory path that shows up in Python.

Yes. Location is corect, with script file in that location. Tried with and without deleting the regen file. Made no difference.

You must also use ONLY
cmd.exe    OR
Powershell

Do not use the Python CLI that comes with the installation.

Used both CMD and PowerShell. Made no difference.

- After that , You are supposed to ensure that you remove the patch method,  this is done by dropping from version 1.3.3.0  to 1.3.2.2 (you've done this)

Yes, did that.

Load the -i command
Load the -r command
Load the script without any switch
then shutdown and reinstall 1.3.2.2
then restart and again
Load the -i command
DO NOT DO THE -r again
then load the script without any switch again

At this point it will activate

Same "AssertionError". Nothing activated.

Thanks for trying, appreciate the effort.

[BTO]

Hey BTO, thank you for trying. However, I have given up and just used the patch method, which worked perfectly.

Sure no problem, i mean , i'm happy to jump on zoom but if you don't want to , then,  ok
as for the patch method,   Yes it does work, the only thing is you'll have to upgrade and repatch manually when the time comes.

in saying that,  I have a DS2000A that when i bought it was on version 1.1.0.0  or something like that
and i literally didn't upgrade for 11 Firmware versions and EVERYTHING WAS FINE

so i reckon you'll be ok with the patch.
so.. You're Welcome for the effort.

[BTO]

UPDATE
ASSERTION ERROR SOLVED

The first thing i want to say here is this....
If you got this error while activating
- You're probably scared
- You're probably discouraged
- You probably don't want to risk bricking your scope
- You're probably saying "You know... JUST IN CASE"

DO ME A FAVOUR.........FORGET ALL THAT OK
Because it's not relevant

Now that being said
I've created another script , it's at the same location.

https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ

The script you need is named :   rigol_kg2_KEY2.py
The PDF File has been updated to include new information relating to the Assertion Error.

Follow the same process as you did before
and you should then find that you get 2 progress bars and no assertion error
and then the scope will be activated with all the options

WE HAVE PROVEN THIS WORKS

Also let me know which scope you have, as this worked on a MSO5072 with no bundles installed.
if you have a MS5100 i do still have another modification i can use on the script, but for now lets' try this one, i reckon it'll work.

NOW ....WHAT IS DIFFERENT IN THIS SCRIPT

An Assertion Error occurs
- When an Assertion is made
- And the Assertion returns FALSE
- Then an ASSERTION ERROR gets put up
- And the entire program HALTS

The reason it returns false is due to a "len" Statement.  which means... The program tested the LENGTH of the HEX Key
in your scope and compared it to the HEX key it was using.
Since the one the script is using is going to replace the one in your scope they need to be the same length.
In your case they were not and as such you get the error

The new script called  KEY2 (as the name suggests) Uses a different key or a different length
and when the challenge assertion is issued it returns  TRUE

SO.. GOOD NEWS GUYS,   WE HAVE A SOLUTION FOR YOU

Do let me know how it goes ok

[BTO]

MSO8000 HAS NOW BEEN HACKED SUCCESSFULLY

I'm putting this post here only because the MSO8000 and MSO7000 Guys are inevitably going to arrive here.

I don't want MSO8000 Discussions to happen on this thread so please PROCEED TO THIS LINK
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso8204-mso8000/msg5555455/#msg5555455

But yeah... Heads up.  THE MSO8000 HAS NOW BEEN FULLY LICENSED and unlocked with all options and up to 2GHz Bandwidth.
I'm not going to say i'm not jealous 
I mean... I helped the guys get to the goal, while i'm on my pityful MSO5000 with my pityful 350MHz   LOL

But yeah, it was cool.. CHECK IT OUT
and i reckon if we have any MSO7000 Guys out there we should be able to help them out as well.

That being said... Let's get back to MSO5000

[jujug28]

I'm getting the AssertionError even with the rigol_kg2_KEY2.py script. So far I've tried upgrading from 1.3.2.2 to 1.3.3.0, patching on 1.3.3.0, and "upgrading" back to 1.3.2.2. I have a brand new MSO5074 with no options other than some trial options that remain even after patching 1.3.3.0 and rolling back to 1.3.2.2. I'm not sure if that is normal, as I haven't found any information about it in other threads.

I'm willing to poke around some more with you if you want.

[BTO]

I'm getting the AssertionError even with the rigol_kg2_KEY2.py script. So far I've tried upgrading from 1.3.2.2 to 1.3.3.0, patching on 1.3.3.0, and "upgrading" back to 1.3.2.2. I have a brand new MSO5074 with no options other than some trial options that remain even after patching 1.3.3.0 and rolling back to 1.3.2.2. I'm not sure if that is normal, as I haven't found any information about it in other threads.

I'm willing to poke around some more with you if you want.

Hi mate
1., You don't need to poke around,  I'll help you
2. You're not gonna find anything anyway if you do poke around
3. in the last few days we've had some big progresses happening

so i reckon we'll do this.
As well as getting the 5000's activated, we can now do 7000's and 8000's as well

Do me a favour...PM ME and we'll make a time to get on skype and i'll help you out

[BTO]

Hi mate
ASSERTION ERROR IS SOLVED
WE HAVE A NEW SCRIPT

1. The script has been Re-Written
2. There is a new Script

Same location
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ
it's called

Code: [Select]

rigol_kg_LicensingUtility.py
Grab it

NOW READ THIS CAREFULLY
(SOME COMMANDS HAVE BEEN CHANGED)

1. it doesn't really matter what version your scope is on

2. Delete and discard of all other scripts that you have and use this one moving forward
   (it will work for ANY MSO5000, MSO7000 and MSO8000)

3. Ensure your working directory has the script copied into it
   and delete all Priv.pem files from it

4. Assume your I.P. Address is  10.1.1.666
RUN -i  INFORMATION

Code: [Select]

python rigol_kg_LicensingUtility.py -i 10.1.1.666
5. RUN -r REGENERATE PRIV.PEM

Code: [Select]

python rigol_kg_LicensingUtility.py -r 10.1.1.666
6. RUN -a ACTIVATION

Code: [Select]

python rigol_kg_LicensingUtility.py -a 10.1.1.666
7. RESTART THE SCOPE

8. RUN -a ACTIVATION........AGAIN

Now your scope will be activated and No Assertion Errors

After this

- Upgrade your scope to the latest version 1.3.3.0  if not already on it
- Do a Self Test
- Do a Self Cal

ENJOY

[BTO]

IF ANYONE IS STILL GETTING ASSERTION ERROR

ASSERTION ERROR IS SOLVED
WE HAVE A NEW SCRIPT
EDIT : This Post has been edited to include the latest script
- it's Faster
- Easier to use
- No need for you to know when to restart

1. The script has been Re-Written
2. There is a new Script

Same location
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ
it's called

Code: [Select]

Rigol_MSO_LicensingUtility_2.09b.pyGrab it

NOTE : It's Based on the 2.09b script by asp, I've made a few changes so it's easier to read and understand what's happening at each stage.
           But all in all asp did the heavy lifting.

NOW READ THIS CAREFULLY
(SOME COMMANDS HAVE BEEN CHANGED)

1. it doesn't really matter what version your scope is on

2. Delete and discard of all other scripts that you have and use this one moving forward
   (it will work for ANY MSO5000, MSO7000 and MSO8000)

3. Ensure your working directory has the script copied into it
   and delete all Priv.pem files from it

4. Assume your I.P. Address is  10.1.1.666
RUN -h  HELP and CREDITS and to familiarize yourself with the commands you will be using.

Code: [Select]

Rigol_MSO_LicensingUtility_2.09b.py -h 10.1.1.666
5. Assume your I.P. Address is  10.1.1.666
RUN -i  INFORMATION

Code: [Select]

Rigol_MSO_LicensingUtility_2.09b.py -i 10.1.1.666
6. RUN -r REGENERATE PRIV.PEM

Code: [Select]

Rigol_MSO_LicensingUtility_2.09b.py -r 10.1.1.666
NOTE : RESTART WILL HAPPEN AUTOMATICALLY
NOTE : ACTIVATION AND LICENSING WILL HAPPEN AUTOMATICALLY
NOTE : RESTART WILL HAPPEN AUTOMATICALLY
NOTE : YOU WILL BE ADVISED WHEN YOUR SCOPE IS RESTARTED AND READY AGAIN

NEW FEATURE ADDED ... REBOOT  (From Command Line) - No Need to press the button

Code: [Select]

Rigol_MSO_LicensingUtility_2.09b.py --reboot 10.1.1.666
ALSO, The Script runs much faster now,  Approx 1min for activation (not 15mins)

Now your scope will be activated and No Assertion Errors

After this

- Upgrade your scope to the latest version 1.3.3.0  if not already on it
- Do a Self Test
- Do a Self Cal

ENJOY

[Dude McGee]

EDIT : New pdf uploaded to include the step that shows you how to install the modules.

Yesterday I have licensed my MSO5074 using your method successfully, thanks a lot! I used the PDF as the basis for the procedure. Worked right off the bat without any problems at all.

I just have one question: Maybe it's my fault but I couldn't find details about the BACKUP DUMP folder. This is not pre-defined in the dataset on MEGA. Furthermore I don't understand how the backup data which is generated by your script can be used later in case I need to restore the scope. And should I put all of the different backup files in just one folder? I have no idea what all of these files are good for and how to organize them.

It is highly unlikely that I'll ever do this but who knows...

And the last question: In case of a return to Rigol, I could just remove all options with your script and reset it to one of the firmware versions, right?

Thanks for taking your time!

[BTO]

EDIT : New pdf uploaded to include the step that shows you how to install the modules.

Yesterday I have licensed my MSO5074 using your method successfully, thanks a lot! I used the PDF as the basis for the procedure. Worked right off the bat without any problems at all.

I just have one question: Maybe it's my fault but I couldn't find details about the BACKUP DUMP folder. This is not pre-defined in the dataset on MEGA. Furthermore I don't understand how the backup data which is generated by your script o restore the scope can be used later in case I need t. And should I put all of the different backup files in just one folder? I have no idea what all of these files are good for and how to organize them.

It is highly unlikely that I'll ever do this but who knows...

And the last question: In case of a return to Rigol, I could just remove all options with your script and reset it to one of the firmware versions, right?

Thanks for taking your time!

ALL GOOD QUESTIONS....

Yesterday I have licensed my MSO5074 using your method successfully, thanks a lot!

- You're Very Welcome, ENJOY IT
Now.. Don't forget a few things

- Do your backups (i'll address that in a second)
- Do your 3 Self Tests
- Do your Self Calibration

Then if you wish to learn how to use your scope in depth, i have around 13 Tutorial videos for you to learn from.  here..
https://www.eevblog.com/forum/testgear/post-hacking-rigol-mso5000-post-hacking-tutorial-deep-dive

OK.. Now..

I used the PDF as the basis for the procedure

- Well Done
I'm in the process of updating the PDF, But hey, these things take time, it should be done in a few days.

See.... That PDF was created around the time when DrMefist0 and tv84 came out with the rigol_kg2.py script (Basically, the second script)
and the PDF was relevant for the 2nd script
then.. We had  a few modifications as a result of... someone had a 70MHz Scope with BUNDLES or they had a 100MHz scope etc etc
and there were slight modifications which resulted in around 4 or 5 scripts in total, but that pdf was still relevant

Then when we got the Assertion Errors and Rigol started playing with the Private Key again with scope models up to around 3months ago....
we altered the script again

THE SCRIPT HAS NOW HAD A COMPLETE OVERHAUL
It's Faster
and as you have seen
it's More Automated
No More Assertion Errors

See... Your scope activated BECAUSE, The script looks at the Private key and the padding and the Length of allocated FRAM
then it does a bunch of stuff that i won't go into detail with ... Basically, we've added more stuff into it that will audit your scope
and check what key length is needed , instead of using the same key length for all (Because that's how Rigol Triggers the Assertion Errors)

Then.. We made the script so..
1. When you select  -r  for Regen of Priv.pem   You don't need to reboot
2. Reboot is now Automatic, if required
3. You also don't need to -a  for Activation,   the script goes ahead and activates Automatically after the generation of the priv.pem file

Basically it does everything for you , You just need to put in   -i   and then  -r
it's kinda hard to get it wrong 

So.. Good work for using the PDF as a basis, at this point
SHORTLY I WILL UPDATE THAT PDF
We are also going to see a lot more people activating MSO5000, MSO and DSO7000 and MSO8000
Because this script looks at your scope and determines which one it is and applies the correct key length

We were looking at having it activate the DHO Series as well, Although at this point, i don't think they work the same way.
but.. WE ARE LOOKING INTO THAT AS WELL.

I just have one question: Maybe it's my fault

- OF COURSE IT'S YOUR FAULT :p  WHY WOULD YOU ASK SUCH A STUPID QUESTION... IT'S ALL YOUR FAULT MATE ... EVERYTHING !!!   

but I couldn't find details about the BACKUP DUMP folder. This is not pre-defined in the dataset on MEGA.

- YES IT IS..!!
it's in Steps 6 , 7 and 8 of the pdf
Here is the link to the cloud

https://mega.nz/folder/OsJyFY5A#8uS0fmepgBdNrXqvnxmFfg

and I HAVE ATTACHED THE PDF FOR YOUR CONVENIENCE

1. Since you're activated, UPGRADE TO 1.3.3.0 Firmware Version,  If you are on that version, it doesn't matter, Get the same file anyway
2. You're supposed to get the UPGRADING TO 350MHZ (1.3.3.0)  Zip File and Extract it
3. After Extraction, you're going to have 3 folders
BACKUP
GEL FILE
FIRMWARE

No Points for guessing which one you're supposed to get   (BACKUP FOLDER)

do that and follow the PDF

So, Since your scope is now fully licensed and Activated, You want to back it all up, JUST IN CASE, something happens.

Furthermore I don't understand how the backup data which is generated by your script

OK...  A BIT OF TECHNICAL JARGON COMING UP
I don't wish to confuse matters, But....

1. For simple backup, You don't use the script, in the first place.... You use the zip file that i provided
2. You put that bugger on a USB stick and stick it in the scope in the pre start menu and hit UPGRADE and it adds the backup files to your USB,
    Then, You copy those files to your computer and save them

NOW, IF YOU WANT TO GO BEYOND THAT.....

3. OK, The script in total, HAS THE FOLLOWING OPTIONS
Which you can achieve by running the script with the -h Switch as follows

Code: [Select]

python Rigol_MSO_LicensingUtility_2.09b.py -h 10.1.1.666
but the switches are as follows

Code: [Select]


INFORMATION (Brings up Basic Information)
python Rigol_MSO_LicensingUtility_2.09b.py -i 10.1.1.666

REGENERATE PRIVATE KEY (Creates the Priv.pem file and places it in the current working directory)
python Rigol_MSO_LicensingUtility_2.09b.py -r 10.1.1.666
(this will in turn trigger the Activation)

ACTIVATION (If you need to do it manually, Only if Priv.pem already exists)
python Rigol_MSO_LicensingUtility_2.09b.py -a 10.1.1.666

Now... All of that is standard stuff
BUT LET'S NOW GET INTO USEFUL STUFF

Code: [Select]

REBOOT THE SCOPE (No Need to press the power button, Restart the Scope from the C.L.I.)
python Rigol_MSO_LicensingUtility_2.09b.py --reboot 10.1.1.666
(FEEL FREE TO PLAY WITH THIS OPTION, it doesn't hurt your scope)

DEBUGGING MODE (adds Extra Useful information if a problem exists)
python Rigol_MSO_LicensingUtility_2.09b.py -d 10.1.1.666
(FEEL FREE TO PLAY WITH THIS OPTION, it doesn't hurt your scope)

Now.. if for any reason we need to debug your scope further and someone gets another Assertion Error
we are going to ask for
1. A DUMP of your FRAM
2. A DUMP of your PUBLIC KEY
so...

FRAM DUMP (Copies your FRAM to a file in your Current working directory)
python Rigol_MSO_LicensingUtility_2.09b.py -f 10.1.1.666
(FEEL FREE TO PLAY WITH THIS OPTION, it doesn't hurt your scope)

PRIVATE KEY DUMP (Copies your Private key to a file in your Current working directory)
python Rigol_MSO_LicensingUtility_2.09b.py -p 10.1.1.666
(FEEL FREE TO PLAY WITH THIS OPTION, it doesn't hurt your scope)

There are other switches such as
-k = Manually Change the Key in Use
-m = Manually change the Model Name in Use
-s = Manually change the Serial Number in Use

it's highly likely we will never need to use these, However, it's just a provision IN CASE the script doesn't Automatically detect the key in use
or Model Name or Serial number, (These options are here JUST IN CASE), it's not even worth explaining it , at this stage.

NOW..... IF YOU WISH TO SSH INTO YOUR SCOPE

Code: [Select]

SSH (Allows you to connect via SSH to your scope)
python Rigol_MSO_LicensingUtility_2.09b.py -e 10.1.1.666

NOW TAKE NOTE
1. This option is put here so you IF YOU NEED TO, You can go in and change certain things or that i can , It's unlikely you'll need it.
2. HOWEVER IT IS FUN TO PLAY WITH IF YOU HAVE NEVER DONE IT BEFORE
3. but TAKE CAUTION
4. So.. If you want to poke around a little,  You can do this....

5. Run the Above command and it will say
"****SSH ACTIVATED****"
"Now..Open PuTTY."

If you don't have it already, Download PuTTY, it's a serial Console that allows you to interface with the scope via a  C.L.I.

6. Open PuTTY
- Enter the IP Address of your scope (Make sure your scope is turn on of course and connected to the network)
- leave the port as 22
Press connect and you'll see a console window pop up

7. You want to now login as root  Your Username and password are either going to be
Username :  rigol
Password  :  rigol
or
Username :  root
Password  :  Rigol201

You won't see the cursor progressing,  Just type it in and press enter  DO NOT PRESS BACKSPACE

if it lets you in, You'll see some more directories, You're going to access the root directory first, it'll be weird

NOW LET'S BRUSH UP ON SOME INSTRUCTIONS

Code: [Select]

cd = Change Directory , But this will fail if you don't specify WHICH directory you want to go to

cd[SPACE][DIRECTORY NAME]
Example :
cd data = This will change the directory location to the "data" folder

cd .. = This takes you BACK one step

cd / = This takes you back to the HOME Directory

ls = List the folders and files in THE CURRENT DIRECTORY

ls la = List ALL the folders and files in the current directory and add a few extra details

so here is what you want to do
AS SOON AS YOU GET THE SHELL AND GET PAST LOGIN

Code: [Select]

cd ..BECAUSE, You're going to be in the root folder and you want to be in the HOME DIRECTORY

Now

Code: [Select]

ls laPRESS ENTER

You might want to look around a little, so.. To see the contents of the home DIRECTORY you use "dir"

Code: [Select]

dirPRESS ENTER, You will see the folders in that directory

Now..
You might want to go to, Let's say...... "data" or  "user" if you want to go to user folder

Code: [Select]

cd userPRESS ENTER

and.. that's how you navigate through the folders
Remember

Code: [Select]

cd ..is to go back to the previous folder

and if you come across a file , you can open the file with

Code: [Select]

od [filename]PRESS ENTER

So if you're game....   Be Cautious and have some fun poking around a bit

to get out, You just type
exit
press enter

NOW...

restore the scope can be used later in case I need it

- I Purposely didn't include that as i didn't want to confuse people, it's also very unlikely to occur
- FOR NOW........BACKUP YOUR SCOPE,   if it happens.... Send me a PM
if it never happens, You'll never need to use it
But it's handy if you brick your scope (which almost never happens)

And should I put all of the different backup files in just one folder? I have no idea what all of these files are good for and how to organize them.

The PDF Explains it
But...
You're going to do 2 Backups
BACKUP 1,  You'll create a folder in your computer called BACKUP SCRIPT
and when you run the backup script,  it's gonna add files to your USB
You place those extra files into the BACKUP SCRIPT on your PC

BACKUP 2, You do the same thing, except the folder is now called NAND SCRIPT.
same thing, Run the NAND SCRIPT and copy the files from the USB to the folder

What are the files good for.
You'll thank yourself when you brick your scope or if the scope fails for some reason.

And the last question: In case of a return to Rigol, I could just remove all options with your script and reset it to one of the firmware versions, right?

OK, SO... EVERYONE ASKS THIS....

We have included two switches that are relevant

Code: [Select]

UNINSTALL OPTIONS (Uninstalls all options in the scope)
python Rigol_MSO_LicensingUtility_2.09b.py -u 10.1.1.666

if however you want to just Uninstall 1 option at a time you use

Code: [Select]

UNINSTALL OPTIONS (Uninstalls all options in the scope)
python Rigol_MSO_LicensingUtility_2.09b.py -o [Option Name]10.1.1.666

Now, if you purchased the scope from Rigol WITHOUT OPTIONS, then you can use

Code: [Select]

python Rigol_MSO_LicensingUtility_2.09b.py -u 10.1.1.666
This will Uninstall ALL OPTIONS and then it will Automatically REBOOT the scope to finish the process.
when you restart you can run  -i to confirm that they are all gone

AS FOR RESETTING FIRMWARE VERSIONS

1. it's not a RESET,  do not view it that way .
it's an UPGRADE or  DOWNGRADE of Firmware Versions

2. So.... if you are on a lower version, Say... 1.3.2.2   and you want to upgrade
    YOU CAN DO THAT DIRECTLY FROM THE SCOPE'S OPERATING SYSTEM
     or
    You can enter the PRE BOOT Menu and select  FIRMWARE UPGRADE.
    To do this you must have a USB Stick with the Higher Firmware Version loaded (Let's say 1.3.3.0)
    This process takes you from 1.3.2.2  to 1.3.3.0

3. You don't need to upgrade or downgrade Sequentially, You can jump from any version to any version, But not the same version

4. Now... if you need to downgrade,   Say from  1.3.3.0  to   1.3.2.2
    YOU PREPARE THE GEL FILE (1.3.2.2)  , it's at the link
     in this case, you cannot do it via the operating system, it won't allow downgrading
     HOWEVER... The preboot menu option that says UPGRADE FIRMWARE   can do it

     You see.... UPGRADE FIRMWARE doesn't mean UPGRADE firmware....... it means   LOAD FIRMWARE

SO YES.... YOU CAN DOWNGRADE THE FIRMWARE

But..
- Since your scope is fully licensed (unlike the Patched version, that would lose the options during upgrade or downgrade)  YOU WON'T LOSE THE OPTIONS
  in the downgrade

- You then need to Uninstall the options

- it doesn't matter if you uninstall them , Before or After the downgrade or upgrade


NOW WHEN YOU GET THE SCOPE BACK FROM RIGOL
Run the script again -r
and it'll just activate the scope as it did before
You then upgrade to the latest version
and confirm that your scope is licensed and activated

and do your Self Checks and Self Cal

LASTLY..........
You are now fully licensed so.....
ANY FUTURE FIRMWARE VERSIONS THAT COME OUT
You can just go to the Rigol Website and get the .GEL file and load it either via the operating system or Pre Boot Menu

AND.......THAT'S PRETTY MUCH IT

ANY QUESTIONS ?

[Dude McGee]

ANY QUESTIONS ?

  At least not at this very moment! Your dedication is awesome, a thousand thanks go out to you for these answers!

I've found the BACKUP DUMP reference in STEP 8 of the PDF, and I'll work further with your latest post and the PDF to understand more of all this. And then I'll be watching the 13 videos you've prepared 

[BTO]

EDIT : New pdf uploaded to include the step that shows you how to install the modules.

Yesterday I have licensed my MSO5074 using your method successfully, thanks a lot! I used the PDF as the basis for the procedure. Worked right off the bat without any problems at all.

I just have one question: Maybe it's my fault but I couldn't find details about the BACKUP DUMP folder. This is not pre-defined in the dataset on MEGA. Furthermore I don't understand how the backup data which is generated by your script can be used later in case I need to restore the scope. And should I put all of the different backup files in just one folder? I have no idea what all of these files are good for and how to organize them.

It is highly unlikely that I'll ever do this but who knows...

And the last question: In case of a return to Rigol, I could just remove all options with your script and reset it to one of the firmware versions, right?

Thanks for taking your time!

NOTE : THE PDF FILE HAS BEEN UPDATED

It can be obtained from here
https://mega.nz/folder/A8cEgQRI#5FSoMrCurJi71T7VkRPgYQ