[ROM-AOSP] Unofficial CM10.1 (JB 4.2.2) [08/12 ICON DRAG FIX] - 8.9" Kindle Fire HD Android Development

Unofficial CyanogenMod 10.1 for the Kindle Fire HD 8.9
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
AUDIO: DO NOT ENABLE "LOCK SCREEN AUDIO" OR "TOUCH SOUNDS" IN SOUNDS MENU. THIS *CAN* BREAK AUDIO.
CyanogenMod Changelog (DO NOT DOWNLOAD ANY .ZIP FILES -- FOR OFFICIAL DEVICES ONLY)
http://changelog.bbqdroid.org/
Download Information:
[LATEST][08/12] BETA CM10.1 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
Mirror 2: d-h.st/xMG
md5sum: 6a717e9b085909e6407cab486f585b54
[07/26] BETA CM10.1 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130726-UNOFFICIAL-jem.zip
Mirror 2: d-h.st/4Uc
md5sum: 41d6331a9492ddc2dd576c6cad71c8f5
[07/17] ALPHA CM10.1 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130717-UNOFFICIAL-jem.zip
Mirror 2: http://d-h.st/XxG
md5sum: 1a1204e8e74211213fd1414ebca80194
[07/13] ALPHA CM10.1 + 3.0.50+ KERNEL
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130713-UNOFFICIAL-jem.zip
md5sum: 5050e8c31851162a117d87d17a1b6806
Older builds can be found in the same folder on goo.im:
http://goo.im/devs/Hashcode/jem/cm10.1/
Download Google Apps:
Http://goo.im/gapps
(For Android 4.2.1/CM 10.1 use the top row gapps)
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.
CHANGES:
[08/12] Includes a Trebuchet patch to fix the screen flip-flop when trying to drag an icon in landscape (by XDA user Wickets^)
[08/12] Headphone volume raised (set to 114)
[07/26] Fixed occasional drawables issue with background / etc reverting to HDPI graphics
[07/26] More Dalvik VM changes
[07/17] Dolby: [WIP] Initial work for Dolby support in CM10.1 -- Still troubleshooting audio effect pre-gain handling
[07/17] Audio: Fixed MIC initialization -- works perfectly now, everytime.
[07/17] Camera: cleaned up DCC file handling for a bit more "Amazon"-like performance.
[07/13] USB Vendor ID / Product ID's have been reset to match the Amazon OS / TWRP values. Should help keep Windows drivers from going bonkers.
[07/13] Some Audio issues have been resolved. It shouldn't stop when swapping apps, etc. Still low volume currently where Dolby decoder is used.
[07/13] CM refreshed which includes several well-known security exploit patches
[07/13] PVR/SGX driver updated to 1.[email protected] fixing several games and Google Earth
[07/13] Enabled "dirty region" rendering which helps 2d rendering quite a bit.
[07/13] Fixed a Bluetooth issue: stuck in TRANSITION mode till it's enabled/disabled after a reboot. This was causing extra battery drain.
[07/13] Some tweaks to Android vm allocations. Still needs work, but less apps are being killed off on the boot.
[06/04] CM refresh for changes (no device updates)
[05/14] New android OS audio driver. MIC works but may need to be stopped / re-started once (WIP)
[05/11] Camera should be working again
[05/08] Fixed orientation for HDMI output (requires a /data wipe) -- sound is W.I.P.
[05/08] Fixed default landscape orientation (was backwards)
[05/08] Fixed power HAL to retain current max CPU freq (original code by twa_priv, patched by Hashcode)
[05/07] Raised headphone volume by 10%
[04/20] [Thanks to Javabugs] Bluetooth firmware is now renamed correctly so that it loads and should work
[04/05] Basic audio function is now working. This means volume adjustable speaker output and headset output. NO input works yet -- still WIP.
[04/01] Basic camera function now working, tho after video recording is stopped, camera will FC during thumbnail creation. Video is recorded successfully tho. Panorama crashed out entirely still WIP.
[02/25] Updates to CM10.1 (4.2.2_r1)
[02/01] First release
FEATURES:
3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
PowerVR Graphics Drivers: DDK [email protected] for Android (Jellybean compatible)
Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
Audio
Camera
Wifi
Bluetooth
Sensors
HWAcceleration
HD Codecs for YouTubeHD and Netflix
HDMI video out is now correct and work across several resolutions. YMMV
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire Android projects by doing the following:
(This manifest allows for building Kindle Fire 1st and 2nd gen as well)
Code:
mkdir android
cd android
# Use main repo for CyanogenMod 10.1
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
# Then add the local_manifest.xml for the Kindle Fire
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/KFire-Android/android_local_manifest/cm-10.1/local_manifest.xml
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch jem

CURRENT KNOWN ISSUES:
When long pressing icons in landscape mode to move them, etc the screen will flip upside down for a moment and right itself. This causes the action to be aborted.
Rotation selection in games is hit and miss. Some work perfectly and some like to flip the device upside down. Still debugging what is causing this.
AUDIO: Any decoder which uses Dolby surround current has a lower volume than the rest of the system (Netflix, Google Movies, etc). It's a WIP.
AUDIO: Headset volume still may be lowish. Testing better ways of increasing volume w/o distortion. It's a WIP.
3D Performance: Is only OK. Needs some troubleshooting and perhaps kernel cleanup. Work-In-Progress.
Sensors: Testing various sensors, gyro seems 90 degrees off, etc.
I don't have an LTE version so this is not enabled in current builds.
CURRENT KNOWN APP/GAME ISSUES:
Need For Speed Most Wanted: Crash
EZPDFReader: PDF close = Crash

Hey,
HashCode this is very great job!
Thx

Awesome work, Hash and Verygreen (and whomever else is involved). Much appreciated

slacka-vt said:
Awesome work, Hash and Verygreen (and whomever else is involved). Much appreciated
There's CM10 Development for the KFHD 7" here:
From past experiences, the Dev's do not like having requests for a different device in their threads (or any requests for that matter ). Just sayin' . . .
Click to expand...
Click to collapse
Yes i know, and i allready know that HashCode have not time to do something for the 7" and i have updated my post so you can also do it

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
Hashcode said:
Unofficial CyanogenMod 10.1 for the Kindle Fire HD 8.9
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
Download Information:
[02/01] ALPHA CM10.1 + 3.0.50+ KERNEL
Download the ROM
md5sum: 36a6ec8df79b6dedbe56692ee2f07391
Download Google Apps:
Http://goo.im/gapps
(For Android 4.2.1/CM 10.1 use the top row gapps)
Older builds are found here (under my "Jem" folder on goo.im):
http://goo.im/devs/Hashcode/jem/cm10.1/
PLEASE BE SURE TO WIPE DATA/CACHE WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
CHANGES:
[02/01] First release
CURRENT KNOWN ISSUES:
AUDIO DOES NOT WORK. I'm still troubleshooting and working on a custom audio HAL (if needed)
I need to tweak the build.prop settings so that more apps are compatible.
Camera crashes at the moment
Bluetooth function turns on, but is largely untested.
Haven't touched HDMI yet
I don't have an LTE version so this is untested. Tho much of the RIL files are in place as well as APNs.
FEATURES:
[02/01] 3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
[02/01] PowerVR Graphics Drivers: DDK [email protected] for Android (Jellybean compatible)
[02/01] Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
[02/01] Wifi
[02/01] Bluetooth pairing (no audio)
[02/01] Sensors
[02/01] HWAcceleration
[02/01] HD Codecs for YouTubeHD and Netflix
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire Android projects by doing the following:
(This manifest allows for building Kindle Fire 1st and 2nd gen as well)
Code:
mkdir android
cd android
# Use main repo for CyanogenMod 10.1
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
# Then add the local_manifest.xml for the Kindle Fire
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/KFire-Android/android_local_manifest/cm-10.1/local_manifest.xml
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch jem
Click to expand...
Click to collapse
How we can port this rom to the kindle fire hd 7". I love your work, you are a great developer
Sent From My Super Modded KFHD

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
Thanks for the hard work, downloading now!

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
ChrisFa5 said:
Thanks for the hard work, downloading now!
Click to expand...
Click to collapse
Great, let me now how both the bootloader (from the other thread) and ROM installation goes.
Sent from my DROID RAZR HD using Tapatalk 2

Thank you!
Now to get a fastboot cable.
If anyone installed it please give us your impressions.

kls2k said:
Thank you!
Now to get a fastboot cable.
If anyone installed it please give us your impressions.
Click to expand...
Click to collapse
You can definitely do the install w/o a fastboot cable, but you do need to have a working fastboot driver on your machine. The KFHD's stock bootloader will check for fastboot commands for a short period of time during the boot.
There are other methods as well to get the partitions setup for this, however, in the case of disaster having a working fastboot setup will be required to restore.

Hashcode said:
You can definitely do the install w/o a fastboot cable, but you do need to have a working fastboot driver on your machine. The KFHD's stock bootloader will check for fastboot commands for a short period of time during the boot.
There are other methods as well to get the partitions setup for this, however, in the case of disaster having a working fastboot setup will be required to restore.
Click to expand...
Click to collapse
Hashcode,
Does a factory/fastboot cable work on the 8.9? Some say to buy it, and others say that it only works for the Kindle fire 2 and 7" and that there is no need for it. If it is needed, is there a specific cable that you recommend? Thanks

vaggolena said:
Hashcode,
Does a factory/fastboot cable work on the 8.9? Some say to buy it, and others say that it only works for the Kindle fire 2 and 7" and that there is no need for it. If it is needed, is there a specific cable that you recommend? Thanks
Click to expand...
Click to collapse
I do all my work without a fastboot cable but I have my fastboot driver configured correctly so that the KFHD8 is recognized as a fastboot device during the bootup.
So, while I have tested fastboot on almost every other device that I own, I've never needed to use it on the KFHD8.
EDIT: I just did a quick functional test and my Motorola OEM factory cable did *NOT* place me in fastboot mode. So I think getting a fastboot cable may be a waste of time for the HD 8.9. Rather that users download the Android SDK and make sure it's setup correctly for fastboot. Updating my OP's.

Hashcode said:
I do all my work without a fastboot cable but I have my fastboot driver configured correctly so that the KFHD8 is recognized as a fastboot device during the bootup.
So, while I have tested fastboot on almost every other device that I own, I've never needed to use it on the KFHD8.
EDIT: I just did a quick functional test and my Motorola OEM factory cable did *NOT* place me in fastboot mode. So I think getting a fastboot cable may be a waste of time for the HD 8.9. Rather that users download the Android SDK and make sure it's setup correctly for fastboot. Updating my OP's.
Click to expand...
Click to collapse
Thank you!!

Hashcode, I'm getting a black screen after installing the rom + gapps. Any help?

same here... wiped, factory reset, then installed cm10.1, then wiped and factory reset, then gapps. After blue Kindle screen just a black screen, nothing happens. installed again, cm10.1, then gapps, no wipe/reset. black screen. Got an Fire 8.9 32GB.

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
are both of you using 32gb devices?
has anyone had a successfully installed this?
Sent from my DROID RAZR HD using Tapatalk 2

Just tried your build on my 16GB wifi model but got a black screen on boot (right after the blue KF logo). Happens no matter gapps installed and wiped or not.
I have a recently synced copy of your git repo and I could build myself and run the rom properly though.

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
siruba said:
Just tried your build on my 16GB wifi model but got a black screen on boot (right after the blue KF logo). Happens no matter gapps installed and wiped or not.
I have a recently synced copy of your git repo and I could build myself and run the rom properly though.
Click to expand...
Click to collapse
Can you get a copy of /proc/last_kmsg from the black screen boot and send it to my email? Dont pastebin as there is serial #, etc information that shouldnt be shared. hashcode0f at gmail.com
I will also wipe and flash this build again. could have been a bad build somehow.
Sent from my DROID RAZR HD using Tapatalk 2

I am afraid I couldn't. After the black screen I had to hold the power button to forcefully turn the tablet off and on again - it seemed that the kmsg didn't persist through that to recovery.

Hashcode
first of all, Thank you very much for developing this roms. I bought KD HD 8.9 16Gb when you were developing cm10.1 :laugh:
I read your post (bootloader and this rom) and follow steps. and succeed to enter twrp recovery. (+ blue amazon logo)
but after i installed this rom and gapps, logo appeared and black screen ...
I can enter twrp recover (by power + volume button) but i can't connect kindle 8.9 to pc (windows7 can't recognize KD driver )
so I can't move the file or enter the fastboot .. ( I ordered a factory cable.)
If you know to connect kindle to pc at black screen or at the twrp recovery mode ( I tried to mount use mode of twrp recovery but it was no useful)
tell me something please.

Related

[ROM GUIDE] How to install Android on the HP TouchPad "The Easy Way"

