This is timely! I'm trying to take control of my Echo Wall Clock which connects to an Alexa device that I want to get rid of. There's very little info on it but Claude was able to find the FCC filings and now we've got lo-res images of the circuit board. It's inspecting the test pads on the circuit board now to see if it can figure out how to replace the firmware.
Everything I own, owned
161–170 of 367 posts
Re: Everything I own, owned
#162Earlier quoted context omitted.
The user should be the final authority over what his computer does. Not the computer manufacturer. Not the OS developer. Not the 3P app developer. Not some product manager at a software company. The end user. Even time computer says no, or does something without your permission, or does something counter to your wishes, or alerts you to do something, or urges you to do something, or makes you opt-out, is a failure.
The end user disables pixel cleaning because the pop-up annoys them. They then start bitching about burn-in within 6 months, RMA the monitor even though it was their choice to do so, and spread negative sentiment about your brand going forward for being "prone to burn in".
Re: Everything I own, owned
#163Earlier quoted context omitted.
Surprising. I have hit its BS guardrails a lot lately, working on my vintage computers from the 80s and early 90s. Just about done with Claude.
I’ve been doing this with Qwen 3.8 27B with success. Kindle, Android Tablet, and Raspberry Pi all working better and fully owned thanks to agentic help. No issues with hitting the guardrails here ofc.
Re: Everything I own, owned
#164Two weeks ago I told Claude “I have a on the LAN at . Assume direct control of it.” And about 8 command approvals later I had a new firmware running on it. Mind you, it found and used an existing firmware flashing library for this family of devices. But it felt amazing to do in 20 mins what would probably have been hours and hours of research and tinkering that I wasn’t interested in. I just wanted a WiFi lava lamp.
Surprising. I have hit its BS guardrails a lot lately, working on my vintage computers from the 80s and early 90s. Just about done with Claude.
Re: Everything I own, owned
#165But it's all dressed up as terror. "I did this thing, isn't it so so so very bad?!"
I hate this framing so much. The work here is so good, and making it look scary serves to bind us closer to a world where humankind has no control no visibility to powers over the world about them, where devices are sterile fixed things. That's the bad planet.
Re: Everything I own, owned
#166I posted [1] a few days ago my experience using LLM to reverse engineering an entirely undocumented device that was only supported by a (crappy) Windows application, and it was honestly remarkable how good Claude was at decompiling the Windows EXE and reverse engineering the protocol. Very exciting. "The developer refuses to write software for this device" is no longer as scary as it used to be. 1: https://news.ycomb…
Re: Everything I own, owned
#167Earlier quoted context omitted.
I know of the project but it doesn’t actually extract the stroke information. It converts the raster into vector. My reverse engineering extracts each pen stroke directly into a svg vector.
This sounds awesome if it works as you say. Will give it a shot tomorrow! Thank you for the tokens to solve this.
https://philips.github.io/supernote-web-component/
Click the "Pen" icon then the "Play" button.
Re: Everything I own, owned
#168Oh, I can have this thing read and write software for me? Great, I'm going to have it read and customize the software in every single computing device I own.
Re: Everything I own, owned
#169Ah, I remember when reversing hardware took weeks / months, an oscilloscope, logic analyzer, Ghidra/IDA, Wireshark, breakout boards, wireless sniffers... back in the olden days of... 2019.
if an AI could do it without an oscilloscope, probably a human could too.
https://netliststudio.com/articles/2026/02/23/claude-oscillo...
Re: Everything I own, owned
#170Earlier quoted context omitted.
If you're prepared to get out a soldering iron and/or chip-clip, you can usually back up and restore whatever IC stores the firmware you're modifying, giving you a recovery path. > we also need good glitching tools There are a lot already, what do you feel is missing?
How should I learn more about how to do it, what to buy, etc ? I haven't found ChatGPT to be a good teacher about this topic, and in particular re glitching, AI will refuse to discuss specifics I have enough basic soldering to get UART attached, but not sure what to try after that. Equipment-wise, I currently just have a few ESP32-C3s and electronics basics kit and some basic soldering stuff.