Posts by yinyang

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    <?xml version="1.0" encoding="utf-8"?>
    <Flash maker="Samsung" name="Samsung KFG5616U1M" type="OneNAND">
    <Command type="OneNand" programmode="Block" maxbyte="1024"/>
    <ID>
    <Maker maxword="1" offset="0x00">0x00EC</Maker>
    <Device maxword="1">
    <DevId offset="0x02">0x0015</DevId>
    </Device>
    </ID>
    <Size unit="mbit">256</Size>
    <Sector uniform="true" secure="false">
    <MaxSector>512</MaxSector>
    <Size unit="kbyte">64</Size>
    </Sector>
    </Flash>

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    <?xml version="1.0" encoding="utf-8"?>
    <Flash maker="Samsung" name="Samsung KFG1216U2B" type="OneNAND">
    <Command type="OneNand" programmode="Block" maxbyte="2048"/>
    <ID>
    <Maker maxword="1" offset="0x00">0x00EC</Maker>
    <Device maxword="1">
    <DevId offset="0x02">0x0025</DevId>
    </Device>
    </ID>
    <Size unit="mbit">512</Size>
    <Sector uniform="true" secure="false">
    <MaxSector>512</MaxSector>
    <Size unit="kbyte">128</Size>
    </Sector>
    </Flash>

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    <?xml version="1.0" encoding="utf-8"?>
    <Flash maker="Samsung" name="Samsung KFG4GH6U4M" type="OneNAND">
    <Command type="OneNand" programmode="Block" maxbyte="4096"/>
    <ID>
    <Maker maxword="1" offset="0x00">0x00EC</Maker>
    <Device maxword="1">
    <DevId offset="0x02">0x0255</DevId>
    </Device>
    </ID>
    <Size unit="mbit">4096</Size>
    <Sector uniform="false" secure="false">
    <MaxSector>1024</MaxSector>
    <Size unit="kbyte">512</Size>
    </Sector>
    </Flash>

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    <?xml version="1.0" encoding="utf-8"?>
    <Flash maker="Samsung" name="Samsung K9LBG08U0M" type="NAND" technology="MLC">
    <Command type="Nand" programmode="Block" maxbyte="4096"/>
    <ID>
    <Maker maxbyte="1" offset="0x00">0xEC</Maker>
    <Device maxbyte="1">
    <DevId offset="0x01">0xD7</DevId>
    </Device>
    </ID>
    <Size unit="gbit">32</Size>
    <Sector uniform="true" secure="false">
    <MaxSector>8192</MaxSector>
    <Size unit="kbyte">512</Size>
    </Sector>
    </Flash>

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    <?xml version="1.0" encoding="utf-8"?>
    <Flash maker="Samsung" name="Samsung K9F2G08U0A" type="NAND" technology="SLC">
    <Command type="Nand" programmode="Block" maxbyte="2048"/>
    <ID>
    <Maker maxbyte="1" offset="0x00">0xEC</Maker>
    <Device maxbyte="1">
    <DevId offset="0x01">0xDA</DevId>
    </Device>
    </ID>
    <Size unit="gbit">2</Size>
    <Sector uniform="true" secure="false">
    <MaxSector>2048</MaxSector>
    <Size unit="kbyte">128</Size>
    </Sector>
    </Flash>

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    <?xml version="1.0" encoding="utf-8"?>
    <Flash maker="Samsung" name="Samsung K9F2G08R0A" type="NAND" technology="SLC">
    <Command type="Nand" programmode="Block" maxbyte="2048"/>
    <ID>
    <Maker maxbyte="1" offset="0x00">0xEC</Maker>
    <Device maxbyte="1">
    <DevId offset="0x01">0xAA</DevId>
    </Device>
    </ID>
    <Size unit="gbit">2</Size>
    <Sector uniform="true" secure="false">
    <MaxSector>2048</MaxSector>
    <Size unit="kbyte">128</Size>
    </Sector>
    </Flash>

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    <?xml version="1.0" encoding="utf-8"?>
    <Flash maker="Samsung" name="Samsung K9F1G08U0A" type="NAND" technology="SLC">
    <Command type="Nand" programmode="Block" maxbyte="2048"/>
    <ID>
    <Maker maxbyte="1" offset="0x00">0xEC</Maker>
    <Device maxbyte="1">
    <DevId offset="0x01">0xF1</DevId>
    </Device>
    </ID>
    <Size unit="gbit">1</Size>
    <Sector uniform="true" secure="false">
    <MaxSector>1024</MaxSector>
    <Size unit="kbyte">128</Size>
    </Sector>
    </Flash>

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    <?xml version="1.0" encoding="utf-8"?>
    <Flash maker="Samsung" name="Samsung K9F1G08R0A" type="NAND" technology="SLC">
    <Command type="Nand" programmode="Block" maxbyte="2048"/>
    <ID>
    <Maker maxbyte="1" offset="0x00">0xEC</Maker>
    <Device maxbyte="1">
    <DevId offset="0x01">0xA1</DevId>
    </Device>
    </ID>
    <Size unit="gbit">1</Size>
    <Sector uniform="true" secure="false">
    <MaxSector>1024</MaxSector>
    <Size unit="kbyte">128</Size>
    </Sector>
    </Flash>

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    Quote from Compo

    Does any one have the Samsung K9K8G08U0D.xml file ?


    This is i think the correct file for the flash nand in the ultimo not the one quoted in the VU.pdf guide.


    regards


    let's give some help here.
    you always need to check the NAND data that you have on board, and to check for revisions. Also you need to read technical news regarding NAND writting, and reading

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    Quote from piolo68

    please, I'm not an expert . I have ST NAND512W3A nand and bcm96361 ,wat can i do...please can you help me step by step for configure studio3:09:



    you need this


    1. plugin for your processor --- bcm96361
    2. in program files> Broadcom> Broadcom studio3> Flashes-- you need to add the definition of XML file for your memory ST NAND512W3A, and this XML need to be correct made


    open program Broadcom studio3
    go to
    TOOLS>Device Manager> ADD { plugin for your processor }
    after
    View>> DEVICES> PLUG IN {bcm96361}


    and start


    select your interface type - SPI , I2C , usb, etc


    start to play


    ==================


    <?xml version="1.0" encoding="utf-8" ?>
    - <Flash maker="ST" name="ST NAND512W3A" type="NAND" technology="SLC">
    <Command type="Nand" programmode="Block" maxbyte="512" />
    - <ID>
    <Maker maxbyte="1" offset="0x00">0x20</Maker>
    - <Device maxbyte="1">
    <DevId offset="0x01">0x76</DevId>
    </Device>
    </ID>
    <Size unit="mbit">512</Size>
    - <Sector uniform="true" secure="false">
    <MaxSector>4096</MaxSector>
    <Size unit="kbyte">16</Size>
    </Sector>
    </Flash>


    ======================
    but you need the bcm96361 plugin - to start playing

  • Need info on VU+ JTag Broadcom Tools ( Solved )

    verify the data sheet from your memory that you have on your board , and compare with the data sheet for memory that Broadcom studio3 selected from Flash list, when program give you CONNECTED.


    between this 2 memories , in data sheet , you will find some difference on ID marker
    generate in Flash folder, a new XML. file for your new memory that will be corected , with new Marker.


    after that, the error need to not reappear.


    but you need to modify the XML for this memory to fit to what you have on your board


    ========================


    <?xml version="1.0" encoding="utf-8" ?>
    - <Flash maker="Samsung" name="Samsung K9F1G08U0A" type="NAND" technology="SLC">
    <Command type="Nand" programmode="Block" maxbyte="2048" />
    - <ID>


    <Maker maxbyte="1" offset="0x00">0xEC</Maker>


    - <Device maxbyte="1">
    <DevId offset="0x01">0xF1</DevId>
    </Device>
    </ID>
    <Size unit="gbit">1</Size>
    - <Sector uniform="true" secure="false">
    <MaxSector>1024</MaxSector>
    <Size unit="kbyte">128</Size>
    </Sector>
    </Flash>


    ======================================


    look very - closer on the code of the version of the memory that you have on board, and find the data sheet for her, and produce your XML - using the example posted already


    after that , the broadcom studio will communicate with processor from board , and the back-up can become .


    check for revision of this memory , and for modifications , after revisions.


    see
    page 29
    page 35


  • Vu solo reflash

    remark:
    this is used, only when you have the box already blocked , with RED LED , on frontal panel.
    read the instruction, and you have 2 bin there for each phase.
    after that the Cfe2.0 that you will install , is your decision.

  • Vu solo reflash

    I do not know if this soft is for clone or original, but can be use for boxes that are blocked , and that they have the boot secvence damage.
    {because user put a image that is not suitable for that board }


    after flash is erased , flowing the procedure described in read me text, you can put latest Cfe 2.0 that you want
    soft is using RS232 , not Jtag connection, from board.


    success


    the users that manage to repaired their blocked boxes,using this soft , please post some feedback.


    link


    http://www.4shared.com/rar/Cvr…_solo_-_soft_reflash.html

  • tntsat on azbox enigma 2 viaccess 5

    AES key need to be extracted from card


    need to have 32 digits, in HEX---for your Caid / provider ID


    you add in Oscam reader this AES , and after that the message will become


    AES key(s) added on reader orange_romania for 0500:051300



    if the key is correct , the Oscam will open the imagine on your screen


    enjoy , the Sharing :32_002: :10_002:



  • Protect your s@y italia card !!!!!!


    Hello Nano,
    thanks for your post, it help me a lot.


    I purchase a new card, and get blocked after 24 hours.


    Ip is monitorized. possible also the domain xyz...DNS
    soo, my conclusion is that if they see outside , the shared key of the card, { that contain the 6 digits from your card} , they will put your serial in server - to generate de EMM killer, special for your card.
    this EMM will came , on data channel, and will be sent by your processor that will process him and sent after to the TDA8024 that is the reader-writter of card.


    I'm curious if somebody tried to make share from original NXS box?
    or if somebody , manage to use other EMU { or combination of EMU }- for outside share - without damaging the card.


    the INS responsible for 9666 must have a number- I hope that somebody will identify him , in near future.
    the real problem, is that even if we know what is his number- what you will get- will be the bad one- for your serial .
    to generate the correct one, for your card, will be very hard, if you don't know - the procedure to generate the OTA (emm.)
    the EEprom , is capable to write inside only one cell, by the internal processor.
    soo.,... now you have on I/O line, this security Cip- that need to be open - to permit the writing inside the card.
    this is open by a code that came with the EMM- and switch the processor from card to writing.


    now is harder to correct the EPProm info - by a soft from your personal PC, because all the time were used TXT info - to sent to card
    and now is needed to use only Bin file info- and this bin file to contain also the valid passcode for security Cip { that can be updated by Ota also }


    soo , I hope will identify the number from INS killer { codepass , plus procedure to compose the EMM after }
    or provide the procedure to make share from original box.
    or a other EMU - that makes the update correct like in original box


    but , if your serial - is seen outside in share- they will put in server your serial in blacklist- and your card will be hunted- hopping by provider to be killed. and they sent this killer for your serial , until they see, bad key outside, or shared key of your card disappear from network that is monitorized.


    if you use your card internal- for local shared- your card will safe forever
    if you share outside - your card is doomed .


    soo everybody , will take his personal conclusions.


    all the best
    to all

  • Protect your s@y italia card !!!!!!

    you test the HD channels? { only here you will get channels not subscribed - because the key obtained , is seen as invalid }
    or also the SD channels?
    this you need to specify , more clearly .
    thanks


    you will find other, EMU, very good for update {correct }, of card. {you only need to read some forum documentations}
    the idea , is to keep the card-updated each week, now,...


    you can use for this task = the original box, or you can use a Enigma EMU-- only to keep the card updated.


    success


  • Protect your s@y italia card !!!!!!

    Quote from nano

    Nothing ever surprises me here. In all honesty you could work for MacDonalds or Interflora, it really wouldn't matter to me.


    If what your saying in your previous posts is true it really wouldn't make any differenece to your basic card user as there is little we could do anyway. We have to leave it up to the experts to figure out what is going on.


    Nano


    dear Nano,
    some times this experts, do nothing to inform the people.


    maybe because - they do not want to, or because they are out of subject { and they donnot understand what happened - what kick them- or us all }
    regards
    PS:
    I post my observations after my trip- and I get out this conclusions

  • Protect your s@y italia card !!!!!!

    Quote from Mee®kat

    Need to get my head round this post mate so bear with me..


    Are you saying sly italia have hardware paired cards to all boxes/changed the mpeg4 codec system and are also changing a nano byte every 3 months..and you believe italia have done most of these countermeasures recently?


    yes
    is a measure to protect again illegal activation, also cut out the cards that are not at update in official box.



    mpeg 4 was develop special for Caid 09CD { is no user mistake }
    the rest of Caid 093B , 0919 will disapear in 1 year
    only one CAID will remain.
    =======
    we already open again HD programs caid 09cd on nonofficial box- but the freeaze is too much { not suitable for CS }
    =========
    first was marriage only with HD boxe, but they can make marriage with only one box , by serial of box- like Dolce





    1.my card is prepaid
    but is happened also 3 weeks before for the card with full subscription , to a friend.
    2.yes, unplugged for 3 weeks
    I came back and I put the card inside, 9996- from first second.
    no update inside the EEProm
    I also have a special EMU that never ever updates


    soo if you donnot get the global Nano update, you will get 9996 automatically { doing nothing } - on every card 09cd abonament or prepaid , indifferent.
    the update see , only the Caid , and serial HEX,



    Quote from Mee®kat

    Ye sure...ok i have ignored option 1 and your new rule comment here (dohhhhh) of course but option 2 haha...good luck with that...its very easy for any monkey to log oscam emms sent to their cards but to suggest asking for a group of members to contribute to a web based emm databse system for italia like that is just ridiculous and plain idiotic i,m afraid.


    To do this properly and to configure private software.... yourself and your compatriot's would have to disassemble how italia receivers communicate with the said card but unfortunately nds is notoriously difficult to log especially with secure cards such as 09cd so good luck again with that.


    MK


    some Russian friends, made a similar data base in 2010-2011 for each mouth.

  • Protect your s@y italia card !!!!!!

    last new here:
    on HD - provider put online a new Mpeg4 codec
    to run the HD programs { on official box or in other box } , you will need a Update of your card ROM- sent by provider- to your serial of card and box { this can be like a marriage system }
    {if you have the ROM intact- before ROM update you still can see the programs in HD}
    ======================
    now they change the rule
    in every 3 months- they update the Nano info in EEprom
    ==============
    this is for abonament subscription
    ==========================
    I will tell you a story
    I was 3 weeks gone, in a trip and
    the card was out from original box
    and also out from DM
    after I came back from trip, I test the card in original box, and surprise-- 999x without any update!!!! the EEprom info was the same when I left.
    conclusion:
    provider change in this 3 weeks the Nano info and I miss the update because I was gone
    this EMM Nano is sent only 1 time to all the cards { global update } { and if you miss this update, your card will get 999x , without any modification inside the EEprom }
    soo if you have the card total protected- you will miss this Global update for NAno - and your card will get 999x- because is not updated to next day emission !!! signal that is broadcasting.
    ============
    ok what is the solution?to this new problem?
    1. to keep the card in original box- and to capture ALL the TIME, all the updates that provider sent to our card
    2. to start capture the EMM, each day, and to make a data base with this EMM, and put in online, to share servers.
    sort this folders of LOG , by date, and frecence .
    in this EMM data base, you can find the EMM in future = suitable to your card, and also EMM nano, and EMM for Mpeg update for HD programs.
    you only need to know what you are searching , in the folder,... according to your serial, or a special Len {INS}
    this will be a start that can help everyone, in future.
    you will find several method of capture.
    regards
    PS: this new rule, with frequent update- is made to force you to keep card in official box, and to eliminate illegal activated card.