u/Objective_Fox7761

Settings stuck at 0%, messages reappear after reboot, reflashing does NOT fix it

I wanted to document this because it took many hours to figure out and may help someone else.

Symptoms

Two Seeed Wio Tracker L1 nodes developed identical behavior.

Android app connected normally over Bluetooth.

Nodes could send and receive messages.

Every Settings page remained at 0% and never loaded.

Deleted messages would reappear after every reboot.

Node configuration could not be changed.

Reflashing firmware (multiple versions) had no effect.

Erase UF2 appeared to complete successfully, but the node always came back with the exact same configuration and messages.

What DID NOT fix it

Reflashing the latest firmware.

Downgrading firmware (2.7.26 → 2.7.15).

Using the nrf_erase_sd7_3.uf2 erase file.

Using the Universal Nuke UF2.

Drag-and-drop UF2 flashing.

Multiple firmware reflashes.

The bootloader worked perfectly, but none of those methods cleared the corrupted configuration.

What DID work

Install the Meshtastic Python CLI:

py -m pip install meshtastic

Verify communication:

py -m meshtastic --info

Then perform a factory reset:

py -m meshtastic --factory-reset

The CLI responded:

Connected to radio

INFO ... Telling node to factory reset (config reset)

After unplugging and rebooting, the node displayed the Welcome to Meshtastic first-run screen.

The Android app immediately worked normally again.

Settings loaded correctly.

Old messages were gone.

Node could be configured normally.

I repeated the exact same procedure on my second Wio Tracker L1 with identical results.

Conclusion

The problem was not:

Bad firmware.

Bad hardware.

Bad flash memory.

Bluetooth.

The Android app.

The problem was a corrupted Meshtastic configuration that survived firmware reflashing and UF2 erase operations.

The Meshtastic CLI --factory-reset clears something that the normal firmware flashing process does not.

If your Wio Tracker L1:

Connects normally.

Has Settings stuck at 0%.

Keeps bringing deleted messages back after reboot.

Reflashing doesn't help.

Try this before assuming the hardware is defective:

py -m meshtastic --factory-reset

Hopefully this saves someone else several hours of troubleshooting.

Special thanks to ChatGPT for sticking with me through hours of troubleshooting and helping narrow the issue down to a corrupted configuration instead of a hardware failure. Without that guidance, I probably would have assumed both nodes were defective.

I hope this helps the next person who runs into the same problem.