I hope no total failure 4.2″ ESPaper Plus Kit

Question

Recently I ordered and received the 4.2″ ESPaper Plus Kit. Unpacked, switched on, configured, account set up, screen defined, everything will be fine until then.

In the evening of 23.12. I noticed that the battery was probably already empty and so of course no more updates can be seen. So I switched to off and connected the 4.2 for loading.

A few hours later I switched the 4 back on, but no reaction(s)

Various procedures performed.

1. left button and right button procedure (ConfigReset) - NOK
   here was briefly my stored SSID name (M1K3Weather) in the WLAN to see,
   no possibility to connect (...Error occurred during connection.
   I have tried this from different clients 
   Nothing has changed on the 4.2 display.
2. LeftButton and PowerON Procedure - NOK
   No reaction in WLAN 
   Nothing has changed on the 4.2 display.
3. current client downloaded and reloaded.
   According to the Arduino IDE this worked without errors,
   No WLAN SSID
   Nothing has changed on the 4.2 display.
4. procedure 1 and 2 tried several times but no success

Ask now what else can I do from my side, test.

Comments

Please plug in the USB-to-Serial converter ("programmer"), hook it up to your PC or Mac via USB and report the output from the serial console.

---

Today i switch ON after many Days without reaktion my ESP4.2

Screen is change from my Weather to ThingPulse Welcome Screen ...
I can see the SSID ESPConfig

I Find an readable Output on Serial Monitor at 74880 Baud after Reset ESP4.2
Fatal exception (28):
epc1=0x4025d4da, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000100, depc=0x00000000
Fatal exception (28): ...

After Switch OFF/ON
load 0x4010f000, len 1392, room 16
tail 0
chksum 0xd0
csum 0xd0
v3d128e5c
~ld

Output When i press Config & Reset Procedure:
ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1392, room 16
tail 0
chksum 0xd0
csum 0xd0
v3d128e5c
~ld
Fatal exception (28):
epc1=0x4025d3c1, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000044, depc=0x00000000
Fatal exception (28):
epc1=0x4025d3c1, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000044, depc=0x00000000
Fatal exception (28):
epc1=0x4025d3c1, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000044, depc=0x00000000
Fatal exception (28):

---

I cant connect to SSID ESPConfig

Actual i bcome no SSID From ESP4.2

---

Now that's definitely odd.

A) What you're seeing at 74880 baud is the ESP8266 boot message (details: https://github.com/espressif/esptool/wiki/ESP8266-Boot-ROM-Log). Everything else should be gibberish. The regular output from our application is at 115200.
B) Why would it now start crashing when it's been running smoothly for days or weeks before it ran out of battery? Did anything out of the ordinary happen in between?