Blacktape

I am looking for information on the procedures to replace the integrated BIOS Logo on several laptops. The model numbers are the P650HP6-G, and P650HS6-G. In the past, we have been able to replace the logo on those BIOS's using an Asus BIOS Logo tool, and Secure ROM Signing tool successfully. However, with newer BIOS updates, I have been getting an error message "18-Error: Secure Flash ROM Verify Fail." So I have been staying with older BIOS versions instead of trying to force a bad flash. The P650HS is still using a .BIN for the main BIOS flash file, however, the P650HP6-G has changed from a .ROM to a .8M or .04 file, depending on which method of flash used. One file size is very different from the other (most likely because of a combined ME and BIOS flash code in one file. The trouble is, I am unsure whether these are to be seen as a normal BIN or ROM file, just named differently, or as a completely different type of file. I am using the BIOS flash file that is used only for the BIOS, which should be free from abnormal code arrangement for multiple components. I am in need of an appropriate Logo replacement utility, as well as the digital signature utility for Secure boot. If there is the matter of having a valid key assigned to the company for this purpose, I can present that to my managers for their follow up. --------------------------- I realize I should have posted this in the parent forum, I do not have the options to remove this message though, as far as I know. You may if you can, I will post a copy in the parent forum.

I am looking for some software that I can run on laptops to verify the correct operation of the Fingerprint Reader. We are installing the basic drivers so that the device is operational, but we are not installing the security suite that comes with it, unless specifically requested by the customer. When we first carried the Clevo W150HNQ, the software suite allowed the testing of the fingerprint reader without creating accounts or registering finger prints in the Demo Mode. I was wondering if there is a small program that I can run, without installation, that will show me the input from the fingerprint reader each time it is use, so that I can verify that it has not been affected during the disassembly, painting and reassembly processes. I have been searching for a program to do this for a few years now, and have still not found anything that even comes close (except for that initial version of the security software, which has been verified to be insecure).

In the same area of expertise: I am working on my Bosses P157SM (not SMA), and it has the original BIOS on it (1.00.01) and /had/ the original EC firmware (1.00.1) as well. The problem I am running into, is trying to flash the BIOS forward to one of the latest, 1.03.01 . We found the 1.03.01 package on the Clevo Mirror and downloaded it, and flashed in pure DOS. The EC flash worked fine, but the BIOS keeps returning a mismatched Bios ID. I have two ROM files in the BIOS flash directory, one is P15sm.301, the other is P15sm6m.301. Both of them are giving me the ID mismatch errors in their own way (one is a string of flash commands.) The System has the IDs: ROM ID = P150SM ROM GUID = b5c59087-feac-4b41-9d80780ba5aa070f The Rom File p15SSM6M.301 has the IDs: ROM ID = P150SM ROM GUID = 76183244-c0c1-469a-acb9bd90ca0f0f87 and the Rom File P15sm.301 has the IDs: ROM ID = P150SM ROM GUID = 76183244-c0c1-469a-acb9bd90ca0f0f87 The question is.. Would it be safe to override the ID check and force the flash (/x), or am I going to brick this board by doing so? This is the only system of this model that we have in house, and getting replacement boards for this is rather hard at this time.

I had been contacting Sager for their procedures, and they were giving me an EFI method. While I was able to boot into the EFI environment, (which was kinda cool to figure out) the flashing still didn't work, so I went back to old proven methods.. Dos. So far, it's worked flawlessly each time, for both the P650RE and P650RG. We also figured out how to insert a custom logo into it as well, and I am much happier to be shipping a completed product. Edit: Also, the 1.05.13 bios for the P770DM-G is no longer giving 7B bluescreens when booting into a new OS image. Yay!

As of the time you posted this link, I was able to follow the link to the correct page, but I wasn't able to get the download to work. Now that I try the link again, it leads to a page titled and for a file called: Dusk - 07 - Audio - Dusk-Pizz - 09 - Instrument - pizz-01.wav (44.42 MB) which is not the ESM...

Ok, I found the P65xSE, SG, and SA models on your ESM listing, but I haven't seen any mention of the P650RG, and P650RE models. After looking though the Service Manual, it appears the chassis are Identical, and the operative changes are the Nvidia chips. For now, that is an insignificant difference for my uses.. though other departments aren't going to take it with a grain of salt, so I am still looking for the specific ESM's for both the RG and RE.

You are referring to the P650RE or RG models? I can post step by step instructions with pictures if you need. Edit: Not applicable. Phoenix model is P870DM(-G), I have not worked on those.

Unfortunately, one of the reasons I am looking for the P650RE/P650RG service manual, is to see if there are any specific BIOS flash procedures I should be observing. The updated BIOS CD's come with a variety of ways to flash the BIOS/EC, but they do not provide any instructions for this particular model of laptop. I have flashed these laptops successfully on several occasions, however, I have recently had two that bricked on me, due to the flash program crashing during the flash process in windows. I would like to get the proper flash order/procedure set up for DOS application, but a little explanation on all the tools, preset modes, and programs would be beneficial.

Awesome, this is the only place that I've been able to find the service manual for the P770DM-G Series.. hopefully the site will allow me to access the download in time. I'm dealing with some interesting issues on a system in production.