AMITSESetup Decryptor

[Stefan Steff]

Isn't there any other solution? (this is not my area of expertise), I am afraid of breaking my laptop, as I need to remove the administrator password so I can enable virtual technology or something similar.
I set the password 2 or 3 years ago and forgot it; since then, I have been trying to remember it or crack it.

The script "AMITSEDecrypt.py" script gave me a wrong password: "hƸG2f".
I also have a question: Is the BIOS password case-sensitive, or are all letters automatically converted to lowercase/uppercase?

I just give you the other solution...and yes the BIOS passwords are case sensitive.

[TraJikar Mac]

hoaca388 is right, the best and (almost) 100% safe method to remove the password is to read the BIOS with a programmer (twice is better and compare the readings to be sure they are the same).
In your case I try to remove the password from the dump you have provided. Try to write it and check for the Admin password if it's been removed. Provide feedback.

the screen in the image below showed up after i installed the patched version you provided using this command line:
.\AFUWINx64.exe G712LWS_patched.rom RECOVERY /B /N REBOOT

and it retained for like 2 to 3 minutes and then the device booted by itself to windows, but the password still exist.
also the AFUWIN GUI kept giving me errors, so i used the terminal instead, errors like 18 and 32, (unable to read sectors or something)

[Stefan Steff]

the screen in the image below showed up after i installed the patched version you provided using this command line:
.\AFUWINx64.exe G712LWS_patched.rom RECOVERY /B /N REBOOT

and it retained for like 2 to 3 minutes and then the device booted by itself to windows, but the password still exist.
also the AFUWIN GUI kept giving me errors, so i used the terminal instead, errors like 18 and 32, (unable to read sectors or something)

...and did you try the presented recovery method ?
I downloaded your recovery file, so copy it to the root of a USB stick and reboot your laptop.
At least we try to unlock your device. If you will manage to read the BIOS flash with a programmer then are more chances to reset your forgotten password...

[TraJikar Mac]

...and did you try the presented recovery method ?
I downloaded your recovery file, so copy it to the root of a USB stick and reboot your laptop.
At least we try to unlock your device. If you will manage to read the BIOS flash with a programmer then are more chances to reset your forgotten password...

Yes, I tried it multiple times with different USB formats (NTFS and FAT32), but nothing happened. The same screen showed up until it disappeared, and the computer booted back to Windows again.
If I buy a programmer, will I inadvertently harm my device, or does it handle errors safely? Like, can it read the actual password without replacing the firmware, or will I have to modify it?
(I watched some YouTube videos about the flasher "ch341a", but I found it hard to understand)

[Stefan Steff]

Yes, I tried it multiple times with different USB formats (NTFS and FAT32), but nothing happened. The same screen showed up until it disappeared, and the computer booted back to Windows again.
If I buy a programmer, will I inadvertently harm my device, or does it handle errors safely? Like, can it read the actual password without replacing the firmware, or will I have to modify it?
(I watched some YouTube videos about the flasher "ch341a", but I found it hard to understand)

Did you rename your file on the FAT32 formatted USB stick to G712LWS.BIN ? If not, rename it and try again...
It's possible to plug the usb to your laptop. turn on laptop and quickly press CTRL+HOME and wait... it should boot to EZflash bios and reupdate it.
Try with an older version...rename the bios file to .BIN - put in the root of USB stick - press-power on - then press CTRL+HOME.

[TraJikar Mac]

Did you rename your file on the FAT32 formatted USB stick to G712LWS.BIN ? If not, rename it and try again...
It's possible to plug the usb to your laptop. turn on laptop and quickly press CTRL+HOME and wait... it should boot to EZflash bios and reupdate it.
Try with an older version...rename the bios file to .BIN - put in the root of USB stick - press-power on - then press CTRL+HOME.

It doesn't even want to boot anymore, is it dead?
I'm freaking terrified right now. 🙁

[TraJikar Mac]

