Bios for Insys GW1-W149 or GW1-W148

[lulox]

Please someone have clean bios for this models?

GW1-W149 or GW1-W148

Or can clean the ME on this files please

[SMDFlea]

Please someone have clean bios for this models?

GW1-W149 or GW1-W148
Or can clean the ME on this files please

Type the laptop serial number, full name and model, motherboard model, etc.

read the forum rules..https://www.badcaps.net/forum/troubl...before-posting

[lulox]

Type the laptop serial number, full name and model, motherboard model, etc.

read the forum rules..https://www.badcaps.net/forum/troubl...before-posting

Sorry i forgot

Brand: Insys
Model: GW1-W149
Serial: GW1W1490129288
Motherboard: EM_IC218_376B_V2.0

[boneco69]

Hello. I have similar problem with one of these boards - I have one school laptop that i need to fix that have the BIOS "corrupted" - do not even boot to BIOS it self. Changing the UEFI from another (damaged) board and the system boots to UEFI but refuses "to see" (it blocks the access to) the SSD. NOTE - Can boot to USB Linux in it but the SATA SSD wont show up in kernel. Of course cannot boot to Windows because i do not have the SSD functional.
Now,t his is clearly some ME or the security module (CUCo) inside that is blocking or not enabling SATA interface. Using UEFITool we can see exactly that module in the flash file.

I am trying to detect where the serial number is stored so i can copy (or write it) to the known good boot UEFI. I have contacted the importer asking them if they can send me an original file to flash it but they refuse - they want to sell another motherboard... so is not an option. The motherboard is good...

I do not think that cleaning the ME region will resolve the issue. There are some scripts that disable ME - i am reading them and try to see if i can.
Trying also to clean NVRAM, because it can cause freezing in some laptops after the BIOS could even switch on the graphics.

Comparing the EC zone and the BIOS (code) modules between two files (dumped both bios chip) they are equal - so the problem is in the "data" segments (NVRAM) not the code (but it is buggy because of this lockup).
The UEFITool can extract all modules without any problem in any of this two dumps, so the "corruption" is not bad flashing or bad flash sector, or else there were errors.

NOTE/IMPORTANT: I do not want to disable nor remove the CUCo module because it is needed to be there - so we can block the computer if conditions apply. But i want to know how to fix this UEFI so i can repair future cases - those are school laptops and if we can save some money to the organization, better.

[SMDFlea]

post your backup and serial number, let`s see if it can be fixed

[boneco69]

Hello. I have similar problem with one of these boards - I have one school laptop that i need to fix that have the BIOS "corrupted" - do not even boot to BIOS it self. Changing the UEFI from another (damaged) board and the system boots to UEFI but refuses "to see" (it blocks the access to) the SSD. NOTE - Can boot to USB Linux in it but the SATA SSD wont show up in kernel. Of course cannot boot to Windows because i do not have the SSD functional.
Now,t his is clearly some ME or the security module (CUCo) inside that is blocking or not enabling SATA interface. Using UEFITool we can see exactly that module in the flash file.

I am trying to detect where the serial number is stored so i can copy (or write it) to the known good boot UEFI. I have contacted the importer asking them if they can send me an original file to flash it but they refuse - they want to sell another motherboard... so is not an option. The motherboard is good...

I do not think that cleaning the ME region will resolve the issue. There are some scripts that disable ME - i am reading them and try to see if i can.
Trying also to clean NVRAM, because it can cause freezing in some laptops after the BIOS could even switch on the graphics.

Comparing the EC zone and the BIOS (code) modules between two files (dumped both bios chip) they are equal - so the problem is in the "data" segments (NVRAM) not the code (but it is buggy because of this lockup).
The UEFITool can extract all modules without any problem in any of this two dumps, so the "corruption" is not bad flashing or bad flash sector, or else there were errors.

NOTE/IMPORTANT: I do not want to disable nor remove the CUCo module because it is needed to be there - so we can block the computer if conditions apply. But i want to know how to fix this UEFI so i can repair future cases - those are school laptops and if we can save some money to the organization, better.

Ok, so lets see what you can make.
Attached is the "BAD" flash with its serial number in its name (GW1W1490006778), and
one that is working ok in its respective motherboard (GW1W149001227). As i wrote before, if i solder the "OK" chip in de "BAD" motherboard, the system works aside the SATA port not "detected".
Note: I uploaded ZIP file because i can not upload bin. The "_OK" and "_BAD" part, of course, are not in the Serial Number...