[Samsung Galaxy Star] Doc_cheilvenerdi.org:
CWM 6.0.2.8 Up and Running!

News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):

I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!

First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...

On first build everything was fine but the LCD screen didn't light up...

...Recovery was running, anyway, but I could not see anything...

...I could, perhaps, control the phone from PC with "adb shell"! :)

doc@saucy:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #

Recovery log recorded the problem:

...
failed to put fb0 info
...

It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:

...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...

Well done! Recovery 6.0.2.8 up and running

Now testing:

- I can mount/unmount and list all filesystems

- I can backup the current firmware

- I can format and restore the external second partition (I use it a lot):

Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks

...

Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...

~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #

- I can restore the boot image (and recovery of course):

...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...

Restore complete!

- I can Install boot images inside zip files from sdcard:

-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...

########################
# Doc Modded #
# new boot image #
########################

Installing Boot...
script result was [ ]

Installation Completed!!!!

- I can install zip files from sideload:

Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...

sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you

own a relaxed recovery!
Cheers :)
~ #

- I can "wipe cache":

-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.

- I can "wipe data/factory reset" :cool::

-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead

...
Data wipe complete.
/tmp #

Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset :cool:

I took an extra-check with the following 'shell command' before and after the wipe action:

/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...

looking for no relevant differences!

..after boot... everything fine!

- Last but not least:

- I fully restored the previously backupped firmware:

...
...
Restore complete!

Easy Play :cool:

What's Wrong in this recovery?

I Dont Know...

Wish List?

Sure: I cannot handle /efs partition via 'menu options'...

...and everybody knows how dangerous could be wander around it :)