[Fairphone 1] mrueegg:
boot.img and partitions

hi all

be aware that the orginial software build is

W20-HL.V0009 (FP/ahong89_wet_jb2/ahong89_wet_jb2:4.2.2/JDQ39/1387200600:user/test-keys dated 2013-12-16 14:35)

while the one of the recovery-zip is

W20-HL.V0010 (FP/ahong89_wet_jb2/ahong89_wet_jb2:4.2.2/JDQ39/1388753011:user/test-keys dated 2014-01-03 13:48).

www .fairphone .com/downloads/software/fp1_fairphone_os_recovery/Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip

they differ a bit:

IIRC in the original build the google apps where installed as user apps, while in 1388753011 they are installed to the /system. (can anybody pleas confirm?)

the kernal image differs.

the boot.img also differs. in 1388753011 they changed:

- /sbin/adbd

- /custom_build_verno (added)

- /init.rc

the changed adbd does not give you a root user anymore, but only a limited shell user. so e.g. you cannot flash your boot.img using dd. you have to first start your device, install a terminal, become root and then flash the boot image or do it using the recovery and an update.zip.

not sure if the change in init.rc has something to do with that too. they removed the following lines:

on property:ro.debuggable=0
start console
setprop persist.sys.usb.config mass_storage,adb

you can get back to your root-adb-shell by installing your old boot.img.

be aware: the recovery-zip given by fairphone does not fix any partition issue! so when you're messing with any changes there, which what i did with my first device, then you might end up with a bricked phone as i did. (could anybody please point me to how i can dd my /dev/ebr1 and /dev/ebr2 from an other device? what is the size of these? and how can i - if i got them - flash them using an update.zip?)

an other interesting thing is: while you get to recovery mode by pressing power+volume-up you can get into a debug/testing mode by pressing power+volume-down. in this mode you can use adb (e.g. to flash your boot.img if you have sufficient privileges [see above].)

btw: i could successfully use my ext4-partition on my sdcard by changing the following lines to init.rc (in section on fs_property:ro.mount.fs=EXT4:

exec /sbin/e2fsck -pfD /emmc@usrdata
exec /sbin/tune2fs -O has_journal /emmc@usrdata
exec /system/bin/ext4_resize
mount ext4 /emmc@usrdata /data noatime nosuid nodev wait noauto_da_alloc,discard

with this:

# create mountpoint for internal data
mkdir /mnt/internal_data 0775 root system

# create symlinks for easy access
symlink /dev/block/mmcblk1p1 /sd@fat
symlink /dev/block/mmcblk1p2 /sd@usrdata

exec /sbin/e2fsck -pfD /sd@usrdata
exec /sbin/tune2fs -O has_journal /sd@usrdata
mount ext4 /sd@usrdata /data noatime nosuid nodev wait noauto_da_alloc,discard

exec /sbin/e2fsck -pfD /emmc@usrdata
exec /sbin/tune2fs -O has_journal /emmc@usrdata
exec /system/bin/ext4_resize
mount ext4 /emmc@usrdata /mnt/internal_data noatime nosuid nodev wait noauto_da_alloc,discard

this worked fine with the original software release. but currently I'm having an issue with it after flashing the recovery-zip. so it ends up in a boot-loop. but this can be fixed by installing the original boot.img.

what i actually wanted to achieve is that the internal storage, aka "phone storage" or /emmc@fat, is removed so it gets not mounted at all. i'd like to use it, possibly as one with /emmc@usrdata as pure ext4 storage which i would use for my synchronized data.

regards,

martin.

ps: i had to remove/put the url in that messy form as the system would not yet allow external links ...