@Lost_N_BIOS - I see. I didn't know that about laptops...

Anyway, ok. I already did the redo of write/dump as you have instructed before (which was how I got the .bin file). I was just describing how I did the comparison of the 2 files since I do not have a hex editor.

But just in case, I did it again - redo of write/dump as outlined before.

Zitat von Lost_N_BIOS im Beitrag #508

---

Here, program this back via >> Open app >> Hit Unprotect Icon (not dropout menu, just the lock icon) >> Erase >> Black Check >> Open BIOS file >> Write >> Verify
If it fails to start after that, please repeat this process exactly, then do not power on, instead do below and send me the file to compare vs the file you wrote (or you can, compare in hex, should be 100% match, otherwise there is a write issue)
>> Close app after verify above >> Open App >> Read >> Verify >> Save

---

@Enab - Thanks. That's 100% match to the fixed file I sent you, so writing is working perfectly. This leaves only messed up ME FW, or EC FW on other chip.
Here is next BIOS to try with cleaned updated ME FW, if this fails then you'll have to find the EC FW chip, dump it, and check vs some other stock EC FW (if I can find, or if it's in stock BIOS package etc) If it's on a chip that is not SOIC8 then it may be impossible to fix
**** On pause, while I ask plutomaniac for latest PCHC CMP FW to merge into ME FW, sorry, but I want to be sure all is latest and everything is clean/stock in there as much as we can.

I can't pull complete ME FW from stock BIOS to use vs making a cleaned one from your dump because the stock BIOS package you linked me to is not for this model I'm not sure what that's for, BIOS structure is totally 100% different, looks nothing like your BIOS at all.
That stock package has differnet BIOS ID/Tag, version layout, and says it's for "S2 Air Series PF4NU1F / RENOIR" vs your original dump is from "Z2 Air-S Series GK5MP5X / CML"
I think you maybe downloaded wrong package, or possibly they have wrong package linked at the download page for your system?
Can you check again, and redownload to confirm, or link me to the download area so I can see what's going on

@Lost_N_BIOS - That is a sad realization that it may have to be brought back to the manufacturer just to have it fixed if I fail to get it to run. On that note, I have asked them now for a copy of the BIOS because I realized from what you said that the 2 BIOS are for different models. I am less hopeful that they would give me that from what I have been reading about Tongfang but I still asked for it just in case. Regarding the BIOS that I sent you, well I double-checked it, and true enough, the one I sent you that I thought was the BIOS for the laptop was for another model (S2 Air), and not for the model of my laptop, which is Z2 Air-S. So since I made that mistake and it is wrong, then I don't think there's no need to do anything there, as there are no BIOS available for download for the model of my laptop at http://www.mechrevo.com/plus/search.php?...eyword=z2+air+s (I just use google translate for my chrome browser).

While reading this thread, I read a user named shtooka who did the same as me and tinkered with his memory timings. The picture of his board looks similar to mine but I read it was a different board (GK5CN6Z) with a different BIOS. But in the end, you guys made it run, so I'm hopeful we could at least make my laptop go and run again. Just like him, I also am disappointed in having bricked our computers just because we adjusted our memory timings. It's become such a hassle.

@Enab - Yes, sorry to say, it could come to that since BIOS fix isn't fixing it.
Hopefully they send you stock BIOS package, but we should not need, I only looked at what you sent to see if stock ME FW was in that files BIOS (due to ME FW update concern I had, but that would be answered/solved by plutomaniac anyway once he got back in) But, would be great to see the FD, in case yours is corrupted!

What you can try, which not sure if you have yet or not, is to remove all HDD/SSD, and ALL Memory, then start the system, let it run/attempt to run for a minute or so.
Then shut down and put back in a single stick of memory only, then try to start again. Sometimes this will clear CMOS and or load fail-safe defaults

So, shtooka did same, and I helped him fix via BIOS? If yes, then maybe it's not an EC FW issue, and once I send you a few more BIOS we'll get it sorted out
Please link me to those posts, or tell me the post # - From his folder, it looks like I just did the same I did for you above, but redid some NVRAM stuff too, so maybe just tried to leave his BIOS as-is and reset NVRAM only at first.
What I did for you in fix 1 BIOS, would have done all that anyway, I made BIOS for you which was in full = to what I sent you that you first flashed to unlock it, other than the FD and ME FW that was in your dump, and that's why I'm thinking maybe ME FW got corrupted and is causing a failure to boot, because it should otherwise be "square 1" unlock BIOS
Here, let's confirm, this is your 100% stock BIOS region, first FPT dump + your FD/ME from current chip dump (if it fails to start, then FD or ME FW issue, or EC FW). As soon as I am 100% sure on question I had to ask about some parts of your ME FW, I will make you BIOS with that cleaned/updated to see if that will resolve the issue.

Actually, I went ahead with ME FW stuff for now, please test in the following order (always erase and blank check, etc.... same process each time when you do an a program in of file )
1. whatwasreadbyprogrammer-Fixed1MEFW << This is what I sent you initially to fix, with unlocked menu, + now Cleaned/Updated ME FW
2. whatwasreadbyprogrammer-Fixed2OGRNN << This is your chip dumped FD/ME (as-is, like it was in fix1 previously) + your original FTP BIOS region dump with locked menu
3. whatwasreadbyprogrammer-Fixed2OGRNNMEFW << This is same as #2 but with clean/Updated ME FW

https://ufile.io/rnl69e5a
---------------------

@Enab - wait! Do not use above files until I redo, I should have waited on the ME FW thing I was asking about, plutomaniac just sorted it out for me and I picked wrong thing for your BIOS (may cause future ME FW update issues) But, it will work/boot etc, and we can fix later, if you've already flashed and got it booting.
For now, I am redoing package, if you have not programmed anything yet, toss those files out and wait for edit

