well, each ME firmware have its own information and adjustments over each chipset I think, so it would be need to be a laptop with the same chipset and hardware.
however, those laptop firmwares can be used to analize it and take them as examples to mod the firmware from the laptop to be modded.
this is what is basically explained at this topic:
Hey, guys. Sorry for my lack of inactivity :| Have been polishing my OSX experience regarding touchpad and battery, thanks to @Rehamman over at tonymac.
@kasar regarding your dump .. I have attempted to mod some values but it doesn't save for me either, I have no idea how I managed to export it back then, when we first tried the cross-flashing or ME v8. To be absolutely hoest with you I didn't do anything special back then but just followed how ME was configured for that Alienware x-something machine, or was it Dell anyway ..? You know what I'm referring to, the thread called "Let's unlock bladi-bla". I will try to reiterate the steps I did then to see if it will end up exporting properly and not moaning on some errors.
@jkbuha I have finally tried your VBIOS 2158 that you had posted a while ago, needless to say it didn't work very well for my machine. I lost brightness control and like @ashp (in Acer thread) mentioned the display seemed noticeably dimmer than usual. Man, I just absolutely hate Dell for doing this to their customers..
You can read more about how crappy Dell's SCT is by reading from here and on the following page.
Posts: 523
Threads: 0
Joined: Aug 2011
Reputation:
23
01-21-2013, 09:42 AM (This post was last modified: 01-21-2013, 10:25 AM by kasar.)
(01-21-2013, 06:43 AM)TimeWalker Wrote: Hey, guys. Sorry for my lack of inactivity :| Have been polishing my OSX experience regarding touchpad and battery, thanks to @Rehamman over at tonymac.
@kasar regarding your dump .. I have attempted to mod some values but it doesn't save for me either, I have no idea how I managed to export it back then, when we first tried the cross-flashing or ME v8. To be absolutely hoest with you I didn't do anything special back then but just followed how ME was configured for that Alienware x-something machine, or was it Dell anyway ..? You know what I'm referring to, the thread called "Let's unlock bladi-bla". I will try to reiterate the steps I did then to see if it will end up exporting properly and not moaning on some errors.
np mate
mmm, do you remember what firmware you modded? the one you extracted from my whole chip image? or the one I got via fptw64 ?
curius notes:
fptw64 version 7.1 does not detect my chip and cant dumpt it, but the 8.1 version does!
FITC 8.1 cant open my ME image, give error, but the version 7.1 can open and read all the parameters perfectly ^^ (however it fail while saving it)
another posibility would be to create a completly new ME image from 0, but checking exactly all the parameters from mine, by reading it, do you think that will work?
edit, I attached the ME image extracted by FPTW64, I think that was the one you sucesfully modded.
I found another tool with the intel tools package, but not sure what it does
Available options:
/v0 - Verbose level 0 (default mode, smallest amount of information).
/v1 - Verbose level 1 (debug). Includes raw HECI messaging.
Available commands:
gl - Get Lock
rr - Read ICC Register
wr - Write ICC Register
gr - Get ICC Record
gcc - Get ICC Clocks Capabilities
gcdr - Get Clock Range Definition Record
sl - Set Lock
sce - Set Clock Enables
gp - Get ICC Profile
sp - Set ICC Profile
rrd - Read all dynamic ICC Registers
wuob - Write UOB Record
smr - Read Single ICC Register via SMBUS
smw - Write Single ICC Register via SMBUS
To get help on specific command, use "cctWin.exe command ?"
mmm, this seems also to have the ability to write registers, but I dont know what to change exactly, what do you think guys?
some more parameters I got
Available selectors:
intel - Intel Record
oem - OEM Record
perm - Permanent UOB Record
temp - Temporary UOB Record
preuob - Platform Boot Time Record Pre UOB
postuob - Platform Boot Time Record Post UOB
current - Current Record
01-21-2013, 10:56 AM (This post was last modified: 01-21-2013, 06:06 PM by kasar.)
oh, I forgot to attach the tool ^^
here is it, it also have a PDF file with some ussage help and stuff, it also talk about more hardware required and a required DLL to take be able to use the SMbus feature (however the app worked fine to output those results without aditional HW or DLL in my case, however it obiusly ask for the dll file and extra hardware & test machine while trying the smbus commands)
Posts: 523
Threads: 0
Joined: Aug 2011
Reputation:
23
01-22-2013, 04:28 AM (This post was last modified: 01-22-2013, 04:31 AM by TimeWalker.)
Ash, or @ashp as he's known here, has shared some knowledge with me in terms of Intel VBIOS modding, turns out *there's an app for that*. The tool is called Intel Bios Modification Program (or BMP for short). There's some documentation to accompany it, which fortunately is more easily obtainable then the actual software. As it doesn't seem like the app is really out there in the wild, I won't be uploading it for security reasons, 'cause it's Intel's inside stuff you know, and by the looks of it even Dell don't seem to have it, otherwise they wouldn't have rolled back VBIOSes due to screen test issues and ePSA failing for range of other reasons.
The script files (bsf) used by BMP and actual blank stock Intel VBIOSes come bundled with Intel's Windows XP 64-bit VGA drivers, here's an archive full of them.
This one for example comes bundled with script for VBE 2089: http://wikidrivers.com/wiki/Intel_GMA_14.46.0.5313
Unpack vbios_pgm.zip, the *.bsf file is a script to preserve configuration of the current VBIOS (which has to be of same or similar version), the *.dat file is a blank stock Intel VBIOS binary, which can be used to apply the OEM settings to and pack it into the firmware.
Ash went down the following route IRRC:
- Using 2089 script he has pulled config from my OEM 2098 (notice the versioning is not the same), configuration is stored in an *.ssf file
- Using 2108 script (this is still SNB-only VBE) he has patched my settings from 2098 OEM to a blank 2108 from Intel
- Pulled settings again from just patched 2108 using the 2108 script
- Applied 2108 SNB-only settings onto a blank 2119 SNB/IVB
- Pulled settings from 2119 he just had patched using the 2119 script
- Applied settings to from 2119 to a blank 2158
There're some minor hiccups along the way, because some settings are absent from newer VBIOSes, hence you have to alter the resulting *.ssf config files when going from some lower version to a higher, especially if it's a transition from SNB-only to an SNB/IVB combo VBIOS.
After carrying over all of the settings from my OEM 2098 SNB-only VBIOS, Ash was able to patch Intel's stock 2158 SNB/IVB combo VBIOS and now I get high resolutions as well as proper brightness controls, backlight level and port setup. Which I give him huge props for this!
This is not a guide by any means, but hopefully I'm leaning in a right direction, some things can be a little misleading or off as I wasn't doing this myself.
Posts: 178
Threads: 4
Joined: Jan 2011
Reputation:
31
![[-]](https://www.bios-mods.com/forum/images/black/collapse.png "[-]")
(UEFI) Dell XPS 15z L511z modded BIOS - and HOWTO
![[Image: 2c70a200_fuuuu_by_ku127-png.jpg]](http://cdn.head-fi.org/2/2c/2c70a200_fuuuu_by_ku127-png.jpg)
![[Valid RSS]](valid-rss.png "Validate my RSS feed")
