Jump to content
EwinRacing Flash Series Gaming Chairs
svl7

Lenovo Y400 / Y500 - unlocked BIOS / wlan whitelist mod

Recommended Posts

Hi again, i have a question;

I'm using BIOS v2.04. I have SLI confugration. I'm going to be able to update my first GPU.. (After i paid 6 bucks to save time)

But how will i do for ultrabay GPU? 

Because -svl7- says that " Flashing the ultra bay 650m - only for SLI users with BIOS v2.02: "

So what can i do?  Thanks for answers.

SS-GPU.jpg

Share this post


Link to post
Share on other sites
4 hours ago, CanTOKER said:

Hi again, i have a question;

I'm using BIOS v2.04. I have SLI confugration. I'm going to be able to update my first GPU.. (After i paid 6 bucks to save time)

But how will i do for ultrabay GPU? 

Because -svl7- says that " Flashing the ultra bay 650m - only for SLI users with BIOS v2.02: "

So what can i do?  Thanks for answers.

SS-GPU.jpg

 

Don't worry, Ultrabay vBIOS is separate from primary GPU and will flash fine on v2.04.

 

3 hours ago, Bless said:

can u get the files sent to me

 

Read

  • Thumbs Up 1

Share this post


Link to post
Share on other sites

Thank you for reply -octiceps- :)

So i'm starting then. Wish me luck :frantics:

i will let you know how was it going. Thank you again everyone.

 

Share this post


Link to post
Share on other sites

Hi again guys, i did it :rofl:

But now i have some problems with voltage control, before when i had stock bios, my GPU's voltage was 0.812 V and when i was playing games it was going to 1000-1025 mV.

Now i changed the voltage but it didnt effect, it seems like stock. Still going on games 1000-1025 mV, and my game (Need For Speed 2016) crashes after 5-6 minutes.

So what can i do? Thanks for replies.

1111.jpg

22222.jpg

44444.jpg

3333.jpg

Share this post


Link to post
Share on other sites
3 hours ago, CanTOKER said:

Hi again guys, i did it :rofl:

But now i have some problems with voltage control, before when i had stock bios, my GPU's voltage was 0.812 V and when i was playing games it was going to 1000-1025 mV.

Now i changed the voltage but it didnt effect, it seems like stock. Still going on games 1000-1025 mV, and my game (Need For Speed 2016) crashes after 5-6 minutes.

So what can i do? Thanks for replies.

1111.jpg

22222.jpg

44444.jpg

3333.jpg

 

The actual 'zero' for voltage offset is at +112.5 mV. So +125 mV adds 12.5 mV to stock, +137.5 mV adds 25 mV, etc.

Share this post


Link to post
Share on other sites

Oh thanks for reply -octiceps- :sorcerer:

I will try that, and let you know how it was going :frantics:


Edit : Game still crashing after 5-6 minutes. Dxdiag error says that graphic card removed or undetected.. :too_sad2:

And also check the picture, there are some drops after i open the game ; voltage drops from 1050 mV to 0.812 mV than its going again to 1000 mV than 1050 mV..
 

55555.jpg

Edited by CanTOKER

Share this post


Link to post
Share on other sites

For now, at desktop i just saw that kind of drops at Ultrabay GPU. Everything was OK, but my voltage's are not stable..

Check this out ;

77777.jpg

666666.jpg

Share this post


Link to post
Share on other sites

Hm ... It's pretty strange.

When i try to start the "BiosFixer_2.0" i can see it starting in the task-manager, but i see no window.

The windows log got errors:

Spoiler

