[OFFICIAL] CyanogenMod 12 - Tilapia [ext4][f2fs]

[PoedelPCS]

Will post a f2fs twrp for tilapia.

that means you are working on a f2fs capable twrp clone? cool!

 

[linuxxxx]

that means you are working on a f2fs capable twrp clone? cool!

It will be just a twrp with a few changes for cm12 and a f2fs fstab.

Sent from my A0001

 

[ferglobal]

I have checked that modifying the update script, the grouper TWRP f2fs 2.8.5.0 can upgrade to the latest nightly. I do still look forward to the specific tilapia TWRP though.

 

[PoedelPCS]

I have checked that modifying the update script, the grouper TWRP f2fs 2.8.5.0 can upgrade to the latest nightly. I do still look forward to the specific tilapia TWRP though.

why don't you take the original from here ?

 

[PoedelPCS]

by the way, my data and cache are f2fs, just checked it. See attached screenshot

 

[ferglobal]

by the way, my data and cache are f2fs, just checked it. See attached screenshot

Are you able to reboot to recovery? That image wouldn't allow me to (it only helped me to change the partitions and do the initial flash of zip files), and corrupted my N7 into boot cycle and forced me to flash my system from scratch. I can only operate with that modified grouper one and tinkering with the update script to upgrade to new nightlies.

 

[PoedelPCS]

according to my own experiences the only way to get this working is:
flash twrp 2830 or cyanogen recovery to recovery partition.
Boot twrp 2841 as I did, maybe 2850 works as well, temporarily.
Use this to fatory reset and wipe system, set cache & data partition to f2fs.
To make sure everything works you can now reboot to bootloader and flash that twrp2830 temporarily again, then hit the button in the middle on the bottom to enter twrp's console output to see everything was mounted correctly.
Then push the cm image and gapps to your sdcard. You can either sideload them or use adb to push them:
adb push cmXXXXX.zip /sdcard/
Do the same to gapps package.
Then use this temporarily booted twrp to install both.
Mission completed.

 

[Thömy]

why don't you take the original from here ?

The recovery uses a kernel with a outdated F2FS driver and can cause corruption in combination with the kernel used by CyanogenMod.

 

[linuxxxx]

why don't you take the original from here ?

As Thomy said

Nightlies now have experimental support for F2FS for /data and /cache. A compatible recovery is requiried.

WARNING
The F2FS version used by CM is newer than the one used by existing ROMs, recoveries and custom kernels. Features like inline_dentry and inline_data have been enabled to save disk space and improve the performance. Those features are not available on older kernels and this can cause corruption and data loss if you switch back! Just rebooting into a unsupported recovery can be enough. Always make a backup when you switch ROMs!

Sent from my A0001

 

[linuxxxx]

Just compiled them:
Recovery (TWRP) : http://puu.sh/fZrcH.img (md5: 67385e0e5e75cce59a0cfb92d6278593)
Recovery (SR): http://puu.sh/fZrsa.img (md5: e6f5b67035f57a61e2b9d6f46988bfcd)

Built for cm12, it supports f2fs, (I did not test twrp before upload, there should be no problems anyway)

Sent from my Mi 2S

 

[rashq]

no deep sleep here also

The device will be awake continuously even when not being used. Battery drains like crazy. Same was the case while using stock 5.0.2. I thought cm will not be having that issue but same issue I am facing in cm also . Any solution guys ?

 

[brainvision]

Just compiled them:
Recovery (TWRP) : http://puu.sh/fZrcH.img (md5: 67385e0e5e75cce59a0cfb92d6278593)
Recovery (SR): http://puu.sh/fZrsa.img (md5: e6f5b67035f57a61e2b9d6f46988bfcd)

Built for cm12, it supports f2fs, (I did not test twrp before upload, there should be no problems anyway)

Sent from my Mi 2S

Hi linuxxxx, thanks for that!
But don't you that the recovery should be safe enough to flash? Someone should try it before releasing.. IMO..

The device will be awake continuously even when not being used. Battery drains like crazy. Same was the case while using stock 5.0.2. I thought cm will not be having that issue but same issue I am facing in cm also . Any solution guys ?

Yea that's absolutely true.. To solve this big issue you can permanently stop and deactivate a bunch of Google Play Service services and others ones, or flash a custom kernel (no support by linuxxxx and cm)

 

[Marasta86]

SMS problem

Hi guys!!!
I'm using the nightly since the first releases, I want to thank the entire staff for good the work done!
I just have a problem, don't know if there's a problem with my configuration or it's due to the CM12, but when Hangout is set as default program for SMS it's unable to read messages, and I have to use the messages app.
If you have any advice to use Hangout for reading SMS it'll be useful.
Thank you again and good work!

 

[linuxxxx]

Hi guys!!!
I'm using the nightly since the first releases, I want to thank the entire staff for good the work done!
I just have a problem, don't know if there's a problem with my configuration or it's due to the CM12, but when Hangout is set as default program for SMS it's unable to read messages, and I have to use the messages app.
If you have any advice to use Hangout for reading SMS it'll be useful.
Thank you again and good work!

Hangout does not support SMS on tilapia cuz for Google this device should not be able to send them.

Sent from my A0001

 

[linuxxxx]

Hi linuxxxx, thanks for that!
But don't you that the recovery should be safe enough to flash? Someone should try it before releasing.. IMO..

Yea that's absolutely true.. To solve this big issue you can permanently stop and deactivate a bunch of Google Play Service services and others ones, or flash a custom kernel (no support by linuxxxx and cm)

For the first question: here you have a working twrp (the previous one had problems loading ui) http://puu.sh/g13Tu.img (tested)

And you can disable GPlay Services permission to wake up your device with Privacy Guard

 

[rauhut]

Just compiled them:
Recovery (TWRP): # (md5: 67385e0e5e75cce59a0cfb92d6278593)
Recovery (SR): # (md5: e6f5b67035f57a61e2b9d6f46988bfcd)
Built for cm12, it supports f2fs, (I did not test twrp before upload, there should be no problems anyway)

Just installed both via Fastboot with following results:

1. Recovery (TWRP): installed successfully but device did not boot in recovery (just black screen)
2. Recovery (SR): installed successfully and started (but can't read encrypted data partition)

 

[linuxxxx]

Just installed both via Fastboot with following results:

1. Recovery (TWRP): installed successfully but device did not boot in recovery (just black screen)
2. Recovery (SR): installed successfully and started (but can't read encrypted data partition)

About twrp read my previous post. We'll give a look at sr encryption later

Sent from my A0001

 

[rauhut]

About twrp read my previous post. We'll give a look at sr encryption later

twrp-tilapia-f2fs.img version from first post installs and boots but gives
"E:Could not mount /data and unable to find crypto footer"
while openrecovery-twrp-2.8.4.1-tilapia.img asks for the password at statup.

 

[limingg]

Factory reset and wizard crash at Google account login successfully. I just want to restore app from backup by wizard at first boot.
I have try man nightly version, only cm-12-20150204-NIGHTLY-tilapia is fine which didn't crash. Other nightly version are always crash.

 

[linuxxxx]

twrp-tilapia-f2fs.img version from first post installs and boots but gives
"E:Could not mount /data and unable to find crypto footer"
while openrecovery-twrp-2.8.4.1-tilapia.img asks for the password at statup.

This is a twrp problem.