[spyderboyant]

All good then. I have VCP but didn't think it had GEM activation? Haven't looked at the scripts for a while..

There is no script in VCP for GEM activation. For 5F, you need to change the diagnostic session in engineering mode rather than standard mode, and then activate the GEM with adaptation chan.45 ID9279 Developer menu

That’s it.

ta. I originally activated via ODBEleven dongle... however it is a real pain for reliability.

[sottopiombo]

ta. I originally activated via ODBEleven dongle... however it is a real pain for reliability.

Ok, another update...
GEM activated, user defined SWDL activated, exited from GEM (no reboot) red update menu, update selected, but still “train is blocked” error message.

Is there something missing or wrong in my procedure???

Attached some GEM menu photos.

[spyderboyant]

ta. I originally activated via ODBEleven dongle... however it is a real pain for reliability.

Ok, another update...
GEM activated, user defined SWDL activated, exited from GEM (no reboot) red update menu, update selected, but still “train is blocked” error message.

Is there something missing or wrong in my procedure???

Attached some GEM menu photos.

Hey mate,

Upgrade should work and what you have done is what I did. Unfortunately I cannot see your pictures. What version are you upgrading from? My issue was there was a TPI to upgrade my MIB2 from 00358 "P" (MHI2_ER_AUG22_P2133) image factory to 0358 "K" (MHI2_ER_AUG22_K2140_1) update image but my unit was missing from the supportedTrains section of the metainfo2.txt file on the update media. What I got in the RED engineering menu was:

"A variant conflict has occured!"
Main Unit version: MHI2_ER_AUG22_P2133
Release metainfo version: Train is blocked

The reason for this was the train into in the update CD had missed my unit version: 4M0 906 961 B

SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_K2140*"

What might be happening is that the SWDL only ignores the last characters that are relevant to the actual train and not the first ones which relate to the hardware.

ie Unit must be MHI2_ER_AUG22 but ignore the rest...

[sottopiombo]

Hey mate,

Upgrade should work and what you have done is what I did. Unfortunately I cannot see your pictures. What version are you upgrading from? My issue was there was a TPI to upgrade my MIB2 from 00358 "P" (MHI2_ER_AUG22_P2133) image factory to 0358 "K" (MHI2_ER_AUG22_K2140_1) update image but my unit was missing from the supportedTrains section of the metainfo2.txt file on the update media. What I got in the RED engineering menu was:

"A variant conflict has occured!"
Main Unit version: MHI2_ER_AUG22_P2133
Release metainfo version: Train is blocked

The reason for this was the train into in the update CD had missed my unit version: 4M0 906 961 B

SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_K2140*"

What might be happening is that the SWDL only ignores the last characters that are relevant to the actual train and not the first ones which relate to the hardware.

ie Unit must be MHI2_ER_AUG22 but ignore the rest...

Ok mate,

the original version of my MIB2 is MHI2_ER_AUG22_P3241 (SW 0678) (attached photo)
   

The strange thing is that in metainfo2.txt of 4M0906961AF (SW0976) the release info is release = "MHI2_ER_AUG22_K2156" MUVersion = "0976"

and the related trains are:
SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_P2133*,MHI2_ER_AUG22_K2140*,MHI2_ER_AUG22_P2148*,MHI2_ER_AUG22_K2150*,MHI2_ER_AUG22_K2152*,MHI2_ER_AUG22_K2154*,MHI2_ER_AUG22_K2155*,MHI2_ER_AUG22_K2156*"

As you can see, my train number is higher than the related trains for the update, so I don't know how to verify if there are others update releases.

Are my thoughts right?

Mark

[spyderboyant]

Hey mate,

Upgrade should work and what you have done is what I did. Unfortunately I cannot see your pictures. What version are you upgrading from? My issue was there was a TPI to upgrade my MIB2 from 00358 "P" (MHI2_ER_AUG22_P2133) image factory to 0358 "K" (MHI2_ER_AUG22_K2140_1) update image but my unit was missing from the supportedTrains section of the metainfo2.txt file on the update media. What I got in the RED engineering menu was:

"A variant conflict has occured!"
Main Unit version: MHI2_ER_AUG22_P2133
Release metainfo version: Train is blocked

The reason for this was the train into in the update CD had missed my unit version: 4M0 906 961 B

SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_K2140*"

What might be happening is that the SWDL only ignores the last characters that are relevant to the actual train and not the first ones which relate to the hardware.

