TunerPro INA0S VIN_original.bin query

General.Massacre

Corporal
May 14, 2018
219
57
0
Ride
2009 E92 335i DCT
Hi guys,
So i have been playing with Tuner Pro, and have noticed something on the stock INA0S Bin files (VIN_original.bin)
If i load up the stock bin from my friends car (2009 Z4 35i INA0S), and also a 335is bin that was provided on a thread i saw, then load up the INA0S .xdf from the Github repository, i get the below strange mapping, this leads me to think that the bin is not an INA0S ROM.

StockINA0S.png


However, if i load the INA0S BEF files from N54 Tech, they are fine, and done have an issue.
Has anyone else come across this,

Thanks in advance.
 

RSL

Lieutenant
Aug 11, 2017
937
501
0
It's not INA0S, layouts are family-specific. Try opening it in the other XDFs and see if any look correct. There are unmapped rom families too, could always be one there is no xdf for.
 

General.Massacre

Corporal
May 14, 2018
219
57
0
Ride
2009 E92 335i DCT
It's not INA0S, layouts are family-specific. Try opening it in the other XDFs and see if any look correct. There are unmapped rom families too, could always be one there is no xdf for.
Thanks bud. Yes i already checked the other XDFs to make sure. And the others are way off.

Would there perhaps be a INA0S_IS xdf. Or would that still fall under the INA0S xdf?
Coz surely the 335is would be the INA0S/INA0S_IS rom?
 

RSL

Lieutenant
Aug 11, 2017
937
501
0
Thanks bud. Yes i already checked the other XDFs to make sure. And the others are way off.

Would there perhaps be a INA0S_IS xdf. Or would that still fall under the INA0S xdf?
Coz surely the 335is would be the INA0S/INA0S_IS rom?
INA0S and INA0S_IS are the same layout. It's probably IKC0S, ILA0S or another with no xdf defined.
 

carabuser

Lieutenant
Oct 2, 2019
870
1
766
0
UK
Ride
Z4 35i & 335i
2009 35i probably came with IGD0S from the factory. They also updated a lot of them to IMC0S around 2013. Both have very different layouts.

You can find the ROM family name by opening it up in a hex editor and looking at 0x40000.

I have a partial XDF for IMC0S but if you want to tune the car then it would be best to update it to INA0S anyway.
 
  • Like
Reactions: RSL

General.Massacre

Corporal
May 14, 2018
219
57
0
Ride
2009 E92 335i DCT
Thanks you for that information.Took me a while to figure out and find 0x40000
But seems the correct ROM is IKC0S. am i right?
1580969019521.png


If so, does anyone have an IKC0S xdf.

also, it seems my friends Z4 35i is on the INA0S as when flashing MHD, it says "HW: INA0S".
Thanks in advance.
 

RSL

Lieutenant
Aug 11, 2017
937
501
0
Yes, it's IKC0S. I have an XDF for it somewhere, but it's very thin compared to supported XDFs that continue to be updated and I think Shiv defined what is there in it, so I don't have much confidence in it lol

IKC0S isn't supported on MHD, so when it installs, it updates to INA0S. The original backup prior to install would be IKC0S and it would be INA0S after install.
 

General.Massacre

Corporal
May 14, 2018
219
57
0
Ride
2009 E92 335i DCT
Yes, it's IKC0S. I have an XDF for it somewhere, but it's very thin compared to supported XDFs that continue to be updated and I think Shiv defined what is there in it, so I don't have much confidence in it lol

IKC0S isn't supported on MHD, so when it installs, it updates to INA0S. The original backup prior to install would be IKC0S and it would be INA0S after install.
Thats ok thanks man. wont really need it, was just wondering why the parameters were different.
but it makes sense now.
my friend flashed back to stock Via MHD letting mHD write the stock file, so it will be a proper file now.
 

RSL

Lieutenant
Aug 11, 2017
937
501
0
Ideally it is an INA0S now.

If he left the IKC0S backup in the folder as VIN_original.bin, it would write that back. If he moved it out or changed the name and no VIN_original.bin file was in the folder, it would've built/written a stock INA0S instead.