[nevertells]

@Nevertells, I know you've a regular user of Maliq's CM10.1 ROM and just want to get your opinion on something.

I have my tablet set to turn off the Wi-Fi when the device is asleep (as long as it's not plugged in) but do not have Wi-Fi Optimisation ticked, it may be just my imagination but it appears that JC Sullin's CM10-20130418 reconnects to Wi-Fi faster then Maliq's cm10.1-20131007, is this just my imagination or is it due to me having installed update-cmtp-ath6kl-v20130722-test.zip / 'Jcsullins newer WiFi drivers V4.5' (Which I've heard it not compatible with cm10.1)

While I was running J.C.'s CM10, I did notice that it seemed to reconnect faster after sleep than Milaq's build. But it's not like painfully slow, a difference in seconds. I don't flash anything extra, just run Milaq's Roms as they come. Right now I'm using J.C.'s 0808 BT build which is based on Milaq's code. J.C. will have to answer your question about the drivers you flashed.

 

[Wellzy4eva]

While I was running J.C.'s CM10, I did notice that it seemed to reconnect faster after sleep then Milaq's build. But it's not like painfully slow, a difference in seconds. I don't flash anything extra, just run Milaq's Roms as they come. Right now I'm using J.C.'s 0808 BT build which is based on Milaq's code. J.C. will have to answer your question about the drivers you flashed.

yeah, I was going to use JC's 0808 BT Build, but after reading about the occasional app compatibility issue, I went for a later build of Milaq's mod (as I rarely use bluetooth)

I have no problem with the few seconds difference, I was just trying to determine if it was only my configuration that was causing it or not.

Thanks for your clarifying feedback.

 

[nevertells]

yeah, I was going to use JC's 0808 BT Build, but after reading about the occasional app compatibility issue, I went for a later build of Milaq's mod (as I rarely use bluetooth)

I have no problem with the few seconds difference, I was just trying to determine if it was only my configuration that was causing it or not.

Thanks for your clarifying feedback.

I tried something that may or may not help you. I installed Milaq's 9/23 nightly, and then I dirty flashed jcsullins 0808 build over the top of that and I don't seem to have any compatibility issues.

 

[Wellzy4eva]

I tried something that may or may not help you. I installed Milaq's 9/23 nightly, and then I dirty flashed jcsullins 0808 build over the top of that and I don't seem to have any compatibility issues.

Sounds like something worth experimenting with.

 

[Wellzy4eva]

I tried it, but there was no Bluetooth access.

 

[michaelahess]

I've lost my mind. I can't get apps to store stuff in the external_sd portion of the memory. I've gone so far as to acmeuninstaller followed by webos doctor. Then I re-installed as follows, still nothing wants to store to the data partition:

Acmeinstaller3 with:

Moboot

CWM datamedia version

Then reboot into webos:

tailor to resize

Then reboot into CWM:

CM10.2 latest nightly

Attempt 2:

Acmeinstaller3:

Moboot

CWM datamedia version

512Mb resize thing

CM10.2 latest nightly

Nothing works. I need a root enabled app to browse to all my data on the external_sd. This is the native area that opens when connected via USB with WebOS. When I try to download or do anything else that saves a file, it goes into the 2Gb system partition thus filling it very quickly. Google Play Music won't work even, says "no space" or some such.

Did I miss something or am I just loosing it here? Thanks for any and all help!

 

[RolandDeschain79]

I've lost my mind. I can't get apps to store stuff in the external_sd portion of the memory. I've gone so far as to acmeuninstaller followed by webos doctor. Then I re-installed as follows, still nothing wants to store to the data partition:

Acmeinstaller3 with:

Moboot

CWM datamedia version

Then reboot into webos:

tailor to resize

Then reboot into CWM:

CM10.2 latest nightly

Attempt 2:

Acmeinstaller3:

Moboot

CWM datamedia version

512Mb resize thing

CM10.2 latest nightly

Nothing works. I need a root enabled app to browse to all my data on the external_sd. This is the native area that opens when connected via USB with WebOS. When I try to download or do anything else that saves a file, it goes into the 2Gb system partition thus filling it very quickly. Google Play Music won't work even, says "no space" or some such.

