Announcement

Collapse
No announcement yet.

Hacked XP ORX firmware

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Hacked XP ORX firmware

    Do you think that’s realistic ?


  • #2
    It was tempty for me to attempt the teardown of so called ORX Firmware Studio (version string V141126, build r3), packaged as a self-contained Windows GUI app.
    Out of caution I didn’t run it — instead I pulled it apart to see exactly what it does before deciding whether it’s safe to use.
    Sharing the findings here in case it’s useful to others who are braver than me and want to try it on real device (lol).
    1. Packaging
    The executable is a PyInstaller bundle (Python 3 "comma" 8 Unpacking it with a standard PyInstaller extractor reveals a normal Tkinter GUI application plus a handful of custom modules, and a data file called firmware.orxpack.
    2. The GUI itself
    The main script builds a fairly polished installer window (Russian-language UI, with an EN/RU toggle) that walks the operator through:
    - charging the device fully,
    - putting it into an “UPDATE” mode on-screen,
    - connecting it over USB,
    - confirming a battery/risk acknowledgment,
    - then choosing between writing a “modified” firmware image or restoring the original factory image.
    It includes real safety engineering: device identity checks (it explicitly verifies the chip is a PIC24FJ1024GB606, including accepted silicon revisions), checksum verification at every stage, read-back comparison after writing, and an encrypted local backup of whatever firmware was on the device before any changes — so it’s not a sloppy or careless tool, whoever built it clearly understood the hardware.
    3. The firmware payload
    firmware.orxpack turned out to be a JSON container holding an AES-GCM encrypted blob.
    The decryption key is hard-coded in one of the bundled modules (so it’s “protection” only in the sense of obscuring the payload from casual inspection, not real security).
    Once decrypted, the payload is a zlib-compressed JSON structure containing 19 separate firmware images — the current factory original, a “modified” image, and a long chain of intermediate development builds dated from roughly June through November, suggesting this was refined over several months rather than thrown together in one sitting.
    4. What the modification actually changes
    Comparing the “original” and “modified” images byte-for-byte: the differences are confined entirely to the application code region of the firmware (the bootloader and protected/calibration areas are untouched).
    A leftover debug path string inside the installer’s helper code references something like an “ORX-silencer-prototype / ORX-silencer-menu-candidate” build — which points fairly clearly at the purpose: an unofficial addition of some kind of silent/muted operating mode that isn’t present in the stock firmware.
    5. What it is not
    No destructive behavior was found — no data wiping, no code that touches anything outside the device’s own application memory, and no network/exfiltration logic.
    It talks to the device over USB HID only.
    In other words, this looks like an unofficial, privately developed firmware modification tool built by someone with real familiarity with the device’s internals — not a piece of malware aimed at the host PC.
    Posting this mainly so others who encounter the same file know what they’re actually looking at before deciding whether to run it.
    Here is the bins extracted from it.


    ​P.S.
    Namely, I am waiting for the first "candidate" who will bring ORX to be "bricked" at my place!
    I bought an XP Deus 1 back in 2012.
    Already after a couple of months I did a similar "teardown" but I never dared to write it on the detector.
    I'm not that rich, and both Serbia and France are friendly countries,
    I don't want to end up behind bars...


    Attached Files

    Comment


    • #3
      Just in case, I checked the datasheet.
      Yes, "bin" files meet at least this trivial criterion:

      PIC24FJ1024GB606:
      - Flash memory: 1 MB (1,048,576 bytes)
      - RAM: 32 KB
      - EEPROM: does not have a separate EEPROM memory.
      The maximum .bin file for the entire Flash memory is approximately 1 MB.
      The actual size depends on the program.
      ​
      ...
      P.S.
      Quick note on the .bin file size
      For anyone wondering why the firmware image is 1,409,024 bytes instead of exactly 1 MB (1,048,576 bytes) for a PIC24FJ1024GB606 chip: that’s normal, not an error.
      PIC24 instructions are 24-bit (3 bytes), but these binary images store each instruction as 4 bytes — the 3 real bytes plus one always-empty “padding” byte.
      I checked: every single one of those padding bytes across the whole file is zero, confirming this packing.
      Strip out the padding and you get ~1,056,768 bytes of real content — basically 1 MB, plus a small ~8 KB extra for config/ID data and a flash page likely used to emulate EEPROM (this chip has no dedicated EEPROM).
      So the file size lines up fine with the chip’s specs once you account for that standard packing format.
      ​

      Comment


      • #4
        I hope the forum administrators won't make a problem because of this, because I didn't give the original "hack" package anywhere here, but only an analysis of something from an external link.
        Nor do the XP folks have any arguments to complain about.
        This is just an academic analysis, nothing more.

        ​

        Comment


        • #5
          So... I am waiting for the first "candidate" who will bring ORX to be "bricked" at my place!

          Comment


          • #6
            It's interesting how someone figured it out, but if it really works, I think it's largely the work of AI.

            Comment


            • #7
              99%

              Comment


              • #8
                Truth be told, the update file for XP Deus 1 could be unzipped with 7-Zip and you could extract the bin file without any problems.
                But the problems only start with decompilation.
                I know from past experience that there is no such thing as an ideal decompiler.
                But programming experience and many nights spent in trial&error methods can reveal some locations in the bin/hex file.
                That's how I got rid of the famous "300" limit on the FelezJoo Pi.
                Of course, today things become much easier with the help of AI.


                ​

                Comment


                • #9
                  I could perhaps understand someone managing to extract the firmware from an XP Deus control unit, but figuring out the communication protocol between the X35 coil and the control unit which communicate wirelessly using an nRF24L01 is, in my opinion, not nearly as simple.

                  Comment


                  • #10
                    Alain Loubet, until he got rich and became very overbearing; on one occasion he unknowingly gave me a clue in an email about how the BT protocol was written.
                    It could be reverse engineered... but you need a strong motivation for that, I don't have it.
                    What is the benefit of that?
                    To work for the people?
                    That grateful "master, bro, teacher" characters pat me on the back as a sign of gratitude?
                    That I have "forum fame" that is of no use?
                    It won't put bread on the table for my family.
                    Who cares about that "secret" BT protocol of theirs?
                    Anyway, AI will soon solve all that by itself.

                    ​
                    ​

                    Comment


                    • #11
                      For example, the XP Deus 1 update file: "DEUS_UPDATE_V4.1_English_Setup.exe"
                      When unpacked, you can see this:


                      Click image for larger version

Name:	image.png
Views:	91
Size:	43.9 KB
ID:	454611​

                      ​

                      Comment


                      • #12
                        Essentially, the .bin file itself that is written to the processor is this:
                        Attached Files

                        Comment


                        • #13
                          Yes, I looked into that too, and I have the update files at home. I also recently managed to get the binary files for updating the XP Deus 2.

                          Comment


                          • #14
                            Now you need to analyze that .bin file, find locations, strings, procedures, edit the whole .bin file as desired, fix the checksum and return it back to the packed .exe... et ... voila!
                            ​

                            Comment


                            • #15
                              This should be an update file for the XP Deus 2 unit, for the STM32 processor.
                              Attached Files

                              Comment

                              Working...
                              X