fabiobassa

@Khalid Pro
 
hello man, are you aware of some terms such as " please", "thank you" and so going on?

Any way we don t talk of roms here,  google is the best friend in these cases

@primoitt perhaps you should consult first page on "Multimedia" paragraph.
The way to go on mainline kernel is, as suggested by @fabiobassa, use ffmpeg, but AFAIK you still have to patch it manually with some libreelec patches to let it work.

Thank You , ok switching things by adding a part of it
 
 

@primoitt: @ilmich solved it for me by compiling a libreleec 11 build with mpv binary included- Everything works, h264/hevc/mpeg2 ..... brilliant.

@ochentay4
 
What do you mean " inspected by my camera"
 
Have read, again, the whole post ( no, i Guess)
 
Because already discussed that even if marked 3229 sometimes are fake and they really are amlogic or allwinner.
Heve you skills to get a USB TTL converter and give us a serial log ?
 
 
 
 

NAND are not exactly easy beasts, if the multitool does not detect it anymore it is because the kernel rockchip driver does not detect it.
It is difficult to say what happened exactly, we have spent hours and hours to figure out what was the behaviour of the nand driver and all the other proprietary software pieces of the puzzle.
Also they are quite "fragile" pieces of hardware, and abusing of them can quickly destroy the cells capacity to work.
 
In the past, people has restored the NAND functionality restoring original android images with AndroidTool for windows, or uploading particular bootloaders; you should look for such resources in this thread (or with google) because some procedures were described to do so I forgot to bookmark.
 
For what me and @fabiobassa have seen, what seems to be an apparently random behaviour of the NANDs, in reality it is deterministic and can be understood. What we've found to be totally confusing was the fact that keeping anything attached to the board (HDMI, ethernet, keyboard, serial adapter, ... whatever!) can prevent the NAND from being detected after a reboot.
 
Also remember to use the armbian image with the legacy kernel, those with mainline kernel miss the proprietary driver. Also you could post a dmesg log after booting such legacy kernel image to see what the driver has to say about NAND.
 

Hello friends,
 
No request this time, just another success story, at least partial !
I managed to run multitool on a mxq pro tv box.
Now I will try to edit this image to make a linux image working from
the sd card, my parents still like too much their laggy android to delete it, hehe.
 
Installing linux on mini pcs is so useful, I have done it on many different ones.. Im curious on what people here are doing with their desktops and servers !
ok, all the best, greetings from Brazil, and thanks everyone for the work and research
 
fangis

@hexdump 
In my case study ( and I own many different boards)I always found a uart somewhere, maybe little copper pads but always I found a uart for debugging
if you post a photo of your board up/down maybe we can identify them

I can confirm that the buildings from @jock are working fine and never happened that boots and hangs: if boot it works, otherwise no boot occurs, because of 1) wrong ddr settings 2) wrong trust OS but this is easily debugged by uart

