Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

cid-updater error

This site may earn commission on affiliate links.
I'm getting an error when trying to install firmware on MCU1 from cid-updater recovery. Anyone know how to fix this?
cid-updater:40122: pending_command for retry: install http://192.168.90.101:80/2020.36.16-5-3e9e4e8dd2.mcu1 -o 0 cid-updater:40145: download status=complete cid-updater:36361: flush_relays sid=204 filename=/dev/mmcblk0p1 abs_filename=/dev/mmcblk0p1 cid-updater:36399: relay status=flushed monitor_sid=204 monitor_name=downloading filename=/dev/mmcblk0p1 cid-updater:40149: complete_download status=flushed retval=0 cid-updater:19636: do_after sid=291 pending_command = stage install http://192.168.90.101:80/2020.36.16-5-3e9e4e8dd2.mcu1 cid-updater:32506: write_file status=error path= open=No such file or directory cid-updater: 6393: dispatch_command status=error cmd=stage transition_state=fail state=ERROR cid-updater: 6422: TIMER: do after: timerfd OD parent: 0 fd:03 dtr:-1 READY:i pending: stage install http://192.168.90.101:80/2020.36.16-5-3e9e4e8dd2.mcu1 cid-updater:40872: verify_offline_and_stage sid=291 retry command=install http://192.168.90.101:80/2020.36.16-5-3e9e4e8dd2.mcu1 cid-updater:41722: sid 291 has just asked to be kept awake cid-updater:40920: signature status=starting cid-updater:13764: send_gwcmd line=13998 sid=291 status=success latency=0.10 command=0xa retval=0a01 cid-updater:14509: verifysig status=in_progress fused=1 cid-updater:14563: verifysig elapsed=389 status=success key=prod chunked=false cid-updater:14579: verifysig status=valid key=prod cid-updater:40951: signature status=verified elapsed=389 cid-updater:14673: verifyversion status=error reason=offline_version_too_small offline=9 online=10 cid-updater:11007: mount_offline_package status=error reason=ratchet cid-updater:40964: staging status=mount_error cid-updater:17865: terminate_update from=verify_offline_and_stage at_line=41008 reason=package_signature_invalid sid=291 token=status=failure activity=signature invert_bank=0 reboot=0 early=1 cid-updater:12518: Writing sentinel /var/spool/cid-updater/factory_redeploy_active: false cid-updater:12549: Wrote sentinel /var/spool/cid-updater/factory_redeploy_active. cid-updater:12518: Writing sentinel /var/spool/cid-updater/terminated/terminated-: status=failure package_signature_invalid cid-updater:12549: Wrote sentinel /var/spool/cid-updater/terminated/terminated-. cid-updater:17787: enable_gateway_features status=error reason=swr cid-updater:17791: enable_gateway_features status=error reason=drive cid-updater:17661: kill_update_monitoring_sessions killing session 'keepawake' sid=36 cid-updater:17661: kill_update_monitoring_sessions killing session 'wifi-watcher' sid=205 cid-updater:45659: handle_sentinel_file status=sentinel_already_removed file=gostaged/gostaged_in_progress cid-updater:17012: communicate_termination sid=291 status=starting token=status=failure activity=signature early=1 cid-updater:11794: warning: got 26 expirations (expected only one)
 
Is this separate from CID-updater’s CID recovery you get when a rootfs is corrupt?
There 2 maybe 3 updaters...
1. Standard updater run out of /deploy/cid-updater off the active firmware p1,p2 partition off the eMMC
2. Recovery updater run out of partition #7 (8th partition, starts at 0) of the Spansion NOR Flash
3. If there's a staged update, it could be running the updater out of the staged offline firmware p1,p2 partition off the eMMC but this one is not as common.

to enter #2 recovery without a corrupt eMMC, login to the gateway and run this... I'm sure there are other ways too.
tegrareset 0