I tried with 4 different gapps - @Setting.Out gaaps, open gapps, dynamic gaaps, bank's gaaps on 3 different rom jgcaap 7.1,pure nexus rom, archi droid rom, all latest (in a after "factory reset" condition)
I started with Clean flash and then standard procedure of flashing rom. I had also tried cleaning up the data and cache of play store but no effect. Changing and resiging accounts. I have recommended firmware provided by jgcaap and tugapowers.
At Last I went back to jgcaap 6.0 (currently running it and loving it ) and everything works like charm.
I had came here to ask anything that I had left which lead me into this or how I can solve it . Now I am scared of upgrading to 7.x. For now hehe
Hopefully someone will report
[Solved the problem by just waiting for the next Gaaps build]
Related
I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.
I have 2 of the same phones (i747M with twrp 2.7.1 for d2att installed)
On one, everything worked flawlessly (the older one)
On the other, I had to talk to a developer of twrp to get twrp working...
Now I just realized that the camera app isn't working. It works fine when I restore to the touchwiz stock rom.
I tried wiping my entire device before installing the new stable build 6 rom for d2lte. I also tried flashing the weekly roms for that device on both phones
the result is the same: camera works fine on the older phone while on the newer one, it doesn't
Someone suggested that this might be a hardware issue.. Basically, the TWRP guys fixed my other problem by pulling the latest cyanogenmod build and compiling a recovery. -So I'm wondering if something can be done to make my camera work again on my new phone...
(Before all of this, I of course tried rebooting, closing other apps, clearing data, etc...)
Update: I tried flashing the latest cyanogenmod nightly (June 30) and the camera app worked, but I prefer slimrom
Another update: all the bug report shows when I reproduce the error is
Device: Slim-d2lte-4.4.4.build.6-OFFICIAL-5242
Kernel: 3.4.95-cyanogenmod-gd56ed95 [email protected] #1
Hi there members of xda
A few months ago i updated to marshmallow on my moto g3 , and the experience was awful, not to mention the touch screen issues. I successfully downgraded to lollipop by skipping gpt.bin and bootloader.img, and i used lollipop for a while then got bored of it, so i tried to install cm13 official. When i did that , my phone gets google play store and google play services FC's on cm13. I have set google play services all permissions .. I have tried a wide variety of gapp packages and they all have the same problem. Google play store instantly crashes when i tap it, if that helps atall.
For now, i reflashed marshmallow stock. Should i be flashing cm13 from stock mm , or stock lp.. becuase i havent tried flashing using stock mm , becuase i didnt think it would make a difference as i always wipe the system partition before flashing cm anyway. :/
Many thanks,
therealduff1
therealduff1 said:
Hi there members of xda
A few months ago i updated to marshmallow on my moto g3 , and the experience was awful, not to mention the touch screen issues. I successfully downgraded to lollipop by skipping gpt.bin and bootloader.img, and i used lollipop for a while then got bored of it, so i tried to install cm13 official. When i did that , my phone gets google play store and google play services FC's on cm13. I have set google play services all permissions .. I have tried a wide variety of gapp packages and they all have the same problem. Google play store instantly crashes when i tap it, if that helps atall.
For now, i reflashed marshmallow stock. Should i be flashing cm13 from stock mm , or stock lp.. becuase i havent tried flashing using stock mm , becuase i didnt think it would make a difference as i always wipe the system partition before flashing cm anyway. :/
Many thanks,
therealduff1
Click to expand...
Click to collapse
Which gapps did you use? If you are having issues on cm try CrDroid or BrokenOS (go to their G+ community)
Btw, on the cm thread Alberto posted a fix for the touchscreen issues.
Henriquefeira said:
Which gapps did you use? If you are having issues on cm try CrDroid or BrokenOS (go to their G+ community)
Btw, on the cm thread Alberto posted a fix for the touchscreen issues.
Click to expand...
Click to collapse
I installed an old build of cm in the end and then updated to new version via ota. thanks anyway !
Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.
hjrry said:
Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.
Click to expand...
Click to collapse
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?
Nitefire77 said:
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?
Click to expand...
Click to collapse
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?
hjrry said:
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?
Click to expand...
Click to collapse
Try a different GAPPS package, maybe a larger one. Just to see. For one, some people complained of missing features like notification bar pulldown with the very smallest GAPPS package. Now this isn't a reason it shouldn't install, but try a different package to see if it make a difference in completing the installation.
hjrry said:
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Click to expand...
Click to collapse
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.
plasticdoc said:
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.
Click to expand...
Click to collapse
First, restore your backup. You did make a backup, right?
Then re-flash after you download a different GAPPs package. Some say Open Gapps works great for them, while others say Slim GAPPS is best. We don't know why some don't work for some people but work for others.
If that doesn't fix your issue, then try this:
Download the unofficial CM13 found here in this forum and try it.
Also, download Resurrection Remix (Marshmallow) and try it.
Both are variants of CM13 anyways. Just trying to see if something is wrong with your phone and you can't flash any ROM whatsoever or if it's something your phone doesn't like about official CM13.
The unofficial CM13 is CM13 with just a few of the Resurrection Remix tweaks thrown in, like permissions to download Moto apps from the Google Store, etc. It's 90% CM13, 10% RR.
If none of those CM13 variants work, you can alway try AOSP Mokee (Marshmallow).
IF NONE of those work, either your phone is severely messed up or you are doing something wrong.
ChazzMatt said:
Download the unofficial CM13 found here in this forum and try it.
Click to expand...
Click to collapse
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.
plasticdoc said:
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.
Click to expand...
Click to collapse
I don't know. Not everything with our phones is completely logical. Occasionally more of an art than science. Same reason one GAPPs package works well for someone but won't install for another person. Open GAPPS vs Slim Gapps.
Here's a personal example... My wife and I both have XT1225 with CM12.1 and yet hers can't run BHB27 kernel. Occasionally I'll get it to install, and run OK for a day or two but then next time I reboot it it does endless bootloops. I even tried different governors and I/O schedulers. Nada.
Mine is a Puerto Rico (unlocked Claro) XT1225 I flashed to India 5.0.2 before flashing to CM.
Her's is a Mexico direct-from-China-Motorola factory XT1225 I flashed to India 5.0.2 before flashing to CM.
Later I flashed Puerto Rico XT1225 radio over both.
There's just some difference there in her XT1225 which does not like BHB27 kernel.
Maybe if I did an exhaustive formatting of the entire internal memory and reinstallation of everything on her phone, it would work. But instead I take the easy way out and she's just running CM12.1 with default CM kernel, and that's running well. So, I go with what works.
phone app not working
unfortunately telephone has stopped working.
wajid1213 said:
unfortunately telephone has stopped working.
Click to expand...
Click to collapse
What does that have to do with this thread? > cm13 setup STUCK AT 'JUST A SEC' SCREEN (URGENT!!!)
I don't even think you are using this phone, to be honest. So, why did you post here? You posted same thing in another thread, for ANOTHER PHONE, not even related to Quark.
You seem to be using this phone: Xiaomi Redmi 2 -- since all your other posts before this and after this are over there.
http://forum.xda-developers.com/search.php?searchid=422491957
Ever since I upgraded to android 10, I haven't been able to get OK Google to enable on any ROM (tried ArrowOS, AOSiP, Evolution X, AICP); in every ROM, switching on OK Google in Assistant settings just has it turn right back off after a few seconds, with a driving warning and "Something went wrong. Try again." at the bottom of the screen. I grabbed a logcat while running Evolution X, but I took a peek at logcat on other ROMs and the error is identical:
https://pastebin.com/Ryqz1iww
For the record, this is a Perseus global model on 11.0.3.0.QEEMIXM firmware that's had MIUI 11 then Xiaomi.EU's latest MIUI 11 stable on it prior to going to custom android 10 roms.
If any more info would be helpful toward solving this, let me know and I'll grab it.
EDIT: OK Google IS WORKING under Xiaomi.EU's latest MIUI 11 build, but still no dice on any custom ROM.
EDIT 2: If a ROM has gapps included, it works. If I have to flash opengapps, it doesn't.
EDIT 3: Solved! Just flash the latest firmware again after you flash everything else - you can get the firmware here.
I'm on the latest Xiaomi.EU weekly ROM and OK Google works just fine.
Official ROMs are the only things I CAN get it to work on. Vanilla MIUI 11 and Xiaomi.EU both work for this, so it's not just an issue with my Google account or something - but something is preventing OK Google from working on any of the custom ROMs, including the latest versions of the ROMs mentioned in my OP, even those that include GApps, so it's not like I'm using a bad GApps package. Literally all I do is wipe everything (incl. formatting data), flash the ROM, flash Magisk (which I also did on the MIUI ROMs it works with), reboot, connect to wifi, log in to google (I've tried declining to restore a backup), go straight to Assistant settings and it fails, same error as in that logcat in OP on every ROM it happens on.
Hey, I have the same issue on Evo X. Have you managed to work it out? Thanks
Same issue here on AOSIP. Interestingly, I have two identical devices (Mi Mix 3), running the same version of AOSIP, and on one it works fine, and the other does not!
In case it makes any difference, I am using a gsuite account.
Solved! Thanks to a tip from @Caccu, I now have it working. The secret was to flash the latest firmware over the ROM, even if you're already on the latest firmware. I'm not clear on why, but it works. If you need the latest firmware, you can get it from here. For reference I'm using V12.0.1.0.QEEMIXM on my global Perseus model.
if you flash the latest firmware over a ROM. then you'll be using the latest firmware, and not the ROM you wanted. is that right?
bluviper said:
if you flash the latest firmware over a ROM. then you'll be using the latest firmware, and not the ROM you wanted. is that right?
Click to expand...
Click to collapse
No no, just the firmware, not the whole MIUI package/ROM. The link I provided only has the firmware, with the rest of MIUI stripped out. The ROM is unaffected, the only change I notice after flashing it is that OK Google works now.