Skip to main content
Ellyas
Ellyas
New Member
July 30, 2015
Question

Unable To Downgrade FGT Firmware

  • July 30, 2015
  • 4 replies
  • 25560 views

Greetings,

 

Hello team. Currently I am in the midst of downgrading a FGT firmware from the default v5.2.2, Build 642 to v5.0.7, Build 271. Once the downgrading has been done, the FGT is refreshed and I was prompted to log in again.

 

However once I had logged in, I can see that the firmware was not downgraded to the preferred firmware. I had tried to downgrade again, but still firmware still shows v5.2.2, Build 642 instead of the preferred v5.0.7, Build 271.

 

Our engineer had suggested to try and downgrade via TFTP. But currently resources for the TFTP method is not available at the moment and might be delayed.

 

May I know is there any other way to perform the downgrade? Also, way was the downgrade not successful even though there were no error message prompted? Seek your immediate advice.

 

 

 

 

Thanks & regards,

 

Ellyas.

    4 replies

    AlexFeren
    AlexFeren
    New Member
    July 30, 2015

    Ellyas wrote:
    ... I am in the midst of downgrading a FGT firmware from the default v5.2.2, Build 642 to v5.0.7, Build 271...
    I cannot help with the downgrade, however, would you mind sharing the reason for downgrade - is it functionality, reliability, or security related? [You see, we're in consideration to upgrade from 5.0.x to 5.2.y.]

     

    ... currently resources for the TFTP method is not available at the moment and might be delayed.

    if your unit has a USB port, try "execute restore image usb ..."?

    Also see How to restore previous version of firmware from flash disc via CLI.

    Ellyas
    EllyasAuthor
    New Member
    July 30, 2015

    Greetings,

     

    Hi Alex. We are downgrading to this particular firmware is due to standardization process. When a new FGT is installed, this was the instruction received.

     

    I tried to re-downgrade again today and just noticed the error message as per image named "FGT_01.jpg". I had checked the firmware file and it is indeed for this model and was used successfully to downgrade other FGT with the same model.

     

    Any idea on what are the possible reasons that this error message might appear?

     

     

     

     

    Thanks & regards,

     

    Ellyas.

    AlexFeren
    AlexFeren
    New Member
    July 30, 2015

    Since this is a new device..., I'd use CLI to load the firmware as secondary image and see how that goes - "secondary-image usb ...".

    PS. verified MD5 of the file?

     

     

    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    July 31, 2015

    hi,

     

    this doesn't need to be complicated.

    First, please post your hardware model, and the exact filename of the image you are planning to use.

     

    You can downgrade to any version using a USB stick:

    1. load the right image file onto the stick. Make a copy with the name "image.out".

    2. Copy a matching config file onto the stick. Make a copy with the name "fgt_system.conf".

    3. In the GUI, in System > Config > Advanced, check both checkboxes to auto-load the firmware and config files on boot.

    4. reboot the FGT

    After the reboot check for config errors:

    in the CLI, type "diag deb conf read"

    and post it here if any.

    emnoc
    emnoc
    New Member
    August 3, 2015

    Are you 100% sure you have the right image for your model-type? It's common to  incorrectly try to place a non-Wireless image on a wiFi model or even a PoE model

     

    Also have you looked and doing a tftp-upload after a disk reformat?

     

    Also have you tried to look at what's on your disk partions?

    (start with )

     

    diag hardware deviceinfo disk

     

    and then

     

    execute disk list

     

    and then a scan

     

    execute disk  scan

     

    I bet your problem is one of the following;

     

     1: wrong image for the model of unit

     

     2: wrong calculated checksum

     

     3: bad partition that needs a reformat

     

     4: or it's a bug that requires you reformat in order to download

     

    I known with  earlier pre5.0 code the filesystem format is extended type2 vrs now it's extended type3. If your doing a downgrade and are local to the unit, I would just do a interrupted boot , followed by a re-fromat, and then tftp upload.

     

    I would also look at the release notes for the proper download path if any. I wouldn't be surprised if this is a issue from 5.2.x to 5.0.7 but who knows.

     

    let us know what you  find?

     

     

    Terms & ConditionsAccessibility statement