[Q] Updated CWM and resized partition, now CWM can't find my folder structure - TouchPad Q&A, Help & Troubleshooting

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

Related

CWM Recovery [GT-P6810][wifi]

Hi,
Please find port of Clockwork Mod Recovery 5.0.2.7 for GT-P6810.
(this is not a kernel replacement- just a cwm recovery image)
This is ported from the garyd9 6210 cwm recovery so please go thank him. (in 7.0+ forums)
Modified to work on 6810.
Incorporates garyd9 patches for sd card handling.
also thanks to ezynow and kassemja - for advice and bug fixing
based on stock firmware.
I have tried backup & restore, wipe cache , wipe dalvik-cache and so far has worked.
New version 2012-02-01: data wipe and then restore, backup to external and to internal (internal is now the default).
But we need some further testers.
Please only try if you what you are doing & know how to flash with odin.
Requirements: you need to be rooted.
Please know how to recover your device independently before using this!
DO NOT ATTEMPT TO USE ON ANY OTHER DEVICE. THE PARTITIONS ON THE P6810 ARE DIFFERENT!
Ok - first identified issue: If we are backing up to the external sdcard. This is fat32. So we have a file size limitation.
Also there may be a tool set size limitation in the binaries (as ported). This mainly affects "data", as this seems to include
pictures, video etc from the /data/media directories. So looks like to me data > 2G wont restore. Although it does create
(in my example 3.5G file and checksum is ok). I found that the 3.5G would not load. I retarred with all stuff in /data/media
deleted, (and fixed the nandroid checksum) then the data file loads (about 900M) and my device is recovered. I'm expecting if you try to back up more than 4G, the file will not be usable due to FAT32. I Hope this is clear.
So please check your file sizes (and nandroid sums) before attempting a restore.
So with this in mind,
Update: 2012-02-01: now backing up in the CWM tradition by default to the internal sd (which is ext4), and there are extra options enabled in the backup/restore menu. Please remember we are still in test mode. I think It is now working as intended and not backing up /data/media its easy to tell from the size of the data nandroid file.
So please backup your precious videos, pics etc from the /data/media directory independently.
Odin tar file (in the pda):
davp said:
Hi,
Please find port of Clockwork Mod Recovery 5.0.2.7 for GT-P6810.
(this is not a kernel replacement- just a cwm recovery image)
This is ported from the garyd9 6210 cwm recovery so please go thank him. (in 7.0+ forums)
Modified to work on 6810.
Incorporates garyd9 patches for sd card handling.
also thanks to ezynow and kassemja - for advice and bug fixing
based on stock firmware.
I have tried backup & restore, wipe cache , wipe dalvik-cache and so far has worked.
But we need some further testers.
Please only try if you what you are doing & know how to flash with odin.
Requirements: you need to be rooted.
Please know how to recover your device independently before using this!
DO NOT ATTEMPT TO USE ON ANY OTHER DEVICE. THE PARTITIONS ON THE P6810 ARE DIFFERENT!
Odin tar file (in the pda):
Click to expand...
Click to collapse
Big applause!
I've just tried to install CWM Recovery on my GT-P6810.
Wipe: works fine
Backup: seems to work fine
Restore: MD5 mismatch! error
I tried the following.
adb shell
# cd /sdcard/clockworkmod/backup/2012-01-30.**.**.**
# rm nandroid.md5 (error)
# md5sum *img > nandroid.md5
My GT-P6810 started to restore. But after reboot, nothing changed...
padebije said:
Big applause!
I've just tried to install CWM Recovery on my GT-P6810.
Wipe: works fine
Backup: seems to work fine
Restore: MD5 mismatch! error
I tried the following.
adb shell
# cd /sdcard/clockworkmod/backup/2012-01-30.**.**.**
# rm nandroid.md5 (error)
# md5sum *img > nandroid.md5
My GT-P6810 started to restore. But after reboot, nothing changed...
Click to expand...
Click to collapse
You installed via odin from above link? Any other source (market, another thread will not work on the P6810)
Thanks for trying.
Replacing the md5s is probably not a safe thing to do, the md5s are to ensure the backup is good. It would have been better to check the md5s and see which file is damaged.
Suggest:
Try a different microsd
Make sure your external microsd card is working correctly and has enough space
Move or delete the existing backup you did
Make another backup
check the md5sums of the files match the nandroid.md5 (cat nandroid.md5 ; md5sum *)
check the file sizes make sense (recovery and boot are 8M exactly, system ~684M, data varies)
If recovery and boot are not 8M, or any sums dont match what is in nandroid.md5, dont try to restore.
report back (please)
davp said:
You installed via odin from above link? Any other source (market, another thread will not work on the P6810)
Thanks for trying.
Replacing the md5s is probably not a safe thing to do, the md5s are to ensure the backup is good. It would have been better to check the md5s and see which file is damaged.
Suggest:
Try a different microsd
Make sure your external microsd card is working correctly and has enough space
Move or delete the existing backup you did
Make another backup
check the md5sums of the files match the nandroid.md5 (cat nandroid.md5 ; md5sum *)
check the file sizes make sense (recovery and boot are 8M exactly, system ~684M, data varies)
If recovery and boot are not 8M, or any sums dont match what is in nandroid.md5, dont try to restore.
report back (please)
Click to expand...
Click to collapse
Could you tell me the URL of Odin you mentioned above?
I installed via Odin3-v1. 85...
Ok guys, looks like there are file size issues due to fat32 external sdcard etc.
I believe the tool can still be useful, but be aware its limitations.
Have documented this in the first post as an issue.
The download is the same (I cant fix the fat32 limits).
padebije said:
Could you tell me the URL of Odin you mentioned above?
I installed via Odin3-v1. 85...
Click to expand...
Click to collapse
I use the one I had installed months ago (for phone). It the same version (downloaded mine from Intratech's gs2 official rom thread).
Sent from my GT-I9100 using XDA App
BRAVOOOOO!!!!!
I deleted all movie files > 2GB, and tried backup, wipe data, and restore again.
This time, I could make it thanks to your advice!
davp & ezy now, looks like you're famous.
http://www.theandroidsoul.com/new-g...or-both-3gwifi-edition-and-wifi-only-edition/
Thanks for your help with this kassemja!
cheers
Update posted in first post.
Hi davp,
You should push source to git hub, perhaps we could enlist Koush or Codeworkx to assist us. of all the options i have tried with recovery.fstab i was never happy.
i could never get both internal and external sd cards to mount. when i had them both setup the menu options for flashing and restore / backup will show option for internal sd cards.
IMHO, recovery should back up to external, as if you really bung up your device you will not have access to internal memory. The fact most of us only have 16gb internal memory its makes more sense to back up to external sd card.
i remember the nook colour, had a simalar debacle when they 1st released CWM mod for it. you could look there. i really havn't had a chance to dig into this. perhaps over the weekend i get more time
davp said:
Thanks for your help with this kassemja!
cheers
Update posted in first post.
Click to expand...
Click to collapse
Any chance somebody could please extract stock recovery and send me a target version?
Sent from my GT-P6810 using XDA Premium App
Tar not target...
Sent from my GT-P6810 using XDA Premium App
Help
Hi Guys,
EDIT: - I flashed an incomplete tar file as the download had not finished when I copied to sd card.
Got a small issues,
I have a Tab 7.7 running HC 3.2.
I gained root access and then install mobile odin pro.
I then proceeded to install this CWM and its not stuck at the galaxy tab 7.7 black and white screen at boot.
I selected the file i downloaded here using the recovery option to flash in mobile odin.
any ideas what i can do to get this working again?
Many Thanks
Syl

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

[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

Android Version 4.4.4 Upgrade Issue

Hi,
I upgraded my Android to version 4.4.4 via the updater following these steps (from what I can recall).
1) I downloaded the latest Release version & the latest Gapps files locally to the tablet & went to recovery.
2) I took a backup, wiped Dalvik cache & apply update from sdcard.
3) I ran the Android release build zip file but forgot to run the Gapps zip file.
4) Android upgraded to version 4.4.4 but when I log in I get prompted that 'Unfortunately Google Play Store has stopped' . As I forgot to run the Gapps zip file that is to be expected.
When I boot into recovery it can only see the following directories & not the update folder where the Gapps file was downloaded.
Android
DCIM
LOST.DIR
appdata
clockworkmd
downloads
ringtones
wallpapers
The recovery doesn't seem to be able to see the sdcard & only the internal storage.
However if I copy the Gapps zip file to any of the folders above, boot to recovery again it won't see the zip file.
I also seem to have wiped my backup trying to recovery the situation so can't roll back.
Within the recovery menu I've tried to mount/unmounts the below but it still can't see any of the folders.
Mount /boot
Unmount /cache
Mount /data
Mount /system
unmounts /sdcard
The above is my current settings but I've tried mounting them all.
To complicate the matter further the USB port on the tablet is broken so I can't connect it to my computer.
Previously to transfer files I used a ftp client on my laptop & Wifi File Transfer Pro on the tablet.
I don't know whether to finally give up on my touchpad so any help/advice is much appreciated.
Thanks,
Chip
ChipJnr said:
Hi,
I upgraded my Android to version 4.4.4 via the updater following these steps (from what I can recall).
1) I downloaded the latest Release version & the latest Gapps files locally to the tablet & went to recovery.
2) I took a backup, wiped Dalvik cache & apply update from sdcard.
3) I ran the Android release build zip file but forgot to run the Gapps zip file.
4) Android upgraded to version 4.4.4 but when I log in I get prompted that 'Unfortunately Google Play Store has stopped' . As I forgot to run the Gapps zip file that is to be expected.
When I boot into recovery it can only see the following directories & not the update folder where the Gapps file was downloaded.
Android
DCIM
LOST.DIR
appdata
clockworkmd
downloads
ringtones
wallpapers
The recovery doesn't seem to be able to see the sdcard & only the internal storage.
However if I copy the Gapps zip file to any of the folders above, boot to recovery again it won't see the zip file.
I also seem to have wiped my backup trying to recovery the situation so can't roll back.
Within the recovery menu I've tried to mount/unmounts the below but it still can't see any of the folders.
Mount /boot
Unmount /cache
Mount /data
Mount /system
unmounts /sdcard
The above is my current settings but I've tried mounting them all.
To complicate the matter further the USB port on the tablet is broken so I can't connect it to my computer.
Previously to transfer files I used a ftp client on my laptop & Wifi File Transfer Pro on the tablet.
I don't know whether to finally give up on my touchpad so any help/advice is much appreciated.
Thanks,
Chip
Click to expand...
Click to collapse
Access to the sdcard has to be enabled by the developer. You must have installed one that doesn't (since you didn't specify which it was)
shumash said:
Access to the sdcard has to be enabled by the developer. You must have installed one that doesn't (since you didn't specify which it was)
Click to expand...
Click to collapse
Here is the build info currently on the tablet.
Kernel Version:
3.4.82-tenderloin
Mod Version:
ev_ternderloin=testing-2015.01.22
Build number:
ev_tenerloin-eng 4.4.4 KTU84Q eng.flintman.20150122.215911 test-keys
If this build doesn't recognise the sdcard, should it not recognise the Gapps zip file on the internal storage?
There is 1.4GB in total on the internal storage with 388MB free.
Do you know if there is anyway I could get a build of Android & Gapps on the tablet & upgrade to that?
Thanks for responding to the thread.
ChipJnr said:
Here is the build info currently on the tablet.
Kernel Version:
3.4.82-tenderloin
Mod Version:
ev_ternderloin=testing-2015.01.22
Build number:
ev_tenerloin-eng 4.4.4 KTU84Q eng.flintman.20150122.215911 test-keys
If this build doesn't recognise the sdcard, should it not recognise the Gapps zip file on the internal storage?
There is 1.4GB in total on the internal storage with 388MB free.
Do you know if there is anyway I could get a build of Android & Gapps on the tablet & upgrade to that?
Thanks for responding to the thread.
Click to expand...
Click to collapse
I doubt you've used the latest and proper way to install 4.4/5.0 ROM's. Go here. Start over and follow the instructions to the letter. Read everything first and decide how you want to proceed before doing anything.

