Using A Waffle To Check The Health Of Your Wii U’s NAND Flash

October 13, 2026 by Maya Posch 13 Comments

Game consoles tend to have a weak spot or two that will take certain units out sooner than they would due to normal parts aging. In the case of the Wii U it’s the eMMC storage IC with the console’s firmware and any user data that likes to keel over, with the SK Hynix variant reportedly developing faulty cells much sooner than the Samsung and Toshiba chips. If you want to check the health of these eMMC ICs in your Wii U, you can do so easily now with the Wafel Installer project by [zer00p].

This doesn’t take much more than navigating to the wafel.xyz URL on the Wii U to launch the installer on any (unmodified) Wii U, or alternatively starting it from an SD card if you’re running a homebrew-enabled console. This can also install the Stroopwafel CFW, ISFSax and the Aroma homebrew environment, but the NAND testing option in the installer’s menu is what you want to select if you’re not into homebrew or have already cracked open the console for said sweet homebrew action.

All of this is covered in this video by [FunkyScott47], whose Wii U’s Samsung-branded eMMC is fortunately still all fine, but it shows off the variety of tests available. Unless the eMMC is already quite cooked this should take only a minute or two, so it’s pretty good for ease of mind.

With the heavily waffle, syrup and stroopwafel-coded naming scheme for these tools we can not be held responsible for a sudden case of the munchies, of course.

Continue reading “Using A Waffle To Check The Health Of Your Wii U’s NAND Flash” →

Fixing An Expensive Amprobe Cable Tracer With Mystery Fault

August 31, 2026 by Maya Posch 13 Comments

Perhaps the most annoying kinds of faults are those that involve expensive equipment that just sit around in a cupboard, only for them to just stop working at all. Such was the case with the £2,000 Amprobe cable trace kit that [Tom] bought for work-related purposes. After sitting around unused for a few years, the signal generating part of the kit refused to power up at all, with Fluke’s service department wanting at least £600 to even attempt a repair after already having had [Tom] cough up £70 to even get this quote.

Subsequently he instead sent it to [Buy it Fix it] on YouTube for an attempted repair, which at the very least would be a less costly option. These systems use a signal generator connected to the cable, with a separate detector wirelessly tracking this signal. By itself that doesn’t sound too complex, but as it turns out it wasn’t quite so straightforward to diagnose.

After eliminating a basic power or display issue, the SoC’s boot sequence was traced, including reading from the 128 MB NAND Flash. At first glance the unit appeared to be trying to boot and work as normal, which was confirmed after finding a serial port and seeing the log output on it. This showed that the NAND Flash’s boot image failed validation due to apparent corruption.

After desoldering the TSOP 48 Flash package and stuffing it into a reader, at first glance the data on it looked fine. After a tragic detour with Google’s Gemini chatbot that led to a lot of wasted time, the solution that the human intelligence came up with was to crack open the tracer unit in the set and ogle at its firmware, in particular the bootloader.

Comparing the two Flash dump files, there were a few flipped bits in the bootloader section, likely due to cells in the Flash having lost their charge. Writing the generator’s Flash with a corrected image led to it booting up happily again into the Linux 2.6-based firmware, seemingly no worse for wear. Of course, one has to consider here that the NAND Flash IC clearly has a few leaky cells in it, so replacing it with a fresh one could be a good idea for a long-term fix.

Continue reading “Fixing An Expensive Amprobe Cable Tracer With Mystery Fault” →

Remember When Flash Drives Were Going To Make Your PC Faster?

May 26, 2026 by Zoe Skyforest 47 Comments

The 2000s was a decade of great change in the computer industry. The world had grown accustomed to corruptible floppy disks, blue screens of death, and achingly slow load times. In a few short years, all of that would change, as USB drives, better operating systems, and faster processors brought forth a new age of stability and speed.

Amidst this era of upheaval, Microsoft introduced a new technology. It was intended to increase performance on the cheap to a new generation of machines, but it would turn out to be little more than a gimmick that never really caught on. Let’s explore the easily-forgotten legacy of ReadyBoost.

Continue reading “Remember When Flash Drives Were Going To Make Your PC Faster?” →

Upgrading A MacBook Neo Using A 1 TB IPhone NAND Flash

April 9, 2026 by Maya Posch 10 Comments

The nekkid Flash footprint with unused pads perimeter. (Credit: dosdude1, YouTube)

For some reason the newly introduced MacBook Neo appears to be the subject of a lot of modding, though a recent mod by [dosdude1] leans into the fact that this laptop has been assembled using what are effectively iPhone 16 parts inside a laptop case. This consequently means that there’s an overlap with certain iPhone 16 components, such as the NAND Flash. Incidentally storage on the Neo is limited to 512 GB when you purchase it from Apple, which is weird since the same SoC in the iPhone 16 Pro happily uses 1 TB.

Even if it was just a price point thing that Apple went for, there’s seemingly nothing standing between a Neo owner with a hot air gun and sheer determination. As long as you’re comfortable soldering a fine-pitched BGA NAND Flash package, natch.

Of course, there was always the possibility that Apple used a different NAND Flash package footprint, but the installed 256 GB model chip that comes installed matches the replacement 1 TB model K8A5 chip as hoped. This just left disassembly and preparing the PCB for a storage replacement. Removal of the BGA underfill and desoldering the old chip without taking out surrounding SMD parts is definitely the hardest part, but handled in the video with the equivalent of an IC spatula and a temporary removal of some capacitors.

