Products > Test Equipment

Hacking the Rigol MSO5000 - Dr Mefisto Licensing Method

<< < (19/21) > >>

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  :-DD
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:

--- Quote from: jujug28 on June 29, 2024, 03:19:12 pm ---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.

--- End quote ---
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: ---rigol_kg_LicensingUtility.py
--- End code ---

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: ---python rigol_kg_LicensingUtility.py -i 10.1.1.666
--- End code ---

5. RUN -r REGENERATE PRIV.PEM

--- Code: ---python rigol_kg_LicensingUtility.py -r 10.1.1.666
--- End code ---

6. RUN -a ACTIVATION

--- Code: ---python rigol_kg_LicensingUtility.py -a 10.1.1.666
--- End code ---

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

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod