yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] middle_road:
Hi all, long time no see. My first TP was doing great & RL has been hectic and I haven't been able to come around much except to lurk.

Well TP-One bricked, battery went south, nothing nada, not even a blink or flicker. So I went and bid on another on EBay and ended up with two.

- Where do we find the logs JCS requested?

Finally have time tonight to try to flash them and figure I would give the toolbox a try.

Jumped right in a grabbed 41b, tossed it on, copied the files into 'ttinstall' and tried & failed to get an install to take.

The ROM and GApps checked out OK, but the CWM and/or TWRP ZIPs failed the check.

Did what I thought was a wipe, booted to recovery and tried 41a. - Same results.

There didn't appear to be any sort of Android on it but I went and tried acmeuninstaller2 anyway, then tried again. more No Joy.

Wiped it back to WebOS and that is where it is sitting now whilst I try to figure out which way I should proceed.

(I've more than likely left some details out and I apologize - I'm tired and frustrated. I figured to get at least one up and going tonight...)

Later,

_mr

*** EDIT ***

Found a previous post, and DL'd v41. Also DL'd : update-TWRP-jcs-dm-tenderloin-20140612.zip

Toolbox success with the following files using v41:

cm-11-20140625-SNAPSHOT-jcsullins-tenderloin.zip

gapps-kk-20140105-signed.zip

update-TWRP-jcs-dm-tenderloin-20140612.zip

TP is coming up as I type this. ( and the crowd goes wild!!! or at least I do...)

I still have one more TP to flash, @jcsullins: I want to do it trying out 41a or 41b, in order to get you some feedback, how should I proceed?
[TouchPad Development] jerryatherton:
Make sure you have the current recovery and rename it like on the original post op.
[TouchPad Development] jcsullins:
v41a and v41b were for a specific person to test possible fixes for a very specific issue (not being able to mount the media volume to the PC to copy files).
[TouchPad Development] jcsullins:
Don't bother with v41b. Test these two instead:

NOTE: The only reason anyone would want to try these is if they are having issues mounting the media volume to the PC.

NOTE: The only differences between these and v41 are related to that specific issue

.

https://goo.im/devs/jcsullins/cmtouchpad/testing/TPToolbox-2014-10-04-v41c.zip

https://goo.im/devs/jcsullins/cmtouchpad/testing/TPToolbox-2014-10-04-v41d.zip

NOTE: The only reason anyone would want to try these is if they are having issues mounting the media volume to the PC.

NOTE: The only differences between these and v41 are related to that specific issue.

I'm expecting that they will both work. Especially v41d (if it doesn't, then you will need to start looking for different USB cables or something). However, we really want v41c to work, so if it doesn't at first, try disconnecting the USB cable for a few seconds before trying to mount the media and reconnecting it. I can explain more about why we really want v41c to work after I've had some sleep.
[TouchPad Development] 35russ:
Great news JCS, 41c worked perfectly and I'm now setting up my account. Thanks you so much for taking the time and find a way. You are the man! Hope this all added something that benefits your work and your work as well as all the others that contribute is greatly appreciated.
[TouchPad Development] middle_road:
Well I sure flunked the test on 'paying attention', I didn't pick up that '41c' & '41d' were for a specific situation.

I was reading the threads too quickly in order to get these puppies up and running. I've been six weeks without my TP and was Jones'in.

The Nexus is a tad too small and the Toshiba is a POS.

Battery on the TP was down 35% this morning from where it was when I shut it down at 1:30am. I'd better go do the A6 flash.

I'll give the '41d' a shot on the second one today when I get time. I had no problems connecting to my PC (Win7Pro, AMD Proc) last night.

The TP showed up every time.

One thing I might suggest if someone is having a problem connecting with Win7 or 8 is to use a different USB port.

(This is over and beyond the usual driver issues that Windows always has.)

I've noticed over the years that on desktops you want to use the rear ports that are right on the mobo, and on laptops not all ports

seem to behave the same. This is true on everything from Android devices to GPS devices on Windows Mobile (yuck!).

_mr
[TouchPad Development] jcsullins:
Glad to hear it worked.

Now for the next big question: how well do USB connections work for you now that you have the ROM installed?

Could you test charging, adb, MTP, etc. and let me know how they work and which ROM you installed?

This will help me determine if the fix/workaround I implemented in v41c might need to be also added to ROM/Recoveries as well.
[TouchPad Development] 35russ:
Have tested with charging since battery was very low at the time I was successful with v41c. Charged to full quickly and have had on for several hours and holding charge well. ROM installed is "cm-11-20141002-UNOFFICIAL-tenderloin".

Was there something that I had done previously with the HP (had Evervolv 4.4.4 installed previously) that caused the problem with installing v41 of toolbox? Thanks.
[TouchPad Development] Steelskinz:
It's great ! I never used it before and tried it to delete webos and install Android. Really cool stuff !

Could it be used to install luneOS instead of webos with touchpad toolbox in the future ?
[TouchPad Development] synchron50:
Just wondering if these new TPToolbox versions support mounting of the data partition as well as the media partition? Back in the old days of CM9 and CM10, recovery tools like TWRP and CWM could have me access TP contents via USB mass storage (like WebOS). But with CM11 and the data/media partition, I am finding no way to access the data partition in recovery (Philz CWM does show a drive with no access) and/or HPToolbox and it would be great to xfer large files from the data partition to PC in recovery mode using USB Mass storage as opposed to within CM11 as an MTP device, which, IMHO, is slower and has tendencies to get corrupt during large xfers.
[TouchPad Development] preflex:
Is there any way to use Touchpad Toolbox to install android without gapps?

Or do i have to install with gapps, and then use clockwork to reinstall without?
[TouchPad Development] cdzo72:
As far as I know gApps never has to be installed on ANY device. .. that's why it's a separate package
[TouchPad Development] mschumacher69:
That's right, but he means can it be done with tptoolbox? Because the toolbox requires a certain number of files to be present in order to execute and it might need the gapps package to be present.

His question is, does the gapps package need to be there for it to execute and start the installation or can it be done without the gapps package?
[TouchPad Development] shumash:
Gapps does not need to be there, but if it is, it has to be consistent with the requirements of the version being used to actually get installed.
[TouchPad Development] nevertells2:
Why would you want to install Android without Gapps? That pretty much guts the functionality of Android. That would be like installing Android and turning off WiFi. You have your answer about using toolbox, just wondering about your reason.

NT

---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------

No, it's a separate package because Google told CM they could not include it in their Roms. True, it does not have to be installed, but Android will be pretty much useless without it.

NT

---------- Post added at 06:32 PM ---------- Previous post was at 06:17 PM ----------

TP Toolbox only mounts the /media volume SD card to allow the installation files to be copied to the ttinstall folder. The /data volume is accessible after the installation of Android is complete. Philz CWM allows you access to both data and media volumes for backup and restore purposes, so something is wrong if you cannot access /data. But when you mount USB from CWM, that only mounts the /media volume just like when you mounted the USB drive in WebOS or when TP Toolbox mounts the /media volume to transfer the install files to ttinstall. Before data/media Roms came along, the /media volume SD card was the only drive available. So, back in the good old days, that is the only drive you were accessing via CWM, TWRP and WebOS.

NT
[TouchPad Development] preflex:
How? When I tried to do it without, it refused to run, complaining there was no gapps. To get it to work, I had to install with gapps, and then use clockwork to wipe, and do a fresh install of CM.

I don't use the play store or any of the google apps. I mostly just use Firefox, XBMC, X-server-sdl (for an ubuntu chroot), and Limelight, plus a few other goodies from F-Droid (with XPrivacy to make sure they behave). Since all the apps I use on my TP are open-source, I don't need the play store, and thus have no desire to register with Google.
[TouchPad Development] vqstaphbeard:
That's awesome and inspiring.
[TouchPad Development] mschumacher69:
Makes sense...
[TouchPad Development] rmagere:
I would also be interested in the above point
[TouchPad Development] Maverick0984:
This tool is pretty impressive. Thanks!
[TouchPad Development] nevertells2:
Did you read my post/reply to synchron50?

NT
[TouchPad Development] xcessi:
I'm tried all the recovery ZIPs and I am getting the same error.

unrecognized/unsupported zip

Has anyone had this problem?
[TouchPad Development] mschumacher69:
Which toolbox version are u using? v40 or v41?
[TouchPad Development] xcessi:
Hi..

thanks for responding..

