Not entirely sure if I should start a whole new thread as I saw someone else had a similar issue, please correct me if i did this wrong.

I have a M15R3 that died during a bios update. I get the 7 beeps of death - and a black screen, on a computer that has had around 200 hours max usage that has been sitting as a python coding machine in the corner of my room. unfortunately i thought i could do an update without issue... girl was I wrong. T_T

The difference between myself and the other thread on the M15R3 is that I have an i5 other than that - the one thing i didn't do was turn of [cpu performance option] in bios before update which dell recommends per support article: (https://www.dell.com/support/article/en-...-update?lang=en)

Dell support is saying get a new mobo we don't help remote bios issues, but I see that @brickedalien had some success here.I ordered the CH341A + SOIC8 items to dump the bios, hoping someone can help me as I really would prefer to fix this - rather than get a whole new computer. seems like a good skill to learn rather than wasting time with dell support for the next two months convincing them to swap my mobo. Thanks for all the help in advance! I just don't know where to go from here... especially while locked up in apt in nyc during the pandemic.

Again,

Sorry if this is the wrong place to ask - happy to join the old thread, but didn't want to confuse the two issues. Sorry if that is incorrect.

Abita

@St00 - do you still need help on this?

@abitadrift - I replied to you with reply on most of this in PM, but I will repeat here, please DO NOT erase or write anything to BIOS chips until you've dumped BIOS and I've checked your files and said OK we can move forward

We'll get this fixed once your programmer stuff arrives. What is your BIOS chip/chips ID? Read off the chip, you may need magnifying glass and or flashlight.

Merging with other thread now since both are BIOS brick/recovery for the same system

Hey @Lost_N_BIOS

Got everything and dumped the file -
https://easyupload.io/asxdty
password alienware

Same bios chip ID as far as I can tell. 25q128fvsq - can't quite read whats under but i believe that to be the correct id.

My bios is much smaller in size though compared to BrickedAlien - even though i verified 1mb seems small..

@abitadrift - Not sure what you used to dump that, but no need for me to look at that file since it's not correct size from a dump from the chip you mentioned. Please see below

For W25Q128FV you need to use 1.18 version CH341A software, or use ASProgrammer 1.41
Here is CH341A software package that has 1.18 (W26Q128BV ID will be used with 1.18) - http://s000.tinyupload.com/index.php?fil...695330485827902
And here is ASProgrammer 1.41 - https://github.com/nofeletru/UsbAsp-flash/releases/ << I suggest using this, since I have not personally tested with 1.18, but few others were OK using 1.18 (all other version fail, that I have personally tested)

Be careful using new software, do not erase or use auto etc!!

Please also link me to your stock BIOS download page at dell, thanks! I'm not sure if 15 R3 = same as M15 R3, so wanted to be 100% sure what BIOS/system you have

Ohh! Also, I checked the file you uploaded, and from what I can see this is split BIOS (you should see two chips).
Or, it's possible that I may see this due to it's not full dump, but check to be sure you do not have 8MB chip and 16MB chip on there, or two 16MB chips etc

Woops Sorry mate! @Lost_N_BIOS

https://easyupload.io/u02mx1 : password alienware


16mb - verified

@abitadrift - So, only one chip then, correct? If yes, great! Also, please tell me what software/version you used for the above dump, in case we need to know later.
Also, please see my edits above, in case you missed them. I need you to confirm system model and link me to stock BIOS (in case it's not same as Brickedalien BIOS I already downloaded stock stuff for) - In case BIOS is too corrupted for me to be able to tell.

* edit - @abitadrift - Also, what is your CPU, now staring down same question as started at post #14 on page one here. Your BIOS IS the BAP11022, and brickedaliens dump wasn't, so when we guessed and went ahead with 11033 it was OK due to that was original
But, the main reason for this being of concern is that the bricking may happen due to stock BIOS package contains two BIOS images 11022 and 11033, both for this system and brick may be due to wrong one flashed in thus your dump may be 11022 incorrectly.

i used 1.18 for the above dump.

I have the same 3 chips that brickedalien had - my system is slightly lower specced.

Processor is an I5 : i57300hq


I have 3 chips that I think are bios chips on the motherboard- the one as mentiioned above same as BrickedAlien and two others i can't quite make out. I believe the one in back is


The chip I dumped (same info on it as brickedalien): winbond 25q128fvsq

The second chip in back of the machine winbond 25q80dvsig

Third chip i really just cant seem to read it doesn't say winbond though, has a weird G symbol on it.




P.S. If i remember right the bios was before: 1.0.5 American Megatrends(?) but i could be wrong. Definately a i5-7300HQ @ 2.5GHZ + GTX1060


Let me know if you want me to take close photos, or you need more info. Thanks @Lost_N_BIOS

@abitadrift - Please redo dump with ASProgrammer 1.41, this way we can confirm dumped contents are valid as they are, and then we know write should also work with 1.18
The file is corrupted at 2-3 areas, but this may also be some to do with what you dumped BIOS with, so we need to do with ASProgrammer now to be sure, that way we know the write will go in properly (it may be fine with either, but best we check)

Thanks for chip info, I think just one BIOS then (other is EC FW sized) I can't read any on the image you attached, it's way too small

So, due to your CPU, then BAP11022 is correct, so I will use that (1.7) BIOS to fix your BIOS.

I was having an issue with ASP Programmer where it locks out whenever it tries to save :( any suggestions? I'll try again with compatibility mode, but that was why I used 1.18 instead of ASP XD

On the image- there is two winbond chips, one i dumped one i didn't and a third i can't read. :(




I will try again with ASP now!


Update I see this when trying to write:

What do you mean "Locks out"? Try running as Admin.

Yes, I knew what you meant about the chips, but I thought maybe I could see/tell what the other chip was by looking at your image, but when clicking it I found it's WAY too small, so I couldn't help to tell you what chip it was

Maybe if @BrickedAlien is around right now, he could confirm is 1.18 did the write OK or not, or if he used ASProgrammer instead. I looked back, he didn't confirm which software he used

* Edit - @abitadrift - Not sure what you mean "When trying to write" you shouldn't be writing anything at this point!?
Close program, open again by right click the EXE, run as Admin. Then hit the little lock icon to unprotect in case protected (not the drop out next to it), then do read, verify and then save.

Ahh thanks,

Lock out - says "access violation" in ASP Edited - i uploaded the image of the issue to previous post :) alwaays running as an admin thanks!!! sorry i mean "save a file" as in write a save - not write to chip sorry my english :(

See edit above What version is that? if it's 1.41, try 1.40 and see if you have same issue
If issue persists, we'll just have to try write with 1.18 and see if it runs or not

* Edit - @abitadrift - Also, try NOT running it as Admin, just regular, and NO compatibility mode changes, that is how I use it in Win10

1.40 worked https://easyupload.io/7fcms3 password alienware :))))) thanks @Lost_N_BIOS .

"Saved" not wrote file lol - did what you said, unprotect, read verify save

Confirmed dump is match, thanks! This means 1.18 "May" be OK to write, but we still can't be 100% sure, so if you use it and it fails to start, then try the same write again but with ASP instead (For writes, do erase first, then blank check, then write/verify)
OK, please wait, I am in middle of rebuilding you a BIOS now

@abitadrift - Here, should be fixed now!
http://s000.tinyupload.com/index.php?fil...413964112411941

Due to ME FW Update, after programming, unplug PSU from system if you have it connected, press and hold case power on button for 1+ minute to drain all power from board.
Let sit for 1+ Minute like that with no power, this resets the ME FW state

*Edit - If it fails, then I will have to remove your original NVRAM and replace with stock, then you will run and get system going, then dump again and send to me so I can put back in your system details.

Dear Lost_N_Bios and Abitadrift,
perhaps I have same sort of issue. But i got locked out by a bluescreen while installing FW! I was updating an Alienware M15 R3.

Whilst downloading all drivers from Dell site where I also wanted to make ISO for later use. I noticed that all files where to be installed after downloading too late. Then whilst flashing a blue screen appeared which forced me to reboot..
that did not ever work, screen turns on for 10 seconds with bootlogo and press F2 or F12. No response and turns off whatever .

Hope you can help us both out Lost! Or if this thread needs another location, feel free to move.

Greeting Allan