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

[thekraven]

We could maybe hack the cwm source to make it work. The best solution is probably a 'smart' cwm that can handle 2 installations on one phone.
Or a bootloader on the recovery partition that lets you pick either the standard recovery or a recovery that you load off the sd card.

Try the philz cwm. It has multi zip and ors script capability.

 

[yaconsult]

I tried this tonight on my spare phone using the latest versions of files from the beginning of the thread. Flashed the non-sd version in the first post, and cwm and cm11 and everything seemed to work as expected including wifi and play store. That phone is not activated so I could not test calling.

I then tried flashing the sd version of cwm but when I boot it I only get a backlit black screen. I have all the partitions created and formatted as described in the second post using my linux system. I still have the rom from the first post installed so I tried flashing the recovery a second time with the same result. md5 verified - the download was good. flash_image completed successfully.

The phone I am using for testing is an VM670ZV5. Let me know if I can provide any further info or testing. So for my phone, the cwm works fine but the cwm-sd does not. The cm11 works as far as I was able to test it but I am unable to install cm11-sd because of the issues with cwm-sd.

p.s. With the help of the wonderful folks here, I was able to find and record the AAA codes and other important information for my phones in case I ever need them for a recovery.

 

[bigsupersquid]

Maybe I misread the first time.
Did you try the fakeflash sd-recovery?
if so, does adb connect when it's blackscreened?

if you tried the regular sd-cwm recovery, instead, first flash the skinbark non-sd cwm.
then try the fakeflash (info post ... link)

the generic testing steps I'd take for a rom flash that blackscreened on boot:
at any failure point stop and report.
using adb shell in fakeflash cwm first (you have to adb kill-server first if adb was connected to the regular cwm)

adb shell mount should return /dev/block/mmcblk0p4 for what /cache is on
recovery menu: format /system, factory reset, and mount /system
adb shell ls /system should return nothing or lost and found only
recovery: install rom zip, mount /system
adb shell ls /system should return a regular-looking batch of sub directories
recovery: reboot system
if cm11 doesn't start
at the black screen: after five or ten seconds,
adb shell should either complain about /system/bin/sh
or return device not connected, or another device message like device offline, or a security device dialog message, or a shell
if it gets to a shell you can exit and adb logcat > log.txt
then pastebin the log.

I've had installs fail to write to /system and adb connects but fails to find a shell.. reinstall sometimes works.
I had no issues with either the flashed or fakeflash recoveries myself, so can't evaluate too well.
thanks for the data!

 

[brotherswing]

