So not "Nada" then? You works have seen a message on the front panel prompting you to press the button.
Anyway, if you are getting the flashrootfs message now, then it is currently upgrading.
So not "Nada" then? You works have seen a message on the front panel prompting you to press the button.
Wiz HQ wrote: ↑Mon Dec 09, 2019 12:33Download the Upgrade files here, please make sure you choose the correct model number:
T2 - https://beyonwiz.com.au/firmware/t2/bey ... 06_usb.zip
sonicblue wrote: Can't find any way around this so far.
I'll give that version a try and report back tomorrow.Grumpy_Geoff wrote: ↑Tue Jan 28, 2020 22:05I followed your steps.
Our T2 is still on 19.3 series "stable beta" 20190818 - it doesn't have that issue.
It was changed to always be visible a while back.sonicblue wrote: ↑Wed Jan 29, 2020 01:45Unrelated question: does 19.3 now not let you remove the EPG detailed info text at the top quarter of the screen when in the full screen EPG view (i.e pressing EPG on remote)? Because I can't seem to find a way to remove it, and on the previous version 16.3 I definitely had it removed.
Just on this one too, I would advise you to use a fixed DHCP assignment for the T2 instead of using a static address in the T2.sonicblue wrote: ↑Wed Jan 29, 2020 11:24The issue was that T2 sets the subnet mask to 0.0.0.0 by default, which I guess is interpreted as "all traffic is local" and therefore disables the network adapter altogether.
I either didn't notice it or forgot that it was the wrong subnet mask for my network (255.255.255.0).
MrQuade wrote: ↑Wed Jan 29, 2020 14:36It was changed to always be visible a while back.sonicblue wrote: ↑Wed Jan 29, 2020 01:45Unrelated question: does 19.3 now not let you remove the EPG detailed info text at the top quarter of the screen when in the full screen EPG view (i.e pressing EPG on remote)? Because I can't seem to find a way to remove it, and on the previous version 16.3 I definitely had it removed.
See this thread for more info.
sonicblue wrote: ↑Sat Feb 01, 2020 14:06I'm having a separate issue where some EPG events keep randomly disappearing from the EPG. Every now and then a few events will randomly become blank in both the graphical EPG and single EPG views. The start and end times are still there, but their titles are blank.
FTA.
No, because I saw that it only lets you reload it once per hour at most, and the problem occurs multiple times within an hour.
Yea, the community channels are a nightmare. guide will be fine one minute, though only 24 hours in advance, then completely blank an hour later. The intern probably takes care of it .
prl wrote: ↑Sun Feb 02, 2020 09:32My guess that the ABC is sending EPG items with small overlaps. The code that takes the EPG source (FTA or IceTV) and inserts it into the EPG cache removes overlaps by removing one of the two overlapping entries.
I have a speedup waiting for acceptance that takes advantage of the non-overlap condition. It reduces the time to insert a single EPG event from O(N) to O(log N) (where N is the number of events in the channel's EPG). It makes most obvious difference to the initial full IceTV EPG load when you restart the GUI. A full IceTV EPG load goes from O(N^2) to O(N log N).
It's already in the latest beta firmware.
It depends on your settings. Mine doesn't.
Ahh yep, good spot. My settings have all SD/HD and default resolutions set to the same 2160p50, so I didn't see the intermediate switch to the default rate.sonicblue wrote: ↑Wed May 20, 2020 12:07After some further testing, it seems the root cause of the unnecessary video mode reinitialisations on the V2, is that on channel change it insists on first setting the display mode to the global (fixed) resolution, even when autores is enabled, before autores finally sets it to the specified resolution. The T2 does not have this behaviour, which allows it to sidestep the issue altogether.
Just trying to write the recovery image to internal flash.
Have you tried a second power cycle? Leave it off for about 20 seconds just in case.
Yep, done both of those things
Strange, maybe your download or extraction went wrong. Maybe download a fresh 19.3. Definitely not normal to have it fail like that.
Code: Select all
md5sum
0512a1a0957829ae57ceddf512d2545b *beyonwiz-19.3-beyonwizt2-20191106_usb.zip
5ee30038ca19335b18a1afb426278909 *beyonwiz-19.3-beyonwizt3-20191106_usb.zip
305903af8871d5bc8b5c1084791a9745 *beyonwiz-19.3-beyonwizt4-20191106_usb.zip
9bb0b5c81e30e7eebc6eff2a5b253de3 *beyonwiz-19.3-beyonwizu4-20191106_usb.zip
5844f60f974e694f89629b8ec4bf3cf7 *beyonwiz-19.3-beyonwizv2-20191106_usb.zip
sha1sum
3fca47d9631a2de90770e14d6b51731e09491eea *beyonwiz-19.3-beyonwizt2-20191106_usb.zip
7c88e7dbb956c63ed451830c1bb4c482f0c82787 *beyonwiz-19.3-beyonwizt3-20191106_usb.zip
3e69e24fc6cf901ea92819b50d31ff19d5e26556 *beyonwiz-19.3-beyonwizt4-20191106_usb.zip
dcf1f55aaa30eec2765c3b3fe72df553c1b4abde *beyonwiz-19.3-beyonwizu4-20191106_usb.zip
ed8ad1351ec611d949694a63b26a5794eed27ff9 *beyonwiz-19.3-beyonwizv2-20191106_usb.zip
sha256sum
cdfdb838844323159dd78623ff5972cd34d0cf1ea50353519a8ecc9df492ed38 *beyonwiz-19.3-beyonwizt2-20191106_usb.zip
9662f655e130e28be7d5f76501ca813de0c076d1431b1a31661f6740b105c5b6 *beyonwiz-19.3-beyonwizt3-20191106_usb.zip
cd85bdafa8b8d12a26df85e6051adaffd4399710f7a3f3b73775451cb509bad2 *beyonwiz-19.3-beyonwizt4-20191106_usb.zip
50aee35f0410ca35be9d708299953f09ecf4152e2365dd339e2798fc1710a2f1 *beyonwiz-19.3-beyonwizu4-20191106_usb.zip
3d6f3a013f39c8a5edb363bf54071f8ed1c05b2f6ea9100cd99de85058763813 *beyonwiz-19.3-beyonwizv2-20191106_usb.zip
I was just using an off the shelf 32GB Sandisk USB3.peteru wrote: ↑Mon Jun 01, 2020 16:42Sounds like the flash process went wrong.
Try not using the Beyonwiz supplied USB flash drive for the upgrade. One of the batches of USB drives that Beyonwiz bought appears to have had some fake USB drives thrown in by the Chinese manufacturer. The USB drives were written in such a way that as supplied the firmware on the USB drive was perfectly fine. However, writing new files to the same USB drive could result in corrupted files which, when flashed, can result in unbootable firmware. The bigger the firmware, the more risk of this happening. The bigger 19.3 firmware file is more susceptible to this problem than the smaller files in previous firmware images.
If you are interested in testing your USB drive, f3fix works.
https://fight-flash-fraud.readthedocs.io/en/latest/
Once you have used that tool to limit the USB drive capacity to what it can actually do, it's OK to use those USB drives for the firmware upgrades.
That might be your problem. Wizzes can be very picky about which USB sticks they will recognise when flashing firmware. Anything that's USB3 is probably waay too new to work with the Wiz.
Perhaps, but that doesn't really explain why either of the USB's I tried, (one new, one old) allowed 17.5 to be flashed back successfully does it?vader1111 wrote: ↑Tue Jun 02, 2020 00:57That might be your problem. Wizzes can be very picky about which USB sticks they will recognise when flashing firmware. Anything that's USB3 is probably waay too new to work with the Wiz.
The Lexar S50, available from Woolworths, is one which is known to work reliably:
https://www.woolworths.com.au/shop/sear ... 0usb%20s50
tb123 wrote: ↑Tue Jun 02, 2020 11:44Perhaps, but that doesn't really explain why either of the USB's I tried, (one new, one old) allowed 17.5 to be flashed back successfully does it?
Also, the fact that I did manage to get it to boot once with 19.3 installed (by flicking the power off and on) but not again would suggest something more intermittent or flaky, wouldn't it?