[Verizon Galaxy S 5 Android Development] Surge1223:
Out of curiosity, has anyone that has done this happened to grab last_kmsg or dump of seclog before and after successfully changing a retail device to a developer edition device? [MENTION=711482]beaups[/MENTION] ?

I'm really curious what it shows here:

[1260] skip check low power
[1270] check_boot_mode = key Down[0], Up[0]
[1270] check_ramdump_mode :: k_param.debuglevel[0x574f4c44]::k_param.cp_debuglevel[0x0]
[1280] Do checksum V2
[1280] Not Need Movinand Checksum
[1280] [MUIC] microusb_get_attached_device: STATUS1:0x3f, 2:0x00
[1290] [MUIC] microusb_get_attached_device: chgtyp+adc: 0x1f
[1300] get_wireless_charger_detect : WCIN_OK 0x00)
[1300] get_wireless_charger_detect : CHG_DTLS(0x00)
[1300] is_reboot_case =1
[1310] cable_status = 0
[1310] enter normal booting mode
AST_POWERON
[1540] [MUIC] microusb_get_attached_device: STATUS1:0x3f, 2:0x00
[1540] [MUIC] microusb_get_attached_device: chgtyp+adc: 0x1f
[1550] get_wireless_charger_detect : WCIN_OK 0x00)
[1550] get_wireless_charger_detect : CHG_DTLS(0x00)
[1560] [MUIC] microusb_get_attached_device: STATUS1:0x3f, 2:0x00
[1560] [MUIC] microusb_get_attached_device: chgtyp+adc: 0x1f
[1570] rb=1 jig=0
[1570] v=4231 soc=101
[1570] skip check low battery
[1570] reboot_mode = 0x12345678, boot_mode = 0, por = 0x20080
[1580] Loading boot image (9365504): start
[2130] Loading boot image (9365504): done
[2760] Platform_id : 126
[2760] Hardware_id : 1
[2760] model_info 7e015201, dt_model_info 7e015201, dt_board_rev 0
[2770] update device tree : 7e015201,r00
[2770] model_info 7e015201, dt_model_info 7e015201, dt_board_rev 1
[2780] update device tree : 7e015201,r01
[2780] model_info 7e015201, dt_model_info 7e015201, dt_board_rev 2
[2780] update device tree : 7e015201,r02
[2790] model_info 7e015201, dt_model_info 7e015201, dt_board_rev 3
[2790] update device tree : 7e015201,r03
[2800] model_info 7e015201, dt_model_info 7e015201, dt_board_rev 4
[2800] update device tree : 7e015201,r04
[2810] model_info 7e015201, dt_model_info 7e015201, dt_board_rev 5
[2810] update device tree : 7e015201,r05
[2820] model_info 7e015201, dt_model_info 7e015201, dt_board_rev 6
[2820] update device tree : 7e015201,r06
[2830] model_info 7e015201, dt_model_info 7e015201, dt_board_rev 7
[2830] update device tree : 7e015201,r07
[2840] model_info 7e015201, dt_model_info 7e015201, dt_board_rev 11
[2840] update device tree : 7e015201,r11
[2860] boot image size(10864896)
[2860] cmdline = 'console=null androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x3F'
[2870] lcd_attached=1
[2870] init_ddi_data: usable ddi data.
[2880]
Booting Linux

in particular in relation to

init_ddi_data: usable ddi data.

Because when the mmc card init function executes in aboot this determines a lot of things, the binary Count is ignored if the CID value matches a value in qfprom I believe. I'd love to see a log to confirm what I've been studying. Samsungs mmc_init function in aboot is one of the more obvious differences from lk's implementation.

The struct is something like this:

struct ddi_data
{
unsigned magic;
uint32_t cust_count;
uint32_t odin_count;
uint32_t binary_type;
uint8_t model[16];
uint32_t sysscope_flag;
uint32_t knox_code;
};