Trim Area research

[SquallATF]

In Sony Update Engine, I get some TA info from jar package.
in com.sonymobile.cs.device.io.s1.protocol package:

public static final int PARTITION_TA = 1;
public static final int PARTITION_MISC_TA = 2;

in com.sonymobile.cs.ma.domain package:

public static final byte NORMAL_TA_PARTITION = 1;
public static final String NORMAL_TA_PARTITION_NAME = "TA";
public static final byte MISC_TA_PARTITION = 2;
public static final String MISC_TA_PARTITION_NAME = "miscTA";

The code tells us TA have two partition, one is normal TA and one is misc TA.
When I flash baseband, after first time boot, I get NV/TA-log(/nvta_log/log.txt) from EFS Explorer
part in log

0007933 Loading trim area to NV (<unit> [<size>]):
0009424  0 [4]
0009425  1 [4]
0009425  4 [1]
0009425  5 [1]
0009425  6 [1]
0009425  7 [2]
0009426  8 [1]
0009426  9 [2]
.......

and I have compared nv unit in ta parition 1
all units are loading from trim area partition 1
then I conpared the units and qcn dump
most of the units map to nv iem and the have same id.
and another units are files in /nv/item_files/rfnv , the unit id same as file name.
We can see most of baseband init configuration are from TA partition 1.
In misc TA (TA partition 2)
there have some thin about signed imei, DRM info, WLAN MAC address and some device only thing, but I noticed unit 000009F7, this is a name decision to load witch baseband config in amss_fs_3(m9kefs3 partition)
here is another part of NV/TA_log

0007883 nvpreload/nv_L1245_17W12458.bin removed successfully.
0007883 nvpreload/nv_L1245_17W12458_cal_true.bin removed successfully.
0007884 nvpreload/nv_L1245_17W12458_ets.bin removed successfully.
0007884 nvpreload/nv_L1_19_21W156_19.bin removed successfully.
0007884 nvpreload/nv_L1_19_21W156_19_cal_true.bin removed successfully.
0007884 nvpreload/nv_L1_19_21W156_19_ets.bin removed successfully.
0007884 nvpreload/nv_W12458.bin removed successfully.
0007884 nvpreload/nv_W12458_cal_true.bin removed successfully.
0007884 nvpreload/nv_W12458_ets.bin removed successfully.
0007885 nvpreload/nv_W1358.bin removed successfully.
0007885 nvpreload/nv_W1358_cal_true.bin removed successfully.
0007885 nvpreload/nv_W1358_ets.bin removed successfully.
0007886 Selecting band configuration file
0007886 Selected band configuration file '/nvpreload/nv_L1357_20W1358_cal_true.bin'.
0007887 /nvpreload/nv_L1357_20W1358_cal_true.bin removed successfully.
0007887 /nvpreload/nv_default_band_cal_true.bin removed successfully.
0007887 Selecting band configuration file
0007887 Selected band configuration file '/nvpreload/nv_L1357_20W1358_ets.bin'.
0007888 /nvpreload/nv_L1357_20W1358_ets.bin removed successfully.
0007888 /nvpreload/nv_default_band_ets.bin removed successfully.
0009793 Selecting band configuration file
0009793 Selected band configuration file '/nvpreload/nv_L1357_20W1358.bin'.
0009795 /nvpreload/nv_L1357_20W1358.bin removed successfully.
0009795 /nvpreload/nv_default_band.bin removed successfully.

when I changed value from W12458 to L1357_20W1358 in unit 000009F7, I successfully changed the baseband configuration.

 

[iamdude]

@SquallATF, very interesting finding.

Do you make additional research about this issue?
I want to understand the contents of the TA units and their purpose.

For example, 000007DA unit contains information about sim-lock state.

Then you change value in one NVitem, does it save after phone reboot?

 

[zviki]

This is a 6 months old post... ?

Sent from my SM-N910C using Tapatalk