Rupa X88 Pro 13 - RK3528 board with images

[SuLorde]

A question from a beginner: how do I install it to use it for the first time? Should I use a flash drive and Rufus, or is there another way? I didn't quite understand, and I couldn't find any clear information.

[johlnx]

Use Armbian Imager to create SDcard with curent Release.

Connect HDMI Monitor and USB Keyboard.

Put Sdcard into sdcard Slot and Power the Box. 

Follow instruction on Monitor

[SuLorde]

I tried installing it to the internal eMMC memory, and now it won't boot. It looks like it'll have to stay on the SD card—or is there a way to install it? 

[Joao Cordeiro]

On 6/29/2026 at 8:40 AM, SuLorde said:

now it won't boot

You are not the 1st to do this:

 

Let me explain the problem first.

 

The CPU itself, without any storage attached, has a built-in U-Boot.
However, this U-Boot does not initialize video output, so you won't be able to see it on an HDMI screen. (The good news is that it usually initializes the serial port.)
This U-Boot reads environmental data from a data blob on the MMC (usually within the first 10 MB of the disk).
This environmental data tells the U-Boot the sequence of commands needed for the MMC/USB U-Boot to boot.
Once the MMC/USB U-Boot boots, you get video output.

The problem is that you deleted the data blob containing the environmental data from the MMC, so the CPU's U-Boot does nothing. It just loops, saying that it found no device to boot.

 

If you have a serial adapter, it is possible to interact with this CPU U-Boot. Pressing Ctrl+C (in a terminal that does not intercept Ctrl+C—my advice is to use PuTTY, even on Linux) should stop whatever it is doing.
By interacting with this CPU U-Boot, you can instruct it how to boot your MMC or USB U-Boot.
However, you will have to do this manually every time you boot.

 

To fix the issue, you need to restore that data blob containing the properties to its specific location on the MMC.
I don't know where it starts or what format it uses, so I was unable to recreate one from scratch.
My way of fixing this was to find a backup of the original MMC and restore the first GB.

 

So, did you make a backup? If yes, you can restore it with some serial magic.
If you did not make a backup, you can search for one or ask someone who has one. (check that this thread for the other guy's solution)