R36H Black Screen: Check the Cause Before a DTB Swap
A black, garbled or color-shifted screen after changing firmware is a symptom, not proof of a panel mismatch. The image, card, board revision, power state or display configuration may be involved. This guide helps you decide what to verify before touching another file.
⚠️ Preserve the known-working setup
Do not overwrite your only original card or copy a DTB from a different model just because its screen symptom looks similar. If the stock card is still working, keep it unchanged. If it no longer works, preserve it for diagnosis and obtain the seller's or project's recovery instructions before further writes.
First, compare the symptom
| What you observe | What it tells you | Next check |
|---|---|---|
| Original card displays normally; new image is black | The new image or its setup may not match this unit. It does not identify the panel by itself. | Check the exact board ID, release support list and image hash. |
| Original card is also black | Do not assume a custom-firmware DTB is the cause. | Preserve the card and record power/LED behavior; consult the seller or a qualified repair source. |
| Image boots but colors or orientation are wrong | Display configuration is one possibility, but not a confirmed diagnosis. | Use only the same firmware project's instructions for this exact board and release. |
Record the details before changing anything
- The exact motherboard marking and revision printed on your unit, if accessible without damaging it; do not infer the board from the seller's “R36H” label alone.
- The firmware project's name, release version, image filename and published checksum, plus whether your downloaded file matches that checksum.
- When the image disappears: before a logo, after a logo, only in an emulator, or continuously. Note any sound or LED behavior without treating it as a diagnosis.
- Whether the original card still displays normally. Back up readable saves and settings before experimenting with another card.
Why a generic DTB swap is not a safe shortcut
A device-tree file can describe more than a screen. The dArkOSRE maintainer's DTB notes discuss board-specific elements affecting other hardware. Its installation guide pairs DTB paths with motherboard IDs inside that particular project; those paths are not universal R36H instructions.
For example, the project's beta notes list both HL-R36H-V20 2024-05-18 and HL-R36H-V21 2024-11-18. At this source check, the published installation path table explicitly names V20 but not V21. Do not guess that V20's DTB or another R36S profile is suitable for a V21 board. Check the current release and ask the project maintainer if the exact board path is unclear.
A reversible decision sequence
- Stop using the unverified image. Preserve the original card and note the exact board and symptom.
- Check the image integrity and the firmware project's current device list and release notes. If your exact board is absent, stop rather than trying near-matches.
- Only if the project explicitly supports your board and documents a panel or DTB procedure for that release, follow that project's own backup and recovery steps. Do not mix files from unrelated builds.
- If the original card also fails or no documented recovery path exists, seek seller or maintainer support instead of assuming a software-only fix.
For general preparation before any firmware change, see our R36H firmware compatibility checklist. It does not certify a particular image or panel file for your unit.