[Solved] No sdcard after flash The_apes Flashable zip in clockwork - TouchPad Q&A, Help & Troubleshooting

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

Related

[Q] Installing multiple recoveries

Installed CWM 6.03.6-datamedia recovery to install CM11 (Milaq) 12/24 CM11 ROM build. And then did a nandroid backup and backed up apps and system data with TiBU.
Now I wish to install several other new Kit Kat experimental ROMs (Evervolv and invisiblek) to test how the updated Kernel upgrades are coming along.
To prepare for the Evervolv ROM I installed open-recovery TWRP 2.6.3.0 (Sep12-2013). Was very easy to install TWRP by renaming as uImage.TWRP and copying to /boot. (thanks for the info from nevertells)
But not sure how to install Invisiblek CWM update which supports SE Linux as required by invisiblek ROM.
cwm_selinux_6.0.5.4_datamedia.uImage
I renamed the new recovery as "uImage.cwm_selinux_6.0.5.4_dm" and moved to /boot. And indeed it appears in the moboot menu. But when I select it I observe the following error:
Loading '/boot/uImage.cwm_selinux_6.0.5.4_dm' ... OK
Checking uImage... Invalid Size
I've re-downloaded and re-installed twice and the issue repeats itself.
I do not wish to destroy my existing CWM 6.0.3.6 (non selinux) recovery install.
So is it possible to install the newer CWM recovery so both CWM recovery tools can coexist and be accessible via the moboot menu at the same time?
woodytrain said:
Installed CWM 6.03.6-datamedia recovery to install CM11 (Milaq) 12/24 CM11 ROM build. And then did a nandroid backup and backed up apps and system data with TiBU.
Now I wish to install several other new Kit Kat experimental ROMs (Evervolv and invisiblek) to test how the updated Kernel upgrades are coming along.
To prepare for the Evervolv ROM I installed open-recovery TWRP 2.6.3.0 (Sep12-2013). Was very easy to install TWRP by renaming as uImage.TWRP and copying to /boot. (thanks for the info from nevertells)
But not sure how to install Invisiblek CWM update which supports SE Linux as required by invisiblek ROM.
cwm_selinux_6.0.5.4_datamedia.uImage
I renamed the new recovery as "uImage.cwm_selinux_6.0.5.4_dm" and moved to /boot. And indeed it appears in the moboot menu. But when I select it I observe the following error:
Loading '/boot/uImage.cwm_selinux_6.0.5.4_dm' ... OK
Checking uImage... Invalid Size
I've re-downloaded and re-installed twice and the issue repeats itself.
I do not wish to destroy my existing CWM 6.0.3.6 (non selinux) recovery install.
So is it possible to install the newer CWM recovery so both CWM recovery tools can coexist and be accessible via the moboot menu at the same time?
Click to expand...
Click to collapse
Your /boot partition does not have enough space for cwm_selinux_6.0.5.4_datamedia.ulmage, and you will need to clean up your /boot partition to make room for it.
goog888 said:
Your /boot partition does not have enough space for cwm_selinux_6.0.5.4_datamedia.ulmage, and you will need to clean up your /boot partition to make room for it.
Click to expand...
Click to collapse
I tried "cwm_selinux_6.0.5.4_datamedia.uImage", but it does not work with uImage.CyanogenMod. It caused this error "Checking uImage. Invalid Size", and I had to restore the backup to fix the issue.
However, I found out that Flemmard's "openrecovery-twrp-2.6.3.0-tenderloin-selinux.zip" can work very well with Invisblek's "cm-11-20131227-UNOFFICIAL-tenderloin.zip".
1. You should be able to flash Invisbleh's ROM over Milag's build to get 3.4 kernel.
2. The known black box issue has been fixed.
3. Playing video on YouTube could cause system reboot occasionally.
I have decided to go back to 10.2.
I am waiting for a cm11 release which includes a more stable 3.4 kernel.
Actually "cwm_selinux_6.0.5.4_datamedia.uImage" is functional, after I cleaned up my /boot folder.
And because it supports datamedia, it can restore my cm10.2 backup without any issue.
goog888 said:
Actually "cwm_selinux_6.0.5.4_datamedia.uImage" is functional, after I cleaned up my /boot folder.
And because it supports datamedia, it can restore my cm10.2 backup without any issue.
Click to expand...
Click to collapse
How did u clean it up?
Moody66 said:
How did u clean it up?
Click to expand...
Click to collapse
My /boot folder didn't have enough space for two different CWM.
You will need to download the free application "Rom Toolbox Lite" from the Store.
First I backed up and removed the original uImage.ClockworkMod (rev 6.0.3.6) from the /boot folder to save 5.8MB.
Then Invisiblek's "cwm_selinux_6.0.5.4_datamedia.uImage" (7.1MB) is renamed to uImage.ClockworkMod and "moved" to /boot folder.
Thanks. Recovery is driving me nuts. So many roms. Each wanting a different recovery. I try to help by testing rooms but I guess I will just stick to one as its to difficult to keep up with them all. Had to Webos doctor several times this week. Back to mom data media for me. Thanks again!

