Hacking the Kodak Reels 8mm Film Digitizer (New Thread)

FrenchNum

New Tinkerer
Jul 11, 2026
3
0
1
Bonjour à tous (voix de Nick Rivera)

Merci infiniment pour votre travail acharné de désensibilisation de ces unités. C'est inestimable ; votre contribution est tout simplement phénoménale.

Mon appareil possède un numéro de série qui semble différent de tous les autres. Je l'ai acheté récemment, donc je ne sais pas exactement où il se situe dans la hiérarchie des firmwares. Mon numéro de série est A3026148BK01272. Il utilise probablement le firmware B, puisqu'il ne figure pas sur la liste, mais il présente également des similitudes avec le firmware D.

H2825148BKxxxx - le D
A3026148BK01272

Je l'ai acheté sur Amazon, en Australie. Les prises fournies sont de type européen, britannique et américain (je les ai simplement pliées pour leur donner la forme coudée australienne, après avoir vérifié qu'elles supportent le 240 V).

La numérisation est correcte, mais avec tous les défauts habituels du firmware standard. Je ne compte pas investir dans des améliorations complètes comme un objectif 12 mm ou des modifications du boîtier, mais une meilleure résolution et un débit binaire plus élevé seraient appréciables. Je suppose également que le moteur de la bobine réceptrice a une durée de vie limitée, compte tenu des problèmes signalés par d'autres utilisateurs.

Need help recovering Kodak REELS (RODREELSEU) after wrong firmware – Looking for original firmware or SPI dump​


Hello everyone,

I hope someone can help me.
Unfortunately, before reading the latest posts in this thread, I used the old firmware lookup tool, which identified my scanner as Firmware B.
The firmware flashed successfully, but after reboot the scanner no longer works correctly.

Current symptoms​

  • Kodak logo appears normally.
  • LCD display works perfectly.
  • Power button still works.
  • All other buttons are completely unresponsive.
  • Motors never start.
  • Film transport is completely dead.
  • The scanner cannot be used anymore.
I waited more than 5 minutes after flashing to make sure the update had completed.

I have tested all three Firmware B variants:
  • Original Firmware
  • Original Resolution HBR
  • 1440p HBR
All three produce exactly the same result.

I have NOT tried Firmware A, C or D because I have read about users damaging their displays by flashing the wrong firmware.

Device Information​


Model
Kodak REELS Film Digitizer (RODREELSEU)

Main board
DV280N_MAIN_V0.6

PCB Date:
2021-04-16

Main SoC
Novatek NT96658MBG-NH

SPI Flash
Macronix MX25L3233F (32 Mbit)

Motor Driver Board
DV280N_TMC_Driver_V0.2

Motor Driver IC
Trinamic TMC2226-SA

Camera Board
DV280M_S_A4010_V0.1

PCB Date:
2025-03-07

Additional hardware information:
  • UART header available (3.3V / TX / RX / GND)
  • High-resolution PCB pictures are attached.
Why I think this is a hardware revision issue

While searching the forum, I found another user with an almost identical serial number (A3026148BK01272).

My unit is:

A3026148BK013xx

The serial numbers differ by only 99 units.

From the recent discussion, it appears that the old lookup table is no longer reliable for these newer revisions, and my scanner may actually belong to a newer hardware revision rather than the old Firmware B family.

What I am looking for​

I am NOT looking for Firmware A, B, C or D.
I am looking for one of the following:
  • Original factory firmware for this exact hardware revision
  • Original FWDV280.BIN
  • Original UITRON.BIN
  • Complete SPI flash dump (MX25L3233F)
  • Official recovery procedure
  • Novatek recovery tools
If anyone owns the same hardware revision, or has already dumped the original firmware, I would really appreciate any help.

Thank you very much.

Attached:
  • Main board photos
  • Camera board photos
  • Motor driver board photos
  • Diagnostic report

