Acer Extensa 5635G hi all. I appeal to you asking for advice on how to load the modified bios in dos to acer laptop extensa 5635g. trying ph161700 /X /FORCE /O /C /S ZK6_3311.BIN - error message "Invalid FlashInt.BIN". for any help in advance thank you very much.
WARNING ??? Remove any LOADER, PATCH or CRACKS Bebore flashing the modded BIOS ??? --------------------------------------------------------------------------- IMPORTANT QUESTION TO THOSE WHO MOD BIOS : PLEASE HELP ME !!!!! --------------------------------------------------------------------------- This is a very simple question. In many modded BIOS archived file you provide, in addition of the modded BIOS, the Tools, and Instructions... One of the first instructions' step is: <<< ... Remove any - LOADER, PATCH or CRACK - BEFORE flashing the modded BIOS... it is very important... >>> I want ot know WHY IT IS SO IMPORTANT .... could it cause the bios flashing process to fail and kill the laptop ??? Or more worst ... the flashing process (of the modded bios) succeed with updated SLICv2.1 however the presence of the loader could lead to problems in the long term... ???
The loader could interfere with the slic in bios, or other issues not allowing the OS to boot. A slic bios is generally not advised with a loade4r and vise versa
The original name is ZK6_3311. the error reported by the modified and even the original BIOS. Flash BIOS slic 2.1 from the windows is ok, but the shows SLIC toolkit v3.2 Dump Error! (SLIC Table Not found!). I was recommended flash from dos, but that I unfortunately can not.
- Each BIOS as its own trick and instructions that comes with it. Instructions are your best friend. - However I use the same flash tool ph161700.exe. - In my case the BIOS is a Phoenix. The laptop is a HP Pavilion dv9700t series. In my case the command I should type to flash is : ph161700.exe bios.wph /o /force /x /c /s construction is: flashtool_name[]bios_name[]/token1[]/token2[]/token3[].../token(i) ...where "[]" represent a space. Your construction looks weird to me! 1) you place the tokens sequence after the flashtool_name. It should be placed after the bios_name. 2) there should be no space "[]" between "/"and the token. (look at my example). 3) You should be sure to know how to treat the bios name and its extension. In my case (again check with your instructions) the original bios name is "30CCF59.wph". Then I should rename it "bios.wph". If the extension would have been ".rom" or ".bin" then I will have end up with "bios.rom" or "bios.bin" respectively. hope this help
Tx for the reply.... I decided to flash the bios this week. I do read the instructions. In my mind there was no issue with loaders since I was sure to have removed them before removing win7 last january...(long story) Flashing was successful! I checked with Everest and the SLIC_Tool v3.0. Both show the new SLICv2.1 It's only the day after flashing that I begin to question myself. I was not so sure anymore! So in light of this info... Do you still believe that there can be a "sleeping" threat lerking around and ready to wake up one day even if the SLIC_Tool show successful SLIC2.1 installation (green light for both [Validated] & [Cert. OK] )??? sorry to not have been more clever with my question earlier thanks!