I discovered my error.. I was using the 4.1 toolbox and the 4.0 recovery zips..

I found a link to the correct recovery zips.

I will find it and post it here for anyone that might encounter the same issue
[TouchPad Development] middle_road:
Well, I messed up somewhere. I just plugged in TP-II today for the first time since flashing it and all I get is 'unknown device' from windows7/64.

Going to fire up my lubuntu laptop and see if it is recognized there...

*Edit: Later that same day...

Tried two other Win7/64 machines, both laptops. Then on the Lubuntu laptop, and syslog reported that it couldn't enumerate device on Port X.....

_mr
[TouchPad Development] fouad796:
Read-only

Hello ,

Still not fixing the Read-only mode tp both v40 and v41

when selecting Install android i get : eZfsck: unable to set superblock flags on /dev/store/cm-cache

complete data reset doesnt work either

thx for the hard work
[TouchPad Development] racenrich:
Dude, i will say you amaze me with the things im able to do with my Touchpad, i have had this bad boy since CM7! does that sound weird? I hope not

Been running a 4.2.2 build for quite some time now, finally took the plunge, read thru some threads, and followed the toolbox with a FULL resest.

Running the 1018 build. Awesome. Simply Awesome.

Rich K.
[TouchPad Development] Spektre99:
Bricked after TP Toolbox?

Well I'd like to be singing the praises of this tool, but I cannot today.

Sometime back in June, I upgrade my Touchpad to KitKat using the Toolbox. I have to admit, the process was pretty easy.

I am preparing to use the Touchpad in a different application and decided to upgrade to the lasted CM tenderloin build.

So put my fully charged Touchpad into WebOS recovery mode, plugged it into the PC and ran the Toolbox script: tptb_v40_win.bat from a 5-18 build. (The one I had used before.)

The Touchpad responded accordingly and I first did a "Complete Data Reset"

Followed by an "Install Andriod".

edit: Who knows what happened but a few hours off the charger brought it back to a CWM recovery screen.

It mounted the touchpad and I copied the three requested files into the directory: cm-11-20141002-SNAPSHOT-jcsullins-tenderloin.zip , gapps-kk-20140105.zip , update-CWM-jcs-dm-tenderloin-20140317.zip

TP Toolbox checked the files and proceeded with the install. All seemed fine until the final reboot.

Then the Touchpad restarted. It came up with a brown derby looking hat for a few seconds...and that is the last life I have seen from my Touchpad. I cannot boot it, I cannot being up the WebOS recovery mode, nothing. I'm quite sure the battery is fully charged.

Any ideas what happened and if it is possible to recover my touchpad?
[TouchPad Development] Carpetman:
How much free space should I have on 16 gb TP after using toolbox?
[TouchPad Development] britoso:
does this tool have the functionality to de-brick? (like TPDebrick v004 )
[TouchPad Development] AllanSim:
Spektre99, try the latest Toolbox which is 'TPToolbox-2014-08-10-v41.zip".

Also use "update-CWM-jcs-dm-tenderloin-20140612.zip" with the gapps and jcsullins snapshot you have used in your post. Do the complete wipe if possible.
[TouchPad Development] nevertells2:
First off, since you already had KitKat installed using TP Toolbox, why did you opt to install a later version of KK using toolbox again rather than just flashing it with CWM? Can I assume that you know how to use CWM to flash an newer version of Android?

In the middle of your post you say " Who knows what happened but a few hours off the charger brought it back to a CWM recovery screen. " So somewhere after starting Toolbox you found yourself back at CWM recovery after you took your TP off the charger? This does not make sense. Then you say you you copied the files to the ttinstall folder and attempted to have Toolbox install them? So you copied them while the TouchPad was mounted in Toolbox or at some other point? Because after that the Toolbox should reboot your TP and launch CWM to finish the installation. The way you explained is confusing and seems all out of sequence. Also, you did not state what version of KK you had installed back in June.

If you cannot hold down the power button for up to 30 seconds to a minute and get your TP to respond, then I suspect you need to try reading up in J.C. Sullin's Debricking thread.

NT

---------- Post added at 07:23 PM ---------- Previous post was at 06:35 PM ----------

Around 10 to 12 gigs if you did a complete data reset to remove WebOS and allowed Toolbox to allocate all available memory to the /data volume.

NT

---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------

