Hantek DSO1202e stuck in boot/recovery loop

[mrmax]

Hello,
My Hantek DSO1202e (s/n DSO1201169) was working but now on power up, it gets stuck in a boot/recovery loop as documented below. I was hoping something from the extensive DSO2D10 threads would apply and help, but no luck so far. 
I sent a message to Hantek support, but have received no response.
Can't seem to communicate with it from PC to USB port (using the "DSO Measurement Device" device that does briefly pop up in Device Manager and then goes into a "failed" state). 
Also tried booting scope (and also choosing "Recover" from the boot menu) with Hantek's firmware image (dso1kb_func_hantek_dso_dso1202e_20160329.0.up) on USB stick but no luck.
Does anyone know how to restore firmware or software on this unit?

On power up:
############
System is not shut down properly last time, please select the start-up mode
Press F1 to reboot the system
Press F2 to recover the system
Press F3 to update the recover partition

#############   Pressing F1: reboot ###############
The scope reboots to a blank screen and the AutoRange and Run/Stop buttons are lit.
Nothing further occurs, even after hours in this state.

#############   Pressing F2:  recover ###############
The following sub menu is displayed:
System recovery will reset the oscilloscope back to factory default setting
Press F1 to confirm
Press F2 to return

###Pressing F1 displays:
System is recovering...
Please do not turn off the power!

After displaying this for a few minutes, the scope reboots to a blank screen and the AutoRange and Run/Stop buttons are lit.
Nothing further occurs, even after many hours.

#############   Pressing F3:  update recover partition ###############
The following message flashes very briefly:
System is updating...
Please do not turn off the power!

Operation failed!
...is displayed for a second before it returns to the main boot menu above (F1, F2, F3 options)

Thanks for any help or insight!
Max

[eM]

Hi, I have the same fault on my DSO1202E. Did you manage to solve the problem?

[mrmax]

Seems like a few of us are suffering from this 

I progressed to connecting an FTDI adapter to the motherboard and was able to access the low level interface.  However, it is a "menu" of things you can do (limited shell?), and not the native OS (linux variant).  I was unable to break out of that and get to the OS so I still have not been able to reflash with a functional scope image.