- 2017: 6432, 6452, 7202, 7272
- 2016: 6401 (nicht 32PFS6401), 6501, 6521, 6551, 6561, 6581, 7101, 7181, 7601
- inoffiziell 2015: xxPUS71x0/R2, xxPUS7600/R3
- inoffiziell 2014: xxPUS7909/R2, 55PUS8809/R3, 55PUS8909C/R3, xxPUS9101/R3
- Dieses Thema hat 100 Antworten sowie 2 Teilnehmer und wurde zuletzt vor vor 5 Jahren von
aktualisiert.
-
Thema
-
Tachchen, es gibt eine neue Firmware für Philips TV-Modelle /-Fernseher der folgenden 2014er, 2015er, 2016er und 2017er TV-Serien: 2017 – QM163E (Down
[Vollständiger Blog-Eintrag: Philips: Neue Firmware für 2014/2015/2016/2017er TVs mit Android TV 8 Oreo (QM163E: 26.39)]
-
Antworten
-
I have the same problem on my 48PUS7600. Update downloads from USB stick, TV asks to restart, progress bar gets to about 20% and TV restarts without error message but is still on the old firmware.
Will try to install in recovery mode next.
Tried to install in recovery but got this message “This software package is not applicable to tour TV””. Maybe Philips messed something up?
@Toengel Same error as Momchil in recovery mode. I will e-mail you a picture of the error message. Looks like something is wrong with the upg file, at least for the 7600/R3 model.
@Toengel I’m not sure what you mean by “Oreo is not supported for Rework-Models”. My 7600/R3 is already running Oreo, but it’s the previous version (25.238). Are you saying we will be “stuck” on this version and won’t receive any further updates? I find that hard to believe, because the hardware platform is QM163E, same as the other TVs with the same board.
Maybe the “trick” with temporarily giving the TV a different model number in the service menu will work. I know that worked for the previous version that would not be offered over the internet until you changed the model number.
I can confirm update does obviously NOT work on upgraded models.
My 7180/r2 stops update on approx. 20%, reboots and gets back to TV Mode.
Tried both, online update and usb-download. Both no succes :-(
Has anybody successfully applied the “trick” with the model version?
Could anybody provide the 26.17 Oreo version as a download link as I am stuck on the initial Oreo?
@toengel I’m not sure what you mean by „Oreo is not supported for Rework-Models“. My 7600/R3 is already running Oreo, but it’s the previous version (25.238). Are you saying we will be „stuck“ on this version and won’t receive any further updates? I find that hard to believe, because the hardware platform is QM163E, same as the other TVs with the same board.
Maybe the „trick“ with temporarily giving the TV a different model number in the service menu will work. I know that worked for the previous version that would not be offered over the internet until you changed the model number.
Hi,
if the rework is done by a service center, the TV will come with Nougat. And since the rework TVs don’t have official support websites you depend on OTA updates… and all rework TVs will only receive Nougat updates (16.x) – and will never receive Oreo…
That Oreo could be installed via USB manually is only known, since some guys around the internet (;-)) know, that it’s the same platform as in 2016… Now with 26.39 Philips decided to check the TV model number during the update procedure… if the TV is a rework model, the update won’t finish successfully…
Toengel@Alex
Has anybody successfully applied the „trick“ with the model version?
Could anybody provide the 26.17 Oreo version as a download link as I am stuck on the initial Oreo?
Hi,
see firmware archive…
Toengel@Alex
Hi Alex!
There is a remedy for the problem…?
@Toengel I know you don’t have any influence on it, but that is a pretty pathetic move from Philips/TP Vision in my opinion :(
@Marc You said you also tried the online method, does that mean you changed your TV model first in the service menu?
I decided to test the model change trick myself and what do you know, it worked!
I changed the model number in the NVM Editor in the service menu from 48PUS7600/R3 to 49PUS7101/12 and rebooted the TV. After that I could successfully install the 26.39 version from a USB stick. Internet download would probably have worked as well, because the TV did find an online update. However, USB was quicker for me because I had already downloaded the software.
After the upgrade I changed the model number back again and rebooted. I checked the option numbers and they all stayed the same, so I don’t think reflashing the NVM.BIN and NVM.EEE files is necessary.
Hi,
reflashing NVM/EED is only necessary to re-activate 3D via HDMI (only working for 4k sources)… without NVM/EED flashing, e.g. your PS3/Xbox don’t detect your TV as a 3D device.
Toengel@Alex
Great, it worked with modifying the model and afterwards updating via USB. It is fantastic that this forum exists and I am happy to see that it is becoming more international. The downside of this is of course the fact that there is hardly any other place to get support for Philips TVs.
It is a pity that Philips apparently startet to check model type during the update. Especially when you did not get the hardware “upgrade” during the warranty period and paid a lot of money for that.
Does anyone know if/when the ambilight patent expires? I bet the sales of Philips TVs will crash if that is the case.
The update is successful 43PUS7150 / R2 !!! Type changed to 43PUS6401 / 12 !!! OTA Update OK and USB Update OK !!! This page is good! THX Alex!
