Linuxium's Bootloader software to dualboot Android and Linux

[mmm123]

adb pull /system/bin/toolbox toolbox

FTP toolbox to /home/linuxium

linuxium@LINUXIUMONE:~$ ls -al t*
-rw------- 1 linuxium users 134976 Mar 4 01:18 toolbox
linuxium@LINUXIUMONE:~$ sudo chmod a+x toolbox
[sudo] password for linuxium:
linuxium@LINUXIUMONE:~$ ls -al t*
-rwx--x--x 1 linuxium users 134976 Mar 4 01:18 toolbox

BUT
linuxium@LINUXIUMONE:~$ sudo toolbox reboot recovery
sudo: toolbox: command not found
linuxium@LINUXIUMONE:~$ sudo toolbox
sudo: toolbox: command not found

If I don't forget something or do a mistake, it don't work...

@linuxium: how do you handle it?

try sudo ./toolbox reboot recovery
or
ln -s toolbox reboot
sudo ./reboot recovery
if it still doesn't work, try ldd ./toolbox and see if it requires any libraries

[mmm123]

Simply because I don't know of a command to reboot and substitute the current kernel for another one other than the command 'reboot recovery' which requires the "recovery" kernel to be located in the 'recovery' partition.

If there are better ways of storing an alternative kernel and then being able to boot it this would be great.

kexec will do exactly that - replace current kernel with new one:

http://www.linux.com/community/blogs/129-servers/413862

you just need to compile kernel with kexec support enabled, and install kexec tools.

[no_spam_for_me]

lol... You're kidding? At the other thread I wrote "Compared to my knowing about "error-soft" (micro-soft) I'm a really newbie at linux..." AND now you write "you just need to compile kernel with kexec support enabled" yeeees
It's something for the next few weeks...

In earnest, first I have to learn buildup enviroment (git clone, rk tools, and so on), compilig, pack/unpack imgs (boot, recovery) ...
And if I've a basic understanding of what to do, I will give it a chance... but THX

[no_spam_for_me]

if it still doesn't work, try ldd ./toolbox and see if it requires any libraries

BTW

linuxium@LINUXIUMONE:~$ ldd ./toolbox
        not a dynamic executable
