Mierscheid

First of all, more than heartfelt thanks for all your effort and the excellent and detailed explanations that serve as self-help. I don't know what's wrong with me. I'm afraid the first time I didn't activate bootloader. *facepalm* Therefore, rkdevelopetool does not work the second time until I loaded the Bootloader. *sic* So the procedure is as follows (on Ubuntu, hence sudo *sic*). I wrote it down for myself, but I will publish it on my german website with reference to you and the forum. Restore We first have to activate the real MaskROM mode and then restore the backup of our firmware. Note: This is actually RockUSB mode, which cannot write the first 0x2000 sectors, even if lsusb reports "2207:320a Fuzhou Rockchip Electronics Company RK3288 in Mask ROM mode". 1) Press the reset button (download button). 2) Plug the USB-A to USB-A cable into the slave USB (OTG) port of the box. 3.) Release button 4) Download the bootloader to the box: sudo ./rkdeveloptool db ../rk32/rk3288_ubootloader_v1.01.06.bin 5) Activate bootloader ./rkdeveloptool ul ../rk32/rk3288_ubootloader_v1.01.06.bin 6) Delete Flash: ./rkdeveloptool ef Only now is the Mask-ROM-USB-Mode also activated! 7) Restore image sudo ./rkdeveloptool wl 0x0 tvbox-backup.data Now the original Android 5.1 from Hannspree boots again. Strange: As soon as you do it right, it works. But without your explanations I wouldn't have noticed that I had forgotten the line with the more active one. It looks identical at first glance, so I must have made a mistake in the line. I'm sorry for all the effort you had to put in. I will now try out some Armbian images (only find Asus TB-2 instead of -S).

