PDA

View Full Version : Help Recovering My OS MIO 4K From a Bootloop



navagator
01-12-2024, 03:35 PM
Last night I was watching a Pluto channel and when it went to a commercial the screen turned black as it usually does, I moved the channel up and down in order to restore the video. But instead of the video coming back up a green screen came up with this message:

We are really sorry. Your set top box encountered a software problem and needs to be restarted. Please send the log file/temp/enigma2_crash.log to the OpenPli forum. Your STB restarts in 10 seconds.

Close failed in the object destructor. ID Error (Error22) Invalid argument

Close failed in the object destructor. ID Error (Error22) Invalid argument

I was using TNAP 4.2 when the receiver crashed but I was able to reboot in TNAP 4.0 by pushing the menu button repeatedly after unplugging and plugging the receiver back in. One thing I noticed when it was looping was that just for a brief second a popup window came up to tell me it was going to starting a timed recording. After I was able to boot up in 4.0 I checked my recordings and saw that it did try to record Newhart many times, every time it tried to bootup I guess. I don't know if the timed recording has anything to do with the crash or not?

Another thing I noticed is, if I try to do a normal restart while in TNAP 4.0 it boots back up into 4.2.

Do I need to reinstall 4.2 or is there something else I can do to fix this issue? I do have a backup of 4.2 that I did a while back on a usb stick if I need it.

Thanks

el bandido
01-12-2024, 07:26 PM
Really no clue without seeing the crash log. Then maybe no clue with the log.

Sometimes when rebooting between images, the receiver will boot into something else on a reboot instead of the current slot. To fix this, go into multi-boot and reboot to the current slot. Doing this one time should fix it.

For the rest of the stuff, try reloading the image and see if that fixes it.

navagator
01-17-2024, 04:51 PM
Thank you.

I didn't have to reload the image. I unplugged the receiver, inserted the usb stick with 4.2, plugged it back in and 4.2 loaded successfully.