[CM10] Build 201211-11-NIGHTLY-d2att Launcher options missing. - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Generally whenever I install a new rom (update or not) I will use the following steps:
download rom / put on sd
Wipe data / factory reset
Wipe dalvik and cache partition
Format System
flash rom
flash gapps
Reboot
This has always worked without fail and in this case it seems to have worked again.
However, I noticed in my settings menu that I no longer have "launcher options" under interface. Has this option been removed from the newest nightly? or has something gone wrong during my flash?
Used:
clockwork-6.0.1.2-d2att
cm-10-20121111-NIGHTLY-d2att
JB-4.2-Gapps-signed.zip
Phone:
Samsung Galaxy S3 SGH 1747
Carrier: Bell
EDIT: Also receiving: Android is upgrading, starting apps on every single reboot. Still loads fine but minor annoyance.
EDIT2: Figured it out, installing the 4.2 gapps was causing all problems. Reverted back to the 4.1.2 gapps and everything is fine. Thread can be closed.
SOLVED!

Could I ask: Did you have to reflash the ROM to fix this? Or just flash an older version of the gapps?
I have the same problem and just got all my apps back ... would rather not have reflash the ROM and then restore everything if I don't have to.
Jalopy
djjohnnyblaze said:
Generally whenever I install a new rom (update or not) I will use the following steps:
download rom / put on sd
Wipe data / factory reset
Wipe dalvik and cache partition
Format System
flash rom
flash gapps
Reboot
This has always worked without fail and in this case it seems to have worked again.
However, I noticed in my settings menu that I no longer have "launcher options" under interface. Has this option been removed from the newest nightly? or has something gone wrong during my flash?
Used:
clockwork-6.0.1.2-d2att
cm-10-20121111-NIGHTLY-d2att
JB-4.2-Gapps-signed.zip
Phone:
Samsung Galaxy S3 SGH 1747
Carrier: Bell
EDIT: Also receiving: Android is upgrading, starting apps on every single reboot. Still loads fine but minor annoyance.
EDIT2: Figured it out, installing the 4.2 gapps was causing all problems. Reverted back to the 4.1.2 gapps and everything is fine. Thread can be closed.
SOLVED!
Click to expand...
Click to collapse

JalopyPilot said:
Could I ask: Did you have to reflash the ROM to fix this? Or just flash an older version of the gapps?
I have the same problem and just got all my apps back ... would rather not have reflash the ROM and then restore everything if I don't have to.
Jalopy
Click to expand...
Click to collapse
You do not have to wipe data if the rom is the same. Just wipe cache/dalvik and then reflash rom/gapps 4.1.2.

Installing home2launcher will also wipe away your option of launcher under settings. Which is unfortunate.
Sent from my SGH-I747 using xda app-developers app

Related

[Q] CM10.0.0 d2att / gapps-jb-20121011-signed (Gapps will NOT install)

