You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I recently owned an A4 B9 with the MHI2Q_ER_AUG22_P5092 system.
I unlocked with M.I.B. activated lifetime map license and installed the new 2024 maps. Everything ok.
The only thing is that the system sometimes restarts on its own for inexplicable reasons. Scanning with OBD shows no errors. From the real time data menu on the 5F it only reports system reset as the reason for the reset system.
I was reading about the problem with the ExceptionList BUG. The symptoms look like that. Since the car is used I don't know who owned it before what kind of changes they made to the software.
Is there a way through the GEM to launch the script "rm /mnt/efs-persist/FEC/mmx_fec_ids.bin" and try to delete any folder if it were present?.
Or in this case is it better to try to load the same version of the firmware again from the user menu to try to return stock and re-execute the change?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I recently owned an A4 B9 with the MHI2Q_ER_AUG22_P5092 system.
I unlocked with M.I.B. activated lifetime map license and installed the new 2024 maps. Everything ok.
The only thing is that the system sometimes restarts on its own for inexplicable reasons. Scanning with OBD shows no errors. From the real time data menu on the 5F it only reports system reset as the reason for the reset system.
I was reading about the problem with the ExceptionList BUG. The symptoms look like that. Since the car is used I don't know who owned it before what kind of changes they made to the software.
Is there a way through the GEM to launch the script "rm /mnt/efs-persist/FEC/mmx_fec_ids.bin" and try to delete any folder if it were present?.
Or in this case is it better to try to load the same version of the firmware again from the user menu to try to return stock and re-execute the change?
Beta Was this translation helpful? Give feedback.
All reactions