Database Develop

[Q] Yet another Market issue...

I'm using HoneyComb (HC) v4 on eMMC 2nd edition i got from the following post:
http://forum.xda-developers.com/showthread.php?t=947071
The main problem I'm having with it is that the Market isn't keeping track of what has been installed. First thing I did after flashing it to the emmc (following all directions) was to install Titanium Backup. Once it was installed and I went back into market, I clicked on the MyApps link and it said no installed aplications.
Is this a common issue? I've been reading for weeks, but never seen this issue. I have tried the cache and data fix, but still no go. I didn't have this issue with the 1st edition of HCv4.
I would have posted this in the main tread for the release, but haven't contributed enough to be able to post in that forum.
Thanks for any help!
Dan

Strange. Will investigate...
Sam
Sent from my HTC Desire using XDA App

I did follow your directions:
Instructions:
These differ from above instructions, but you can refer to them if you have a doubt.
- Boot to Ext4 Bootable CWR SD with zip file on it.
- In mounts and storage, format /system, /data and /cache -> MANDATORY!
- In the same menu, make sure /system /data and /boot aren't mounted
- make sure sdcard is mounted
- choose zip from sdcard​
I had flashed the 3.0.0.6 CWR SD to try out Phiremod's CM7 rom. Didn't like it after running Honeycomb. Formatted those three partitions, and checked mounting before installing the zip.
Am I the only one having this issue? I can reload it if you think that might help. I can't wait until there is a version of HC that will do video!
Thanks! Dan

I was reading the CM7 Developers Thread http://forum.xda-developers.com/showthread.php?t=960537 and noticed they are having this same issue with Market.
Looking back at your post, I see you are using the Gingerbread versions of the GApps... So I think this explains the issue.
Hopefully you and them together can get this figured out. I can't wait for a AOSP release of Honeycomb! lol...

[Q] Nandroid backup - cant mount /data

Hi,
I would like to flash a new baseband on because 0622 gives me terrible battery life. So I tried to do a nandroid backup from within CWM 4.0.0.9, but it keeps failing. It seems able to backup the boot image, recovery image, and system, but then says cant mount /data. The size of each backup seems to be just under 200MB.
I am running CM7 #84, with vorkkernel from Friday. I did convert my filesystem to ext4, and had to run the vorkkernel updater with the internal flag (so I think my CWM is also internal).
Can anyone help?
NOT DEVELOPMENT CLOSED USE THE Q & A or the genral section for such questions

Have you tried the last CWM ?

I've never been able to successfully restore a complete backup - something always ***** up along the way for me. I have to wipe, install the ROM, GAPPS, and then do an 'advanced restore' of just the /data/ partition.
Also, the latest CWM won't install for me. I just get "an error occurred while attempting to run privileged commands"
...whatever that means...

Thanks guys, I was able to solve this. I think I needed to upgrade from CWM 4.0.0.9 (obtained via rom manager) to 4.0.1.4 (obtained from a thread on these forums).
Once I had done that, I could backup to the internal SD card (previously it was trying to backup to the external SD card), and also restore the backup. So all fine.

Ancalagon_ZA said:
Thanks guys, I was able to solve this. I think I needed to upgrade from CWM 4.0.0.9 (obtained via rom manager) to 4.0.1.4 (obtained from a thread on these forums).
Once I had done that, I could backup to the internal SD card (previously it was trying to backup to the external SD card), and also restore the backup. So all fine.
Click to expand...
Click to collapse
I've the same problem.
But upgranding to CWM 4.0.1.4 doesn't helped me :/
If I've installed an ext4 rom, CWM are not able to do a nandroid backup...
With an ext3 rom, no problem.
You can make a nandroid backup with, for example, slick2x-F rom???

Wing_Zero85 said:
I've the same problem.
But upgranding to CWM 4.0.1.4 doesn't helped me :/
If I've installed an ext4 rom, CWM are not able to do a nandroid backup...
With an ext3 rom, no problem.
You can make a nandroid backup with, for example, slick2x-F rom???
Click to expand...
Click to collapse
The recovery must be capable to support ext4 partition, try rusty's recoveries. And be sure you have enough free space on the sd card.
Inviato dal mio Optimus 2X usando Tapatalk

In my case I think it was because I was not using a version of recovery mod that was designed for the Optimus 2X. I also used the internal version, I'm not sure if that made any difference.

Ancalagon_ZA said:
In my case I think it was because I was not using a version of recovery mod that was designed for the Optimus 2X. I also used the internal version, I'm not sure if that made any difference.
Click to expand...
Click to collapse
The recoveries from ROM Manager are designed for the O2X, and the 'official' builds. Mine are built from the same source but with a couple of minor changes... one of which is to allow EXT4 data partitions to be backed up.
Using internal or external version wouldn't have made any difference, that just lets you pick where you want your backups to be saved.

Wing_Zero85 said:
I've the same problem.
But upgranding to CWM 4.0.1.4 doesn't helped me :/
If I've installed an ext4 rom, CWM are not able to do a nandroid backup...
With an ext3 rom, no problem.
You can make a nandroid backup with, for example, slick2x-F rom???
Click to expand...
Click to collapse
Yes, all Rusty's 4.0.x.x works perfectly with ext4 ROMs, I used Slick 2X - F and now Slick 2x G (also in ext4), and backups are not a problem.

Actually 4.0.1.0 External might not work on EXT4

Rusty! said:
The recoveries from ROM Manager are designed for the O2X, and the 'official' builds. Mine are built from the same source but with a couple of minor changes... one of which is to allow EXT4 data partitions to be backed up.
Using internal or external version wouldn't have made any difference, that just lets you pick where you want your backups to be saved.
Click to expand...
Click to collapse
with 4.0.1.4 I can't either mount /data partition with slick-F rom :/

Interesting, 'cos someone above you can. Wonder what would make yours different.

Rusty! said:
Interesting, 'cos someone above you can. Wonder what would make yours different.
Click to expand...
Click to collapse
I'm wonderering the same.
I'm thinking to make a video of that :/
trying to install the external version, also if shouldn't be difference from internal.
I appreciate really much your help.
A last question:
peewster said me to "repartition everything" to make it work, what does it mean? How can i do that?

Wing_Zero85 said:
I'm wonderering the same.
I'm thinking to make a video of that :/
trying to install the external version, also if shouldn't be difference from internal.
I appreciate really much your help.
A last question:
peewster said me to "repartition everything" to make it work, what does it mean? How can i do that?
Click to expand...
Click to collapse
Yes! Now it works!!
Don't really know why, maybe first with internal version i've messed up something...now the external version it is working good!

Hmmm, that could just be another **** up on my part
Will look into it later and make sure I actually made the internal one work on EXT4.

But the internal 4.0.1.4 works fine for me! External 4.0.0.9 from rom manager did not. Also ext4.
If I restore an ext3 rom over an ext4 rom, what happens? Does it reformat the partition? Just wondering because I'm toying with the idea of a sort-of dual boot setup, where I change from a modaco type rom to a CM7 rom depending on need.

You need to convert back to EXT3 to do that, very easy to do so, there is a CWM script for it (wipes the phone though).
Or you could use the universal converter zip to convert CM7 to EXT4 instead.

I might investigate it, my CM7 is on ext4 right now, so my only problem would be that it is the only rom that uses ext4, everything else is on ext3.
But probably not really worth doing for me, since I would only gain HDMI mirroring. I dont really use A2DP and never use FM radio. HDMI mirroring does sound useful for an upcoming holiday though.

[RECOVERY] TWRP 2.6.3.0 for gt-P311X

