I found a mod BIOS on a forum of a VAIO with (not exactly) similar model of my VAIO and flashed it. The flash worked but all the details of my laptop (Machine name, Serial number, UUID) was replaced with the other VAIO.
All I have before the flash is only the ROM extracted using Universal BIOS Backup Tool, my mistake for not clearly understand the matter before doing the flash.
So I’m reaching out for your help/guidance to load my own VAIO info into the mod BIOS or any services that can do it.
Address in bios region is 0x1C5000, for a complete image (possibly 4 MB spi) this would be 0x345000
There’s a possibility that you might find a SONY DMI tool for editing, but I suppose it’d be easier to simply update the image you flashed and flash again.
What was the reason that you used a dump from another model?
The reason I used a dump from another model is because I was dumb thinking it is just as simple as install a program. What motivated me to do that is because I had the SSD installed but the original BIOS only enable RAID, so I was trying to enable AHCI for the drive and upgrade to Windows 10.
I hesistated to use the mod BIOS at first but I can’t resist it; therefore, the catastrophe now. After the flash, I try to reinstall the OS with the recovery media from SONY but it wouldn’t allow me to, and that moment I realized that I was F (pardon my language) and it’s been 2 long nights for me recently
So for next step, I take your advice. Could you please guide me through the process to update the image and flash again?
On another thought, if the info can be updated into the modded BIOS, is it possible to unhide the menus in my original ROM so the BIOS is modded for my own VAIO?
The modded BIOS unveil all the hidden menus, and allow to choose between the mode (IDE, AHCI, RAID) and other stuff like graphic card, CPU temperature etc. My laptop was able to switch to AHCI after the mod. About what didn’t work I think I wouldn’t be able to say coz out of my knowledge and I was too freaked out after finding out the info was replaced.
FPT stands for “flash programming tool”, use the version according to OS, in Windows as written with properly installed driver and in an administrator command window, But I recommend to do this in DOS.
It’s just a try to maybe keeping you from disassembling and using the programmer. First step is to dump the dmi area with fpt, check if address and range is correct. If the addresses are correct you’ll try to flash back the same little piece, if that’s allowed one can update the dmi information.
Was thinking a little complicated here, after checking how you did the update it’s clear that you can reqrite the complete bios region with fpt, there can’t be any protected ranges.
Just out of curiousity try to dump the complete firmware: ftp -d spi.bin
(Might give an error because of ME locked for reading in Flash Descriptor, then ignore this command)
Download and put it in the same directory where fpt is located: DMIOK.zip (312 Bytes)
Execute fpt.exe -bios -d biosreg1.bin
(=> Backup of the bios region before flash)
Execute fpt.exe -f DMIOK.bin -A 0x345000 -L 0xA0
Please be absolutely precise, fpt writes without checking the content or the area it writes to!
If you write the DMI information into relevant firmware code you get a brick.
fpt.exe -bios -d biosreg2.bin
(=> Backup of the bios region after flash)
If you can remove the usb stick and have another Windows pc accessible you can do the following to be absolutely sure:
Open biosreg1 and biosreg2 in a hex editor (HxD), compare them (Ctrl-K), they should (using DOS version of fpt) only differ in the small region with the DMI information, should look like:
Before proceeeding this part, I would like to check with you about the command to make sure I read your instruction correctly (kind of nervous when you said the laptop can be bricked )
fpt.exe -f DMIOK.bin -A 0x345000 -L 0xA0
the 0 in “0x345000 -L 0xA0” are all 0 as in number (zero) and not the letter “O”
Good to hear this worked out, thanks for the feedback!
Keep the backup of the bios region, might come in useful sometime later… (But you don’t have a complete image, you’re missing at least FD and ME region)
It’s ‘nice to have’ in case somthing will happen to your firmware.
But you’d have to deal with the flash descriptor or using a progammer, meaning possibility for damaging things in the process. For now definitely not worth the effort!