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

[skinbark]

Try doing clean wipe, flash the rom, reboot, enable developer options, install keyboard, get wifi going etc. then boot into recovery and flash gapps.
Then when you boot into the rom it should show 'preparing apps 1 of 9...' etc. I think you won't see this if you install immediately after flashing the rom but you will if you reboot first and then flash the rom. Both ways of installing worked for me.

 

[skinbark]

Sadly I have to agree with the new wave testers. I'm not seeing flashing the Nbss apps actually work. Wiped cache and factory resetdata, advanced options wiped the system, boot, data, and cache just for good measure, flashed the newest post, then right after flashed the app pack, it didn't actually post anything, even though it said flashing apps and all that on CWM.

Also, just to be sure you're aware, apps.zip is not meant to be flashed. That's just so rom users will have all the apps and ringtones that a full install of the rom would give and they can experiment with pushing them to /system/app or installing off sdcard. Slim_4.4.X_gapps_Nbsss_v2.zip is the flashable gapps.

 

[Eduardo Galvan]

It shows I'm on Sprint, and wifi is working flawlessly. (Oh and I flashed my OV to Sprint, so yeh.) ##Edit: Gapps work, back button doesn't but whateva.

 

[skinbark]

Virgin fix uploaded.
Virgin.fix.CM11.0.zip
Link in OP.

 

[skinbark]

It shows I'm on Sprint, and wifi is working flawlessly. (Oh and I flashed my OV to Sprint, so yeh.) ##Edit: Gapps work, back button doesn't but whateva.
View attachment 98687

It take a little while for the back button to 'kick in', it'll work.

 

[bigsupersquid]

using the files linked in the OP,
on theKraven's CWM *06
'factory reset'
install rom
install gapps
recovery sez everything cool
reboot

I get:
basic phone service
wifi sees networks (can't test more than that right now as my wpa2 is down)
no play store (no extra apps in /system/app or in /system/priv-app)

'factory reset', reflash gapps, reboot
still no play store (no extra apps in /system/app or in /system/priv-app)

I think there be a glitch in the gapps package maybe. recovery says it flashes ok.
uh, yeah, it's got an old update-binary and old-style updater script.
plus something appears to be borked in my current recovery. switching. I didn't check but the existing Slim file may flash ok with the skinbark v06 recovery.
the skinbark recovery flashes a modded version with new update-binary and improved updater-script bits imported from the cm11 zip. I won't post a whole Gapps package, but if you take this updater-script and update-binary and drop it into the existing Slim zip file, it seems to work. flash gapps right after rom after full wipe.
View attachment update-bits.zip
it also appears that a dirty flash of the rom after the gapps may work. the backuptool.sh or whatever grabs the gapps files and puts them back after an install, even though the updater-script says to format /system.

 

[bigsupersquid]

virgin fix looks good... still no data.

 

[skinbark]

It might be that the latest cwm works with both old and new updater binaries. I'm going to fix and upload the new slim gapps regardless.

 

[skinbark]

virgin fix looks good... still no data.

I'm looking into packages/services/Telephony as a starting point for unravelling the data problem. I'll also probably reactivate my VM670 for testing purposes, since I don't really need data atm. I switched it over to the One V last month.

 

[bigsupersquid]

here's a teaser.
I had to manually force the aufs mounting script on startup as soon as adb connected to get this to scan for the dalvik cache, but it's (2) one-gig ext partitions (system and data)
data has zero apps installed. I can fit a heckuva lot more on /system than the measly 90MB on there now, but it's what I had on hand. not to mention that those 1G partitions are relatively small for the card.
includes the op gapps installed to nand.
sms messaging gives error 97 failing to send on an unactivated phone... may well work on a daily driver.
oh, and at its current stage of development, it blocks access to the vfat for android. boo.

 

[skinbark]

That's incredible! Total game changer. Can't wait till it's ready!

 

[bigsupersquid]

one part of the gimmick is to make a minimum usable install for /system.
then a /full/ install of everything that'll run with the same build configuration.
the full install minus the files already on system goes on the 3rd sd partition.
I think cache should go on a fourth. the way I ran it, the base install worked alone and didn't carry over any data from the ext addon after reboot, and the cache should act the same.
it will require either recovery modifications, good install scripts, or manual file copying in terminal with the card mounted to pc to install the extra goodies. I used the third method this time.
right now it looks like init.d scripts aren't running. I need them for this and am looking into it.

 

[thewraith420]

You guys know... I picked up a Verizon droid razr m.. I got it running stock jb 4.1.2 and there's no rooting and roming this version. Despite the obvious hardware advantage. It almost feels like a downgrade when I've been playing with Android 4.2+ for so long on the OV. just amazing work here in these forums.

Sent from my XT907 using Tapatalk

 

[Shinkenred]

After you reboot once or twice the buttons start working. Camera works, along with Gallery. They're in the apps.zip along with all the other default cm11 apps, well as ringtones and alarms that I removed from the rom to save space. The gapps I posted is working for me but it's just to get the play store working. If you do a clean install and flash the gapps right after you flash the rom you'll have a working play store.

...it was a clean install, and I flashed gapps after the rom. I'll try again with the updated stuff, though.

Posted via Android Central App

 

[bigsupersquid]

adding this to init.qcom.rc turns on the init.d scripts.
I put it right before the "#########SERVICES###########" section.

# Run sysinit
    exec /system/bin/sysinit

I dunno why they're disabled by default because CM already has everything needed except turning them on.

 

[skinbark]

Useful article from the CyanogenMod wiki:
Barebones - CyanogenMod

 

[Eduardo Galvan]

I tried flashing to Cricket and activating, see if I could get SMS or calling. QXDM wouldn't put in the MEID and ESN I get cause code 97 when sending. I just figured out that the back button worked when I installed a keyboard. I'll have to remember that. Calling right now works but it asks if I wanna collect call...Again, thanks for all the hard work you guys put into this ROM and phone.

 

[bigsupersquid]

Useful article from the CyanogenMod wiki:
Barebones - CyanogenMod

Last time I read that was trying to optimize Gingerbread

Good news!
adding bits to init.qcom.rc (create mount directories and mount ext partitions right after nand, enable init.d) and an init.d script (insmod aufs.ko and aufs mount the ext partitions) seems to work.

still a few glitches but I think it's because of stale duplicate files, I will fresh flash and try again. Gonna put the whole app pack from the OP on there

once it looks decent on my end I will post the flashable zip(!) I am using to change the boot process, and also post the build changes neccesary to avoid having to flash anything.

 

[skinbark]

adding this to init.qcom.rc turns on the init.d scripts.
I put it right before the "#########SERVICES###########" section.

# Run sysinit
    exec /system/bin/sysinit

I dunno why they're disabled by default because CM already has everything needed except turning them on.

This might help with my selinux issues.

 

[skinbark]

Last time I read that was trying to optimize Gingerbread

Good news!
adding bits to init.qcom.rc (create mount directories and mount ext partitions right after nand, enable init.d) and an init.d script (insmod aufs.ko and aufs mount the ext partitions) seems to work.

still a few glitches but I think it's because of stale duplicate files, I will fresh flash and try again. Gonna put the whole app pack from the OP on there

once it looks decent on my end I will post the flashable zip(!) I am using to change the boot process, and also post the build changes neccesary to avoid having to flash anything.

That's awesome, we're gonna get a REAL kitkat! Many thanks man!