Clevo BIOS to Sager BIOS

If you flashed your Sager laptop with a Clevo BIOS, it is generally not recommended to go back to a Sager BIOS, since this will most likely brick your machine. This applies to models produced after 2010, like the P150HM, P170HM, etc., previous models, like the M570TU should not be affected.

There is however a method discovered by Prema that should allow you to flash back to a Sager BIOS.

This involves flashing both the EC and BIOS one after the other without restarting the laptop.

This method is not without risks, and it is highly recommended to only use it if you are really desperate.

In order to do this, you must edit the ".bat" file (this file may be: autoexe.bat, update.bat, step1.bat, ECFlash.bat, etc) that is responsible for flashing the EC and remove the
from this line "afudos EP15HM13.sa1 /E /shutdown" - the "/shutdown" part

Ex:


Go into DOS and flash the EC using the new bat file.
After the EC has been flashed, don't restart the laptop! Just go and flash the BIOS.

You should be fine.

 

And what about the other way around?

I've a Sager BIOS 1.0.0.7 on my Clevo x7200.

 

It's fine to switch from Sager to Clevo, you just use the normal method from the Clevo BIOS thread.

 

I want to express my utmost gratitude to Sir Blacky as this guide has worked flawlessly for me and my NP8150

(I almost wet myself from the tension during the flashing process )

 

Got a question on that matter:
I flashed the most recent SagerBIOS on my X7200 and wanted to update it with the BIOS Mod to unlock OC options from this thread. I flashed the BIOS using a CD-RW, but as the author of the mod suggests I used a bootable Win98 DOS USB-Key to flash the modded BIOS. I got the following error message after typing "bios.bat": "Cannot flash when Memory Managers are present"

Any ideas how to get it to flash?

 

When you start up with the bootable USB stick, press F8 key, a menu will appear, choose safe mode, then no memory managers drivers are loaded

 

Then he can't flash the BIOS if he's loading into safe mode right? He needs to do it in pure dos. When you boot off the USB, it goes to DOS, not Windows.

 

Rufus - Create bootable USB drives

 

Nice guide Prema, but is this any different from my USB DOS drive? I already used my USB key to flash the VBIOS several times, so it works... just the BIOS does not like it being a memory thing

 

In win98 there is a safe mode boot for "dos-promt" since he is using a win 98 dos usb stick. This mode boots in to pure dos that does not load Himem.sys or EMM386 memory managers. We're not talking about the GUI Safe Mode.

 

Ah alright. Yes I got the EMM386 memory error code.
So I should just press F8 repeatedly when the USB boot begins?

 

Yes, and then you press F5 when the Dos-boot menu appear, which is safe-mode dos prompt, with only 640kb of memory available. That is the mode I always flash bios updates in.

 

What about Eurocom machines? Can i use Sager NP9280 (D900F) BIOS in a Eurocom Panther Mobile Workstation (D900F)??

I noticed Sager has a newer BIOS update from 1.00.05cs / 1.00.02sa to 1.00.09cs/1.00.04sa.

 

Eurocom uses Clevo Bioses. So it's the same as any other Clevo to Sager BIOS transition.

 

mmmmm.... I think I might be just one step before getting into trouble. I have a SAGER NP7338 (CLEVO W2300ss). After receiving my machine I went and flashed Prema's BIOS. Now I find that my sound card is getting some problems ( see here) And asked SAGER to send me my original BIOS to flash it back. How bad under risk am I? I flashed Clevo's stock rom and I have a message saying that vendor and hardware IDs don't match.. but apart from that all is fine (sound problem still remains). I wanted to try the original SAGER BIOS up to the moment I found this thread... can you people give me an advice?

Thanks so much!

 

Does this apply solely to Sager? What about flashing another vendor's bios to Clevo, can that be reverted back from Clevo to that particular vendor's without a problem?

 

This doesn't apply at all, don't worry...its a story a certain company made up when they send a customer a non-matching EC/BIOS combination which bricked his board.
It has nothing to do with being any vendor version, BIOS and EC have to be compatible, that's all.
All my stock BIOS and Mods flash matching versions in one go.
If you update BIOS and EC separately, then always flash the new EC first then only the BIOS and try to avoid major EC downgrades as that sometimes may not end well.