A community for the repair bench. Since 2022.LAPTOP + DESKTOP BOARD REPAIR
Advertisement
EC / KBC BIOS Unlock Service Unlock MEC17xx, Nuvoton, ITE using BIOS patch BIOS patch · Private check · Verified owners and repair technicians MEC17xxNuvotonITE

ASK 820-01987-A SoC Rom Dump

Laptops and Desktop Bios, Schematic and Boardview Files And Repairing Discussion
Search files by board code
Browse all 32,531 files →
Hello, I have a 820-01987 that I need a SoC Rom image for. Whoever programmed it when I bought the board it was banned from activation and I just want to clear whatever junk was programmed in it with a fresh image. Just hoping someone out here may have access to it.
 
About this board

This thread is for the SoC Rom with main board 820-01987-A.

Files wanted for this board
  • EFI firmware (full SPI ROM dump)
  • Schematic (PDF)
  • Boardview (.brd / .bdv / .cad)

Typical reasons to reflash: no boot or no chime after a firmware update, a firmware (EFI) password lock, or a corrupted ROM after liquid damage.

Before flashing, always read and save the original chip. It holds the serial number, UUID, MAC address and ME data for that exact machine.

Have a tested file for 820-01987-A? Reply below and help the next technician. Looking for something else? Search all files in the File Finder.

Hello, I have a 820-01987 that I need a SoC Rom image for. Whoever programmed it when I bought the board it was banned from activation and I just want to clear whatever junk was programmed in it with a fresh image. Just hoping someone out here may have access to it.
Please sent back cover photo Emc model need
 
I don't have the EMC number as the board was bought without any information :(
It was bought to replace a burnt out board
 
give me a bit, I need to take all the electronic components off the blown T201 and install pins to go into my programmer so I can use the socket
 
The old bin showed the error I do believe 4010. I would have to force it into DFU mode as it was stuck in recovery. The bin you all made worked perfectly as soon as I connected to the other mac it went directly into DFU mode without forcing it and it looked like it was going to work this time but then threw the error and when closed the error it went right into recovery. I'll check the board one last time maybe something fell off when it was stored with three other boards. But i may think after the very first time it booted and threw a fit about being a banned serial number when it was online, it may have corrupted the T2 to beyond repair.
 

Make PKBIOSFIX part of your bench.

Professional resources. Shared experience. A stronger repair community.

Explore PRO
Back
Top