Framework 16 won’t turn on at all- no lights or anything

Hi!
Earlier today I was using my laptop completely normally when it died from running out of power. I pulled out my charger to plug it in, but I got no orange light by the usb c port and no light on the power button. I’ve left it plugged in for almost 40 minutes at a time now and I’m still not getting anything. I’ve been using this laptop daily since January and have had no issues so far. I’m wondering what my next steps should be and how to approach fixing this. This was a diy kit and I’m also completely comfortable taking it apart to fix it. I’m unable to currently take it apart right now, but once I have a chance to, I’ll add anything to this post that I find.

Thanks so much for any advice or help!

If it was a bad battery, having it connected may be preventing the system from working even when plugged in to the charger. Maybe try disconnecting the battery and seeing if it will power on? If so, I think that tells you the battery failed.

Yep, that seemed to be the case. Taking the battery out allowed it to boot no problem. I’ve sent suppport an email about it, so hopefully I can get a new battery from them. Thanks for your help!

1 Like

Nice! Happy I could help. A bummer that you got a bad battery in an expensive new product, but at least it’s easily replaced!

I just had this exact same issue. Will be checking out the battery this evening.

@Finn_Wolff
What fixed this?

There was some setting in the BIOS that had automatically been turned on when the battery had gotten to a very low voltage which disconnected the battery from the mainboard to protect the battery. After I took it out and put it back in a few hours later it seemed to have forgoten about this (?) and it just worked. I didn’t have to change any BIOS settings at all.

Had the same issue. This reddit thread summarizes several common fixes: https://www.reddit.com/r/framework/comments/1erk00m/common_causes_for_no_power_and_no_led_when/

Mine ended up being poorly seated dGPU interposer. Removing it and installing it back fixed the issue for me.