I came across this bug report when trying to unpack a sparse ext4 image from an Android 4.1 phone, loop-mount it, modify and repack it to a sparse ext4 image for flashing.
To address your question whether the -a parameter is needed for make_ext4fs, I built (with the kind help of a friend) the Debian package with the ANDROID compiler option. My plan was, to flash the resulting image file with (as recommended in the corresponding android forums) and without -a option to see whether this makes any difference. However, even after flashing with the -a option, the phone does not boot anymore, because the file permissions get changed by the make_ext4fs tool (as can be seen by unpacking it again and comparing the permissions). The same happens with the original AOSP upstream files (I used git tag android-4.1.2_r2.1). So your question cannot be answered yet because of another problem. For the record: The user jazzor seems to have fixed the problem and also shares the source code of a working version at http://forum.xda-developers.com/galaxy-s2/general/ref-unpacking-repacking-stock-rom-img-t1081239 I'll ask him whether he is willing to create a diff or tell me what version his modifications are based on so that I can do a diff by myself. Best regards, Philipp Spitzer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
