[ROM][WIP][4.4.2] CyanogenMod 11 KitKat for Optimus S/V

[brotherswing]

Yeah, what ^ he said!

VM670 on 4.4.2? Yes, indeed.

 

[smittss]

If you unzip the gapps you can see which files are in which folders, then you should check those directories on your phone to see if the files are there. If so, then you should check if the permissions on the files and directories are right. You can compare to a working install or look at the updater script in the zip file to see what the permissions are supposed to be. You could use File Manager (after enabling root access in settings) but adb is much handier for this sort of thing.

Running out of time for the evening, but it looks like from a quick spot check, all of the files are there when I look in adb shell (and a spot check of the permissions looks correct). However, looking in the zip, I don't see an APK that looks like the play store to me.

Here are the apks within the file:
system/app/GoogleCalendarSyncAdapter.apk
system/app/GoogleContactsSyncAdapter.apk
system/priv-app/GoogleBackupTransport.apk
system/priv-app/GoogleLoginService.apk
system/priv-app/GoogleServicesFramework.apk
system/priv-app/Phonesky.apk
system/priv-app/SetupWizard.apk

 

[thewraith420]

Its phonesky.apk I'd check the size on the one in the zip vs the one in app-priv

Edit: how full is your system partition?

Sent from my XT907 using Tapatalk

 

[yaconsult]

No partitioning in the recovery unfortunately. For the sd version make or shrink your fat32 partition so there's 1.5 gb empty space after it then make the first partition 1024 mb second partition 256 mb third partition 256 mb or thereabouts, all primary partitions. Make them as ext4 partitions then format them. I used gparted on linux, not sure if there's a windows version but there's a version where you make a bootable cdrom and boot into it so you don't need to be running linux to use it. Very useful program actually. The regular version doesn't require any sd-ext partitions unless you want to experiment with getting int2ext or something similar going.

Thanks for the partitioning details. I usually partition on linux. For those on windows, this free tool works well for partitioning: Best Free Partition Manager Freeware and free partition magic for Windows 7, Windows 8, Windows Vista and Windows XP 32 bit & 64 bit. MiniTool Free Partition Manager Software Home Edition.

See following posts concerning partitions.

Partitions to be created and formatted before ROM install:

1. fat32 - rest of space not used below - primary type
2. ext4 - 1 GB - primary type
3. ext4 - 256 MB - primary type
4. ext4 - 256 MB - primary type

Hmmm, having trouble with the recovery. After flashing cwm SD, it shows the cwm logo and version but then it boots into the ROM instead of stopping in cwm. This happens both when I use adb to reboot recovery or with home-volume down-power. BTW, is that the correct combo for the virgin phone or are the keys swapped in cwm too? I still have a bootable ROM so I can reflash the recovery if I need to. The non-SD version of the recovery seemed to work as expected.

I've learned my lesson the hard way - I won't be flashing any ROMs until the recovery works as expected! LOL

 

[smittss]

Its phonesky.apk I'd check the size on the one in the zip vs the one in app-priv

Edit: how full is your system partition?

That's it... System partition is full.

So my system parition is 160MB. After the install, I have about 10MB remaining.. (should I just go buy a class 10 card?)

I deleted everything from /system in adb shell, reinstalled the rom, which left 10MB. I then rebooted into recovery and tried installing the gapps, which seemed to get a bit further, think it said install completed, but when I booted, still no play store, and the system partition was full.

 

[smittss]

I think I got it working... I went into the adb shell, deleted some of the /app apks (calculator, calendar, etc) and the bootanimation to save some extra space. After install, everything appears to be working correctly, and I have 10MB left on my system partition

Play Store is there and link2sd installed correctly.

Thanks for the help. If you want me to provide a listing of what I deleted, I could probably come up with it.

 

[skinbark]

I think I got it working... I went into the adb shell, deleted some of the /app apks (calculator, calendar, etc) and the bootanimation to save some extra space. After install, everything appears to be working correctly, and I have 10MB left on my system partition

Play Store is there and link2sd installed correctly.

Thanks for the help. If you want me to provide a listing of what I deleted, I could probably come up with it.

I'm curious what the size of your /system partition is. Could you run the df command from adb and post the output? I'm wondering if different phone versions have different partition sizes. Glad you got it working by the way. 10 mb is ok for system.

 

[anon(319503)]

123

 

[bigsupersquid]

I'm curious what the size of your /system partition is. Could you run the df command from adb and post the output? I'm wondering if different phone versions have different partition sizes. Glad you got it working by the way. 10 mb is ok for system.

the os has more room in system than ov if i recall.
164.5 M.

 

[brotherswing]

I think I made a few mistakes during partitioning. My system partition is 1GB. Not that that's bad, just not what I had intended. That being the case, I'm thinking that my data partition is MUCH smaller than intended and therefore responsible for my issues. I'm going to repartition my card and reinstall later today. I'll keep you posted...

VM670 on 4.4.2? Yes, indeed.

 

[skinbark]

I think I made a few mistakes during partitioning. My system partition is 1GB. Not that that's bad, just not what I had intended. That being the case, I'm thinking that my data partition is MUCH smaller than intended and therefore responsible for my issues. I'm going to repartition my card and reinstall later today. I'll keep you posted...

VM670 on 4.4.2? Yes, indeed.

That might be my fault, I got the ordering of the partitions mixed up in my instructions when I first posted them, sorry. It's data, then system, then cache.

