yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] levio:
This part is wrong. If you flash as first step the isorec recovery without a isorec support kernel, it doesn't work. Starting from kk compatible kernel then you have to flash cm13 or one of the last nightly of cm12(because the snapshot hasn't the isorec support kernel) then gapps( but on cm13 you have to resize system partition to 1gb otherwise it fails) then isorec recovery. If then you want a trim isorec kernel you flash this after the cm and then flash a isorec recovery.
[Galaxy S II Original Android Development] chrisXL:
no matter when you flash isorec recovery
[Galaxy S II Original Android Development] the.divergent:
But it matter does your rom have IsoRec support;)

Послато са GT-I9100 уз помоћ Тапатока
[Galaxy S II Original Android Development] :
The only step here you don't need to do is flash isorec kernel after, unless you want to flash the one with trim, as flashing the CM12.1 or CM13 will give you an isorec kernel anyway. If you were using CM12.1 snapshot(not recommended) yoiu would need that step

The recovery is flashed to the old recovery partition. It doesn't matter when this is done, and you only need to do it once. Only an isorec kernel will make use of it though
[Galaxy S II Original Android Development] the.gangster:
Nevertheless you are describing it in a way that will lead to the yellow triangle!

You can avoid that if you flash a signed recovery prior to Odin and using Odin only for repitting (if you need to use Odin at all).
[Galaxy S II Original Android Development] chrisXL:
obviously, I consider only rom/build with isorec support.

---------- Post added at 11:52 PM ---------- Previous post was at 11:46 PM ----------
[Galaxy S II Original Android Development] :
Yes, you are correct, although chrisXL may have meant flash philz, then flash pit with odin.....

And if not having the yellow triangle was a priority, you could do it in a different way and not use odin at all, but not everyone cares whether they get a yellow triangle. After all, it doesn't have any practical or functional value other than annoying some users visually
[Galaxy S II Original Android Development] the.gangster:
Right, the yellow triangle has no further impact, but there are many people here, that ask how to get rid of it, so I would not guide them to run into it at all, if it is not needed. And running triangle-away app is always a risk (although it still seems to work).

At least if you come from original Samsung stock ROM 4.1.2 I would:

flash "philz-touch_3.00_i9100-signed.zip", which will give you a "runtime recovery" that allows you to flash other stuff, like:

flash "philz_touch_6.48.4-i9100.zip" (yes, you could flash other KK-compatible recoveries, too, but this one allows you to format /preload)

optionally: now use Odin (e.g. Odin 3.0.7) with PIT for re-partition only (no PDA) (no auto-reboot)

Boot into recovery and format system, data, internalSD (emmc) and preload. (yes Philz survived repitting with ODIN)

Flash IsoRec-Recovery and CM12.1 or CM13 ROM

optionally: if you haven't repitted yet you can now still change partition sizes with [MENTION=4141005]Lanchon[/MENTION] 's flashable Repit tool (to gain enough space for GApps in CM13) from within IsoRec-TWRP-Recovery.

So no increase of flashcounter, no yellow triangle, not even a PC is needed if you downloaded everything to your external-SD before you started.
[Galaxy S II Original Android Development] iistoryahi:
will , Triangle-away is working perfectly , i used it on stock and CM12.1 , and now im running CM13 and i used it too

Just sharing :)
[Galaxy S II Original Android Development] chrisXL:
Sorry, maybe I'm wrong but AFAIK you can't re-pit without a kernel (or rom) in pda. :what:
[Galaxy S II Original Android Development] Skyline:
It's possible to re-pit that way. Personally tried 4-5 times with my device
[Galaxy S II Original Android Development] the.gangster:
You are wrong. It is.

This is simply because no pitfile should ever change the layout of the boot partition mmcblk0p5 or recovery partition mmcblk0p6. So neither a standard nor an Isorec recovery would be deleted.
[Galaxy S II Original Android Development] zbsbabar:
thankx .
[Galaxy S II Original Android Development] the.gangster:
[MENTION=7299626]SalvaXr[/MENTION]

as CM13 got official status the CM12.1 builds vanished from cyanogenmod downloads sites.

E.g. here is the latest build.

[MENTION=6159291]Lysergic Acid[/MENTION]

maybe you should add a comment on OP that "new" users have to search for mirrored downloads of Nightly-20160203.

As you still link to official download site without hinting, that nightlies have been removed.
[Galaxy S II Original Android Development] the.gangster:
LOL,

