Crash - Wait Reboot in 10..9..8. in a repeat cycle

Minari

New Member
I suspect my HDR T2 has finally died but does anybody know what this message on the recorder display means? It’s normally in deep standby but I noticed last night that it had turned itself on, was running very hot and the above display was on constant loop. The HUMAX logo appears briefly on the TV then it goes to no signal, so I can’t access it by the remote.
 
Powered down and left overnight but the problem remains. Thanks for the link - lots to digest there.
I’d pretty much given up on the T2 but kept it as a backup when the Aura occasionally goes bonkers.
When I get a chance I’ll disconnect the hard drive but that’s probably as far as my expertise goes.
Otherwise, I’ll put it up here if anyone wants it for parts.
Thanks again
 
With my humax the rebooting is only on specific channels, just had 5 reboots in 5 minutes watching Challenge off Winter Hill transmitter.

Switched to BBC1 HD and reboots stopped.
 
With my humax the rebooting is only on specific channels, just had 5 reboots in 5 minutes watching Challenge off Winter Hill transmitter.

Switched to BBC1 HD and reboots stopped.
This is not uncommon when tuned to some of the minor channels. It only seems to happen on some programmes as well – another time, another programme on the same channel will be fine.

They must be doing something "novel" with the data that the HDR-FOX was not programmed to expect.
 
My T2 fails to boot up and is stuck in a “Crash - Wait, Reboot in 10 … “ loop. My previous T2 had the same problem but never displayed the “Reboot” messages, just rebooted straight after showing the custom firmware message. I discovered in another thread on this forum that replacing a 4u7 capacitor on the main board may cure it. I have the necessary skills so did the replacement and it worked. So I have tried the same thing on my current T2 but without success. The reboot cycle happens whether or not the HDD is connected. In fact I disconnected the 4u7 capacitor too and it made no difference either 😏. It is very hard to fault find if the unit cannot even boot up. I did try changing the PSU in case the 5V or 12V supplies were low but still no luck. I guess I will have to scrap the main board and keep the rest for spares unless anyone else has any bright ideas. Thanks, Aviator.
 
I have tried the same thing on my current T2 but without success. The reboot cycle happens whether or not the HDD is connected.
Did you try disconnecting the drive before you replaced the capacitor? It would have saved you a job...
I did try changing the PSU in case the 5V or 12V supplies were low but still no luck.
Did you try measuring the voltages? I don't think I've ever seen anyone have a genuine PSU problem here.

'Install' the System Flush image in the same way you would a firmware image and then see what happens.
 
Typical. People read (or AI tells them) there is a capacitor fix for a rebooting problem, but don't go into the details to find out it only applies to one specific situation.
 
My T2 fails to boot up and is stuck in a “Crash - Wait, Reboot in 10 … “ loop.
Try reprogramming the firmware from USB stick. We have had two instances recently (one mine) where the flash contents are getting tired and may read as the wrong value (so the code crashes), it being close to a decade since they were last programmed.
 
Indeed. Removing the hard disc to check is vastly easier than changing the capacitor.
Thanks for the positive advice, Owen. Yes, I did remove the hard disk first. I also tried reprogramming the firmware, but neither worked. I also read all the newbie and things everyone should know documents. I then read the troubleshooting documentation but somehow missed the significance of the System Flush image approach.

Typical. People read (or AI tells them) there is a capacitor fix for a rebooting problem, but don't go into the details to find out it only applies to one specific situation.

I accept that the symptoms that I was experiencing did not fully match those for the capacitor replacement scenario but they were close enough to make it worth a go. My mistake.

I reprogrammed the box with the System Flush image and this did indeed fix the rebooting problem. Unfortunately, the hard disk is no longer visible to the system and having run the box in maintenance mode then it confirms that the disk is not present. Looks like I have managed to break something (probably the mosfet or just the via on the board under the replaced capacitor connection). I don’t have an oscilloscope any more and without a circuit diagram I certainly won’t be spending further time and effort on this board. Again, my fault but I have learned a lesson and appreciate the helpful advice from all of you that replied. I know that it must be frustrating when you get asked the same questions over and over from newbies such as myself, particularly as the forums have been going for many years. I love my existing three T2 boxes and think that the CFW is amazing. Well done to all involved.
 
Did you try disconnecting the drive before you replaced the capacitor? It would have saved you a job...

Did you try measuring the voltages? I don't think I've ever seen anyone have a genuine PSU problem here.

'Install' the System Flush image in the same way you would a firmware image and then see what happens.

Apologies, I had intended to reply to you in my previous post. Thanks for responding and I have answered two of your helpful suggestions in that post, but as for the voltages then no, I didn’t measure them. I had a spare PSU and just swapped it in as a possible quick fix, more in desperation by that point than anything else. As you said, I don’t think that there have been any reports of power supply failures in the forums. Thanks again.
 
I accept that the symptoms that I was experiencing did not fully match those for the capacitor replacement scenario but they were close enough to make it worth a go.
No, they were not. You mistook a software crash-reboot cycle for a hardware loop. The HDD capacitor thing results in a hard reset, the (obvious) distinction being no time for any diagnostic messages.

The reason this is particularly important is that PCB rework is not risk-free. One does not casually start swapping components, particularly on an SM board, without having assessed alternatives first. Even if that doesn't bother you, it is a message which needs to be out there for the less experienced.

My step-by-step diagnostics linked in Post 2 could have steered you in the right direction.
 
Last edited:
I don't think I've ever seen anyone have a genuine PSU problem here.
Just to clarify that: I meant a power supply that was obviously not dead but giving wrong voltages.
There have been a (very) few instances of a blown ceramic capacitor on the PSU board, but that stops it working completely.
 
No, they were not. You mistook a software crash-reboot cycle for a hardware loop. The HDD capacitor thing results in a hard reset, the (obvious) distinction being no time for any diagnostic messages.

The reason this is particularly important is that PCB rework is not risk-free. One does not casually start swapping components, particularly on an SM board, without having assessed alternatives first. Even if that doesn't bother you, it is a message which needs to be out there for the less experienced.

My step-by-step diagnostics linked in Post 2 could have steered you in the right direction.

You’re absolutely right, and I would have avoided swapping components had I realised that my problem was different to that which occurred on my previous Box. Folks without the skills and experience should indeed be discouraged from doing what I did. Your step-by-step instructions for debugging are also excellent. I simply missed the point and got it wrong. Mea culpa.

There's a bit of a circuit diagram for the relevant circuitry here:

Once again, thanks Owen. Armed with the diagram I felt confident enough to have another look at the changes that I had made, and it is now working fine. I had broken a connection when replacing the capacitor (easily done when trying to desolder and lift SMDs as Black Hole has already pointed out), and I was able to reinstate it with some delicate solder work. The MOSFET and transistor were both undamaged.

Final recap:
1. Had I simply reprogrammed the box with the System Flush image, and then programmed the box with the custom firmware again, all would have been working fine.

2. I overlooked the above and wrongly assumed a hardware fault. I replaced the 4u7 SMD capacitor with a standard electrolytic. I broke a connection on the board in the process.

3. Having received advice in this thread I performed the reprogramming detailed in 1. above. The box then booted ok but the HDD was not being seen by the box.

4. Armed with the circuit diagram for the relevant area I was able to fault find and identify that there was a broken connection. I fixed the break and everything now works.

Suitably chastised, I will know better next time.
 
I've had the same problem and assumed my HDD had died, but thanks to this forum (again), this thread, and with some AI help it's working perfectly again.
Many thanks
 
Back
Top