Well I burnt
zImage
system.img
userdata.img
ramdisk.img
and its stuck on the animated screen, i'll give it half an hour
This happens because you need build uImage instead zImage. Try to do:
Code:
mkimage -l original_kernel_image
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Well I burnt
zImage
system.img
userdata.img
ramdisk.img
and its stuck on the animated screen, i'll give it half an hour
mkimage -l original_kernel_image
Also this may occur due to framebuffer code or it configuration. Need do kernel debug messages on disk or console (com or network). Or also may try temporary disable gles for vivante (use libGLES_android.so). Android will go to soft-renderer but it will be start point.stopping after the logo just black screen
Mixing and matching potentially means bricking, be careful! Let us know what combinations are in your recipe.
U0 version
Ramdisk - custom or from which .ius ?
Kernel - custom zImage or uImage from which .ius?
Userdata - from which .ius?
System - custom or from which .ius?