Strange, there no special requirements, just flash zip....
Yeah, I don't get it as well, I'd bet at bootstrap failing, though no idea why. Let's see if I can get uart to work
D/OMX_JPGENC(121): JPEGENC_GetParameter():1220 Exit function eError = 80001005
Looks like the jpeg encoder chokes and thus doesn't give a bit..
Edit:
Humm...
614 adb push ramdisk /system/bootstrap/2nd-boot
615 adb push zImage /system/bootstrap/2nd-boot
629 adb push system/lib/modules /system/lib/modules
Ok, doing the above on the 2.6build keeps boostrap working and kinda boots the kernel. I'm glad it has early adb support, cause the video driver ain't working yet (but that was to expect)
Edit2:
Adb pushing the libs even gets graphics, and the bootanimation and 'android is updating'...
If I had to guess I'd say that
-console=/dev/null mem=500M init=/init omapfb.vram=0:4M usbcore.old_scheme_first=y panic=30 mmcparts=mmcblk1
20(kpanic)
+console=/dev/null mem=500M omapfb.vram=0:4M
the cmdline difference is the problem.
Because it's probably not
$BB_STATIC echo "inserting hbootmod.ko"
+if [ -e /cache/uart_en ]; then
+$BB_STATIC insmod ./hbootmod.ko kill_dss=1 emu_uart=115200
+else
$BB_STATIC insmod ./hbootmod.ko kill_dss=1
+fi
and the differing zImage, and ramdisks is to be expected.
w00t... it finished it's hackery boot.
"
[email protected]:/ $ uname -a
Linux localhost 3.0.8-g2149493 #1 PREEMPT Tue May 13 10:29:27 OMST 2014 armv7l GNU/Linux"
Though I doubt it would survive copying your cmdline :/
Edit3:
Uhh, now I wonder why you are able to boot
Code:
if (execute_command) {
run_init_process(execute_command);
printk(KERN_WARNING "Failed to execute %s. Attempting "
"defaults...\n", execute_command);
}
run_init_process("/sbin/init");
run_init_process("/etc/init");
run_init_process("/bin/init");
run_init_process("/bin/sh");
panic("No init found. Try passing init= option to kernel. "
"See Linux Documentation/init.txt for guidance.");
So, there's no /init in that list, thus I'd say no boot without init=/init. And just in case: is there a way to modify the system partition while not being able to get into running system/recovery?
