rkdeveloptool shows device, absolutely no command works

[86dd]

Hello,
I have a NanoPC T4 with an RK3399,
Recently I was able to use rkdeveloptool just fine, but yesterday it would not work anymore, absolutely not.
Every command failed, even though it was listed on the devices list.
I tried 2 computers and one VM, multiple cables and usb ports but absolutely nothing seemed to make it work.
The exit code is always 1, there is nothing useful logged and there is nothing in the dmesg.

# rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=101    Maskrom
# rkdeveloptool ppt
Read GPT failed!
Read parameter failed!
Not found any partition table!
# rkdeveloptool ef
Starting to erase flash...
Getting flash info from device failed!
# rkdeveloptool td
Test Device failed!
# rkdeveloptool rd
Reset Device failed!
# rkdeveloptool rid
Reading flash ID failed!
# rkdeveloptool rfi
Read Flash Info failed!
# rkdeveloptool rci
Read Chip Info failed!
# rkdeveloptool rcb
Read capability Fail!
# rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=101    Maskrom

This is what I am always getting, no matter where and how I connected it.
I'm at a point where I seriously don't know what to do anymore and I feel like I'm about to go crazy.
Is the board defective? Because I honestly just can't think of any other reason, especially since there is no logging at all

[7ROLI101]

I think it's because you need to do the download boot command first.
Try rkdeveloptool db (name of the loader file).
I've had this same thing happen to me using a Radxa CM3, and that was how I solved my issue.

[wtjcn]

https://opensource.rock-chips.com/wiki_Rkdeveloptool
use download boot command to make target init DRAM and run usbplug;

[anomaly256]

Unsure if it’s the same problem or not but I’m experiencing the same symptom even after downloading the spl. It stays in maskrom mode and no other commands work.

BUT, using the windows rkdevtool and the exact same SPL does work. Something isn’t right with this Linux version.

[ziguana]

Just hit the same issue, wtjcn's comment fixed it.