It's still a cost, though. People are still going to file tickets for warranty replacements, it won't be until the company receives the broken item that they'll detect the firmware replacement (if they even can, what if the hardware damage broke the ability to check?), people return items to the store they bought them from where they can't even check...
It's honestly a whole mess that will absolutely wind up costing the company money in support and returns. You can argue that it's still worth the cost, but just declaring that altering the firmware voids the warranty doesn't stop people from trying, which costs money.
How can they know/figure it out? (They can't/or it's prohibitively expensive/difficult).
>it's very common to find my firmware reverse engineered and available within a month or so of the product being released.
Sure, but it's hidden from 99.99% of your user base
In short - write the manufacturer public key in ROM and a fuse selects if signature check is enforce.
Disclaimer: I didn't come up with this, I'm just summarizing approximately how I understand some Android devices to already work. This also makes me view this system as somewhat battle tested.
That's not a difficult problem, technically. There are a number of ways it can be done. Anything from comparing checksums to eFuses.
> Sure, but it's hidden from 99.99% of your user base
Yes. My point is that avoiding open sourcing firmware because of the risk of piracy or reverse-engineering doesn't make sense because pirates and/or interested engineers will do it directly from the devices anyway.
But they don't need to make it too easy by giving the source on a silver platter.
Sony's answer for Xperia phones used to be that you'd unlock the bootloader with a key you got from them by entering the serial number/IMEI. As part of that, they warn that using custom ROMs that damage the phone - by overclocking, for example - would void the warranty.
It's a reasonable compromise, in my opinion.
I don't think this reasoning makes any sense. The company can just declare that replacing or altering the firmware voids the warranty.
> I would kind of hate handing that over to potential competitors.
But you do that the instant that your product ships. I've shipped a lot of firmware in products, and it's very common to find my firmware reverse engineered and available within a month or so of the product being released.