[Q] Switching the default moboot option to AOKP - TouchPad Q&A, Help & Troubleshooting

Hello everyone, recently i switched my Main Android to AOKP from the build at RootzWiki for Kitkat and choose to remove WebOS. At the first flash i tried Pacman rom but the sound problem was the main reason i tried AOKP. When i flashed pacman, i was using the Touchpad Toolbox and removed the WebOS stuff tried the roms for some stuff and decide to revert to a stable Kitkat one.
So my main problem was the default boot option was Cyanogenmod, as i know, i just need to go to the boot menu and erase the two file for cm based build. After rebooting, the main option was the recovery... I tried to switch recovery and between the 3 recommended in TP Toolbox OP and always the same result, recovery by default... Is there any tool in Android for doing this ? I know there is one in WebOS and if i wanted to keep it i could have used it.
Also, is there any utility to the media partition used for sharing between WebOS and Android in non data/media build ? It is a good 800mb partition wasted in my mind, idk if this was used for the boot menu or anything for recovery. If in result i need to use the toolbox again for reflashing the AOKP build, will it erase my personal data ? I don't mind for doing a partial data erasing (android app) or doing a dirty flash but i just don't want to transfert all my data back from my computer.
Thank for your answer guys.

Atari-San said:
Hello everyone, recently i switched my Main Android to AOKP from the build at RootzWiki for Kitkat and choose to remove WebOS. At the first flash i tried Pacman rom but the sound problem was the main reason i tried AOKP. When i flashed pacman, i was using the Touchpad Toolbox and removed the WebOS stuff tried the roms for some stuff and decide to revert to a stable Kitkat one.
So my main problem was the default boot option was Cyanogenmod, as i know, i just need to go to the boot menu and erase the two file for cm based build. After rebooting, the main option was the recovery... I tried to switch recovery and between the 3 recommended in TP Toolbox OP and always the same result, recovery by default... Is there any tool in Android for doing this ? I know there is one in WebOS and if i wanted to keep it i could have used it.
Also, is there any utility to the media partition used for sharing between WebOS and Android in non data/media build ? It is a good 800mb partition wasted in my mind, idk if this was used for the boot menu or anything for recovery. If in result i need to use the toolbox again for reflashing the AOKP build, will it erase my personal data ? I don't mind for doing a partial data erasing (android app) or doing a dirty flash but i just don't want to transfert all my data back from my computer.
Thank for your answer guys.
Click to expand...
Click to collapse
1)Go back to the boot folder open moboot.default and change CM to AOKP.
2)Jcsullins TPToolbox can see the media partition and access it, so can his CM11 rom or the Evervolv rom. Take a look at this video and thread, it should clear up most of the info for you.
New Super Easy Way Guide and video available
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"(DM & Non-DM)

RolandDeschain79 said:
1)Go back to the boot folder open moboot.default and change CM to AOKP.
Click to expand...
Click to collapse
Thank you, i did not know we could open this file as a plain text file. Thank you. ^_^
Gonna watch the video too. Thank. ^_^

So, after watching your video and mounting the media partition from the TP Toolbox (because my rom cannot open it), it seem there is not anything worth in this partition and it seem there is no delete option while resizing it. So i guess the old commandline recovery could help me to delete the media partition and i could use the toolbox for resizing it to the max. I still don't know if it is safe to delete but seem there's only android stuff in the partition. Thank Rolland for the info again. :highfive:

Related

[HOW TO] DUAL BOOT for P990 & SU660 on BOTH Bootloaders v5.0

