Hello Lost_N_BIOS,

I am currently attempting to unlock the bios, however i'm weary about the list you are currently supporting compared to my version.

CyberPower NB-408-120 Tracer III
GK5CN6Z
BIOS Version: American Megatrends Inc. N.1.03, 7/12/2018
EC Version: 1.28.09
SMBIOS Version: 3.1
BIOS MODE: UEFI
ME FW Version: 12.0.0.1069
ME Firmware SKU: Consumer SKU

Cyberpower no longer supports this computer, and the keyboard has failed. The WiFi is also turned off (not disabled). I can not turn it back on without using the fn+f4 key (windows fails to turn it on). My last option is to unlock the bios and see if i can get things working again. A replacement keyboard seems to be impossible to obtain.

I have provided the biosreg.bin file for you but upload is limited to 6MB. The file is 10MB

biosreg.bin

@I_Alex_1 - translation issue here. Please explain in English. I translated what you said, still didn't understand what you are asking?

@Tuscani - Yes, that is all wrong Sounds like you shorted something out, time to RMA or return if you can.
You can try programming back your original dump of the 256KB chip, but if you didn't make one then nothing we can do to fix it. This is not anything to do with BIOS/settings etc, this would be EC FW chip, or other FW Chip.
I don't have these systems, the only way you can fix this if you didn't dump that chip before you erased or wrote to it (if there was not a short that blew out a trace or resistor) is to find someone with exact same model as you and a flash programmer and talk them into dumping this chip for you

I cannot download from Mega 99% of the time, but I don't need to download any files there, you need what I mentioned above + program back in your original BIOS dump into the BIOS chip.
If after you do that, provided you find a dump for the 256KB chip, and still nothing happens when you press power then you blew out a trace or resistor and will need to RMA the system

If you need me to build you a complete BIOS to program into the main BIOS chip, using your dumped BIOS region, in case you never dumped entire chip. Let me know and give me your MAC ID

@nlagee2191 - Sorry, that list is old/original list I made out for this thread, long ago, and I haven't updated the list in a long time, and it applies to many I've already unlocked in this thread but haven't added + many more that may not have been discussed yet too.
So, don't worry, I'm sure your system can probably be done as well

Do you have Lighting Effect option in advanced BIOS section? If yes, let me know what is first and last values of that setting, or show me image of the choices. Then I can unlock for you.
You probably will need to disable BIOS lock first still, if you have not already. This will be impossible without keyboard, so not sure if you can flash in mod BIOS. Can you write your FPT BIOS region dump back, or do you get error 280/368?

Hello Lost_N_Bios,

I appreciate your assistance. I currently have a USB keyboard that is working within BIOS. The on-board keyboard does have lighting options in the bios, and i have attached an image of them. I have also attached a screenshot of the output of flashing the BIOS back with FPTw. The error you mentioned did not appear

@Lost_N_BIOS I managed to flash back the EC chip desoldering it, reprogramming it soldered to the programmer itself with no errors and soldered it back to the motherboard.
Now the computer turns on again, fans spin for about ten seconds and the keyboard gets backlight, but after a minute or so it turns off again and repeats the loop.
This is the same behavior as when I lowered the vcore offset to -200mv saved the settings and then it started to do this, that's all I originally did. It is as if the setting is persistent somewhere else and I cannot figure out why is this or where are these settings saved if not in these two chips. I tought that I would be safe as long as I had the programmer to write back the chips if something went wrong.

I dont think that RMA is an option since I brutally voided the warranty doing this and a motherboard probably will cost more than the laptop itself...
Do you have some pointers that I can follow other than RMA it?.

@Tuscani
Disconnect the battery and battery from the Board. Wait about an hour. Reset the Bios to default settings.

@I_Alex_1

Thanks for trying, but I already left the laptop about two days with every power source disconnected and this behavior keeps happening.
Something deeper is going on here and I can't for the life of me figure out what is it.

@Tuscani did you dump your EC Write to confirm the write was 100% what you gave it, to manually verify the write was good? What did you write anyway, I mean where did you get the file/data to write?
If write was 100% good, manually confirmed, then I would again write back the original BIOS dump you made and try again. If that does not work for you, send me a dump of this BIOS and tell me the exact setting you changed and I can change it back to default for you. If this is all that's wrong then this will fix it
RE - RMA - These are from Walmart right? If yes, I doubt they would take the system apart to check for such things, so you may be OK if it comes to that.

@nlagee2191 - Thanks, and sorry for the delay! Please upload your biosreg to tinyupload.com or uploadfiles.io, I can't download from Microsoft it always is just blank page for me (same as their hotmail/outlook now too!)
* Edit - Never mind, I finally got it to load the page and then after 1.5 hours trying I was able to make it finish downloading I will make BIOS for you tonight
Please confirm this is the MD5 for your BIOS so I know it's OK, since you didn't zip it up - 3274F70BDB27966699B9E020C15A5765
If it's not, please zip and upload to one of the hosts mentioned above

Hello @Lost_N_BIOS ,

Thank you for your time on this. The MD5 did not match, so here is an encrypted zipped version. the pw is bios1234.

I attached the file to this post, and here is a tinyupload
http://s000.tinyupload.com/index.php?fil...796778336044379

@Lost_N_BIOS Thanks for all your effort.

