balbes150

While the kernel is being updated manually. This option has its pros and cons. Otherwise , support for Khadas from Armbian products is stable and complete (exception , support for some wifi models on VIM 2 \ 3).

During the installation, a regular MBR is created and then the main kernel works with eMMC, as with a conventional HDD\SSD (all utilities work as with conventional disks). If desired, after installation in eMMC, you can change partitions, add your own split and mount options.

These are sections in the Android format. Khadas uses the old 4.9 kernel from Amlogic, which is heavily patched for this. In the main core there is no support for partitions of Android. If you want to install a new kernel in eMMC and keep the u-boot-2015 installed, you must use a special procedure to install the system in eMMC. This feature is present in Armbian images for TV boxes (and it works perfectly on all Khadas VIM 1 2 3 products).

I don't have that equipment.

Please note, the principle of using the button may be different. There are hardware buttons, they work correctly with Linux, there are "soft" buttons, they do not work well with Linux (supported only in Android firmware). What tasks do you plan to solve on this device ? With Tanix products I would recommend to be more careful, there may be problems with running Linux.

I am asking about specific steps (instruction) for the end user so that he can run your image. An important fundamental difference between TV boxes (by the term TV box I mean all devices with built-in u-boot on eMMC or SPI) from the old variants of SBC , in the principles of starting the system. Khadas products belong to the category of TV boxes, with all the ensuing consequences in the development of systems for them. Again, how do you plan to run the system on Khadas products with AML chips (VIM 1 2 3)? By the way, the built-in u-boot gives a unique opportunity to use the TV boxes as a normal PC with the launch of the system from USB media. Given that modern chips support USB 3.0, which is significantly faster than SD cards, the use of USB to host the entire system is an important element. The ease of use of USB is many times higher than SD cards.

For the first time I hear that in China there are problems with obtaining images from the y-disk. I communicate with Khadas developers from China and they regularly download and test my images on all Khadas products. If you really want to help integrate all versions into a single build branch, you can take up the tvboxes branch. @Igor did the primary work, but he and I do not have enough time to bring everything to full readiness. By the way, how do you plan to run your image on VIM ?

One question. The Armbian build system is already overloaded with a bunch of different options. Why multiply entities ? For all Khadas models, there are already perfectly working Armbian images.

New image 5.94 20190821

Version 5.91_20190802. Added thermal control for g12

No If the corresponding option is enabled

New image 5.91_20190801. Fixed displaying of information about the frequency of cores for the g12. add image dev for g12 (kernel 5.3.0)

I'll only watch it after my vacation.

If you haven't done a full backup as indicated in the instructions, then only via USB Burn Tool.

The sixth message on the first page of the topic.

You can try two options. 1 look For a firmware version where u-boot will be able to install to eMMC (maybe even older versions with Android 6\7\8 will be better). 2. Try to test the new u-boot-2019 for gxbb models, but it is potentially dangerous to get a brick with recovery only through the contact closure on the eMMC.

According to the logs, u-boot does not support installing a new kernel in the eMMC.

Show the output UART of commands from u-boot (printenv) before and after installation.

If you are not familiar with unpacking firmware (that would pull out of it ready u-boot for eMMC), you'd better use standard USB tools Burn Tool to restore the working firmware. By default, the system checks for updates, try disabling it and performing updates manually.

Start the system from external media, mount the EMMC partition with the data, and run a simple package command to the TAR archive (or tar.gz) eMMC Disk /dev/mmcblk0: 14.5 GiB, 15518924800 bytes, 30310400 sectors What exactly is the version of the Armbian image ? I have not checked the eMMC, Noa SD card or USB flash drive system restarts without problems.

non-desktop image = SERVER ? As far as I remember, there is no NetworkManager in the server image. What media is used ? Which u-boot option is used (where does the - SPI or SD\eMMC switch point) ?

You can make a backup of the entire root system and after u-boot recovery, deploy it back. When restoring u-boot will not clear the partition table (MBR), it will require you to perform a clean installation of Armbian (with a subsequent recovery is made of the copy in the created partition EXT4).

Restore the stock Android firmware. Run Armbian from external media and show the output of 'fdisk -l' command. Most likely you have a failed HDMI output , there is no protection on x96max. If you completely turn off the power and after 10 minutes to try to turn on does not help, you need to contact the repair.

Judging by the log, there is no working u-boot in eMMC. Show the entire log when starting the system with the SD card connected.

By the way, you can run Armbian and LibreELEC on Odroid C2 from USB media. That is, You can have a connected SD card or eMMC module with default system and without disconnecting them, quickly start the test system from USB media. To add to the run settings file u-boot (for SD or eMMC media boot.ini) the second line in this string.  --------------------------------------------------- ODROIDC2-UBOOT-CONFIG # Add run USB script s905_autoscript if usb start; then setenv dtb_mem_addr "0x1000000"; if fatload usb 0 1020000 s905_autoscript; then autoscr 1020000; fi; fi; ######################################################################## # Changes made to this are overwritten every time there's a new upgrade You can then run any images for s9xx using the standard s905_autoscript scripts and settings in (uEnv.ini)