rafaelSorel

[Update] I manage to make linux booting from the eMMC, it seems that the boot.img needs to be the same one recovered from android firmware. If we put anther one, the linux one it will ends up onto the recovery screen. [nextstep]: How to change the dtb file to be in sync with the one used on the SD card ? knowing that in andoird the dtb.img file is concatenated with some linux kernel header. any ideas ? Thanks

[Update] I have backup the android firmware from another mxq box and restore the one that ends up onto the recovery screen, but when I try to install the firmware into the emmc using one of the two scripts (install.sh or nand_sata_install), I always ends up into the recovery screen. Here attached the recovery screen. I don't know why I cannot copy LE from SD to eMMC ? Thanks for your help,

Yes that is my thoughts also, may be we are gona need help from @balbes150 ? to give us some hints about this ? [Update] It seems that the copy to internal memory that I have done is from armbian-config tools/system/Install to nand, emmc, sata by doing this I could start linux with the mentionned problem of chnaged dtb file. But when running ./install.sh which is suppose to be the same thing I ends up into the android recovery screen. So basically the two methods are not the same : 1- The first one (armbian-config install to nand, emmc) just generate a new dtb file based on the dtb file present on the /boot partition, but really a different dtb file from the sd /boot partion. 2- The second method which is the execution of the ./install.sh script make an exact verbatim copy to the emmc which ends up into recovery android mode.

Yes that is my thoughts also, may be we are gona need help from @balbes150 ? to give us some hints about this ?

Well actually it's name is install.sh and here is the attached script. install.sh

Thanks for help but this is not my problem. I want to know why when I have executed the ./linux.sh to copy linux to internal emmc, it does not use the same dtb.img file that is in /boot partition of the SD file, but it generates new one.

No the mxq_SD.dts is a decompiled gxbb_p200.dtb generic file that we could find in the /boot/dtb/ folder . And the mxq_emmc.dts is a decompiled dtb file from emmc after I have run the ./install.sh script. It is a standard armbian server img with kernel version 3.14

My box is 1G ram I am not sure about the p200 or p201 but you can check the mxq_SD.dts that I have attached with minor changes that I made to load some other drivers. My problem is coming from the one in the emmc. I don't know how it is autogenerated ? And how to edit/fix it ?

Hello, I am using mxq pro 4k and the only dtb file that goes untill the end is the gxbb_p200.dtb, so I have installed every thing on the SD card and every thing works very well. Things getting worse when I installed the linux on the eMMC using the ./install.sh script. The installation goes very well, and every thing starts correctly, the only problem is that many drivers behave strangely, So I have compared the dmesg logs from SD and eMMC and many changes were noticed. So I suspected the dtb file to be not the one used in the SD card, so I have extracted the dtb file used when booting from eMMC and compare it with the one used in SD, and I got a very changed dtb file. I have attached the two dts files. I don't know why the dtb file has changed/patched ? Is there a way to correct the dtb file used in the eMMC ? Thanks for help, mxq_eMMC.dts mxq_SD.dts

I don't understand ? You want to install the uboot on sd card or internal emmc ?

You need to follow the balbes150 tuto to get the box booting from the sd card, basically you need to activate the multiboot. Booting on android then plug the sd card and go to update&backup android application and choose the aml_update.zip file from you boot partition inside the sd card. Here is the link: Please note that mxq pro 4k has different meson version(s905, s905x...), so basically you need to try different device tree files dtb.

Ok than i need to perform the install process each time outside on the SD and plug it to the tvbox onece done ?

Yes but if the installation is on the SD card, it will try to flash the SD card not the emmc ?

@balbes150: Well after the brick of my box, I just wanted to understand what happens, when running those commands: dpkg --install linux-dtb-amlogics905x_5.37_arm64.deb dpkg --install linux-image-amlogics905x_5.37_arm64.deb dpkg --install linux-u-boot-amlogic-s905x_5.37_arm64.deb Knowing that I am running my ubuntu server image on an external SD card ? Thanks,

Well I think it is breaked once and for all, I have tested the SD , the USB burning tool with the USB male/male cable and even the serial output through the SD card reader and nothing pops up, no logs from the bootloader or the boot rom

Ok thanks, I will try the USB cable procedure and see if something pops up.

Is there any procedure I could follow to restore the uboot, I have tried the sdcard method without a success, I will try the USB cable one, but what is the exact procedure of doing that ?

Hello, I have compiled the kernel and bootloader from: https://github.com/150balbes/build It generates *.deb for uboot, kernel and dtb files , i downloaded those file to my ubuntu installed os on my sd card, then I have run dpkg --install *.deb files and rebooted, when rebooted the box won't start, even the LED is not lighted !? , I have tried to make hard reset even I have removed the SD card and made a hard reset , the box won't start at all. I think when I have run the dpkg install command it wrotes the bootloaded into /dev/mmcblk0 which is I guess the internal emmc file. Is there any thing I could do to deblock the situation. [Edit] my box is an mxq pro 4K. Thanks for your help,

Well you mean the git branch amlogic from https://github.com/150balbes/Amlogic_s905-kernel/ ? Or the openlinux amlogic kernel 3.14 ?

@balbes150: is it possible to have a hint regarding such an upgrade ? thanks

I have checked all the images provided and they all integrate the mali driver r5p1, is it possible to have an image with a more recent driver r6p1 or r7p0 for kernel based 3.14.29 ? When I try to integrate one of the mentioned driver version , I got a lot of compiling errors . Thanks for help,