@pepebmx - reclip to be sure the clip is on there good, then also try dump with ASProgrammer 1.41.
Yes, all software look different, it's OK. Be sure you are doing read, then verify, then only if verify OK then you save file.
Try with power cable and main battery attached too, if you are not already, then test with both removed. Some systems need one way or the other.

Will try with battery atached and power cable, should i attach cmos battery? ASProgrammer read 000 too. Will try again now.
-----------

It did actually with battery and power cable! Im using colibri but cant find the verify button, is it the one that says compare?

CMOS Battery should always be there. If both read 0000 for the entire file, even if verify, then something wrong (not clipped perfect, or needs power stuff added or removed etc)
Yes, compare = verify

YES! Here it goes, hope you can find something! https://drive.google.com/file/d/1-H4VYlg...iew?usp=sharing
THANKS A LOT!

@pepebmx - So, what was the initial 0000 issue, bad clip connection, or you needed to add/remove power/battery (if so, which)
Also, what software did you end up dumping with for future reference. Dump looks OK, and BIOS "at a glance" does not look corrupted or messed up, but that does not necessarily mean it's not. Did you take apart/put back together and see if it was just something loose yet?
I will try to get this sorted for you tonight, if I can find any issue If not, I will just rebuild you a BIOS with stock NVRAM and all stock BIOS, with clean ME FW etc, and see if that works for you, if that does not then something else is wrong.

Initial 000 issue was because not even cmos was there, pluged in everything and went all fine!. Dump it with colibri! Already put together and still the same problem, nothing loose. Thank you a lot, waiting for your magic.

OK, thanks for the info. Hopefully BIOS can fix this, and it's not dead SB or something like that

* Edit - @pepebmx - Here, this is strictly a test, so stock BIOS mainly but unlocked FD and clean updated ME FW, missing all your info, just so we can see if BIOS is issue directly or not.
http://s000.tinyupload.com/index.php?fil...295753215416015

I see signs of incorrect/bad flash (not following directions on what to disable before update, or trying to backflash), someone recently had a thread about this, and how it was a common Alienware BIOS issue.
Anyway, I see same thing in a certain area of your BIOS, that causes black screen, loss of display due to incorrect update attempted - Sorry, I can't find the thread now though
Message I see, repeating is this MANY times in certain area, google it and you will see it's very common issue >> alienware unable to access EDID EEPROM (Many see this on screen, but not the guy I helped, we only found by looking in BIOS)

Also, I did not notice before when I had a quick look, but your ME FW is trashed also, this could be cause of above as well possibly.

If this BIOS boots, leave system open and I will make follow up BIOS putting your system details back in + one with your system details and original NVRAM too (Latter mentioned one here should be tested first, this would be ideal goal BIOS)

Lost n bios thank you a lot. I will begin the process of reflashing right now. But i have some doubts. In guide says i need to erase bios, is that correct to do in this case too? After that says to blank bios but i cant find this option in colibri. Only found under operation , spi, blank check. Should i do that instead?

@pepebmx - You're welcome! Yes, erase, then blank check, then open BIOS file and write then verify (compare)

Sad to say, same lights error. Had no problem during writing the chip. Thank you a lot lost n bios, dont know what to do now.

@pepebmx - Sorry to hear! Lets confirm the write went it OK. Please redo the erase, blank check, open file, write, verify. Then, do not start system! Close program, open again and read, verify, then save.
Then compare that file with the one you wrote (I sent you) in hex editor, or send to me if you don't know how to compare like this, and I will check, if not 100% match then write failed.
The re-write must be done because as soon as you tested the start of system the BIOS contents would be changed, so dump as-is now would not be valid compare for this manual write check confirmation.

It may be EC FW chip contents. Find that chip and give me the chip ID, and go ahead and dump it with 1.18 and BV ID for now and send me copy.
It's W25Q80DV, if I am looking at board images you sent me, if not it may be other ID << For that, I am not 100% sure, so dump with 1.31Free (Pick correct type 25, and size 1MB), and then also dump with ASProgrammer 1.41 using exact ID too.
Looks like flashrom also works for this chip, so you can try this Windows GUI'd version too (post #510) - [Guide] Using CH341A-based programmer to flash SPI EEPROM (34)

I like that u still have hope! Sending you to compare! Dont know how to do that with the hex editor. I already send you pics from the mother, could u help me identify that EC FW chip? I googled what is an EC FW chip, but cant understand what they manage exactly.
https://drive.google.com/file/d/1NluFOMj...iew?usp=sharing ----here are the pics from mobo

https://drive.google.com/file/d/1rRt_Pq1...iew?usp=sharing --- here dumped file following your orders

@pepebmx - Yes, still hopeful for now Please see my edits above in case you missed anything, I edited several times.
So yes, if the images I have are yours then that chip ID I mentioned above is correct one for you You sent them to me earlier, correct?
Please, anything you send me in future, always put in max compressed zip or rar, thanks

Write is OK, 100% hex match! Please also now test this one - http://s000.tinyupload.com/index.php?fil...331182709675104
The first one I sent should work, if nothing else wrong and BIOS was only issue, I just want to test this to be sure of something.

Found w25q80dvsig 1646
Read them with 1.31 and asp
Will reflash the second bios you send to me, and try to turn on.

Those match, and look OK Sorry, sounds like this might be some other failure, CPU, NB, GFX Card, or something else on the board
Can you see anything on screen if you program in BIOS from 182 and then connect external monitor?
Check all external possible connection methods, connect cable before boot attempt, then wait at least a minute or two, then shut down, connect to next method, then boot and check again