* Edit - Here is proper files to use >> https://ufile.io/wt1lcykx
1. whatwasreadbyprogrammer-Fixed1MEFW2 << This is what I sent you initially to fix, with unlocked menu, + now Cleaned/Updated ME FW
2. whatwasreadbyprogrammer-Fixed2OGRNN << This is your chip dumped FD/ME (as-is, like it was in fix1 previously) + your original FTP BIOS region dump with locked menu
3. whatwasreadbyprogrammer-Fixed2OGRNNMEFW2 << This is same as #2 but with clean/Updated ME FW

@Lost_N_BIOS - I did all as you have said. From removing all memory and SSD then trying to start with only 1 stick of memory, etc. - it did not work.

Then I tried all 3 files that you sent (the corrected ones), 1-by-1, in order, and still, none worked. I have even redone everything to make sure I have erased it and blank checked it before programming in a new file then verifying it before trying it out - still, none worked. It is truly exasperating.

Oh, the time shtooka mentioned that he had his computer running in this thread was at #396. But in #387 he mentioned he had a different BIOS for his model computer. I didn't even think that was possible. But if it is running, then I guess that is all that matters. I suppose he just built up the serial and everything from there. But for my computer, I have no idea. Is there still a way for this to be rectified?

@Enab - Sorry to hear!! Sounds like possibly EC FW is messed up then, or maybe your FD got corrupted and that's been carried over into all BIOS I've made you. Hopefully they send you stock BIOS to try soon.
Yes, all these systems discussed in this thread, that are Tongfang based, you can usually use some other brands BIOS, as long as it has same Tongfang model.
But, in those cases, users are usually in running state, so they can reflash stock BIOS and EC FW at same time (needs to match, usually sent out in sets)
These compatible systems all usually have same graphics card as well, kind of a must. Your system's Tonfgang model is GK5MRFX.
I searched all my BIOS stock and user dumped folders and do not find any with same model, but you may find some in Google. * Edit, I tried, no luck Hopefully they will send you stock BIOS+EC package soon!

Did you try the 10 times booting shootka mentioned at 398? I read through all the posts in that area, and I see as I thought while looking at his folder, we just rebuild his BIOS in a few ways like I've done for you, except we focused more on resetting NVRAM at first.
In your case, all that was done instantly by the BIOS I sent you all with pre-issue NVRAM due to all have BIOS region from before issue (original FPT dump, or original unlock made from that, which you already confirmed booting)

Hi @Lost_N_BIOS, hope you're doing well.

I have a PC Specialist Recoil III RTX (GK7CP0S) i7 9750h and RTX 2060. I was wondering if you could assist me with an unlocked BIOS? I am new to this and I do not know what the benefits are. Would this allow me to unlock my RTX 2060 to 115W? Or boost the CPU power limit?

I believe it is a 1.55 BIOS. I have attached the files that I have flashed from the vendor.

@dinamo_909 - CPU power limit maybe, if EC FW is not controlling that. Please send me images of your BIOS advanced page top to bottom + one of Boot page too, put all this in a single zip (images + file from below)
Then do as you see in spoiler and let me know what error if any you get at step #2. I suggest you reset to default any changes you made with throttlestop and or XTU, then uninstall them, if you plan to make similar/same changes in BIOS

Thanks @Lost_N_BIOS. Please see the attached ZIP.

ME: v12.0.20.1307
Small error on step 2: "GbE Region does not exist" (Attached screenshot)

Also, anyway to unlock the RTX 2060, or get the Eluktroboost feature?

@dinamo_909 - Sorry, I forgot to mention, at the Light Effect option on Advanced, what is first and last choice?
GbE error is normal, looks like you do not need to do anything else to flash in mod BIOS, already unlocked

Sorry, I know nothing about Nvidia cards, only that you can't edit their vBIOS on modern models like that due to Nvidia blocking this via signature checks and signed certificates now.
Not sure on Eluktroboost, if that is something that relates to this and you see others using, then you can try and see if it works on your system.

@Lost_N_BIOS - I attached a picture below. Could that be the EC FW chip? It is also near the motherboard chip. If it is, what chip ID should I use to read it?

@Enab - could be, read it and see. This is Gigadevice GD25LQ80 1.8V chip, so you need to use adapter - Use 1.34 software and exact ID

@Lost_N_BIOS - Ok, got it read. But then, after saving it, I'm not sure if it is correct, as the file looks too short (?). But who knows? I placed it below as an attachment.

@Lost_N_BIOS - Hi. The manufacturer sent me 2 BIOS in zipped files. I don't know which is which, so I just sent you both in the link below.

https://ufile.io/f/onrub

@Enab - I can't say for sure, since name is clipped, but those files you uploaded look like maybe same package you downloaded twice (so windows added the (1) to the file name)
Please confirm, compare both zip in hex editor and see if it's a match, or compare each files MD5 checksum, if it's a match then same package. Let me know, then I will download other one if needed (For now, I only grabbed the one without (1))

Your 1MB chip dump looks OK, why do you say too short? But, this is Nvidia E4904 SKU 11 VGA BIOS, so not EC FW


Do you see any other similar chips? Look under heatpipes, may be hidden there, or below black stickers/tape, or under memory, wifi or NVME/M2 cards etc

On EC FW in package, as manufacturer how you are supposed to know which one is for you?
I see in change log notes >>
1.08.20 for IDO
1.08.70 for BR KB

Ask them how you know if you need IDO one or BR KB one. Also, since they are replying to you, ask them where the EC FW is located, and if it's in QFP package or SOIC