However, these commands are no longer necessary. I've already sent you another bootloader.
Now install dtb as already described. Then install aml_upgrade_package.img.
Posts by bumerc
-
-
it seems nothing happened (log was blank, after it)
Strange. Ok, I will set selinux to engorcing in uboot config by default.
As long as we do not do this, access to some kernel resources (in permissive mode) will be denied by sepolicy…
-
but wifi and bluetooth not working in this image
uart log of successful boot is attached...
I only see problems in the incompatibility of Sepolicy rules..
Try to put the SELinux into Enforce mode.
Abort autoboot and change the mode:
Codesetenv EnableSelinux enforcing saveenv reset -
FEAT:BDFC31BC
aml log : R1024 check fail with ERR = 85 aml log : SIG CHK : 85 for address 0x01700000
In your case, the box manufacturer has activated secure boot. Information about whether the board is actually encrypted can be extracted from the SEC_AO_SEC_SD_CFG10 register. You can only boot with an encrypted FIP. The error “wrong chip..”: The chip id is defined in BL30 blob (closed source). This id is also used for MAC generation in BL33, u-boot. As long as the chip id is not known, the uboot will perform the reset, which leads to a boot loop. I managed to convert the normal, unencrypted bl30 blob to an ELF binary through small manipulations and to decompile its code into a legible format. With a small change in ELF binary, the fake "s905w" was now running and was recognized as s905l Soc. If you still have one of these encrypted boards where the original u-boot is not damaged, you could read the bl30 dump into a file and compile it into an executable file to create an ELF binary from it..
It is best to contact the manufacturer regarding original fw
-
-
You need to replace 4 files:
bootloader.PARTITION = u-boot.bin
aml_sdc_burn.UBOOT = u-boot.bin.sd.bin
u-boot.bin.usb.bl2 = DDR.USB
u-boot.bin.usb.tpl = UBOOT.USB
-
new boot log attached
Do a clean installation with aml_upgrade_package.img, either with UBT, or sdcard update. Repack the stock fw with the new uboot files I sent you
-
box stopped booting on mbox flashing logo..
It's not entirely clear why you burned uboot and dtb 2 times.. And where is the android's boot log?
-
My guess is that you have a clone device and it is a gxbb (s905) platform, that would explain the PLL error. I'll send you gxbb blobs, well worth a try…
-
jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' run 0xd9000000
[update]Run at Addr d9000000
AmlUsbRunBinCode:ram_addr=d9000000
jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' write '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/DDR.USB' 0xd9000000
ERR: write data to device failed
Here you have already initialized RAM. In this step, instead of DDR.USB, load the TPL UBOOT.USB to the address described above
Codemedia/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update write media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/UBOOT.USB 0x200c000then
Codeupdate write ..yourpath../gxl/usbbl2runpara_runfipimg.bin 0xd900c000 update run 0xd9000000 -
1. run ddr init:
update cwr DDR.USB 0xd9000000
update write ..yourpath../gxl/usbbl2runpara_ddrinit.bin 0xd900c000
update run 0xd9000000
2. run uboot (usb tpl)
update write DDR.USB 0xd9000000
update write UBOOT.USB 0x200c000
update write ..yourpath../gxl/usbbl2runpara_runfipimg.bin 0xd900c000
update run 0xd9000000
-
Before you write the new u-boot.bin into the emmc, you have to test it to avoid the boot loop
1. Burn the new u-boot.bin.sd.bin onto the mSD card and insert it into the TV box
2. Run init 3 and reset
3. Check whether the new uboot is functional
4. If everything is OK, write the new uboot.bin on emmcDownload
-
from where i can get 'Nougat (stock) bootloader' that can work with my box.
I don't know, but that's not a problem, I can compile the nougat u-boot for you
-
same steps were followed as explained by you log attached
but when HDMI connected only big mecool logo was on the screen and nothing else (box does not boots )
Android 7 cannot be operated with Pie Bootloader. You need to use the Nougat (stock) bootloader
-
stock dtb will be available in installation image itself?? i may extract and find it.... stock rom will be working on android 7.1 not on any latest version
Yes, unpack stock fw 7.1 and write _aml_dtb.PARTITION on emmc
can you suggest some any other image link for the box which support dvb (liberlec android or any other)
I'll see what I can find later…
and also i am experimenting on current installed aml package to install dtv and other android apps, but it seems to be slow and most of the time does not responds,, i was unable to login in to play store also, may be its due to my internet or box wifi connection, i hope, it will get better as i spend more time with it.
For the time being, you have to adapt the DTV APP to the current Android version. Start Logcat and see what errors occur. Decompile, correct errors and recompile. Does eth connection work in the new ATV9 version? Do you have a 100 or 1000 Mbit interface?
-
Yes, you can reinstall stock fw. However, please note - first run init 3, then you have to write stock dtb to emmc in order to partition it for the respective Android version. Then start the sdcard upgrade as normal with aml_upgrade_package. Regarding emulators - I don't know my way around here.
-
but in this software there is no dtv app. i am not able use tv tunner(satellite channels )
You are welcome
DVB tuner support is only integrated on the kernel side. You can implement DTV in the Android later. Unfortunately, I no longer have a test device to do this. Use LibreElec for these purposes.
-
