Hi, does anyone know if it's safe to mod the new ASUS P8H67 BIOS 3506 (rel.date: 2012/03/07) with PTv1.96? Can I use the old RW-Report to mod the BIOS or do I need to create a new RW-Report with the new BIOS? Many thanks in advance
The Dynamic method is automatically suggested by the tool, I think because the BIOS has SLIC2.0 inside. I've modded now one BIOS with RW-Report and one without and the result are two BIOS with the same CRC. So why does the tool asks me, if I really wanna go on without a RW-Report, as it's not needed?
Yah... dummy AMI SLIC 2.0 R/W report is optional for most of the EFI's; but some others (Phoenix, Dell) need it. As this is an universal tool, so it incorporates the option of asking the user about r/w report.
Hi, Can the tool be used for modification HP ProBook 5330m bios (ver. F22) ? I heard there were problems with ProBook/EliteBook bioses. Guys from whitelist-removal threads concluded there is no an ability to patch modern probook/elitebook bioses at this moment. Also I would to know which patch should be applied to HP flashing utility in order to have moded bios flashing succeed? (and why the patch actually needed?) Also, what about a cryptography around these bioses? Should I know something important about that or tool handle it itself? Would be grateful for any help. Thank you, Chris
Encountering the same problem - file access to 'TEMP.MOD' denied (Phoenixtool196, DMI method) - on Win7/64 Ultimate SP1, disabling the AV for me was not the solution. Configuring all .EXEs in the Phoenixtool directory for "run this program as an administrator" (file properties / Compatibility) did solve the issue, though. And, by the way, my sincere thanks to AndyP for the great tool and of course to Tito and all the other unpaid advisers for their ongoing support!
hi, BIOS HOME member feedback, for asus mobo UEFI bios,some latest bios ver.3xxx don't use phoenixtool196/new module method to mod,when u flash to mobo sometime still don't have slic or seriously brick,be careful to use this method qtm