r/hardwarehacking • • 19h ago

Need help booting into recovery mode on a automotive board without recovery button

Post image
33 Upvotes

This is a headunit board of mercedes i can’t find any resources on how to boot into recovery mode RCM.

These are better higher quality picture of the front and back

https://imgur.com/gallery/hu6-board-x0pHj9l


r/hardwarehacking • • 4h ago

Bricked a Smartlink SL6801 ("Jointbees" / Amazon "Cason" MP3) after an interrupted flash - need the mask-ROM boot strap to reach 301A:2800

1 Upvotes

Generic Amazon "Cason" MP3 player (Smartlink SL6801, 2 MB flash inside the SoC package).

What happened

  1. Dumped the full 2 MB over USB twice (byte-identical), built a .up package and verified it against the dump.
  2. Wanted album art, so I used dbrant/SL6801_player (built for yp3_2.0.43, a different model of the same family) to build an image, and wrote it with smartlink_flash starting at offset 0.
  3. The transfer died at [TODO: how far - bytes or offset, or unknown]. Since then: no USB device of any kind. Pressing Home makes the screen flicker, then it goes black [TODO: confirm].

An interrupted 2 MB write left the app partition corrupt. Now: black screen, nothing enumerates on USB. I need the mask-ROM USB download mode (301A:2800) to restore my backup, but no button combo triggers it. Looking for the boot-strap pin/pad on this board, or anyone who has recovered one.

Hardware

  • Player: Amazon "Cason" 16 GB MP3 player (the 16 GB is the bundled microSD; the brand is a sticker)
  • Board: silkscreen T90198-MP01-V2
  • SoC: marked "Jointbees MP3", QFN-48 [TODO: verify pin count], Smartlink SL6801 family (the string SL6801 is in the bootloader)
  • Flash: 2 MB inside the SoC package. No external SPI flash, so no clip or programmer route
  • Firmware: yp3_2.0.44
  • Other: [TODO: display type, confirm], microSD, USB-C, 5 buttons, small LiPo
  • USB IDs: card reader 301A:2801 "SMTLINK CARDREADER 1.00"; ROM bootloader 301A:2800 "SMTLINK DEVICE 2.00"

Flash layout from my dump:

0x00000   HLKJ header + bootloader (to ~0xC94C)
0x0D000   partition table
0x0E000   FIRM (~1.6 MB)
0x1A3000  TONE
0x1FC000  PSMP

Current state

Observed: nothing enumerates on USB (monitored with [TODO: dmesg -w / other tool], including the first second after plug-in). Screen flickers on Home, then black.

My reading (inferred, I can't read flash back now): the bootloader is still stock and running, and FIRM is corrupt. Basis: [TODO: what you checked, e.g. HLKJ header entry point, code offset, size, CRC16 recomputed and matching; how you know the transfer didn't overwrite 0x0-0xE000]. Please challenge this if you think the boot region could be damaged.

Boot path analysis (Ghidra + Capstone)

  • The bootloader picks its mode from a 3-bit value in the on-chip PMU registers (0x40085000): bit 0 of reg 0 plus bits 7:6 of reg 0x23. 6 = SD update (opens 0:\update.up and rewrites flash), 7 = update from PC over USB, anything else = normal boot.
  • Only software sets that value (the app's "firmware update" routine). With FIRM dead, nothing can set it.
  • I walked every instruction reachable from the reset vector. It never reads a button, GPIO input, or strap. It only touches the PMU, NVIC/SysTick, and GPIO writes for SD pin setup.
  • The SD updater has one call site, inside the mode == 6 branch. There's no "firmware broken, try the card" fallback. When loading FIRM fails, it prints an error over UART only (I can't reach it) and spins with interrupts off.
  • Mask ROM (per [TODO: link to the ROM-dump writeup, or delete this bullet]): it reads GPIO port 3 pin 0 at reset (active low). If low, it briefly waits for a USB host and shows up as 301A:2800. If the flash header/CRC is invalid, it stays in download mode.

What I tried

  1. update.up on the SD card (correct name and size). Nothing, which makes sense since the mode flag is never set.
  2. Each of the 5 buttons held on its own from a fully unpowered state (battery disconnected, USB out), then USB plugged in while still holding. Nothing.
  3. A few button pairs. Nothing.
  4. USB enumeration watched throughout. No device appears, not even briefly.
  5. Button wiring check: 4 of the 5 buttons share one analog ADC key ladder (there's a labelled ADC test pad), and only the center/power button is a plain GPIO line.

Questions

  1. Which button or pad is wired to the boot-strap pin (P3.0?) on SL6801 / "Jointbees" / T90198-MP01-V2 boards? Is it the center/power key, and does it have to be low at power-on reset rather than at USB insertion? My battery is disconnected during tests, so reset = USB plug.
  2. Is there a dedicated test pad on the back? The front has labelled pads for 5V, DM, DP, GND, ADC only. I haven't mapped the back yet.
  3. Does anyone know the UART TX pad? The bootloader prints its failure message there.
  4. Any other way to force ROM download mode (VBUS/D+ timing, a short-while-plugging trick)?
  5. Has anyone actually recovered one after a bad write? Even "it was button X" helps.

What I can share

Full 2 MB stock dump with checksums and layout, my annotated disassembly notes for the boot decision and the SD updater, the .up package, photos of both sides of the board. I also have an ESP32 and basic bench tools, so I can drive pins, sniff UART, or power-cycle under software control.

The mistake was mine: I flashed from offset 0 without first confirming how to reach ROM mode. I'm not after a lecture, just a way back to stock. Thanks!


r/hardwarehacking • • 4h ago

How much can you actually be certain of when debugging at the firmware/hardware level?

0 Upvotes

Coming from software, I'm used to well-defined standards and protocols. If a server returns a 404, I can be confident that, almost always, it means exactly what the HTTP spec says it means.

Lately I've been getting more hands-on with my own hardware and tinkering with electronics, and I've noticed there's no equally clear mapping between the signals the hardware gives you (POST codes, a fan that won't spin, and so on) and what they actually mean or what you can safely infer from them.

Where does that certainty come from in the hardware world, if anywhere? How do experienced people decide which signals they can trust besides just trying out a suspcious piece of hardware in a new system?