Nope. Sounds like you have never used Toolbox.

NT
[TouchPad Development] britoso:
Yes I've only used it to see if it works. It has an A6 battery reset option that I was interested in, but it seems like tpdebrick is the only option if you cannot get to the USB logo screen. I noticed a tptools jar file inside tpdebrick as well.
[TouchPad Development] nevertells2:
So you used TP Toolbox to remove WebOS and install Andorid? Did you know you can place the toolbox .bin in the /boot volume/folder by renaming it uImage.Toolbox and copying it into /boot? Then you PC is no longer needed to run the A6 flash or resize volumes if needed. You can rename it whatever you want, Toolbox is just a suggestion. And what looks like a lowercase L in uImage is actually an uppercase i.

NT
[TouchPad Development] josepr2012:
Deleted nd posted in othe Q/A thread...
[TouchPad Development] Razor512:
Are there any plans to improve support for cyanogenmod 9?

I would like yo be able to install it with the toolbox, in addition to also getting rid of webOS.

(I am currently not interested in upgrading as even a few days ago, I have not found a better experience with the newer builds in terms of the UI. Overall, less screen space, less space for icons and widgets on the home screen, nagivation buttons in bad location (bottom center instead of bottom left, app switcher spanning the width of the screen instead of vertically on the left (while some builds have a vertical app switcher, the gesture control on them is very unresponsive).

Overall CM9 is more efficient with the use of screen space (and it works better with dice player which is the main video application that I use)

With all of this, there are many users who still prefer CM9, and thus, I feel it will be good to have better support for it with this tool.
[TouchPad Development] nevertells2:
You are kidding, right? What exactly would you use TP Toolbox for even if Mr. Sullins did expand support to include CM9? There has not been any support for CM9 in like two years. No nightlies official or unofficial, nothing. TP Toolbox was created primarily to support installation of data/media Roms like CM11. Like Mr. Sullins said in the OP, it takes the place of a variety of tools to simplify installing CM11 and other data/media Roms. The fact that he included some legacy support was a gift which he did not really have to do. So, I'll ask again, what exactly would you use the Toolbox for?

NT
[TouchPad Development] Razor512:
It is useful for when you want to simply erase everything, and do a fresh install from scratch. especially since when HP kills the webOS servers on the 15th of January next year, it will be a lot harder to install CM9 the normal way. While there have not been any updates for CM9 in a long time, the latest build is very stable, and offers far better and more stable hardware acceleration for video without the system randomly freezing or crashing. (if you have a newer build, try installing diceplayer https://play.google.com/store/apps/details?id=com.inisoft.mediaplayer.a&hl=en

you will see how it is less able to handle things like having a hardware accelerated video playing in a floating window, while using other applications which also make use of the GPU e.g., chrome.

That is on top of the more efficient use of screen space (space for 100 icons per home screen, no screen space wasting top bar (why does a tablet even need it? there is more than enough space on the bottom bar for that (as proven by CM9).

Overall, while there were some improvements with newer versions of android, compared to CM9, there was a lot more that was degraded in comparison, than improved (from a UI standpoint).

The touchpad toolbox is currently the easiest way to perform the functions that it offers, and thus it is very desirable to have it support CM9 even better, especially in the way of getting rid of webOS and having only CM9 installed.
[TouchPad Development] green2000:
I saw someone ask this before but can't find any answer. Can we use the toolbox to install LuneOS? This works be a great addition.
[TouchPad Development] nevertells2:
No
[TouchPad Development] caicom98:
usb issue

I was able to get to webOS recovery and launched the Touchpad Toolbox batch file (tptb_v40_win.bat)

After that I was not able to run anything unless i did the "Complete Data Reset" as recommended.

Next I tried to run "Install Android" and my computer no longer detects the usb connection to the touchpad. I am unable to copy rom/gapp/etc.

Is there any other way to do it? Why does the USB work while running the bat file but not the USB Storage mode. It was working with CWM, but now that got blown away by the data reset.

It still has moboot with minimum items, so I am able to go to webOS recovery to get into the toolkit again, but just cant figure out why the USB connection flakes out leaving me no way to transfer the ROMs over.

Any suggestion or help? (I am running Win7 64bit)
[TouchPad Development] 35russ:
I had the same problem. Find v43 in thread and give that a try. Worked for me.

Edit: Meant to say 41c . Be sure thank JC Sullins for his great work: https://goo.im/devs/jcsullins/cmtouc...10-04-v41c.zip
[TouchPad Development] Steelskinz:
could someone opst the 43 link ? Can't find it on jcsullin's files on androidfileshost. Thanks
[TouchPad Development] 35russ:
Sorry, I meant to say v41c and here is the link: https://goo.im/devs/jcsullins/cmtouc...10-04-v41c.zip
[TouchPad Development] garux:
For the latest toolbox, should we be using v41 or 41c?
[TouchPad Development] Steelskinz:
thanks !

edit: link did not work
[TouchPad Development] middle_road:
Finally got some free time to mess with my mine. I was having all sorts of strange freezes and blue screen lock ups.

I'm suspecting that there might be something funky with this used one I bought off of Ebay.

I had messed up before and wasn't paying attention and used version "A" or "B". This time around I went with the first version of 41.

Previously I flashed:

cm-11-20140625-SNAPSHOT-jcsullins-tenderloin.zip

gapps-kk-20140105-signed.zip

update-TWRP-jcs-dm-tenderloin-20140612.zip

This time though I went back to milaq's which I had on my now dead TP, and still the same gapps & TWRP.

I did perform the A6 flash first since I was having some strange battery drains overnight, and then I did do a complete wipe - blew it all away.

It's been a few days now and I've only had one lock up and that was a blue screen after rebooting from TWRP. The tablet seems to reboot or freeze

everytime after I go into TWRP - I haven't determined exactly why though.

The USB connection to my PC is working fine, however it does sometimes require re-plugging/connecting the cable to get it to take, precisely

as mentioned in previous posts.

I've still got a second TP sitting here that I need to do something with...

Thank you jcsullins for such a great utility!

_mr
[TouchPad Development] caicom98:
Its in the testing folder here:

I tried both 41c and 41d i am getting same issue it just does not detect after mounting as usb mass storage in TP Toolkit.

Novacom is installed, not sure if I need a newer version or anything. It appears to be working fine.

Do i need to update moboot or ACMEInstaller? I did this like 2 years ago so it had previously used ACMEInstaller2

Any suggestion would be great.
[TouchPad Development] caicom98:
i read a few posts and swapping to the original cable that came with the touchpad worked out.

I did some debugging with palmenv.bat procedures to produce the klogs and noticed that the TP was detecting with the new cable so I eventually got it working.

I had issues installing with the recoveries from the OP not accepting them, but turns out you have to use the right recovery if you are doing DM vs non-DM

http://xdaforums.com/showpost.php?p=54986968&postcount=293

Hopefully that helps out some of you that are having issues. great tool, will enjoy the ease of use and also the full removal of webOS...big props jcsullins:good:
[TouchPad Development] Cobra11Murderer:
Or use a LG cable, i wouldn't recommend using a samsung cable since those do cause issues with some devices on transferring data and what not.., HP original cable does suck though they break even if your careful they become so touchy that you have to have it in a certain way for the device to charge
[TouchPad Development] jaggrey:
I have a used Touchpad that's currently on eBay. I believe I have Touchpad Toolbox installed on there along with Android 4.4. Should I wipe the tablet clean and restore webOS, and if so, how? I did the option where it removed webOS when I installed 4.4. I'm still reading thru all the threads looking for that information but it's a little overwhelming!
[TouchPad Development] nevertells2:
You also have to pay attention to what recovery you use depending on which version of Toolbox you use, v40 or v41.

NT

---------- Post added at 03:25 PM ---------- Previous post was at 03:20 PM ----------

You do not need to install WebOS again. Support for it is gone come Jan. 15, 2015. If you want to be sure that everything you put on it in Android is gone, they running the complete data reset again would make sure of that. Then just install Android and don't set it up. Be sure to mention on eBay that WebOS is gone and only Android 4.4.4 is installed and not set up.

NT
[TouchPad Development] jaggrey:
My thinking was putting webOS on and letting whoever purchases it do whatever they want regarding Android. The version I have installed now isn't the most reliable, so I'd rather whoever wants to do the research put whatever they want on it.
[TouchPad Development] jaggrey:
On second thought, I may just do what you said. I can't find friggin webos doctor anywhere!