Dell G16 7630 ~ Downgrading BIOS Block Workaround & Help

[ouko]

Hello Everyone on the planet, ouko here and a newcomer to this website.

I decided to upgrade the RAM on my Dell G16 7630 (also a month-old laptop), going from the factory 16GB (2x8GB) Samsung DDR5 5600 to 64GB (2x32GB) Crucial DDR5 4800. After seeing so many success stories online—people upgrading this same model to 64GB or even 96GB—I thought it would be a straightforward process. Crucial even confirmed compatibility, so I was confident it would work.

But when I installed the new RAM, I was hit with a surprise. Instead of booting into Windows after memory training as it should, the laptop got stuck in an endless loop. I tried waiting hours, swapping out sticks, and using just one 32GB stick, but nothing worked. The system recognized all 64GB in the BIOS, but it refused to finish memory training and POST.

After digging deeper, I found out that BIOS version 1.14.0 was the last version where upgrading beyond 32GB RAM on the Dell G16 7630 was possible without running into issues like memory training failures. It seems Dell enforced a cap on RAM capacity in later versions, possibly as a safeguard, though many users have reported stable operation with 64GB or even 96GB on earlier BIOS versions.

Unfortunately, I’m currently on BIOS version 1.21.1, and Dell has blocked downgrades to earlier versions like 1.14.0. This leaves me wondering if anyone here has found a workaround for this—perhaps through modding the current BIOS or flashing an older version using tools like a BIOS programmer.

I’ve just ordered a BIOS programmer from Amazon as a potential last-resort option, but before diving into that, I wanted to see if any experienced BIOS modders or those who’ve dealt with similar Dell limitations might have advice. Specifically:

• Is there a way to modify the current BIOS (1.21.1) to remove or bypass the RAM capacity restriction?
• Has anyone successfully flashed version 1.14.0 or earlier on this model despite the downgrade protections?
• Are there hidden settings or a whitelist in the current BIOS that could be edited to allow the laptop to boot with 64GB RAM?

I’m open to any guidance or resources, whether it’s BIOS modding tips, software tools, or steps for safely using the programmer. If there’s no software-based solution, I’ll likely go ahead with the programmer to reflash the older BIOS. Any advice is greatly appreciated! I’ve been trying to hunt down answers for about a month after I bought the 64GB RAM and yet I’m Curious if other users have got 64GB RAM to Boot with this model. Please lemme know. Thank you.

[Heder]

Hi.

Annoying with vendor protection.

The BIOS is always up/down gradable the issue is just how the protection was done. You should play around with “flashrom” to figure out if your BIOS is manual programmable or not, but I would guess its programmable, and the “dell” protection is just checking the version of the bios and saying “no no” if it’s an older version. flashrom can read/write on linux (read only on windows ?)

< “flashrom -o internal -r bios.rom”

The “-r” option means “READ”, you might also need the “-r ” option if flashrom get confused, where is an example on my Lenovo

sudo flashrom -p internal -c MX25L12805D -r dump.bin

And this gave:

flashrom v1.3.0 on Linux 6.8.12-200.fsync.fc39.x86_64 (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Using clockgettime for delay loops (clk_id: 1, resolution: 1ns).
< Found chipset “Intel C60x/X79”.
< Enabling flash write… SPI Configuration is locked down.
< FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
< FREG1: BIOS region (0x00800000-0x00ffffff) is read-write.
< FREG2: Management Engine region (0x00014000-0x007fffff) is locked.
< FREG3: Gigabit Ethernet region (0x00012000-0x00013fff) is read-write.
< FREG4: Platform Data region (0x00001000-0x00011fff) is read-write.
< Not all flash regions are freely accessible by flashrom. This is most likely
< due to an active ME. Please see ME (Management Engine) — flashrom documentation for details.
< At least some flash regions are read protected. You have to use a flash
< layout and include only accessible regions. For write operations, you’ll
< additionally need the --noverify-all switch. See manpage for more details.
OK. Found Macronix flash chip MX25L12805D (16384 kB, SPI) mapped at physical address 0x00000000ff000000.

===
This flash part has status UNTESTED for operations: WP
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to [email protected] if any of the above operations
work correctly for you with this flash chip. Please include the flashrom log
file for all operations you tested (see the man page for details), and mention
which mainboard or programmer you tested in the subject line.
Thanks for your help!
Reading flash… Transaction error!
Read operation failed!

The operation failed because Intel ME was locked, but that is not important.
The text “read-write” means it’s programmable via flashrom.

FREG1: BIOS region (0x00800000-0x00ffffff) is read-write.

If you entire bios is readable you would’nt get the error above, but if some of the regions was locked you’ll get an error and need to create an layout (telling which segment it should read), mine was:

0x00000000:0x00000fff descriptor
0x00001000:0x00011fff data
0x00012000:0x00013fff giga
0x00014000:0x007fffff intel
0x00800000:0x00ffffff bios

then I dumped the bios region using

flashrom -p internal --layout layout.txt --image bios -c MX25L12805D -r dump.bin

flashrom will then create a file for the entire chip area but it only read form the real “bios” segment, not the others. Then you need to split the file, but that depends on where you bios is placed within the file ,as the bios needs to go into it’s own file. Then you can load the bios into uefitool or similar and verify it’s an actual bios.

You can also program using flashrom, but I guess first step it to ensure you it bios is accessible and R/W

[ouko]

Thanks for the in-depth Information! I’ll try this method this weekend.

Are there any other methods I can contribute to try to bypass the downgrade block on my Dell? (in case the BIOS is read-write/accessible or not?)

Also, where can I find Flashrom for Windows?

[Heder]

There seem to be a version here : https://github.com/therealdreg/flashrom_build_windows_x64,

BUT I have’nt tested it, as I’m solely on linux.

There are other tool, but I have lost track of those. If the bios segment it locked, then only DELL can unlock it (and you’ll need the programmer).

[ouko]

In case I use the BIOS Programmer as a last-resort option, Do you know If I just flash the old version onto the Motherboard, or do I have to Modify the Old BIOS such as moving the Windows Key or Service Tags to the new BIOS considering it’s a DELL Model?

This is where I bought the Programmer: Amazon.com: AiTrip EEPROM BIOS USB Programmer CH341A + SOIC8 Clip + 1.8V Adapter + SOIC8 Adapter for 24 25 Series Flash : Industrial & Scientific

[Heder]

spi-eeproms are never “only” bios code, but alot of other information, so you’ll have to investigate your own spi-eeprom and figure out where the different segment are placed, and unless someone has try’ed that before on your model - and writes here then it’s trail and error, that is why flashrom is such a nice tool as it will tell you the area of the different regions and name.

There is another tool you would try “AFUWINx64”, see GitHub - mogelpeter/BIOS-Utility: Save your BIOS Settings and restore them at anytime you want.

[ouko]

How can I get AFUWIN to work properly on the Dell model? It says “failed to find drivers” Can I load an older BIOS version and force Flash with the said program to bypass Dell’s restrictions? the instructions stated in the GitHub article sound a bit unclear.

[mspant]

Dear Ouko,
have you had any progress? I am also planning a ram upgrade and have the latest bios version.

Thank you

[ouko]

I’m perhaps gonna downgrade using the BIOS Programmer I’ve bought from Amazon. There are 2 “Winbond” chips on the motherboard, but I’m planning to do the operation this weekend and see the outcome. I do feel pretty confident about the downgrade and understanding the risks completely.

[mspant]

Dear Ouko,
I wish you the best of luck.

If you want, keep us updated.
Thank you.