[Android Q&A, Help & Troubleshooting] horris87:
Hi guys,

After years of using this site to read up on how-tos for my g1 and desire hd, I have finally hit a brick wall and need to post a question.

My mum won this GT-P7320T branded to telstra ( Australia) and overall, the hardware specs werent too bad, but before the ics update came out finally in january it was terribe to use.

The update has actually been a massive improvement, but being branded and all that junk is as annoying as hell, so i have decided to build my own rom. this is my first time building a rom. ive flashed plenty, but its a different kettle of fish.

i am using the telstra branded stock ics rom with rom kitchen to try to build something acceptable, but first things first, the compiled rom must boot.

because the device isnt supported i have to create i file in the /directory_to_kitchen/tools/edify_defs named GT-P7320T defining all the mount points.

this is where it gets tricky,

here is the contents of the /directory_to_kitchen/tools/edify_defs named GT-P7320T that i have created

#

# The values below should be set in each file in this folder.

#

# Each file represents a device name (set in ro.product.device of

# build.prop)

#

# If yes, then this device requires changing the mount point

# names in the new updater-script or update-script

# DO NOT SET TO 'yes' IF DEVICE IS BY DELL

change_mnt=yes

# If yes, the device is by Dell and requires changing the mount

# point names in the new updater-script or update-script

change_mnt_dell=no

#

# NOTE: The update-script will be converted to updater-script if the

# definition file for the device exists. If 'change_mnt' or

# 'change_mnt_dell' are set to 'yes' then the mount names will

# also be changed.

#

# Mention the mount point names if change_mnt=yes

# Use '\/' instead of '/'

# e.g. sys_mnt=\/dev\/block\/mcblk0p25

#extract from recovery.fstab

#/boot	emmc	/dev/block/mmcblk0p8

#/efs	ext4	/dev/block/mmcblk0p21

#/cache	ext4	/dev/block/mmcblk0p25

#/data	ext4	/dev/block/mmcblk0p26	length=-16384

#/misc	mtd	misc

#/recovery	emmc	/dev/block/mmcblk0p22

#/sdcard	vfat	/dev/block/mmcblk0p28	/dev/block/mmcblk0

#/system	ext4	/dev/block/mmcblk0p24

#

# If unknown, set to: ???

sys_mnt=\/dev\/block\/mmcblk0p24

cache_mnt=\/dev\/block\/mmcblk0p25

boot_mnt=\/dev\/block\/mmcblk0p8

data_mnt=\/dev\/block\/mmcblk0p26	#length=-16384

sdcard_mnt=\/dev\/block\/mmcblk0p28	#\/dev\/block\/mmcblk0

# Set this mount point for the modem.bin in Samsung devices like the Galaxy S2

modem_mnt=

# Set this mount point for the preload partition on some Samsung devices like the Galaxy S2

preload_mnt=

# Set this mount point if you know what it is (e.g. on Motorola Atrix)

webtop_mnt=

# Filesystem info for SYSTEM/DATA/CACHE/etc.

# e.g. param1=ext3, param2=EMMC

param1=ext4

param2=EMMC

# If SDCARD filesystem is different from above, then mention it

# e.g. param1_sdcard=vfat, param2_sdcard=MTD

param1_sdcard=vfat

param2_sdcard=

# If CACHE filesystem is different from above, then mention it

param1_cache=

param2_cache=

# If yes, the device does not require using a 'tmp' folder when

# flashing the boot.img in the updater-script

#

# e.g. package_extract_file("boot.img", "/dev/block/blah1");

fix_boot=no

# If yes, the device requires a 'tmp' folder when flashing the

# boot.img in the updater-script, PLUS the boot partition name

# needs to be used, rather than just 'boot'

#

# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")

# with: write_raw_image("/tmp/boot.img", "/dev/block/blah1")

fix_boot2=no

# If yes, the device requires a 'dd' command to write the boot.img

#

# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")

# with: run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/blah")

fix_boot3=no

# Device uses /cache instead of /tmp, e.g. when writing boot.img

use_cache_not_tmp=no

as you can see,

i have copied and pasted the contets of my recovery.fstab and commented it out as a reference.

this should be quite straight foward, but the mount points for data and sdcard hve additional parameters, which i dont know what to do with.

the parameters are currently commented out and i cannot get it to flash i've tried lots of different combinations but to no avail.

During flashing attempts it is giving me error 7, which to me seems to indicate a problem with setting the mount points.

could sombody please at least point me in the right direction? there is only one other custom rom for this device and i personally don't like it.

many thanks in advnce and i hope i have posted this in the right spot. im all new to this posting stuff and i cant post in any development forums yet