yashsingh1/xdaforums huggingface dataset:
[TouchPad General] HP_TOUCHPAD:
When done all at once, the Tablet will be set up as an out of the box, meaning brand new from factory!

For the first time ever, the HP Touchpad will finally be running with the appropriate settings to be use on Android.

Android will use the full 1GB Memory ( RAM ).

The hardware will perform as it should be with no limitations by under performance settings.

The user will experience performance like never before not even seen in WebOS.

Attached are screenshot of Evervolv 9, showing the 1GB been use by Android.

Settings will be posted as HpTp_MAX.

I will try to get all the other ROMs Kernel to perform the same as the kernel needs to be re-compile.
[TouchPad General] DoubleStuff:
Enabling ADB interface worked with success on my Touchpad with Nougat loaded.

But on my CM 11 Kit Kat, with Rom Reducer, Pico Gapps, SuperUser and the newest

HPTP_1782_max_settings, after making sure ADB interface was enabled in developers mode, also tried ADB over network on and off. I even tried to run command 'adb kill-server' but still get same error message, below and in picture attached.

This adb servers's $ADB_VENDOR_KEYS is not set.

Try 'adb kill-server' ect....

I am not sure you can duplicate it or not, or if you have any suggestions.

Because once its fixed I look forward to looking a live memory usage while

playing RunRace 3D, and using CastBox podcast in the ADB shell.
[TouchPad General] HP_TOUCHPAD:
The connection is successful and the PC sees the Tablet, but you must check on the Tablet the window that pop up to Authorize the PC for running the Abd shell command, otherwise it gets block.
[TouchPad General] middle_road:
Which ROM? I've got a tablet sitting here that I'm getting ready to nuke/wipe.

I'm going to try "cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip" and see what happens with ADB.

UPDATE: flashed it, and ADB is functioning fine. Found device right after enabling Developer Options.
[TouchPad General] DoubleStuff:
Yes I flashed cm-11-2015116, but I am trying to hook up the HP TOUCHPAD to the Android Novacom Tool which is on Puppy Linux ( look at my pic a couple posts back ), then I select the ADB button in the bottom of the pic, and get the error that I presented.

What is your definition of "ADB is functioning fine"?? Tell me what you do with ADB and I will try the same.
[TouchPad General] middle_road:
Straight ADB from a CMD window, then 'ADB shell' into the tablet and called it good.

I'll go back and take a look at your picts.

I've got Puppy 'Nix running on a laptop around here - somewhere. . . Have to find it.

*EDIT* - I'll need a basic 'Dummies' guide or links to setup 'Nix like you've got it shown in your picts. -Thx.
[TouchPad General] DoubleStuff:
OK I opened up a CMD window on my PC and like you said "Straight" ADB, not sure what that means, but I assume you

want me to type "adb" at the prompt, and I get which I expected

'adb' is not recognized as an internal or external command,

operable program or batch file.

Then I was not sure what you mean by "ADB shell" into the tablet? I did not know where to start with that instruction.

So just guess I opened up a terminal window on my Touchpad, and typed "ADB shell" and of course got an error.

Can you please be more specific on what you want me to do.....thanks.
[TouchPad General] HP_TOUCHPAD:
On a PC with the ADB install

All adb commands needs to be enter in the PC not the Tablet.

Open a terminal window on the PC ( Tablet must be connected and the service enable )

type:

adb shell

to use a command that require root

then type again on a new terminal window on the PC

adb root

then

adb shell
[TouchPad General] middle_road:
OK, your path variable on the PC must not be setup quite right.

On my workstation, Win7Pro, I navigate with File Explorer to the folder that contains adb.exe

which on mine, it is located in: C:\<PATHto>\ADB\platform-tools

Hold down <SHIFT> and right mouse click on the folder 'platform-tools', Select "Open Command Window here"

That will give you a cmd window where you can execute ADB from.

entering: ADB DEVICES

should show you the tablet...

entering: ADB SHELL

will take into the tablet. You'll see something like this at the command line:

shell@tenderloin:/ $

