Medion Akoya E6232 Bios Bricked Need some advice/help (Solved)

Hi all,

I did something stupid, I was trying to flash my modded Aptio IV bios I just changed some settings to “User” using AMIBCP, however I flashed it using flashrom… (Instead of afudos /gan) and the bios was only 6 MB and not 8, So i think it was not a full SPI flash.

Now the notebook is not turning on at all, two lights just keep blinking nothing more then that. I feel so stupid because normal i’m so careful doing such things however the excitement got me so far bricking it. So now I ordered a SOIC8 SOP8 Clip and lots of pin headers and I hope i’m able to fix it using my Raspberry PI. I was hoping someone could get me on the right track.

(Current BIOS BRICKED)

BIOS DATE: 08/20/12 20:43:45 VER: 04.06.05 (6MB)
Motherboard Name Medion E6232 MSN 4004 2827

BIOS Type AMI EFI
BIOS Version 0.26
System BIOS Date 08/20/2012
Video BIOS Date 04/26/12

Bios Chip Motherboard:

Winbond 25q64fvsig (8M-byte)

Datasheet:

https://cdn.sparkfun.com/datasheets/Dev/Teensy/w25q64fv.pdf

Edit:1

I found a other rom file full SPI flash (8mb) see below:

Edit 2:

Bios fixed by using SOIC8 test clip and Raspberry PI.

medion akoya E6232.-0.26.zip (2.65 MB)

(Bios found on the internet FULL SPI V0.24 8MB)

Storage Controller BIOS modules:

Intel RST EFI and OROM (DevID 2822/282a):
Ø 11.2.0.1527
Ø 11.6.0.1702
Ø 12.9.0.2006
Ø 13.1.0.2126
Ø 13.2.0.2134/13.2.2.2224
Ø 13.5.0.2164
Ø 14.8.2.2397
Ø 15.1.0.2545
Ø 15.2.1.2771
Ø 15.5.0.2760

Intel RST enterpise EFI and OROM (DevID 2826, 2827, 1d68/1d69):
Ø 3.8.0.1029
Ø 4.5.0.1012 SATA and sSATA + 4.3.0.1018 SCU

AMD:
Ø 3.3.2.0 (AHCI OROM DevID 4391/7801)
Ø 3.3.1540.19 (RAID OROM DevID 4392/4393/7803)
Ø 3.3.1593.20 (RAID OROM DevID7802)
Ø 1.0.0.49 (RAID Driver and Utility)

AMD RAIDXpert2 EFI and OROM (DevID 8803/8804):
Ø 6.1.4-00059/6.2.0-00060
Ø 7.1.0-00076/7.1.0-00064

Marvell 88SE91xx/92xx EFI:
Ø 1.1.0.1020 (AHCI)
Ø 1.1.0.1015 (RAID)

Marvell 91xx/92xx OROM:
Ø 1.0.0.1038 (DevID 9120/91a0, 9123/91a3, 9128, 9130)
Ø 1.0.0.1034 (DevID 9172/917a, 9182/918a, 9192/91a2)
Ø 1.0.0.1024 (DevID 9230)

ASMedia 106x OROM (DevID 611/612/613):
Ø 0.951
Ø 0.97
Ø 3.80

JMicron SATA Host Controller:
Ø 1.07.28 (OROM DevID 2362/2363)
Ø 1.08.01 (OROM DevID 2363)

Graphics Controller BIOS modules:
Intel EFI GOP Driver:
Ø 2.0.1024 – SandyBridge
Ø 3.0.1030 – IvyBridge
Ø 5.5.1033 – Haswell and Broadwell
Ø 9.0.1056 – Skylake and Kabylake

AMD EFI GOP Driver:
Ø 1.60.0.15.50 (MS signed)

Ethernet Controller BIOS modules:
Intel LAN only chips 82579/i217/i218/i219:
Ø 0.0.14 EFI Gigabit Undi
Ø 0.1.10 OROM Boor Agent CL

Intel LAN only chips i210/i211/i350:
Ø 7.3.20 EFI PRO/1000 Undi
Ø 1.5.81 OROM Boot Agent GE

Intel LAN chips 82579/i217/i218/i210/i211/i350:
Ø 6.6.04 EFI PRO/1000 Undi
Ø 1.5.62 OROM Boot Agent GE

Intel LAN 10GbE chips:
Ø 5.5.15 EFI 10GbE Undi
Ø 2.3.72 OROM Boot Agent XE

