Here is a brief much more complete guide to creating your own Odin images for distributing custom ROMs or making backups. Thanks to kam197, BH_MAN, chadmd23, SoulCreator, and all the other community members.

Requirements:

• A Samsung Behold 2 to backup/edit/ ROMs on
  


• Root via try3/asroot2, persistent su, or modified kernel
  
• Working ADB connection
  
• SD Card with ~300MB free
  
• Cygwin - if you are working in Windows
  
• Basic knowledge of a command line
  

Making the ROM Dump:

The Behold 2 has 14 partitions in its flash memory, but only a few of these are useful to modify. You will want to focus on different partitions depending on what you want to do. After you make a ROM dump you will need to package it using the instructions in the following section before you can flash it.

Backup your personal data?

You may want to backup your data while trying out a different ROM. It is simple to do.

Start an ADB shell session and obtain root access.

Run the following command to dump the UserData partition:

Code:

# dd if=/dev/block/stl14 of=/sdcard/userdata bs=4096

Retrieve the dumped file from the SD Card.

Don't include userdata in a distribution unless you don't mind everyone knowing your email, passwords, app choices, web history, etc!

Make a custom system image (ROM)?

Creating a custom ROM can involve no more than changing out a few included applications to modifying advanced features of the phone. A lot of ing should be performed before distributing a heavily customized system image. It is recommended to make multiple system image dumps as "in-progress" snapshots or saves as you work on the ROM. Otherwise messing up normally means starting over!

Once dumped a system ROM cannot be edited, so you must work with it directly on the phone (recommended while in Recovery Mode). The System dump will be an exact copy of what is already loaded so get everything set up first and that the phone can reboot.

Start an ADB shell session and obtain root access.

Run the following command to dump the System partition:

Code:

# dd if=/dev/block/stl9 of=/sdcard/system bs=4096

Retrieve the dumped file from the SD Card.

If you want to get files out of another system image (or userdata image) without flashing, open them in an archive program that can read FAT disk image files - 7-Zip is recommended - or mount them read-only under Linux. Trying to write to the image with these methods will corrupt it as its non-standard.

Make a custom kernel or recovery image (ROM)?

ADVANCED: Modifying the kernel or recovery image can allow you to enable root, change startup logos, and tweak environment settings for boot. In addition to the other requirements you will need an decent understanding of Linux file permissions, startup, and mount process, as well as a hex editor

Start an ADB shell session and obtain root access.

Run the following command to dump the kernel partition:

Code:

# dd if=/dev/block/bml8 of=/sdcard/kernel bs=4096

Run the following command to dump the recovery partition:

Code:

# dd if=/dev/block/bml6 of=/sdcard/recovery bs=4096

Retrieve the dumped file from the SD Card.

Make a copy for backup purposes! We will be editing these.

Create a working folder for each of the dumped kernel and/or recovery images and move them there.

Split the images in each working folder into the binary and ramdisk.

Code:

$ head -c 1785856 kernel > krnl.bin

$ tail -c +1785857 kernel > rd.cgz

$ head -c 1937408 recovery > krnl.bin
$ tail -c +1937409 recovery > rd.cgz