Custom Firmware Has Gone

[peterpi]

I had a USB memory stick, with some MP4 media on it, plugged into the front port of my T2, when it decided to do a reboot. I am now presented with the "Custom Firmware Successfully Installed" page. When I click on the "Download & Install........." I get the "Reboot System" button. When I click reboot, it gets stuck in a loop and I get the first screen again. Although I can view programs, and scheduled programs are recorded, when I attempt to watch them the system constantly reboots. Should I just do a normal CF install via a reboot with a suitably prepared stick in the front.

TIA Pete

 

[Black Hole]

Should I just do a normal CF install via a reboot with a suitably prepared stick in the front.

NO!!!!

The CF is still installed (in Flash), it's not "gone" – the CF is giving you the "install WebIF" web page (no CF, no web page). If the CF had re-installed from your UPD (if you accidentally had the .hdf file on it), you would see a screen (TV) telling you the firmware install had completed and requiring you to restart. Then it would find the WebIF still there (which is on the HDD, not in Flash). When the unit reboots, you'll see the CF version displayed on the VFD – that's more evidence the CF is still there.

You need to recognise the difference between the Custom Firmware (which is a modified version of the Humax firmware, installed in Flash memory using the firmware update process), and the packages (software) which (mostly) exist in the file system on HDD. The CF enables the packages to be invoked, and it is the packages which provide the bulk of the functionality. WebIF is just a package (and in theory you could write your own alternative WebIF).

I had a USB memory stick, with some MP4 media on it, plugged into the front port of my T2, when it decided to do a reboot. I am now presented with the "Custom Firmware Successfully Installed" page.

This is just a coincidence. The UPD is not responsible for CF not finding WebIF. If CF can't find WebIF it assumes the CF has only just been installed ("Custom Firmware Successfully Installed") and you need to proceed to the next stage (ie downloading the WebIF and its dependencies).

The real question here is what has happened that WebIF has gone missing, and the fact is your report indicates a problem with the HDD. It might be cured by a fixdisk, but my hunch is something more serious.

You've been around long enough, did neither of these occur to you?:

Steps for Resolving HDR-FOX Crash/Reboot Issues (click)

Quick Guide to Disk Recovery (click)

 

[peterpi]

NO!!!!

The CF is still installed (in Flash), it's not "gone" – the CF is giving you the "install WebIF" web page (no CF, no web page). If the CF had re-installed from your UPD (if you accidentally had the .hdf file on it), you would see a screen (TV) telling you the firmware install had completed and requiring you to restart. Then it would find the WebIF still there (which is on the HDD, not in Flash). When the unit reboots, you'll see the CF version displayed on the VFD – that's more evidence the CF is still there.

You need to recognise the difference between the Custom Firmware (which is a modified version of the Humax firmware, installed in Flash memory using the firmware update process), and the packages (software) which (mostly) exist in the file system on HDD. The CF enables the packages to be invoked, and it is the packages which provide the bulk of the functionality. WebIF is just a package (and in theory you could write your own alternative WebIF).


This is just a coincidence. The UPD is not responsible for CF not finding WebIF. If CF can't find WebIF it assumes the CF has only just been installed ("Custom Firmware Successfully Installed") and you need to proceed to the next stage (ie downloading the WebIF and its dependencies).

The real question here is what has happened that WebIF has gone missing, and the fact is your report indicates a problem with the HDD. It might be cured by a fixdisk, but my hunch is something more serious.

You've been around long enough, did neither of these occur to you?:

Steps for Resolving HDR-FOX Crash/Reboot Issues (click)

Quick Guide to Disk Recovery (click)

Thanks for the heads up.

I should have said that it crashes playing stuff off a USB stick as well, so I think the HDD may be OK. It's 2TB and not that old. I can also access media on a NAT server and play compatible files. When I do a reboot it says Custom FW 3.13.

 

[peterpi]

I had to reregister for the portal, but when I try to access it I get this message. "sorry, this application is not currently available on your device".

 

[prpr]

it crashes playing stuff off a USB stick as well,

What sort of stuff? Native files, or something else?

so I think the HDD may be OK.

Well clearly something's amiss, otherwise the WebIf would start, but it doesn't.

It's 2TB and not that old.

Non sequitur.

I can also access media on a NAT server

Huh?

I had to reregister for the portal, but when I try to access it I get this message. "sorry, this application is not currently available on your device".

What's that got to do with any of this? The Humax portal is defunct.

