Android Tablets Forum banner
1 - 1 of 1 Posts

·
Registered
Joined
·
30 Posts
Discussion Starter · #1 ·
Hi all,

Wanted to used dsixada's android kitchen but a little stuck with the edify syntax currently used. Managed to grab the update-binary from one of christian troys cm9 builds, and had a read through his syntax - am I on the right track here to create a custom defs file for dsixda? I'm unsure about my mount points, and sdcard and cache params. Any devs able to shed some light?
Regards,
Sam
...
Code:
#<br />
# The values below should be set in each file in this folder.<br />
#<br />
# Each file represents a device name (set in ro.product.device of<br />
# build.prop)<br />
#<br />
<br />
# If yes, then this device requires changing the mount point <br />
# names in the new updater-script or update-script<br />
# DO NOT SET TO 'yes' IF DEVICE IS BY DELL<br />
change_mnt=no<br />
<br />
# If yes, the device is by Dell and requires changing the mount<br />
# point names in the new updater-script or update-script<br />
change_mnt_dell=no<br />
<br />
#<br />
# NOTE: The update-script will be converted to updater-script if the <br />
#       definition file for the device exists.  If 'change_mnt' or <br />
#       'change_mnt_dell' are set to 'yes' then the mount names will <br />
#       also be changed.<br />
#<br />
<br />
# Mention the mount point names if change_mnt=yes<br />
# Use '\/' instead of '/'<br />
# e.g. sys_mnt=\/dev\/block\/mcblk0p25<br />
#<br />
# If unknown, set to: ???<br />
sys_mnt=\/dev\/block\/nandd<br />
cache_mnt=???<br />
boot_mnt=\/dev\/block\/nandc<br />
data_mnt=\/dev\/block\/nande<br />
sdcard_mnt=???<br />
<br />
# Set this mount point for the modem.bin in Samsung devices like the Galaxy S2<br />
modem_mnt=<br />
<br />
# Set this mount point if you know what it is (e.g. on Motorola Atrix)<br />
webtop_mnt=<br />
<br />
# Filesystem info for SYSTEM/DATA/CACHE/etc.<br />
# e.g. param1=ext3, param2=EMMC<br />
param1=ext4<br />
param2=EMMC<br />
<br />
# If SDCARD filesystem is different from above, then mention it<br />
# e.g. param1_sdcard=vfat, param2_sdcard=MTD<br />
param1_sdcard=<br />
param2_sdcard=<br />
<br />
# If CACHE filesystem is different from above, then mention it <br />
param1_cache=<br />
param2_cache=<br />
<br />
# If yes, the device does not require using a 'tmp' folder when<br />
# flashing the boot.img in the updater-script<br />
#<br />
# e.g. package_extract_file("boot.img", "/dev/block/blah1");<br />
fix_boot=yes<br />
<br />
# If yes, the device requires a 'tmp' folder when flashing the<br />
# boot.img in the updater-script, PLUS the boot partition name<br />
# needs to be used, rather than just 'boot'<br />
#<br />
# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")<br />
#      with:    write_raw_image("/tmp/boot.img", "/dev/block/blah1")<br />
fix_boot2=no<br />
<br />
# If yes, the device requires a 'dd' command to write the boot.img<br />
# <br />
# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")<br />
#      with:    run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/blah")<br />
fix_boot3=no<br />
<br />
# Device uses /cache instead of /tmp, e.g. when writing boot.img<br />
use_cache_not_tmp=no<br />
<br />
<br />
 
1 - 1 of 1 Posts
Top