Related
Hi,
Just wanted to ask if anyone know how to completely uninstall CM9 from touchpad.
I know there is acme uninstaller for cm7, but I haven't found acme uninstaller 2.
I need to wipe it completely clean, get rid of moboots, cwm.
I tried boot into CWM, Format System (in Mounts and Storage menu) and Format cache. But when I reinstall CM9, it remembers all my google passwords and all my apps are there, suggesting that it was never completely wiped.
Any insights will be greatly appreciated. I want to completely wipe off everything since I am having problem with my speaker (no sound is coming out of it) since yesterday. I am not sure what is the issue, but I wanted to revert to factory state to troubleshoot. But even when I do the secure wipe from webOS OS, when I reinstall CM9 alpha 0.6, all my login info and apps are there, suggesting that not everything was wiped clean.
i believe you can still use the old acmeuninstaller. its not cm specific.
Sent from my cm_tenderloin using Tapatalk
Wipe data/factory and wipe cache partition to wipe Google password..... then go to mount and storage to wipe other things.......also cm9 backs up your purchase from market as soon as u put ur Google credentials.
I used acme uninstaller to clean android....I was on classicnerd. So I am sure you can use it too.....
Sent from my Touchpad using xda premium
Anyone have step-by step idiots guide on how to do un-install CM9? I sold my touchpad so I need to wipe Android completely off this TP.
TIA.
-dave
simply dave said:
Anyone have step-by step idiots guide on how to do un-install CM9? I sold my touchpad so I need to wipe Android completely off this TP. TIA. -dave
Click to expand...
Click to collapse
Download ACMEUinstaller
Put it in the same folder where you have novacom.exe (probably c:\program files\palm,inc) (I assume you used this when you installed CM9)
shutdown your touchpad
Press and hold the volume up button and press power button at the same time. You should see a white USB symbol.
Connect the USB cable to your pc and touchpad
Open a command window and CD to the palm, inc folder or If your using Windows 7, go to the Palm, Inc folder, hold down shift key, right click in that folder and choose open command window here.
In the command window type exactly: novacom boot mem:// < ACMEUninstaller
It will then go through uninstalling everything CM9. If you need more help, I think there may be videos on YouTube.
Thanks so much for replying. I should've mentioned that I'm running MAC OSX, so I think instead of my files being in Palm, Inc, they're in opt/nova.
And instead of using the 'command window' I'll be using the 'terminal' but here's where I'm hung up:
I keep getting the "No such file or directory" response.
I remember it took me a dozen or so attempts at install ICS the first time so I'm assuming that the process will be the same this time around.
Anyone with an idea can contribute?
TIA.
EDIT: got it to work using a video on how to INSTALL and I just switched the commands from ACMEInstaller to ACMEUninstaller. I found out I was missing a space in one of the commands.
HTH someone else out there!
http://forum.xda-developers.com/showthread.php?t=1426244 is another great resource for completely removing CM9 (or any other OS that's installed on there - Ubuntu, ClassicNerd, etc). It completely restores your TP to factory default.
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
Click to expand...
Click to collapse
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
zefir738 said:
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yes
spikejnz said:
Yes
Click to expand...
Click to collapse
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
zefir738 said:
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yikes. OTA is supposed to drop today, so hopefully that becomes available soon thereafter. Not sure how long I can survive without my phone.
spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. !
Click to expand...
Click to collapse
I assume you mean the 5.1 update? or did you try to use a 5.1.1 update for some other phone by mistake? if so there may be no easy solution.
I don't accept defeat. Everyone said my data was a lost cause, and that Factory Reset was my only hope. Yeah, well who's copying data off his device right now?
THIS GUY.
I downloaded the firmware, removed the "erase userdata" line from the batch file, and ran it to restore the images and partitions.
I then cleared the cache (again) and rebooted my device.
Back to the 'System UI has stopped' loop
Tried unsuccessfully to send ADB commands to the device
Opened and ADB Shell in Cerberus Dashboard, but kept getting disconnected
Sent an Unlock command in Cerberus Dashboard to my device ... voilla!
UI is still crashing, but Windows is now attempting to install drivers
After trying to manually install drivers for an extended period of time, decided to attempt it on my Mac
BOOM, FS mounts and Android File Transfer is now accessing all the files, even if my display is all jacked!
Next comes the factory reset. I knew there was a reason I installed Cerberus on my non-rooted device.
Fix RTL via ADB
I had this problem on my turbo after reading about a possible fix for snapchat image problems.
After a bit of googling, I came up with this simple fix.
This will only work if ADB Debugging is enabled and your PC is already authorized.
No need for root.
Code:
adb devices
adb shell
settings put global debug.force_rtl 0
reboot
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
AnoraxAudio said:
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
Click to expand...
Click to collapse
If your phone has a secure lock screen, it will not recognize a usb port for file transfer or ADB mode until the password/pin/pattern/etc. has been entered. The Cerberus method described above worked because it was able to meet this requirement. With this in mind, you have the following options depending on your lock screen situation:
1. Insecure lock screen, ADB previously enabled: use the ADB method described above.
2. Insecure lock screen, ADB disabled: Plug in the USB, transfer over your important files, reboot the phone in bootloader mode, select recovery mode, perform a factory reset.
3. Secure lock screen (all cases, assuming you can't unlock it with Cerberus or something similar): Wipe cache through recovery to see if that helps anything. If it doesn't, you can try reflashing the system image via mofo or fastboot to see if that helps anything. If not, bite the bullet and perform a factory reset. You will lose your data.
Now if you have mofo, you might be able to flash a rooted rom that can perform the adb method using a su.d script, but I'm not entirely sure about that.
I did a search and did not find anything so here it goes. I am running KitKat on my HP Touchpad with no issues. However, I was going to try and load the new MM build. When I try to go into the usb mode by either rebooting and selecting webos recovery or by pressing the vol key and power button while it is rebooting, I do not get the usb symbol, but instead I get 4 designs that appear identical except for shades of color. It freezes in that state (or at least a couple of minutes). To get out of it I do the pwr and press menu 15 times to reset. I am used to using the toolbox, but can't get to it this way. Is there a way to get back to the usb from here? PS. Detailed steps are preferred if possible.
You could load TPToolbox onto the /boot partition so you don't need to use pc and webos recovery?
Peace.
chris5s said:
You could load TPToolbox onto the /boot partition so you don't need to use pc and webos recovery?
Peace.
Click to expand...
Click to collapse
Thanks, but I'm not sure which files to place where. I can still get pc access via twrp 2.8.3, but I have wiped the tp of an OS so I'm really messed up.
golfnut22 said:
Thanks, but I'm not sure which files to place where. I can still get pc access via twrp 2.8.3, but I have wiped the tp of an OS so I'm really messed up.
Click to expand...
Click to collapse
So you still have moboot and can boot in recovery?
And can you access the TP using adb?
If you can mount the sdcard thru twrp, can you not copy the files over from the pc to install an os , prob kitkat at this stage?
Otherwise use adb to push the files over, eg using these commands:
adb push /sdcard/name.of.kitkat.rom
adb push /sdcard/name.of.gapps.file
All done whilst in recovery, then use twrp to flash the rom.
Once kitkat reinstalled, use a rooted file manager, eg ES File Explorer to get TPToolbox into the boot folder.
If you manage to get kitkat up and running I'll detail the next steps.
You could circumvent all this by deleting webos from /boot and pushing TPToolbox all using adb but i dont feel confident telling you how to do that, so the 'longwinded' way may be better!
Peace
chris5s said:
So you still have moboot and can boot in recovery?
And can you access the TP using adb?
If you can mount the sdcard thru twrp, can you not copy the files over from the pc to install an os , prob kitkat at this stage?
Otherwise use adb to push the files over, eg using these commands:
adb push /sdcard/name.of.kitkat.rom
adb push /sdcard/name.of.gapps.file
All done whilst in recovery, then use twrp to flash the rom.
Once kitkat reinstalled, use a rooted file manager, eg ES File Explorer to get TPToolbox into the boot folder.
If you manage to get kitkat up and running I'll detail the next steps.
You could circumvent all this by deleting webos from /boot and pushing TPToolbox all using adb but i dont feel confident telling you how to do that, so the 'longwinded' way may be better!
Peace
Click to expand...
Click to collapse
Thanks Chris. I am able to get into moboot. I just now mounted the TP, created a folder called ttinstall (which is what the tptoolbox always used), copied my kitkat rom and gapps into that folder, unmounted the tp, then from twrp ran install for the rom first then the gapp and it all worked. I still may try your way to get to the toolbox, but at least now it is working again. I have had several of these over the years and this is the only one that gives me a weird pattern on the tp when I want to go into recovery. Thanks for the response.
golfnut22 said:
Thanks Chris. I am able to get into moboot. I just now mounted the TP, created a folder called ttinstall (which is what the tptoolbox always used), copied my kitkat rom and gapps into that folder, unmounted the tp, then from twrp ran install for the rom first then the gapp and it all worked. I still may try your way to get to the toolbox, but at least now it is working again. I have had several of these over the years and this is the only one that gives me a weird pattern on the tp when I want to go into recovery. Thanks for the response.
Click to expand...
Click to collapse
The four block weird design or pattern apparently was just substitue picture of the usb symbol as far as I can tell. I was thinking because I did not see the usb symbol, it was not going into recovery, however, the tptoolbox loaded anyways and I was able to perform the changes to ttinstall folder as ususal. I'm not sure why I get that weird pattern instead of the usb symbol, but nervertheless, it worked. I may try MM now.
golfnut22 said:
The four block weird design or pattern apparently was just substitue picture of the usb symbol as far as I can tell. I was thinking because I did not see the usb symbol, it was not going into recovery, however, the tptoolbox loaded anyways and I was able to perform the changes to ttinstall folder as ususal. I'm not sure why I get that weird pattern instead of the usb symbol, but nervertheless, it worked. I may try MM now.
Click to expand...
Click to collapse
Cool! Running flintman's MM build right now, well worth a punt!
Peace.
I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.
1sharpguy said:
I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.
Click to expand...
Click to collapse
Which rom and build of Android 4.4.4 are you currently using?
Try this:
Plug the tablet into the PC with the USB cable. Go to settings/storage/ click the 3 dots in the upper right/USB computer connection.
Switch from Media device to Camera, see if windows detects and installs drivers. Then set it back to media device.
Still no luck with mounting Touchpad
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay
1sharpguy said:
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay
Click to expand...
Click to collapse
Hi have you tried rebooting both the tablet and the PC, sometimes thats necessary. You might also try running the universal novacom installer again now that the tablet is detected here. I tested plugging in the tablet with the rom you're currently using on a virgin windows 10 setup and it worked fine, unfortunately I don't have a windows 7 system to test.
If nothing works you can always transfer the backed up files over the WiFi with a free app WiFi file transfer here
That should take care of your files if you're looking to upgrade with Nougat.
Hope this helps :fingers-crossed:
Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J
1sharpguy said:
Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J
Click to expand...
Click to collapse
No problem, I've got one more thing for you to try. Found this in an older post of mine from 2012, back when I was using windows 7. Give it a try, you can always use the WiFi transfer app but it might take a while to complete. Good luck:good:
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next
Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?
Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.
1sharpguy said:
Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?
Click to expand...
Click to collapse
I'ts probably just a corrupt download, I've read this complaint before. Redownload the Nougat files and reinstall the recovery, rom and gapps.
1sharpguy said:
Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.
Click to expand...
Click to collapse
Wiping a blank partition won't hurt the tablet, its just a bad download. Right under swipe to wipe its says go back to main menu... I could add click the home button to return to the main menu, if you think that would help. This is why I have both a video and a written guide, I'd recommend using both resources simultaneously.
Edit: I double checked the video and I tell you to press the home button and return to the main menu here
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-go back to the main menu and select Install, locate the download folder on the left menu
-select and install the 7.1 Rom and the Gapps package then reboot.
Note: The first boot to android 7.1 can take sometime, Wait for it...
That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!
1sharpguy said:
That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!
Click to expand...
Click to collapse
Congratulations are in order for getting this all done, i'm happy to hear the experience has empowered you with confidence and knowledge. I appreciate the feedback, my guide is aimed at users with little to no experience who just want to keep their HP TouchPad going.
No apology needed I just take my guides seriously and i'm always looking to improve them or fix mistakes. You'll see below I've added portions of this conversations to my troubleshooting section to help other users here. I'm just glad I didn't mess up that step in the video cause you can't fix those, a forum post is much easier to edit.
Nougat is still being worked on but as with any new version of android there will be bugs. Shumashs has an overclocked kernel that can boost the performance of the Evervolv nougat rom. However I highly recommend CM11 for users just looking for a stable and reliable setup. I'm happy we could save your tablet, enjoy it and check back sometime to see how Nougat is coming along.
Edits from my install guide:
Help I get this Error message after installing the Evervolv Nougat rom
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
Solution
-You've downloaded a corrupt file, delete it and re-download the Nougat files.
-Repeat step 10 of the guide, flash the Rom and Gapps package from TWRP recovery.
Can't mount USB drive with CM11 and Windows 7
-Plug the HP TouchPad into your PC with the USB cable
-Go into Device manager. You will see "MTP USB Device" under portable devices.
-Right Click it and select update driver software
-Select Browse my computer for driver software
-Select Let me pick from a list of device drivers on my computer
-Select USB Mass Storage Device then click next to install the driver
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-Click on the TWRP home button(bottom middle) to return to the main menu.
-Select Install, locate the download folder on the left menu.
-Select and install the 7.1 Rom and the Gapps package then reboot.
-After choosing to install the rom click the button to add additional zips, add the gapps package and put a check beside reboot when complete.
Note: The first boot to android 7.1 can take sometime, Wait for it...
I am having trouble with this.
I have tried the universal installer which correctly identifies it as 64bit system. But it fails at download stage, I guess because the file is no longer available where the installer is expecting it.
So then I tried running "NovacomInstaller_x64.msi" by double clicking it, which installs novacomd in my add/remove programs so it seemed to work. But when I run "tptb_v42_win.bat" it says
Code:
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
unable to find device
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
Press any key to continue . . .
The touchpad is definitely on the Web OS recovery screen and connected via USD so I assume it must be to do with drivers not installing properly. Any advice on how I can check drivers?
thanks,
James
jamesking420 said:
I am having trouble with this.
I have tried the universal installer which correctly identifies it as 64bit system. But it fails at download stage, I guess because the file is no longer available where the installer is expecting it.
So then I tried running "NovacomInstaller_x64.msi" by double clicking it, which installs novacomd in my add/remove programs so it seemed to work. But when I run "tptb_v42_win.bat" it says
Code:
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
unable to find device
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
Press any key to continue . . .
The touchpad is definitely on the Web OS recovery screen and connected via USD so I assume it must be to do with drivers not installing properly. Any advice on how I can check drivers?
thanks,
James
Click to expand...
Click to collapse
You can following this thread ( I have you start at post 405 ) where another user called @smithylovestouchpad had the same issue with novacom not connecting to the server, and he was able to use a backup PC and it worked....
https://forum.xda-developers.com/showpost.php?p=80016590&postcount=405
But that being said, your in luck James, because a "regular user" by his own admission, @HP_TOUCHPAD will be posting very soon what he likes to call "HP_Touchpad_Novacom_Recovery_Android", and with this, any user can perform the following tasks with one click on any computer:
1) Load the ToolBox (flash the A6 Firmware)
2) Fix /boot using Create_Boot ( If the Bermuda Triangle shows up ) or the Tablet can not boot.
3) Automatic_Wipe_All_and_Create_Android_with_Swap ( Total Data Reset )
4) If the Tablet needs to be set up only for Android.
5) Change the Ramdisk, make all setting modifications and create a Custom boot file.
HP_TOUCHPAD once said,
If the user ever needs help, the tablet can be setup "completely" by another user, even remotely running Automatic_Wipe to Android, all they need is an internet connection.
The Novacom Driver and Android ADB Shell will be permanent and fully working all the time regardless of the PC being used.
DoubleStuff said:
You can following this thread ( I have you start at post 405 ) where another user called @smithylovestouchpad had the same issue with novacom not connecting to the server, and he was able to use a backup PC and it worked....
https://forum.xda-developers.com/showpost.php?p=80016590&postcount=405
But that being said, your in luck James, because a "regular user" by his own admission, @HP_TOUCHPAD will be posting very soon what he likes to call "HP_Touchpad_Novacom_Recovery_Android", and with this, any user can perform the following tasks with one click on any computer:
1) Load the ToolBox (flash the A6 Firmware)
2) Fix /boot using Create_Boot ( If the Bermuda Triangle shows up ) or the Tablet can not boot.
3) Automatic_Wipe_All_and_Create_Android_with_Swap ( Total Data Reset )
4) If the Tablet needs to be set up only for Android.
5) Change the Ramdisk, make all setting modifications and create a Custom boot file.
HP_TOUCHPAD once said,
If the user ever needs help, the tablet can be setup "completely" by another user, even remotely running Automatic_Wipe to Android, all they need is an internet connection.
The Novacom Driver and Android ADB Shell will be permanent and fully working all the time regardless of the PC being used.
Click to expand...
Click to collapse
Thank you for your help. In the end a combination of installing and reinstalling novacom, restarting, and then plugging in the touchpad to a different USB port finally sorted it out! Then I used your tool to get a ROM etc on there.
Do you have any particular recommendation for a smooth ROM? Doesn't have to be latest version of Android, just something that runs super snooth!
I've installed Dirty Unicrorn Pi but it's a bit laggy. It'll be fine to use fit it's intended purpose, but anything that improves on this would be appreciated.
Cheers,
James
jamesking420 said:
Thank you for your help. In the end a combination of installing and reinstalling novacom, restarting, and then plugging in the touchpad to a different USB port finally sorted it out! Then I used your tool to get a ROM etc on there.
Do you have any particular recommendation for a smooth ROM? Doesn't have to be latest version of Android, just something that runs super snooth!
I've installed Dirty Unicrorn Pi but it's a bit laggy. It'll be fine to use fit it's intended purpose, but anything that improves on this would be appreciated.
Cheers,
James
Click to expand...
Click to collapse
I am curious to what install process you have used to install the Dirty Unicorn Pie? Please respond, its nice to see what install processes some users are using....like what speed of Universal swap settings did you install?, did you use ROM reducer?
In the meantime since you have Novacom and TPTB installed try this process to install maybe Nougat, Oreo or Pie ( with /swap ) or KitKat or Lollipop. Once you read the OP it will direct you to the key Android versions to install on HP_TOUCHPAD's page.
I currently use KitKat and I am fine with that.
https://forum.xda-developers.com/hp...-guide-alternative-method-to-install-t3575861
Hi,
Thanks again for the advice.
I booted in to TPToolbox
Ran Complete Data Reset
Then rebooted to WebOS recovery.
Ran the ."TPTB_WipeAll_TWRP_v02_win.bat" which ended up with me in TWRP.
Then I installed ROM, reducer, gapps, optimiser, recovery, and super user via TWRP and it all raun when rebooted.
Now - another question - my second touchpad - It is currently sitting in the Touchpad toolbox screen. My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
I've already ran "Complete Data Reset" but wasn't able to run the "TPTB_WipeAll_TWRP_v02_win.bat" before my windows PC got Blue Screen of Death!
So now I can copy zips to my touchpad and potentially install android, gapps, recovery using the tool. Then I figured I'd go in to recovery and flash "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition" and start again.
The problem I have is I cannot flash android/recovery/gapps with TP Toolbox as I need a set of three compatible files.. Can anyone point me to a set of such files? Or another way of doing this from TP Toolbox - remember - I can't currently run anything on a PC!
This wouldn't be desperately urgent if it weren't for the fact that my mum wants to use these devices as digital photoframes on Thursday (my grandads funeral!).
Any help would be appreciated.
Currently I have
du_tenderloin-v13.0-20190328-1316-RC.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip
I downloaded a zip from Open Gapps but TP Toolbox says its not compatible and will not flash.
jamesking420 said:
Hi,
Thanks again for the advice.
I booted in to TPToolbox
Ran Complete Data Reset
You don't have to do a Complete Data Reset anymore with the TPToolbox if your going to run TPTB_WireAll_TWRP_02_win.bat or flash Automatic_Wipe_All_and_Create_Android_with_Swap_Partition, it almost seems like your combining three different methods of installs, because TPTB_WipeAll_TWRP_v02_win.bat actually flashes Automatic_Wipe_All_and_Create_Android_with_Swap_Partition in the background and that actually does a complete data reset and 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.
Only use TPToolbox to flash A6 firmware, or look at partition sizes.
Then rebooted to WebOS recovery.
Ran the ."TPTB_WipeAll_TWRP_v02_win.bat" which ended up with me in TWRP.
Then I installed ROM, reducer, gapps, optimiser, recovery, and super user via TWRP and it all raun when rebooted.
Now - another question - my second touchpad - It is currently sitting in the Touchpad toolbox screen. My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
I've already ran "Complete Data Reset" but wasn't able to run the "TPTB_WipeAll_TWRP_v02_win.bat" before my windows PC got Blue Screen of Death!
So now I can copy zips to my touchpad and potentially install android, gapps, recovery using the tool. Then I figured I'd go in to recovery and flash "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition" and start again.
How are you copying zips to your touchpad if your PC does not work? Once you
flashed Automatic_Wipe_All_and_Create_Android_with_Swap_Partition it should get you to a
TWRP Recovery install screen, and you can then flash your zips, no need to use TPToolbox as I said before. Essentially TPToolbox is an "old school" method now. And flashing from TWRP Recovery you don't need compatible zips, that is a bug of TP Toolbox that has not been fixed.
The problem I have is I cannot flash android/recovery/gapps with TP Toolbox as I need a set of three compatible files.. Can anyone point me to a set of such files? Or another way of doing this from TP Toolbox - remember - I can't currently run anything on a PC!
I am curious, even if we point you to a set of such files, how are you going to copy them from a broken PC?, and see above for another way of doing this than from TPToolbox, if you can get into TWRP recovery and have zips on your Touchpad your all set.
This wouldn't be desperately urgent if it weren't for the fact that my mum wants to use these devices as digital photoframes on Thursday (my grandads funeral!).
Any help would be appreciated.
Currently I have
du_tenderloin-v13.0-20190328-1316-RC.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip
I downloaded a zip from Open Gapps but TP Toolbox says its not compatible and will not flash.
Your PIE version above is the latest version, good. But the TWRP 2.8.3 version above is "old school" we are currently at this version FLINTMAN-TWRP-3.2.1-0-03-15-2018, and like I said above the "Wipe All" methods automatically install this latest TWRP version, so no need to flash an "old school" TWRP's afterwords.
Click to expand...
Click to collapse
I made comments above in blue. Here is my summary.
Because your PC broke, like you said "blue screen of death, RAM corruption". This is the very reason that @HP_TOUCHPAD is thinking "outside the box" trying to create an environment that users will not be dependent on a PC anymore. He is in the process of creating this environment, but lets give him time. For by his own admission he is just a regular user, he is learning, experimenting, creating and testing. He is also documenting his findings for all of us to read, learn and apply. So let us do our due diligence and do the best we can.
I have a raspberry pi computer I can use that I can copy files to/from with but I cannot install novacom drivers on it as they are not compatible, as far as I'm aware.
I think I might have found a suitable grouping of ROM/gapps/recovery I can flash with tptoolbox - literally trying again now
jamesking420 said:
I have a raspberry pi computer I can use that I can copy files to/from with but I cannot install novacom drivers on it as they are not compatible, as far as I'm aware.
I think I might have found a suitable grouping of ROM/gapps/recovery I can flash with tptoolbox - literally trying again now
Click to expand...
Click to collapse
This appears to be working to install a KK ROM so I will see if it comes up and I can then run the various flashes.
PS - yes - I did think that running Complete Data Reset and the "TPTB_WipeAll_TWRP_v02_win" was probably unecessary but I'd already run Complete Data Reset before I realised that it probably was overkill. Since this process worked I decided to do it again on the second touchpad, but the Windows PC died before I got the chance. But I had already run the process to load TPToolbox on to the tablet. So I'm now flashing TWRP v2.8.3.0 (data media), a KK ROM, and some KK compatible GApps using TPToolbox.
I hope that after that I can use the recovery I have loaded to install a new ROM, Rom Reducer, SU, Optimiser, GApps, and a more recent Recovery.
jamesking420 said:
snip...
My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
...snip
Click to expand...
Click to collapse
I learn something new everyday, I just googled Raspberry Pi and its some sort of tiny, dual-display, desktop computer. At first I thought it was some sort of "Rogue ROM", I guess we can always learn something new everyday, like last month I learned to play Run Race 3d and I am not even a gamer.
And yesterday I wrote a program in a UNIX language called "AWK"
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
jamesking420 said:
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
Click to expand...
Click to collapse
As per your comment recovery ( again?! ), only flash recovery if you want a different version than what the Wipe all zip flashes ( currently flashes TWRP 3.2.1 ), lets say in the future nobody is updating the Wipe all zip, and it still flashes TWRP 3.2.1, but you see a newer version of TWRP 4.1 compatible with the touchpad, then you can flash that at the tail end, or if your fond of an older version like TWPR 2.8, same thing.
Thanks - yes - I want sure if Wipe all Zip was flashing or just into TWRP so I flashed it again just to be on the safe side. Because it was called wioe ask I thought maybe it wasn't actually flashing anything new, just wiping and booting.
Anyway, thanks for your help it was very useful.
jamesking420 said:
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
Click to expand...
Click to collapse
The HP Touchpad Novacom Repair Android guide:
Click HERE for the Guide and File
A live Linux CD, just boot it from any PC, no installation is need it and have full control of the Tablet for ever !
Thanks for posting this, I'm sure it will be useful for many people.
Unfortunately on the way home from the funeral I left the two touchpads on top of the car as I was putting my kids in their car seats. They feel off at a roundabout which I imagine caused some damage. We turned around and went back for then and someone has nicked them! Ah well!
At 8 years old and costing less than £100 each they'd had a good innings.
Sent from my ONEPLUS A5000 using Tapatalk
jamesking420 said:
Thanks for posting this, I'm sure it will be useful for many people.
Unfortunately on the way home from the funeral I left the two touchpads on top of the car as I was putting my kids in their car seats. They feel off at a roundabout which I imagine caused some damage. We turned around and went back for then and someone has nicked them! Ah well!
At 8 years old and costing less than £100 each they'd had a good innings.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
That is very unfortunate, but there is nothing to worry. The Tablets can be found for $10 anywhere and you maybe surprise to find in a dumpster somewhere.
But it can be revive to its full working conditions and all the files are posted on here, it only takes a click and is done!