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

[thorbsd]

here is it (untested anyway):

I just remembered that you are working with the L502x. I confused you with jkbuha. I've got an L511z.

I should take some time over the next couple of weeks to make myself more familiar with some of these tools so I can make these modifications myself.

Is it as straight forward as unpacking the BIOS using the PhoenixTool, modifying the bytes of the appropriate files with a hex editor (and in this case also swapping the vbios ROM file), packing it up again with the PhoenixTool, flashing, then pray it boots?

---

Thank you for modding that file BTW.

[kasar]

hehe, yeah, I am not jkbuha nor have a L511z ^^

I am kasar, the guy of the L502x with some hardware and BIOS mods ^^

yeah, that is correct, phoenixtool and hex editor are the main tools

[Brabbelbla]

@thorbsd
PhoenixTool works pretty much the way you say. One has the .WPH file, unpack, unpack the actual BIOS capsule (F33...). Under advanced options, select 'No SLIC' and something like allow user modification of files, and wait until it prompts for you to do the changes. Modify, repack, flash. And yes, it supports 1920x1080 resolution, but don't expect fireworks. Splash, setup, boot manager, shell and stuffs still stubbornly use 640x480.

@kasar
I might be wrong, but shouldn't it be unnecessary to make those changes now? I will go and see what changed in BMP, but right now my sweet sister keeps my machine occupied

[kasar]

well, I am not fully sure what you changed with BMP wich I assume it is some intel software to make changes at the video bios, well , any extra information wold be apreciated, but I assume you added extra resolutions and other stuff.


the point of me patching the table it was I remember I had some issues by using newer intel bioses, like having issues with the internal screen baklit and mDP port.

I compared the device table stated by jkbuha, from my original vbios and your new l502x video bios and it had some differences.
thats why I patched it

[Brabbelbla]

BMP is, like you said, an Intel utility to change settings in their binary files (Binary Modification Program). To use it you need the binary (actual VBIOS) file to modify and a BMP script file. First are many ways to come by, second can be found for some VBIOS versions in the 64-bit Intel drivers. As an example of what settings one sees, I attached the exported settings file for the L702X v2158 VBIOS.

My actual work was rather minor. Loaded the stock v2104 VBIOS with the best fitting script file (v2089) in BMP, exported the settings, made four changes to make it compatible with the v2158 script and then applied the settings and saved. There was no need to 'add' higher resolutions, as they actually were already present in stock v2104, but somehow didn't work. Basically all OEM settings have been carried over, and over here brightness controls work just as they did. If you want to have a look yourself, PM me. Kudos for TimeWalker for providing me.

I compared the settings files of my and your patched version, and couldn't find any differences. Strange. Maybe you changed the actual VBIOS code instead of settings?

[kasar]

yeah, I didnt used BMP even a single time.

I just replaced the hex part jkbuha said with a hex editor.

probably it is VBIOS code itself instead settings.

if you hex compare the files, there are definitly some changes at the part jkbuha said.

[Brabbelbla]

@kasar
Yep, there are binary differences. But yeah, without your changes, my backlight and it's controls work just as they should. Unfortunately, I cannot test the mDP port, so I don't know about that. I think it should work left in the way I posted them, but I cannot say for sure. Do as you see fit; yet unlikely, I don't want to cause bricks by being stubborn

BTW, I presume you weren't lucky with flipping 01's and 00's in the setup module?

[jkbuha]

Hey guys - happy weekend!

I'd like to relate an interesting story that happened to me yesterday. Based on DoiX's Clover discussion on insanely's forum I was trying to reanimate my EFI boot via Clover, and for some reason I got a KP on OSX booting (for some reason the latest clover loaded the GeForce kext which then collided with my FakeSMC and DSDT, ie: Nvidia disabled). I mistakenly thought it was due to the ACPI DMI settings in the BIOS, so I tried to change all the DMI settings to disabled, saved and rebooted. Nothing - Black screen at first and laptop then powered off by itself. Hmmm. I unplugged power, replugged and tried again. Same thing. Not good.

This carried on without any joy, and there I was thinking I now had a proper excuse to get the new XPS. Thankfully I remembered the bios recovery cd me+kasar had done, whipped it into the drive, unplugged power, pressed End key and released it 0.5s after plugging the power cable back in. Voila - laptop boots into recovery mode, I nip into the BIOS setup, reset everything to default, save and restart normally. Worked a treat.

So... (i) has this ever happened to anyone here (ii) is this an incorrect BIOS setting, or corrupt nvram seeing as I was playing about with UEFI?

Guess the 15z will be hanging around for a bit longer

Cheers
jkbuha

[TimeWalker]

heh, I guess these machines are just begging to be bricked glad you had the crisis CD handy.

[kasar]

yeah, I cant belive my machine didnt got bricked after all the stuff, even soldering and desoldering chips and messing with the ME region part.

glad I had a whole chip backup and some extra bios chips and programer ^^