this post was submitted on 15 Sep 2026
3 points (100.0% liked)

Retro Handhelds

582 readers
17 users here now

This community is about retro handhelds. You can post anything that broadly is about retro handhelds, it can be emulation devices or modified hardware, it can be news or your games you are playing.

Rules:

  1. Posts must be on topic

  2. Don't be a dick.

The logo is licensed under CC BY-NC 4.0 with the permission to share without attribution. The banner is from Retrododo.

Sister community: ROM Hacking

founded 2 years ago
MODERATORS
RmDebArc_5@piefed.zip
3
R36S OTG port not working: patching the boot partition may be needed (thebrainbin.org)
submitted 5 days ago by Auster@thebrainbin.org to c/retrohandhelds@sh.itjust.works
1 comments fedilink hide all child comments
 

R36S OTG port not working: patching the boot partition may be needed

#retrohandhelds #R36S

Got an USB to OTG adapter, and though it would work on another device with a working OTG data port, even the USB showing its led blinking, no response would be given on the R36S. Formatting from NTFS (which should already work) to FAT32 didn't work, changing the order of plugging the stick and booting didn't either, testing another stick now in exFAT, which should also work by the R36S' terminal message, and also with a led didn't either.

Digging around, I found this file which then worked: https://github.com/user-attachments/files/23063504/patched-boot-partition.zip

Source, this thread: https://github.com/AeolusUX/ArkOS-R3XS/issues/208#issuecomment-3447733941

I had to extract the downloaded zip's files, remove the SD card from the R36S, back up the files from the SD card's boot partition¹, and copy the extracted files into the SD card's boot partition, merging any folders and replacing any files as asked by the file manager. After connecting the SD card to the R36S, booting it up and connecting the adapter with the USB stick, the stick's led blinked, meaning it was now communicating.

¹Safety measure if restoring anything is needed, specially as the issue affects two different board series apparently, the v21 and v22, and there may be quirks not covered or considered by the patch like distros with specific modifications.

you are viewing a single comment's thread
view the rest of the comments
[–] BoxOfFeet@lemmy.world 1 points 5 days ago

Interesting. I must have a different revision board. If anybody figures out the issue with the R36Plus vibration, please tell me. I added the exact haptic vibration motor as in my R36S, but it just vibrates 100% of the time.