Database Develop

[Q] Logcat - Heap size overflow's

Hi
I can't debug my apps because logcat does not work correctly.
It prints a lot of AudioCache overflows, but my own logs never show up.
Code:
E/AudioCache( 1053): Heap size overflow! req size: 1056768, max size: 1048576
E/AudioCache( 1053): Heap size overflow! req size: 1056768, max size: 1048576
E/AudioCache( 1053): Heap size overflow! req size: 1056768, max size: 1048576
V/AudioCache( 1053): memcpy(0x4325a000, 0x2bfc08, 8192)
V/AudioCache( 1053): write(0x2bfc08, 8192)
V/AudioCache( 1053): write(0x2bfc08, 8192)
V/AudioCache( 1053): write(0x2bfc08, 8192)
V/AudioCache( 1053): memcpy(0x4325a000, 0x2bfc08, 8192)
Has someone a fix for that?
It's the same on Stock (v10b) and Modaco rom

[Q] How to fastboot boot (not flash) into recovery on 4.3?

As per this thread: http://forum.xda-developers.com/showpost.php?p=43940670&postcount=1061 it is no longer possible after 4.3 to simply do "fastboot boot recovery.img" -- if you don't give a -c parameter, fastboot just hangs.
Instead, we have to give kernel parameters to fastboot with the -c option.
The thread for Nexus suggests that the contents of /proc/cmdline would be sufficient. From my install of CWM ( http://forum.xda-developers.com/showthread.php?t=2390651 ) I have:
poweron_status=1 reset_status=0 board_m7_ul.disable_uart3=0 diag.enabled=0 board_m7_ul.debug_uart=0 userdata_sel=0 androidboot.emmc=true androidboot.pagesize=2048 skuid=0 ddt=20 ats=0 dap=6 androidboot.lb=1 uif=m000 td.sf=0 td.td=0 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=696 imc_online_log=0 androidboot.efuse_info=1NSL androidboot.baseband=4A.18.3263.15 androidboot.cid=GOOGL001 androidboot.devicerev=3 androidboot.batt_poweron=good_battery androidboot.carrier=GOOGLE androidboot.mid=PN0712000 androidboot.keycaps=qwerty androidboot.dq=PASS androidboot.mode=recovery androidboot.serialno=FA34WW906464 androidboot.bootloader=1.54.0000 lscd=0x1 wificd=0x2 androidboot.nledhw=0 androidboot.ddrmid=(0x6) acpu.footprint=0B010101 abnrst=0 zygote_oneshot=on kmemleak=off rpm_debug.enable=0 console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31
HOWEVER, this line is too long and fastboot gives me an overflow error when I try to give that entire line.
Any ideas?

Did you ever find out how to do this?

[HOWTO]Some possible way to recover inverted scrren for T,TX,V

(I don't know if T suffers from inverted screen...)
According to my research,inverted screen is caused by cross-flashing.Wrong screen driver is used for initializing the screen,and the registers get corrupted(written data from the inappropriate driver).After that,the screen will be recognized as other model(written data suggests)so even if you use stock kernel,no proper driver will be loaded.
In order to fix this,we need to write proper register data into the screen again.If we take a look at the source of the driver,we will find "RECOVER_NVM" feature.That's how pre-defined data gets written into screen and we will use it for rescuing the screen.
Step 1.COLLECTING CORRECT DATA.
1.1 Identify your actual screen model
Since the screen is already broken,we can't use any software to make it clear.You need to distinguish them using other ways.For example,TX's B screen has a much wider viewing angle than Screen C.Looking from side will give you answer.​1.2 Get to know current detected model.
1.2.1 Reboot your phone to clear dmesg cache.
1.2.2 When it finishes boot,open ADB SHELL or Terminal Emulator.
1.2.3 Type "su".
1.2.4 After # shows up(root privilege acquired),type
Code:
dmesg | grep "panel"
1.2.5 Look at the lines in red
<6>[ 1.006409] default panel: mipi_sharp_panel
<6>[ 1.006775] setting pdata->panel_info.fb_num to 3. type: 8
<6>[ 1.012208] mdp_probe: panel_detect function
<6>[ 1.061651] mipi_renesas_r63306 mipi_renesas_r63306.0: found panel vendor: mipi_sharp_panel
<6>[ 1.062078] mipi_renesas_r63306 mipi_renesas_r63306.0: found panel: mipi_video_sharp_wxga_ls043k3sx04
<3>[ 1.397588] msm_fb_detect_panel: comparing name=hdmi_msm with mipi_video_renesas_fwvga
<6>[ 1.398718] setting pdata->panel_info.fb_num to 1. type: 7
<6>[ 1.399450] mdp_probe: panel_detect function
<6>[ 1.399603] mdp_probe: no panel_detect function
<6>[ 1.402685] setting pdata->panel_info.fb_num to 1. type: 10
<6>[ 1.403906] mdp_probe: panel_detect function
<6>[ 1.403998] mdp_probe: no panel_detect function
Click to expand...
Click to collapse
In this case,ls043k3sx04 is detected screen model.
(Mine is MDX80,not this log)​1.3 Collect correct register data for your ACTUAL screen model.
You may ask your friend who has the same phone and screen to run the script from this post:http://forum.xda-developers.com/showthread.php?t=2607323
And run the dmesg | grep "panel" also to find the model number.
Note that the register number may differ.The numbers in the script is for TX with Screen C.You can download the kernel source of your phone,navigate to /drivers/video/msm and search for your DETECTED model,open the .c file with any text editor.Search for "nvm_**_reg".The hex number is the register number.List them all in the script.
EG.Mine is Screen C/MDW30​
2.MODIFY THE DETECTED MODEL'S DRIVER
2.1 Open the driver mentioned above.​2.2 Scroll to the first "nvm_**_reg".
You can simply skip the nvm_e4_00_00_00_f0_ff_reg ones(have more than one hex num in their names-they are not storing the register data and are more like START/END BURNING commands )
For example,you find
Code:
static char nvm_[COLOR="Red"]e7[/COLOR]_reg[] = {
0x[COLOR="red"]E7[/COLOR], 0x0F, 0x0C, 0x0B, 0x34
};
The first byte in the array is the same as register number.Leave it unchanged and modify the rest bytes accroding to the correct data you have just collected.
EG.The collected data for E7 is
Code:
GEN_READ
reg=0xE7
len=10
data[0]=0x02
data[1]=0x02
data[2]=0x0D
data[3]=0x36
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0xCE
data[9]=0x9A
We have 1+4 bytes in the nvm_e7_reg array,1 for reg number and 4 for rest bytes.So you copy 4bytes from this list to the array.
After modding,it should be
Code:
static char nvm_e7_reg[] = {
0xE7, 0x02, 0x02, 0x0D, 0x36
};
NOTE! The last 2 bytes in each register data is checksum.DO NOT write them into the driver.So the max. available data is 8 bytes.If you find some arrays have more than 8 bytes of data,you need to skip them and go on.​2.3 Find the correct values of long arrays
Open ACTUAL screen's driver,search 0xREG_NUM.
EG. You find
Code:
static char nvm_[COLOR="Red"]ca[/COLOR]_reg[] = {
0xCA, 0x0A, 0x15, 0x2E, 0x2D, 0x27, 0x1B, 0x20, 0x2B, 0x29, 0x31,
0x4F, 0x79, 0x3F
};
There are 1+13 bytes.So you search for 0xCA in mdw30.c(my actual model)
You will find in mdw30.c
EG.
Code:
static char gamma_ctrl_set_r_neg[] = {
[COLOR="red"]0xCA[/COLOR], 0x00, 0x12, 0x22, 0x26, 0x21, 0x1C, 0x25,
0x31, 0x2D, 0x49, 0x5F, 0x3F, 0x3F
};
So this is the actual value for Register CA.Copy the rest bytes to mdx80.c(my detected model)
Note: do not use value from arrays named "eco".​2.4 Save the file.​
3.RE-COMPILE THE KERNEL AND APPLY MOD
The rest is pretty easy:compile this kernel with CONFIG_MSM_FB_RECOVER_PANEL,boot into recovery,and follow command in this post:
http://forum.xda-developers.com/showthread.php?p=49297118
Note:
Code:
cd /d/msm_fb/mipi_[COLOR="red"]r63306[/COLOR]
r63306 is the controller name.You can see it in the directory name of the driver.
I hope this will help you.If you have any question,please ask.

Ive run into a problem. It seems the NVM read data is all blank except the checksums bytes.
Additionally, the CONFIG_FB_MSM_RECOVER_PANEL for all the panels do not appear to use the same values.
Your mdw30 panel doesnt even have this! What did you do?
mdx80 CONFIG_FB_MSM_RECOVER_PANEL
Code:
#ifdef CONFIG_FB_MSM_RECOVER_PANEL
static char nvm_e4_00_00_00_f0_ff_reg[] = {
0xE4, 0x00, 0x00, 0x00, 0xF0, 0xFF
};
static char nvm_e7_reg[] = {
0xE7, 0x0F, 0x0C, 0x0B, 0x34 /* default data according to SoMC */
};
static char nvm_bf_reg[] = {
0xBF, 0x01, 0x22, 0x33, 0x06, 0xB0
};
static char nvm_b2_reg[] = {
0xB2, 0x00
};
static char nvm_b4_reg[] = {
0xB4, 0x02
};
static char nvm_b6_reg[] = {
0xB6, 0x51, 0xE3
};
static char nvm_c0_reg[] = {
0xC0, 0x40, 0x02, 0x7F, 0xC8, 0x08
};
static char nvm_c1_reg[] = {
0xC1, 0x00, 0xA8, 0x00, 0x00, 0x00, 0x00, 0x00, 0x9D, 0x08, 0x27,
0x09, 0x00, 0x00, 0x00, 0x00
};
static char nvm_c2_reg[] = {
0xC2, 0x00, 0x00, 0x09, 0x00, 0x00, 0x00, 0x00
};
static char nvm_c3_reg[] = {
0xC3, 0x04
};
static char nvm_c4_reg[] = {
0xC4, 0x4D, 0x83, 0x00
};
static char nvm_c6_reg[] = {
0xC6, 0x12, 0x00, 0x08, 0x71, 0x00, 0x00, 0x00, 0x80, 0x00, 0x04
};
static char nvm_c7_reg[] = {
0xC7, 0x22
};
static char nvm_c8_reg[] = {
0xC8, 0x4C, 0x0C, 0x0C, 0x0C
};
static char nvm_c9_reg[] = {
0xC9, 0x00, 0x06, 0x10, 0x2E, 0x36, 0x34, 0x3F, 0x44, 0x38, 0x32,
0x31, 0x6A, 0x35
};
static char nvm_ca_reg[] = {
0xCA, 0x0A, 0x15, 0x2E, 0x2D, 0x27, 0x1B, 0x20, 0x2B, 0x29, 0x31,
0x4F, 0x79, 0x3F
...
...
mdw30 does not have CONFIG_FB_MSM_RECOVER_PANEL
ls043k3sx04 CONFIG_FB_MSM_RECOVER_PANEL
Code:
#ifdef CONFIG_FB_MSM_RECOVER_PANEL
static char nvm_rsp1[] = {
0xE7, 0x07, 0x0E, 0x0E, 0x35 /* default data */
};
static char dev_code[] = {
0xBF, 0x01, 0x22, 0x33, 0x06, 0xA4
};
static char test_mode1[] = {
0xE4, 0x00, 0x00, 0x00, 0xF0, 0xFF
};
static char test_mode2[] = {
0xE4, 0x39, 0x87
};
static char test_mode3[] = {
0xE4, 0x00, 0x00, 0x00, 0x00, 0x00
};
static char test_mode4[] = {
0xE4, 0xB9, 0x47
};
static char test_mode5[] = {
0xE4, 0xBD
};
static char nvm_read_e4_reg[] = {
0xE4
};
static char nvm_read_e1_reg[] = {
0xE1
};
static char test_mode7[] = {
0xFD, 0x04, 0x55, 0x53, 0x00, 0x70, 0xFF, 0x10, 0x33, 0x22, 0x22, 0x22,
0x37, 0x00
};
static char nvm_erase_and_write_rsp[] = {
0xE0
...
...
NVM.txt
Code:
e7 03 00 0f 34 de 00 00 11 0b 00 00 00 00 00 00 00 00GEN_READ
reg=0xE6
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xE7
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xDE
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xBF
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xE4
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xE1
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
...
...

Brewski606 said:
Ive run into a problem. It seems the NVM read data is all blank except the checksums bytes.
Additionally, the CONFIG_FB_MSM_RECOVER_PANEL for all the panels do not appear to use the same values.
Your mdw30 panel doesnt even have this! What did you do?
mdx80 CONFIG_FB_MSM_RECOVER_PANEL
Code:
#ifdef CONFIG_FB_MSM_RECOVER_PANEL
static char nvm_e4_00_00_00_f0_ff_reg[] = {
0xE4, 0x00, 0x00, 0x00, 0xF0, 0xFF
};
static char nvm_e7_reg[] = {
0xE7, 0x0F, 0x0C, 0x0B, 0x34 /* default data according to SoMC */
};
static char nvm_bf_reg[] = {
0xBF, 0x01, 0x22, 0x33, 0x06, 0xB0
};
static char nvm_b2_reg[] = {
0xB2, 0x00
};
static char nvm_b4_reg[] = {
0xB4, 0x02
};
static char nvm_b6_reg[] = {
0xB6, 0x51, 0xE3
};
static char nvm_c0_reg[] = {
0xC0, 0x40, 0x02, 0x7F, 0xC8, 0x08
};
static char nvm_c1_reg[] = {
0xC1, 0x00, 0xA8, 0x00, 0x00, 0x00, 0x00, 0x00, 0x9D, 0x08, 0x27,
0x09, 0x00, 0x00, 0x00, 0x00
};
static char nvm_c2_reg[] = {
0xC2, 0x00, 0x00, 0x09, 0x00, 0x00, 0x00, 0x00
};
static char nvm_c3_reg[] = {
0xC3, 0x04
};
static char nvm_c4_reg[] = {
0xC4, 0x4D, 0x83, 0x00
};
static char nvm_c6_reg[] = {
0xC6, 0x12, 0x00, 0x08, 0x71, 0x00, 0x00, 0x00, 0x80, 0x00, 0x04
};
static char nvm_c7_reg[] = {
0xC7, 0x22
};
static char nvm_c8_reg[] = {
0xC8, 0x4C, 0x0C, 0x0C, 0x0C
};
static char nvm_c9_reg[] = {
0xC9, 0x00, 0x06, 0x10, 0x2E, 0x36, 0x34, 0x3F, 0x44, 0x38, 0x32,
0x31, 0x6A, 0x35
};
static char nvm_ca_reg[] = {
0xCA, 0x0A, 0x15, 0x2E, 0x2D, 0x27, 0x1B, 0x20, 0x2B, 0x29, 0x31,
0x4F, 0x79, 0x3F
...
...
mdw30 does not have CONFIG_FB_MSM_RECOVER_PANEL
ls043k3sx04 CONFIG_FB_MSM_RECOVER_PANEL
Code:
#ifdef CONFIG_FB_MSM_RECOVER_PANEL
static char nvm_rsp1[] = {
0xE7, 0x07, 0x0E, 0x0E, 0x35 /* default data */
};
static char dev_code[] = {
0xBF, 0x01, 0x22, 0x33, 0x06, 0xA4
};
static char test_mode1[] = {
0xE4, 0x00, 0x00, 0x00, 0xF0, 0xFF
};
static char test_mode2[] = {
0xE4, 0x39, 0x87
};
static char test_mode3[] = {
0xE4, 0x00, 0x00, 0x00, 0x00, 0x00
};
static char test_mode4[] = {
0xE4, 0xB9, 0x47
};
static char test_mode5[] = {
0xE4, 0xBD
};
static char nvm_read_e4_reg[] = {
0xE4
};
static char nvm_read_e1_reg[] = {
0xE1
};
static char test_mode7[] = {
0xFD, 0x04, 0x55, 0x53, 0x00, 0x70, 0xFF, 0x10, 0x33, 0x22, 0x22, 0x22,
0x37, 0x00
};
static char nvm_erase_and_write_rsp[] = {
0xE0
...
...
NVM.txt
Code:
e7 03 00 0f 34 de 00 00 11 0b 00 00 00 00 00 00 00 00GEN_READ
reg=0xE6
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xE7
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xDE
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xBF
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xE4
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
reg=0xE1
len=10
data[0]=0x00
data[1]=0x00
data[2]=0x00
data[3]=0x00
data[4]=0x00
data[5]=0x00
data[6]=0x00
data[7]=0x00
data[8]=0x8C
data[9]=0x7C
GEN_READ
...
...
Click to expand...
Click to collapse
Maybe your panel require different reading method(or different registers)...And you should modify the RECOGNIZED model's driver.Since it's able to corrupt the registers,it should contain such section.

updateing said:
Maybe your panel require different reading method(or different registers)...And you should modify the RECOGNIZED model's driver.Since it's able to corrupt the registers,it should contain such section.
Click to expand...
Click to collapse
Yes I understand that but I dont know how you find the values for your phone! You have mipi_tmd_mdw30 correct?
The files I pulled from source for your phone are also very different! How did you know what to change the values to?
I attached the source files for your phone. are these the same ones you used?

Brewski606 said:
Yes I understand that but I dont know how you find the values for your phone! You have mipi_tmd_mdw30 correct?
The files I pulled from source for your phone are also very different! How did you know what to change the values to?
I attached the source files for your phone. are these the same ones you used?
Click to expand...
Click to collapse
The data was collected by some member in another forum.MDW30 driver doesn't contain RECOVER_PANEL section.My screen was recognized as MDX80 and it happens to have such a section,so I replaced the data in original MDX80 driver with the one I collected.I didn't touch the mdw30 driver,only replaced the bytes in mdx80.

please Help me My xperia tx no show anything after today call and the screen is gray. The phone is receive calls and SMS. Even touch screen working but it is
gray and don't show anything.

[Q] Backup TA hangs on restore

I'm trying to restore my TA partition with Backup TA v9.9 for Sony Xperia.
I'm trying to do a dry run to test if my backup is OK and then the program hangs forever when trying to push backup to SD-card, as seen below.
Do you think this could be related to me running eXistenZ Ultimate 3.0.0 and not a stock ROM?
I would really like to restore my bootloader and DRM keys so any answer will be greatly appreciated.
Regards,
Hvilsted.
[ ------------------------------------------------------------ ]
[ Backup TA v9.9 for Sony Xperia ]
[ ------------------------------------------------------------ ]
[ 1. Backup ]
[ 2. Restore ]
[ 3. Restore dry-run ]
[ 4. Convert v4 backup ]
[ 5. Quit ]
[ ------------------------------------------------------------ ]
Please make your decision: [1,2,3,4,5]?3
=======================================
RESTORE DRY-RUN
=======================================
When you continue Backup TA will perform the restore of a TA partition
in 'dry-run' mode. This mode performs the restore just like the regular
restore with the exception that it will not do an actual restore of the
backup to the device. It will however perform every integrity check, so
you can test beforehand if your backup is invalid or corrupted.
Are you sure you want to continue? [Y,N]?Y
Waiting for USB Debugging...OK
--- Restore dry run ---
=======================================
CHOOSE BACKUP TO RESTORE
=======================================
[1] TA-backup-20131225.181524.zip
[Q] Quit
Please make your decision:1
Are you sure you want to restore 'TA-backup-20131225.181524.zip '? [Y,N]?Y
=======================================
EXTRACT BACKUP
=======================================
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: backup\TA-backup-20131225.181524.zip
Extracting TA.blk
Extracting TA.img
Extracting TA.md5
Extracting TA.serial
Extracting TA.timestamp
Extracting TA.version
Everything is Ok
Files: 6
Size: 2097243
Compressed: 140970
=======================================
INTEGRITY CHECK
=======================================
OK
=======================================
COMPARE TA PARTITION WITH BACKUP
=======================================
OK
=======================================
BACKUP CURRENT TA PARTITION
=======================================
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.482270 seconds, 4.1MB/s
=======================================
PUSH BACKUP TO SDCARD
=======================================

[Request] Would you help me 'dd' some partiton of your smartphone, plz <3

Hello everyone and moderators !
First , let me thank you for spending time to read this request.
I have a7000 smartphone and I updated new ROW rom with SP tool. But I
chosed "format and download" option, and now some emmc partitions data had gone.
I look in scratter file and see address of some partition, and then read back emmc storage, open hex viewer, all hex are zero. So that mean those partitons are format with zero.
So, I want to request someone have a7000 or k3 note smartphone read back those partitions, by SP tool or command 'dd' in TWRP to separate file, and send those by email for me.
Would any of you can give me some hand, please :-3 <3
This is the list of partitions and address of those which I want :
- partition_index: SYS2
partition_name: proinfo
file_name: proinfo.backup.bin
physical_start_addr: 0x80000 ## start sector 1024
partition_size: 0x300000 ## = 3M
region: EMMC_USER ## /dev/block/mmcblk0p1
- partition_index: SYS3
partition_name: nvram
file_name: nvram.backup.bin
physical_start_addr: 0x380000 ## start sector 7168
partition_size: 0x500000 ## = 5M
region: EMMC_USER ## /dev/block/mmcblk0p2
- partition_index: SYS6
partition_name: persistent
file_name: persistent.backup.bin
physical_start_addr: 0x1c80000 ## start sector 58368
partition_size: 0x80000 ## = 512K
region: EMMC_USER ## /dev/block/mmcblk0p5
- partition_index: SYS7
partition_name: seccfg
file_name: seccfg.backup.bin
physical_start_addr: 0x1d00000 ## start sector 59392
partition_size: 0x40000 ## = 256K
region: EMMC_USER ## /dev/block/mmcblk0p6
- partition_index: SYS12
partition_name: para
file_name: para.backup.bin
physical_start_addr: 0x43a0000 ## start sector 138496
partition_size: 0x80000 ## = 512K
region: EMMC_USER ## /dev/block/mmcblk0p11
- partition_index: SYS14
partition_name: expdb
file_name: expdb.backup.bin
physical_start_addr: 0x4c20000 ## start sector 155904
partition_size: 0xa00000 ## = 10M
region: EMMC_USER ## /dev/block/mmcblk0p13
- partition_index: SYS17
partition_name: metadata
file_name: metadata.backup.bin
physical_start_addr: 0x6020000 ## start sector 196864
partition_size: 0x2000000 ## = 32M
region: EMMC_USER ## /dev/block/mmcblk0p16
- partition_index: SYS18
partition_name: frp
file_name: frp.backup.bin
physical_start_addr: 0x8020000 ## start sector 262400
partition_size: 0x100000 ## = 1M
region: EMMC_USER ## /dev/block/mmcblk0p17
- partition_index: SYS19
partition_name: pad
file_name: pad.backup.bin
physical_start_addr: 0x8120000 ## start sector 264448
partition_size: 0x6e0000 ## = 7040K
region: EMMC_USER ## /dev/block/mmcblk0p18
My email is : [email protected]
Last thing, thank you so much for replying me. And I'm very grateful to you for all your help.
Love you guy, man.
Sincerely !