Did I miss something or am I just loosing it here? Thanks for any and all help!

Question: If you're having so much trouble with CM10.2, then why don't you try Flintmans Evervolv AOSP Android 4.3 Roms? Its the same thing minus one giant headache. No data media CWM and no Partition changing, just one solid Rom and back to business as usual.

I won't even try to address the many issues people are experiencing with this Rom. Many users have reported issues using Play music and this build,ect. Have a quick read of that thread if your hoping for work arounds but I recommend just avoiding the headaches.

Edit: if you want to keep using CM10.2 flash one of these zips to give you more system space for apps. You will still have two separate SDcards showing up. However the author hasn't posted a zip to switch this back so you'd have to use tailor to change this back. Also this won't fix the other issues with apps like Play Music. I also use this app so its a deal breaker for me if it doesn't work.

http://forum.xda-developers.com/showthread.php?t=2477806

 

[michaelahess]

Question: If you're having so much trouble with CM10.2, then why don't you try Flintmans Evervolv AOSP Android 4.3 Roms? Its the same thing minus one giant headache. No data media CWM and no Partition changing, just one solid Rom and back to business as usual.

I won't even try to address the many issues people are experiencing with this Rom. Many users have reported issues using Play music and this build,ect. Have a quick read of that thread if your hoping for work arounds but I recommend just avoiding the headaches.

Edit: if you want to keep using CM10.2 flash one of these zips to give you more system space for apps. You will still have two separate SDcards showing up. However the author hasn't posted a zip to switch this back so you'd have to use tailor to change this back. Also this won't fix the other issues with apps like Play Music. I also use this app so its a deal breaker for me if it doesn't work.

http://forum.xda-developers.com/showthread.php?t=2477806

Thank you Roland! I'm pretty much of the same mind at this point.

I've always been happy with CM and always had more issues with other roms so I guess it's just habit. I'll try one of those others whenever I find the time. As of right now, I'm working around the issues with minimal effort so it's not worth yet another reflash!

Thanks again for the advice, and all the video's!

 

[RolandDeschain79]

Thank you Roland! I'm pretty much of the same mind at this point.

I've always been happy with CM and always had more issues with other roms so I guess it's just habit. I'll try one of those others whenever I find the time. As of right now, I'm working around the issues with minimal effort so it's not worth yet another reflash!

Thanks again for the advice, and all the video's!

Thank you, i'm glad to help :grin: I actually just spent a lot of time updating my CM10.2 info. I hope this does a better job of explaining it to people. I actually ran out of space and had to cut down my post.

CyanogenMod 10.2/Android 4.3 nightlies are now Available (Testing Builds)

Great News HP TouchPad Users! CyanogenMod 10.2/Android 4.3 Nightly Builds are now available for testing. Make a backup before installing this fantastic new Rom. Remember to thank Milaq and please leave feedback and info about bugs/issues in the XDA forum links below.

[ROM] [NIGHTLY] [JB] [4.3] CyanogenMod 10.2 nightlies

Notes: Low battery drain (-4mA), H/W video works, Nightly Builds, audio plays with the screen off, Pie Controls, Inverted Volume contorls, Camera works, No Bluetooth.

Note(Important):This Rom is larger than normal and its developer Milaq recommends increasing the size of the System partition to 500MB. The ACMEInstaller3 only gives us 400MB so he recommends using the WebOS Preware app Tailor to change the partition size to 500MB. Perhaps its time for an ACMEInstaller4 to be created.

Spoiler

Flash this .zip file through recovery to change the partition size to 512MB(Gradular&codycoyote)
How to guide for changing your system, data, and cache partition sizes(how to use Tailor): (Gradular)

Note(optional): Lite 4.3 Gapps package for Download:
I've reduced the size of the gapps package by removing the optional face-lock stuff, Google+ and Quick Search. Both of those apps are rather large and can be installed from the Play Store. This leaves me with a System storage size of 22.79/394MB.
Download Android 4.3 20130812 CM10.2 Lite Gapps: 55.52MB

