Page 10 of 26
#136 RE: Accessing Locked BIOS Menu Settings by Lost_N_BIOS 01.09.2018 20:48

avatar

Yes, as long as there is no other "BIOS Lock" you can flash BIOS region. If there is "BIOS Lock" enabled in the BIOS you might have to do some other dance before flashing BIOS.

Yes, I was thinking of PROCHOT# as in CPU reaching 85-95C whatever PROCHOT# is set to on that CPU. Thanks for the further info, I will see if I can find anything in BIOS tonight.

Good find on the exe, I extracted it already before I asked, but wasn't sure if that was BIOS or not (Didn't have time to look into it). I just assumed it was a downloader only since it appeared to be that way when ran, so I assumed even if BIOS was in there it would be older.
Looks like we now know how to flash BIOS then, good looking around! After reading that, I think I was correct, you still need to run this tool and download the BIOS first or use the URL info on that page to download using the platform ID (So I need that from you)

#137 RE: Accessing Locked BIOS Menu Settings by akm 02.09.2018 09:14

I already shared the downloaded BIOS with you in post #135. The exe file that you shared, when executed, downloaded the latest BIOS (which is the same as running on my system) as an exe file. The process to extract that exe to get the actual rom file is there in the link that I shared with you, but apparently it doesn't work. When I run the exe, unless I run the firmware update process, it does not reveal the files in the Temp folder. As I ran the firmware update process, I could see some files in the Temp folder which was open during the update, but I could not copy its contents as keyboard mouse stopped working during the update. After the finish of the update and restart of the system, again there were no files in the Temp folder except for the log file, which I have shared here.

If I just use the dumped bios.bin file and flash it, do you think there could be any risk?

I should mention that if I check the dumped BIOS, then by default BIOS lock is disabled. The status of different locks is:

SMI Lock: Disabled
BIOS Lock: Disabled
GPIO Lock: Disabled
BIOS Interface Lock: Enabled
RTC RAM Lock: Enabled

#138 RE: Accessing Locked BIOS Menu Settings by raun0 02.09.2018 16:44

Maybe offtopic, but is there anything that could be done with mobo that won't boot without graphic card?

I have couple of computers running headless servers and there is graphic card warming up inside just to get server booted.

#139 RE: Accessing Locked BIOS Menu Settings by Lost_N_BIOS 02.09.2018 20:09

avatar

Sorry, I don't see any BIOS in post #135. And yes, that downloader, downloads the BIOS file, which is what I was asking you to send. The guide explains how to get URL to download this BIOS, aside from the downloader.
The downloader itself does not contain a BIOS or AFUWin, you have to do as the guide says, and or follow these steps outlined to get the BIOS file http://forum.notebookreview.com/threads/...5#post-10728275

I think your method mentioned would be fine and should update the BIOS. I would use AFU that is not part of their downloaded tools, in case it's tied to BIOS signature or some security check etc.

@raun0 - I am not sure what you are asking?

#140 RE: Accessing Locked BIOS Menu Settings by akm 02.09.2018 20:38

Zitat von Lost_N_BIOS im Beitrag #139
Sorry, I don't see any BIOS in post #135. And yes, that downloader, downloads the BIOS file, which is what I was asking you to send.

It is there. I shared it alongwith the Descriptor dump. The link is here.

