Quote:
Originally Posted by S3raph
great idea j0534ng31 I didn't thought about that, however the probably greatest advantage of the ramdisk solution is its simplicity.
I attached my modified ramdisk, its the "normal" ramdisk with a modified init.rc and includes the e2fsck binary.
Code:
# check filesystem
exec /sbin/e2fsck -py /dev/block/mmcblk2p1
exec /sbin/e2fsck -py /dev/block/mmcblk2p9
exec /sbin/e2fsck -py /dev/block/mmcblk2p10
credits go to porkupan for the flash script/tools and all his great work.
[EDIT]
This was the "normal" ramdisk without adb enabled, sry for the mistake. Ive added a second archive which enables e2fsck and adb support, please redownload the archive enable-fsck-adb_v2.zip the old one missed the adbd binary, thanks for the hint to j0534ng31.
[/EDIT]
I DONT TAKE RESPONSIBILITY FOR ANY BRICKS |
WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
YOUR DEVICE SURELY WILL BE BRICKED IF YOU FLASH THAT
In do_update.sh it says:
Code:
dd if=${UPDATE_MP}/tmp/ramdisk-adb-fsck.uimg of=/dev/mmcblk2 seek=10240 count=600 bs=512
That means that 600x512=307200 bytes will be copied from ramdisk-adb-fsck.uimg to the internal flash.
Porkupan's ramdisk-adb.uimg is only 290202 bytes, no problem there, but ramdisk-adb-fsck.uimg has 555204 bytes.
That means, the initrd will be incompletely written and guess what happens.... when you try to boot that....