Shiftyy wrote on 2026-05-05, 17:45:

EDIT: Ahh dang, it looks like the RPi that came from Serda's shop doesn't have the WiFi module. Other than installing Linux on my machine, does anyone have ideas for accessing the .img files?

The easiest way (in my opinion) would be to use VirtualBox and get a pre-made linux VHD from OSBoxes, passthrough your SD card reader to the guest machine and then mount the img file as an ext4 folder

It seems WSL2 allows mounting EXT4 in Win11:

https://learn.microsoft.com/en-us/windows/wsl … wsl2-mount-disk

Alternatively you can use any of a gazillion Linux live distros out there to do the job.

appiah4 wrote on 2026-05-06, 06:22:

It seems WSL2 allows mounting EXT4 in Win11:

https://learn.microsoft.com/en-us/windows/wsl … wsl2-mount-disk

Alternatively you can use any of a gazillion Linux live distros out there to do the job.

Seems like it doesn't support USB drives, card readers or mounting from .img files

So I downloaded VirtualBox and tried mounting the .img files.

Apparently these img files are RPi kernel boot files and don't actually contain any files or filesystem.

I am confused because I can't locate the MUNT files or code. Has it been obfuscated into a .bin file or something?

Shiftyy wrote on 2026-05-08, 05:53:

So I downloaded VirtualBox and tried mounting the .img files.

Apparently these img files are RPi kernel boot files and don't actually contain any files or filesystem.

I am confused because I can't locate the MUNT files or code. Has it been obfuscated into a .bin file or something?

Could you just backup on the configs, SoundFonts, and ROMs and just rebuild the card with the latest release of MT32Pi? Even better if you have a spare card you can test with.

SScorpio wrote on 2026-05-08, 16:00:

Shiftyy wrote on 2026-05-08, 05:53:

So I downloaded VirtualBox and tried mounting the .img files.

Apparently these img files are RPi kernel boot files and don't actually contain any files or filesystem.

I am confused because I can't locate the MUNT files or code. Has it been obfuscated into a .bin file or something?

Could you just backup on the configs, SoundFonts, and ROMs and just rebuild the card with the latest release of MT32Pi? Even better if you have a spare card you can test with.

I just want to locate the MUNT files. Recompiling mt-32 does not achieve this.

Shiftyy wrote on 2026-05-09, 13:49:

I just want to locate the MUNT files. Recompiling mt-32 does not achieve this.

It's not recompiling. It's just updating to the latest release which would include the WiFi module and whatever other changes and fixes happened since the version you have.

appiah4 wrote on 2026-05-06, 06:22:

It seems WSL2 allows mounting EXT4 in Win11:

https://learn.microsoft.com/en-us/windows/wsl … wsl2-mount-disk

Alternatively you can use any of a gazillion Linux live distros out there to do the job.

why not just boot a live linux from stick.
You also can boot a virtual machine image under windows and just passthrough the drive to it.

To read only:
https://www.diskinternals.com/linux-reader/

ext2fsd is a Driver for Windows to read ext filesystems, but not sure about development, seems its stopped some years ago.

https://www.ext2fsd.com/

A thought - could you break out a hex-editor on the raw .img and change the existing hash values to the hashes of your edited files directly?

(Assuming compiling hasn’t turned them into something unrecognisable)

ed: Curiosity overtook me, some quick-n-dirty PowerShell to do a recursive search didn't bring anything, except the .ps1 that was doing the search 🙁

1$files = Get-ChildItem -Path "D:\Downloads\mt32-pi-0.13.1" -Recurse
2foreach ($file in $files) {
3	if (Select-String -Quiet -InputObject $file -Pattern "9cd4858014c4e8a9dff96053f784bfaac1092a2e") {
4		Write-Host $file.FullName
5	}
6
7	if (Select-String -Quiet -InputObject $file -Pattern "fe8db469b5bfeb37edb269fd47e3ce6d91014652") {
8		Write-Host $file.FullName
9	}
10
11
12	if (Select-String -Quiet -InputObject $file -Pattern "5a5cb5a77d7d55ee69657c2f870416daed52dea7") {
13		Write-Host $file.FullName
14	}
15
16}
17pause

PS D:\Downloads\mt32-pi-0.13.1> D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\find.ps1
Press Enter to continue...:

