If your R36S will not turn on, shows a black screen or keeps restarting, first separate a power problem from a boot or game-launch problem. The same symptom can have several causes; a black screen alone does not identify a hardware revision or prove that a unit is a clone.
Protect your original setup: keep the supplied cards, cancel format prompts and avoid trying unrelated firmware images. Start with the checks that do not erase or replace anything.
Choose the symptom you actually see
| Symptom | First checks |
|---|---|
| No light and no screen | Power source, charging cable and the charging instructions supplied with the unit. |
| Light on, but no usable picture | Original system card seating; whether the problem began after a software or card change. |
| Logo appears, then restart | Charge state, original card seating and the point at which the restart occurs. |
| Menu works, but one game fails | File format, BIOS or emulator compatibility; treat this as a game-launch issue first. |
1. Check power and charging
Use the charging input, cable and supply specified in the supplied instructions. Give a depleted battery time to charge before trying to start the handheld again. Check the cable connection and, if available, try a known-working compatible cable and supply one at a time.
If you notice unusual heat, swelling, a burning smell or visible damage, stop charging and contact support. Do not open or press on a damaged battery.
2. Check the original cards
Turn the console off before removing a card. Note the original slot for each card, inspect for obvious damage and reseat it gently. A card that holds the system software needs to remain in the correct system slot. Return both cards to their original positions before testing a two-card setup.
If a computer offers to format a card or partition, cancel. Formatting can erase the system. Preserve the original cards while support helps identify the problem.
3. Did the problem begin after a change?
If the console previously worked, note exactly what changed: a new card, deleted files, a firmware image, screen configuration or emulator setting. Where possible, test the untouched original setup rather than making several further changes at once.
A copy of visible folders is not the same as an image of a bootable system card. If you already have a verified recovery backup, use the procedure for your exact hardware. Otherwise, ask support before overwriting the card.
4. Black screen after a firmware change
Firmware and display configuration can depend on the screen or board revision. The R36S community project documents screen-specific configuration, so a black screen after an update is a reason to check compatibility—not a reason to keep installing random images. This guide does not certify any particular replacement firmware for your unit.
5. If the menu works but a game does not
Test whether the problem affects one title or the whole console. A single failing title can point to a format, related-file, BIOS or emulator mismatch. Follow the file-transfer checks and the R36S compatibility guide before changing the system software.
When to contact support
Email support@retroorbitgames.com with your order number, when the problem started, which lights appear, and a short video of the boot sequence. Tell us whether you changed a card or software. Support and any return request are reviewed under our published return policy.
Back to the R36S product page or compare handheld models.
Software reference
The R36S community firmware project explains hardware and screen configuration. It is a software reference, not a claim that this firmware is supplied with, or suitable for, every R36S variant.