Instructions to How to replace the target binary in Slimbook EC flasher

[aminevsaziz]

First of all thanks @minortex for the efforts that put into such problem with Wujie 14XA charging issue.
After following @w568w gist and comments carefully I stumbled on your comment in about [flash the 1MB chip via a SPI programmer or replace the target binary in the Slimbook EC flasher](url).
However, checking the repo there's no clear instructions on how to replace the target binary of the Slimbook EC flasher? With simple instructions we could be able to flash the modified firmware instead the original EC that comes with Slimbook.

[minortex]

It's really simple! Look at this:

❯ tree
.
├── BIOS
│   ├── CHANGELOG_BIOS.txt
│   ├── F.nsh
│   ├── GXxHXxxN114GOS07_CAP.efi
│   └── GXxHXxxN114GOS07.ROM
├── EC
│   ├── CHANGELOG_EC.txt
│   ├── F.nsh
│   ├── GXxHXxx_21.200 <- replace this!
│   └── ifux64.efi
├── EFI
│   ├── boot
│   │   └── bootX64.efi
│   ├── Insyde
│   └── UpdateCapsule
└── readme.txt

7 directories, 10 files

Just replace the GXxHXxx_21.200 with the modded firmware with my patch script, then copy the whole folder to a USB drive with FAT32 filesystem, boot from the USB then cd into EC folder, execute F.nsh, the flashing procedure will start.

---

You can also try the ec-flash program on some Linux distros (like ArchLinux), but remember when flashing starts, your keyboard will be locked, and the system will be shut down forcefully after about 3 minutes. A reset must be performed to take effect so I make a hook for systemd-shutdown.

---

Both methods only need 256KiB EC firmware, while using CH341 needs 1MiB firmware with padding.

However, I must caution you that flashing the EC is a high-risk operation, keep in mind that you should have a fallback plan in case the laptop gets bricked.

[aminevsaziz]

Thanks for the detailed explanation. I will follow the instructions and let you know what happen 🤞 (I hope the firmware flashing process succeed like yours). Btw, why use the Slimbook BIOSN.1.14GOS07 EC2.12 instead of the last one EC2.16?

As for the risky part, The battery is dieing slowly and lose capacity super fast because of bad firmware in the first place. IMO, Mech upgraded the bios to 50 yet the same issue persist for over 2 years and I will be remain the same.

[minortex]

When I started reversing the firmware, the latest version was 2.12 and 2.16 hadn't been released yet. Due to the compiler optimization, the assembly structure varies significantly, so I stuck with 2.12.

AFAIK, version 2.16 didn't resolve this problem, the only thing they did is removing the charge limit option in the BIOS, which makes no sense to us.

[aminevsaziz]

I start working on the patched firmware, but I stumble into:

1. Which of patches to apply first?
2. If multiple *.py script to apply in in secession, then which order?