Hi BTO,
First of all, thank you for the work that you have put in to this.
Secondly, I have a couple of questions regarding upgrading my scope to the latest version 1.3.3.0.
My scope (5074) has a version of 1.3.0.3 currently with all options enabled via a "hack".
Is it possible for me with version 1.3.0.3, to upgrade to the version 1.3.3.0 by following your guide?, https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-dr-mefisto-licensing-method/
Why do you first upgrade to the 1.3.3.0 and the down grade to 1.3.2.2 and then back up again?
thanks!
BR
Niklas
Hi BTO,
First of all, thank you for the work that you have put in to this.
You're Welcome i appreciate that.
Secondly, I have a couple of questions regarding upgrading my scope to the latest version 1.3.3.0.
OK, so you mean THE PATCH METHOD. No problem.
Is it possible for me with version 1.3.0.3, to upgrade to the version 1.3.3.0 by following your guide?,
YES, ABSOLUTELY, the process would go like this..
Most people these days buy their scopes and it's on 1.3.3.0 , But you are on 1.3.0.3 (Just like when i bought mine)
Obviously you bought your one a while ago, possibly around a year or so ago.
Now.. the patch method doesn't survive upgrades or downgrades so what you would do is this...
- Upgrade to version 1.3.2.2 (Not 1.3.3.0)
- Then you would follow the instruction to applying the script and after your scope is licensed properly
- You would then upgrade to 1.3.3.0
So YES you can absolutely do that , and if you need help i can jump on zoom or something with you
to walk you through the process if you are not confident.
Why do you first upgrade to the 1.3.3.0 and the down grade to 1.3.2.2 and then back up again?
Good Question...
There are a few reasons,
- Firstly as i said most people buy a scope with version 1.3.3.0. Usually MSO5074. and these people like you have their scope's patched.
that being the case...
- Initially there was difficulty on the forum activating on 1.3.3.0
(Granted this could have been user error, in hindsight i can see how mistakes would have been made)
as a result a user decided to downgrade to 1.3.2.2 and then had success with the method
- We downgrade because we have tested the method as WORKING and a secure method
- But that's not the only reason, We could argue that one could now try to license the scope from 1.3.3.0 and personally,
knowing what i know now, i think it'll work. But there is still a problem that being, When the scope is licensed,
HOW DO YOU VERIFY THAT IT WORKED ?
if you are still on the highest version, your only option is to downgrade and see if the options survive. you wouldn't know otherwise.
Therefore we don't bother starting from 1.3.3.0, but instead We start from 1.3.2.2 by downgrading and the downgrade loses the patched options so it saves you doing -u to uninstall
you then license the scope and then to verify that it worked and in the same step to upgrade, you go to 1.3.3.0 to check it.
In the future when a new firmware version comes out it'll be fine to start from 1.3.3.0 , but for now since it's the latest version
we start from 1.3.2.2 but again, we haven't actually tested that the script works from 1.3.3.0 that's just my assumption
but we know it works from 1.3.2.2
After the licensing method however
- You can upgrade and downgrade to any version you want
- You can use the script to uninstall the options if you want
- After you uninstall them you can reinstall them again
- You can also return to the patch method if you like (Although i don't see why you would)
SO FAR WE KNOW THE FOLLOWING
this is verified
The Script
rigol_kg2
has worked on the following models (Bundled Options installed seems to affect it)
MSO5074
MSO5074 with MSO5000 BND
I had one instance of a MSO5104 with MSO5000BND work (but only 1 so far)
The Script
rigol_kg2_3_000
has worked on the following models
MSO5102
MSO5104
This is a list of all the models
MODEL # MSO500 SERIES BANDWIDTH CH's
MSO5072 MSO5 07 2
MSO5074 MSO5 07 4
MSO5102 MSO5 10 2
MS05104 MS05 10 4
MSO5204 MSO5 20 4
MSO5354 MSO5 35 4
The only one's that have not activated so far are
MSO5072 - I assume that since it's just a 2 Ch it will work with
rigol_kg2
MSO5204 - This is likely either going to work on
rigol_kg2_3_000
or i have an idea for another modification.
But i think this will be a rare occurence
MSO5354 - This will likely never happen for obvious reasons
All in all, i think we have all the likely models covered.
I have posted on an MSO7000 and MSO8000 thread, but they dont' seem to have responded.
i think it's unlikely we'll haev 7000 and 8000's but i'm happy to try the script on those if the situation presents itself
for now THE MSO5000's are sorted, Let's get everyone on board.