Clonazepunk

Hi! @balbes150 provided a working image for a RK3399 box. Maybe you should give it a shot. Good luck!

Hi! @hexdump is right I think the best way to figure it out is first, to find out what wifi chip the board has. If the package armbian-firmware-full has support to it, you're good to go I had good experiences with rockchip boxes. They're the cheapest ever, and always with the same two supported wifi chips (ssv6051 or ssv6252). If you want to bet on one of those cheap Chinese boxes,put your bets on MX9 or MX10 boxes. MXQ boxes has a good chance to come with a rockchip CPU, but there arr fake ones with the AllWinner H3 CPU (whose wifi isn't supported). But it also worthy trying Take your time finding a box and come back if you need support with it! Good luck. (You'll need it lol)

Hi! We are here to help, but first we need more info from you Which Armbian build are you using? Can you tell? As the log says, the error is in the U-Boot parameters, but can me something more. Can you detail your problem a bit more? Starting from the image download

Just to add: You have a powerfull toy with you. It's a waste to use it as a paper weigth!

After some research, i realized the same error happened when users tried to update their ROM from a LPDDR3 memory to a DDR3 Box, or vice versa Uploading software on Amlogic CPUs is like a surgery. I think that's why the Meson support is kinda poor compared to Rockchip CPUs. Well... There's no unbrickable device. Maybe you should try the short pin method and skip the boot from e-MMC, or even more radical: Remove the e-MMC chip I was able to save a fully bricked (surprisingly) rockchip box using this method. It's always my last resource If you need any tips about the electronics, feel free to ask!

Hi! Those boxes play flawlessly on Android. I think it's a matter of time and better drivers will come up The best results i got was using Arch Linux and lima (open source drivers for Mali GPUs). Maybe you should give it a try. PM me if you need help with this! Good luck

I had the same problem with some versions of the Amlogic S905W processor My workaround was to short the UART TX pin to ground using a small resistor. It fakes a UART connection and the boot continues If the step fails, try the same with the RX pin. Good luck!

Hi! This screen says your board is booting properly. See? The U-Boot starts, finds your extlinux.conf file and starts the kernel as well If the screen blanks after a while, it's probably a HDMI fault. Try to connect your box to a serial console via UART (open the case, and you'll find the pins) To do this, you'll need a Serial to USB converter (such as CH340 or FT232. Both cheap as heck) You'll notice that the boot continues from there. If so, you'll need extra configuration to your HDMI inside your extlinux.conf file. Try the serial and send us the terminal output. We're here to help! Good luck!

Hi! Did you check alsamixer? Had the same problem on my S905W box. I just needed to alternate between I2S / SPDIF and it worked like magic If you have any doubts, post an image of how your alsamixer screen looks like

That's weird. What happened before that? Did you try to update the bootloader or something like that? The bootloader should first look for a SD Card bootable system. So, flashing it through UART is not possible, although you still can flash an Armbian image via USB using aml-flash-tools Also, burning the stock android image would also do the trick. with the stock ROM working, it'll begin to boot from SD again For Android, use this tool: https://androidmtk.com/download-amlogic-flash-tool

Hi! The simple fact that it still shows serial output and running the bootloader mean that the box isn't totally dead. Something is corrupted inside the eMMC installed system. Did you already try to boot it via SD Card? The Amlogic CPUs try the SD card before the eMMC storage (at least the ones I have). I don't know anyone who's supporting S905x3, but maybe you can find a booting image for it in this forum. Burn it to a SD Card and see if your box responds. Hope it helps somehow Good luck!

Well...I can't explain why it worked with me You have a point

Try the PhoenixSuit solution Your box doesn't need root accees on Android. There's a button somewhere in your board that triggers FEL mode Every Allwinner processor has it More info at https://linux-sunxi.org/FEL When in FEL mode, you can plug your board on your PC using a USB male to male cable. It allows direct access to the internal memory, thus allowing to dump it I found the cable available online, but with two old USB cables and some electric tape you can build your own lol Besides the PhoenixSuit, there is also the sunxi-fel tool. It allows the memory dump. Just tried with Allwinner H3 and Allwinner F1C100 and it works like a charm

That's not true We have a lot of people who could boot Armbian on their boxes by using the original DTB file. Sometimes, is the only way

So, Allwinner chips have a flashing tool called PhoenixSuit I'm not sure, by maybe you can dump the image through it It worth the test

Hi! Well, directly to your questions The first step to compile a operating system to any ARM board is to know your board's Device Tree (DTB file) You can extract the DTBs from the stock Android ROM. I do it on Linux using the tool binwalk to lookup the image and find the DTBs There are other methods you can search About the u-boot, you can't use the Android u-boot. Android uses very old kernels, so it's U-Boot release Is made to boot those. You need a modern U-Boot release, so that's your first step To bring Linux to a new board, you'll need to compile U-Boot from source and use the DTB file you just extracted from the stock Android ROM. After that, you can use the Armbian kernel and use any Armbian image or even use your own custom rootfs My boxes are running Arch Linux ARM actually! If you get stuck in one of those steps, just post it here or, if you want to, PM me Good luck!

Not in Chinese logic, I guess haha But talking about fake specs, that's true. They always do it.

Yeah, you can easily find at Shopee or Aliexpress some boxes with Allwinner H3 and 4G of RAM Knowing that this processor can only handle 2 GB max, they're talking about Gigabits. So 4G = 1GB

Yeah, you're right Disconsider the symbology

Hi, Ricardo! I think I understood your question about the calculation The amount shown in the datasheet and your box package is shown in Gigabits (Gb), not Gigabytes (GB) This is a common Chinese strategy to make the boards have more memory than they actually do. The Allwinner H3 processor can handle the maximum of 2 GB of RAM. So no wonder those 4G in our box is in Gigabits I hope I could help a little 😃 By the way, your name sounds Brazilian. If I'm right, you can PM me I. Portuguese if you need extra support. BR aqui 🇧🇷 Good luck!

HI! @SteeMan I work with development for ARM-based products The Armbian community helped me a lot with my beginning in this area. That's why I want to help others as well So, I'm waiting for my order to arrive. It's two boxes with both Allwinner processors (H3 and H6) And yeah! I accept the challenge I'll have more material to share soon thank you!

H6 is newer an has a way better GPU on it, and also a higher clock. Between them, H6 wins And mine is a T95 Mini (TUREWELL). It didn't arrive yet. Soon I'll be able to give support to it

Hi! The GPU support to Rk322x is kind of experimental Check if you're running the latest GPU drivers Also, which kernel are you running? The mainline or legacy?

Hi! It depends of what you want to do with them Rockchip Rk3229 and 3328 Has both good support. 3229 to light desktop or server use, and 3328/3388 for power-demanding tasks I can provide support to the rk3229 because I have one. I have a Allwinner H6 shipping and planning to get a Rockchip 3328. I'll give support for all of them

Yo guys Recently I've aventured myself into building and installing Arch Linux ARM on my RK3229 MXQ 4K box. It works! Running mainline kernel and U-Boot! Does anyone else tried it or want to? I'm thinking about writing a walkthrough or kinda. This is my first topic here in the forum Thanks for reading this! :)