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
Related
Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ORIGINAL POST (from May):
This is a work in progress.
TWRP (Team Win Recovery Project) 2.1 by TeamWin is an alternative recovery (instead of ClockworkMod) that is a good companion for Goo Manager. See this video for more info.
This is an experimental, mostly untested build of TWRP2 for entertainment purposes only. USE OR ATTEMPT TO USE ENTIRELY AT YOUR OWN RISK. It is intended for those who are willing to risk any and all damage, loss, and STD infection to their hardware, data, person, and associates resulting from this software. Do not attempt to use unless you understand and accept these risks.
Please note this is using the still-being-developed 3.x kernel.
I am including the raw .imgs which can be fastbooted or used on an SD (rename recovery.img.sdcard to recovery.img and put on SD in place of the existing version). Which I don't recommend doing of course, given the disclaimer above. Remember I don't have an NT so I haven't run this... ever.
Finally, this has not at all been put through any kind of paces. That's for you, assuming all the risks, to do. And report it back here for everyone's benefit.
Thanks to dees_troy, eyeballer and demetris_I & frustro for testing this. I'm busy the next few days, so I'm volunteering demetris_I, who has it running, to answer anyone's questions per his availability
twrp-2.1-nt-2012-05-17E-fullofbugs.tar.gz
History
6/12/12 - updated first post.. No binaries yet.. Can someone make one?
5/17 -
Updated 3.0 kernel to support new 512GB NTs (untested)
Updated twrp codebase to latest
Newer cm9 stuff as well
5/17B&C
Use cmdline from u-boot.bin to determine max ram size.
fix device showing up as "B" to "NookTablet"
5/17D&E
I can't remember. But it's betterer.
Has anyone successfully flashed this yet? And can anyone offer up the steps in a more-in-depth way?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Well... there's always update.zip
I haven't tried it, but I'm guessing if you've installed fastboot to your computer, this should work:
1. boot into cyanoboot and choose Fastboot from the menu.
2. On your computer, navigate to where recovery.img is and enter into the terminal
fastboot flash recovery recovery.img
Or... maybe someone could whip up a quick update-twrp2-nt-2012-5-14.zip maybe?
I guess that someone might as well be me. This is intended for use with an existing cwm recovery. This will flash to emmc...maybe.
update-twrp-2.1-nt-2012-05-14-fullofbugs-emmc.zip
MD5: 337269fa77017150325d398216a6dd3c
Thoroughly and completely untested. I really don't know if it will even install, and if it does, if it will work. See all disclaimers above, plus make up some additional ones yourself.
Edit: See below about a possible issue with possible difficulties accessing the external SD card. Internal /emmc seems to work consistently. Looking into it, but if you want to help debug this, that would be much appreciated. Just knowing what works or doesn't work and log samples (dmesg via adb) would be great.
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
It will replace cwm.
Rom doesnt matter , they reside in different partitions.
Cyanoboot is all you want if anything goes wrong or/and CWM/TWRP from sd card so you can dd the recovery.
SilentStormer said:
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Should replace it completely. I say should because if you do this with the update.zip, you will be the first one to try it.
Oh, Mister_Argent is trying it on IRC...
The Zip seems to work! Android boots fine, and it's entirely possible to get into TWRP via Cyanoboot. This might just be me, but the terminal seems to lock up...
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
So we can still flash stuff through emmc?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Indirect gave me this command to flash recovery via terminal emulator and it worked out nicely
dd if=/recovery.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
where "/recovery.img" is the file path/file name of the recovery image
Recovery looks nice. I'll do some more playing with it later when I have time.
fattire said:
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
Click to expand...
Click to collapse
No issues with external sd it just take some seconds to mount, is not instant but it will mount.
8gb NT. Successfully flashed internally; will test, log and provide feedback on any issues.
The zip file name is overly long and CWM doesn't like it. Renaming to something shorter solves the issue.
In my experience with other android devices, it is normally recommended you wipe 'dalvik cache' whenever changing / updating kernel. Perhaps this step will avoid some issues for people.
Edit: Flashing gapps update via Goo Manager results in failure of rom to load after Cyanoboot screen. I did not choose to wipe dalvik / cache in Goo Manager. Also unable to access Cyanoboot via N. Screen appears but does not seem to respond and automatically boots emmc (blank screen).
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
demetris_I said:
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
Click to expand...
Click to collapse
I could not access twrp as already stated, because Cyanoboot did not respond to button press. I've managed to get access to CWM via sdcard and reflashed another gapps. CM9 still will not load.
Next, I plan to wipe everything and flash CM9 anew.
Edit: Still won't boot. Looks like I have a brick to fix.
Edit2: Flashing CWM internally got everything working again. Cyanoboot would previously go automatically to loading from emmc; there was no delay / opportunity to press N to access the menu. Now the delay occurs and I have access. CM9 also loads.
Edit3: Reflashed TWRP internally again. It's not working on 8gb NT. It doesn't break Cyanoboot or prevent CM9 from loading, but any attempt to load TWRP results in a black screen.
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
demetris_I said:
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
Click to expand...
Click to collapse
I flashed the above emmc zip via cwm internal
I have adb working, however fastboot seems to require a separate driver to work in windows. I've searched the forum and have not found a clear answer.
I'm guessing the 3.0 kernel doesn't have support added for the 8gb nts yet. I guess maybe I could look into that...
Sent from my HTC Vision using XDA
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Recovery is separate from the rom. You'll be fine. I have it running on my 16GB.
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"?
Years ago, I installed CyanogenMod onto an old Samsung phone with no trouble. A few weeks back, I was given a Barnes & Noble Nook Tablet 16 GB. The UI is pretty limited and I don't want a B&N account, so I thought I'd unleash the beast and install the full Android OS on it.
I read through various HOWTOs including "Install CM for acclaim" from the CyanogenMod Wiki.
I have formatted an 8 GB SD-card with a single FAT32 partition which has been flagged as bootable.
I downloaded and extracted CWM-based-Recovery v5.5.0.4 to the SD-card.
The device booted to recovery mode OK.
I first tried to install "cm-13.0-20160629-NIGHTLY-acclaim".
It failed with the well known OTA update / Status 7 error.
Reading up on this, the main advice is to try an earlier version, maybe even the last stable release.
I then tried "cm-10.2.1-acclaim" which is from all the way back in 2014.
It failed with just "E: Error in /sdcard/cm-10.2.1-acclaim Status 0.
A web search didn't return anything useful.
Next up, I tried the next release CM11: "cm-11-20140210-SNAPSHOT-M3-acclaim".
I got the same failure as with CM10.
Finally I tired the last snapshot before the latest nightly releases: "cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NI-acclaim"
This time it is back to the Status 7 failure.
Considering all the successful HOWTOs I have read and the procedure is basically the same in each one and I have tried searching these forums.
I can only assume I am missing something really basic.
I checked on whether I need to root the device, as I had to with the old Samsung phone, but it seems the B&N Nook Tablet has root access by default.
So, can someone please help?
Thanks!
alloydog said:
Years ago, I installed CyanogenMod onto an old Samsung phone with no trouble. A few weeks back, I was given a Barnes & Noble Nook Tablet 16 GB. The UI is pretty limited and I don't want a B&N account, so I thought I'd unleash the beast and install the full Android OS on it.
I read through various HOWTOs including "Install CM for acclaim" from the CyanogenMod Wiki.
I have formatted an 8 GB SD-card with a single FAT32 partition which has been flagged as bootable.
I downloaded and extracted CWM-based-Recovery v5.5.0.4 to the SD-card.
The device booted to recovery mode OK.
I first tried to install "cm-13.0-20160629-NIGHTLY-acclaim".
It failed with the well known OTA update / Status 7 error.
Reading up on this, the main advice is to try an earlier version, maybe even the last stable release.
I then tried "cm-10.2.1-acclaim" which is from all the way back in 2014.
It failed with just "E: Error in /sdcard/cm-10.2.1-acclaim Status 0.
A web search didn't return anything useful.
Next up, I tried the next release CM11: "cm-11-20140210-SNAPSHOT-M3-acclaim".
I got the same failure as with CM10.
Finally I tired the last snapshot before the latest nightly releases: "cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NI-acclaim"
This time it is back to the Status 7 failure.
Considering all the successful HOWTOs I have read and the procedure is basically the same in each one and I have tried searching these forums.
I can only assume I am missing something really basic.
I checked on whether I need to root the device, as I had to with the old Samsung phone, but it seems the B&N Nook Tablet has root access by default.
So, can someone please help?
Thanks!
Click to expand...
Click to collapse
The CWM version you are trying to use is too old, I think, even for CM 10.2
Thanks, I thought it might be something like that, but one tutorial said it didn't matter. I have been trying to find a newer version of ClockworkMod, but can only find image (img) files that don't seem to work: I used the gnome-disk-utility 3.10.0, UDisks 2.1.3 to write the image (recovery.img extracted from flashable_CWM_6.0.4.8_chrmhoffmann.zip), but it just makes an empty SD-card - that is, when I check the card with GParted, there are no usable partitions.
I have just found "cm-13.0-20160629-NIGHTLY-acclaim-recovery.img" but I cannot find any clear instructions what to do with it next.
Do I just write the image to the SD-card with the image writer? Because then I get a warning that the target disk is over7 GB bigger than the image and end up with an empty SD-card.
alloydog said:
Thanks, I thought it might be something like that, but one tutorial said it didn't matter. I have been trying to find a newer version of ClockworkMod, but can only find image (img) files that don't seem to work: I used the gnome-disk-utility 3.10.0, UDisks 2.1.3 to write the image (recovery.img extracted from flashable_CWM_6.0.4.8_chrmhoffmann.zip), but it just makes an empty SD-card - that is, when I check the card with GParted, there are no usable partitions.
I have just found "cm-13.0-20160629-NIGHTLY-acclaim-recovery.img" but I cannot find any clear instructions what to do with it next.
Do I just write the image to the SD-card with the image writer? Because then I get a warning that the target disk is over7 GB bigger than the image and end up with an empty SD-card.
Click to expand...
Click to collapse
I can't speak to the CM 13 since I haven't gone there (yet). I followed the excellent instructions by @digixmax for CM 10.2 and (more recently) CM 12.1. In some cases there is no working CWM version and you have to use a version of TWRP. Late in the second thread there are a variety of file combinations people found that worked for them. But the instructions--if followed exactly--work, or at least they did for me.
TWRP worked perfectly for me. However I had to flash CM10.2 before I could go higher, otherwise trying to flash CM13 made TWRP reboot outright with no warnings while on stock. I'm sure since it was on Android 2.3 it needed to have the newer partition table to install to.
----------------------- Thread MODIFICATION LOG -----------------
Shout out to Nevertells2 and DoubleStuff who both worked hard on this documentation in 2017. ( Some of which still remains )
Date:03/10/2017 Users: DoubleStuff/Nevertells2
Modification Description: Initial Release.
05/25/2019 DoubleStuff
Major changes in 2019: updated broken ROM/GApps by including HP_TOUCHPAD's master list of ROM/GApps, also fixed the YouTube broken link, made many additions to the documentation as per the changing landscape of the HP Touchpad development, most notably HP_TOUCHPAD's HpTp Universal Optimize Swap Settings and boot.img file.
07/08/2019 DoubleStuff
Created a Main Menu, with 2 options 1) Wipe All and 2) HP ToolBox.
8/3/2019 DoubleStuff
Implemented HP_TOUCHPAD's ROM_Reducer flash files.
8/27/2019 DoubleStuff
On the 2nd Post of this thread I added DoubleStuffs annotated journeys.
8/27/2019 DoubleStuff
On the 3rd Post of this thread I added HP_TOUCHPAD's advanced topic of the HP TOUCHPAD Novacom Repair Android Tool.
----------------------- Previous Zip Statistics -----------------
"The Original"
Obsoleted doubleStuff_v03.zip 3/19/2017 - 5/25/2019 ( RIP )( 797 days )( 7876 downloads )( 53306 views )
Avg. 9.87 downloads/day
"Double Stuff II"
Obsoleted DoubleStuff.2019.zip 5/25/2019 - 7/8/2019 ( RIP )( 045 days )( 372 downloads )( 3140 views )
Avg. 8.26 downloads/day
----------------------------------------------------------------------
Introduction:
In this "new" ( circa 2019 ) method of "starting from scratch", or called "clean installing", the user will flash various ZIP files depending on the ROM version user wants to install.
The actual install of Automatic_Wipe_All_and_Create_Android_with_Swap_Partition.zip ( boot.img ) will be done by the the script TPTB_WipeAll_TWRP_v02_win.bat. Wipe_All creates a 500 Mb swap partition, and re-creates the system, cache, media and data partitions with sizes of 2200 Mb, 200 Mb, 500 Mb, and "rest of memory" respectively, also automatically installs version 3.2.1-0 of TWRP which is required for the other ZIPs.
Boot partition is always 32 Mb, its a fixed size.
To be clear: this method will erase everything, even WebOS and makes the HP Touchpad 100% Android. It will also create new media, cache, data, system and SWAP partitions, and make the HP Touchpad work as a tablet ( laptop with a touch screen ), not a smartphone in Android.
Thoughts about the video:
The Video is now semi-obsolete, because alot has changed since 2017. So you must follow the instructions in this updated thread, but the video helps because if you understand the video you will understand the instructions in this thread. The Video below is Installing Nougat, but you can use this method for ALL VERSIONS of Android since 4.4 just use the proper ZIPs.
https://www.youtube.com/watch?v=KDu1bocZHqw
Assumption:
This method assumes you already loaded and have working TP Toolbox v0.42. ( w/Novacom and Java )
--- if you don't have TP Toolbox installed on your PC please watch the video in RolandDeschain79's link from 0:00 to 2:15 RolandDeschain79Link
======================================================================
Steps to success for loading any version of Android since 4.4:
Perform the following steps on a PC to prepare it for load:
I. Download the NEW DoubleStuff.7.2019.zip:( click link below )
Download DoubleStuff.7.2019.zip
DoubleStuff.7.2019.zip contains these two key files:
1. TPTB_WipeAll_TWRP_v02_win.bat
2. uImage.WIPE
Download and extract, and place both files in the same directory as your working tptb_v42_win.bat on your PC.
II. Select and Download which version of Android ROM, Gapps and other zips you want.
Locate and download the ZIPs: I will link to HP_TOUCHPAD's Master List of Zips: ( see Master list link below ), but you can also find ZIPs in other XDA HP Touchpad threads too.
Its best to put your downloaded ZIPs into a storage folder that you have created on your PC, purely for organization.
#1 ) ROM
#2) Pick one of these three Settings files for this #2 ZIP install: These files are in the "ALL files for this ROM" zip, then look under a folder of the same name, and then select the frequency zip of your choice.
-- MAX_Kernel_Ramdisk_build_prop_Settings ( Latest HpTp_MAX_Universal_Optimize_Swap )
-OR-
-- Stock_Kernel_Changed_Ramdisk_build_prop_Settings ( HpTp_Universal_Optimize_Swap )
-OR-
-- Original_ROM_Settings ( Use the Tablet with phone settings, no swap partition )
( The first two are the magic behind the performance and speed, because these settings enables Android to use the swap partition, the third is the original settings for the ROM and you will have better battery performance. )
All the Universal Optimize Swap Settings files provide the same settings and kernel, the difference is the preset CPU frequency. As per the Boost settings always start with 1674, and after that is working good, you can try to flash a higher frequency for speed like ( 1728, 1782 or 1836 ), and you don't have to re-flash all the ZIPs again, just the UOSS file from TWRP recovery. If it freezes screen, or keeps rebooting just go back and flash lower frequency, Because those symptoms are telling you that your particular HP TOUCHPAD can't handle the higher speed.
#3) ROM Reducer ( Optional ) These files are in the "ALL files for this ROM" zip, then look under the folder with name "ROM Reducer" then out of the 3 zip files in the selected folder, first go with the ROM_reducer, later if you want to permanently remove the features/apps, or restore the features/apps, you can use the "Remove" and the "Restore" zip files.
Essentially this HP Touchpad ( circa 2011 ) has around 650 MB of free RAM (Memory), this is relatively low, so the ROM Reducer flash file "removes" some Android Features and System Apps to give the old Touchpad some extra needed RAM. So in theory this will make for a faster experience.
#4) GApps
Select platform ARM and the android version that matches ROM and the variant you want, Pico is recommended. The goal is to keep the system "lean and clean", and by doing this you will get the best performance and efficiency.
#5) SuperSu v2.82 ( Optional )
ROMs have system Read and Write enabled, download and flash SuperSu v2.82 if you want root access.
#6 ) Latest TWRP ( Optional, but if you want and/or need a different version of TWRP other than 3.2.1-0, then you need to download one. )
==========HP_TOUCHPAD's Master Link: Get ZIP ( #1, #2, #3, #4 here )===========
Note: Once you click link, you have to press page down 3 times to get to the Master List of Zips.
Find all Android version: Rom, GAPPS, HpTp MAX Universal Optimize Swap Settings, and more links as per HP_TOUCHPAD here:
================Get ZIP ( #5 here )=============================
***You can Download and Flash the latest SuperSu zip to ROOT your device***
Root access with SuperSu v2.82
http://www.supersu.com/download
================Get ZIP ( #6 here )=============================
This "latest and greatest" TWRP for ALL VERSIONS OF ANDROID.
Download Permanent TWRP Recovery.
FLINTMAN-TWRP-3.2.1-0-03-15-2018.zip
Stick with the package you select, don't mix and match versions, and stay with WIFI version unless you know better.
Set all ZIPs that you have downloaded into the storage folder on your PC for now, we will need them later.
III. Touchpad/PC Execution steps:
Boot into WebOS Recovery ( giant USB symbol ) with cable connected to PC.
Run the custom script TPTB_WipeAll_TWRP_v02_win.bat:
It will give you the option of running the TPTB where you can perform some maintenance steps. Most users will select '1' to run WIPEALL from Main Menu.
III. Touchpad/PC Execution steps: continued
Most users will START here, after pressing '1' in Main Menu.
Continue ( press "c" ) with the TPTB_WipeAll_TWRP_v02_win.bat, it will then load the uImage.WIPE, you should see a quick blue flash, and an orange header with some white text. Wait until the orange header disappears, it will then automatically reboot. ( about 2 minutes ).
At reboot, select Recovery on moboot menu, then press home key.
Wait, and you will see the automatic load of 3.2.1-0 TWRP recovery.
Wait, and you will see Touchpad drive mounted on your PC.
TWRP recovery automatically creates a folder in the /data/media directory called TWRP, on the Internal SD card ( data ).
IV. TWRP Install steps:
( If screen falls asleep, and power and home buttons don't respond, tap screen )
Once in TWRP Recovery, go to your PC which is still connected via cable to TouchPad:
Locate the storage folder on your PC where you stored your ZIPs.
Copy the ZIPs: ( drag and drop )
1) ROM, 2) Universal Optimize Swap Settings 3) ROM Reducer 4) Gapps, 5) SuperSu and 6) Permanent Recovery zip files into the /Touchpad/InternalStorage/TWRP mounted Touchpad volume.
( P.S. actually you can copy the zips anywhere in 'Internal Storage' or 'Micro SDCard' Touchpad mounts, as long as you know where to find them on your Touchpad, I am just giving you the default location for simplicity sake )
2) Once copy is complete, you can disconnect the USB cable from the PC and Touchpad.
3) These zips will then show up in the /sdcard/TWRP or /data/media/TWRP directory on your Touchpad.
4) Select INSTALL from TWRP, drill to /sdcard/TWRP directory, then load in this specific order ( pressing 'add more zips' between loads )
== ROM,
== HpTp Universal Optimize Swap Settings,
== ROM Reducer,
== Gapps,
== SuperSu
== Recovery TWRP
then swipe to flash.
It will take awhile for the system to flash these zips ( about 5 mins ) until the reboot option shows up.
press reboot system button
At Moboot menu I selected "boot Evervolv" your menu item might be a different name depending on the ROM you installed.
During my experimental testing I loaded Evervolv Nougat and it took about 15 additional minutes until I got to the Android Start screen after "boot Evervolv" selected. Mileage may vary.... but soon your HP Touchpad will be in the promised land of Android with swap.
Advanced Topic #1:
DoubleStuff's Journeys to Novacom Repair Android Tool and Universal Authority: ( with annotated pictures!! )
Journey #1: How files get populated to /boot.
Journey #2: into HP RAMDISK: Using /boot from uImage
Journey #3: to Novacom Repair Android Tool: How are the icons made
Journey #4: Exploring Planet Universal Authority
Journey #5: RAM Memory Stress Test
...
..
Advanced Topic #2:
HP Touchpad Novacom Repair Android Tool
Hello Touchpad users, if you think your HP TOUCHPAD is bricked, your probably wrong and with the tools below you maybe able to fix your HP TOUCHPAD and make it like new again. Read the guide, and download the ISO file, now remember this is an advanced topic, its not for kids. Trix are for kids.
click HERE for guide
click HERE to download ISO file
...
..
Doublestuff, bringing this to this thread since I am using your instructions to get this far.
After using the 4/13 nightly and getting setup wizard has stopped I tried the 4/6 as indicated below.
The steps I have taken are to use tptb_v42_win.bat for the toolbox to wipe the data then resize volumes to
--Media: 1024 MB,
--Cache: 200 MB,
--System: 1312 MB,
--Data: the rest of the memory
Then after shutting that down and bringing up the big USB symbol using the volume and power button again to run TWRP_TmpLoad_v03_win.bat and copy the files below into the TWRP folder on the touchpad.
ev_tenderloin-7.1.2-nightly-2017.04.06.zip
open_gapps-arm-7.1-pico-20170415.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip
Once the files were copied over I disconnected from the PC and added to the install in the order above.
The install indicates no MD5 so a check is skipped and seems to proceed to install each of the three zips fine. When I get to the end of that there are two buttons (one to wipe cache/DavLik and the other to Reboot). I tried both with and without the wipe cache before the reboot with the same results.
After the Evervolve logo with the cycling colored letters goes for a few minutes it gets to the setup screen, clicking on either copy settings or start new setup give the error "Setup wizard has stopped, Open app again" then "Setup wizard keeps stopping, close app".
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
Any ideas for something else to try are appreciated.
----------------------------------------
This part I dont think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
W_three said:
Doublestuff, bringing this to this thread since I am using your instructions to get this far.
After using the 4/13 nightly and getting setup wizard has stopped I tried the 4/6 as indicated below.
The steps I have taken are to use tptb_v42_win.bat for the toolbox to wipe the data then resize volumes to
--Media: 1024 MB,
--Cache: 200 MB,
--System: 1312 MB,
--Data: the rest of the memory
Then after shutting that down and bringing up the big USB symbol using the volume and power button again to run TWRP_TmpLoad_v03_win.bat and copy the files below into the TWRP folder on the touchpad.
ev_tenderloin-7.1.2-nightly-2017.04.06.zip
open_gapps-arm-7.1-pico-20170415.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip
Once the files were copied over I disconnected from the PC and added to the install in the order above.
The install indicates no MD5 so a check is skipped and seems to proceed to install each of the three zips fine. When I get to the end of that there are two buttons (one to wipe cache/DavLik and the other to Reboot). I tried both with and without the wipe cache before the reboot with the same results.
After the Evervolve logo with the cycling colored letters goes for a few minutes it gets to the setup screen, clicking on either copy settings or start new setup give the error "Setup wizard has stopped, Open app again" then "Setup wizard keeps stopping, close app".
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
Any ideas for something else to try are appreciated.
----------------------------------------
This part I dont think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
Click to expand...
Click to collapse
Go have a read at this page in the DevsBase forum if you haven't already. It is discussed that there have been problems with the setup wizard.<Mod Edit: Link removed. Please don't redirect members to other mobile forums. Thanks!>
Also, I see in the discussion there that the nightly builds are now 4/13 so you might try that date build and see if the problem has gone away. I also saw discussed that some folks there were installing older builds that did not have the setup problems and then using TWRP to flash the newest builds. Otherwise, from what you posted, you are doing everything right.
NT
W_three said:
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
This part I don't think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
Click to expand...
Click to collapse
As long as the Media is greater than 1000 MB it should be OK.....
Essentially the program TWRP_TmpLoad_v03_win.bat loads TWRP temporarily by using a novacom command to load uImage.TWRP to the HP Touchpad, but you still have to download and have as one of your 3 zips something like this FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip, so that you can have a permanent load of TWRP after all is said and done.
Hey guys! Went through all of these steps and got it to boot! However, after it booted for quite a while, it started up the setup wizard, and immediately stops whenever you choose an option, whether it be "Set up as new" or "copy your data."
Is it something I've done wrong? Any help would be appreciated!
Seatreader said:
Hey guys! Went through all of these steps and got it to boot! However, after it booted for quite a while, it started up the setup wizard, and immediately stops whenever you choose an option, whether it be "Set up as new" or "copy your data."
Is it something I've done wrong? Any help would be appreciated!
Click to expand...
Click to collapse
No your not doing anything wrong, the new nightly builds are going through a particularly buggy phase the last few builds. I am assuming you used the 4-19 nightly. Lets try an earlier Testing build.
If you have time, just for kicks and for testing purposes can you try again but use Flintmans latest testing 3-25 ROM instead of the Evervolv Nightly.
Try this ROM and lets see if it fixes the issue:
http://evervolv.com/static/builds/testing/Queo/ev_tenderloin-7.1.1-testing-2017.03.25.zip
If you notice the user "w_three" had the same issue in an earlier post on this thread....
okay I'll give that a go tonight! I noticed on the release page forums they were talking about how you had to dirty flash the newer roms on and figured that was my problem.
=UPDATE=
Ran as per the instructions with a nice clean install and it booted fine! Takes forever to boot and get through the" finishing touches" but it looks like it's working fine!! Four days ago this tablet was bricked!
Thanks for all the help!
After letting this rest for a few days I decided to give it another go.
Used the 3/25 zip you posted above DoubleStuff and finally past the set up error. Going through it now. Thanks for posting that Rom.
W_three said:
After letting this rest for a few days I decided to give it another go.
Used the 3/25 zip you posted above DoubleStuff and finally past the set up error. Going through it now. Thanks for posting that Rom.
Click to expand...
Click to collapse
Great! W_three, that you finally got it working, from what I have been reading on devs-base, Open Gapps are only running through 7.1.1, and as of April 4th (4/4) Evervolv nightlies have switched to 7.1.2. ( see pic below ) Some people have a theory that this is causing the set-up wizard to break. To get around this issue, some people have been "clean" flashing an older 3-25 ROM see link to that in post #8 ( or in theory anything before 4/4 nightly ), then "dirty" flashing the newer ROMs on top of that. I am just reporting on what I read, not sure how accurate it is.
See in below screenshot how name changes from 7.1.1 ( green ) to 7.1.2 ( red ).....just sayin'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just know that this Nougat ROM is still only in Beta, so there will be bugs and lagginess.
As Nevertells2 would tell anybody, JC Sullins KitKat 4.4.4 ROM is probably the most stable.
Setup Wizard fails
My Setup Wizard fails and I see the note below:
*NOTE: as of 4/4 since start of 7.1.2, if your having issues with setup wizard after the install you might want to flash this older ROM instead ( before 4/4 ), then dirty flash a newer ROM
How do I perform this?
How do I flash with a older ROM (before 4/4) and then dirty flash a newer ROM? Can you elaborate?
Thank you in advance.
xdakzhf2d said:
My Setup Wizard fails and I see the note below:
*NOTE: as of 4/4 since start of 7.1.2, if your having issues with setup wizard after the install you might want to flash this older ROM instead ( before 4/4 ), then dirty flash a newer ROM
How do I perform this?
How do I flash with a older ROM (before 4/4) and then dirty flash a newer ROM? Can you elaborate?
Thank you in advance.
Click to expand...
Click to collapse
Well underneath that red letter explanation in the Original Post, is a link to a 3-25 ROM, flash that using the alternative method described in OP. That is called a clean install.
Then once you get that going, you can dirty install the current 5-8 ROM, by selecting this once tablet is running:
Settings->About Tablet->Evervolv Updates->Nightly Tab->Refresh, then download the zip, and boot into recovery and flash it. If you don't understand this terse explanation, I have pasted RolandD's How to dirty flash and root video below ( from 1:19 to 3:17 is Dirty Flash )
Dirty Flash Instructions
Hi, Ive ran each step as instructed twice, just to be sure. both times I get only an external sd card selection, no internal card or data selection once files load and I run twerp it installa yet I get a failed to mount data invalid argument. what am I doing wrong?
deafasheck said:
Hi, Ive ran each step as instructed twice, just to be sure. both times I get only an external sd card selection, no internal card or data selection once files load and I run twerp it installa yet I get a failed to mount data invalid argument. what am I doing wrong?
Click to expand...
Click to collapse
Hello deafasheck, I have been following you on these boards for years, and you always get errors and issue that are different from the norm. LOL
In fact you even call J.C. Sullins by an unusual name ( JC Sullivan ) LOL, but I have seen Nevertells2 correct you a few times, so I think we are good to go there.
As far as your issue, did you load the 3-25 ROM first? Then try to dirty flash the latest nightly? I would like to know more details on the procedure you used. But you maybe in luck, because I think there is another thread today that has a similar ( mount and volume issues ) and RolandD gave him a answer and a few links...
Look HERE at post #1094
Missed a step.
Hi DoubleStuff, yeah I'm way out of my league, but have learned so much in forum, I found out what I done wrong. I didn't move file size in data only moved cashe and system to as close as could to instructions. it fixed right up once I put data size, I noticed cam still inverted, does new ROM resolve that? I'm going back and dirty flash that ROM I ove the size if this, it doesn't take up much space has less bloatware and I use UC browser which is so so Philz kk is best I have tried . but I'm gona toy on this one Ive almost mastered this touchpad insyallations even learning codeing, just not yet.. I do dislike the home launcher, so used to having one like the one in kk or nova. Ive not bricked mine yet! was worried for awhile. but any thing I need to know is on here . thanks for the reply..
im still learning how to post specs of tablet. JC Sullin huh? yeah, Im good on typos. dang laptop mouse jumps around.. well here we go, going to dirty flash newest rom, wish me luck.. thanks..
DoubleStuff said:
Hello deafasheck, I have been following you on these boards for years, and you always get errors and issue that are different from the norm. LOL
In fact you even call J.C. Sullins by an unusual name ( JC Sullivan ) LOL, but I have seen Nevertells2 correct you a few times, so I think we are good to go there.
As far as your issue, did you load the 3-25 ROM first? Then try to dirty flash the latest nightly? I would like to know more details on the procedure you used. But you maybe in luck, because I think there is another thread today that has a similar ( mount and volume issues ) and RolandD gave him a answer and a few links...
Look HERE at post #1094
Click to expand...
Click to collapse
deafasheck said:
Hi DoubleStuff, yeah I'm way out of my league, but have learned so much in forum, I found out what I done wrong. I didn't move file size in data only moved cashe and system to as close as could to instructions. it fixed right up once I put data size, I noticed cam still inverted, does new ROM resolve that? I'm going back and dirty flash that ROM I ove the size if this, it doesn't take up much space has less bloatware and I use UC browser which is so so Philz kk is best I have tried . but I'm gona toy on this one Ive almost mastered this touchpad insyallations even learning codeing, just not yet.. I do dislike the home launcher, so used to having one like the one in kk or nova. Ive not bricked mine yet! was worried for awhile. but any thing I need to know is on here . thanks for the reply..
im still learning how to post specs of tablet. JC Sullin huh? yeah, Im good on typos. dang laptop mouse jumps around.. well here we go, going to dirty flash newest rom, wish me luck.. thanks..
Click to expand...
Click to collapse
Hello deafasheck, I am glad your learning and taking the advice of Nevertells2 which is "read, my friend, read!!"
Yes the Stock Camera is still inverted, but haven't you heard? That if you go to google play store and download "Open Camera" app it works fine in Nougat, let me know what you think of it. I am glad you figured out your own problem that is telling me you are learning quite a bit since you were a "newbie" in 2014!! :good:
OK deafascheck I wish you luck in your dirty flash download? And your experiment with "Open Camera" and hope you learn how to code at least in BAT and VBS files, because when Oreo ( Android "O" ) comes out we will need to tweek the code for this Alternative method again!! I am doubling down that its called Oreo, hence my Avatar.
Thank you so much, yes got to learn code and terminal commands. on the subject of dirty flash, is that same as loading the via tptb as I did with the permanent files when Initial install ?
deafasheck said:
Thank you so much, yes got to learn code and terminal commands. on the subject of dirty flash, is that same as loading the via tptb as I did with the permanent files when Initial install ?
Click to expand...
Click to collapse
deafasheck, defasheck, defasheck, come on now we have been studying "dirty flashes" since you were a "newbie" in 2014, and our friend RolandD has made many videos on it....in fact in this ROM alternative thread in post #13 at the bottom of the post is a good video that explains "dirty flashes"....learn it, love it, live it!!!
Good Luck in all your learning Deafasheck!!! :highfive:
POST #13 for deafasheck learning dirty flashes.
Videos don't help much, I'm deaf as heck.. and getting lost in the steps.. from what I recasll dirty flash is asop I did one as I had in the original install ie placed in twerp flashed from twerp. that worked as far as I know? I'm trying to find the super user link I seen earlier, once I get ROM and SU I'm gonna get the camera app. thanks..