Jump to content
NotebookTalk

YAR1307

Member
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

YAR1307's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • First Post

Recent Badges

0

Reputation

  1. laptop Hasee TX9-CA5DP (similar to CLEVO N960KR) I'll ask a very stupid question, how to change uefi to legacy? I want to enter DOS from a USB flash drive, but it is not in the boot device. p.s. DOS was created correctly, it works on another PC but only through legacy
  2. @kaz26unfortunately didn't help. Is there another solution?
  3. @kaz26 I tried to flash vbios with NVFlash version 5.792.0, there are two versions of NVFlash, for 32 and 64 bit systems, I have 64 bit windows. I also used --protectoff. When I flash via nvflash64 I get an error (that I'm using the 32-bit version of the program on 64-bit windows). nvflash32 works without errors, but the result hasn't changed since my last post. When flashing, the screen does not blink, the firmware takes 1-2 seconds, after the firmware, the old and new versions of vbios are not displayed in cmd, after rebooting the vbios, a drain remains. Maybe try flashing vbios via DOS?
  4. Hello! I have a laptop Hasee TX9-CA5DP (similar to CLEVO N960KR) i5 10400 + rtx 3070 It has an unlocked bios v1.07.14 with EC 1.07.02 I want to reflash vbios with a limit of 140w, currently stock: https://www.techpowerup.com/vgabios/236921/23692 reflash to: https://www.techpowerup.com/vgabios/231706/clevo-rtx3070-8192-210104 (they have the same device id) I am using NV Flash 5.804.0 I'm flashing through cmd, there are no errors, the screen does not turn off during the firmware, the firmware takes 1-2 seconds (although it should be about 10-30 seconds), after rebooting the firmware remains stock. I tried to install another vbios but there is an error due to device id incompatibility. I also tried other versions of NVFlash but then it does not see the video card. In cmd also tried with "--protectoff", the result is the same. Can you please tell me what could be the problem?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use