Database Develop

[Q] playstore missing

I installed the Android Open Kang Project - R3.1.
However after rebooting the system. I am unable to fine the playstore link.
Any ideas/suggestions.
Thanks in advance.

You need to download GApps. GApps are pretty much universal. If you cant find them on the ROM page, then just hop into another 4.2.1 ROM thread and take the GApps from there.

Go to too manager site
You can find gapps
Download the one with your jb version
Sent from my Incredible S using xda app-developers app

072665995 said:
You need to download GApps. GApps are pretty much universal. If you cant find them on the ROM page, then just hop into another 4.2.1 ROM thread and take the GApps from there.
Click to expand...
Click to collapse
My mistake. While installing Android Open Kang Project - R3.1, by mistake I unchecked the option to install Gapps.
So I reinstalled Android Open Kang Project - R3.1 again and this time I did not uncheck Gapps. The installation went off smoothly.
Now I have a different problem. After installing the new ROM, I installed a few apps from the play store. However the phone is restarting on its own frequently and it goes into into recovery.
Any idea what could have gone wrong.

simba_leo said:
My mistake. While installing Android Open Kang Project - R3.1, by mistake I unchecked the option to install Gapps.
So I reinstalled Android Open Kang Project - R3.1 again and this time I did not uncheck Gapps. The installation went off smoothly.
Now I have a different problem. After installing the new ROM, I installed a few apps from the play store. However the phone is restarting on its own frequently and it goes into into recovery.
Any idea what could have gone wrong.
Click to expand...
Click to collapse
maybe u can try to reflash the rom.. do it with clean flash, format all part except sd card, wipe dalvik + cache, and reflash the rom..
if it still happen, "maybe" there is something wrong with the rom.. hope this one can help..

simba_leo said:
My mistake. While installing Android Open Kang Project - R3.1, by mistake I unchecked the option to install Gapps.
So I reinstalled Android Open Kang Project - R3.1 again and this time I did not uncheck Gapps. The installation went off smoothly.
Now I have a different problem. After installing the new ROM, I installed a few apps from the play store. However the phone is restarting on its own frequently and it goes into into recovery.
Any idea what could have gone wrong.
Click to expand...
Click to collapse
Are the restarts often or do they happen at a specified time. You can try disabling HW overlay in developer options.

I tried disabling HW overlay in developer options without much success.
I have 4Ext recovery installed on my phone. Could that be an issue?

simba_leo said:
I tried disabling HW overlay in developer options without much success.
I have 4Ext recovery installed on my phone. Could that be an issue?
Click to expand...
Click to collapse
No having a certain recovery should not cause random reboots. Do the reboots occur at a specific time like when you execute a certain task (opening app or something)???

I tried to install LBE Privacy guard immediately after installing the new ROM. After which the ROM starting misbehaving.
Could LBE Privacy guard be the culprit?

simba_leo said:
I tried to install LBE Privacy guard immediately after installing the new ROM. After which the ROM starting misbehaving.
Could LBE Privacy guard be the culprit?
Click to expand...
Click to collapse
It could possibly be. Make a backup of your current AOKP setting and stuff. Then reflash AOKP nad use your phone normallly without LBE Privacy. If it does not reboot then LBE Privacy is the culprit.

Problem solved
I reinstalled AOKP. But this time I did not install LBE Privacy guard. And the problem went away.

[Q] Endless Boot & Gapps issue

Received this phone a month ago, just got around to rooting it yesterday. Root with motochopper went fine. Unlocked the handset with motopocalypse, everything went fine. Installed latest CM10.2 nightly and everything ran fine, even restarted phone and it worked fine. I then realized I forgot to install Gapps, So i went to CWM and installed the Gapps through "install zip from sd card". Now phone will not progress past the bootloader unlocked warning screen. I can restart and put phone into recovery or fastboot no problem but I don't know where to go from here. I tried a factory reset and reinstallation of CM but to no success. I am a bit of a newb when it comes to external programs like RSD Lite and haven't used it. Is there something obvious I'm missing in my progress of trying to fix my phone?

clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.

frog1982 said:
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
Click to expand...
Click to collapse
i can't post outside links yet but on the wiki.cyanogen site in the Gapps section I used the 10.2 20130813 1f51b5cc6370c1f45dc951109b6ce6ed release. I will attempt those steps once i can find a legitimate charger in my house. Phone doesn't accept power unless its on and i need just a bit of juice to boot it up

