Nuno Cruz

Last time I was not able to find amlogic dtb files in build, something change about the support to amlogic tv boxes?

It doesn't flash, has errors on the beginning. The errors below are the logs on an attempt to flash

hi anyone with a X88 Pro X3 can provide a dd backup ?? not sure what happened but my box became stuck on boot no way to flash it again [10:31:07 117][HUB3-3][Inf]-------------Download DDR.USB----------- [10:31:07 117][HUB3-3][Inf]--3-2-0-0 [10:31:07 117][HUB3-3][Inf]--Control write pll reg1 0xfffa0000:0x000000b1 [10:31:07 619][HUB3-3][Inf]--Control write pll reg1 0xfffa0000:0x00005183 [10:31:08 121][HUB3-3][Inf]--Control write pll reg1 0xfffa0000:0x000000b1 [10:31:08 621][HUB3-3][Inf]--Control write pll reg1 0xfffa0000:0x00005183 [10:31:09 122][HUB3-3][Inf]--Write initial succeed [10:31:09 122][HUB3-3][Inf]--Upload encrypt at 0xff800228 [10:31:09 122][HUB3-3][Inf]--ulValue = 0x20444142 [10:31:09 122][HUB3-3][Inf]--Read encrypt value succeed [10:31:09 122][HUB3-3][Inf]--Download DDR.USB,size: 65536! [10:31:09 124][HUB3-3][Err]--Download file failed, sequence 0 [10:31:09 124][HUB3-3][Err]--usbWriteFile len=4096, ret=-5 error_msg=libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning. [10:31:09 124][HUB3-3][Inf]--Failure : 1, FailureMax : 3 [10:31:19 625][HUB3-3][Err]--Download file failed, sequence 0 [10:31:19 625][HUB3-3][Err]--usbWriteFile len=4096, ret=-116 error_msg=libusb0-dll:err [_usb_reap_async] timeout error [10:31:19 625][HUB3-3][Inf]--Failure : 2, FailureMax : 3 [10:31:30 127][HUB3-3][Err]--Download file failed, sequence 0 [10:31:30 127][HUB3-3][Err]--usbWriteFile len=4096, ret=-116 error_msg=libusb0-dll:err [_usb_reap_async] timeout error [10:31:30 127][HUB3-3][Inf]--Failure : 3, FailureMax : 3 [10:31:30 136][HUB3-3][Err]--[0x10103003]Romcode/Initialize DDR/Download buffer/USB transfer error Using android recovery it just show all options, but show error trying to mount /cache some I/O error before most operation. Anyone can provide a dd image so I can put a full disk image back?? It's a bit strange happened after me try boot with armbian, I never got the box booting to home screen again, get stuck on android animation

I was able to boot with meson-sm1-sei610.dtb and another x96 but the it detected only 2gb, instead of 4gb, so I quit to install on emmc.

@hexdump I think I found the serial, in a bad place to my soldering skills, the maskrom poins I also found them, this is mentioned in a freaklab post. But the are recomending to shot the maskroom? put some solder to keep them connected? I gonna try this on a day with more time and without my 4 years daugther on my foot. Thanks

Hi, I have a bricked (maybe broken) h96max rk3328 h2, it doesn't boot, I tried to see if was possible to install armbian without luck. The box seems to not have uart pins (maybe not so clear position), there's any trick to make armbian but from sd/usb.??? When I plug box to the PC with a usb cable, the box is detected as unrecognized device, so a assumed an hardware issue, but I belive that is bricked .

Perfect, is exatcly what I need I'm still learning, and like many people, it's a mix of research and interaction with experts thanks for you help. I was missing the ddbr existence

I have a 2 devices, one is like new, original android running, I can get the backup/partitions from there, I just wanted to know if there's any easy way to copy the original from that second device running android and place it in the device running armbian. I know that I can get a backup, I dont know who to apply this. Can I just clone the emmc from the android /dev/block/mmcblk2 and write it using the running armbian installation ?

I have access to a device with the original partition, but not sure how and watch I should get a backup and write on the broken device? A script or anything to put all (or needed) partitions back? dd if=/dev/block/mmcblk2 | gzip -c > /path/to/my-disk.image.gz gunzip -c my-disk.image.gz | dd of=/dev/block/mmcblk1

Hi, I installed armbian on a Q96 plus but is working some problems. I tried to install again using diferent dtb but strange was not booting any other dtb, not even with the one that I was to install the first time. So I decide put back the original android firmware with the flash tool, Strangely the toothpick methd to make the box connect to flash is not working, So, now I'm not able to install any other firmware, but is still boot a running armbian installing. There's any way to erase and restore the orginal boot, without use the usb cable? using a SD boot to erase the armbian boot? or some comming to do this from the linux running on the device?

Hi, I was able to install last build on an box named Q96 plus, it has 4gb rk3328, for some reason is crashing when copy a large to the usb drive, anynow knows how to check this?

I think that these tv boxes have many diferences, sometimes one model has 1-2gb ddr3 other has 3gb ddr4, cpus, ethernet, wifi, hdmi etc. can also require a specific dtb configurations and drivers to work properly. I have a s10 tv box with s912 3gb ddr4, and for a weeks I'm trying to run this, I was able to install armbian using the khadas vim2 dtb, but is missing something from the original firmware to have a reasonable linux server. on android with graphic interface GPU working it run at 30-40degrs, with vim2 dtb it goes to 75 with the minimal server running, no GUI. We should have a way to discover and produce a build and/or dtb, and is not only for optimization, is beacuse some people don't find a working dtb to their, in my case I have but is not enough. the optimization on this box was based on android and some information may be extract be do some reverse engeering. I' not asking to do this and distribute the artifact online, is missing some guidance to beginnners to do the bit on their on boxes.

my test was in a fresh installation, no desktop, just ssh, It tried to change to conservative governator, no luck, goes up. root@arm-64:~# cpufreq-info -o minimum CPU frequency - maximum CPU frequency - governor CPU 0 100000 kHz ( 6 %) - 250000 kHz ( 16 %) - conservative CPU 1 100000 kHz ( 6 %) - 250000 kHz ( 16 %) - conservative CPU 2 100000 kHz ( 6 %) - 250000 kHz ( 16 %) - conservative CPU 3 100000 kHz ( 6 %) - 250000 kHz ( 16 %) - conservative CPU 4 100000 kHz ( 10 %) - 250000 kHz ( 25 %) - conservative CPU 5 100000 kHz ( 10 %) - 250000 kHz ( 25 %) - conservative CPU 6 100000 kHz ( 10 %) - 250000 kHz ( 25 %) - conservative CPU 7 100000 kHz ( 10 %) - 250000 kHz ( 25 %) - conservative root@arm-64:~# cat /sys/devices/virtual/thermal/thermal_zone0/temp 75000

Anyone got the CPU ok?

I already tried this, doesn't work, seems to be incompatible with the kernel, and decompile the dtb to information seems very hard to know what can be used. maybe a database with know nodes on original android that can be transformed to compatible armbian kernel ones. I'm a beginner I endup quiting to compile a working dtb for me tv box. I had one booting then I found the CPU on 60dgr, to much pain to me.

did you got this box working?

I would like to get more information about this. My linux skills aren't good as a dotnet dev, I have a spare tv box (s10 s912), and unfortunately I was not able to install just copying one of the provide dtb files, (well it boot with khadas vim2 but PCU temperature is to high for me 60degr). I believe there's many beginners around that could do more steps, like unpack the original firmware, copy images from running android or get device firmware information or files and use this to make needed customization due different hardware, devices etc. The scenario of just the right dtb file would work maybe 90% of times is good enough, but still optimist and the problem is when it doesn't work, we end up without guidance. I'm not sure how much of the queries in theses forum are about people stuck when the dtb, device support is not enough to get armbian running well, but it could mininize a place with more details, alternatives to help when the easy path doesn't work.

I got also 60°C, I would like to know how to change this to get 30-40°C

Cool, I gonna try that approach, use the vim2 dts to compile with bit from the original dts if needed

@hexdump Got it. There's a generic dtb for this s912 3rb ram 1 gb ethernet. It's possible to get from the original dts information missing on this? I'm not expert to edit this dts files, but I would like to compile the ogirinal without any setting that is causing this compatitiblity issue

@balbes150 I tried to install it on a s10 tv box, has a s913, 3gb ram 1gb lan. I was able to get working letting the auto-selection find on dtb (selected vim2). But I wanted to work using the original dtb files, I got the original firmware dtb, but it's does but. this is the dts https://gist.github.com/nmocruz/a0baaf537808335ddc8bab2042131624 there's any reason why it fails? I don't have a way to debug uart because the board has not pins, I has to solder something or what in the middle of mainboard

Don't remember the image version, the dtb was auto selected and based on the board name that I have in the installation it's kharas vim2

root@aml:~# free -m total used free shared buff/cache available Mem: 2841 776 376 37 1688 1862 Swap: 0 0 0

I was trying to install armbian in a S10 tv box, s912 3gb 32gb for some reason the generic gxm_q201_3g.dtb and gxm_q201_3g_1gbit.dtb dont work, I tried to extract the dtb from orginal firmware. the boot.partition as no dtb data, the extraction got a meson.dtb from where I got 3 dtb files. I decompiled the gxm_q201_3g just to share the content, https://gist.github.com/nmocruz/a0baaf537808335ddc8bab2042131624 for some reason this box booted with an old version o the armbian image selection the vim2 , but now it does boot even with the original firmware.

I'm trying to install armbin on an s10 tv box, same as xgody 912. It has 3g ddr4, 1000Mb ethernet. but no sucess to boot. I tried to decompile dtb from a original rom, hope I didnt made any mistake in all process to unpack, split the meson.dtb and then decompile the meson-gxm-q201-3g.dtb this is the decompilation, maybe for some people it can make sense why it does but any other system that uses dtb with same name. https://gist.github.com/nmocruz/a0baaf537808335ddc8bab2042131624 I was able to install once using an old generic armbian for s912 after a few reboot I was able to install, and the /proc/device-tree/model is saying Khadas VIM2, maybe was the first with conditions to boot.