With the help of Dees_Troy, helicopter88, MrHyde03 and the various other guides & great folks out there, I compiled TWRP 2.6.3.0 for the gt-p3113. This is for the US-version wi-fi with the IR port, but I'm told it may also work for the wifi-only (3110) version as well.
Files are here for the time being: one .img for a straight dd within an adb shell and the other (.md5) is ODIN-flashable.
https://www.dropbox.com/sh/my09xxmhwo8bcy1/zT80nlWBOj?m
There's a recovery-flashable .zip file there as well (thanks webdroidmt!)
I've also included the stock recovery image from Samsung's 4.2.2 release if you would like to flash back for some reason.
Standard disclaimers apply: I'm not responsible if this bricks your device or causes harm in any way.
Other than that, enjoy, test and let me know your experience!
Changelog from TWRP:
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
Old thread & discussion here:
http://forum.xda-developers.com/showthread.php?t=2168845

Re: TWRP 2.4.4.0 for gt-P3113
Thank you very much. I will test it. Right after nandroid.
Edit: internal SD appears blank when trying to install.
Sent from my GT-P3110 using xda app-developers app

Working great for me. Backed up and flashed with it. Not a single problem yet. :good:

Joe, good to see your thread in dev. I always use ext SD for both flashing zips, as well as backup/restore. However, just checked internal SD and as mentioned above, it comes up empty. It won't find any folders with zips or TWRP backups.
Aside from that and the clock continuously being 1 hour off for EST, it's working great for me. Have installed 4 or 5 different zips and have done 2 backups and restores.
Thanks,
Mike T

Glad you got it goin bud. Enjoy!

your internal SD card is located at /DATA/MEDIA within TWRP for the 3113. We talked about this in the other thread, but here's the bad part...If you WIPE DATA/FACTORY RESET it WIPES your internal card. So if you're a purely external SD guy your good to go but if you have any media data internally, say goodnight.

I use TWRP on other devices and they leave /data/media alone when doing a factory reset. TF101 and Galaxy Nexus.

It's located at /data/media for just about all android I believe, but it's never wiped with a wipe data/factory reset. Unless TWRP was not properly configured, you'll be alright.

who's brave enough to test it? I'm about 5 hours away from being able to myself but I switched back to CWR after reading that in the other thread. Problem is, you have to BU to computer because a nandroid wouldn't bring back the data if it in fact does get wiped. I only doubt this because TWRP does not locate the Touchpad or Skyrocket media data in /data/media. I just don't want to F up my daughter's TAB!

The build as it sits is certainly geared toward someone using their tablet with an external SD card. Having shot myself in the foot so many times in the past, I've just made a habit of backing stuff up there.
I've nuked encryption and gone back to stock and will be testing from that angle.

PS - not sure if it matters but I'm running CM10.1 nightlies. Oh and CMUPDATER doesn't work with this TWRP, it just boots to recovery instead of running the install script. I'm guessing until you can install this straight from GOO it might be a little undercooked.

That's an understatement....
I can't really figure out where the best location for internal storage would be on 10.1. The TWRP guys suggested /data/media, which is what it's currently set to, but that doesn't seem to be right. The fstab supplied on the CM git is not current with the times either.
I'll keep playing around. Any suggestions are welcome.

Joe, was just playing around with the TWRP v2.3.2.3 that forum member aidfarh compiled for P31xx and it allows installing zips and backup/restore from both internal and external SD card. Also, if you do a factory reset, it does not wipe the files on the internal SD card.
What I noticed, is that when performing the factory reset, it says it's wiping data but NOT wiping data/media. Any ideas if something has changed in TWRP source from 2.3.x.x to 2.4.xx? Thanks again for your efforts on this.
EDIT: We must have been posting at the same time. Would it be of any help to "take a look inside" the 2.3 version I mentioned above from aidfarh? I believe the 2.3.x.x versions were the first optimized for 4.2/CM 10.1.
Mike T

That would be ideal, but those settings come from the build environment (BoardConfig.mk, mostly), and is unique to the device. The trick is to pull those files from the CM repo and build against that. You also need to tweak the fstab somewhat, which differs within the GTab2 line.
Essentially, you sync and build a working CM for your device, then replace the built-in recovery with the TWRP repo. Then, it's a matter of tweaking the settings for the device so the recovery builds with the proper partition mappings, etc. When CM10.1 moved to multi-user, the internal sdcard was relocated to /data/media (or something), which suggests that TWRP should be smart enough to wipe all but that location.

I'm trying Joe, thought it could be helpful. I wish I had a better skill level on this stuff. Fortunately for me, I only need external SD card capability but I'm sure you'd like to get it right.
EDITING for your edit: Yeah, in the 2.3.2.3 build it seems that TWRP is acting as it should. Hopefully, you can get it figured out. Thanks. Btw, thanks for the explanation.
Mike T

Original post updated - several changes & new 2.4.4.0 posted to the DropBox share = includes .img, odin .tar.md5 and recovery-flashable .zip. Preserves /data/media in wipe and can mount/backup internal or external sdcard.

Works great Joe. Was able to install zips from internal/external, also able to backup/restore from both internal/external. Did a factory wipe and internal sd card data was preserved. Those functions are now working as they should.
Thanks for sticking with it, it's appreciated. I also found a theme that aside from one minor graphics glitch, looks and works great. It's the Eyecandy theme from XDA member Pimpmaneaton that he made for the Kindle Fire. The small graphic glitch is with the internal/external radio buttons, there's a slight discoloration on the button not selected. Not a deal breaker for me.
Mike T

This new built work great. I prefer TWRP than CWM, it's much easier to use plus I can move backup back and forth to my computer to save space.

You're the man, thanks for all the hard work.

Re: TWRP 2.4.4.0 for gt-P3113
Flashing meow. Its nice having the same recovery and ROM on two different devices.

Invisilek 3.4 variant 4.4.2 with 3.4 kernal thread closed?? and question

I intended to ask a question in the 3.4 variant thread, but this morning its thread closed? Any reason for this?
I was going to ask a slightly off-topic question, I am using the cwm_selinux_6.0.5.4_datamedia recovery and can not see the ext_sd partition with the 'rest' of my free space. I like to do my backups into that space. Is there a way I can manually mount the ext_sd space from inside the recovery so I can backup there? I can see that space form inside of CM, but, can't do a backup that cwm will be able to find.

jaltman said:
I intended to ask a question in the 3.4 variant thread, but this morning its thread closed? Any reason for this?
I was going to ask a slightly off-topic question, I am using the cwm_selinux_6.0.5.4_datamedia recovery and can not see the ext_sd partition with the 'rest' of my free space. I like to do my backups into that space. Is there a way I can manually mount the ext_sd space from inside the recovery so I can backup there? I can see that space form inside of CM, but, can't do a backup that cwm will be able to find.
Click to expand...
Click to collapse
Indeed it is strange a thread would be closed without any final posting from the OP or a forum mod, and even more strange since nightlies for the ROM continue to be generated.
Could be the devs wish to focus the user community testing the 3.01 kernel version, so it can becomes stable, before putting resources into supporting 3.4 kernel build?.
Regards to your issue take a look at Milaq's post in his CM11 ROM thread (3.01 kernel)
http://forum.xda-developers.com/showpost.php?p=49216229&postcount=512
You might have to mount /data in your recovery and then look for /data/media/0

The said thread was probably closed by its OP.

jaltman said:
I intended to ask a question in the 3.4 variant thread, but this morning its thread closed? Any reason for this?
I was going to ask a slightly off-topic question, I am using the cwm_selinux_6.0.5.4_datamedia recovery and can not see the ext_sd partition with the 'rest' of my free space. I like to do my backups into that space. Is there a way I can manually mount the ext_sd space from inside the recovery so I can backup there? I can see that space form inside of CM, but, can't do a backup that cwm will be able to find.
Click to expand...
Click to collapse
Flintman is working on a recovery that mounts the partitions. It's in his Evervolv rom thread. Milaq said he doesn't think it's needed anymore.... Just sit tight and they will have a recovery that does.

Thanks. I look forward to it. I liked being able to backup into that partition as I am less concerned about maintaining the free space in webos's side of things. While I occasionally bop over there, its rare.

question
can I flash unofficial milaq cm11 rom via invisiblek's recovery? http://invisiblek.org/tenderloin/

ennu said:
can I flash unofficial milaq cm11 rom via invisiblek's recovery? http://invisiblek.org/tenderloin/
Click to expand...
Click to collapse
Yes

Invisiblek's CM11 ROM (3.4 kernel) thread is once again open.
http://forum.xda-developers.com/showthread.php?t=2592909

ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies [3.0 kernel]

I am testing Milaq's CM-11 KitKat rom on one of my 5 Touchpads. I love the new rom but since I am not allowed to comment on the developers thread I am reporting a bug that has not been discussed on the development thread. If an Mpeg4 video file is placed in a file the gallery app will crash the operating system and cause a re-boot. If this is not the correct forum please direct me to where I should report bugs. I have already read the development tread from beginning to end.
John

post correct
johnbelloh said:
I am testing Milaq's CM-11 KitKat rom on one of my 5 Touchpads. I love the new rom but since I am not allowed to comment on the developers thread I am reporting a bug that has not been discussed on the development thread. If an Mpeg4 video file is placed in a file the gallery app will crash the operating system and cause a re-boot. If this is not the correct forum please direct me to where I should report bugs. I have already read the development tread from beginning to end.
John
Click to expand...
Click to collapse
you can post in correct forum after 10 posts in general T.

same post count issue here.
i am running 20140112 and have random reboots and google play crashes on each use.

J_E_F_F said:
same post count issue here.
i am running 20140112 and have random reboots and google play crashes on each use.
Click to expand...
Click to collapse
I just flashed 20140113 and can report 2 problems. The mp4 video file just being located on the system still crashes gallery even if it is not selected. Google+ dousnot work either. It displays a message to reinstall it. There is no option to delete it. Play Store has been working OK for me since I flashed Milaq's 1208 gapps. I tried using newer gapps but they must be installed on top of the ROM or they cause boot loops. Try using the 1208 gapps and Google Play should work. I also tried using invisiblek's ROM but found it to be unstable.

I am using 1208 gapps, but they were installed with the previous ROM, not over top of the newest nightly. I'll give that a shot when I get home tonight, thanks for the tip.

same issue, 20140113 nightly and 1208 kk gapps over top. Google Play still crashes for me.

J_E_F_F said:
same issue, 20140113 nightly and 1208 kk gapps over top. Google Play still crashes for me.
Click to expand...
Click to collapse
check if you have /cache partition mounted

I'm not exactly sure how to check if /cache is mounted, but in settings>storage, I see cached data 22.29mb, does that count?
using webOS tailor, the cache partition is set at 200mb

I downloaded "partition table" from the play store which took a few tries since the play store crashes for me on this rom.
yes /cache is mounted and active

Testing Milaq's CM-11
J_E_F_F said:
I'm not exactly sure how to check if /cache is mounted, but in settings>storage, I see cached data 22.29mb, does that count?
using webOS tailor, the cache partition is set at 200mb
Click to expand...
Click to collapse
While waiting for the next ROM I tried using different GAPPS with this ROM. If I use a GAPPS package specific to 4.4.2 things like GOOGLE+ start to work but create other problems like boot loops and crashes. I have gone back to the 1208 gapps but I think this rom needs an update of the gapps to android 4.4.2. specific to the touchpad. At any rate it appears one must do a clean install when changing gapps by doing a complete reset. just make sure you keep your nandroid backups or you may have to do an acme uninstall followed by a new install since the external (WEBOS) is not accessible from the new datamedia CWM. I used Tailor in Webos to leave just enough space for webos and allocated most of my memory to Android storage. I'm waiting to see if a future ROM will fix the reboot from MP4 video file being installed before I can use this ROM as a daily driver. Thanks to Milaq and supporting developers my entire family are now equipped with HP Touchpads.

Testing cm-11 20140117
johnbelloh said:
While waiting for the next ROM I tried using different GAPPS with this ROM. If I use a GAPPS package specific to 4.4.2 things like GOOGLE+ start to work but create other problems like boot loops and crashes. I have gone back to the 1208 gapps but I think this rom needs an update of the gapps to android 4.4.2. specific to the touchpad. At any rate it appears one must do a clean install when changing gapps by doing a complete reset. just make sure you keep your nandroid backups or you may have to do an acme uninstall followed by a new install since the external (WEBOS) is not accessible from the new datamedia CWM. I used Tailor in Webos to leave just enough space for webos and allocated most of my memory to Android storage. I'm waiting to see if a future ROM will fix the reboot from MP4 video file being installed before I can use this ROM as a daily driver. Thanks to Milaq and supporting developers my entire family are now equipped with HP Touchpads.
Click to expand...
Click to collapse
The mp4 video gallery crash problem is resolved in 20140117. Google+ still not working. This ROM is getting close to daily driver status.

After 2 years working with the Touchpad and coming from early versions of CyanogenMod I thought I would install Milaqs CM11. As I can't post in the developer forum I thought I would share my experience with those that might find it useful..... Simply flashing a CM11 4.4 ROM (clean or dirty flash) means you end up with a messed up storage sd card partition layout and actually a system which isn't really usable in the long run, so forget it. However, with patience there is a way around this though, as Milaq rightly states in his original post and that is to re-partition the drive (sd card) so the maximum amount is given over to data as opposed to media storage, this means that when the 4.4 rom is flashed it sees the whole of the sd card and treats it as a single drive which is the way its all going using new datamedia builds. This however is not straightforward and takes some thinking about, but it can be done and is well worth it in the long run. I suggest that RolandDeschain79 really needs to update this and other posts as it is misleading to let people think they can simply flash 4.4 - CM11 following his guides - as you really should not, especially as the newer kernels are being used. The video tutorials created by Roland are great and have helped the TP community a lot but I would like to suggest that a whole new video is created (the existing one is good but could be improved tremendously, having done it myself) to fully explain re-partitioning with 'Tailor' (this is the only way to do it forget all other ways using Apes flashable fixes and the like as they do not work properly). Sideloading the ROM and Gapps using ADB from recovery using the feature in CWM 6.0.4.6, is really the only proper way to install CM11 KitKat on the Touchpad and at same time make use of all of its internal storage capability in one simple easy to navigate installation, without silly emulated card space etc. I will help others where I can as I just spent a whole day figuring it all out and now have a 32GB Touchpad that runs Milaq's CM11 the way it should be, its fantastic and well worth the effort.

Flashed 20140118
frostysnowman said:
After 2 years working with the Touchpad and coming from early versions of CyanogenMod I thought I would install Milaqs CM11. As I can't post in the developer forum I thought I would share my experience with those that might find it useful..... Simply flashing a CM11 4.4 ROM (clean or dirty flash) means you end up with a messed up storage sd card partition layout and actually a system which isn't really usable in the long run, so forget it. However, with patience there is a way around this though, as Milaq rightly states in his original post and that is to re-partition the drive (sd card) so the maximum amount is given over to data as opposed to media storage, this means that when the 4.4 rom is flashed it sees the whole of the sd card and treats it as a single drive which is the way its all going using new datamedia builds. This however is not straightforward and takes some thinking about, but it can be done and is well worth it in the long run. I suggest that RolandDeschain79 really needs to update this and other posts as it is misleading to let people think they can simply flash 4.4 - CM11 following his guides - as you really should not, especially as the newer kernels are being used. The video tutorials created by Roland are great and have helped the TP community a lot but I would like to suggest that a whole new video is created (the existing one is good but could be improved tremendously, having done it myself) to fully explain re-partitioning with 'Tailor' (this is the only way to do it forget all other ways using Apes flashable fixes and the like as they do not work properly). Sideloading the ROM and Gapps using ADB from recovery using the feature in CWM 6.0.4.6, is really the only proper way to install CM11 KitKat on the Touchpad and at same time make use of all of its internal storage capability in one simple easy to navigate installation, without silly emulated card space etc. I will help others where I can as I just spent a whole day figuring it all out and now have a 32GB Touchpad that runs Milaq's CM11 the way it should be, its fantastic and well worth the effort.
Click to expand...
Click to collapse
I flashed 20140118 tonight. The only thing I can find that does not work is Google+. It still displays an error message to reinstall the Google+ app. Since it is part of the 1208 gapps and not a download I don't see a way to delete it. Is anyone else experienceing the same issue?

frostysnowman said:
...now have a 32GB Touchpad that runs Milaq's CM11 the way it should be,...
Click to expand...
Click to collapse
Just wondering what is meant by "the way it should be" ?

woodytrain said:
Just wondering what is meant by "the way it should be" ?
Click to expand...
Click to collapse
Its all installed on a single partition making most efficient use of the layout and storage capability. No need to move apps onto sd card and all that nonsense . It is very fast and makes cm10 seem so yesterday

frostysnowman, do you have a good tutorial available detailing how to properly sideload the ROM?

sdcard not mounted - milaq's CM11 - 1/18
I have been using milaq's cm11 nightlies, after first week of Jan14 my sdcard1 (another partition on TP) stop showing on file explorer.
However, when I installed invisiblek nightlie (ofcos with 3.4 kernel cwm), start showing the sdcard1 partition.
based on my analysis milaq's 'init.tenderloin.rc' file do not have entries to mount the sdcard1.
Appreciate any kind of help.

[email protected] said:
I have been using milaq's cm11 nightlies, after first week of Jan14 my sdcard1 (another partition on TP) stop showing on file explorer.
However, when I installed invisiblek nightlie (ofcos with 3.4 kernel cwm), start showing the sdcard1 partition.
based on my analysis milaq's 'init.tenderloin.rc' file do not have entries to mount the sdcard1.
Appreciate any kind of help.
Click to expand...
Click to collapse
If you have any backups saved you can restore one that had access to both sd0 and sd1. Use file manager to move the files you need from sd1 to sd0. Restore the new ROM and you will have your files on sd0. When you are ready to stay with cm-11 go back to webos and use Tailor to shrink the external SD to just enough to support your webos and allocate the remainder of memory to Android storage. With the new data media cwm just use sd0 for everything.

johnbelloh said:
If you have any backups saved you can restore one that had access to both sd0 and sd1. Use file manager to move the files you need from sd1 to sd0. Restore the new ROM and you will have your files on sd0. When you are ready to stay with cm-11 go back to webos and use Tailor to shrink the external SD to just enough to support your webos and allocate the remainder of memory to Android storage. With the new data media cwm just use sd0 for everything.
Click to expand...
Click to collapse
Thanks John!
How much space I should left on sd1 for WebOS?
Also, I am trying to settled myself with invisiblek's rom, where my another partition (sdcard1) shows mounted (& accessible)
In terms of help, to be specific, how can I mount the another partition (sdcard1), once the rom is running. I mean is there way via TerminalEmulation, etc?
Another purpose about the post is to drag milaq's attention for the point/matter.
Again thanks for your help.:good:

ashman said:
Thanks John!
How much space I should left on sd1 for WebOS?
Also, I am trying to settled myself with invisiblek's rom, where my another partition (sdcard1) shows mounted (& accessible)
In terms of help, to be specific, how can I mount the another partition (sdcard1), once the rom is running. I mean is there way via TerminalEmulation, etc?
Another purpose about the post is to drag milaq's attention for the point/matter.
Again thanks for your help.:good:
Click to expand...
Click to collapse
Ashman - Once you commit to Milaq's cm-11 rom there is no way to access SD1 from Android since he does not mount it. The amount of space you allocate to the external sd card in Tailor for webos would depend on the amount of apps and files you want to save for webos. I left a back door on my Touchpad by leaving 1 old backup in place that supports both sd1 and sd0. This allows me to place a zip file on sd1 with webos and move it to sd0 with file manager under the old version restored when needed. At any rate I understand Milaq's logic that once we move over to a data media recovery every thing Android can use sd0 as one big chunk of memory.