DSOX2000 and 3000 series - licence , have anyone tried to hack that scope ?

[EE-digger]

This might be a little old but looks like Keysight have new app bundles. Here is links related to 3000 A/T X-Series:

OLD: DSOXT3APPBNDL $3600

NEW: D3000BDLA $2530

I compared the app/software packages contained in each (listed in the brochure on each page) and didn't notice any difference.  Are they the same and this is just a revised SKU?  The new one is significantly cheaper -- is it missing something?

Or have the apps been revamped with new capability and you can only get it with purchasing the NEW app bundle?  I hope not!!

Anyone know details of this?

Similar situation for the 4000A series.

A little late on the reply here but I discovered that these ultimate bundles DO NOT INCLUDE WAVEGEN or the DUAL WAVEGEN2    

But the new ultimate bundle plus wavgen add up to a bit less than the old full bundle (at least for the 4000A).

Edited to remove all rant material 

[cgz2001]

theSteve,

I have spent hours on this thread and am having trouble getting the information I need (I'm new to this).

1.) I have a DSOX2002A which will not boot up.  I'm not interested in hacking the instrument but rather simply getting it working again.
2.) I don't have a telnet ability as I don't have the LAN option installed.
3.) I also cannot find winCE cab manager 3.0 on the internet.

What steps can I take?  Can I simply place the .cab file onto a flash drive, formatted to FAT32, with the .txt file as previously indicated with 'TRUE' placed inside to boot up the instrument through the USB drive?  I suspect I need a link file in the USB drive but I am not clear on this.  Can you help me out?

[TK]

It probably has the NAND Flash problem, you could send it to Keysight for a free repair.

[TheSteve]

Once in a while a NAND corruption issue can be fixed solely with a USB drive. When that isn't possible the lan option is preferred but the recovery image can be transferred via the serial connection.
If you did want to try fixing it yourself the first step would be to post exactly what it does, and then connect to the internal serial port.
As TK mentioned Keysight will often fix a NAND corrupted scope for free so may want to use that option.

[Ordinaryman1971]

does anybody have a usb stick with "all I need" on it so I can upgrade my poor dsox3034a

[Hydrawerk]

DSOX2000 series is 9 years old now. Will Keysight release a new model soon??
Dave´s video was released on 15. 2. 2011

[myhobo]

do you have msox4000 firmware version 7.20.20171026

[jrgandara]

Hello all!

Need a little help from who have all this huge thread fresh in mind. 7 years ago I successfully re-flash my DSO-X2004A with the hack. Have being working great until last week when I get this message: "System concerns detected: OS version is not correct. Please reload system firmware". I ignored the message and keep using it. Today it will not boot. I tried reboot several times and finally it boot again with that system concerns alert". Well, it is time to take care of this problem before it stops completely.

I recall at that time to telnet the scope for the modified firmware. I get my files from that time and in the instructions say telnet the scope... Well, looking at the back panel, there is not LAN port. So I´m wondering if I did that of other manner, like with flash drive, or really by telnet. Reading my old instructions says telnet... But how? I´m very confident with a firmware update will fix this problem. So I have the following questions:

1) I really need a LAN board now? Why in the past it was not needed?

2) Is possible to do this using flash drive by the USB port?

2) How do you recommend perform this task today?

Ps: My firmware version is 2.35.20013061800

Thank you!

[Mr. Scram]

You don't need a LAN board any more, just a prepared thumb drive. See the message linked for the steps. I've seen that system concerns message before but I'm uncertain whether the booting issues might spoil your fun.

https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg2364363/#msg2364363

[jrgandara]

Wow! Thank you a lot Mr. Scram!

You save me a lot of trouble. I remember last time a lot of reading to realize the correct procedure. This recipe is great! I will let you know later if fix the problem.

[jrgandara]

Successfully updated and the firmware error message gone.

Thank you again!!!

[Mr. Scram]

Successfully updated and the firmware error message gone.

Thank you again!!!

I'm glad things worked out!

[sbvr4]

Hi all,
I have a DSOX3024T fw 7.20 that I am currently trying to access via Telnet. I am using a 3rd party LAN card. The screen displays System Concern: Faulty Network Card at start up. When I check the network settings, it displays a Network Failed status. Occasionally it will work right and display the IP address. Has anyone experienced this issue? May be my cheap RJ45 to usb converter.

Also, Does fw 7.20 end telnet access after booting, like 7.30? If so, what is the timing for accessing prior to the port being turned off at boot up? Has everyone changed the IP to a static address, so to enter it in Telnet prior to the unit booting? I only get the login failed notification after entering
login: infiniivision
pw: _________   

Any help would be greatly appreciated.

Thank you

[EE-digger]

The 3000T with 7.20 does not timeout on access via Telnet.  Only for the T series, you do need to generate an appropriate PW.  Search the thread as it's easy to find.  I've always run a static IP.

Sorry can't help with debugging of the card.

[Pinkus]

......I have an original Keysight VGA+LAN card for the DSOX2000/3000 (a or T) series for sale......
Edit: Sold within minutes to a nice eevblog member from Hamburg.

[sbvr4]

Does the 4k patched file also work for MSOX3000T series  (because it has the same firmware revision number and date)?

Thanks in advance, Josef

Hey All,

the 3000T series is NOT quite the same, at least for the DLL, so here is the patched image for the 3kT series...7.20.2017102614

