I'm not seeing those on my "original" keg drive...
How do I go looking for them?
I can email these files to someone if they can host them somewhere for downloading. They're very small.
You will likely first need to replace your current rc.sh and rc.sig files with a matched pair
Where did you get these files? I presume they're "support editions" provided by Phatnoise for remote diagnostics...?
Does that help us? Maybe not.
Just been exploring the firmware on sixpak,
http://phatbox.sixpak.org/firmware/
and noticed the old versions available there go right back to 2001.
That made me wonder if any of the early firmware versions didn't use the signing (.sig) files.
Sure enough there is a BMW version firmware without signing... ;D
http://phatbox.sixpak.org/firmware/?BMW=1.00
Download all 4 zips for BMW v1.00 and take a look.
Does that help us? Maybe not. I don't know if we can use any of that to reprogram one part of a Keg/PB so that we can avoid the DMS checking.
Also notice that the RoyalLin.ux and Linux files are much smaller.
You know, I wonder if you try using that BMW firmware and a set of the head unit files from another firmware thats more recent just not putting the sig files in place if the box will boot up.
"RoyalLin.ux" is smaller with the BMW v1 firmware and there isn't a separate "Linux" file. It is also never signed (not even now).
USAGE: phat [option] where options are: help shows this screen testmode sends a FDh to the 51, putting it into self test update forces the reloading of BOOT and FIRMWARE into the 51 blank 'blanks' the 51, returning to factory state update_noenc same as update w/o decryption (faster!)
I noticed that, it isnt signed. "RoyalLin.ux" is the same size as the "Linux" file so im wondering if it was just a renaming job and those files are just there to be backward compatible.
What about "phat" (not the daemon)?
I havn't read anything about it here yet... "51" obviously means PB or DMS but it could also be the "startprog" ::) I'd like to know more about "testmode" and "update". As the latter uses some decryption there's possibly some private key in there. Furthermore it seems to be an unsigned file to be played with 8)
Just in case, Para
(Oops, just saw Firefox mentioned it already)
"RoyalLin.ux" is the same size as the "Linux" file so im wondering if it was just a renaming job and those files are just there to be backward compatible.