yeah, becomes much more easy to google mirrors if you know what exactly to search for...

cm-12.1-20160203-NIGHTLY-i9100.zip

(as on february 4th the CM13 nightlies started)
[Galaxy S II Original Android Development] ajislav:
Or you could try these builds.

http://xdaforums.com/showthread.php?t=2686887

The freshest CM12.1 for i9100..
[Galaxy S II Original Android Development] Lanchon:
avoid yellow triangle

start with stock 4.1.2.

get a temporary recovery.

flash it (means run in this case) from stock recovery. you need an sdcard.

flash my trim kernel.

flash isorec twrp.

reboot recovery.

flash my repit. make it wipe system, data, preload. use 1gb sys, 6gb data, min preload. if you want to wipe sdcard, format it from TWRP before flashing repit. do not wipe sdcard with repit.

format /data AGAIN after repit.

flash cm and open gapps mini (or nano).

flash my trim kernel again.

optionally flash a modem XXMS4.

reboot and wait a bunch.

user kernel aduitor if you want.

AVOID PEGASUSQ.

you might want to raise min freq to 500 or 800 and set scheduler to ROW or something similar.

the Trimmer app should not be needed, but you can use it.
[Galaxy S II Original Android Development] the.divergent:
If you want to remove yellow triangle just search for Triangleaway.apk

Regards
[Galaxy S II Original Android Development] franticfreddy:
You could also make stock 4.1.2 kernel tar and flash only stock kernel.tar with pitfile in odin, then reboot in stock recovery, then flash philz recovery, do reboot into philz, format all partitions, then flash Lanchon kernel zip and/or isorec recovery and go on with flashing cm12.1 or cm13 if like :)
[Galaxy S II Original Android Development] makix13:
Perhaps this can be useful, all credits to [MENTION=5811506]gsstudios[/MENTION]

http://xdaforums.com/showthread.php?t=2994381

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] misterthe:
Is it possible that notifications show up on the lockscreen when I'm not using the phone? So that the display goes on without touching the phone.
[Galaxy S II Original Android Development] niftyspark:
Yes, but only via a third-party App; "https://play.google.com/store/apps/details?id=com.lukekorth.screennotifications"
[Galaxy S II Original Android Development] misterthe:
Awesome, works great! Thank you :)

Does it have a huge impact on the battery life?
[Galaxy S II Original Android Development] makix13:
in my case nils lock screen works great too.

Regards

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] chrisXL:
Are these apps similar to xposed "ambient display" module?
[Galaxy S II Original Android Development] makix13:
more or less, as xposed module, doesn't work when you pick up the phone, but I like Nils coz has more config options and less draining battery than xposed modules.

Has a lot of customization ,headup notification etc, in my experience it's great[emoji6]

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] WhiskeyBravo:
Hi,

I'm trying to upgrade to CM12.1 from stock Rom 4.1.2 (non-rooted; Buildnummer: JZO54K.I9100XWLSZ) by following the quoted procedure. As I ran into troubles and didn't found any useful advice searching the net / forum, I'm asking for your help.

At the second step, I'm getting a "Installation aborted" message with the error code "Status 7". Have I forgotten something to do before that step? Or does this recovery require root access?

In a second attempt: I also tried to flash an other recovery (PhilZ.cwm6.XWLSZ.OJC.5.15.9.signed.zip) according to the procedure provided in this thread, which, in my understanding, should provide me an KK-compitible rom directly from stock ROM. Thinking that I would then be able to continue with the 3rd step of the quoted procedure. But the installation is also aborted with the error message "Signature verification failed". Is this version maybe not compatible with device or this recovery need some further steps beforehand.

Thanks for your support.
[Galaxy S II Original Android Development] fireburner-de:
Don't really know about this procedure, but have you powered off and rebootet to recovery after step1?
[Galaxy S II Original Android Development] Klaus20:
When I try in TWRP to install something I just see the TWRP Logo and landing again in the main menu knows anybody how to fix it ??

Where can I find a TWRP 2.8.7.0 to flash with Odin ?

Regards Klaus

It is workin now --> stock_kernel_twrp_1120-signed-for_Odin.tar --> boot to system --> Recovery --Install is working again.
[Galaxy S II Original Android Development] WhiskeyBravo:
Yes, I did. But the first recovery is only temporary, so it's gone after the reboot and the stock recovery is back.
[Galaxy S II Original Android Development] the.gangster:
[MENTION=7308675]WhiskeyBravo[/MENTION]

