topic A1 OLED shows PKG0.0000.0065EUA After Dolby vision update (6.285) in Android TV

A1 OLED shows PKG0.0000.0065EUA After Dolby vision update (6.285)

Alecb500 — Mon, 23 Apr 2018 15:54:16 GMT

Hey! Got a problem here.. After manually updating the KD-65A1 to 6.285 it says that the update finished successfully. But no new search bar and certainly no Dolby Vision. And the version number says PKG0.0000.0065EUA. Tried multiple different usb sticks (read on another thread that it was sensitive to the manufacturer) and tried different Formats (first fat32) and all of the usb ports. Also followed the instructions carefully. Anybody have a clue of whats going on? or how to fix this?

Re: A1 OLED shows PKG0.0000.0065EUA After Dolby vision update (6.285)

dutchice — Tue, 24 Apr 2018 15:10:26 GMT

I recommend you contact SONY Customer Service and describe the steps you have taken with as much detail as possible. There is a Software Recovery package which you will require in order to flash the unit to its recovery state. After that you will have to upgrade the unit with the latest firmware revision. This is the only way to be able to upgrade the TV with the same FW revision level. They possibly will ask to verify the current status of your unit through remote assistance. But they will provide you with the instructions on how to proceed for that, so there’s no need to worry. In the future please make a habit of executing a Factory Data Reset prior to upgrading your firmware. This reduces the risks of running into trouble.

Re: A1 OLED shows PKG0.0000.0065EUA After Dolby vision update (6.285)

Alecb500 — Wed, 25 Apr 2018 17:41:10 GMT

Thanks! Will contact them tomorrow

Re: A1 OLED shows PKG0.0000.0065EUA After Dolby vision update (6.285)

Alecb500 — Mon, 30 Jul 2018 08:17:58 GMT

As a follow up. The recovery package is just the firmware on a Sony usb stick, nothing special about they told me. I have to send the TV in and will probably get a replacement. But it will take a week or two... 😞 😞

Re: A1 OLED shows PKG0.0000.0065EUA After Dolby vision update (6.285)

dutchice — Mon, 30 Jul 2018 11:29:04 GMT

You could try a manual firmware update, it most probably will fix the issue.

Find your most reliable USB device which is in good working order. Download a formatting application called Rufus. Format the USB device using the following settings:

Boot selection: Non bootable
Partition scheme: MBR
Target system: BIOS or UEFI
File system: FAT32
Cluster size: Default

Then download the firmware for your A1 from here. Copy the file "sony_dtv0FA60A0AA0AA_00004100_16056031000175.pkg" from inside the ZIP file you just downloaded to the root directory of your USB device. This means do not place the file inside any folders.

To install the update please follow the simple steps below:

Turn on the TV.
Make sure that no USB devices are inserted into your TV.
Insert your USB storage device containing the file "sony_dtv0FA60A0AA0AA_00004100_16056031000175.pkg" into a USB port of the TV set.
NOTE: Any USB slot can be used if the TV has multiple USB ports.
Once the USB storage device has been detected, a series of different messages will appear on the TV set. Follow the on screen instructions.
NOTE: If the messages do not appear automatically, try turning the TV off and on with the remote control.
When the file is finished copying from the USB storage device, the update process will begin, the POWER indicator on the TV will begin flashing white, and the update progress screen is displayed on the TV.
After several minutes, the TV will turn off and then turn back on to complete the update.
WARNING: During the software installation process, please do not:
- Remove the USB device
- Turn off the TV
- Disconnect the TV from the power supply
When the software update is complete, a message appears on the TV indicating the software update is complete.
Carefully remove the USB device from the USB slot.

Check the current software version to confirm that the update has successfully been installed.

Re: A1 OLED shows PKG0.0000.0065EUA After Dolby vision update (6.285)

unrealwzg — Sat, 18 May 2019 13:34:25 GMT

same issue here. have you managed to solved this issue?