frog1982 said:
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
Click to expand...
Click to collapse
Here's the official name. Installed cm-10.2-2-130814-NIGHTLY-mb886.zip for the cm and gapps-jb-20130813-signed.zip for the GApps, both latest versions I believe

frog1982 said:
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
Click to expand...
Click to collapse
none of the above steps worked unfortunately. Is there a set order of certain things to be mounted and unmounted in the mount section? Such as the system or sd card?

yodelyfish said:
none of the above steps worked unfortunately. Is there a set order of certain things to be mounted and unmounted in the mount section? Such as the system or sd card?
Click to expand...
Click to collapse
try changing the mount status of the cache
also are you getting any funny messages in cwm
PS are you flashing gapps before first boot up

frog1982 said:
try changing the mount status of the cache
also are you getting any funny messages in cwm
PS are you flashing gapps before first boot up
Click to expand...
Click to collapse
i got Cyanogen up and working. And no I was not flashing gaps Before first boot. i will try doing that before everything else

I got both GApps and cyanogenmod to install properly and the phone boots normally, but now I don't see any of the GApps actually present on the phone. Did I F somethin over again?

yodelyfish said:
I got both GApps and cyanogenmod to install properly and the phone boots normally, but now I don't see any of the GApps actually present on the phone. Did I F somethin over again?
Click to expand...
Click to collapse
did you flash gapps before flashing the ROM because the ROM flash will overwrite the gapps.
PS I suggest using zgapps http://forum.xda-developers.com/showthread.php?t=2240652 because they are stripped down which tends to prevent a lot of issues and if you want a 4.3 ROM try skeevydudes PAC ROM it is more stable plus has more features.

frog1982 said:
did you flash gapps before flashing the ROM because the ROM flash will overwrite the gapps.
PS I suggest using zgapps http://forum.xda-developers.com/showthread.php?t=2240652 because they are stripped down which tends to prevent a lot of issues and if you want a 4.3 ROM try skeevydudes PAC ROM it is more stable plus has more features.[/Q]
Awesome. Pac-Rom already looks better on review. I get to the dl page tho and have a monster list of choices. Which one do I go for?
Click to expand...
Click to collapse

frog1982 said:
did you flash gapps before flashing the ROM because the ROM flash will overwrite the gapps.
PS I suggest using zgapps http://forum.xda-developers.com/showthread.php?t=2240652 because they are stripped down which tends to prevent a lot of issues and if you want a 4.3 ROM try skeevydudes PAC ROM it is more stable plus has more features.
Click to expand...
Click to collapse
Thank you for all the help. PACROM is up and running swimmingly, all of the features are there and it is definitely better than CM by itself. Thanks again

Unable to install latest Mokee build properly

Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?

isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3

bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?

A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.

isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:

I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?

bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps

isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .

'do a wipe' ? not sure what this means exactly, maybe it is what i need to do?

I have a HTC ONE m7, rooted, I have been running CM11, flashing the nightlies with great success. When CM12 came out, it 'soft bricked' my phone, continuous reboots, failing android functions. was able to reinstall Titanium backup, then restore the phone to a previous point. back running, but not without bugs. after trying this 3 times, I have given up. but I read where people say, "do a wipe" then flash the ROM....... What, specifically does this mean?
yes I have rooted my phone, but I am just knowledgable to be dangerous. if It means back to factory specs, then how do I flash the rom? I think that my phone should run CM12, and maybe I need to wipe? wipe what? dalvic cache? is that a wipe?
Anybody have some ideas or can point me to some postings that may help me. Many Thanks, very tired of operating on the last build of CM11
blairan

Do a wipe typically means wipe the data, system, cache, and dalvik cache partitions. If you are using TWRP as your recovery (I do for this phone), boot into it and then press Wipe, then Advanced Wipe. Select those four (not internal storage or USB OTG) and then Swipe to Wipe. Of course, your phone won't boot at this point, so you'll need a new ROM waiting on internal storage to be flashed.

