Clear cmos and load defaults after flash..It isnt the slic, it is the insertion.. Be sure that this asrock has recovery options, most do not... You may have to flash the bootblock, depending where the slic is oriented.. Core 0700 AMI are difficult to mod for SLIC...
Thanks 911medic , I decided to try AMI SSV3 with default settings *I have flashed and tested the original bios *Then added my own bios OEM logo using ASUS MyLogo to that bios and it worked fine Do you recommend applying AMI tool SSV3 mod before or after modifying my oem logo? I have tested the tool on a clean bios and one with the modified logo and both were "success" and compared both modded bioses on MMTools , the 1B was on the same rom location on both cases , however the "OEM Logo" module was in a different position. I think that question popped since reading the AMI tool log , it was doing some "padding" and since the new oem logo size is smaller , i feared it might affect locations or sizes of other modules during the modding By the way, sometimes the AMI tool opens MMTool in a wierd way which makes 1B insertion a failure and sometimes it starts writing C:/..... in the module ID instead of the module file which also fails , i tested it several times and these happen randomly with the same default settings and bios Thanks again for the advice
Hi I have mod my MSI AMI Bios and it work nearly fine. Every start up the error is CMOS CHECKSUM BAD but if i load default it works and the windows 7 is activated. I used the AMI SLIC Mod v1.47 and al lookes fine there. and SLIC ToolKit V3.0 also looks fine. Clear the battery but it not helps. Slic 2.1 in NVRAM. Someone that can help me please?
Hi again, Hello and thank You for your help... This time, I flashed the BIOS by following this procedure : 1.) flash the BIOS (including the Boot Block) 2.) turn off the computer 3.) unplug the power cord 4.) remove the CMOS battery (and wait a few seconds) 5.) put the CMOS battery back 6.) plug the power cord in 7.) turn on the computer 8.) load the default settings in BIOS setup (then save and exit) 9.) reboot the computer... But I still don't get any SLIC... Is there another way/method to mod this BIOS ? Another thing that I can try ? Thanks for your time !
Feedback tested SSV3/MMtools with SLIC 2.1 and it worked then added my logo and it worked tho i'm not sure why i'm still tempted to try out the dynamic mod anyways it was an asus maximus formula mobo with bios 1403 using asus slic included
Not to be redundant but are you sure you flashed the bootblock? Did you use all the switches with ASRFLASH...I do not know what they are, but you should be able to find them by just typing the asrflash from dos prompt..
Hello 911medic, Yes, the boot block was really flashed and it includes the SLIC ! Here are some informations about the "ASRFLASH.EXE" that I use : Its real name is "AMIFLASH.EXE", ASRock probably just renames the file... So, it's the AMI Flash Utility (8.27.44) named -Flash EPROM Programming Utility- in the help screen. Only four commands are available : 1.) /? or /H to display the help/command screen 2.) /B to enable the boot block programming 3.) /-B to disable the boot block programming 4.) /Sfilename to save the BIOS into a file named "filename" I flashed your modified BIOS with the /B command (a:\asrflash k7vt2_1.383 /B) I also made a backup of this BIOS with the /S parameter. The backup is identical to your modded BIOS I used for flashing, only some values about the hardware are added to the NVRAM zone. Do You think a newer version of the AMI Flash Utility will change something ? (Even if the boot block is already correctly updated...) What do You think about to insert the SLIC in the NVRAM zone ? (As, from the backup, only a short part of this area is used by datas.) Thanks once again !
Hi again, If I dump the BIOS after the flash and open the file in WinHex, I find this (the boot block is from offset 3C000 to offset 3FFFF) : Code: 0003F800 53 4C 49 43 76 01 00 00 01 6B 5F 41 53 55 53 5F SLICv....k_ASUS_ 0003F810 4E 6F 74 65 62 6F 6F 6B 27 08 09 20 4D 53 46 54 Notebook'.. MSFT 0003F820 97 00 00 00 00 00 00 00 9C 00 00 00 06 02 00 00 —.......œ....... 0003F830 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 .$..RSA1........ 0003F840 83 A4 C2 5B 5A 18 2A FE 79 59 DB D9 7E EA 3D 26 ƒ¤Â[Z.*þyYÛÙ~ê=& 0003F850 20 88 CE 6B D0 EA 79 D3 85 2B 95 00 9A C4 55 BF ˆÎkÐêyÓ…+•.šÄU¿ 0003F860 EA 39 A0 8F BE 23 61 59 60 73 C8 2C 5B E5 A8 8A ê9*¾#aY`sÈ,[娊 0003F870 7F 74 F5 BF CB 00 2D 99 76 AB 94 8C E3 CF 9E 47 tõ¿Ë.-™v«”ŒãÏžG 0003F880 28 61 91 B2 B5 F8 C8 DB D9 87 04 8A 48 EB 9B 7F (a‘²µøÈÛÙ‡.ŠHë› 0003F890 B3 38 0A FB 6F DD 86 75 A5 42 49 33 E2 2E 39 BE ³8.ûo݆u¥BI3â.9¾ 0003F8A0 64 8E 49 7D 78 DD 83 36 62 88 67 02 77 79 AF 3B dŽI}x݃6bˆg.wy¯; 0003F8B0 2F D4 04 53 F9 0E DA C5 38 F5 4B 7F 9C 69 63 B1 /Ô.Sù.ÚÅ8õKœic± 0003F8C0 01 00 00 00 B6 00 00 00 00 00 02 00 5F 41 53 55 ....¶......._ASU 0003F8D0 53 5F 4E 6F 74 65 62 6F 6F 6B 57 49 4E 44 4F 57 S_NotebookWINDOW 0003F8E0 53 20 01 00 02 00 00 00 00 00 00 00 00 00 00 00 S .............. 0003F8F0 00 00 00 00 00 00 9E D5 31 E9 0B 0F 73 70 D1 14 ......žÕ1é..spÑ. 0003F900 24 5D 8E 2C 20 5C 93 CF C6 6A EE 30 93 12 AA 53 $]Ž, \“ÏÆjî0“.ªS 0003F910 BA 3B 8F BE 76 9A ED AD 91 F3 7E 5E 31 01 F6 A3 º;¾vší*‘ó~^1.ö£ 0003F920 B2 E8 28 B5 20 F4 DE 57 92 E4 51 42 0D 94 E3 D8 ²è(µ ôÞW’äQB.”ãØ 0003F930 33 50 8D E5 66 D2 47 94 AA 57 B7 CB C2 9A 6E B1 3PåfÒG”ªW·Ëšn± 0003F940 9D 71 24 AD 33 0D 3C A8 26 71 3D B9 14 AA 1F A1 q$*3.<¨&q=¹.ª.¡ 0003F950 05 1A 8A FB 63 E6 DD 7F 98 E2 5B E1 6B 8E 47 E1 ..Šûcæݘâ[ákŽGá 0003F960 F7 18 12 B1 7E 50 B3 71 05 A7 EF 12 9E C7 09 AD ÷..±~P³q.§ï.žÇ.* 0003F970 29 46 DD 75 52 E2 89 00 00 00 00 00 00 00 00 00 )FÝuRâ‰......... So, I suppose that the boot block has successfully been flashed, right ?