[b][/b]
[i][/i]
[u][/u]
[s][/s]
[code][/code]
[quote][/quote]
[spoiler][/spoiler]
[url][/url]
[img][/img]
[video][/video]
Smileys
smile
smile2
spook
alien
zunge
rose
shy
clown
devil
death
flash
sick
heart
idee
frage
blush
smokin
mad
sad
wink
frown
crazy
grin
hmm
laugh
mund
oh
rolling_eyes
lil
oh2
shocked
cool
[mail][/mail]
[pre][/pre]
Farben
[rot][/rot]
[blau][/blau]
[gruen][/gruen]
[orange][/orange]
[lila][/lila]
[weiss][/weiss]
[schwarz][/schwarz]
quetzalin
Posts: 49 | Last online: 05.23.2017
Name
Miguel
Location
Spain
Date registered
06.20.2013
Sex
male
    • quetzalin has written a new post "Recovering the ME on a Fujitsu computer..." 12.26.2016

      Yes the new CPU i want to use is an Ivy Bridge while the old one was a SB. I will try to clean the ME region tomorrow then and leave it with v8 ME then, the greset i already tried but didn't work.

    • quetzalin has written a new post "Recovering the ME on a Fujitsu computer..." 12.26.2016

      I'm trying to figure if i can follow the process you described >here< about cleaning the DATA section of a dumped SPI image with the BIOSes i have and flashing it... ?

      Let's say i pick the firmware 7.0.10.1203_1.5MB_CPT_PRD_RGN.bin from the repository which matches the same ME firmware that comes with the D2990-A1.UPD bios rom and i dump it on FIT v7 to extract the ME Region.bin from it, then i dump the D2990-A3.UPD on FIT v??? and replace his ME Region.bin with the extracted one from the repository and then i build and flash with FPT... ?

      If this could help, which version of FIT should i use when i dump D2990-A3.UPD ?, v7 or v8?, i tried and it actually works with both without errors...

      What is the command line i should use to flash with FPT?, just FPT -f bios.bin and after FPT -greset ?

      Thanks again!

    • quetzalin has created the topic "Recovering the ME on a Fujitsu computer...". 12.26.2016

    • quetzalin has written a new post "Advices updating Intel ME 3 AMT Firmware" 12.22.2016

      Zitat von plutomaniac im Beitrag #5
      I cannot understand what you mean by "AMT tool".


      It's the utility coming with the motherboard that loads during boot, u can access to it if u press a combination of keys (Control+P) to configure MEI parameters.

      Looks like this one (not my capture):

    • quetzalin has written a new post "Advices updating Intel ME 3 AMT Firmware" 12.20.2016

      @plutomaniac I just flashed the MEI and it was successful but the AMT tool is still on the same version; v3.0.2.0004, i guess this is normal and it doesn't get updated with the ME firmware right?

    • quetzalin has written a new post "Modding and upgrading an ASUS P5E-VM DO bios" 12.20.2016

      I was finally able to flash my modded bioses and i succeeded with the next:

      Intel OROM updated to v10.1.0.1008 with TRIM support
      Intel Boot Agent updated to v1.5.43
      Intel VGA Rom updated to v1653
      JMicron PCIE-to-SATAII/IDE RAID Controller updated to v1.08.0

      And just for the record, the download link for the modded BIOS (based on the official version 0902) in case someone needs/wants it is >here<.

      Intel OROM v11.2.0.1527 didn't work, the computer gets stuck with a blank screen when it was supposed to load the OROM, no errors or anything.

    • quetzalin has written a new post "Advices updating Intel ME 3 AMT Firmware" 12.16.2016

      This is the ME firmware the BIOS comes with:

      1
      2
      3
      4
      5
      6
      7
      8
      9
      10
      11
      12
      13
       
      -------[ ME Analyzer v1.6.8 ]-------
      Database r73
       
      File: P5EVMDO.ROM
       
      Firmware: Intel ME
      Version: 3.0.2.1105
      Release: Production
      Type: Region, Extracted
      SKU: AMT
      Date: 26/06/2007
      Platform: Desktop
      Latest: No
       

    • quetzalin has created the topic "Advices updating Intel ME 3 AMT Firmware". 12.16.2016

    • quetzalin has written a new post "[Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS" 11.30.2016

      So, since flashing with AFU (AMI Aptio V) didn't work for me (i got an error about not enough memory when trying to flash with AFUDOS) i took the risk and tried with this method and it worked just fine.
      Very important to say i did exactly as it was described here by SoniX:
      1. First i flashed the BIOS with a pristine original latest version.
      2. Saved the bios with fpt -d bios.bin -bios
      3. Modded the bios with UEFITool (VBIOS) and UBU.
      4. Flashed with fpt -f mod_bios.bin -bios

      EDIT by Fernando: Unneeded fully quoted own post removed (to save space and for a better Forum performance)

    • quetzalin has written a new post "[Guide] How to flash a modded ASUS/ASRock/Gigabyte AMI UEFI BIOS" 11.28.2016

      Zitat von SoniX im Beitrag #72
      How to flash the BIOS mod Asrock motherboard with BIOS Aptio 5:
      1. Flash the original version of the BIOS.
      2. Use FPT Utility to make a backup of the Region BIOS.
        - example:

        1
         
        fpt -d bios.bin -bios
         

      3. Modified file "bios bin", for example in UBU or UEFITool, and save the changes as a "mod_bios.bin".
      4. Now, using the FPT, to flash the modified file.
        - example:

        1
         
        fpt -f mod_bios.bin -bios
         

      5. Reboot and Reset.

      Added:
      Why do we have to work with a backup?
      If you flash the original version of the BIOS, you can lose the unique data such as MAC, S/N and etc.
      @SoniX Is this method also valid for an ASUS B150 in case AFUDOS fails?, thanks.

      EDIT by Fernando: The code of the quoted text has been slightly customized (for a better understanding), unneeded parts and blank lines have been removed (to save space).

    • quetzalin has written a new post "[Discussion] UBU Tool related Questions, Reports and Suggestions" 11.28.2016

      Hello, i just updated the microcode on a ASUS B150M-A/M.2 and i got this:

      1
      2
      3
      4
      5
      6
      7
      8
      9
      10
      11
      12
      13
      14
      15
      16
      17
      18
      19
      20
      21
      22
      23
      24
       
      Checksum correct. Microcode not damaged.
      Checksum correct. Microcode not damaged.
      Generate FFS files Microcode
      Found 3 module(s).
      Remove "Empty" module.
      Update Microcode Patch...Ok!
      Update Microcode Patch...Ok!
      Restore "Empty" module...
      +-----------------------------------------------------------+
      |No| CPUID | Platform | Version | Date | Size Hex |
      +--+----------+----------+----------+------------+----------+
      |01| 000906E9 | 22 | 00000042 | 02-10-2016 | 00017800 |
      |02| 000506E3 | 36 | 000000A6 | 21-08-2016 | 00017C00 |
      +-----------------------------------------------------------+
      MPDT Boot - YES
      _FIT_ in GUID B52282EE-9B66-44B9-B1CF-7E5040F787C1
      01 mCode Adrress - FFD1C3F0
      02 mCode Adrress - FFD33BF0
      03 mCode Adrress - FFD4AFF0
       
      Attention!!!
      Check the Address in the _FIT_
      Address 01 mCode + Size 01 mCode = Address 02 mCode
      0xFFD1C3F0 + 0x00017800 = 0xFFD33BF0
       

      I assume i'm good to go, since the checksum (0xFFD33BF0) matches the 02 mCode Address right?

    • quetzalin has written a new post "Multiple Raid Arrays on the same set of HDD's" 11.22.2016

      Hello,

      You are actually wrong, you can create several different arrays on the same disks. For example, on a computer at work which has 2x WD 1TB Black; first i created a 200GB RAID0 and then all the remaining is on a RAID1. Then i partitioned the first array with two partitions (one is the boot partition and the other the system partition) and partitioned the second array in only one partition for file storage.

      This is on a Z170 motherboard tho, but im pretty sure what you want to do is achievable on a Z87 too, i even swear i did this on a old computer with an ICH8R controller.

    • quetzalin has written a new post "[INFO] About "modded" drivers and how to get them installed" 09.13.2016

      Is there any way to load the modded drivers during a Windows 10 setup?.

      If i hit the load controller and select a modded driver it obviously doesn't "find" any driver since they are not certificated with M$ certificates and i cant load your certificate during the setup :/

    • quetzalin has written a new post "ASUS P5Q PRO Turbo Intel Raid OROM Mod" 10.22.2015

      Zitat von Fernando im Beitrag #2
      The question is not, which is the latest available or the best Intel RAID ROM module. According to our BIOS Modding Success/Failure table (look >here<) you will probably not be able to get any Intel RAID ROM version working with your Asus P5Q series mainboard, which is newer (and bigger sized) than v10.1.0.1008.
      I was about to post new info since i have been testing.

      Yes, v11.2.0.1527 doesn't work. When the computer boots and needs to load the intel orom i get an error message about not enough space to load the rom bla bla. I tried with deleting the OEM Logo but still the same error, don't know if deleting other useless modules would help here, if so and is woth a try, any recommendation?.

      Later i tried modding with the v10.1.0.1008 since it has a similar size as the original MSM orom and it works.

Recipient
quetzalin
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor