Re: Update.disable again...
Posted: Sun Feb 05, 2017 3:14 pm
Why we still do not know how to fake firmware upgrade files to be recognized by non rooted tv's 
Page 3 of 4
Re: Update.disable again...
Posted: Sun Feb 05, 2017 3:17 pm
well if you provide priv signing keys, no problem then:)
Re: Update.disable again...
Posted: Sun Feb 05, 2017 3:21 pm
fwiw some TDM have "micom toggle" but there might be a chance to brick
hw solutions: EMMC programmer or mainboard replacement
hw solutions: EMMC programmer or mainboard replacement
Re: Update.disable again...
Posted: Sun Feb 05, 2017 3:31 pm
Re: Update.disable again...
Posted: Sun Feb 05, 2017 3:41 pm
dont have device to check at hand and its too long ago i last dealt w/ that old tvs.
check /mtd_exe/partition.txt
check /mtd_exe/partition.txt
Re: Update.disable again...
Posted: Sun Feb 05, 2017 3:53 pm
Code: Select all
0 /dev/mmcblk0p0 512K onboot.bin MLC OTHER BOOTLOADER0 NONE RO
1 /dev/mmcblk0p1 512K seret.bin MLC USER SERET0 NONE RO
2 /dev/mmcblk0p2 512K seret.bin MLC USER SERET1 NONE RO
3 /dev/mmcblk0p3 512K secos.bin MLC USER SECOS0 NONE RO
4 /dev/mmcblk0p4 0K ex_partition MLC NONE NONE NONE RO
5 /dev/mmcblk0p5 512K secos.bin MLC USER SECOS1 NONE RO
6 /dev/mmcblk0p6 7168K uImage MLC USER KERNEL0 NONE RO
7 /dev/mmcblk0p7 5632K rootfs.img MLC USER RFS0 NONE RO
8 /dev/mmcblk0p8 7168K uImage MLC USER KERNEL1 NONE RO
9 /dev/mmcblk0p9 5632K rootfs.img MLC USER RFS1 NONE RO
10 /dev/mmcblk0p10 8K sign0.bin MLC NONE SECUREMAC0 NONE RO
11 /dev/mmcblk0p11 8K sign1.bin MLC NONE SECUREMAC1 NONE RO
12 /dev/mmcblk0p12 8K VD-HEADER MLC NONE NONE NONE RO
13 /dev/mmcblk0p13 3072K NONE MLC NONE NONE mtd_drmregion_a RW
14 /dev/mmcblk0p14 3072K NONE MLC NONE NONE mtd_drmregion_b RW
15 /dev/mmcblk0p15 204800K NONE MLC NONE NONE mtd_rwarea RW
16 /dev/mmcblk0p16 2222080K uniro.img MLC OTHER NONE mtd_uniro RO
17 /dev/mmcblk0p16.v1 0K exe.img MLC USER EXE0 mtd_exe VIRT
18 /dev/mmcblk0p16.v2 0K exe.img MLC USER EXE1 mtd_exe VIRT
19 /dev/mmcblk0p16.v3 0K rocommon.img MLC USER CONTENT0 mtd_rocommon VIRT
20 /dev/mmcblk0p16.v4 0K rocommon.img MLC USER CONTENT1 mtd_rocommon VIRT
21 /dev/mmcblk0p17 1356640K unirw.img MLC OTHER NONE mtd_unirw RWBtw, it's common on Tizen too
Re: Update.disable again...
Posted: Sun Feb 05, 2017 4:16 pm
its not same w/ tizen, first of all "other" partitions get erased on fw upgrade and platform.img (ro) is always written, which contains a "rw_common" img. and there are cases where that img gets flashed. hence all user data is lost
Re: Update.disable again...
Posted: Sun Feb 05, 2017 4:33 pm
If "user" partition is erased, it means that's there's no "spare" one, so it's common. QED.
Otherwise I believe you
Otherwise I believe you
Re: Update.disable again...
Posted: Sun Feb 05, 2017 7:03 pm
Very carefully (and gratefully) read your ideas.
As to "fw upgrade/downgrade". Yes, I did it, updated to 0000 fw (don't know actual number and origin) and back - t'was no effect.
As to "micom toggle" - there are no "micom toggle" (it seems).
As to "change country". Shall try tomorrow, today TV is busy.
As to "EMMC programmer". Can you give more detailed guidance: what chip is meant and what source should be there flashed.
As to "fw upgrade/downgrade". Yes, I did it, updated to 0000 fw (don't know actual number and origin) and back - t'was no effect.
As to "micom toggle" - there are no "micom toggle" (it seems).
As to "change country". Shall try tomorrow, today TV is busy.
As to "EMMC programmer". Can you give more detailed guidance: what chip is meant and what source should be there flashed.
Re: Update.disable again...
Posted: Sun Feb 05, 2017 7:53 pm