Originally Posted by romdroid.
will u upgrade bmm to be compatible with cm 10.1 from hashcode? thanks. if yes, will it be possible to install cm 10.1 as stock rom?
I believe it was caused by this commit :
mount("tmpfs", "/dev", "tmpfs", MS_NOSUID, "mode=0755");
mount("devpts", "/dev/pts", "devpts", 0, NULL);
mount("proc", "/proc", "proc", 0, NULL);
mount("sysfs", "/sys", "sysfs", 0, NULL);
/* indicate that booting is in progress to background fw loaders, etc */
close(open("/dev/.booting", O_WRONLY | O_CREAT, 0000));
/* We must have some place other than / to create the
* device nodes for kmsg and null, otherwise we won't
* be able to remount / read-only later on.
* Now that tmpfs is mounted on /dev, we can actually
* talk to the outside world.
BMM always clean all tmpfs partition before 2nd-init, so that init can do a fresh start.
But since this commit, some devfs is not recreated, thus ROM can't be booted.
If you want to boot newer build, you have to build your own init. (undefine BOARD_USE_NO_DEVFS_SETUP)
or take init binary from 24012013 build. (Not recommended)
Attached is init binary taken from 24012013 build for testing.
Flash this zip after flashing STS CM zip file.
Why we have to skip devfs
Should I fix this in BMM boot script???