That is, after deleting (boot.ini) from the /boot section of the eMMC module, Android started normally ?

2 minutes ago, dante6913 said:

The only thing since the bigining of editing boot,ini, is the HardKernel logo that is messed out

Not using that file, I deleted and it boots normaly

4 minutes ago, dante6913 said:

Not using that file, I deleted and it boots normaly

Try searching for files (boot.ini) on the eMMC module, there may still be a place where they are located

8 minutes ago, dante6913 said:

The only thing since the bigining of editing boot,ini, is the HardKernel logo that is messed out

 

3 minutes ago, balbes150 said:

Try searching for files (boot.ini) on the eMMC module, there may still be a place where they are located

Its copied from some file, because after i deleted it, is allways restored

3 minutes ago, dante6913 said:

Its copied from some file, because after i deleted it, is allways restored

Run

grep -r "boot.ini" *

Should show the location where it is being restored from

11 minutes ago, balbes150 said:

Run

grep -r "boot.ini" *

Should show the location where it is being restored from

cp /system/etc/boot.ini.template /internal/boot.ini

Just now, dante6913 said:

cp /system/etc/boot.ini.template /internal/boot.ini

gonna make a pause for lunch and edit /system/etc/boot.ini.template

Try using a USB flash drive and these lines in (boot.ini). By the way, after editing (boot.ini) and starting the system , what was changed is saved ?

 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

17 minutes ago, balbes150 said:

Try using a USB flash drive and these lines in (boot.ini). By the way, after editing (boot.ini) and starting the system , what was changed is saved ?

 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

all boot.ini file is restored

3 minutes ago, dante6913 said:

all boot.ini file is restored

all the changes that you make are reset when you power on C2 ?

6 minutes ago, dante6913 said:

all boot.ini file is restored

It Worked, booted at in armbian, but its stucked at

finished daily man-db regeneration

27 minutes ago, balbes150 said:

Try using a USB flash drive and these lines in (boot.ini). By the way, after editing (boot.ini) and starting the system , what was changed is saved ?

 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

booted in armbian and stuck at finished daily man-db regeneration

2 minutes ago, dante6913 said:

booted in armbian and stuck at finished daily man-db regeneration

I'm sorry, I didn't understand what it was stuck on. What is displayed on the screen ?

1 minute ago, balbes150 said:

I'm sorry, I didn't understand what it was stuck on. What is displayed on the screen ?

"Finished Daily man-db regeneration" 

That is what is displayed on the screen

Managed to ssh and is and configured a new user

reboot and I was able to boot in armbian desktopt.

Is it possible to boot in sd card?

 

2 minutes ago, dante6913 said:

Managed to ssh and is and configured a new user

reboot and I was able to boot in armbian desktopt.

Is it possible to boot in sd card?

Try

 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

mmcinfo

fatload mmc 1 1020000 boot.scr

autoscr 1020000

 

 

By the way, I dug out my sample Odroid C2 and checked the launch of the latest version of Armbian 20.05.4. Recorded to the Android SD card. Added lines to (boot.ini), wrote Armbian to a USB flash drive, and configured (uEnv.txt). Everything starts normally from USB and you can configure the system without ssh. In the same mode, I checked the launch of Libreelec from USB, everything works. I don't have eMMC for C2, so I can't test working with SD+eMMC.

7 minutes ago, balbes150 said:

Try

 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

mmcinfo

fatload mmc 1 1020000 boot.scr

autoscr 1020000

 

 

It boots if in the sd card if I have the usb dongle

It must be run from SD without an USB stick.

try

 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

mmcinfo

fatload mmc 1 1020000 boot-emmc.scr.aw

autoscr 1020000

2 minutes ago, dante6913 said:

It boots if in the sd card if I have the usb dongle

now whith some scripts i can launch odroid from emmc or armbian from sd or Libreelec from USB

Thanks balbes150 for your patitence and time

By the way, the sound in Armbian not stutter much. I haven't found a way to fix it yet. In LE, this is solved by switching the sound setting to fixed mode and in LE, the sound works cleanly.

On 5/9/2020 at 4:46 AM, balbes150 said:

 

Contact the hardware manufacturer to develop and source the correct DTB for the mainline kernel with support for all devices for your models.

@balbes150 do you mean this is a hardware isse and it's just a matter of right mapping inside DTB?

 

Thanks.

3 hours ago, dante6913 said:

now whith some scripts i can launch odroid from emmc or armbian from sd or Libreelec from USB

Thanks balbes150 for your patitence and time

This thing is completly killing me. installed LE on the usb stick and tried to boot edited boot.ini to 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

but just booted on android 

reverted all, tried again to boot to armbian but none of the configurations seem to work, I'm getting mad 

56 minutes ago, dante6913 said:

but just booted on android 

reverted all, tried again to boot to armbian but none of the configurations seem to work, I'm getting mad 

What is the contents of the file (boot.ini) on eMMC ? I hope you didn't forget to make the settings in (uEnv.txt) the correct dtb and startup strings are correct ?

To fix the sound on s905 without stuttering, you need to add a parameter to the sound settings file.

 

 rate 48000

 

(the fix will be included in the next version of images).

3 minutes ago, balbes150 said:

What is the contents of the file (boot.ini) on eMMC ? I hope you didn't forget to make the settings in (uEnv.txt) the correct dtb and startup strings are correct ?

using the first configuration

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

made the cooret change uEnv.txt

puted now armbian debian in the usb stick

burned a image of my emmc card to an sd card tried to boot from the usb stick with armbian, with the boot.ini with 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

but got the same result, just booted on android

Pay attention to one more nuance - the order of connected USB devices. In this change, the system is searched for on USB 0. If there are other devices, the number may change.

 

4 minutes ago, dante6913 said:

burned a image of my emmc card to an sd card tried to boot from the usb stick with armbian, with the boot.ini with 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

but got the same result, just booted on android

Did I understand correctly that only the SD card is connected (eMMC is disabled) and the USB flash drive ?

yes you are right, but I'm tring what you said about the usb number because there where a lot of dongles and I have changed the order, so I'm going to try it with the usb armbian pen only