You have to flash the other recovery from within the first (runtime) recovery.

So no reboot after step 1.
[Galaxy S II Original Android Development] WhiskeyBravo:
Yes, that's what I understood and acually did. The variant with reboot was a just try after I saw that it didn't worked the way you described. Do you have an idea what might went wrong?
[Galaxy S II Original Android Development] the.gangster:
[MENTION=7308675]WhiskeyBravo[/MENTION]

I used that method on my two S2 devices several times already and I can't remember to ever have seen an status 7 error using it.

So just to reassure: you are getting this error within the 3.00 runtime when you install the philz 6.48.4, right? Is there any other message displayed?
[Galaxy S II Original Android Development] WhiskeyBravo:
All the messages disapear very quickly. I've tried to record them on video to then read it out. I then saw the following message just before the status 7 error:

"E: Error in /sdcard/CM12/philz_touch_6.48.4-i9100.zip"

"(Status 7)"

So it might be a bad file (Source: First link on Google) . Can you provide me a link to your file? I already tried to redownload and replacing it on the sdcard.
[Galaxy S II Original Android Development] the.gangster:
Don't know where I downloaded it from back then. But it has following hashes:

MD5: 14d69a0b968b76ab8b8d0bb963c2aeea

SHA-1: c16a8434eb87f55a3ac46e6b4daa0013c5eb8d43
[Galaxy S II Original Android Development] WhiskeyBravo:
I don't see the SHA-1 code of the file. But the MD5 checksum is the same (at least the same code is stated on the site).

Do you have an other idea what I could try to do differently?
[Galaxy S II Original Android Development] the.gangster:
[MENTION=7308675]WhiskeyBravo[/MENTION]

you should check the hash of the file you downloaded.

Most filemanagers offer you to calculate these hash values.

Another possibility would be to try flashing stock_kernel_twrp_1020-signed.zip.

It's the last non-isorec-recovery I know. So this would install CM12.1 kernel and recovery.

Check, if that also fails.
[Galaxy S II Original Android Development] BenjyTec:
Anyone knows if there will be a last stable Snapshot? I saw that some other devices already got one, but the last for S2 still is from November last year, not even including Freezefix :/

Or will Cyanogenmod will put all their resources into Cm13?
[Galaxy S II Original Android Development] juapao:
To resolve your status 7 error code prompt, you should flash a kitkat compatible recovery it is based on a CWM recovery. it would be a best practice if your flashing kitkat - marshmallow based roms. there is also a thread here in xda about the converting .zip files to .tar files so it would be flashable via odin. I hope it helps.
[Galaxy S II Original Android Development] the.gangster:
[MENTION=5030336]juapao[/MENTION]

The goal was not to use Odin for flashing a kernel. The question is, why it failed on his device while this worked already many times on others'.
[Galaxy S II Original Android Development] juapao:
Sorry my bad, though to avoid "error status 7" code is to use a kitkat compatible recovery then after that flash the rom and the recovery that you desire to use. that's just afaik. I haven't encountered any issues after settling to that method.
[Galaxy S II Original Android Development] ChiliCN:
Hi guys,

I want to revert from cm13 but unfortunately I forgot to backup my 12.1 nightly rom. Do you know where I can download it again? On the cm download page all 12.1 nightlies are gone and the last snapshot is from 2015/11.

Thank you in advance
[Galaxy S II Original Android Development] the.gangster:
Search this thread for "20160203" and you'll find a link.
[Galaxy S II Original Android Development] ChiliCN:
Perfect, thank you.

http://xdaforums.com/showpost.php?p=65250980&postcount=3168
[Galaxy S II Original Android Development] falke69:
Just one question. Will there be any further updates for CM 12.1 like security updates or implementing trim enabled equal to todays CM13 ?
[Galaxy S II Original Android Development] JanJabko:
And if there will be, could the last one be made persistent on CM download page like snapshots? This would be easier to find.
[Galaxy S II Original Android Development] the.gangster:
I don't think this will ever happen. Everyone was waiting for that to happen with CM11 already, once CM12. 1 became official. Today we still see a totally outdated CM11Snapshot in the downloads, while the rock steady latest Nightlies never reappeared there.
[Galaxy S II Original Android Development] j1gga84:
Even CM13 will not get fully stable I think, because Android N will come this year and when this happens, every Dev will dash on it and develop only for CM14 (?) and will show CM13 the cold shoulder like it happened before, that is a big disadvantage of CyanogenMod in my opinion but okay, that is how development works ;)

