Writing to /data with a flashable update zip

[Guest Simon O]

Hello,

I have a bit of a problem. I'm trying to create a flashable update zip to write some files to /data/app/ on an installed ROM. Currently I'm using this script:

show_progress 0.1 0


copy_dir PACKAGE:app DATA:app[/code]


with the apk files placed inside a folder named app


This script works fine for placing files onto the system drive (obviously changing DATA to SYSTEM) but fails when trying to copy to DATA.


I assume the problem is due to DATA not being mounted in recovery? Anybody know how I can modify the script to make DATA writable?


Could the issue be caused by /data/app being symlinked to the ext partition and this not being mounted? If this is the case then I guess the only option would be to flash the /data update right after the ROM is flashed.


If anybody wonders what I'm doing I'm trying to move all the touchpal languages into a separate installer.

[Guest BigBearMDC]

Hello,

I have a bit of a problem. I'm trying to create a flashable update zip to write some files to /data/app/ on an installed ROM. Currently I'm using this script:

show_progress 0.1 0


copy_dir PACKAGE:app DATA:app[/code]


with the apk files placed inside a folder named app


This script works fine for placing files onto the system drive (obviously changing DATA to SYSTEM) but fails when trying to copy to DATA.


I assume the problem is due to DATA not being mounted in recovery? Anybody know how I can modify the script to make DATA writable?


Could the issue be caused by /data/app being symlinked to the ext partition and this not being mounted? If this is the case then I guess the only option would be to flash the /data update right after the ROM is flashed.


If anybody wonders what I'm doing I'm trying to move all the touchpal languages into a separate installer.


Hiho, just have a look at the init.rc.

There you should see if /data is mounted (and also where - I pretty sure it is mounted :lol: ).

You can also have a look at the 1.7 MCR, I'm pretty sure Paul moved google maps to the data partition, so you could maybe gather some information from there.

Also you could run adb in recovery mode and have a look at fstab or something similar to see which partitions are mounted where.

In the worst case you'd have to modify your init.rc to mount the data partiton.


Best regards,

BigBear

[Guest rss2k]

In recovery mode not everything is mounted. Just go into recovery and then check via adb

which are mounted.

I used a trick by starting a nandroid restore (not completing it) and it would mount certain

partitions. At least the sdcard was mounted so I could copy files from sdcard from wuthin adb.

So for yourselves you have to mount the partitions you need.