Attached: High-resolution PCB photos and detailed hardware report (FR/EN).
 

Attachments

  • Kodak_REELS_Diagnostic_Package.zip
    2 MB · Views: 5
Last edited:

Eradicator

New Tinkerer
May 27, 2026
10
5
3

Need help recovering Kodak REELS (RODREELSEU) after wrong firmware – Looking for original firmware or SPI dump​


Hello everyone,

I hope someone can help me.
Unfortunately, before reading the latest posts in this thread, I used the old firmware lookup tool, which identified my scanner as Firmware B.
The firmware flashed successfully, but after reboot the scanner no longer works correctly.

Current symptoms​

  • Kodak logo appears normally.
  • LCD display works perfectly.
  • Power button still works.
  • All other buttons are completely unresponsive.
  • Motors never start.
  • Film transport is completely dead.
  • The scanner cannot be used anymore.
I waited more than 5 minutes after flashing to make sure the update had completed.

I have tested all three Firmware B variants:
  • Original Firmware
  • Original Resolution HBR
  • 1440p HBR
All three produce exactly the same result.

I have NOT tried Firmware A, C or D because I have read about users damaging their displays by flashing the wrong firmware.

Device Information​


Model
Kodak REELS Film Digitizer (RODREELSEU)

Main board
DV280N_MAIN_V0.6

PCB Date:
2021-04-16

Main SoC
Novatek NT96658MBG-NH

SPI Flash
Macronix MX25L3233F (32 Mbit)

Motor Driver Board
DV280N_TMC_Driver_V0.2

Motor Driver IC
Trinamic TMC2226-SA

Camera Board
DV280M_S_A4010_V0.1

PCB Date:
2025-03-07

Additional hardware information:
  • UART header available (3.3V / TX / RX / GND)
  • High-resolution PCB pictures are attached.
Why I think this is a hardware revision issue

While searching the forum, I found another user with an almost identical serial number (A3026148BK01272).

My unit is:

A3026148BK013xx

The serial numbers differ by only 99 units.

From the recent discussion, it appears that the old lookup table is no longer reliable for these newer revisions, and my scanner may actually belong to a newer hardware revision rather than the old Firmware B family.

What I am looking for​

I am NOT looking for Firmware A, B, C or D.
I am looking for one of the following:
  • Original factory firmware for this exact hardware revision
  • Original FWDV280.BIN
  • Original UITRON.BIN
  • Complete SPI flash dump (MX25L3233F)
  • Official recovery procedure
  • Novatek recovery tools
If anyone owns the same hardware revision, or has already dumped the original firmware, I would really appreciate any help.

Thank you very much.

Attached:
  • Main board photos
  • Camera board photos
  • Motor driver board photos
  • Diagnostic report

Attached: High-resolution PCB photos and detailed hardware report (FR/EN).
Have you tried installing the D stock firmware? It cannot hurt anything at this point.
 

FrenchNum

New Tinkerer
Jul 11, 2026
3
0
1
Have you tried installing the D stock firmware? It cannot hurt anything at this point.
Thank you for your suggestion.

I have considered installing the original Type D firmware, but I am honestly a bit hesitant.
I have read several reports from users who ended up with display issues after flashing an incompatible firmware, so I would prefer not to make the situation worse.
My scanner still boots, the LCD works perfectly, and the power button is functional. The only problem is that all other buttons and the motors are completely unresponsive after flashing Firmware B.
Since my hardware appears to be a newer revision (DV280N_MAIN_V0.6, NT96658MBG-NH, camera board dated 2025-03-07), I would like to avoid risking the display or any other hardware if possible.
Have you personally tested the original Type D firmware on this exact hardware revision, or are you suggesting it because my symptoms match a Type D unit?

Thank you for your help.
 

Hook Line and Tinker

New Tinkerer
Mar 17, 2026
20
8
3
Thank you for your suggestion.