linuxium@LINUXIUMONE:~$ file ./toolbox
./toolbox: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped
linuxium@LINUXIUMONE:~$ strace ./toolbox
execve("./toolbox", ["./toolbox"], [/* 17 vars */]) = -1 ENOENT (No such file or directory)
dup(2)                                  = 3
fcntl64(3, F_GETFL)                     = 0x20002 (flags O_RDWR|O_LARGEFILE)
fstat64(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4001c000
_llseek(3, 0, 0xbee86328, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory
) = 40
close(3)                                = 0
munmap(0x4001c000, 4096)                = 0
exit_group(1)                           = ?
linuxium@LINUXIUMONE:~$ strace ./toolbox reboot
execve("./toolbox", ["./toolbox", "reboot"], [/* 17 vars */]) = -1 ENOENT (No such file or directory)
dup(2)                                  = 3
fcntl64(3, F_GETFL)                     = 0x20002 (flags O_RDWR|O_LARGEFILE)
fstat64(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40059000
_llseek(3, 0, 0xbe856318, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory
) = 40
close(3)                                = 0
munmap(0x40059000, 4096)                = 0
exit_group(1)                           = ?
linuxium@LINUXIUMONE:~$ strace ./toolbox reboot recovery
execve("./toolbox", ["./toolbox", "reboot", "recovery"], [/* 17 vars */]) = -1 ENOENT (No such file or directory)
dup(2)                                  = 3
fcntl64(3, F_GETFL)                     = 0x20002 (flags O_RDWR|O_LARGEFILE)
fstat64(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40046000
_llseek(3, 0, 0xbeabb318, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory
) = 40
close(3)                                = 0
munmap(0x40046000, 4096)                = 0
exit_group(1)                           = ?
linuxium@LINUXIUMONE:~$

[mmm123]

BTW

linuxium@LINUXIUMONE:~$ ldd ./toolbox
        not a dynamic executable
linuxium@LINUXIUMONE:~$ file ./toolbox
./toolbox: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped
linuxium@LINUXIUMONE:~$ strace ./toolbox
execve("./toolbox", ["./toolbox"], [/* 17 vars */]) = -1 ENOENT (No such file or directory)
dup(2)                                  = 3
fcntl64(3, F_GETFL)                     = 0x20002 (flags O_RDWR|O_LARGEFILE)
fstat64(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0

device it tries to open (136,2) should be /dev/pts/2 Check if it is there.
Also run as root - e.g. "sudo bash -login" and then ./toolbox ... or strace

[mmm123]

lol... You're kidding? At the other thread I wrote "Compared to my knowing about "error-soft" (micro-soft) I'm a really newbie at linux..." AND now you write "you just need to compile kernel with kexec support enabled" yeeees
It's something for the next few weeks...

In earnest, first I have to learn buildup enviroment (git clone, rk tools, and so on), compilig, pack/unpack imgs (boot, recovery) ...
And if I've a basic understanding of what to do, I will give it a chance... but THX

This was not for you
But compiling kernel is quite simple nowdays, just find proper guide and follow steps.

[linuxium]

kexec will do exactly that - replace current kernel with new one:

http://www.linux.com/community/blogs/129-servers/413862

you just need to compile kernel with kexec support enabled, and install kexec tools.

Thanks for the info. Unfortunately my original post was overley simplified: besides 'replaceing' the kernel it needs to reboot by loading the Android initramfs as well as the Android kernel. 'kexec' doesn't reboot which is what I am using the Android 'reboot recovery'.

[mmm123]

Thanks for the info. Unfortunately my original post was overley simplified: besides 'replaceing' the kernel it needs to reboot by loading the Android initramfs as well as the Android kernel. 'kexec' doesn't reboot which is what I am using the Android 'reboot recovery'.

kexec boots new kernel with new initramfs without hard reset. What you eventualy need is to extract initramfs from boot.img, which is trivial.

[Killerdude]

Maybe A simpel question

Linuxium,


I got a simple maybe stupid question, but I installed everything and it works fine.
but with booting Linux he has a linuxium user, what is the password to get in?
I am using the xubuntu image.


thanks

[enrique66_35]

Linuxium,


I got a simple maybe stupid question, but I installed everything and it works fine.
but with booting Linux he has a linuxium user, what is the password to get in?
I am using the xubuntu image.


thanks

If it's the same as ubuntu, password is p (and root password is blank).
I'd recommend typing sudo passwd into terminal and settting a root password and similarly you can run sudo passwd linuxium to change that password from p to one of your choosing.

Alternatively set up a new user and set passwords as you see fit for it.

[Killerdude]

Thanks inks for the quick reply Enrique

If it's the same as ubuntu, password is p (and root password is blank).
I'd recommend typing sudo passwd into terminal and settting a root password and similarly you can run sudo passwd linuxium to change that password from p to one of your choosing.

Alternatively set up a new user and set passwords as you see fit for it.

[kayak1987]

I can't understand if it is possible for a real noob as I am, to make it work on a T-R42..
is this supported?
Do I have only to flash things and copy files or there is to insert command or compile something etc?
thank so much

[no_spam_for_me]

I can't understand if it is possible for a real noob as I am, to make it work on a T-R42..
is this supported?
Do I have only to flash things and copy files or there is to insert command or compile something etc?
thank so much

No, because of the "build in" Android this solution is only for the 'Radxa Rock', 'Minix Neo X7' and 'Rikomagic MK802IV (latest model)'...
Generally the 'Linux root file system' can use with every rk3188 device (it is like the system.img), but you need a matching/fitting kernel&boot for your device installed at your device (kernel.img + boot.img or recovery.img (which include kernel+boot))...

[no_spam_for_me]

device it tries to open (136,2) should be /dev/pts/2 Check if it is there.
Also run as root - e.g. "sudo bash -login" and then ./toolbox ... or strace

Hi,

for me it is a really mysteries how you can identify /dev/pts/2

  linuxium@LINUXIUMONE:~$ ls -al /dev/pts/
  total 0
  drwxr-xr-x  2 root     root      0 Jan  1  1970 .
  drwxr-xr-x 12 root     root  13980 Jan  1 22:32 ..
  crw--w----  1 root     tty  136, 0 Jan  1 22:28 0
  crw--w----  1 linuxium tty  136, 1 Jan  3 15:03 1
  crw--w----  1 root     tty  136, 2 Jan  1 22:28 2
  crw--w----  1 root     tty  136, 4 Jan  1 22:28 4
  c---------  1 root     root   5, 2 Jan  1  1970 ptmx
   
  linuxium@LINUXIUMONE:~$ sudo bash -login
   
  root@LINUXIUMONE:~# ./toolbox reboot recovery
  bash: ./toolbox: No such file or directory
   
  root@LINUXIUMONE:~# sudo ./toolbox reboot recovery
  root@LINUXIUMONE:~# 
   
  root@LINUXIUMONE:~# strace sudo ./toolbox reboot recovery

[mmm123]

Hi,

for me it is a really mysteries how you can identify /dev/pts/2

It is quite obvious:
crw--w---- 1 root tty 136, 2 Jan 1 22:28 2

strace of sudo is useless. capture strace of toolbox
e.g.:
1) sudo bash -login
2) strace ./toolbox reboot recovery 2>file
Still this is waste of time, i am sure this "toolbox" is available somewhere as source. Look for it and compile.