Since you are getting an error about 30 minutes in, either the unit is NA and you are trying to install EU maps, the USB drive you are using is bad or the APIM is not ok.
Use a decent quality branded USB pendrive (not a disk, not an sd).
Also, has been the car imported?. If it was, you can’t install EU maps onto a NA APIM.
If you want to recover the unit, recreate the pendrive but before configure Syn3updater as NO-NAV to avoid installing MAPS.
Then there’s something wrong with the unit or device you are using to upgrade.
Don’t you have a quality pendrive you could use?.
If you don’t, lets try this with your current usb:
configure syn3updater as a non-nav unit
recreate the usb (current 3.0, new 3.4)
go to the car and recover the unit
Once it’s recovered, set sync3updater to have 3.4 as your current build.
Then, create an interrogator log usb and run it against the unit.
Post the results back, edit your vin if you care about that.
That will tell us which type of APIM the car has.
Good, you found a Kingston device.
Now create and run the interrogator log and post the results.
If the APIM is 32GB, it’s NA and EU maps won’t fit without some tuning.
If the APIM si 64GB, then you should recreate a full NAV USB with the Kingston device and try again.
Check the USB you created, what’s inside the autoinstall.lst ?
Is it package -AC or -AD?
The log that you provided is strange, it cannot be opened by Syn3updater and there are some values missing.
From what I’ve read, it’s a 64GB APIM:
/fs/images/" total=“54G” available="49G
Before trying again, please confirm which package is referenced in the autoinstall.lst file for the interrogator log you created, if it’s GB5T-14G386-AC or GB5T-14G386-AD…
It should be -AD, but if it’s, try creating one with the -AC one and try again.
Since we didn’t hear back from you in 2 days and assuming no farther assistance is required, I’m setting a 2 day inactivity auto closure for the thread.
