Just posting my specs, I have decided to use the CH341 Programmer:
System Model: OMEN by HP Laptop 17t-cm200
(HP official website does not see 17T-CM200 as an actual model prob because it got discontinued, it is recognized as 17T-CK2000)
System SKU: 70W93AV
Bios: F.12
Motherboard: 8BAD
I am gonna post photos of the MicroChips I believe are bios chips soon.
I have managed to get the CH341A Programmer, I also found out that I have 2 winbond IC chips which i assume to be BIOS chips. One is near the CPU which as I have read from many threads (IC Bios chips are usually closest to the CPU) and one is the image that MeatWar showed. I think I will read both of the chips and compare which oneâs data has something similar to that of Bios to determine which one is correct.
So Now I am trying to read the BIOS chip with CH341A.I used 1.8v Adapter because specs say 1.65V-1.9V the Chip operates on.The software detects it, it thatâs there isnât the Chip in the library of AsProgrammer that I am reading with. It only gives me W25Q16FW
Nvm, I just decided to follow by the Base IC âW25Q16â,It does read the chip.Hope I am doing it right.
Just a quick update:
I checked both chips mentioned, one WinBond and another Macronix
CH341A managed to pickup the Macronix chip unlike WinBond for which I had to choose the âBaseâ type.
Trying to extract and check the data from WinBond Chip gave me 2MB file with something I am unsure of, whether itâs a security thing or not. I am uploading it here.
Extracting the Macronix gave me a 16MB file with turned out to be BIOS files, So I just took the F.11 and pushed it to the Macronix chip.
Just to note, ME and TPM are still undetected and corrupted.
Now what I wonder is:
Could that WinBond Chip store the TPM / ME ( I believe this is unlikely for TPM due to Specs for this series laptop being fTPM " Firmware Based TPM" ) B1.zip (924.5 KB)
NVidia vbiosâŚkeep working, youâre ridding the âhorseâ like a cowboyâŚhope the âfuelâ doesnât run out!!!
Now⌠still without the user provided any clear HP motherboard identification/usefull full photos⌠theres a couple of more IC on the rigth of memory banks, at least one, keep digging.
EDIT: ALELUIAAAAAAâŚwe got âPICTURESââŚdamm sir, was this so hard to take out the ram stick??? Itâs not always like this on all mbs, thatâs for sureâŚ
HP G3LC is indeed an HP Mb Dscrtx408012gbfgsyni913900h (N35245-601)
BIN files are data⌠data is coded, code can be viewed with specific tools, some not public and other utilities like an Hex editor for ex, dis(a)assembler etc⌠youâre not on that point yet to put the wagon on front of the horsesâŚ
That smaller IC is a voltage regulator, thereâs another IC below the M.2 slot and seems not any more visible at first sight, that can be an EC/TPM/THB etc⌠unless on the other side of the board.
EDIT:
No you cannot, what or who indulge you to believe that UEFI tool can read/decompose and identify all kind of content, this is a PHY SIO component controller and indeed it may be THB relatedâŚas its a 1Mb data content, traces of it can be viewed with a HeX Editor.
This IC Chip is both near the CPU and the SSD Slot. I am going to attempt to read them both.
Also could you tell me what that tool is to read the .Bin files? Thanks.
I think I found Bingo. They hid it under a piece of tape. (Might be wrong since itâs near the USB-C Thunderbolt and this just might be the Thunderbolt controller. The other IC Chips i showed previously are some Power Control chips with no data i could get from.
16 MByte or 128 Mbit. Not 8 Mbit or 16 Mbit. Iâd strongly recommend to read the datasheets. You dumped the firmware already, so you should be aware of its size?!
Yes I was aware of it, when I read and extracted the data from the MX Chip is it was 16 MB. 2MB came from WinBond chip which MeatWar showed was a Graphiv vBios IC.
I am currently not able to work on the issue. I would like to say that I am currently lost on what I am suppose to do, I seem to have checked all of my IC chips and check them all for any TPM or ME or BIOS files. No luck of that tho, maybe I am missing something or just not understanding something?
The way to get to a clean image with your machine specific information was described already.
If thereâs no such second chip/ no recovery information can be found itâs dumping the 16 MB chip, compare it to the dump done with software, preparing a firmware and to flash it to the correctly identified firmware chip.
I might be a bit jungled up in the Transfer of padding from one bios to another. I managed to do the first padding transfer but not the second one which you mentioned to be as âLaterâ.
While trying to transfer the second padding I get reconstructed region size 9C0000h (10223616) is smaller then original A00000h (10485760) Which I assume is either something I am unaware of or itâs due to the missing NVRAM you mentioned?
If I could get some push help on this part, that would be awesome.
Sorry, deleted the files regarding this thread when there was no answer to my last post after 4 days. Itâs a little tiresome to restart working on the same task over and over again.
Yea sorry about these long pauses in-between. I am playing around to see what could help me to modify the bios. I am using MMTools, Phoenix and UEFITools and all of them give me the same type of error related to size of the padding. I am going to just see if maybe starting from clean might work.