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

[marstone]

Hello everyone I made test with bios for Dell XPS l702x and also working

@all, i just seen the unlock, that's great!!! congratulations and thanks to all.

can you attach a modded-l702x version?

[TimeWalker]

jkbuha,
I've seen his posts regarding this matter. No, unfortunately I haven't since I got Vostro 3450 and mine came with just the recovery partition to restore OEM Windows installation. No physical disk .. nor can I request them since they only ship to US.

[marstone]

Hello everyone I made test with bios for Dell XPS l702x and also working

@all i just heard the unlock, that's great! thanks all & congrats!

@krzysio30, could you plz post your modded-l702x bios here? thanks!

[TimeWalker]

man ... someone's impatient lol
https://dl.dropbox.com/u/2573233/L702X_A18_UNLCK.zip

[Fawar]

Yes Fawar, but seriously - DON'T flash this bios. I'm really worried you're going to brick your laptop because from the questions you're asking you're not completely familiar with what you're doing.

If you really want to proceed, run winflash.exe /BIOS /EC /SA /SV /BBL "BIOS1_A11.WPH"

TimeWalker - I was chatting to DoiX on the mac forums and something just crossed my mind.
Do you have the original XPS 15z recovery DVD? We could try to initiate recovery using the usb drive, which may trigger reading the files from the dvd?

---

Well, from the point i got the right folder, with the right items and the right command in the right directory.

Is thre something that could go wrong, is there something that i will need to choose once i call the command to flash my Bioses?

No - just sit back, cross your fingers, and pray

Seriously though - an error may occur when flashing the bios that we haven't seen yet on your machine, which may put your laptop into a non recoverable state, and since we don't yet have a recovery method which works you will not be able to recover your laptop. That's why TimeWalker and I are very concerned that you may not have enough experience to recover your machine should something go wrong. It's important to remember that we're playing with $1000-$2000 worth of equipment here, so it wouldn't be a cheap mistake

Hope that makes sense.

Those recovery methods won't be given by dell is that it? you need to create your custom one?

Are you working on it actually ?

[TimeWalker]

Have you been following the topic recently ?

Dell would rather get cash from you for replacing your motherboard after voiding your warranty for no apparent reason then give you a recovery method. Not to mention they sell you extended warranty for ridiculous amounts of money.

I have been talking to their suppor for like a week to determine what was causing my DW1702 bluetooth to fail at pairing with anything .. when this was finally sorted out ir turned out that a Dell mouse that has cost me 30$ was dropping connection after every login, also it was required to re-pair after every reboot. We spent another good 3 days going with debates about me needing to reinstall my OS and blindly ignoring the links to the dell community forum posts that I have provided when lots of people reported the same behaviour. After all that it turned out that Dell service provider failed to uninstall Intel's wi-fi driver after swapping out the card for an Atheros one ...and now I'm unable to do this since tells you to make sure the intel card is installed properly (why on earth would I need the card in place to do this???) which in hand created this series of frustration. This is your 'next day on site' warranty for you ...

---

With a probability of 90% I can say that the recovery file should be named BIOS.cap and probably should be the entire capsule.
Both SystemCdExpressPei.efi (31E147A6-D39A-4147-9DA3-BEFD4D523243_x_xxxx) and SystemFatLitePei.efi (5B60CCFD-1011-4BCF-B7D1-BB99CA96A603_x_xxxx.ROM) use this name ..

and

I just learned that Phoenix Tool determines the name for Insyde by looking at this string in PeiFat module .. but since our module is called differently it's unable to tell what is the proper name for the recovery image.

Here is an example for an Acer laptop ..




So basically pre EFI initialization will seek for this name and so will CdExpress then the drivers will kick in.

The actual bios flashed on the chip appears to be only 2.5 Mb in size. I just dumped it using Universal BIOS Backup Toolkit 2.0.

[krzysio30]

Hello everyone I made test with bios for Dell XPS l702x and also working

@all, i just seen the unlock, that's great!!! congratulations and thanks to all.

can you attach a modded-l702x version?

Bios A16 and A18

https://dl.dropbox.com/s/7gqg6vk4xbtlxyv..._unlck.zip
https://dl.dropbox.com/u/2573233/L702X_A18_UNLCK.zip

[marstone]

Hello everyone I made test with bios for Dell XPS l702x and also working

@all, i just seen the unlock, that's great!!! congratulations and thanks to all.

can you attach a modded-l702x version?

Bios A16 and A18

https://dl.dropbox.com/s/7gqg6vk4xbtlxyv..._unlck.zip
https://dl.dropbox.com/u/2573233/L702X_A18_UNLCK.zip

@krzysio30, thank you very much! have you changed your SLIC? Winphlash16 said "platform signature not found in interface" to me.. or anybody who knows how to solve this problem?

[TimeWalker]

Use the tools you are supposed to use with UEFI bios.. Phoenix Tool is one of them .. check for SLIC using it.
Also use proper tools provided by OEM to flash the bios unless you desire to brick your 2k$ machine.

[marstone]

I patched the L702X_A18_UNLCK.WPH with DELL SLIC 2.1 but it still don't work.

my original BIOS is L702x A17, then I updated my BIOS to stock A18, still no luck.

I flash the WPH file in DOS with the command: phlash16 /S /X /FORCE, which following this thread: http://www.bios-mods.com/forum/Thread-HO...GINAL-BIOS

then I decompressed the stock BIOS.WPH, which I just flashed using official program.
and copy it to my USB disk, the error still the same.
so, i think this error should be nothing to do with the SLIC.