DeltaLima

Just to get sure, you have the "real" x96 mini - can you please post the output of cpu-z (you can download it from playstore) which SOC is identified?

would be interesting how exactly and on the correct way we could extract the DTB on this device - is there a guide for extacting DTB on allwinner devices corretly?

I will close this Topic, because the discussion is going on here Conclusion for this Topic: Choosing a Sony SD-Card solved my problem. In the other topic discuission is going on why the device is picky with SD-Cards. Maybe the wrong DTB causes this behaviour.

Maybe this R69 device is not able to handle at boot stage the Micro SDXC Cards, I think the Sandisk Ultra and Transcent Premium are those. The Sony Card seems to be a "normal" Class 10 SDHC Card, which worked. I order a new SD card, a Kingston SDHC Class 10 - i hope this will work and live longer then the Sony card @ljones0 Could you please post an image of your SD Cards? Would be interesting if the working ones are SDHC oder SDXC

This image is working for me fine: https://dl.armbian.com/beelinkx2/archive/Armbian_5.65_Beelinkx2_Debian_stretch_next_4.14.78.7z unfortunate my sd card died But its booting without kernel panic!

I can confirm this! Thanks! I found a Sony 16GB SD Card and tried it - It boots now the Kernel and also starts the kernel and systemd. Then i get a kernel panic, which I post later

"Glad" to see that another person has the same problem as me with this device! Your PCB pictures looks exatkly the same like mine - so I guess we have the same device. I don't think that's a Rockhip SOC is on there, because your cat of /proc/cpuinfo shows as Hardware also "sun8iw7" which is definitely an Allwinner SoC. To get 100% sure that's an Allwinner i will disamble the heatsink of mine and post a picture later on!

Thanks for the reply! I guess the damaged serial output is caused by my UART Adapter, which is an Arduino Uno with following circuits: I've ordered a "real" UART Adapter to ensure there are no probles caused by that and make debugging easier When the new Adapter is here i will try to interact with the uboot command line. I also thought that this could be the problem. For now I haven't found a suitable DTB File for this device. I tried to extract it from the dumped files, but I only got garbage. I used the file "boot_nandc" from my archive , which is the android kernel, with this tool: github.com/PabloCastellano/extract-dtb Is there any other way to get the correct DTB file for this device?

I tried to dump the /dev/block/nand devices, i just dumped that ones, that looked interesting to me. You can find them here for interest: http://blx274.tk/r69/images.tgz Content of this archive: -rwxrwxrwx 1 marcus marcus 67108864 Jun 30 15:18 alog_nandi -rwxrwxrwx 1 marcus marcus 16777216 Jun 30 15:16 bootloader_nanda -rwxrwxrwx 1 marcus marcus 33554432 Jun 30 15:15 boot_nandc -rwxrwxrwx 1 marcus marcus 16777216 Jun 30 15:16 env_nandb -rwxrwxrwx 1 marcus marcus 16777216 Jun 30 15:17 misc_nandf -rwxrwxrwx 1 marcus marcus 16777216 Jun 30 15:17 verity_block_nande

Thanks for moving the thread into the correct place! Now i've tried a nightly image from Libreelec (https://test.libreelec.tv/LibreELEC-H3.arm-9.80-nightly-20190628-bb9c865-orangepi_pc.img.gz) with a recent mainline u-boot. now i get some more errors: In this log you see when i plugged in and out the power cable. i'm bit confused about "Failed to set core voltage! Can't set CPU frequency" and when he was trying to start something but got stuck there. Maybe this is a useful information: In Android CPU-Z just shows me an Unknown SOC Type with a Clock Speed of 1GHz - I guess the H3 should be able to run at 1,3-1,5GHz. EDIT: This BeelinkX2 image from libreelec https://test.libreelec.tv/LibreELEC-H3.arm-9.80-nightly-20190628-bb9c865-beelink_x2.img.gz just gives me the same: U-Boot SPL 2019.04 (Jun 28 2019 - 10:15:24 +0200) DRAM: 1024 MiB Trying to boot from MMC1 Edit2: Just as note, I also trying different SD-Cards. A Sandisk Ultra 16GB and a Transcend Premium 16GB - Just the same with both cards. Edit3: For case it's helpful, here are the Screenshots from CPU-Z: Edit4: Some links to the device: https://www.cnx-software.com/2019/02/09/wechip-r69-cheap-allwinner-h3-tv-box/ https://www.ebay.de/itm/R69-Quad-Core-Android-7-1-Smart-TV-Box-4K-3D-WIFI-HDMI-H-265-Media-Streamer-DE/133075545075?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649

Good evening! I've bought the R69 1GB TV-Box on eBay some days ago with the plan in mind to run Armbian there. Sadly the box even dont want to start the kernel, it's stuck in U-Boot Loader when a SD is inserted: U-Boot SPL 2018.05-armbian (Jul 31 2018 - 05:08:39 +0200) DRAM: 1024 MiB Trying to boot from MMC1 And then nothing happens. I've tried couple of images. Beelink Image with Mainline and legacy Kernel, RetroOrangePi Images and so on - for now I haven't found a working one. In some other Thread someone mentioned that there are different versions of this device, and i found some Thread where someone also has trouble with the 2GB Version. For the case there are helpful information, here is the android Boot-Log And some photos of the Device: It looks kinda different like the other PCBs i found from the r69, also the Revision "R69-4x4Bit DDR3_V1.0_20181210" i havent seen before when i was searching about this Box Has anyone suggestions what i can try to get there Armbian running? I already tried different dtb, builds, mainline and legacy kernel versions. Thanks for reading! I hope someday Armbian will boot on this little guy!