[Q&A] [GT-I9190/I9195][ROM][Official][5.1.1] CyanogenMod 12.1 for S4 Mini 3G/LTE

[arco68]

Facebook fails to update on my tablet as well, so it's probably something broken with the update. The feedback on the play store indicates this as well.

 

[davidmlondon]

As long as it's working :thumbup:

 

[patrik.sebest]

Nice

 

[nsw42]

Google apps ... no luck at all ...

Hello there,
I recently installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1K3-serranoltexx.zip on my GT-I9195, Galaxy S4 mini; which worked fine.
But then I tried to add Google Apps; and keep falling:
open_gapps-arm-5.1-stock-20151219.zip or open_gapps-arm-5.1-pico-20151219.zip ... installs fine; but when system comes up afterwards; there is an endless chain of
"Unfortunately app xyz has stopped" (for pico, it is just the setup wizard, backup service and so on; but well: all the new apps keep failing; so the phone pretty much turns useless).
I then tried to install gapps-lp-20150314.zip; but that fails already during installation with TWRP.
I then thought about downloading the "mini gapps" as mentioned in comment #430; but unfortunately (again; i start to hate this word) ... the link is down.
EDIT: I downloaded the APKs for google services; and play store from androidsapksfree.com ... both can be installed ... and when I restart the mobile; I am told "Unfortunately Google Play services has stopped". Wtf?!
Any ideas, anybody?

 

[sameeradush]

Cannot Flash cm 13 updates using TWRP

I have installed first cm13 nightly using TWRP without any issue. It worked fine. But now I cannot update it to any new cm 13 update neither I can't flash the same zip again using TWRP. I can install cm 12.1 nightlies though. Anyone experienced this? I am posting here because cm 13 thread does not have a Q&A section and I am not permitted to post there

 

[Goncalot]

Please help...


I've just installed the Dec. 26 update and my GTI9195 became unusable, did it the same way I always do (CM updater) and now Gapps are stopping, no sim card is detected and I was reading the original tread and noticed that the dev's aren't doing any more updates for now.... I´m on CM13.0-20151226 and I´ve erased all the previous versions so now I can't go back to the version I had.
Any advice? Thank You in advance
GE

 

[Hyst]

I've just installed the Dec. 26 update and my GTI9195 became unusable, did it the same way I always do (CM updater) and now Gapps are stopping, no sim card is detected and I was reading the original tread and noticed that the dev's aren't doing any more updates for now.... I´m on CM13.0-20151226 and I´ve erased all the previous versions so now I can't go back to the version I had.
Any advice? Thank You in advance
GE

Read the filename carefully. Dez 26 is cm13 and not cm12.1. Meaning you have to flash the gapps for marshmallow.
Maybe this helps already. But dirty flashing major releases often leads to problems. So probably flashing the right gapps does not solve all the problems.

Do you have a nandroid backup?

I assume, you don't. As you would probably restored the backup already.
If not, you might want to do a clean install. Backup your stuff first with titanium. Or do a nandroid backup and later extract what you need with some nandroid explorer app or something.

Maybe someone has an older cm12.1 version he or she could upload, so that you can downgrade. But as I said before, you probably run into problems anyway, as the damage is already done.
But I think doing a clean install of either cm12.1 or cm13 would solve your problems

Without trying to patronize you... BUT:
Always do a backup, always keep older versions somewhere, so that you can go back if you need to.
Or more general: keep in mind that sometimes things goes wrong and prepare.
I guess you learned this the hard way now.

 

[Goncalot]

Solved

Read the filename carefully. Dez 26 is cm13 and not cm12.1. Meaning you have to flash the gapps for marshmallow.

Without trying to patronize you... BUT:
Always do a backup, always keep older versions somewhere, so that you can go back if you need to.
Or more general: keep in mind that sometimes things goes wrong and prepare.
I guess you learned this the hard way now.

Thanks for you reply. As I have done in the past multiple upates without checking the file names, didn't bother to do a backup as there was nothing that made me think that this was a major upgrade... Been away from the forum for too long (stupid me!).
Followed you advice and re-flashed everything and i'm on CM13 6.0.1 with no problems so far other that my headset (hm1200) that doesn't work on this build, any advice on that? Thank You yet again.
GE

 

[andy3103]

Gapps

Hi,
I did a clean install to cm 13 but now Ehen i installiert open gapps 6 every Google service stops Witz an error. Seems to be missing permissions? Anyone knowing how to fix this?

 

[nsw42]

Not sure, how but in the end it worked for me

Hi,
I did a clean install to cm 13 but now Ehen i installiert open gapps 6 every Google service stops Witz an error. Seems to be missing permissions? Anyone knowing how to fix this?

I encountered similar issues.

In the end, I did:
* install twrp 2.8.7
* downloaded and installed the latest CM 13 nightly ... together with google apps 6 arm pico ....

See here forum dot cyanogenmod dot org/topic/119740-google-play-service-crash-serveral-times/

 

[xdeverett]

Super user breaks after nightly update

I am not very knowledgeable with the android operating system as a whole, I tried to learn as much as I can but mostly just wanted functionality so I installed cm12.1 for simplicity and root capabilities. Everything was going fine until one day the superuser built into cm12 stopped working after a nightly update, I didn't know what to do, so I tried downloading the app superuser from the play store. When I launched the app there was a notification saying the binaries needed updating and it wasn't working so I found the xda tread for SU 2.46 and downloaded it from chainfire's website. Then everything was back to normal, root checker was showing proper root and all apps were working fine.

When I updated to the current nightly (20151229) and booted back up I had the same problem where root checker shows no root and none of my apps work. So I thought all I need to do is reflash the binaries for SU. After I selected to reboot but right after the s4 mini screen it goes to a black screen and stays there.

Just reading about superuser now, I read that there can only be one super user method so I am thinking that when I downloaded SU from the play store I broke the cm12 internal rooting method, which caused real problems when I flashed the nightly as it overwrote that new method.

What I don't get is why cm12's superuser stopped working in the first place? If somebody knows what I am doing wrong I would really appreciate the help!

My plan as of now is to try and remove the app cleanly remove the app superuser and hopefully restore function to the in built cm12 superuser.

PLEASE HELP :cyclops:

 

[arco68]

Nightly 20151229 is CM13.

 

[tchavei]

So there is no way of transitioning to cm 13 without a full wipe? Arg, that sucks

 

[Royal Ranger]

So there is no way of transitioning to cm 13 without a full wipe? Arg, that sucks

I thought i'd give it a try and dirty flashed cm13 over the latest cm12.1 nightly. root works properly (without superuser, which i also didnt use on cm12.1). At the beginning some apps crashed but wiping app data helped.

Now the only bugs i have are
- not working screen rotation
- Battery settings crash

Keep up the good work

Sent from my GT-I9195 using XDA Free mobile app

 

[tchavei]

Thx for the info

 

[echo124]

---

 

[XerotoHero]

CM13.0 Bluetooth is crap.

I would have posted this to the 13.0 thread but I don't have 10 posts yet... I recently updated to CM13.0 nightly 20160121) and have had nothing but issues with Bluetooth. Apparently this is a MM issue generally and is not restricted to just our phones. FWIW, I've done a clean re-install, reset BT on all devices, (Sony car audio, OT Big Turtle Shell, Sync), disabled HCI snoop log in Dev Options, shut off WiFi and I have managed to successfully have music pour forth correctly once. Calls seem to be unaffected thus far but I've only had two. Any ideas on what to try next aside from reverting back to Lollipop?

 

[flipeicl]

Can I wipe the internal memory to clean all trash from old rom flashs and install a new one without problem?