I see two ways forward. Recover data or replace the system image.
Assuming you have a certain amount of essential data backed up I would go for the second. The risk will be not too much more than a usual /e/OS update (unless something else is the underlying cause of the fail). I have to wonder if there is any reason why you are a few months behind with updates?
You say " e.1.10 stable avicii" (please confirm for yourself that you were running Android S, as listed in this link https://images.ecloud.global/stable/avicii/. You could download the e-1.10-s again as a replacement, or take the opportunity to update.
Now reflash the phone, this is the method for a manual update.
Boot into Recovery
Select Apply Update and in next screen Apply update from adb
In the next screen, the device is now in sideload mode
Note at this point the Cancel option is highlighted that does not mean you have canceled the action. The device is in adb sideload mode.
On your PC begin adb sideload.
Type the below command in a console
adb sideload downloaded_file_name.zip
Replace downloaded_file_name.zip with the name of the /e/OS file you downloaded.
Press enter key on the keyboard to start the sideloading The screen will show the progress percentage…This might pause at 47%
Give it some time
The PC console will now display Total xfer: 1.00x
The phone screen will now display some text with a message similar to
Script succeeded result was [1.000000]
This means that the install was successful.
In /e/OS recovery main screen:
Select Reboot system now
The reboot process may take 5 - 10 minutes