I have recently installed the new stable version of CM10 that was released today. The rom seems to be working fine but i cannot for the life of me get the gapps to install.
here are the steps I have followed to do a FULL CLEAN wipe.
Phone being used: S3 1747 att / Carrier:Bell
Rom=cm-10.0.0-d2att.zip
Gapps=gapps-jb-20121011-signed.zip
CWM= d2att 6.0.1.4 touch
1- Boot into recovery
2- Wipe cache
3- Under advanced wipe dalvik cache / battery stats
4- Under mounts: format system, data, and cache
5- Flash the ROM's zip file
6- Flash the gapps zip file
7- Reboot
This has always worked for me and i have no idea why the Gapps will not instal. Does anyone have any idea why this might be? Ive tried 3 times now. Thanks in advance!
EDIT: forgot to mention, the actual install within Clockwork recovery goes fine but when I boot into the rom and check my apps, the gapps are not present. Sorry for any confusion.
Check to make sure signature verification isn't turned off. If it continues, try twrp recovery (to rule out a recovery issue).
Thanks for the quick reply!
I turned signature checking on in ClockWorkMod, Reflashed gapps, wiped cache, dalvik cache and fixed permissions. Still does not work.
I then installed TWRP Recovery (latest version for d2att) Factory reset, Wiped cache, Wiped System, Wiped Dalvik. Installed ROM then Gapps both with signature verification turned on. Still no Gapps. Any ideas?
Also tried going back into TWRP, wiped cache, wiped dalvik and fixed permissions. Still no Gapps.
Where did you dl them from? i would try dl'ing again from a different place.
Downloaded directly from this page: http://wiki.cyanogenmod.org/wiki/Latest_Version/Google_Apps
Direct link: http://goo-inside.me/gapps/gapps-jb-20121011-signed.zip
Going to try:
http://d-h.st/NIs
and then
http://www.mediafire.com/?gbwm3ba55ple8d8
Will report back soon. Thanks again!
I tried many different links including the ones posted above and this still doesnt work. I also got curious and flashed a few older nightly builds mainly:
cm-10-20121110-NIGHTLY-d2att
cm-10-20121111-NIGHTLY-d2att
cm-10-20121112-NIGHTLY-d2att
and gapps does not work on any of them. There has to be something im doing wrong but i cannot for the life of me figure it out. Im not sure what to try next. Any suggestions?
EDIT: wait a minute... what apps does the gapps package include by default now?
EDIT2: GOOD LORD. I feel so stupid. I was under the impression that navigation, maps the new camera app was part of the 201210 gapps. I somehow forgot that recently I installed the 4.2 leaked apps which came with all the new goodies. Jesus lol. I also remember that installing the 4.2 apps made me lose the launcher options in cm10 settings which is why I have gotten rid of them. I guess this problem is now solved lol
Haha, well normally GAPPS don't include much. Just playstore, voice search (google now) and some other apps I don't remember. Not many though.

[Q] How to get rid of having to do a battery pull

Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Firewalker1980 said:
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Click to expand...
Click to collapse
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
ahmadallica said:
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
Click to expand...
Click to collapse
Hey thx for your suggestions!
I always flash a "new" rom that way though. But an update of the same rom, I "dirty" flash, which should be fine according to everyone.
No matter what Rom/Kernel I use, I still frequently have to pull the battery out.
It's never from locking up within Android. It just freezes/loops on the Google bootlogo.
I once wiped everything, even the storage space, and it helped for a little while, but did not make it go away for good.
Could it be related to certain apps ? Maybe PGM or Seeder or smth ?
All input welcome
---------------------------------------------------------------
Phone: Samsung Galaxy Nexus Maguro
Rom: AOSPA 2.99 latest
Kernel: AK Purity v20
Recovery: TWRP 2.3.3.0

[Q] Boot Fail after Custom ROM

