PINE64

Full Version: Not charging, not detected when booting jumpdrive
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Okay, so I made this thread, PinePhone replacement board won't stop vibrating, detailing how I basically cut of the vibration motor from the sideboard after it started malfunctioning with the newest version of the PinePhone boards. One thing I didn't make a post about was the fact that I ultimately couldn't flash another OS onto the eMMC because I couldn't detect the device when booting jump drive. I used multiple versions. Furthermore, the latest build of Mobian which I booted off of an sd card didn't indicate that it was charging when the phone was plugged in. And the phone wouldn't charge. 

So, I bought a new sideboard, installed it, and the same issues are still there. No light when plugged in, although, it's been about a year since my Pinephone even worked, so I'm having a hard time remembering what it does when it charges. No vibration issues, though. It's plugged in now, and it doesn't seem to have increased in battery since it was plugged in. Lsblk doesn't return anything when the phone is booted into jumpdrive. I tried this on another laptop with Ubuntu, but no dice. I've flashed the eMMC on this phone plenty of times using this exact cable, so I don't think it's that.

I also bought a replacement screen, so maybe I'll see how that goes. At that point, this is going to be the Theseus' ship of PinePhones. I really hope it manages to float, somehow, at this point. The sunken cost fallacy only stays in effect for so long.

Edit: Nope, nothing changed. I'm not sure why I thought it would. Perhaps the connector from the mainboard to the sideboard is damaged? If that's the case, I don't see any damage. The pins look fine, and the cable itself doesn't seem worn down.

The ribbon of my new sideboard snapped off, somehow, so I'll be using the old sideboard from now on.
What a nightmare…