Just for the record and for others who may have similar problems in the future: I restored the multitool backup using sudo ./rkdeveloptool wl 0x0 tvbox-backup.data. The unpacked image had no extension. I simply added ".data". This may have been a mistake, because the box seemed to be really bricked now, because the box doesn't start anymore and no LED lights up. I no longer get any input via picocom, only brief confused characters when I press the reset button. Even without pressing the reset button, the box appears via USB as "2207:320a Fuzhou Rockchip Electronics Company RK3288 in Mask ROM mode". It also does this without me connecting the power supply. rkdeveloptool can no longer do anything with the box. Every operation "failed". I removed the battery and left the board without power for a while, but this behaviour does not change. All right, so now I have plugged in the multi-boot SD card and lo and behold: now I can get back into the multitool. This box seems to be unbrickable. I installed the above-mentioned Armbian image again, but the screen remains black. Via picoterm I see that the start-up procedure stops at "Starting kernel ...". I will now try another image and report back. Or how would you proceed? And yes: the device tree is very reminiscent of the Kext (kernel extensions) of macOS, which you sometimes have to deal with if you want to get natively unsupported hardware to work on a Hackintosh. Unfortunately, I would have to get _some_ OS to work on the box before I could read out the configuration. Dumb. Edit: Oh yes, okay, that doesn't work properly, because after the Armbian installation it is again not possible to boot from the SD card. So I wanted to install the original image again with the rkdeveloptool, even if this is not executable, you can still boot from an SD card with it. But now I have the problem that the rkdevelop tool no longer recognises the box. Every operation ends in a failure, even if lsusb shows me the box correctly. Status: Box boots with non-functioning armbian (kernel panic?) Box no longer boots from SD card rkdevelopetool can no longer read the box (Getting flash info from device failed! Any suggestions? 🙂

Hi Jock! Sorry about the threads, I thought the box in the Q8 thread was completely wrong. There are days when it's best not to do anything. Lie quietly on the sofa and passively watch a complete series. Then you don't stress yourself or others. I had forgotten to mention that the box no longer started with Multiboot and I therefore tried to get the unpacked backup onto the box with the RockChipBatchTool (and other, apparently more or less identical tools). I changed the monitor in between, thought nothing of it, but this monitor shows no picture with this box. When I use another monitor, I see that the box does(!) start with Android 7.1, which means that the update with the tools for the Rikomagic TV-Box worked despite the error message! I don't know why the box no longer appears as a USB device, maybe it's because of the update to 7.1? The joke of the whole story is that just now, on my own website with articles on smarthome devices, a comment came in with a question about reading out a smart meter under an article on window contacts, to which I said please work through the instructions again in a structured and step-by-step manner. I will heed my own advice and now follow your instructions step by step in the normal RK8288 thread. Read. Read again. Understand. Only then begin. Thank you for your work, your answer and your efforts. I will now make an effort to work properly and not have panic attacks if something does not go as expected. Regards Mierscheid Edit: Okay, one moment ... Q8 means RK3288? Every RK3288 is also a Q8-Board? My understanding of the text (and even numbers!) is an absolute disaster. I will use the instructions for the Q8-Board again. Edit 2: That is my board "R36-V2.2", Q8 ist a real board, not a board-family. I have access again via USB-MaskROM-Mode. I was just so stupid and somehow mixed up the port. How stupid can you be? 😞 Now I have burned Multitool on a SD-Card again, but it doesn't start at all. Via picocom, I get this error message at the end: I'm a bit confused that it recognises the board as Q8. Or does it misrecognise it? Is my board compatible with the Q8 after all? And at first I was still able to boot with Multitool. It's the same image from my download folder that worked.

I have a Hannspree TV box with RK3288 (Android mini PC) on which I would like to install Armbian according to instructions from this forum (Multitool). Multitool booted Backup of the original firmware Flash written with Armbian. Reboot (did not happen, box does not respond) Power off and power on. Monitor stays black, monitor goes into standby Just now I have to note that there would have been a more appropriate thread (without Q8), so I fucked up from the start. I tried to recover the box with the original firmware I had backed up with the multitool using a USB-A to USB-A cable. But this image was not recognized. I tried to install the Rikomagic firmware (MK902II seems to be identical in construction), but it kept aborting at 99% (download firmware fail). I tried several times, but after some time the recovery tool under Windows (*sic*), did not recognize the box. Also under Ubuntu, the box no longer appears under lsusb. I made a connection via UART. The first error message is: GPT 0x3337df8 signature is wrong recovery gpt... GPT 0x3337df8 signature is wrong recovery gpt fail! UBoot still seems to work? CPU: rk3288 cpu version = 0 CPU's clock information: arm pll = 8160000HZ periph pll = 3000000HZ ddr pll = 3960000HZ codec pll = 5940000HZ Board: Rockchip platform Board Uboot as second level loader or not? #Boot ver: 2019-07-11#2.54 empty serial no. normal boot. checkKey vbus = 1 board_fbt_key_pressed: ir_keycode = 0x0, frt = 0 no fuel gauge found no fuel gauge found Rockchip UBOOT DRM driver version: develop-v1.0.0 Warn: route-hdmi: can't find connector driver read logo on state from dts [1] no fuel gauge found Sorry, this is rather new territory for me. Anyway, the boot process ends with: [ 19.162284] init: Starting service 'clear-bcb'... [ 19.173024] fs_mgr: Warning: unknown flag resize [ 19.959316] read descriptors [ 19.959347] read strings [ 19.959992] pcd_pullup, is_on 1 [ 20.162759] fs_mgr: Warning: unknown flag resize [ 20.165006] init: Service 'clear-bcb' (pid 1802) exited with status 0 Nevertheless a Linux starts: cat /proc/version Linux version 4.4.143 (work2@czkj) (gcc version 4.9 20150123 (prerelease) (GCC) ) #23 SMP PREEMPT Fri Jul 5 16:35:06 CST 2019 But there is no signal output via HDMI. How should I proceed to bring the box back to life? Does anyone have a link to a manual that could help me? Thanks in advance Mierscheid

Hi Jock, I have a Hannspree AK01 Mini PC with RK3288. It seems to be identical to the Rikomagic MK902II. Yes, I should have read through the entire thread before, but it's too late now. I went through the first tutorial: Multitool and Armbian_22.05.0-trunk_Xt-q8l-v10_bullseye_current_5.15.35_minimal.img.xz Multitool booted Backup of the original firmware Flash written with Armbian. Reboot (did not happen, box does not respond) Power off and power on. Picture stays black, monitor goes into standby Have I bricked the box? 😞 Can I possibly still access the box via USB2Go? It doesn't have a micro USB port, but I just ordered a USB A to USB A cable. Or is a rescue only possible via UART? Thanks in advance Regards Mierscheid