Related
Play store "connection time out" error in both Kitkat & Resurrection Remix Zenfone 5
Hi,
I upgraded my Zenfone 501CG T00J Jelly Bean 4.3 (which was working fine) to KitKat firmware WW 2.22.40.54 (OTA), after which I couldn’t connect my Play Store through Wi-Fi (Connection time out error) , though I could browse sites with my chrome browser. There was no problem with Wi-Fi router, which I checked by connecting Play store with my Zenfone 7” tab and also my laptop. Then, I tried with various steps like clearing cache, clearing data, uninstalling updates and updating again, installing an older play store apk, checking date and time, (that are available all over internet) and finally contacted Asus customer support through online chat. They suggested clearing cache and no more, and disconnected. Frustrated at their support, I decided to flash a custom ROM and installed Resurrection Remix. Still my problem persisted. Added with Play store, I was left with no GPS, FM Radio and most importantly, the Call recording feature, which I loved so much since many other phone never offered!. Also after upgrading, my model number changed to T00F from T00J. Now I’m thinking of reverting back to stock (Asus) KitKat or Jellybean.
How should I do it?
What could be the cause for the Play Store “Connection time out” error in both Stock KitKat and RR?
Any solution? Have a Great Day! Thanks in advance!!
ajith26 said:
Hi,
I upgraded my Zenfone 501CG T00J Jelly Bean 4.3 (which was working fine) to KitKat firmware WW 2.22.40.54 (OTA), after which I couldn’t connect my Play Store through Wi-Fi (Connection time out error) , though I could browse sites with my chrome browser. There was no problem with Wi-Fi router, which I checked by connecting Play store with my Zenfone 7” tab and also my laptop. Then, I tried with various steps like clearing cache, clearing data, uninstalling updates and updating again, installing an older play store apk, checking date and time, (that are available all over internet) and finally contacted Asus customer support through online chat. They suggested clearing cache and no more, and disconnected. Frustrated at their support, I decided to flash a custom ROM and installed Resurrection Remix. Still my problem persisted. Added with Play store, I was left with no GPS, FM Radio and most importantly, the Call recording feature, which I loved so much since many other phone never offered!. Also after upgrading, my model number changed to T00F from T00J. Now I’m thinking of reverting back to stock (Asus) KitKat or Jellybean.
How should I do it?
What could be the cause for the Play Store “Connection time out” error in both Stock KitKat and RR?
Any solution? Have a Great Day! Thanks in advance!!
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
Here is everything you need to know
Good luck!
Resolved!!
Thanks for all those who replied!
Solution that worked for me...
1. Installed Super Su
2. Entered recovery mode via reboot options in RR
3. Flashed/Installed a file "4.44 fastboot flash.zip" that I saved in my sd card and shared by a android developer in facebook (Sid Kondekar......thanks to him).
I Couldn't share links coz I'm a newbie (<10 posts) ....sorry...
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 !
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
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.
I have a Moto G3 XT1543 and since december I have given this device a second life and have been using it as a secondary phone. I decided to install LOS 14.1 because I feel is better for this device than LOS 17.1. Since then I had been using the phone and installing the updates without problems until a few weeks ago.
I thought I couldn't install the update because my version of TWRP was so out of date. So I decided to install the latest version for this device (twrp-3.5.2_9-0) and I was able to update the rom but it got me a lot of bugs, basically forced close in many processes.
So I decided to do a clean installation but still had a lot of bugs. So I installed previous versions of the rom, including the first one that I installed and worked fine, but it still had a lot of bugs (basically forced close in many processes, as I said before).
So I decided to go back to the TWRP I had before (twrp-3.4.0-0) and the bugs disappeared and I was able to use the rom without problems, but no matter what I do I cannot get youtube working now.
The gapps that I have been installed are open_gapps-arm-7.1-pico-xxxxxxxx and I have done all the possible combinations: old gapps with the most recent rom (lineage-14.1-20210829-UNOFFICIAL-osprey), the most recent gapps with the oldest rom I have (lineage-14.1-20201221-UNOFFICIAL-osprey), the oldest rom I have with old gapps and the most recent rom with the most recent gapps, but youtube still doesn't work
As I said before, it doesn't matter what combination I do, even the first one I installed and worked since last december, nor what version of YouTube I have installed, the application closes. As a possible solution I have deleted cache and data of youtube but the problem still. The funny thing is all the applications that I have, including other google apps (chrome, gmail, maps) work without problem.
I have tried alternatives like YT Go, YT Vanced and New Pipe and all three work without problem, but honestly, although they are better alternatives, I don't want to use them.
So does anyone know how to fix this?
I used this weekend for testing and long story short I can use youtube but I have no idea how it was fixed.
But I will tell you about everything I did in case someone in the future is going through a similar situation to mine.
Following the indications that FNetV1 gave me in another post, I downgraded my TWRP version to 3.0.2-r5, then I installed the oldest rom I have (lineage-14.1-20201221) with the oldest gapps I have (open_gapps-arm-7.1-pico-20210112) but youtube was not working.
So with that same version of TWRP I installed the most recent rom available (lineage-14.1-20210829) with the most recent gapps and still youtube did not work.
So I installed the latest unofficial version that Squid2 developed for this device (twrp-osprey-3.2.3-r1) and then installed the oldest rom I have with the oldest gapps I have. The result was the same, youtube was not working.
I thought the problem was the gapps, so I installed the latest rom available with the most recent gapps but now with the Nano package. But the result was the same, youtube was not working.
So I gave up and for the last time I reinstalled the latest rom avaible with the most recent gapps, again with the pico package and as expected youtube was not working.
The funny thing is after I finished setting up my phone, I restarted it, reinstalled YouTube and voilà, I can now use YouTube without any problem.
As I said at the beginning, I have no idea how the problem was fixed, especially because I also rebooted my phone on several occasions with the previous tests.
So if anyone has an idea what I did wrong from the beginning or how the problem was fixed, feel free to comment.