To further increase the amount of free space I did the following and now I have a System storage size of 38.73/394MB.

How to monitor free System Storage spaceOptional):
-You can use a free app,Quick System Info PRO, to check the size of your partitions and remaining free space, it could be = 387MB or 394MB or 402MB. Any of these is acceptable and indicates that the ACMEInstaller3 worked correctly.
-Having a system size of 387Mib = 400MB and is perfectly normal after using ACME3
-Users report having a size of 394 after flashing to a new Rom. This is also acceptable.

Quick System Info PRO Video Link:
Quick System Info PRO Play Store Link:

How to free up System Storage space on the HP TouchPad(Optional):
I have located about 15.89MB of data we can safely delete. Android in space videos and Phone Ring tones are located @
root/system/media/videos & root/system/media/audio/ring tones.

X-plore File Manager, use this app to delete the files:

Note* X-plore needs to be given Root Permissions by clicking the 3 dots in the corner and choosing configuration. Here check your Root Access settings. SuperUser + Mount Writable, this is what it should say. Next you may need to reboot before it takes effect.

Note(Important): This build also requests that you use a new data media CWM that requires you to change the layout of your partitions. Previously Android and WebOS shared SDcard space in the Media partition (the space you see when transferring data via the USB cable). This build separates the Android and WebOS space by asking you to move free space from the Media partition to the Android Data partition(the place where apps are stored). This new layout will show two SDcards when accessing the tablet from the PC, one for Android and one for WebOS. To make this change you can use either Tailor or a flashable .zip created by XDA member the_ape.

Downloads:

Spoiler

Data Media CWM 6.0.3.6

The_apes Flashable zips

Note: Make sure you have enough free space before flashing one of these zips. There are two types of .zips in a variety of different sizes. one that changes just the Data/Media partition and another that changes both the System and Data/Media partitions. Be sure to choose a zip that best accommodates your TP model 16or32GB.

Note: Once you've made these changes you'll need to use Tailor if you wish to change them back.

Note(Important):The Evervolv AOSP Android 4.3.1 Rom doesn't need these changes and is recommended for all users especially those who are new or inexperienced. This setup should only be done by experienced users!

Known bugs / caveats:

Spoiler

• wifi turns off in suspend -> uncheck "wifi optimisation" in advanced wifi settings
• wifi region code does not stick
• buzzing noise audio on suspend -> toggle (non-working) bluetooth once
• no bluetooth
• Google Play music has problems with this build.

 

[krustybaguette]

I've had my TP for a few months and when I first got it I installed CM9_tenderloin_20130512-nightly. I've been pretty happy with its performance but I hesitated to install Jellybean since everything I read seemed to indicate that JB wasn't ready as a daily driver. I came back and decided it was safe to go ahead and have been working at installing the AOSP 4.3 version of JellyBean. Here's what I did step by step

• nandroid backup ( I had to figure out how that differs from using Titanium Backup)
• used update-cm-tenderloin-system_resize_512-0.4.zip to bump up my partition size
• downloaded and saved ev_tenderloin-nightly-2013.10.29.zip and Evervolv-Queo-3.0.0p1-tenderloin.zip
• Saved the older "release build" just in case something went bad with the nightly.
• downloaded and saved gapps-jb43-20130810-dmd151.zip

After trying to figure out how to use ACME installer, reading up on dirty flashing an AOSP ROM over a cm rom and hanging out in the Evervolv Freenode chat area a couple of times the only reply I got seem to suggest that I could go ahead and boot into recovery wipe cache, wipe dalvik cache, and the install my ROM ev_tenderloin-nightly-2013.10.29.zip followed by installing gapps.

