@code9523 - you are too funny! >> "I know this partial BIOS wont work, I know it's wrong size..... But I flash it anyway" ??? Since you knew it was wrong size, and wouldn't work, what did you think the outcome would be when flashing? Magic?
Yes, I would not use AFU on this system anyway, it's Intel based so use Intel FPT. Don't use blindly, ie without help, instructions, us telling you to do this or that, I'm only speaking in general here in regards to AFU or FPT and my preference.
You have a hardware flash programmer, so you really never need to use either of these, except maybe later once you get it all sorted and put back together, then I would use FPT for any flashing I needed to do.

About 16MB file? It could be broken, did they say it was working dump wherever you grabbed it from? I've not looked at or used any 16MB file for anything, and didn't plan to either, so it doesn't matter to me if it works or not.
But yes, if that is a working file, it would need BG disabled and ACM/BG entries removed from FIT before it could ever have a chance to work. And another but, it can't work anyway due to production ME FW is there, so you can basically toss that out.
I may use it for what I mentioned above though, so please attach by themselves into a single zip/rar so I only have to download those if I need them later.

Now, I have tool to work with this BIOS properly, please wait, test BIOS coming soon

plutomaniac - Thanks for the FIT info, I tried old and new, but didn't have one old enough I guess Thanks, that was all I really wanted to check in FIT, about the BG, I assumed you did but wasn't sure and since he mentioned it at first post I wanted to check to be sure.
On the stock dumped region thoughts I mentioned, I only thought maybe an actual stock dumped region would = 8MB vs that HDR region, but yes if it's same then same issue would be presented anyway.

Yes, I wanted to increase it due to UEFITool would not rebuild at a BIOS region swap only, and I'm not great at FD editing to resize region, so wasn't sure if I could build it manually in hex and then correct the FD BIOS region size etc.
And now mentioning that, this would leave final file 31MB, so still 1MB too small, so something's got to be corrected in my mind (as you mentioned, by build with FIT instead)I did consider FIT building too, but it wasn't working for me yesterday so never made it that far.
I've never built a BIOS like that with FIT, changing region sizes etc, so this may be best done by you at first, unless you don't want to do it? I will try now since you sent me that FIT
* Edit - I looked, and don't see what I expected at Flash Layout, all sizes are zero, so lost on doing that with FIT - *Edit 2, never mind, that ways easy, and not unexpected

*** Edit - @code9523 - Here is BIOS to test, put on with programmer only

First test these two BIOS trying the 2017 one first - Straight stock region swap in - one with latest original included microcode for your CPU, other with 2017 microcode from BIOS at post #4 ACM/BG removed from FIT on ALL
Stock2017
Stock2019

Then if both fail to boot, test these BIOS again trying 2017 first. These are same as above but with your original NVRAM in place and old original Setup, AMISTE, AMITSE/SetupData, 2 x StdDefaults outside NVRAM swapped in
This much easier than NVRAM swap of setup entries in NVRAM - other way nearly impossible for me, takes hours to redo all NVRAM especially when there is 100's of entries.
These may fail no matter what, for many various reasons related to the new/old swapping of the modules mentioned above, but also due to AMI Hash mismatch (Sometimes that cause any BIOS edit to fail, other times nothing)
Stock2017NV
Stock2019NV

http://s000.tinyupload.com/index.php?fil...731289720798234

No boot. Only fans spin and cpu error.

Please give me full exact report for each BIOS, or did you mean that is same for all 4 BIOS? If yes, same for all 4, then you may not be able to use retail stock region with old PRE ME FW.
You are erasing chip, then blank check, before write/verify each time correct? If not, please always do this, otherwise you can have issues, failure etc.

Maybe only thing we can do is mod the original BIOS and see if we can correct the problems you are having.

Zitat von Lost_N_BIOS im Beitrag #18

---

Please give me full exact report for each BIOS, or did you mean that is same for all 4 BIOS? If yes, same for all 4, then you may not be able to use retail stock region with old PRE ME FW.
You are erasing chip, then blank check, before write/verify each time correct? If not, please always do this, otherwise you can have issues, failure etc.

Maybe only thing we can do is mod the original BIOS and see if we can correct the problems you are having.

---

Thanks for detailed info!

My four BIOS I sent you are 32MB and have the old ME region, they were built from BIOS in post #4 that Plutomaniac did clean ME in (552read_clean.rar)
Seals the deal for me, on stock BIOS region not being compatible, especially since first set acts no different than second set. I expected different results from first to second set, at least something different between the two sets.

Back to 552read_clean, flash that. Then explain to me the issues you have, we'll go from there. Also, once you do that, please zip or rar for me one image of each main BIOS page (ex. main, adv, chipset, security, boot, save and exit etc)
Unless it's not standard AMI type looking BIOS (Gray/blue), and looks like Dells crap BIOS instead. If you are unsure which type I mean, show me a single image of the BIOS, then I'll tell you if I want the rest of the images or not.
Please resize images, I don't need 3-5MB images just to look at the BIOS, thanks [wnk]

I figured out what stalled me at first about the BIOS region size and swap with FIT, then few minutes later I realized duh same as swapping out ME . That's what I did, opened file, saved XML, replaced that region, opened FIT, loaded XML and built.
Yes, all looked correct in UEFITool after that too, I just never did region swap that way so it confused me at first. I was expecting to see and change the BIOS region size at flash layout

I'm used to doing the ME process a little bit now, and so that seemed easiest to me, since I don't play with that tool often enough.
It's too bad CPU is soldered to PCB in this case, otherwise I'd probably suggest retail CPU at least to try, in case that silicon is part of what's causing him the issues with the temps/fan speeds, and since it is soldered this is something we can never test to confirm/deny too

Guys! How about thundertbolt? Can it cause an issue? In the production bios there are thunderbolt settings in es there is no thunderbolt settings. also when i try to update TB firmware using dell/intel TBFW tools they both said that there is no TB devices found in the system! Also i have USB C controller error code 43 in device menager and laptop does not recognise USB hub with devices connected to it.There is I think a TB firmware chip near TB controller. May be i should flash there firmware?

Also there is a chip with a (I suggest) with a Alien FX firmware should be or a separate EC firmware like it is on AW 17 r4 and all old AW's. May be we need to extract it from the factory dell's bios. Because as far as i know when i was working with dell systems you always had to flash both chips with 16mb and 4mb may be this is an issue?

I mean mean if we swap bios body to dell's offical bios update may be then EC controller needs a separate firmware on separate chip?

Board chips https://drive.google.com/file/d/1NwLoW6i...iew?usp=sharing

By the way I done clean windows install. And I installed aw command center and it recognized laptop as aw17 using Fn + F12 key I turned off alienfx for good. Now its compleatly dark even when i start laptop. But now alien cc says no alienfx devices detected!

It doesn't matter if that can or cannot cause issues, it's not easily removable from the stock BIOS, so not something we can address.
As for TB and USB, don't try to flash them, until you first dump them with some programmer or software, they may be fine and have working FW in them now (I suspect they do), you just have to find proper software that will work with them.
Yes, it's very likely there is a EC chip, this is common with Dell. This would control, or at least help control the lights and fans sometimes too. EC FW is not something I can edit, well I can edit anything, but I mean I have nothing that will break this down into readable settings to change etc (usually)
Dump the EC chip and send me a copy to look at.

EC chip is empty. I checked there is no firmware there.

How do you know? That can't be right, or it wouldn't boot. Probably you need to use other software version to dump that chip, or you tried to dump something that is not a flash rom. What is the chip ID?
Is BIOS images what you linked me to in PM? If yes, I'll go check, if not, please put that link here with explanation of what it is, I can't keep track of anything in a PM