[ROM][4.4.4][YP-G70][UNOFFICIAL]CyanogenMod 11.0

iurnait · Dec 25, 2013

Happy Holidays to everyone. Here is a new build of CM 11.

Notes:
This build and all future builds will have LVMv2 implemented (thanks to @Meticulus), where mmcblk0p13 (/system), mmcblk0p14 (/system/vendor), and mmcblk0p16 (/data) are placed in a logical volume group. This enables /system to be enlarged from 290MB to 600MB (or more as necessary later on). The packages that were removed from the first build (Apollo, File Manager, etc.) have all been re-added. Also, the removal of the vendor hack means that from now onwards, there is no need to reflash gapps after updating the rom.

-Installation Notes
--On the first flash, if the system logical volume is not present or
is less than 600M there is an assert error. This is so that if anyone
needs to backup information contained in /data, they can. In order to
proceed with the installation, the zip must be flashed a 2nd time.
--During the 2nd flash partitions in the logical group are wiped and
the logical volumes are created and formated then the /etc/fstab and
/etc/recovery.fstab are switched so that, when we hand everything off
to the normal rom installer, the new logical volumes are mounted.

-Reverting to a PRE-LVM ROM
--In the YP-G70 the "recovery", be it CWM or TWRP and in the kernel's
recovery-ramdisk. So in order to get a different recovery you just
flash a different kernel. So to get back to a PRE-LVM ROM, you just:
1. Reboot to recovery like normal.
2. Flash your PRE-LVM ROM like normal.
-- Note: All we really care about at this point is that the kernel
(boot.img) gets flashed. Ignore any other errors!
3. After the flash, Power off.
4. Hold volume up and power on, till you get to recovery.
5. Full wipe, including /system

Installation Instructions:
1. Reboot to recovery and make backup.
2. Do a full wipe.
3. Flash rom. You will see an error pop up this is perfectly normal. Flash the rom again
4. Flash Gapps.
5. Flash US kernel if necessary
6. Have fun!

Links:
ROM: cm-11-20131224-UNOFFICIAL-venturi.zip - 176.60 MB
US Kernel: cm11-USKernel-Dec24.zip - 5.76 MB
Gapps: http://www.androidfilehost.com/?fid=23269279319196268

iurnait · Dec 25, 2013

Lorddemonrage said:
I too would really like this, because just like zardack i've spent several hours trying to get viper working on anything post 4.2.2. or if this can be implemented into a flashable zip patch that would be great.

Sorry about this but I totally skipped over this post before building. Ill look into it and make a new build with the commits reverted

tontiv said:
thanks for this! is hw acceleration supported already?

Theres actually some code in cm that disables HW acceleration for devices with less than 512 mb ram in userspace. There was something in CM's gerrit to lower the limit, but i think it has been abandoned. It has been enabled on the nightly builds of PAC 4.3 for quite a while now, but to be honest there really is only a negligible difference with it enabled vs disabled.

Edit: PAC has had it since Oct 30: http://review.pac-rom.com/#/c/3110/

TheRealBubba said:
2) I miss the owner info string that would display on the lock screen (yeah, I'm firmly in the Absent Minded Professor demographic and it is a remarkable improbability that I havn't lost this device permanently yet).

Should be under Settings>Security>Owner Info

FweaKiid305 said:
Is Voice+ Integrated With CM11?

Yes, it is now included.

chicinwang · Dec 25, 2013

Arrrghh!! Less than an hour after I flash 12/15 build "someone" just had to release a NEWER build! Fml :banghead:

fixing to download and flash!!! Thanks! Btw 12/15 was slick
<R760X>

annoyingduck · Dec 25, 2013

God dam you iurnait, I'm way too drunk to actually read directions right now!! Thank you so much, I can't wait to run this tomorrow...
I'm assuming it's a script in the initial flash the overwrites the current boot partitions... In the event of a possible bad download, are we looking at a hard brick? Or does the recovery partition stay fully intact?

iurnait · Dec 25, 2013

annoyingduck said:
God dam you iurnait, I'm way too drunk to actually read directions right now!! Thank you so much, I can't wait to run this tomorrow...
I'm assuming it's a script in the initial flash the overwrites the current boot partitions... In the event of a possible bad download, are we looking at a hard brick? Or does the recovery partition stay fully intact?

All the partitions stay intact. We get more space because lvm is able to basically combine the /system, /vendor, and /data partitions and then allocate a hunk of that to /system. The other partitions are untouched. It is not very likely that something would go wrong, but reflashing the rom or another kernel should solve any problems

Mevordel · Dec 25, 2013

annoyingduck said:
God dam you iurnait, I'm way too drunk to actually read directions right now!! Thank you so much, I can't wait to run this tomorrow...
I'm assuming it's a script in the initial flash the overwrites the current boot partitions... In the event of a possible bad download, are we looking at a hard brick? Or does the recovery partition stay fully intact?

You will always have download mode available even after a bad zip flash.

FweaKiid305 · Dec 25, 2013

For Those Who Have Trouble Installing Viper4Android. I confirmed it was not a root access issue so I thought it might be a mount issue. I confirmed this by doing the below in either Terminal Emulator or via an adb shell before launching v4a for the first time:

Code:

mount -o rw,remount /system

This solved the issue, driver installation succeeds. Just thought I should post this in case anyone else gets to the same issue and is looking for a solution.

Sent from my YP-G70 using XDA Premium 4 mobile app

zardak · Dec 25, 2013

I can confirm Viper4Android works on 24/12 build. I used root explorer to manually mount /system rw before installing the driver.

Actually I got V4A working once on a 4.3 CM ROM in the past, but only once. After flashing that rom again never worked anymore, so now i'm confused where the problem is...

