Trouble with my Os Mio 4k receiver.

This Does Not seem to be a common problem with the MIO line of receivers. It would be nice to know Exactly what was wrong with it, but that will probably forever remain a mystery. At least you have a replacement on the way.
 
Ok, got my warranty replacement receiver back late yesterday. Was very cold from shipping, so let it sit overnight to get to room temp. I asked Brian to load TNAP 4.0 into slot 1, and TNAP 3.2 into slot 2. That way I can get it back up and running quick on 3.2, while I can take my time to setup 4.0 from scratch.

I have the receiver up and running on slot 2, set video settings, and it can see the attached 2TB harddrive with folders in it. It's hooked to my network by ethernet cable, and I set the original IP address, and can get to the WebIF screen just fine.

OK, so:

I have TWO backups for my receiver on the attached harddrive (that I use for recordings and such, it's 2TB's).

One is a FULL backup dated 20200817_1832, in a folder called: "fullbackup_osmio4k" which has a "osmio4k" folder inside of it, and in the root of it, files called "BackupSuite.log" and "imageversion"

the other is an interim backup when I loaded 3.2 and used my 3.0 Restore on it. That's in a folder called: "backup" and has these files inside of it: "autoinstall", "autoinstall5cfa000011d3" "PLi-AutoBackup.tar.gz" and "PLi-AutoBackup5cfa000011d3.tar.gz"

Can someone run me step by step through the RESTORE process again from a drive, because it's been quite some time since I've had to do one, and want to make sure I do it right the first time.

I'm thinking to run the FULL restore from the "full backup" first, since it's a bit older. Then, I can run the newer backup from when I installed 3.2 on 10/11/20. I'm unsure how to do it, and it gives me all sorts of warnings that make me jumpy, so I haven't gone completely through with it as of yet.

Thanks!
 
I need the enigma2 folder, located in /etc enigma2. Can you extract that folder from your backup files? You need to extract this folder form the rootfs.tar.bz2 file located in your back files. With the enigma2 folder, I can set you up a TNAP-4 image.
 
Here it is. I extracted it from that file you mentioned above using 7zip, and then zipped the Enigma folder using the same 7zip program.

Thanks!

Oh, and no big hurry for this. I restored the 10/11/20 interim backup for TNAP 3.2 using the regular Backup program, and I'm fine for now using that version as normal at the moment.
 

Attachments

Last edited:
el bandido said:
Download the image, multiboot or emmc.
Install the image.
Download the plugin
Install plugin
Those steps should restore it.
Click to expand...

Well, I downloaded and followed the steps above as you stated, using the multiboot image. TNAP 4.0 is running, BUT, none of my settings are there. It claimed to install the .ipk file, (though it did say "installing 0 of 0 packages") and I rebooted afterwards, but no difference. Even tried a power-plug plug restart, but the settings didn't load, it's all blank as a new image.

Can we try again, with the "2nd try" enigma zip I attached above? I extracted that one from the 10/11/20 backup.
 

Attachments

Last edited:
I'm all set! I remembered I had saved some info on how to use Putty to telnet to the receiver, and do the init 4, I then copied the 10/11/20 enigma folder over to the receiver replaced the default one, then did an init 3.

Receiver rebooted, and it's up and running on TNAP 4.0 with my settings!

Thanks again!
 
Hello ,

Sometimes you have to be careful when using the old settings after a blocking of the receiver.
We have reset the device, it is finally working again and we want to reset the old setting.
It should be taken into account that the blocking can come from the old backup.
It would be annoying to reblock the receiver. :sadtear:
have a good day
 
stephan94 said:
Hello ,

Sometimes you have to be careful when using the old settings after a blocking of the receiver.
We have reset the device, it is finally working again and we want to reset the old setting.
It should be taken into account that the blocking can come from the old backup.
It would be annoying to reblock the receiver. :sadtear:
have a good day
Click to expand...

It's a new warranty replacement receiver. The original MIO went bad all by itself for whatever reason, it had nothing to do with flashing an image, or restoring a backup.

All I reloaded yesterday over the base TNAP 4.0, was my user settings, nothing else. So, as far as I can tell, all is fine now.
 
Back
Top