68 fails to install. Is there an error log to see what's wrong?

fletch

It's been trying to update for the past couple of days. It fails but offers no explanation. Thanks.

EdAtlanta

I have two units and one of them auto installed to V68 the first time it was available. The other unit took 2-3 days before it finally updated. Both are set to update at 4:00am local time and they are on different wife sources.

EdAtlanta

After my second one finally updated to v68 and several hours of usage later, I changed profiles and it shut off completely. I tried all of the appropriate things to get it back on. Long press on the power button, changed usb cables, changed the power supply and made sure the one I had was 2.0a, press both buttons for a long press and nothing. The next morning it failed to start as scheduled at 3:00am, but when I pressed the power button it booted, but shut off again shortly after when changing profiles again. So I d/l the recovery program and ran it. It now works fine after setting all up again, but I'm not going to install a beta on this one again for a while. It recovered on v61. Why would one of my two os4's run on v68 and one locks up per the description above?

HA2NON

Make sure you don't switch profiles or reboot after updating to a new firmware version until the unit has not been running for at least 1 minute otherwise it will revert back to the previous firmware version. If you press and hold both buttons the device will enter into bootloader mode and won't operate until you press and hold the power button for at least 8 seconds.

EdAtlanta

HA2NON

It had been over 1 minute since the update to v68. Several hours in fact. When I changed profiles it totally shut down. No led function. It would not turn back on with the power switch or enter bootloader with both buttons. It was essentially a brick. After recovery it is working fine now on v61, but I'm concerned about trying a beta again. I know how to recover, just don't want to have to it. And my second OS4 is running fine on v68.

HA2NON

Please send us the exported configuration profiles which cause issues to info@sharkrf.com

Please don't press and hold both buttons as it is only used for entering bootloader mode. In bootloader mode the status LED will not be lit and you may think the unit is dead. The only way to exit bootloader mode is to press and hold the power button for at least 8 seconds. That's why pressing and holding both buttons is not described (and not recommended) in the user manual.

EdAtlanta

I didn't save the profiles before so they disappeared when I had to recover the os.4 pro. The problem it has now is it won't install v.68. I have it set to d/l betas at 4:00am daily and it failed to do that this morning. It's UID: 60499FE9. My second unit does runs v.68 fine, but not this one. My second one is UID: 03B9FF80.

Thoughts?

Thank you.

HA2NON

What happens if you click on the upgrade button manually?

EdAtlanta

Trying manual upgrade yesterday, 4-2-24, d/l ok, but did not actually update to v68 Stayed on v61.

I just tried the manual update just now, 4-3-24 4:17am US Central Daylight Time and it did update to v69.
It seems v68 and this particular os4 didn't like each other. This is the first update problem I have ever had as well as the first requirement for the recover procedure. I'm sure you guys learned something about v68 and thus we have v69. I'm sure I wasn't the only one.

Great product guys. Thanks.

EdAtlanta

After talking over the os4 with the new v69 firmware all seems to be good. I finished a 30 minute or so qso cross mode c4fm to dstar with a friend in Georgia. I then rebooted the os4 and it is definitely still on v69.

Thanks again.