Oh man…noises, shut that thing off, damm it, thats why no app can detect the damm IC, probably its fried now or the cheap CH341 is damage/have now damage.
And take the board out…cant you see that all is still connected yet, LVDS, CMOS etc…
Did you at least unpled the AC and battery???
Some system board requires AC on or OFF, CMOS battery ON or OFF, rare cases if even require to power the board…
I do understand…but this is no work for unexperienced users, instead of paying a 50€ service, spend 20 or 30 plus their own time and headaches and do worst…
Sorry but im out of this… all the best, good luck.
1 Like
Ok ill take the board out
Yes i did remove cmos and any power
After a long time, i managed to flash the bios sucsesfully but i still have black screen and my laptop keeps rebooting
Do i have to flash ec too?
Did you check if the bios you flashed has the same version as the original bios? If not the first 4 MB of the firmware would have another version than the last 1 MB. That’s a bad idea and most often not going to work…
Yes it was the same version as the one on the original bios chip
If i remember correctly, i had a modded version of bios bersion 2.2.1 and i found the version 2.2.1 original bin file on badcaps fourm. I flashed the alisaler one first and after flashed the badcaps 2.2.1 one
Before the bios mod and all the bricking, i had version 2.1.5 then i used the acer website to update my bios to 2.2.1 then i used acer crisis mode to flash the modded bios. Im not sure if updating the bios from 2.1.5 to 2.2.1 modified the ec
And what makes you think that the last part of the firmware in the 1 MB chip was left unchanged when “modding” your bios region? Did you check?
How do i check?
Also how can i extract bin file from modded fd
Which part of this don’t you understand?
Hexeditor (HxD), UEFIToolNE for structure.
Attach the ‘fd’ or give a link. How would one know which format an unknown file has. ‘fd’ is just a file- extension, could be anything.
https://www.dropbox.com/s/jf13hk5fnnnw0gu/Acer%20V3-571G-_2.21-Q5WV1221-UnlockUpdate_ModFinal.zip?dl=1
Thats the modded fd
I dont understand the ec part
One thing that i noticed is that when i open any of the bios bin files in uefitoolne it keeps saying “not a single volume top file is found. image may be corrupted.”
Maybe you want to do some reading what an EC firmware is and what an UEFI firmware is and how it can be that it’s distributed to more that one chip in some cases?
I’m sorry, I can’t explain it any better: The manufacturer decided to use one 4 MB and one 1 MB for a 5 MB UEFI firmware.
And it’s completely correct that UEFIToolNE can’t recognize a structure in both the 1 MB and the 4 MB file if they are not combined properly to one firmware image.
Which file did you flash to the 4 MB chip with the programmer?
As far as I can see the firmware is 5 MB. That’s confirmed by your modded file which is 5 MB, opens fine in UEFIToolNE and has a correct UEFI firmware structure.
You flashed something from badcaps (thanks for not giving the link) which is apparently 4 MB, which means the content of the second chip with the last 1 MB of the firmware (incorrectly named / referred to as EC***) no longer fits to the first 4 MB.
Yep, me too.
I found another chip on my motherboard that looks kind of like an bios chip. Im assuming that this is the chip that contains the other 1 mb.
But no flash software recognizes it.
So could anybody help me identify it?
1 Like
Can you help me fix mine too please. Just write the steps how to do it. Please bro
Wasn’t this alive just 4days ago?
Yes thats true. I think I have a problem with the Nvidia card that needs to heat up to work as called reflow. But instead of that I unlock the BIOS and tried changing the integrated graphics card from 64MB to 256MB. It worked for me and played some games. but when I tried to increase it to 288mb, I got a black screen and I was bricked.
I got the all the steps. One 4mb main bios goes to the 4mb bios under the wifi card and one of 1mb refer to EC file goes to the one beside the com.
But which files you used to flash thoses twos ?
Is that the ones from badcaps or the ones from packard bell pack main and ec??
As written before there’s no EC, the firmware is distributed on two chips which have to be congruent since they both build together a complete firmware.
You need a programmer and have to dump your own firmware.
General rules:
Find the correct chip, check voltage, get the correct clamp / adapter (SOIC vs. WSON)
Always read the chip you want to overwrite, make 2 dumps which have to be a 100% identical and have the same structure than the file you intend to flash (UEFIToolNE) - that way you know that your setup is OK and that you’re on the correct chip.
(“If you can’t read properly you can’t write properly”)
If you flash a foreign firmware you have to flash both chips, 4 MByte and 1 MByte. If you repair your own firmware you only need to work on the 1 MByte chip.
I downloaded 3 working bios files. One for Q5WV1 and Q5WVHa and one for the same bios that cause the problem 2.21 bios files but its locked.
As my motherboard got Q5wv1 but in the file theres 2 bin files one called (name )…main.bin have 4mb and other called (name)…ec.bin have 1mb. The one of thain i know where is locate. But what about ec? If theres no ec why theres ec file separated from the main bin file? Or that called ec it just a firmware that have 1mb and should program it to the 2nd bios chip.
Should i programm it next to the same chip or do as the writer of the post and try to programm it to that chip he found at the end?
What is unclear in the following statement?