- - - Updated - - -

the os has more room in system than ov if i recall.
164.5 M.

I think 164.5 is what my ov has.

 

[skinbark]

I'm having the same problem as Yaconsult. I've partitioned my SD card in the same way, all partitions set as primary, try to start OS2SD CWM recovery, logo displays for a second or two, then it just boots to android.

edit: So I partition my card the same as Yaconsult's, MiniTools Partition wizard shows each Ext4 partition is set as primary. Insert card and try to boot into recovery, recovery auto closes then boots to android. When I take out my card and check it in with MiniTools it shows one of my Ext4 Partitions is completely full and partition type set as (Other).

edit 2: CWM SD boots up if I only have 2 Ext4 partitions. I'm going to try booting with 4 Ext4 partitions and see what happens.
small edit: It says "No free MBR slots" when trying to make 4 Ext4 partitions.

edit 3: Back to 3 Ext4 partitions. Recovery boots if no SD card inserted. Insert SD card while in recovery, recovery reboots to android. I boot into recovery with no SD card, go to Mounts and Storage Menu, insert SD card, recovery doesn't reboot and I'm able to mount SD card, go back to main menu, recovery boots to android.
small edit: It's only in the main menu OS2SD will reboot when SD card is inserted. If I go into any sub menu then insert card recovery is normal and can explore SD card.

Sorry if it sounds obvious, but you need exactly 4 partitions on the card:
1) fat32 - /storage/sdcard0<br>
2) ext4 /data<br>
3) ext4 /system<br>
4) ext4 /cache<br>
They should all be formatted before use.

 

[anon(319503)]

123

 

[bigsupersquid]

I think 164.5 is what my ov has.

I don't have a LS670 firmware flashed on anything right now to check, but usually things made for the S fit fine on my V.
And, in the normal skinbark recovery, I find it odd people aren't getting errors when flashing gapps into overful system partition... too much stuff to fit always gives me 'some symlinks failed' errors.

 

[bigsupersquid]

also, if you're interested, I might be able to make a fakeflash sd-recovery to retain the regular one in NAND... it's possible because they're the same CWM version and the files will copy over nicely.

 

[skinbark]

also, if you're interested, I might be able to make a fakeflash sd-recovery to retain the regular one in NAND... it's possible because they're the same CWM version and the files will copy over nicely.

?? fakeflash recovery

 

[skinbark]

Yes i have 4 partitions on my SD card. My card is formatted as follows:

|---------------------------29Gb Fat32----------------------------| |----1Gb Ext4----| |-256Mb Ext4-| |-256Mb Ext4-|

All are set as primary. When I have my card inserted then try to boot into recovery, the CWM logo displays for a second or two then boots to android. After this, when I examine my card with MiniTools Partition Wizard, my card show as this:

|---------------------------29Gb Fat32----------------------------| |----1Gb Ext4----| |-256Mb Ext4-| |-256Mb (Other)-|

CWM SD will not boot if I have the 3 Ext4 Partitions. 1 or 2 yes, 3 no. And even then, it only reboots when at the main menu of CWM SD if i have my card inserted. If i go into any sub menu then insert my card with the 3 Ext4 partitions it works fine until i return to the main menu.

Switch back to the regular recovery and try installing os2sd. It should work you just won't be able to mount or format the sd-ext partitions in recovery. I'm going to try to get this figured out but you can go ahead with your install if you want. Use the os2sd gapps as well.

 

[bigsupersquid]

?? fakeflash recovery

haven't seen one in a while, but it's a zip installer that overwrites / (root dir) and its subdirectories and then kills recovery, which respawns recovery from the ramdisk. lets you run a different model without actually flashing it. but I never could get radically different versions to work.

Switch back to the regular recovery and try installing os2sd. It should work you just won't be able to mount or format the sd-ext partitions in recovery. I'm going to try to get this figured out but you can go ahead with your install if you want. Use the os2sd gapps as well.

I posted this earlier before you made the sd recovery.
cm-11-wipe_mmcp2-p4.zip
so at least you can 'format' them. it's actually a

rm -rf ./*
rm -rf ./.*

for each partition instead of mke2fs.
//edit: skinbark pointed out that this formats internal partitions too. Beware of that.

 

[skinbark]

haven't seen one in a while, but it's a zip installer that overwrites / (root dir) and its subdirectories and then kills recovery, which respawns recovery from the ramdisk. lets you run a different model without actually flashing it. but I never could get radically different versions to work.

I posted this earlier before you made the sd recovery.
cm-11-wipe_mmcp2-p4.zip
so at least you can 'format' them. it's actually a

rm -rf ./*
rm -rf ./.*

for each partition instead of mke2fs.

I suppose I should take down the sd recovery from post #2 since it's causing hassles. I'd like to figure out what's going on though. Strange that it works for some but not others. Variables: different partitioning software, different sd cards, different phones. I guess using the wipe script is less hassle anyway though. It might be better to have individual wipe zips for each partition, also zips to mount each partition from recovery. I can make those.

 

[skinbark]

I used the regular CWM to install the os2sd rom on my spare phone. When I rebooted the system booted up to the desktop but no icons were present and the button on the bottom didn't take me to the app drawer, it just kind of darkened the screen. All there was was a blank desktop. I rebooted and the second time it came up everything was normal. I just wanted to mention this in case it happens to others.