If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
Linuxium's Bootloader software to dualboot Android and Linux
I will give it a chance, but not today, today I must sleep
First I will flash your new build recovery and reboot to recovery to see if it works...
Than I will flash your minix-usb-boot and your minix-kernel (but I think I will get problems, because of different HW)...
If first will work, at 1.2.4 there are for k, t (old and new) and ut1 boot&kernel ...
BTW: the mmm123 recovery with your Ubuntu at USB seems to be working well (first impression)...
First I will flash your new build recovery and reboot to recovery to see if it works...
Generally it works, but not really nice
- 720p instead of 1080p
- portrait instead of landscape
- other desktop
- reboots after some minutes (during I write this)
- than blank / black screen (but signal at tv)...
Power off / on
- no Ethernet
=> I hate you (NO, just a joke )
- enable Ethernet
- Power off / on
- nfs (via init.d) share is back
- xbmc resume at video function works....
first impression everything it fine
e.g. your Ubuntu Image is at the stick Ext2Fsd
- File system: EXT3
- Total size: ~2,5GB
- Used size: ~1,6GB
- Partition Type: FAT32
Because my stick is 16GB, I try to modify the partition size with AcronisDiskDirector but it say the Stick is "not initializes"...
How can I modify the partition-size to fit to the stick-size?
/dev/sda on / type ext4 (rw)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/kernel/debug type debugfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
so it seems to be '/dev/sda'
'seems to be', because I'm a little bit confused, because Windows and the Ext2Fsd says EXT3 ...
BTW: BackUp
Because of the missing partition because of the hole device, I can not use Acronis or HDDRawCopy1.02Portable (it crashes at the beginning)...
The benefit of HDDRawCopy1.02Portable is the compression...
Ok, Win32 Disk Imager 0.9 seems to work (my test crashes my system nearly the end so I've to test it one more time)...
Any idea of a BackUp alternative?
I thinking about to find out a way to put it into a partition, if it will work with partition???
ext3, ext4 are ext2+journal - they are compatible.
e.g ext2 tools will work on ext3 and ext4, but will eventually damage journal, it that happens it will be fixed automatically when you re-mount it (e.g. restart)
To backup (because the Win32 Disk Imager 0.9 crash every time at the end with windows BlueScreen) I use WinHex (17.3 SR-5 Specialist) to get the img-file (BackUp) and it works perfect...
BackUp image with WinHex
1. File -> Create Disk Image
2. Select CORRECT Disk ...
2a. "Raw Image ..."
2b. "Copy entire Medium"
2c. check or uncheck "Split Image into segments of"
2d. "Path and filename:"
2e. [OK]... wait...
Writing image with WinHex
1. File -> Restore Image -> file typ = "Raw Image/Container" ...
2. Select CORRECT Target Disk
3. Go... wait...
works generally perfect too, BUT it write/generate a partition-table, so I get sda & sda1 or mmcblk0 & mmcblk0p1...
With mmm123's kernel (recovery) for SD with mmcblk0 & mmcblk0p1 it works perfect, BUT not for USB with sda & sda1... it needs only sda without partition-table to start up the rfs so for USB I have to use Win32 Disk Imager 0.9 BUT it is not really stable at writing too (50% working / 50% BlueScreen)...
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.
Hi,
because of the possibility to work with partitions at SD with the kernel by mmm123 (try it with mmcblk0p1 & mmcblk0p2 and switch label with 'e2label' and it works perfect) I try
sudo reboot recovery
but it only reboots the device, but not to recovery. Is it something special in your kernel or how do you handle it?
this "reboot recovery" is android "reboot" program, not linux one
I don't know what will happen if you just copy it to linux and run - try it if you want.
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.
because of the possibility to work with partitions at SD with the kernel by mmm123 (try it with mmcblk0p1 & mmcblk0p2 and switch label with 'e2label' and it works perfect) I try
sudo reboot recovery
but it only reboots the device, but not to recovery. Is it something special in your kernel or how do you handle it?
this "reboot recovery" is android "reboot" program, not linux one
I don't know what will happen if you just copy it to linux and run - try it if you want.
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...
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment