There are four scenarios, and for each of them, it is recommended to have a slightly different setup and way to send them to our MOBILedit Forensic Support team for analysis.

Please note, the logging settings apply to subsequent extractions and must therefore be entered before starting the extraction of the device for which you want to log.


Device communication error

In the case that you have followed all the instructions to connect your device and your device is still having trouble connecting to MOBILedit Forensic, the Basic Log level will be appropriate.

How to set the Basic Log level

How to send Logs to MOBILedit Forensic Support for analysis


Potentially incorrect or non-standard data in the device

In cases of suspected incorrect or non-standard data contained in the connected device, the Detailed Log level will be appropriate.

How to set the Detailed Log level

How to send Logs to MOBILedit Forensic Support for analysis


A software bug in MOBILedit Forensic

In case you need to report a software error in MOBILedit Forensic, the Debug Log level is appropriate.

How to set the Debug Log level

How to send Logs to MOBILedit Forensic Support for analysis


MOBILedit Forensic crashes

In the event that MOBILedit Forensic crashes, Crash Dump files are automatically generated and can be sent to the MOBILedit Forensic Support Team for analysis.

How to send Crash Dump files to MOBILedit Forensic Support for analysis


Summary_full.txt

File summary_full.txt contains all information that was presented on the screen in the white log window, together with all files copied from the phone, and if the password breaker has been used then it contains the resultant password as well.


Summary_short.txt

In the summary_short.txt there is the info of the extraction phase, together with a list of failed items indicating what might be missing in the report, such as skipped folders. The contents of this file are also included in the HTML and pdf reports in the Data Extraction Log section.


Profiling