[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]
Vento
Posts: 20 | Last online: 01.10.2017
Location
Italy
Date registered
01.08.2015
Sex
male
    • Vento has written a new post "Winbond chips compatiblity - Naming rules" 10.10.2016

      Chips have arrived!!!.... aaaand.... They send me the wrong ones... 25Q64FVAIG instead of 25Q64FVAIQ...Guys, can you pls help me to find these chips somewhere in europe? Or at least from another store that isn't aliexpress.

    • From: AMI bios dumps differences


      I would like to update Intel RST OROM/EFI SataDriver and Intel microcode, are there some known compatibility issue? I've a Xeon E3-1231 v3 cpu, is there any possibility that "downgrading" my current haswell microcode from 19 (marked as "Best overclocking" inside UBU) to 7 (marked as "Last for non-K overclocking") could allow me to change the BCLK or the cpu ratio? I know that I've an H97 chipset, but I'm talking about this old article: https://www.techpowerup.com/202196/asus-enables-overclocking-on-h97-h87-b85-and-h81-series-motherboards

      Should I just switch to the latest microcode if the v7 will not work at all or not work as I intended?

      I've a Asus H97M-E motherboard btw.

    • Vento has written a new post "AMI bios dumps differences" 09.14.2016

      Yep the descriptor is locked, Intel Flash Image Tool does not work, the ME region is dumped correctly only by the flashrom-method, UBU can read the ME region properly only from that dump. Thank you for the fast reply.

      Zitat von plutomaniac im Beitrag #2
      ... Otherwise, update just the BIOS and use FWUpdate later on as you probably have already done based on the latest firmware found at your one working dump compared to ASUS stock SPI/BIOS. ...

      Also that's true :D

      Btw, some other questions:

      I would like to update Intel RST OROM/EFI SataDriver and Intel microcode, are there some known compatibility issue? I've a Xeon E3-1231 v3 cpu, is there any possibility that "downgrading" my current haswell microcode from 19 (marked as "Best overclocking" inside UBU) to 7 (marked as "Last for non-K overclocking") could allow me to change the BCLK or the cpu ratio? I know that I've an H97 chipset, but I'm talking about this old article: https://www.techpowerup.com/202196/asus-enables-overclocking-on-h97-h87-b85-and-h81-series-motherboards

    • Vento has created the topic "AMI bios dumps differences". 09.14.2016

    • Vento has written a new post "[Guide] Recover from failed BIOS flash using Raspberry PI" 01.13.2015

      Zitat von CodeRush im Beitrag #24
      ...
      3. The resulting image must have the exact size that the SPI chip has, so you need to stip the image down from any capsule headers and other stuff like this, if it's bigger. If, on the other hand, it's smaller for a megabyte or two - it's not a full image, but only a copy of BIOS region, and you need a full BIOS dump from the same board to reconstruct your full image.
      ...



      As CodeRush said, to recover my ultrabook (S56CM/K56CM from ASUS) I had to use my full dump! I've use fptw.exe in this simply way:

      1
       
      fptw.exe -D DUMP.ROM
       


      When you open it with UEFITool the result should look like this:
      Just look at the structure "Intel Image" (with BIOS region an some others), the numbers at the right may be different


      Keep in mind that your board may be totally different, without this structure and/or fptw.exe may not work. Again, follow CodeRush's words

      Zitat von CodeRush im Beitrag #24
      ...
      2. For Intel-based systems with a single SPI flash chip (there are some dual chip configurations, but they aren't popular) you need an image that starts with Descriptor region and has ME and BIOS regions. There can be additional GbE and PDR regions, but they aren't required.
      ...

    • Vento has written a new post "[Guide] Recover from failed BIOS flash using Raspberry PI" 01.13.2015

      And also, if you do not want to remove/replace your bios chip or solder wires directly on your motherboard (like I did, it was a pain), you can buy this: http://www.amazon.com/ZJchao-xFF08-socket-adpter-programmer/dp/B00HIBKVYO you can also find it for lower price :D

      This connectors do not work for every chip! Your chip may have different shape, dimension, pin... Find the correct clips for your chip.

      Some images: (click on the link to view more images and details)

    • Vento has written a new post "[Guide] Recover from failed BIOS flash using Raspberry PI" 01.12.2015

      Hi, I've done some experiments (ASUS S56CM / K56CM Bios Modding - I'm doing this right?) and I've used this fantastic guide to recover my bios. I have some changes to propose:

      Optional pre-pre-install:

      1
      2
      3
       
      #Maybe an update will be nice
      sudo apt-get update
      sudo apt-get upgrade
       



      Pre-install:

      1
       
      sudo apt-get install subversion pciutils-dev
       



      Flashrom install/update script:

      WARNING: This script create and delete a directory named "flashrom" form the directory where you use these commands. You have been warned! It's not my fault if you lose your only copy of the work of your life that you saved in your raspberry under a directory named "flashrom".

      1
      2
      3
      4
      5
      6
      7
      8
      9
      10
      11
      12
      13
      14
       
      #This command delete old flashrom sources downloaded in this directory from you or prevoius run of the script
      rm -rf ./flashrom
      #Download the last version of flashrom
      svn co svn://flashrom.org/flashrom/trunk flashrom
      #Go in the sources directory
      cd flashrom
      #Compile
      make
      #Install
      sudo make install
      #Return in the previous directory
      cd ..
      #Delete the sources directory
      rm -rf ./flashrom
       



      Before reading/writing the chip:

      1
       
      sudo flashrom -V -p linux_spi:dev=/dev/spidev0.0
       



      This command will only probe for flash chips, without read or write anything. In this way you will know the chip that you motherboard use.
      You can check the chips compatiblity here: http://flashrom.org/Supported_hardware

      But why I told you to use this command? flashrom work also without it... yes and no...

      If you know what chips you have you can add "-c <chipname>" when you read/write your chip.
      I've a "W25Q64.V" chip so my write command become:

      1
       
      sudo flashrom -w /tmp/1.rom -V -p linux_spi:dev=/dev/spidev0.0 -c W25Q64.V
       


      This also applies for read ("-r"), erese ("-E"), verify ("-v") and every other command that require to read or wirte the chip.

      So this is how, but why I shoould use this information?

      1) Is faster If you have to do this multiple times, flashrom will try to probe for chips only with the chip name given.
      2) I've experienced some problems. If I do not specify the chip name, the automatic verify after every write will return "fasle" expected value errors. Flashrom think that the write is gone wrong somewhere but actually it's ok. In fact if I verify ("-v" option instead of "-w") , after the write command (with "false" errors), it's everything ok.

      This command actually do not change anything, but will save you from "small heart attack" and question like "oh god why my raspberry won't write correctly? I've to trash my motherboard?"

      And also, this sounds very very to much, but if you have time you can follow my rule:
      - Completely shutdown the raspberry after every flashrom command. Just to be sure that there are no interferences/problems between a command and another.

    • Vento has written a new post "ASUS S56CM / K56CM Bios Modding - I'm doing this right?" 01.12.2015

      Here I am :D sorry for the dealy :D btw I've flashed a bad modded bios but I've successfuly recovered my PC (I'm using right now to write this post) with yours fantastic guide [Guide] Recover from failed BIOS flash using Raspberry PI Thanks to all those who contributed to that guide :D I've also found something that may be useful to future bios recovery :D (I'll post them later)

      Before attemptiong new flashes I'd like to know if there is a way to avoid soldering wires the bios chip? I do not want to waste 2/3 hours again (the chip is so small!!!!) just to solder 8 wires properly xD

    • Vento has written a new post "ASUS S56CM / K56CM Bios Modding - I'm doing this right?" 01.08.2015

      To Fernando :D

      Just to be sure, a fast way to include it in my BIOS should be to delete "2170.bin" file in this UBU folder "UBU_v190\Modules\VGA\", extract the "8086-0106_v2170.bin" from the archive and rename it in "2170.bin", and use UBU like always?

      Another question: If a use AMIBCP to change EVERY "Access/Use" collumns from "Default" to "USER" to unlock/show EVERY settings, can I cause some damage? I know that some settings won't work (like the bluetooht, i do not have it), so I leave them untuched. Again (as update #1) can this modification make some damage? The modification only, not the future/possible settings that I might use.

    • Vento has written a new post "ASUS S56CM / K56CM Bios Modding - I'm doing this right?" 01.08.2015

      Update #2 new questions XD see main post

    • Vento has written a new post "[Guide] Flashing modified AMI Aptio UEFI using AFU" 01.08.2015

      Maybe I'm doing something wrong but the AFU link do not work for me xD This sould be the correct one:

      AMIBIOS_and_Aptio_AMI_Firmware_Update_Utility.zip

      Make sure to use the correct .exe!

    • Vento has written a new post "ASUS S56CM / K56CM Bios Modding - I'm doing this right?" 01.08.2015

      Title: done :D

      Why I'm doing this?: I'm updating my hardware (new SSD and 7200 RPM HDD) and I'm a "lasest version and performance" maniac, also I'm very interested e curious about BIOS modification. I'm a IT Student and I like to discorver, hack and try new "IT things" since I was 8 (my first PC :D a Pentium 2)

      And... another question :D Yes I know that UBU is not designed for mobile system... I'd like to know why :D Whats the main difference between a desktop BIOS and a mobile one? Are there different values placed in different locations? Different srtucture? (I do not know I'm just making assumptions). Could a manual mod with the official AMI tools make a difference?

      EDIT by Fernando: Unneeded fully quoted text deleted (to save space within this thread)

    • Vento has created the topic "ASUS S56CM / K56CM Bios Modding - I'm doing this right?". 01.08.2015

Recipient
Vento
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor