The host CPU does not have read access to the target flash area.

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � The host CPU does not have read access to the target flash area.

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#1 | The host CPU does not have read access to the target flash area. datum

Sat Jan 21, 2017 12:52 pm (Last edited: Sat Jan 21, 2017 12:59 pm)

Im living this problem when i try to dump my me firmware to harddrive

http://prntscr.com/dyf7oa

how to edit descriptor area ? how can i solve this problem ?

edit: here is my description area dump https://www.sendspace.com/file/p6w4vd

reply

#2 | RE: The host CPU does not have read access to the target flash area. datum

Sat Jan 21, 2017 1:07 pm

You eeprom is locked. The only way to unlock it is via an eeprom programmer
or the pinmod method.

reply

#3 | RE: The host CPU does not have read access to the target flash area. datum

Sat Jan 21, 2017 1:25 pm

what is pinmod method how to do that ?

reply

HP EliteBook 8560w displays "ME is in recovery state at startup" � � HP Laptop Me state recovery, unable to flash firmware: solved

Please enter a reason for warning.