thankyou Coal, I have been trying to install a CM12 and/or a CM12.1 ROM I can get them to boot up, but play store is not present. I can access play store via themes, and it comes up as a web page rather than an app. (is this norm for CM12?)
once I sign in to play store, I try to install titanium backup to restore all my apps. it says it is installed, I press it anyway, and it says it will be installed soon, which never happens. CM12 and CM12.1 seem to be running fine, but I can't restore any of my old phone. I can recover to a CM11, but it is a little unstable, so I would like to upgrade the system and be flashing nightlies again. what do you think?

and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!

blairan said:
and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!
Click to expand...
Click to collapse
I was going to suggest GAPPS, but I wasn't sure if you needed it for CM. Glad you figured it out!

Google voice search making my phone unusable

I've tried flashing slim rom and paranoid Android and all do the same thing. As soon as Google apps are installed the Google voice search prompt pops up repeatedly. It disables calling and also all sounds. I have turned it off in Google settings best I could and it still keeps happening. It has essentially made my nexus 6 unusable. And since I need the Google app I don't know what to do. Anyone seen this problem before? I am guessing it is not rom specific as it happens on all I have tried. Help severely needed
Sent from my Nexus 6 using Tapatalk

wessiide said:
I've tried flashing slim rom and paranoid Android and all do the same thing. As soon as Google apps are installed the Google voice search prompt pops up repeatedly. . .
Click to expand...
Click to collapse
When I flashed a different ROM there were always issues when I did not a wipe in TWRP recovery (factory reset).

I have cleared data and cache along with a system wipe. Any thing else I can try to wipe?
NLBeev said:
When I flashed a different ROM there were always issues when I did not a wipe in TWRP recovery (factory reset).
Click to expand...
Click to collapse
Sent from my Nexus 6 using Tapatalk

wessiide said:
I have cleared data and cache along with a system wipe. . .
Click to expand...
Click to collapse
In TWRP there is a message about wiping.
When you did that it is OK.
Effect should be that after booting the new rom, you need to completely setup the device again (setup wizard).
When there are still issues it could be a corrupt download.

I'll try to be more clear here.
I have done a factory reset (system, data, cache, dalvik) from TWRP.
I install new rom (chroma, paranoid, slim, and a stock build)
Boot up phone, complete setup wizard.
"Listening" prompt from google voice search starts popping up repeatedly, over and over no matter what I am doing on the phone.
I disable google voice search, doesn't matter, continues to pop up.
In the meantime it disables all sounds on the phone and I cannot place a call/take a call.
Again, this is the same actions that happen regardless of what rom I have installed, even after doing the reset.

Try changing the GApps package you flash after your ROMs.
I'm guessing you've been using the same GApps with each ROM you listed. Download another GApps and use that instead in a clean flash of a given ROM.
Good luck!
(One more thought: You could try clean flashing a ROM with a built-in GApps and see if that works...)
Sent from my A0001 using Tapatalk

wessiide said:
I have done a factory reset (system, data, cache, dalvik) from TWRP.
I install new rom (chroma, paranoid, slim, and a stock build)
Boot up phone, complete setup wizard.
Click to expand...
Click to collapse
There are two important options in TWRP.
WIPE and FORMAT.
You have installed several different roms. The memory could be messed up.
A format could help.
The last suggestion I can do is: back to stock.
Flash a factory image.
Leave bootloader unlocked.
Check if the issue is gone when the stock rom is set up.
Than choose a custom rom, start with Chroma.

NLBeev said:
There are two important options in TWRP.
WIPE and FORMAT.
You have installed several different roms. The memory could be messed up.
A format could help.
The last suggestion I can do is: back to stock.
Flash a factory image.
Leave bootloader unlocked.
Check if the issue is gone when the stock rom is set up.
Than choose a custom rom, start with Chroma.
Click to expand...
Click to collapse
What do I format? System? It doesn't seem to be a Google specific problem as even with Google not installed the phone just hangs up when I dial a number and sound doesn't work. It went away on its own about an hour after start up and I've been good for a week. Now just this morning it started doing it again. The volume turned itself up a notch and boom no sound on video can't call anyone. It's very strange, and must be a deep rooted issue as it is across all roms. The only difference with Google now installed is the listening prompt popping up constantly. Without its just what I listed above.
Sent from my Nexus 6 using Tapatalk

Revert back to stock (e.g. with Wug's nexus root Toolkit), leave bootloader unlocked. Then reflash your things and see if problem persists. If it does, try TK GApps and don't install Google App (per gapps-config.txt).