Search the Community

Goodmorning, I have a Q plus TV Box with the chip Allwinner H616 v2.0 in configuration RAM: 4GB eMMC: 64GB . This is what is written on the box, but not completely trusted because was said also H6, instead of H616 that's actually is. These are some images of the pcb. I have tried to flash some random armbian, but nothing seems to work. From ttl serial this is a part of log, and I don't know why is found only 1GB of DRAM. https://i.ibb.co/1GSbZdRg/20250813-083105.jpg https://i.ibb.co/rG4zZ0s6/20250813-083122.jpg Which armbian you suggest to try out? If I start with pressing "UBOOT" button nothing appears on Serial console. Thanks in advance to all who could help me [344]DRAM BOOT DRIVE INFO: V0.645 [347]the chip id is 0x5000 [350]chip id check OK [354]DRAM_VCC set to 1500 mv [357]DRAM CLK =648 MHZ [359]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [366]Actual DRAM SIZE =1024 M [369]DRAM SIZE =1024 MBytes, para1 = 30eb, para2 = 4000000, dram_tpr13 = 6041 [378]DRAM simple test OK. [380]rtc standby flag is 0x0, super standby flag is 0x0 [386]boot0 Nand0 clk: 10MHz,PERI=600,N=4,M=15,T=10 [391]boot0 Nand Ecc clk: 20MHz,PERI=600,N=2,M=15,T=20 [396]NB0 : nand phy init ok [399]block from 4 to 11 [658]Check is correct. [660]OLD version: 0.0 [663]NEW version: 0.0 [738]load rotpk hash [801]load monitor-key hash [803]load monitor hash [1007]load boot-key hash [1009]load boot hash [1075]load vbmeta-key hash [1077]load vbmeta hash [1144]load recovery-key hash [1147]load recovery hash [1151]monitor entry=0x48000000 [1153]uboot entry=0x4a000000 [1156]optee entry=0x48600000 [1161]run out of boot0 NOTICE: BL3-1: v1.0(debug):be96482 NOTICE: BL3-1: Built : 18:32:32, 2021-04-21 NOTICE: BL3-1 commit: 8 NOTICE: cpuidle init version V1.0 NOTICE: secure os exist MESSAGE: [0x0] TEE-CORE: OP-TEE version: 5c40397e #1 Tue Feb 2 07:45:37 UTC 2021 arm NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 U-Boot 2018.05 (Oct 25 2021 - 08:42:07 +0800) Allwinner Technology [01.251]CPU: Allwinner Family [01.253]Model: sun50iw9 I2C: ready [01.258]DRAM: 1 GiB [01.261]Relocation Offset is: 35ec5000 [01.296]secure enable bit: 1 [01.299]pmu_axp152_probe pmic_bus_read fail [01.303]PMU: AXP1530 [01.309]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=400Mhz

hello everyone! I bought this tv box..https://www.aliexpress.com/item/1005009346784515.html?spm=a2g0o.order_list.order_list_main.11.79e81802pgNRxu but after starting it was not possible to log in to googleplay even though I had a connection via wifi or ethernet. the preinstalled version for applications was Aptoide TV..through it I wanted to update all applications (youtube, netflix, etc.) I managed to do that but no application could be started. the original file manager did not show the internal memory or USB disk or SD card until I managed to download ES file manager through aptoide and it showed my flash disk I installed HW info device and there I found out that it was an RK3528 chip. so I wanted to flash the firmware and I used a rom image for H96max with the same parameters. the firmware upgrade went OK but the device is dead. I can't find the correct firmware. I'm attaching a photo--- maybe someone will recognize the board and identify which rom-img should be correct. the seller can't help me in any way.

Hello, I have x96q2 H313 2/16 board v4.0 ram k4b2g0446c hyh9 and apx305. I tried all img, and no one worked on my TV box. Mb u can help me, how I can build img for my board? I need sd card version armbian or arch Linux (not emmc installation)

Hi I think that a boot on this TV box it should be not so hard, I never tested an Allwiner. Please, start reading some advices from this post from 2023: once that h313, probably follows at the same procedure of the H61X ... I hope to help you ccs

(sorry for bad english) i'm looking to boot in an armbian bookworm by sicxnull on my mxq pro 4k 5g, i checked the aida64, it showed the allwinner h313, i tried the toothpick method to the recovery menu (which have a boot option?) i'm novice to android 😕 by the way here are the images of the tv box pcb:

I have an old and weak mxq pro 4k TV box (fake amlogic s905w), rk3228a checked, sv6051p wifi. I recorded the desired version on the micro sd via the multiboot.img adapter and it worked but did not respond to the remote control, I checked the remote for robotics, recorded libre elec and booted from it without multiboot and it even worked on wi-fi and the remote reacted, I replaced the dtb file and booted from the multiube but it no longer worked I thought that dtb was capricious and decided to replace only part of the it_receiver code in dts format and converted it and recorded it via dd on Linux, but this time the eumultool worked but the remote control did not respond again. I do not know why it stopped turning on on android 7.1.2, but I know for sure that after downloading minecraft or similar games, it will boot up and you can go to recovery, I tried two firmware for TV box in the format.zip but there was a message map location failed like I recorded the desired version on the micro sd via the multiboot.img adapter and it worked but did not respond to the remote control, I checked the remote for robotics, recorded libre elec and booted from it without multiboot and it even worked on wi-fi and the remote reacted, I replaced the dtb file and booted from the multiube but it no longer worked I thought that dtb was capricious and decided to replace only part of the it_receiver code in dts format and converted it and recorded it via dd on Linux, but this time the eumultool worked but the remote control did not respond again. I do not know why it stopped turning on on android 7.1.2, but I know for sure that after downloading minecraft or similar games, it will boot up and you can go to recovery, I tried two firmware for TV box in the format.zip but there was a message map location failed like that,this is off topic, but please help me fix this, I definitely need linux to make a server for the telegram bot.

I have a Odroid C2 that was being used as a TV box with Coreelec, and has now been retired due to upgrade. I want to repurpose the C2 for a completely different role, so I am trying to install Armbian in it. I downloaded the Armbian image from here and followed the official install instructions, but the C2 refuses to boot. The red light turns on when powered but nothing more happens, no other lights, no screen, nothing. Coreelec was booting with no issue, so it must be something I'm setting wrong. Just in case I tried a different SD card and two different images, Bookworm minimal (the one I'm interested in) and Ubuntu Noble XFCE (just to test). Same result. Once I boot I let the C2 on for some minuts, as per the inatructions, no change at all. I am also using usbimager, again as per instructions. Anyone has any idea what I could try to see if I can boot Armbian in my C2?

Hi. Looking for help. I have uploaded Armbian v6.12 Desktop Ubuntu to a card and run on my device. You can see in the screenshot (video of the boot here: https://drive.google.com/file/d/1_1dm1rP33tbYISPUsta7nZV1eKPy3Plq/view?usp=drive_link) that some rubbish is displayed. I would also add that the device is sending a signal that is only displayed by the TV. No other monitor in the house is able to display anything that is sent from the device. This is even stranger, as when I upload the old ubuntu 18.04 to the same card, the device connected under any display displays my desktop. Any suggestions or suggestions? Maybe an older version? I want to make myself a RetroPi from the device, but that requires something newer than the old ubuntu.

My best guess is that you have an Android install on your eMMC (Android uses those two boot partitions as part of how it installs new versions, while still keeping the old). How Android formats a disk is generally somewhat custom and often the partitions aren't readable by mainline uboot / mainline linux. (It should be a GPT partition table, but for some reason I haven't dug into, isn't recognized by mainline). I deal with these things on Android TV Boxes all the time. You should be able to just format the entire emmc for your use as what is on their isn't useful to you. However, I'm not familiar with this specific board and what the specifics of its booting process is. So there is a chance that something on the eMMC is required for a successful boot.

Hi everyone, Please, someone knows to inform if this thread is open yet? I am resuming to Armbian after almost 4 years. I have a TV BOX model T95Z Plus (RUPA Diamond S912) running for a long time ... but with a kernel 5.9. Yesterday, I follow the steps described in : I upgraded all the packages to Brookworm, but no the kernel. # apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. AND # cat /etc/os-release PRETTY_NAME="Armbian 25.5.2 bookworm" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian 25.5.2 bookworm" BUT the problem is here: echo "$(grep PRETTY_NAME /etc/os-release | cut -d= -f2-) | Kernel: $(uname -r)" "Armbian 25.5.2 bookworm" "Armbian 25.5.2 bookworm" | Kernel: 5.9.0-arm-64 So, I am afraid about how to choose the right kernel once that they are not supported anymore by @balbes150 To get a kernel from here https://www.armbian.com/amlogic-s9xx-tv-box/ (Debian with XFCE) should be a safe step? How can I test it safely? With # aptitude search "linux-image" we have a lot of kernels for arm-64 .... but which them will work? In true, I am not sure by the right place to put my doubts ... Someone could give me some guidance? Maybe to open a new thread of this help? Thanks in advance. Claudio

Hello, I have this TV box and it's difficult to find the firmware, only the logo appears on the screen and it freezes, I've already reset it and nothing, if anyone can help me, thank you very much. Here are photos of the board.

All you need is in this thread CSC Armbian for RK3318/RK3328 TV box boards And the special uboot is there. You have a chance to brick you device so if you don't understand something don't go ahead.

R-TV Box S10 I know this is an old topic but I am trying to get this S10 box going for a old colleague which updated and now no longer starts but stays in the animation and not booting into android. Cannot find any firmware download. Thanks in advance

I've successfully setup Armbian with home assistant preinstalled The image build command is ./compile.sh BOARD="rk3318-box" BRANCH=edge RELEASE=bookworm ENABLE_EXTENSIONS="ha" KERNEL_CONFIGURE="no" BUILD_MINIMAL="yes" I build on edge branch because only kernel after 6.15 can boot on rk3318 tv box, at this time it's 6.16.0rc3 Don't forget to add docker-ce and home assistant extension files to userpatches/extensions folder. After installation you need to cchange internet adapter manager from "Networking" to "Internet Manager" nmcli device set eth0 managed yes This is my prebuild version, use it at your own risk cause everyone on the internet might be the bad guy that want to hack your machine👻 Armbian-unofficial_25.08.0-trunk_Rk3318-box_bookworm_edge_6.16.0-rc3_minimal.img sha file attached Armbian-unofficial_25.08.0-trunk_Rk3318-box_bookworm_edge_6.16.0-rc3-homeassistant_minimal.img.txt Armbian-unofficial_25.08.0-trunk_Rk3318-box_bookworm_edge_6.16.0-rc3-homeassistant_minimal.img.sha

CSC Armbian for RK3318/RK3328 TV box boards is a community-supported Linux distribution for Rockchip-based TV boxes. Install by downloading the image (e.g., Armbian_23.02.2_Rk3318-box_jammy), burning it to a microSD card using balenaEtcher, and booting the device. Configure via HDMI and keyboard; WiFi may need manual fixes.

Hi, can anyone help me with this TV box? I need to unlock it, but I don't know where to short the cable because the PC won't connect. Rk3228a, zq01-v1.51

Your tv stick probably has secure boot enabled. You can compile a secure boot image using these steps.

wow, the help from chatgpt is in fact quite good ... I now unmuted that SPDIF in alsamixer and tried also to change the pavucontrol configuration profile for something with digital hdmi (but this is NOT necessary ... its all really in the alsamixer unmuting that primary SPDIF - which is reverted to MM with some changes to pavucontrol profile !!) - pavucontroll still shows "headphones" but the audio goes to the hdmi out playing video ... that manual adding of sink to pa probably helped - internal PCI audio shows as "built in audio analog stereo" and the hdmi tv output shows in pa as "builtin audio" ... uff, that audio channels naming ... excuse me, I am linux newbie in this area completelly, may be it was obvious for some, ... quite mess for me but okay, loading module, unmuting spdif ... will see Petr

hi, I have the hdmi issue in uefi-x86 on intel nuc10 minipc - now testing it from fast sandisk microsd in usb3 reader, thats quite fast (after few issues with overheating and slow verbatim and kingston flash keys) this is armbianmonitor output https://paste.armbian.com/jidekuvaza here I tried to ask machine for possible issues and from some detection, it says that my TV is not reporting in EDID any audio?? in windows it works, so may be its something missing? first try to add some forcing to grub didnt helped ... https://chatgpt.com/share/68836e5f-9e4c-8000-8874-46ea35a07331 **** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC256 Analog [ALC256 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [Beyond TV] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 falken@uefi-x86:~$ xrandr --verbose | grep -A20 HDMI subconnector: HDMI supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native link-status: Good supported: Good, Bad CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 CONNECTOR_ID: 99 supported: 99 non-desktop: 0 range: (0, 1) 1920x1200 (0x45) 154.000MHz +HSync -VSync *current +preferred h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 74.04KHz v: height 1200 start 1203 end 1209 total 1235 clock 59.95Hz 1920x1080 (0x46) 148.500MHz -HSync -VSync h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x47) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1680x1050 (0x48) 119.000MHz +HSync -VSync h: width 1680 start 1728 end 1760 total 1840 skew 0 clock 64.67KHz v: height 1050 start 1053 end 1059 total 1080 clock 59.88Hz -- Clones: HDMI-1 CRTC: 1 CRTCs: 0 1 2 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: EDID: 00ffffffffffff006318512800000100 141d0103807944780a0dc9a057479827 12484c2108008140a940818081c0a9c0 01010101010108e80030f2705a80b058 8a00b9a84200001e023a801871382d40 582c4500b9a84200001e000000fc0042 65796f6e642054560a202020000000fd 00324b1e503c000a202020202020017d 020367f15261605f6665909f05140413 1221225e625d20320907071517505517 016704033d07c05f7e0183010000e200 cb6e030c002000b84421008001020304 68d85dc40178880702e305e301e20f1b -- subconnector: HDMI supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native link-status: Good supported: Good, Bad CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 CONNECTOR_ID: 112 supported: 112 non-desktop: 0 range: (0, 1) 3840x2160 (0x58) 594.000MHz +HSync +VSync +preferred h: width 3840 start 4016 end 4104 total 4400 skew 0 clock 135.00KHz v: height 2160 start 2168 end 2178 total 2250 clock 60.00Hz 4096x2160 (0x59) 594.000MHz +HSync +VSync h: width 4096 start 4184 end 4272 total 4400 skew 0 clock 135.00KHz v: height 2160 start 2168 end 2178 total 2250 clock 60.00Hz 4096x2160 (0x5a) 594.000MHz +HSync +VSync h: width 4096 start 5064 end 5152 total 5280 skew 0 clock 112.50KHz v: height 2160 start 2168 end 2178 total 2250 clock 50.00Hz 4096x2160 (0x5b) 593.407MHz +HSync +VSync h: width 4096 start 4184 end 4272 total 4400 skew 0 clock 134.87KHz v: height 2160 start 2168 end 2178 total 2250 clock 59.94Hz -- HDMI-1 disconnected (normal left inverted right x axis y axis) Identifier: 0x43 Timestamp: 5494311 Subpixel: unknown Clones: DP-2 CRTCs: 0 1 2 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: HDCP Content Type: HDCP Type0 supported: HDCP Type0, HDCP Type1 Content Protection: Undesired supported: Undesired, Desired, Enabled max bpc: 12 range: (8, 12) content type: No Data supported: No Data, Graphics, Photo, Cinema, Game Colorspace: Default supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater aspect ratio: Automatic

I have a couple of cheap Allwinner h313 tv sticks "G96" that I would like to try to port to Armbian. Not exactly sure where to start, but I managed to soft emmc brick one doing so (boots off sd card fine). No compatible firmware is available anywhere, so I rooted it and dumped the emmc firmware, available here: https://archive.org/details/G96_Firmware_Dump . This firmware boots just fine off a sd card. The wifi chip is BCM43340, which has been patched into Armbian before. There are a few more images at the link, let me know what I should do/dump to help.

@eselarm I agree with you, it's a fabulous device. And like you, hours after the post, I realized that I only need a VM host. I was thinking about the M6, but why get stuck with Windows ARM when Debian and Android also work on Intel? These bonsai devices are really appealing, but for now I've returned it to Amazon. I bought it as a gateway-media server, to have priority on the LAN and lighten Android TV, but I realized that with MediaTek there is a huge gap in network management, so I put it on the LAN, and Debian in VNC was running strong, I wanted to speed it up with Armbian. Apart from the fact that they call their community “third parties,” it still seems like a good idea to me. I could install the generic Arm64-xfce with mesa-vpu... engineering-wise, it's incredible in 6 square centimeters, but an i7 tower is more convenient for VMs.

I Have an A96X with rockchip RK3228 and i tried booting armbian on it, but I got no display on HDMI. I connected a serial adapter to it and here is the information it displays when trying to boot: ▒▒▒▒DDR Version V1.05 20160805_dbg In 300MHz DDR3 Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB mach:2 OUT Boot1 Release Time: 2016-03-15, version: 2.31 ChipType = c 275 No.1 FLASH ID:2c 64 44 4b a9 0 ECC:60 SdmmcInit=0 0 BootCapSize=0 UserCapSize=76f5000 FwPartOffset=2000 , 0 StorageInit ok = 1520008 SecureMode : SBOOT_MODE_NS hdr 0x0:ff a1 0 0 1b 0 0 0 f0 f2 2e 68 f0 f2 2e 68 hdr 0x0:a4 81 0 0 4e 23 0 0 f0 f2 2e 68 f0 f2 2e 68 hdr 0x0:ff a1 0 0 3 0 0 0 f4 f2 2e 68 f4 f2 2e 68 hdr 0x0:a4 81 0 0 44 0 0 0 f4 f2 2e 68 f4 f2 2e 68 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SecureMode : SBOOT_MODE_NS Loder code check ok! theLoader 0x60000000, loadaddr: 0x2000 Loder code check ok! theLoader 0x68400000, loadaddr: 0x4000 INF TEE-CORE:init_primary_helper:319: Initializing (1.0.1-63-g23e91df-dev #16 Tu e Mar 7 10:07:15 UTC 2017 arm) INF TEE-CORE:init_primary_helper:320: Release version: 1.8 INF TEE-CORE:init_teecore:79: teecore inits done U-Boot 2017.02-RK322X-06-02276-ga7c7ca8-dirty (May 19 2017 - 11:16:15) CPU: rk322x cpu version = 3 CPU's clock information: arm pll = 600000000HZ periph pll = 600000000HZ ddr pll = 600000000HZ codec pll = 500000000HZ Board: Rockchip platform Board Uboot as second level loader DRAM: Found dram banks: 1 Adding bank:0000000060000000(0000000040000000) Reserve memory for trust os. dram reserve bank: base = 0x68400000, size = 0x00100000 128 MiB GIC CPU mask = 0x00000001 rk dma pl330 version: 1.4 remotectl v0.1 pwm freq=0x11e1a3 pwm_freq_nstime=0x355 SdmmcInit = 0 0 SDCard Update. storage init OK! Using default environment Writing env to storage... done GetParam W: Invalid Parameter's tag (0x00000000)! Invalid parameter No pmic detect. SecureBootEn = 0, SecureBootLock = 0 #Boot ver: 0000-00-00#0.00 empty serial no. normal boot. no fuel gauge found no fuel gauge found read logo on state from dts [0] no fuel gauge found 'recovery' does not seem to be a partition nor an address Unable to boot:recovery try to start backup 'backup' does not seem to be a partition nor an address Unable to boot:backup try to start rockusb Can anybody point me to the right direction? I'd really like to turn this piece of junk into something useful 😄 Any help will be greatly appreciated! Thank you.

Hello, I found this guide: https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md I followed the steps and built an Armbian image with current 6.12 kernel and now TV OUT (CVBS, Composite Video), after soldering a cable to the video pin on the board, is working on my Orange Pi One with an Allwinner H3 CPU (the patches might work for other H3/H2+ boards). I would like to get that functionality incorporated into Armbian.

Does anyone know of a compatible image for the MXQ PRO 4K 5G TV Box with Allwinner H3, model Q44_V4.1_20210120? I've searched a lot and only found images compatible up to version V4.0. Since mine is V4.1, I haven't been able to get a successful boot from the SD card. If anyone has any tips, a working image, or experience with this specific model, I’d really appreciate the help!

Hi everyone, I’m experiencing a recurring and very specific issue with my TX2 TV Box, with the following specifications: SoC: Rockchip RK3229 RAM: 2GB DDR3 Storage: NAND flash (not eMMC!) Board: Generic TX2 board 🛑 Main Issue The system shuts down abruptly at exactly 29 minutes and 47 seconds of uptime (i monitoring via htop). It always shuts down at this time. It’s not a clean shutdown or reboot — it behaves as if the power was cut off. No meaningful logs appear in journalctl or dmesg, and the shutdown is instantaneous and silent. 🧪 What I’ve Tried: Disabled idle and sleep functions: Masked systemd-logind Set IdleActionSec=0 and HandlePowerKey=ignore Tried different kernel versions: Legacy: Armbian 22.02.0-trunk Focal legacy 4.4.194 Mainline: Armbian Jammy kernel 5.15 Attempted to disable the watchdog: Boot parameter nowatchdog Kernel parameter rcu_cpu_stall_timeout=0 Created a systemd service to periodically write to /dev/watchdog Tried to remove dw_wdt module (modprobe -r), but it either auto-loads or refuses to unload (watchdog did not stop) Tried building a custom kernel with CONFIG_DW_WATCHDOG=n, but the process failed due to gcc-arm-linux-gnueabi toolchain issues. Used config-rk322x to properly set RAM, NAND, and Wi-Fi chip before first boot + update/upgrade. Tried adding sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target ⚠️ Additional Critical Note: The system does not work at all when flashed to eMMC/flash — only boots properly from NAND or SD card. Any image written to internal flash does not boot. Therefore, booting from NAND is required, which may be related to the watchdog being active by default on NAND-based boards. ❓ My Question: Has anyone with a TX2 or RK3229-based NAND board experienced this same issue? Is this a known watchdog timer issue on NAND models? Is there any stable image or device tree overlay known to work for this configuration? Any tips to fully disable the watchdog either via software or kernel patch? Thanks in advance for any help or suggestions!