@tank0412 I modify the defconf file and build the kernel and also my twrp recovery build works without any problem so the problem is in the ramdisk of the boot.img. i dont know where the problem is!!!!!
Every new version brings a lot of new features and correct a lot of bugs. Try the rc-proposed channel is relatively stable.
Can't wait to have the 9th version.
Thank you again for the great job you're doing!
Hi Frano212,
I stopped working on the port. It does boot up into adb but graphics and so on are not working. It is very hard to get help, so i will just buy the new meizu pro 5 ....
Installed developer build 218 its stuck at 1+ logo, and 219 build is throwing some error which states that multirom has been stopped to avoid file corruption.. On the move now will post details later if anyone wants them.
News 6/03:
MultiROM v33 is under development, just need patched kernel to boot heterogeneous ROMs (ex. CyanogenMOD and Ubuntu).
MultiROM on XDA
Thanks.
Hahaha.....seems like you are on same error as mine. Even i have recovery working properly but when booting normally it gets stuck at vendor logo. Check which initrd version are u using and then see if ubuntu rootfs version is same as initrd version. I think the issue is somewhere in initrd as stressed by ubuntu porting guide. Also get last_kmsg. That will help alot us in figuring out the problem.
Ok sorry. I read how to go into recovery without damaging last_kmsg. So when i am in bootloop and i press recovery mode key combination the screen goes off and on again. Should i keep pressing the combination until i get to recovery or leave the buttons as soon as screen goes black?
