[Q] I9100 Getprop mismatch while updating radio/baseband - Galaxy S II Q&A, Help & Troubleshooting

Afternoon all,
I have an aging ex-Orange Galaxy S2, now running Omnirom nightlies and still going strong. However, I've been experiencing really choppy audio quality on two different brands of in-car bluetooth handsfree for almost a year now, so I got looking at baseband versions.
Currently on XXMS2, I tried to update to XXMS3 and XXMS4, but it always failed on getprop assert fails. I've narrowed it down to this.
The phone is reporting...
Code:
~ # getprop | grep ro.product.device
[ro.product.device]: [i9100]
~ # getprop | grep ro.build.product
[ro.build.product]: [i9100]
~ # getprop | grep ro.product.board
[ro.product.board]: [smdk4210]
And the XXMS3 and XXMS4 flashing scripts are checking for...
Code:
assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || getprop("ro.product.board") == "galaxys2" ||
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.board") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" || getprop("ro.product.board") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T" || getprop("ro.product.board") == "GT-I9100T" ||
getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" || getprop("ro.product.board") == "GT-I9100P");
Clearly nothing in that list will match. I have an XXMS2 firmware file, and it doesn't perform these checks. I don't know why my phone would have a slightly out of the ordinary set of properties, other than the fact it's had a few warranty repairs by Samsung.
Thus, is it safe to edit updater-script and remove those checks in order to let it pass the test?
Any advice or scary warnings would be greatly appreciated!
Cheers
Kyle

---

Changing modem isn't going to fix your BT problems, BT drivers are in the kernel (with WiFi drivers).

---

That's a bit disappointing to hear then The problem has been apparent since the CM10 days, and persisted into Omnirom. Only affects HFP too. A2DP is fine. Will keep wishing then.

---

Does it happen with stock ? If it doesn't, might be worth mentioning to the developer of the custom rom(s) you're using/have tried.
Could easily be an AOSP specific issue; due to a lot of proprietary code, lots of things only work on their roms due to the skill of the coders involved - being able to 'hack' solutions/reverse engineer stuff. And that proprietary code is also the reason why some stuff doesn't work/has problems with AOSP.