Help with OSID XDF creation

[SuperGTP01]

Hello all!
So I've used pcm hammer to read my P04 but I've found that my OSID isn't covered in Tiny Tuner nor in UP. Is it possible to get an XDF created or have this added to Tiny Tuner to be able to change the BIN? Thanks for your time!

[zack4200]

it's pretty straightforward to add the OSID into the database for TT/UP, you basically figure out which existing OSID is most similar (that's the part I don't really know how to do, maybe comparing the FlashCRC?), then open the TinyTuner.mdb with Microsoft Access and find the OSIDData table, copy the row with a similar OSID, paste it and change the new row's OSID to yours.

there are a couple of posts in this thread that explain it in a little more detail, DethRattles reached out to Eddie to find out which OSID row to use I think.

viewtopic.php?p=122932#p122932 according to this post, I think the v6CrossRef.mdb that was added to UP may actually make it even simpler?

Either way, upload your bin and I'll see if I can sort it out, otherwise I'm sure one of the devs of UP will come along and get you sorted.

[SuperGTP01]

it's pretty straightforward to add the OSID into the database for TT/UP, you basically figure out which existing OSID is most similar (that's the part I don't really know how to do, maybe comparing the FlashCRC?), then open the TinyTuner.mdb with Microsoft Access and find the OSIDData table, copy the row with a similar OSID, paste it and change the new row's OSID to yours.

there are a couple of posts in this thread that explain it in a little more detail, DethRattles reached out to Eddie to find out which OSID row to use I think.

viewtopic.php?p=122932#p122932 according to this post, I think the v6CrossRef.mdb that was added to UP may actually make it even simpler?

Either way, upload your bin and I'll see if I can sort it out, otherwise I'm sure one of the devs of UP will come along and get you sorted.

Here's my bin

[zack4200]

okay, extract this zip and replace the files of the same names in your UniversalPatcher>DB folder and give it a try.

Adding your OS to the V6CrossRef.mdb alone didn't seem to make a difference, but once I added it to the TinyTuner.mdb all of the tables showed up. So maybe you could replace only the TT mdb. not really sure what's going on there

just to be safe - I'd recommend only flashing changes you made with this if you have a spare pcm or a way to recover if your pcm bricks. I matched up your file's CRC with an existing one from the database so it should be fine, but I can't guarantee anything lol.

[SuperGTP01]

okay, extract this zip and replace the files of the same names in your UniversalPatcher>DB folder and give it a try.

Adding your OS to the V6CrossRef.mdb alone didn't seem to make a difference, but once I added it to the TinyTuner.mdb all of the tables showed up. So maybe you could replace only the TT mdb. not really sure what's going on there

just to be safe - I'd recommend only flashing changes you made with this if you have a spare pcm or a way to recover if your pcm bricks. I matched up your file's CRC with an existing one from the database so it should be fine, but I can't guarantee anything lol.

Done and done. I really appreciate you taking the time to do tthat.Thank you! I'll maybe try flashing with LS Droid to test it until PCM Hammer 2.0 is confirmed for use with little issue.

[V8fan]

my OSID isn't covered

Just check all OSid supported for ur hardware and choose most covered
I reflashed entire PCM for change OS to achieve full access