Lambert

The question is more about editing .dts but for running LE. I am using another .dts for Armbian which I have not researched yet. Still fight for onboard wlan.

Can I discuss LibreElec here?

So THANK YOU so much for most working rk3318-box.dtb!!! ------------------ But not everything as good as would like. WLAN and USB 3.0 port are still away.

Does Multitool support Terminal window? Exactly! I don't think so... Yesterday I took rk3318-box.dtb from your image, burn my trust.img and starting any Armbian_20.07...current_5.7.8 successfuly. Definitely except yours(not rc) and LE. firefly-dtb-1.txt

I've been attached log with many errors. Did You see it? I find dtb in boot folder but i can't try my dtb: not owner. Can I do enything else? I feel useless...

rk-kernel.dtb - this is device-tree from Android firmware. It's not match for Linux. I need try this: rk3318-N5-NOVA.rar

I understand where: in GPT My MB support MBR only. Sorry. Need some upgrade!

Jock! Your img not contain BOOT partition! Where is .dtb placed for example? There are 3 partitions on SD: first and last are empty. Middle partition has no label, looks like BOOTFS. How it can boot?

Now used Rufus + Your img: the same result as before. (See attach) Will try to burn my Trust.img. (Can You explain me where is error in log?) jock_img_rk3328-box=z29.txt

eMMC was not be erased. I checked it later - all files and folders are remains in their original locations. Pity inner memory is definately dead. Once I tryed to burn your image, but I used balenaEtcher only. Must I shell have try another burner in case maybe? Thank You for your cares!

Did it because I burn correct for my device images maybe? They is 4096 kb lenght both. Yours?

eMMC not be able to be burned as I told before. 5 Burn image to flash proceed about 2sec long. 3 Erase flash was take with couple sec more. eMMC must be forget.

I was run Multitool at last! It could only start this way: 1. Rufus+Multitool.img 2. dd if=trust.img of=/dev/sdb seek=24576 3. dd if=uboot.img of=/dev/sdb seek=16384

There was Android-boot-log from eMMC, ofcouse without SD. I must to had to log the "MultiBoot" booting I guess...

If You explain how - I'll do.

I use Balena in both: under WINDOWS and UBUNTU - same result. Ten times. No boot from SD....

Report. Burn Multitool on SD, insert, turn Power On --> no result: boot Android from eMMC.

Need some help about instructions; "Build or download your preferred Armbian image and a copy of the Multitool" • I can't use Armbian on my box: it's started ok but I can't tune any ethernet connections there. Can I try other OS imge? "Choose “Burn image to flash” from the menu, then select the destination device (usually mmcblk2) and the image to burn" • What exactly type of memory is it talking about here? If it mean "eMMC" - it's useless: eMMC switched to R/O mode. This is my second box with a similar malfunction. BTW I guess more suitable for my case will be "Quick installation instructions to boot from SD Card". Is that true? Next point to clear: -------------------------------------------- Quick installation instructions to boot from SD Card: • If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal eMMC; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use “Backup flash” if you want to do a backup of the existing firmware, then choose “Erase flash” menu option. • Build or download your preferred Armbian image; • Uncompress and burn the Armbian image on the SD Card; -------------------------------------------- Must I format SD before burn "preferred Armbian image" or burn it next on "Multitool"? ----------------------- I attached that log here: Android boot.txt

1. Show me where I can put this log please. 2. eMMC not fully dead: I see two logos during Android boot trying . 3. I'll try definitely. But I'm not sure that I clearly understand those instructions. It may be complicated for me... Thanx for Help!

How I wish it be true but isn't. There is Android boot log with so many errors. Pity I can do nothing with eMMC. I try write/burn Multitool before: still unsuccessful... All "Android-trying" are crashed the booting.

Hi again! Sorry for long silence. I try "Armbian_20.11.0-trunk_Rk3318-box_focal_dev_5.9.6_desktop", but it's no work! Seems like this image has no BOOT partition: "ROOTFS" only. No ".dtb", no kernel... Look yourself: BOOT not existing even in Linux-explorer. Other results is: Install LibreELEC-RK3328.arm-9.2.6-box.img : no wlan but extrenal dongle work OK. Wired - present and working properly. Install Armbian_20.07...5.7.8_focal : no eth0, eth1: wired and wlan not present, not configuring. Fight with it now....

That's it! My fault. Thanx! But I can't edit it no longer. Thanx a lot for help! I'll try yours image definitely soon! There is only one common card left. Until I was waiting for an answer - did something: figured out RX & TX. In order: 1. I burn bionic image (Armbian_20.07_Rk3328-tv_bionic_current_5.7.8.img) first. But SDcard even wasn't found I guess: 2. Then I burn "trust.img" (by: "dd if=trust.img of=/dev/sdb seek=24576") and put "rk3318-t9.dtb"(from here) in the root of SDcard. I got "trust.img" from stock Android Firmware. The log has become much longer this time: what is more password does it required? "1234" mismatch. --- How can I post more than one per day? It's too slow!

Hi all! Have RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND. Need revive this trash any way. Want to try this way but would be nice to be able watch console. Guess this is what I need. But I have no idea where is RX TX. First PIN is GND (rihgt side). Please help! Thanx!