(I managed to...) Botched keyboard/trackpad firmware

[zivben]

So I wasn't initially aware of the existing trackpad issues, and so a quick google search brought me to this pinebook pro forum post
I was so eager to fix the issue that I didn't really notice this wasn't a pine TAB forum as the OP was simply commenting on how a linked procedure worked for them.

In any case, now my KB/Trackpad are completely unusable. 
I'm able to repeat the procedure, so the basic USB communication is still there. Also the keyboard reacts on some keys but the resulting signal is nothing related to the actual key pressed.

I'm wondering if there's any way to get a hex dump of the actual keyboard/trackpad from the pinetab in order to revive my now botched keyboard...

[tllim]

So I wasn't initially aware of the existing trackpad issues, and so a quick google search brought me to this pinebook pro forum post
I was so eager to fix the issue that I didn't really notice this wasn't a pine TAB forum as the OP was simply commenting on how a linked procedure worked for them.

In any case, now my KB/Trackpad are completely unusable. 
I'm able to repeat the procedure, so the basic USB communication is still there. Also the keyboard reacts on some keys but the resulting signal is nothing related to the actual key pressed.

I'm wondering if there's any way to get a hex dump of the actual keyboard/trackpad from the pinetab in order to revive my now botched keyboard...

I will post the PineTab keyboard firmware at wiki site on next week.

[zivben]

So I wasn't initially aware of the existing trackpad issues, and so a quick google search brought me to this pinebook pro forum post
I was so eager to fix the issue that I didn't really notice this wasn't a pine TAB forum as the OP was simply commenting on how a linked procedure worked for them.

In any case, now my KB/Trackpad are completely unusable. 
I'm able to repeat the procedure, so the basic USB communication is still there. Also the keyboard reacts on some keys but the resulting signal is nothing related to the actual key pressed.

I'm wondering if there's any way to get a hex dump of the actual keyboard/trackpad from the pinetab in order to revive my now botched keyboard...

I will post the PineTab keyboard firmware at wiki site on next week.

Awesome! thanks!

[fritz]

Hmm. My keyboard keys never worked, only trackpad. Wonder if this would help.

[zivben]

So I wasn't initially aware of the existing trackpad issues, and so a quick google search brought me to this pinebook pro forum post
I was so eager to fix the issue that I didn't really notice this wasn't a pine TAB forum as the OP was simply commenting on how a linked procedure worked for them.

In any case, now my KB/Trackpad are completely unusable. 
I'm able to repeat the procedure, so the basic USB communication is still there. Also the keyboard reacts on some keys but the resulting signal is nothing related to the actual key pressed.

I'm wondering if there's any way to get a hex dump of the actual keyboard/trackpad from the pinetab in order to revive my now botched keyboard...

I will post the PineTab keyboard firmware at wiki site on next week.

Hey! Did you get around to getting the firmware by any chance?
I couldn't find anything new on the wiki but maybe i'm looking in the wrong place?
Thanks again!

[zivben]

So I wasn't initially aware of the existing trackpad issues, and so a quick google search brought me to this pinebook pro forum post
I was so eager to fix the issue that I didn't really notice this wasn't a pine TAB forum as the OP was simply commenting on how a linked procedure worked for them.

In any case, now my KB/Trackpad are completely unusable. 
I'm able to repeat the procedure, so the basic USB communication is still there. Also the keyboard reacts on some keys but the resulting signal is nothing related to the actual key pressed.

I'm wondering if there's any way to get a hex dump of the actual keyboard/trackpad from the pinetab in order to revive my now botched keyboard...

I will post the PineTab keyboard firmware at wiki site on next week.

Just to update - 
I downloaded the hex file from the wiki to my tab, and used ayufan's flashing tool (here) to try and flash it.
I tried to rename the hex file as one of the provided files, either 'fw_iso.hex' or 'fw_ansi.hex', and tried to follow the flashing process as usual for both versions.
I got the same results as before and my keyboard is still using wrong mapping and the touchpad still doesnt work...

I'm wondering if I killed it for good or if there's anything left to do...

[tllim]

So I wasn't initially aware of the existing trackpad issues, and so a quick google search brought me to this pinebook pro forum post
I was so eager to fix the issue that I didn't really notice this wasn't a pine TAB forum as the OP was simply commenting on how a linked procedure worked for them.

In any case, now my KB/Trackpad are completely unusable. 
I'm able to repeat the procedure, so the basic USB communication is still there. Also the keyboard reacts on some keys but the resulting signal is nothing related to the actual key pressed.

I'm wondering if there's any way to get a hex dump of the actual keyboard/trackpad from the pinetab in order to revive my now botched keyboard...

I will post the PineTab keyboard firmware at wiki site on next week.

Just to update - 
I downloaded the hex file from the wiki to my tab, and used ayufan's flashing tool (here) to try and flash it.
I tried to rename the hex file as one of the provided files, either 'fw_iso.hex' or 'fw_ansi.hex', and tried to follow the flashing process as usual for both versions.
I got the same results as before and my keyboard is still using wrong mapping and the touchpad still doesnt work...

I'm wondering if I killed it for good or if there's anything left to do...

Jack may release his firmware build for PineTab keyboard.

[gnuoob]

Hello,
I'm having an issue with the mousepad on the device. It doesn't respond correctly. Is there a patch for this and if so where?