Only my 2 cents an OT

regards
[Galaxy S II Original Android Development] daniu:
Hi

I wonder: what is "fully stable" and what is the problem with the latest existing nightlies?

I think the problem about nightlies is that you don't really know what you get. But after some time you can be pretty sure that people tested every corner of the software.

I wonder which bugs you guys would like to get removed from cm12.1...

I myself cannot really find annoying bugs in cm13 and see no reason not to use a nightly from - let's say 2 weeks ago (right now I would rather wait until trim integration is a little bit older) so that you know it's tested by the crowd ...

In my opinion: "fully stable" exists only with very simple software - considering the compiler will also not be "fully stable", the software that can claim to be "fully stable" must be even simpler as it has to be based on a very simple, fully stable compiler ...

Regards

Sent from my x-phone using brain 2.0
[Galaxy S II Original Android Development] makix13:
In my case only one issue with camera, I can't record any video in any resolution, tested with stock camera and other (opencamera) in any resolution and in internal or external SD. In any case I can live with it.

Perhaps it's a good idea a final snapshot with trim support for CM 12.1, but only it's my opinion. I'm moving to CM 13.0 [emoji6]

Regards

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] the.divergent:
I never had issues with camera recording on 5.1.1.

Regards
[Galaxy S II Original Android Development] KickerTom:
Are you using custom display density by any chance?

In my experience, video recording doesn't work with DPI lower than 200. That's unfortunately the case in CM13 as well (where you also get crashes from some Google Apps like contacts with low DPI number).
[Galaxy S II Original Android Development] makix13:
No, I didn't change it. Don't worry last night move to CM 13, doing tests know, I'll write here about it, till know everything goes great except v4a [emoji6].

S2 Cyanogenmod 6.0.1 [official nightly] - arnab isorec twrp - Xposed [official framework]
[Galaxy S II Original Android Development] the.divergent:
You just need to install busybox and V4A will work like charm.:)
[Galaxy S II Original Android Development] makix13:
I did that but something went wrong.

In LP I used v4a with selinux in enforcement mode, using supolicy from Chainfire and a script at boot without any issue.

But in CM13,I've got an issue

I'll report in Supersu thread if someone have an idea it will be great, sorry for the off-topic [emoji2]

S2 Cyanogenmod 6.0.1 [official nightly] - arnab isorec twrp - Xposed [official framework]
[Galaxy S II Original Android Development] the.divergent:
I did it on a different way. Just to make sure you have installed busybox, have you opened it and clicked on button install in bottom left corner? If you did it then ok. Now after this download apk Viper4Android(you can find it on XDA) and install it, open it, grant root access and app wil ask you do you want to install drivers, click on yes and wait a little bit, after no more than few minutes it will say that drivers are installed and you need to reboot your device. Reboot and V4A should be working, open it and set it as you want.
[Galaxy S II Original Android Development] makix13:
Yes, I did just you said, busybox and v4a steps, but the issue happened. I would like to run v4a in enforcement but I can't. I just write in Supersu thread, hope someone can help, I'll inform you about it, many thanks for your help[emoji122] [emoji106]

S2 Cyanogenmod 6.0.1 [official nightly] - arnab isorec twrp - Xposed [official framework]
[Galaxy S II Original Android Development] the.divergent:
Hope you will get it working!

---------- Post added at 11:01 AM ---------- Previous post was at 10:52 AM ----------

Just one more question, do you have SuperSU or built-in stock root on your phone? Becouse I think that SuperSU is not supporting Marshmallow yet.:)
[Galaxy S II Original Android Development] makix13:
I hope so, I'll report in CM13 thread, I find something similar and it seems it's necessary a patch in the kernel, fyi here it's the link to the problem : http://comments.gmane.org/gmane.comp.security.seandroid/2591

Thanks all

S2 Cyanogenmod 6.0.1 [official nightly] - arnab isorec twrp - Xposed [official framework]
[Galaxy S II Original Android Development] makix13:
Hi,

I'm using stock CM su, in both CM 12.1 & 13.

I configured it with supolicy and libsupol.so from Chainfire.

In CM 12.1 works great but in CM13 fails.

Well I'll continue with the investigation.

In the other hand, camera works great in CM13, and in whatsapp some issues with storage are solved after reinstall, reboot and restore backup.

Xposed works too, so apart v4a everything goes well, will see Bluetooth and GPS. [emoji6]

S2 Cyanogenmod 6.0.1 [official nightly] - arnab isorec twrp - Xposed [official framework]
[Galaxy S II Original Android Development] the.divergent:
I never had similiar issue, on my S2 V4A worked perectly on 5.1 and now on 6.0 too

Regards
[Galaxy S II Original Android Development] makix13:
Ojdanic sorry, is selinux in permissive or enforcement? Which v4a version do you install? Uhmm perhaps it's better move to 6.0.1 thread (I think we are spamming 5.1 thread[emoji23] )

Thanks mate for your answers & help

S2 Cyanogenmod 6.0.1 [official nightly] - arnab isorec twrp - Xposed [official framework]
[Galaxy S II Original Android Development] the.gangster:
### Warning

After testing twice myself and getting also 2 further reports I would like to warn:

Currently the newly published TWRP-3.0.0-0-Recovery can lead to boot loop.

(tested on cm-12.1-20160203-NIGHTLY-i9100 with kernel-Lanchon-TRIM-IsoRec-20160206-cm-12.1-i9100)
[Galaxy S II Original Android Development] DAusRon:
hi everyone..im currently on the latest cm12.1 nightly.

why sometimes i receive no incoming calls and after rebooting my phone, i'll receive notification message from my network provider that told me i've been called by xxxxx number?
[Galaxy S II Original Android Development] TheHaso:
I'm currently on latest CM12.1 snapshot, but people reporting in with a newer nightly build 2016xxxx.

I can't find this one in get.cm,, where can I don't this latest CM12.1 rom?
[Galaxy S II Original Android Development] alienflorina:
I'm on the snapshot as well. Just flash latest launchons kernels for 12.1 and you get freezefix, trim, isorec.. Basically anything you need.
[Galaxy S II Original Android Development] TheHaso:
I kinda want to try the 201603xx build as people claim using.
[Galaxy S II Original Android Development] falke69:
If you would read some pages back in this thread you would find it.

For example in the quote here.
[Galaxy S II Original Android Development] psychoid:
I cannot send sms, but can receive sms.. using latest build stock cm messaging app. Anyone knows how to fix?appreciate for the help ☺
[Galaxy S II Original Android Development] fireburner-de:
[MENTION=4273458]psychoid[/MENTION] Did you check SMS provider number.

Can't try if this works on CM12.1 (I run CM13 and there it doesn't work).

If not, maybe someone else knows, where one can manually set the SMS provider number.
[Galaxy S II Original Android Development] psychoid:
Yes, already did that all. But still, did not worked out ?. Tried with other sms app (google messenger) and got the same result.
[Galaxy S II Original Android Development] marzametal:
Any chance to get the Android Security Patch Level upgraded to 1st of March or even wait till 1st of April is available?
[Galaxy S II Original Android Development] fireburner-de:
[MENTION=5795738]marzametal[/MENTION] There are no more official builds for CM12.1. I don't know if the source is still being updated. If so, you could build it your own, otherwise maybe consider to upgrade to CM13.
[Galaxy S II Original Android Development] Karele:
Can i flash it using philz touch 3 recovery ?
[Galaxy S II Original Android Development] the.gangster:
No, but if you use touch 3 to flash e.g. a philz 6.48.4, then you can go on from there.
[Galaxy S II Original Android Development] MasterTim17:
I downloaded and installed the cyanogen mod update from 01.04 and now my device only show the samsung bootlogo. After that the installation of system pops up a short time and disappers. The device doesnt boot and doenst go into recovery mode.

Also the device isnt recognized on my computer, so i cant use odin.

What should i do??
[Galaxy S II Original Android Development] BenjyTec:
I think you have CM13, but this is the Cm12.1 thread. Check out the first post, there's the link to the CM13 thread, and search there.
[Galaxy S II Original Android Development] MasterTim17:
i had cm12.1. Does it update to cm13 over ota updates? i dont think so
[Galaxy S II Original Android Development] fireburner-de:
No, major Version steps do not work via OTA!!!

Have a look at this thread and read all carefully.

Recovery Mode is sometimes tricky to get with the button combination.

Concerning ODIN, try different PCs and Cables. This does not break through ROM flashing. (Has it ever been recognized properly? If not driver, cable or OS might the the problem)