Actually, “The active FMCF sends its flightplan data to the inactive FMCF for these conditions:
- Long term power ups
- BITE induced restart
- Flight plan entries and performance data changes.
When the active FMCF fails, a resynchronization (resync) occurs. Resyncs take about 1 second for an entire flight plan update. The active FMCF always resyncs the inactive FMCF. The active FMCF selection is a function of the FMC selector position and FMF partition health.” 777 Training Manual 34-61-00 p106
If the link between both FMCFs in the respective Left and Right AIMS Cabinet is severed, and the active Left FMCF has failed, a resync is not possible. An auto fail switch is not possible.
A software reset is a function of BITE/fault monitoring. If a software reset should occur, the active route becomes inactive, the performance data is erased, and LNAV and VNAV (if engaged) modes fail. At this time, the crew cannot be using LNAV because it has failed eg diverting to Penang in a chaotic cockpit. The Flight ID has been erased. To regain FMC operation, manually selecting the FMC selector to the right, will make the right FMCF as the active. The crew need to activate and execute the flight plan, enter the necessary performance data, and engage LNAV and VNAV. Now LNAV is available eg tracking west from Penang.
When the SATCOM logged on at 1825:27, the Flight ID was missing.
You've made two assumptions: First, that an auto failover is not possible; and second, that a software reset will occur. The manual does not state either of those things. You also conveniently ignored the first part of that paragraph you quoted from the manual:
FMC synchronization monitoring occurs at power-up and during normal operation. The active FMCF sends flight plan data to the inactive FMCF. This occurs so the inactive FMCF can take over if the active FMCF fails.
As I said previously (and as described in the manual), during normal operation the active FMC synchronises the inactive FMC any time there is a change to the flight plan or performance data. If a resync did not occur in your scenario, the inactive FMC is already synchronised with the active FMC that has failed.
Now, how about answering the questions you were asked, which you have not answered?