Hantek DSO1152S - Wont boot after firmware update

[WanaGo]

Ok Thanks WanaGo,
I might check for a replacement aftermarket. But first I need to know how to open this scope.
Could tel me how to open it?
It seems that I first need to remove the rubbers on the sides by pulling them but not sure. They are pretty stiff.

Pop the end caps on the rubbers off, which reveals a couple of screws.

[Alfik]

Another question is around the LAN IP address. Every time I power cycle the scope, my IP address is reset back to default. Is this normal? Is there any way to have it remember the IP address, as its a pain in the butt.

Did you solve this problem? I have DSO1062S, fw 2.01.1 (130129.0), hw 1.00.1 and my IP address is reset back to default also.
Thanks

[WH_Mike]

I contacted Hantek and they promptly replied with this message to me:

Just uncompress packet file.
And store packet and emerg.do files to a USB drive, and plug the USB drive to DSO, turn on DSO.
If the DSO can reboot automatically when your upgraded the firmware last time, DSO can recall the factory setup.
Pls try.

With this file: http://www.taktik.co.nz/EEVBlog/packet.zip

Hello WanaGo!
After update my DSO1152S I have loop reboot too.
Do you still have "packet.zip" file from Hantek service?
Previouse link is dead.
If so, can you share it to me?

Best wishes and thanks before.
Mike

[WH_Mike]

Hello friends.
I was able to restore the functionality of my DSO1152S by analyzing the composition of the decrypted firmware archive 170801.
In short, then:
1) I recorded the decrypted and unpacked archive on a USB flash drive.
2) at the end of the failed download, the oscillator closed the operation of the watchdog timer by issuing the killall dsod command
3) created the /tmp folder in the root and copied all the files of the unpacked archive there
4) launched the update script file from the root do_update.sh in the copied archive folder
5) Restarted the oscilloscope.
Voila, everything works!

If you are interested, below is a complete, directed uart log of a single session, including both erroneous commands and correct ones with the results of their processing:

[WH_Mike]

If you are interested, below is a complete, directed uart log of a single session, including both erroneous commands and correct ones with the results of their processing: