@lordkag

Zitat von lordkag im Beitrag #30

---

@@JSebastian

Do you also get all those unknown sections with the original K55A.bin? The security check happens in WinFlash.exe and I think it can be by-passed with replacing first ja with jmp.

---

Zitat von lordkag im Beitrag #30

---

The first one is to try CodeRush's guide, which Fernando pointed. The /GAN command should be avoided, as it might not work with your laptop.

---

Zitat von lordkag im Beitrag #30

---

The second method is to use Intel FPT. Download the attached rar (many thanks to CodeRush for FTK, I just updated the components to 8.1.40.1456 and added metest+flash bat) and use the appropriate folder. First use spiinfo.bat and post the screenshot. Then use backup.bat or biosbck.bat and update the .bin file you obtained with UBU or MMTool, while keeping the same name. To flash the modded BIOS use the corresponding -flash.bat with the updated bin file. But it is better to wait and only report the outcome of spiinfo.bat, backup.bat and biosbck.bat

---

Zitat von lordkag im Beitrag #30

---

As stated before, it is your full responsibility how you use the files and information provided here.

---

@lordkag
Here's a screenshot of SPIINFO.BAT... How does it look???


Here's a shot of Backup.BAT (Top) & BIOSbck.BAT (Bottom):


Now, what do I do with the BIOSBCK.BIN file created??? Do I use that with UBU and modify it?

Spiinfo shows that your BIOS has standard semi-locked access. You have full access to BIOS and GbE regions, only read to descriptor - when using Intel FPT. This is good, since your only concern is BIOS region. You are now at the last step: either use the first method with afudos, or use this one with FPT to flash your modded BIOS.

I give this later method a slight edge, since you have an Intel chipset and AMI must have followed Intel guidelines. Before attempting any modding, flash back the file you obtained by using biosbck-flash.bat. This is to test that the flashing works and to rule out a bad flashing. Restart the system and check if everything is OK. Just a fair warning: while there shouldn't be any problems with flashing the backup bin, you just can't be 100% sure.

Use the biosbck.bin for modding with UBU or MMTool, keep the same name when saving. Place this modded biosbck.bin in the same folder you obtained it, by replacing the original one. Be sure to save the original biosbck.bin to a USB flash, also save the original BIOS file as K55A.bin and place it in the same USB. This is to have them for recovery.

Run biosbck-flash.bat with the modded biosbck.bin and restart, load BIOS defaults, shutdown. Have the power cord connected the whole time. If this works, we can move to drivers, device manager and other problems.

As a last warning, you must have the original hidden partitions your system had when bought; if the BIOS has its own checks for a secure image, it will attempt to flash a backup K55A.bin from one of those hidden EFI partition.

@lordkag

Zitat von lordkag im Beitrag #33

---

As a last warning, you must have the original hidden partitions your system had when bought; if the BIOS has its own checks for a secure image, it will attempt to flash a backup K55A.bin from one of those hidden EFI partition.

---

@lordkag
Hey one doubt, just to minimize any chance of an error... With MMTool I extracted the CSMCORE to verify the IRST OROM version... And its v11.0 ok... Now, is it ok if I update to v12.7 from UBU??? Or is it best to update with a same version series? Like using v11.6???

First thing first is to flash that original biosbck.bin to test the flasher. Then you can update only RAID OROM to 12.7 and test if the BIOS has checks embedded. Since the RAID OROM is not used, flashing this modded BIOS should have no problems. If it works, do again a biosbck.bat backup and check the version of Intel RAID. Lastly, update any components you like and do again a backup of this flashed BIOS to check if everything is updated.

I don't think Asus could have hardcoded a specific partition to be a recovery one. Rather than that, it should seek all partitions for a recovery K55A.bin. So, if you have that original hidden partition on any HDD/SSD, it will use it - if it has checks from the BIOS file itself.

@lordkag
Hey! I just flashed the original BIOSBCK.BIN using biosbck-flash.bat and everything went perfect! Forgot to take a screenshot, but it worked! I restarted, entered BIOS, F9 Optimized... Saved and Rebooted successfully into Win8.1... Now I updated the BIOSBCK.BIN with these mods: IRST OROM v11.6 and ONLY EFI GOP's ok... Nothing else... Is that ok??? Or should I just update the GOP's???
And is it ok if I only have the original K55A.BIN on C:\??? That's where it is on the OEM HDD but that also has it in the EFI partition or the Recovery partition... My current SSD doesn't have it on ANY partition... ONLY on the Root of C:\ where I put it...
Should I go ahead and Flash the modded BIOSBCK.BIN???

@Fernando @lordkag
I flashed the modded BIOS SUCCESSFULLY!!!!! I forgot to take a screenshot, but gimme a minute and I'll re-flash it to post my results... Thx a lot for all your help!!!! I'm truly grateful!!! Now, let's move on to the next step! I already updated ME 8 Firmware a while back... Can you guys help me Unlock the ME region? So I can have full access to ME functions??? Or completely unlocking my BIOS to have more features???
Should I do anything else now that I flashed the modded BIOS??? Like reinstall drivers or something for IRST and HD 4000???

@Fernando @lordkag
Here's a shot of the BIOS Mod success...

I did notice one possible side-affect... After the flash I entered the BIOS and loaded "Optimized Defaults" set my personal settings and rebooted... Right when it started to boot the CPU Cooling Fan revved up to I assume MAX RPM's and then slowed down to idle speeds... I immediately opened Aida64 and checked the sensor data... CPU Fan was at 4500 RPM's... Now it back to 2000 RPM's idle speed... Hopefully for some odd reason the Modded BIOS FIXED an issue I was having with the fan... It was always stuck between 2000 - 2100 RPM's no matter what I did... It sometimes revved up to 2400 RPM's or 2600 RPM's when running Aida64 CPU Benchmarks.... Now it seems to be working as it did when I bought my laptop... Cool Huh!!!!

I was curious as to another aspect of my BIOS... What SATA controller do I have? Do I even need one since its a laptop? What controls AHCI functions given I'm not RAID capable??? I'm going to update the IRST OROM agin to v12.7 or v12.9 I think is now available here...

Ok I see... So I'm pretty much set then! Other than wanting to access ME functions, I've done all I need to do...

@@JSebastian

For the updates:
- The Intel RAID OROM will not be used by your system, so you can do anything you want. You can use the "why not" principle, but you will have no use with it.
- The Realtek PXE and Realtek EFI LanDriver will be used only for Lan Boot, so it is again a case of doing your own way.
- The GOP drivers and Microcodes will have an immediate impact on your system, be it performance or only bug fixes. I haven't seen anyone complaining after updating those, so you will have only to gain. You will also get to fix a bug in the current microcode module, which has a padding after the first patch, thus preventing the other 3 patches to appear or work. With UBU you will have a good microcode module, with the latest patches for Sandy and Ivy CPUs.
- The VBIOSes have their use only when CSM is enabled. I have kept them to their original settings, so you have good chances of a successful update. I just can't vouch them with 100% safety.

For the ME region:
It is locked for your own good. You have a laptop with a low-mid range CPU. Even if you unlock your ME, you will at best gain 4% performance, but with terrible chances of ruining your laptop in the process. The ME can be unlocked by shorting a pin of the audio chipset and flashing a modded ME firmware. But again, why would YOU want to do that? What you can do is run metest.bat from the previous package and see if the ME firmware is OK.

For the BIOS "fealing":
- You seem to expect from UEFI a big leap. It is, when changing the paradigm from the monolithic legacy to a modular-complexity UEFI. But the user will only feel UEFI when using Secure Boot, Fast Boot, booting from an EFI Shell etc...
- I think you saw some awesome screenshots of an UEFI BIOS and expected to have the same, even though that was only for high-end desktop. Why should the manufacturer spend time and money on customizing a laptop BIOS, when most user won't even know what BIOS means?

For a complete unlocking:
- Download AMIBCP from here and open your original BIOS. Compare the options from there with the ones you see in your actual BIOS screen. Write down the missing ones, highlight the most important missing ones.
- Can it be done? Maybe: your Setup utility uses a lot of "Suppress If" statements, so it can be unlocked if you get the right variables. Is it worth it? Not for the modder, as he should spend his time (maybe hours, maybe less) with some unneeded settings; not for the user, as he could brick his laptop by changing something that was hidden for a reason.

@lordkag

Zitat von lordkag im Beitrag #44

---

@@JSebastian

For the updates:
- The Intel RAID OROM will not be used by your system, so you can do anything you want. You can use the "why not" principle, but you will have no use with it.
- The Realtek PXE and Realtek EFI LanDriver will be used only for Lan Boot, so it is again a case of doing your own way.
- The GOP drivers and Microcodes will have an immediate impact on your system, be it performance or only bug fixes. I haven't seen anyone complaining after updating those, so you will have only to gain. You will also get to fix a bug in the current microcode module, which has a padding after the first patch, thus preventing the other 3 patches to appear or work. With UBU you will have a good microcode module, with the latest patches for Sandy and Ivy CPUs.
- The VBIOSes have their use only when CSM is enabled. I have kept them to their original settings, so you have good chances of a successful update. I just can't vouch them with 100% safety.

---

Zitat von lordkag im Beitrag #44

---

For the ME region:
It is locked for your own good. You have a laptop with a low-mid range CPU. Even if you unlock your ME, you will at best gain 4% performance, but with terrible chances of ruining your laptop in the process. The ME can be unlocked by shorting a pin of the audio chipset and flashing a modded ME firmware. But again, why would YOU want to do that? What you can do is run metest.bat from the previous package and see if the ME firmware is OK.

---

Zitat von lordkag im Beitrag #44

---

For the BIOS "fealing":
- You seem to expect from UEFI a big leap. It is, when changing the paradigm from the monolithic legacy to a modular-complexity UEFI. But the user will only feel UEFI when using Secure Boot, Fast Boot, booting from an EFI Shell etc...
- I think you saw some awesome screenshots of an UEFI BIOS and expected to have the same, even though that was only for high-end desktop. Why should the manufacturer spend time and money on customizing a laptop BIOS, when most user won't even know what BIOS means?

---

Zitat von lordkag im Beitrag #44

---

For a complete unlocking:
- Download AMIBCP from here and open your original BIOS. Compare the options from there with the ones you see in your actual BIOS screen. Write down the missing ones, highlight the most important missing ones.
- Can it be done? Maybe: your Setup utility uses a lot of "Suppress If" statements, so it can be unlocked if you get the right variables. Is it worth it? Not for the modder, as he should spend his time (maybe hours, maybe less) with some unneeded settings; not for the user, as he could brick his laptop by changing something that was hidden for a reason.

---