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

linuxxxx

Senior Member
Sep 22, 2013
764
2,307
0
cm-12-20150206 also bricked my device.
Steps to reproduce:

1. Installed current TWRP (2.8.4.1)
2. Factory reset + converted cache and data to f2fs
3. Installed cm-12-20150206 + gapps

CM12 booted fine and i enabled root + installed some apps. Then i tried to reboot to recovery.
- recovery hangs at the "teamwin" logo (waited for 10+ minutes)
- normal boot hangs at the google logo
- bootloader works, reflashing recovery from bootloader doesn't change anything
OK, i can confirm this issue. How to unbrick: get factory images and from bloader run
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase cache
fastboot flash cache cache.img
This will reset ur data and sdcard partition. I suggest u to try to use an older twrp (I tried 2.8.3). The nightly is not the problem, it looks like twrp f*c*s something when it boots. I'll give a look at this asap
 
Last edited:
  • Like
Reactions: PoedelPCS

thedap

Member
Jun 25, 2010
6
2
0
OK, i can confirm this issue. How to unbrick: get factory images and from bloader run
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase cache
fastboot flash cache cache.img
This will reset ur data and sdcard partition. I suggest u to try to use an older twrp (I tried 2.8.3). The nightly is not the problem, it looks like twrp ****s something when it boots. I'll give a look at this asap
Thanks!
The factory image wasn't even necessary, i just flashed TWRP 2.8.3.0, rebooted to recovery (which worked now) and formated /data and /cache with ext4 (TWRP 2.8.3.0 doesn't seem to support f2fs) - everything fine now
 

thedap

Member
Jun 25, 2010
6
2
0
a small update, i tried the following:
- flashed TWRP 2.8.4.1
- formated /data and /cache with f2fs
- reboot to bootloader and flashed TWRP 2.8.3.0
everything seems to work, rebooted several times (system and recovery) and no brick yet.

for me it looks like TWRP 2.8.4.1 messes something up when it starts while f2fs partitions are present (i didn't test TWRP 2.8.4.0)
 
a small update, i tried the following:
- flashed TWRP 2.8.4.1
- formated /data and /cache with f2fs
- reboot to bootloader and flashed TWRP 2.8.3.0
everything seems to work, rebooted several times (system and recovery) and no brick yet.

for me it looks like TWRP 2.8.4.1 messes something up when it starts while f2fs partitions are present (i didn't test TWRP 2.8.4.0)
Yep thanks..

So it should also be safe to flash CM recovery and then wipe/format f2fs/eventually flash ROM files using fastboot boot twrp.img
 

ScanaX

Member
Nov 6, 2010
47
9
0
Palermo
Just installed. Now i'm downloading alla my apps from play store, no backup of previous settings or app. Let me use it and update the ROM.
P.S.: i' m using the last nightly. :)
Coming from stock rooted with twrp 2.8.4.1, factory reset, changed file system trhough twrp for data and cache, installed from USB with otg, it is working
 
Last edited:

paolocorpo

Senior Member
Jan 9, 2013
1,783
378
113
Sassoferrato
Kernel

Ciao to all
I am using a custom rom of SYNMAN with Carcosa a33 kernel both based on 5.0.2 AOSP
My friend BRAINVISION is using CM12 and he is very happy about battery drainage and performance

May i extract boot.img from this CM12 and flash it on my system ??
Or i will have explosion ? :)
 
  • Like
Reactions: brainvision

x-system

Senior Member
Aug 17, 2008
54
0
0
Hello. Yesterday I flashed cm12 (2015.02.07) and was problems whith very long charging.
If tablet is off charging is normal.
How fix it byg?

What kernel is slow battery drain?
 

linuxxxx

Senior Member
Sep 22, 2013
764
2,307
0
Hello. Yesterday I flashed cm12 (2015.02.07) and was problems whith very long charging.
If tablet is off charging is normal.
How fix it byg?
The charge time has been slowed down from Google on aosp 4.3 because of he issues (AFAIK)
Ciao to all
I am using a custom rom of SYNMAN with Carcosa a33 kernel both based on 5.0.2 AOSP
My friend BRAINVISION is using CM12 and he is very happy about battery drainage and performance

May i extract boot.img from this CM12 and flash it on my system ??
Or i will have explosion ? :)
Flash the whole ROM. Its safer
 
hey guys can you please show me a screenshot of the notification drawer with a few notifications on with the default CM12 theme and style?

I applied a bunch of different themes and now it seems that the default one is messed up.. don't know, but I remember white background - sorry I mean light grey - with dark text for notifications.. While now I always eve dark background, even with the default style.. rebooted tons of times!

thanks guys..
 
Last edited:
OK..

don't know why and don't know how, but it really seems that afetr applying a bunch of CM themes the original framework messed up a little bit.. Original colors on notifications and original notification bar buttons were gone, lost.. I rebooted a lot of times to be sure that the default theme was fully applied but nothing changed..

now I want to start from scratch again, for different reasons..

so I have a question related to TWRP issues with f2fs causing bootloop..

as other users reported ATM safe steps are:
1. flash or boot twrp 2.8.4.1
2. format /data and /cache with f2fs file system
3. flash permanently twrp 2.8.3 (but maybe also 2.8.4.0, that does NOT have f2fs support, but it's not sure it will work)

and that's OK.. but what about next nighties updates?
how should I update so that I wouldn't lost f2fs support but without boot-looping again and again?
TWRP 2.8.3 does not have f2fs support: what would happen if I dirty flash a ROM and GAPPS with such a recovery? It should not be an issue 'cause /data and /cache partitions should remain untouched.. am I right? Even if I need to wipe cache and davilk?

Does someone know something about all that?

thanks guys! ;)


EDIT: so I can now reply my own questions..

If you use f2fs partitions there's no way to update, nor via twrp 2.8.3 nor via adb sideload: the process fails when it tries to mount /data partition.
This old version of twrp doesn't support f2fs, so it isn't able to mount data and cache partitions!

So I choose to go back to etx4 partitions.. [emoji27] [emoji27]
At this stage nighties are too much important so I prefer to be able to update..
 
Last edited:
  • Like
Reactions: ferglobal

thedap

Member
Jun 25, 2010
6
2
0
If you use f2fs partitions there's no way to update, nor via twrp 2.8.3 nor via adb sideload: the process fails when it try to mount /data partitions.
This old version of twrp doesn't support f2fs, so it isn't able to mount those partitions!

So I choose to go back to etx4 partitions.. [emoji27] [emoji27]
At this stage nighties are too much important so I prefer to be able to update..
yep, for f2fs users TWRP is not working and pretty much useless. If you want to update use EXT4 or wait for a TWRP fix.
 

paolocorpo

Senior Member
Jan 9, 2013
1,783
378
113
Sassoferrato
If you use f2fs partitions there's no way to update, nor via twrp 2.8.3 nor via adb sideload: the process fails when it try to mount /data partitions.
This old version of twrp doesn't support f2fs, so it isn't able to mount those partitions!

So I choose to go back to etx4 partitions.. [emoji27] [emoji27]
At this stage nighties are too much important so I prefer to be able to update..
Dear,
can you do a test with ANTUTU with your N7 TILAPIA and CM12 in ext4 and (if i remember weel) with Carcosa Kernel ??
My N7 TILAPIA with Synman + Carcosa has a score around 24000
 
Dear,
can you do a test with ANTUTU with your N7 TILAPIA and CM12 in ext4 and (if i remember weel) with Carcosa Kernel ??
My N7 TILAPIA with Synman + Carcosa has a score around 24000
No, dear..

Still on CM with standard kernel.. I had to flash everything from scratch 'cause I formatted /data and /cache partitions to ext4 again..

Antutu score on 02.05 build with f2fs was 19.920 or something like that..
I'm going to do the same test with 02.08 build with ext4, but I bet it would be pretty the same..

Later, this afternoon or maybe this evening I'll finally flash the carcosa.a33..
 

paolocorpo

Senior Member
Jan 9, 2013
1,783
378
113
Sassoferrato
Great
I am sorry for your issues related to f2fs sytem
I am waiting for you news about ANTUTU's test and for your 3D dedicated to this rom on Androidiani forum :)
Ciao
 
Last edited:
?

Don't think I would have time to follow a dedicated thread, that's the reason why I still haven't created one for the official CM12 into the forum you are talking about..

BTW, tests done..

First Antutu test was pretty the same as with f2fs: 19.535
Second one was much lower: 18.971..
And a third one: 19.729...

So it really seems that f2fs file system works and it gives this device a little help when talking about performances, even if only related to read/write access to the nand memory.

I think o have to absolutely try the carcosa kernel.. ;)
 
  • Like
Reactions: paolocorpo

linuxxxx

Senior Member
Sep 22, 2013
764
2,307
0
:)
I am sure that you will found necessary time to create a 3D ... ;)
I am waiting for your upgrade to Carcosa a33 and its new test
Ciao
?

Don't think I would have time to follow a dedicated thread, that's the reason why I still haven't created one for the official CM12 into the forum you are talking about..

BTW, tests done..

First Antutu test was pretty the same as with f2fs: 19.535
Second one was much lower: 18.971..
And a third one: 19.729...

So it really seems that f2fs file system works and it gives this device a little help when talking about performances, even if only related to read/write access to the nand memory.

I think o have to absolutely try the carcosa kernel.. ;)
Great
I am sorry for your issues related to f2fs sytem
I am waiting for you news about ANTUTU's test and for your 3D dedicated to this rom on Androidiani forum :)
Ciao
No, dear..

Still on CM with standard kernel.. I had to flash everything from scratch 'cause I formatted /data and /cache partitions to ext4 again..

Antutu score on 02.05 build with f2fs was 19.920 or something like that..
I'm going to do the same test with 02.08 build with ext4, but I bet it would be pretty the same..

Later, this afternoon or maybe this evening I'll finally flash the carcosa.a33..
Benchmarks scores may not be perfect because of cm profiles that haven't been fully enabled on tilapia (I'm Woking on this), and keep in mind I won't support anyone with custom kernels
 
  • Like
Reactions: brainvision