[Tizen Software Development] adfree:
Thanx for info mapcuk.

:good:

So I can try 2.3.x without panic... not be able to downgrade...

Meanwhile I have little progress with Windows THOR Tool...

3 Values... at end of file...

size of TAR 1 and size of TAR 2...

This is easy...

Third Value is 2 Bytes...

Some CRC/Checksum... could be CRC16 Samsung style... but I have problems to generate for such huge file... 1 GB + :o

First try was to delete CRC Bytes... result fail. :o

<ID:0/009> Added!!
<ID:0/009> Thor engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> NAND Write Start!!
<ID:0/009> u-boot-mmc.bin
<ID:0/009> s-boot-mmc.bin
<ID:0/009> uImage
<ID:0/009> modules.img
[COLOR="Red"]<ID:0/009> MZ[/COLOR]
<ID:0/009>
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
<ID:0/009> Added!!

First TAR is unpacked and flashed... but..

RD-PQ is alive... :good:

Second attempt... I have zeroed second size... so second TAR is ignored. :D

CRC Bytes also 0000 like in attempt 1...

<ID:0/009> Added!!
<ID:0/009> Thor engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> NAND Write Start!!
<ID:0/009> u-boot-mmc.bin
<ID:0/009> s-boot-mmc.bin
<ID:0/009> uImage
<ID:0/009> modules.img
<ID:0/009> Removed!!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!

:D

Now I charge battery and think about next steps...

To inject my own TAR file...

Only question... if good idea to try Bootloader package ...:confused:

Maybe first I will try simple only flash second TAR without Bootloader... and check if this work...

Before I unpack migrate_2.3_bootloader.tar.gz and "repack" as TAR... to play with Windows THOR...

Best Regards

---------- Post added at 10:00 PM ---------- Previous post was at 09:14 PM ----------

:D

<ID:0/009> Added!!
<ID:0/009> Thor engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> NAND Write Start!!
<ID:0/009> u-boot-mmc.bin
<ID:0/009> params.bin
<ID:0/009> Removed!!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Added!!

Injected TAR from migrate_2.3_bootloader.tar...

RD-PQ is alive and PIT is now Version 13...

Next step...

tizen-2.3.1-mobile_20150921.1_mobile_boot.tar

<ID:0/009> Added!!
<ID:0/009> Thor engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> NAND Write Start!!
<ID:0/009> params.bin
<ID:0/009> modules.img
<ID:0/009> uImage
<ID:0/009> u-boot-mmc.bin
<ID:0/009> Removed!!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Added!!

:D

RD-PQ is alive... after reboot in Dump mode... dump_panic...

Next step is proceed with:

tizen-2.3.1-mobile_20150921.1_mobile_target.tar

<ID:0/009> Added!!
<ID:0/009> Thor engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> NAND Write Start!!
<ID:0/009> rootfs.img
<ID:0/009> user.img
<ID:0/009> system-data.img
<ID:0/009> Removed!!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!

Done!

:cool:

I am now on Tizen 2.3.1 on my RD-PQ via Windows.

But 2.3.1 looks really ugly now... nothing is installed... WiFi seems not... :cyclops:

Anyway.

RD-PQ is flashable with Windows. :victory:

Its not perfect way for now...

I've used whole 1clickbinaries... x 3... as template.

So each EXE was 1 GB... :D :o