Anwendung: BiosFixer_2.0.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.NotSupportedException
   bei System.Windows.Input.ModifierKeysConverter.GetModifierKeys(System.String, System.Globalization.CultureInfo)
   bei System.Windows.Input.ModifierKeysConverter.ConvertFrom(System.ComponentModel.ITypeDescriptorContext, System.Globalization.CultureInfo, System.Object)
   bei System.Windows.Input.KeyGestureConverter.ConvertFrom(System.ComponentModel.ITypeDescriptorContext, System.Globalization.CultureInfo, System.Object)
   bei System.Windows.Input.KeyGesture.CreateFromResourceStrings(System.String, System.String)
   bei MS.Internal.Commands.CommandHelpers.RegisterCommandHandler(System.Type, System.Windows.Input.RoutedCommand, System.Windows.Input.ExecutedRoutedEventHandler, System.Windows.Input.CanExecuteRoutedEventHandler, System.String, System.String)
   bei System.Windows.Documents.TextEditorSelection._RegisterClassHandlers(System.Type, Boolean)
   bei System.Windows.Documents.TextEditor.RegisterCommandHandlers(System.Type, Boolean, Boolean, Boolean)
   bei System.Windows.Controls.TextBox..ctor()
   bei System.Windows.Baml2006.WpfSharedBamlSchemaContext+<>c.<Create_BamlType_TextBox>b__1035_0()
   bei System.Windows.Baml2006.WpfKnownTypeInvoker.CreateInstance(System.Object[])
   bei MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstanceWithCtor(System.Xaml.XamlType, System.Object[])
   bei MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstance(System.Xaml.XamlType, System.Object[])

Ausnahmeinformationen: System.Windows.Markup.XamlParseException
   bei System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
   bei System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
   bei System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
   bei System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
   bei System.Windows.Application.LoadComponent(System.Uri, Boolean)
   bei System.Windows.Application.DoStartup()
   bei System.Windows.Application.<.ctor>b__1_0(System.Object)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.DispatcherOperation.InvokeImpl()
   bei System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   bei MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   bei System.Windows.Threading.DispatcherOperation.Invoke()
   bei System.Windows.Threading.Dispatcher.ProcessQueue()
   bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   bei System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   bei System.Windows.Application.RunDispatcher(System.Object)
   bei System.Windows.Application.RunInternal(System.Windows.Window)
   bei System.Windows.Application.Run(System.Windows.Window)
   bei BiosFixer_2._0.App.Main()

 

 

Spoiler

Name der fehlerhaften Anwendung: BiosFixer_2.0.exe, Version: 1.0.0.0, Zeitstempel: 0x51d7dfab
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.14279.1000, Zeitstempel: 0x56d51331
Ausnahmecode: 0xe0434352
Fehleroffset: 0x000c6ed8
ID des fehlerhaften Prozesses: 0xf14
Startzeit der fehlerhaften Anwendung: 0x01d182b0b1eb7770
Pfad der fehlerhaften Anwendung: C:\y500\BiosFixer_2.0.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
Berichtskennung: 044660e7-6c8d-45c6-a2d6-2f9171dd5d71
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

 

Seems it's not compatible with Win10 x64 ?

 

PS: AV disabled, only Windows firewall active, All Updates done. No "TuneUp" tools installed in any kind

Edited by maxim008

Share this post


Link to post
Share on other sites
21 minutes ago, maxim008 said:

Hm ... It's pretty strange.

When i try to start the "BiosFixer_2.0" i can see it starting in the task-manager, but i see no window.

The windows log got errors:

  Reveal hidden contents

Anwendung: BiosFixer_2.0.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.NotSupportedException
   bei System.Windows.Input.ModifierKeysConverter.GetModifierKeys(System.String, System.Globalization.CultureInfo)
   bei System.Windows.Input.ModifierKeysConverter.ConvertFrom(System.ComponentModel.ITypeDescriptorContext, System.Globalization.CultureInfo, System.Object)
   bei System.Windows.Input.KeyGestureConverter.ConvertFrom(System.ComponentModel.ITypeDescriptorContext, System.Globalization.CultureInfo, System.Object)
   bei System.Windows.Input.KeyGesture.CreateFromResourceStrings(System.String, System.String)
   bei MS.Internal.Commands.CommandHelpers.RegisterCommandHandler(System.Type, System.Windows.Input.RoutedCommand, System.Windows.Input.ExecutedRoutedEventHandler, System.Windows.Input.CanExecuteRoutedEventHandler, System.String, System.String)
   bei System.Windows.Documents.TextEditorSelection._RegisterClassHandlers(System.Type, Boolean)
   bei System.Windows.Documents.TextEditor.RegisterCommandHandlers(System.Type, Boolean, Boolean, Boolean)
   bei System.Windows.Controls.TextBox..ctor()
   bei System.Windows.Baml2006.WpfSharedBamlSchemaContext+<>c.<Create_BamlType_TextBox>b__1035_0()
   bei System.Windows.Baml2006.WpfKnownTypeInvoker.CreateInstance(System.Object[])
   bei MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstanceWithCtor(System.Xaml.XamlType, System.Object[])
   bei MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstance(System.Xaml.XamlType, System.Object[])

Ausnahmeinformationen: System.Windows.Markup.XamlParseException
   bei System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
   bei System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
   bei System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
   bei System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
   bei System.Windows.Application.LoadComponent(System.Uri, Boolean)
   bei System.Windows.Application.DoStartup()
   bei System.Windows.Application.<.ctor>b__1_0(System.Object)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.DispatcherOperation.InvokeImpl()
   bei System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   bei MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   bei System.Windows.Threading.DispatcherOperation.Invoke()
   bei System.Windows.Threading.Dispatcher.ProcessQueue()
   bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   bei System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   bei System.Windows.Application.RunDispatcher(System.Object)
   bei System.Windows.Application.RunInternal(System.Windows.Window)
   bei System.Windows.Application.Run(System.Windows.Window)
   bei BiosFixer_2._0.App.Main()

 

 

  Reveal hidden contents

Name der fehlerhaften Anwendung: BiosFixer_2.0.exe, Version: 1.0.0.0, Zeitstempel: 0x51d7dfab
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.14279.1000, Zeitstempel: 0x56d51331
Ausnahmecode: 0xe0434352
Fehleroffset: 0x000c6ed8
ID des fehlerhaften Prozesses: 0xf14
Startzeit der fehlerhaften Anwendung: 0x01d182b0b1eb7770
Pfad der fehlerhaften Anwendung: C:\y500\BiosFixer_2.0.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
Berichtskennung: 044660e7-6c8d-45c6-a2d6-2f9171dd5d71
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

 

Seems it's not compatible with Win10 x64 ?

 

PS: AV disabled, only Windows firewall active, All Updates done. No "TuneUp" tools installed in any kind


I did it yesterday on Windows 10  x64, i just turn off antivirus and did it. 

Share this post


Link to post
Share on other sites

Does the tool require anything spezial?

Java, c++ 05/08/10/12/13, .net framework 4.6.1 is installed

Share this post


Link to post
Share on other sites
8 hours ago, CanTOKER said:

Edit : Game still crashing after 5-6 minutes. Dxdiag error says that graphic card removed or undetected.. :too_sad2:

 

If it doesn't happen at stock, then the OC is unstable.

 

8 hours ago, CanTOKER said:

And also check the picture, there are some drops after i open the game ; voltage drops from 1050 mV to 0.812 mV than its going again to 1000 mV than 1050 mV..
 

55555.jpg

 

7 hours ago, CanTOKER said:

For now, at desktop i just saw that kind of drops at Ultrabay GPU. Everything was OK, but my voltage's are not stable..

Check this out ;imageproxy.php?img=&key=2ac7e5ac02b90b29

77777.jpg

666666.jpg

 

Looks OK to me. If adaptive power mode is selected in Nvidia driver, it will dynamically switch P states (hence frequency and voltage) depending on load. You can change it to prefer max perf if desired to prevent this.

 

You're using a voltage offset of +162.5 mV in Inspector, which is effectively a +50 mV overvolt, or 1.05 V. The reason max voltage is reported as 1.087 V is that the normal vBIOS behavior will drop it down to 1.05 V after GPU reaches ~60C. Same behavior is observed on stock voltage but it drops from 1.025 V to 1 V.

 

Share this post


Link to post
Share on other sites

