r/hardwarehacking • u/ahmedwalid05 • 12h ago
I bricked my smart ceiling fan, then reverse-engineered it back to life
r/hardwarehacking • u/ahmedwalid05 • 12h ago
r/hardwarehacking • u/emirdev_mo • 7h ago
I kept buying hardware (case LCDs, RGB controllers, fan hubs) that only works with a Windows vendor app, and doing the same reverse engineering by hand every time: capture with USBPcap or usbmon, stare at hex, diff packets, guess which byte is the fan speed and which one is a counter or CRC.
So I built usb-rea to automate the boring part. You capture traffic while you use the vendor app, mark what you did ("set fan to 40%", "set color red"), and it infers the command structure: constant headers, counters, value fields, lookup tables and checksums (it brute-forces common CRC variants). The output is a Markdown protocol report plus a standalone pyusb driver you can run on Linux.
How I checked it without guessing: I run it on public captures of devices whose protocol is already documented. On NZXT Kraken X captures it recovers the same fan command liquidctl sends, byte for byte, and the generated driver builds correct packets for values that never appeared in the capture. There is also a lookup command that checks a VID:PID against about 270 devices that already have an open-source Linux implementation, so you don't redo work someone already did.
It is MIT licensed, pip install usb-rea. It also runs as an MCP server if you want an LLM client to drive the analysis, but the CLI works on its own.
Repo: https://github.com/emirmrkaljevic/usb-rea
Limits, honestly: it is alpha. Linear value fits have to survive a leave-one-out cross-check, otherwise it falls back to a lookup table and says so, and a matching USB ID alone does not prove your unit speaks the same protocol. I would love captures or feedback from devices where it gets things wrong.
r/hardwarehacking • u/ConsequenceThen217 • 5h ago
r/hardwarehacking • u/sativalius • 14h ago
r/hardwarehacking • u/Significant-Leg-3857 • 8h ago
$1$..He2Y7u$/4hOpu/J6s6zFixbzvkDm.
r/hardwarehacking • u/ChunkyLover57- • 13h ago
I am on a dell latitude 5300 and did not have this option from the factory. Ai told me that theres no power because its not detectable etc. im running linuxmint btw. In my bios there is the option to enable it. Not sure what to do.
I was told there’s a severe hardware limitation, but it communicates with the computer and nevertheless it should be able to be repurposed.
I’m not opposed to taking it to a shop and having them add something I just don’t know where to start
“Slapped an M.2 2230 NVMe drive into the WWAN slot on a Latitude 5300.
Bullet Checked the BIOS: AHCI was already on, both SATA-2 and M.2 PCIe SSD-0 were enabled, and tested toggling WWAN/GPS on and off with cold boots.
Bullet Ran lspci -nnk, lsblk, nvme list, and checked dmesg on Linux—only the main NVMe drive (nvme0n1) shows up, and zero PCIe lanes or controllers initialize for the WWAN slot.
Bullet Popped the bottom cover and looked at the board around the WWAN slot—the SMD components and PCIe traces needed for storage were left unpopulated from the factory.”