edit2:
Memory says the kernel images are compressed (gzip?), so let's see about extracting them and see if it's in there?

jright-click, 7-Zip, Open archive...
run the thing again
GOTCHA!

PS D:\Downloads\mt32-pi-0.13.1> D:\Downloads\mt32-pi-0.13.1\find.ps1 D:\Downloads\mt32-pi-0.13.1\find.ps1 D:\Downloads\mt32-pi-0 […]
Show full quote

PS D:\Downloads\mt32-pi-0.13.1> D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\kernel8-rpi4
D:\Downloads\mt32-pi-0.13.1\kernel8-rpi4
D:\Downloads\mt32-pi-0.13.1\kernel8-rpi4
Press Enter to continue...:
PS D:\Downloads\mt32-pi-0.13.1>

Picking the correct kernel image for your Pi (look in config.txt!), editing it, re-compressing the kernel image and putting the stuff on the SD is left as an exercise for the reader (assuming I don't get bored while making dinner and want to see my front-panel say "butts butts butts") 😀

edit3: got bored, started doing it:
hexed.it is happily opening the decompressed files and finds the bytes, for the kernel8 for a Pi 3/Zero2, I think you're looking between 0x000F0310 and 0x000F0B80.

DJNW wrote on 2026-05-12, 14:45:

A thought - could you break out a hex-editor on the raw .img and change the existing hash values to the hashes of your edited […]
Show full quote

A thought - could you break out a hex-editor on the raw .img and change the existing hash values to the hashes of your edited files directly?

(Assuming compiling hasn’t turned them into something unrecognisable)

ed: Curiosity overtook me, some quick-n-dirty PowerShell to do a recursive search didn't bring anything, except the .ps1 that was doing the search 🙁

Copy code to clipboard

1$files = Get-ChildItem -Path "D:\Downloads\mt32-pi-0.13.1" -Recurse
2foreach ($file in $files) {
3	if (Select-String -Quiet -InputObject $file -Pattern "9cd4858014c4e8a9dff96053f784bfaac1092a2e") {
4		Write-Host $file.FullName
5	}
6
7	if (Select-String -Quiet -InputObject $file -Pattern "fe8db469b5bfeb37edb269fd47e3ce6d91014652") {
8		Write-Host $file.FullName
9	}
10
11
12	if (Select-String -Quiet -InputObject $file -Pattern "5a5cb5a77d7d55ee69657c2f870416daed52dea7") {
13		Write-Host $file.FullName
14	}
15
16}
17pause

PS D:\Downloads\mt32-pi-0.13.1> D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\find.ps1
Press Enter to continue...:

edit2:
Memory says the kernel images are compressed (gzip?), so let's see about extracting them and see if it's in there?

jright-click, 7-Zip, Open archive...
run the thing again
GOTCHA!

PS D:\Downloads\mt32-pi-0.13.1> D:\Downloads\mt32-pi-0.13.1\find.ps1 D:\Downloads\mt32-pi-0.13.1\find.ps1 D:\Downloads\mt32-pi-0 […]
Show full quote

PS D:\Downloads\mt32-pi-0.13.1> D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\find.ps1
D:\Downloads\mt32-pi-0.13.1\kernel8-rpi4
D:\Downloads\mt32-pi-0.13.1\kernel8-rpi4
D:\Downloads\mt32-pi-0.13.1\kernel8-rpi4
Press Enter to continue...:
PS D:\Downloads\mt32-pi-0.13.1>

Picking the correct kernel image for your Pi (look in config.txt!), editing it, re-compressing the kernel image and putting the stuff on the SD is left as an exercise for the reader (assuming I don't get bored while making dinner and want to see my front-panel say "butts butts butts") 😀

edit3: got bored, started doing it:
hexed.it is happily opening the decompressed files and finds the bytes, for the kernel8 for a Pi 3/Zero2, I think you're looking between 0x000F0310 and 0x000F0B80.

Thank-you so much. Yes, extracting the .img file using 7-zip was the key, and I can now locate the SHA-1 hashes we need to replace.

I can confirm that it is working.

A bit of advice for anyone else wanting to do this;

The SHA-1 value that you replace needs to be in lower-case.
The replacement string cannot be longer than the old one, only shorter or the same size.
If your replacement string is shorter than the old string, replace the rest of the characters with "00" in your hex editor.

E.g.

to

Great success!