I have considered installing the original Type D firmware, but I am honestly a bit hesitant.
I have read several reports from users who ended up with display issues after flashing an incompatible firmware, so I would prefer not to make the situation worse.
My scanner still boots, the LCD works perfectly, and the power button is functional. The only problem is that all other buttons and the motors are completely unresponsive after flashing Firmware B.
Since my hardware appears to be a newer revision (DV280N_MAIN_V0.6, NT96658MBG-NH, camera board dated 2025-03-07), I would like to avoid risking the display or any other hardware if possible.
Have you personally tested the original Type D firmware on this exact hardware revision, or are you suggesting it because my symptoms match a Type D unit?

Thank you for your help.
I think you're wise to be hesitant and it's probably best to wait and see if the firmware guys can weigh in. I'm curious if the reports about display issues were on this site and what the symptoms were. Can you list a few of the posts so I can go back and read them?

It seems as though the consensus here has been that the risk is low if you flash the wrong version because you can always revert.
As you pointed out though, A3026 is still unknown so you may not be able to revert if that is a new variant until someone captures and posts the file.

So if you had an unknown version and you flashed to "D" and it didn't work, you'd be stuck.

But you're stuck now so I think @Eradicator is saying you have little to lose by trying the stock "D" firmware, or the latest "D" drop for that matter.
Stock "D" firmware is in post #143:

I'm far from an expert on this but if I were in your shoes, I'd try the "D" stuff.
 
Last edited:

hobbified

New Tinkerer
Apr 23, 2026
3
2
3
Thank you for your suggestion.

I have considered installing the original Type D firmware, but I am honestly a bit hesitant.
I have read several reports from users who ended up with display issues after flashing an incompatible firmware, so I would prefer not to make the situation worse.
My scanner still boots, the LCD works perfectly, and the power button is functional. The only problem is that all other buttons and the motors are completely unresponsive after flashing Firmware B.
Since my hardware appears to be a newer revision (DV280N_MAIN_V0.6, NT96658MBG-NH, camera board dated 2025-03-07), I would like to avoid risking the display or any other hardware if possible.
Have you personally tested the original Type D firmware on this exact hardware revision, or are you suggesting it because my symptoms match a Type D unit?

Thank you for your help.

That's exactly what you would see if flashing one of the older model firmwares on a D. Barring the remote possibility that they've gone and invented an E (in which case nothing is going to help you right now), flashing D is what you need.
 

FrenchNum

New Tinkerer
Jul 11, 2026
3
0
1
Thank you both.

Before I try the original Type D firmware, could you please clarify one point?
Have you actually seen a Type D flashed with Firmware B showing exactly these symptoms (LCD OK, power button works, all other buttons dead, motors inactive), and then successfully recovered by flashing the original Type D firmware?
If so, I'll give it a try.
I just want to make sure I'm not risking permanent LCD damage if my A3026 turns out to be a newer revision.
 

Hook Line and Tinker

New Tinkerer
Mar 17, 2026
20
8
3
Thank you both.

Before I try the original Type D firmware, could you please clarify one point?
Have you actually seen a Type D flashed with Firmware B showing exactly these symptoms (LCD OK, power button works, all other buttons dead, motors inactive), and then successfully recovered by flashing the original Type D firmware?
If so, I'll give it a try.
I just want to make sure I'm not risking permanent LCD damage if my A3026 turns out to be a newer revision.
I just tried this for you and I see no ill effects.

My unit: H2825
Has been running with post #616 firmware since the version was dropped

For this experiment: Flashed to "B" from post #143
Splash screen for this variant appeared, then went to normal operating screen as expected
No motor actuation and buttons unresponsive
Able to power off with power button although a "long press" was required

Flashed back to post #616
Normal operation restored
Scanned a 50ft reel with success

Keep in mind that your A3026 is still unknown so this might not result in a working unit. Also, I'd still like to read about the experiences of those with the damaged units you're referring to.