(UEFI) Dell XPS 15z L511z modded BIOS - and HOWTO

[jkbuha]

I tried disabling ME from BIOS, but with same result.

One thing I realized though - I can actually dump the 4MB descriptor file through ftpw.exe -DESC -D <filename>. Could we modify the descriptor, re-flash and enable ME modding?

EDIT: Oh this is interesting. We *can* modify the descriptor.

1) Dump your Desc table via fptw.exe -DESC -D DESC.BIN
2) Open FITC and load up DESC.BIN
3) Go to Master Access Section, and select Manageability Engine.
4) Change Read/Write Access...

Can't be that simple can it?

[TimeWalker]

According to Intel if descriptor is unlocked it compromises security on all of the other regions (GbE, BIOS and ME) .. since our native ME has no AMT feature it's highly likely to just say "unable to bla bla" because even if you change the Access flag the current active setting prevent you from writing the region. The funny part is .. it wouldn't have allowed you to dump the region in the first place // oO

You tried disabling ME altogether but I've tried disabling just the ME POST Message, which according to description will not send anything to ME after the POST. This sounds somewhat similar to what flashrom guys had mentioned. But unfortunately this had no positive result for desc. unlock.

[jkbuha]

Well I've prepared a modified descriptor binary but I'm reluctant to flash it. It's a 4kb file with a few modified bytes that can be flashed as follows:

fptw.exe -DESC -F DESC_MODIFIED.BIN

update: doesn't work - most likely because the Descriptor is read only.

Code:

C:\Temp\ME(1.5M_8.1.10.1286)\Tools\System Tools\Flash Programming Tool\Windows>fptw -DESC -F DESC_MODIFIED_COMPACT.bin

Intel (R) Flash Programming Tool. Version:  8.1.10.1286
Copyright (c) 2007 - 2012, Intel Corporation. All rights reserved.

Platform: Intel(R) HM67 Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid

    --- Flash Devices Found ---
    MX25L3205D    ID:0xC22016    Size: 4096KB (32768Kb)

PDR Region does not exist.
GBE Region does not exist.

Error 25: The host CPU does not have write access to the target flash area.  To enable write access for this operation you must modify the descriptor settings to give host access to this region.

[kasar]

yeah, I have an i3
i3-2310m

it could be related I am using drivers version 8.1.10.1275

edit, tried the version timewalker sent to me, and results were different

Intel® MEInfo Version: 7.1.10.1065
Copyright© 2005 - 2011, Intel Corporation. All rights reserved.

PMXUtil: Error during PMX Call: PMxDrv!MAPPHYS - Bad Input Parameters
GBE Region does not exist.
Intel® ME code versions:

BIOS Version: A12
MEBx Version: 0.0.0.0
Gbe Version: Unknown
VendorID: 8086
PCH Version: 600005
FW Version: 7.1.52.1176
UNS Version: 8.1.10.1300
LMS Version: 8.1.10.1300
MEI Driver Version: 8.1.10.1275
Wireless Hardware Version: 2.5.68
Wireless Driver Version: 14.1.1.3

FW Capabilities: 17833024

Intel® Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel® ME Dynamic Application Loader - PRESENT/ENABLED

Level III Manageability Upgrade State: Not Upgradable
CPU Upgrade State: Upgrade Capable
Cryptography Support: Disabled
Last ME reset reason: Power up
Local FWUpdate: Enabled
BIOS and GbE Config Lock: Unknown
Host Read Access to ME: Disabled
Host Write Access to ME: Disabled
SPI Flash ID #1: EF4016
SPI Flash ID VSCC #1: 20052005
SPI Flash BIOS VSCC: 20052005
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000
OEM Tag: 0x00000000

it seems even having 8.1 drivers, the 7.x apps seems to work better.

and yes, I got same error while trying to flash a descriptor file, it doesnt matter if it isnt modded.

Error 25: The host CPU does not have write access to the target flash area. To enable write access for this operation you must modify the descriptor settings to give host access to this region.

[TimeWalker]

It's a dead end for us right now, Intel made sure to make it secure, and Phoenix has created even more obstacles along the way....

On a side note can you guys if running Windows 8 test something? I find it amusing personally. Dell has noted the following in their A13 bios release:

1. Fix issue when system resume from S4 automatically after upgrade to Windows 8
2. Fix the QuickSet compatibility problem on Windows 8

1. Hibernate is still broken, it resumes and all the apps I had open either quit or crash and stop responding. Everything is fine with A04 though...
2. With A13 I can't call the vid-mirror bar http://puu.sh/1lbmV the Fn+F1 combo does absolutely nothing .. however this works absolutely fine with A04.
Resume: what the point of going beyond A04 anyway ??

[kasar]

1) Dump your Desc table via fptw.exe -DESC -D DESC.BIN
2) Open FITC and load up DESC.BIN
3) Go to Master Access Section, and select Manageability Engine.
4) Change Read/Write Access...

interesting
however, even without modify anything and just creating the image with that tool, I noticed small hex differences from the original file with the one generated by the tool D:

[thorbsd]

On a side note can you guys if running Windows 8 test something? I find it amusing personally. Dell has noted the following in their A13 bios release:

1. Fix issue when system resume from S4 automatically after upgrade to Windows 8
2. Fix the QuickSet compatibility problem on Windows 8

1. Hibernate is still broken, it resumes and all the apps I had open either quit or crash and stop responding. Everything is fine with A04 though...
2. With A13 I can't call the vid-mirror bar http://puu.sh/1lbmV the Fn+F1 combo does absolutely nothing .. however this works absolutely fine with A04.
Resume: what the point of going beyond A04 anyway ??

I've got an XPS 15z with Windows 8 with A12. Hibernate is working fine and so does bringing up the second screen option (with Fn+F1 and Win+P).

Are you using a clean install of Windows 8? Just curious because even though I had an almost completely fresh install of Windows 7 and while the upgrade to 8 was totally smooth, I had programs crashing all the time, really poor performance, and just really strange behaviour all around. A clean install fixed everything.

[TimeWalker]

Thanks for your comment. It's not the system, it's definitely the BIOS' fault. As soon as I roll back the bios to A04 both of these problems are gone .. but then a new one arises, the laptop will just freeze randomly at early stage of loading up software after logging in.. it appears to be some IRQ 1/12 conflict because both keyboard and touchpad lock up, but USB mouse works ... seems to be due to an outdated bios. So I't something in-between A04 and A13 that would be an ideal bios version hehe .. but I guess I'm just dreaming to much :<

I was unaware about Win+P, thanks for the info about that.. actually are new hotkeys documented anywhere? I've found that Win+PrintScreen now captures an actual screenshot and saves it to Pictures library ..

[Paralel]

Nevermind, I'm a moron, ME 8 is necessary for Ivy Bridge Support:

[Paralel]

From what I'm reading, the Cougar Point Desktop boards that can be upgraded for Ivy Bridge run hybrid ME, latest version of 7 (7.1.56) AND a version of the ME 8 as well (8.0.13, if I remember correctly). If we are going to get ME 8 on these laptops, we will need to take the same approach, if possible, a hybrid ME 7/ME 8 setup.