help with what exactly?
what may be the cause of this and if all of the signs make sense that it is a firmware issue and if it could be related to rtc and if suzyQ or wson8 clip is needed
.
.
.
… Maybe those?
I already said it wasn’t likely a firmware issue and reflashing was unlikely to help
Then what could be the issue? I can try to continue providing info.
hardware issue possibly? IDK.
… do you have any possible ideas as-to which part could be causing the system’s power circuits to turn on, yet for the device to Fail To POST? Because the USB-C Port starts working as intended as the device is able to turn on other devices through the port.
I really don’t like that such a project can suddenly wield such issues and then no one has a clue as to how it happened/ how to fix it.
you’re assuming it’s an issue with the firmware, and I’m telling you it’s likely not.
then you’re asking me to remotely diagnose a hardware issue.
And then I asked you what information i could provide that might find the cause. Answered?
seems that ignoring is common after posts get older.
MrChromebox
Is it that:
you have an answer, and don’t want to tell,
you don’t have a clue what is going on with it, OR
am I still not telling you something?
If the third one is the issue, then ask me some questions atleast.
If you do not answer, I will simply believe that you do not have interest in finding out why my chromebook and some other peoples chromebooks are failing like this, and old posts are ignored just because they are “old.”
I don’t have the time, energy, or desire to answer every post. I’ve already told you that this is likely not a firmware issue, and not something that can be easily diagnosed remotely. I’m sorry that I can’t be of more help, but I have nothing more to add to that.
Thank you for [finally] responding, as i was hoping that I would get some sort of close to this. I will keep debugging on my own (or try some methods)!