Hello and welcome to the full "Easy Way" guide for installing Android on the HP TouchPad. Rootzwiki Version of this thread here (Noobs can post here):
Additional resources:
[ROM GUIDE] How to Install Android 8.1.x/7.1.2 builds on the HP TouchPad
[ROM GUIDE]How to install Android 5.x.x/4.4.x with Jcsullins TPtoolbox Super Easy Way
[ROM GUIDE]How to install Android 4.4.2 Data Media builds on the HP TouchPad (Non-TPtoolbox method works for 4G HP TP builds)
[ROM GUIDE]How to Update/Install Android 5.x.x/4.4.x Builds on the HP TouchPad(How to update your Roms)
General Unofficial Release Notes:
Working:
-Sound and Mic
-Camera
-H/W Video
-WiFi and Bluetooth
-Most builds have a Low to medium battery drain during sleep -4mA to -10mA or -4mA to -30mA(See below)
Known Issues:
-Flashing CM9/CM10 Over CM10.1/Android4.2/4.3 through CWM or TWRP, can cause a boot loop.(use a Backup)
If your HP TouchPad is stuck in a boot loop or not responding Don't Panic! Try the following:
-Hold down the Power and Home buttons together for 30sec to force the TouchPad to Reboot.
-Hold down the Power button and click the Home key 14 times.
-Doing an install with ACMEInstaller can sometimes result in a boot loop.
-To fix the boot loop, Use a backup or flash the Rom and Gapps package through CWM or TWRP.
The usual HP TouchPad battery drain issues:
-If your battery is heavily drained, then you may need to leave it charging for a full day.
-When the battery is fully drained it can take the TP a longtime to reach even the lowest battery level.
-The USB cable that comes with the HP TP is often defective and breaks easily. Try using another USB cable if possible.
-The USB cable does not transfer enough power to effectively charge the tablet. You must use the wall plug when charging the HP TouchPad.
-To be safe don't let your TouchPad run out of Batteries ever!!
-You can add an automatic shutdown Rule
-AutomateIt, Play Store Link- What to do: New Rule/Trigger Battery level(Below 20%)/Action/Shutdown//save. Or
-Llama, Play Store Link- Location Profiles:Event tab choose + (at the bottom of the screen) Addcondition (battery Level Below 20%) Actions (turn off phone)
-Flashing the A6 Firmware could drastically improve your battery life, Click here to watch the How to Video
How to install Android The Easy Way Guide Video
How to Uninstall Android The Easy Way Guide Video
Note(Important)This will completely remove all Android Partitions and Recoveries and get your TP back to default with WebOS.
How to make a Nandroid backup video:
Note(Important) I highly recommend you make a Nandroid backup after installing and setting up Android on your HP TouchPad.
This perfectly preserves your current configuration and can easily be restored through CWM or TWRP Recovery.
How to install Android on the HP Touchpad "The Easy Way"
Hello and welcome to the full "Easy Way" guide for installing Android on the HP TouchPad.
1) Start by downloading and Installing both Java and the Novacom Software onto your PC or Mac Computer. These files are required before doing the next step.
Note(Important) If you have previously installed an older version of Android its recommended to do a full Uninstall before Reinstalling with the instructions here. If you wish to upgrade your version of Android please read this thread here:
Note(Important)You may need to disable your Antivirus/Firewall software before installing Java and the Novacom software. If you unable to install Android from the dos prompt in step 4, then you will need to redo this step.
a]Download Java
Download and run the Universal Novacom Installer 1.4.1 here:
Note: You will need to have Java installed to run the Universal installer, click here:
Note: You may need to reboot after installing this software.
Or
Download, extract and install the appropriate version of Novacom for your OS here:
Note: Under Linux the Novacom driver is installed at /opt/Palm run it from this location.
2)The Novacom software you installed will create a new folder called Palm, Inc. You will need to place the ACMEInstaller5/5E/5M and ACMEUninstaller2 files into this Palm, Inc folder. By default this folder will be located on your PC @ C:/Program Files/ Palm, Inc. Mac OS X users will find this folder @ /opt/nova/bin. Download the files and copy and paste them right into either of these directories.
a] ACMEInstaller5 (Install CM7, CM9, CM10, or Flash .zips located in the cminstall folder)
b] ACMEInstaller5E (Install Evervolv AOSP Android, or Flash .zips located in the cminstall folder)
c] ACMEInstaller5M (Install CM10.1,CM10.2, or Flash .zips located in the cminstall folder)
d] ACMEUninstaller2 (uninstalls Android and removes recovery, All versions)
Click the picture to see the default location:
View attachment 2492218
3) Choose One of the following versions of Android. Download your chosen package and extract it to your PC. The extracted cminstall folder will contain 4.zipped files. Next attach your HP TouchPad to your PC with the USB cable and place it into USB Drive Mode(WebOS) or MTP mode(Android). Open the extracted folder and transfer the cminstall folder(Contains 4 .zips) into the Internal Storage of your HP TouchPad; the location the opens when the USB is attached to the PC/Mac. Make sure that the folder is named "cminstall" and contains 4.zip files. Once complete disconnect your TouchPad from the USB cable.
Android Installation Package Downloads:
a]Evervolv AOSP Android 4.3.1 JB (20140129) cminstall package Download:
Notes: Low battery drain(-4mA to -10mA) h/w video, Audio & Mic, Camera, Automated Updater, Bluetooth
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into the 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.
And/Or
6.Turn on USB mass Storage from the USB connection notification on the Android device
b]CM10.2 Android 4.3.1 JB (20131209)cminstall package Download:
Notes:Low battery drain(-4mA to -10mA) h/w video, Audio & Mic, Camera, No Bluetooth.
c]CM10.1 Android 4.2.2 JB (20131210)cminstall package Download: (Roland Recommended)
Notes:Low battery drain(-4mA to -10mA) h/w video, Audio & Mic, Camera, Bluetooth.
d]CM10 Android 4.1.2 10 JB (20131019)cminstall package Download:
Notes:Low battery drain(-4mA to -10mA) h/w video, Audio & Mic, Camera, Bluetooth.
e]CM9 Android 4.0.2 ICS (20130929)cminstall package Download:
Notes:Low battery drain(-4mA to -10mA) h/w video, Audio & Mic, Best Flash Support, Camera, Bluetooth, Last Official CM9 release(Netflix works).
f]CM7 Android 2.3.7 Gingerbread (CM7Alpha3.5)cminstall package Download:
Notes:Medium battery drain(-30mA to -60mA) h/w video, Audio & Mic, Flash Support, Camera, Bluetooth, Original CM7 Alpha Release.
Note: Each package contains all 4.zips files needed to install Android!
(Thanks to Mpgrimm2 for Dev hosting the files)
How to Install Android
4)Installation:
-Once the cminstall files are on The HP TouchPad, it’s time to reboot into WebOS Recovery 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. Note* the large USB symbol that should be on the screen.
If you miss it just reboot again and hold down 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
View attachment 2492218
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). You can either enter the individual commands or just copy and paste the full (Typed all at once) line into the command prompt.
Note(Optional): You can run batch files to automatically input the following commands for you easily everytime download here:
On Your PC
cd\ (enter)
cd program files (enter)
cd palm, inc (enter)
or (Typed all at once)
cd c:\Program Files\Palm, Inc (enter)
On your Mac
cd / (enter)
cd opt (enter)
cd nova (enter)
cd bin (enter)
or (Typed all at once)
cd /opt/nova/bin (enter)
(Only type One of the Following lines below.)
On your PC
novacom.exe boot mem:// < ACMEInstaller5 (Install CM7, CM9, CM10, or Flash .zips located in the cminstall folder)
novacom.exe boot mem:// < ACMEInstaller5M (Install CM10.1, CM10.2, or Flash .zips located in the cminstall folder)
novacom.exe boot mem:// < ACMEInstaller5E (Install Evervolv Android, or Flash .zips located in the cminstall folder)
novacom.exe boot mem:// < ACMEUninstaller2 (uninstalls Android and removes recovery, All versions)
On your Mac
./novacom boot mem:// < ACMEInstaller5 (Install CM7, CM9 or CM10, or Flash .zips located in the cminstall folder)
./novacom boot mem:// < ACMEInstaller5M (Install CM10.1, CM10.2, or Flash .zips located in the cminstall folder)
./novacom boot mem:// < ACMEInstaller5E (Install Evervolv Android, or Flash .zips located in the cminstall folder)
./novacom boot mem:// < ACMEUninstaller2 (uninstalls Android and removes recovery, 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 Android onto your HP TouchPad, Have Fun.
Note(Important) If you're unable to install Android and get a message like "failed to connect to server" you may have encountered a problem when installing either Java or Novacom. Try to uninstall and reinstall both of those programs. You may need to disable your Antivirus or firewall software, this could be blocking the connection to your PC. If its still not working try another computer or laptop, this fixes the problem 99% of the time.
CyanogenMod package contents explained:
-You will need 4 files to install CyanogenMod. The first two files can vary depending on the version you choose to install. CyanogenMod 9 is used here for Example:
1)update-cm-9-20130929-NIGHTLY-tenderloin.zip (Installs your Android Operating System)
2)update-gapps-ics-20120429-signed.zip (Installs your Gapps Package, Play Store & Applications)
3)moboot_038-tenderloin.zip(Installs your Boot Menu options)
4)update-CWM6_tenderloin-20121215.zip (Installs ClockWorkMod6 recovery)
Notes, Fixes and Tweaks:
Note:The following are Solutions for the most Frequently asked questions and problems.
1)If the WiFi turns off in Sleep/suspend mode then uncheck wifi optimization.
Note:Turning off "WiFi optimization" might help to improve WiFi functionality.
-Settings/WiFi/3 Dots/Advanced/WiFi optimization (uncheck)
-In Shumash's Schizoid build you can find it @ RomControl/General
2)If the HP TouchPad isn't charging do the following. If MTP is already checked,then uncheck and recheck the option.
-To Enable MTP mode, Go to settings/storage, look for the three dots in the upper right hand corner of the screen, tap computer connection, make sure there is a check next to MTP.
-This will enable the TouchPad to transfer files and charge using the USB cable.
3)If your Touchpad skips moboot and boots right into Android, then do the following:
-Hold the home key while booting to force moboot to display the Menu.
-To fix this problem use a Rooted File explorer, like X-plore, to delete the moboot.next file located @ Root/Boot/
-This problem is often caused by using the CyBoot app in WebOS.
4)Turning off "network location services" might help to improve overall battery drain and longevity.
-Settings/location access/ access to my location set to off
-You may wish to monitor your battery drain history during sleep.
-Install the the free app Battery Monitor Widget:
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to either 6300 (F29C) or 5800 (S29C) and tap OK
-Note* See the Battery p/n # on the original packaging.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
5)You can enable additional reboot options like recovery by enabling Developer options.
-Go to Settings/About Tablet/ Tap on "Build number" 7 times.
-A new menu will appear in the Settings/About Tablet/Developer options/ tab on the left.
-Check "Advanced reboot" to get the Recovery/Boot loader options.
6) When installing Roms and .zips with the ACMEInstaller3, you may need to add "update-" to the beginning of the file names or they won't flash correctly. Like so "update-cm-10.1-20130808-EXPERIMENTAL-tenderloin-BLUETOOTH_TEST.zip"
7)If Moboot is displaying multiple Rom or recovery names that you are not currently using, then do the following.
-With a rooted File explorer go to root/boot/ and delete the unwanted uImage.( X) file to remove the entry from Moboot.
-Here you can also change the default boot option by editing the moboot.default as text.
-Also you can change the default recovery option by editing android.default.recovery
8)If you are unable to find the Play Store after you install Android, then you will need to reflash your gapps package. Click Here for the how to video!
9)If you are unable to find the camera app install this Nexus 7 Camera Launcher:
-This will also make the camera preview full screen.
10)Use this free app "4.2 Multiple User Enabler Root" to enable multi-user functionality.
-You can also use the terminal emulator to enable it too, see VFF instructions here.
Optional Patches, Tweaks, and Customization's (Not included):
(Optional)Add flash Support for Android:
[Video]How to Install the Adobe Flash Player on Any Android Device 2.3-4.4
Note: Official flash support for Android was removed after CM9(Android 4.0.2).
You can add support back by installing the Flash apk file and using a supported Web Browser.
To use Nexfix properly it's recommend to use CM9.
(Optional) Updated CWM(6.0.2.8) and TWRP(2.6.3.0) Recovery flashable .zips:
iMarck90 has packaged the latest CWM6 and TWRP recoverys into flashable zips. Download the latest version of CWM and TWRP then flash it through your current recovery to install them:
Recovery Download:
TWRP 2.6.3.0
ClockworkMOD 6.0.2.8
(Optional) Additional ACMEInstaller versions by iMarck90:
iMarck90 has modified the ACMEInstaller to work with TWRP and Milaqs CM builds. Checkout his thread below for full details and instructions.
Note: Milaqs CM10.2 builds requires additional partition changes and the installation of the Data media CWM. Full install information is covered in my How to update/upgrade Android thread here:
ACMEInstaller4 [Testing] and other things..
(Optional) Roland's Custom HP TouchPad Boot Animations:
[Boot Animation] Roland's HP TouchPad Custom Boot Videos (XDA Thread)
A variety of fun Boot Animations to enhance your TouchPad experience here:
(Optional) HP TouchPad CM9/CM10 WebOS-like Card Switcher Mod Watch theVideo Here!youtu.be/06jdESXEzYs
[MOD] WebCM10 - WebOS-like app switcher [3/10/13] [PA/CM10/CM9/AOKP]
Download: WebCM9 WebCM10 and flash it through CWM6 or TWRP recovery.
(Optional)[Video]How to Customize your Android Device. Launchers, Themes, Widgets & Live Wallpapers. Have fun
(Optional)Camera Launcher for Nexus 7(makes the Camera preview full screen):
(Optional)[Video]How to install flash on Android: Note* Use the Dolphin, Firefox or the Puffin Browsers [font=Arial, Helvetica, sans-serif][/font]
(Optional) Automated Installers/Uninstallers/Toolkits [Threads]:
-There are now three great threads about automated installers that can make your Android experience almost effortless.
Touchpad Toolkit - Android automated installer
[Easy Installer] [v 1.0.3] [Lazy/Noob Android Installer]
All the TouchPad PC files in a few simple clicks!
Gapps Downloads & Extras:
Main Gapps page @ Goo.im
Android 4.4 Gapps:
Android 4.4 Kitkat Gapps:
Android 4.3 Gapps:
Android 4.3 20130813 Gapps:
Android 4.3 20130813 CM10.2 Lite Gapps:
Android 4.2 Gapps:
Android 4.2 20130812 CM10.1 Gapps:
Android 4.2 20130812 CM10.1 Lite Gapps
Android 4.1.X Gapps:
Android 4.1.x 20121011 CM10 Gapps:
Android 4.1.x 20121011 CM10 Lite Gapps:
Android 4.0.3-4 Gapps:
Android 4.0.3-4 20120429 CM9 Gapps:
Android 4.0.3-4 20120429 CM9 Lite Gapps:
Extras:
Mpgrimm2 Dev-Host backup files
Mpgrimm2 Dev-Host backup files*mirror
Flashable.zip file to change the partition size to 512MB
CWM6 tenderloin-20121215:
Nexus 7 Camera Launcher:
moboot_038-tenderloin.zip
WebOS Doctor 3.0.5
tpdebrick-v004.zip
moboot_0.3.5.zip
ACMEInstaller3
News and Updates
[ROM GUIDE]How to install Android 4.4.2 Data Media builds on the HP TouchPad
[ROM GUIDE]How to install Android 4.4.2 Data Media builds on the HP TouchPad
Jcsullins CM10.1 Kernel 3.0 Bluetooth Test build
Notes: Low battery drain (-5mA to -10mA), h/w video, Audio, Bluetooth, No Camera.
Download cm-10.1-20140125-EXPERIMENTAL-3KERN_TEST-tenderloin.zip
iMarck90's Post about the new Build:
Android 4.2 Gapps:
Android 4.2 20130812 CM10.1 Gapps:
Android 4.2 20130812 CM10.1 Lite Gapps
[ROM] [CM10/CM10.1] [Experimental Preview by Jcsullins] [01/05/14]
-Read the discussion about this great new rom here.
10/19/2013 Builds based on Jcsullins CM10 that include the Master key exploit fixes: By iMark90
The Problem: A Master key security exploit issue was discovered in CM9/CM10 that was later fixed in all Android 4.2+ builds. However this still effects many HP TouchPad CM10 builds. You can test for these exploits by installing and running the Bluebox security test App here.
The solution: RootzWiki member iMarck90 has included the Master key fixes into two new builds of Jcsullins CM10. These builds by iMarck90 are entirely based on the fantastic work of Jcsullins, Dorregaray, and Dr Marbel, et al. Install these new CM10 builds by dirty flashing them over your current build of CM9/CM10.
Note:In addition to these fixes iMarck90 has included all the current upstream changes like, Jcsullins newer WiFi drivers V4.5 and Bluetooth fixes.
1)CM10 Rom Download:
cm-10-20131019-UNOFFICIAL-tenderloin
Note: This is the latest CM10 build includes the Gyroscope patch.
2)Gaps Download:
CM10 Gapps 20121011
3)(Optional)HP TouchPad CM10 WebOS-like Card Switcher Mod, Watch theVideo here.
WebCM10 for CM10
reserved
Troubleshooting:
Notes, Fixes and Tweaks:
Note:The following are Solutions for the most Frequently asked questions and problems.
1)If the WiFi turns off in Sleep/suspend mode then uncheck wifi optimization.
Note:Turning off "WiFi optimization" might help to improve WiFi functionality.
-Settings/WiFi/3 Dots/Advanced/WiFi optimization (uncheck)
-In Shumash's Schizoid build you can find it @ RomControl/General
2)If the HP TouchPad isn't charging do the following. If MTP is already checked,then uncheck and recheck the option.
-To Enable MTP mode, Go to settings/storage, look for the three dots in the upper right hand corner of the screen, tap computer connection, make sure there is a check next to MTP.
-This will enable the TouchPad to transfer files and charge using the USB cable.
3)If your Touchpad skips moboot and boots right into Android, then do the following:
-Hold the home key while booting to force moboot to display the Menu.
-To fix this problem use a Rooted File explorer, like X-plore, to delete the moboot.next file located @ Root/Boot/
-This problem is often caused by using the CyBoot app in WebOS.
4)Turning off "network location services" might help to improve overall battery drain and longevity.
-Settings/location access/ access to my location set to off
-You may wish to monitor your battery drain history during sleep.
-Install the the free app Battery Monitor Widget:
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to either 6300 (F29C) or 5800 (S29C) and tap OK
-Note* See the Battery p/n # on the original packaging.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
5)You can enable additional reboot options like recovery by enabling Developer options.
-Go to Settings/About Tablet/ Tap on "Build number" 7 times.
-A new menu will appear in the Settings/About Tablet/Developer options/ tab on the left.
-Check "Advanced reboot" to get the Recovery/Boot loader options.
6) When installing Roms and .zips with the ACMEInstaller3, you may need to add "update-" to the beginning of the file names or they won't flash correctly. Like so "update-cm-10.1-20130808-EXPERIMENTAL-tenderloin-BLUETOOTH_TEST.zip"
7)If Moboot is displaying multiple Rom or recovery names that you are not currently using, then do the following.
-With a rooted File explorer go to root/boot/ and delete the unwanted uImage.( X) file to remove the entry from Moboot.
-Here you can also change the default boot option by editing the moboot.default as text.
-Also you can change the default recovery option by editing android.default.recovery
8)If you are unable to find the Play Store after you install Android, then you will need to reflash your gapps package. Click Here for the how to video!
9)If you are unable to find the camera app install this Nexus 7 Camera Launcher:
-This will also make the camera preview full screen.
10)Use this free app "4.2 Multiple User Enabler Root" to enable multi-user functionality.
-You can also use the terminal emulator to enable it too, see VFF instructions here.
Bricking, Boot Loops, Help & Fixes(Important):
If your HP TouchPad is stuck in a boot loop or not responding Don't Panic! Try the following:
-Hold down the Power and Home buttons together for 30sec to force the TouchPad to Reboot.
-Hold down the Power button and click the Home key 14 times.
-If you're stuck in a boot loop restore a back or do a fresh install, Click here for a how to Video:
-Dirty flashing older builds (CM9/CM10) over newer builds (CM10.1/CM10.2) will result in Boot loops.
-If this happens use your backup or do a fresh install, Click here for a how to Video:
-Doing an install with ACMEInstaller can sometimes result in a boot loop. Use a backup or flash the Rom and Gapps package through CWM or TWRP.
If your TouchPad seems bricked and won't turn on:
-If your battery has been fully drained, then you may need to leave it charging for a full day.
-When the battery is fully drained it can take the TouchPad a longtime to reach even the lowest battery level.
-The USB cable does not transfer enough power to effectively charge the tablet. You must use the wall plug when charging the HP TouchPad.
-After charging the HP TouchPad for a full day try holding down, home + power + volume down for 30+ seconds.
-If the tablet does not turn on after the previous steps it may be bricked and you will need to run the TPDebrick procedure found in the thread below:
Developer Jcsullins has posted a thread "TPDebrick v0.4" dedicated to helping people with bricked HP TouchPads(Important):
Note* All debricking questions should be posted here!
If you ran the WebOS doctor but it got stuck at 8-12% follow the instructions in the threads below:
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap) thread.
Touchpad Backup with QPST -- need this for unbricking:
-Warning: Certain TouchPads can become "Bricked" if you let the battery drain to zero.
-Installing one of these free apps could solve the problem and save you time.
-AutomateIt, Play Store Link- What to do: New Rule/Trigger Battery level(Below 20%)/Action/Shutdown//save.
Or
-Llama, PLay Store Link- Location Profiles:Event tab choose + (at the bottom of the screen) Add condition (battery Level Below 20%) Actions (turn off phone)
Fixes for SDCARD issues for all versions of CyanogenMod
-Download a flashable.zip to increase the size of your internal storage.
How to Change the DPI settings for CM10:
-If your home screen looks a little off then you may wish to change the DPI/LCD density.
Note: Setting the DPI to something other than 160 or 120 can cause compatibility issues with the Google Play Store. If you are unable to download and install apps then change the DPI to 160 or 120.
You can change the DPI settings either by using a free LCD app or by editing the build prop. The two apps below will do the job.
Resolution change / Density, DPI Play Store Link:
or
Try editing the build prop with an easy to use free app.
Build.prop Editor, Play Store Link:
How and when to Use the WebOS Doctor(Important):
Q: What’s the WebOS Doctor and when should I use it?
The WebOS Doctor is a program that has two main functions for HP TouchPad users. It can either update your version of WebOS or fix problems with a damaged WebOS by completely reinstalling it. If WebOS no longer boots or apps and preware have stopped working correctly, then you will need to resinstall WebOS with the Doctor. A failed or interrupted attempt at changing the partition sizes with WebOS preware app Tailor may cause these problems. To check what version of WebOS is currently installed go to Launcher(Up Arrow)/Settings/Device Info/ Version
Note(Important): You MUST uninstall Android before running the WebOS doctor. Failing to remove Android before running the Doctor can result in the process becoming stuck at 8-12% and potentially bricking the device. If you are currently stuck visit the thread below for information about fixing the problem. If you’re unable to use the tablet at all follow the instructions in Jcsullins TPDebrick thread.
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(Rootzwiki)
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(CM)
TPDebrick v004 - Jcsullins dedicated thread for fixing Bricked TouchPads:
Note(Important): Running the Doctor will completely wipe all personal information, applications and preware from the TouchPad. Media like music and movies will not be affected. However I would recommend backing your important files to PC, before running the Doctor.
Note(Important): In order to install apps from the WebOS store you will need to get the Root Certificate fix for WebOS cloud services.
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
How to run the WebOS Doctor:
1) Install Java
-Java must be installed in order for the TouchPad to communicate with your PC.
2) You MUST completely uninstall Android from the HP TouchPad before running the WebOS doctor. Remove Android by running the ACMEUinstaller2. Watch the following video for full uninstall instructions.
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
3) Download the latest 3.0.5 WebOS doctor application to your PC. If upgrading you can check your current version from WebOS by going to Launcher(Up Arrow)/Settings/Device Info/ Version.
WebOS Doctor 3.0.0 to 3.0.5 Official Links
4) Put the tablet into WebOS recovery mode by doing the following:
-In WebOS Reboot the device by going to Launcher(Up Arrow)/Settings/Device Info/ select “Reset options” choose restart.
-As soon as the screen goes dark hold down the volume up button until you enter WebOS Recovery 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. Once in WebOS recovery mode connect your USB cable to the PC.
5) Now you’re ready to run the WebOS Doctor app by clicking on the .jar file you downloaded in the previous step. Be sure that your tablet is fully charged and connected with the USB cable before starting this process. Running out of power or interrupting this process in anyway could brick your HP TouchPad. Please be careful and fully read the instructions before beginning.
-Double click the webosdoctor.jar file to launch the app
-Select your language then click next
-Accept the licence agreement, read the warning message then select next to begin the install.
-Be patient the process can take anywhere from 15min to 1hour to complete.
HP TouchPad Battery Drain issues during sleep (Important):
[Video]How to Reflash the A6 Firmware Method 1:
[Video]How to Reflash the A6 Firmware Method 2:
Full step by step A6 Firmware Flashing instructions and Info here!
The Problem:
Developer James Sullins, Aka Jcsullins, has informed HP TouchPads users that there is a problem with our tablets A6 Firmware. This issue can cause an usually high battery drain during sleep. This problem occurs overtime while running both CyanogeMod and WebOS, on the HP TouchPad. As a results the Touchpads battery drains more quickly with daily use and the overall life span is reduced.
The Solution:
Reflashing the A6 Firmware effectively fixes the problem but may need to be repeated as a part of regular HP TouchPad maintenance. Watch this video and follow the step by step instructions to reflash your own Touchpads A6 Firmware.
How to test:
How to monitor your battery
To monitor your battery drain history during sleep install the free app Battery Monitor Widget:
-Once installed open the app and go to history to see a log of your devices sleep history.
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to 6300 (*f29c), 6000 (*i29c) or 5800 (*s29c) and tap OK
-Note* See the Battery p/n # on the original packaging.
-Note* after setting the calibration, users will have to allow several hours to pass before the history can be accumulated.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
A6 Firmware Threads & Info:
[Fix Guide] How to Reflash the A6 Firmware XDA
How to Reflash the A6 Firmware Method 2:
[Video] How to fix the A6 firmware Battery Drain Problem on the HP TouchPad Method 2
1) Boot to WebOs and in the "Just Type" box enter the following: webos20090606 or upupdowndownleftrightleftrightbastart
-Tap the developer mode icon and slide the toggle to on, then press submit.
-Plug the USB cable into the HP TouchPad and your PC.
2)On your PC Install Java and the WebOSQuickInstall-4.5.0 software*
- Note* If you have already previously installed Android with Java, then skip it.
a]Download Java:
b]Download Novacom Universal Installer:
c]Download WebOSQuickInstall-4.5.0:
3)Run the WebOSQuickInstall-4.5.0 software, note your TouchPad must be connected with the USB cable.
-Click on the Small globe icon located under the plus minus buttons.
-This will take us to a new menu where we will search “preware”
-Click the install button and the Preware app will be installed.
-You may now unplug the USB cable.
4)On the tablet while booted into WebOS navigate to downloads and select Preware.
-scroll down until you see a button appear to continue
-Search for “wterm” and install the app.
-Run wterm, and set a password to give the app Root permissions.
- You can set or change the password by looking for the wterm menu in the upper left corner and select setup.
-Click on New password and enter a simple password like ”0000”
-Confirm the password and press “Set Password” button, now hit done and exit.
-Note you can increase the font size by going to wterm preference settings.
5) Now in wterm enter the following command
PmA6Updater -f -d 0 /lib/firmware/a6_firmware.txt.00
PmA6Updater –a (Note this shorter command flashes two firmwares)
-It should take about 20-30 seconds to complete and will inform you upon completion.
-Congratulations you have now reflashed the A6 Firmware and can safely close the terminal and reboot your HP TouchPad.
Note: If you input the command and get a message saying it said can't open the A6 device, then try toggling developer mode off and on.​
How to Reflash the A6 Firmware Method 1:
[video]How to Reflash the A6 Firmware Method 1:
1) Boot to WebOs and in the "Just Type" box enter the following: webos20090606
-Tap the developer mode icon and slide the toggle to on, then press submit.
WARNING: Do not enter a password. Just tap submit.
-Plug the USB cable into the HP TouchPad and your PC.
2)Install Java and the Novacom software*
- Note* If you have already previously installed Android with, Java and Novacom drivers, then proceed to step 3.
a]Download Java:
b]Download Novacom Universal Installer:
3)Open windows explorer and go to C:\Program Files\Palm, Inc\Terminal
-Now run the Terminal.bat*
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
4)In the open Novaterm window, select file\connect\Ok
-Now copy and paste the following line into Novaterm and press enter*
PmA6Updater -f -d 0 /lib/firmware/a6_firmware.txt.00
PmA6Updater –a (Note this shorter command flashes two firmwares)
-Note* Do Not! disconnect the TouchPad After starting this procedure.
-Novaterm will tell you "firmware update complete"
- In the open Novaterm window, select file\disconnect\Ok
-Congratulations you have now reflashed the A6 Firmware and can safely disconnect your HP TouchPad from the USB cable.
[/spoiler]
Rom Flashing issues with CWM5 (Important):
Spoiler
The Problem:
-Developer Green has advised that using CWM5 to install(flash) a nightly or format the /data and /system partitions, may introduce corruption into the file system.
-It is advised to avoid updating though CWM5 for this reason.
-By installing Jcsullins new CWM6 you can avoid future corruption.(Included)
-CWM6 Download:
-Updating your Rom with CWM5 can cause the inode errors seen in double penguin mode while installing with the ACEMEInstaller3.
-Due to corruption introduced from flashing/Updating Roms though CWM5, your system partition may have errors.
The Solution: (Also a safe way to upgrade from CM9-CM10)
-Uninstalling CyanogenMod with the ACMEUninstaller and freshly installing with the ACMEInstaller 3 will resolve any possible issues.
-To avoid problems when updating from CM9-CM10 you should first make a full Nandroid backup, then uninstall CM9.
-Next Fully install CM9 using the ACMEInstaller3.
-Once Complete restore your CM9 Nandroid backup,
-Now you can safely update from CM9- CM10 with the ACMEInstaller3 or
-You can also safely flash the CM10 Rom and gapps package with CWM6.
-It’s fine to flash regular.zip files through CWM5; such as gapps files, fixes/patches and CWM6.zip These will not cause corruption and are safe for daily flashing.
-Use CWM6 from now on Download:
-Note* CWM6 has already been included for everyone using this guide to install CyanogenMod for the first time.
-[RECOVERY] JCSullins' Touchpad CWM6 v6.0.1.9 [2012-12-15] Full Thread Here!
-For more information Please watch the CWM6 Video Here:
Spoiler
Rom Flashing issues with CWM5 (Important):
The Problem:
-Developer Green has advised that using CWM5 to install(flash) a nightly or format the /data and /system partitions, may introduce corruption into the file system.
-It is advised to avoid updating though CWM5 for this reason.
-By installing Jcsullins new CWM6 you can avoid future corruption.(Included)
-CWM6 Download:
-Updating your Rom with CWM5 can cause the inode errors seen in double penguin mode while installing with the ACEMEInstaller3.
-Due to corruption introduced from flashing/Updating Roms though CWM5, your system partition may have errors.
The Solution: (Also a safe way to upgrade from CM9-CM10)
-Uninstalling CyanogenMod with the ACMEUninstaller and freshly installing with the ACMEInstaller 3 will resolve any possible issues.
-To avoid problems when updating from CM9-CM10 you should first make a full Nandroid backup, then uninstall CM9.
-Next Fully install CM9 using the ACMEInstaller3.
-Once Complete restore your CM9 Nandroid backup,
-Now you can safely update from CM9- CM10 with the ACMEInstaller3 or
-You can also safely flash the CM10 Rom and gapps package with CWM6.
-It’s fine to flash regular.zip files through CWM5; such as gapps files, fixes/patches and CWM6.zip These will not cause corruption and are safe for daily flashing.
-Use CWM6 from now on Download:
-Note* CWM6 has already been included for everyone using this guide to install CyanogenMod for the first time.
-[RECOVERY] JCSullins' Touchpad CWM6 v6.0.1.9 [2012-12-15] Full Thread Here!
-For more information Please watch the CWM6 Video Here:
Partition Size Problems and ACMEInstaller3(Important):
The Problem:
-CM10 requires a larger partition size than CM9.
-The ACMEInstaller 3 is meant to increase the partition size from 300MB to 400MB.
-CM9 only needed 300MB but Jelly Bean is a larger Rom and requires more space(350MB).
-In some cases users have reported 0.0/400MB of space left after installing CM10.
-Although everything may still run fine it is recommend to leave at least a little space free. The consequences of running it without free space are not known.
How to monitor free System Storage space with CM10(Optional):
-You can use a free app,Quick System Info PRO, to check the size of your partitions and remaining free space, it should be = 387MB or 402MB. Either 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.
-If your partition is an odd size or you get random reboots,then you may have encountered problems due to flashing you Rom.
Quick System Info PRO Video Link:
Quick System Info PRO Play Store Link:
-If you use the ACMEInstaller3 and then later restore your Nandroid backup of CM9, you will still retain the larger partition size.
-You can then use CWM or TWRP to safely flash from CM9-CM10 but flashing from CM10-CM9 can cause a boot loop.
How to free up System Storage space with CM10(Optional):
I believe 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.
How to guide for changing your system, data, and cache partition sizes(Optional): (Gradular)
Related Links:
-[ROM] CM10.1 Test Builds for the HP TouchPad, Android 4.2.2
[ROM] How to install jcsullins CM10 Unofficial Preview Builds @ RootzWiki
XDA thread for CM10:
TPDebrick v0.4
Android on 4G TouchPad Thread
How to guide for changing your system, data, and cache partition sizes: (Gradular)
Cool Tools for Tweaking and monitoring your Battery in CM10, the must have testing app:
Official CyanogenMod 9 Nightly Build Discussion:
Latest Official Nightly Builds of CM9:
GOO.IM: All Gapps Downloads:
ACMEInstaller3 thread @ RootzWiki
How to install Jcsullins CM10 with Sound @ RootzWiki
Extra Downloads:
Mpgrimm2 Dev-Host backup files
Mpgrimm2 Dev-Host backup files*mirror
Flashable.zip file to change the partition size to 512MB
CWM6 tenderloin-20121215:
Nexus 7 Camera Launcher:
moboot_038-tenderloin.zip
tpdebrick-v004.zip
moboot_0.3.5.zip
ACMEInstaller3
Donate to the Developers:
Donate to show your appreciation to our hard working developers:
Donate to Jcsullins:
Donate to Dorregaray:
Donate to Evervolv Team (Flintman):
Donate to Milaq
Donate to Invisiblek:
How to install Android 4.2 and 4.3 Builds on the HP TouchPad
Hello HP TouchPad users, Great News! Android 4.2, 4.3 and 4.4 Roms are now available. These Roms are almost fully functional except for a few that lack Bluetooth support see the Rom notes. Most builds have h/w video, Camera, WiFi, Bluetooth, Sound & Mic support. Battery drain during sleep is low around (-4mA to -10mA) for most builds, see guide. Below you will find a comparison and overview of all the available Android 4.2, 4.3 and 4.4 Roms. Read the summarized descriptions for important information and notes about the builds. Remember many of these are testing builds, so Please make a nandroid backup and read the information carefully. Please thank and leave our incredible developers some feedback here or in the related threads.
General Unofficial Release Notes:
Working:
-Sound and Mic
-Camera
-H/W Video
-SDcard
-WiFi
-Most builds have a Low to medium battery drain during sleep -4mA to -10mA or -4mA to -30mA(See below)
Known Issues:
-Flashing CM9/CM10 Over CM10.1/Android4.2/4.3 through CWM or TWRP, can cause a boot loop.(use a Backup)
If your HP TouchPad is stuck in a boot loop or not responding Don't Panic! Try the following:
-Hold down the Power and Home buttons together for 30sec to force the TouchPad to Reboot.
-Hold down the Power button and click the Home key 14 times.
-Doing an install with ACMEInstaller can sometimes result in a boot loop.
-To fix the boot loop, Use a backup or flash the Rom and Gapps package through CWM or TWRP.
The usual HP TouchPad battery drain issues:
-If your battery is heavily drained, then you may need to leave it charging for a full day.
-When the battery is fully drained it can take the TP a longtime to reach even the lowest battery level.
-The USB cable that comes with the HP TP is often defective and breaks easily. Try using another USB cable if possible.
-The USB cable does not transfer enough power to effectively charge the tablet. You must use the wall plug when charging the HP TouchPad.
-To be safe don't let your TouchPad run out of Batteries ever!!
-You can add an automatic shutdown Rule
-AutomateIt, Play Store Link- What to do: New Rule/Trigger Battery level(Below 20%)/Action/Shutdown//save. Or
-Llama, Play Store Link- Location Profiles:Event tab choose + (at the bottom of the screen) Addcondition (battery Level Below 20%) Actions (turn off phone)
How to update/install Android 4.2, 4.3 and 4.4 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.
Clean install(Recommended):
When updating your version of Android its recommended to do a clean install of Android. You can do this by using your recovery(CWM or TWRP) to Format/Wipe the system data and the cache partitions. You can also fully Uninstall and Reinstall Android to accomplish a clean install. You will find a full step by step instructional video below. First choose an Android 4.2, 4.3 or 4.4 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. Watch the how to update video below for step by step instructions. note that you must have the correct Gapps for your version of Android or you may experience errors with the Keyboard, Play Store or other Google apps.
Note(Important):If you have not installed Android before, then start by using the "Easy Way" guide below and installing one of the prepared install packages. Once you have Android running make a Nandroid backup before trying the large selection of available Roms in this thread. If you are currently using an older version of Android like 2.3 or 4.0.1(CM7/CM9), then you should do a Full uninstall and reinstall. This fixes several problematic issues like increasing the system partition size from 400-600MB to accommodate larger Android 4.2+(CM10+) Roms. If you're currently using a newer Rom like CM10+ and have CWM6+ then you can upgrade with a clean install after increasing your system partition size. You can do this by using the WebOS Preware app Tailor, or by using a flashable 512MB zip located in Gradular's thread, How to guide for changing your system, data, and cache partition sizes to whatever you want.
How to check your Android version and System Partition size:
-Get the free app,Quick System Info PRO, to check the size of your partitions and remaining free space.
-Having a System Partition size of 500-600MB is needed when installing Android 4.2+ Roms.
-Check your version of Android by going to Settings/About Tablet/Android Version.
Tailor Video:
Don't forget! First make a Nandroid backup of your current setup! Full CWM and TWRP Video here:
Dirty Flash(Not Recommended):
If you wish to keep your current setup and have made a Nandroid backup, then you can attempt to upgrade using a Dirty flash. Download your selected Rom and gapps zips and flash them through CWM or TWRP recovery. Don't forget to wipe your caches, Click here to see a how to dirty flash your Rom video clip.I would only recommend doing this over similar Roms and only moving upwards version wise. For example CM10 to CM10.1 or Evevolv AOSP 4.3 to 4.4. Flashing CM10.2 to CM10.1 can cause boot loops, so be sure to have a backup before you attempt any Dirty flashing.
Clean Install vs Dirty Install Rom/Updates via Recovery: (After initial install with Acme3) ->Mpgrimm2 Quote
"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.
See Picture here:
http://rootzwiki.com/uploads/monthly_09_2013/post-130675-0-90084800-1379142203.jpg
"Full Install" Installing Android on the HP TouchPad by using the ACMEINstaller5 to flash zips located in the cminstall folder.
"Full Uninstall and Reinstall" Removing Android with the ACMEUninstaller then Fully Installing Android with the ACMEInstaller5.
Read all about using CWM6 in this great thread by Mpgrimm2:
[RECOVERY] JCSullins' Touchpad CWM6 v6.0.1.9 [2012-12-15]
If this if your first time install Android onto the HP Touchpad, then refer to my Full guide in the 2ND post below!
Android 4.4 Kitkat Test Builds Guide and Links:
[ROM]Evervolv | 4.0.0p1 [AOSP 4.4.2] [3.4 kernel] [TEST] W/UMS,MTP,PTP support
Download 4.4 Kitkat Gapps here:
Notes:Low to Medium battery drain(-4mA to -30mA) Android 3.4 Kernel, h/w video, Audio & Mic, Non Data Media Builds, Automated Updater and Installer, No Camera, No Bluetooth.
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.
and/or
6.To transfer files to PC, turn on USB mass Storage from the USB connection notification on the Android device.
Note(Important): This build Requires that you use a new version of TWRP Recovery with selinux support.
Download openrecovery-twrp-2.6.3.0-tenderloin-selinux.img
[Note(Important): I would recommend increasing the size of your System Partition for this build. After my install I had 398/400MB free, so Flash the 512MB zip below or use Tailor to adjust the size.
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 causes errors and rebooting issues. Always do a clean install when moving from CM to AOSP and vise versa.
Flash through recovery to change the partition size to 512MB(Gradular&codycoyote)
ACMEInstaller4/5 Testing by iMark90 Thread here:
News and Updates Video, ACME4/5 new CWM and TWRP zips by iMarck90:
[ROM][UNOFFICIAL][4.4.2] CyanogenMod 11.0 Nightlies - 3.4 kernel variant By Invisiblek
Download 4.4 Kitkat Gapps here:
Notes:Low to Medium battery drain(-4mA to -30mA) h/w video, Audio & Mic, Test Build Make a Backup!, No Camera, No Bluetooth.
[Note((Warning)): This is a Data Media build and could cause you major problems if the following instructions are not fully read and understood by the user. Once you've made these changes you'll need to run the ACMEUninstall2 to change them back.
[Note(Important): It is recommended to increase the size of your partition from 400-500/600MB using the ACMEInstaller4/5, Tailor in WebOS, or The_apes Flashable zips
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:
cwm_selinux_6.0.5.4_datamedia
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 changes just the Data/Media partition and another changes both the System and Data/Media partitions. Be sure to choose a zip that best accommodates your TP model 16or32GB.
[ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies [2.6/3.0 Kernel]By Milaq
Notes: Low battery drain (-4mA to -30mA) h/w video, Audio & Mic, Nightly Builds, Pie Controls, Inverted Volume Controls, No Camera, No Bluetooth.
[Note((Warning)): This is a Data Media build and could cause you major problems if the following instructions are not fully read and understood by the user. Once you've made these changes you'll need to run the ACMEUninstall2 to change them back.
[Note(Important): It is recommended to increase the size of your partition from 400-500/600MB using the ACMEInstaller4/5, Tailor in WebOS, or The_apes Flashable zips
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:
Data Media CWM 6.0.4.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 changes just the Data/Media partition and another changes both the System and Data/Media partitions. Be sure to choose a zip that best accommodates your TP model 16or32GB.
Android 4.3 Rom Guide and Links:
[ROM] Evervolv | 3.3.0p1 [AOSP 4.3.1] [Nightlies] W/UMS supportBy flintman
(Download)Evervolv | 3.3.0p1 [AOSP 4.3.1] [Test Build] W/UMS support:
Notes:low battery drain(-4mA to -10mA) h/w video, Audio & Mic, Nightly Builds, Automated Updates, Camera works, 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 causes errors and rebooting issues. Always do a clean install when moving from CM to AOSP and vise versa.
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.
and/or
6.To transfer files to PC, turn on USB mass Storage from the USB connection notification on the Android device.
[ROM] Invisiblek Android 4.3 CyanogenMod 10.2 Nightly Builds By Invisiblek
Notes:Low battery drain(-4mA to -10mA) h/w video, Audio & Mic, Camera, No Bluetooth.
Note This CM build does not use the Data Media CWM and is recommended.
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.
and/or
6.To transfer files to PC, turn on USB mass Storage from the USB connection notification on the Android device.
[Note(Important): I would recommend increasing the size of your System Partition for this build. Use the ACMEInstaller4/5, Flash the 512MB zip below or use Tailor to adjust the size.
[ROM] [NIGHTLY] [JB] [4.3] CyanogenMod 10.2 nightlieshttp://forum.xda-developers.com/showthread.php?t=2450358http://forum.xda-developers.com/showthread.php?t=2450358By Milaq
Notes: Low battery drain (-4mA to -10mA) h/w video, Audio & Mic, Nightly Builds, Pie Controls, Inverted Volume Controls, Camera doesn't fully work, Bluetooth.
Note(Important): It is recommended to increase the size of your partition from 400-500/600MB using the ACMEInstaller4/5, Tailor in WebOS, or The_apes Flashable zips
Note:If wifi turns off in suspend/Sleep mode - uncheck wifi optimisation.
-Settings/Wi-Fi/3 Dots/Advanced/Wi-fI optimization (uncheck)
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:
Data Media CWM 6.0.4.5
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 and Invisibleks Roms doesn't need these changes and recommended for average or inexperienced users. This setup should only be done by expert users!
CM10.2 Nightly Video:
Android 4.2.2 Rom Guide and Links:
Jcsullins Full CM10.1 Bluetooth Build [20131210] based on Milaqs Nightly builds:
Notes: Low battery drain (-4mA to -10mA), h/w video, Audio & Mic, Camera, Pie Controls, Bluetooth + Bluetooth tethering.
cm-10.1-20131210-SNAPSHOT-VPN-tenderloin.zip
Drmarbles Post about the new build:
[ROM][4.2.2 CM10.1] <KANG>SCHIZOID 2.11 All-in-One[12DEC2013] By shumash
Notes:Low battery drain(-4mA to -10mA)h/w video, Audio & Mic, Camera works, Pie Controls, AOKP Rom Control, Performance settings(OC), Hybrid Properties, Bluetooth.
Schizoid 2.11 Video:
[NIGHTLY][ROM][JB][4.2.2] CyanogenMod 10.1 nightlies By milaq
Notes: Low battery drain (-4mA to -10mA), h/w video, Audio & Mic, Nightly Builds, Camera works, Pie Controls, Bluetooth.
CM10.1 Builds Video:
[ROM] Evervolv | 3.2.0p1 [AOSP 4.2.2] [Nightlies] W/UMS support By flintman
Notes:Low to medium battery drain(-4mA to -10mA) h/w video, Audio & Mic, Nightly Builds, Camera works! No Bluetooth.
Evervolv AOSP 4.2.2 Video:
[ROM] [4.2] CarbonROM Alpha [7-6-13] By PatrickC
Notes:Low to medium battery drain(-4mA to -10mA)h/w video, Audio & Mic, Camera works, No Bluetooth.
[rom][cm 10.1] |||true tablet ui|| By fahd_freak
Notes:Notes: Low to Medium battery drain (-4mA to -10mA),h/w video, Audio & Mic, Tablet UI(Single navbar at the bottom), No Bluetooth and No Camera.
[ROM] Uncapped 0.5.4.1 (CM10.1) (Android 4.2.2) 7/06/13 *Vanilla Working* By blmvxer
Notes: Low battery drain (-4mA to -10mA),h/w video, Audio & Mic, Pie Controls, Camera works, No Bluetooth.
Re: [ROM] [12/16] How to install jcsullins CM10 Unofficial Preview Builds with Sound
Request a mod to make this a sticky
Sent from my LT30p using xda premium
Re: [ROM] [12/16] How to install jcsullins CM10 Unofficial Preview Builds with Sound
I've been referring people to your rootzwiki thread for awhile. Thanks for making one here.
Found it Roland! I'll PM BigSimon. Don't forget to add the "Edited: 2-13-13" so it matches the date on the Rootz thread, and maybe throw in that picture I posted showing the correct Palm,Inc folder contents.
Re: [ROM] [12/16] How to install jcsullins CM10 Unofficial Preview Builds with Sound
Tnx alot buddy,thats what I looking for,
Sent from my cm_tenderloin using xda premium
Re: [ROM] [12/16] How to install jcsullins CM10 Unofficial Preview Builds with Sound
Wow! Very nice thread! Thank you for making this. Good job.
XDA Rocks
waynekirby said:
Request a mod to make this a sticky
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
bananagranola said:
I've been referring people to your rootzwiki thread for awhile. Thanks for making one here.
Click to expand...
Click to collapse
sina.1993h said:
Tnx alot buddy,thats what I looking for,
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
nickster1 said:
Wow! Very nice thread! Thank you for making this. Good job.
Click to expand...
Click to collapse
Thank you guys We have a great Android community here and i'm glad to be a part of it:good:
mpgrimm2 said:
Found it Roland! I'll PM BigSimon. Don't forget to add the "Edited: 2-13-13" so it matches the date on the Rootz thread, and maybe throw in that picture I posted showing the correct Palm,Inc folder contents.
Click to expand...
Click to collapse
I actually wasn't able to fit it into the title so I added it in a additional post. I just added your Palm, Inc picture, thank you for making it:good:
For RolandDeschain79, updated CM9 packs for your OP...
CM9 20130224 mbt3.5 cminstall.zip - 178.03 MB
CM9 20130224 mbt3.8 cminstall.zip - 178.17 MB
---------- Post added at 04:03 AM ---------- Previous post was at 03:53 AM ----------
RolandDeschain79 said:
I actually wasn't able to fit it into the title so I added it in a additional post.
Click to expand...
Click to collapse
You really need that edited date in the OP if possible. Pehaps you can modify the title to fit for both sites..
[How to] Install Jcsullins CM10 20121216 Unofficial Build - Edited 2/23/13
mpgrimm2 said:
For RolandDeschain79, updated CM9 packs for your OP...
CM9 20130224 mbt3.5 cminstall.zip - 178.03 MB
CM9 20130224 mbt3.8 cminstall.zip - 178.17 MB
---------- Post added at 04:03 AM ---------- Previous post was at 03:53 AM ----------
You really need that edited date in the OP if possible. Pehaps you can modify the title to fit for both sites..
[How to] Install Jcsullins CM10 20121216 Unofficial Build - Edited 2/23/13
Click to expand...
Click to collapse
Hey mpgrimm2, Thanks for the updated CM9 file hosting. I'll update the thread title too:highfive:
Re: [ROM] [12/16] How to install jcsullins CM10 Unofficial Preview Builds Edited 2/2
RolandDeschain79 said:
Known Issues:
-Streaming videos via flash in Web Browsers is glitchy and often only the Audio plays.
Click to expand...
Click to collapse
This is not an issue with the ROM whatsoever. It is a feature of JB.
Sent from my cm_tenderloin using xda app-developers app
Flash videos for CM10
GuyIncognito721 said:
This is not an issue with the ROM whatsoever. It is a feature of JB.
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
Hello, i'm a little confused by your statement. Are you saying that all devices using JB have issues playing flash videos in the Web Browsers? My Note 2 runs flash just fine with the Firefox Beta browser. Of course I had to manually install flash but videos play fine.
Did you see this note and try this method?
-Flash videos work in the Dolphin Browser, if you double tap the video after starting it video
RolandDeschain79 said:
Hello, i'm a little confused by your statement. Are you saying that all devices using JB have issues playing flash videos in the Web Browsers? My Note 2 runs flash just fine with the Firefox Beta browser. Of course I had to manually install flash but videos play fine.
Did you see this note and try this method?
-Flash videos work in the Dolphin Browser, if you double tap the video after starting it video
Click to expand...
Click to collapse
I'm saying it's incorrect and disingenuous to state that problems with flash videos is a "known issue" with the ROM. Sure you can try to sideload it and use a third party browser to try and load flash videos, but when the base of the ROM, Jelly Bean, fundamentally does not support flash, it is not an "issue", and any functionality you achieve should be considered a bonus.
"Known Issues"
GuyIncognito721 said:
I'm saying it's incorrect and disingenuous to state that problems with flash videos is a "known issue" with the ROM. Sure you can try to sideload it and use a third party browser to try and load flash videos, but when the base of the ROM, Jelly Bean, fundamentally does not support flash, it is not an "issue", and any functionality you achieve should be considered a bonus.
Click to expand...
Click to collapse
Thanks for the clarification, I do see your point. However the "Known Issues" section isn't there to list just problems with the specific Rom but the TouchPad problems in general. For-instance the charging issues are not specific to this Rom but to the TouchPad in general. Its simply a very frequently asked question that people should be made aware of, like using the ACMEInstaller3. If you have a look at my RootzWiki thread or YouTube Page you will see that dozens of people have asked about using flash. Adding a simple note about something we know is an issue for many people saves me from having to answer that question over and over again.
Perhaps a little rephrasing is in order like so.
-Streaming videos via flash in the Web Browsers is unsupported in JB and often only the Audio plays.
Note these are "Unofficial Release Notes" because we don't have official release notes.
I do appreciate peoples feedback and I will make some revisions to this. Thank you for your input:good:
Re: [ROM] [12/16] How to install jcsullins CM10 Unofficial Preview Builds Edited 2/2
I think what it is edited to now is more appropriate. Thanks. Also, it would appear the chrome update today alleviated the issues that were plaguing it previously. Anyone else confirm?
Sent from my One X using xda app-developers app
Chrome issues on the HP TouchPad
GuyIncognito721 said:
I think what it is edited to now is more appropriate. Thanks. Also, it would appear the chrome update today alleviated the issues that were plaguing it previously. Anyone else confirm?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Thanks for your input and news about Chrome. I will test Chrome out on my TouchPad, its been so glitchy for so long........
I've Tested Chrome now and it appears to be working normally and without the keyboard disappearing, :victory:
I will now remove the note about chrome not working properly from the OP. Thanks again for testing it out and letting us know.:good:
New CM10 build!
Hello HP TouchPad Users, Great news!
I have just spotted a new Build of Jcsullins CM10 for the HP touchPad, Time for testing! Thank you Jcsullins!
http://goo.im/devs/jcsullins/cmtouc...L-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM.zip
So far everything is working. The only problem so far is the long pause (up to 30 seconds) before OS is ready to be used upon a reboot.
Chrome works fine now as well
Battery life has improved significantly as well, without sacrificing rock solid WiFi.
Still lots more to test. Antutu also gave me a higher score - still much lower than CM9 though.
One thing I noticed in the 20130304 version is that the battery icon one the bottom right doesn't show the lightning bolt when charging as well as in settings. It says discharging even though its connected and charging. The lock screen does say charging though.

[LTE][ROM-AOSP] Unofficial CM10.2 (JB 4.3) [08/07 LTE TEST #3]

Unofficial CyanogenMod 10.2 for the Kindle Fire HD 8.9 LTE
THIS THREAD IS SPECIFIC TO THE LTE VARIANT OF THE KINDLE FIRE HD 8.9". IF YOU HAVE A STANDARD 8.9" MODEL USE THIS THREAD:
http://forum.xda-developers.com/showthread.php?t=2388352
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
**** I DO NOT OWN THE LTE VARIANT OF THE KINDLE FIRE HD 8.9", SO THIS ROM WILL BE A WORK IN-PROGRESS. IF YOU'RE THE EASILY FRUSTRATED TYPE, YOU MAY WANT TO HOLD OFF. ****
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
LTE MODEL Download Information:
[LATEST][08/07 #3] BETA CM10.2 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130807-UNOFFICIAL-jemlte.zip
md5sum: d499384a940dffb3ca7e6ac512fcf370
Older builds can be found in the same folder on goo.im:
http://goo.im/devs/Hashcode/jemlte/cm10.2/
Download Google Apps:
http://goo.im/devs/Hashcode/gapps
(For Android 4.3)
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.
CHANGES:
[08/04] First CM10.2 build for Jem LTE
[07/31] Added RIL setup for LTE
[07/31] First CM10.2 build for Jem
FEATURES:
3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
PowerVR Graphics Drivers: DDK [email protected] for Android (Jellybean compatible)
Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
Audio
Camera
Wifi
Bluetooth
Sensors
HWAcceleration
HD Codecs for YouTubeHD and Netflix
HDMI video out is now correct and work across several resolutions. YMMV
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
[ COMING SOON ]
SCREEN SHOTS:
FOR BUGS / TROUBLESHOOTING:
I need the output from:
adb logcat -b radio > logcat-radio.txt
SAME BUGS AS THE STANDARD VERSION OF KINDLE FIRE HD 8.9"
CURRENT KNOWN ISSUES:
Benchmarks are quite LOW at the moment due to lack of bionic optimizations for OMAP in 4.3. This will probably get worked out over time. DONT COMPLAIN ABOUT BENCHMARKS. YOU HAVE BEEN WARNED.
When long pressing icons in landscape mode to move them, etc the screen will flip upside down for a moment and right itself. This causes the action to be aborted.
Rotation selection in games is hit and miss. Some work perfectly and some like to flip the device upside down. Still debugging what is causing this.
AUDIO: Any decoder which uses Dolby surround current has a lower volume than the rest of the system (Netflix, Google Movies, etc). It's a WIP.
3D Performance: Is only OK. Needs some troubleshooting and perhaps kernel cleanup. Work-In-Progress.
Sensors: Testing various sensors, gyro seems 90 degrees off, etc.
I don't have an LTE version so this is not enabled in current builds.
Great news! Thank you very much.
logcat-radio as you request.
logcat-radio in attachment.
I get it on stock rom.
Thank you.
No LTE setting
Intalled.
But i can't find LTE setting.
GPS not work too.
Bluetooth can't turn on.
tethien said:
Intalled.
But i can't find LTE setting.
Click to expand...
Click to collapse
Same here. Don't have mobile data options under "setting-data usage".
But still many thanks to hashcode! ...and willing to continue testing.
logcat-radio get on this rom
in attachment
I found some issues with my first build and I'll be putting up #2 here in a bit once I iron out some other changes I currently have going.
Hashcode said:
I found some issues with my first build and I'll be putting up #2 here in a bit once I iron out some other changes I currently have going.
Click to expand...
Click to collapse
Sweet!
Updated OP w/ test #2:
LTE MODEL Download Information:
[LATEST][08/06] BETA CM10.2 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130806-UNOFFICIAL-jemlte.zip
md5sum: d2d0be88c07ca9623d3b87e03797a33e
This ROM has a few notable changes:
- It's using the new sensor hardware layer (from source!) which is almost -- but not quite done. So for now, the ambient light sensor doesn't work. All other sensors work. Tho, the gyro still has mixed X and Y axis.
- I did some comparisons to the regular JEM build and noted that rild, the gsm permissions, MMS.apk and Phone.apk are in this build. Obviously, once things start working, I'll want to remove some of that as it doesn't apply but for now thats a good sign.
I need a new logcat -b radio of this build.
Tks god now I can post -_-
Thank you @Hashcode for trying to build rom for us
I follow topic every hour and I have some infomation for you:
-Your first LTE build has nothing about mobile network.
-Your second one has a setting named: emegency alert and setting about which situation and action.
-The Messenger app can't send a messenger to another number.
-No sign of mobile signal, nothing, no data roaming on off, no apn etc ...
-Call at lockscreen doesn't work.
I've tried many rom, but the rom that LTE network worked is stock 8.1.4 that has APN adding option (I'm living in Vietnam so I used local network operator here). The Stari-rom doesn't has APN option but still has network system and can recieve sms.
/// I've just tried to install your 8.4.3 stock rom zip, ithe 3G network worked
Thanks for the input. Did you by chance get the output from "adb logcat -b radio > logcat-radio.txt"?
Sent from my XT926 using Tapatalk 2
installed 0806 rom. still no mobile data options under "Settings - Data usage"
however, under "Settings - more...", there is line saying "cell Broadcasts".
i'm away from home on a business trip. will do the logcat once getting back to the bay area.
thanks a lot, hashcode!
Logcat radio from 0806 rom
As you request.
Thank.
Updated the OP with a new TEST build:
LTE MODEL Download Information:
[LATEST][08/07 #3] BETA CM10.2 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130807-UNOFFICIAL-jemlte.zip
md5sum: d499384a940dffb3ca7e6ac512fcf370
CHANGES:
Fixed the overlay so that mobile data is supported by the OS
Using CM apns.conf file now (it includes the 2x ATT entries from the stock file)
Changed from a "phone" style build to a tablet + mobile data set of packages (No Dialer / MMS)
Need a new: adb logcat -b radio > logcat-radio.txt
Thanks!
The new rom has a Mobile networks settings, but no signal. Maybe this park is for the smartphone hardware and not for tablets. Cuz I see Network Operater doesn't show up at status bar, just a triangle with nothing. And when I was in the network operations setting, it scan for network, manage mobile plan doesn't recognize sim (the stock 8.4.3 does). Or maybe it just setup for AT&T network?
I don't know why I can't get the log file, my computer does recognize as ADB, but when I tried to log, it said waiting for device.
Your rom is improved every update ^^
thanks for your work, bro.
logcat radio from 0807 ROM
waiting your new rom!
gamer941 said:
The new rom has a Mobile networks settings, but no signal. Maybe this park is for the smartphone hardware and not for tablets. Cuz I see Network Operater doesn't show up at status bar, just a triangle with nothing. And when I was in the network operations setting, it scan for network, manage mobile plan doesn't recognize sim (the stock 8.4.3 does). Or maybe it just setup for AT&T network?
I don't know why I can't get the log file, my computer does recognize as ADB, but when I tried to log, it said waiting for device.
Your rom is improved every update ^^
thanks for your work, bro.
Click to expand...
Click to collapse
You must enable "USB debugging" under "Developer option" before run adb command.
Go to Setting/About tablet the press 7 time to "Build number" line. "Developer option" will appear on left menu.
tethien said:
You must enable "USB debugging" under "Developer option" before run adb command.
Go to Setting/About tablet the press 7 time to "Build number" line. "Developer option" will appear on left menu.
Click to expand...
Click to collapse
Oh that's it
I just a newbie started to use android :victory:
tethien said:
waiting your new rom!
Click to expand...
Click to collapse
I'm seeing lines like this in your radio logcat:
W/use-Rlog/RLOG-RIL_VDR( 134): ril_oem.c:194 Failed to set mtu::rc=1,0, cmd=[echo 1400 > /sys/class/net/rmnet0/mtu]
E/use-Rlog/RLOG-RIL_ODL( 134): pktio.c:271 cant open device: device=/dev/ttyUSB0, errno=13
Can you check the following in adb and post it for me?
ls -l /sys/class/net/
ls -l /dev/ttyUSB*
Thanks

[ROM-AOSP] OFFICIAL CM11.0 KFire HD 8.9 (KK 4.4.2) [05/20 AUDIO/CAMERA FIXES]

OFFICIAL CyanogenMod 11.0 for the Kindle Fire HD 8.9
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER AND TWRP 2.7.0.0 INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
NIGHTLY BUILDS SHOULD BEGIN IN THE NEXT FEW DAYS:
Official CM Downloads:
http://download.cyanogenmod.org/?device=jem
Download Google Apps for CM11:
[UPDATED: 01/05] http://wiki.cyanogenmod.org/w/Gapps
Unofficial builds can be found in the mirrors below (cm11 folder for those builds):
Mirror 1: Download (Goo.im)
Mirror 2: Download (Crackflasher)
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) BEFORE UPGRADING TO ANDROID 4.4.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
CHANGES:
[04/14] Kernel cleanup including bugfix for app-asec related APP crashes
[04/14] Partition mount flag cleanup
[03/25] Bugfix for streaming video where stream dies every 4-5mins (specifically Google Play Movies)
[03/15] Testing 128mb of ZRAM use
[03/15] Added KSM and ZRAM to kernel
[03/15] MMC discard / trim fix
[01/17] Kernel updated to google/common 3.0.72
[01/17] "Manufacturer" and "Brand" props changed to: Android / Google for app compatibility
[11/25] First CM11.0 build
[11/15] SElinux now included in the kernel and set to permissive. I don't recommend turning it to enforcing as I'm still debugging the "deny" messages.
[08/12] All new "from source" sensor driver
[08/12] Temp. disable light sensor (due to recode of sensor driver)
[07/31] First CM10.2 build
FEATURES:
3.0.72 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
PowerVR Graphics Drivers: DDK [email protected] for Android (Jellybean compatible)
Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
Audio
Camera
Wifi
Bluetooth
Sensors
HWAcceleration
HD Codecs for YouTubeHD and Netflix
HDMI video out is now correct and work across several resolutions. YMMV
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
[ COMING SOON ]
IGNORE THE LINE BELOW THIS SAYING THIS ROM IS FOR THE KINDLE FIRE HD 7". IT'S NOT. IT'S FOR THE KINDLE FIRE HD 8.9".:
XDA:DevDB Information
OFFICIAL CM11.0 KFire HD 8.9 (KK 4.4.2), ROM for the Amazon 7" Kindle Fire HD
Contributors
Hashcode
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2014-05-20
Created 2013-11-26
Last Updated 2014-05-27
Reserved
KNOWN ISSUES:
Bluetooth tether (to say a phone for internet) doesn't seem to be working correctly
Accelerometer can stop working occasionally. Needs debugging.
Ambient light sensor needs to be re-coded as an IIO driver
Headphones / BT audio route testing (plugging / unplugging can cause stuck audio)
Fix USB OTG support in the kernel
Better HDMI support for more resolutions
No Amazon Prime Video support
No Dolby audio support
"Cast Screen" does not function correctly under Settings -> Display
[FIXED-2014-05-20] Audio HAL cleanup and use system/media audio-route sources
[FIXED-2014-05-20] More camera tweaks
[FIXED-2014-05-13] Hardware Decoder/Encoder support update to KK-based sources
[FIXED-2014-05-13] Camera could use a small update for better handling
[FIXED-2014-05-02] Audio low latency issues when cover is closed or 2 apps play audio at once (stuttering)
[FIXED-2014-04-18] VPN has issues, needs debugging
[FIXED-2014-04-18] Some games like Plants Vs. Zombies 2 don't work right, researching
[FIXED-2014-04-15] Possible other game issues, but I need more examples of games that don't run
so are you gonna abandon the cm10.2 development?
i was trying to flash it a few days ago, but it didn't work...now of course this one would be nice, but it's still in an erly development i suppose^^
---------- Post added at 09:57 AM ---------- Previous post was at 09:57 AM ----------
so are you gonna abandon the cm10.2 development?
i was trying to flash it a few days ago, but it didn't work...now of course this one would be nice, but it's still in an erly development i suppose^^
Thank you !!!!!!!!!!
Thanks a lot...
No problems during installation.
Until now it works like a charm...
dirthy flash from cm10.2 without problems
cache+dalvik wiped...
Installed on my Jem LTE.
-install completed with no problems.
-Run very smooth.
-Icon drag bug come back
Thank Hashcode.
Waiting for Jem LTE version.
I don't know how you do it man, but you've always got something new and awesome every single day for me, whether it's my KFHD or my S4, so thanks for being awesome!
Downloading now.
Cannot get this to install. It just gets stuck at the blue kindle fire logo. ANY ROM I flash ends up this way.
Sent from my SCH-R530M using Tapatalk
legmando33 said:
Cannot get this to install. It just gets stuck at the blue kindle fire logo. ANY ROM I flash ends up this way.
Sent from my SCH-R530M using Tapatalk
Click to expand...
Click to collapse
Please make sure you're flashing this with the latest TWRP 2.6.3.1 and that you've done the required wipe + advanced -> format system.
Hashcode said:
Please make sure you're flashing this with the latest TWRP 2.6.3.1 and that you've done the required wipe + advanced -> format system.
Click to expand...
Click to collapse
Okay I'll try that. Thanks Hashcode.
Sent from my SCH-R530M using Tapatalk
I am unable to get the new Amazon AppStore to run on this rom. Immediately force-closes. The same problem happened when updated the Amazon appstore on the 11-15 CM10.2 build. There is a similar comment on that thread by another user but without reply.
I tried re-installing, clearing data, and even a full wipe and clean install but to no avail.
Any suggestions?
P.S. No post in this forum should go without thanking Hashcode for his time and efforts. Without him, this tablet isn't good for anyone between 5-60 years old.
mssaleh said:
I am unable to get the new Amazon AppStore to run on this rom. Immediately force-closes.
Click to expand...
Click to collapse
Juppp... same here installed the old Version of the store, everything is OK.
Wow thank you so much! I wish there was some way I could help but I only know the basics on programming but I am more than willing to help in any way. I really hope this improves the device with kitkats memory management
Having lots of problems
First I did a backup (TWRP 2.6.0.1 or something dont remember exactly but older version)
Then I updated TWRP to the newest one
After that I restarted recovery it seams to work fine (other then USB mount which would be very very much appricated if it worked) I wiped System and Seamed to Working like it should
Then I did factory reset and then advanced wipe System
after that I installed the 2 files for CM11 and Gapps
CM11 will look like its starting then go really fast and say success but really do pretty much nothing
the GAPPs will just fail
Now I cant restore the file from the older TWRP since its in a different folder and it fails when i use the file managment to move it to the correct folder..
I cant ADB push a rom file to try an older version of CM ADB sideload also fails Smaller files Like TWRP work but not Roms and this is plenty of open space that is not a problem
Right now I cant install anything but TWRP
Is anyone else having problems?
Thanks!
Just wanted to say Thanks Hashcode, really pleased and surprised to get KitKat for my Kindle, especially so early.
I did a clean install (wipe system, data and cache) with the newest TWRP and then enabled Art as the runtime environment and so far everything seems to be working ok. Installed rotate app to take care of the rotation bug and so far not found any other problems.
Thanks again
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
narse said:
Installed rotate app to take care of the rotation bug and so far not found any other problems.
Click to expand...
Click to collapse
Which one do you have installed? There are so many diiferent apps on playstore
Bastlwastl2010 said:
Which one do you have installed? There are so many diiferent apps on playstore
Click to expand...
Click to collapse
I use https://play.google.com/store/apps/details?id=nl.fameit.rotate. There is a 7 dart trial, but I use the paid for version. It has always worked well for me.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Here's a test CM11 build which seems to fix the rotation/orientation issues - at least for me far as I can tell.
http://d-h.st/users/loosethisskin/?fld_id=28911#files or http://goo.im/devs/loosethisskin/jem/cm-11.0
@Hashcode ... the relevant commit is here: https://github.com/loosethisskin/an...mmit/f5c558fa4acee3b793be6e1de9949e9624014c55
It's a first version and will need to be modified if it's worth pursuing (e.g. make it property driven). The change should have a result similar what apps like Rotation Control do. I am forcing sensor (landscape) orienation for every landscape or reverse landscape request.
Let me know...
lizzord30 said:
Having lots of problems
First I did a backup (TWRP 2.6.0.1 or something dont remember exactly but older version)
Then I updated TWRP to the newest one
After that I restarted recovery it seams to work fine (other then USB mount which would be very very much appricated if it worked) I wiped System and Seamed to Working like it should
Then I did factory reset and then advanced wipe System
after that I installed the 2 files for CM11 and Gapps
CM11 will look like its starting then go really fast and say success but really do pretty much nothing
the GAPPs will just fail
Now I cant restore the file from the older TWRP since its in a different folder and it fails when i use the file managment to move it to the correct folder..
I cant ADB push a rom file to try an older version of CM ADB sideload also fails Smaller files Like TWRP work but not Roms and this is plenty of open space that is not a problem
Right now I cant install anything but TWRP
Is anyone else having problems?
Thanks!
Click to expand...
Click to collapse
I'm getting the same thing. Also did the same with updating recovery. Had 2.6.0.0 before updating. Now even with the recommended wipes it won't boot, just stuck on blue kindle fire logo. =(
Sent from my SCH-R530M using Tapatalk

[ROM GUIDE]How to install Android 5.x.x/4.4.x with Jcsullins TPtoolbox Super Easy Way

Additional resources:
RootzWiki Version of this thread
Touchpad Toolbox Main Thread By Jcsullins
[ROM GUIDE] How to Install Android 7.x Nougat builds on the HP TouchPadhttp://forum.xda-developers.com/hp-...p-touchpad-t3512182/post69912613#post69912613http://forum.xda-developers.com/hp-...p-touchpad-t3512182/post69912613#post69912613
[ROM GUIDE] How to Flash Install Android 7.x/6.x/5.x.x/4.4.x HP TouchPad Roms(How to update your Roms)
Video Guide for this thread:
How to install Android 5.0.x/4.4.x on the HP TouchPad Video
https://www.youtube.com/watch?v=Ysii0DBQ7V4
Video Timecode:
Data Media Q & A (What's the TP Toolbox?) @ 1:30
What is a data media [email protected] 2:38
What are the Advantages/Changes for Data Media Builds? @ 4:14
How can I go back to my old setup? @ 5:15
How can I check my current Android version and System Partition size? @ 5:40
1)Getting started, Requirements and Preparation: @ 6:07
2)(Optional)Time to Choose the Fate of WebOS: @ 7:40
3)Enter webOS recovery mode and connect the Touchpad to your PC with the USB cable: @ 12:36
4)Download, extract and run the latest version of Jcsullins Touchpad Toolbox on your PC: @ 13:52
5)Using the TouchPad Toolbox to install Android: @ 15:05
Extra uses for the Touchpad Toolbox: @ 22:55
Q & A:
Read all the background information about The TPtoolbox and Data Media builds here:
What is the TouchPad Toolbox?
The Touchpad Toolbox(TPToolbox) is an easy to use and reliable tool that replaces previous methods of installing Android onto the HP Touchpad. This excellent tool created by Jcsullins has dramatically simplified the installation of the latest Lollipop and Kitkat Data Media builds onto the Touchpad. The TP Toolbox can also install a few non data media roms, which will be listed in the guide below. In addition it gives users the ability to completely remove WebOS if desired.
It replaces the following procedures and tools:
-ACMEInstallers
-ACMEUninstallers*
-Various methods of resizing partitions/volumes (erroneously called partitions)
-Various methods of reflashing the A6 battery monitoring chip
-Various methods of completely wiping/recreating volumes
What is a data media build?
Previously on the HP Touchpad Android and WebOS shared SDcard space in the media partition. This was the space you saw when transferring data via the USB cable. It stored all your media like music, pictures and movies. Data media builds separate the Android and WebOS space by emulating a 2nd ext4 SDcard in the data partition. The place where your app data was stored, separate from the SDcard media partition. With this setup the data partition now becomes the main place where your apps and users files(Music, pictures, movies, ect) are stored. The left over space in the media partition is now separate and only used by by TP Toolbox or WebOS. The media partition/volume will only be left with a small amount of free space and the majority will be given to the Android Data partition. If you keep WebOS the space will be around 1.17GB with V3.0.5 and lots of apps/preware, if you remove WebOS it will be around 600-800MB, so the total cost for WebOS is about 500-600MB.
What are the Advantages and Changes for Data Media Builds?
Data media builds change the default partition layout to more efficiently use the available space. You get a larger area for storing apps and mount an emulated ext4 SDcard on the Data partition. The ext4 doesn't suffer from the 4GB file size limit that the older Fat partition had and gives you more space for large apps. “Performance on ext4 in Android is also probably better than FAT.” The next advantage for HP TouchPad users is the updated 3.x Kernels all the new Android 4.4.x/5.x.x builds use. The updated Kernel's more efficiently communicates and allocates resources between the hardware and software.
What is a data media device?(TeamWin)
How can I go back to my old setup?
I don't want to keep WebOS installed:
Use the TPToolbox to do a complete data rest on your tablet. Install an android 4.2.2 roms, gaps, and recovery. Transfer your backup onto the touchpad, reboot into recovery and restore it. Note: You will need to make sure you have a compatible recovery installed to restore your backup.
Or
I want to keep WebOS installed:
If you wish to go back to your previous setup you can run the ACMEUninstaller2 then install just CWM and moboot with the ACMEInstaller5. You can now Boot into recovery and restore your older backup. Note: That you can use Jcsullins and Philz Touch DM-CWM recoveries to restore your older nandroid backups. Data media recoveries can see both SDcards while restoring your backups. The Data partition will show up as SDcard and the Media Partition as SDcard1.
How can I check my current Android version and System Partition size?
-Get the free app,Quick System Info PRO, to check the size of your partitions and remaining free space.
-Check your version of Android by going to settings/About Tablet/Android Version.
1)Getting started, Requirements and Preparation:
A)You must have Java and the novacom software installed on your PC before running Jcsullins Touchpad Toolbox.
You will need to have Java installed to run the Universal installer. Click here:
Download and run the Universal Novacom Installer 1.4.1. Click here:
OR
Download the Novacom files and manually install them here or here
Note: You may need to reboot after installing this software.
Note: If you're having issues getting the Novacom drivers installed disable any antivirus or spyware protection that might be preventing the app from downloading the correct drivers for your system.
B)Backup, Backup, Backup, Using the "Complete Data Reset" feature of the TPtoolbox or the "Erase USB drive" from WebOS, will delete absolutely everything on your HP TouchPad including the SDcard! So you will want to make sure you have your personal data files(music, pictures, videos, etc.) backed up on your computer. Don’t forget to move your Nandroid backups onto your PC. By default CWM backups are located in SDcard/clockworkmod/backup.
NoteMake sure your tablet is fully charged before starting any install procedure on the HP TouchPad. Running out of batteries during an install procedure will ruin the process and possibly damage the device.
2)(Optional)Time to Choose the Fate of WebOS:
Note: If you wish to remove WebOS, or have already removed it, just skip to step # 3
Before running the Touchpad Toolbox you should decide whether or not you wish to completely remove WebOS. Even if you remove WebOS there will still be around 600-800MB of space left where it used to be on the media partition/volume. That extra space will only be used for the initial install of your roms via the TouchPad Toolbox. This space will not be accessible from some roms and will only be used by the TPToolbox or WebOS. So you must make a personal decision about WebOS’s usefulness to you. Would you rather have extra free space or a second OS that is unique but not well supported?
On my 32GB Touchpad I have a maximum of 27.5GB available. With Android, WebOS(V3.0.5) lots of apps/preware and the free space required to use the TPToolbox(600MB+) it takes up around 1.17GB. If you remove WebOS the remaining media space will be around 600-800MB, so the total cost for WebOS is only about 500-600MB Click here. You will need to boot into WebOS to access its media SDcard space or use either the Jcsullins CM11 or Evervolv DM Kikat roms. Personally I like WebOS and think having a dual boot device is one of the unique and intriguing features of owning an HP TouchPad, the choice is yours.
Note: Official WebOS support ends March, 15, 2015 see video below.
-If you previously removed WebOS but want to add it back use Jcsullins instructions click here:
-If you need to bypass the WebOS activation get the tool and instructions click here:
If you wish to keep WebOS then do the following steps:
Uninstall Android and Clean up your SDcard:
A]Uninstall Android completely by using the ACMEUinstaller2, watch the instructional video below. After uninstalling Android you will automatically reboot to WebOS.
How to use the ACMEUninstaller2 (Short Version)
1)Install the Novacom software(You installed this in step 1)
2)Next place this ACMEUninstaller2 file into the Novacom folder.
-By default this folder will be located on your PC @ C:/Program Files/ Palm, Inc. Mac OS X users will find this folder @ /opt/nova/bin.
-Download the ACMEUninstaller2 file and copy and paste it right into either of those directories.
3)Boot the tablet into WebOS recovery mode and attach it with the USB cable to your PC.
Download and extract these ACME5 batch files and run the "removecm2.bat" file to uninstall Android.
Or
Open a command prompt and type the following:
On Your PC
cd c:\Program Files\Palm, Inc (enter)
novacom.exe boot mem:// < ACMEUninstaller2 (enter)
On your Mac
cd /opt/nova/bin (enter)
./novacom boot mem:// < ACMEUninstaller2 (enter)
How to enter WebOS recovery mode from Android:
-If you currently have Android installed you can hold down the power button choose reboot and select "webOS recovery mode" from the moboot menu.
Connect the HP Touchpad to your PC via the USB cable.
Or
How to enter WebOS recovery mode from WebOS:
-Reboot the HP Touchpad via WebOS rest options menu located @ launcher/settings/device info/reset options/restart.
-Hold down the volume up button while the Touchpad reboots. Once you see the large USB symbol on the screen release the volume button.
Connect the HP Touchpad to your PC via the USB cable.
B]Now from WebOS we will wipe our SDcard before the TPtoolbox can setup our partition/volumes. Completely wipe your SDcard by booting into WebOS and going to, launcher/settings/device info/reset options/erase USB drive. The Touchpad will then reboot itself and the data will be completely erased. Note:This will not affect your WebOS setup, apps or Preware.
View attachment 3127243
3)Enter webOS recovery mode and connect the Touchpad to your PC with the USB cable:
Note: Even if you choose to remove WebOS, the WebOS recovery mode will still exist as it's part of the bootloader.
How to enter WebOS recovery mode from Android:
If you currently have Android installed you can hold down the power button choose reboot and select "webOS recovery mode" from the moboot menu.
Connect the HP Touchpad to your PC via the USB cable.
Or
How to enter WebOS recovery mode from WebOS:
Reboot the HP Touchpad via WebOS rest options menu located @ launcher/settings/device info/reset options/restart.
Hold down the volume up button while the Touchpad reboots. Once you see the large USB symbol on the screen release the volume button.
Connect the HP Touchpad to your PC via the USB cable.
4)Download, extract and run the latest version of Jcsullins Touchpad Toolbox on your PC
-Download Jcsullins latest Toolbox v42 below(replaces v40, v41x)
Download TPtoolbox v42 mirror
Download TPtoolbox v42 mirror
-Extract the TPToolbox v42 zip file and open the folder.
On Windows, run the batch file named tptb_v42_win.bat
On Linux, run the script named tptb_v42_nix.sh
On Mac, run the script named tptb_v42_mac.command
5)Using the TPtoolbox to install Android
-The TPToolbox consists of 3 different panels, 1 menu, 2 help, and 3 output, see picture.
-Use the volume button to navigate the menu and the home button to make selections.
View attachment 3127242
A)(Optional) Complete Data Reset, Completely Removes WebOS and Android
-The procedure will completely remove WebOS and Android from the device. The partitions/volumes will be rebuilt new and boot will be remade with a minimal amount of programs provided by the TPToolbox.
-Scroll down to Complete Data Reset and select it with the home button and choose yes to begin the process.
-If you previously did step number 3 then skip this step and proceed to step B.
-If you previously removed WebOS but want to add it back use Jcsullins instructions click here:
-If you need to bypass the WebOS activation get the tool and instructions click here:
View attachment 3127241
B)Installing Android onto the HP TouchPad
-scroll down to Install Android from the menu and select it with the home button.
-The TP Toolbox will mount the media partition/volume to your PC. Open the Touchpads Media partition/volume and look for the “ttinstall” folder. Place the Rom, Recovery and Gapps zips into the “ttinstall” folder.
-The Rom contains the Android operating system, the Gapps package contains all your Google apps and the Recovery allows for installation, restoration, and maintenance operations on your Android device.
View attachment 3127244
Download Recommended default setup
Rom:Download the latest Lineage11 build
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-base-arm-4.4.4-20170902-1-signed.zip
Note: Do Not unzip the files.
TPToolbox checks your File's
-The TPtoolbox will now check the files for compatibility then begin to set your partitions/volumes based on the type of Rom you’ve selected. If it fails to run it will display which file is incompatible, start the install again and replace the offending file(s).
TPToolbox creates your Volume/Partition layout
-The output window will display the Pending Android Installation details; the partitions/volumes resize details that are about to be setup on your HP Touchpad. Review this information and confirm the layout by selecting yes. This starts the partitions/volumes resizing, followed by the Auto Android installation from your chosen recovery.
Note: All HP Touchpad sizes are supported, 16GB, 32GB, 64GB.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lollipop/Kitkat DataMedia Volume (re)sizing criteria
system: MIN_SIZE: 700-800MB
cache: MIN_SIZE: 200MB
data: MIN_SIZE: 1500MB
data: also takes any free-space "media" has over 600MB
Legacy Non Data Media Volume (re)sizing criteria
system: MIN_SIZE: 600M
cache: MIN_SIZE: 200MB
data: MIN_SIZE: 1500MB
TPToolbox Auto Installs your Rom, Gapps and Recovery(Please stand by..)
-The details of partition/volume resizing will scroll across the Toolboxes bottom output window(Bottom) and the device will auto reboot into your chosen recovery. The Rom and Gapps package will now be installed automatically, this may take a few muintes, Please stand by..... Once complete the Touchpad will restart and boot into Android. Be patient, it my take several minutes before the HP Touchpad completes it first boot into Android.
Note(Important): If the TP Toolbox fails to run several times you may get an error message when trying to mount the volume during the install. To fix this rerun the complete data reset or wipe the USB drive from WebOS.
How to change Roms or update your version of Android:
TPToolbox Method:
After installing a data media rom you can do a clean install of another Rom listed in the guide by again using the TPtoolbox. Return to step 5 B) and install a different Rom. The TPtoolbox will wipe the system, data and cache partitions/volumes and do a clean install, WebOS will not be changed. Your apps and user data will be lost but your media content on the SDcard remains the same. If you wish to completely remove WebOS, Android and all data on the device return to step 5 A) and do a complete data reset.
Note: When installing new roms the TPtoolbox will automatically prompt you to adjust smaller system partitions/volumes from older versions of the TPtoolbox(v40, v41x). For example a 700MB Kikat install will be increased to 800MB for Lollipop or a new Kitkat Rom install.
Recovery Method:
Updating your current Rom with a newer build can be done using your recovery and will keep your current setup and apps. However, this can't be done from the TPtoolbox and will require learning about a few Rom flashing techniques from my instructional update guide below.
How to Flash Install Android 6.0.1/5.x.x/4.4x Builds on the HP TouchPad
Using this Rom Guide:
-Select One of each, Rom, Gapps, and Recovery .zip files to download and install with the TPtoolbox(Do Not unzip the files).
-The Rom contains the Android operating system, the Gapps package contains all your Google apps and the Recovery allows for installation, restoration, and maintenance operations on your Android device.
-Each Rom requires a corresponding Gapps package for its version of Android. 4.4.x Roms need 4.4.x Gapps, or 5.x.x. Roms need 5.x Gapps.
-Each Rom has notes about its details and a rating for the battery drain during deep sleep.
-Three recovery types are available to choose from; each does the same tasks but the interface is different, CWM, Philz CWM, TWRP.
-For some Roms one of the recoveries may be recommended by the developers, always check their threads and read all notes.
Which Rom should I choose?
-Currently the Android 4.4.x Kitkat Roms are the most mature, stable and fully functional. I would recommend them as your daily driver.
-Android 5.x.x Lollipop Roms are in developmental but aren't as fully functional as 4.4.x Roms. The battery life is shorter and more bugs have been reported.
-Some Android 5.1.x Lollipop Roms and No Android 6.0.1 Roms may not be fully compatible with the current TPtoobox version42 and may need to be installed by flashing through recovery.
-It takes several months after the initial release of a new android version for it to become mature and stable. Please see the developers threads for the latest details about their Roms, Happy Flashing.
Compatible Data Media Recoveries (TPtoolbox v42):
Note: These recoveries are meant to be used with TPtoolbox v42 and v41x
Download Philz Touch CWM Recovery:
Philz-CWM-jcs-dm-tenderloin-20140612 via mediafire:
Philz-CWM-jcs-dm-tenderloin-20140612 via androidfilehost:
Download TWRP Touch Recovery:
TWRP-jcs-dm-tenderloin-20140612b via mediafire:
TWRP-jcs-dm-tenderloin-20140612b via androidfilehost:
Download standard Non-Touch CWM Recovery:
update-CWM-jcs-dm-tenderloin-20150703 via androidfilehost:
CWM-jcs-dm-tenderloin-20141231 via mediafire:
Android 4.4.x Kitkat Data Media Rom Guide and Links:
[ROM] [NIGHTLY] [KitKat] [4.4.4] CyanogenMod 11.0 nightlies [3.0 Kernel] By Milaq(Roland Recommended)
Rom Details: Low to medium battery drain (-5mA to -20mA), h/w video, Audio, Camera, Bluetooth, Inverted volume controls, Performance OC tab, Milaq Update app.
Note:This Rom still gets regular updates
Note: Automated Milaq updater app (downloads and installs new builds for you)
Note:Increased default CPU clock from 1188Mhz-1512Mhz,
[ROM] [4.4.4][3.0 Kernel][CyanogenMod 11 by Jcsullins] [DM] By Jcsullins(Roland Recommended)
Rom Details: Low to medium battery drain (-5mA to -20mA), h/w video, Audio, Camera, Bluetooth, Inverted volume controls, Performance OC tab.
Note:This Rom can see both SDcards
Note:This is the most popular Rom
Click Here to watch the [ROM] [4.4.4][3.0 Kernel][CyanogenMod 11 by Jcsullins] [DM] video:
https://www.youtube.com/watch?v=CQCrm-Otxmw
[ROM][OFFICIAL][KitKat 4.4.4][TENDERLOIN] PAC-man KK RELEASE [DEV] By Shumash(Roland Recommended 4 Gamers)
Note: Download the Final stable PAC-man build here:
Kernel 3.0: Low to medium battery drain(-5mA to -20mA), Antutu Score=12000+
Kernel 3.4: Medium battery drain (-30mA to -60mA), Antutu Score=13000+
Rom Details: h/w video, Audio, Camera, Bluetooth, Inverted volume controls, PAC Console (OTA updates), PAC Performance settings (overclocking), Increased 2D & 3D GPU clocks up to 320Mhz, Increased default CPU clock from 1188Mhz-1512Mhz, overclocks up to 1782Mhz(3.4 Kernel), 1890Mhz(3.0 Kernel) Great for Gamers.
Note: The Pac Performance app is missing from newer builds install the free Kernel Adiutor app here
Note:Using the lock screen may cause SOD(sleep-of-death), disable it by going to Settings->Security->Screen Security->screen lock=none.
Note:Hold down power and home together if the screen is black(SOD) and you need to reboot.
Note:This Rom can see both SDcards
Click Here to watch the [ROM][OFFICIAL][KitKat 4.4.4][TENDERLOIN] PAC-man KK RELEASE [DEV] video:
https://www.youtube.com/watch?v=Y3B0nU8Ld2Y
[ROM] Evervolv | 4.0.0p1 [AOSP 4.4.2] [3.4 kernel] [Nightlies] With /data/media By Flintman
Rom Details: Medium battery drain drain(-20mA to -30mA), h/w video, Audio, Camera, Bluetooth, Automated Updater
Note:This Rom can see both SDcards
[ROM] [Tenderloin] [4.4.4] [DATA/MEDIA] TeamEOS - The Revival || Nightlies By Team EOShttp://forum.xda-developers.com/hp-touchpad/development/rom-teameos-revival-nightlies-t2829311http://forum.xda-developers.com/hp-touchpad/development/rom-teameos-revival-nightlies-t2829311http://forum.xda-developers.com/hp-touchpad/development/rom-teameos-revival-nightlies-t2829311
Rom Details:Low to medium battery drain (-5mA to -20mA), h/w video, Audio, Bluetooth, No Camera
Note:If you can't connect the USB in Win7/8.1 go to settings/Developer options/USB debugging and (Uncheck the box)
Note: Enable the developers tab by going to "About tablet" and clicking on the "Build number" 7 times.
Note: Download the Final build here:
Click Here to watch the [ROM] [Tenderloin] [4.4.4] [DATA/MEDIA] TeamEOS - The Revival || Nightlies video:
https://www.youtube.com/watch?v=pRnDTJJRCJo
4.4.x Gapps Downloads:
gapps-444-base-20160602-1-signed.zip
Android 5.x.x Lollipop Data Media Rom Videos:
https://www.youtube.com/watch?v=s7vLuQGjptI
Android 5.1.x Lollipop Data Media Rom Guide and Links:
[ROM] [5.1.x] [CyanogenMod 12.1 by Jcsullins] [DM]
-Note: use this TWRP-jcs-dm-tenderloin-20140612b recovery
Rom Details: h/w video, Audio, Camera, Bluetooth.
[ROM][OFFICIAL][Lollipop 5.1.1][TENDERLOIN] PAC-ROM LP-MR1
Rom Details: h/w video, Audio, Camera, Bluetooth.
[ROM] [EXPERIMENTAL] [Lollipop] [5.1] CyanogenMod 12.1 nightlies [3.0 kernel]
5.1.x Gapps Downloads:
gapps-511-base-20160602-1-signed.zip
Gapps Downloads all versions:
OpenGapps
CM Gapps downloads
Delta Gapps Downloads
Legacy Roms & Extra uses for the Touchpad Toolbox :
Legacy Non-Data Media Roms, Gapps and Recovery below: Warning do not mix Non-data media and data media files when using the TPToolbox.
Note: If you accidentally mix the two file types you may need to run the "Complete data rest" or the "Erase USB drive" procedure again before you can install android.
Android 4.2.x Non Data Media Rom Guide and Links:
[ROM][4.2.2 CM10.1] [3.0 Kernel] Bluetooth Test builds By Jcsullins
Rom Details: Low battery drain (-5mA to -10mA), h/w video, Audio, Inverted volume controls, Bluetooth, No Camera.
Click Here to watch the Jcsullins Kernel 3.0, CM10.1 Build video:
https://www.youtube.com/watch?v=asE0lzs9A-I
[ROM][4.2.2 CM10.1]-SNAPSHOT-Jcsullins-VPN-tenderloin-20131210 By Jcsullins
Rom Details: Low battery drain(-4mA to -10mA), h/w video, Audio, Inverted volume controls, Pie Controls, Camera, Bluetooth.
Click Here to watch the HP TP News: Jcsullins Fixes Bluetooth Support video
[/URL]
https://www.youtube.com/watch?v=bRMOV7AZt74
[ROM] [4.2.2 CM10.1] <KANG>SCHIZOID 2.11 All-in-One [12DEC2013] By Shumash (Roland's Favorite for Gaming)
Rom Details: Low battery drain(-4mA to -10mA) h/w video, Audio, Camera, Bluetooth, Pie Controls, AOKP Rom Control, Hybrid Properties, Performance settings(OC), Custom Kernel Overclockable to 2157MHz, Increased 2D & 3D GPU clocks up to 320Mhz, Great for Gamers.
Click Here to Watch the Schizoid 2.11 All-in-one video:
https://www.youtube.com/watch?v=-1OmUwr1yWs
4.2.x Gapps Download:
Android 4.2 20130812 CM10.1 Gapps:
Supported Non-Data Media Recoveries Downloads:
Note: These recoveries are meant to be used with TPtoolbox v42 and 41x
Download Philz Touch CWM Recovery:
Philz-CWM (NODM 2014-06-14) via mediafire:
Philz-CWM (NODM 2014-06-14) via androidfilehost:
Download TWRP Touch Recovery:
TWRP (NODM 2014-06-14b) via mediafire:
TWRP (NODM 2014-06-14b) via androidfilehost:
Download Traditional Non-Touch CWM Recovery:
CWM (NODM 20141231) via mediafire:
CWM (NODM 20141231) via androidfilehost:
Extra uses for the Touchpad Toolbox:
Reflash A6 Firmware:
https://www.youtube.com/watch?v=NnWH7FhaMg4
The Problem:
HP Touchpad developer Jcsullins, has informed HP TouchPads users that there's a problem with our HP Touchpas A6 Firmware. This issue can cause an usually high battery drain during sleep. This problem occurs overtime while running both Android and WebOS. As a result the Touchpads battery drains more quickly with daily use and the overall life span is reduced. If your battery drain seems to be much higher on average, then flash the A6 Firmware to bring it back down. Users experiencing sudden drops in battery life should run this as well.
The Solution:
Reflashing the A6 Firmware effectively fixes the problem but may need to be repeated as a part of regular HP TouchPad maintenance. I would recommend reflashing it ever few months to maintain good battery health. Watch this video and follow the step by step instructions to reflash your own Touchpads A6 Firmware.
How to test:
-To monitor your battery drain history during sleep install the free app Battery Monitor Widget:
-Once installed open the app and go to history, click the heading at the top "%/h" to change it to "mA".
-You can now monitor the history and compare it to the information in my rom guide.
Mount Media Volume:
Allows you to access the 'media' volume from your PC
Resize Android Volumes:
This allows you to interactively resize the Android (and media) volumes.
This is not needed to "Install Android", but can be used at other times to 'tweak' the volume sizes as needed.
Repair Android Volumes:
If a fsck (file system check) determines that there are non-trivial errors on a filesystem, then this can be used to attempt to fix those errors.
Create webOS Volumes:
If you want to re-install webOS following a "Full Data Reset," you will need to run this prior to running webOS doctor.
At this time, re-installing webOS should only be done prior to installing Android. Tools to assist re-installing webOS after
Android has been installed (without detriment to the Android install) may be provided in the future. Full instructions for reinstalling WebOS here.
Future development and limitations:
Only Touchpad Wifi supported (not 4G) at this time, use the instructions here to install the Evervolv 4G data media build.
Support for non-KitKat/DataMedia installs very limited for now.
Re-install of webOS after Android installed is not supported yet.
Method for permanently installing TPToolbox (always available via moboot) not available yet.
The main focus at this time is providing a reliable method to install KitKat/DataMedia ROMs.
Additional/expanded legacy and/or other install types will be implemented after demand for such is determined.
News and Updates:
https://www.youtube.com/watch?v=ISWZ0c48gNA
reserved
Troubleshooting:
HP TouchPad | WebOS Activation Bypass Video
https://www.youtube.com/watch?v=IjtLNL-Lspc
Download WebOS activation package for the HP TouchPad:
Notes, Fixes and Tweaks:
Note:The following are Solutions for the most Frequently asked questions and problems.
Battery Saving Tips
1)a) Keep your Touchpad in deep sleep and reduce the battery drain by disabling Google Play SystemUpdateService:
-Go to Settings > Privacy > Privacy Guard > Advanced (3 dot menu) > Google Play services and disabled "Wake up" and "Keep awake".
b)If your tablet repeatedly doesn't wake up from sleep and has to be rebooted, then do the following :
-Google Settings\Search & Now\Voice"Ok Google" Hotword detection\ Toggle the switch to off and see if that helps.
Note: This can also help to reduce high battery drain during sleep.
c)Turning off "network location services" might help to improve overall battery drain and longevity.
-Settings/location access/ access to my location set to off
-You may wish to monitor your battery drain history during sleep.
-Install the the free app Battery Monitor Widget:
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to either 6300 (F29C) or 5800 (S29C) and tap OK
-Note* See the Battery p/n # on the original packaging.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
2)How to fix "Unfortunately Google Play Services Has Stopped"
Settings > Apps > Scroll Right to All Apps > click on 3 dots on top right > Select Reset Preferences
3) Android 5.x.x Root premission fix
-Rooted permission might be missing from your android 5.x.x rom, fix it by do doing the following.
1)Install the Superuser app on your Android device here
2)Download and flash this Superuser .zip file here through recovery to get the permissions working.
4)If you're moving from Evervolv to CyanogenMod and your TP sees and tries to boot Evervol.
- (Mpgrimm2) I have modified JcSullin's "Set CyanogenMod as Moboot Default zip to also delete the Evervolv ROM from /boot to prevent you from running out of space. Thanks to JcSullins and Flintman for the original zips and script templates.
Flash the zip after a wipe/format and before flashing a CM rom zip.
Download JCs-update-boot-cm-default_Plus-DELETE-EV .zip
5)If your Touchpad skips moboot and boots right into Android, then do the following:
-Hold the home key while booting to force moboot to display the Menu.
-To fix this problem use a Rooted File explorer, like X-plore, to delete the moboot.next file located @ Root/Boot/
-This problem is often caused by using the CyBoot app in WebOS.
6)f the WiFi turns off in Sleep/suspend mode then uncheck wifi optimization.
Note:Turning off "WiFi optimization" might help to improve WiFi functionality.
-Settings/WiFi/3 Dots/Advanced/WiFi optimization (uncheck)
-In Shumash's Schizoid build you can find it @ RomControl/General
7)You can enable additional reboot options like recovery by enabling Developer options.
-Go to Settings/About Tablet/ Tap on "Build number" 7 times.
-A new menu will appear in the Settings/About Tablet/Developer options/ tab on the left.
-Check "Advanced reboot" to get the Recovery/Boot loader options.
8)If Moboot is displaying multiple Rom or recovery names that you are not currently using, then do the following.
-With a rooted File explorer go to root/boot/ and delete the unwanted uImage.( X) file to remove the entry from Moboot.
-Here you can also change the default boot option by editing the moboot.default as text.
-Also you can change the default recovery option by editing android.default.recovery
9)If you installed Android and are unable to find the Play Store, you get keyboard errors or Android system errors , then you will need to reflash your gapps package. Click Here for the how to video! Note: If problems still persist then reflash the Rom and gapps to fix them.
Bricking, Boot Loops, Help & Fixes(Important):
If your HP TouchPad is stuck in a boot loop or not responding Don't Panic! Try the following:
-Hold down the Power and Home buttons together for 30sec to force the TouchPad to Reboot.
-Hold down the Power button and click the Home key 14 times.
-If you're stuck in a boot loop restore a back or do a fresh install, Click here for a how to Video:
-Dirty flashing older builds (CM9/CM10) over newer builds (CM10.1/CM10.2) will result in Boot loops.
-If this happens use your backup or do a fresh install, Click here for a how to Video:
-Doing an install with ACMEInstaller can sometimes result in a boot loop. Use a backup or flash the Rom and Gapps package through CWM or TWRP.
If your TouchPad seems bricked and won't turn on:
-If your battery has been fully drained, then you may need to leave it charging for a full day.
-When the battery is fully drained it can take the TouchPad a longtime to reach even the lowest battery level.
-The USB cable does not transfer enough power to effectively charge the tablet. You must use the wall plug when charging the HP TouchPad.
-After charging the HP TouchPad for a full day try holding down, home + power + volume down for 30+ seconds.
-If the tablet does not turn on after the previous steps it may be bricked and you will need to run the TPDebrick procedure found in the thread below:
Developer Jcsullins has posted a thread "TPDebrick v0.4" dedicated to helping people with bricked HP TouchPads(Important):
Note* All debricking questions should be posted here!
Download tpdebrick v005
TPdebrick instructional video by Joshsnice here
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap) thread.
Have a rom that's crashing or rebooting?
-Give the developer a dmesg file to help fix the problem with this easy to use appSysLog
How and when to Use the WebOS Doctor(Important):
Q: What’s the WebOS Doctor and when should I use it?
The WebOS Doctor is a program that has two main functions for HP TouchPad users. It can either update your version of WebOS or fix problems with a damaged WebOS by completely reinstalling it. If WebOS no longer boots or apps and preware have stopped working correctly, then you will need to resinstall WebOS with the Doctor. A failed or interrupted attempt at changing the partition sizes with WebOS preware app Tailor may cause these problems. To check what version of WebOS is currently installed go to Launcher(Up Arrow)/Settings/Device Info/ Version.
Note: If run the WebOS doctor after March, 15 ,2015. then you will need to bypass the WebOS activation with the instructions here
-If you previously removed WebOS but want to add it back use Jcsullins instructions click here:
Timeline
· 10/15/14 Announcement to users and developers COMPLETE
· 11/1/14 New app purchases end COMPLETE
· 11/10/14 App update submissions end
· 3/15/15 Public shutdown of services
Full WebOS shut down Email:
How to Use the WebOS Doctor on the HP TouchPad (Video)
https://www.youtube.com/watch?v=wFAIJiS8g4o
The WebOS Doctor is a program that has two main functions for HP TouchPad users. It can either update your version of WebOS or fix problems with a damaged WebOS by completely reinstalling it. If WebOS no longer boots or apps and preware have stopped working correctly, then you will need to resinstall WebOS with the Doctor. A failed or interrupted attempt at changing the partition sizes with WebOS preware app Tailor may cause these problems. To check what version of WebOS is currently installed go to Launcher(Up Arrow)/Settings/Device Info/ Version
Note(Important): You MUST uninstall Android before running the WebOS doctor. Failing to remove Android before running the Doctor can result in the process becoming stuck at 8-12% and potentially bricking the device. If you are currently stuck visit the thread below for information about fixing the problem. If you’re unable to use the tablet at all follow the instructions in Jcsullins TPDebrick thread.
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(Rootzwiki)
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(CM)
TPDebrick v004 - Jcsullins dedicated thread for fixing Bricked TouchPads:
Note(Click here): Running the Doctor will completely wipe all personal information, applications and preware from the TouchPad. Media like music and movies will not be affected. However I would recommend backing your important files to PC, before running the Doctor.
Note(Important): In order to install apps from the WebOS store you will need to get the Root Certificate fix for WebOS cloud services.
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
How to run the WebOS Doctor:
1) Install Java
-Java must be installed in order for the TouchPad to communicate with your PC.
2) You MUST completely uninstall Android from the HP TouchPad before running the WebOS doctor. Remove Android by running the ACMEUinstaller2. Watch the following video for full uninstall instructions.
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
3) Download the latest 3.0.5 WebOS doctor application to your PC. If upgrading you can check your current version from WebOS by going to Launcher(Up Arrow)/Settings/Device Info/ Version.
WebOS Doctor 3.0.5 Link
4) Put the tablet into WebOS recovery mode by doing the following:
-In WebOS Reboot the device by going to Launcher(Up Arrow)/Settings/Device Info/ select “Reset options” choose restart.
-As soon as the screen goes dark hold down the volume up button until you enter WebOS Recovery 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. Once in WebOS recovery mode connect your USB cable to the PC.
5) Now you’re ready to run the WebOS Doctor app by clicking on the .jar file you downloaded in the previous step. Be sure that your tablet is fully charged and connected with the USB cable before starting this process. Running out of power or interrupting this process in anyway could brick your HP TouchPad. Please be careful and fully read the instructions before beginning.
-Double click the webosdoctor.jar file to launch the app
-Select your language then click next
-Accept the licence agreement, read the warning message then select next to begin the install.
-Be patient the process can take anywhere from 15min to 1hour to complete.
HP TouchPad Root Certificate fix for WebOS cloud services(Important)
HP TouchPad Root Certificate fix for WebOS cloud services
https://www.youtube.com/watch?v=L63RiBXhQCY
The Problem:
A vital "root certificate" on webOS devices is due to expire on July 23, 2013. This certificate gives Touchpad users access to HPs cloud services for the App catalogue and Backing up the device. When the "root certificate" expires users will no longer have access to the App catalogue and backed up data. Furthermore HPs online WebOS support is expected to disappear altogether by the end of the year. So it’s recommended to backup your personal data and essential Touchpad software to your PC now.
Read the full WebOS Survival Kit Guide Here:
The solution:
Getting a free App catalog update will fix the "root certificate" problem as long as you downloaded it before July,23,2013. If you are hearing about this after July,23,2013, then you will need to first set the date to June,23,2013. To do this boot into WebOS and go to settings/Date & Time, toggle off the "Network Time". Now adjust the date accordingly and download the Update, once complete comeback and Toggle on the "Network Time" button back to on.
To get the update in WebOS go to Downloads/HP App Catalog. Open the app Catalog and select the categories tab at the bottom. Next click on the “new” tab at the top and Scroll down the page till you see “App Catalog Update”. Now install the update and your Touchpad support will continue to work in a post WebOS world.
Note: You may get a message saying the installed failed but this is incorrect. You just need to reboot the tablet into WebOS and the patch will be installed.
Note:This update requires webOS 2.1+ to be installed. Devices with older versions will need to run the WebOS Doctor first, the latest version is 3.0.5.
Additional threads and info:
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
HP to issue root certificate fix, ensure continued access to webOS cloud services
The webOS Survival Kit: everything you need to know should webOS doomsday come
Read the full WebOS Survival Kit Guide Here:
Recommended downloads:
webOS Quick Installer
WebOS doctor
Additional WebOS Performance Tweaks:
I would highly recommend doing the following tweaks. Read the full instructional guide in the link below:
HP TouchPad Setup Guide Part 1: Speed Up Your Tablet With Preware, Homebrew & Patches [WebOS]
Download and install the following packages from Preware:
You should see a noticeable speed improvement while using WebOS. Also a few apps to improve functionality.
Note* You will need to reboot the device after installing most of these packages:
-EOM Overlord Monitoring
-Muffle System Logging
-Remove Dropped Packet Logging
-Unset CFQ IQ Scheduler
-Unthrottle Download Manager
-Increase Touch Sensitivity and Smoothness 10
-Quiet Powerd Messages (sic)
-Faster Card Animations HYPER Version
-Advanced Rest Options
-Disk Cache Mod
-Unhide Developer Mode Icon
-Reduce Minimum Brightness
-CyBoot
-Ad Blocker OR Max Block – Do not install both.
-Private Browsing (adds an option to your browser)
Reduce Logging & Patch ‘em Up:
This patch require you to log into Skype with the "Phone and Video Calls" app.
Once there place a call to this number using the dialer type: "##5647#"
A logging window will launch, choose to "Clear Logs" first then "Change Logging Levels" and setting logging to "minimal".
Once done, exit the app – your logging levels are now changed.
If you have never used Preware you can watch the 2nd video about Flashing the HP Touchpads A6 Firmware to get it installed.
You will also learn how to use the WebOSQuickInstall-4.5.0 software to install Preware.
Both of these procedures are highly recommended and can be done as part of your post-apocalyptic WebOS Survival.
Donate to the Developers:
Donate to show your appreciation to our hard working developers:
Donate to Jcsullins:
Donate to Dorregaray:
Donate to Evervolv Team (Flintman):
Donate to Milaq:
Donate to Invisiblek:
Donate to Shumash:
reserved
reserved
Battery Brick / Discharge Prevention
Is it still recommanded / necessary to use an automated shutdown app, like automateit, to prevent the battery from total discharge with the new 4.4.4 ROMS? Is there still any risk of a battery brick, like it was reported a lot of times in the past?
nikogh said:
Is it still recommanded / necessary to use an automated shutdown app, like automateit, to prevent the battery from total discharge with the new 4.4.4 ROMS? Is there still any risk of a battery brick, like it was reported a lot of times in the past?
Click to expand...
Click to collapse
I am running it for half a year now without any battery problem.
Reflashing the A6 every once in a while though.
Thank You for the reply!
Updates
Itshuta said:
I am running it for half a year now without any battery problem.
Reflashing the A6 every once in a while though.
Click to expand...
Click to collapse
nikogh said:
Is it still recommanded / necessary to use an automated shutdown app, like automateit, to prevent the battery from total discharge with the new 4.4.4 ROMS? Is there still any risk of a battery brick, like it was reported a lot of times in the past?
Click to expand...
Click to collapse
I've seen a few people ask this on YouTube but no its not a problem anymore and the tablet won't become bricked if it runs out of batteries. Follow Itshuta advice and flash the A6 every few months or so and you should have good battery life and longevity :highfive:
The thread has now been updated to inculde android 5.0 Roms and Jcsullins TPtoolbox v42
Thank you Roland for the update.
As my tablet is running smoothly for the moment, do you think the upgrade worth it ?
Itshuta said:
Thank you Roland for the update.
As my tablet is running smoothly for the moment, do you think the upgrade worth it ?
Click to expand...
Click to collapse
There's no really hurry to upgrade, the Kitkat roms are nice and mature now. I like to try out the new interface and features, however I'd stick to Android 4.4.4 roms for a few months till Lollipop gets more mature. I'll be posting updates about the roms as I get them tested
I'd recommend trying the Pac Rom below.
[ROM][OFFICIAL][KitKat 4.4.4][TENDERLOIN] PAC-man KK RELEASE [DEV] By Shumash
Note: Kernel 3.0 and 3.4 builds are available
Kernel 3.0: Low to medium battery drain(-5mA to -20mA), Antutu Score=12000+
Kernel 3.4: Medium battery drain (-30mA to -60mA), Antutu Score=13000+
Rom Details: h/w video, Audio, Camera, Bluetooth, Inverted volume controls, PAC Console (OTA updates), PAC Performance settings (overclocking, custom governors and schedulers), Increased 2D & 3D GPU clocks up to 320Mhz, Increased default CPU clock from 1188Mhz-1512Mhz, overclocks up to 1782Mhz, Great for Gamers.
Note:Using the lock screen may cause SOD(sleep-of-death), disable it by going to Settings->Security->Screen Security->screen lock=none.
Note:Hold down power and home together if the screen is black(SOD) and you need to reboot.
Note:This Rom can see both SDcards
Can't install drivers for HP touchpad on computer
Hi guys,
I recently flashed to this rom using the TPtoolbox.
Everything works fine except that when I connect it to my computer it can't install the drivers.
I'm running WIndows 7 Ultimate 64 bit.
I really want to add movies on to my Touchpad..
Any ideas??
Try another cable
wyu24 said:
Hi guys,
I recently flashed to this rom using the TPtoolbox.
Everything works fine except that when I connect it to my computer it can't install the drivers.
I'm running WIndows 7 Ultimate 64 bit.
I really want to add movies on to my Touchpad..
Any ideas??
Click to expand...
Click to collapse
Please specify which rom you're using. Try using a different USB cable, the one that comes with the tablet often stops working. You can go to the win7 device manager and see if the HP TP is detected. Failing that there are several apps you can use to transfer files over the WiFi.
WiFi Apps from the play store:
https://play.google.com/store/apps/details?id=com.file.transfer
https://play.google.com/store/apps/details?id=com.smarterdroid.wififiletransfer
https://play.google.com/store/apps/details?id=com.majedev.superbeam
Recovery zip unrecognized / unsupported
Hi all, Im using Toolbox 42. After successful "Complete Data Reset", when in "Install Android" I run into the following error:
- "unrecognized / unsupportd zip update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip"
The following files I copied successfully to "ttinstall"
- cm-11-20150113-SNAPSHOT-jcsullins-tenderloin.zip
- gapps-kk-20140105-signed.zip
- update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip
The drive was successfully ejeted before continuing.
Thanks for support
M.
Use a supported DM reocvery file
mullern said:
Hi all, Im using Toolbox 42. After successful "Complete Data Reset", when in "Install Android" I run into the following error:
- "unrecognized / unsupportd zip update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip"
The following files I copied successfully to "ttinstall"
- cm-11-20150113-SNAPSHOT-jcsullins-tenderloin.zip
- gapps-kk-20140105-signed.zip
- update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip
The drive was successfully ejeted before continuing.
Thanks for support
M.
Click to expand...
Click to collapse
You're not using a supported DM recovery (update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip). Use one of the correct files found in this guide for use with TPtoolbox v42 and v41x.
Supported Data Media Recoveries (TPtoolbox v42-v41x) Download:
Note: These recoveries are meant to be used with TPtoolbox v42 and v41x
View attachment 3128785
Download Philz Touch CWM Recovery:
Philz-CWM-jcs-dm-tenderloin-20140612 via mediafire:
Philz-CWM-jcs-dm-tenderloin-20140612 via androidfilehost:
Download TWRP Touch Recovery:
TWRP-jcs-dm-tenderloin-20140612 via mediafire:
TWRP-jcs-dm-tenderloin-20140612 via androidfilehost:
Download Standard Non-Touch CWM Recovery:
CWM-jcs-dm-tenderloin-20140612. via mediafire:
CWM-jcs-dm-tenderloin-20140612. via androidfilehost:
RolandDeschain79 said:
You're not using a supported DM recovery (update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip). Use one of the correct files found in this guide for use with TPtoolbox v42 and v41x.
Thanks a lot, Roland, got that and worked like a charm. I could successfully install on a TP WIFI and on a TP 4G, very pleased with both so far. Only little issues with a Logitech Bluetooth headset not working well with Skype. Works perfect with Music / Internet radio. Searching on for that
Do you have any information for/experience with a TP Go installation? Does Toolbox work? Does 4G Tenderloin work?
Regards M.
Click to expand...
Click to collapse
mullern said:
RolandDeschain79 said:
You're not using a supported DM recovery (update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip). Use one of the correct files found in this guide for use with TPtoolbox v42 and v41x.
Thanks a lot, Roland, got that and worked like a charm. I could successfully install on a TP WIFI and on a TP 4G, very pleased with both so far. Only little issues with a Logitech Bluetooth headset not working well with Skype. Works perfect with Music / Internet radio. Searching on for that
Do you have any information for/experience with a TP Go installation? Does Toolbox work? Does 4G Tenderloin work?
Regards M.
Click to expand...
Click to collapse
TP Go is an unsupported device. Nothing here works on it.
Click to expand...
Click to collapse
RolandDeschain79 said:
Legacy Non-Data Media Roms, Gapps and Recovery below: Warning do not mix Non-data media and data media files when using the TPToolbox.
Note: If you accidentally mix the two file types you may need to run the "Complete data rest" or the "Erase USB drive" procedure again before you can install android.
Android 4.2.x Non Data Media Rom Guide and Links:
[ROM][4.2.2 CM10.1] [3.0 Kernel] Bluetooth Test builds By Jcsullins
Rom Details: Low battery drain (-5mA to -10mA), h/w video, Audio, Inverted volume controls, Bluetooth, No Camera.
Click Here to watch the Jcsullins Kernel 3.0, CM10.1 Build video:
[ROM][4.2.2 CM10.1]-SNAPSHOT-Jcsullins-VPN-tenderloin-20131210 By Jcsullins
Rom Details: Low battery drain(-4mA to -10mA), h/w video, Audio, Inverted volume controls, Pie Controls, Camera, Bluetooth.
Click Here to watch the HP TP News: Jcsullins Fixes Bluetooth Support video
[/URL]
[ROM] [4.2.2 CM10.1] <KANG>SCHIZOID 2.11 All-in-One [12DEC2013] By Shumash (Roland's Favorite for Gaming)
Rom Details: Low battery drain(-4mA to -10mA) h/w video, Audio, Camera, Bluetooth, Pie Controls, AOKP Rom Control, Hybrid Properties, Performance settings(OC), Custom Kernel Overclockable to 2157MHz, Increased 2D & 3D GPU clocks up to 320Mhz, Great for Gamers.
Click Here to Watch the Schizoid 2.11 All-in-one video:
4.2.x Gapps Download:
Android 4.2 20130812 CM10.1 Gapps:
Supported Non-Data Media Recoveries Downloads:
Note: These recoveries are meant to be used with TPtoolbox v42 and 41x
View attachment 3128786
Download Philz Touch CWM Recovery:
Philz-CWM (NODM 2014-06-14) via mediafire:
Philz-CWM (NODM 2014-06-14) via androidfilehost:
Download TWRP Touch Recovery:
TWRP (NODM 2014-06-14) via mediafire:
TWRP (NODM 2014-06-14) via androidfilehost:
Download Standard Non-Touch CWM Recovery:
CWM (NODM 2014-06-14) via mediafire:
CWM (NODM 2014-06-14) via androidfilehost:
Extra uses for the Touchpad Toolbox:
Reflash A6 Firmware:
The Problem:
HP Touchpad developer Jcsullins, has informed HP TouchPads users that there's a problem with our HP Touchpas A6 Firmware. This issue can cause an usually high battery drain during sleep. This problem occurs overtime while running both Android and WebOS. As a result the Touchpads battery drains more quickly with daily use and the overall life span is reduced. If your battery drain seems to be much higher on average, then flash the A6 Firmware to bring it back down. Users experiencing sudden drops in battery life should run this as well.
The Solution:
Reflashing the A6 Firmware effectively fixes the problem but may need to be repeated as a part of regular HP TouchPad maintenance. I would recommend reflashing it ever few months to maintain good battery health. Watch this video and follow the step by step instructions to reflash your own Touchpads A6 Firmware.
How to test:
-To monitor your battery drain history during sleep install the free app Battery Monitor Widget:
-Once installed open the app and go to history, click the heading at the top "%/h" to change it to "mA".
-You can now monitor the history and compare it to the information in my rom guide.
Mount Media Volume:
Allows you to access the 'media' volume from your PC
Resize Android Volumes:
This allows you to interactively resize the Android (and media) volumes.
This is not needed to "Install Android", but can be used at other times to 'tweak' the volume sizes as needed.
Repair Android Volumes:
If a fsck (file system check) determines that there are non-trivial errors on a filesystem, then this can be used to attempt to fix those errors.
Create webOS Volumes:
If you want to re-install webOS following a "Full Data Reset," you will need to run this prior to running webOS doctor.
At this time, re-installing webOS should only be done prior to installing Android. Tools to assist re-installing webOS after
Android has been installed (without detriment to the Android install) may be provided in the future. Full instructions for reinstalling WebOS here.
Future development and limitations:
Only Touchpad Wifi supported (not 4G) at this time, use the instructions here to install the Evervolv 4G data media build.
Support for non-KitKat/DataMedia installs very limited for now.
Re-install of webOS after Android installed is not supported yet.
Method for permanently installing TPToolbox (always available via moboot) not available yet.
The main focus at this time is providing a reliable method to install KitKat/DataMedia ROMs.
Additional/expanded legacy and/or other install types will be implemented after demand for such is determined.
News and Updates:
Hello Android users great news! Android 5.0 Lollipop builds have arrived for the HP Touchpad. Today I will show you how to install the latest Evervolv 5.0 Preview builds onto your HP Touchpad and take you on a tour of the new UI.
Timecode:
How to install Evervolv 5.0 Builds on the HP Touchpad @3:49
How to flash the Rom and Gapps with Philz CWM @6:20
Android 5.0 Tablet Tour @8:40
Android 5.0 Lollipop Easter Egg @9:10
How to fix YouTube videos @10:32
[ROM] Evervolv | 5.0.0p1 [AOSP 5.0] [3.4 kernel] [PREVIEW] With /data/media:
Download Android 5.0 CM12 Gapps:
Click to expand...
Click to collapse
I have WebOS in one partition and Android 4.0.2 in another. I only want to upgrade the Android version and leave WebOS intact. I tried the CWM method but that failed. Which option do you recommend for ToolBox for my situation? If I choose "Install Android", will it only touch the Android partition only or will it also wipe the WebOS parition? Thanks.
Can I use JCsullins snapshot 4.4.4 Android for this install?
I am using ACMEUninstaller2 but novacom can't find my device. I checked the services and it is running.
iknight8 said:
I have WebOS in one partition and Android 4.0.2 in another. I only want to upgrade the Android version and leave WebOS intact. I tried the CWM method but that failed. Which option do you recommend for ToolBox for my situation? If I choose "Install Android", will it only touch the Android partition only or will it also wipe the WebOS parition? Thanks.
Can I use JCsullins snapshot 4.4.4 Android for this install?
Click to expand...
Click to collapse
iknight8 said:
I am using ACMEUninstaller2 but novacom can't find my device. I checked the services and it is running.
Click to expand...
Click to collapse
Did you install the novacom software in the OP? Are you in WebOS recovery mode? Have you tried a 2nd USB cable I see you posting over in the TPtoolbox thread so I assume you've taken the time to actually read the OP and have figured it out by now. Make sure your using compatible recovery files with TPtoolbox v42, everything you need is linked in this thread. Happy flashing
Supported Data Media Recoveries (TPtoolbox v42-v41x) Download:
Note: These recoveries are meant to be used with TPtoolbox v42 and v41x
View attachment 3128785
Download Philz Touch CWM Recovery:
Philz-CWM-jcs-dm-tenderloin-20140612 via mediafire:
Philz-CWM-jcs-dm-tenderloin-20140612 via androidfilehost:
Download TWRP Touch Recovery:
TWRP-jcs-dm-tenderloin-20140612 via mediafire:
TWRP-jcs-dm-tenderloin-20140612 via androidfilehost:
Download Standard Non-Touch CWM Recovery:
CWM-jcs-dm-tenderloin-20140612. via mediafire:
CWM-jcs-dm-tenderloin-20140612. via androidfilehost:
Hi
Thanks for this tutorial and combo helps. It was a bit convoluted but got it done. it can help to have a very mini review at the top of the initial posts which explains the basic purposes of the steps. There is just too much informations which is great.
So I have pacman rom running. Now how do I go ahead if I have to update the roms regularly? Do I need the Hp Tool box again> Or I have to drop to recovery like it is done in other roms?
Btw on Linux the novacom is installed under /opt/Palm and that is where the user has to run it from
thanks

Postmarketos for Amazon Fire 7 HD (2017) (Austin)

Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin
Amazon Fire 7 (2017) postmarketOS Armv7l Mediatek MT8127 Mali-450MP4 600x1024 display 1GB RAM Linux 3.10.54
What seems to work:
Boot Touch screen Battery percentage Usb internet OTG usb Wayland, Mate, Xfce4, Lxde, Sxmo, i3wm
Does NOT work:
Wifi & Bluetooth (no drivers) GPU acceleration (drivers do not work) Audio Sleep and fully turning off the display Screen rotation Wifi adapter does not work even with drivers and kernel support, mobo support issue(?) FDE Cameras You tell me
Special options: *Must be flashed to USERDATA partition as system partition is too small
msm-fb-refresher packaged is added to the depends to make the screen refresh. After flashing the device must be booted into recovery once. From the recovery it is to be powered off and booted and then as normal. This is because the device depends on the AMONET exploit which is applied by twrp after every flash.
Flashing Instructions
This assumes that you already have linux installed and the bootloader on the tablet is unlocked. Don't worry if it looks complicated. If you are unsure of something ask on the postmarketos matrix or leave a comment for help.
Install pmbootstrap as stated in the postmarketos wiki, does not matter which options or device you pick.
Once that is done download and drag the two folders in the git repo into "/home/YOURUSER/.local/var/pmbootstrap/cache_git/pmaports/device/testing/" also displayed as "~/.local/var/pmbootstrap/cache_git/pmaports/device/testing".
Run pmbootstrap init and select amazon as manufacture and austin as the device, mate, lxde, xfde, are confirmed working.
Run pmbootstrap install
Boot into twrp and wipe all partitions including data
Boot into the hacked bootloader from the twrp options
Run pmbootstrap pmbootstrap flasher flash_rootfs --partition userdata (system partion is too small to flash!) and once it is done flashing run pmbootstrap flasher flash_kernel
Unplug the device, wait 10 seconds and then hold the power button. Once it is powered on YOU MUST boot it into twrp at least once as it needs to restore the AMONET exploit, until you do that the device will not boot.
Issues
If something does not work such as the display rotated wrong or device not booting just comment or open an issue, I changed the rotation of the display in the kernel options to horizontal but i did not test the effects as I already have android with books on it.
Reinstall android/lineage
Simple as cake, just boot into twrp wipe all partions(some will fail), you may need to resize and fix until it starts working. You just need the system and data partitions to be reformated to ext4 even if they already are. Then just flash the lineageos zip file and reboot the device normally(amonet is fine)
GitHub - GjergjiFloychi/amazon-austin-pmaports: Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin
Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin - GitHub - GjergjiFloychi/amazon-austin-pmaports: Working ebuild for installing postmarketos on the Amazon ...
github.com
This looks promising, nice job. I will try installing it on my Austin during the next days.
Rortiz2 said:
This looks promising, nice job. I will try installing it on my Austin during the next days.
Click to expand...
Click to collapse
Good luck. Tell me if the display works if you do install it. Thanks
hexdump0815 cleaned up the config file, use his fork if you are going to install.​
Is it wifi working? It'll awesome
Baonks81 said:
Is it wifi working? It'll awesome
Click to expand...
Click to collapse
Unfortunately the drivers for this SOC are nonexistent so nothing works. WIfi and hdmi adapters don't work, but OTG does. Hexdump made a Debian and Ubuntu image for this tablet, it is great but the tablet is mostly useless without WiFi and GPU support. You can also flash the main image to the userdata partition instead of using an SD Card, but if I remember correctly the rootfs won't auto extend. It would have been great to use this as a linux tablet, however this SOC is uncommon and is not supported by any Linux maintainer. https://github.com/hexdump0815/imagebuilder/releases/tag/211101-02
Fandroid Tech said:
Unfortunately the drivers for this SOC are nonexistent so nothing works. WIfi and hdmi adapters don't work, but OTG does. Hexdump made a Debian and Ubuntu image for this tablet, it is great but the tablet is mostly useless without WiFi and GPU support. You can also flash the main image to the userdata partition instead of using an SD Card, but if I remember correctly the rootfs won't auto extend. It would have been great to use this as a linux tablet, however this SOC is uncommon and is not supported by any Linux maintainer. https://github.com/hexdump0815/imagebuilder/releases/tag/211101-02
Click to expand...
Click to collapse
Thanks for new information. I'll searching around
I think we can find firmware it out on /dev/mmcblk---
Baonks81 said:
Thanks for new information. I'll searching around
I think we can find firmware it out on /dev/mmcblk---
Click to expand...
Click to collapse
I looked at the firmware dump on github, it is all proprietary and seems to be compatible only on android. The closest I got to getting working wifi was moving the original libs and networkmanager bin to linux however it only showed wifi working for a few seconds without detecting anything.
I'm working on this device right now. I just downloaded the repository below, and I will make a pull/merge request upstream soon.
Fandroid Tech said:
GitHub - GjergjiFloychi/amazon-austin-pmaports: Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin
Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin - GitHub - GjergjiFloychi/amazon-austin-pmaports: Working ebuild for installing postmarketos on the Amazon ...
github.com
Click to expand...
Click to collapse
I have my own fork of the pmaports repository at https://gitlab.com/Worldblender/pmaports, where I will push your files (eventually with my changes) to. Maybe we can work together on getting this tablet supported upstream, if you still want to (anything else that isn't working, like the Wi-Fi/Bluetooth, will have to come later).
UPDATE: Well, I'm going to use https://github.com/hexdump0815/pmaports-amazon for the config now, didn't notice it the first time around. I also noticethat it's possible to get Wi-Fi working with https://github.com/hexdump0815/imagebuilder-firmware/blob/main/tablet_amazon_austin-firmware.tar.gz, that I will try out with my builds soon.
From https://github.com/hexdump0815/imagebuilder/tree/main/systems/tablet_amazon_austin:
wifi seems to work by using the android firmware and tools in a minimal android bionic chroot env
wifi can be stated via /scripts/start-wifi.sh
uncomment the start of this script in /etc/rc.local in case wifi should be enabled by default
wifi support was added in february 2022, so all images from before do not have it yet but it can be added easily afterwards
Click to expand...
Click to collapse
Worldblender said:
I'm working on this device right now. I just downloaded the repository below, and I will make a pull/merge request upstream soon.
I have my own fork of the pmaports repository at https://gitlab.com/Worldblender/pmaports, where I will push your files (eventually with my changes) to. Maybe we can work together on getting this tablet supported upstream, if you still want to (anything else that isn't working, like the Wi-Fi/Bluetooth, will have to come later).
UPDATE: Well, I'm going to use https://github.com/hexdump0815/pmaports-amazon for the config now, didn't notice it the first time around. I also noticethat it's possible to get Wi-Fi working with https://github.com/hexdump0815/imagebuilder-firmware/blob/main/tablet_amazon_austin-firmware.tar.gz, that I will try out with my builds soon.
From https://github.com/hexdump0815/imagebuilder/tree/main/systems/tablet_amazon_austin:
Click to expand...
Click to collapse
You could package the wifi hack into an Alpine Linux for firmware package if you want. Debian 11 runs really well, to bad we can't get everything working.
Fandroid Tech said:
You could package the wifi hack into an Alpine Linux for firmware package if you want. Debian 11 runs really well, to bad we can't get everything working.
Click to expand...
Click to collapse
Will work on that soon. I just got a build to boot today, and basic functionality seems to be working. I'm going to try a different distro for accessing more functionality (likely Ubuntu 20.04 or 22.04) I just opened up a merge request at https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3251 for the progress on upstreaming.
I'm thinking about using the exact same kernel that the LineageOS image uses:
https://github.com/cm14-mt8127/device_amazon_mt8127-common
https://github.com/cm14-mt8127/kernel_amazon_mt8127-common
This kernel has been updated to 3.10.108, and it's the last one for the 3.10 branch. I'm going to try creating a new build using this kernel, and see how it goes.
Worldblender said:
I'm thinking about using the exact same kernel that the LineageOS image uses:
https://github.com/cm14-mt8127/device_amazon_mt8127-common
https://github.com/cm14-mt8127/kernel_amazon_mt8127-common
This kernel has been updated to 3.10.108, and it's the last one for the 3.10 branch. I'm going to try creating a new build using this kernel, and see how it goes.
UPDATE: Three patches would not apply successfully for this kernel:
fix-host-card-inserted.patch
silence-power-logspam.patch
silence-thermal-logspam.patch
After building without these patches, the kernel boots, but it stays stuck without being able to process further, with some kernel messages displayed. I wonder what I should do to get this kernel working, or if this one shouldn't be used.
Click to expand...
Click to collapse
Use any kernel you want. It literally does not matter as it cannot be mainliner in the future anyways. It makes no difference what you use.
Fandroid Tech said:
Use any kernel you want. It literally does not matter as it cannot be mainliner in the future anyways. It makes no difference what you use.
Click to expand...
Click to collapse
Here's my results after building and boot it:
There are some kernel messages that pop up, and the splash screen never appears. It doesn't matter whether there is a microSD card inserted or not; there seems to be too many changes made to it from 3.10.54 to 3.10.108, along with additional changes that are designed more for Android/LineageOS usage. Finding every one of them is too much work for me.
Three patches would not apply successfully for this kernel:
fix-host-card-inserted.patch (will apply successfully once the entry for line 271 is removed)
silence-power-logspam.patch
silence-thermal-logspam.patch
Again, after building without these patches, the kernel boots, but it stays stuck without being able to proceed further, with some kernel messages displayed. I tried building without any of the patches shipped, but the end result is still the same. I need some help as to what what I should do to get this kernel working, or else I will go back to the 3.10.54 kernel that I know is actually booting to the splash screen. Here, I don't care whether I use a mainline kernel here, since I know the SOC is not supported by mainline. I simply care that I can get a newer kernel version working (from 3.10.54 to 3.10.108), unless there's too many changes for me to go through.
Worldblender said:
Here's my results after building and boot it:
There are some kernel messages that pop up, and the splash screen never appears. It doesn't matter whether there is a microSD card inserted or not; there seems to be too many changes made to it from 3.10.54 to 3.10.108, along with additional changes that are designed more for Android/LineageOS usage. Finding every one of them is too much work for me.
Three patches would not apply successfully for this kernel:
fix-host-card-inserted.patch (will apply successfully once the entry for line 271 is removed)
silence-power-logspam.patch
silence-thermal-logspam.patch
Again, after building without these patches, the kernel boots, but it stays stuck without being able to proceed further, with some kernel messages displayed. I tried building without any of the patches shipped, but the end result is still the same. I need some help as to what what I should do to get this kernel working, or else I will go back to the 3.10.54 kernel that I know is actually booting to the splash screen. Here, I don't care whether I use a mainline kernel here, since I know the SOC is not supported by mainline. I simply care that I can get a newer kernel version working (from 3.10.54 to 3.10.108), unless there's too many changes for me to go through.
Click to expand...
Click to collapse
Just use the stock 3.10.54 kernel. Both versions have long since been EOL. It does not matter what is used as functionality will still the same, both now and any future development. I would not bother upgrading the kernel to 3.10.108. Hexdump told me a while back that somebody else maintaining a similar soc on the mainline branch told him that mainlining the device is almost impossible due to some proprietary components by Amazon. I am not entirely sure as to the validity of this claim but I think that it is not worth the effort of upgrading the kernel of this device. Check this page for more info, I found it to be very helpful to my port. https://wiki.postmarketos.org/wiki/Amazon_Fire_7_2015_(amazon-ford)
[waits eagerly nonetheless]
This is a solid old device in a lot of ways. I'd love to see it supported by PMOS.

Categories

Resources