I have a Samsung Galaxy Nexus GSM and have been trying to install the Paranoid Android flavor custom ROM, I had 2.22 installed not long ago but managed to screw it up when I updated it without clearing my security settings (I had a 4x4 pattern swipe which I couldn't enter with the update which restored it to 3x3 pattern) so I wiped and restored to stock 4.2. I'm now trying to re-install with any custom ROM but it's not working.
Whenever I install a ROM it seems to install ok but when I get to the boot screen it just hangs on the nexus/PA logo.
I've tried with:
Goo Manager
TWRP 2.2
TWRP 2.3
CWM 6.0.1.5
and with
PA 2.22
PA 2.99.1
PA 2.99.5
PA 2.99.6
PA 2.99.7
and I always get the same error, I've tried wiping all options within TWRP and CWM and going from there but that doesn't seem to work, the strange thing for me though is that if I re-install a stock Google ROM it works perfectly fine.
I'm fairly new so please be gentle.
flash the latest twrp and move the rom and gapps to your sdcard then follow this..
1. factory reset
2. wipe system
3. wipe cache
4. wipe dalvik
5. flash rom
6. flash gapps
7. reboot
if it still freezes at boot animation pull battery reboot to recovery wipe cache/dalvik and reboot
Thanks for the suggestion but that didn't work.
Any other suggestions?
When you say TWRP 2.3 do you mean 2.3.2.1? http://teamw.in/project/twrp2/90
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
zephiK said:
When you say TWRP 2.3 do you mean 2.3.2.1?
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
Click to expand...
Click to collapse
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Using TWRP, wiping cache, dalvik, and system should wipe everything except the sdcard contents. So doing these wipes should make your phone "bare stock" again as you described
Why don't you try downloading another custom ROM or download the same ROM again because maybe it is corrupted or something
osiris231 said:
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Click to expand...
Click to collapse
RANT: huh..... seriously? you couldn't have browsed around, searching for this COMMON issue (which usually comes down to user "error"), read the STICKIES, before posting?
first, internal storage = /data/media aka /storage/sdcard0/ aka /sdcard/
Please read all of this
http://forum.xda-developers.com/showthread.php?t=1626895

Updating Cyanogenmod without losing settings

I've been flashing the nightly cyaongenmod 10.1 builds on my i747m using cwm.
Is there a way to prevent losing all the settings and apps that I have? For example, if I don't clear data/cache will this cause bad things to happen?
Or is there another way to do this?
nmunro said:
I've been flashing the nightly cyaongenmod 10.1 builds on my i747m using cwm.
Is there a way to prevent losing all the settings and apps that I have? For example, if I don't clear data/cache will this cause bad things to happen?
Or is there another way to do this?
Click to expand...
Click to collapse
Get titanium backup and do a full backup of your apps/data. When you restore, dont restore any system app but you can restore the rest.
And to avoid problems, always clear cache/dalvik.
nmunro said:
I've been flashing the nightly cyaongenmod 10.1 builds on my i747m using cwm.
Is there a way to prevent losing all the settings and apps that I have? For example, if I don't clear data/cache will this cause bad things to happen?
Or is there another way to do this?
Click to expand...
Click to collapse
All you need to do is download the new nightly that you wanna flash, boot into recovery, flash the nightly. If you have any other files that you wanna flash like a kernel, flash them after the nightly. Clear cache & dalvik cache & reboot. You won't lose any apps or settings doing it this way. This is how I update every day. Now if you wanna do a clean install every single time you update, that's another story. The way I just explained to you will work just fine. There is no need in wiping EVERYTHING for every update.
Sent from my Galaxy S3
RobbieL811 said:
All you need to do is download the new nightly that you wanna flash, boot into recovery, flash the nightly. If you have any other files that you wanna flash like a kernel, flash them after the nightly. Clear cache & dalvik cache & reboot. You won't lose any apps or settings doing it this way. This is how I update every day. Now if you wanna do a clean install every single time you update, that's another story. The way I just explained to you will work just fine. There is no need in wiping EVERYTHING for every update.
Sent from my Galaxy S3
Click to expand...
Click to collapse
It's not only about wiping everything (Clean flash), having a backup is always good and *needed* imo. Never know when something will go wrong, could be as simple as a corrupted download.
So just to confirm, if I download the latest nightly, boot into cwm, clear cache and dalvik, but don't delete user data, then flash ROM and gapps, it will have all my settings and apps already setup?
nmunro said:
So just to confirm, if I download the latest nightly, boot into cwm, clear cache and dalvik, but don't delete user data, then flash ROM and gapps, it will have all my settings and apps already setup?
Click to expand...
Click to collapse
Yes.
Should still concider Tibu. Friendly suggestion.
nmunro said:
So just to confirm, if I download the latest nightly, boot into cwm, clear cache and dalvik, but don't delete user data, then flash ROM and gapps, it will have all my settings and apps already setup?
Click to expand...
Click to collapse
Yes.
Sent from my Galaxy S3
---------- Post added at 11:22 AM ---------- Previous post was at 11:21 AM ----------
BWolf56 said:
It's not only about wiping everything (Clean flash), having a backup is always good and *needed* imo. Never know when something will go wrong, could be as simple as a corrupted download.
Click to expand...
Click to collapse
Thanks. I didn't think about mentioning that. It's kind of a given to me to keep a good nandroid. Some people may not know though. Thanks for adding that.
Sent from my Galaxy S3
I have a touchwiz nandroid and a cm10 nandroid on my SD card and my computer.
Will I have to flash gapps again or will that already be there?
nmunro said:
I have a touchwiz nandroid and a cm10 nandroid on my SD card and my computer.
Will I have to flash gapps again or will that already be there?
Click to expand...
Click to collapse
Gotta flash the Gapps everytime you flash a ROM. (Their respective one)
nmunro said:
I have a touchwiz nandroid and a cm10 nandroid on my SD card and my computer.
Will I have to flash gapps again or will that already be there?
Click to expand...
Click to collapse
You will only have to flash Gapps the first time. If you update like I told you, you will not have to flash them.
Sent from my Galaxy S3
Changing from stable to nightly
Hi,
I'm currently running on a cm 10.1.3 stable (note 2 N7100). I would like to install cm-11-20141027-NIGHTLY-n7100. Do i have to do a complete wipe or just flash the downloaded file from recovery.
cm upgrade manually w/o losing data
RobbieL811 said:
All you need to do is download the new nightly that you wanna flash, boot into recovery, flash the nightly. If you have any other files that you wanna flash like a kernel, flash them after the nightly. Clear cache & dalvik cache & reboot. You won't lose any apps or settings doing it this way. This is how I update every day. Now if you wanna do a clean install every single time you update, that's another story. The way I just explained to you will work just fine. There is no need in wiping EVERYTHING for every update.
Sent from my Galaxy S3
Click to expand...
Click to collapse
Does it apply to stable updates and upgrades also and not only for nightly?
Can I use the same method for updating CM11s to CM12 whenever they release...?
Titanium Backup
Will the Titanium Backup * root be the correct one, or the Titanium Pro?

[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"

[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
nwjimmy said:
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
Click to expand...
Click to collapse
Are you wiping system and data before flashing? This is most likely your issue.
zelendel said:
Are you wiping system and data before flashing? This is most likely your issue.
Click to expand...
Click to collapse
yes, cache and dalvik, and a factory reset.
nwjimmy said:
yes, cache and dalvik, and a factory reset.
Click to expand...
Click to collapse
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
zelendel said:
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
Click to expand...
Click to collapse
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
nwjimmy said:
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
Click to expand...
Click to collapse
No wiping the system doesnt format the data partition. Wipe system then format the data and then wipe the caches and then flash the rom.
Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
matt_schieman said:
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Agreed.
Double check your gapps and make sure uts the right version
sent from my 1920 overclocked note 2 running jedi xp12
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
nwjimmy said:
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Most rom threads have a download link to the gapps that work with the version of android that specific rom is on. Look in the rom thread for the one you're currently running. There are different gapps for each android version (4, 4.1, 4.2)
I have that same problem too
I was trying to install new roms for my phone i tried liquid smooth and avatar and CM 10. I also tried install a new kernel and also different recoveries but nothing seems to work. I never "dirty" flashed and i use the right gapps. Someone please help me here i hate stock roms!
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't work.
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
fig03 said:
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
That's a good point. You should be on TWRP 2.7.0.0 that's the latest version of that recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, but it constantly froze, tried to reset, stuck with the same issue. Never used TWRP, so if someone could actually point me in the right direction, that'd actually be helpful.
xantechie said:
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, though...it doesn't really look the way I remember it last it worked, but it's had the issue so long, I forget what it actually looked like before.
Click to expand...
Click to collapse
I have no idea how to use TWRP...it only lists a .img file and no instructions on how to use it. zip files can be used from the bootloader or recovery. WTF am I supposed to do with an .img file. And it can't be to use the terminal emulator because to do that I would have to be able to get passed the Setup Wizard...which is the issue.
I finally figured it out with CWM. Thankfully. The phone would've went flying otherwise.
If anyone else stumbles upon this thread (so they can find the answer for CWM also), you have to format the device from the CWM Recovery to get rid of the crap that is blocking it. I did the following:
Once in CWM Recovery, Remove your SD card to avoid formatting it by accident.
Use the Volume Key to scroll to "mounts and storage".
Format all existing options (this is why the SD needed to be removed); this will blank out the phone's system which was causing the Setup issue to begin with.
Put your SD card with the ROM to be installed back into the phone.
Follow the guide as normal after this (install ROM, then reboot, then KK_gapps, then wipe the two caches, then reboot.)

Categories

Resources