i installed 4.1.2 first time w/ROM GUIDE how to install HP TP the easy way but after used for several days, got error "unfortunately, android kybd stopped".
i followed instruction on this website to uninstall used ACMEUninstaller2(and previous version) but screen displayed hp logo without any lines running up the screen as it supposed to.
i did at least 4-5 times w/same results.
Once i left screen at HP logo till battery drain and TP came back w/ANdroid 4.1.2 still alive but no kybd.
HELP, please!
thank you,
-t
Sorry for the issues you are having.
I used JCSullins TP Toolbox to do my installs. Do you want to keep web OS or install just Android?
gtallmadge said:
Sorry for the issues you are having.
I used JCSullins TP Toolbox to do my installs. Do you want to keep web OS or install just Android?
Click to expand...
Click to collapse
i used CM10 Android 4.1.2 10 JB (20131019)cminstall package Download and follow the guide.
i found lots of replies in forum mentioned about after ACMEUinstaller2, run WEBOSDoctor. i did that and it seemed like the app fixed not only WEBOS(?) but also able to uninstalled after that.
But now I'm trying different packages in easy way guide and wasn't able to install any of them: either after reboot hanged at flash screen till battery drained or some conmponents missing(installed same package you mentioned above).
thanks for your response,
-t
tpham56 said:
i used CM10 Android 4.1.2 10 JB (20131019)cminstall package Download and follow the guide.
i found lots of replies in forum mentioned about after ACMEUinstaller2, run WEBOSDoctor. i did that and it seemed like the app fixed not only WEBOS(?) but also able to uninstalled after that.
But now I'm trying different packages in easy way guide and wasn't able to install any of them: either after reboot hanged at flash screen till battery drained or some conmponents missing(installed same package you mentioned above).
thanks for your response,
-t
Click to expand...
Click to collapse
So, do you want to keep web OS? The advantage of using tptoolbox is that you can really start over, clean cache and and do a complete data reset which wipes previous installs of android and web OS.
For what it is worth, this is what I did as I found web OS to be almost unusable for me. I really liked the OS but the lack of support and available apps made it unsuitable for me. So, installing Android has made the TP relevant again for me and my family. We have Android on three TP's and are not looking back. We do have other Android devices but now the TP is once again our favorite and most versatile device. Kudos to all the developers here for giving life back to the TP.
Here is the link to the easiest install guide for using tptoolbox: http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
this TP belongs to my sister and she prefers to have both OS. While i was trying to install Android to her TP, i did successfully install 4.2.2 to two other TPs.
i think this troublesome TP is unique!
do you have another way to install android while keeping WebOS?
thx,
-t
tpham56 said:
this TP belongs to my sister and she prefers to have both OS. While i was trying to install Android to her TP, i did successfully install 4.2.2 to two other TPs.
i think this troublesome TP is unique!
do you have another way to install android while keeping WebOS?
thx,
-t
Click to expand...
Click to collapse
I don't want to keep WebOS, because HP touchpad hardware is near the end of life, and WebOS is useless and slow.
I used JCSullins TP Toolbox to help me to install CM11, and currently I stay with the CM11 by JCSullins.
Since CM11 is still under development, I have encountered several CM11 common issues on my HP touchpad, but luckily I found the workarounds for them.
If you don't want to deal with trouble, you should stay with WebOS, CM9 or CM10.
i finally got it to work. i suspected the pkg i downloaded @home missed some bits. i downloaded @work and it worked fine.
i also google checksum app and verified the new pkg.
everything is GREAT!
thank you for all your help.
-t
Related
I have a Touchpad running CM 10, but I still like running WebOS every now and then. I've been getting an update notification in WebOS and would like to apply it, but I'm not quite sure how I would do this with a dual boot TP. I know I've done this before a few years back but I can't remember what I did. Anyone here updated their WebOS partition and remember how?
First you MUST remove android using acmeuninstaller before allowing webOS to update.
The latest version I thought is 3.0.5 which can be downloaded as webOS Doctor 3.0.5 and installed at your convenience. I also think webOS updates can be turned off.
What version are you currently running?
kitsunisan said:
I have a Touchpad running CM 10, but I still like running WebOS every now and then. I've been getting an update notification in WebOS and would like to apply it, but I'm not quite sure how I would do this with a dual boot TP. I know I've done this before a few years back but I can't remember what I did. Anyone here updated their WebOS partition and remember how?
Click to expand...
Click to collapse
I'm pretty sure you don't have to remove android to update, at least I didn't. You will lose moboot, but you can reinstall it easily.
I updated OTA, but you can also run the appropriate webos doctor (webos is at 3.0.5).
In webos, just follow the on screen instructions to update. After it's done, reinstall moboot using acmeinstaller3. I think you can also install it using recovery (I use cwm).
If you haven't already, update your moboot to 0.3.8, and your cwm to the 6.xx one. Here's the link for cwm (use the 12/15 one) : http://goo.im/devs/jcsullins/cmtouchpad/recovery
Here's the link for moboot : http://goo.im/devs/jcsullins/cmtouchpad/testing
There are several good guides here which a search will turn up. Also, do a little reading over at webos nation forum, there's lots of good information there too.
Good luck.
Thanks for the answers. I believe sstar is correct, removing Android is necessary. The update always fails because it can't get itself into the appropriate recovery. No big deal I guess, just do a nand backup, remove it, update, redo the acmeinstaller3 and restore.
I'm still running 3.0.4, it's been that long since I've used it. I really don't know why, there's nothing fundamentally wrong with WebOS, and when I'm on it I like it, it's just I'm so used to Android, I guess.
kitsunisan said:
Thanks for the answers. I believe sstar is correct, removing Android is necessary. The update always fails because it can't get itself into the appropriate recovery. No big deal I guess, just do a nand backup, remove it, update, redo the acmeinstaller3 and restore.
I'm still running 3.0.4, it's been that long since I've used it. I really don't know why, there's nothing fundamentally wrong with WebOS, and when I'm on it I like it, it's just I'm so used to Android, I guess.
Click to expand...
Click to collapse
I did some reading over at webos nation forum and you don't have to remove android. You do have to remove the preware patches and whatever kernel you installed (if any).
Once updated you can reinstall the patches and kernel.
I strongly recommend you do some reading over at webos nation forum, it's really informative.
Like I said before, you will lose moboot, but all your android files will still be there. Once you reinstall moboot, you can get back to android.
Edit : to remove the patches, use EPR (you get it in preware). Once you run it, it removes the patches and also itself once it's done.
Webos is great. I actually like it better than android, but the app selection is severely limited, android does a lot better in that respect.
When i did my updates from 3.0.2 to 3.0.4 and then 3.0.5 I never removed any of my preware patches, although they were gone afterwards and had to be re installed. All of which were done before I even new what android was.
sstar said:
When i did my updates from 3.0.2 to 3.0.4 and then 3.0.5 I never removed any of my preware patches, although they were gone afterwards and had to be re installed. All of which were done before I even new what android was.
Click to expand...
Click to collapse
I think the update to3.0.4 was the only one that messed with boot folder and partitions.
Sent from my GT-P3110 using xda app-developers app
can't believe my decrepit and all-but-abandoned nook color is humming along with kitkat. succulent is the bomb. he rightly credits all the developers he relied on, but he put it all together. download and flash the cwm update, then the rom and gapps and voila! i used a pc for downloading and the nook data cable and the "send to" option in downloads. great thanks to all.
I agree, it's great that so many people put in so much effort to bring Kitkat to the aging NC.
I do have one question. Would someone be so kind as to post a link to a suitable CWM for CM11 on the NC? I have 6.3.0.1 on mine, and can't find a link to anything newer for the life of me.
EDIT: I found it, but can't post a link because I'm a n00b. Google for cm11-encore-recovery.zip_links to find it on the Cyanogenmod wiki.
I'm booting CM11 for the first time now.
I have today reinstalled my two Nook Color from scratch with CM11 running on SD-card.
“generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8b” loaded on two” SanDisk Mobile Ultra Class4 16GB” with “win32diskimager-v0.9-binary”
“cm-11-20140131-NIGHTLY-encore” installed as OS, went fine. Runs fast & nice.
“gapps-kk-20140105” installed trough SD card recovery PowerOn & then “n” . There was Android upgrading-something 6/6 installed during boot after the recovery. But I cannot find any PlayStore and so on. But the Gmail icon is there now & maybe something more.
dfarquhar said:
I agree, it's great that so many people put in so much effort to bring Kitkat to the aging NC.
I do have one question. Would someone be so kind as to post a link to a suitable CWM for CM11 on the NC? I have 6.3.0.1 on mine, and can't find a link to anything newer for the life of me.
EDIT: I found it, but can't post a link because I'm a n00b. Google for cm11-encore-recovery.zip_links to find it on the Cyanogenmod wiki.
I'm booting CM11 for the first time now.
Click to expand...
Click to collapse
Best versions are here: http://forum.xda-developers.com/showpost.php?p=49915965&postcount=34
Homer
I have two (2) Nook Color devices. As I wrote above I reinstalled them both today with CM11. I got a problem except for the GAPPS that dosen't install the Play, it is that I coulden't use them at the same time with Wi-Fi. I found out that both have the same MAC address. Dosen't CM11 KitKat use the chip MAC address? Is it a software MAC?
How do I change so the CM11 use the Wi-Fi chip burned in original MAC address?
frav.se said:
“gapps-kk-20140105” installed trough SD card recovery PowerOn & then “n” . There was Android upgrading-something 6/6 installed during boot after the recovery. But I cannot find any PlayStore and so on. But the Gmail icon is there now & maybe something more.
Click to expand...
Click to collapse
That's odd. I used the same build and have the Play store and other Google apps. Maybe try re-flashing the gapps zip?
I found the 11-29 build to run much faster than any other 4.x version (no surprise) but occasionally would do odd things like change icons. These things happen of course with experimental builds. I'm upgrading to 1-31 now.
frav.se said:
I have two (2) Nook Color devices. As I wrote above I reinstalled them both today with CM11. I got a problem except for the GAPPS that dosen't install the Play, it is that I coulden't use them at the same time with Wi-Fi. I found out that both have the same MAC address. Dosen't CM11 KitKat use the chip MAC address? Is it a software MAC?
How do I change so the CM11 use the Wi-Fi chip burned in original MAC address?
Click to expand...
Click to collapse
I don't know how you could have installed them with the same wifi MAC address... when I look at my advanced internet settings on NC it says MAC address is not available... however when I look in my router it is seeing the hardware MAC address.
So CM isn't even reading the /rom/MACaddress file for the information... however it is not returning a MAC on polling either... perhaps this is why play store is giving you issues.
Now I have reinstalled both NCs again. This time it seems like it worked out well.
Regarding the MAC problem. It could maybe be like this, that I accidently did the first time install & boot with the same NC device. But anyhow I think it is strange if it doesn't use the h/w MAC as the default choice.
This time I did like this:
1. “generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8b” from http://forum.xda-developers.com/showthread.php?t=1941858 loaded on two” SanDisk Mobile Ultra Class4 16GB” with “win32diskimager-v0.9-binary”
2. "cm-11-20140131-NIGHTLY-encore.zip " from http://download.cyanogenmod.org/?device=encore&type=nightly
3. Removed Hangouts.apk and GoogleHome.apk according to this http://forum.xda-developers.com/showpost.php?p=49942253&postcount=529
4. Installed "gapps-kk-20140105-signed.zip" from http://wiki.cyanogenmod.org/w/Google_Apps (This time it was 20 "things" installing & not 6 like last time)
Upgraded both to "cm-11-20140201-NIGHTLY-encore.zip" , that worked out fine. Have installed approx 150 apps, more or less no problems more than that Play Store sometimes shuts down.
So I'm satisfied so far. Thank you to the Devs.
Upgraded both ny NCs today to "cm-11-20140202-NIGHTLY-encore.zip". On one of the devices it went fine, but on the second one something got wrong. The "desktop" is now not possible to slide sideways & the time/weather widget is not there. On the first one I got google maps, gmail & play store Icon on the first desktop screen, but they are not on the second device.
Anyone having a clue of what could have happened & how to solve it?
Tried to downgrade to 0101, but then i only got "Unfortunately, Trebuchet has stopped", so I upgraded to 0202 again. Then I don´t get this error, but the home screen is still not working properly.
If I understood that error message right it has something to do with the homescreen cache. And it is the home screen that is strange in my case. How do I reset the Trebuchet cache?
---------- Post added at 03:48 PM ---------- Previous post was at 03:36 PM ----------
Managed to solve it. Went in to settings/apps/all/Trebuchet, cleared data & voila the home screen is now working again.
can someone upload a movie about the performance of the tablet under kitkat? I gave my nook to a family member and want her to have a faster system, but don't want to delete all her data if it's not worth it
speedfreak007 said:
can someone upload a movie about the performance of the tablet under kitkat? I gave my nook to a family member and want her to have a faster system, but don't want to delete all her data if it's not worth it
Click to expand...
Click to collapse
If your running CM7, it's still snappier than CM11. CM11 is a huge improvement over the CM10.x versions, take up a smaller footprint on the Nook and has nice functionality.
Runs smooth...
...I have only been playing around with CM11 for a couple days now, but enjoy the overall OS and it out ways the minor performance loss in many ways.
- You can use YouTube off of Play, but might not have smooth HD viewing and will need to watch in non-HD
- You can manually install the newest Crackle TV (Play will not allow it due to incompatibility warning), but have to turn on Disable HW overlays (Always use GPU for screen compositing) to have it work properly
- You can either use the older 1.8.1 NetFlix flawlessly or use the workaround on here
That's about it for me. Everything else seems to work ok. haven't tried any performance or graphic intense games yet.
2-05-2014 Nightly
Anyone get this nightly to load?
f1jim
Nevermind...It's working now.
Kitkat on Nook Color
I flashed CM11 on my NC last week.
Android 4.4.2, but kernel 3.0 - it doesn't seem to be Kitkat.
To my phone running 4.2.2 with kernel 3.4 that higher than NC flashed CM 11, called Kitkat.
Sorry if I am wrong, but that's all I've found.
"I have no technical skill, so just a thought that higher is better"
stevedat said:
I flashed CM11 on my NC last week.
Android 4.4.2, but kernel 3.0 - it doesn't seem to be Kitkat.
To my phone running 4.2.2 with kernel 3.4 that higher than NC flashed CM 11, called Kitkat.
Sorry if I am wrong, but that's all I've found.
"I have no technical skill, so just a thought that higher is better"
Click to expand...
Click to collapse
Each device has its own version of kernel. Yours is right.
Sent from my BN NookHD+ using XDA Premium HD app
Kitkat 4 Nook Color
leapinlar said:
Each device has its own version of kernel. Yours is right.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks.
Anyway, CM 11 on my NC running very well. A big thank to CM developers & Nookies Dev.
Ak, only one thing bothering me that I cannot use my new external keyboard with it(Cover with usb keyboard). It worked on CM 7.2 with an 3rd tool.
Issue with recognizing external keyboard on NC running CM 11 Nightly
Does anyone know how to use an external keyboard (usb keyboard cover) on Nook Color running CM 11?
In past I could use the usb keyboard cover when using CM 7.2 on my NC with Nook Color tweak.
Last week, I decided to upgrade my NC to Kitkat by flashing CM 11 Nightly and from that point I haven't been able to use my usb keyboard cover with my NC any more.
Any tips, suggestions ... plz help.
Thanks.
stevedat said:
Does anyone know how to use an external keyboard (usb keyboard cover) on Nook Color running CM 11?
In past I could use the usb keyboard cover when using CM 7.2 on my NC with Nook Color tweak.
Last week, I decided to upgrade my NC to Kitkat by flashing CM 11 Nightly and from that point I haven't been able to use my usb keyboard cover with my NC any more.
Any tips, suggestions ... plz help.
Thanks.
Click to expand...
Click to collapse
I don't think Bluetooth is working yet. Not sure if it will get fixed, but it is in the change log that it is not working. Otherwise I am very happy with the performance. I just got my nook off craigslist and it is running much better than I ever imagined it could!
frav.se said:
Now I have reinstalled both NCs again. This time it seems like it worked out well.
Regarding the MAC problem. It could maybe be like this, that I accidently did the first time install & boot with the same NC device. But anyhow I think it is strange if it doesn't use the h/w MAC as the default choice.
This time I did like this:
1. “generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8b” from http://forum.xda-developers.com/showthread.php?t=1941858 loaded on two” SanDisk Mobile Ultra Class4 16GB” with “win32diskimager-v0.9-binary”
2. "cm-11-20140131-NIGHTLY-encore.zip " from http://download.cyanogenmod.org/?device=encore&type=nightly
3. Removed Hangouts.apk and GoogleHome.apk according to this http://forum.xda-developers.com/showpost.php?p=49942253&postcount=529
4. Installed "gapps-kk-20140105-signed.zip" from http://wiki.cyanogenmod.org/w/Google_Apps (This time it was 20 "things" installing & not 6 like last time)
Click to expand...
Click to collapse
So, using what you did, and the guide it came from. Does this root and install a CWM? Or do you need to do all those steps first. Just a bit confused as how to take my stock Nook Color and get it to CM11
Never mind; got it figured out and up and running. This process did root and get it up and running on CM11 for me.
Late last night I went to fix a touchpad that was handed to me, was told that the Android install was started, but had messed up. If I fixed it I could keep the touchpad.
So, i wandered over here and followed RolandDeschain79's how to install android thread, using the novacom,exe route with ACMEUninstaller2 and ACMEInstaller5. After running both of these (and placing the Cyanogen9 Mod on the tablet... i followed the instructions to the T). I got Android to run on it. BUT there was a problem! I got a bunch of notices @ initial startup, (Like 3). I don't remember what the other 2 were, but the biggest problem was the android keyboard would not function. Thinking that it would fix it, I went ahead and re-did what I had already done, running ACMEUninstaller2 and ACMEInstaller5. When I was in the middle of doing this the battery died (wish the stupid thing would just feed off power from my PC when it's plugged into it but apparently not). Now, I'm stuck in a bootloop (i think).
what does it do?:
The WEBOS boot screen, the little circle w/ HP in it? It just sits there. Sat there the entire time it was plugged in, didn't show me it was charging or anything. When I force it to shut off (hold power button and home key) it'll sit there 4 10 seconds or so, then turn itself right back on. I CAN GET INTO RECOVERY MODE however.
What I have done since then:
1. left it sit on the charger for about 7 hours... should be fully charged I hope.
2. Re-ran ACMEUninstaller2
3. Re-ran ACMEInstaller5
my thoughts were that if I can get an older ROM to work on it, I can upgrade to the most current from there.
HELP!!!!
Any ideas would be appreciated. This is the first tablet I've messed with, actually the first tablet I've owned and I'd really like to fix it...
Thanks in advance!
The easiest and most simple means of installing Android is with TP Toolbox. Follow the advice and instructions in the developers forum, you will have to do some reading to understand what you are doing.
I also am listing a link that I think is clear on the install:http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
As for the ROMS, there are a number to choose from. I have jcsullins installed on several TP's as well as pac-man ROM on another. Please take your time to read and decide.
Also, using toolbox will require that you use the naming convention for gapps as outlined in the toolbox thread.
Thank you. I followed the instructions on that site and the touchpad is working excellent.... Minus one glitch thus far: the camera works on boot, but as soon as you go to take a photo the whole screen digitizes and the touchpad loses connectivity with the camera. Is there an easy fix for this?
What ROM are you using? Also, which gapps did you install? Please be as specific as possible.
The ROM I am using is cyanogen 11 and I downloaded the gapps from the same page. The tablet upgraded itself last night and after that everything works great. It said something like upgrading apps, and reinstalled all the apps I had put on it. I'm playing with it as much as possible, making sure it acts like it should.
Thanks 4 all the help thus far
more issues
okay guys I am using invisiblek's cyanogen 11 and gapps... still have an issue with the camera I randomly acting up. it will work and then it won't. I have no clue where to even start with this. the build is from June of 2014. I do have an update available, I don't know if that will fix it but I do not have my laptop available at this current moment, so I cannot try it. Any ideas?
Are you reading the posts in the forum thread for that particular ROM? Other people using it may have encountered and fixed the issue.
I would invite you to read information about the various ROMS in the developer section as issues such as you are describing are
usually addressed and fixes or work arounds are presented.
I do not use the particular ROM you have installed but run other ROMS on several touchpads and do not have the problem you describe.
like an idiot I have not read the other threads regarding this particular CyanogenMod... I will look into them.
Thank you.
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Greasemonkey50701 said:
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Click to expand...
Click to collapse
You can't bypass moboot, and what you're proposing is going to ultimately cause you problems. But if you must, the easiest way to do what you want is to reduce the moboot timeout so that it goes directly to boot quickly. Create (if it's not already there) or edit (if it is) a file named moboot.timeout and put the number of seconds you want moboot to wait before booting CM. You can do that with a root browser like ROM ToolBox lite, or you can do a terminal session and type in:
Code:
su
mount -o remount,rw /boot
cd /boot
echo "1" >/boot/moboot.timeout # will set timeout to 1 sec (defaults to 5)
sync
What problems would this cause? Call me stupid (and I am sometimes) but i really don't forsee any problems caused by doing this...
I think Shumash already answered your question.
You need moboot to boot into Android.
Android is Linux based and Linux requires the use of a bootloader.
The best you can do is to shorten the time out before it boots.
In spite of the best advice given to you...it is your touchpad and you are free to do what you choose.
Even if that means borking it for good.
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Greasemonkey50701 said:
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Click to expand...
Click to collapse
You were clear enough, but seem to have some misunderstanding of what the sequence is. On boot, moboot times for a default 5 seconds and then automatically boots into Android, unless you screw with it by touching buttons or making selections. If you want it to do that faster, change the timeout as I suggested. You do not need to take anything off of it, and in fact, doing so will cause you grief eventually. If you take CWM off, and want to update your ROM, create a nandroid backup, clear the caches, or do any other low level stuff, you won't be able to. If it's booting into CWM (which you haven't said it does yet), then the moboot.default file has been changed. It should contain the word "CyanogenMod" (w/o the quotes) to boot directly to CM/Android. Use a root browser to edit or recreate it.
So, I've heard about the recent Lollipop ROM for TouchPad, and this made me consider getting out my TouchPad. I'm curious though, if the guides and such account for having a comparatively ancient Android/recovery installed, from ICS - possibly even a beta. Do I just reflash those with little troubles, or something else? Do the modern ROMs co-exist with webOS? I might get a small nostalgia trip from seeing how much better webOS multitasks than Android.
ampharos said:
So, I've heard about the recent Lollipop ROM for TouchPad, and this made me consider getting out my TouchPad. I'm curious though, if the guides and such account for having a comparatively ancient Android/recovery installed, from ICS - possibly even a beta. Do I just reflash those with little troubles, or something else? Do the modern ROMs co-exist with webOS? I might get a small nostalgia trip from seeing how much better webOS multitasks than Android.
Click to expand...
Click to collapse
First, modern Roms can coexist with webOS, however at this point I don't how how useful webOS is anymore. You may want to give TPToolbox a try and wipe webOS altogether. You can find great tutorials for this online.
Nonetheless, if you choose to keep webOS, you can flash a newer recovery from your old recovery, which will allow you to install lollipop or marshmallow. This will coincide with webOS. Although, if you have trouble installing a new recovery through the old recovery, then you can install a new recovery through TPToolbox, and from thereon flash a new rom.
As a former WebOS user I found that I stopped using my TP after HP shut down the servers in March. For a phone I jumped to BlackBerry and enjoy it all but for a few missing appps. My TP just sat in the charger. So this week I downloaded jstoolbox and installed Lollipop on it. So far so good an I am actually using it again.
It isn't WebOS but it is being used again.
Hello, I recently found an old HPTP lying around that is running Android 4.1.2 through CyanogenMod, it also has webOS and ClockworkMod installed.
I am thinking of mainly using the touchpad to play games on so I no longer have to use my phone to do so, and most require Android 8.
My question is, will the Android 8.1.2 release for the HPTP be able to run games from the play store properly? I have never done this before so I am asking before I attempt to, and realize later on that what I am looking to use the TP for won't work.
This is the guide I was going to follow to get Android 8.1.2 running: https://forum.xda-developers.com/hp-touchpad/help/how-to-install-android-7-x-hp-touchpad-t3512182
Thanks.