I have downloaded the latest version of the beta firmware for the original tracker, 1.9. 2, until now it was working with 1.8 because the following ones had problems. I have not seen significant changes and the master audio bars are still lagging, I have created a new project, and I have tried again to load version 1.8 which did work for me, I get a message to confirm the memory flash and when starting it, I get an error, update failed and the screen stays there, I have removed the power cable because I had no other option, it starts, but it stays on version 1.9. 2 if I try to put another version it does not let me.
Steps to Reproduce
1- Downloaded latest beta firmware version 1.9.2 for the original tracker
2- Previously using version 1.8 (last stable version) - subsequent versions had problems
3- No significant improvements observed in v1.9.2 - master audio bars still lagging
4- Created new project to test
5- Attempted to rollback to version 1.8 (previously functional)
6- System prompted memory flash confirmation
7- ERROR: “Update failed” message appeared during startup
8- Screen froze on error message
9- Forced to remove power cable (no other option available)
10- Device restarted but remained on version 1.9.2
11-CURRENT ISSUE: Unable to flash any other firmware version - all attempts blocked
I deleted all updates from the firmware folder and left only 1.8. I followed the instructions: I disconnected the power, inserted the SD card, connected the power, held the small reset button while pressing the power button - it didn’t start, neither by pressing the power button once nor by holding it. I released the reset button and tried to start it, and I got the “update failed” message. I inserted the 1.9.2 update back into the firmware folder and the tracker started up.
Yes, I tried version 1.9.1 during this process, but the result is the same. The problem is that it stays locked on version 1.9.2 and won’t allow any changes - it refuses to flash any other firmware version.
Alright.. just flashed back to 1.8.0 and then to 1.9.1 on my OG.
I’m attaching the firmware i have for you here, in case something is up with your firmware files.
I’m hoping i’m trustworthy enough that you don’t have to assume my files are malicious in any way
firmwares.zip (1.6 MB)
The zip contains OG Tracker firmware 1.8.0 and 1.9.1.
If this doesn’t work either. Try deleting the /workspace folder from your SD card.
As a last resort delete the trackerConfig file found in the root of the SD card.
Make a backup first of everything that i told you to delete, as it will delete/remove the last unsaved state and or reset your settings.
SOLVED - But something unusual happened during the process
Here’s the complete process and the strange behavior I encountered:
Backed up everything from my SD card (projects, samples, instruments)
Formatted the SD card to FAT32 using AOMEI Partition Assistant Standard (free tool) - necessary for my 128GB card since Windows won’t format cards larger than 32GB to FAT32
Downloaded the factory SD card content from my Polyend account and copied it to the formatted SD card
First boot attempt: Inserted the SD card and powered on normally - the Tracker still showed firmware 1.9.2. This confirmed the firmware is stored in the device’s internal memory, not on the SD card.
Added only the 1.8.0 firmware file (from your firmwares.zip) to the /Firmware folder
Performed the emergency flash procedure:
Powered off and disconnected from power
Inserted SD card
Connected USB cable
Held Reset button while pressing Power
Kept Reset pressed until device started
Strange behavior: The update process appeared to freeze/hang at the end (around 100%). After waiting with no progress, I had to disconnect the power cable to force a restart.
After forced restart: The Tracker booted successfully and is now running firmware 1.8.0.
This doesn’t seem normal - the update freezing and requiring a forced power disconnect isn’t standard behavior. However, it’s working now.
Should I be concerned about this, or is it a known issue with the emergency flash procedure? Has anyone else experienced the update hanging at the end?
