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

[yaconsult]

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.

As a test, I plugged my sdcard into my linux system and found, as dman861 reported, that the last partition on the sdcard had a type of unknown. I reformatted it as ext4 on linux and now, the phone boots into cwm instead of just displaying the cwm screen and then continuing to boot the phone to android. I rechecked the sdcard on the linux system and the last partition remains properly formatted ext4.

I have not updated or changed anything since the last time I tried, so the only difference was the formatting of the last ext4 partition on a linux system instead of minitool partition manager on windows 7 x64 which may not able to create these four primary partitions properly. After all, according to windows, you are only supposed to have one primary partition on a disk - LOL.

I used gparted on linux, so using the live CD or live USB version of gparted.org might be the way to go if you are on windows.

My phone is the Virgin model.

 

[smittss]

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

I have an optimus S (I think). It returns 158.5MB from df -h for the /system partition, so that may be where some of the problem is.

 

[smittss]

It seems like for some reason, my wireless password isn't saved, and after every reboot, I need to reenter it to connect. I didn't think any of the APKs I deleted should be related. Anyone else having the same problem?

 

[skinbark]

It seems like for some reason, my wireless password isn't saved, and after every reboot, I need to reenter it to connect. I didn't think any of the APKs I deleted should be related. Anyone else having the same problem?

Yes that's happening to me too.

 

[skinbark]

Note on the wipe zip bigsupersquid uploaded - this zip formats data, system, and cache on both internal memory and sd card. Remove the lines in the updater script that refer to yaffs and MTD unless this is what you want. You can use the mount and format menu in the regular cwm to wipe internal partitions. I'm going to prepare individual scripts to format each sd-ext partition for more control.

 

[bigsupersquid]

Note on the wipe zip bigsupersquid uploaded - this zip formats data, system, and cache on both internal memory and sd card. Remove the lines in the updater script that refer to yaffs and MTD unless this is what you want. You can use the mount and format menu in the regular cwm to wipe internal partitions. I'm going to prepare individual scripts to format each sd-ext partition for more control.

I didn't intend to leave in the internal partition formats. good catch. I'll edit the post to reflect.

 

[thekraven]

I noticed this in your msm7x27-common Boardconfig. These values are for the P500, thunderc are different. The BOARD_KERNEL_BASE is the only one that mght need fixing, the others are just size parameters.

BOARD_KERNEL_BASE := 0x12800000

## Partition Sizes: Fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00440000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00600000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0xff00000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x0c780000

 

[brotherswing]

What is the average battery life you guys are experiencing with OS2SD? I'm currently getting about four hours...

VM670 on 4.4.2? Yes, indeed.

 

[skinbark]

I noticed this in your msm7x27-common Boardconfig. These values are for the P500, thunderc are different. The BOARD_KERNEL_BASE is the only one that mght need fixing, the others are just size parameters.

BOARD_KERNEL_BASE := 0x12800000

## Partition Sizes: Fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00440000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00600000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0xff00000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x0c780000

I think when I started building kitkat I had to fudge those values because my build was erroring out. What'll happen is make won't generate a system image that's larger than those settings so unless you're building a tiny config or something you almost have to fake the values. Those really shouldn't be in msm7x27-common IMO they should be in the device folder. Interesting though that the common_full_phone builds we've been doing haven't thrown the error though, since they generate a larger system.img than the p500 could use.

 

[bigsupersquid]

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.

The concept of fakeflash recovery is courtesy of Koush, like CWM proper. Thanks!
Dunno if it matters, I got the fakeflash to work. it uses the ext partition fstabs and recovery binary from the sd-recovery.
If you flash it you have to "adb kill-server' before adb will connect to recovery again. reboot into recovery and it's the original one. this does NOT overwrite the recovery partition.
meant for the skinbark-non-sd recovery only, probably won't work right with other recoveries.
View attachment cwm-sd_fakeflash.zip
it flashed the OP sd version ok.
it did not back up or restore internal /system or /data or /cache. instead it backs up and restores the ext partitions, like it should for what it is.
it does not handle MTD partition restores or flashes (well, except the boot partition.)
Reboot into the other recovery for those.
This is experimental for evaluation purposes.
Don't gripe if it gives you trouble, instead, give useful data to fix it. You'll be guided to what info to post. Like the 2nd post says, you should have adb installed and a clue how to use it.

for extra amusement value, the restore I did booted with my wifi connected and dev settings correct. but it forgot the CM activation.

 

[hfl12]

Where can i get the patch for newer radio ? Thanks.

 

[skinbark]

Amazing work, squid! I'll try it out a little later and let you know how it goes.
Edit: Tried it. Looks good so far. Flashed the button fix with it and made a backup. I'll try a restore later.
That's what I call an elegant solution!

 

[skinbark]

What is the average battery life you guys are experiencing with OS2SD? I'm currently getting about four hours...

VM670 on 4.4.2? Yes, indeed.

Can't say myself but it'd make sense that the battery life would be affected by having to power the external memory more. I know my mp3 player used to get worse battery life when I played music off the sd card.

 

[brotherswing]

Granted read/write activities on SD use more juice than mtd, I expected a reduction in battery life. I'm just looking to find a basis for comparison. I'm trying to establish a baseline so people using OS2SD will know what to expect.

VM670 on 4.4.2? Yes, indeed.

 

[bigsupersquid]

based on past experience with sd gingerbread, I'd say that the radios are going to determine battery life. No syncing or data-moving apps, and easy on the 3g, more life.
You'd need to test a basic install in NAND and SD both without gapps to get a more reliable baseline.

 

[skinbark]

The first backup I made with fakeflash worked fine but the second one gave "Error while backing up cache." Then when I went to restore the first backup I got the error E:format_volume: no MTD partition "/dev/block/mmcblk0p4"
Error while formatting /cache!
After that I wiped cache which worked.
Edit:
After that, I booted into the restored system, then back into recovery. Fakeflashed and wiped individual partitions which worked I then tried restoring individual partitions and got MD5 mismatch! errors. Then I tried a normal restore and got MD5 mismatch! again.

 

[bigsupersquid]

I thought that was fixed by unmounting the mtd partitions before killing recovery. dang.
manually unmounting all partitions right before or right after the fakeflash takes care of it.

 

[skinbark]

Where can i get the patch for newer radio ? Thanks.

http://forums.androidcentral.com/lg...zvj-zvd-zvd-zvj-flashable-zips-optimus-s.html

 

[cammykool]

This is zvd based right? And where do we find the recoveries for this.

Sent from my SCH-I535 using Tapatalk

 

[bigsupersquid]

long time no see, cammy.

regular NAND recovery linked in first post (in the mediafire folder.)
experimental SD recovery fakeflash is here: View attachment 100042
For the run-from-sd rom version in the second post.
The experimental requires the regular NAND recovery to be installed first. The regular recovery remains there while using the experimental one.

//edit: I forgot, it runs fine on ZV4.
has 3g and wifi. sms works fine. no mms. no bluetooth. if installed with the fakeflash recovery, it remembers wifi passwords.