Posts by yinyang

    final version here, {because I made some error, of editing }
    ####################################################
    ##################################################################################
    #!/bin/sh
    ###############################################################################


    if ! ps x |grep -v grep |grep -c /usr/bin/oscam_r5893 >/dev/null


    # example { if ! ps x |grep -v grep |grep -c /emu/oscam/oscam.x86 >/dev/null }
    #/usr/bin/oscam_versionexxxx
    #also take attention to the path to Oscam binary !!!!!!!


    then


    # oscam start or restart


    /usr/bin/killall -9 oscam_r5893
    /usr/bin/oscam_r5893 &


    #/usr/bin/oscam_versiunexxxx
    #also take attention to the path to Oscam binary !!!!!!!



    echo `date "+%d/%m/%y %R Oscam NOT working , restarting...."` >> /var/log/oscam.check



    # This part above will check if there is NO oscam process running.
    # And if this condition it truth, it will start it and write to log.
    # Log entry will contain time stamp and reason of execution (process not working)
    # If first condition in not truth (oscam was running), go further to next condition.


    elif


    tail -8 /var/log/oscam.log |grep -v grep |grep -c ins40 >/dev/null


    then


    #oscam restart
    /usr/bin/killall -9 oscam_r5893
    /usr/bin/oscam_r5893 &


    #/usr/bin/oscam_versiunexxxx


    echo `date "+%d/%m/%y %R ins40 error detected"` >> /var/log/oscam.check


    elif


    tail -8 /var/log/oscam.log |grep -v grep |grep -c deadlock >/dev/null


    then


    #oscam restart
    /usr/bin/killall -9 oscam_r5893
    /usr/bin/oscam_r5893 &


    #/usr/bin/oscam_versiunexxxx


    echo `date "+%d/%m/%y %R deadlock error detected"` >> /var/log/oscam.check



    # Those 2 conditions will look for 2 common errors in Oscam: "ins40" and "deadlock"
    # If last 8 lines of your oscam.log contain any of those errors, it will restart oscam.
    # Log entries will include the exact reason of restart.
    # ins40 error is random error that will keep oscam running but no CWs returned.
    # deadlock is older error that appear if you use CCcam protocol in oscam.server


    else


    echo " Oscam still ok 2 "
    #echo " Oscam still ok 2!" >> /var/log/oscam.check
    echo `date "+%d/%m/%y %R Oscam still ok 2!"` >> /var/log/oscam.check



    # If oscam passes all conditions and all is OK, it will simply echo "Oscam still OK 2 !"


    fi



    ##################################################################################
    #!/bin/sh
    ###############################################################################


    if ps x |grep -v grep |grep -c usr/bin/CCcam_2.1.3 >/dev/null
    #if ps x |grep -v grep |grep -c CCcam_2.1.3 >/dev/null


    then


    echo "CCcam OK 3"
    #echo "CCcam OK 3" >> /var/log/CCcam.check
    echo `date "+%d/%m/%y %R CCcam OK 3"` >> /var/log/CCcam.check


    else


    echo "CCcam restarting"
    #echo "CCcam restarting" >> /var/log/CCcam.check
    echo `date "+%d/%m/%y %R CCcam restarting... "` >> /var/log/CCcam.check


    /usr/bin/killall -9 CCcam_2.1.3
    /usr/bin/CCcam_2.1.3 &


    fi


    ######################
    ####End of script ####
    ######################




    ####################################################
    Tested, and Works well
    22/06/13 21:34 Oscam still ok 2!
    22/06/13 21:35 Oscam still ok 2!
    22/06/13 21:36 Oscam NOT working OK
    22/06/13 21:37 Oscam still ok 2!
    22/06/13 21:38 Oscam still ok 2!
    ................
    22/06/13 22:23 Oscam still ok 2!
    22/06/13 22:24 Oscam still ok 2!
    22/06/13 22:25 Oscam still ok 2!
    22/06/13 22:26 Oscam still ok 2!
    22/06/13 22:27 Oscam still ok 2!
    22/06/13 22:28 Oscam still ok 2!
    22/06/13 22:29 Oscam still ok 2!
    22/06/13 22:30 Oscam still ok 2!
    22/06/13 22:31 ins40 error detected
    22/06/13 22:32 Oscam still ok 2!
    22/06/13 22:33 Oscam still ok 2!


    ...............

    #!/bin/bash


    #if ! ps x |grep -v grep |grep -c /emu/oscam/oscam.x86 >/dev/null


    if ! ps x |grep -v grep |grep -c /usr/bin/oscam >/dev/null


    then


    # oscam start


    /usr/bin/oscam_5893 &


    #/usr/bin/oscam_versiunexxxx
    #also the path to Oscam binary


    echo


    `date "+%d/%m/%y %R process working OK"` >> /var/log/oscam.check



    # This part above will check if there is NO oscam process running.
    # And if this condition it truth, it will start it and write to log.
    # Log entry will contain time stamp and reason of execution (process not working)
    # If first condition in not truth (oscam was running), go further to next condition.


    elif


    tail -8 /var/log/oscam.log |grep -v grep |grep -c ins40 >/dev/null


    then


    #oscam restart
    /usr/bin/killall -9 oscam_r5893
    /usr/bin/oscam_r5893 &


    #/usr/bin/oscam_versiunexxxx


    echo


    `date "+%d/%m/%y %R ins40 error detected"` >> /var/log/oscam.check


    elif


    tail -8 /var/log/oscam.log |grep -v grep |grep -c deadlock >/dev/null


    then


    #oscam restart
    /usr/bin/killall -9 oscam_5893
    /usr/bin/oscam_5893 &
    #/usr/bin/oscam_versiunexxxx


    echo


    `date "+%d/%m/%y %R deadlock error detected"` >> /var/log/oscam.check



    # Those 2 conditions will look for 2 common errors in Oscam: "ins40" and "deadlock"
    # If last 8 lines of your oscam.log contain any of those errors, it will restart oscam.
    # Log entries will include the exact reason of restart.
    # ins40 error is random error that will keep oscam running but no CWs returned.
    # deadlock is older error that appear if you use CCcam protocol in oscam.server


    else


    echo " still OK 2 " # you can select your option , with date or without date
    echo " still OK 2!" >> /var/log/oscam.check
    echo


    `date "+%d/%m/%y %R Oscam still Ok 2"` >> /var/log/oscam.check



    # If oscam passes all conditions and all is OK, it will simply echo "Oscam still Ok 2" or you can select the version with date + hour


    fi


    #######################
    Script was tested and works,....
    see here



    still OK 2!
    22/06/13 15:24 Oscam ok 2
    still OK 2!
    22/06/13 15:25 Oscam ok 2
    still OK 2!
    22/06/13 15:26 Oscam ok 2
    still OK 2!
    22/06/13 15:27 Oscam ok 2
    still OK 2!
    22/06/13 15:28 Oscam ok 2
    still OK 2!
    22/06/13 15:29 Oscam ok 2
    still OK 2!
    22/06/13 15:30 Oscam ok 2
    still OK 2!
    22/06/13 15:31 Oscam ok 2
    still OK 2!
    22/06/13 15:32 Oscam ok 2
    still OK 2!
    22/06/13 15:33 Oscam ok 2
    still OK 2!
    22/06/13 15:34 Oscam ok 2

    Script with Feedback , monitor OSCAM , and CCcam
    works like a clock,...



    #############################################
    #!/bin/bash
    #############################################


    process=`ps auxwww | grep oscam | grep -v grep | awk '{print $1}'`


    if [ -z '$process' ];


    then


    echo "Couldn't find oscam running. Restarting server-binary"
    echo "Couldn't find oscam running. Restarting server-binary" >> /var/log/oscam.check
    #nohup /usr/bin/oscam_r4396 >> /var/log/oscam.log &


    /usr/bin/killall -9 oscam_r5893
    /usr/bin/oscam_r5893 &



    else


    echo " OK 1!" >> /var/log/oscam.check
    echo "oscam is still OK!" #aceasta linie o afiseaza doar pe Ecran, prima are calea spre folder oscam.check


    fi




    ##################################


    founds=`tail -10 /var/log/oscam.log | grep "ins40" | wc -l`
    founds2=`tail -10 /var/log/oscam.log | grep "classD0" | wc -l`
    founds3=`tail -20 /var/log/oscam.log | grep "(-2)" | wc -l`


    if [ $founds -gt 3 ] || [ $founds2 -ge 1 ] || [ $founds3 -ge 1 ]


    then


    echo "Error found, restart Oscam";
    echo "Error found, restart Oscam" >> /var/log/oscam.check
    /usr/bin/killall -9 oscam_r5893
    /usr/bin/oscam_r5893 &


    else


    echo "oscam still ok 2";
    echo "ok 2!" >> /var/log/oscam.check


    fi



    #################


    if ps x |grep -v grep |grep -c usr/bin/CCcam >/dev/null


    #or


    #if ps x |grep -v grep |grep -c CCcam_2.1.3 >/dev/null
    #if ps x |grep -v grep |grep -c CCcam >/dev/null


    then


    echo "CCcam ok"
    echo "CCcam ok" >> /var/log/CCcam.check



    else


    echo "CCcam restarting"
    echo "CCcam restarting" >> /var/log/CCcam.check



    /usr/bin/killall -9 CCcam_2.1.3
    /usr/bin/CCcam_2.1.3 &


    fi

    small modifications to first script ,....


    process=`ps auxwww | grep oscam | grep -v grep | awk '{print $1}'`


    if [ -z '$process' ];


    then


    echo "Couldn't find oscam running. Restarting server-binary"
    echo "Couldn't find oscam running. Restarting server-binary" >> /var/log/oscam.check
    #nohup /usr/bin/oscam_r5893 >> /var/log/oscam.log &


    /usr/bin/killall -9 oscam_r5893
    /usr/bin/oscam_r5893 &



    else
    echo " oscam is still OK 1!" >> /var/log/oscam.check
    echo "oscam is still OK 1!" #aceasta linie o afiseaza doar pe Ecran, prima are calea spre folder oscam.check


    fi



    with this correction, both scripts will work separate , like a clock,...
    bye



    oscam is still OK 1!
    oscam is still ok 2!
    oscam is still OK 1!
    oscam is still ok 2!
    oscam is still OK 1!
    Error found, restart Oscam
    oscam is still OK 1!
    oscam is still ok 2!
    oscam is still OK 1!
    oscam is still ok 2!
    oscam is still OK 1!

    ###########################################################################
    #!/bin/bash
    ###########################################################################


    process=`ps auxwww | grep oscam | grep -v grep | awk '{print $1}'`


    if [ -z '$process' ];


    then


    echo "Couldn't find oscam running. Restarting server-binary"
    echo "Couldn't find oscam running. Restarting server-binary" >> /var/log/oscam.check
    nohup /usr/bin/oscam_r5893 >> /var/log/oscam.log &


    else


    echo "oscam is still OK 1 !" ############################## #this will be on TV screen only
    echo "oscam is still OK 1!" >> /var/log/oscam.check ############# this will be in file oscam.check



    fi


    ####################################################################


    founds=`tail -10 /var/log/oscam.log | grep "ins40" | wc -l`
    founds2=`tail -10 /var/log/oscam.log | grep "classD0" | wc -l`
    founds3=`tail -20 /var/log/oscam.log | grep "timeout" | wc -l`


    if [ $founds -gt 3 ] || [ $founds2 -ge 1 ] || [ $founds3 -ge 1 ]


    then


    echo "Error found, restart...";
    echo "Error found, restart..." >> /var/log/oscam.check
    /usr/bin/killall -9 oscam_r5893
    /usr/bin/oscam_r5893 &


    else


    echo "oscam still ok 2";
    echo "oscam is still ok 2!" >> /var/log/oscam.check


    fi



    ###########################################################################
    # end of script
    ###########################################################################


    oscam.check folder from var/log/
    will show this


    oscam is still OK 1!
    oscam is still ok 2!
    oscam is still OK1!
    oscam is still ok 2!
    oscam is still OK 1!
    oscam is still ok 2!
    Couldn't find oscam running. Restarting server-binary
    Error found, restart...
    oscam is still OK 1!
    oscam is still ok 2!
    oscam is still OK1!
    oscam is still ok 2!
    Couldn't find oscam running. Restarting server-binary
    oscam is still ok 2!
    oscam is still OK1!
    oscam is still ok 2!
    oscam is still OK1!
    Error found, restart...
    oscam is still OK 1!
    oscam is still ok 2!
    oscam is still OK1!
    oscam is still ok 2!
    oscam is still OK 1!
    oscam is still ok 2!


    PS: oscam is check from 2 directions,... according with oscam.log file

    Oscam.log folder -- history


    2013/02/23 11:43:39 2E5034B0 c card (09CD&000000/106E/B7:5AE8): found (101 ms) by ***it (of 1 avail 1)
    2013/02/23 11:43:49 2E5034B0 c card (09CD&000000/106E/B7:25ED): found (100 ms) by ***it (of 1 avail 1)
    2013/02/23 11:43:59 2E5034B0 c card (09CD&000000/106E/B7:673E): found (100 ms) by ***it (of 1 avail 1)
    2013/02/23 14:26:32 2C6334B0 r client timeout=5000 ms, fallback timeout=2500 ms, cache delay=120 ms
    2013/02/23 14:26:32 2C6334B0 r [videoguard2-reader] classD0 ins40: (-2) status not ok f8 ef
    2013/02/23 14:27:16 2C6334B0 r [videoguard2-reader] classD0 ins40: (-2) status not ok f8 ef
    2013/02/23 14:27:16 2E7FF4B0 c card (09CD&000000/1FAC/B7:9D4F): not found (2535 ms) by ***it (of 1 avail 1)
    2013/02/23 14:27:18 2C6334B0 r [videoguard2-reader] classD0 ins40: (-2) status not ok f8 ef
    2013/02/23 14:27:39 2C6334B0 r [videoguard2-reader] classD0 ins40: (-2) status not ok f8 ef
    2013/02/23 14:27:39 2E7FF4B0 c card (09CD&000000/0FC7/B7:8497): not found (2535 ms) by ***it (of 1 avail 1)
    2013/02/23 14:27:41 2C6334B0 r [videoguard2-reader] classD0 ins40: (-2) status not ok f8 ef
    2013/02/23 14:28:03 2C6334B0 r [videoguard2-reader] classD0 ins40: (-2) status not ok f8 ef
    2013/02/23 14:28:03 2E7FF4B0 c card (09CD&000000/3C03/B7:4C64): not found (2535 ms) by ***it (of 1 avail 1)
    2013/02/23 14:28:06 2C6334B0 r [videoguard2-reader] classD0 ins40: (-2) status not ok f8 ef
    2013/02/23 14:28:45 2C6334B0 r [videoguard2-reader] classD0 ins40: (-2) status not ok f8 ef



    this script follow the word from oscam.log
    is perfect functional, with cronjob at 1 or 2 minutes
    Oscam1.10_SNV_r5893


    ################################
    monitor restart for Oscam_r5893


    is working correct, after you start the cronJob
    tested Ok !!!
    feedback from oscam.log-- following this tree words "ins40","classD0",and "timeout"


    if one of this 3 words , will appear (pup up) 10 times in oscam.log, restart of oscam will follow,....


    super ok !!! is put in usr/script and atr 755 or 777
    #################################################
    #oscamcheck.sh or oscammonitor.sh
    ##################################################



    #!/bin/bash


    founds=`tail -10 /var/log/oscam.log | grep "ins40" | wc -l`
    founds2=`tail -10 /var/log/oscam.log | grep "classD0" | wc -l`
    founds3=`tail -20 /var/log/oscam.log | grep "timeout" | wc -l`


    if [ $founds -gt 3 ] || [ $founds2 -ge 1 ] || [ $founds3 -ge 1 ]
    then
    echo "Error found, restart...";
    echo "Error found, restart..." >> /var/log/oscam.check
    /usr/bin/killall -9 oscam_r5893
    /usr/bin/oscam_r5893 &
    else
    echo "oscam still ok 2";
    echo "oscam is still ok 2!" >> /var/log/oscam.check
    fi


    ##########
    the end
    and have fun
    #######################
    cronjob etc/cron/crontab/root


    ++++++++++++++
    in root --atr 755-- I put:
    */1 * * * * /usr/script/CCcamCheck.sh start /dev/null
    or
    1 * * * * /usr/script/CCcamCheck.sh start /dev/null


    I don 't know which is correct for ver 2.2 gutamine CRON
    =============


    oscam.check folder from var/log/
    will show this


    oscam is still ok 2!
    oscam is still ok 2!
    oscam is still ok 2!
    oscam is still ok 2!
    oscam is still ok 2!
    oscam is still ok 2!
    Error found, restart...
    oscam is still ok 2!
    oscam is still ok 2!
    oscam is still ok 2!
    oscam is still ok 2!


    also when you will run manual the script -- you will get same message on screen of TV
    ==========
    don't forget to start from cronmanager /START ON--- the crontabs !!!!!
    or run with DCC
    crontab -e
    ================
    and set also Crontab START at BOOT-- to be active !!!!
    ================
    restart , and have fun, will work like a clock ,...
    bye


    I tested on DM800HD , image nemesis2.3_ svn_095r6 _SSL84 by ramiMAHER


    Nemesis2-3-dm800HD-SVN(095r6)-10-23-2011-ramiMAHER #ssl84

    script is checking the Oscam, also the CCcam.
    is super good , and simple to use ,.....
    no folder of trash, --with confirmation of status,-- something that you need to delete , (empty ) after each day.


    #################################
    #CCcamcheck.sh or ccheck.sh
    ##################################


    IP="127.0.0.1"
    ERRORLOG="/tmp/error.log"


    #CCcam Options#########
    CCCAMPORT="12000" #
    CCCAMVERSION="_2.1.4" # here you modify according to your needs, that your box have
    CCCAMPATH="/usr/bin/" #
    #######################


    #oscam Options#########
    OSCAMPORT="34000" #
    OSCAMVERSION="_0.99.4"#### or 1.10,....
    OSCAMPATH="/usr/bin/" #
    #######################
    CCCAMCHECK=nc $IP $CCCAMPORT
    OSCAMCHECK=nc $IP $OSCAMPORT
    if [ $CCCAMCHECK = ]
    then
    echo && date >> $ERRORLOG
    echo "CCcam is frozen, restarting CCcam" >> $ERRORLOG
    killall CCcam$CCCAMVERSION
    killall oscam$OSCAMVERSION


    $OSCAMPATH && oscam && $OSCAMVERSION &
    sleep 15
    $CCCAMPATH && CCcam && $CCCAMVERSION &


    else
    echo "Cccam is responding like it should"
    fi


    if [ $OSCAMCHECK = ]
    then
    echo && date >> $ERRORLOG
    echo "oscam is frozen, restarting CCcam" >> $ERRORLOG
    killall CCcam$CCCAMVERSION
    killall oscam$OSCAMVERSION


    $OSCAMPATH && oscam && $OSCAMVERSION &
    sleep 15
    $CCCAMPATH && CCcam && $CCCAMVERSION &


    else
    echo "oscam is responding like it should"
    fi




    ####################


    cronjob ----for 1 minute in crontabs root


    */1 * * * * /usr/script/ccheck.sh
    or
    */1 * * * * /usr/script/ccheck.sh start


    start the cron, for this script from cronmanager that you will find
    Meniu>pluin>cronmanager


    or with DCC >telnet , commands
    crontab -e with DCC


    verify process is running-- Command : PS also in DCC telnet


    bye


    locations of folders


    usr/script/ccheck.sh


    etc/cron/crontanbs

    you can start with all.
    or call *** center ,and ask them, what they recommend, my dear friend from Italy.
    or call this guys - Thor II, and Deltafox , and Maseitexan- and ask them,
    you are very new here, I see.....and a very good programmer. success.

    No emu can stop 9996 all of them kill the card



    FALSE


    you need to get the OSCAM source, and to make your own Oscam version without any EMM - G,U,B ,and NANO , support inside.


    Provider SXY decided to replace the card to NDS 4 during this year, that has a new secure memory near CPU- and will protect better the written inside EEProm.
    process will be ended until 2014. { always in may , June, they send this Nano EMM, to attack the cards, in sharing}
    this memory - is develop for security
    AT88SCxx,
    AT88SC0104C、AT88SC0204C、AT88SC0404C、AT88SC0808C 、AT88SC1616C、AT88SC3216C、AT88SC6416C、AT88SC12816C、AT88SC25616C
    produce in China, and very High tech


    ALL OSCAM have - a gate inside to accept NANO- soo, provider use this backdoor ,to block your cards.{ I think that is a pack between developer of soft Oscam, and TV provider- unofficial, or they make this mistake in program .....by mistake....but I belive they made this on puurpose ]
    the solution is a new OSCAM version , made by you, and to eject EMM functions. please start,....do not lose time?
    Italian forums, cut this info out-- only to help Italian provider- to change the NDS 3 in NDS 4 more easy- and to let the provider to have control on last version of Oscam, and to keep control on users of cards with OTA update. ( with this back door) they can block the cards, in Sharing , when they want.


    first are attacked the users from Sharing ( special Oscam users}, after , that they will sent the nano EMM to affect also cards in official box-- to replace the cards from normal ( correct ) user that have the card ONLY in official box. { this will be in last phase]
    I hope I was helpful
    bye
    solution, is special OScam{homemade], or try different EMU {Sbox}

    My vu+Uno stay on red light please see this link from cypress and Tell me what it takes to buy for J-Tag VU+Uno receiver
    and on ebay find this is this bbs tools for vu+ receiver? I want to buy but dont know what to order



    buy
    this Cypress CY7C68013A EZ-USB FX2LP USB2.0 Develope Board for Logic Analyzer
    Cypress CY7C68013A EZ-USB FX2LP USB2.0 Develope Board for Logic Analyzer | eBay


    1.after you install the Broadcom Studio,
    2.you need to update the flash , memories XML database, according with what you have on your main board.
    verify in MANAGEMENT , if your computer see the Cypress CY7C68013A EZ-USB (driver )
    3.you select the Plugin according with your processor BCM 97325 or 97335, or 97413, 0r other
    4.select SPI , or USb, or I2C
    5.startup>>>flash explorer
    6.verify that cables are connected {but box is now power OFF}
    7.put power on box - and you need to see connection , on startup, or in BVN-Map


    and you can access all line from your Flash


    PS: on BVN MAP- if you get the correct connections ->>> lines will be in green.


    success


    I manage to access also the mainboard on solo Clone and original
    important is the data base of XML memories, from flash forder, to be according with the memory that is on your mainboard box


    the Cypress CY7C68013A EZ-USB is working , and you can back-up complete full memory contain, and also partial from line 0000FF to other line 0000FFF that you can select-- your can manage everything , read write in Flash.
    the communication protocol is I2C via Bradcom processor.
    { other alternative is JTAG connection-but is on other part of the board on some models, is exist by producer}
    when you rewrite the Flash, you need to search soft, according with the version of mainboard 1.0 or 2.0 for clone
    success

    thanks for your feedback.
    inside the original box is running a linux debian operating system. set on NXS marriage system reader.{I extract already the soft from original box}


    somebody breached the encryption procedure, because I find a C line in share- working.
    but he don't share the info with us
    --------
    i don't know what EMU is using , and I cannot find him again.
    -----
    3 weeks ago I sow the line working with dolce Caid. the blocked channels, were running, in that line.


    If somebody can give me some recommendation , for a EMU, that support easy, this marriage system, please post.I have already the boxkey and cardserial-HEX. Thanks

    please give me a feedback- if Oscam and what versionSNV , can support a marriage system, NXS , card , between Boxid and Hex serial card.
    --
    I have a provider, Dolce, that use both this Hex to codes , to incode the programs.


    maybe somebody know a other Emu, that can digest this NXS card, in marriage system.
    I extract already the Boxid, and Hex of serial card, but I donnot have a proper Emu to run it.


    thanks for feedback

    people, I provide to all the principle, that provider for Italy , is using to destroy our hobby.


    please start to use at maximum your brains, { brain storm } and find a solution {efficient } , to avoid this shit {EMM update } in future, that want to damage your card.
    ask Deltafox , Maseitexan and others....


    I'm not Jesus , I'm only saint Peter,....


    I only observe this, on my last card Update, and I share this info with all.


    soo please start experiencing yourself's, and find a solutions , to protect efficient our cards.


    try to move in future from Oscam to other EMU, ---- and share your results with us,...


    testing, testing and more testing , is my recommendation.
    And look inside your card , before update and after update, and save this info, and analyze , compare them .
    If you will see big difference in size, on this info, that will be the EMM inside your Epprom, waiting to go out :))))
    in time we will find a solution , to protect us better.


    until that day comes, nice sharing to all....

    news is this:
    from 2013, on update - for data tiers, they sent EMM for each tier, according with your card contract and serial.
    BUT after they finish the date update for each tiers, they sent a last EMM, that goes , in the card , in the section with free space {not used by operating system ROM}
    you finish your card update- in origial rec
    and you want to put the card in OSacm box
    :)))
    now comes the fun part....
    if you are using Oscam 1.20, the remaining EMM from card, will go out from card via TDA 8024,{ and will force your processor or your operating system } and will change the Oscam server setting, disable reader and change also MHZ value from set value by you
    in this way the provider can burn your card, please notice that. very simple procedure.
    the good part is that the this EMM has power only one time, after is out { he left the card }you are safe. { is a one time run}


    depending on what is programed to do,...on card or on box.


    soo avoid , version 1.20 and possible 1.10 rc ........... 1.20 I tested myself, you cannot control it.


    in conclusion: they put the bomb , inside your card, in free space reaming , of card, because they have enough {4096 Bytes of EEPROM}
    [is the principle of troian Horse -- very simple and efficient ]
    this bomb can have different purpose, and if starts to delete or rewrite , and after this process the info is out....from the original version { from card or Oscam -depending on EMM purpose ]


    last year they block the cards, with this system, by modifying the Nano inside all cards- contract or prepaid because of black market for this items from Italy .... and to correct, you need to go to them to present the card.