So I've gone through this entire thread and about 3 dozen others over the span of about 20 hours trying to get all the correct software together. Almost none of the software on this website (that I paid the 6 bux for) is usable. My computer says this application isn't compatible then the few that do start are missing the .bat file so I can't even use them. The HP boot usb maker doesn't move any files to the flashdrive at all and just freezes my computer at bootup. I have no idea where to go from here as I have no idea where to even start when I can't backup my bios or even modify it.

Share this post


Link to post
Share on other sites
1 hour ago, Jecklen16 said:

So I've gone through this entire thread and about 3 dozen others over the span of about 20 hours trying to get all the correct software together. Almost none of the software on this website (that I paid the 6 bux for) is usable. My computer says this application isn't compatible then the few that do start are missing the .bat file so I can't even use them. The HP boot usb maker doesn't move any files to the flashdrive at all and just freezes my computer at bootup. I have no idea where to go from here as I have no idea where to even start when I can't backup my bios or even modify it.

 

There are a LOT of steps, and different tools being used. If you'd like some help, then you've got to try things step by step. You'll need GPU-Z or NvidiaInspector to see your current settings (and bios, etc). Screen shots of the errors, etcs. It's not easy, but it isn't that hard either. I had trouble at first, but figured it out by doing things SLOWLY. 

 

I'd say a GPU-Z or InvidiaInspector screenshot of your current state to start. And info on your current OS and hardware. 

 

 

Share this post


Link to post
Share on other sites

@Jecklen16

when you even didn't get your boot-stick on running, you, my friend, are doing it wrong. and it's not the forums fault, but yours.

even thou, when you not even say which errors your pc is showing, you wil get no help, cause the ppl here are no psychics

Share this post


Link to post
Share on other sites

I'm getting Error 28 with fptw64. Unfortunately, prr2 that fixes this error isn't compatible with x64. The instructions at the beginning don't address x64 issues and 95% of the posts deal with GPU issues. There's no way to search these 80+ pages for details and cross referencing the entire site only yields ~4 results and only 2 deal with error 28. With no answers. I've run through my 10 downloads for 6 bucks thinking my downloads were corrupt. Where do I go from here? I just need to replace this faulty wifi card. 

Share this post


Link to post
Share on other sites

Okay I submitted the screenshots of Nvidia inspector for both of my cards. My setup is a Lenovo y500 with windows 10 64 bit. My bios is on version 2.04. I have an i7-3630QM, 8 gigs of DDR3.

 

I assumed the flashdrive didn't load the correct files because there were no files on it, unless when you create a boot drive the files are invisible.

Card 1.png

Card 2.png

dxdiag.png

Share this post


Link to post
Share on other sites

@octiceps 

Really thank you, i did it and it is working well for last 48 hours.

