The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Flashed non gsync 980m vbios on a gsync 980m vbios

    Discussion in 'Sager and Clevo' started by zxc20033, Sep 5, 2018.

  1. zxc20033

    zxc20033 Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    6
    Yes i know i am stupid and it actually went through but i cant flash it back to gsync vbios as it said Board ID mismatch
     
  2. Khenglish

    Khenglish Notebook Deity

    Reputations:
    799
    Messages:
    1,127
    Likes Received:
    979
    Trophy Points:
    131
    How did you manage to do that? Nvflash should block flashing vbios with different device IDs. The nongsync is 13D7 and gsync is 1617. This plus the original board ID mismatch should have completely blocked a flash.

    Getting a board ID mismatch but not a device ID mismatch does not make sense, and I can't figure out what you managed to flash onto your card.
     
    Vistar Shook likes this.
  3. mnewxcv

    mnewxcv Notebook Enthusiast

    Reputations:
    0
    Messages:
    48
    Likes Received:
    5
    Trophy Points:
    16
    Must have used a flag to ignore mismatch ID.
     
  4. Meaker@Sager

    Meaker@Sager Company Representative

    Reputations:
    9,436
    Messages:
    58,194
    Likes Received:
    17,909
    Trophy Points:
    931
    Force it with a /f and ignore.
     
  5. Khenglish

    Khenglish Notebook Deity

    Reputations:
    799
    Messages:
    1,127
    Likes Received:
    979
    Trophy Points:
    131
    That can only be done on special versions of nvflash. Standard versions downloaded from say techpowerup can't do that. The -4 -5 -f flags have not been supported on the standard release in years.
     
  6. Falkentyne

    Falkentyne Notebook Prophet

    Reputations:
    8,396
    Messages:
    5,992
    Likes Received:
    8,633
    Trophy Points:
    681
    Need to break out a Skypro Hardware programmer and 1.8v adapter, and a Pomona clip and some jumper cables.
    Then force flash the card back. This always works.

    Drawback is it costs you money.

    https://www.amazon.com/WINGONEER-high-speed-Programmer-EZP2010-supports/dp/B01DZC36GY/

    https://www.amazon.com/CPT-063-Test-Clip-SOIC8-Pomona/dp/B00HHH65T4/

    https://www.amazon.com/WINGONEER-adapter-motherboard-programmers-ezp2010/dp/B072KYK2DR/

    https://www.amazon.com/gp/product/B01EV70C78/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1

    Then you can bypass NVflash and just force flash any Bios or the original backup at will.

    (This will not bypass checksum protection of modded Bioses with incorrect checksums, but WILL bypass "falcon" protection from NVflash itself).
     
  7. zxc20033

    zxc20033 Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    6
    dunno i was going to flash my card back to original vbios but didnt saw that was an non gsync one, it was just normal command, nvflash64 ori.rom after reboot i found out i was ****ed up, vbios device id went from 1617 into 13D7 i just cant get it to flash back to an gsync one
     
  8. zxc20033

    zxc20033 Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    6
    um so i have to get programmer or i have to settle with the vbios that i have?
     
  9. zxc20033

    zxc20033 Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    1
    Trophy Points:
    6
    tried with nvflash64 /f -6 backup.rom it was the same error, board id mismatch
     
  10. Danishblunt

    Danishblunt Guest

    Reputations:
    0
    If you have teamviewer I could take a look at it.