ie Unit must be MHI2_ER_AUG22 but ignore the rest...

Ok mate,

the original version of my MIB2 is MHI2_ER_AUG22_P3241 (SW 0678) (attached photo)


The strange thing is that in metainfo2.txt of 4M0906961AF (SW0976) the release info is release = "MHI2_ER_AUG22_K2156" MUVersion = "0976"

and the related trains are:
SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_P2133*,MHI2_ER_AUG22_K2140*,MHI2_ER_AUG22_P2148*,MHI2_ER_AUG22_K2150*,MHI2_ER_AUG22_K2152*,MHI2_ER_AUG22_K2154*,MHI2_ER_AUG22_K2155*,MHI2_ER_AUG22_K2156*"

As you can see, my train number is higher than the related trains for the update, so I don't know how to verify if there are others update releases.

Are my thoughts right?

Mark

Hey Mark,

It should upgrade and ignore your current version. I updated to 976 from 358 using the SWDL method.

---

[quote='spyderboyant' pid='364250' dateline='1534541000']

Hey mate,

Upgrade should work and what you have done is what I did. Unfortunately I cannot see your pictures. What version are you upgrading from? My issue was there was a TPI to upgrade my MIB2 from 00358 "P" (MHI2_ER_AUG22_P2133) image factory to 0358 "K" (MHI2_ER_AUG22_K2140_1) update image but my unit was missing from the supportedTrains section of the metainfo2.txt file on the update media. What I got in the RED engineering menu was:

"A variant conflict has occured!"
Main Unit version: MHI2_ER_AUG22_P2133
Release metainfo version: Train is blocked

The reason for this was the train into in the update CD had missed my unit version: 4M0 906 961 B

SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_K2140*"

What might be happening is that the SWDL only ignores the last characters that are relevant to the actual train and not the first ones which relate to the hardware.

ie Unit must be MHI2_ER_AUG22 but ignore the rest...

Ok mate,

the original version of my MIB2 is MHI2_ER_AUG22_P3241 (SW 0678) (attached photo)


The strange thing is that in metainfo2.txt of 4M0906961AF (SW0976) the release info is release = "MHI2_ER_AUG22_K2156" MUVersion = "0976"

and the related trains are:
SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_P2133*,MHI2_ER_AUG22_K2140*,MHI2_ER_AUG22_P2148*,MHI2_ER_AUG22_K2150*,MHI2_ER_AUG22_K2152*,MHI2_ER_AUG22_K2154*,MHI2_ER_AUG22_K2155*,MHI2_ER_AUG22_K2156*"

As you can see, my train number is higher than the related trains for the update, so I don't know how to verify if there are others update releases.

Are my thoughts right?


Hey Mark,

It should upgrade and ignore your current version. I updated to 976 from 358 using the SWDL method as did a mate. Maybe use the "B" SD card to go back to then go forward? What version is your GEM? You are doing what I did so I find it strange especially considering I can confirm the firmware matches your hardware.

Also, FYI, 976 is the last update for our hardware as the newer MIB2s (last 18 months) are no longer Nvidia chipset but Qualcomm. You will note that their hardware ID is MHI2Q_ER_AUG22..

Maybe 678P"roduction" was seen as bug free but the earlier versions not? I still think SWDL should allow that update as its supposed to "ignore" train.

The history of firmware updates for our MIB2s are:

333P
358P
358K (SD card update - "B")
442P
678P
917P - But Qualcomm MIB2
968K (SD card update - "AF")

---

[quote='spyderboyant' pid='364250' dateline='1534541000']

Hey mate,

Upgrade should work and what you have done is what I did. Unfortunately I cannot see your pictures. What version are you upgrading from? My issue was there was a TPI to upgrade my MIB2 from 00358 "P" (MHI2_ER_AUG22_P2133) image factory to 0358 "K" (MHI2_ER_AUG22_K2140_1) update image but my unit was missing from the supportedTrains section of the metainfo2.txt file on the update media. What I got in the RED engineering menu was:

"A variant conflict has occured!"
Main Unit version: MHI2_ER_AUG22_P2133
Release metainfo version: Train is blocked

The reason for this was the train into in the update CD had missed my unit version: 4M0 906 961 B

SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_K2140*"

What might be happening is that the SWDL only ignores the last characters that are relevant to the actual train and not the first ones which relate to the hardware.

ie Unit must be MHI2_ER_AUG22 but ignore the rest...

Ok mate,