we can summarise 3 BIG categories of boards:
3228 ddr 2 ( NO dinamic frequency scaling of ddr speed DMC)
3228 ddr 3 ( DMC is working fine)
3229 ( well exactly even here ddr2 and ddr3 but.... let's assume newer 3229 have only ddr3)

3229images will not boot on 3228 because different trst OS (thanks @knaerzche for all those USEFULL infos)
 
and yes if on the original emmc/nand is present the loader and some other little stuffs then the board looks for uboot on sd , without touching the internal process and the boot occurs from external SD

Just to be complete, give a try to  this rootfs :

https://drive.google.com/open?id=1jmtwGs88iXfCs7UtaEv1d5h7C9-9KGFg
 
EDIT : if we find the UART put the command line to both ttyS2

https://github.com/armbian/community/commit/2dc0a364c8a31e11d708885e0622f1be30402de1

@DavidJS
you SHOULD at least know that FAT has a limitation to maximum 4gb for a single file so the problem isn't the partition but the file itself
Anyway when you insert SD for 1st time without any image inside the fat partition is resized to maximum. Then remove the SD and out the image on it
you can try to compress .GZ the image and see if it Is under 4gb and fit
 
 
 

My board decided to crap its pants after flashing armbian for the 10th time but I managed to revive it.
 
Not sure if this is useful but I found the clock pin that I can connect GND to make the box enter MASKROM mode my board has an emcp chip on it
My model is MXQPRO_V71
you can solder a wire to this point and short it to ground then plug in your sdcard with multitool
short the clock pin to the ground and plug the power, wait till the led indicator turns red then remove the jumpers. if the led starts flashing then you are all set! you can try flashing armbian or your stock firmware to your box

Wow !!! it's magic !
I have WiFi

Hmmm, I did not understand if the board crashes or OMV becomes unresponsive (and which part, since OMV leverages nginx and php for the web admin and samba/nfs/ftp for the file serving services).
 
You say that you can "ssh the box", but you mean that you can login via ssh and the board still operates normally or the ssh service is apparently responding but you can't login?
I have a board with debian buster that is running OMV perfectly fine for several months right now, but also I'm experimenting with an eMCP board that has Home Assistant and running as wireless AP without any issues. Both of the board are running headless with no problems or crashes. The eMCP board is a MXQPRO_V73, should not be far different than your MXQ_V71 (I may guess it is a MXQPRO_V71? You could post some high resolution photos that may be helpful identifying the board and its components)

Hi @jock and @fabiobassa, it's great that you guys support the TV boxes that Armbian won't, amazing!
I have a HDMI stick with a RK3229 SOC, and this pathetic stick/board is a clone of a product with the brand "Any-cast", which at the same time is a clone of the Google Chromecast.
 
I thought I had bricked it, but I wonder if there's anything to do with it? 
I didn't expect to run Armbian on it, but if I can ssh into it and run something like lighttpd, it will be already great
 
I think the two soldered spot near the USB port is the UART serial, but I'm not sure
I also managed to do
rkdeveloptool db rk322x_loader_vxxx.bin , seems that the image is flashed successfully, but it still show "Maskrom" mode after I do
rkdeveloptool ld But I'm afraid to say that I'm not too clear about what I am doing 😅
(Oh there is an external WiFi chip that is soldered to a USB cable, you can look at the last three photos)
 

@marras

if you need just for 3d printer no desktop at all and it will be fast as lightnening
 

A terrible suspicion came to me right as I was writing the previous post, so I did a quick cat /proc/cpuinfo... and it has an H3 CPU.

Everything that was written on the box and on the eBay auction was completely off.
 
It looks like this one: 
 
 
Apologies for wasting your time, I'll go and try out another image for the correct CPU!

Sorry for the late reply, it looks like I'm allowed only one post per day due to bot/spam prevention measures.

The board is marked as MXQ-HX-V2.0 and has a sv6256p wifi chip which means no wi-fi for me (not that I really needed it, but still...)
 
Here's a picture:
 

 
I can clearly see the serial port pads marked between the USB and SPDIF connector so I should be fine if anything goes pear shaped.

Still, I'd feel more comfortable knowing if there's been any test done on this board.
I don't need video output or anything else as this is going to be the DNS server of my local network (Pi-Hole, DNSCrypt and all that jazz), but I'd really appreciate not having to sacrifice an SD to hold the rootfs and, more importantly, the ethernet MUST work.

@jock at the end I was impatient and I cleared the emmc and tried to restore the backup... Everything went well, Android has been restored successfully! I think I was lucky because the backup is 2.5gb, under the fat32 limit, but after decompression it is as big as the all emmc (16gb). The problem is that I cannot extract anything from it, since the decompressed file is not an archive according 7zip, it's just a file without any extension. After cleared the emmc again, Linux from sd booted successfully and also after flashing in the emmc. wifi, hdmi works (only audio doesn't but I don't need that). I'm a bit disappointed by the performance, xfce doesn't run that fast, but it's ok since I need just to install klipper for my 3d printer and I hope it's enough for this purpose. Thank you for all the support, you have been precious!
 
 
 
 

@donluca

yes this board is NOW supported and you will have great satisfaction in using it for your purposes.

And yes ethernet will work out of the box ( and if I am not wrong, wifi too but about this let's wait @jock suggestion )

@donluca

yes this board is NOW supported and you will have great satisfaction in using it for your purposes.

And yes ethernet will work out of the box ( and if I am not wrong, wifi too but about this let's wait @jock suggestion )

@Henn
This forum Is about armbian and Linux, not android 
Go find Android forum please
 
 
 
 

Fixed multicast too: https://github.com/HandyMenny/ssv6xxx/commit/5ff256e8c84665253379e43e2608f7debef2d1b4

@handymenny Cool, thanks! Maybe the broadcast decrypt can be fixed adding a proper -DUSE_MAC80211_DECRYPT_BROADCAST directive in the kernel module makefile nearby the other conditionals that relate to hardware/software encryption and decryption, without hardcoding the conditional.
 
Anyway thanks, do what you prefer and if you open a pull request I will accept and rebuild the armbian patches to fix the problem

@jock Done. I wonder if it's a hw/firmware issue or it's the driver itself the cause. But so many flags linked to SW decryption, makes me think that even the authors didn't trust the HW capabilities...

board version? sometimes those 4 pads do not work for me, what i sometimes do when i'm feeling lazy is i try connecting the ground on the board first then i try connecting the rx pin of usb serial to different pads of the board while booting to find its tx pin. you only need two pins to capture serial debug logs. i found mine at the back of the board. i think i posted the pics in this post at page 26. you get very low chances of bricking your board if you do it this way. other method i use is a low cost stm32 o-scope and a multitester which a is way safer method in my opinion.