Related
Huh. Just noticed the international version of the Optimus G is now officially supported by CM (via nightly builds):
get.cm/?device=e975
Does this mean we may be seeing the unofficial E971/E973 moving more toward the official side?
Edit: typos and grammar.
Sent through the magic of an LG Optimus G (E971) running RootBox 4.2.2.
Ive already tried the nigtly build, unlike the chad's version, official one doesnt work lol
To be honest it works, but screen showing nothing.
Is the CM team and chad working together? Or are these 2 completely different builds?
Tim4 said:
Ive already tried the nigtly build, unlike the chad's version, official one doesnt work lol
To be honest it works, but screen showing nothing.
Click to expand...
Click to collapse
What do you mean by that?
Gesendet von meinem GT-I9000 mit Tapatalk 2
haasgo said:
What do you mean by that?
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
chad's version:
http://forum.xda-developers.com/showthread.php?t=2229806
It's very stable and nearly completely full-featured apart from phone, notification LED and some modem issues. I'm running it as my daily driver.
As for what Tim is saying, I'm assuming he wants to say that the official version is less complete than chad's version...
I mean on the nightly one, all i can see is nothing but just black screen.
I just found that tread on Google because I was looking for a working CWM for the E975. Does anybody has experience with that CWM?
http://donandroid.com/how-to-install-cm-10-1-on-lg-optimus-g-e975-1016
Edit: It works .
How's the battery life compared to stock rom?
i do not flash this rom dated April 14 by TWRP, why that?
Folowing Ricardo's post on Google + announcing the official CM10.1 for E975, I said give it a try.
I had installed the ClockworkMod from the Play Store (the premium version), I flashed the CWM touch recovery for E975 (in app payment), booted in recovery and installed the official CM10.1 zip.
Rebooted and... bootloop!
The Cyanogenmod logo was spinning but it would not start.
So I got my first softbrick with E975.
I had to reflash the official kzd, reroot, unlock bootloader.
For now I will stay with the official 4.1.2 stock ROM.
I hope that CM10.1 will work with the TWRP and then I'll give it a try.
Just use FreeGee to unlock, reboot and flash. Works everytime
Sent from my LG-E975 w. CM10.1 using xda premium
goodmamba said:
Folowing Ricardo's post on Google + announcing the official CM10.1 for E975, I said give it a try.
I had installed the ClockworkMod from the Play Store (the premium version), I flashed the CWM touch recovery for E975 (in app payment), booted in recovery and installed the official CM10.1 zip.
Rebooted and... bootloop!
The Cyanogenmod logo was spinning but it would not start.
So I got my first softbrick with E975.
I had to reflash the official kzd, reroot, unlock bootloader.
For now I will stay with the official 4.1.2 stock ROM.
I hope that CM10.1 will work with the TWRP and then I'll give it a try.
Click to expand...
Click to collapse
Did you do a factory reset from recovery? This step is very important otherwise you end with a bootloop. So you just had to reboot in recovery and wipe data or do factory reset and reboot.
The ROM is working 100%. Fully working 13 megapixel camera and very smooth.
The easiest way is:
Use FreeGee from Play Store and free your device (void your warranty)
Download RomManger from Play store and flash CWM recovery. Not TWRP !!!
Put the ROM on your Internal storage Download here: http://get.cm/?device=e975
Put Gapps for jb 4.2.2 (20120301) on internal storage Download here: http://goo.im/gapps
Reboot to recovery (Keep Volume up while rebooting and press the Volume down rocker two times and press Power button)
Select option “install zip from sdcard”
Then select “choose zip from sdcard”
Flash CM10.1 rom.
Flash Gapps package.
Go back to main screen in recovery
Important step !!! - Select FACTORY RESET in Recovery and press Power button - !!!
Reboot into system
Enjoy CM 10.1 on your LG OG E975
goodmamba said:
Folowing Ricardo's post on Google + announcing the official CM10.1 for E975, I said give it a try.
I had installed the ClockworkMod from the Play Store (the premium version), I flashed the CWM touch recovery for E975 (in app payment), booted in recovery and installed the official CM10.1 zip.
Rebooted and... bootloop!
The Cyanogenmod logo was spinning but it would not start.
So I got my first softbrick with E975.
I had to reflash the official kzd, reroot, unlock bootloader.
For now I will stay with the official 4.1.2 stock ROM.
I hope that CM10.1 will work with the TWRP and then I'll give it a try.
Click to expand...
Click to collapse
there shouldn't be a reason why CM10.1 from Ricardo won't work with TWRP, u should flash it, and gapps then reboot ur phone, ofc clear cache, dalvik cache and that
puma99dk| said:
there shouldn't be a reason why CM10.1 from Ricardo won't work with TWRP, u should flash it, and gapps then reboot ur phone, ofc clear cache, dalvik cache and that
Click to expand...
Click to collapse
I tried myself and it didn't work with TWRP. Wrong device id E975...
Best to read his Google+ Blog. So I found out myself.
After flashing CWM the ROM flashed fine. The ROM works fine. And I have 13 megapixel camera with focus.
Just delete the phone checking from update script
Are there any issues if you dirty flash from an unofficial 10.1 build to the official 10.1 nightly?
Yeah, it stucks at boot logo. For me at least.
Never dirth flash from another rom.
Thats a NO GO
Sent from your moms bed!
There is no reason for dirty flash anyway as you get all settings back from Google right after install? And if you make backups of your data omce in a while you loose nothing.
You should know, that old settings can screw with a new flash aswell. Then you will need to clear the old data from some apps ( like youtube ).
Thats why a total clean flash without saved data ( from google ) is the best
Then its also easier for a dev to find the right bugs, if there are some
I have just flashed cm-11-20140118-NIGHTLY-endeavoru, gapps-kk-20140105-signed and recovery-6.0.4.5-endeavoru.img. Now I get stuck at the CM logo, it just keep spinning around. From what I can read online, it should work, and does work for other users. But no matter what I do, I cannot get past the boot animation.
Does anyone have any idea as to why that is. Everything is done right. I have flashed several ROMs many time sover on my HOX, and bootloop has always been resolved by flashing boot.img via Fastboot, but that does not work either.
Did a complete full wipe before?
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
Did a complete full wipe before?
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
Wiping of data should never be a requirement. But I did wipe/hard reset after installing CM.
shopperen said:
Wiping of data should never be a requirement. But I did wipe/hard reset after installing CM.
Click to expand...
Click to collapse
If you flash a new ROM its always better to wipe data and format system.... Or just factory reset in recovery will be enough
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
If you flash a new ROM its always better to wipe data and format system.... Or just factory reset in recovery will be enough
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
It is often a solution to several issues yes, but it is not better. No official System Updates ever requires factory reset. Not that it really matters, if that would be the requirement, then okay. I just think it is a bit amateurish of Cyanogen Inc. not to have resolved that yet. And in any case, it does not work. I think it is because my phone is for the Scandinavian market, and there might be something different, since I cannot find anyone from the cold north who have managed to install CM11 on their HTC One X.
Flashed boot.img?
Sent from my C6903 using Tapatalk
tomascus said:
Flashed boot.img?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Already tried that. Perhaps CM11 requirs S-Off to work.
shopperen said:
Already tried that. Perhaps CM11 requirs S-Off to work.
Click to expand...
Click to collapse
No it doesn't require otherwise nearly no one could flash it...like I said...also flash philz latest recovery and do a complete full wipe...including factory reset and format system...
Then flash the ROM again and afterwards the gapps .. It SHOULD work then...you NEED to do factory reset in recovery!!!
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
No it doesn't require otherwise nearly no one could flash it...like I said...also flash philz latest recovery and do a complete full wipe...including factory reset and format system...
Then flash the ROM again and afterwards the gapps .. It SHOULD work then...you NEED to do factory reset in recovery!!!
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
I have already tried all of that. It does not work. When stuck in boot animation for CM, it is usually because you have flashed the wrong ROM for your device. Since that is not the case here, I do believe that Cyanogen Inc. just haven't made the CM11 compatible with the European market version of the HTC One X.
shopperen said:
I have already tried all of that. It does not work. When stuck in boot animation for CM, it is usually because you have flashed the wrong ROM for your device. Since that is not the case here, I do believe that Cyanogen Inc. just haven't made the CM11 compatible with the European market version of the HTC One X.
Click to expand...
Click to collapse
Completely wrong...its already compatible since its out...since 24th December.... Its working for all so you are doing something wrong...try another gapps package like that from paranoid android...it should work...or flash a custom kernel like audahadi's aosp kernel and maybe then it works......but at first try also fastboot erase cache...that helps often too
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
Completely wrong...its already compatible since its out...since 24th December.... Its working for all so you are doing something wrong...try another gapps package like that from paranoid android...it should work...or flash a custom kernel like audahadi's aosp kernel and maybe then it works......but at first try also fastboot erase cache...that helps often too
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
I really appreciate all the advice. It can often be difficult to find help with these kind of issues. But truth be told, CM isn't worth all that effort. I have a stock LG G2, and it runs perfectly with root. So I may try another kernel, but that will be the final thing I'll try. I have already invested 6+ hours in this, and unless Cyanogen Inc starts offering official support within the community, I am just going to stick to stock ROMs. Fastboot erase cache is something I haven't tried either, but that shouldn't make a difference after a factory reset.
Again thank your for your responses and assistance. But I am stopping here.
shopperen said:
I really appreciate all the advice. It can often be difficult to find help with these kind of issues. But truth be told, CM isn't worth all that effort. I have a stock LG G2, and it runs perfectly with root. So I may try another kernel, but that will be the final thing I'll try. I have already invested 6+ hours in this, and unless Cyanogen Inc starts offering official support within the community, I am just going to stick to stock ROMs. Fastboot erase cache is something I haven't tried either, but that shouldn't make a difference after a factory reset.
Again thank your for your responses and assistance. But I am stopping here.
Click to expand...
Click to collapse
Cm11 is already official for our device.. Fastboot erase cache is deleting the cache for flashing...and that can prevent from booting ...the cache which will be wiped in recovery is for data bla bla for the apps etc..but the cache which is erased in fast boot is also in another place...
If you have a LG G2 why then still using and trying to flash roms on hox? ...I also flashed the different cm11 Roms and never had any problems with not booting etc..
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
Cm11 is already official for our device.. Fastboot erase cache is deleting the cache for flashing...and that can prevent from booting ...the cache which will be wiped in recovery is for data bla bla for the apps etc..but the cache which is erased in fast boot is also in another place...
If you have a LG G2 why then still using and trying to flash roms on hox? ...I also flashed the different cm11 Roms and never had any problems with not booting etc..
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
Because I really like my HOX. It is still the best smartphone I have ever had. So I thought it could get an life extension via CM11, since Android 4.4 requires less memory to run and is more battery efficient. But appearently it's just not working on my phone. I will try fastboot erase cache and maybe another kernel when I get home from work today.
It works! I have no idea what I did different. Just redid everything I have tried over the past few days again, and this time it worked. Maybe there was an issue with my computer, it had been running for 4 days without reboot.
shopperen said:
It works! I have no idea what I did different. Just redid everything I have tried over the past few days again, and this time it worked. Maybe there was an issue with my computer, it had been running for 4 days without reboot.
Click to expand...
Click to collapse
HI I've got same issue on my HTC One S (Ville).
I upgraded CWM to latest version (6.0.4.8) and done that:
- Wipe data / factory reset
- Wipe dalvik cache
- Install CM11 from zip + Gapps from zip
- Wipe data/ factory reste (again)
but I'm still stuck on rotating Cyanogen logo...
Any idea ?
julien.gresse said:
HI I've got same issue on my HTC One S (Ville).
I upgraded CWM to latest version (6.0.4.8) and done that:
- Wipe data / factory reset
- Wipe dalvik cache
- Install CM11 from zip + Gapps from zip
- Wipe data/ factory reste (again)
but I'm still stuck on rotating Cyanogen logo...
Any idea ?
Click to expand...
Click to collapse
If you wipe data/factory reset after flashing the Rom you dont need to wonder yourself why it's not working flash the Rom and the gapps again and if boot.img needs to be flashed via fastboot do it otherwise just reboot...man really xD
Gesendet von meinem HTC One_M8 mit Tapatalk
One-M8-Master said:
If you wipe data/factory reset after flashing the Rom you dont need to wonder yourself why it's not working flash the Rom and the gapps again and if boot.img needs to be flashed via fastboot do it otherwise just reboot...man really xD
Gesendet von meinem HTC One_M8 mit Tapatalk
Click to expand...
Click to collapse
I feel really stupid...
Reading too much posts about wiping after flashing ROM. Sometimes ot's good to know what I'm doing.
About boot.img: do you take it from latest Android SDK ?
I may have a problem to connect my phone on my Windows 8: is there another way with CWM to flash boot.img without using factboot command ?
julien.gresse said:
I feel really stupid...
Reading too much posts about wiping after flashing ROM. Sometimes ot's good to know what I'm doing.
About boot.img: do you take it from latest Android SDK ?
I may have a problem to connect my phone on my Windows 8: is there another way with CWM to flash boot.img without using factboot command ?
Click to expand...
Click to collapse
Wiping after flashing Rom means wiping cache and dalvik cache...second if you really have the HTC Ville go to its forum...also you have to take the boot.img from the Rom.zip not from any sdk...and yea for drivers etc go to HTC Ville thread or one s forum
Gesendet von meinem HTC One_M8 mit Tapatalk
I had the same issue, tried to load CM11 a couple of times, coming from Viper. I knew I had done it all in order.
Kept retrying and then it just took. Strange, but I'm loving it now.
UPDATE!
The bootloop was caused by a low hboot number, i flashed android revolution and it is now working! thanks for your help! when i sell my crap iphone, imma donate to you leefear!
well,
that's my first post, and i'm french so for further error and inapropriate thing excuse me :angel:
I have the beautifull LG g pro, french model so it's e986. when I flash for the first time a rom on this phone (liquid/jellysmooth) I didn't get any problem at all...
you see the problem begin when I flash xperianze rom, it's not exactly a flashable zip but a backup, so I carrefully did a full wipe data/cache then format system then wipe dalvik cache.
when the phone reboot everything was ok until I see that i don't have any signal, it was because of my imei who disapeared...
so i decided to return to paranoid rom...same thing again...
after that i reflashed jellysmooth, everything seems to be ok until the phone reboot...
And here the phone freeze on the boot image!! and this is for every rom I flash! (CM11,10.2,10.3, PAC ,PA, Carbonrom, mokee... etc etc)
so the problem is not on the package,I think it's only on the boot.img, it freeze at the middle of the animation and then reboot again and again...
I tried philztouch, CWM with freegee, with 2nd-init, twrp 2.6 etc etc....
however don't worry about my imei I just recover it with flashtool so for now I'm on stock rom...
but you guess how much custom rom miss me :crying:
To resume, it's impossible to flash any custom rom without having a bootloop because of a freeze in the animation boot.
I noticed also that when i root a fresh stock recover from flashtool and install cwm, i can only flash 1 custom rom, jellysmooth worked for me after a return to stock rom. but when i want to flash another rom after that, I get this problem again ...
i'm not a novice, I didn't make an error like forgeting to wipe something because i did lot's of try ,in fact I have flashed more than 80roms with around 6 devices, because i want to find the best one (especially for game like real racing 3) but it's not the problem right?
So, please can you help me? :fingers-crossed:
Ho came on guy ! ?
Sent from my LG-E986 using XDA Premium 4 mobile app
Hi all,
I have an international (Asia_TW CID__621) HOX. After running CM10.1 for the past while I decided to try CM11. I was at hboot 1.33 so I needed to take care of that first so I found out how to do so by flashing a nandroid backup and allowing it to update to the most recent stock ROM. All was well with the up to date HTC Sense ROM however I still decided to move to CM11 which I did. After a few bugs in CM11 that I didn't like I've decided to give the stock rom a shot again however I am running into a few issues.
I re-flashed the same nandroid backup as I did previously as well as boot and recovery images. Now I boot into the stock rom and the touchscreen does not work. Not the end of the world, I plugged in an OTA USB cable with a mouse and used my mouse to setup the phone, I then made the phone check for an update and one was found and it downloaded, rebooted, installed, rebooted, and I am back into the OS again however I still have no mouse and even worse I have no data or wifi either and they can not be enabled.
Anyone have any idea what I have done wrong? Do I need a different kernel or something? I believe that even after the first update the hboot was still at 1.33. Do I need to move the hboot back to a previous version? What to do what to do?
Thanks xda for your help.
You can't lower the hboot without s-off...try to get a nandroid backup for your new main version which is for hboot 1.7x and restore it...be sure to flash the boot.IMG of that backup...then all should work..
Gesendet von meinem One X mit Tapatalk
One-X-master said:
You can't lower the hboot without s-off...try to get a nandroid backup for your new main version which is for hboot 1.7x and restore it...be sure to flash the boot.IMG of that backup...then all should work..
Gesendet von meinem One X mit Tapatalk
Click to expand...
Click to collapse
Thanks for the response One-X-master.
I managed to do just that shortly after posting. I re-read the "Getting back to stock" thread here http://forum.xda-developers.com/showthread.php?t=1859714 and then I downloaded the CID__621 Nandroid Backup 4.18.950.2 from THIS THREAD. I extracted it, flashed boot.img via fastboot, copied it to /sdcardo/clockworkmod/backup/ and restored via recovery, and also flashed the recovery.img that was in the nand backup although it is not the stock recovery. I'm still looking for the 4.18.950.2 recovery image however everything is working now and there are no pending updates so not having the current recovery isn't the end of the world right now
https://www.dropbox.com/s/h0kko0c304992w7/Stock recovery 4.18.img
This should do the trick whenever you need it.
Mr Hofs said:
https://www.dropbox.com/s/h0kko0c304992w7/Stock recovery 4.18.img
This should do the trick whenever you need it.
Click to expand...
Click to collapse
Thanks Mr Hofs
Q&A for [GT-I9190/I9195][ROM][Official][5.1.1] CyanogenMod 12.1 for S4 Mini 3G/LTE
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GT-I9190/I9195][ROM][Official][5.1.1] CyanogenMod 12.1 for S4 Mini 3G/LTE. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
cm 12.1 color bug
Hi!
Yesterday i installed 12.1 nightly version. After that many app has color bug. For example simcity build it, and nova launcher (when i want to change wallpaper). Red color hanges to blue and the other colors wrong too.
Is there any solution?
Otherwise the system works smoothly and i haven't faced any other bug yet.
step 3 & 4
Hi
"3) Flash cm-12*.zip. " do you mean Copy the zip to your device SD card, then install zip? I do it, but I don't see the zip files on my card in recovery mode...
idem step 4)
need help
thanks!
Burl0743 said:
Hi
"3) Flash cm-12*.zip. " do you mean Copy the zip to your device SD card, then install zip? I do it, but I don't see the zip files on my card in recovery mode...
idem step 4)
need help
thanks!
Click to expand...
Click to collapse
When you download a file, the file qoes in a map. Under recovery you should move to this map and install.
Envoyé de mon GT-P5110 en utilisant Tapatalk
Hy
First of all thanks for updating cm tot 12.1.
I have played with some settings , and now i have changed my recovery into the recovery from cyanogen. But i cant flash gapps or xposed with this recovery. Is this normal?
If so i wil go back tot custom recovery. Witch one do you guys recomadate. Cwm or twrp
Thanks
_nicolas_ said:
Hy
First of all thanks for updating cm tot 12.1.
I have played with some settings , and now i have changed my recovery into the recovery from cyanogen. But i cant flash gapps or xposed with this recovery. Is this normal?
If so i wil go back tot custom recovery. Witch one do you guys recomadate. Cwm or twrp
Thanks
Click to expand...
Click to collapse
I use TWRP 2.8.5.0 and I can add the gapps to my device.
Envoyé de mon GT-P5110 en utilisant Tapatalk
Has anyone tested whether Bluetooth works? I want to get some BT headphones but have no BT devices to test with 12.1. Thanks :thumbup:
Sent from my GT-I9195 using XDA Free mobile app
I did a dirty flash from Unofficial from @F4k's , have to say, still nog encountered any problems, even Xposed is working well
Problems with wi-fi
Quote:
Originally Posted by zishan.iqbal
Hi Guys,
I just flashed this ROM yesterday from stock with a total clean wipe. I have issues with signal now. I'm based in the UK and on the signal bar i get this "!" and no apps work at all until i enable wifi.
baseband i have is - I9195XXUBML1
Any suggestions please.
Thanks is advance
End Quote
Same happened to me (also with cm12.0)
Frabati said:
Quote:
Originally Posted by zishan.iqbal
Hi Guys,
I just flashed this ROM yesterday from stock with a total clean wipe. I have issues with signal now. I'm based in the UK and on the signal bar i get this "!" and no apps work at all until i enable wifi.
baseband i have is - I9195XXUBML1
Any suggestions please.
Thanks is advance
End Quote
Same happened to me (also with cm12.0)
Click to expand...
Click to collapse
Update your modem.
[MODEM][ODIN] SGS4-mini I9195
Good luck
Question
this rom have Bug??
Hi,
Want to say thank you for the continued support. I must say that I was a little impatient in waiting hihi .
I have a WiFi issue though. When I dirty flashed, it was working just as flawlessly as with 12, but after a forced reboot, it won't stay connected. If I push power, it'll go off, getting a "no internet access" in WiFi settings. I have to reconnect it, sometimes several times, and sometimes it'll drop out while it's on, and in the middle of a download/upload.
I reflashed the kernel, thinking it might be a driver issue, but no go. I've no idea what's up.
---------- Post added at 10:43 ---------- Previous post was at 10:42 ----------
I just rebooted the phone, and it's worse, it won't stay connected, even on the 2.4 MHz band, without the icon changing.
Google apps stopped working after upgrade from cm12 to cm12.1
Hi everyone. I have a s4 mini i9195 cnk4 with clockwork recovery 6.0.5.1. I was using the cm12 and decided to update to 12.1. I flashed the update and since then the google apps stopped working. The notifications doesn't let me do anything with my phone. I tried to flash other gapps but the problem persists. I tried to flash back to cm12 but there was no change. Is there a way to fix this without a hard reset of the device?
tkontonis said:
Hi everyone. I have a s4 mini i9195 cnk4 with clockwork recovery 6.0.5.1. I was using the cm12 and decided to update to 12.1. I flashed the update and since then the google apps stopped working. The notifications doesn't let me do anything with my phone. I tried to flash other gapps but the problem persists. I tried to flash back to cm12 but there was no change. Is there a way to fix this without a hard reset of the device?
Click to expand...
Click to collapse
Do you have a backup of your latest ROM?
Try to do a clean flash and use 5.1 gapps. I had the same (?) problem using 5.0 gapps and after a clean flash and 5.1 gapps everything is ok . I flashed all the nightlys since then.
Envoyé de mon GT-P5110 en utilisant Tapatalk
trying to avoid a clean install
hollandais said:
Do you have a backup of your latest ROM?
Try to do a clean flash and use 5.1 gapps. I had the same (?) problem using 5.0 gapps and after a clean flash and 5.1 gapps everything is ok . I flashed all the nightlys since then.
Envoyé de mon GT-P5110 en utilisant Tapatalk
Click to expand...
Click to collapse
I'm trying to avoid a clean install. But if there is no other way i will do one. I'm just trying to find another solution.
@tkontonis: Just wipe /system, not /data, then flash ROM and correct gapps.
This will not affect your configuration and user data and will probably fix your issues. Make a backup, just because.
Google apps stopped working after upgrade from cm12 to cm12.1
tkontonis said:
I'm trying to avoid a clean install. But if there is no other way i will do one. I'm just trying to find another solution.
Click to expand...
Click to collapse
After numerous attempts and flashes i didn't find any way that i could make google apps work again. So i did a clean install of the latest cm12.1 and google apps and it works fine. Now i have to reinstall everything from the top.
tkontonis said:
After numerous attempts and flashes i didn't find any way that i could make google apps work again. So i did a clean install of the latest cm12.1 and google apps and it works fine. Now i have to reinstall everything from the top.
Click to expand...
Click to collapse
That's what I mostly do with a new(er) ROM.
Envoyé de mon GT-P5110 en utilisant Tapatalk
And that is why the paid version of Titanium Backup is really worth the money.
Google apps stopped working after upgrade from cm12 to cm12.1
michelsberg said:
@tkontonis: Just wipe /system, not /data, then flash ROM and correct gapps.
This will not affect your configuration and user data and will probably fix your issues. Make a backup, just because.
Click to expand...
Click to collapse
I had to install TWRP recovery because clockwork doesn't have a system format only cache. Sadly this didn't work either. I flashed only CM so that I could use the phone with no notifications but i couldn't see my apps. When i install gapps, and I tried 7 different ones, the problem returns.