(I can't get my screen grabs to upload...)
[TouchPad General] DoubleStuff:
Oh OK, your first sentence tells it all "On a PC with ADB install". I don't have ADB installed on the PC I was testing your method. So let me go back to my puppy Linux "Android Novacom Tool" and show you my errors, it definitely shows the difference between my Nougat Touchpad, and my KitKat Touchpad.

I use 2 methods,first I connect the Touchpad to the PC, then I open up a Linux window and type, "adb devices -l" and Nougat appears to have a legit device, but the same command with KitKat Touchpad connected yields different results, I see the word "unauthorized".

Then the second method I select the ADB button ( bottom of pics ) and it brings up another window with a similar error. Seems like you had trouble posting your images, I will try now too.
[TouchPad General] HP_TOUCHPAD:
The error message is device unauthorized, meaning the PC is not authorized to run commands on the Tablet.

Check for a confirmation dialog on your device ( Tablet )

The connection is active, working and the Tablet is found but the user must authorized the PC to run adb shell commands by confirming on the Tablet.

Attached are screenshot on how is done in the Tablet.

Enabled Developers mode

Under Debugging select

Android debugging

USB debugging notify

Touch on Revoke USB debugging authorizations

( It will reset previous connections )

Connect Tablet to PC and issue the Adb Shell command

On the Tablet a dialog windows comes up

Allow USB debugging?

Check on Always allow from this computer and then ok

This is how Kitkat is set up, no settings makes any modification to it.
[TouchPad General] middle_road:
So you have two TPs, one with Nougat and the other with KitKat?

Or is it a single tablet?

Sounds like maybe the RSA Key is messed up.

If you're using two tablets, try restarting Puppy between attempts to connect the KK tablet.

=====

attaching images: I've had problems for quite awhile, need to get it figured out sometime.
[TouchPad General] DoubleStuff:
[MENTION=8005714]HP_TOUCHPAD[/MENTION] and [MENTION=3698561]middle_road[/MENTION]

Thanks for all the good adb advice, I do have 2 separate Touchpads currently with KitKat and Nougat and I tried all the below commands a few times in different order.

adb devices -l

adb kill-server

adb usb ( essentially adb start-server )

Turn Developer options off and back on

Turn USB debugging off and back on

Revoke USB debugging authorizations. Tried this while USB debugging is on and when USB debugging was off.

Unplug and replug USB cable into Touchpad.

Switched physical ports on the PC that my USB cable was connected into.

Deleted my /root/.android folder on PC in Linux, because sometime this folder can have the wrong permissions which can cause issues. And by removing ( rm -r ) the folder I also deleted /root/.android/adbkey file. Folder and file gets recreated on adb restart.

Touchpad says, "USB debugging connected" even though I never get a popup like

HP_TOUCHPAD's 3rd picture shows, and I get "Connected as a Media Device" dropdown message too.

but.......

This did not fix the issue, so until I reinstall KitKat down the road, I will do my adb experimenting with live memory with my Nougat Touchpad.
[TouchPad General] HP_TOUCHPAD:
1. Revoke USB debugging on Tablet.

2.Connect Tablet to PC

3. Type the command adb shell on PC, or just press the ADB icon (linux)

4. The popup will show on Tablet to authorized the PC.

That is all to do, nothing more or less.
[TouchPad General] kojam:
BINGO!

Tried DU and Evervolv...then just went to CM11, since I've been reading about it being the 'go to' for years. Cannot use it though get "Unfortunately, Trebuchet has failed" popping up every second. Help Please!!!

I followed the steps to a the letter.

Oh! I get an error that Play Store cannot be reached when I'm trying to set up my Google account so i can try installing a different launcher to get rid of Trebuchet. I noticed I got this same error when I broke out an old Android phone that I was giving to my kid for his first phone last year. Think it has something to do with Play Store apk being too out-dated? Is that correct? Is there a work around? If not, what's the best/safest/most trusted site to get apk's?

Thanks in advance!
[TouchPad General] HP_TOUCHPAD:
What process did you use to flash the ROM?
[TouchPad General] middle_road:
What is the difference between the two SuperSU packages floating around?

SuperSU-v2.82-201705271822.zip

vs.

SR5-SuperSU-v2.82-SR5-20171001224502.zip
[TouchPad General] HP_TOUCHPAD:
Take a look at this link:

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[TouchPad General] kojam:
I followed the steps as outlined. I flashed the WIPE, then all steps from #1 to #6. I didn't do #7
[TouchPad General] HP_TOUCHPAD:
Make sure the correct files were applied for Kikat.

All listed ROMs works with the Play Store and do not have any issues as you posted.
[TouchPad General] kojam:
I got all the files from the links in the post. I dunno why i have this issue then.

I will re-download them all and do the entire thing again ...starting from the WIPE ALL.

Thanks
[TouchPad General] HP_TOUCHPAD:
Once the Wipe All is done, there is no need to do it again.

Using TWRP Recovery, just wipe the partitions Dalvik /Art Cache, Cache, Data, Internal Storage, System and everything will be removed.

Flash all the zip files exactly in the same order as posted ( got to be that way )

Flash all files with no reboot, ( all in one shot )
[TouchPad General] kojam:
Oh. Ok. Thanks..

Question, if I wipe the Internal Storage, won't that delete these files before I can install them? Or will they still be available? Or should i use ADB to flash them after wiping the Internal Storage?

Thanks 4 your help.
[TouchPad General] HP_TOUCHPAD:
If using Wipe_All, the files must be copy from PC to tablet after is done as everything will be wipe.

If using TWRP Recovery the only partitions that can not be wipe is Boot.

Place all the files in the Micro SD card ( usb media ) and do not wipe that partitions, there is no need for it.

Is like the installation media where all the files can be place and wipe cache, data, system, then flash the zip files.
[TouchPad General] kojam:
Wait a minute! That's right! Wipe All should be wiping all my files, but doesn't. I just realized that even after running the Wipe All, all my files were still in the Downloads folder. That means it didn't 'wipe all'. As well, the wipe process yields a few lines of error but says it's normal and the wipe all was successful. I just remembered that now...So the wipe isn't really wiping my HP then?
[TouchPad General] HP_TOUCHPAD:
Have you read the very first page of this guide?

The Automatic_Wipe_All, when flash by any recovery will do everything with no errors code.

What guide or file are you using?
[TouchPad General] kojam:
I'm following the 1st page of this thread. I don't see any where it says that? Sorry. I just checked again and do not see those words. :eek::(:crying:
[TouchPad General] HP_TOUCHPAD:
The Automatic_Wipe_All_and_Create_Android_with _Swap can be flash using any Recovery.

It is best to use TWRP Recovery Version 3.1 or 3.2

Click here to download TWRP Recovery 3.1 by Flintman

Click here to download TWRP Recovery 3.2 by Flintman

__________________________________________________ ______________

Easy Automatic process to Wipe All and Create Android partitions with Swap

Click Here to Download Automatic_Wipe_All_and_Create_Android_with _Swap

This file MUST BE FLASH to create the swap partition to be use by the listed ROMs

A complete Data RESET of all the internal storage.

All partitions are deleted, is a total fresh start as if the Tablet came from factory with only Android install.

The Android partitions are created and formatted ready for use:

/system 2.2 GB ( Allows to install any ROM plus the maximum size of Open Gapps Variant Super )

/cache 200 MB ( Standard size )

/media 500 MB ( USB Media in Android, use it to save the ROM, Gapps and Universal Settings to Flash )

/swap 500 MB ( It allows Android to store temporally Data from RAM to allocate more Memory for Apps. )

/data depends on the model 16, 32 or 64 GB ( The free space available for Android Apps and user Data )

/boot 32 MB ( Is a fixed sized ) Moboot will be created and also TWRP Recovey 3.2.

The Tablet will boot as always, with Recovery in the Moboot Menu ready to Flash any ROM.

First Page:

https://xdaforums.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
[TouchPad General] kojam:
It's working now. No more errors. I haven't done anything yet. Weird.

I have been using TWRP to flash the wipe....

Although, i am still getting the error, "Couldn't sign in. There was a problem communicating with Google servers. Try again later." when trying to sign into Play Store app...that's ok. I got Mobro working on this. I may put Perfect Player as well and that's it. Don't even need a web browser. I use this as my portable tv. LOL. Nothing else. Thanks for your work. Mobdro plays beautifully now!

It was unusable with DU13 and the Evervolv.
[TouchPad General] HP_TOUCHPAD:
Great to know, I will be posting MAX settings for all the ROMs that for the first time Android will be able to use the full 1 GB of RAM and faster speeds, if you think that is working great now, it will be way better.

The settings are optimized for streaming, it has a 6 MB buffer, with the new MAX settings youtube plays in HD 720 as if it was running on a local file. I should be able to post all the new settings by this weekend.
[TouchPad General] kojam:
Sounds amazing!

Thanks!
[TouchPad General] HP_TOUCHPAD:
If you flash Kitkat then you can try it right now, is a first build that offers 887 MB of RAM, I will try to get the full 1 GB.

Go here and install the fastest frequency the tablet can handle.

https://www.mediafire.com/folder/cbddab4x02aqd/#lkw3wdx5l99v7
[TouchPad General] middle_road:
'Wipe All' might need to be ran twice on older installs/configs.

I had one tablet that has been running 4.4.4 for a long time. WebOS was wiped off it back when I put 4.4.4 on it.

Can't remember which method I used back then but it was probably HPTB Toolbox.

Anyway fast forward to last night, I wiped this one.

Has TWRP version 3.2.1-0 on it.

Copied over "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition.zip" to it and rebooted into recovery.

After the orange bar display and it rebooted, I noticed that TP Toolbox was still on the MoBoot menu. Compared to the several times I've run this on other tablets since early this month - I figured that wasn't quite right.

After it booted into TWRP I opened File Manager and sure enough there was data all throughout it.

Something didn't go correctly on the first run.

I re-ran "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition" and this time MoBoot came up w/o TP Toolbox

Went into File Manager and everything was cleared out this time.

So if the tablet has an older install on it perhaps Wipe All just needs to be ran twice to get everything cleared out.

Don't know why this was, doesn't matter, it's running EV9 nicely, and everything seems to be functioning.
[TouchPad General] HP_TOUCHPAD:
Thanks for reporting the issue, the reason that it did not work is because the TP Toolbox was copy to /boot. Is not related to older ROMs or configuration, it can easily be duplicated in any Tablet.

The TP Toolbox can not be permanently copy into /boot. It will create a lot of issues when flashing new Android versions. The /boot partitions is a fix 32MB and it's only use is to copy the Android uImage. Every time a new ROM is flash the developer assumed that only uImages of previous ROMs are the only one located into /boot and a script is run to delete old uImages and copy the new one. If the user has any customs named uImage or the Toolbox, it will not get deleted and the new uImage will fail to be copy completely, resulting in errors.

The only use for the TP Toolbox is to flash the battery A6 Firmware if need it, probably once every five years.

If the user copy it to /boot then after it have been used, it must be move to another location.

The Automactic_Wipe_All process delete all the uImages from /boot then it is copy and reboot to wipe all and create Android with swap. But it could not be copied entirely as the TP Toolbox was in /boot occupying 11 MB of space.

If the TP Toolbox needs to be use, I have provided flash files to be copy and removed from /boot on the first page of this guide. It can also be done using a PC with HP TOUCHPAD Novacom Repair Android:

https://xdaforums.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
[TouchPad General] middle_road:
OK, let's make this a bit clearer. I have (5) HPTP's. I mess around with (4) of them.

Moboot was the same on all.

-6- menu items.

TPToolbox was on all (4) before I started using 'Wipe All'

- boot TWRP

- boot Android or CyanogenMod or whatever

- boot TPToolbox

- boot webOS Recovery

- reboot

- shutdown

Last night was the first time out of (4) of them that there seem to be a hiccup.

The previous (3) Wiped with no issues. 'Wipe All' cleared everything.

Something was odd with this one.

So if someone comes upon this thread and digs out their HPTP that's been sitting in a drawer for awhile and wants to try it, 'Wipe All' might need to be ran twice.

That's the info that I was trying to get across.

In regards to the A6 flashing, I think it's been posted elsewhere that it might need to be ran more often than every (5) years.
[TouchPad General] HP_TOUCHPAD:
- boot Android or CyanogenMod or whatever ( The whatever, is the most important, there could be a ROM with a unique uImage name that could not get deleted )

If after flashing the Automatic_Wipe_All TWRP 3.2.1 ( Recovery ) is not in the moboot menu then it did not finish the process.

Once it starts nothing can be touch on the tablet, no screen or any key. It must be left until it reboots. If the user tries to touch or press anything to get any info, it may terminate and not finish the process.

If for any reason the Automatic_Wipe_All is not working, then it can be loaded using a PC with novacom or using the HP TOUCHPAD Novacom Repair Android.

Once the process successfully finish, only the following will be available in the moboot menu:

- boot Recovery

- boot webOS Recovery

- reboot

- shutdown
[TouchPad General] smithylovestouchpad:
OK, have to leave lurking mode and jump in here. I concur with middle_road. The Automatic_Wipe_All should completely remove all uImages including TPTB. If that is not happening, then the removal should be added to the script that removes all previous Android uImages including TPTB. Before and while I was testing HPTP's method I was always manually copying TPTB into /boot. Running "Complete Data Reset" from TPTB leaves you with a clean slate with all unnecessary uImages removed.

I also concur with middle_road about flashing A6. If one keeps an eye on battery drain, when it is noticed that it is higher than normal, reflashing A6 gets it back into a normal range. That is why J.C. Sullin's added the A6 reflash to TPTB. In my experience over 9 years with several different TouchPads and most all of the versions of Android, reflashing A6 was necessary every month or two.

Middle_road, have you thought of trying to duplicate the occurrence? I can say that in the time I was playing with all of this, I never experienced a failure of the Automatic_Wipe_All zip like you describe.

Back to lurking for now.

Smithy
[TouchPad General] middle_road:
Whatever, meant Lineage, Evervolv, etc.

Those are the (4) choices that came up last night - as well the first time on the other (3) tablets.

But there was still data on the SDCard and External from the previous 4.4.4 setup

The external SD partition was still showing up with data in it and it was still at the 4GB I had configured it for way back when.

'Wipe All' is working great! Makes it so much easier to nuke/re-install.

Just had to run it twice is all. No big deal. Some weird configuration on the old 4.4.4 setup that caused a problem.

Nah, I'm going pass on trying to recreate the previous setup that I had on that tablet. :cool:

It had (2) or (3) years on that setup and it was doing some wonky things lately.

Feels good to have a fresh Tablet(s).

Back on A6 subject. I've got one here that I took on the Trip from H*ll in July and the battery by the beginning of this month was not holding up.

I've flashed it (3) times now in the past couple of weeks with the last time being Tuesday night and it seems to finally be holding through the night.

Heck some of the batteries in mine must be at least (8) years old. :fingers-crossed:

I've got (2) NOS that I bought about (5) years ago but I'll be darned if I can remember which devices they are in...
[TouchPad General] DoubleStuff:
I was curious from all this discussion about /boot so I took a look at the "Wipe All" code and found that it does remove all boot files with extensions: Here is a snippet of the commands, and my comments in BLUE.

mount("ext3", "EMMC", "/dev/block/mmcblk0p13", "/boot");

This mount command, mounts the /boot partition.

package_extract_file("remove.sh", "/sbin/remove.sh");

This command takes the file "remove.sh" and copies it to /sbin on the Touchpad. I will show the contents of "remove.sh" later.

set_perm(0, 0, 0755, "/sbin/remove.sh");

This command sets the permissions so the remove.sh can be executed ( ran ) later.

run_program("/sbin/busybox", "sh", "/sbin/remove.sh");

Then the program "remove.sh" gets run by "busybox"

Here is the contents of "remove.sh"

#!/sbin/sh

cd /sbin ( changes directory to /sbin, where "remove.sh" now resides )

rm /boot/*.* ( removes ALL files with the format *.* from /boot )

Which means it will remove ALL files with extensions. So I did an experiment

and created files that look like this in a /test directory.

test.uImage ( extension of .uImage )

test.bat ( extension of .bat )

experiment.exe ( extension of .exe )

experiment.tga ( extension of .tga )

file ( notice no extension )

plainFile ( notice no extension )

And after a "rm *.*" this is whats left in the /test directory

file

plainFile

Only a "rm *" will get rid of ALL visible files. but if the /boot directory

only contains files with extensions then "rm *.*" will do the job.
[TouchPad General] smithylovestouchpad:
So this makes one wonder why middle_road experienced a failure of the Automatic_Wipe_All zip to remove all files from /boot that rm *.* is supposed to delete? HPTP purports that MR did something to interrupt the actions of Automatic_Wipe_All zip. Like Sullin's TPTB, I believe the touch screen is not active while Automatic_Wipe_All zip is executing, it's not needed. Can you test to see what it would take to cause Automatic_Wipe_All zip to fail to finish? If there is something that would, then there should be a warning to anyone using Automatic_Wipe_All zip to avoid touching the screen or inadvertently pressing a button.

Smithy

P.S. And to add to my comments about including the refreshing of the A6 in TPTB. Mr. Sullins noticed that the software engineers at HP saw the necessity of reflashing the A6 when WebOS was run and incorporated the code in his applications, TPTB and TPDebrick.