I'm running my gpu's with 1150/2400 with 1.075 V. Also the temperatures were not so high ( after 2-3 hours play GPU's 81-82 C max. ; processors 83 C max.)

Thank you for your helps.

@Jecklen16

I did this 3-4 days ago on Windows 10 x64 with BIOS v2.04. First thing, you cant see what is inside the USB. For me it was the same, I coudn't see something inside USB but it was OK for MS-DOS restart. It was working.

Second thing everything you download were for MS-DOS, not windows. You should read again, trust me it is so easy.

Good luck.

  • Thumbs Up 2

Share this post


Link to post
Share on other sites
On 2/3/2013 at 6:38 AM, svl7 said:

Lenovo Y400 / Y500 - 'unlocked' BIOS / wwan-wlan whitelist removal + modified VBIOS for higher overclockin

 

 

 

Thanks very much for all this information.  I recently upgraded my modem, router, and pc wireless to AC.  I knew that I could eventually upgrade the wifi on the 3 year old Y500, but didn't know all the steps.  I found a cheap/ used intel 7260 that I hope will help improve my laptop.  Will report back once I get going. 

Share this post


Link to post
Share on other sites
14 hours ago, Jecklen16 said:

Okay I submitted the screenshots of Nvidia inspector for both of my cards. My setup is a Lenovo y500 with windows 10 64 bit. My bios is on version 2.04. I have an i7-3630QM, 8 gigs of DDR3.

 

I assumed the flashdrive didn't load the correct files because there were no files on it, unless when you create a boot drive the files are invisible.

 

Ok. Cool. See in the NvidiaInspector pic, for GPU 1, you should see the Bios ends in 33, you know that it's still un-modded.

 

First thing is make a backup of your current bios:

  1. Get that FPT Windows x64 version you downloaded from this site.
  2. Un-zip it somewhere you can find it. It helps to create a new folder for it.
  3. Open a Command Prompt as an Administrator. [Right click the Win-key, click "Command Prompt (admin)"].
  4. Change the directory to where you unzipped the fptw63.exe files. (If you don't know how to do this, this may be too advanced for you.)
  5. Within the directory you unzipped those files, run the following: 
  6. fptw64.exe -d bkupbios.bin -bios
  7. You should NOW see a new files called bkupbios.bin in that directory. 

Next make that USB Bootdisk. (I had problems with making a USB bootdisk with the HP tool they recommended too. Mine was also blank.)

 

  1. Get Rufus: http://rufus.akeo.ie/
  2. Use that to make a Freedos USB Boot drive.
  3. It should have files on it.
  4. Then follow the original directions, and report. 

Hopefully the rest of the steps work.

 

 

  • Thumbs Up 2

Share this post


Link to post
Share on other sites
1 hour ago, musarraf172 said:

Can Anybody help me to download BiosFixer_2.0.exe ??

 

Look up. :rolleyes:

Edited by octiceps
  • Thumbs Up 2

Share this post


Link to post
Share on other sites

I got my new wifi adapter and will be installing today hopefully. 

 

So far I was able to make the bootable drive and do a back up of my bios, but when I run the bios fixer, it doesn't run like it does in the pictures.  It makes a black dos command type window. 

 

It asks for the bios file so I drag and drop the back up copy and it says to enter the name of the modified backup bios.  It's there I get stuck and I am not sure what to do.  I was thinking maybe I used the wrong file or set the bios fixer utility incorrectly, but I'm not sure where I messed up.  In the tutorial it makes a modified bios.

 

Any advice would be greatly appreciated. 

 

Thx!

 

Edit:  Last week I updated the 2.02 bios to 2.04 directly from lenovo

Y500

Windows 8.1

 

Edited by L8show

Share this post


Link to post
Share on other sites

@L8show

Hi, i was taking the same mistake. When i was trying to drag the Backup Bios file to the program, the program wasn't react. So try to take your bios backup with diffirent method (you can find on google) and check it's extension.

I remember that my backup bios's extension was ".bin" but when i drag ".bin" file, it wasn't react, so i find a different way to backup my bios and my bios backuped with ".rom" extension. When i drag ".rom" backup file, the program suddenly reacted and created a modded bios file. (but you must drag again and again until the program react :whistle:)

 

Good luck.

  • Thumbs Up 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By PepoJ
      Hello there!
      I am new on the forum. I'd need some help. I own a lenovo ideacentre t540-icb g, and i would need to unlock all the options in my bios, especially overclocking and thermal configuration. I tried with both amibcp and mmtool, but i didn't succeed (Error 18).
      I wonder if you could help me or give me some advice.
      Thanks in advance.
    • By thinkdad
      Hi,
       
      I need help in fixing my Thinkpad.

      I just got a T440p yesterday. It was working perfectly until the following:

      I reinstalled Windows and then I installed Vantage.

      I installed all the latest drivers.
      I also choose to install the bios update. The bios update ran in Windows and it asked me to restart. After restarting, the screen was blank. I tried powering it off and on and I saw the Thinkpad logo but after that the screen was blank.

      I tried powering on and off again and there's no Thinkpad logo now and the screen is just blank with the green power on. No sound, no nothing.


      Here's what I tried:
      Pressing the power button 10 times and then holding it for 30 seconds. Unplugged and battery is detachted Detached the CMOS battery and the reattached it Removed the ram, harddisk and optical disk drive. Attached the battery and inserted the charger. I turned it on and there was a couple of beeps Tried pressing FN+R and created a bootable USB I'd like to ask: How do I fix this? What do I need to do?
      Can I reflash the bios in some other way? Do I need to buy a new motherboard? Will this solve the issue? It's my first thinkpad and I'm really excited but I was bummed out that this happened. Can you please help me?

      Thanks in advance!
    • By pippocarlot
      Hello everyone! I am looking for an answer to a problem I cannot find a solution to ... I purchased an Amd wx 4150 MXM GPU module su e bay to upgrade my HP 8570W Mobile Workstation which is currently equipped with a Fire Pro M4000. Once the new GPU has been installed, the PC screen no longer turns on but works only with external monitors connected via the docking station. The same happens once the drivers are updated! If I put the old card back on, the integrated monitor starts working again ... How can I fix it?
    • By Swick1981
      Bios Release Version – v2.0.0
       

       
      Updated or Modded Items:
      A11 UNLOCKED BIOS FOR m18Xr2 (UNLOCKED BY SVL7 AND FULL CREDIT GOES TO HIM FOR UNLOCKING!)
      SVL7 Also created the PRR2.EXE tool that allows you to flash the new bios by unlocking it.  (FULL CREDIT GOES TO HIM FOR THAT FILE PRR2.EXE)
       
      Here are ALL the things I've added, modded, and enhanced on this bios -
      I've added FULL LEGACY SUPPORT ON THIS BIOS with ONE or TWO CARDS (SLI).  You can FINALLY use Win 7 OS on your machine and run the 900 series GPU's! 
      This is a MAJOR breakthrough!
       
      LEGACY SUPPORT Confirmed.  Works with 900 series GPu's in single OR SLI formation Updated the Intel RST Legacy to v12.9.0.2006 (Supports TRIM in RAID0 - CONFIRMED) Updated Intel RST UEFI to v12.9.0.2006 (Supports TRIM in RAID0 - CONFIRMED) Updated the ONBOARD Video Card for the HD3xxx to v2171 - FROM v2132 Updated ONBOARD Video Card for the HD4xxx to v2171 - FROM v2132 Updated the LAN Firmware & PXE Boot from 2.0.5.9 to v2.0.6.6 ADDED NvMe Support for m18xr2 ADDED M.2 support for m18xr2 Updated CPU Microcode to v29 for the 2900 CPU's Updated CPU Microcode to v1c for the 3900 CPU's Updated GOP Driver for Intel Sandy Bridge CPU Updated GOP Driver for Intel Ivy Bridge CPU Updated MAIN GOP Policy module for the m18xR2 Eliminated some code that wasn't used in the m18xR2 Updated CSM Module (v2) Streamline some coding to make mod(s) run a little more efficiently (v2) Added FPARTS.TXT to rar file in v2. (I had forgot to add it in v1) v2.5 to be released shortly.  I've updated a few more modules that I didn't realize could be updated.  (It's only 3 modules, but it's still an update!)   It should be released in about a week.  Hope this helps ya'll!  
      Instructions to flash:
      Use a flash drive to create a boot disk into dos Unzip ALL files into the root of the flash drive (flash.bat, r2final.bin, fpt.exe, flash.bat, prr2.exe, fparts.txt,m18r2.hdr, m18r2.hdr.bin, readmefirst.txt) BOOT INTO DOS – Note, that when you set the bios to legacy in order to boot into dos, you MAY have to reinstall OS!  (Just be prepared to reinstall no matter what) Once you boot into dos, run the file flash.bat It will unlock your bios (THANKS TO SVL7’s BIOS UNLOCKING TOOL – ALL CREDIT TO HIM FOR THIS TOOL!) Let it flash… Reboot your pc, and enjoy the MASSIVE updates!  
      Be on the lookout as I do plan to release newer version with more updates in the future.  However, it wont be for at least a few weeks as I'm now working on legacy support for the m17xR4 and several other systems.  So please be patient!
       
      ENJOY!
       
      Thread link for more information and discussion:
       
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. 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.