Realtek LAN:
Ø 2.037 EFI Undi
Ø 2.64 OROM PXE Boot Agent

Qualcomm-Atheros LAN:
Ø 2.0.6.6 OROM PXE Boot Agent old
Ø 2.1.1.5 OROM PXE Boot Agent new

Broadcomm LAN:
Ø 17.2.2 EFI NetXtreme Undi
Ø 17.2.0 OROM PXE Boot Agent

Intel CPU microcode BIOS modules:
Sandy Bridge/Ivy Bridge
Sandy Bridge-E/Ivy Bridge-E
Haswell/Broadwell
Haswell-E/Broadwell-E
Skylake/Kabylake


Intel ME:

Firmware: Intel ME
Version: 8.1.0.1248
Release: Production
Type: Region, Extracted
FD: Locked
SKU: 1.5MB
VCN: 2
PV: Yes
Date: 21/06/2012
FITC Ver: 8.1.0.1248
Latest: No

Stock bios (6MB V0.26): (Caused the brick because I used flashrom)

Storage Controller BIOS modules:
Intel RST EFI and OROM (DevID 2822/282a)
Ø 11.2.0.1527
Ø 11.6.0.1702
Ø 12.9.0.2006
Ø 13.1.0.2126
Ø 13.2.0.2134/13.2.2.2224
Ø 13.5.0.2164
Ø 14.8.2.2397
Ø 15.1.0.2545
Ø 15.2.1.2771
Ø 15.5.0.2760

Intel RST enterpise EFI and OROM (DevID 2826, 2827, 1d68/1d69)

Ø 3.8.0.1029
Ø 4.5.0.1012 SATA and sSATA + 4.3.0.1018 SCU

AMD

Ø 3.3.2.0 (AHCI OROM DevID 4391/7801)
Ø 3.3.1540.19 (RAID OROM DevID 4392/4393/7803)
Ø 3.3.1593.20 (RAID OROM DevID7802)
Ø 1.0.0.49 (RAID Driver and Utility)

AMD RAIDXpert2 EFI and OROM (DevID 8803/8804)
Ø 6.1.4-00059/6.2.0-00060
Ø 7.1.0-00076/7.1.0-00064

Marvell 88SE91xx/92xx EFI
Ø 1.1.0.1020 (AHCI)
Ø 1.1.0.1015 (RAID)

Marvell 91xx/92xx OROM
Ø 1.0.0.1038 (DevID 9120/91a0, 9123/91a3, 9128, 9130)
Ø 1.0.0.1034 (DevID 9172/917a, 9182/918a, 9192/91a2)
Ø 1.0.0.1024 (DevID 9230)

ASMedia 106x OROM (DevID 611/612/613)

Ø 0.951
Ø 0.97
Ø 3.80

JMicron SATA Host Controller

Ø 1.07.28 (OROM DevID 2362/2363)
Ø 1.08.01 (OROM DevID 2363)


Graphics Controller BIOS modules:
Intel EFI GOP Driver

Ø 2.0.1024 – SandyBridge
Ø 3.0.1030 – IvyBridge
Ø 5.5.1033 – Haswell and Broadwell
Ø 9.0.1056 – Skylake and Kabylake

AMD EFI GOP Driver

Ø 1.60.0.15.50 (MS signed)


Ethernet Controller BIOS modules:
LAN

Intel LAN only chips 82579/i217/i218/i219

Ø 0.0.14 EFI Gigabit Undi
Ø 0.1.10 OROM Boor Agent CL

Intel LAN only chips i210/i211/i350

Ø 7.3.20 EFI PRO/1000 Undi
Ø 1.5.81 OROM Boot Agent GE

Intel LAN chips 82579/i217/i218/i210/i211/i350

Ø 6.6.04 EFI PRO/1000 Undi
Ø 1.5.62 OROM Boot Agent GE

Intel LAN 10GbE chips

Ø 5.5.15 EFI 10GbE Undi
Ø 2.3.72 OROM Boot Agent XE

Realtek LAN

Ø 2.037 EFI Undi
Ø 2.64 OROM PXE Boot Agent

Qualcomm-Atheros LAN

Ø 2.0.6.6 OROM PXE Boot Agent old
Ø 2.1.1.5 OROM PXE Boot Agent new

Broadcomm LAN

Ø 17.2.2 EFI NetXtreme Undi
Ø 17.2.0 OROM PXE Boot Agent


