[Galaxy S III Q&A, Help & Troubleshooting] adfree:
http://xdaforums.com/showpost.php?p=49036438&postcount=67

Tizen_GPT_Ver08.pit

Partition info is different... compared between RD-PQ and few I9300 PIT files I've found...

Other stupid test, because I have no eMMC device nor I9300 nor RD-PQ nor any Live Unit Device...

http://xdaforums.com/showpost.php?p=48883684&postcount=66

Maybe some "lucky" guy with RD-PQ is able to use UART cable, like in this Video...

More stupid tests I can make with my S8500... :D

Seems we have enough time before Samsung release Tizen devices for endusers...

Best Regards

Edit 1.

If I flash SBL from I9000 in my S8500 with renamed string ODIN into THOR...

I can see over UART:

[B]Error:Invalid connection string![/B]

So I modified Odin.exe:

- [B]Thor[/B] is connected!
FlashDevRead 63: Error(offset,length,j4fs_end,nErr)=(0x40000,0x1000,0x1a000005,0x80040001)
j4fs_write_file_bootloader 192: Error(nErr=0x40000000)
process_packet: request id(100), data id(0)
process_rqt_init: platform number(0x0), revision(0x0)
process_packet: request id(100), data id(2)
process_packet: request id(101), data id(0)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(3)
Device not opened
partition_backup: efs. meta data=3(units), real size=6553600
Device not opened
partition_backup: sbl. buf=0x46e00000, size=1310720(bytes)
Device not opened
partition_backup: sbl2. buf=0x46f40000, size=1310720(bytes)
FlashDevClose 262: Error(nErr=0x80040001)
fsr_bml_format_device start
set_dynamic_partition: pit magic code=0x12349876
bbm format success
bbm_erase_all: step 1. Start unit=1, End unit=2.
.
bbm_erase_all: step 1. Start unit=52, End unit=2004.
................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
bbm eraseall success.
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
Erasing: 1 to 2
.
bbm erase part success
.Done.
Written 1 units.
current percent: 0 (1/0)
board partition information update.. source: 0x403ee838
Erasing: 2 to 42
........................................
bbm erase part success
[FNW: ] STL formatted (partition ID: 20)
[FNW:INF] nVol : 0, partition_id : 20, stSTLInfo.nTotalLogScts : 12800, buf :0x46400000
TotalLogSct : 12800, size : 6553600
Done.
Written 25 units.
current percent: 0 (26/0)
Erasing: 42 to 47
.....
bbm erase part success
.....Done.
Written 5 units.
current percent: 0 (31/0)
Erasing: 47 to 52
.....
bbm erase part success
.....Done.
Written 5 units.
current percent: 0 (36/0)
process_packet: request id(101), data id(1)
.Done.
read 1 units.
check_pit_integrity: valid pit magic code.
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(3)
process_packet: request id(103), data id(0)
process_rqt_close: xmit completed!
FlashDevRead 63: Error(offset,length,j4fs_end,nErr)=(0x40000,0x1000,0x1a000005,0x80040001)
j4fs_write_file_bootloader 192: Error(nErr=0x40000000)
process_packet: request id(103), data id(1)
process_rqt_close: target reset!
ARIES MAGIC_ADDR=0x0 / INFORM5=0x12345678

Then seems okay... Odin perform Flashing action. :D

WARNING!

Only short tested with OLD Odin3 v1.85.exe... on my S8500 bada device.

At your own risk.

Remember RD-PQ could be an Live Demo Unit, with missing Hardware...

No GPS, no Call... no IMEI etc...

You can kill Tizen device...

Best Regards