Posts by bumerc

Quote from s4shail

but putty window can't stops running codes when power is plugged in

Short the pins and and press the space bar on the keyboard. This aborts the autoboot

s4shail

To avoid the installation errors, perform the following steps in the u-boot terminal (gxl_p230_v1#):
1. Copy u-boot.bin and gxl_p230_2g_pie.dtb to the FAT partition of the previously prepared mSD card. Boot the box from the mSD card and execute the following commands:

store disprotect key
store init 3
reset

2. Write the u-boot.bin into the eMMC

fatload mmc 0 ${loadaddr} u-boot.bin
store rom_write ${loadaddr} 0 100000
reset

3. Write the *.dtb file into the eMMC (partitioning)

fatload mmc 0 ${loadaddr} gxl_p230_2g_pie.dtb
store dtb write ${loadaddr}

After these steps you must now be able to boot from the LibreElec SD card.
Insert the LE SD card into the box and execute this command in the u-boot terminal:

run update

or use the RESET button.

I will upload Android IMG a little later...

Very good, the new u-boot works now. I'll do an IMG update on the weekend and send you the download link via PM

Quote from s4shail

when i press on make with selected bin file, it formats the card in fat32 and then shows success.

but sd card shows empty, then i copied the provided bin file manually on sd card. & booted the box with sd card, with recovery button pressed,

but no benefit, it still initializing on 720mhz.... may be it's not booting through SDcard....

That's right - Bootcardmaker writes the u-boot.bin from the 0 sector into a non-partitioned area on the SD card and creates a new partition table + formats it in FAT32. You do not have to copy the u-boot.bin to the FAT partition. Plug the mSD into the box, short-circuit the eMMC pins 29-30 and switch the box on. After 2 sec. let go of the pins. In this case, the processor ROM BL1 searches for the BL2 from the 0 sector on the mSD card

Quote from s4shail

Do not know how to burn bin file to sd card

Read here -> Method 3

This is the wrong bootloader that you installed earlier. The new u-boot initializes the RAM at 768Mhz

Quote from s4shail

Failed to install the rom provided by bumerc (by nand pin short method)

attaching logs and screen shots for information

Please guide me further........

Small bootloader update for Samsung LP memory..

1. Extract the *.7z file and burn the u-boot.bin to the mSD card. Use Amlogic BootcardMaker for this.
2 Now start the box with the inserted mSD card and post the uart log.

u-boot.bin_p230_lpddr3.7z

Quote from dtech

I think you should get a factory USB A-A cable instead of a DIY cable.

I don't care which firmware can hudyj flash to the device, the point is that EVERYTHING should work on the box. (Ethernet too!)

Please keep in mind that this is the LibreELEC forum, so this is not the place to advertise your own Android creation.

It is only a help for those who want to restore their device. Fantasies about advertising are superfluous here my friend.

Quote from dtech

Now you just plugged in the UART and got this output, or did you even manage to flash the image I linked earlier?
Because what you copied from letter to letter is the same as what creited copied in the first post.

I don't think the image for the KI Pro would work because KI Pro has Gigabit Ethernet and Broadcom/Ampak wlan chip.

If the PCB ID is the same (KI PLUS S905D 1G 8G DDR3 LR), it should work with my image (KI_PLUS_S905D_v4_OTA-REPACK-20180815).

The ATV ROM I posted already includes the correct WiFi driver and fw. 1g eth has nothing to do with installation for the time being, the TV box would also work without eth.

He could try to install this FW first via the sdcburn method, it is for lpddr3 devices. At least the bootloader should be running. I could add 1G dtb later..

download lpddr3

hudyj

try this FW

s4shail

I have an ATV9 version for this device (experimental), but it works fine. I will send you the download link later by PM.

It looks like you created a short between TX and GND, check this out. Furthermore.. run a driver search in the device manager..

u-boot.bin = bootloader.PARTITION

u-boot.bin.sd.bin = aml_sdc_burn.UBOOT

without a log it's hard to imagine what is happening..

Take a look at the section with flash_firmware_with_u-boot.bin file

the FIP's are also encrypted, extract the original firmware and burn aml_sdc_burn.UBOOT to the SDcard

dd if=aml_sdc_burn.UBOOT of=/dev/sdX bs=1 count=444
dd if=aml_sdc_burn.UBOOT of=/dev/sdX bs=512 skip=1 seek=1

search for cfgload for your device in CE forum and play with it..

Quote from scarface911

this one for the second

External Content pastebin.com

Content embedded from external sources will not be displayed without your consent.

Display all external content

Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

Quote

FEAT:B2F839B2

The manufacturer of this box uses secure boot, ROM BL1 has been programmed to decrypt the signature and can only load original BL2 after decrypting this signature. BL2 what you have burned on SD card is read out, but not loaded due to missing signature

Quote

SD?:0;SD:0;READ:0;CHK:1F

You can also see this in your ABT log, after extracting the ulValue(FEAT) it is automatically switched to DDR_ENC.USB

Quote

[12:15:58 429][HUB8-2][Inf]--Get Encrpt ulValue = 0xb2f839b2

marius1980

compare the bootargs of the two u-boot‘s using fw_printenv, change them if necessary and recompile the u-boot

Do you have HDMI cables and uart connected at the same time?

The values were not accepted. Replace aml_autoscript in the root directory with the attached script, then in the uboot terminal

run update

Quote

When boot to LE/CE with correct dtb it's the same, Beelink logo and SPIDF on/off.

When boot to LE/CE with wrong p212 dtb get LE/CE logo and SPIDF stay on.

sounds like a HW issue. Try to reduce the number of CPU cores gradually and see what happens..

use proper dtb

uboot terminal:

setenv maxcpus 6
run storeargs

or

run bootfromsd

then

setenv maxcpus 4
run storeargs

or

run bootfromsd