[Q] Updated CWM and resized partition, now CWM can't find my folder structure

I just updated my CWM to 6.0.4.6 in preparation for upgrading my CM10 to CM11. Here's what I did:
Backup app data using Titanium.
Cleared both caches, installed the new CWM zip.
Rebooted to CM10:
copied my old nanroid backup to my computer.
Rebooted into CWM:
made a new nandroid backup.
Rebooted into webos:
resized my system partition from 400 to 600 mb.
When I booted in CWM to install the 4.4 rom all my folders were missing. All I can see is
/sdcard/
-0/
-clockworkmod/
The only folder in 0/ is clockworkmod/backup/[mynewnandroidbackup]/
Any idea what I need to do to get things straightened out?
CM10 still boots fine and my files show up in /sdcard0/. There is no sign of a folder called /sdcard/. Same story if I explore the device with a computer.
I should mention that I also moved my nandroid backup to my computer, off the touchpad to save space before I resized my partitions. I then moved it back into the folder. I wouldn't be opposed to wiping the thing and starting over to get 4.4 working.
Any ideas?
kspanks04 said:
I just updated my CWM to 6.0.4.6 in preparation for upgrading my CM10 to CM11. Here's what I did:
When I booted in CWM to install the 4.4 rom all my folders were missing. All I can see is
/sdcard/
-0/
-clockworkmod/
The only folder in 0/ is clockworkmod/backup/[mynewnandroidbackup]/
Any idea what I need to do to get things straightened out?
Click to expand...
Click to collapse
First, this issue that you observe has been discussed ad nauseam in various CM11 ROM development threads.
Second, you did not post which specific CM11 ROM you are planning to employ. So I assume it is Milaq's CM11 ROM (kernel 3.0+).
At any rate, what you are observing in an inability to directly access the /external_sd partition (on the TouchPad), which is accessible in previous CM builds, but is no longer directly accessible in Milaq's recent CM11 builds (Kernel 3.0.101) or in his recent CWM recoveries.
http://forum.xda-developers.com/showpost.php?p=49216229
• Milaq and others have suggested you can use ADB to mount the partition manually (sorry no instructions).
• Some have posted you can use Invisiblek's recovery (CWM 6.0.5.4 selinux datamedia) to flash Milaq's recent CM11 (Kernel 3.0+) ROM's
• You may be able to find a version of TWRP that can access the /external_sd partition.
On a related note, the new DataMedia storage paradigm which is the future of Android, has been designed into the newer CM11 and other KitKat ROM and recovery builds. Thus you need to increase the size of your /data partition.
You can use the Tailor app within WebOS to reduce the size of /media partition, then increase the /data partition size. And there are some scripts available that do similarly.
Best to read the specific ROM thread (including the OP) for more info on how DataMedia applies to the ROM build you are employing, and then be sure to read later posts in the thread regarding the inaccessibility of /external_sd: http://forum.xda-developers.com/showthread.php?t=2542353
It is possible that future builds of the CM11 ROM (kernel 3.0+) might provide access to /external_sd once again. Will see. Fingers crossed.
I tried invisiblek's cwm recovery and it did not provide access to /external_sd
(and there is confusion on the recoveries specific version number)
http://forum.xda-developers.com/showpost.php?p=49423381
There is another recovery on invisiblek's site: openrecovery-twrp-2.6.3.0-tenderloin.zip
Anyone have experience with that recovery version, ability to access /external_sd or "compatibility" with Milaq's newer CM11 ROM builds?
Yes sorry, Milaqs rom that you linked is the one I was working from. I don't have ten posts so that's why I'm posting here. I read through most of that forum and tried searching for my issue with no luck.
I went back and saw a couple posts that matched my problem with the following solution:
http://forum.xda-developers.com/showpost.php?p=49154585&postcount=471
When I get home I will try this although I didn't remember seeing that folder when I explored my device on Windows.
Thank you for the reply and sorry for the redundancy!
Ok so I browsed my sd storage and there is no 0 folder in /sdcard0/media
Not sure what to do now
kspanks04 said:
Ok so I browsed my sd storage and there is no 0 folder in /sdcard0/media
Not sure what to do now
Click to expand...
Click to collapse
Hey buddy,
Make sure your file browser is using root. Personally I use Es file explorer. Turn on root explorer (find it at the bottom in the side panel) and make system writeable (By clicking on 'root explorer' then 'Mount R/W'). I'm sure most file managers will have something similar in their settings.
Then go to the root of your device by clicking '/' at the top. From there you should be able to follow the post you linked above by gabhroo123. And yes i tried his method and indeed i could see the files i pasted into the folder.
Good Luck
Here is another trick that worked for me. Recover a previous stored ROM that supported both sd1 and sd0. Use file manager to copy the files you want from sd1 to sd0. Then go back to the new ROM and you will have access to your files on sd0.
Merfy said:
Hey buddy,
Make sure your file browser is using root. Personally I use Es file explorer. Turn on root explorer (find it at the bottom in the side panel) and make system writeable (By clicking on 'root explorer' then 'Mount R/W'). I'm sure most file managers will have something similar in their settings.
Then go to the root of your device by clicking '/' at the top. From there you should be able to follow the post you linked above by gabhroo123. And yes i tried his method and indeed i could see the files i pasted into the folder.
Good Luck
Click to expand...
Click to collapse
Ahhh thank you. I had tried this with a different file explorer in root. Es did the trick.
Now I need figure out how to fix these black screens that lock up after a good amount of inactivity.
Greeting HP Touchpad Expert: I need help.
I didn't mean to post this thread but I have same issue.. only I have this..
I also updated my CWM to http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.7-tenderloin.zip
in preparation for upgrading my CM09 to CM11 (Milanq 4.4 Kitkat). Here's what I did:
Backup app data using Titanium.
Cleared both caches, installed the new CWM zip.
Rebooted to CM9:
copied my old nanroid backup to my computer.
Rebooted into CWM:
made a new nandroid backup.
I have not yet resize system partition.
Now, when I want reboot to CWM install the 4.4 rom all my folders were missing.
All I can see is
/sdcard/
-0/
-clockworkmod/
-clockworkmod/backup
Yes I have tried to ES File Explorer (R+W root) and following gabhroo123's notes above
I do not have
/data/media nor /data/media/0 folder
only empty /data folder.... I am able to write to copy older recovery-clockwork to /data but not "/" ...
When reboot to CWM 6.0.4.7 I still don't see any zip file.. (No files found message show).
Can someone at least point me the right URL or discussion xda-developers.com thread so I can read them.
I am not sure what I did wrong...
What extra steps I suppose to do ...because I have HP Touchpad with CWM 5.x.x + Android 4.0.1.x + CM 9 + mobo 0.35 ?
My planning steps were
#1) upgrade CWM to 6.0.4.7
#2) upgrade CM 11
#3) upgrade Gapps
Reference http://forum.xda-developers.com/showthread.php?t=2542353
([ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies [3.0 kernel])
I do see /sdcard/clockworkmod/backup/backupfolder.. in CM 9 and I did put CM 11 and Gapps in several place in
/media , /sdcard/media, /sdcard/cminstall etc.. but nothing.. kept saying file not found..
Should I downgrade CWM back to 5.x.x ? I do not see any install zip file at all ...how?
HELP!
Thank you

[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.

[Q] Switching the default moboot option to AOKP

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:

[Q] Move from CM-11 to CM-13

I have CM-11 (2016-08-15 nightly) installed on my HD+, along with CWM recovery "6046", and am happy with it. However, my other Android devices have Android 6.0, so I thought I'd consider CM-13. Questions:
Is moving to TWRP a requirement? I see statements that CWM recovery is no longer in active development. So what? Are changes being made (see next item) just for the sake of change (a popular activity in software development), or are there real advances that TWRP enables?
In preparation, I downloaded the cm_ovation-ota-MOB31K.161125.zip and open_gapps-arm-6.0-nano-20170117.zip files. I was astounded by the sixe of the latter. What is with the "Open Gapps" files??? I note that the pico one for v4.4 is 2.5 times the size of the one I have been using ( pa_gapps-modular-pico-4.4.4-20141110-signed.zip ). I thought these were supposed to be basic, minimal files.
I'm looking for an install procedure from CM-11. I assume that just means upgrade to TRWP if necessary, and then just use that to install the above zip. I see no discussions of this in this subforum; is it all over in the "Development" forum?
What is the performance of CM-13 like, and is it now stable enough for daily use? I see a long thread peppered with "thank you"s that started two years ago, and I'm wondering if there's anything more succinct.
DeanGibson said:
I have CM-11 (2016-08-15 nightly) installed on my HD+, along with CWM recovery "6046", and am happy with it. However, my other Android devices have Android 6.0, so I thought I'd consider CM-13.
Click to expand...
Click to collapse
FWIW -- I had enjoyed good performance CM11 until about mid last year when many commonly used apps started to become unresponsive and oftentime crashed (force-closed). So over the holidays break I took the plunge and upgraded to Amaces' LN14.1 experimental build lnos_ovation-ota-NMF26Q.170104, so far the performance is as good as it used to be with CM11.
Questions:
Is moving to TWRP a requirement? I see statements that CWM recovery is no longer in active development. So what? Are changes being made (see next item) just for the sake of change (a popular activity in software development), or are there real advances that TWRP enables?
Click to expand...
Click to collapse
Every major release of CM, starting from CM7 -> CM9 -> CM10 to CM11, has required a new and non-backward compatible version of CWM.
I don't believe that CWM 6.0.4.6 can flash CM12 and CM13, and you can find pointers on what recovery versions are needed and are available at https://forum.xda-developers.com/nook-hd/development/boot-sd-external-recoveries-twrp-2-8-3-t3314870.
In preparation, I downloaded the cm_ovation-ota-MOB31K.161125.zip and open_gapps-arm-6.0-nano-20170117.zip files. I was astounded by the sixe of the latter. What is with the "Open Gapps" files??? I note that the pico one for v4.4 is 2.5 times the size of the one I have been using ( pa_gapps-modular-pico-4.4.4-20141110-signed.zip ). I thought these were supposed to be basic, minimal files.
Click to expand...
Click to collapse
I used the minimalist pico package, and then added afterward a couple of missing essential apps like Google Maps.
I'm looking for an install procedure from CM-11. I assume that just means upgrade to TRWP if necessary, and then just use that to install the above zip. I see no discussions of this in this subforum; is it all over in the "Development" forum?
Click to expand...
Click to collapse
The most straightforward route which I found and used is to create a SD-based recovery using the pre-packaged SD image available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778, just unzip and burn the image to SD then add to the card the ROM, GApps, and (EMMC) TWRP zip files you wish to flash. Then boot up the SD card into TWRP, (optionally backup your CM11 ROM system & data), do "wipe /data & factory reset", and flash the 3 zip files and you are set to go.
Alternatively you can try to use a similar approach as outlined at https://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171 -- i.e., use CWM 6.0.4.6 to flash new TWRP then boot into the new TWRP to wipe and flash new ROM and GApps. This was the route I took when I upgraded to CM12.1 to try it out.
digixmax said:
... Alternatively you can try to use a similar approach as outlined at https://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171 -- i.e., use CWM 6.0.4.6 to flash new TWRP then boot into the new TWRP to wipe and flash new ROM and GApps. This was the route I took when I upgraded to CM12.1 to try it out.
Click to expand...
Click to collapse
Thanks very much for the info! That's what I did, and it was simple and (reasonably) quick. I note that CM wants to go ahead and install the CWM recovery. I assume I should not let it do so.
Now, to get Titanium Backup to think it's got root. This appears to be a bit of silliness. I tried several "superuser" apps (including the "phh" one), to no avail so far ...
Edit: OK, here it is ...
belfastraven said:
There is still a "bug" I believe, in that when the cm/ln rom is first installed on a device with a clean data partition (after a wipe or factory reset), even though developer options will say you have root, you actually don't. Changing the root selection to something else and then changing it back causes the necessary system file to be created. As long as you don't wipe data, you will not have to do this again on dirty flashes. What is new in the last few months is that, accessible through developer options, there is a rudimentary root manager available in the rom, where you can determine how root requests from various applications should be handled and see which apps have requested root access.
Click to expand...
Click to collapse

Categories

Resources