[UB]FOTA TWRP/PhilZ installer APK and Flashable ZIP recovery

F2FS improves the benchmark score in most (if not all) devices by around 20%..
For testing:
I have modified an APK containing Aroma Installer to flash recoveries to fotakernel for our ZR's. This is an initial release..
It contains 2 recoveries.
PhilZ Touch and TWRP with f2fs (TWRP) support which has been tested and working in both Resurrection and Validus builds/ports and should work in all cm11 and CM12/CM12.1 with f2fs working in cm12 after march this year
Install the apk and flash either Philz or Twrp through the app in the drawer..
And no, this is not Xperia Recovery manager.
The recoveries are both contained in the app so making it 22MB to download.
The TWRP 2.8.7.0 has new graphics and f2fs support
PhilZ is stock 6.57.9 cwm v6.0.5.1 shared by @uncomment
Download APP here (contains the 2 recoveries mentioned above): Removed because of bugs.. will fix and upload to new link..
TWRP 2.8.7.0 f2fs with updated graphics flashable zip: https://drive.google.com/file/d/0B3slVcYWwXQ-RjNKUDhWWk5OemM/view?usp=sharing
(This is the latest recovery from TeamWin with their new blue theme.. I personally didn't like all that blue so I changed the images.. See screenshot below)
Philz Touch 6.57.9 flashable zip:https://drive.google.com/file/d/0B3slVcYWwXQ-MEd4TU1vb0NYcmc/view?usp=sharing
Flashable ZIP stock TWRP 2.8.7.0 with f2fs:
Put the zip in you sd card and flash through recovery.. This will push the twrp 2.8.7.0 f2fs to your fota kernel, reboot recovery after flash...
Download: https://drive.google.com/file/d/0B3slVcYWwXQ-YTB6V1N0eEx5SU0/view?usp=sharing
Please test (recovery.img)
UPDATED TO TWRP 2.8.7.0
Download here: https://drive.google.com/file/d/0B3slVcYWwXQ-SjJRRjdyZ2pzeXc/view?usp=sharing
Instructions are the same as below...
This is TWRP 2.8.6.0
Download here:
https://drive.google.com/file/d/0B3slVcYWwXQ-Q0pEYzlFSjhPNFk/view?usp=sharing
Place the recovery.img (it is named twrp.img when you download but rename to recovery.img) to you internal storage and use adb or emulator (download Android Terminal Emulator free from Store) commands to install to your Fota:
su (enter and grant root access if using Emulator)
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel (enter)
If you use Xperia Recovery Manager app by @championswimmer, rename the recovery.img to twrp.img and put in the TWRPXperia folder on your sd-card and flash to Fota through the app. Confirmed working.
If the image doesn't install correctly, please flash this hack:
http://forum.xda-developers.com/show...51&postcount=2
Only cache and data/ ext-sdcard is convertible for now, if you try to convert system, you will brick your phone..
Use the following method to convert:
Convert to f2fs by pressing Wipe > Advanced Wipe > select the desired partition > Repair or change filesystem > Change filesystem > f2fs
Some added info by @nostupidthing
with f2fs twrp installed, i've changed /cache and /data into f2fs without wiping. you just have to backup /data, then format it as f2fs, click "use rm-rf instead for format" in twrp settings, then restore /data.
If any one is looking for a theme for twrp recovery, i found an excellent theme here: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
(Download resolution 720x1280 for ZR)
As an added service I am willing to personalize the splash screen at recovery start-up should you have any request ie your name, flag etc but i will insist that "TeamWin" will be present somewhere on your personalized splash.. After all, we all benefit from their hard work.. Do not expect your request to be done within the hour but periodically check and i will upload and link as and when you request is done..
Massive thanks to @uncomment and @o-l-a-v and @Olivier and @blastagator and @qsnc including @nostupidthing for testing and for making this possible. @SdtBarbarossa for the app!!
the "now changing the microsd to f2fs" is not necessary for /data & /cache. you may or may not like to do it, and i ended up not doing it because copying my several gbs of files out of the microsd takes so much time and i just gave up..
but if anyone wants to do it, basically you just copy the files to your PC, then format the microsd to f2fs, then copy the files back there.
nostupidthing said:
the "now changing the microsd to f2fs" is not necessary for /data & /cache. you may or may not like to do it, and i ended up not doing it because copying my several gbs of files out of the microsd takes so much time and i just gave up..
but if anyone wants to do it, basically you just copy the files to your PC, then format the microsd to f2fs, then copy the files back there.
Click to expand...
Click to collapse
I agree with you.. I have formatted my ext sd card but like you said, took ages to copy the content to pc and back again.. In my opinion not worth doing if anyone, like me, use the ext_sd card for storage of music and downloads etc.. Cache and data absolutely worth doing tho.. A great many thanks for your comments and help doing this..
sent from Paul's phone
one more thing. backing up /data via twrp will not back up your "internal sd" files, like camera photos if you store them internally instead of on the microsd, so you have to copy those yourself as well.
Added flashable zip to op... Should make things easier..
the 2.8.7 flashable zip works, bro. thx.
hey, any chance that you make an insaller version ?
Ilko said:
hey, any chance that you make an insaller version ?
Click to expand...
Click to collapse
I'll look in to it..
hagar006 said:
I'll look in to it..
Click to expand...
Click to collapse
Great
BTW, I would suggest you to set TWRP's file manager to open SDCARD1 by default instead of SDCARD0, if possible, or even both to let users choose. I'm not sure if this is ROM or Recovery dependent because it worked this way through the latest Validus ROM. I'd bet on the recovery side though.
Ilko said:
Great
BTW, I would suggest you to set TWRP's file manager to open SDCARD1 by default instead of SDCARD0, if possible, or even both to let users choose. I'm not sure if this is ROM or Recovery dependent because it worked this way through the latest Validus ROM. I'd bet on the recovery side though.
Click to expand...
Click to collapse
It's party of the recovery but a few spaces down from the top in file manager is external_SD and a few spaces lower is SD_card so should be easy enough to find the way around..
BTW I've made new images and things for twrp which makes it a little easier to see but I'm waiting for permission from someone as I used their ui.xml to make that.. Will be added as soon as
Sent from my ZR

Categories

Resources