If you provide a dump it should be possible, obviously with a programmer. Do you know what part of the SPI image got corrupted like BIOS, ME etc?
Did you mod the BIOS before flashing or anything like that? That’s a Skylake system so if the problem occurred after trying to flash the official Dell BIOS, it would be better if you contacted Dell first. That system is still covered by warranty based on it’s platform. Do you know what exactly got corrupted? For example, if it’s the BIOS region only we could replace it with the one from the .hdr but you will lose laptop-specific info such as DMI data, Serial Numbers etc which are found at the BIOS region. If it’s the ME, since Dell includes only “Stock” firmware at their HDR, we will need to transfer settings from the dump you provided and then re-integrate into a “fixed” dump. If you don’t know what region is the problem and are not interested for the warranty, we can start by replacing non-BIOS regions and see where that leads us. If nothing works, we will try the BIOS region as a last resort with the obvious result of losing some laptop-specific information.
donot worry about warrenty, dell rejected to pass beacuse i changed di mSata disk, i flashed normal bios not any moddded,.so you can start work, if you want serial number or other info i will send you in the email. bundle of thanks
Attached are two “fixed” files. First try “9350_dump_fix_me.bin” which only has a clean + configured ME Region changed. If that’s the problem then it should boot. Otherwise, try “9350_dump_fix_me_bios.bin” which apart from a clean+configured ME also has the BIOS replaced based on the one provided by Dell inside the HDR image. If the second image works (ME+BIOS) then the problem was in the BIOS. I don’t know how to get any laptop specific info out the dump in such case so you might have to live with it. But first let’s see where’s the problem and if these fixed SPI images can even solve it.
9350_dump_fix_me.rar (5.43 MB)
9350_dump_fix_me_bios.rar (5.5 MB)
i test but i will tell you tomorrow because writting is too slow on 16 mb chip, bundle of thanks
EDIT: hi, "9350_dump_fix_me" is not working, no fan spin, no front led blinking, only led on power button. i will try second and post the result.
i tested aslo "9350_dump_fix_me_bios" but same result as first.
Can you get the name of recovery file to recove from usb?
Thanks
@plutomaniac , can you tell me a tool to extract the bios region from Dell .hdr file?
edit: Managed to get the .rom file with the exe file and /writeromfile. But which software to take a look at the extracted .rom? For example to see the bios menu structure or to edit something.
edit2: With Andys Tools I got the ROMs extracted and with tool Xsearch I can search into them. Who can tell me how to find the rom with the bios menu inside to see if there are hidden menus. The goal is to change the cpu multiplier.
Thank you.
If you want to address a post to a certain Forum member, you should better write "@nickname". Otherwise the addressed person (here: plutomaniac) will not get an info via PM.
Thank you Dieter, didn´t know about it.
i used >AMI Aptio UEFI MMTool v4.50.0.23< with the SABERTOOTH X79 BIOS 4701
https://www.asus.com/Motherboards/SABERT…pDesk_Download/
but when i open the cpu patch tab then the tool crash…
so i used >Aptio UEFI MMTool v5.0.0.7< to check what is happening and there is no troubles …should i use it to update rom and add the asm1061 uefi ?
I am pretty sure, that you can use it for this purpose, but I do not recommend to use it generally, if you want to modify an AMI AptioIV BIOS manually.
Hello,
I am new to this fourm and had a question. I have a aurora R3 running bios A06 is it possible for me to modify my bios so i can install windows 10? Thank you for your time.
Exsus
@exsus :
Welcome at Win-RAID Forum!
A BIOS modification of your system is very difficult and probably not required.
You can find a guide about how to get Win10 installed onto your Alienware Aurora-R3 within >this< discussion. Search for the post written by the user dfernand.
Regards
Dieter (alias Fernando)
Hello to all the seemingly gentle people here, I would really like to ask for a little help.
This is one of the weirdest problems I or the techs that built my PC have ever come across, so please bare with me, while I try to explain.
The tower is this:
Aventum III PC
ASUS RAMPAGE V EXTREME 3.1
i7 5960x @ 4.62GHz
32GB Corsair Dominator Platinum DDR4 3000 @ 2,750 MHz
980Ti Asus Strix w/core @ 1,319 MHz and bus @ 2,002 MHz
OS Drive an Intel 400GB 750 PCI-E SSD w/NVMe
2x1TB Samsung 850 Pro SSD in Raid0
2x6TB Seagate SATA3 7200 RPM HDD in Raid0
2x4TB Western Digital SATA3 7200 RPM HDD in AHCI
2x2TB Seagate SATA3 7200 RPM HDD in AHCI
PSU 1200W Corsair AX1200i
OS Windows 7 Professional
Now here’s the problem. On boot, no matter what I do, I get 1-3 BSODs, right after the Windows Splash screen as it tries to go to desktop. It then goes to the black screen with start recovery or start normal. Click start normal and it either finally boots up or repeats the same process 1 or 2 more times. I’ve gone through Windows Startup repair, ran memtest, ran every diagnostic and test available, went through and reinstalled or updated ALL the hardware drivers, still the same thing. It’s not the Over Clock, because once it’s it’s started, it runs like a monster, I’ve even ran 4 stress tests simultaneously on it for more than 12 hours and it barely even kisses 80C for split seconds and I even tried it with default clock. What makes this BSOD even more troublesome is the fact that it leaves no event log, no memory dump, literally no sign that it even happens, so I’m assuming it’s still in the early part of boot, before Windows is actually fully booted.
That’s probably the weirdest thing, once I get passed the retarded BSODs on boot and it’s started up, I can beat on this thing with a stick, I’ve even tried to intentionally crash it by encoding heavy/agressive Bluray Disc Images, with this tower redlined, with EVERYTHING in use, including a CPU stress test running in the background, copies being written to ALL 9 drives from external, a 4K vid playing, multiple browsers open with tabs auto-refreshing and it doesn’t even blink. The only thing that I know crashes it, is if I’m encoding and doing a bunch of other stuff and I try rebuilding the index (on about 12 TB of data). Not that I care, since Windows indexing sux for databases that big so I use apps like Ultra Search and Everything.
What I discovered is that if one of the drive slots is pulled out it boots up perfectly fine. Now here’s the specifics on that. My tower has 8 slots. The top 4 has 2 pairs of drives in Raid 0 (2 Raids) while the bottom 4 slots are AHCI. It does not matter what kind of drives, what size of drives or which slot, but at least one of the AHCI drives must be pulled out for the BSODs on boot to permanently stop. It can’t be cables, because as I said, it doesn’t matter which slot and all the different drives I’ve used have been tested, both with software and on other towers, showing they’re perfectly healthy. Along with the fact that once actually booted, the drives work and test fine. The software on the PSU also says everything’s fine with the PSU and even the PSU was tested in a similar setup with no problems as well as tested professionally at a PC shop. I’m being told that I may have to RMA the board, but I would really like to avoid that if possible, because the cooling system on this thing is rather huge (3 hefty radiators, a sizable reservoir, a big pump), with a custom made EK Predator waterblock that literally covers half the mobo along with all chromed brass piping.
Someone in the ROG forum said maybe I should try a “modded BIOS” to fix my drive issue, but this is so far out of my league I don’t even know where to start. The most I’ve ever done with a BIOS, other than extensive overclocking is just install or update them. I do know that my BIOS (v. 1801) and Ctrl+I Raid configuration recognizes all the drives fine, but most of the RAID software and things like Crystal Disc sees the drives as either Intel, which they are not and/or completely different sizes than they actually are.
@plutomaniac
Hello,
may I ask how did you extract .rom and .hdr file from Dell’s .exe file?
thank you
edit:
ok I extracted .hdr from Dell’s exe.
There are 2 ways:
1. phoenixtool (let phoenixtool load exe, and then go to folder DUMP/BIOS and pick the largest file
2. install python 2.7 and use lordkag script from post #21
still I don’t know how to extract .rom file
@ greg.chalk:
You extract the HDR with the script you found or via PhoenixTool. The rom is inside the HDR. I use a different script to extract it’s contents but it’s neither my own nor public currently. I can extract the BIOS section if you like, what exact model are you talking about?
I have a Dell XPS 13 9350 laptop.
Is it possible to send me the script through pm?
Thank you very much.
@plutomaniac ,
I ended up setting my DVMT setting to 0x0 (0M) in my bios and now my screen doesn’t turn on at all. I was hoping to try and reflash my bios to fix this…but I cannot use the /writehdrfile with the current dell bios and I was wondering if you could help me with that?
I have attached the bios EXE to this post. If you can help with that or post any suggestion on what to try doing…or if its even fixable…let me know.
https://downloads.dell.com/FOLDER04143679M/1/XPS_9360_1.3.2.exe - that link should work to download the bios.
Thanks!
There are two steps for Dell BIOS executables with no icon.
First, you need to extract the HDR from the EXE using this Python 2.x script or alternatively PhoenixTool. Lately some newer EXE have appeared which require that move twice, meaning EXE to compressed HDR and then again from compressed HDR to uncompressed HDR. Then the output HDR needs to be extracted to its components. Use Lordkag’s Extractor which can be found here. It requires Python 3.x, module pypiwin32 installed (cmd > pip install pypiwin32) and the Python installation directory changed at the Z.version batch script first.
Make sure the HDR is at the same folder as Lordkag’s Extractor files, run Z.version batch script and type the HDR filename followed by “dellhdr” command.
Generally, ignore any rsa,hdr file extensions and the "main" binary file. Other than that, some user knowledge and understanding is a requirement here, pick the correct file for the correct need.