[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]
RoadrunnerDB
Posts: 18 | Last online: 08.29.2017
Date registered
05.19.2015
Sex
male
Warnings
This member has been warned 1 times. (details).
X

Warnings

Warnings for user RoadrunnerDB
Last warning: 04.21.2017
Note: Because of the forum permissions maybe not all warnings will be shown.
If the member have5 warnings, he will be locked automatically.


Type Title Description
Post[Discussion] UBU Tool related Questions, Reports and SuggestionsThis post does not match the desired netiquette of the Forum.
    • RoadrunnerDB has written a new post "[Discussion] UBU Tool related Questions, Reports and Suggestions" 08.29.2017

      Zitat von 4o4TV im Beitrag #3157
      UBU is just Intel playground?
      No playground but also nothing for beginners or nothing for people who do not understand the basic knowledge.

      A few pictures as you can see the changes.
      Internal graphics Intel!
      Or also in bios Uefi setup!


      Windows start in Uefi "GOP"



      Windows normal start "VBios"



      Uefi setup





      Intel Managment Interface





      Bootscreen



      Bootscreen Raid



      Uefi Raid-Menü

      EDIT by Fernando: Quoting codes corrected and unneeded parts of the quoted text removed (to save space)

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

      @4o4TV

      Example, An Intel Platform!
      About the GOP version in the graphic properties.
      If Windows is active as UEFI start or in normal mode then Vbios version.
      In my Uefi surface I can see the CPU microcode, network "GigabitUndi" and Intel management interface.
      Of course, also in raid mode!

      If you're not sure, you can check out Everest (AIDA)
      continue watching.

      AMD is not my platform ...

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

      Hallo

      Which modules have been updated?

      In many Uefi bios interfaces, you will see certain modules.
      For example, the CPU microcode or the raid mode the version number.
      But not all modules!
      Read the rest with AIDA (Everest) via Windows ....

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

      OK thanks...
      But is no art to offer a file which is not compatible with UBU.
      I can also rename a file from FFS to EFI without modifying the header!

      It is nevertheless a UBU thread and not an Intel thread or?

      Pacman is also active on the stationdriver-side and there are here and
      there times files that are not always comfy of him.
      If he already postet in a UPU thread ... then also same comfy files for UBU ...
      Or immediately write the header must be removed so that it is compatible.

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

      Exactly this is the problem ... Thanks

      @ Pacman why do you offer things with header?
      Make it right without header!

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

      Nice that you think I would not have changed in the body.
      The 0.17 is faulty!
      Try it yourself ...
      If I in the ASRock Bios directly in bios a firmware over the Internet start, comes immediately a failure message.

      Just load your 0.17 in the UEFI tool and save it, then read your firmware again in the UEFI tool.
      (Signature error)

      @plutomaniac Pacman always offers times mist.
      This is nothing new with him!
      The 0.16 in UBU is fully functional!

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

      Zitat von Pacman im Beitrag #2904
      Intel Gigabit Lan UNDI 0.0.17


      parseSection: PE32 image with invalid DOS Signature
      See in (Screenshot1)

      Gigabit Lan UNDI 0.0.16
      Correctly is in ( Screenshot 2)

      The 0.17 is faulty and identical to the content to 0.16
      HEX editor

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

      @Pacman
      I know that an older version does not work!

      @Fernando
      Thank you have the version 1.49.4 itself found.

      Back to the topic!
      Have tested and found that it was my fault.
      Module exchange no instant flash possible.
      Sorry was all in August 2015!
      But a CPU microcode update works on UBU.
      Instant flash process successfully!
      This security check includes all modules ....
      CPU patch is excluded thereof!

      EDIT by Fernando: Unneeded blank lines removed (to save space)

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

      Fernando

      Do you have an older version? UBU

      Sorry for my bad English!

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

      @Pacman

      Which version was active in August 2015?

      The Slic tool does not work on ASRock Z170!
      The slic is written in an empty address area without knowing.
      ASRock has implanted no OEM Slic. Or Dummy ORM!
      In my old Z68 or Z77 a dummy Slic was always present.
      This was recognized by the Phoenix tool and replaced with a real Slic.

      Version less than 2.66 the BIOS is crashed.

      The "Gigabyte Z170" works is not important
      You have no real UEFI! You have a work based.

      Slic is my matter!
      It was only my knowledge ...
      The Phoenix security protection not changed.

      I will test it with UBU 1.50 and will report!
      I need an older version of UBU where no security check is removed.
      Have the old versions deleted....


      who has an older version?

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

      Fernando I know that!

      Decentralization is the magic word!
      "UBU" for AMI Aptio IV and "UBU" with "UEFI-TOOL" for AMI Aptio V
      Motherboard!
      The Orom address areas in all Z170 motherboards are identical.
      AMD I would not touch it!

      Area:
      Raid-rom GUID = D46346CA-82A1-4CDE-9546-77C86F893888
      VBIOS GUID = C5A4306E-E247-4ECD-A9D8-5B1985D3DCDA
      BootAgentCL GUID = 50339D20-C90A-4BB2-9AFF-D8A11B23BC15
      ASUS, ASROCK, MSI and GIGABYTE!

      Furthermore, AMI Aptio IV is no longer just asked about long.

      Yet what the info!
      A removal-of the board battery caused on Z170 deletion of MAC address.
      In case of power interruption and battery removal-!

      It must be installed by a manufacturer software the Mac by Dos surface.

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

      A question?

      Why is enabled in "UBU" no "Orom" update.
      X99 and Z170 boards need to be updated to "UEFI-TOOL" manually by hand.
      One need not a "UBU" anyway because 50% of the modules on
      "UEFI-TOOL 'must be made.
      Why a routine is not part of "UBU"?

      The manual processing of "VBIOS" must be done with the known guide in the forum.

      These instructions are completely unusable because the Intel Content protection is thus destroyed.
      I start in "VBIOS" there is no sound on "HDMI DP DVI"!
      If you start in "GOP UEFI" there are no problems.
      The is also correct because "EFI GOP" does not have to be adjusted manually.

      I always have to compare an original intel "VBIOS" with my mainboard "VBIOS".
      This I always do with "HEX EDITOR" because the original intel "VBIOS" must be adapted to the graphic connections.

      The address range to remove the security check is quite large since a large area is cleared with "FF".
      Why is the area changed from ".." in "FF"?

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

      I bought the board in August 2015 because I noticed the "ASROCK" has implanted a new security check.

      I wanted to flash the "ROM" with "Slic tool" and then finish the "ROM" on "UBU".
      It did not work so I went on troubleshooting!

      I then only the "SLIC-TOOL" used. The "INSTANT-FLASH" process worked.
      So is the culprit "UBU"!

      Now I have changed every single "module" ...
      So only "EFI ROM Raid" then stored and worked on "INSTANT-FLASH".
      Then again the edited "Rome" change in "UBU" to the "EFI GOP" again saved and tries error about "INSTANT-FLASH".

      I then looked over the "UEFI-TOOL" to any entries.
      but then I gave up!

      I bought a "USB PROGRAMMER" with "DIP SOCKETS" and described the "BIOS" with it!
      Read some point here about "AFU" and use the method!

      It is the fakt "ASROCK" generates the checksum of the modules and "lordkag" has the address space found.
      Congratulations!

      The charade of "ASROCK" should be left.
      Who "BIOS" destroyed his own fault as are warranty provisions.

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

      Sorry for my bad english ... google help

      It is not necessary to use "AFU"!
      A "Clear CMOS" is not necessary!

      "UBU" does not change the security check when no modules are exchanged.

      Load original "BIOS" in "UBU" and removed the security check.
      Then the "BIOS" save without further changes, restore the original name of "BIOS" again.

      Flash the "BIOS" on "INSTANT FLASH" finished.
      Now should any new "BIOS" are previously read about "UBU" so that the security check is not written back into the "BIOS".

      Now you can easily integrate the "BIOS" in "UBU" and replace the modules.

      The people of "ASROCK" use a tool to this security check by the "BIOS" completion so to decorate ...
      I find it to be unnecessary especially if you have a dual "BIOS" on the Main board.

      I have the motherboard "Z170Extreme4" ...
      versions tested with different "BIOS".

      If "ASROCK" the address space do not change it should work on life ..

      I find "ASROCK" should make it exactly like "GIGABYTE"!
      An entry in the BIOS interface so the user can determine whether the security check activated or deactivated.

      Thanks!

    • RoadrunnerDB has written a new post "Intel Me firmware 1173 1.5MB Problem" 09.18.2015

      How do i get now the 1173 flashed?
      My version 1168 i saved as "Old.bin" on
      "fwupd -save old.bin"!
      This is then 1.38MB, you can then without problems
      "fwupd -f -allowsv" make a reflash!

      Now if i want to update the 1173 comes an error message.
      What am i doing wrong?
      Had previously Z77, since no problems!

      Z170 with it has become more difficult!

      You must not forget that all Z170/X99 must be signed bios!
      Without signing it just goes over Aptio5 "afudos"!
      Fortunately, my mainboard on Dos flash signing is not active!
      Intel ME clutching the entire BIOS.
      An error and HDMI rights are in the bucket.

      Slowly I curse this ME technology ....

      The consumer electronics comes massively to the back door!

      Soon we are no longer our own king on PC!
      Microsoft wants to dominate us

      Sorry my english is real shit

    • RoadrunnerDB has created the topic "Intel Me firmware 1173 1.5MB Problem". 09.18.2015

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

      sorry for my bad English!

      My Mainboard is ASROCK Z170 EXTREME 4 Skylake!
      Some bugs in UBU1.36 ...Here are a few Screenshoots!











      After each storing the checksum is rotated, so that a flash the Bios is impossible with ASUS, Gigabyte, etc.

      AmiAPTIO (V) no Orom support!
      Why?


      EDIT by Fernando: Post moved into the correct UBU Discussion thread (the other one is reserved for the UBU guide and the announcements of a new UBU version).

Recipient
RoadrunnerDB
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor