chinhhut

And perhaps try with different SD cards. I first used some expensive recommended 64GB SanDisk card and nothing worked then I tried a "no-name" cheap 8GB card and it worked perfectly. I think it's up to luck when it comes to the SD cards. The recommended expensive cards might work more often than the cheap ones, but sometimes it's the other way around. 

@chinhhut
Will try to explain you what loader is with an analogy: in normal pc you have bios and master boot record. Well, maskrom is bios and is contained in the soc itself, loader is a sort of master boot record and it enables the emmc and ddr.
You can have a look here
http://opensource.rock-chips.com/wiki_Boot_option

 

I did extract it by a working firmware using a tool that unpacked the whole firmware. Try to google for RK3xxx_firmware_tools_5.23.1_by_SergioPoverony.zip and leave alone that github since it is just one piece of the puzzle. The detailed infos how to get a working loader are in the rockchip instructions

 

Of course and the command would be rkdeveloptoo rl 0x0 etc etc etc ( try rkdeveloptool -h to get the help)
But if you are lucky that works multitool, well that is the easiest way to clone and clone back

That's true, because the sdcard controller is not where u-boot and kernel are told by device tree to look for.
 
Adapting the device tree for the kernel is easy, but u-boot dtb requires a recompilation.
 
When armbian is installed, u-boot is totally responsible for the boot process. It scans the devices to find a valid bootable system and the order is first sdcard, then USB and finally internal eMMC.
If you have a lucky USB stick, you could try to put the Multitool on a USB stick and see if boots from there. I say "lucky USB stick" because u-boot USB code is buggy and does not always work.
 
All kind of regular images (armbian, multitool, libreelec if available too...) can be burnt on USB stick or USB external hard drive: u-boot should prefer booting from there (if the buggy code doesn't kick in).
 
 

Maybe with another USB stick or drive it may work. Also consider to use all the USB ports of the board, since they are not all the same. u-boot is picky.
 
About the backup, indeed you can burn the multitool backup with rkdeveloptool. You just need to decompress it first.

@fabiobassa @jock @hexdump 
Thank you once again for your support.
 
By the way, I still confused how to get the MiniLoaderAll.bin as you suggested.
That file is built by yourself or pick up from here:
https://github.com/rockchip-linux/rkbin/tree/master/bin/rk33
 
As I checked, from the official Rockchip repo, there are several boodloader files related to RK3328 and I don't know how to choose the correct one.
 

@jockI have one more question. Is there a way to dump the whole eMMC to .img file then using "./rkdeveloptool wl 0X0 file.img" to clone to new box. It looks similar to the backup and restore function from your Multitool. 
That's great if we can use some function of Multitool under Linux.
 
THank you.

Thank you for detail explanation in a basic way.  I can understand the logic of booting process now.
 
After booting from eMMC successfully, I try to boot from SD card again to try the multitool but not success. At current, my box still only can boot from eMMC.
 
I guess using rkdevelopertool to backup will create the .img file that could be restored using "rkdeveloptool wl 0X0 yourimage.img" command, right?
I will try to backup the entire eMMC using rkdevelopetool and report the result later. 

I used Etcher to flash the Armbian image to the SD card as usual but it is unable to boot from SD card. 

I'm going to follow your guide but I just want to confirm about the whole story from your idea.
According to your guide, the MiniLoaderAll.zip contain the u-boot of the box? After flashing it to the eMMC successfully, the box may support to boot from USB and unable to boot from Android anymore? 
 
One more question, how to get the MiniLoaderAll.zip as your attachment? You extract it from similar Rk3328 box or that's built manually by yourself.
Thank you once again for detail suggestion.

@fabiobassa @jock I've followed your guide and got success. Thank you so much.
root@mybox:~/rkdeveloptool# ls 99-rk-rockusb.rules Makefile.in RKComm.h RKImage.h RKScan.h cfg configure.ac main.cpp CMakeLists.txt Property.hpp RKComm.o RKImage.o RKScan.o config.h.in crc.cpp main.o DefineHeader.h RKBoot.cpp RKDevice.cpp RKLog.cpp Readme.txt config.ini crc.o parameter_gpt.txt Endian.h RKBoot.h RKDevice.h RKLog.h aclocal.m4 config.log gpt.h rkdeveloptool Makefile RKBoot.o RKDevice.o RKLog.o autom4te.cache config.status license.txt Makefile.am RKComm.cpp RKImage.cpp RKScan.cpp boot_merger.h configure log root@mybox:~/rkdeveloptool# ./rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=101 Loader root@mybox:~/rkdeveloptool# ./rkdeveloptool rd 3 Reset Device OK. root@mybox:~/rkdeveloptool# ./rkdeveloptool db MiniLoaderAll.bin Opening loader failed, exiting download boot! root@mybox:~/rkdeveloptool# ./rkdeveloptool db /root/MiniLoaderAll.bin Downloading bootloader succeeded. root@mybox:~/rkdeveloptool# ./rkdeveloptool wl 0X0 /root/Armbian_21.11.0-trunk_Rk3318-box_bullseye_edge_5.14.14_minimal.img Write LBA from file (100%) root@mybox:~/rkdeveloptool# ./rkdeveloptool ---------------------Tool Usage --------------------- Help: -h or --help Version: -v or --version ListDevice: ld DownloadBoot: db <Loader> UpgradeLoader: ul <Loader> ReadLBA: rl <BeginSec> <SectorLen> <File> WriteLBA: wl <BeginSec> <File> WriteLBA: wlx <PartitionName> <File> WriteGPT: gpt <gpt partition table> WriteParameter: prm <parameter> PrintPartition: ppt EraseFlash: ef TestDevice: td ResetDevice: rd [subcode] ReadFlashID: rid ReadFlashInfo: rfi ReadChipInfo: rci ReadCapability: rcb PackBootLoader: pack UnpackBootLoader: unpack <boot loader> TagSPL: tagspl <tag> <U-Boot SPL> ------------------------------------------------------- root@mybox:~/rkdeveloptool# ./rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=101 Maskrom  

@chinhhut - this might be some interesting reading too regarding boxes, which cannot boot from sd card: https://github.com/hexdump0815/u-boot-misc/issues/2
 
best wishes - hexdump

@chinhhut
Glad you got success .
Don't forget to put a like that helps @jock and myself in community reputation
 
 
 

@chinhhut

@fabiobassa @jock I've followed your guide and got success. Thank you so much.
root@mybox:~/rkdeveloptool# ls 99-rk-rockusb.rules Makefile.in RKComm.h RKImage.h RKScan.h cfg configure.ac main.cpp CMakeLists.txt Property.hpp RKComm.o RKImage.o RKScan.o config.h.in crc.cpp main.o DefineHeader.h RKBoot.cpp RKDevice.cpp RKLog.cpp Readme.txt config.ini crc.o parameter_gpt.txt Endian.h RKBoot.h RKDevice.h RKLog.h aclocal.m4 config.log gpt.h rkdeveloptool Makefile RKBoot.o RKDevice.o RKLog.o autom4te.cache config.status license.txt Makefile.am RKComm.cpp RKImage.cpp RKScan.cpp boot_merger.h configure log root@mybox:~/rkdeveloptool# ./rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=101 Loader root@mybox:~/rkdeveloptool# ./rkdeveloptool rd 3 Reset Device OK. root@mybox:~/rkdeveloptool# ./rkdeveloptool db MiniLoaderAll.bin Opening loader failed, exiting download boot! root@mybox:~/rkdeveloptool# ./rkdeveloptool db /root/MiniLoaderAll.bin Downloading bootloader succeeded. root@mybox:~/rkdeveloptool# ./rkdeveloptool wl 0X0 /root/Armbian_21.11.0-trunk_Rk3318-box_bullseye_edge_5.14.14_minimal.img Write LBA from file (100%) root@mybox:~/rkdeveloptool# ./rkdeveloptool ---------------------Tool Usage --------------------- Help: -h or --help Version: -v or --version ListDevice: ld DownloadBoot: db <Loader> UpgradeLoader: ul <Loader> ReadLBA: rl <BeginSec> <SectorLen> <File> WriteLBA: wl <BeginSec> <File> WriteLBA: wlx <PartitionName> <File> WriteGPT: gpt <gpt partition table> WriteParameter: prm <parameter> PrintPartition: ppt EraseFlash: ef TestDevice: td ResetDevice: rd [subcode] ReadFlashID: rid ReadFlashInfo: rfi ReadChipInfo: rci ReadCapability: rcb PackBootLoader: pack UnpackBootLoader: unpack <boot loader> TagSPL: tagspl <tag> <U-Boot SPL> ------------------------------------------------------- root@mybox:~/rkdeveloptool# ./rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=101 Maskrom  

@chinhhut Probably Perhaps your h96 max is unable to boot from sdcard because the sdcard is allocated to the "alternative" controller. Much more important than the box name is the board name/signature though.
From what I have seen on the forums, this breaks any kind of sdcard boot or update. I guess it is just not supposed that the tvbox manufacturers use this alternative controller for sdcard, so there is the need to find an alternative solution to boot, which I'm not yet aware of.
USB boot is available only if u-boot from armbian image is installed in the eMMC. The stock u-boot does not care about USB devices.
 
This is the most serious issue that is preventing me to ask to merge rk3318/rk3328 tvbox support in main Armbian source code.

I have the plus. However, I was never able to boot Armbian from the SD card, I used Multitool from this thread. Added the Armbian ISO to it, multitool booted fine from the SD card, then took a backup of the stock ROM with multitool and then erased eMMC and installed Jock's Armbian via multitool. 
 

how do get the dts file for my box?
do i need to use multitool to dump it first?
i want my clock to work in armbian along with working graphics and a decent overclock
i know that dmssru on 4pda ru forums made a semi decent attempt to overclock android 9 for h96 max but my wifi and bt would not work properly.
and how do i get the metal can off my wifi module? it seems to be soldered on.
here is the firmware for the h96 max modded by dmssru on 4pda
https://drive.google.com/drive/folders/1W7BkOj1Q16O_wvlLlFh06v_D5Yol9KvE
and here is the tools and Firmware , Software & Drivers
https://drive.google.com/drive/folders/1vevBj3JySrkcurvnLPqU6aY-5APtXHYI
and here some random builds as well
https://drive.google.com/file/d/1w1KgbetDIIIU08-jmN3ll_0IF9cR5Lic/view
also this...
https://drive.google.com/file/d/1l_WECaMMWS0BI0rIY7uiWcw6X_BPu-yZ/view?usp=sharing
 
Hope These help

I have a T9 box (2G memory & 16GB flash) and just install Armbian 21.11 - Debian Bullseye minimal - mainline kernel 5.14.14 successfully to eMMC according to the guide.
Everything seems to work well until I tried to unplug the adapter and then replug the adapter again. After that,  the box unable to start even I tried to unplug/replug the adapter several times again. There is only black screen via HDMI output.
Of course, I can install Armbian to the eMMC from scratch again but I'm afraid the "black screen" error above will happen.
@jockdo you have any suggestions to fix this? Please let me know if you need any detail steps or log to debug.
Thank you very much for your great work again.

I did not run the rk3318-config yesterday, just keep default. But I run the "apt get upgrade" and also forgot to run the following command after installing to eMMC:
Run apt-mark hold linux-image-edge-rockchip64 linux-dtb-edge-rockchip64 to avoid the upgrade of kernel with the armbian official one, since it still does not contain rk3318 That would be the reason the kernel of my box was updated to the latest one from armbian official. It did not contain 3318 dtb so the box was unable to boot.
 
Today, I just re-install from scratch again then run the hold command to prevent to upgrade the kernel. The "black screen" error is not happened again up to now even unplug/plug about 3 times.
 
Thank you very much for your quick response. 

Hi,
I have a TX3 Mini with 1.6 motherboard. I've installed Armbian on emmc and it works great. I've also used the same method mentioned to get AP6330 wifi working.
 
I share this strange issue happening sometimes randomly. I power off the device by plug off directly, because it doesn't work the shutdown.
 
Sometimes when I plug off from power the device, next time I power on it doesn't boot, showing only a black screen (not showing the "hit any key to stop autoboot..." message). 
When this issue happen, I perform the following steps to solve:
1. Power off the device and plug a configured USB drive with Armbian. This is the same USB drive from where I installed initially Armbian.
2. Power on the device (without pressing any button) and the system starts OK from emmc.
3. Power off the device and unplug the USB drive.
4. Power on the device without nothing connected. It boots OK from emmc.
 
Anyone knows the reason about this issue and why it's solving by simply power with the USB drive a single time?
 
Thanks!

latest release works for me (Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img.xz)
extlinux.conf:
------------------------------------------------------------------------------------------------------------------------
LABEL Armbian
LINUX /zImage
INITRD /uInitrd

 
FDT /dtb/amlogic/meson-g12a-x96-max.dtb
APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
------------------------------------------------------------------------------------------------------------------------
rename u-boot-s905x2-s922 to u-boot.ext