Interestingly, the uncovered IC footprint shows a whole perimeter of unused pads that might target other NAND Flash packages. Regardless, the new chip installed fine, giving the Neo 1 TB of storage and a slightly faster read/write performance.

Continue reading “Upgrading A MacBook Neo Using A 1 TB IPhone NAND Flash” →

An SD Card Of Your Own For Microcontroller Projects

January 13, 2026 by Tyler August 22 Comments

If you’ve wiring up a microcontroller and need some kind of storage, it’s likely you’ll reach for an SD card. Compared to other ways of holding data on your project, SD cards are just so much cheaper, resilient to physical and magnetic shocks, and simpler to work with from both a hardware and software perspective. On the other hand, it might seem silly to put a SD card slot on a board that’s never going to see a replacement card. [DIY GUY Chris] wants to advertise a solution for that: a cardless SD card chip by XTX that can act as a drop-in replacement for your projects.

The XTXD0*G series are NAND flash chips of precisely the sort you’d find in an SD card, except without the SD card. That means you can use your usual SD card access libraries to speed prototyping, but skip the BOM cost of an actual card reader. In his Instructable and the video embedded below [Chris] shows how he used the 4 Gbit version, the XTSD04GLGEAG to make a custom SD-compatible breakout board that is equally happy in your laptop’s card reader or on a breadboard.

To get it plugged into the breadboard, [Chris] is using the standard 2.54 mm headers you can get anywhere; to get it plugged into a card reader, he’s just relying on the PCB being cut to shape. [Chris] notes that you’ll want to have the board built at 0.6 mm thickness if you’re going to plug it in like a micro SD card.

Of course once you’ve gotten used to the little NAND chips, there’s no need to put them on breakouts but this looks like a fun way to test ’em out. You don’t need to keep your flash chip on an SD-card sized PCB, either; we saw something similar used to make modern game cartridges. If you insist on using a standard SD card and don’t want to buy a slot, you can certainly DIY that instead.

Continue reading “An SD Card Of Your Own For Microcontroller Projects” →

The Flash Memory Lifespan Question: Why QLC May Be NAND Flash’s Swan Song

July 8, 2024 by Maya Posch 87 Comments

The late 1990s saw the widespread introduction of solid-state storage based around NAND Flash. Ranging from memory cards for portable devices to storage for desktops and laptops, the data storage future was prophesied to rid us of the shackles of magnetic storage that had held us down until then. As solid-state drives (SSDs) took off in the consumer market, there were those who confidently knew that before long everyone would be using SSDs and hard-disk drives (HDDs) would be relegated to the dust bin of history as the price per gigabyte and general performance of SSDs would just be too competitive.

Fast-forward a number of years, and we are now in a timeline where people are modifying SSDs to have less storage space, just so that their performance and lifespan are less terrible. The reason for this is that by now NAND Flash has hit a number of limits that prevent it from further scaling density-wise, mostly in terms of its feature size. Workarounds include stacking more layers on top of each other (3D NAND) and increasing the number of voltage levels – and thus bits – within an individual cell. Although this has boosted the storage capacity, the transition from single-level cell (SLC) to multi-level (MLC) and today’s TLC and QLC NAND Flash have come at severe penalties, mostly in the form of limited write cycles and much reduced transfer speeds.

So how did we get here, and is there life beyond QLC NAND Flash?

Continue reading “The Flash Memory Lifespan Question: Why QLC May Be NAND Flash’s Swan Song” →

Reverse Engineering Reveals EV Charger Has A Sense Of Security

November 16, 2022 by Dan Maloney 11 Comments

As more and more electric vehicles penetrate the market, there’s going to have to be a proportional rise in the number of charging stations that are built into parking garages, apartment complexes, and even private homes. And the more that happens, the more chargers we’re going to start seeing where security is at best an afterthought in their design.

But as this EV charger teardown and reverse engineering shows, it doesn’t necessarily have to be that way. The charger is a Zaptec Pro station that can do up to 22 kW, and the analysis was done by [Harrison Sand] and [Andreas Claesson]. These are just the kinds of chargers that will likely be widely installed over the next decade, and there’s surprisingly little to them. [Harrison] and [Andreas] found a pair of PCBs, one for the power electronics and one for the control circuits. The latter supports a number of connectivity options, like 4G, WiFi, and Bluetooth, plus some RFID and powerline communications. There are two microcontrollers, a PIC and an ARM Cortex-A7.

Despite the ARM chip, the board seemed to lack an obvious JTAG port, and while some unpopulated pads did end up having a UART line, there was no shell access possible. An on-board micro SD card slot seemed an obvious target for attack, and some of the Linux images they tried yielded at least a partial boot-up, but without knowing the specific hardware configuration on the board, that’s just shooting in the dark. That’s when the NAND flash chip was popped off the board to dump the firmware, which allowed them to extract the devicetree and build a custom bootloader to finally own root.

The article has a lot of fascinating details on the exploit and what they discovered after getting in, like the fact that even if you had the factory-set Bluetooth PIN, you wouldn’t be able to get free charging. So overall, a pretty good security setup, even if they were able to get in by dumping the firmware. This all reminds us a little of the smart meter reverse engineering our friend [Hash] has been doing, in terms of both methodology and results.

Thanks to [Thinkerer] for the tip.