Initially it did not worked for me from the first time as well.
Keep pressing "SINGLE" key at the same time as you Power On.
You should see two options at the top right corner.
How long did you hold pressed the SINGLE key? At what time the menu popup ? Do I need to release it at particular moment.
It doesn't work for me, I tried several times - my Boot: 2018.06.27
Initially it did not worked for me from the first time as well.
Keep pressing "SINGLE" key at the same time as you Power On.
You should see two options at the top right corner.
How long did you hold pressed the SINGLE key? At what time the menu popup ? Do I need to release it at particular moment.
It doesn't work for me - my Boot: 2018.06.27
Press "SINGLE" button multiple times until you see additional menu items.
If progress bar is in the middle this indicates that you missed it - start over again (turn off & on).
Initially it did not worked for me from the first time as well.
Keep pressing "SINGLE" key at the same time as you Power On.
You should see two options at the top right corner.
How long did you hold pressed the SINGLE key? At what time the menu popup ? Do I need to release it at particular moment.
It doesn't work for me - my Boot: 2018.06.27
The trick is to
Press "SINGLE" button multiple times until you see additional menu items.
If progress bar is in the middle this indicates that you missed it - start over again (turn off & on).
It works from first time
The trick is to pressed it Multiple times rapidly - I was just holding it
A Big thank you!
Interestingly when you use the web interface the options list shows many with the demo time.
Haha I was waiting for somebody to notice this. The check function exists twice, and I missed it back when I did the patch. Better luck next time
For now I don't want to change the patch anymore, since it is well tested by now. Maybe I or somebody else will do one based on my lua package?
Hi,
It seems, that the trial time for the options at my 5074 was running out - no decoder functions avaible, except parallel-bus ( hm? )…
So I want to try the hack.
There´s so much written here in the last days ( and so much I don´t understand), so a little summary would be nice.
What must I do to get the options, actual ?
Are there any risks, like this overshoot Thing ( which I don´t have ) ?
A short explanation would be fine .
Martin
Please find a script for automatic backup of the /rigol/data directory attached. It is based on oliv3r's work, but adds status output to know things work.
EDIT: Fix to backup script to make it more reliable.
Current best practice:
First: You will perform a series of upgrades. These have to be done using the help menu and the
DS5000Update.GEL filename. The files you download here have a .txt extension. Remove it and rename it to the proper name. Attention, Windows might just hide the .txt extension! Make sure to properly unmount your USB drive, and that there is free space left on it (<50MB).
Now:
- Note your current software version down. If it is older than 01.01.04.04 you will need to upgrade.
- Backup your scope specific data such as calibration values. Get the DS5000Update_backup.GEL.txt from here. Rename to DS5000Update.GEL and put it on a USB drive. Execute an upgrade using the help menu in your scope, NOT the secret menu. You will see the scope doing a backup. Unplug the stick and make sure you have a backup in the data_backup folder on the stick.
- If you have an older version of the firmware, download 01.01.04.04 from here. Also rename it to DS5000Update.GEL, put it on your usb drive, and upgrade.
- Make sure you are on the 01.01.04.04 firmware in the about dialog.
- Patch the scope to have all licenses. For that download the patch from here. Again rename and copy to usb drive. This time the upgrade might take a bit longer, it should ask you to reboot, if not something failed, but it is probably not fatal for your scope, no worries. Reboot.
- Check that all licences are activated.
- If you want, do an auto calibration and check that everything is still okay.
You can get temporary SSH access by executing
this upgrade. The upgrade will "fail", but you will have ssh until reboot. You can use this to fix your calibration data, if truly required.
Are there any risks, like this overshoot Thing ( which I don´t have ) ?
The risks are minimal. As long as you have done the backup, there is always a way to get back to where you are. The most important things is probably to use a clean USB drive and unmount it properly in your computer. Even then, most actions are with checksums and will fail before doing damage.
Thank You !
I already got the 01.01.04.04 Version (and wonder, why it isn´t on the webpages of rigol U.S. or europe), will try it tomorrow.
When a new FW is there and upgraded to the scope, the hack will be gone, I guess ?
When a new FW is there and upgraded to the scope, the hack will be gone, I guess ?
Yes. with no trace left. Somebody will need to create a new patch then.
So it is a difference between installing the options buying - which stays forever.
It would be helpful I guess, when someone buy the option-bundle (or even one) and let the cracks having a look on it.
So it is a difference between installing the options buying - which stays forever.
It would be helpful I guess, when someone buy the option-bundle (or even one) and let the cracks having a look on it.
Of course, real licenses are the only thing that will be future-proof...
The trial licenses that everybody has are sufficient to see how they are done. The .LIC files are basically ECDSA Signatures.
Those signatures are verified with the PubKey in KEY.DATA file.
Is there a good solution to have SSH enabled on each boot?
Of course, real licenses are the only thing that will be future-proof...
If I buy the option-bundle, having you or other a look on it - I will get the 350Mhz and 200 Mpts for free and "ever" from you/them.
Deal ?
Seriously, I´m thinking long time about to do this and bandwith-upgrades are too expensive....
Hi mabl,
Thank you so much for the concise summary, much appreciated (I am sure numerous others feel the same).
One quick question, does the DS5000Update_backup.GEL also backup other data other than the calibration data? I understand some files could be lost as part of the patch (I believe the license file being one of them, is there others?), it would be nice if this backs up all the files that could be lost so we can do a full rollback/restore if needed.
Thanks in advance.
Current best practice:
- Note your current software version down. If it is older than 01.01.04.04 you will need to upgrade.
- Backup your scope specific data such as calibration values. Get the DS5000Update_backup.GEL.txt from here. Rename to DS5000Update.GEL and put it on a USB drive. Execute an upgrade. You will see the scope doing a backup. Unplug the stick and make sure you have a backup in the data_backup folder on the stick.
- If you have an older version of the firmware, download 01.01.04.04 from here. Also rename it to DS5000Update.GEL, put it on your usb drive, and upgrade.
- Make sure you are on the 01.01.04.04 firmware in the about dialog.
- Patch the scope to have all licenses. For that download the patch from here. Again rename and copy to usb drive. This time the upgrade might take a bit longer, it should ask you to reboot, if not something failed, but it is probably not fatal for your scope, no worries. Reboot.
- Check that all licences are activated.
- If you want, do an auto calibration and check that everything is still okay.
You can get temporary SSH access by executing this upgrade. The upgrade will "fail", but you will have ssh until reboot. You can use this to fix your calibration data, if truly required.
So it is a difference between installing the options buying - which stays forever.
It would be helpful I guess, when someone buy the option-bundle (or even one) and let the cracks having a look on it.
Of course, real licenses are the only thing that will be future-proof...
The trial licenses that everybody has are sufficient to see how they are done. The .LIC files are basically ECDSA Signatures.
Those signatures are verified with the PubKey in KEY.DATA file.
OK, then just patch the KEY.DATA PubKey to whatever?
One quick question, does the DS5000Update_backup.GEL also backup other data other than the calibration data? I understand some files could be lost as part of the patch (I believe the license file being one of them, is there others?), it would be nice if this backs up all the files that could be lost so we can do a full rollback/restore if needed.
Yes it backs everything scope specific up, including licenses. Regarding loosing things, only the actual firmware upgrade has been observed messing with it, not the license patch.
OK, then just patch the KEY.DATA PubKey to whatever?
Sure, could do. "All Roads Lead to Rome". But you will loose compatibility to original keys, and that is what you initially wanted.
One quick question, does the DS5000Update_backup.GEL also backup other data other than the calibration data? I understand some files could be lost as part of the patch (I believe the license file being one of them, is there others?), it would be nice if this backs up all the files that could be lost so we can do a full rollback/restore if needed.
Yes it backs everything scope specific up, including licenses. Regarding loosing things, only the actual firmware upgrade has been observed messing with it, not the license patch.
OK, then just patch the KEY.DATA PubKey to whatever?
Sure, could do. "All Roads Lead to Rome". But you will loose compatibility to original keys, and that is what you initially wanted.
If we get full access do we care if KEY.DATA is replaced with a bogus pubkey that we know the privkey to? As long as you can patch it back to Rigol's keypair, all's good
OK, then just patch the KEY.DATA PubKey to whatever?
A "special" whatever...
it would be nice if this backs up all the files that could be lost so we can do a full rollback/restore if needed.
I've said this before:
The only thing that is necessary to backup is the /rigol/data directory. With that you can erase everything in the scope and recreate it from scratch.
Edit: This thread is so full of OT BS that people forget the essential. Remember:
https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg2083927/#msg2083927
OK, then just patch the KEY.DATA PubKey to whatever?
A "special" whatever...
Of course. Does anyone know the key algo that Rigol uses? Might be easier to just generate our own licenses after patching the firmware
Current best practice:
- Note your current software version down. If it is older than 01.01.04.04 you will need to upgrade.
- Backup your scope specific data such as calibration values. Get the DS5000Update_backup.GEL.txt from here. Rename to DS5000Update.GEL and put it on a USB drive. Execute an upgrade. You will see the scope doing a backup. Unplug the stick and make sure you have a backup in the data_backup folder on the stick.
- If you have an older version of the firmware, download 01.01.04.04 from here. Also rename it to DS5000Update.GEL, put it on your usb drive, and upgrade.
- Make sure you are on the 01.01.04.04 firmware in the about dialog.
- Patch the scope to have all licenses. For that download the patch from here. Again rename and copy to usb drive. This time the upgrade might take a bit longer, it should ask you to reboot, if not something failed, but it is probably not fatal for your scope, no worries. Reboot.
- Check that all licences are activated.
- If you want, do an auto calibration and check that everything is still okay.
You can get temporary SSH access by executing this upgrade. The upgrade will "fail", but you will have ssh until reboot. You can use this to fix your calibration data, if truly required.
Ive upgraded to the newest firmware but when I upload the patch (with renaming) scope says fail to update please check package
Current best practice:
- Note your current software version down. If it is older than 01.01.04.04 you will need to upgrade.
- Backup your scope specific data such as calibration values. Get the DS5000Update_backup.GEL.txt from here. Rename to DS5000Update.GEL and put it on a USB drive. Execute an upgrade. You will see the scope doing a backup. Unplug the stick and make sure you have a backup in the data_backup folder on the stick.
- If you have an older version of the firmware, download 01.01.04.04 from here. Also rename it to DS5000Update.GEL, put it on your usb drive, and upgrade.
- Make sure you are on the 01.01.04.04 firmware in the about dialog.
- Patch the scope to have all licenses. For that download the patch from here. Again rename and copy to usb drive. This time the upgrade might take a bit longer, it should ask you to reboot, if not something failed, but it is probably not fatal for your scope, no worries. Reboot.
- Check that all licences are activated.
- If you want, do an auto calibration and check that everything is still okay.
You can get temporary SSH access by executing this upgrade. The upgrade will "fail", but you will have ssh until reboot. You can use this to fix your calibration data, if truly required.
Ive upgraded to the newest firmware but when I upload the patch (with renaming) scope says fail to update please check package
Did you read the last sentence? (highlighted)
Ive upgraded to the newest firmware but when I upload the patch (with renaming) scope says fail to update please check package
If you are talking about the license patch. This is strange. It is the first observed failure. I could only recommend trying again with a freshly FAT32 formatted usb drive. (It uses the drive as space for intermediate patching results, so there should be space.) If this does not work, you either have to wait for a new patch with better debug output on the screen, or ssh in and execute "/rigol/shell/update.sh /media/sda1/DS5000Update.GEL" and report back any failures you see.
I already got the 01.01.04.04 Version (and wonder, why it isn´t on the webpages of rigol U.S. or europe)
Now it´s launched:
https://www.rigolna.com/products/digital-oscilloscopes/MSO5000/Including upgrade instructions and release notes.
Fun fact : At rigol europe page you must "register" (Name, Email, Model, Serialnumber) before you can download it.