After quite a while everything seemed to come up roses except that not only did BT not work (I expected that but decided I could get by without it by using USB in WebOS or one of my cloud accounts for moving files about. However, not only was BT not working but I couldn't get wifi to work. I searched and read everything I could in the 78 pages of this thead and googled about but nothing got wifi working. So I tried flashing the release build cited above and had even less success.

Tonight I discovered my nandroid backup by connecting my TP to my laptop in WebOS. Once I located it I decided to use CWM recovery to get back to cm9 and that worked fine. So I'm back to square #1 but still want to upgrade to a JB ROM. Tonite was the first time I've used CWM Recovery and that gives me more confidence to go ahead with experimentation. I'd like a recommendation as to correcting any mistakes I made in re: "dirty flashing" and whether or not installing via USB cable from my laptop might yield better results.

I did an AOSP JellyBean upgrade on my old tablet, a Lenovo K1 over a year ago and that was done by installing from the laptop via usb cable.

 

[whitesoxfan]

Hello,

First of all thanks to the Touchpad genuises for creating a great CM10.2 image.

Now, I have recently upgraded the ROM on my Touchpad from CM9 to CM10.2.

I followed all the procedures from A to Z, but I noticed that MoBoot is gone, in which does not let me into the WebOS.

Is there a way how to get this Touchpad to dual-boot (CM10.2 & WebOS)?

Or is there a way to get to WebOS?

Thanks!!!!

 

[RolandDeschain79]

Hello,

First of all thanks to the Touchpad genuises for creating a great CM10.2 image.

Now, I have recently upgraded the ROM on my Touchpad from CM9 to CM10.2.

I followed all the procedures from A to Z, but I noticed that MoBoot is gone, in which does not let me into the WebOS.

Is there a way how to get this Touchpad to dual-boot (CM10.2 & WebOS)?

Or is there a way to get to WebOS?

Thanks!!!!

Hey,

I'm not fully understanding what has happened here. Explain what you did, obviously something went wrong. Can you not boot the tablet at all? This seems to keep happening with the CM10.2 Rom. You may wish to use Evervolv AOSP 4.3.1 Rom instead.

If you can transfer data then do this. To fix this problem place the Moboot and CWM6 .zips into the cminstall folder and run the ACMEInstaller3. If you can't transfer data run the WebOS doctor.

 

[RolandDeschain79]

I've had my TP for a few months and when I first got it I installed CM9_tenderloin_20130512-nightly. I've been pretty happy with its performance but I hesitated to install Jellybean since everything I read seemed to indicate that JB wasn't ready as a daily driver. I came back and decided it was safe to go ahead and have been working at installing the AOSP 4.3 version of JellyBean. Here's what I did step by step

• nandroid backup ( I had to figure out how that differs from using Titanium Backup)
• used update-cm-tenderloin-system_resize_512-0.4.zip to bump up my partition size
• downloaded and saved <a>ev_tenderloin-nightly-2013.10.29.zip and </a><a>Evervolv-Queo-3.0.0p1-tenderloin.zip </a>
• Saved the older "release build" just in case something went bad with the nightly.
• downloaded and saved gapps-jb43-20130810-dmd151.zip

After trying to figure out how to use ACME installer, reading up on dirty flashing an AOSP ROM over a cm rom and hanging out in the Evervolv Freenode chat area a couple of times the only reply I got seem to suggest that I could go ahead and boot into recovery wipe cache, wipe dalvik cache, and the install my ROM <a>ev_tenderloin-nightly-2013.10.29.zip followed by installing gapps.</a>

After quite a while everything seemed to come up roses except that not only did BT not work (I expected that but decided I could get by without it by using USB in WebOS or one of my cloud accounts for moving files about. However, not only was BT not working but I couldn't get wifi to work. I searched and read everything I could in the 78 pages of this thead and googled about but nothing got wifi working. So I tried flashing the release build cited above and had even less success.

Tonight I discovered my nandroid backup by connecting my TP to my laptop in WebOS. Once I located it I decided to use CWM recovery to get back to cm9 and that worked fine. So I'm back to square #1 but still want to upgrade to a JB ROM. Tonite was the first time I've used CWM Recovery and that gives me more confidence to go ahead with experimentation. I'd like a recommendation as to correcting any mistakes I made in re: "dirty flashing" and whether or not installing via USB cable from my laptop might yield better results.

I did an AOSP JellyBean upgrade on my old tablet, a Lenovo K1 over a year ago and that was done by installing from the laptop via usb cable.

Hi, well it looks like you are on the right path to learning about your TP. Making that backup is the right thing to do but I should point out that all the info you need is located in the OP already. I would read this over since I will now just quote it. I made these long boring post to answer these questions but I realize it takes sometime to absorb all the info. Time to get out your thinking cap and some strong coffee

How to install Android 4.2 and 4.3 Builds on the HP TouchPad

Disclaimer: Make a backup before installing any of these Roms! Testing builds should only be used by experienced users whom are familiar with recovering their device.

When updating your version of Android its recommended to do a clean install of Android. You can do this by using Clockworkmod to Format/Wipe the system data and the cache partitions. You will find a full step by step instructional video below. First choose an Android 4.2 or Android 4.3 Rom and Gapps package from the detailed guides. Next transfer the two .zip files to your Android device with the USB or direct download them. Note that you must have the correct version of Gapps for your version of Android or you may experience errors with Google apps and the Play Store.

Clean Install vs Dirty Install Rom/Updates via Recovery: (After initial install with Acme3) ->Mpgrimm2 Quote

Spoiler

"Clean installing" a rom usually means to format the 3 basic partitions (& sometimes the /boot too depending on the rom/kernel script) and flash the rom as recommended by most devs to avoid issues (some rom installer scripts will handle the formatting for you, but shouldn't be assumed unless stated by the rom's developer. 9-14-13: See Attachment for example).

"Dirty Installing" a rom typically involves formatting the system & cache (sometimes only the cache :thumbdown: ) and flashing a rom to preserve /data partition with user apps & settings.
A cleaner method for this is to format all 3 partitions, flash rom, and restore only /data from a backup.

I've rarely seen dirty installs recommended by devs, but when I have seen them say it was "OK to try", it was done on the same rom/firmware base between incremental rom updates only (vs b/w CM7 - CM9 or CM9 - CM10, etc), and if you had a bug, you needed to go back and do a clean install before reporting it or expecting help. I will add that many people have been successful restoring their CM9 data after flashing CM10 & Gapps.

Attached Thumbnails

• 

[ROM] Evervolv | 3.3.0p1 [AOSP 4.3.1] [Test Build] W/UMS support By flintman (Testing Builds)

Notes:Low battery drain(-4mA to -10mA) h/w video, Nightly Builds, Automated Updater, Audio plays with the screen off, Camera works, No Bluetooth.

Note(Important):This is an Android Open Source Project (AOSP) rom not a CyanogenMod (CM) rom. Dirty flashing an AOSP rom over a CM rom can cause errors and rebooting issues. Always do a clean install when moving from CM to AOSP and vise versa.

(Download)Evervolv | 3.3.0p1 [AOSP 4.3.1] [Test Build] W/UMS support:

Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.

Spoiler

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.

6.Turn on USB mass Storage from the USB connection notification on the Android device

 

[whitesoxfan]

Hey,

I'm not fully understanding what has happened here. Explain what you did, obviously something went wrong. Can you not boot the tablet at all? This seems to keep happening with the CM10.2 Rom. You may wish to use Evervolv AOSP 4.3.1 Rom instead.

If you can transfer data then do this. To fix this problem place the Moboot and CWM6 .zips into the cminstall folder and run the ACMEInstaller3. If you can transfer data run the WebOS doctor.

Ronald, after I installed CM10.2 over CM9, I am able to boot fine in CM10.2, but do not have capability for dual-boot (with Moboot installed to access either recovery mode TWRP, WebOS or Cyanogenmod 9) in which I had with CM9. When I power on the Touchpad with CM10.2, it boots directly in CM10.2 (no Moboot in sight). After this upgrade, will I still be able to access WebOS, an if so, what is the process to get there? Thanks.

 

[RolandDeschain79]

Ronald, after I installed CM10.2 over CM9, I am able to boot fine in CM10.2, but do not have capability for dual-boot (with Moboot installed to access either recovery mode TWRP, WebOS or Cyanogenmod 9) in which I had with CM9. When I power on the Touchpad with CM10.2, it boots directly in CM10.2 (no Moboot in sight). After this upgrade, will I still be able to access WebOS, an if so, what is the process to get there? Thanks.

Ok I've got it now, you can boot android still but not WebOS. No problem just do this.. To fix this problem place the Moboot and CWM6 .zips into the cminstall folder and run the ACMEInstaller3. Now you can boot both again. Note this will resize the partition to 400MB so you will need to increase the size again with the flashable .zip or tailor.

 

[whitesoxfan]

Ok I've got it now, you can boot android still but not WebOS. No problem just do this.. To fix this problem place the Moboot and CWM6 .zips into the cminstall folder and run the ACMEInstaller3. Now you can boot both again. Note this will resize the partition to 400MB so you will need to increase the size again with the flashable .zip or tailor.

Roland, are these the files?

- update-CWM6_tenderloin-20121215.zip

- moboot_038-tenderloin.zip

- ACMEInstaller3

Do you have a link to the procedures for this? Thanks.

 

[RolandDeschain79]

Roland, are these the files?

- update-CWM6_tenderloin-20121215.zip

- moboot_038-tenderloin.zip

- ACMEInstaller3

Do you have a link to the procedures for this? Thanks.

You don't need to add the ACME3 into this folder.

Hello,

First of all thanks to the Touchpad genuises for creating a great CM10.2 image.

Now, I have recently upgraded the ROM on my Touchpad from CM9 to CM10.2.

I followed all the procedures from A to Z, but I noticed that MoBoot is gone, in which does not let me into the WebOS.

Is there a way how to get this Touchpad to dual-boot (CM10.2 & WebOS)?

Or is there a way to get to WebOS?

Thanks!!!!

I thought you read the instructions already, do you need me to tell you where that is?

Place these two files into the cminstall folder and run ACME3.

CWM6 tenderloin-20121215:

moboot_038-tenderloin.zip

4) Installation:
-Once the cminstall files are on The HP TouchPad, it's time to reboot into WebOS Recovery mode(aka USB mode).
-If you are currently running WebOS you must disconnect the USB cable from the PC.
-On your PC look for the USB icon in the bottom right corner, click it and eject the HP TouchPad.

-In WebOS Reboot the device by going into Settings/Device Info/ and select "Reset options" choose restart.
or
-In Android Reboot the device by holding down the power button and select Reboot/OK.

-As soon as the screen goes dark hold down the volume up button until you enter WebOS Recovery mode(aka USB Mode). Note* the large USB symbol that should be on the screen. If you miss it just reboot again and hold down the Volume up button right away. Now connect your USB cable to the PC.

Open a Command Prompt or Terminal

On your PC:
-Open a command prompt by going to the start button and typing CMD into the search window (enter)
Or
-Open a command prompt by Opening the Palm, Inc folder, Hold [Shift] & [Right Click] then select "open Command window here"

On your Mac:
Mac OS X users will need to start a Terminal window. This can be found in the /Applications/Utilities folder.

Using the Command Prompt or Terminal
-Next either type or copy and paste the following into the command prompt (without the part in brackets)

cd\ (enter)

cd program files (enter)

cd palm, inc (enter)

(Only type One of the Following lines below.)

Note:The ACMEInstaller3 can and should be used to install all versions of CyanogenMod.

On your PC

novacom.exe boot mem:// < ACMEInstaller3 (Upgrade from CM7 to CM9)

novacom.exe boot mem:// < ACMEInstaller3 (Upgrade from CM9 to CM10 or install CM10)

novacom.exe boot mem:// < ACMEUninstaller (uninstall CyanogenMod, All versions)

On your Mac

novacom boot mem:// < ACMEInstaller3 (Upgrade from CM7 to CM9)

novacom boot mem:// < ACMEInstaller3 (Upgrade from CM9 to CM10 or install CM10)

novacom boot mem:// < ACMEUninstaller (uninstall CyanogenMod, All versions)

Note: Mac OS X users will enter the commands without the ".exe" extension.

-You will see the lines of text scrolling on the HP TouchPad while CyanogenMod is installing. Now disconnect the USB cable from the HP TouchPad. Once this is complete you will be greeted with the Moboot menu and CyanogenMod will boot for the first time. You will be taken through a series of menus to setup the device. Congratulations you have now installed CyanogenMod onto your HP TouchPad, Have Fun.

 

[shumash]

Ronald, after I installed CM10.2 over CM9, I am able to boot fine in CM10.2, but do not have capability for dual-boot (with Moboot installed to access either recovery mode TWRP, WebOS or Cyanogenmod 9) in which I had with CM9. When I power on the Touchpad with CM10.2, it boots directly in CM10.2 (no Moboot in sight). After this upgrade, will I still be able to access WebOS, an if so, what is the process to get there? Thanks.

http://rootzwiki.com/topic/15931-touchpad-skips-moboot-boots-into-cm9/?p=408122

 

[whitesoxfan]

You don't need to add the ACME3 into this folder.

I thought you read the instructions already, do you need me to tell you where that is?

Place these two files into the cminstall folder and run ACME3.

CWM6 tenderloin-20121215:

moboot_038-tenderloin.zip

4) Installation:
-Once the cminstall files are on The HP TouchPad, it's time to reboot into WebOS Recovery mode(aka USB mode).
-If you are currently running WebOS you must disconnect the USB cable from the PC.
-On your PC look for the USB icon in the bottom right corner, click it and eject the HP TouchPad.

