Posts by Nepose

    About version spoofer: you can manually change image version, description and date by using SSH utility. Stalker middleware may check for them before loading web portal.


    If you don't know what is SSH:

    1. Go to System Settings -> Network info -> either Wired or Wireless (which one you use)
    2. Find the IP of STB and write it down somewhere
    3. Download PuTTY app on your Windows PC. Turn it on, to "IP" field enter IP of STB and to "Port" enter 22, then click "Connect"
    4. Login as: root
    5. Password: 930920
    6. Congrats, you've loaded embedded Linux command line ;)

    Image version, description and date are written in STB's bootloader memory. There are two commands to modify it:

    Bash
    fw_printenv [here variable name]            to check value of a variable
    fw_setenv [variable name] [value]           to set a value of a variable

    For MAG 322 latest official firmware is 2.20.09r2 and there are required values of variables:

    • Image version (variable Image_Version): 220
    • Image description (variable Image_Desc): 2.20.09r2-324
    • Image date (variable Image_Date, must be in such format): Thu Jun 27 13:51:48 UTC 2019

    So for this example the required commands are:

    Bash
    fw_setenv Image_Version "220"
    fw_setenv Image_Desc "2.20.09r2-324"
    fw_setenv Image_Date "Thu Jun 27 13:51:48 UTC 2019"

    and after it it's recommended to reboot using reboot.

    In this way user of every STB can change details to spoof official firmware with using my images

    Okay, IMHO the problem was with some missing files at root file system of image. I've recompiled images, try please downloading the new ones from website (in the same way as earlier).

    If trouble persists let me know


    PS about DTS. May you know which versions of firmware supported DTS on particular STBs? And could you send me them, please, if possible? :)

    Infomir doesn't provide any info about supporting it on any of STBs like MAG 322/324, MAG 254, MAG 256. The curious thing is that MAG 254, 256, 349 and 351 are now marked as discounted. They are not such old IMO.

    Hello! Sorry for my absence, I've had lot of private stuff.


    Finally there comes new upgrade v2.20.00. The new upgrade of MAG Software Portal firmware comes with two changes:

    • Improving online upgrade functionality.
      Now there is no transitional and final image. You can just grab image from my website and flash it manually. Or you can go to STB settings and do upgrade - but unfortunately this particular 2.20.00 must be flashed from Bootloader / System Recovery Utility.
    • Adding new shortlink Firmware docs
      This shortlink launches my website at STB.

    You can download it from Downloads subpage on my website and flash by Bootloader / System Recovery Utility menu. As I've said, unfortunately this must be done by Bootloaders (USB method preferred), but any next upgrades should be available through STB settings.


    This image is available for all STBs expect MAG 420/424. Support for those STBs is planned soon.


    The second great news is that I've done a better and more usable website of project at https://portal.magboxes.xyz - old website at firmware.magboxes.xyz redirects to the new one now.


    Hi Nepose,

    Is it possible to contact you on your business email ?


    Thank you for the incredible work ! ^^

    Yes, at nepose.magportal@gmail.com :)

    Big thanks for appreciating it! :)


    It would be nice function, I'll try to find out whether it is possible :)



    how can I update my mag322 on the latest firmware?

    Go to https://portal.magboxes.xyz/download and grab image for MAG 322/324.

    Hi,


    I've fixed links, look please at https://vps.magboxes.xyz/image…2-rc.1/imageupdate_mag256 for image :)


    About rc2, I'm soon going to compile a new firmware which fixes problems with transitional and final images, they will not be needed and firmware will be just firmware ;)

    Hi friends :)



    Did you download version 2.19.02-rc.1? This is current transitional image and this must be used by everyone who wants to flash my firmware for first time.

    What shows when you try to install?



    Unfortunately I haven't touched this, if you could describe it please more specificly and write which STBs are corrupted.

    can you already say something, if and when an update for the Mag 322 comes? :)

    There is now available upgrade 2.19.02-rc.2. This is only for MAG 322/324 and Aura HD Pro STBs. It unlocks possibility to set 1920x1080 resolution in embedded portal settings.

    This upgrade is a release image, which means that you firstly have to install transitional image if you didn't do it before. Then go to embedded portal settings -> Software upgrade and try check for updates.

    Remember please that the 2.19.02-rc.2 cannot be installed on STBs other than 322/324/Aura HD Pro, violating it will result unsupported architecture error.

    What's with it, I've even written a post about issue with this portal, go with https://firmware.magboxes.xyz/…with-not-working-no-block :)


    And one nice thing: imageupdate 2.19.02-rc.1 is now available also for MAG 256, if you are interested https://vps.magboxes.xyz -> firmware_transitionals -> 2.19.02-rc.1 -> mag256 :)

    No, at the moment this current version is the latest. It contains no block patch.

    thanks for your replay my box is mag 250 and 254 i need help when i start from usb its say wrong signature i try with diffrent usb but same problem

    Let me please know, do you try flashing my firmware on a box from operator? And you try on MAG 250 or MAG 254 or both?

    If your box is from operator, there's a big likelihood that they have locked it. In such case look please through my guide how to unlock such box: https://firmware.magboxes.xyz/docs/modify/unlock-mag-255.

    Check default credentials when logging in by SSH: username root and password 930920.

    Thanks for link, for other interested people there is an instruction how to do patch on your STB in a quick and dirty way (taken from link):


    1. Disable autoupdates because they might restore lock. Do it before you take the box online (the best option is to disable temporarily any Internet connection and enable it when ending guide, leave only local network to use SSH)
    2. Check if you have access by SSH, if no, than flash public Infomir image from soft.infomir.com which has enabled connection by default.
    3. Enter SSH and do following commands:


    Code
    echo 127.0.0.1 mag256.dcbs.infomir.com >> /etc/hosts 
    rm /mnt/Userfs/data/dls.backup 
    reboot && exit


    It will deny requests to Infomir database of blocked portals, replace mag256 with the model you have (e.g. mag254). The "dcbs.infomir.com" contains this database and prefix with STB model gets request of and redirects to particular table for each device. The "dls.backup" may contain offline cache with list of already blocked portals or some instructions for this mechanism so we have to remove it in case.


    4. After rebooting wait some time and reconnect STB to Internet to check.


    Wysłane z mojego LG-M250 przy użyciu Tapatalka

    Thanks for patch, ask please this guy if I can embed it onto new imageupdate so the block will be disabled by default :)