It doesn't even want to boot anymore, is it dead?
I'm freaking terrified right now. 🙁

It somehow turned on, but only the keyboard lights, and then nothing happens. It doesn't boot neither to BIOS nor to windows nor to USB.
Just nothing.

[Stefan Steff]

It somehow turned on, but only the keyboard lights, and then nothing happens. It doesn't boot neither to BIOS nor to windows nor to USB.
Just nothing.

Take out your battery and your power adapter and do a CMOS reset by holding power on button for at least 30 seconds.
...or take out the CMOS battery after removing the back cover and reinsert it after 30 seconds.
The USB restore method worked fine on another ASUS models...it's the same on Rog.
So after all it seems you get to read your BIOS with a programmer.
See here: https://www.youtube.com/watch?v=DWWigscuQDY

[Holaa321]

Here

Thank you after flashing it worked like a charm. Many thanks.

[TraJikar Mac]

Take out your battery and your power adapter and do a CMOS reset by holding power on button for at least 30 seconds.
...or take out the CMOS battery after removing the back cover and reinsert it after 30 seconds.
The USB restore method worked fine on another ASUS models...it's the same on Rog.
So after all it seems you get to read your BIOS with a programmer.
See here: https://www.youtube.com/watch?v=DWWigscuQDY

It didn't work for me, i tried all possible solutions, (Ctrl + Home) and (Fn + Esc), also tried to discharge it (for 30s and more), and nothing happens, i guess ill go buy a programmer or taking it to a repair service, I'll type a feedback about what happens later.

[TraJikar Mac]

Take out your battery and your power adapter and do a CMOS reset by holding power on button for at least 30 seconds.
...or take out the CMOS battery after removing the back cover and reinsert it after 30 seconds.
The USB restore method worked fine on another ASUS models...it's the same on Rog.
So after all it seems you get to read your BIOS with a programmer.
See here: https://www.youtube.com/watch?v=DWWigscuQDY

