Sync 3.4.19274 downgrade black screen.

Jwitz · 24 January 2025 23:13

Hi,

This is my first install, so any help and patience is greatly appreciated.

I currently have Sync 3.4.19274 and am trying to upgrade to Sync 3.4.23188. I used the auto function last night and it would say “updating system software” for over an hour. I tried several times with no luck. I read on one of the forums, that 3.4.19274 must be down graded before it can be updated. I selected the downgrade option and loaded it to my USB drive.

After plugging it in, the update was working. It told me to turn off the car. I turned off the car, but for some reason I also opened my door. I thought it was supposed to turn the stereo off all the way for some reason. Then the screen turned black, and won’t do anything. Just a black screen, won’t turn on. I tried a soft reset, but it didn’t work.

Im not sure what I did when I turned the stereo off all the way, but it doesn’t seem good! Here is my log file. Any help is greatly apperciated!

Thank you ! Jason

SYNC Region: NA

Navigation Variant: Non Nav

Manufacturer Year: Pre MY20

Install Type: OEM Replacement

Old SYNC Version: 3.4.19274

New SYNC Version: 3.4.23188

Do you have a error message, if so what is it?
Just a black screen

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: SYN3 UPDATER - V2.13.0.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

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

PREVIOUS CONFIGURATION
Version: 3.4.19274
Region: NA
Navigation: False
Install Mode: downgrade (downgrade)
Install Mode Overridden: True
My20 Protection Enabled: Disabled / Not MY20

DESTINATION DETAILS
Mode: Drive
Model: General UDisk USB Device
Size: 29.3GB
FileSystem: FAT32
Partition Type: MBR

REFORMAT.LST
VOICE=5U5T-14G391-CS_1660783942000.TAR.GZ
GRACENOTES=4U5T-14G423-CC_1615429225000.TAR.GZ
APPS=NU5T-14G381-AD_1689364279000.TAR.GZ


AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.13.0.0 Stable - downgrade FORCED  Mode - Sync 3.4.23188 NA

[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 (7)
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-CS_1660783942000.TAR.GZ (385.5MB)
4U5T-14G423-CC_1615429225000.TAR.GZ (564.2MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869.8MB)

LOG
[1/24/2025 1:54:41 PM] Selected Region: NA - Release: Sync 3.4.23188 - Map Version: Non Nav APIM 
[1/24/2025 1:54:41 PM] Install Mode: downgrade (downgrade) Forced: True 
[1/24/2025 1:54:41 PM] MY20 Protection: Disabled / Not MY20 
[1/24/2025 1:54:41 PM] Formatting USB drive
[1/24/2025 1:54:41 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[1/24/2025 1:54:49 PM] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[1/24/2025 1:54:49 PM] Downloading: 4U5T-14G381-AN_1552583626000.TAR.GZ
[1/24/2025 1:56:24 PM] Validating: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[1/24/2025 1:56:26 PM] Downloaded: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[1/24/2025 1:56:26 PM] Checking Existing File: GB5T-14G386-SC_85041.tar.gz 
[1/24/2025 1:56:26 PM] Downloading: GB5T-14G386-SC_85041.tar.gz
[1/24/2025 1:56:27 PM] Validating: GB5T-14G386-SC_85041.tar.gz 
[1/24/2025 1:56:27 PM] Downloaded: GB5T-14G386-SC_85041.tar.gz 
[1/24/2025 1:56:27 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[1/24/2025 1:56:27 PM] Downloading: 1u5t-14g386-cb.tar.gz
[1/24/2025 1:56:30 PM] Validating: 1u5t-14g386-cb.tar.gz 
[1/24/2025 1:56:30 PM] Downloaded: 1u5t-14g386-cb.tar.gz 
[1/24/2025 1:56:30 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/24/2025 1:56:30 PM] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
[1/24/2025 1:56:30 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[1/24/2025 1:56:33 PM] Validated: 5U5T-14G391-CS_1660783942000.TAR.GZ (Skipping Download) 
[1/24/2025 1:56:33 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[1/24/2025 1:56:37 PM] Validated: 4U5T-14G423-CC_1615429225000.TAR.GZ (Skipping Download) 
[1/24/2025 1:56:37 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[1/24/2025 1:56:44 PM] Validated: NU5T-14G381-AD_1689364279000.TAR.GZ (Skipping Download) 
[1/24/2025 1:56:44 PM] Preparing USB drive
[1/24/2025 1:56:44 PM] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[1/24/2025 1:56:44 PM] Copying: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[1/24/2025 1:57:51 PM] Validating: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[1/24/2025 1:58:13 PM] Copied: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[1/24/2025 1:58:13 PM] Checking Existing File: GB5T-14G386-SC_85041.tar.gz 
[1/24/2025 1:58:13 PM] Copying: GB5T-14G386-SC_85041.tar.gz 
[1/24/2025 1:58:13 PM] Validating: GB5T-14G386-SC_85041.tar.gz 
[1/24/2025 1:58:13 PM] Copied: GB5T-14G386-SC_85041.tar.gz 
[1/24/2025 1:58:13 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[1/24/2025 1:58:13 PM] Copying: 1u5t-14g386-cb.tar.gz 
[1/24/2025 1:58:14 PM] Validating: 1u5t-14g386-cb.tar.gz 
[1/24/2025 1:58:14 PM] Copied: 1u5t-14g386-cb.tar.gz 
[1/24/2025 1:58:14 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/24/2025 1:58:14 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/24/2025 1:58:14 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/24/2025 1:58:14 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/24/2025 1:58:14 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[1/24/2025 1:58:14 PM] Copying: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[1/24/2025 1:59:05 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[1/24/2025 1:59:20 PM] Copied: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[1/24/2025 1:59:20 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[1/24/2025 1:59:20 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[1/24/2025 2:00:32 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[1/24/2025 2:01:04 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[1/24/2025 2:01:04 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[1/24/2025 2:01:04 PM] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[1/24/2025 2:02:57 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[1/24/2025 2:03:39 PM] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[1/24/2025 2:03:39 PM] Generating reformat.lst
[1/24/2025 2:03:39 PM] Generating autoinstall.lst
[1/24/2025 2:03:39 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

SaNdMaN · 24 January 2025 23:25

Hello.

I’m not sure where you read that, but that’s not true.

It seems your APIM is no NAV, so that’s expected. You need to make enough room first, then you can upgrade.

Based on the log you sent, that installation was the reformat tool. You can’t reformat My20 hardware, and if you do, well, a black screen is the result.

So this seems to be a reformat on MY20 hardware. Did you ever run the interrogator log to check the APIM’s model?. Do you have forscan and an adapter?.

I’m also assuming the the unit is super dead, no power to USB ports, NOTHING…

Jwitz · 25 January 2025 00:05

Thanks for your help. Yes I do have forscan and adapter. I just got the adapter yesterday and haven’t used it yet.

My truck is a 2016 F 250. It had sync 2 and I upgraded to sync 3 with a new screen as well. The donor APIM was from a 2019 vehicle.

You are correct, the unit appears to be super dead. No power to the USB.

I emailed the company I bought the hardware from and this is what they said.

“Ohh, you’ll just need to let it run with the black screen. Since the newer displays need 3.4 to operate, it downgrades to 3.3 first then re-upgrades to 3.4. Once it updates to 3.4 then the image should return”

I’m wondering if I messed it up by opening up the door and turning off the system entirely in the middle of the reboot?

SaNdMaN · 25 January 2025 00:19

Then query the APIM’s model through forscan and share that with us.

Jwitz · 25 January 2025 04:10

I plugged in the forscan. Not sure if this is what you are looking for but here are the screen shots. Is this helpful? Thanks!

SaNdMaN · 25 January 2025 09:58

Thank you for the information. So, according to our DB that’s not a MY20 APIM, so it should not be dead. I’m not sure about the screen though, and Forscan can’t see that part number. And even if it did, I’m not sure if there’s a naming convention.

There’s a chance the screen is MY20 and the reformat disabled the unit because it lacks the proper drivers for MY20 hardware (which includes the screen). If that’s the case, the unit should be recoverable by temporarily connecting a not-MY20 screen so that the process can complete.

I’m not sure if there’s some calibration that you could do on the APIM to solve this, this is a little out of my scope.

Is there any DTC present at the moment?

Lets wait to see what others have to say.

system · 24 February 2025 09:58

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