Just to clarify, I have been talking about ITEM_20141028_21442_WIN_P09ABI.exe (shared above and in post #135), which is downloaded from BIOSUpdate.exe that you provided. I am not able to further extract ITEM_20141028_21442_WIN_P09ABI.exe to get the rom/bin/cap file, as the instructions provided in that link don't seem to work.


Zitat von Lost_N_BIOS im Beitrag #139
The downloader itself does not contain a BIOS or AFUWin, you have to do as the guide says, and or follow these steps outlined to get the BIOS file http://forum.notebookreview.com/threads/...5#post-10728275

These instructions don't work. There is no BIOS file in C:\Users\username\AppData\Local\Temp\__Samsung_Update or in C:\Program Files (x86)\UEFI WinFlash.


Zitat von Lost_N_BIOS im Beitrag #139
I think your method mentioned would be fine and should update the BIOS. I would use AFU that is not part of their downloaded tools, in case it's tied to BIOS signature or some security check etc.

Although I am not able to extract the manufacturer provided BIOS file from the exe file, I have the dump of the BIOS region.

#141 RE: Accessing Locked BIOS Menu Settings by Lost_N_BIOS 02.09.2018 21:17

avatar

I seen and downloaded the descriptor yesterday, sorry I forgot BIOS was in there too. Plus, I wanted new/latest BIOS using the downloader program, so we could get correct tool that normally would be used with it's BIOS.
My bad man, I forgot about that and it was lost in pile of folders with me thinking only the desc.bin was there, I should have looked again!

I was able to get extracted contents, as seen below, zipped it up for you too

https://nofile.io/f/DFwFVgUAeJw/___Samsung_Update.zip

Yes, It uses AFUWin so AFUwin or AFUDOS should be fine to use. You may need to find certain versions of the tools though, sometimes older BIOS only work with older versions, new with new etc.
You may be able to use the ones zipped above from the BIOS package, but if it does any security check then may be best to find version that works that doesn't come from Samsung.

FPT should also work for this BIOS, per these FD restrictions (So BIOS region yes, ME no but ME should work ok with ME FW Update tool)

#142 RE: Accessing Locked BIOS Menu Settings by akm 02.09.2018 22:24

So, what do you suggest?:

1. which BIOS file should I use for making modifications using AMIBCP:
the .cap file that is there in the extracted files which you have shared, or
the dumped .rom/.bin file?

I should mention that the .cap file is 3076KB while the other is 3072KB. None of these files have ME (but that is not a problem). Also, if I make any change to the .cap file, I get some message like "Saving unsigned changes" or something of that sort. I will make a small change first, flash it and then try making further changes.

2. which AFU do you suggest to flash the file:
AFU current version, or
AFU that is there in the extracted files?

If you see the DEBUG log that I shared in post #137, the default BIOS process does certain things before and after running AFU like changing Power Policies etc. So, Windows flashing process looks a bit risky to me. I am more inclined to use AFU (current version) and flash from DOS. What do you say?


And above all, do you suggest that I wait for the external programmer to come before flashing the modded BIOS or it is relatively safe like it was in the other laptop?

#143 RE: Accessing Locked BIOS Menu Settings by Lost_N_BIOS 03.09.2018 07:29

avatar

Ohh! I thought you figured that all out, and I said OK yes Sorry for not clarifying, I thought you had it!

Use the .cap file, remove the capsule to get BIOS.rom (ie extract body via UEFITool) Edit that and flash via AFU

On rom/bin FPT/AFU, do those match via hex? Neither will match the extracted rom from capsule file, since it wouldn't have any of the NVRAM or board specifics that may/should be include with the AFU/FPT dumps.
If you use AFU/FPT dumps, only use same tool to put back (ie use AFU Dump with AFU, FPT w/ FPT)

Any of the three would be fine, only the capsule/rom extracted from that will be latest BIOS of course. Yes, capsule is 2kb.

Yes, that is common message with AMIBCP/Capsule BIOS. You can use/edit capsule files, but sometimes it's easier to flash with BIOS extracted from the capsule (capsule is security and signed)

Which AFU to use, I would use the one included with the files first, if it gives you security error or integrity error find it's version and download similar version non-Samsung.
Or yes, you can try AFUDOS first if you want/feel more comfortable with that. The processes mentioned in the log are only to make BIOS flash process safer.
Disable safely remove the USB while it's in use flashing the BIOS, and the powerpolicy is to block power changes while flashing, disabling power switch and lid switch, all standard practices to try and save end user from accident during flash
Then all those changes are released/reset and restored back to user access once BIOS flash is done

Dumping and flashing modified BIOS are not related, so no that does not mean it's a sign that it will flash mod BIOS.

On your final question, you never can tell. If you are worried, and it's a critical to you system but you still want to go for it, make only a single change and then test.
Also, be sure before you flash anything that once you make a mod/change and save that BIOS, open that modified BIOS in as many other tools as you can and the tool you edited it with initially.
Do this to make sure all looks OK and same, ie same errors or not same errors as before, like in UEFITool sometimes always error show when open BIOS.

#144 RE: Accessing Locked BIOS Menu Settings by akm 03.09.2018 09:02

Thanks! That clarifies it very well.

1. I tried flashing with the afu that was included with Samsung files. I got an error:

1e - Error: Secure flash function is not supported on this file.

So, I think it won't be possible to use the AFU that came with the files. I checked its version. It was v.3.05.03. The AFU version that I have is v3.09.03.1462. I was not able to find a non-Samsung v3.05.03 AFU. But I found AFU v3.06.01, can I use it?

2. Upon comparing dumped bin/rom using HxD, I found they were not 100% same. There was a slight difference. The size of each dump is the same (3072KB) though.

#145 RE: Accessing Locked BIOS Menu Settings by Lost_N_BIOS 03.09.2018 09:11

avatar

It's safe to try either AFU you found, even 4 or 5 too. I just thought it would be best to try first ones in the range of the one supplied with the BIOS.

I assumed AFU/FPT were not the same, if you want me to check if I can see what the differences are put both in a zip and I'll look when I have a chance (leaving right now)

#146 RE: Accessing Locked BIOS Menu Settings by akm 03.09.2018 10:21

I tried flashing the capsule removed BIOS using AFU v3.06 and it was the same error:

1e - Error: Secure flash function is not supported on this file.

Looks like there is some security enabled somewhere.

I took fresh dumps of the BIOS (bin and rom) and found that the dumps are identical when compared using HxD editor. Perhaps I did something wrong the last time and so, I was seeing differences between the dumps. I have shared the Dumped BIOS files here, for your reference.

#147 RE: Accessing Locked BIOS Menu Settings by Lost_N_BIOS 03.09.2018 21:07

avatar

Thanks for dumps, I will take a look and see if I can find the locks, if I do I will try to help you with a way around.

In the meantime, can you find out ME version, and download matching Intel System Tools package, then run meinfowin. You may have to guess, either based on current available ME driver version download (Back on early versions, driver more closely matched ME version).
Or you may need to try a few Meinfowin versions from different packages until you find one that works, start at 5, 6, 7, 8 etc.
Intel Management Engine: Drivers, Firmware & System Tools

And, then from Flash Programming Tools / win/win32/windows etc run FPTw and use these three commands and show full image of each so I can see command entered and success or error output, then upload any files created.
fptw.exe -d spi.bin
fptw.exe -me -d me.bin
fptw.exe -desc -d desc.bin

SMI Lock, BIOS Lock, and GPIO Lock all disabled by default. There is no ME in your backup, so doubt AFU is trying to access/write to the ME section, so I'm not sure what is causing the security lock message. It may be due to AFU versions, did you try any 4 or 5 versions yet?
Hopefully the FPT stuff and MEinfo will tell us more, I'm betting you can write to BIOS region with FPT so problem solved anyway since we are not updating ME (and that can likely be done with ME FW update tool later if needed)

#148 RE: Accessing Locked BIOS Menu Settings by akm 03.09.2018 23:22

Zitat von Lost_N_BIOS im Beitrag #147
In the meantime, can you find out ME version, and download matching Intel System Tools package, then run meinfowin. You may have to guess, either based on current available ME driver version download (Back on early versions, driver more closely matched ME version).
Or you may need to try a few Meinfowin versions from different packages until you find one that works, start at 5, 6, 7, 8 etc.
Intel Management Engine: Drivers, Firmware & System Tools

ME version is 8.1.65.1586. MEInfo dump has been shared along with the Descriptor region dump and other text files here.


Zitat von Lost_N_BIOS im Beitrag #147
And, then from Flash Programming Tools / win/win32/windows etc run FPTw and use these three commands and show full image of each so I can see command entered and success or error output, then upload any files created.


I already tried that previously. As I mentioned in post #133, I get an error message when I try to dump the entire spi image or the ME region. The error message is:
Error 26: The host CPU does not have read access to the target flash area. To enable read access for this operation you must modify the descriptor settings to give host access to this region.

I can dump the Descriptor region and the BIOS region with success though. Nevertheless, I tried running these commands again in verbose mode and have captured the complete error and other details in text files. All the text files along with the dump of the Descriptor region dump have been shared in the attachment link above. The Descriptor region rom file was also shared in post #135.


Zitat von Lost_N_BIOS im Beitrag #147
SMI Lock, BIOS Lock, and GPIO Lock all disabled by default. There is no ME in your backup, so doubt AFU is trying to access/write to the ME section, so I'm not sure what is causing the security lock message. It may be due to AFU versions, did you try any 4 or 5 versions yet?

I have not yet tried AFU versions 4 or 5. Which version do you recommend? You told me earlier that matching AFU version as compared to Samsung AFU should be used, so I did not bother trying any higher AFU versions.


Zitat von Lost_N_BIOS im Beitrag #147
Hopefully the FPT stuff and MEinfo will tell us more, I'm betting you can write to BIOS region with FPT so problem solved anyway since we are not updating ME (and that can likely be done with ME FW update tool later if needed)

Yes, some time back I updated the ME firmware of this laptop.

#149 RE: Accessing Locked BIOS Menu Settings by Lost_N_BIOS 04.09.2018 05:38

avatar

Sorry man, I didn't look back or think to look back. Main goal there was so you could choose correct Intel Tools Package to run the FPT stuff. And sorry, we've done so much here, now on several models, I forget what's been done already and where we are
So then, fptw.exe -bios -d me.bin Works correctly of course, and that is how you get BIOS FPT dump, derpppp! I remember now, the descriptor, posted image of it inserted into a BIOS above, you can only write to BIOS and GbE

Try both 4+5 AFU, I only mentioned the older ones because that's the one it came with so best to start there, but I assume 4-5 will give same error.

BIOS is all you want to write to anyway, so FPT can be used for that without issue using this command
fptw.exe -bios -f biosfile.bin

Or
fptw.exe -rewrite -bios -f biosfile.bin

#150 RE: Accessing Locked BIOS Menu Settings by akm 04.09.2018 09:28

No problem. And please don't apologize for anything. I am much obliged to you for all the help.

I could not find a working link to download AFU 4, but found AFU 5. I checked that AFU 5 is only supported for APTIO 5 BIOS. This laptop has APTIO 4 BIOS, so I guess that it may only cause issues if I use AFU 5. Shall I still try AFU 5?

I tried both the commands that you shared. I am surprised that the flashing went successful, but the changes made in the BIOS file do not reflect. I disabled HPET and forced visibility of CPU Configuration in Advanced Menu. After flashing, I found that HPET was still there in device manager and CPU Configuration did not get exposed. I opened the flashed BIOS file to see if the changes were saved correctly and they were. Any idea what could be wrong?

Xobor Forum Software von Xobor
Datenschutz