NAC/RCC/SMEG Updates Datenbank

edu_chirimoya:

No, that's only about connected services - NAC Wave 2 also have that message.

The 44.07.33.32_NAC-r0 version (UpdateID 001315031692686757) was released in August and is still in AVP state.

Dear... where did that update come from

can't find anything anywhere

greetings from Belgium

brandwacht That firmware is still in testing state, unreleased to public.

{
  "updateType": "ovip-int-firmware-version",
  "updateVersion": "44.07.33.32_NAC-r0",
  "updateProvider": "CONTINENTAL",
  "updateId": "001315031692686757",
  "updateDate": "2023/09/21 10:36:56",
  "updateStatus": {
    "code": "AVP",
    "label": "En attente de validation PSA"
  }
}

Has anyone had any joy uploading the new firmware to implement on Wave 4 Peugeot systems. Want to finally get full screen CarPlay and the updated UI

seanyp99 : It won't happen. In the NAC Wave 4, the area for apps (including Android Auto and CarPlay) it's designed to be 1280x620 in the 1920x720 10" wide HD display. The new UI with the Android Auto and CarPlay in full screen, only in the new infotainment system hardware, IVI.

Zitat von rui.saraiva

brandwacht That firmware is still in testing state, unreleased to public.

Code

{
  "updateType": "ovip-int-firmware-version",
  "updateVersion": "44.07.33.32_NAC-r0",
  "updateProvider": "CONTINENTAL",
  "updateId": "001315031692686757",
  "updateDate": "2023/09/21 10:36:56",
  "updateStatus": {
    "code": "AVP",
    "label": "En attente de validation PSA"
  }
}

Alles anzeigen

uploading to share server

--done--

Link removed

Zitat von j23

Zitat von rui.saraiva

brandwacht That firmware is still in testing state, unreleased to public.

Code

{
  "updateType": "ovip-int-firmware-version",
  "updateVersion": "44.07.33.32_NAC-r0",
  "updateProvider": "CONTINENTAL",
  "updateId": "001315031692686757",
  "updateDate": "2023/09/21 10:36:56",
  "updateStatus": {
    "code": "AVP",
    "label": "En attente de validation PSA"
  }
}

Alles anzeigen

uploading to share server

--done--

Link removed

Alles anzeigen

Sry, because of the legal rights, i had to remove the link.

Such links are not allowed because missing permission from stellantis.

Zitat von Mittns

Zitat von j23

uploading to share server

--done--

Link removed

Alles anzeigen

Sry, because of the legal rights, i had to remove the link.

Such links are not allowed because missing permission from stellantis.

Alles anzeigen

Legal rights? is legal to share smeg Fw on google drive servers:) ? it's more illegal than this as for SMEG Fw you need to pay at dealer

just for curiousity ....

is needed permision to reverse engineer API to get the install pack ? have you got any permission? from Stellantis or to inject seed with Y cable using illegal cracked diagbox?

I could ask you the same.

Do you have permission to upload the firmware?

Reverse engineering is a gray area in certain aspects.

Software that is available to everyone can be reverse engineered, you just can't share source code and so on.

There's still a difference between owning something and uploading something illegally.

And what I do with Diagbox isn't a big deal.

I'm not distributing it or link it somewhere.

I also could know a workshop that let's me play with Diagbox.

Canbus reverse engineering is also not forbidden either (Except for things like mileage manipulation and stuff like that).

But yes, the links for the Smeg firmware could be a problem, I'll have them removed.

Even though PSA has never complained in any way since years in several websites.

Zitat von Mittns

'''

Even though PSA has never complained in any way since years in several websites. ''''

that's what i mean no one care about and private key used to pack is not know so not possible to get(make-hack-rebulid) a custom build FW ..... din't posted genuine link as don't wona have it blocked in the future.....

Zitat von j23

Zitat von Mittns

'''

Even though PSA has never complained in any way since years in several websites. ''''

that's what i mean no one care about and private key used to pack is not know so not possible to get(make-hack-rebulid) a custom build FW ..... din't posted genuine link as don't wona have it blocked in the future.....

Yes, but i always play it safe.

You never know.

For example in Germany, linking to illegally uploaded material can also cause problems, which is why I avoid such links, you know.

Zitat von j23

Zitat von Mittns

'''

Even though PSA has never complained in any way since years in several websites. ''''

that's what i mean no one care about and private key used to pack is not know so not possible to get(make-hack-rebulid) a custom build FW ..... din't posted genuine link as don't wona have it blocked in the future.....

I removed the (recent) "fileName" JSON entry from the getUpdateStatus reply for the same reason, it gives too many clues for the full URL and the generic format for future ones.

I also don't see the point of sharing that beta software. The "final" versions already have enough bugs and it isn't easy to rollback a firmware. That version might also not be the final version anyway, there are many versions in AVP status that were never released (44.06.44.22_NAC-r0, 44.06.42.32_NAC-r0, 44.05.33.42_NAC-r0, 44.04.25.52_NAC-r0 or 44.03.20.32_NAC-r0, just to name a few of the recent ones and there are 3 other versions after the last public release in testing state - this one for instance:

{
  "updateType": "ovip-int-firmware-version",
  "updateVersion": "44.07.30.52_NAC-r0",
  "updateProvider": "CONTINENTAL",
  "updateId": "001315031690989825",
  "updateDate": "2023/08/03 09:40:38",
  "updateStatus": {
    "code": "AVC",
    "label": "En attente de validation fournisseur"
  }
}

It was "released" just a few days before 44.07.33.32_NAC-r0.

Also in the context of those unreleased (to public) versions, many are just partial updates and not full upgrades. For instance this one:

{
  "updateType": "ovip-int-firmware-version",
  "updateVersion": "43.04.27.02_NAC-r0",
  "updateProvider": "CONTINENTAL",
  "updateId": "001315031643204228",
  "updateDate": "2022/02/16 20:22:40",
  "updateStatus": {
    "code": "AVP",
    "label": "En attente de validation PSA"
  }
}

Has only 40.960 bytes, and it's in AVP state. I'll bet that installing this one in the incorrect base version, and you'll have a nasty surprise.

Zitat von edu_chirimoya

Zitat von rui.saraiva

Also in the context of those unreleased (to public) versions, many are just partial updates and not full upgrades. For instance this one:
Code { "updateType": "ovip-int-firmware-version", "updateVersion": "43.04.27.02_NAC-r0", "updateProvider": "CONTINENTAL", "updateId": "001315031643204228", "updateDate": "2022/02/16 20:22:40", "updateStatus": { "code": "AVP", "label": "En attente de validation PSA" } } Weniger anzeigen

Has only 40.960 bytes, and it's in AVP state. I'll bet that installing this one in the incorrect base version, and you'll have a nasty surprise.

Looks like the patches I have seen for AIO versions. I still do not understand why PSA would not just release such patches instead of offering a whole new version each time.

Mostly patches are probably OTA as is small

maybe this

Zitat von edu_chirimoya

Zitat von j23

maybe this

But this is not OTA? The patches I mean were all mean to be installed via USB, just like the regular updates.

not all patches , some can be installed via ota(small in size) , cost saving...