01/25/2012, 11:21 PM
I installed CM7 on both of my touchpads, and let one's battery completely die (thought I had it on the charger but never got around to it). When I plugged it into the charger or PC's usb, nothing happens on the screen, but eventually the home button notification LEDs begin alternating (slowly, slower than the blinking that occurs when the battery is super dead). Doing a reset (home+power) without it plugged in gives me a battery with a question mark.
Of course, I assumed that if I were to just send in my touchpad after having installed cm7 onto it, that they wouldn't fix it and say my warranty is void, so I just popped it open to take a peak (using flat screwdrivers of course, so the evidence is there, warranty likely null).
Anyway, I figured, maybe it's a dead battery? So I popped my other TP open, stole the battery and tried it in the dead one, same question mark unplugged after reboot or alternating LEDs when plugged in to charger or PC. Also swapped the USB circuit board of the internals from working TP to non-working, and no difference.
I don't believe it is hardware related. I've been reading a bunch, and accidentally discovered the two different boot methods of power+voldown+home (QDL mode), and the opposite is another mode that brings up an unknown device called "Palm" in device manager on my Windows PC. I have the Novacom drivers installed for the standard recovery mode, but this is something different.
To linux users familiar with hacking the TP: Unfortunately, while my home server has crunchbang on it, it's rather...inaccessible for testing with this. When this mode (power+volup+home) is enabled with linux, does it already recognize the driver equivalent?
I'm willing to try whatever I can on this, and would love to share it for the general public. I personally think that the bootloader (bootie) is corrupted or something similar, since I cannot seem to get it into standard recovery mode with power+volup.
Any ideas? I can have this usb port assigned to a linux vm no problem if it makes things easier. I saw in this thread (http://rootzwiki.com...ge/page__st__10) and jcsullins there asked for a vid and pid to give other possible solutions to that guy's similar issue, but didn't see a reply after he provided that info. I have posted this message there as well, but from what I've read, this community is #1 for the TP, so I figured I would try here as well.
Sorry again for the wall of text, and I (and likely others as foolish as I have been) would be grateful for any info. There has to be a way to fix it, the guys fixing them at HP are likely flashing them through one of these methods to fix the bootloader. I know we'd probably need those files to replicate the solution, but perhaps those files are out in the wild somewhere?
Thanks for reading.
Edit: This is not CM-dependent.