Looks like the 4000T now behaves and looks like the 5000T - new menu interface, quicker tv schedule. Haven't really had a chance to look in depth as yet but everything seems to work OK. No negatives as yet (fingers crossed it stays that way!).
My Humax Forum » Freeview HD » FVP 4000T, 5000T
New software version for FVP 5000T - 1.03.37
(100 posts)-
| Wed 24 Jan 2018 11:21:59 #41 |
-
1. Humax have not stated that 4000T support has ended.
2. Would not recommend anyone else trying the 5000T software on a 4000T until I have checked this out with Humax Towers.
Notwithstanding peterobb post - welcome to our Forum btw
In theory it should not be impossible as the system id's are different.
| Wed 24 Jan 2018 11:43:40 #42 | -
peterobb - 2 hours ago »
OK - so I downloaded the update file, re-named it as fvp-4000t_upgrade, burned it to a usb stick and tried to update my FVP4000T. The new firmware was recognized and the device updated successfully (screengrab attached). So the 5000T is just a 4000T ?
I wonder how this would handle a rollback to 4000t firmware. Thanks for experimenting though as I've been stopping myself from doing the same.
Edit: Looking at the picture the bootloader hasn't updated but is still the 4000t's UKTFAE1.05 not the 5000's UKTFAE1.06 (according to the 5000t Humax Support page).
| Wed 24 Jan 2018 12:17:31 #43 | -
Barry - 5 hours ago »
1. Humax have not stated that 4000T support has ended.
2. Would not recommend anyone else trying the 5000T software on a 4000T until I have checked this out with Humax Towers.
Notwithstanding peterobb post - welcome to our Forum btw
In theory it should not be impossible as the system id's are different.Barry
I think you are quite right to add a note of caution but the reality is that Humax have not issued a software update for the 4000T for some 10 months so it is a reasonable conclusion now that software support for the 4000 has ended - I would however welcome a positive statement from Humax to the contrary if that is not the case and if so some indication as to when the next 4000T update is scheduled ?
Have to say I have downloaded a copy of the latest 5000T upgrade just in case Humax do anything to block it being used for the 4000T.
| Wed 24 Jan 2018 17:37:24 #44 | -
I downloaded it a while ago as I have been very tempted to do this as well, especially as the early internal photo showed a FVP-4000 sticker on it.
I think once I know it can be downgraded back to the FVP-4000, just in case there are any issues, I will give it ago.
| Thu 25 Jan 2018 8:13:22 #45 | -
After doing the firmware update yesterday morning, I spent most of yesterday evening trying everything out to see if it all works properly. I've watched live tv, catch-up tv, previous recordings, new recordings and video streamed from a number of DNLA sources. All worked perfectly. I can find no instabilities or other issues. My FVT-4000T acts like an FVP-5000T.
I'm reluctant to try the firmware downgrade at present mainly because I don't see the point - I was prepared to brick the device when trying the initial firmware upgrade but, now that it's been successful, I'm not prepared to risk bricking it again just to end up where I started!| Thu 25 Jan 2018 9:07:15 #46 | -
peterobb - 36 minutes ago »
After doing the firmware update yesterday morning, I spent most of yesterday evening trying everything out to see if it all works properly. I've watched live tv, catch-up tv, previous recordings, new recordings and video streamed from a number of DNLA sources. All worked perfectly. I can find no instabilities or other issues. My FVT-4000T acts like an FVP-5000T.
I'm reluctant to try the firmware downgrade at present mainly because I don't see the point - I was prepared to brick the device when trying the initial firmware upgrade but, now that it's been successful, I'm not prepared to risk bricking it again just to end up where I started!Thanks for being the alpha tester on this! Just wondering if you have tried the tv guide website/app to set timers and if that still worked okay after this update?
| Thu 25 Jan 2018 9:44:56 #47 | -
Yes - timers work fine. Did two recordings last night and watched earlier today.
| Thu 25 Jan 2018 12:12:33 #48 | -
giverny - 19 hours ago »
Have to say I have downloaded a copy of the latest 5000T upgrade just in case Humax do anything to block it being used for the 4000T.
A wise precaution no doubt, although the fact that the update isn't already blocked for 4000 users leads me to suspect that there's not enough difference between the 4000 and 5000's hardware to make such a block possible - unless it was simply an oversight and even now, some hapless Humax employee is sitting on the naughty step ruing his lack of foresight.
| Thu 25 Jan 2018 12:53:01 #49 | -
Marius - 8 minutes ago »
giverny - 19 hours ago »
Have to say I have downloaded a copy of the latest 5000T upgrade just in case Humax do anything to block it being used for the 4000T.
A wise precaution no doubt, although the fact that the update isn't already blocked for 4000 users leads me to suspect that there's not enough difference between the 4000 and 5000's hardware to make such a block possible - unless it was simply an oversight and even now, some hapless Humax employee is sitting on the naughty step ruing his lack of foresight.
In theory this should not have worked. The first thing a update checks is the device it's intended for has a matching system-ID to the device the update is intended for. This is a key check to avoid a incorrect software bricking the box.
This can also be used to test new software by temporarily changing the box system ID so it can only be used on a modified box. This works even though the two boxes have identical hardware.
The 5000T and 4000T do have different system ID's as looking at the photographs on this thread confirms but only in the last two digits.
Guessing that for some reason the update failed to check the complete system-ID in this case. So it slipped through the check, and fortunately the two are so similar it actually worked without any apparent ill effects.
| Thu 25 Jan 2018 13:10:28 #50 |
Reply »
You must log in to post.
