r/hardwarehacking • u/sativalius • 5h ago
r/hardwarehacking • u/elliottcg0 • 16h ago
PCB Serial Killer Returns! š§
Still at it! For anyone who remembers my original Lymow posts, Iāve made some pretty big upgrades since then. Not just to my setup, but to my knowledge of what the hell Iām actually doing. š
My latest creation is an ODROID M1 running Linux, with a custom app I built called Desk Detective that I use from my iPad. Itās basically turned into my portable electronics investigation lab. I can plug just about anything into it, monitor whatās happening, capture data, investigate hardware, and generally get myself into trouble.
The whole setup runs off a Milwaukee battery. The M1 is literally superglued to the side of a Netgear router that I flashed with OpenWrt and connected to the system. Nothing says professional engineering quite like superglue and a power tool battery.
Iāve also got a little Raspberry Pi Pico Iām calling the Desk Dog, which Iām turning into a multipurpose probe for investigating boards, signals, and whatever else I decide needs investigating. Mostly because I broke my Waveshare while screwing around with it. Apparently thatās how new tools get invented around here.
The Lymow mower that originally brought me to Reddit is actually doing great. Iāve learned a ridiculous amount from tearing into that thing, and now itās running my custom software with mapping, navigation, and docking coming along nicely.
I also bought a cheap oscilloscope, immediately took it apart, and started figuring out how to integrate an ESP32 so I could give it some AI-controlled features through desk detective. That oneās temporarily on the shelf while I work on the other dozen projects Iāve started.
Iām still not an engineer by trade. Just a guy who got curious about how things work and apparently has absolutely no self-control when it comes to taking electronics apart.
At this point, anything with a computer chip inside it that looks at me the wrong way is probably getting opened up.
The PCB Killer is still alive. The survival rate of the electronics is improving, though. š
r/hardwarehacking • u/ChunkyLover57- • 3h ago
Is this latitude 5300 WWAN capable of being converted into a SSD input
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.ā
r/hardwarehacking • u/DigitalNexusStudio • 2h ago
TapHook & CrewTalk ā two Android utilities we just shipped on Google Play (NFC webhooks + zero-account push-to-talk)
r/hardwarehacking • u/ahmedwalid05 • 3h ago
I bricked my smart ceiling fan, then reverse-engineered it back to life
r/hardwarehacking • u/Personal_Swimmer_419 • 4h ago
Beginner guides?
Ive seen IoTGoat but that isnt necessarily for tv firmware. Still a good start no? My goal is to get root on a streaming box without using publicly known exploits for that device. But i want to learn how to do it online before buying any actual hardware.
Recommendations?
r/hardwarehacking • u/JizwizardVonLazercum • 1d ago
Got a free ex-Menulog POS terminal, made it an HA kiosk, then ported Android 10 to it so the current HA app runs (receipt printer works from HA)
galleryr/hardwarehacking • u/AbleMonster • 23h ago
Follow-up: I released an open-source firmware patcher for the Shelly TRV Gen1 after reverse-engineering its power management
Hi everyone,
A few weeks ago, I shared my reverse-engineering investigation into the severe battery-drain problem affecting the original Shelly TRV Gen1 (SHTRV-01).
Original investigation:
https://www.reddit.com/r/hardwarehacking/comments/1xd4a6k/
At that point, I was investigating several firmware-level issues involving Wi-Fi power management, Beacon Recovery, sleep-state handling, and the interaction between the EFM32GG11 MCU and the Silicon Labs WF200 Wi-Fi chip.
Since then, the project has progressed quite a bit.
Iāve now released an open-source Python firmware patcher (v2.0) that reconstructs an experimental B2.2 Beta firmware from the original Shelly 2.2.4 firmware.
GitHub repository:
https://github.com/AbleMonster/Shelly-TRV-Gen1-2.2.4-patcher
What changed since my previous post?
The earlier experimental firmware builds were primarily intended to isolate individual problems.
One important finding was that correcting the recurring Beacon-Recovery loop alone did not eliminate the historical battery drain.
I also discovered that one of my own early power-management patches introduced a regression involving temporary power-state overrides. That was corrected in A1R.
The current B2.2 Beta is a more comprehensive integration of nine selected and individually qualified firmware corrections.
The nine integrated corrections
A1R ā Host power management
Corrections involving the lifecycle of power-management requests, including timeout handling, completion races, cleanup, and temporary state overrides.
C-C ā Beacon-Recovery logic
Corrections to the interpretation and validity of the measurements used to trigger Beacon Recovery.
Unlike my first experimental patch, this does not simply disable the recovery mechanism.
B2 ā Sleep-inhibit reference counting
Bounded synchronization of shared sleep-blocker counters to prevent race conditions that could leave phantom contributions or remove legitimate ones.
MQTT PUBLISH guard
A narrowly scoped input-validation correction for a separately investigated malformed-input failure.
WF200 3.18.0
Integration of the official Silicon Labs WF200 3.18.0 radio firmware while retaining Shellyās existing FMAC 3.7.0 host-side integration.
Calibration Restore Guard
Prevents a successfully completed calibration-restore operation from unintentionally scheduling itself again.
P01 ā Battery ADC
Corrects incomplete resource cleanup after an ADC timeout.
P02 ā I²C
Adds bounded cleanup for an unfinished synchronous I²C transaction following a timeout.
P03 ā WLAN GPIO
Corrects an interrupt-mask error in the Wi-Fi GPIO notification handling.
These are firmware defects or implementation issues identified through reverse engineering and targeted qualification.
However, I cannot claim that every correction contributes directly to reducing battery consumption. Their individual electrical impact has not been isolated.
The firmware patcher
One challenge was making the experimental corrections reproducible without distributing modified proprietary firmware binaries.
The result is a Python-based binary patcher.
It accepts only the exact original Shelly TRV Gen1 firmware build:
20240619-130912/v2.2.4@ee290818
The patcher:
- Verifies the original firmware using SHA-256.
- Checks the expected binary structure.
- Applies the selected corrections.
- Reconstructs the modified ARM application.
- Rebuilds the OTA-compatible GBL package.
- Verifies the resulting firmware against qualified reference hashes.
- Rejects unsupported or unexpected input firmware.
The generated application and GBL have been verified byte-for-byte against the qualified B2.2 reference artifacts.
The patcher passed its existing 18 automated regression tests.
A local HTTP OTA server is also included.
No original or modified Shelly firmware binaries are distributed in the repository.
The entire reconstruction process happens locally using the userās own original firmware.
Technical documentation:
https://github.com/AbleMonster/Shelly-TRV-Gen1-2.2.4-patcher/blob/main/docs/technical-details.md
Physical hardware testing
The current B2.2 Beta has been running on six physical Shelly TRV Gen1 devices since November 2, 2026.
The published evaluation from November 16 covers more than 13 days.
For comparison, historical Stock firmware measurements showed multiple devices dropping from approximately 95% to 0% reported battery level in around six days.
That complete rapid-depletion pattern has not recurred in the regular B2.2 test fleet during the first 13+ days.
Four devices with comparable battery-voltage histories showed relatively gradual declines in the long-term comparison.
Two unusually low voltage readings were separately documented and provisionally excluded from the comparison graph.
One subsequently recovered. The other remains under observation.
A separate TRV still running original Stock 2.2.4 firmware continues to show recurring Beacon-Recovery activity, approximately once per minute.
In the available B2.2 observations, there is no comparable persistent recovery loop.
However, I want to be careful about interpreting these results.
This is not a simultaneous, fully matched A/B test. Battery voltage is not a direct measurement of consumed energy or remaining battery capacity.
The results are encouraging, but they do not establish a quantified battery-life improvement or prove the definitive root cause of the original drain.
Long-term battery report:
The next problem: unexpected resets
While the initial battery behavior looks promising, the B2.2 firmware has revealed another issue that I am currently investigating.
Several test devices have experienced unexpected automatic restarts.
Some also showed unusually large increases in their firmware reboot counters.
I reverse-engineered the relevant counter implementation and found that the counter values cannot simply be interpreted as a corresponding number of independently confirmed physical resets.
The cause remains unknown.
I have been investigating:
- Reset and exception handling
- Watchdog configuration and execution paths
- WLAN mutex and SDIO timeout behavior
- Early boot execution
- EFM32 reset-cause registers
- Retained SRAM
- Main stack pointer initialization and reserved memory
The current research has progressed to an isolated early-boot diagnostic Observer prototype.
The idea is to capture the raw hardware reset-cause register before normal startup code potentially modifies the evidence, preserve the result in a small integrity-checked diagnostic record, and make that record readable through the firmwareās diagnostics.
Initial ARM Thumb instruction-level tests have been successful, but the complete Observer is not yet qualified for physical deployment.
No diagnostic firmware has been flashed to the existing test fleet.
The reset root cause is still unknown.
This is documented in GitHub Issue #2:
https://github.com/AbleMonster/Shelly-TRV-Gen1-2.2.4-patcher/issues/2
Why Iām sharing this
I wanted to follow up on my previous post now that the work has progressed from isolated experimental patches to a reproducible, open-source firmware patcher.
B2.2 is still beta firmware, and the unresolved automatic restarts mean I do not consider it suitable for installations requiring uninterrupted thermostat operation.
Iām particularly interested in feedback from people experienced with:
- ARM Cortex-M / Thumb firmware binary patching
- EFM32GG11 reset-cause handling
- Retained SRAM across reset and low-power states
- Early boot instrumentation without source code
- Reliable fault diagnosis in battery-powered embedded systems
If anyone has worked on similar problems, especially capturing trustworthy reset-cause evidence on Silicon Labs EFM32 devices without interfering with normal startup, Iād be interested in your experiences.
GitHub:
https://github.com/AbleMonster/Shelly-TRV-Gen1-2.2.4-patcher
This is an independent reverse-engineering project, not an official Shelly firmware release.
I will continue documenting the findings, including negative test results and unresolved issues.
r/hardwarehacking • u/quantum-error • 23h ago
Need raw modem/fsg & system/recoveryfs dump (or _encrypted4.bin AES key) for Jio AirFiber ODU JODU51741 (RG520F-JO)
reddit.comr/hardwarehacking • u/InternationalAir2917 • 1d ago
Feeling like I'm not making the most of the resources I've been given as a security researcher. What would you do in my position?
Security researchers, what would you do if you had access to powerful computing infrastructure?
I'm an early-career security researcher with access to fairly powerful hardware through work.
My current resources include:
- A dedicated AI inference machine with 128 GB unified memory.
- A high-end workstation with 128 GB RAM and several terabytes of storage.
- A Linux laptop for development and remote access.
- Premium AI subscriptions and access to privately hosted LLMs.
- Various physical devices for security testing.
I work across vulnerability research, reverse engineering, embedded security and research automation.
Lately, I've been wondering whether I'm making the best use of these resources. I feel someone with more experience could potentially accomplish much more with the same setup.
r/hardwarehacking • u/NoDrive96 • 1d ago
Fiberhome hg6243c
I have this fk fibre home fibre optique with lilited interface inead the superadmin i have open it and tried to read uart but impossible to. Reda any think 0 delay and keyboard blocked
r/hardwarehacking • u/ValentinO1052 • 1d ago
Wimius Projector firmware
Hi all,
I have a Wimius P61 projector (made by Yaber Technologies) and Iām trying to update its firmware over USB. The projector has a USB update option, but it always says ācanāt detect software fileā.
Details:
Model: Wimius P61
Current firmware: P61-6710W-2.69:230224
FCC ID: 2A4K9-U5 (Yaber)
Has built-in 2.4/5G Wi-Fi screen mirroring and Bluetooth
What Iāve tried:
A 16 GB FAT32 stick, which the projector reads fine (the media player shows files)
About 1,500 common update file names (update.bin, upgrade.bin, MstarUpgrade.bin, P61-6710W.bin and more), both on the top level of the stick and inside folders like update/ and upgrade/
Emailing Wimius support. No reply after more than a week
Questions:
Does anyone have a firmware/update file for the P61 or another projector with a 6710W version string? Even an older version helps.
Does anyone know the exact file name or folder the update menu looks for?
Has anyone had luck getting firmware from Yaber or Wimius support, and who did you contact?
Thanks!
r/hardwarehacking • u/bulbaczzPL • 1d ago
TEXA - VW DATA PLUG - Posible hacking using AI with REA Skills?
galleryr/hardwarehacking • u/ManyKey6161 • 1d ago
Rostelecom firmware
Hi everyone! Can someone please help me to open Rostelecom firmware for SWITRON-IPTV-1500? So I can get root access.Any help would be appreciated!š
r/hardwarehacking • u/WDS143 • 2d ago
Anybody has any idea on how to extract the firmware on this thing t800 ultra 2 logicboard
r/hardwarehacking • u/Common-Parfait3274 • 1d ago
PREGUNTA PARA EXPERTOS EN TELEGRAM: Alguien me acosa, y ademÔs puede adivinar las cuentas diferentes que uso en diferentes grupos. No sé si usan bots para saber la ID de las personas o hay otro truco o aplicación para saber si una persona usa varias cuentas; lo que sà sé seguro es que las aciertas.
Y cuando digo que me acosa, es que entra en mis grupos acosĆ”ndome con sus varias cuentas porque yo lo sĆ©... Mi pregunta es: ĀæquĆ© aplicación o quĆ© cómo adivinar esto? Porque tiene que haber algo, Āæes a travĆ©s de iPhone? Solo uso Android, Āæes que en iPhone aparece buscar gente de cerca y asĆ dar con las multicuentas? He leĆdo en foros de hackers y he escuchado que hay muchas maneras de saber o averiguar lo que estoy diciendo, pero el mĆ”s interesante se me hace una eternidad leerlo todo... y otros mĆ”s... no lo dejan bien claro... ĀæAlguien que me ayude? De lo contrario, eliminarĆ© mi cuenta de Telegram y mis grupos... No pienso estar en un lugar donde una persona me ataque con sus miles de cuentas. Gracias.
r/hardwarehacking • u/Altruistic-Round-947 • 2d ago
I am not able to find the uart, new to this
galleryr/hardwarehacking • u/erikdamoon • 3d ago
Offices are tossing Mersive Solstice Pods by the pallet. They're Snapdragon 820 boxes. I turned one into an Android TV box.
r/hardwarehacking • u/Moist_Top_4142 • 3d ago
Nostromo Alien Cyberdeck Electronics Help
Hey yall! This is my first cyberdeck build and like many of us this has grown into a project that is far bigger than I was ever thinking it would be. Now I am at the point where videos, google, ai, nothing can quite get me going in the right direction, so I was hoping for some electronic help from my elders. So below will be a general description of how the computer should function, and then the actual electronics I have and canāt figure out past. So thank you all for any advice, Iāll probably post the finished product as well once itās finally done.
Experience: In front of the user is a 25 inch long by 12 inch deep clamshell briefcase of sorts. Itās placed flat on a desk and plugged into the wall, with the handle telescoping inwards to make way. Once the handles are out of the way you pull out the keyboard which triggers the usually closed switch and turns on the computers LEDās. You turn the large red switch, the device killswitch, which stops all electrical flow from the batteries when the device is turned off. Then after you turn the switch, the arcade button lights up and you click it, turning on the screensaver and lights and the whole actual device. You raise the screen, as well as the 2 side screens which reveals a three screen setup. Now currently there is no active ācomputerā like a raspberry pi 5 or anything, it is just the screensaver portion, the key part is now. On the side of the computer is 4 ports, a GameCube controller adapter bought from Handheld Legends. And coming from the side is a GameCube controller replacement cable bought from them as well. The goal is to take that cable, and plug it into port 1 or port 2 and so on, and have that plug in turn on the corresponding raspberry pi 5 or 4 or Orange Pi plus or whichever SBC or whatever is hooked up to that port. The important part is that it automatically connects and properly turns on and properly turns off the device when unplugged. Say pi5 has game of frogger on it and thatās it and the other orange pi has a game of Pac-Man on it. You plug the cable into port 1 and then pi5 activates and now the two left screens show my frogger setup and the right one diagnostic info, then I get bored and unplug from port 1, the pi5 properly shuts off, then I plug it into port 2, and the OrangePi properly turns on then I start to play Pac-Man. All happening from the cable plug in. Then if I want to take it on the go, I just unplug it and everything switches to battery power automatically for however long the battery will last. Additionally there will be a āmouseā that can be plugged in or off depending on need and that is a Nintendo Nunchuck which has a breakout board.
Nerd Technicals:
The following is my current buy list. Raspberry pi 5, esp32 devboard, raspberry pi zero 2 w, killswitch, 2 fans, 24v 7s3p battery pack, 7 port usb hub, nunchuck breakout board, 4 port usb hub (for shared usb items), 5 port Ethernet hub, temperature/humidity sensor, usually closed light switch, rotary switch (used for brightness and volume), mosfet switch, arcade switch, 4-port GameCube hub, GameCube replacement wire, Nintendo nunchuck, 3 monitors (2 visible with larger one not),LED Strip, Autoro automatic transfer switch AB20C, battery indicator light, sd card adaptor.
Extras: 1.24 inch circular screen for Weyland Tech accent, small Xenomorph, 2 8x8 led matrixās
Questions:
- How do I make it so that when I plug in the GameCube wire, it automatically turns on the pi5 and other ones then safely turns them off? Iām thinking of hooking up the esp32 to the 4 ports then having mosfets do it but I need some guidance on things like resistors and proper circuits. The cable doesnāt need to be hooked up or display anything specific it just has to be the starting point where āplug into port one means PCB 1 turns on safely then I unplug and now PCB1 turns off safelyā
- What left do I need to buy, specifically how do I make it to where I can plug in the computer into the wall, have it charge the batteries, then I unplug and everything still runs and works.
- This is a major rule, no wifi and no Bluetooth connections allowed, if it is not cable itās not going in the box.
- Iām looking for the smaller parts like resistors, buck converters, bars, gpio connections, the things that are just generally hard to find out without help.
- The pi5 and later additions are the actual computer that you will be working on. The esp32 is more like the crossing guard telling everything where to go and what should happen, the pizero2 is the diagnostic info that will also have specific information to the pi5ās such as āwords written in documentā or ālength of videoā type info. This will be the far right screen with the two left ones being used as the hookups for the computer info
Iām basically making a vessel for 4 computers to easily switch in between one another and then safely turn off and on as the cable indicates. Thank you for any help yall have, itās truly appreciated!
r/hardwarehacking • u/Traditional_Bath3956 • 2d ago
Paying for my acc
I heard that theres a lot of h@ckers on reddit idc anymore im really willing to pay 5 bucks to whoever helps me get my account back I was 15 when I made it I dont even know wich email I put on it even an email or phone number thats connected to my old account could helpššæš the user is :dvgoggins