- #Aurora blu ray player doesnt play any sound serial#
- #Aurora blu ray player doesnt play any sound update#
- #Aurora blu ray player doesnt play any sound code#
- #Aurora blu ray player doesnt play any sound download#
#Aurora blu ray player doesnt play any sound serial#
Unfortunately, both of these fixes require low-level access to the serial debug port of the player, soldering wires to the motherboard, proprietary hardware and software tools as well as deep knowledge of the player’s architecture.
At the time of writing this, no such updated firmware exists.
#Aurora blu ray player doesnt play any sound update#
The only ways to revive the player are: erase the invalid policy file from the flash partition, or update the firmware of the player with a version in which the XML parse bug has been corrected. Gray suggested this XML file was sent to the Blu-ray players without proper verification.īecause of the monumentally stupid idea of parsing a downloaded XML file unconditionally at every boot, there seems to be no way to recover the devices from the boot loop using normal means – such as a USB stick, CD or network – because the crash happens too early in the boot sequence.
#Aurora blu ray player doesnt play any sound code#
The device code appears not to have been designed to handle that possibility because the empty list produces an invalid memory reference in the device's main program, called bdpprog, which causes the kernel to terminate it.Ĭrashing the main program results in a reboot, but since the logging policy XML file is always processed early on after startup, the crash simply reoccurs before a fixed version of the file can be fetched. "Unfortunately for Samsung, the code which handles the processing of the log policy XML file has not been tested for such an empty element and causes a crash," Gray explained. Though a valid XML file, it contained an empty list element, we're told: The problem with the XML file, sent out on June 18, 2020, is that it wasn't formatted in a way compatible with the device's code.
#Aurora blu ray player doesnt play any sound download#
Samsung never asked the user if it was OK to download the bomb," said Gray, referring to the dodgy XML policy file. It was enough for the player to be connected to the internet. "Players were bricked even though the users never performed a network update.
The firmware routinely automatically fetches, stores, and parses the logging policy file regardless of anything else. Also, it explains why players that never performed a software update nor used a network service, and were simply connected to the internet, were bricked. That's why, our source tells us, Samsung Blu-ray players that have never connected to the internet were not affected by the flawed file. After that notice is accepted, these Blu-ray players no longer bug their users with privacy notices, and simply quietly send the telemetry while the system checks for software updates.Īnd even if you don't use something like Netflix, or don't accept the privacy notice nor download a software update, but do connect the device to the internet, your player will still routinely fetch the logging policy file. The privacy notice comes into play when the customer connects the device to the internet and tries to use a network service like Netflix. The affected Blu-ray players, we're told, do not transmit their logs until a privacy notice has been accepted by the user. These logs include things like when you opened, say, the Netflix app and when you closed it on the player.Įxactly how much the device should log and transmit back to HQ is defined by Samsung in an XML logging policy file regularly fetched from this URL: This telemetry is sent to the tech giant's servers when the player's firmware is told to check for a software update. One thing you have to understand is that these internet-connected Blu-ray players in question are programmed to log their activities and send copies of this information to Samsung. Drilling inĪ Register reader who is savvy with low-level hardware, and asked to be identified simply as Gray, provided us a detailed technical analysis of Samsung's blunder. Crucially, the XML file would be parsed before a new one could be fetched from the internet, so once the bad configuration file was fetched and stored by these particular Samsung Blu-ray players in the field, they were bricked. Upon reboot, the player parsed the XML file again from its flash storage, crashed and rebooted again. This file, when fetched and saved to the device's flash storage and processed by the equipment, crashed the system software and force a reboot. However, it's been suggested to The Register that the cause of the failure was an XML file downloaded by the network-connected devices from Samsung servers during periodic logging policy checks. It was speculated by netizens and some media reports that a HTTPS certificate error was to blame.
0 kommentar(er)
