Searched before asking, came up empty.
I tried upgrading to various ICS roms from on the forum. Every single one give me the same problems with market/play: Server error. I can not connect to the market. I never had a problem with honeycomb, and I've tried various roms and different versions of gapps. Also my cellphone (Huawei U8800) connects fine. I'm downloading the NVflash stock version now to try: http://forum.xda-developers.com/showthread.php?t=1524302
Any ideas on what may be the problem or what I can try to fix it?
The only possible thing I can think of is that because I'm in China it doesn't like the ICS versions of market/play, but that doesn't really make much sense.
Update: The NVFlash stock non-rooted version didn't work. Tried downloading and manually updating to the latest Google play, still got server error. Downgraded back to Honeycomb, didn't work. I ended up having to use a “Chinese Market" whose name I shouldn't mention. At least I can get adobe flash and the rest of the basics. Thanks Google. Even better was the "Chinese Market" updated Google play.
typci said:
Searched before asking, came up empty.
I tried upgrading to various ICS roms from on the forum. Every single one give me the same problems with market/play: Server error. I can not connect to the market. I never had a problem with honeycomb, and I've tried various roms and different versions of gapps. Also my cellphone (Huawei U8800) connects fine. I'm downloading the NVflash stock version now to try: http://forum.xda-developers.com/showthread.php?t=1524302
Any ideas on what may be the problem or what I can try to fix it?
The only possible thing I can think of is that because I'm in China it doesn't like the ICS versions of market/play, but that doesn't really make much sense.
Update: The NVFlash stock non-rooted version didn't work. Tried downloading and manually updating to the latest Google play, still got server error. Downgraded back to Honeycomb, didn't work. I ended up having to use a “Chinese Market" whose name I shouldn't mention. At least I can get adobe flash and the rest of the basics. Thanks Google. Even better was the "Chinese Market" updated Google play.
Click to expand...
Click to collapse
I had the same problem, full wipe, installed different ROMs didn't help.
If you have a VPN to US for once, the problem will resolve, after that the Market/Play will work even outside of US. The problem is on Google side.
So I woke up today and after about an hour I wanted to open the Play store when it immediatly crashed after opening it. After trying to reboot the phone trouble started.
- My Nexus got stuck in a boot loop (I should probably tell I was running the Google L beta (the one which was out for a while not the newly released 5.0 preview), let it run for over 30 minutes and still nothing, even after a few tries.
- Decided to flash the stock 4.4.4 image from the Google developer website and I got it to work again.
- After I reconfigured all the settings I noticed I didn't have any network: no calls, no text messaging, no LTE, 3G, etc. Also Google play services and other apps weren't working and immediately crashed (camera and gallery).
- I decided to reflash the radio image but without succes.
- After reflashing the stock image a few times I decided to try different versions, so I tried 4.4.3. Still no network.
- Then I tried to flash the newly release 5.0 preview, but that too got stuck in a bootloop (even after going to recovery mode and cleaning the cache, wiping all data).
- So after doing this for a few hours without any luck I thought maybe a custom ROM like Cyanogenmod might work. Things got worse. I noticed when trying to paste the CM image on my device (via windows/usb cable) I was unable to acces my folders. (see images)
- Trying to use the CM installer (from get.cm) resulted into trying to download the installer (APK file) and getting the error 'No SD'. Just that. This also happens when I try to install any other APK. So basically not being able to acces the play store or being able to download single APK's from Google leaves me with all standard apps... Which isn't alot.
- USB drivers are OK (can post pictures if needed). Reinstalled them anyway.
I tried 4.4.0, 4.4.3 and 4.4.4 using fastboot without any succes.
So yeah i'm pretty stuck, any help is really appreciated. I tried so many different topics on these forums and others its just getting worse with each method I try to fix the issues.
Flash stock 4.4.4 with fastboot.
http://forum.xda-developers.com/showthread.php?t=2513701
---------- Post added at 06:37 PM ---------- Previous post was at 06:36 PM ----------
See where you're at then. Go from there.
KJ said:
Flash stock 4.4.4 with fastboot.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
I did that, this is where the network issues and Google play crashes started.
I would ask in the L developer release Q&A thread. I believe it can cause similar issues, but I don't know them myself. Those guys in that thread may tho.
You probably need to format your partitions fully before flashing or something along that lines.
KJ said:
I would ask in the L developer release Q&A thread. I believe it can cause similar issues, but I don't know them myself. Those guys in that thread may tho.
You probably need to format your partitions fully before flashing or something along that lines.
Click to expand...
Click to collapse
I asked it there, thank you for your response.
It's an IMEI issue that's unrelated to Android Lollipop as far as I know.
Hi guys,
My girlfriend purchased a brand new Xperia Z3 D6653 not too long ago (about 2 months ago?). I flashed the 5.1.1 pre-rooted firmware for her and it's working fine and all but it does a random reboot every day or so, at random times, with random applications.
I have tried 2 different pre-rooted 5.1.1 firmwares already (yes, the correct model D6653 as well) and it still does it. The System Incident reports don't really say much (in fact you only see details about when it crashed, nothing else), and it seems like Google Play Services is the only thing mentioned in the Application Report.
The same thing also happened (more frequently) when she was on the 5.0 pre-rooted firmware. I'm not sure why, I haven't unlocked the bootloader or anything, it's just stock pre-rooted ROM, that's it. I haven't flashed any other ROMs other than the official pre-rooted ones.
Furthermore, before I flashed the 5.0 and 5.1 firmware for her, the phone came with Android 4.4.4. She used it for a month and reported several crashes as well, so that's with the original factory firmware, unrooted, unmodified etc.
She doesn't run any dodgy or random apps, she's just a typical girl that use Facebook and texting, that's pretty much it. I've done a lot of research on this issue and it seems to be quite common, however there isn't really a solution to this. The same apps she currently use never caused any issues on her older phones.
Also in case anyone asks, the only reason I flashed the pre-rooted 5.1.1 firmware for her is because it makes it easier for me to manage her phone (with Teamviewer, you can remote into the phone as long as it's rooted). Also, I get to backup her phone and do tests etc, makes it easier for me.
Also, I'm not using any custom kernels or overclocking the CPU etc. Everything is just stock but rooted.
Could this be caused by a hardware fault in the phone? I'm not sure what else I can do and would appreciate some suggestions.
Nobody have this issue??
Well, how about you try to flash a full, clean, stock ROM, don't root it, don't install any unnecessary app and see where it goes? If the issue persists, try getting a logcat from the phone and we can take a look at it. If it works fine after returning to stock, there might be a problem with the ROM or some apps you are using.
If it really is Gapps that are causing all the trouble, go to APKMirror and download the latest apps available (Play Services, etc) and see where it goes.
As mentioned already, prior to flashing anything, my girlfriend was running a completely stock, factory version of the phone. It came with Android 4.4.
I could flash a completely stock 5.1 ROM but was hoping that someone would share their experiences or a potential solution to this, considering this is quite commonly asked. I would also like to avoid doing this if possible, because if I were to go back to rooting the device, I'd have to downgrade to v4.4 pre-rooted, then flash to 5.1 rooted with custom recovery. It's just a lot of work for a simple testing that could be answered by others if possible.
Anyway, she didn't have any apps installed other than Facebook and Whatsapp, that's it. I might test with GAPPS and see how it goes, but I thought I'd ask here in case someone knows it's definitely a hardware issue or something else.
i would definitely give a pure stock 5.1.1 a go. I used to get the random reboots on the previous versions but i no longer have such issue.. Make sure you do a clean wipe and do it a few times.
Hi all, it's been a while but I thought I'd post an update and share what I've found/learned so far....
Basically, I'm still getting the frequent random reboots. I've tried reflashing the ROM and also tested out the latest .232 pre-rooted stock ROM, still getting the same issue. I've noticed that other than Google Play Services, sometimes Gapps will crash as well. But most of the time, there's nothing reported in the system or application crash logs. I've tested with everything running as stock, no additional apps installed. I then decided to flash the Minimal GAPPS 5.1.x and that sort of made the phone a bit more stable, but still reboots randomly every now and then.
Later on, I decided to try a custom ROM that still works on a locked bootloader. I found this here:
http://forum.xda-developers.com/z3/development/d6603-23-1-1-28-t3102271
The chef has provided a .232 firmware for you to flash in recovery, as well as the ROM base for the D6603 model. Mine is a D6653, but luckily the chef has also provided a D6653 patch for you to flash as well. I've flashed the ROM like so:
1. Wipe everything except my external microSD in TWRP. So basically, wipe system, data, cache, dalvik, internal storage etc.
2. Install .232 firmware.
3. Install v10.5
4. Install v12.0
5. Install D6653 v5 patch
It boots up fine but after using it for a while, I still get the random reboots. What's interesting is that I've also tried without flashing the D6653 patch, which essentially means I'm running just the D6603 base ROM on my D6653. It works, but still crashes as well. I just found it quite surprising that a D6653 could run a D6603 ROM, but it does make sense considering the main differences is just the baseband/frequencies.
Anyway, I later on decided to flash the pure 5.1.1 stock ROM, still getting the crash. Again, everything is tested on pure stock, no additional apps etc installed.
I'm starting to think perhaps this is a hardware issue on my phone?? I noticed that sometimes, my screen will show a bit of tearing and then it'll crash not long after. BUT, I also know that as soon as gapps or google play services crash, the phone will crash not long after as well.....
In fact, I later on used Titanium Backup to convert Google Play Services from a System to a User app, the phone will just boot into the lockscreen and then restart every time. This is a bit ridiculous because I've done this several times on other phones before and they never had such an issue. Of course, I'm not saying I always run Google Play Services as a User app, but that was just for testing and I honestly don't think it should cause a bootloop just because of that. I've also cleared dalvik and cache by the way, so it doesn't make sense that the phone boots into the lockscreen and then just restarts randomly.
I haven't tried uninstalling Google Play Services completely, but at this point I'm back to square one as I've exhausted pretty much all my options and it's been a complete waste of time. I'm beginning to hate this phone more and more. The only thing left is to unlock bootloader and play with other custom ROMs. But yeah, flashing the .232 firmware didn't fix it, AND flashing pure stock 5.1.1 Android didn't fix it either...
Just wondering if others have the same issue and any ideas what could be causing it? If I provide some Logcat logs, would someone be kind enough to look into this for me?
Update:
I'm still getting the random reboots and I think it's very likely to be hardware related. But sometimes also a bit related to software, specifically with Google Play services. I've had more time to test out a few things since my last update, they are as follows:
- Tested complete stock 4.4 ROM without root. Still crashes every now and then, but not as much compared to 5.0 and 6.0 (doesn't matter if it's stock or custom ROM).
- Finally gave in and unlocked bootloader (backed up my DRM keys of course). I thought perhaps that the stock Sony roms (and even the stock-based Sony custom roms) have issues for some reason. They are all the same base, so I thought I'd do a fair test by trying a completely different based rom, such as AOSP. I've used CM 1.2.1 nightly here:
forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201/page117
And yes, I know that nightly have bugs, but the nightly build as of 2016-03-03 seemed pretty stable according to most users. I've tried various other AOSP based roms and stock based Sony roms (for unlocked bootloaders) and they all produce crashes.
I've flashed custom kernels as well and updated my recovery to TWRP 3.0, but all the same results. On all of the custom ROMs I've flashed, the only thing I've done was setup my Google account (so I have my contacts and Gmail) and that was it. No other apps installed. I wanted to limit the environment down to just the stock setup of the ROM itself, as this helps me rule out any potential bugs caused by 3rd party apps.
Having done all of the above and still resulting in crashes, it's safe to assume that this is most likely unrelated to the software, but hardware. I've noticed that sometimes when I scroll a page too fast and move it up and down with my thumb, the screen will freeze and restart.
However, sometimes I will get crashes related to Google Play Services. Anything that relies on Google Play Services will crash randomly. If you re-open the apps, it just crashes again. If you force stop the app and open it, still crashes. The ONLY fix is to restart the phone. I have tried flashing different GaPPs, starting with the pico and nano versions, as well as the ones recommended by the ROM chefs. Still the same result.
So the conclusion is, I haven't really gotten anywhere with this annoying issue. There's definitely an issue with the phone somewhere, maybe a bit of software related, but mostly hardware.
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2
I own a BLU Pure XL, installed the custom CM12 rom to try out and I forgot to backup. I noticed someone uploaded the Stock Rom for 5.1 but for some reason It won't let me download anything from the play store showing it as paused all the time. I have cleared data for all the download apps,play store, and play store services within the apps section and installed a GAPP zip get the same result. The same error occurs with the OTA update saying cannot connect even with access to the internet and the ability to search the app store.
So if anyone has a stock 6.01 version and could upload it I would greatly appropriate it
I have the same problem. Unable to download anything from the play store. Still searching for a solution. Please let me know if you resolve this issue and I will do the same
I'm going through it ,too, thought about flashing Gionee ROM
Bought New Phone
I am not to much of a fan of the phone anyways so bought a BB Priv. If anyone finds a solution please post so I can have a backup phone
OK, I had to utilize the Gionee scatter file and stock ROM in order to get the phone partitioned correctly,
I then took the BLU Scatter file and Stock ROM , boot, and recovery and flashed it afterward. Then did a factory reset. Took updates then rooted, again. You are left with the Gionee splash screen... But that's an easy fix.
Appears that the versions of TWRP posted DO NOT partition the phone correctly and writes a TWRP partition that screws everything up.
I will post links or you can find them yourself in the meantime. They are all on xda mainly on the thread about rooting... Odd thing is. Phone seems to run better than before... I would have left the Gionee ROM up and running if it wasn't 4G only... I'll post links later.
Its been well documented to use the TWRP 2.8 not the 3,0 as it has issues partitioning. there is a whole thread about unbricking where we went into EXTENSIVE depth on this