-In WebOS Reboot the device by going into Settings/Device Info/ and select "Reset options" choose restart.
or
-In Android Reboot the device by holding down the power button and select Reboot/OK.

-As soon as the screen goes dark hold down the volume up button until you enter WebOS Recovery mode(aka USB Mode). Note* the large USB symbol that should be on the screen. If you miss it just reboot again and hold down the Volume up button right away. Now connect your USB cable to the PC.

Open a Command Prompt or Terminal

On your PC:
-Open a command prompt by going to the start button and typing CMD into the search window (enter)
Or
-Open a command prompt by Opening the Palm, Inc folder, Hold [Shift] & [Right Click] then select "open Command window here"

On your Mac:
Mac OS X users will need to start a Terminal window. This can be found in the /Applications/Utilities folder.

Using the Command Prompt or Terminal
-Next either type or copy and paste the following into the command prompt (without the part in brackets)

cd\ (enter)

cd program files (enter)

cd palm, inc (enter)

(Only type One of the Following lines below.)

Note:The ACMEInstaller3 can and should be used to install all versions of CyanogenMod.

On your PC

novacom.exe boot mem:// < ACMEInstaller3 (Upgrade from CM7 to CM9)

novacom.exe boot mem:// < ACMEInstaller3 (Upgrade from CM9 to CM10 or install CM10)

novacom.exe boot mem:// < ACMEUninstaller (uninstall CyanogenMod, All versions)

On your Mac

novacom boot mem:// < ACMEInstaller3 (Upgrade from CM7 to CM9)

novacom boot mem:// < ACMEInstaller3 (Upgrade from CM9 to CM10 or install CM10)

novacom boot mem:// < ACMEUninstaller (uninstall CyanogenMod, All versions)

Note: Mac OS X users will enter the commands without the ".exe" extension.

-You will see the lines of text scrolling on the HP TouchPad while CyanogenMod is installing. Now disconnect the USB cable from the HP TouchPad. Once this is complete you will be greeted with the Moboot menu and CyanogenMod will boot for the first time. You will be taken through a series of menus to setup the device. Congratulations you have now installed CyanogenMod onto your HP TouchPad, Have Fun.

Roland, it worked...you guys are the best!!!! Thanks!

 

[carlbeech]

Hi

Quick query about the evervolve 4.3 rom - any idea why the microphone doesn't work? - everything appears to work fine - seems a strange thing (it seems one of the early basic things that gets ironed out...)

But at least it seems to have cured the wifi issue I was having.. (where it got confused, kept saying 'turning wifi off' and then draining the battery because it had gotten stuck...)

Thanks

Carl.