Related
I went ahead and uploaded the doctor file for those that the OTA did not work.
this is the full file not the bs web start app hp has on their site. lol
http://www.multiupload.com/762XCTTMUX
Plug in your Touchpad to the PC before starting.
The webOS Doctor tool will guide you through the installation process.
The tool may autorun after you download it. If not, double-click the file in the location where you downloaded it.
Warning Do not disconnect your device from your computer during the recovery process. Disconnecting the device cancels the recovery process and may damage your personal information.
Note If the battery level is low, the recovery process first charges your battery. This can take up to one hour.
Tip If connection options appear on your device's screen when you plug it in, your device is not frozen and it is not in USB Update mode.
When the Reset Complete screen appears, click Done.
Wait a few minutes for your device to reset.
When prompted, enter your existing HP webOS Account email address and username. This restores any information backed up to your webOS Account (such as contacts, calendar events, and tasks) back to your device. It also restores information from any online accounts you synchronize with, such as Google or Microsoft Exchange ActiveSync.
Click to expand...
Click to collapse
note: this will reset your touchpad.
note: you will need to reinstall moboot / CM7/ CWM
once you do that though, your CM7 install will be just as you left it.
file is safe
Thanks Scrizz! You rock!
http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar
What is this then?
Nburnes said:
http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar
What is this then?
Click to expand...
Click to collapse
it's the same exact file. I just renamed mine
I pulled mine from the java web start app and renamed it.
and besides when I went to my account and got the doctor the web start app was the only option.
so idk how you got that one.
scrizz said:
it's the same exact file. I just renamed mine
I pulled mine from the java web start app and renamed it.
and besides when I went to my account and got the doctor the web start app was the only option.
so idk how you got that one.
Click to expand...
Click to collapse
Can you post an MD5 of your file? I downloaded both yours and the other one and the checksums don't match, I may have gotten a corrupted download somewhere though.
EDIT: File compare is going crazy, they are almost definitely not the same file. The webOS.tar file seems to be the same in both downloads, so I'm not sure where the actual difference exists.
Slack3r said:
Can you post an MD5 of your file? I downloaded both yours and the other one and the checksums don't match, I may have gotten a corrupted download somewhere though.
EDIT: File compare is going crazy, they are almost definitely not the same file. The webOS.tar file seems to be the same in both downloads, so I'm not sure where the actual difference exists.
Click to expand...
Click to collapse
I pulled mine from the java web start app from HP and renamed it.
It works and I got it before that other link was available.
you probably got a bad download.
I don't post anything without trying it first.
here are the checksums for the file I uploaded
ADLER32: 15c2b488
CRC32: ffd58914
MD2: 5f8ea5cccab823ada7f1ff3577ce60e8
MD4: 31b2e85462b3d44e11db01168010707c
MD5: 94c0b30798f062bcfe03db016e0aabd7
SHA1: 0696959061e1f9dc6a20040f866fd4f8ac80594e
SHA256: 500676bc4042b46d44a5eeb55ad01f92534772291c7aae2e4ea4f2c797ccecb5
SHA384: f534b6bd754981a9960c4610a65a43e11b41509bd05dd7da06efba7a69ad93d33be4a95f5fe4549d7628b0ccdd6ce8b4
SHA512: 84126373b66995294f2167862a8501b1d23fc2e647afc8508cff6c446e9539c7aada41c6a32b4b2aaaaffbe276f8af88f7ed3250158ac46b3f0dda349df4ae9c
RIPEMD128: 8ce6f8995cbee687b20f55ba0d904a8b
RIPEMD160: fddab786ac2cca2485a35a87420c094ef009d120
TIGER128: 296c5f3c2c3cf147ce2830275fdf3a98
TIGER160: 296c5f3c2c3cf147ce2830275fdf3a98b9bdea0e
TIGER192: 296c5f3c2c3cf147ce2830275fdf3a98b9bdea0e6559f28b
GOST: 2fe764762b8c6136387280879fca887c42d11c7b5ecd340106c63a02bf07a53b
Click to expand...
Click to collapse
Been trying to install android on my touchpad, but having an issue with the "boot cyanogenMod" option showing up. I'm wondering if I need to put the touchpad back to 100% stock before doing android? I had a different kernal plus a large amount of patches.
Do you recommend WebOS Doctor prior to doing CyanogenMod....or would I be wasting my time?
No it doesn't have to be stock. Just make sure you have all the necessary drivers installed. And the palm webos sdk.
Sent from my HD2 using XDA App
Thanks. Installed yesterday and now loving the android option on this.
NISMOFO said:
Thanks. Installed yesterday and now loving the android option on this.
Click to expand...
Click to collapse
glad to hear you're up and running.
I'm getting ready to put the Android Alpha V2 on my TP for kicks, and while researching it, I sometimes read about WebOS Doctor... yet after Googling it, I'm STILL not sure just what the heck it is or what you use it for? Thanks!
EDIT: I found a better link explaining it. It's a recovery tool in case you brick your TP. It will wipe and restore. I'm looking for a way to BACK UP everything on my TP... so I don't see why copying everything from the TP Hard Drive to a folder on my computer can hurt? I may not be able to technically restore it, but it'll be there. I also did a WeOS Dr backup too.
Thanks!
Jason
well, got stuck on 62% and now pc is not recognizing the pad.
(mindflash to "it aint broke dont fix it"... well... screen was popping out, so technically...)
looking for solutions.
stuck at 12% for hr and half , should unplug and restart?
This solution is an alternative to WebOS Doctor that will preserve your data and settings in case WebOS kernel got corrupted or deleted.
The solution is taken from http://www.webos-internals.org/wiki/Memboot and I corrected some details in the instructions and added links to relevant downloads in the hope that this would help people who had the same problem (I happened to accidentally delete the WebOS kernel image - uImage-2.6.35-palm-tenderloin - while trying to free up some space on /boot partition).
So, here goes:
What you need:
Up-to-date SDK (especially novacom & novacomd) - download from here
Up-to-date WebOS Doctor Image - download from here
Steps to follow:
Extract the original kernel from the WebOS Doctor Image:
open the .jar file as an archive (I used 7zip)
inside, there is an archive /resources/webOS.tar - open/extract that one, too
inside webOS.tar, there is an archive nova-cust-image-rootfs.tar.gz - open/extract that one
inside the rootfs, in /boot there'll be the uImage, called uImage-2.6.35-palm-tenderloin
Copy the uImage to the novacom folder on your computer (for Windows it is %programfiles%\HP webOS\SDK\bin)
Get into bootie mode:
power off the TP,
connect the TP via USB cable to your computer
hold the volume up key, while powering on the device,
you should see a big white usb-resembling logo on the screen
Open cmd.exe and run the following commands
Code:
cd %programfiles%\HP webOS\SDK\bin
novacom boot mem:// < uImage-2.6.35-palm-tenderloin
TP will automatically boot into WebOS
I hope this helps. Enjoy!
thanks for this!
it would've been really, really helpful two days ago, when i "accidentally" deleted the webOS kernel...it was a lot more work when i had to acmeuninstall, then run webOSdoctor and reinstall everything...
i'll have to keep this in mind, just in case i "accidentally" do the same thing again
ofmirroreye said:
it would've been really, really helpful two days ago, when i "accidentally" deleted the webOS kernel...it was a lot more work when i had to acmeuninstall, then run webOSdoctor and reinstall everything...
Click to expand...
Click to collapse
I almost did the same... was actually 5 minutes away from reinstalling everything... that's why decided to post this here
this is awesome - I recently updated web os and messed up by boot....web os doctor stops at 8 percent....many thanks for details.
What about a clean restore, I want to delete everything and get my HP the way it was originally without any extra Android files. Then I want to re-add from scratch the CM9...
TurboTronix said:
What about a clean restore, I want to delete everything and get my HP the way it was originally without any extra Android files. Then I want to re-add from scratch the CM9...
Click to expand...
Click to collapse
The simple way is to uninstall Android using acme uninstaller or preware Remove Android app, then webos doctor the TP. don't forget to back up your data/apps first. Hope this helps.
voxter said:
The simple way is to uninstall Android using acme uninstaller or preware Remove Android app, then webos doctor the TP. don't forget to back up your data/apps first. Hope this helps.
Click to expand...
Click to collapse
It didn't work - still frozen at 8% - how do you acme unistall the moboot? I think that's what causing my loop error - stuck on HP logo....
Donmotobike said:
It didn't work - still frozen at 8% - how do you acme unistall the moboot? I think that's what causing my loop error - stuck on HP logo....
Click to expand...
Click to collapse
Here you can watch a small tutorial on this: http://www.youtube.com/watch?feature=player_embedded&v=p7IXl6XB6ig
Alternatively you can look in this thread: http://forum.xda-developers.com/showthread.php?t=1331540&highlight=webos+doctor - the problem looks similar
Hello guys.
I just got a brand new TouchPad 32GB. WebOS is very nice, but there are not many applications, so I'm trying to intall CM9.
I have all the drivers installed correctly, I can put the touchpad in developer mode, and USB mode
Problem is, MOST of the links on the guides are outdated. I tried guides here, guides on rootwiz, guides on XDA.
So I started looking for the files myself, and now I have.
e0664157ed69f8999e1c3ee77cdc53ae ACMEInstaller2
7b49b53a9d70315c40dccde9fc20e7a9 ACMEInstaller3
7642f3f0a8090dc52445541a94ed8164 cm-9-20120816-NIGHTLY-tenderloin.zip
980139d6b46b9cbba4db0e07ad17ba5d moboot_0.3.5.zip
1308300f38685d44afde730efd9132cc update-cwm_tenderloin-1012.zip
So I copied all the files from c:\downloads\touchpad to \cminstall on my touchad.
Rebooted into recovery, and did the:
C:\DOWNLOADS\TOUCHPAD>"C:\Program Files\Palm, Inc\novacom.exe" boot mem:// < ACMEInstaller2
The touchpad did some magic, including some linux thing/scorlling, rebooted, but now I'm back at webos.
So, did i forgot something? Should I use ACMEInstaller2 or ACMEInstaller3 (or even ACMEInstaller?).
Thanks.
EDIT: OK. I just realized that the Boot menu gives you some seconds and then it boots to WebOS.
Now, when it boots, I get this options:
Boot webOS
Boot ClockworkMod
boot webOS Recovery
reboot
shutdown
NONE of the options allows me to boot into CM9. I'm missing something?
kwanbis said:
Hello guys.
I just got a brand new TouchPad 32GB. WebOS is very nice, but there are not many applications, so I'm trying to intall CM9.
I have all the drivers installed correctly, I can put the touchpad in developer mode, and USB mode
Problem is, MOST of the links on the guides are outdated. I tried guides here, guides on rootwiz, guides on XDA.
So I started looking for the files myself, and now I have.
e0664157ed69f8999e1c3ee77cdc53ae ACMEInstaller2
7b49b53a9d70315c40dccde9fc20e7a9 ACMEInstaller3
7642f3f0a8090dc52445541a94ed8164 cm-9-20120816-NIGHTLY-tenderloin.zip
980139d6b46b9cbba4db0e07ad17ba5d moboot_0.3.5.zip
1308300f38685d44afde730efd9132cc update-cwm_tenderloin-1012.zip
So I copied all the files from c:\downloads\touchpad to \cminstall on my touchad.
Rebooted into recovery, and did the:
C:\DOWNLOADS\TOUCHPAD>"C:\Program Files\Palm, Inc\novacom.exe" boot mem:// < ACMEInstaller2
The touchpad did some magic, including some linux thing/scorlling, rebooted, but now I'm back at webos.
So, did i forgot something? Should I use ACMEInstaller2 or ACMEInstaller3 (or even ACMEInstaller?).
Thanks.
EDIT: OK. I just realized that the Boot menu gives you some seconds and then it boots to WebOS.
Click to expand...
Click to collapse
Your third file should should be renamed so that it reads ,
update-cm-9-20120816-NIGHTLY-tenderloin
And yes use ACMEIinstaller2
I hope this helps
Boot into CWM and then flash the 8-16Nightly file that you have then the latest Gapps 4-29
Sent from my cm_tenderloin using XDA Premium HD app
sstar said:
Your third file should should be renamed so that it reads ,
update-cm-9-20120816-NIGHTLY-tenderloin
And yes use ACMEIinstaller2
I hope this helps
Click to expand...
Click to collapse
Yeah, I re-read one of the guides, and it mentioned that, so i'm trying again.
Thanks.
kwanbis said:
Yeah, I re-read one of the guides, and it mentioned that, so i'm trying again.
Thanks.
Click to expand...
Click to collapse
How did you get on?
i tried acmeinstaller3 and i was complaining of inode errors ? has anyone else experienced this ? is there anyway of checking the filesystems again for errors, as there was lots of inode fixes maybe it was due to partitian resizing ?
i personally used this link:
http://liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html
The only thing i did different was that i used the latest version of the files.
imeem said:
i personally used this link:
http://liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html
The only thing i did different was that i used the latest version of the files.
Click to expand...
Click to collapse
I did exactly the same.
Just wanted to say this really helped me. And for any of the noobies, if you take the OP's MD5 codes, and plug them into Goo, you will find the files very very quick. And in order for me to download the ACMEInstaller2, I had to change it to a .zip file, and download as such, and then when plugging in the CMD code, just add .zip to the file name, and you're golden. Hope this helps!
partition repair prior to ACMEinstall3
alienkidmj12 said:
i tried acmeinstaller3 and i was complaining of inode errors ? has anyone else experienced this ? is there anyway of checking the filesystems again for errors, as there was lots of inode fixes maybe it was due to partitian resizing ?
Click to expand...
Click to collapse
If you are partitioned once using ACMEinstaller2, you should ACMEuninstall to remove/repair partitions. After that you can use ACMEinstaller3. Just make sure your CM9 and Gapps file names begin "update-" as you copy them into the cminstall folder.
ACMEInstaller3 is for CM10, not CM9.
not just for CM10
ve6ay said:
ACMEInstaller3 is for CM10, not CM9.
Click to expand...
Click to collapse
As posted by Developer green, it was designed for CM10 in mind to provide a little more partition room to accomodate CM10. It can be used with no ill effects* with CM9 to get that space from the beginning flash of CM9 and then you would be CM10 ready. You are able to use the benefit of a little more system partition than what is deployed with ACMEinstaller2.
I've used ACMEinstaller3 with great success on 6 of the 15 touchpads I help support with CM9. I use ACMEinstall3 by routine now as there is no need to have either ACMEinstall or ACMEinstall2.
* - the use of a few hundred MB from the SDcard to System partition is a small sacrafice of storage space on SDcard with the potential gain of CM10 ready and more headroom for the system, even on CM9.
I picked up a 32gb TP a few weeks ago.and have just been sitting on it. I was hoping to see some updated guides to simplify my learning curve to get android on it (i know I just need to read and learn). Can't believe I'm so hesitant to do anything with it, but the op's experience seems inline with my expectations of the device at the moment.
Sent from my "Up all night, Sleep all day" EVO3D!
mpgrimm2 said:
I picked up a 32gb TP a few weeks ago.and have just been sitting on it. I was hoping to see some updated guides to simplify my learning curve to get android on it (i know I just need to read and learn). Can't believe I'm so hesitant to do anything with it, but the op's experience seems inline with my expectations of the device at the moment.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
I used the same lilliputing site linked above. Like another post said, just plug the md5sum into goo.im and you should find the files.
First time install instructions for CyanogenMod
If you haven't seen these posts by the original Touchpad CM dev, you might want to check em out.
Rootzwiki post by Dalingrin: http://rootzwiki.com/topic/33872-first-time-install-instructions-for-cyanogenmod/#entry947163
The "maintained" instructions list in that post point here: http://wiki.cyanogenmod.com/wiki/HP_Touchpad:_Full_Update_Guide
^^^ There are a couple small inconsistencies here. I'm not sure how to submit to have them corrected.
Overall, this is designated as the official source.
In the top section they list ACMEinstaller3 (although the lower section they list ACMEinstaller)
NOTE: CyanogenMod product designation for HP Touchpad = tenderloin
Jonas. said:
Just wanted to say this really helped me. And for any of the noobies, if you take the OP's MD5 codes, and plug them into Goo, you will find the files very very quick. And in order for me to download the ACMEInstaller2, I had to change it to a .zip file, and download as such, and then when plugging in the CMD code, just add .zip to the file name, and you're golden. Hope this helps!
Click to expand...
Click to collapse
ZedZardoz said:
If you are partitioned once using ACMEinstaller2, you should ACMEuninstall to remove/repair partitions. After that you can use ACMEinstaller3. Just make sure your CM9 and Gapps file names begin "update-" as you copy them into the cminstall folder.
Click to expand...
Click to collapse
ZedZardoz said:
If you haven't seen these posts by the original Touchpad CM dev, you might want to check em out.
Rootzwiki post by Dalingrin: http://rootzwiki.com/topic/33872-first-time-install-instructions-for-cyanogenmod/#entry947163
The "maintained" instructions list in that post point here: http://wiki.cyanogenmod.com/wiki/HP_Touchpad:_Full_Update_Guide
^^^ There are a couple small inconsistencies here. I'm not sure how to submit to have them corrected.
Overall, this is designated as the official source.
In the top section they list ACMEinstaller3 (although the lower section they list ACMEinstaller)
NOTE: CyanogenMod product designation for HP Touchpad = tenderloin
Click to expand...
Click to collapse
Thanks to everyone who posted. I plugged the MD5's in as suggested, found the liliputin, CM, and jcsullins goo.im sites for files and read/the liliputin guide. I'm sure I will have additional questions for when I get back up later tonight to attempt this, but it looks like I have all the needed files ready plus some extras (screenshot).
For now:
- Do you have to "dual boot" android & webos, vs wiping out webos and keeping only android?
- How much space is WebOS taking up on the "dual boot" setup, ie does it have it's own partitions etc separate from android?
- Can you just turn the device on and have it automatically boot android (WAF = Wife Acceptance Factor)
- When installing roms I have been used to formatting /system, /data, & /cache first. Does AcmeInstaller do this for you. If so, you can just do new rom flashes & backups "manually" through CWM or TWRP right? I keep seeing mention of only wiping "cache" beforehand?
- How would I restore the tablet to stock WebOS, AcmeUninstaller? (I plan on going with AcmeInstaller 3)
- My impression is that the latest CM9 Nightlies are the most stable/functional ICS versions currently available for the TP as a daily driver. Is this correct?
mpgrimm2 said:
Thanks to everyone who posted. I plugged the MD5's in as suggested, found the liliputin, CM, and jcsullins goo.im sites for files and read/the liliputin guide. I'm sure I will have additional questions for when I get back up later tonight to attempt this, but it looks like I have all the needed files ready plus some extras (screenshot).
For now:
- Do you have to "dual boot" android & webos, vs wiping out webos and keeping only android?
- How much space is WebOS taking up on the "dual boot" setup, ie does it have it's own partitions etc separate from android?
- Can you just turn the device on and have it automatically boot android (WAF = Wife Acceptance Factor)
- When installing roms I have been used to formatting /system, /data, & /cache first. Does AcmeInstaller do this for you. If so, you can just do new rom flashes & backups "manually" through CWM or TWRP right? I keep seeing mention of only wiping "cache" beforehand?
- How would I restore the tablet to stock WebOS, AcmeUninstaller? (I plan on going with AcmeInstaller 3)
- My impression is that the latest CM9 Nightlies are the most stable/functional ICS versions currently available for the TP as a daily driver. Is this correct?
Click to expand...
Click to collapse
Re Files: You have more than enough.
move a copy of ACMEinstall3 to your PCs Palm, Inc folder
rename gapps-20120429-signed.zip to update-gapps-20120429-signed.zip
rename cm9 ROM to update-cm-9-20121007-NIGHTLY-tenderloin.zip
From webOS / USB mode connect your PC and copy your cminstall folder to the tablet. (cminstall folder should have 4 .zip files: CWM, MoBoot, gapps, cm9) when you reboot to Novacom Bootie, you are ready for your ACMEinstall invocation command. Takes about 15 min. to flash.
CyanogenMod is dependent on webOS to be present. You cannot remove webOS. If you are that concerned for space, webDoctor to ver 3.0.0 and never OTA update. That version has the smallest footprint, you might get a couple hundred MB saved, but IMHO, not worth the effort.
The default boot order selects Android after 5 seconds. You can edit this or use a preware webOS app: CyBoot to edit the default and how long to wait in MoBoot before default is loaded.
ACMEinstaller3 handles the partition chores for you. You don't have any CM or other ROM loaded? If you did, you should ACMEuninstall first or to return it to stock webOS. wiping cache is a selection that is done from CWM or TWRP on re-flash of the ROM. You could select ClockworkMod on first boot to do this step, but I have never bothered on an initial load.
I'm currently on cm-9-20121007, the latest nightly.
Good Luck
mpgrimm2 said:
Thanks to everyone who posted. I plugged the MD5's in as suggested, found the liliputin, CM, and jcsullins goo.im sites for files and read/the liliputin guide. I'm sure I will have additional questions for when I get back up later tonight to attempt this, but it looks like I have all the needed files ready plus some extras (screenshot).
For now:
- Do you have to "dual boot" android & webos, vs wiping out webos and keeping only android?
- How much space is WebOS taking up on the "dual boot" setup, ie does it have it's own partitions etc separate from android?
- Can you just turn the device on and have it automatically boot android (WAF = Wife Acceptance Factor)
- When installing roms I have been used to formatting /system, /data, & /cache first. Does AcmeInstaller do this for you. If so, you can just do new rom flashes & backups "manually" through CWM or TWRP right? I keep seeing mention of only wiping "cache" beforehand?
- How would I restore the tablet to stock WebOS, AcmeUninstaller? (I plan on going with AcmeInstaller 3)
- My impression is that the latest CM9 Nightlies are the most stable/functional ICS versions currently available for the TP as a daily driver. Is this correct?
Click to expand...
Click to collapse
The Touchpad's hard drive will show as 27.1gig before installing Android and 25.4 after if you use ACMEInstaller 3 or 25.5 with ACMEInstaller 2 .
You should not attempt to remove webos.
After installation it will automatically boot into Cyanogen/Android with a 5 second delay. To give you the option to change . Both the boot preference and time out can be changed either by installing an app called Cyboot through preware on webos , or by editing the boot folder when running Android.
Use gapps 20120429 and if using ACMEInstaller 3 rename so that it begins update- .
Yes use the latest nightly and rename so it begins update-
Acmeuninstaller will return the tablet back to webos and running Android uninstall from preware will remove moboot .
Install it have fun then you will probably have a few more questions.
Good luck
Thanks guys. I'm up and running on latest CM9.. AWESOME!
Still would like to see someone with a guide here that has up to date links. But the Lilliputin site guide was good minus links.
Sent from my "Up all night, sleep all day" HP CM9 Touchpad
Just installed JCSullins KitKat ROM using his fantastic TPToolbox. Whole process was very straightforward and worked a breeze. Would have written to thank him in his thread about it but haven't enough posts yet to do so. Made an intimidating process straightforward.
Thanks to JCSullins !
Spherewalker said:
Just installed JCSullins KitKat ROM using his fantastic TPToolbox. Whole process was very straightforward and worked a breeze. Would have written to thank him in his thread about it but haven't enough posts yet to do so. Made an intimidating process straightforward.
Click to expand...
Click to collapse
Same from my side. I'm new here and I like it a lot. Seems to be the best place for technical webos / TP users.
I agree. It seems like an excellent tool. I'm about to sit down and put in my touchpad, hopefully it's smooth sailing. Have you reinstalled android or anything like that? If so, is android smoother or faster for you?
dwalk51 said:
I agree. It seems like an excellent tool. I'm about to sit down and put in my touchpad, hopefully it's smooth sailing. Have you reinstalled android or anything like that? If so, is android smoother or faster for you?
Click to expand...
Click to collapse
I used the toolbox yesterday to blow away WebOS and an old CM install from last year. Used it to flash latest CWM and CM11, easy as pie. I would definitely say it's smoother than my previous install.
seboj said:
I used the toolbox yesterday to blow away WebOS and an old CM install from last year. Used it to flash latest CWM and CM11, easy as pie. I would definitely say it's smoother than my previous install.
Click to expand...
Click to collapse
I agree, my experience was similar. I saw an increase in performance. That being said, I'm still playing around with different gapps installs. For me, the smoothest has been the stock, latest, kk-gapps that's like 200+ Mb. Have you found anything better?
dwalk51 said:
I agree, my experience was similar. I saw an increase in performance. That being said, I'm still playing around with different gapps installs. For me, the smoothest has been the stock, latest, kk-gapps that's like 200+ Mb. Have you found anything better?
Click to expand...
Click to collapse
I'm just using the gapps from the CM11 nightly thread, only about 85mb I believe. No issues yet.
Quick n easy installs with TT!
Touchpad
Very slick!
Can't believe it was so easy to get kitkat on my Touchpad.
Touchpad Toolbox-recovery issue?
Hi, all. After unmounting the media volume (post copy of recovery, gapps and rom to ttinstall folder) I see the following: Checking Install files...
1 logical volume (s) in volume group "store" now active
No supported recovery file found. Aborting.
My ttinstall folder contains:
cm-11-20140705-UNOFFICIAL-3.4_kernel-tenderloin.zip
gapps-kk-20140105.zip
update-TWRP-jcs-dm-tenderloin-20140512.zip
I'm assuming the last is my recovery. I've done the complete data reset three times, with the same issue. If I choose reboot, I get:
Selected: 'boot'
Loading ' /boot/uImage-2.6.35-palm-tenderloin'...FAILED
BOOT FAILED!
Any idea on what's going on? Is there a "standard" recovery file I should try instead to make this work? Any assistance would be greatly appreciated.
Agreed, excellent tool - just a note about re-installing WebOS
Just finished installing the Toolbox (way to go JCS!!), just wanted to note that I received a "NOT COMPATIBLE DEVICE" error when following the instructions from JCS Post #64. When I used a WebOS doctor that I already had, there was no problem.
The doctor listed in post #64 is "webosdoctorp305hstnhatt.jar" which gave me the error
The doctor I used is "webosdoctorp305hstnhatt.jar" which worked fine
not sure what the difference is, but wanted to post this for non-devs like me.
Well, thanks to JCsullins !! (and all the others...)
I just used tptoolbox to resuscitate my TP which was sleeping with android 4.0 for a while in a desk...
I now use it as a "media solution" to stream Google Music and my movies (bubbleupnp/ or plex) from the NAS to my TV and my stereo... awesome ! (i prefer having a device at home dedicated to that job than using my phone...)
i wouldn't have done it without tptoolbox, it was boring and time-consuming before that ...
I couldn't get the HP toolbox to recognize the novacom driver / service, even though I could run acme and communicate / query the TP.
Anyways, was running 4.4.2 can't remember which build. Updated to the jscullin 4.4.4 6/25?
Reading through the forums I didn't really see many instructions for this update path. Ended up copying the install .zip to the TP and ran install .zip from clockworkmod in the boot menu. Figured they were both 4.4.x and this shouldn't be an issue.
After the .zip load the TP booted and updated android with no problems. Optimized apps ect. When I logged in I had a few app updates but nothing major.
Impressed with 4.4.4 so far. I use chromecast to watch football (american), and it works flawless. Not a Netflix fan so no comment, although I think it would work fine since watchespn / YouTube cast w/o issue.
I don't use Bluetooth so...
Seems stable, not a single freeze or anything like that.
Just wanted to say that a "dirty" flash from 4.4.2 to 4.4.4 works fine, at least for me and I didn't need to restore all my apps etc.
Been running android on this puppy for a few years now. Had access to an "early" device.
Kindly,
Tpnsd.
[email protected] said:
Just finished installing the Toolbox (way to go JCS!!), just wanted to note that I received a "NOT COMPATIBLE DEVICE" error when following the instructions from JCS Post #64. When I used a WebOS doctor that I already had, there was no problem.
The doctor listed in post #64 is "webosdoctorp305hstnhatt.jar" which gave me the error
The doctor I used is "webosdoctorp305hstnhatt.jar" which worked fine
not sure what the difference is, but wanted to post this for non-devs like me.
Click to expand...
Click to collapse
Oops, I used the link for the Touchpad 4G instead of Touchpad Wifi. Corrected to include both appropriately labelled.
Thanks.
---------- Post added at 11:49 AM ---------- Previous post was at 11:46 AM ----------
shumad1 said:
Hi, all. After unmounting the media volume (post copy of recovery, gapps and rom to ttinstall folder) I see the following: Checking Install files...
1 logical volume (s) in volume group "store" now active
No supported recovery file found. Aborting.
My ttinstall folder contains:
cm-11-20140705-UNOFFICIAL-3.4_kernel-tenderloin.zip
gapps-kk-20140105.zip
update-TWRP-jcs-dm-tenderloin-20140512.zip
I'm assuming the last is my recovery. I've done the complete data reset three times, with the same issue. If I choose reboot, I get:
Selected: 'boot'
Loading ' /boot/uImage-2.6.35-palm-tenderloin'...FAILED
BOOT FAILED!
Any idea on what's going on? Is there a "standard" recovery file I should try instead to make this work? Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Please try the version of Touchpad Toolbox (v41) I just released in this post:
http://forum.xda-developers.com/show...&postcount=293
Note that you will need to use one of the new Recoveries linked from that post.
If you still have problems with that version of TPToolbox, let me know in this thread.
jcsullins said:
Oops, I used the link for the Touchpad 4G instead of Touchpad Wifi. Corrected to include both appropriately labelled.
Thanks.
---------- Post added at 11:49 AM ---------- Previous post was at 11:46 AM ----------
Please try the version of Touchpad Toolbox (v41) I just released in this post:
http://forum.xda-developers.com/show...&postcount=293
Note that you will need to use one of the new Recoveries linked from that post.
If you still have problems with that version of TPToolbox, let me know in this thread.
Click to expand...
Click to collapse
No worries.......you did an awesome job on this project........just wanted to help where I could. BTW, what is your background that makes it possible to create these projects? I am a mechanical engineer with some programming experience in visual basic, C, FORTRAN 77 (yeah, I know pretty old). Where should I start training myself to be able to help the community (and, of course, have some fun)? Thanks again for your hard.......donation is on the way......
Sent from my TouchPad using Tapatalk
I also have a low post count but I'd like to say thank you for the tool. It's worked flawlessly for me a couple times so far.
Error using hp toolbox v41
Hello;
I am completely new here and was trying to repair my 16 GB HP TP via other JCS post and forums on youtube, rootzwiki etc. but no success get my touchpad repairs.
recently I found JCS new toolbox v41. and downloaded it. it looks very awesome and easy to use. Thanks JCS for making it easy for people with little tech background......
However, when I run new toolbox v41 on my tp. I got following errors.
1) When I tried to use complete data reset option I get following error
Error: Invalid partition info: end-gap greater than 1 percent of mmc
2) When I tried to use Create WebOS Volume option, It failed again with following error:
>>> Obtaining existing Volume size….
Determining volume size….
Problem w/ vgchange –ay
Error: volsize all failed rc=1
I downloaded CWM DM and Non DM ...and copy files on Palm, Inc. Folder and re-run the toolbox again...but got the same error as above.
can someone help, what should I do next? or if someone direct me which thread I should have to follow?
I had read many many thread on rootzwiki ..still no success yet.... thought HP toolbox v41 can assist me... but still need guidance..
mgul said:
Hello;
I am completely new here and was trying to repair my 16 GB HP TP via other JCS post and forums on youtube, rootzwiki etc. but no success get my touchpad repairs.
recently I found JCS new toolbox v41. and downloaded it. it looks very awesome and easy to use. Thanks JCS for making it easy for people with little tech background......
However, when I run new toolbox v41 on my tp. I got following errors.
1) When I tried to use complete data reset option I get following error
Error: Invalid partition info: end-gap greater than 1 percent of mmc
2) When I tried to use Create WebOS Volume option, It failed again with following error:
>>> Obtaining existing Volume size….
Determining volume size….
Problem w/ vgchange –ay
Error: volsize all failed rc=1
I downloaded CWM DM and Non DM ...and copy files on Palm, Inc. Folder and re-run the toolbox again...but got the same error as above.
can someone help, what should I do next? or if someone direct me which thread I should have to follow?
I had read many many thread on rootzwiki ..still no success yet.... thought HP toolbox v41 can assist me... but still need guidance..
Click to expand...
Click to collapse
Go back to the OP for touchpad toolbox and load that version. V41 is experimental and not for nube's like us. The version in the OP should work fine for you.
Sent from my TouchPad using Tapatalk
Just used this works great Thanks for all the hard work .
Anyone experienced the tp toolbox completely ignoring vol up/down and home button input? It loads up fine but i cant use it...
einstein910 said:
Anyone experienced the tp toolbox completely ignoring vol up/down and home button input? It loads up fine but i cant use it...
Click to expand...
Click to collapse
Nope, have used it a couple of times now and no volume button issues. Are you running it from your PC or the standalone version bootable from MoBoot?
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
BornReady_ said:
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
Click to expand...
Click to collapse
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
nmyshkin said:
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
Click to expand...
Click to collapse
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
BornReady_ said:
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
Click to expand...
Click to collapse
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
nmyshkin said:
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
Click to expand...
Click to collapse
Yes, I booted with the power cable connected, I tried on being connected to the laptop and power wall as well. I also held down the N button, which is why I got to the Boot Menu.
Bear with me
Are you sure you got the SD card version of TWRP?
Yes, 100% sure.
BornReady_ said:
Yes, 100% sure.
Click to expand...
Click to collapse
Well that was interesting! We're "live" apparently
I want to help but I'm not digixmax... I'll bet he has an idea. Wait for him to get back to you while I rummage around.
Lol, thanks for the help anyways though. I will have to wait for digixmax.
Wow, everytime you mention digixmax, he replies. He just privated messaged me in return.
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
I'm sorry, I should have been more precise. I don't know if it will help, but this is the TWRP recovery image I used successfully when I tried this process. That's v. 2.8.6.0
digixmax said:
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
Click to expand...
Click to collapse
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
nmyshkin said:
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
Click to expand...
Click to collapse
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
BornReady_ said:
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
Click to expand...
Click to collapse
I've already shut down my computer for the night. I'll have a look at the size that an image of the card would be. Maybe that's the easiest way if there's room in my dropbox. If you've read through the CM11/12 thread you know I ran into problems and if you were to look at the CM10 thread you'd find me floundering around there also, so I know how frustrating it can be. And then suddenly it just works.
I'll let you know tomorrow.
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
digixmax said:
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
Click to expand...
Click to collapse
You are totally correct. I enabled Windows Explorer to display file-name extension and the TWRP recovery file turned out as "recovery.img.img" I am going to try it out now and reply with if it works or not.
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
BornReady_ said:
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
Click to expand...
Click to collapse
Is flashing_boot file on your SD card correctly named "flashing_boot.img", and not "flashing_boot.img.img"?