Speaking of test data, I'm still rolling the OS2SD install I've had for several days now. Kids haven't given me enough time to redo the installation with correct partition sizes and fakeflash. The only quirk to report that hasn't been discussed is the occasional lock up (about five times since initial installation, typically when exiting Dolphin) and about three random reboots (nothing consistent, never while it's in use,) VM670, ZV9

VM670 on 4.4.2? Yes, indeed.

 

[bigsupersquid]

Speaking of test data, I'm still rolling the OS2SD install I've had for several days now. Kids haven't given me enough time to redo the installation with correct partition sizes and fakeflash. The only quirk to report that hasn't been discussed is the occasional lock up (about five times since initial installation, typically when exiting Dolphin) and about three random reboots (nothing consistent, never while it's in use,) VM670, ZV9

VM670 on 4.4.2? Yes, indeed.

if Dolphin kills it, maybe a running logcat while opening/exiting Dolphin until it freezes might say something.
Also watching adb shell cat /proc/kmsg (adb shell 'cat /proc/kmsg > /sdcard/kmsg.txt' to save it) can produce useful data sometimes since the kernel often keeps chugging while Android is kablooey. Pressing keys yields kernel events if that part of the system isn't frozen up.

 

[brotherswing]

I'll see if I can get that for you, I didn't even think about kmsg from adb (rarely get to use the PC.)

VM670 on 4.4.2? Yes, indeed.

 

[bigsupersquid]

both work in terminal too (reading kmsg as su)
logcat > /sdcard/log.txt
or
cat /proc/kmsg > /sdcard/kmsg.txt

 

[bigsupersquid]

for recovery workarounds, maybe the aroma installer would work? It didn't look to natty to tweak into function for the thunderc.
probably would remove any need for fakeflash or cwm modifications.

 

[Shinkenred]

Okay...Play Store still won't work, and as a result, certain games won't work either (so far: Destinia, Zenonia 3). Phonesky.apk is now the Play Store app name? Lame...but I'll try extracting & sideloading it. (Odder still because I looked in the gapps for 4.3 & 4.2, they both have Phonesky as well, whereas the 4.1 SlimROM, ICS, & GB gapps all have it as Play Store. So why did Google make that change, I wonder?)

Another batch of oddity is that the old ability to move apps to the SD card is rather spotty at best. It typically won't do it (error message "Couldn't move app", no matter how much space you have on SD), but, after I'd installed Root Explorer & Titanium Backup, it would occasionally move the apps. BUT!! After a reboot OF ANY KIND, FOR ANY REASON, the apps that were moved would be GONE. As if they were never even installed. (Package installer treats them that way; but my Zenonia 2 says it was in there all along) This makes getting back my apps quite the pain in the nuts.

Oh...and while it's a better browser, I really can't advise installing Dolphin over the stock browser for this rom. It's a LOT bigger (almost 13MB just for the apk, whereas the stock one is about 2.5MB).

 

[yaconsult]

I figured out what I was doing wrong. Sigh, I was flashing the recovery zip file instead of extracting the .img first. That will teach me to do this stuff in the middle of the night!

I wonder how often this happens? We are used to flashing roms, gapps, button switches as zips but for the recovery, you need to extract the img file and flash it, not the zip. Unfortunately, flashing the zip into recovery "works" in that it is able to write the data into the recovery partition, but it won't boot recovery!

Just remember the golden rule to never flash both new recovery and new rom at the same time - make sure that the one you are NOT flashing is working first. Then you always have the other one available to recover from mistakes or problems. In my case, I could just keep booting the cm11 rom and use adb to fix the recovery problem.

I think I've got it all working properly now. Here are the filesystems I have:

Filesystem Size Used Free Blksize
/dev 207.4M 136.0K 207.3M 4096
/sys/fs/cgroup 207.4M 12.0K 207.4M 4096
/mnt/asec 207.4M 0.0K 207.4M 4096
/mnt/obb 207.4M 0.0K 207.4M 4096
/mnt/fuse 207.4M 0.0K 207.4M 4096
/system 356.1M 224.4M 131.7M 1024
/data 1.4G 120.6M 1.3G 4096
/cache 371.9M 10.1M 361.8M 1024
/mnt/media_rw/sdcard0 12.7G 202.2M 12.5G 8192
/storage/sdcard0 12.7G 202.2M 12.5G 8192​

Look at all that space! This is a great solution you guys have come up with!

I can confirm that the wifi password is forgotten on reboot. Also confirm problem with play store, although it's still called play store. I can go there and search for apps - I was using es file explorer as my test case. The play store seems to be hanging after clicking the install button. My phone is VM670ZV5.

 

[smittss]

Is there a common set of patches that everyone is using to build this that I am missing, or are you basically just building the CM11 source?

 

[skinbark]

I figured out what I was doing wrong. Sigh, I was flashing the recovery zip file instead of extracting the .img first. That will teach me to do this stuff in the middle of the night!

I wonder how often this happens? We are used to flashing roms, gapps, button switches as zips but for the recovery, you need to extract the img file and flash it, not the zip. Unfortunately, flashing the zip into recovery "works" in that it is able to write the data into the recovery partition, but it won't boot recovery!

Just remember the golden rule to never flash both new recovery and new rom at the same time - make sure that the one you are NOT flashing is working first. Then you always have the other one available to recover from mistakes or problems. In my case, I could just keep booting the cm11 rom and use adb to fix the recovery problem.

I think I've got it all working properly now. Here are the filesystems I have:

Filesystem Size Used Free Blksize
/dev 207.4M 136.0K 207.3M 4096
/sys/fs/cgroup 207.4M 12.0K 207.4M 4096
/mnt/asec 207.4M 0.0K 207.4M 4096
/mnt/obb 207.4M 0.0K 207.4M 4096
/mnt/fuse 207.4M 0.0K 207.4M 4096
/system 356.1M 224.4M 131.7M 1024
/data 1.4G 120.6M 1.3G 4096
/cache 371.9M 10.1M 361.8M 1024
/mnt/media_rw/sdcard0 12.7G 202.2M 12.5G 8192
/storage/sdcard0 12.7G 202.2M 12.5G 8192​

Look at all that space! This is a great solution you guys have come up with!

I can confirm that the wifi password is forgotten on reboot. Also confirm problem with play store, although it's still called play store. I can go there and search for apps - I was using es file explorer as my test case. The play store seems to be hanging after clicking the install button. My phone is VM670ZV5.

See post #326 for the solution to the wifi password problem. Also remember some issues will resolve after a few reboots.

 

[skinbark]

Is there a common set of patches that everyone is using to build this that I am missing, or are you basically just building the CM11 source?

Initialize your repo to the androidarmv6 android manifest. pm me if you want a copy of my local manifest. My github is skinbark, you could also use TheJBC for device folders. Use bigsupersquid's kernel. To make data work you need to use frameworks/opt/telephony from Team-Hydra. Feel free to pm me if you have questions or issues.

 

[yaconsult]

See post #326 for the solution to the wifi password problem. Also remember some issues will resolve after a few reboots.

That took care of it - thanks! And I've rebooted it a bunch of times to give it a chance to settle down.

I can confirm the bluetooth issue. The phone successfully lists my bluetooth device but does not complete pairing with it. Let me know if I can provide more testing or information. I know my way around the command line but haven't worked on android much.

I am able to install apps from the play store now and it's great to be able to install some apps that only work with android 4+.

 

[Shinkenred]

UPDATED: Extracted and sideloaded the "Phonesky.apk" version of the Play Store, now it works...nope, spoke too soon. It tries to start up, even brought up the TOS screen, but then it crashes. Games that wouldn't work due to reliance on a connection with it still won't work.

UPDATED: The old ability to move apps to the SD card is STILL spotty. It typically won't do it (error message "Couldn't move app", no matter how much space you have on SD), but, after I'd installed Root Explorer & Titanium Backup, it would occasionally move the apps. BUT!! After a reboot OF ANY KIND, FOR ANY REASON, the apps that were moved would be GONE. As if they were never even installed. (Package installer treats them that way) This makes getting back my apps quite the pain in the nuts.

 

[bigsupersquid]

UPDATED: Extracted and sideloaded the "Phonesky.apk" version of the Play Store, now it works...nope, spoke too soon. It tries to start up, even brought up the TOS screen, but then it crashes. Games that wouldn't work due to reliance on a connection with it still won't work.

UPDATED: The old ability to move apps to the SD card is STILL spotty. It typically won't do it (error message "Couldn't move app", no matter how much space you have on SD), but, after I'd installed Root Explorer & Titanium Backup, it would occasionally move the apps. BUT!! After a reboot OF ANY KIND, FOR ANY REASON, the apps that were moved would be GONE. As if they were never even installed. (Package installer treats them that way) This makes getting back my apps quite the pain in the nuts.

the OS2SD version has no sd-ext at all. Since android only sees four partitions, I couldn't think of any way to implement it properly. Needs a symlink to /data/sd-ext or something so CM doesn't spaz about it being missing entirely.
Dunno about issues with it on the regular cm11, which is of course what this thread is for.

 

[skinbark]

UPDATED: Extracted and sideloaded the "Phonesky.apk" version of the Play Store, now it works...nope, spoke too soon. It tries to start up, even brought up the TOS screen, but then it crashes. Games that wouldn't work due to reliance on a connection with it still won't work.

If you have a Sprint phone you have to trim the rom so you have enough space to make the Gapps fit. I didn't know at the time I uploaded the rom that Sprint phones have a smaller /system partition than Virgin phones. So what's working for us Virgin guys won't work for you guys. Just take a few apps out of /system and if you need them sideload them from the sd card. Then the Gapps will fit. Just make sure you still have a few megs of free space on /system after you install Gapps because you don't want /system totally full.

 

[brotherswing]

Or open the zip file on a pc and delete the unnecessary apks, then close it. That will (in theory) allow you to flash gapps. Not certain that would work for a Rom but when I was active making themes I did it all the time. Might need to resign the zip, again I'm not certain. Speaking of, I did notice there aren't a lot of themes for CM11 on mdpi devices like ours. Would there be any interest (or indeed any point) in my cooking up a few for this?

VM670 on 4.4.2? Yes, indeed.

 

[bigsupersquid]

moving this over here since it's a link-to-ext method

Came across this today:
https://github.com/SpazeDog/mounts2sd

it looks well-made, after.looking it over. i bet it'd work well.

 

[brotherswing]

I did play with it on my wife's a510c, and it worked brilliantly. I'd have no problem recommending it and since it is open source the code might be quite useful!

VM670 on 4.4.2? Yes, indeed.