MTK full dump grab

Environment building

notes ： everything dump Based on brushing debugpolicy (boot_para.img)
Check whether to brush debugpolicy
command

adb shell getprop ro.boot.dp
 perhaps 
adb shell
getprop | grep boot.dp

See what to print
Compare enumeration information
Code path ：vendor/mediatek/proprietary/bootable/bootloader/lk/include/dev/mrdump.h

enum {
    
	MRDUMP_SUCCESS_ENABLE = 1,     //usr edition , Need to brush in 
	MRDUMP_ALWAYS_ENABLE = 2,      //userdebug  No need to brush 
	MRDUMP_RUNTIME_DISABLE = 3,    
	......
	};

Generate boot_para.img Look at what I have written before
Generate boot_para.img

Check what is on dump
Code path ：vendor/mediatek/proprietary/bootable/bootloader/lk/app/mt_boot/aee/mrdump_dconfig.c

// Check whether mindump still fulldump
int aee_check_enable(void)
 {
    
   #if MTK_AEE_LEVEL == 1
	int val = AEE_DEFAULT_SETTING;
	const char *params = dconfig_get_env("aee_enable");

	if (params != NULL) {
    
		if (strcmp(params, "mini") == 0) {
    
			val = mrdump_check_enable() > MRDUMP_ALWAYS_ENABLE ? AEE_ENABLE_MINI
				: AEE_ENABLE_FULL;
		} else if (strcmp(params, "full") == 0) {
    
			val = AEE_ENABLE_FULL;
		} else if (strcmp(params, "no") == 0) {
    
			val = AEE_ENABLE_NO;
		}
	}

Why install GAT and SpOffineDebugSuite

When the phone restarts 、 We should analyze the crash problem , however dump There is a large amount of information. It is very inconvenient for us to check ,
At this time, we can use these two tools for brief analysis , Error information extraction .

Environment construction and use

I have written in my previous documents. You can refer to :
MTK be based on GAT Tools and SpOffineDebugSuite Tools dump Grab and parse

Practice is the only criterion for testing truth

Trigger dump front

First check is internal-storage（ Internal storage ） still usb
Internal storage crawl ****************** The mobile phone can be turned on normally
command

adb root
adb shell  
mrdump_tool output-get

The following figure shows internal storage ,

After triggering the orange screen, it will automatically grab
And then take it. pull Just come out

=================================================================================

However , Some problems lead to panic After that, the machine will be restarted , This makes it impossible to use adb pull From the machine pull Out of the above dump file
At this time, we need the following
usb Grab *********************** The mobile phone cannot be turned on normally
Get into fastboot Mode access usb
Set up USB
command

adb shell  mrdump_tool output-set usb

Let's look at... Again
command

adb shell  mrdump_tool output-get

As shown in the figure below OK 了

Download the attached compressed package , Execute the following command to crawl in the extracted path dump：
command

mrdump_host_cmd.exe getcore -o coredump.zip

Tool accessories ：mrdump_host

Manual trigger panic, Make it enter the orange screen to grab dump

command

adb root
adb shell 
echo c > /proc/sysrq-trigger

notes ：full dump Crawling is a long process , If the orange screen flashes and restarts, it indicates that the capture is min dump , Grab failed
As shown in the figure below FASTBOOT_mode, Just explain OK 了 , Wait for him to finish crawling and restart .

After grabbing
dump Storage path ：/data/vendor/aee_exp

aee_exp There is KE The document OK 了