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…
log
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…
log
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.
Please review and approve as i understand below steps to install image......
Method 1 Steps to install stock android 7.1.2 image
Preparation
1 Prepare boot SD Card with new u-boot.sd.bin
2 copy u-boot.bin
3 Copy stock _aml_dtb.partition on sd card
4 copy repacked stock android image, 02 nos files replaced (bootloader.PARTITION = u-boot.bin , aml_sdc_burn.UBOOT = u-boot.bin.sd.bin )
Installation 1st Method
5 Insert SD card in Box
6 boot from Sd card by pin shorting Method pin 29 and 30.
7 abort auto boot by pressing space key
8 Run Commands
CMD A
store disprotect key
store init 3
CMD B
fatload mmc 0 ${loadaddr} u-boot.bin
store rom_write ${loadaddr} 0 100000
CMD C
fatload mmc 0 ${loadaddr} _aml_dtb.partition
store dtb write ${loadaddr}
CMD D
run update
Method 2 -- 2nd method (copy all partitions), if method 1 fails....
Preparation
1 Prepare boot SD Card with new u-boot.sd.bin
2 copy u-boot.bin
3 Copy stock _aml_dtb.partition on sd card
4 copy all partitions of stock android image with 02 nos files replaced (bootloader.PARTITION = u-boot.bin , aml_sdc_burn.UBOOT = u-boot.bin.sd.bin)
Installation 2nd Method
5 Insert SD card in Box
6 boot from Sd card by pin shorting Method pin 29 and 30.
7 abort auto boot by pressing space key
8 Run Commands
CMD A
store disprotect key
store init 3
CMD B
fatload mmc 0 ${loadaddr} u-boot.bin
store rom_write ${loadaddr} 0 100000
CMD C
fatload mmc 0 ${loadaddr} _aml_dtb.partition
store dtb write ${loadaddr}
CMD D
N/a
CMD E
sdc_update _aml_dtb _aml_dtb.PARTITION normal
sdc_update boot boot.PARTITION normal
sdc_update recovery recovery.PARTITION normal
sdc_update logo logo.PARTITIO normal
sdc_update bootloader bootloader.PARTITION normal
sdc_update system system.PARTITION sparse
CMD F
defenv_reserv -a
saveenv
reboot
Method 1 Steps to install stock android 7.1.2 image
No. Repeated unnecessarily.
1. Write aml_upgrade_package.img on the mSD card with Amlogic Burn Card Maker.
2. Copy _aml_dtb.PARTITION to the FAT partition of the mSD card and rename the * .ini file to * .ini.bak.
3. Start the TV Box from this mSD card and write the * .dtb.PARTITION on eMMC.
4. Remove the mSD card and rename the * .ini.bak to * .ini again.
5. Now start sd card upgrade.
P.S. In your case, the vendor uses the misc partition, which contains certain key signatures for certain applications. A manual installation of individual partitions does not help you, as the misc partition also has to be installed. Otherwise the stock fw will not run.
Display MoreNo. Repeated unnecessarily.
1. Write aml_upgrade_package.img on the mSD card with Amlogic Burn Card Maker.
2. Copy _aml_dtb.PARTITION to the FAT partition of the mSD card and rename the * .ini file to * .ini.bak.
3. Start the TV Box from this mSD card and write the * .dtb.PARTITION on eMMC.
4. Remove the mSD card and rename the * .ini.bak to * .ini again.
5. Now start sd card upgrade.
above Method fallowed
WiFi Bluetooth still not working
error system UI has stopped is flashing on screen again and again....
edit
In my observation, system UI stopped error comes when,
"system first time initialization of app" not come on android first boot..
avc: denied { write } for pid=4700 comm="ndroid.systemui" name="property_service" dev="tmpfs" ino=8243 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:property_socket:s0 tclass=sock_file permissive=0
Sys UI
Try to create a new rule for property_socket in sepolicy, allow write access to the sock_file:
and recompile sepolicy..
WIFI
[ 111.636750@1] dhdsdio_download_code_file: Open firmware file failed /etc/wifi/4335/fw_bcm43455c0_ag.bin
[ 111.649276@1] _dhdsdio_download_firmware: dongle image file download failed
Check that the /etc/wifi/4335/ directory contains the correct fw -> fw_bcm43455c0_ag.bin
Now Wifi is working, Thanks for guidance and Patience..
Bluetooth is still not turning on.., may be "Bluetooth: SCO socket layer failed" is the reason for it.
successful boot log attached
Check if BCM4345C0.hcd FW exists in bluetooth folder.
If necessary, you can download it here..
checked
files exists on path
\system\etc\bluetooth\6255\
BCM4345C0.hcd
bt_vendor.conf
\system\etc\bluetooth\4335
bcm4335.hcd
bcm4335_prepatch.hcd
bt_vendor.conf
\system\etc\bluetooth\
4355 folder
6255 folder
auto_pairing.conf
bcm4335c0.hcd
blacklist.conf
bt_did.conf
bt_stack.conf
bt_vendor.conf
Try dropping BCM4345C0.hcd into /system/etc/bluetooth. I cannot read your log because of the different character encoding. Use UTF-8.
Is there any way, that i use dvb s2 tuner (internal) with kodi app
Try dropping BCM4345C0.hcd into /system/etc/bluetooth. I cannot read your log because of the different character encoding. Use UTF-8.
Dear sir
above method does not worked for me.
Regards,
I can't help you without logs
May I re-open this discussion to learn how to find the eMMC pins 29-30 on a Samsung eMMC from S905 box ?
Thanks
Display Moretoday i tried USB burning method
Replace all 04 files, (stock image used, provided by you previously)
and packed the image and burned through USB,
Device booted after reset, but it was giving error "system UI has stopped" after booting
then in same image repacked with replacing only 02 nos files only uboot and uboot sd
and after usb burning, device booted, but wifi and bluetooth not working in this image
uart log of successful boot is attached...
Please can you help me ?I have the same problem. Can you please share your repacked img for usb burn tool
KII PRO Hybrid STB
Hallo,
is there someone from "DACH" or nearby Europe who can bring my bricked device back to life?
I tried a firmware update. A logo or image appeared on the screen for a very short time. I couldn't see what it was. It was just a flash.
From then on the device was completely dead. And hasn't done anything since. I have read all the tips here. But that's technically too high for me. And I would like to have someone do it who understands something about it and has already done it.
ist hier jemand aus "DACH" oder dem nahen Europa, der mir mein gebricktes Gerät wieder zum Leben erwecken kann?
Ich hatte ein Firmwareupdate versucht. Es kam ganz kurz ein Logo oder Bildchen auf dem Bildschirm. Was es war, konnte ich nicht erkennen. Es war nur ein Aufblitzen.
Ab dann war das Gerät komplett tot. Und tut seitdem nichts mehr. Die ganzen Tipps hier habe ich zwar gelesen. Aber das ist mir technisch zu hoch. Und ich würde das gerne jemanden machen lassen, der davon was versteht und schon gemacht hat.