Before starting

• Leave the system card and accessories as received.
• Do not flash the card or replace firmware yet.
• Prepare only the console, suitable power supply or cable for charging checks, and supplied accessories.
• If you find a defect, record and photograph it before changing anything.

Variants matter: R36S revisions and clones differ. dArkOSRE-R36 documents possible GPIO, video-profile, audio-path and control-layout differences. These checks observe your received unit, not establish a universal diagnosis.

1. Inspect the console and identify its parts

Examine the shell, screen, D-pad, buttons, shoulder buttons, both sticks, volume and power controls. Record their actual markings: HOME/F, RESET, TF1-OS, TF2-GAME, OTG or DC may help where present. A photo preserves the layout without opening the console.

Never force a card or connector. The consulted documentation associates TF1 with the system and TF2 with games; exact boot behaviour can vary by card and variant.

2. Check startup and screen

1. Turn on the console with its system card inserted.
2. Wait for the menu to appear.
3. Observe the picture and backlight in the menu, then in content already on the card.
4. Look for persistent lines, flicker, black areas, unstable images or unexpected shutdown.

If the menu does not appear, record the screen, lights and any sound. These clues alone cannot identify a fault or validate the system card. Do not remove the card while powered or change the DTB for this initial check.

3. Check each control

Use a menu or game with known controls to test the D-pad, buttons and shoulders separately. Move the sticks in every direction without force; L3 and R3 refer to stick clicks where available. A control with no function on the current screen is untested: no effect does not prove a fault.

• Record any control that does not respond or needs unusual pressure.
• Check that no direction remains active after release.
• Observe stick recentring and any irregular behaviour.

Keep the supplied system. If a control-test screen is already available, use it to supplement observations; otherwise record controls you cannot verify. R36 Control Centre is specific to some dArkOSRE installations: its presence and features are not guaranteed on supplied firmware.

4. Check sound and headphone output

Change volume and listen to the speaker in the menu or existing content. To check headphones, connect a wired pair without forcing the socket, then record what happens at the headphones and speaker.

Caution: dArkOSRE-R36 documents that separate speaker/headphone handling can vary by board. Record the observed behaviour without generalising to all R36S devices.

5. Check charging

Use only the power supply, cable and charging port identified for your unit. Observe the indicator and connection stability. If you notice unusual heat, smell, swelling or visible damage, stop and contact the seller before charging again.

Record indicator colours and sequence, then compare with your unit’s instructions. dArkOSRE documents board- and software-dependent behaviour: a colour code for another version cannot establish a fault or full charge.

6. Check cards and ports without forcing them

1. Shut down properly through the menu before removing a card.
2. Visually check that the system card is correctly positioned in TF1-OS.
3. Check TF2-GAME if a games card was supplied.
4. Inspect OTG and DC ports for obvious damage or mechanical looseness only.

This initial check does not confirm compatibility with a particular OTG peripheral. Limit it to physical inspection and observable functions without modifying the console.

7. Record the baseline

• Shell and screen: no issue observed / issue / not tested.
• Startup and display: no issue observed / issue / not tested.
• D-pad, buttons, shoulders and sticks: no issue observed / issue / not tested.
• Speaker, volume and any headphones tested: no issue observed / issue / not tested.
• Charging and indicator: no issue observed / issue / not tested.
• TF1-OS, TF2-GAME and visible ports: no issue observed / issue / not tested.

Record each issue with circumstances and photos or videos. For a simple control issue, a second attempt in a known function can help confirm it. Do not reproduce overheating, abnormal smell, swelling or repeated shutdowns. Keep original firmware and boot files while assessing a seller return or warranty claim.

What this check does not prove

• It is not an exhaustive stock-firmware test.
• It does not certify future compatibility with dArkOSRE-R36 or another image.
• It cannot automatically attribute a defect to a DTB, GPIO or another software cause.
• It does not replace seller or manufacturer diagnosis.

After the initial check

Before any later modification, follow the guide to backing up your R36S data. Find other procedures in the R36S tutorials.