the original version of my MIB2 is MHI2_ER_AUG22_P3241 (SW 0678) (attached photo)


The strange thing is that in metainfo2.txt of 4M0906961AF (SW0976) the release info is release = "MHI2_ER_AUG22_K2156" MUVersion = "0976"

and the related trains are:
SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_P2133*,MHI2_ER_AUG22_K2140*,MHI2_ER_AUG22_P2148*,MHI2_ER_AUG22_K2150*,MHI2_ER_AUG22_K2152*,MHI2_ER_AUG22_K2154*,MHI2_ER_AUG22_K2155*,MHI2_ER_AUG22_K2156*"

As you can see, my train number is higher than the related trains for the update, so I don't know how to verify if there are others update releases.

Are my thoughts right?

Mark

I note your GEM is 4.5s. Mine is GEM 3.6. Might have to do with this I reckon as GEM obviously controls the behaviour of SWDL and it ain't working for you... So it seems GEM isn't touched by the firmware update..

---

Hey mate,

Upgrade should work and what you have done is what I did. Unfortunately I cannot see your pictures. What version are you upgrading from? My issue was there was a TPI to upgrade my MIB2 from 00358 "P" (MHI2_ER_AUG22_P2133) image factory to 0358 "K" (MHI2_ER_AUG22_K2140_1) update image but my unit was missing from the supportedTrains section of the metainfo2.txt file on the update media. What I got in the RED engineering menu was:

"A variant conflict has occured!"
Main Unit version: MHI2_ER_AUG22_P2133
Release metainfo version: Train is blocked

The reason for this was the train into in the update CD had missed my unit version: 4M0 906 961 B

SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_K2140*"

What might be happening is that the SWDL only ignores the last characters that are relevant to the actual train and not the first ones which relate to the hardware.

ie Unit must be MHI2_ER_AUG22 but ignore the rest...

Ok mate,

the original version of my MIB2 is MHI2_ER_AUG22_P3241 (SW 0678) (attached photo)


The strange thing is that in metainfo2.txt of 4M0906961AF (SW0976) the release info is release = "MHI2_ER_AUG22_K2156" MUVersion = "0976"

and the related trains are:
SupportedTrains = "MHI2_ER_AUG22_P1056*,MHI2_ER_AUG22_P1064*,MHI2_ER_AUG22_P2116*,MHI2_ER_AUG22_P2133*,MHI2_ER_AUG22_K2140*,MHI2_ER_AUG22_P2148*,MHI2_ER_AUG22_K2150*,MHI2_ER_AUG22_K2152*,MHI2_ER_AUG22_K2154*,MHI2_ER_AUG22_K2155*,MHI2_ER_AUG22_K2156*"

As you can see, my train number is higher than the related trains for the update, so I don't know how to verify if there are others update releases.

Are my thoughts right?

Mark

Hi Mark,

I note your version of GEM is 4.5s while mine is 3.6 and I upgraded from 358 to 976. A mate also did this as well. Obviously GEM is firmware that isn't upgradable and this might be what is stopping you from upgrading... I definitely think it must be this...

Only other option would be root access to MIB and FTP files across (not pretty)

[sottopiombo]

Hi Mark,

I note your version of GEM is 4.5s while mine is 3.6 and I upgraded from 358 to 976. A mate also did this as well. Obviously GEM is firmware that isn't upgradable and this might be what is stopping you from upgrading... I definitely think it must be this...

Only other option would be root access to MIB and FTP files across (not pretty)

Mate, probably GEM 4.5s has locked some functions... I've readed that on Q7 it is possible to set the user defined SWDL with train check skipping, the same is not possible on A4 B9, although they share the same platform. Anyway, have you got any info on checksum calculation? (if needed, reply in PM)

Thanks.

Mark

[Navigationmaster]

Why u wana downgrade higher ver of fw to lower 2156?

[sottopiombo]

Why u wana downgrade higher ver of fw to lower 2156?

The original SW (0678) has P3241 train, the new version (0976) has K2156 train.

It's strange, but it isn't a downgrade. Have you got a more recent version?

Mark

[Navigationmaster]

Oh right well there is nothing newer that 2156 but i think soon will be realsed K4xxx for a4 a5 q5 q7

[sottopiombo]

Oh right well there is nothing newer that 2156 but i think soon will be realsed K4xxx for a4 a5 q5 q7

Hope so, mate.... as soon as the P/N of the K4xXx update will appear, I will order the SD card from AUDI..