[Tizen Software Development] adfree:
Need more time to understand...

But ist seems.

dd stuff works to write something...

I mean this stuff...

http://xdaforums.com/galaxy-s3/orig-development/util-sboot-checker-simple-downgrade-t2081748

I have not found way to check/dump mmcblk0p1... to confirm sboot.bin is written...

But 1 stupid test seems successfully...

I have written s-boot-mmc.bin from RD-PQ to sboot.bin partition mmcblk0p1

About result... not 100 % sure because I see nothing on Display... (damaged Display...)...

But I was not able to write after this action sboot.bin via Odin...

:confused: :confused:

But all other Flash stuff worked with Odin... so I9300 was not bricked...

Also booting to Android ADB stuff...

After I have restored all 3 partitions with original I9300 stuff...

# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4

Odin allowed to write successfully GT-I9300_Boot_Recovery.tar

<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/008> Added!!

After this I have checked again dd stuff... and modified param.bin, because mmcblk0p4 you can dump...

Short test with LO changed into HI for High Debug Mode... and changes visible...

Later I will try to check again s-boot-mmc.bin...

If you dump mmcblk0 you can find Header of eMMC...

Best Regards

dd and partition investigation... :rolleyes:

shell@android:/ # dd if=/dev/block/mmcblk0p3 of=/sdcard/noidea1.bin
dd if=/dev/block/mmcblk0p3 of=/sdcard/noidea1.bin
40960+0 records in
40960+0 records out
20971520 bytes transferred in 12.835 secs (1633932 bytes/sec)
shell@android:/ #

What is in mmcblk0p3 and can I dump it...

mmcblk0p1 is only 0000/empty if you dump...

C:\adb>adb pull sdcard/noidea1.bin
6687 KB/s (20971520 bytes in 3.062s)

I can open with WinHex... 20 MB and see some content... no idea what it is yet...

---------- Post added at 02:08 PM ---------- Previous post was at 01:30 PM ----------

http://xdaforums.com/showpost.php?p=55514573&postcount=36

:D

I am drunken enough to test dump.bin from RD-PQ to write to I9300...

Will post result...

Steps...

- dump.bin copy to I9300 via ADB...

- ADB shell, su, dd... blabla...

Something like this:

[B]d[/B]anger[B]d[/B]anger if=/sdcard/dump.bin of=/dev/block/[B]mmcblk0[/B]

Okidoki... soon I know what happens... :o

Best Regards

Edit 1...

C:\adb>adb push dump.bin sdcard/dump.bin
5165 KB/s (33554432 bytes in 6.343s)

C:\adb>adb shell
shell@android:/ $ su
su
shell@android:/ # dd if=/sdcard/dump.bin of=/dev/block/mmcblk0
dd if=/sdcard/dump.bin of=/dev/block/mmcblk0
65536+0 records in
65536+0 records out
33554432 bytes transferred in 3.514 secs (9548785 bytes/sec)
shell@android:/ # reboot fota_bl
reboot fota_bl

Hmm... dump.bin is written with Error from ADB... this means not it is really 1:1 written...

Android not start... as it seems...

But I can activate Download Mode via JIG... now I am trying to write via Odin, as THOR for Win not detect...

But hey... this looks interesting...

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLI8_I9300OXADLI8_I9300XXDLI8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> [B]There is no PIT partition.[/B]
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

Maybe this sboot.bin from Tizen allow unsigned PIT files...

:confused: :confused:

Because PIT I think I have somewhere for Tizen RD-PQ...

Will test... :D

Best Regards

Edit again...

Original I9300 files work... PIT + sboot.bin

<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!

My other test before failed...

unsigned Tizen PIT + Tizen RD-PQ sboot...

Hmmmmmmmm... maybe necessary sboot from Tizen was not written with dump.bin ...

Will check later again...

Now I will try to flash all Firmwarefiles and check if I9300 is ADB alive...

Or I have something killed...