Help troubleshooting ASUS vivobook e406ma

[madan1]

Hello everyone.

I have this laptop and there is some kind of a problem with it.

Symptoms - when connected to a power supply, the power led goes orange. The led on the power button goes white.
Power consumption is around 3W
No image on both internal and external displays.
There is power on the USB.
Seems to be reacting to the power button ( when pressed for 10+ seconds it enters in a "boot loop" mode - power consumption switches between ~0.5 and ~3W, the leds turn on/off with the consumption ).
The battery circuit seems to be working fine ( when the battery is full, the power led goes white ).
I tried programming the bios IC with several different dumps ( 2 extracted from the official bios update files - e406ma+e406mas and one dump downloaded from the internet - e406ma ) and no success ( even one of the dumps just makes the board to go directly in power boot cycle ).
All but one power rails seem to be working. Only on +VCGI(?) there are 0v.
I injected 0.6 volts and the consumption is something like 100-200ma.
Checked the two mosfets and they seem to be fine (no dead short on any of them ). The resistance on the 470uF cap on the rail is 30ohms though.
I could not find any schematics or boardview for that particular board, so I'm using for reference the boardview for e203na, which seems to share similar ICs.

So any ideas for how to proceed?

[MOD EDIT] Boardview - https://www.badcaps.net/forum/showthread.php?t=99689
.

[madan1]

Re: Help troubleshooting ASUS vivobook e406ma

And to update the topic - while doing some measurements, I managed to shorten something ( most likely the battery charger IC, which is also responsible for the standby voltages ). I got lucky and won a cheap replacement board with physical damage around the power input ( scraped and damaged smd components ), was able to replace the missing and damaged parts, which fixed it. Just for fun, I installed the bios IC from the original board, to the fixed one and it started to fail the same way - no video and no voltage on the VCGI, which leads me to believe that this was the root cause of the original problem.