OK, on libreelec how do I enter the command line?
enable sshd in libreelec settings and ssh into box
(passwd perhaps libreelec or perhaps khadas)
to check value.
I assume/recall there is a GUI way to reboot into other OS as well.
Because I changed the theme the buttons with the boot options disappeared, when I reset the original theme was solved.
Can you add the buttons to other themes?
I do not plan such work yet.
Hi Oleg. I watched the world cup soccer game in my Vim2, and Russia gave a terrific 5-0 shower to the other team, with three goals that seemed from another planet. Are you sure you didn’t put any trck in your ROM?
It worked … for some time.
Now, pressing “power” brings the menu to select which system to boot.
But only android fires up. Can’t boot to Ubuntu nor LibreElec.
No way yet to ssh (root, khadas).
How could I update your 3-1 to the newest version?
Thks a lot for your help!
Write in more detail what actions were performed with the system before the reboot stopped working in other systems (installing packages in Android, changing settings, etc.). Try to start the system from an external media (from which you did the installation) and run the command “fw_printenv” from the user “root”, and show the result here.
I had also gathered a problem with the android box. My elder son had set up his google account, installed chrome and a game (terraria).
I use a logitech mouse and keyboard. The interface respond to the mouse. However, action-click didn’t work. Only form the keyboard.
“fw_printenv bls" from another system gave the right info (“libreelec” in my case).
So, with the keyboard, I did a “reset to factory settings” in Nougat. Selected Ubuntu on next boot and it finally did it.
Alas, my khadas account (which I had set to autologin) did not autolog. And no way to enter a password. Had to use root (which is not fully configured). Even after an update, the graphical tools to manage users do not work.
Moreover, I have no clue how to update to your latest 3in1 (no dbbr folder, even in extpart).
On the verge of giving it all up (with the feeling of a “hous of cards”) to install ubuntu with the more user-friendly emmc burning tools.Although not a total noob, I do not have the spare time required to fiddle in what I feel is still a WIP …
Sorry for that!! And thks for your kind interest!
reboot to flash another rom.
cannot enter upgrade mode via keys.
cannot boot anymore (not even the khadas logo)
boot from sd (coreelec) : starts then stop. Was known to work.
boot from usb (libreelec): nothing.
Fun is over.
I doubt if your box is bricked.
You can always reinstall factory android image and restart experimenting from there.
I guess it’s still working, but I can(t reach upgrade mode…
Finally made it, via TF card update which saved my ass (khadas has none, if I remember well).
Multiboot to reinstall (nothing obvious : still have to find aml_autosript.zip ans time to take care of that - the most difficult part).
All three systems use one common partition (/dev/data) to host user data. If you try to clear data in Android, you erase some (or all) user data from the other two systems (LE and Ubuntu). If you are from under Ubuntu to perform incorrect actions with the data partition, it will also break down the work of the other two systems (Android and Ubuntu). For normal operation of Ubuntu, an important first run, when there is an automatic initial setup (migrating user data in the partition /dev/data). If at this point the process is disrupted, the system will be in an undefined state, with all the ensuing consequences (the khadas user login will not work, etc.). If the primary setting Ubuntu is broken, you will have to perform a number of manual operations to restore (manually delete some parameters\settings and files). Or perform the entire installation procedure from scratch from external media.
balbes150, thks for your welcome reminder which explains the cascade of events.
Although it also stresses the delicate equilibrium of a 3in1 in a reduced space.
I’d rather stick now to a more traditional way (keep things separated).
Btw, how come I can enter into recovery mode (I can see the output on screen : my display supports hdmi (vim2) and DP (windows)) but USB upgrade tool under win10 (1803) can’t connect/find the vim2? Reason why I had thought the vim2 had bricked. I had done a reinstall of upgrade tool (latest version), reboot win10, and so on. To no avail.
Still, thank you very much for your kind interest!!
Are you sure you follow the instructions to start the USB Burning Tool update mode ? Alternatively, you can erase the u-boot in the eMMC and the system should automatically connect to the USB Burning Tool when you connect the USB cable.
Can i install this 3 in 1 OS onto my Odroid C2 ? does it work without a Problem ?
if yes which dtb img should i use for this ?
In theory, this is possible if make image for Odroid C2. But for this you need to perform a lot of manual operations to replace the u-boot and kernel, adapt settings and Android itself, etc.
I’m quiete sure to have followed instructions : I can see that the vim2 is in update mode (via its output) while windows (1803) doesn’t mount the device in the usb burning tool. Tried it on another fresh pc. The same.
How could i erase u-boot? From windows or from linux?
Thks for your help!
There is also an option (without erasing) to disable u-boot in eMMC and start firmware mode from USB Burn Tools - use M-register (it is described in the documentation).
Start the system from external media and you can perform any operations with the eMMC. To remove u-boot, you can simply run one command as user “root”.
dd if=/dev/zero of=/dev/bootloader
By the way, you can immediately write another u-boot to eMMC. Download archive from Khadas downloads page. Unpack. And write a new u-boot to the eMMC.
dd if=u-boot.bin of=/dev/bootloader
PS I see you have not completed one of the important steps of the installation instructions MultiOS_3_in_1. Make a full backup of the eMMC before installation. In this case, the whole recovery procedure would be very simple. Start the system from external media, run the “ddbr” utility and select the recovery mode. After that, you would get the system in exactly the same state as it was at the time of the copy creation (without the need to use the USB Built Tools).
Updated KODI version (fixed bug with add-ons installation).