Acer Aspire 4752G Failed BIOS Flash, Black Screen EFI/INSYDE BIOS

Options
arvindnavaratna
arvindnavaratna Member Posts: 2 New User
edited March 2023 in 2017 Archives

Hello Everyone.

I have an Acer Aspire 4752G Laptop (Intel Core i5-2370M, nVidia GT610M, RAM 6GB) which unable to boot after a failed BIOS flash, the power is on, but there's no display on the screen. I was trying to install the latest BIOS version from Acer BIOS_Acer_2.15_A_A (Version 2.15), strangely enough I recalled that my existing BIOS is 2.19 version, so I use Phoenix UEFI WinFlash tool included with 2.15 download and flash the 2.15 BIOS, it went fine and without any errors, and after the laptop restarted, it won't go to POST screen. Sad

I've read a couple of information on the internet about this problem, and tried using CRISISDISK with different BIOS versions, renaming the BIOS to BIOS.WPH, use the fn + esc method but no luck, the flash drive would flash four times, but I think the flashing process never starts because the laptop won't turn off by itself even if i let it turned on overnight. 

I've also tried the Insyde method, using the base BIOS version (2.10) and the latest (2.15) by putting the JE40210.ROM and JE40210.FD (Renamed from the .ROM file) so there two files inside a FAT32/FAT formatted USB flash drive, and then perform the fn + esc method, I believe this method has failed too.

Please let me know if you guys have a solution or suggestions for this issue, Thank you very much in advance. Smile

Answers

  • JackE
    JackE ACE Posts: 44,561 Trailblazer
    Options

    What was the original Windows version?  Jack E/NJ

    Jack E/NJ

  • arvindnavaratna
    arvindnavaratna Member Posts: 2 New User
    Options
    Windows 7 Home, 64 bit
  • JackE
    JackE ACE Posts: 44,561 Trailblazer
    Options

    Your particular model laptop's BIOS is listed as a Phoenix, not Insyde. Accordingly, Google "Phoenix Bios Recovery" with the quotes and try the WinCris minidos procedure used on the bios mod site. The original version was probably 2.10, not 2.19. Unless you are 100% positive there was an issue due to the 2.10 firmware, I would try to use the 2.10 version. You may have to try re-naming more than one BIOS file that you find in the downloaded DOS subdirectory. If the Phoenix recovery fails, then I suggest as a last resort disconnecting and/or briefly shorting the CMOS cell terminals to try to force the BIOS chip into a default state. Jack E/NJ     

    Jack E/NJ