[Request] Dell G5 15 5590 - orig .bin file to flash on SPI

Could someone please check why my notebook doesnt start up anymore after flashing the orig bios files back to spi ?

Files

I had flashed a modified bios (inserted DXE module) with flash programmer tool from CSME and then the machine had no display.
Tried to reflash orig bios with CH341a but after flashing it, the machine not even starts up anymore.

GD25Q128 was detected.

Link not valid. REBAR on laptop… cant remember seeing a success report …
What did you flashed with fpt, a bios region or full image spi? Same for the programming, a full dump or Dell files?

Files this one should work.

with fpt i flashed the biosreg.bin(backed up with fpt) where i have inserted the DXE module.

after reboot the machine tried to boot, but i got the 6x white 3x amber error code, corrupted bios.

i then flashed the 1 – 1 System BIOS with BIOS Guard v1.27.0.bin extracted from G5_5590_G7_7590_7790_1.27.0.exe.

notebook doesnt power up at all.

i only have 2 chips on the mainboard, the 16MB and a 4MB one.

do i have to flash the about 12MB bin file ?
i have another backup made with the windows backup prog its a 16MB file

This is usually not a complete fw image with all regions expanded, they must be composed/edited with old dump, did you check this integrity before programming?

This is an example of a full fw expanded regions image from a G5 5590…

Multiple ICs motherboards may have different contents, one could be main bios the other ME FW, EC etc…
This was an operation to be done before any attempts of flashing mods, the rule is identifying all IC’s, their content and save them as a backup…then we know each one content and what data is to program into each one…

If you flashed this…(1 – 1 System BIOS with BIOS Guard v1.27.0.bin) then it will never boot, thats why you got the result…

So where is the correct backups you made, in your shared files…???

the biosreg.bin i have added to the link, was the file i modified and flashed on the spi.

biosreg.bin

the FW, etc backups i have on the hard disk unaccessable, as i was really sure getting the write protection solved was the only thing needed and flashing the modified bin file with the DXE module will work 100%. Do i need to find some files from other G5 15 5590 to get what is needed ?

The “mother” of all mistakes…

Not valid…your STAG is not present

No full backup… no original Dell system data possible to recover.

And yes you need a full image to recover the machine… as you may now know…

i have a full spi backup, but not sure how to get the file as i am now on a live usb linux version on a notebook i borrowed..

yeah pretty dumb mistake to flash in such a situation :frowning:

Well…that’s not the notebook with the original files and the respective hard disk, right?
These files were to be stored outside…not with a single system accessible… so irresponsible actions, sleep time for me now, good luck.

VULCAN15_N18E_MAIN_BOARD_DUMP

can anything be done with this file ?

i did not made complete spi.bin backup… i tried once, and there was an issue still with the permissions.

but i have made single backups, maybe they will help in some way

Files

desc.bin
fd.bin
me.bin
biosreg.bin

can this be put together into a full spi.bin ?

No, its usable for swap in a corrupted dump to fix, besides, the files do not contain Service Tag, WinKey Lic or Serial Number, only reference to model, looking like a cleaned/blanked.

A valid dump was to be made with fptw64 -d spifull.bin

Things that can be easily verified by you, in your linked web dump you just found, if it’s working or not your task to try, by now since the main IC was overwritten with wrong firmware image, seems you got nothing to lose as you need to recover the system, what’s been lost, since no full backup was made, it’s all Dell motherboard/system original data, Mac, UUID, SN, ST, WinLic…etc… unless there’s valid info on 2nd IC, not always present.

i totally got the structure of the IC wrong.. i understood, that the spi is the biosreg. bad part to get wrong..

the notebook got once before a spi flash and i think thats the reason why it has no service tag or what you saw about cleared, blanked.

service tag shown in bios was H6BJHS2

HWInfo_Dell_G5_5590.zip (17.1 KB)

its back to life.

you said “REBAR on laptop… cant remember seeing a success report”

The option “4G Above” was possible to activate, so i wanted to give it a try as per Guide there was nothing missing.

I followed the guide (without the patching part) what ended in this file :

inserted_biosreg.zip (5.1 MB)

After getting write permission i did :

flash was successfull and Data identical.
is there anything wrong with the modified biosreg.bin ?

If ReBar would not work with my hardware, should the machine not still booting like normal ?

You’re asking me that??? You’re the one that modded…

It should… according the REBAR mod developer… it’s only an inserted DXE driver that will only called by ReBarstate.exe

What dump was used to recover the system? The one on Badcaps?

What dump was used to recover the system? The one on Badcaps?

Dell G7 17-7790 G5-5590-7590__VULCAN15_N18E.bin
did work, this file was found on indiafix.in, nowhere else i could find a full spibackup/dumb file.

i will include this stuff in the one thread where i collect all the stuff i used/did with the Dell G5 15 5590.

You’re asking me that??? You’re the one that modded…

Yeah, kinda hoping it would work :slight_smile: . I wish i would be able to check such things…

Yes, that’s the one i thought also…

To check what… i don’t have such system to report you anything, as i said “REBAR on laptop… can’t remember seeing a success report”

Be glad that you have now a recovered laptop… and it’s booting with a flashed mod bios region with ReBar on it… the rest is to follow the ReBar developer notes… that was intend primarily for desktop motherboards…
That’s all, good luck and all the best.

i am not using the inserted_biosreg.bin, the last time i flashed it with FPTw -bios -f -inserted_biosreg.bin the machine had no display after a reboot. i havent used the Rebar.exe tool till this point.

Thats why i asked, maybe you see instantly that it could not work with the inserted DXE modul in the bios file for what ever reason.

No one can, due to different bios structures and not having identical models to test/report it… we can’t “guess” how will the system react…

OEM bioses with regions/volumes protected on DXE volumes will lead to a “death” system, yellow/red marks on UEFI tool will identify it for you.

Thank you for this hint. I saw those colored marks before.

“Protected” does this always lead to the Bios Guard ?
(my flash with the inserted DXE module in biosreg.bin was verified as identical Data, why was it accepted if it would lead to a “death” system ?)

The Hardware with the Service Tag was different from mine, what kind of process did manage to boot the machine with different hardware, when just inserting a DXE module lead to a death system ?

can i flash my unmodified biosreg.bin backup to get the Mac, UUID, SN, etc back ? ( i have *up*flashed to the bios vers i had before this super stupid noob mistake)

the “only” thing i found is different:

original : Intel ME FITC Version: 12.0, Build 1919, Hot Fix 85
”new” : Intel ME FITC Version: 12.0, Build 1606, Hot Fix 68

looks like a problem, but so far everything works, Service Tag is wrong, MAC missing, i better not touch anything again until i have a second machine for the ch341a (android, unrooted, does not work very well with the ch341a)

Too many questions and time of mine… don’t you think? How about some research, reading and learning…
Exactly what should have been done before your all mess…