That command only updates ME firmware. Not the BIOS. That is done by the firmwarehdr.cap in the same line as the 2 ReTimer capsules. And the only reason the ME updater would refuse, but run with the -allowsv flag is, because the ME firmware was already updated on a previous run. You’d have better removed that line or commented it out (‘#’). Although I would have thought it would just show you its message of not doing the update (“because up-to-date”) and continue on with the rest.
But you are right, the header information for both capsules actually even states “Framework ADL Retimer01 (Left)” and targets the GUID of the left ReTimer. Fascinating that CapsuleApp would not even warn of trying to target the same GUID twice.
@Kieran_Levin @nrp I am aware you called this “alpha” state, but at this point it is proven, that nobody could have successfully run this update on even a single test machine. And that is what you choose to publish for your customers? That is WAAAY beyond experimental and just plain incompetent.
This deserves an IMMEDIATE and PUBLIC post mortem of the chain of things that Framework did wrong to end up at this point. Otherwise, Framework can absolutely not be trusted to ever deliver on anything firmware related. Are those these process changes that enable you to release firmware updates faster that you promised? Just skipping any semblance of quality control? And not even monitoring the thread where you asked for feedback for your broken installer? Is this the quality work that is delivered by that new team you contracted?
It has been 2 weeks. Everybody that tried the new EFI installer and did not have already updated ReTimers ended up with a half-bricked board. And you did not the slightest bit of troubleshooting after failure reports, that would have clearly told you that the update is inherently broken (apart from the other issues with the script) and needs to be pulled, fixed or for once get updated “KNOWN ISSUES”.
Are you actually just testing all 12th gen updates on boards that are already on 3.06 version and already have the ReTimer updates? And that is how you end up believing that the ReTimer updates work even though you have never actually tested it?
Need I remind you that you claimed for the 3.08 Windows installer, that issues with updating both ReTimers from Windows are fixed (point 6 of your change notes), even though that has clearly not been the case? I have been reporting that issue before and after you released 3.08. And you have still never updated the Known Issues for that installer. I had hoped that maybe it was just very rare and it was my bad luck that I hit that issue on a sample size of 1 (in exactly the same way as I hit it when updating another board to 3.06 beta back when that released). But by the looks of how you cannot possibly have tested the new EFI updater (or the previous EFI updater for that matter), I am starting to believe you are just not testing it all.
And in light of Frameworks problems communicating openly on this issue, it seems that your customers have to assume the worst case for every possible situation until such a time as Framework chooses to actually begin admitting mistakes and actually explaining how things are being changed, so that those mistakes will not be repeated.