• The forum software that supports hummy.tv will be upgraded to XenForo 2.3 on Wednesday the 20th of November 2024 starting at 7pm

    There will be some periods where the forum is unavailable, please bear with us. More details can be found in the upgrade thread.

Non-destructive way to test USB stick compatibility?

mr-b

Member
Hi

I'm testing out a USB stick to post to my mother who is going to try and install CFW (gulp). Luckily she has another Humax as a backup, albeit suffering intermittent resets.

I want to try out various sticks to verify compatibilty, and it seems the only way to do it is to try a CFW install or system flush "firmware" update.
My Humax is already setup wth CFW, but I'm guessing that at least one of these methods will delete all my settings (Humax and package).

How can I restore the settings? Or is there a non-destructive way of testing the USB stick?
I've looked for backup methods but couldn't find anything for settings, except for the schedule.
 
How can I restore the settings? Or is there a non-destructive way of testing the USB stick?
Reinstalling the loader is quick, pretty safe and will test whether the USB memory stick is detected. NB reinstall the same loader version as the box is currently running to be on the safe side. I am sure af123 uploaded the full set somewhere but can't find the link. If you send me your email address and required loader version I can send it to you.
 
Thanks will give that a try.
Just for peace of mind, is there a way of backing up any settings?
 
Just for peace of mind, is there a way of backing up any settings?
Not "back up" as such, but configurable via custom firmware:

https://hummy.tv/forum/threads/is-there-a-good-time-to-retune.7624/post-103888
For HD/HDR-FOX CF users, there is now the boot-settings package which can apply a range of user-specified configuration options at each and every boot. In the context of the Restore Factory Defaults operation, this means the user can pre-configure their preferences and they will be re-applied automatically if the user reboots after the factory reset - overriding the default settings.
 
Ok - it was just that the loader page mentioned " there is a very small potential risk of bricking the box... " [eek].
But BH's link is a useful checklist of things to photo, as it's important to keep everything the same for my mother!
 
" there is a very small potential risk of bricking the box... " [eek].
There's always a risk - and the loader is the only bit that is critical (a corrupt loader can't load a new loader). I don't think anybody has actually bricked their box though.

However, personally, I would not take even the slightest risk where it wasn't necessary. It's not like you need to update your loader. Although it takes longer, it is safer to test a UPD by doing a firmware update rather than a loader update. I suspect you could interrupt the short "downloading" phase without consequences, and avoid the long "programming" phase.

I'm not convinced the System Flush is an adequate compatibility test.
 
Hmm, I've tried 3 different USB sticks 1/2/8GB, formatted with FAT or FAT32, both front and back USB ports, all with the same version of loader renamed HDR_FOX_T2_upgrade.hdf but nothing seems to happen on boot - either on screen or front panel.
Will it definitely show something?
 
Last edited:
Hmm, I've tried 3 different USB sticks 1/2/8GB, formatted with FAT or FAT32, both front and back USB ports, all with the same version of loader renamed HDR_FOX_T2_upgrade.hdf but nothing seems to happen on boot - either on screen or front panel.
Will it definitely show something?
The Humax website suggests firmware updates be done with a FAT32 formatted usb stick.
The only thing I can suggest will be use an older USB drive, make sure it only has 1 partition and is FAT32.
Eg as a guess, 4GB or smaller.
From what I remember firmware or loader flashing will show progress displays on the front panel and also on the TV HDMI.
It should work on either front or back USB.
If necessary, make sure file is renamed to - hdr_fox_t2_upgrade.hdf
 
Last edited:
Hmm, I've tried 3 different USB sticks 1/2/8GB, formatted with FAT or FAT32, both front and back USB ports, all with the same version of loader renamed HDR_FOX_T2_upgrade.hdf but nothing seems to happen on boot - either on screen or front panel.
How are you formatting the USB memory sticks? Are you allowing the Humax to go fully to sleep (disk stop spinning) before attempting the update?
Will it definitely show something?
Yes.
 
Are you allowing the Humax to go fully to sleep (disk stop spinning) before attempting the update?
I don't bother with all that - I just flick the switch at the back. The point is that the update detection occurs during cold boot (when you see the Humax splash screen), not warm start (when you don't).
 
Curiouser and curiouser ...
Toggling the switch vs pressing the power button when on red disc, has definitely changed something. I took my gnarliest 1GB stick formatted with FAT32 and after using the rear switch, it now boots saying "System Start" but the bright blue circle goes to mid blue. The TV goes to no signal detected (I've pulled the AV amp out of the equation too just in case) and I can hear disk activity. Front panel is blank. Then after 30sec it shuts down with the red disc. Press the power button and it boots normally with bright blue disc.

It turns out my vague memories of all this years ago being an utter PITA were correct!
Any ideas what it's doing?

E2A I'm using MiniTool Partition Wizard to format the drives as Windows sometiems wont; let you choose FAT32. And yes I was letting the disk spin down and system power off.
 
Last edited:
Any ideas what it's doing?
No.

Rather than use a loader image where you are not sure what to expect (and neither am I), use the firmware image. So far as my experience goes: either it will start the firmware update, or it will boot to operational - nothing else.

E2A I'm using MiniTool Partition Wizard to format the drives as Windows sometiems wont; let you choose FAT32.
That's a worry. Use a proper DOS tool in preference, Windows can make "incompatible" FAT32, especially Win10, and even corrupt it just by plugging it in.
 
I thought I had the smoking gun in that my USB sticks were all GPT, and so I converted them to MBR, but no dice.
Will investigate creating bootable DOS via Rufus tomorrow. What century are we in again?
 
Back
Top