I bought the laptop from Aliexpress from a sketchy store that no longer exists.
For the BIOS I have a good full dump of my modded bios that was working fine until I changed the CPU undervolt value to -200mv. And for the EC, I have my own confirmed bad dump that once I write it back to the EC chip it does not even turn on.
But with the files from this site wich I will upload as attachments so you can check them, I flashed those with the programmer and the laptop does turn on but with still with that endless loop behavior as if the CPU undervolt value was persistent somehow even with full BIOS flashing...

u8.BIN is the EC data and u20.BIN is the 1.04 BIOS data probably from MechRevo since it is the same stock version that my laptop came with in the first place.

@nlagee2191 - You're welcome! That seems odd, since IDM rebuilt the file and it opens properly. Please confirm above file at post #23 MD5 is following, tinyupload is invalid link (FYI), if not then how you are getting MD5 must be unusual?
* edit - Yes, something in how you check MD5 is not correct, I get same MD5 with attached file at post #23 - 3274F70BDB27966699B9E020C15A5765
So, I will unlock this BIOS, please check back for edit here if you are reading this and do not see file linked below yet.

* Edit - @nlagee2191 - here is your unlocked BIOS, flash via FPTw.exe -bios -f biosregm.bin << - removed from -biosregm.bin (noted, for post posterity )
https://ufile.io/dkolbp3c

*** WARNING *** - This BIOS is user specific! If you are not user nlagee2191 at Win-RAID.com forum, DO NOT USE THIS BIOS!!
If you do, and you are not nlagee2191, then you will loose your serial, UUID, OG NVRAM, and possibly LAN MAC ID as well.
You have been warned!!!

*** WARNING - To ANYONE with laptop and unlocked BIOS!!!! ***
DO NOT try to enable this graphics card or disable that card, switch cards etc. Otherwise you will end up with no display output (ie black screen) and no way to recover except by blind flash or with flash programmer.
You can change graphics related settings, like changing memory sizes, or core speeds etc, just don't try to disable one card or change which is main etc.

@Tuscani - If you have BIOS region dump from before you changed this setting, then that is all you need to program back (+FD/ME and GbE if exist).
If that does not boot, then you have other issues, blown trace, resistor etc (this comment really only applies to before you did anything to EC, after that who knows) EC FW would have never been touched in any of this, other than when you removed/dumped/wrote etc (ie you shouldn't have touched this)
Re-confirm your EC FW now matches what you originally dumped off there, but dumping it again and comparing with what you wrote. This way you manually confirm the write back is 100% same as what you dumped off it to begin with, if not you need to use other software version or ID to write to that chip.

Files from this site? The files here are usually BIOS region only most of the time, from users which you should not use.
And when BIOS region only you cannot program that to your chip without rebuilding it into a full BIOS first (FD, ME, GbE, then BIOS region)

Please send me ONLY your original dumped BIOS region before you had this issue, and also include your first programmer dump from the BIOS chip after this happened, before you wrote anything to the BIOS.
The above files I do not need to see, do not matter from how you describe them. ie "probably" and stock, neither of these terms should be used when considering programming BIOS, stock is not ideal when you have backups and "probably" should never be mentioned (only program "For sure" items )
OK, to be sure, I checked, and u20.bin is NOT stock BIOS, so you need to tell me exactly what that is before I can comment to you about this file. Mainly, to fix your issue, unless there is physical damage to something, I need the two files I requested above only

@Lost_N_BIOS - Yes, I have two region backups that I made with FPT before all this mess, one from the stock 1.04 MechRevo BIOS and other from 1.08 OverPowered .
The full bios is 16MB and the FPT dump is 10MB, can you tell me if I should change any options in CH341A Programm before I to write it to the chip with the USB programmer?.
I uploaded as attachment the backup that I made using FPT of the stock 1.04 BIOS to see if you can do some miracle with it.

@Tuscani - Yes no worries, I know all about the BIOS regions and there sizes etc. Which BIOS/File in above package were you using last, before you did this, that was working properly?
Ahh, there is only one file there So, was this the last BIOS you were using and it was OK before you did all this?
If yes, program this back to BIOS chip, and then confirm the EC FW is OK how I mentioned above, then system should start, unless there is physical damage due to short during reprogram attempts, damaged solder pads, blown trace etc.
https://ufile.io/jozta4xk

@Lost_N_BIOS

I was checking MD5 through Command prompt.
I flashed the bios as instructed, however I ended up with error 189 as shown in this screenshot


I just tried to re-flash the original as well, and got the same error.
I did make 1 change to the system recently, and that was disabling the Intel Optane Memory. I assume this made changed to the Bios somehow, and i'm unable to re-enable without formatting the drive.

I created a new Bios dump named biosreg3.bin, and was successful in re-flashing the Bios with it. I have attached that dump to this post as well.

@nlagee2191 - Your image shows you are not at the correct explorer location that contains your BIOS/mod BIOS files (ie "File not found", since you have browsed to the win32 windows folder for some reason).
Navigate to the correct folder which directly contains your FPTw.exe and your BIOS region files (put bios/mod bios in FPT folder)

I used hex editor to get MD5, but MD5 should be MD5?? Show me how to check via CMD like you did, thanks. Maybe I can see what's going on there

@Lost_N_BIOS
I copied the folder WIN32 from the tools folder to my root C drive, and was running it from there. This is the WIN32 folder and contents in the screenshot.




When I changed the directory back to the original directory that I created it from, I still get the same result as shown in this screenshot:




I used command prompt and ran this to check the MD5:
certutil -hashfile [filename] MD5
Here was my output: