Black screen after trying to update

psjmaster · 30 January 2024 19:39

Hello, I’m from Brazil, sorry for my bad English. I hope you can help me.

I tried to update my sync 3 Ford with a USB drive generated directly by the cyanLabs Syn3Updater app (print attached).

I put the pendriver in the USB port of my Ford Edge and it started
update.

After a while I received a message asking me to turn off the key and then turn the key back on, after this procedure the screen went black.

I believe that the update was not completed and that is why the screen is black and nothing works on it.

I would like help trying to recover my sync3, I wanted to know if it would be possible to try to finish the update or restart it again, could you help me with some information on how to resolve this?

My Sync 3 was running Sync version 3.4.23088, and I tried updating to 3.4.23188 when the black screen appeared.

Note: I have a paid license to use the latest version of FORScan software, in case it helps to recover my sync3

SYNC Region: ANZ

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM Replacement

Old SYNC Version: 3.4.23088

New SYNC Version: 3.4.23188

Do you have a error message, if so what is it?
No

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.12.5.0 (Stable)

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

CYANLABS - SYN3 UPDATER - V2.12.5.0
Branch: Stable
Operating System: Microsoft Windows 11 Pro (2009)

PREVIOUS CONFIGURATION
Version: 3.4.23088
Region: ANZ
Navigation: True
Install Mode: Deteção Automática (downgrade)
Install Mode Overridden: False
My20 Protection Enabled: Deteção Automática

DESTINATION DETAILS
Mode: Drive
Model: ASMT ASM1156-PM SCSI Disk Device
Size: 1,8TB
FileSystem: NTFS
Partition Type: GPT

REFORMAT.LST
VOICE=5U5T-14G391-DS_1660784642000.TAR.GZ
GRACENOTES=4U5T-14G423-DC_1615429585000.TAR.GZ
APPS=NU5T-14G381-AD_1689364279000.TAR.GZ
MAP=4U5T-14G421-DAH_1683053828000.TAR.GZ
VOICE_NAV=4U5T-14G422-DH_1644008342000.TAR.GZ


AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.12.5.0 Stable - downgrade  Mode - Sync 3.4.23188 ANZ

[SYNCGen3.0_ALL_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1 = SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = TOOL - GB5T-14G386-SC_85041.tar.gz
Open2 = SyncMyRide\GB5T-14G386-SC_85041.tar.gz
Item3 = APP - 4U5T-14G381-AN_1552583626000.TAR.GZ
Open3 = SyncMyRide\4U5T-14G381-AN_1552583626000.TAR.GZ
Options = AutoInstall
[SYNCGen3.0_ALL]
Item1 = REFORMAT TOOL - 1u5t-14g386-cb.tar.gz
Open1 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall,Include,Transaction


FILES (9)
4U5T-14G381-AN_1552583626000.TAR.GZ (479,7MB)
GB5T-14G386-SC_85041.tar.gz (1,8KB)
1u5t-14g386-cb.tar.gz (8,5MB)
PU5T-14G386-BB_1690840002000.TAR.GZ (3,2KB)
5U5T-14G391-DS_1660784642000.TAR.GZ (1GB)
4U5T-14G423-DC_1615429585000.TAR.GZ (896MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869,8MB)
4U5T-14G421-DAH_1683053828000.TAR.GZ (4,8GB)
4U5T-14G422-DH_1644008342000.TAR.GZ (1,5GB)

LOG
[30/01/2024 11:39:15] Selected Region: ANZ - Release: Sync 3.4.23188 - Map Version: 2.22 (2022) - ANZ, SA and TW 
[30/01/2024 11:39:15] Install Mode: Deteção Automática (downgrade) Forced: False 
[30/01/2024 11:39:15] MY20 Protection: Deteção Automática 
[30/01/2024 11:39:15] Formatting USB drive
[30/01/2024 11:39:15] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[30/01/2024 11:39:21] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[30/01/2024 11:39:21] Downloading: 4U5T-14G381-AN_1552583626000.TAR.GZ
[30/01/2024 11:39:36] Validating: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[30/01/2024 11:39:37] Downloaded: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[30/01/2024 11:39:37] Checking Existing File: GB5T-14G386-SC_85041.tar.gz 
[30/01/2024 11:39:37] Downloading: GB5T-14G386-SC_85041.tar.gz
[30/01/2024 11:39:37] Validating: GB5T-14G386-SC_85041.tar.gz 
[30/01/2024 11:39:37] Downloaded: GB5T-14G386-SC_85041.tar.gz 
[30/01/2024 11:39:37] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[30/01/2024 11:39:37] Downloading: 1u5t-14g386-cb.tar.gz
[30/01/2024 11:39:59] Validating: 1u5t-14g386-cb.tar.gz 
[30/01/2024 11:39:59] Downloaded: 1u5t-14g386-cb.tar.gz 
[30/01/2024 11:39:59] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[30/01/2024 11:39:59] Downloading: PU5T-14G386-BB_1690840002000.TAR.GZ
[30/01/2024 11:40:00] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[30/01/2024 11:40:00] Downloaded: PU5T-14G386-BB_1690840002000.TAR.GZ 
[30/01/2024 11:40:00] Checking Existing File: 5U5T-14G391-DS_1660784642000.TAR.GZ 
[30/01/2024 11:40:00] Downloading: 5U5T-14G391-DS_1660784642000.TAR.GZ
[30/01/2024 11:40:30] Validating: 5U5T-14G391-DS_1660784642000.TAR.GZ 
[30/01/2024 11:40:33] Downloaded: 5U5T-14G391-DS_1660784642000.TAR.GZ 
[30/01/2024 11:40:33] Checking Existing File: 4U5T-14G423-DC_1615429585000.TAR.GZ 
[30/01/2024 11:40:33] Downloading: 4U5T-14G423-DC_1615429585000.TAR.GZ
[30/01/2024 11:41:08] Validating: 4U5T-14G423-DC_1615429585000.TAR.GZ 
[30/01/2024 11:41:10] Downloaded: 4U5T-14G423-DC_1615429585000.TAR.GZ 
[30/01/2024 11:41:10] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[30/01/2024 11:41:10] Downloading: NU5T-14G381-AD_1689364279000.TAR.GZ
[30/01/2024 11:41:37] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[30/01/2024 11:41:39] Downloaded: NU5T-14G381-AD_1689364279000.TAR.GZ 
[30/01/2024 11:41:39] Checking Existing File: 4U5T-14G421-DAH_1683053828000.TAR.GZ 
[30/01/2024 11:41:39] Downloading: 4U5T-14G421-DAH_1683053828000.TAR.GZ
[30/01/2024 11:45:30] Validating: 4U5T-14G421-DAH_1683053828000.TAR.GZ 
[30/01/2024 11:45:42] Downloaded: 4U5T-14G421-DAH_1683053828000.TAR.GZ 
[30/01/2024 11:45:42] Checking Existing File: 4U5T-14G422-DH_1644008342000.TAR.GZ 
[30/01/2024 11:45:42] Downloading: 4U5T-14G422-DH_1644008342000.TAR.GZ
[30/01/2024 11:48:01] Validating: 4U5T-14G422-DH_1644008342000.TAR.GZ 
[30/01/2024 11:48:05] Downloaded: 4U5T-14G422-DH_1644008342000.TAR.GZ 
[30/01/2024 11:48:05] Preparing USB drive
[30/01/2024 11:48:05] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[30/01/2024 11:48:05] Copying: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[30/01/2024 11:48:14] Validating: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[30/01/2024 11:48:17] Copied: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[30/01/2024 11:48:17] Checking Existing File: GB5T-14G386-SC_85041.tar.gz 
[30/01/2024 11:48:17] Copying: GB5T-14G386-SC_85041.tar.gz 
[30/01/2024 11:48:17] Validating: GB5T-14G386-SC_85041.tar.gz 
[30/01/2024 11:48:17] Copied: GB5T-14G386-SC_85041.tar.gz 
[30/01/2024 11:48:17] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[30/01/2024 11:48:17] Copying: 1u5t-14g386-cb.tar.gz 
[30/01/2024 11:48:17] Validating: 1u5t-14g386-cb.tar.gz 
[30/01/2024 11:48:17] Copied: 1u5t-14g386-cb.tar.gz 
[30/01/2024 11:48:17] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[30/01/2024 11:48:17] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[30/01/2024 11:48:17] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[30/01/2024 11:48:17] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[30/01/2024 11:48:17] Checking Existing File: 5U5T-14G391-DS_1660784642000.TAR.GZ 
[30/01/2024 11:48:17] Copying: 5U5T-14G391-DS_1660784642000.TAR.GZ 
[30/01/2024 11:48:33] Validating: 5U5T-14G391-DS_1660784642000.TAR.GZ 
[30/01/2024 11:48:39] Copied: 5U5T-14G391-DS_1660784642000.TAR.GZ 
[30/01/2024 11:48:39] Checking Existing File: 4U5T-14G423-DC_1615429585000.TAR.GZ 
[30/01/2024 11:48:39] Copying: 4U5T-14G423-DC_1615429585000.TAR.GZ 
[30/01/2024 11:48:51] Validating: 4U5T-14G423-DC_1615429585000.TAR.GZ 
[30/01/2024 11:48:56] Copied: 4U5T-14G423-DC_1615429585000.TAR.GZ 
[30/01/2024 11:48:56] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[30/01/2024 11:48:56] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[30/01/2024 11:49:08] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[30/01/2024 11:49:12] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[30/01/2024 11:49:12] Checking Existing File: 4U5T-14G421-DAH_1683053828000.TAR.GZ 
[30/01/2024 11:49:12] Copying: 4U5T-14G421-DAH_1683053828000.TAR.GZ 
[30/01/2024 11:50:16] Validating: 4U5T-14G421-DAH_1683053828000.TAR.GZ 
[30/01/2024 11:50:45] Copied: 4U5T-14G421-DAH_1683053828000.TAR.GZ 
[30/01/2024 11:50:45] Checking Existing File: 4U5T-14G422-DH_1644008342000.TAR.GZ 
[30/01/2024 11:50:45] Copying: 4U5T-14G422-DH_1644008342000.TAR.GZ 
[30/01/2024 11:51:05] Validating: 4U5T-14G422-DH_1644008342000.TAR.GZ 
[30/01/2024 11:51:14] Copied: 4U5T-14G422-DH_1644008342000.TAR.GZ 
[30/01/2024 11:51:14] Generating reformat.lst
[30/01/2024 11:51:14] Generating autoinstall.lst
[30/01/2024 11:51:14] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

SaNdMaN · 30 January 2024 19:46

If this is true and the screen went black after the 2nd reboot, the unit may be MY20. You cant reformat MY20 units. Do you know what model the APIM is?.

Edit: apologies, images were not loaded before, I’ve just seen the photo. That’s a counterfeit unit if you ask me.

psjmaster · 30 January 2024 19:50

Model APIM 14G370

SaNdMaN · 30 January 2024 19:51

That’s a fake APIM, where did you source it from?.

psjmaster · 30 January 2024 19:55

I understand, so there is no solution, did I lose my sync 3 when doing this update?

NaviUpgrade · 30 January 2024 20:00

Looks to be LU5T-14G371-DAB, so definitely MY20.

To me it looks like you potentially have a knock off Chinese unit as all the units I have seen say made in Mexico, not made in China. This could differ for ANZ vehicles though, as my experience is mainly NA based vehicles.

I’d say you’ve definitely bricked your module.

The only way you’re going to bring it back to life is by running this GH repository.

bigunclemax/sync3flash: Ford Sync 3 reformat flash tool (github.com)

You’ll need a computer with Linux… you can use Puppy Linux (I use fossapup when doing this) and booting from a USB stick, though you’ll need to make sure that secure boot is turned off in the BIOS to boot into the Linux distro.

Take apart the APIM and connect it with a mini USB cable to your computer. Carefully hold the board from the outside edges, and boot the apim with the board bare, either on the bench or in your vehicle. Just be careful not to short anything if doing it in your vehicle.

Once in there you’ll need to run the sync3flash 1.1 release by following the guide in the GH repository.

Once running it’ll say waiting… then short the two pads that are shown in this gh repository: Sync3UsbBootReformat_EN.md (github.com)

Once it finishes sending two images to the target you can disconnect the APIM from the vehicle, rehouse it, then put it back on your screen and begin the reformat process.

SaNdMaN · 30 January 2024 20:01

Possibly, yes…
Keep in mind that the unit is not genuine, so we can’t know what’s inside it.

Since you have Forscan, can you read which model the APIM gives back?. It should be discoverable even in that state.

SaNdMaN · 30 January 2024 20:02

It’s a fake sticker, it’s an L series APIM from 2019 (???) and there are no hyphens in the full model… Not to mention the quality pass shiny sticker

It’s a fake / counterfeit unit…

NaviUpgrade · 30 January 2024 20:03

Yeah that was my takeaway too. Something weird going on for sure. I’d doubt the serials match up either.

Edit: Serials do not match up. Definitely a knock off unit.

psjmaster · 30 January 2024 20:16

You are correct, I bought this module on aliexpress to change my Sync2 to Sync 3 and they must have sent me a counterfeit module.

psjmaster · 30 January 2024 20:19

I have my original sync 2 saved and I have already reinstalled it while I find a solution for the fake sync 3

SaNdMaN · 30 January 2024 20:36

You didn’t say if Forscan can read the unit…

psjmaster · 30 January 2024 20:48

Yes he can read

SaNdMaN · 30 January 2024 21:03

Can you provide that?.

psjmaster · 30 January 2024 21:29

I’m putting it back in the vehicle and I’ll do the reading with Forscan, as soon as I have the reading I’ll post it here again

SaNdMaN · 30 January 2024 21:33

Sure… What I would like to know is what APIM model Forscan reads, since the sticker can be faked/replaced, but the hardware is hardware…

Also, the unit is 100% dead?. I mean, no audio?, no USB ports power?.
If it’s bricked, I would think this should be the case…

system · 1 February 2024 21:34

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.