[Galaxy Tab 3 General] r2d23cpo:
As I said I am a BAD programer.

Bad news wasted many ours trying to learn auto Makefiles, forget about...

Then many more trying to figure out why the same Makefile that I build manually inside Ubuntu Desktop and seems to work. But my Ubuntu in the Tab refuses to accept the compound CFLAGS with path to the different include areas. I just do not understand. I guess there has to be something broken in my installation.

God news THANKS again to the good advice of [MENTION=5864662]moonbutt74[/MENTION] and his suggestion to use "-m32" and "-static", build works perfect in my desktop. So now we have a kernel with kexec and a x86 version of kexecboot. Note: I will expect that the kexecboot is going to require quite a few of revisions in order to make it work. [MENTION=639326]CalcProgrammer1[/MENTION] has mention this a few times.

Also remember that I am expecting help from CalcProgrammer1 to figure out the correct config file and or compilation options.

So I put all together inside "ramdisk"of "/data/local/AIK-mobile" and run a test under chroot to test the different components. Chroot in fact is not build for this because Android Is preventing chroot to pass control to "\init". But I instead created a script inside "/bin/init.sh" like this

chroot ramdisk /bin/busybox ash init.sh

#!/bin/ash
# -*- mode: shell-script; coding: utf-8-emacs-unix; sh-basic-offset: 8; indent-tabs-mode: t -*-
# This code is under Simplified BSD License, see LICENSE for more info
# Copyright (c) 2010, Piotr Karbowski
# All rights reserved.
#
# This code is taken from https://github.com/slashbeast/better-initramfs
# and stripped down (by Arch Linux ARM) to the be tiny and easy to read.
#
# From then it was taken by CalcProgrammer1 and modified to boot Ubuntu on an SGH-I717!
. etc/profile
#export PS=1"root@android:\w#"
#export PATH=/bin:/sbin:/usr/bin:/usr/sbin
#/bin/busybox --install -s

echo '[init] Mounting virtual filesystems'
mount -t proc proc /proc
mount -t sysfs sysfs /sys
mount -t tmpfs -o nosuid,relatime,size=10240k,mode=755 dev /dev

#echo '[init] Starting refresh'
#/usr/sbin/refresh &

echo '[init] Starting hotplug'
touch /etc/mdev.conf
echo /bin/mdev > /proc/sys/kernel/hotplug
mdev -s

#echo '[init] Starting LVM'
#rm -rf /etc/lvm/cache
#lvm vgchange -a y
#sleep 5
#lvm vgmknodes

echo '[init] Launching kexecboot'
kexecboot

echo '[init] Dropping to shell'
ash
root@android:/data/local/AIK-mobile #

You see I am giving every piece of information so you guys readers can repeat if you like. And this is the result.

/busybox ash init.sh <
[init] Mounting virtual filesystems
[init] Starting hotplug
[init] Launching kexecboot
kexecboot 0.6 starting
Kernel cmdline: init=/init[COLOR="Red"] console=sec_log_buf[/COLOR] kmemleak=off ptrace.ptrace_can_access=1 androidboot.bootmedia=sdcard androidboot.hardware=santos10wifi sec_debug.level=0 loglevel=0 androidboot.debug_level=0x4f4c vmalloc=256m sec_log=2052K@0x10000000 sec_bootfb=0x3f000000 lcd_panel_id=0 androidboot.revision=8 switch_sel=3 cordon=38891bc0527004b36227da7aa7c601a7 connie=GT-P5210_OPEN_EUR_42f09c8c182ddc0f36c8d46287bc7382 androidboot.emmc_checksum=3 androidboot.bootloader=P5210UEUAMH1 androidboot.serialno=1234567
We have[COLOR="Red"] no tty[/COLOR]
FB angle is 0, tty is (null)
We have[COLOR="Red"] no tty[/COLOR]
[init] Dropping to shell
root@android:/#

I guess we are closer than yesterday. Les see what my friend CalcProgrammer1 can tell us, I hope that he can provide the mising info Config that we need.

Now the message "We have no tty" it weird. Command line of the Building initrafs reads

cmdline = init=/init pci=noearly [COLOR="Blue"]console=ttyS0[/COLOR][COLOR="Red"] console=logk0[/COLOR] earlyprintk=nologger loglevel=4 hsu_dma=7 kmemleak=off androidboot.bootmedia=sdcard androidboot.hardware=santos10wifi androidboot.spid=xxxx:xxxx:xxxx:xxxx:xxxx:xxxx androidboot.serialno=01234567890123456789012345678901 ip=50.0.0.2:50.0.0.1::255.255.255.0::usb0:on vmalloc=172M

Now I am going to build a boot.img in a zip and test. I will report if it shows something interesting I will post it.

NOOO not yet it still stock at First Samsung Galaxy tab3 Screen. I guess dropping to ash and expect to see something in the screen will require some tweaking. I am hopping that once Ubuntu boot Ubuntu will take care of the screen issue. But That we have to see two. There has to be a way, it is in CWM source!!.