Meticulus · Dec 25, 2013

FweaKiid305 said:
For Those Who Have Trouble Installing Viper4Android. I confirmed it was not a root access issue so I thought it might be a mount issue. I confirmed this by doing the below in either Terminal Emulator or via an adb shell before launching v4a for the first time:

Code:

mount -o rw,remount /system

This solved the issue, driver installation succeeds. Just thought I should post this in case anyone else gets to the same issue and is looking for a solution.

Sent from my YP-G70 using XDA Premium 4 mobile app

zardak said:
I can confirm Viper4Android works on 24/12 build. I used root explorer to manually mount /system rw before installing the driver.

Actually I got V4A working once on a 4.3 CM ROM in the past, but only once. After flashing that rom again never worked anymore, so now i'm confused where the problem is...

Because the problem started with 4.3, I lean towards thinking that the problem is "selinux" related. It's just a guess, but I think that remounting /system rw requires some sort of special security context.....

Lorddemonrage · Dec 25, 2013

zardak said:
I can confirm Viper4Android works on 24/12 build. I used root explorer to manually mount /system rw before installing the driver.

Actually I got V4A working once on a 4.3 CM ROM in the past, but only once. After flashing that rom again never worked anymore, so now i'm confused where the problem is...

tried this, works now.
@iurnait OMG you did it!!.... this is truly christmas!! you sir have restored my faith in humanity.....

now to completly destroy my hearing

Meticulus · Dec 26, 2013

LordZilo said:
Update from problem i posted yesterday. I think its a MAC conflict. Both YPG70s are showing me the same mac and ip addresses.

When i disable Wifi on either one the other one works, when i have it turned on at the same time both dont connect.

and it appears that it does indeed do this on CM 10.2 as well. Same MAC and ip on both devices.

I've been thinking about this and I'm starting to suspect the we ALL might have the same wifi mac address!:laugh:

To confirm, I asking that a few people running the lastest CM or SlimKat to report the last 3 sets of their wifi mac as reported from Settings->About Phone->Status

Mine are:

c5:00:34

Thanks...

mv-clear · Dec 26, 2013

Mine is the same c5:00:34, I actually have a weirdness with my wifi, if I have bluetooth enabled (I usually leave it on for my wireless stereo headset) then I can connect to wifi, but if I cycle it off, and then try and turn it back on wifi hangs (radio never enables) and I need to reboot the device to get reconnected to wifi. If I leave the bluetooth radio off, then I can enable and disable the wifi and it will turn back on without any problems. I'm on the 12/24 build on the North American device with the capacitive home button. Not sure if it's related to the wifi mac access being the same as I only have 1 device.

Meticulus said:
I've been thinking about this and I'm starting to suspect the we ALL might have the same wifi mac address!:laugh:

To confirm, I asking that a few people running the lastest CM or SlimKat to report the last 3 sets of their wifi mac as reported from Settings->About Phone->Status

Mine are:

c5:00:34

Thanks...

iurnait · Dec 26, 2013

Meticulus said:
Mine are:

c5:00:34

Mine are: ~~3a:60:df~~

I have the Intl version

Sent from my Nexus 7 using Tapatalk

Edit:

:facepalm: i just realized that i was looking at the mac for my N7. Mine are actually c5:00:34 too

kfirbep · Dec 26, 2013

I have a problem that I hope someone here could help me.
the problem is that if I charge the device when it is off it always restart itself (show the battery icon and then turn off and after a few seconds it turn on again and show the battery icon again).
how can I fix it?

annoyingduck · Dec 26, 2013

International version
Mac ends in c5:00:34. Very interesting

luraziel · Dec 26, 2013

Meticulus said:
I've been thinking about this and I'm starting to suspect the we ALL might have the same wifi mac address!:laugh:

To confirm, I asking that a few people running the lastest CM or SlimKat to report the last 3 sets of their wifi mac as reported from Settings->About Phone->Status

Mine are:

c5:00:34

Thanks...

running latest cm11 (non slimkat) version I have this same mac, it could be a cm issue?

Meticulus · Dec 26, 2013

OK, So it appears that many of us have the same mac address... Not really a problem unless we are all trying to use the same WIFI

But for those of you that do could you also open this file ( as text file ) and give me the last 3 segments of that mac ....

/efs/imei/.nvmac.info

mv-clear · Dec 26, 2013

C6:12:27 for me

Meticulus said:
OK, So it appears that many of us have the same mac address... Not really a problem unless we are all trying to use the same WIFI But for those of you that do could you also open this file ( as text file ) and give me the last 3 segments of that mac ....

/efs/imei/.nvmac.info

luraziel · Dec 27, 2013

Meticulus said:
OK, So it appears that many of us have the same mac address... Not really a problem unless we are all trying to use the same WIFI But for those of you that do could you also open this file ( as text file ) and give me the last 3 segments of that mac ....

/efs/imei/.nvmac.info

74:7C:74

chicinwang · Dec 27, 2013

meticulus said:
ok, so it appears that many of us have the same mac address... Not really a problem unless we are all trying to use the same wifi but for those of you that do could you also open this file ( as text file ) and give me the last 3 segments of that mac ....

/efs/imei/.nvmac.info

7C:6F

B
That's actually supposed to be a (D) not a d#$& smiley face. SMH

[ROM][4.4.4][YP-G70][UNOFFICIAL]CyanogenMod 11.0

Inactive Recognized Developer

Inactive Recognized Developer

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Meticulus

Guest

Senior Member

Meticulus

Guest

Member

Inactive Recognized Developer

Senior Member

Senior Member

Member

Meticulus

Guest

Member

Member

Senior Member

Similar threads

Top Liked Posts