I bought an SPI programmer (CH341A), and below is the backup file I got from the BIOS (Yes, I watched many videos, and checked that the tool is connected correctly and can detect the BIOS and all backup file's md5 value was the same).

I tried to write the Asus manufacturer file to the BIOS but I got this error:

AsProgrammer v2.1.2
https://github.com/nofeletru/UsbAsp-flash
Current programmer: CH341
ID(9F): EF6014
ID(90): EF13
ID(AB): 13
ID(15): 0000
Current programmer: CH341
8:04:57 PM
Reading memory...
Done
Execution time: 12:00:09 AM
CRC32 = 0xB1397417
Current programmer: CH341
Old SREG: 00000000(0x00)
New SREG: 00000000(0x00)
Current programmer: CH341
8:05:30 PM
Erasing memory...
The process can take more than a minute on large flash!
Done
Execution time: 12:00:00 AM
Current programmer: CH341
8:05:31 PM
File size larger than IC size


I don't get it, how could 16mb BIOS file turn into 1mb BIOS file??


One more thing, after I tried to write that original BIOS file into the BIOS, there are no backup files that their md5 equal to each other anymore. So, luckily I am I made a backup file once it was connected to the PC I'm working on right now, I guess?


EDIT:
If I tried to write the backup file back to the BIOS, I get the following error:

8:18:00 PM
Programming memory (with verification)...
Verification error on address: 00000000
Execution time: 12:00:00 AM

[Stefan Steff]

I bought an SPI programmer (CH341A), and below is the backup file I got from the BIOS (Yes, I watched many videos, and checked that the tool is connected correctly and can detect the BIOS and all backup file's md5 value was the same).

I tried to write the Asus manufacturer file to the BIOS but I got this error:

AsProgrammer v2.1.2
https://github.com/nofeletru/UsbAsp-flash
Current programmer: CH341
ID(9F): EF6014
ID(90): EF13
ID(AB): 13
ID(15): 0000
Current programmer: CH341
8:04:57 PM
Reading memory...
Done
Execution time: 12:00:09 AM
CRC32 = 0xB1397417
Current programmer: CH341
Old SREG: 00000000(0x00)
New SREG: 00000000(0x00)
Current programmer: CH341
8:05:30 PM
Erasing memory...
The process can take more than a minute on large flash!
Done
Execution time: 12:00:00 AM
Current programmer: CH341
8:05:31 PM
File size larger than IC size


I don't get it, how could 16mb BIOS file turn into 1mb BIOS file??


One more thing, after I tried to write that original BIOS file into the BIOS, there are no backup files that their md5 equal to each other anymore. So, luckily I am I made a backup file once it was connected to the PC I'm working on right now, I guess?


EDIT:
If I tried to write the backup file back to the BIOS, I get the following error:

8:18:00 PM
Programming memory (with verification)...
Verification error on address: 00000000
Execution time: 12:00:00 AM

You have read the wrong chip...look for a MX25L12873F I think (U2802???)...a 16MB (128Mb) chip and read that one.
I don't remember that you have posted your serial number , please provide the serial of your laptop.

[TraJikar Mac]

You have read the wrong chip...look for a MX25L12873F I think (U2802???)...a 16MB (128Mb) chip and read that one.
I don't remember that you have posted your serial number , please provide the serial of your laptop.

G712LWS-EV002-Gaming
SN: L7NRKD031177304
CN: 778L
MFD: 2020-07


Thank you bro you take from your time helping me. 🙏🏻

[Stefan Steff]

G712LWS-EV002-Gaming
SN: L7NRKD031177304
CN: 778L
MFD: 2020-07


Thank you bro you take from your time helping me. 🙏🏻

Of course...we make it work again (I hope if I can't somebody smarter will help you out...)

[TraJikar Mac]

Of course...we make it work again (I hope if I can't somebody smarter will help you out...)

isnt it this chip?
there isn't any other chip on the motherboard that the clip can stick on except this one in the image, also the programmer detected it automatically.


WINBOND 25Q80EWNI15 2015

[Stefan Steff]

isnt it this chip?
there isn't any other chip on the motherboard that the clip can stick on except this one in the image, also the programmer detected it automatically.


WINBOND 25Q80EWNI15 2015

No, No...must be something like 25Q128JV or FV...anyway '128' must be in the name of the chip.
Look on the other side too

[TraJikar Mac]

No, No...must be something like 25Q128JV or FV...anyway '128' must be in the name of the chip.
Look on the other side too

is it this one?

and another question, if the flashing succeeded, after turning on the device, will the other chip recover its code? because its erased automatically when i tried to write that BIOS file into it.

EDIT:
I have 3 valid backups with the same md5 value that I extracted from the chip "WINBOND 25Q80EWNI15 2015" today, but the chip doesn't accept to flash any of them.

[TraJikar Mac]

is it this one?

and another question, if the flashing succeeded, after turning on the device, will the other chip recover its code? because its erased automatically when i tried to write that BIOS file into it.

EDIT:
I have 3 valid backups with the same md5 value that I extracted from the chip "WINBOND 25Q80EWNI15 2015" today, but the chip doesn't accept to flash any of them.

Last update:
After I have made tens of researches,
1: I figured out that the WINBOND chip needs an adapter (1.8v) plugged into the ch341a programmer to be able to write on it without problems (luckily I'm it is not broken because of the many times i tried to write back the backup images into it).

2: Later I decided to connect the bios into the flasher, and i took many backups (see the attachment file), they were all with the same md5 value.

Problems I faced:
- Firstly, the flasher couldn't read the real name of the bios chip, but a one the is really close to it, and from the internet, some people faced the same problem and flashed on the different bios name and the claim that they succeeded.
- - I found the reason that was causing this problem and how to fix it.... It was the USB port of the laptop that i plugged the flasher into it, and I fixed it by connecting into a hub that uses its own power supply charger (Ugreen hub 7 ports), and then plugged the hub into laptop's USB port and (NeoProgrammer) was able to get the exact name of the BIOS. OR the clip might not be plugged correctly on the chip, so make sure you try many times before you decide to plug the flasher into, i.e. a usb hub or external power source ==> BTW, this tip was from ChatGPT o4-mini-high

- I also learned that before you try to write any rom/bin/firmware image, you have to click on READ and then VERIFY to make sure that the flasher you use will not fail while its trying to inject/install the firmware image, so you know that you are using the right adaptor or working flasher (not broken).

- from some videos i watched, modifying the flasher may lead to install modified firmware images that gets modified during the installation process. (so don't modify the flasher you bought, just make sure that you are using the right adaptor for the chip you want to flash, and connect it to the adaptor, and connect/plugin the adaptor into the flasher). ==> here I'm talking about CH341A Black flasher cases.

-------

- I need someone to that know how to modify the manufacturer bios file so it's size become equal to one of the backup files' size. I'll be very thankful for who can help me doing this, as I don't know how to do it.

Thanks in advance.

[Stefan Steff]

Last update:
After I have made tens of researches,
1: I figured out that the WINBOND chip needs an adapter (1.8v) plugged into the ch341a programmer to be able to write on it without problems (luckily I'm it is not broken because of the many times i tried to write back the backup images into it).

2: Later I decided to connect the bios into the flasher, and i took many backups (see the attachment file), they were all with the same md5 value.

Problems I faced:
- Firstly, the flasher couldn't read the real name of the bios chip, but a one the is really close to it, and from the internet, some people faced the same problem and flashed on the different bios name and the claim that they succeeded.
- - I found the reason that was causing this problem and how to fix it.... It was the USB port of the laptop that i plugged the flasher into it, and I fixed it by connecting into a hub that uses its own power supply charger (Ugreen hub 7 ports), and then plugged the hub into laptop's USB port and (NeoProgrammer) was able to get the exact name of the BIOS. OR the clip might not be plugged correctly on the chip, so make sure you try many times before you decide to plug the flasher into, i.e. a usb hub or external power source ==> BTW, this tip was from ChatGPT o4-mini-high

- I also learned that before you try to write any rom/bin/firmware image, you have to click on READ and then VERIFY to make sure that the flasher you use will not fail while its trying to inject/install the firmware image, so you know that you are using the right adaptor or working flasher (not broken).

- from some videos i watched, modifying the flasher may lead to install modified firmware images that gets modified during the installation process. (so don't modify the flasher you bought, just make sure that you are using the right adaptor for the chip you want to flash, and connect it to the adaptor, and connect/plugin the adaptor into the flasher). ==> here I'm talking about CH341A Black flasher cases.

-------

- I need someone to that know how to modify the manufacturer bios file so it's size become equal to one of the backup files' size. I'll be very thankful for who can help me doing this, as I don't know how to do it.

Thanks in advance.

This is your rebuilded bios.
Provide feedback .

[TraJikar Mac]

This is your rebuilded bios.
Provide feedback .

- Flash => Complete
- Verification = Complete
- Read & Verify after flash => Complete

- Verify flashed backups' md5 value => complete => 3 backups with the same md5 value

Before installing:
C:\Users\HP\Downloads\BIOS>certutil -hashfile New_BIOS.bin md5
MD5 hash of New_BIOS.bin:
1af147638b8bb5a3309729288a743e69
CertUtil: -hashfile command completed successfully.

After installing:
C:\Users\HP\Downloads\BIOS>certutil -hashfile New_BIOS_backup.bin md5
MD5 hash of New_BIOS_backup.bin:
1af147638b8bb5a3309729288a743e69
CertUtil: -hashfile command completed successfully.


The result after turning on the device will have to be delayed for a few hours until the morning comes and i go buy an adapter for the flasher to burn one of the backup files to the other chip that i erased yesterday.

Thanks for taking from your time to help me. I also hope that you could rebuilding the firmware image correctly from the first time.