Dual Boot for P990 & SU660 on Both Bootloaders
Now with more and more new ROMs being released every day and only one phone (at least for most of us) to try them all, I think this was needed.​
It is based on the method Bihariel found on a Chinese forum and his latest v2 version for the old bootloader and my previous version 3 for the new one.
It is now modified to work on both bootloaders and Partition layouts. Read change log for details.
Thanks to:
SuperSkill personally, for digging it up from the grave and giving me the vote of confidence to port dual boot into the new bootloader. He is also the 1st after me, who tested it. (thank you again my friend)
KingMGT personally, for helping me make the necessary modifications for SU660 and of course for testing it since I don’t own a SU660. (thank you again my friend)
Bihariel of course, for his great work on which I based the new version (and for copying a lot of text from his thread)
ChinaGB, the creator of the System changer app and the original idea.
What is this useful for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won/t need to wipe or backup anything.
Users: you can have a stable ROM, let’s say a stock ROM with everything working and configured and you can have a second partition to test ROMs (for example a custom stock based one or a CM10 beta) so you won't need to do backups and wipes.
How Dual Boot works?
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 1.
What ROMs can I use?
P990 Devices:
You can use theoretically, any combination of ROMs for dual booting, working on the same Bootloader of course.
SU660 Devices:
On OLD layout you can use theoretically, any combination of ROMs for dual booting, working on this Bootloader of course.
On ICS layout, due to lack of any custom ROMs for SU660, the p990 layout and bootloader is used so only custom CM, PA & MIUI ROMs are compatible, working on this Bootloader of course.
Attention !! The only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files. Of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.
Download from here the package for your device and follow the instructions in post #2.
For older versions follow the instructions included in package.
Change Log:
v5.0 Date 05 Feb 2013
DualBoot-Control.zip. All five zips used till now for enabling/maintaining Dual-Boot have been replaced by this aroma-style flash-able zip.
SU660 package now supports also the su660 ics bootloader & layout.
V4.6 Date 30 Jan 2013
512MB-512MB system partitions for both bootloaders,
Reduced data (to 2000MB) for old-bootloader (because a 2048MB one cannot be formatted on old bootloader)
Bug-fix for dual-boot remover (SystemChanger app wasn't removed).
V4.5 Date 22 Jan 2013
Now it auto enters recovery after repartitioning. No need to keep pressing Vol- & Pwr.
Linux nvflash binary added. (I had forgotten to include it in package, sorry.)
Minor changes in flash.sh (for linux).
V4 Date 20 Jan 2013
It now works on both bootloaders. During repartition with nvflash you have the option to select which one
In old bootloader the system partition is splitted in 370MB for ROM1 and 512MB for ROM2 (in case someone wants to install tonyp's & harsh's full ICS version for old bootloader).
Same simple procedure to enable and maintain dual-boot.
Common flash-able zips because they detect current bootloader and partition layout and act accordingly.
Re-compiled SystemChanger app to display more correct messages and also in which ROM you are switching to.
V3 Date 12 Jan 2013
System partition size is 512 MB for each ROM.
Data partition is still shared but with the max size of 2GB.
Included latest cwm recovery 6.0.2.5 by pengus77. It works for all available ROMs for new BL (DM X, FLEX-ICER & unofficial CM10 CM10.1 ones)
NewBL-Dual-Enabler’s scripts are modified not only for the new layout but now also check and format (if needed) the internal SD (the first time after NVFlash is always needed). It also returns to recovery automatically to let you install or restore the 1st ROM.
NewBL-Dual-ROM-1-to-XX.zip & NewBL-Dual-ROM-2-to-XX.zip no longer need to be updated with the boot images of the ROMs.
SystemChanger app’s scripts, before switching to the other ROM, check if current ROM is changed (by md5 checksum of its build.prop as before) and saves the boot.img for next switch.
noshare file, containing the data folders list, is now also saved under /data/dual-boot. This way it will be always accessible and updatable if needed, no matter which ROM is running.
Boot images and md5 checksums are also saved under /data/dual-boot.
Two more flash-able zips added:
Wipe-ROM-data.zip This will wipe the data of the current ROM. Useful for changing ROM or if required by ROM’s chef
Remove-DualBoot.zip This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts from the current ROM. Useful if you want to make a clean nandroid backup, to restore after a repartition to normal layout.
For V2 change log see bihariel's thread
Here is the guide to get Real Dual boot on both BLs.
Please read carefully because this may mess up your phone if you don't know what you are doing.
Oh!! I forgot, this phone is unbrickable, so give it a try.​
Installation Instructions
Extract the downloaded package with WinRAR or similar to any folder.
Copy ROM1, ROM2 and the DualBoot-Control.zip to external SD.
Go to the folder DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions select BootLoader and wait until NVFlash process finishes and the screen goes black.
Disconnect the USB cable, put the battery back and just power on the phone it will enter into recovery automatically. (It takes about 40 secs to enter recovery 1st time after NVFlash)
Install DualBoot-Control.zip and select Enable Dual Boot option. The phone will reboot (if supported by recovery) and enter in recovery again (if not select reboot recovery from recovery).
Make a full wipe just in case to avoid boot-loops and format /system because it may not be formatted by ROM’s updater-script (mounts and storage --> format /system)
Now flash ROM1 (or restore a nandroid backup of ROM1) and without rebooting install DualBoot-Control.zip, select ROM1 update and reboot when it finishes.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switch ROM, it will ask you for root rights, click yes, the phone will reboot quickly, press and hold Pwr button + vol down when the screen goes black to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Format /system (the 2nd system now), because it may not be formatted by ROM’s updater-script.
Now flash ROM2 and without rebooting install DualBoot-Control.zip, select ROM2 update and reboot when it finishes. (Attention: do not restore a backup of ROM2 because it will wipe data files of ROM1)
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switch ROM.
Note for those having experienced the older version 2: No need to add boot images in Dual-ROM zips any more.
How to change/update a ROM or Kernel
You have to be on the ROM you want to change/update.
Enter Recovery
If you are changing the ROM or kernel and/or a wipe is needed, install the DualBoot-Control.zip and select Wipe current ROM data.
Flash the ROM or kernel and before reboot install the DualBoot-Control.zip and select ROM1 update if you flashed ROM1 or ROM2 update if you flashed ROM2.
Info: There is also the wipe-rom-x-data.sh in /data/dual-boot/ which can be used to delete the non-running Rom’s data. You can also run this from terminal or adb shell to clean the data of the non-running Rom quickly. For example if you are on ROM1 and you want to change the ROM2 run the script, switch to ROM2 but when screen goes black press pwr & vol- to enter recovery.
How to disable Dual Boot
You have to be on the ROM you want to keep.
Enter Recovery
Install the DualBoot-Control.zip and select Remove Dual Boot. This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts. Useful if you want to make a clean nandroid backup, to restore after a repartitioning to normal layout with AIO-Toolkit.
Enjoy it !!
Wow......one thing i ws missing on NEW BL......thank you so much....now can hold onto this phone for 1more year....
This is just Aweosme <3 will give a try for sure ! LG O2X still the Crazy phone will try today eveng and comment back again ! can i try CM10.1 & V30B (Roms available) ???
Kudooos 4 ur post
This is what i need, i often flash rom 1 to another and restore my app and setting manualy... with this i would keep my daily rom and other for testing
thanks good job
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Nice ! Trying soon... :fingers-crossed:
SuperSkill said:
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Click to expand...
Click to collapse
Thank you too again.
No, don't give me another challenge now. :laugh:
I am thinking on making a v3 version for old bootloader too, or even better a v4 hybrid one for both bootloaders. So I do have work for now.
Yes I could integrate that into AIO-toolkit eventually in an "Addvanced Options" menu , but let's see how it is working, when more users will try it and "cure" any "baby sicknesses" that may come up first.
I can't thank you enough for your testing it so thoroughly.
I really appreciate it.
i don't really understand how this dual boot work
but, can i use my internal sd card for booting stock-based custom rom and using my external one for booting CM10 based rom?
what about ics and gingerbread on dual boot!?
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Nice man" I ll try it soon!
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
babi_perang said:
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Click to expand...
Click to collapse
I don't know if this will be ever possible or if it's worth trying it.
The only thing that can be done at the moment, is having one 370MB & one 512MB system partitions on the upcoming gb dual-boot version for installing the tonyp's and harsh's full ics 28g version as 2nd ROM on old bootloader.
I installed yesterday dual boot on my 2X and worked fine without any problems!
Great tool Spyrosk!!
You have done our life easier!!!
Thank you for dual boot
is indeed something very special!!!
It works beautifully for me,
the P990 is significantly upgraded:laugh:
And what about dual boot with linux?
tomsi91 said:
And what about dual boot with linux?
Click to expand...
Click to collapse
What do you mean? Read step 3 carefully.
3.Go to the folder NewBL-DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions and wait until NVFlash process finishes and the screen goes black.
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
tomsi91 said:
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
Click to expand...
Click to collapse
And iOS & Windows Mobil 8...
How about flashing the second rom that have aroma installer??

[Solved] No sdcard after flash The_apes Flashable zip in clockwork

Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Edit : on ES Explorer you have to activate root access to see /data/media/0
Bristow69 said:
Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Click to expand...
Click to collapse
Welcome to the world of DataMedia.
In CM10.1 use a Root Browser app (e.g. ROM Toolbox lite) or a file manager app with root permissions (e.g. ES File Explorer or X-Plore) to move your CM11 ROM zip to a directory accessible to your new CWM recovery.
Myself I store all my ROM and recovery zips in the Download directory, where Chrome and Firefox also download files to.
e.g.
/storage/sdcard0/Download
/data/media/0/Download
Thanks woodytrain for your quick reply.
I tried to put my ROM /storage/sdcard0/Download but it's the same, i don't see this folder.
In /data, i've no folder
I tried to find obb/ with ES Explorer and it found it on /mnt/, is it normal ?
Last thing, i gone in WebOS in order to use Tailor and found this partition layout, i think it's not ok to flash KitKat :
USB (media) = 25.43 Gib
Android (system) = 408 Mib
Android (cache) = 200 Mib
Android (data) = 1.5 Gib
Unused Space = 8 Mib
I don't knom how to install KK on my touchpad. I don't understand because i don't thing to be a newbie, i flashed i9000 on CM 10.2, Touchpad on CM10.1, but KK made me crazy !
Thanks for your help !
You need to change your partition sizes. At the very least need to increase /system
And if you want to install a DataMedia (DM) ROM, you need to make additional adjustments.
Right now there are three (or four) KitKat (4.4.2) ROM's for the TouchPad (tenderloin) to choose from:
CM11 - 3.0 kernel (Milaq) - DM
CM11 - 3.4 kernel (invisiblek) - DM
Evervolv - AOSP - 3.4 kernel (flintman) - (two version:- one DM and one not)
If you want to install KitKat on your TouchPad will need to do some reading. Keep in mind all these KK 3.x kernel based ROMs are in development (experimental and/or for testing). Each has its own pros and cons, and various TouchPad features are not yet working, features you might have observed working in previous JB 2.6 kernel ROMs.
If you want to stay with JB, until KK is better baked for the TouchPad you may want to try out the new JB 3.x kernel ROM just released from jcscullins (01-25-14). It is NOT a DM ROM, whereas Milaq's CM10.2 (JB) is a DM ROM.
http://forum.xda-developers.com/showthread.php?t=1811480
Suggestions:
1. For each ROM you are interested in thoroughly read the OP. And suggest reading, at the minimum the last five pages of each thread.
2. Then visit [ROM GUIDE] How to Update/Install Android 4.2, 4.3 and 4.4 Builds on the HP TouchPad
http://forum.xda-developers.com/showthread.php?t=2321397
3. Be sure to read the info on how to update your partition for DM support. If you decide to go with a DM ROM, I would suggest using Tailor to change your partitions since you have Tailor installed on your device already.
4. Backup your device before proceeding. Generate a nandroid backup in your recovery as well as back up your app/data with Titanium Backup
5. A "full wipe" in your recovery (factory reset, including clearing caches, formatting /system) is generally recommended when doing major upgrades (not just a nightly flash of the same ROM).
Once you have chosen a ROM to install, and have downloaded the zips for both the matching ROM and Recovery zips (note each ROM has it's own specific recovery version matched to the ROM), then you should be ready to upgrade.
If you have questions before upgrading post your SPECIFIC questions/issues, identifying the ROM version you are coming from and going to.
Thanks woodytrain for your help.
I understood what i missed : root explorer button on Es Explorer
So, now, i can see my files with clockwork Recovery, yes ! I put them in /data/media/0/Download.
After that, i'm gone on Tailor to resize my partitions.
Now, i have :
600 Mb for system
200 Mb for cache
15 Go for media
and ~ 6 Go for data, it's not enough but don't care now...
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Bristow69 said:
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Click to expand...
Click to collapse
Not sure what is meant by "15 Go for media". Recommend you follow the partition instructions as listed in the OP of Milaq's CM11 ROM thread. At any rate...
Before you started the process did you do a nandroid, and backup your apps and data with TiBu or helium?
Then when you did the wipe, did you clear Dalvick cache as well?
And then did you flash the CWM recovery version listed in the OP of Milaq's CM11 ROM thread (CWM 6.0.4.6)? You MUST use that version.
http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.6-tenderloin.zip
You might want to redo the process and hold off installing gapps until you have booted into CM11. Then go back to recovery and install the gapps listed in the OP. Or install one of the PA-gapps packages.
With a few more posts you receive the right to post to the ROM dev thread. Joy!
I reply only to increase my posts and because i made a big big mistake after this post, i formated all partitions on clockworkmod (6.0.4.6 ). So i will create an other thread on forum...
Mad and Confused
I was duped into updating to 4.4 evervolv when i was on their 4.3.1 rom and im not understanding the layout of my sd-card now. i know all my info is still there but unsure how to reformat so i can use all my space. 32gb touchpad. i will use root explore app to get all my data but can i use onboard storage app to format? Really pissed im in this situation at all. Stupid to be on a 4.3.1 rom and update only to find out it's now a 4.4 rom and my sd-card is different. Thanks much
Nevermind, got it sorted. Good excuse to repartition and reformat everything. Still want nothing from evervolv but there 16mb Gapps package, mwahaha

[Q] Stuck installing Data/Media ROM

I've been trying to install milaq's 4.4 ROM on my Touchpad and I'm getting a bit stuck.
I've removed my previous 4.0.4 build so that I could start fresh and get my head around the data/media build. I've tried following the text guide and Roland's video guides but keep getting stuck at the same point.
I put the following files in the "cminstall" folder on my touchpad and ran ACMEinstaller5M:
cm-11-20140223-UNOFFICIAL-tenderloin
gapps-kk-20140105
recovery-clockwork-6.0.4.7-tenderloin
moboot_038-tenderloin
update-cm-tenderloin-data_resize_12228-0.1
So far I get the moboot menu and am able to get into the CWM-Based Recovery v6.0.4.7. This is where I'm stumped, I have no idea how to install the milaq ROM. I've had experience putting various CM Android builds on different devices (HD2, Defy+, Touchpad) but I'm struggling with this one. I know that I won't be able to install it the way I'm used to but I've tried searching and can't find what I'm supposed to do next.
I know this is a bit of a simple request but could anyone help me out with the next step? Once I'm past that, it'll be plain sailing I'm sure.
Thanks in advance.
yeoldgreat1 said:
I've been trying to install milaq's 4.4 ROM on my Touchpad and I'm getting a bit stuck.
I've removed my previous 4.0.4 build so that I could start fresh and get my head around the data/media build. I've tried following the text guide and Roland's video guides but keep getting stuck at the same point.
I put the following files in the "cminstall" folder on my touchpad and ran ACMEinstaller5M:
cm-11-20140223-UNOFFICIAL-tenderloin
gapps-kk-20140105
recovery-clockwork-6.0.4.7-tenderloin
moboot_038-tenderloin
update-cm-tenderloin-data_resize_12228-0.1
So far I get the moboot menu and am able to get into the CWM-Based Recovery v6.0.4.7. This is where I'm stumped, I have no idea how to install the milaq ROM. I've had experience putting various CM Android builds on different devices (HD2, Defy+, Touchpad) but I'm struggling with this one. I know that I won't be able to install it the way I'm used to but I've tried searching and can't find what I'm supposed to do next.
I know this is a bit of a simple request but could anyone help me out with the next step? Once I'm past that, it'll be plain sailing I'm sure.
Thanks in advance.
Click to expand...
Click to collapse
I just inherited an already rooted/android touch pad, so I'm in your same shoes right now. So i'm following close! haha.
I'm very new to the whole webos stuff here, but very experienced with rooting android.
But at this point, don't you just start flashing the .zips in clockwork after a full wipe (wipe factory, cache, davlik)?
BRUTAL BROCK said:
I just inherited an already rooted/android touch pad, so I'm in your same shoes right now. So i'm following close! haha.
I'm very new to the whole webos stuff here, but very experienced with rooting android.
But at this point, don't you just start flashing the .zips in clockwork after a full wipe (wipe factory, cache, davlik)?
Click to expand...
Click to collapse
That's what I thought but the ACMEinstaller wipes everything in the cminstall folder. Also, CWM only has the option to install zips from the sdcard which isn't there.
AcmeInstaller won't install the zip that resizes your partitions, and when you flash a data/media rom, the sdcard or media partitions are only accessible thru the rom itself so you won't be able to see them in recovery.
I think you will have to start again. Installing a data/media rom from a fresh install is, to be honest, a pain in the ass! You need to have a non-data/media build installed, ie. Jelly Bean/CM10.x, then resize partitions, etc, etc.
If you want to install kitkat from a fresh start, go for flintman's non-data/media version in the link in this post, and this recovery (20121215). Rename rom update-xxx, same for recovery, include moboot, and also have appropriate gapps to flash.
Hope this helps.
Oh yeah, and don't use AcmeInstaller5M, use the one ending in 5E =)
Data media install guide
Additional resources:
[ROM GUIDE] How to install Android on the HP TouchPad "The Easy Way"
[ROM GUIDE] How to install Android 4.4.2 Data Media builds on the HP TouchPadhttp://forum.xda-developers.com/showpost.php?p=42505399&postcount=2http://forum.xda-developers.com/showpost.php?p=42505399&postcount=2
RolandDeschain79 said:
You can't install CM11 data media builds with the ACMEInstaller. Here is my newest thread that explains how to get them fully installed. Please leave some feedback once you get it setup. :highfive:
[ROM GUIDE] How to install Android 4.4.2 Data Media builds on the HP TouchPad
Click to expand...
Click to collapse
That guide has been really helpful so far. I'm stuck at the last bit though.
I've installed PhilZ Clockworkmod but I don't know what to do from there. When I turn on the USB Drive, my PC can only see one SDcard (the WebOS one it sees normally) so I can't copy over the CM11 files to the Android one.
Any ideas?
If anyone is still having problems, this thread helped me. The instructions are in post #7 but you should read the preceding posts for background info.

[Q] Newbie stuck trying to upgrade from CM9 to CM11. Cannot access ROM Zips in CWM?!

Hello all - I am trying to upgrade from CM9 to CM11 using [ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies [3.0 kernel],
I repartitioned the drive with Tailor as suggested, and upgraded my CWM to (6.0.4.7)
My problem now is how do i get access the ROM/GAPPs zips? I can copy them over USB on my Win7 Machine to this folder, but CWM doesnt see them/cant access them.
I only have access to this folder in Win7. tried doing a clean install, and still no look.
Computer\cm_tenderloin\SD Card\rom.zip
the only options i have under "choose zip" in CWM are
/sdcard/0/clockworkmod - how do i get the rom zips there? i am totally stumped. i tried ADP to sideload a rom but the device isnt found. thanks in advance!!
Complete install of Android on the device
HI
I was in the same position I'd tried everything. In the end I decided to start from the beginning. What I did was pretty hardcore. I completely uninstalled Android. You need to erase the usb drive in Webos. you do this by booting into WebOS, going to settings/device info/reset options/erase USB drive. Remember before you do any of this get all you data of your device to you PC. Once this is done you are ready to install Android again. Now I found it was easier to upgrade from CM10.2 Data/Media build to CM11. So I installed Android on the device using these four files;
- moboot_38
- CM10.2,update-cm-10.2-20140126-UNOFFICIAL-tenderloin.zip
- update-gapps-jb4.3-20130813-signed.zip
- update-recovery-clockwork-no_metadata-6.0.3.6-20130926-tenderloin.zip
These files are available as a package at rootzwiki.com. There you will also find instructions on how to install android again and how to unistall android as well. Once android is installed now you need to resize the media and data partitions with tailor in webos. Now that this done you are ready to upgrade to CM11. So then booted up my device into Android. Then I connected it to my PC. enable USB conductivity on the device. I created a folder on the device on the now larger data partition (I used the same cminstall name for the folder).Transfered the CM11 (milaq version), Gapps and CMW 6.04.7 to this folder.
I would then boot into recovery. Now were going to update the CMW. choose install from zip find the folder and the CMW 6.0.4.7 file. install it.
once installed boot back into recovery. Now were going to inst CM11. First you need Perform a factory/data reset and wipe/format cache partition. Once this is done your ready to install CM11 and the Gapps. Choose install from zip. Find the cminstall folder you made install. then do exactly the process with the Gapps.
Android CM11 Milaq should work. This worked for me.
Hope this helps.
cheers
Data media install guide
Here is my full guide for installing Data Media Builds:
[ROM GUIDE]How to install Android 4.4.2 Data Media builds on the HP TouchPad
I have this problem
tgg05 said:
HI
I was in the same position I'd tried everything. In the end I decided to start from the beginning. What I did was pretty hardcore. I completely uninstalled Android. You need to erase the usb drive in Webos. you do this by booting into WebOS, going to settings/device info/reset options/erase USB drive. Remember before you do any of this get all you data of your device to you PC. Once this is done you are ready to install Android again. Now I found it was easier to upgrade from CM10.2 Data/Media build to CM11. So I installed Android on the device using these four files;
- moboot_38
- CM10.2,update-cm-10.2-20140126-UNOFFICIAL-tenderloin.zip
- update-gapps-jb4.3-20130813-signed.zip
- update-recovery-clockwork-no_metadata-6.0.3.6-20130926-tenderloin.zip
These files are available as a package at rootzwiki.com. There you will also find instructions on how to install android again and how to unistall android as well. Once android is installed now you need to resize the media and data partitions with tailor in webos. Now that this done you are ready to upgrade to CM11. So then booted up my device into Android. Then I connected it to my PC. enable USB conductivity on the device. I created a folder on the device on the now larger data partition (I used the same cminstall name for the folder).Transfered the CM11 (milaq version), Gapps and CMW 6.04.7 to this folder.
I would then boot into recovery. Now were going to update the CMW. choose install from zip find the folder and the CMW 6.0.4.7 file. install it.
once installed boot back into recovery. Now were going to inst CM11. First you need Perform a factory/data reset and wipe/format cache partition. Once this is done your ready to install CM11 and the Gapps. Choose install from zip. Find the cminstall folder you made install. then do exactly the process with the Gapps.
Android CM11 Milaq should work. This worked for me.
Hope this helps.
cheers
Click to expand...
Click to collapse
I am starting from a cm10.2 rom and i am encountering the same problem that the original poster is.

how to restore Apps and settings after upgrade from CM 9 to 12

My HP Touchpad 16G was running CM9 for a long time. So I finally uninstalled CM9 and using TPToolbox v42 fresh installed CM12.
Before wipe everything on SDCard, I did a backup in CWM and transferred it to my PC. After installed CM12, google backup brought some of my apps back, but I still lost a lot of settings of Apps and saves of my games.
So, I was wondering if I can restore them from my CWM backup. If yes, how to restore only the Apps, not CM9?
Thanks!
shawn8888 said:
My HP Touchpad 16G was running CM9 for a long time. So I finally uninstalled CM9 and using TPToolbox v42 fresh installed CM12.
Before wipe everything on SDCard, I did a backup in CWM and transferred it to my PC. After installed CM12, google backup brought some of my apps back, but I still lost a lot of settings of Apps and saves of my games.
So, I was wondering if I can restore them from my CWM backup. If yes, how to restore only the Apps, not CM9?
Thanks!
Click to expand...
Click to collapse
You won't be able to restore your data as you've now moved from Non data media, to a data media Rom. A lot of games save their data by linking it your Google+ or Facebook accounts. You can check the options menus and connect your games to your accounts in an attempt to recover your saved games. Good luck and enjoy CM12
A lot of the old games don't link to facebook or google to save, such as "cut the rope" and "plans vs zombies" etc.
If restore is not possible from cm 9 to 12, is it possible to upgrade from cm 12 to cm 12 nightly? How?
Thanks!
shawn8888 said:
A lot of the old games don't link to facebook or google to save, such as "cut the rope" and "plans vs zombies" etc.
If restore is not possible from cm 9 to 12, is it possible to upgrade from cm 12 to cm 12 nightly? How?
Thanks!
Click to expand...
Click to collapse
Like I said you can't restore your data, you didn't exactly list which games in your question but my suggestion remains the same. Some user data will get lost during an upgrade, that's to be expected when switching android versions.
You can upgrade your CM12 nightly Rom but if you wish to keep your data I suggest using your recovery.
From the Super Easy way guide in my signature. Enjoy
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 update Android 5.0.x or 4.4x Builds on the HP TouchPad

Categories

Resources