Crash logs when EDL is activated

[raph3ix]

As it turns out, if the phone crashes and goes into the EDL mode, it can only be re-booted into Android by draining the battery completely.
I could observe it now twice, and in both cases I could reboot without any problems as soon as the battery was empty. You can detect that by plugging in the charger and see if the charging screen turns on or not.

So it would be interesting to know what lead to the EDL mode. Is it somehow possible to get a log for the crash that lead to the EDL mode? Does anyone know a place on the phone were such logs are stored?
Or is it possible to get information from the EDL?

 

[raph3ix]

I tried to create a bugreport using adb bugreport, immediately after the phone was resurrected using the drain battery method...
There are some lines of kernel log before the current boot, but they do not match the time of the last crash...
Also, the kernel log starts with 05.01. 17:58 at time 0, then switches to 30.04. 23:58 at time 16.423927 and then switches to the current time (11.05. 12:55) at time 34.645573.
I guess the device's time was changed two times during boot.

But look whats in the kernel log:

01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] **********************************************************
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] **   NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE   **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] **                                                      **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] ** trace_printk() being used. Allocating extra memory.  **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] **                                                      **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] ** This means that this is a DEBUG kernel and it is     **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] ** unsafe for production use.                           **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] **                                                      **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] ** If you see this message and you are not debugging    **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] ** the kernel, report this immediately to your vendor!  **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] **                                                      **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] **   NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE   **
01-05 17:58:03.297  root     0     0 W klogd   : [    0.000000] **********************************************************

But hey, debug kernel could be nice to trace down this issue :laugh: