$250 BOUNTY: Intel Compute Stick BIOS mod needed

[ssybesma]

Try to install Windows 7 x64 or Windows 8.1 32 bit

OK, just got up...whew...was tired. Doing that too many times this week.

I'll get started on those two.  In case you ever need it, there's a Digital River repository on archive.org for any version of Windows 7 you want.

That way you're ensured of getting a copy that hasn't been messed with and don't need a product key.

https://archive.org/download/digital_river

The text file at the bottom tells you what the file names correspond to.  No hassle download.

Also, you can download directly from Microsoft without using the Media Creation Tool by changing your browser agent:

https://www.howtogeek.com/113439/how-to-...xtensions/

[ssybesma]

Good news!!!

My BIOS actually said Windows 8.1/10 32-bit, so when I tried to use the 32-bit ISO for Windows 8.1 it worked.

Got around product key issue. 

The install is tighter than a glove, leaving no room left so I'm working on freeing up storage space and putting larger swap on external drive.

If I can get significant space freed up I'll put TeamViewer on and you guys can remote into this thing if you want.

I'm typing this from a different PC because the space is so tight on the stick right now.

[Lost_N_BIOS]

Setup_var works on plenty of BIOS, you can ignore that Insyde BIOS warning, I use it all the time on old and modern AMI BIOS

On H@0UVE - ISHI error is normal, if you get no output from any (In Win7/8) then none work, nothing to do there but forget about these tools.

Back to setup_var, we still may be able to do, using modified setup_var files (there is two others), but I'll wait now and let DeathBringer try to help you on this for a while before I jump back in, so it's less confusing.

I can mod BIOS for you and change these settings in less than a minute, no problem there, but finding a way for you to write back mod Intel BIOS is the issue. This is why I said in my very first reply you need programmer and SOIC8 test clip, we'd be done on post #3-4 if you had these tools

[DeathBringer]

I don't need TeamViewer access. Post a screenshot of my unfinished AMIClean

[ssybesma]

This work was done on the Intel Compute Stick STCK1A8LFC under Windows 8.1 Pro 32-bit.


Most work done at Windows CLI as Administrator, the rest was done with Window apps running as Administrator.

Regarding running the three H20UVE executables with the two different strings to produce the text files--

This message popped up in a window on the 9.2 and 11-beta4 versions:

IHISI: Get platform info fail in SMI!

On the 16.08 version I got this at the command line:

This version of D:\Insider_BIOS_Tools-1.1\H20UVE\100.00.16.08\H2OUVE.exe is not
compatible with the version of Windows you're running. Check your computer's sys
tem information and then contact the software publisher.

No text files at all were generated from running both commands on the three executables.



Regarding AMICLEAN.EXE run at Admin command line:

D:\>amiclean
ERROR: Read NVRAM - Invalid access to memory location.


Regarding AFUWIN.EXE run at Admin command line:

D:\amiflash\AptioV\afuwin\32\afuwin32>AFUWIN.EXE STCK1A8LFC.ROM /O
+---------------------------------------------------------------------------+
|                 AMI Firmware Update Utility  v5.05.04                     |
|      Copyright ©2013 American Megatrends Inc. All Rights Reserved.      |
+---------------------------------------------------------------------------+
46 - Error: Problem getting flash information.


Regarding AFUWIN.EXE run at Admin command line:

D:\amiflash\Aptio\afuwin\32\AfuWin32>AFUWIN.EXE STCK1A8LFC.ROM /O
+---------------------------------------------------------------------------+
|                 AMI Firmware Update Utility  v3.05.04                     |
|      Copyright ©2013 American Megatrends Inc. All Rights Reserved.      |
+---------------------------------------------------------------------------+
46 - Error: Problem getting flash information.


Regarding AFUWIN.EXE run at command line:

D:\amiflash\AMIBIOS\AFUWin\32

Error: BIOS does not support AFU.


I'm thinking we have to go to putting the clip on the chip and dumping physically.

(I guess maybe that gets around the problem of the BIOS being unreadable by going down through the OS to get it?)

No AMI utilities work even though the BIOS was probably made by AMI for Intel. I don't know who else programs BIOSes for Intel.

Question for you is will the BIOS dump no matter what if the hardware method is used?

I guess I have to crack one open myself if I can't find anyone to do for me.

The CMOS chips are physically the same, but different brands.

Thanks!

[DeathBringer]

Regarding AMICLEAN.EXE run at Admin command line:

D:\>amiclean
ERROR: Read NVRAM - Invalid access to memory location.

Good news! That was expected. Now I'm working to make new version to write NVRAM.

[ssybesma]

Regarding AMICLEAN.EXE run at Admin command line:

D:\>amiclean
ERROR: Read NVRAM - Invalid access to memory location.

Good news! That was expected. Now I'm working to make new version to write NVRAM.

OK, great.  Thank you sir!

So there is no concern about encrypted BIOS preventing it being read by going from top down through the OS?

I don't know that for a fact, just asking.

[DeathBringer]

I need intermediate results with this version - https://drive.google.com/open?id=1hN-4Im...-qBW80cR6P

[ssybesma]

First I show version 1, then I show version 2 -- I assume there was no command line switch that was supposed to be used.

In both cases below "Administrator: Command Prompt" was used...that is my usual habit anyway.

D:\>AMIClean.exe
ERROR: Read NVRAM - Invalid access to memory location.

D:\>AMIClean2.exe
ssybesma's version 2
ERROR: Read NVRAM - The system could not find the environment option that was entered.

D:\>

[DeathBringer]

Try new version - https://drive.google.com/open?id=1b2OK2w...Rgjft1LHnF