Intel CPU microcode BIOS modules:
Intel CPU microcodes

Sandy Bridge/Ivy Bridge
Sandy Bridge-E/Ivy Bridge-E
Haswell/Broadwell
Haswell-E/Broadwell-E
Skylake/Kabylake


Intel ME:

Firmware: Intel ME = None


EDIT by Fernando: This post has been shortened and customized by me (to save space and for a better readability). Hopefully the author will agree. Otherwise I beg his pardon.

EDIT by Toetje583: Updated post using Fernando’s suggestions.

Thanks Fernando,

I will follow the guidelines sorry for that, from now on I will use the right formatting to make it easy for all the people that would like to help me.
is there any reason why you removed the OLD bios report? or perhaps by mistake?

Thanks,

Toetje583

@Toetje583 :
Welcome at Win-RAID Forum and thanks for your detailed informations.

Unfortunately I can not help you personally, because I am not an expert regarding your problem.
Nevertheless I hope, that you will get support by someone else.

Good luck!

Regards
Dieter (alias Fernando)

It was not my intention to remove the OLD bios report. So I obviously have done it by mistake. I am sorry about that.
Please edit the related post and re-attach the OLD bios report.
Thanks!

It was not my intention to remove the OLD bios report. So I obviously have done it by mistake. I am sorry about that.
Please edit the related post and re-attach the OLD bios report.
Thanks!




Thanks for the warm welcome, from the Netherlands!

Updated post.

So if I understand properly, the BIOS you flashed and have attached at the 1st post is proper. It’s just that you used the wrong tool/command and thus flashed the BIOS-only region (6MB) at the entire 8MB SPI image. You basically wrote the BIOS region on top of the Flash Descriptor and ME which come first (4KB FD + ~2MB ME + ~6MB BIOS = 8MB SPI). Correct? In that case, you can take the full 8MB SPI dump you found online, replace it’s BIOS region with your own via UEFITool (same size, ~6MB) and then follow the ME cleanup guide to make that dumped ME region proper for your own system.

@plutomaniac

Thats about right, two years ago this notebook was send back to Medion due some issues with the screen, However they replaced the hole board and somehow the Intel ME device was gone. I didn’t care that time.
So i used Linux to see if i could find the device, but nope so i assumed they flashed a bios without it. So this is where I started to do some stupid things However i still own a 6MB dump, I make it with afudos before I changed anything. The final goal for me is to get a working notebook and ME back :slight_smile:

They changed the board but left the old SPI image intact. The ME is dirty from the old one though and cannot work properly due to reasons explained at Section A of the ME cleanup guide linked above. It cannot be removed, just soft-bricked so to speak (Recovery mode). If your BIOS is proper and you follow what I said above you should end up with a working BIOS and ME, thus a working system.

@plutomaniac Thanks for the fast reply,

If I merge my backup with the version i found, what about the ME protection, I just found this:

"Probing works (Winbond W25Q64, 8192 kB, SPI), but parts of the flash are problematic: descriptor is r/o (conforming to ICH reqs), ME region is locked."

https://www.flashrom.org/Supported_hardware

You have an external programmer so the Flash Descriptor protection does not matter in your case. It matters for software flashing with flashrom, afu, fpt etc. It only concerns the Flash Descriptor itself and the ME, not the BIOS region so that’s why you were able to flash before with AFU. Mind you that the BIOS can have read/write protections of it’s own but these are not related to the FD locks and are irrelevant to what you are trying to do here. Generally, if you want, you can additionally remove the FD lock before you flash with the programmer so that you are able to reflash the whole SPI with software tools in the future but the choice is yours. By the way, no need to tag me with @username, I check the topic regardless.

Thanks, I fully understand now!

Well i wanted to unlock some bios settings aswell after I replaced it, I found out that there are two bios setup images, one text “Setup” and one “oemsetup”.

Seems like once I enter the bios i get this one:

OEMSETUP

But there is also a normal “setup” with as far as I can tell is fully unlocked. I don’t know if there is way to access it but you never know :slight_smile:

OemSetupPage_Compressed_section_body_unc IFR.txt (70.5 KB)

Setup_Compressed_section_body_unc IFR.txt (686 KB)

I was able to recover the bios using a Raspberry PI and a soic8 test clip, i’m now moving forward to the ME cleanup part :slight_smile:

The system seems to be fully operational :slight_smile:

Thanks for all the feedback!