ok...sim2
than, as you said your receiver boots in #84b . is the image that are you trying to load #84b too?
because here Latest Secondstage Bootloader For SIM2 TEAM for clone Dm800se & SIM2.10 card the last one looks #84d and i think most images use that...
δε νομιζω οτι εχει να κανει με το ποσες μερες εχεις να κανεις ενημερωση... αυτο το πακετο οπως και να εχει, δεν ερχεται απο το feed του image.
για δοκιμη μπορεις να απεγκαταστησεις το υπαρχων oscam και να εγκαταστησεις αυτο απο το feed του image. μετα ενα reboot ( και εαν το χρειαζεσαι, κρατας το υπαρχων oscam-emu.bin για να το ξαναπερασεις)
το πακετο oscamwebif... δεν το βλεπω να ειναι δικο μας...
η εχει περασει με καποια εκδοση oscam που προσπαθησες να βαλεις... η δεν ξερω πως βρεθηκε εκει.
επισης... απο το image, δεν προκειται να παρει update, μια και δεν υπαρχει μεσα...,
δεν ξερω γιατι το ζηταει...
μηπως για καποιο λογο ειχες κανει χειροκινητα εγκατασταση καποιο πακετο owif ?
edit: ακυρο... oscamwebif εγραψες...
it is an original, or clone receiver?
if it is an original, you may do not have the last secondstage, and all the (newest) images has been build in that.
here is a section with 800se original secondstage, try to upgrade to the last one first, and than try to flash image...
Latest Secondstage Bootloader For DM800 SE opendreambox-2.0.0
(of course, you do not use it, if your receiver isn't original)
are you sure that your receiver is" dm800 sim210" ?
it may be "dm800se sim210" or something else?
as i remember, there was a tool for this (wrong image flashing) and if i am not wrong it called "yassinov" or something.
in other way, i think you can flash a correct image (including the correct secondstage loader) from serial port...
i had a look in openeight team repository, and there isn't any image for this model.
and as openeight is a team that supports octagon models... i am not sure if this receiver can load e2...
yes...
no... nothing is removed
but in my case,oscam is always start after reboot...
the softcam manager will be in blue button (extensions)
but ... possibly it didn't installed . try to do it by telnet, or the tools that i wrotte above. if you try to install it from "software manager/install local extension" many times it fails...
i just returned home, and i did a boot in tnap 3.2 ...
there are installed in plugins, the "dream-explorer" and the "file commander" , and you can install any .ipk package through those tools...
i do not remember now, if there is any panel for installing...
place it in /tmp and than (for all .ipk files)
cd /tmp ( to go in /tmp directory)
opkg install *.ipk (to install any .ipk there is in /tmp)
hd51 is an "arm" cpu receiver, so if i am not wrong, the ccam which supports this arch , is 2.32 and after.
in any case... oscam-emu can do a lot more from this...
as i know, no it is not working...
what the oscam log shows?
the "softcam support" is included in the rar.
also, before step 3, you have to correct attributes in the files that i wrotte above.
than reboot (to reload the image the files)
and than go to softcam manager, and select the cam...
Display Moreyes, i absolutely understand the reason...
but, (i do not have use neoboot in the past) if neoboot works in the way as openmultiboot etc... , than you will meet a few problems, as there is a change in the receiver (from 64bit to 32bit) and as i know (maybe i am wrong) there are kernel limits in those multiboot tools...
thanks for your information and for someone like me im a noob in enigma world so i asked a lot excuse me
so what i understanding from what u said the images not will fully function like the one in the internal flash .
i thought it will be like barry allen for dreamos
as i said, i am not sure about this plugin, i just suppose that it works like openmultiboot.
in receivers internal multiboot,every image is independent from each other...(so, no restrictions)
in openmultiboot (and othe common tools) , the multiboot image, is using data, from the flash (master) image. in that case, there are restrictions in the images that are installed in multiboot...(they must use all same kernel).
in any case, in the old past, in my most receivers, i was big "fun" of multiboot. finally i was using 1-2 images, and all the other, just "was" there without any reason (I used them rarely, I did not upgrade them etc ...)
yes, i absolutely understand the reason...
but, (i do not have use neoboot in the past) if neoboot works in the way as openmultiboot etc... , than you will meet a few problems, as there is a change in the receiver (from 64bit to 32bit) and as i know (maybe i am wrong) there are kernel limits in those multiboot tools...
