I asked how I flash it, not from where I download it.
Posts by abu baniaz
-
-
I have attached the file to your post instead of just a link.
How do I flash this recovery file please? I have booted into recovery mode and selected the file, but it says it's invalid.
-
Like you normally do with any receiver.
Receiver connected with ethernet cable to router
PC connected with ethernet or wifi to router.
Download your chosen image
Extract/unzip the image
Restart receiver in recovery mode.
Enter IP address of receiver in your web browser on PC
See here:
-
I just noticed when I went to tuner c and selected configuration mode advanced my SRC had changed from 7 to 1 and frequency has changed from
1257 to 957 this must have been automatic setting that did that.
I am posting this separately to avoid conflation and confusion.
There is no such thing as "Automatic setting". "FBC Automatic" is "internal loop-through" when required, this is the same function as on Solo 2, TM Nano 2 super, TM 3t Combo and other 7356 SOC. "FBC Automatic" does not set FBC tuners automatically. It's a rubbish name that should be changed IMO.
-
Changes made to Freesat provider files. So should be fine now once people update the provider file and run again.
https://github.com/oe-alliance/AutoBouquetsMaker/commit/7c40d4361d719fce6faf6aa1324be8d19890c256
https://github.com/oe-alliance/AutoBouquetsMaker/commit/c51cbfae49e4b60dc29fc2582bfff78d748a0439
-
Yes, you can flash/install ATV 7.6.
Why do you think you cannot?
-
You cannot install chkroot multiboot. It is not available to install. It is built in the images that support it.
If you want to use chkroot multiboot, enable it ( turn it on).
If you do not want to use chkroot multiboot, you don't have to do anything.
-
Have you configured your tuner to match the dish/lnb you have? Please post screenshots.
Have you scanned for channels?
Which options did you use to scan? Pease post screenshots.
Did the scan find channels?
-
There is an issue that needs to be investigated. This is an issue following ABM scans if you enable both Freesat and Sky UK.
That being said:
1. There is no need for you to scan using the scanning functions in enigma2 for 28.2. Just enable the not-indexed option in ABM so that it adds channels in test mode.
2. You don't need to run ABM or Freesat and Sky UK.
3. Manual scan gives you more options than Automatic scan.
4. You dont need to scan UK Terrestrial unless there are transponder changes. These are not very common and they advertise these on the channels.
5. You should disable the Cable Tuner if not done so already. Alas, ATV have a weird way of configuring hybrid tuners.
-
Your tuner configuration is not the issue. Please do not post/mention anything about those as it will just complicate things.
You said "I have rescanned many times". Pleas explain exactly what options you select for scanning. Do you use "automatic scan" or "manual scan". Please show the options you are using.
There is no such thing as "Sky Freesat". "Sky UK" is one provider. "Freesat UK" is another provider. Your issue might be caused by using two providers in ABM that have different names on the SI tables for the same channels. In this case "Blaze" and "Really". We will have to add name hacks for them so the names are identical. Please upload your debug log that contains details of your ABM run so we don't have to go through 20 questions to establish what option you are using.
-
FBC Automatic = Internal loop-through when required.
There is nothing automatic about it. You are loosing tuner independence by selecting it.
The N/A issue comes about because the service in the bouquet doesn't exist in lamedb or the name has changed. As an example, Sky uses one name and Freesat uses different names on SI tables.
Scanning does not affect update bouquet contents.( I'm not talking about ABM). A screenshot of the scanning options used would be ideal as well as the ABM options.
-
Your question are specific to your personal requirements, not to this generic thread.
As SNP strips characters out, how is a computer meant to read a picon name and guess what has been stripped out?. As I mentioned to you in PM and on the other forum, you don't need to rename from SNP to UTF8SNP. Both naming systems as well as SRP are supported by Enigma2. If you are determined to convert them, perhaps a different thread is better. You will have to use the output from missing picon to create commands to rename files. But you run the risk of renaming files that will be needed later in the process. You are duplicating files with different filenames. You wanted to reduce number of files but doing the opposite. As I said in PM, you are better off having symlinks instead of duplicating file names.
-
A script to rename SRPicons to UTF8SNPicons by Huevos is here
https://gist.githubusercontent.com/Huevos/17a267b68851319f48c4dcd272882b03/raw/2affe9daa30c183378366ff778999aa14b2901a0/picons-rename.py
Download and transfer to /hdd. Ensure it has 755 properties
Invoke by issuing following command
python /hdd/picons-rename.py
It will create the renamed picons in /tmp directory of your receiver
-
So that makes 5 versions.
Anyway, dont stop making improvements to your version. Your users will know how to handle the issues that will arise.
-
Version number of your version is not the point being made. There are now 4 versions of the plugin.
OpenPLi version
OE-Alliance version (There is no open ATV version)
Dorik version
Your version.
To avoid issues, you should really install in a different directory to the existing ones from plugin servers.
It's a shame you want to go your own way instead of adding your improvements to existing versions. Anyway, that's your choice.
-
Can you please confirm how many channels you get when performing a manual scan of 19.2?
In manual scan, ensure you select the correct tuner, change the type of scan to single satellite, not just one Transponder.
-
You won't be able to connect to the receiver if it's bootlooping. This is why I said to stop Enigma2 first.
However, the Duo 4K SE has plenty of internal flash, so I am probably wrong about it filling up. You can find out the reason why it's not booting by starting Enigma2 in console mode with following commands:
init 4
enigma2
Were you using Kexec multiboot? Were you using any other multiboot plugin?
Might be easier to flash by USB again if you can't make any progress quickly.
-
You probably filled up the internal flash memory. You should still be able to telnet and FTP into it.
Stop Enigma2 by issuing this command with Putty/Terminal
init 4
Using FTP such as FileZilla, delete the picon folder
Restart it with following command in Putty
init 3
-
That's not a helpful answer .
Menu , Information, About.
This should show you the image that is on there at the moment. Also, what exactly do you want to backup?
-
My rescue loader is version #103
Is the latest one? If not how, do I install the newest one please?
I have tried
Code
Display MoreWelcome to OpenViX for dm900 openvix 6.8 dm900 dm900 login: root root@dm900:~# update-rescue -v Warning: Could not read CA! Warning: Please consider updating your rescue loader! [*] Downloading 'http://dreamboxupdate.com/download/recovery/dm900/release/rescue-image-dm900.bin.sig' % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 310 100 310 0 0 4396 0 --:--:-- --:--:-- --:--:-- 4428 [*] Downloading 'http://dreamboxupdate.com/download/recovery/dm900/release/rescue-image-dm900.bin' % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 11.1M 100 11.1M 0 0 18.0M 0 --:--:-- --:--:-- --:--:-- 18.0M [*] Verifying signature of 'rescue-image-dm900.bin' gpgv: Signature made Mon 02 Dec 2019 21:50:15 GMT gpgv: using RSA key A8A58D40B77248097CFA0E2EF02A0F767DA27561 gpgv: Good signature from "Dreambox DM900 Recovery <dm900@recovery.dreambox.de>" [*] Writing rescue image to flash Warning: Could not read CA! Warning: Please consider updating your rescue loader! Manufacturer ID: c2 Memory type : 20 Memory density : 19 read id ok comparing 2846 sectors... nothing to do [*] Done. root@dm900:~#