You've just chucked loads of extra things in to the pot. Focus on the initial problem.
Provide the output of the relevant logs: /tmp/xinit.log, /tmp/boot.log, /tmp/modinit.log and /tmp/rag.log

There are two things that will stop the WebIf starting - the lighttpd binary not being present/executable or the /mod/webif/html/index.jim file not being present.

 

[Black Hole]

I agree. This scatter-gun thing will get nowhere, concentrate on one problem at a time.

Provide the output of the relevant logs: /tmp/xinit.log, /tmp/boot.log, /tmp/modinit.log and /tmp/rag.log

How? No WebIF. Might not have betaftpd installed. Could Telnet in but grabbing a file via Telnet will require instruction for the uninitiated (see wiki for general Telnet instructions, then maybe cat the relevant files and copy-paste them from the Telnet terminal).

If the unit is stable unless playing back recordings, in my view the first step should be a fixdisk via the Telnet menu.

 

[prpr]

Could Telnet in but grabbing a file via Telnet will require instruction for the uninitiated

Yes, Telnet. If people need assistance with that then they can ask.

If the unit is stable unless playing back recordings, in my view the first step should be a fixdisk via the Telnet menu.

Indeed - as you already suggested that I didn't mention it. But while it may correct any underlying problem which caused this one, it probably won't fix it. It may need a force reinstall of either lighttpd or webif as well.

 

[peterpi]

The last time I had a public bollocking like that I was back in the 50's when I was in Grammar school. It might have been one of my many transgressions. It could have been the railway detonators, the trading of Harrison Marks photos, taking the afternoon off to go swimming in the sea at Langland or one of many other transgressions. I regret none of them.

it crashes playing stuff off a USB stick as well,

What sort of stuff? Native files, or something else?
MPG4's

I can also access media on a NAT server

Huh?
NAS, WD My Cloud. My dyslexia.

I had to reregister for the portal, but when I try to access it I get this message. "sorry, this application is not currently available on your device".

What's that got to do with any of this? The Humax portal is defunct.
I followed the above suggestion and clicked on https://hummy.tv/forum/threads/steps-for-repairing-a-disk-of-unknown-faults.3082/ where I came across this ">If you have the HDR-FOX set up and able to access the TV Portal (eg BBC iPlayer), the HDR-FOX must also be on your home network<. I was only obeying orders!

In the meantime, whilst answering your points, "I clicked the "Download & install the Full Web Interface" button and all of the "Congratulations............." message appeared.
After a reboot all is back to normal.

Prior to this attempt I had accessed the Telnet menu and entered the "Reset" command.

Thanks
Pete

 

[Black Hole]

In the meantime, whilst answering your points, "I clicked the "Download & install the Full Web Interface" button and all of the "Congratulations............." message appeared.
After a reboot all is back to normal.

Prior to this attempt I had accessed the Telnet menu and entered the "Reset" command.

Fine, you've cured a symptom without establishing the cause. I see no reason that will have cured your rebooting problem.

 

[prpr]

Prior to this attempt I had accessed the Telnet menu and entered the "Reset" command.

That seems a bit drastic. You are effectively starting from clean, so will have to reinstall all your packages and configure all their settings.
And we don't get to find out what the cause was. Oh well...

 

[peterpi]

Fine, you've cured a symptom without establishing the cause. I see no reason that will have cured your rebooting problem.

I left the T2 running for several hours without any reboots. I had no packages installed, but I then installed "auto-unprotect" and only that one. I checked it out and it was doing its thing. However when I logged on to the Web IF I had a warning of eighteen crashes. I checked the crash log and they were happening at random intervals between 900 seconds and 67 seconds. I removed the auto-unprotect twelve hours ago and so far no crashes.

Thanks again
Pete

 

[prpr]

I would suggest you do a DLNA database reset, reboot, reinstall auto-unprotect and then see what happens.

 

[Black Hole]

I wonder whether this has anything to do with

2C: Disconnect the network connection (Ethernet cable or WiFi dongle). If the crashes stop, the likelihood is that the DLNA service is conflicting with another DLNA service on your home network. Some versions of Twonky are known to conflict in this way - have you added or updated a DLNA service on your network recently?

 

[prpr]

Just installing auto-unprotect isn't going to change the DLNA service on the Humax or anything on the network interacting with it.

 

[Black Hole]

We don't know that the events were coincident, as usual the OP doesn't make it plain, and he doesn't say he's followed the diagnostic process step be step (which would include checking what happens with the network disconnected).