*** please notice:  3000T firmware is:  7.20.2017102614  *** (notice the 614 ending! ***
(*** 4000A firmware is:  7.20.2017102615  *** (notice the 615 ending! ***)


(same as before, patches and checksum already done)

Code: [Select]

1) options patch:  0x486f3c  --> "04 00 A0 E1" --> "00 00 A0 E3"
2) nag patch:      0x4f22c8  --> "A8 F1 93 E5" --> "01 00 A0 E3"

just unzip this file, and flash it to your scope (*MUST* already have the above firmware installed!)


http://www.mediafire.com/file/y18w4c6hxw85jt8/3kT_7.20_nk.bin.zip


MD5 of the extracted .comp file:  <1B 76 32 CE FF 69 62 85 38 20 D3 E6 D2 5F E4 BC>

Thank you all for making this possible.
How should I go about flashing my 3000T with the patched firmware? I currently have the the unpatched  7.20.2017102615 loaded. I unzipped the .comp file and loaded it on a USB, but my scope doesn't recognize the file type. Any help would greatly appreciated. I need to do some more research. Sorry. 

Thank you
sdvr4

[jake111]

Hi All,

I've recovered my DSO-X 3034A that suffered the crappy NAND problem.  However now my serial number and model number are gone.  Haven't had luck in getting the SCPI commands to set these from Keysight contact, does anyone know these commands?  I have found them for many other products but not these.  I assume they don't publish them to prevent duplication of serial numbers and corresponding multi-machine use of the same license key, however with these scopes being hacked six ways from sunday, I'm hoping someone here knows them and can help me out.

Otherwise, should I assume it's time to start digging through the firmware?

Or maybe someone knows the memory address where they are stored (must be in NAND?) and I can reconstruct this area from a dump that someone could kindly provide in exchange for my eternal gratitude

[SrS]

If you have access to the console you should have a hidden directory "\secure\cal" containing:
sernum.dat
framecal.dat
callog.txt
factorycal.dat

However the file doesn't contain the serial number in the usual format but might be worth experimenting, replace the '#' in attached file with numbers (ASCII)
Or try to get the first public firmware update and read from here
Both methods are untested AFAIK

Hope your cal data is still intact

[kawal]

Thank you all for the knowledge.
Another successful hacked DSO-x-2012A  using USB only . 
The trick is to have files in the main directory not in any sub folders. It fails every time when files are not in the main directory.

 
I followed these instructions from page 89  written by scribble - thank you man - much easier to have it all in one place.


Download Phillyflier's patched firmware from post #2167 on page 87
Download Luminax's license patch from post #1529 on page 62
Extract license patch, open cmd window (if using MS Windows), navigate to license patch folder and rename infiniivision.lnk to .txt
Edit infiniivision.txt and replace text in the file with Odessa's modification from post#2197 on page 88
80#infiniivisionLauncher.exe -l DIS -l MSO --perf -l BW20 -l SCPIPS -l CABLE -l VID
Save and rename file back to .lnk
Copy firmware file (rename from .ksx to .cab if current scope fireware is older than v2.41) to FAT32 formatted USB drive
Copy licence files (2x .cab files and .lnk file) to same USB drive

Now go to your scope, turn on and plug in USB drive to front USB port
Press [Utility] > File Explorer, select the firmware file (3000XSeries.02.50.2019022736_patched.cab); then, press Load File, wait for scope to load and reboot.
Check firmware has updated to v2.5, if successful continue
Press [Utility] > File Explorer, select v241_link_install.cab file; then, press Load File, wait for scope to load and reboot.

[TK]

DSOX 1000X Series:  FW:  01.20.2019061038_patched  https://mega.nz/#!DuIxzA7Q!8wYfTlHPuc4hF3UFPLoq0FOgylfsSVur4B5YSdCTn2I
md5: <5A48A3492AD5BB23336236FDC6A12738>

AFAIK DSOX 1000X Series cannot be hacked using the infiniivision.lnk method.  The only known software hack is the modded firmware by FARCSA.

[Pinkus]

Please let me know if there are any issues with any of these!

Unfortunately on a DSOX4000a: yes, there are issues
I had a (working) patched 7.20 before and installed your 7.30 with the result that the scope showed an error message (corrupted firmware) during the boot process. Next try will be a manual installation of your patched xxx.comp file ... but due to lack of time it will have to wait.
EDIT: I took the time and installed the original 7.30 (scope was working then) and then to write only the patched nk.bin.comp file (extracted from your patched KSX file) to the system like I did with the 7.20 firmware. Same result: after booting up -immediately after the Keysight logo is shown- the error message appears.

[Pinkus]

It works now. Thanks a lot!
Photo shows Firmware V7.30 with the new digitizer option where memory depth and sample rate can be selected manually (though time will show if this is really useful, as the scope did/does a good job by selecting it automatically so far and I seldom missed the manual option).

[EE-digger]

Thank you PhillyFlyers ! ! !

Keysight posted 7.31 just 4 days ago and the 7.30 cab is gone.

Just a reminder to always archive every new version 

[PhillyFlyers]

Thank you PhillyFlyers ! ! !

Keysight posted 7.31 just 4 days ago and the 7.30 cab is gone.

Just a reminder to always archive every new version 

Wow, they released that fast, strange, as the changelog for 7.31 was kinda small.. oh well.. 7.31 was released for both 4000x and 3000x, so I put those two up in my post as well..

[EE-digger]

I'm getting the firmware error message for 7.30 on a 3000T.  Does that also have a checksum problem?

Thanks for the 7.31 update.  This is awesome