So I've never had any issues with the Play Store before. Just a few days ago it was working fine. Now, I get the attached screen when I try to look for updates. I've cleared cache and data for the store, play services, etc. I've removed and re-added my Google account. Rebooted the device. I've tried everything I can think of. Has anyone ever encountered this?
TheIgster said:
So I've never had any issues with the Play Store before. Just a few days ago it was working fine. Now, I get the attached screen when I try to look for updates. I've cleared cache and data for the store, play services, etc. I've removed and re-added my Google account. Rebooted the device. I've tried everything I can think of. Has anyone ever encountered this?
Click to expand...
Click to collapse
+1 Can confirm that I have the same issue as well.
I haven't contacted Google yet because ultimately their advice is to format the device and that's a silly way to fix issues and takes so much time.
After a certain amount of time the updates listed under the Updates section will go away. My last one went away yesterday afternoon (Snapchat). If you don't have any updates to apps then you won't see anything there. There's nothing wrong with that. It's funny that you post about it because I just happen to take a screenshot of mine last night. It was empty like yours, but today I got one update, and now that one app shows.
bobbyphoenix said:
After a certain amount of time the updates listed under the Updates section will go away. My last one went away yesterday afternoon (Snapchat). If you don't have any updates to apps then you won't see anything there. There's nothing wrong with that. It's funny that you post about it because I just happen to take a screenshot of mine last night. It was empty like yours, but today I got one update, and now that one app shows.
Click to expand...
Click to collapse
Sorry, that's not the issue. Look at your screen shot and look at mine. See all the white space where apps are supposed to be on mine and see how there is no white space on yours? I have had it like your screen as well. But not with all the white space. There is truly an issue here.
TheIgster said:
Sorry, that's not the issue. Look at your screen shot and look at mine. See all the white space where apps are supposed to be on mine and see how there is no white space on yours? I have had it like your screen as well. But not with all the white space. There is truly an issue here.
Click to expand...
Click to collapse
Gotcha. I read what you tried also, and you don't mention if you tried uninstalling updates for the Play Store. Did you try that?
bobbyphoenix said:
Gotcha. I read what you tried also, and you don't mention if you tried uninstalling updates for the Play Store. Did you try that?
Click to expand...
Click to collapse
Yup.
I spent over an hour on chat with Google yesterday and we tried pretty much everything. They admit it is a bug. They want me to format the device. They are working on a fix currently and I am working with other "specialists" there before factory resetting my device. Good times.
TheIgster said:
Yup.
I spent over an hour on chat with Google yesterday and we tried pretty much everything. They admit it is a bug. They want me to format the device. They are working on a fix currently and I am working with other "specialists" there before factory resetting my device. Good times.
Click to expand...
Click to collapse
How long do you think it would take to do a factory reset as suggested vs all the time you have spent with support? I assume you are bl locked and unrooted so you can't flash a factory image.
TheIgster said:
Yup.
I spent over an hour on chat with Google yesterday and we tried pretty much everything. They admit it is a bug. They want me to format the device. They are working on a fix currently and I am working with other "specialists" there before factory resetting my device. Good times.
Click to expand...
Click to collapse
bobby janow said:
How long do you think it would take to do a factory reset as suggested vs all the time you have spent with support? I assume you are bl locked and unrooted so you can't flash a factory image.
Click to expand...
Click to collapse
They will likely keep replying to you (from different "specialists") asking you to do a ton of extra work that has no more reliability than the methods you could think of. Like bobby mentioned, flashing the factory image would be the best 1st step, but if not possible have you tried side loading the OTA through stock recovery?
sliding_billy said:
They will likely keep replying to you (from different "specialists") asking you to do a ton of extra work that has no more reliability than the methods you could think of. Like bobby mentioned, flashing the factory image would be the best 1st step, but if not possible have you tried side loading the OTA through stock recovery?
Click to expand...
Click to collapse
I haven't unlocked the bl in years so correct me if I'm wrong. You can't do anything other than sideload an OTA if it's locked? So the options, if that is correct, are what you said, OTA sideload or if it's not a VZW model (and the sideload didn't work) unlock the bl, that'll cause a reset, flash the full Dec factory image, then bl lock again. (another factory reset). Bet that'll fix the problem. And the whole shebang will take under an hour.
bobby janow said:
I haven't unlocked the bl in years so correct me if I'm wrong. You can't do anything other than sideload an OTA if it's locked? So the options, if that is correct, are what you said, OTA sideload or if it's not a VZW model (and the sideload didn't work) unlock the bl, that'll cause a reset, flash the full Dec factory image, then bl lock again. (another factory reset). Bet that'll fix the problem. And the whole shebang will take under an hour.
Click to expand...
Click to collapse
Pretty much, Bobby. If Verizon/locked BL, sideload current OTA (no downgrade possible). If you have a Google variant, you can still sideload OTA or unlock the BL (causing a reset) and then flash the factory image. If you go that route, I probably wouldn't re-lock the BL since stuff like this is as much a reason to keep the BL unlocked as rooting and other tinkering.
sliding_billy said:
Pretty much, Bobby. If Verizon/locked BL, sideload current OTA (no downgrade possible). If you have a Google variant, you can still sideload OTA or unlock the BL (causing a reset) and then flash the factory image. If you go that route, I probably wouldn't re-lock the BL since stuff like this is as much a reason to keep the BL unlocked as rooting and other tinkering.
Click to expand...
Click to collapse
Great, thanks. Only thing is if the OP is as security conscience as I am then relock. If not leave it as is. Being able to recover with a factory image is the only thing I miss. It's a big one too but I'm on VZW so I have no option. He could always leave the OEM switch enabled if ever it was needed again I guess.
I'm curious how this gets resolved as he's not the only one with this issue.
bobby janow said:
How long do you think it would take to do a factory reset as suggested vs all the time you have spent with support? I assume you are bl locked and unrooted so you can't flash a factory image.
Click to expand...
Click to collapse
Oh this will definitely take longer than factory resetting the device, but as an ex software developer, I have to see this through and make Google work. If they find and solve the issue, this will help others who have the issue or stop them from having the problem in the first place. It's a bug that needs to be fixed IMO and being on them about this is the way to go. Sure I could just go away and factory reset, but this way, they have to deal with it.
See the attached pic I took today. After installing an app, this appeared on the updates page. The white space is clearly a bug and it needs to be addressed. If they don't solve this by the new year and I can't get updates for apps I use a lot, then fine, I'll factory reset, but I think they should be aware of this issue and they should have to fix it.
bobby janow said:
I haven't unlocked the bl in years so correct me if I'm wrong. You can't do anything other than sideload an OTA if it's locked? So the options, if that is correct, are what you said, OTA sideload or if it's not a VZW model (and the sideload didn't work) unlock the bl, that'll cause a reset, flash the full Dec factory image, then bl lock again. (another factory reset). Bet that'll fix the problem. And the whole shebang will take under an hour.
Click to expand...
Click to collapse
It's not the factory reset, it's remembering all the passwords for the various apps I have, settings, placement of icons, widgets, etc. It is a pain in the a** to reset a device. Besides, I just got this thing set the way I wanted it setup in the last couple of weeks. I haven't even had it for a month.
TheIgster said:
It's not the factory reset, it's remembering all the passwords for the various apps I have, settings, placement of icons, widgets, etc. It is a pain in the a** to reset a device. Besides, I just got this thing set the way I wanted it setup in the last couple of weeks. I haven't even had it for a month.
Click to expand...
Click to collapse
I can certainly appreciate making Google fix this as well as your setup you currently have. However, I seem to recall that when I did a factory reset all the apps and wallpaper and location of icons were imported from I guess Google cloud? Passwords were not though. Time to pull out that yellow notepad and go over those. lol BTW, are you bl unlocked and have you rooted or modified the system in any way? That was not clear from you OP.
bobby janow said:
lol BTW, are you bl unlocked and have you rooted or modified the system in any way? That was not clear from you OP.
Click to expand...
Click to collapse
My bootloader is locked and I've never rooted my pixel 3 XL, yet I'm experiencing the same issue that the op is facing.
MadCow809 said:
My bootloader is locked and I've never rooted my pixel 3 XL, yet I'm experiencing the same issue that the op is facing.
Click to expand...
Click to collapse
And this happened just all of a sudden? You have any thoughts on why or if perhaps an app screwed things up? Stock launcher? Some setting perhaps? Very curious isn't it? And since it's not very widespread it would be nice to know in order to avoid it.
TheIgster said:
So I've never had any issues with the Play Store before. Just a few days ago it was working fine. Now, I get the attached screen when I try to look for updates. I've cleared cache and data for the store, play services, etc. I've removed and re-added my Google account. Rebooted the device. I've tried everything I can think of. Has anyone ever encountered this?
Click to expand...
Click to collapse
Just to clarify, is it just a cosmetic issue with displaying extra white space on that screen, or is there some other functional problem?
samnada said:
Just to clarify, is it just a cosmetic issue with displaying extra white space on that screen, or is there some other functional problem?
Click to expand...
Click to collapse
The white space was never there before and is not there on other devices that I have encountered. Do you have the white space on your device? Also, updates are not appearing to happen properly either. The only reason I saw that one update is because I just installed another app and it updated one app right after that. I normally have numerous updates, daily.
Google has already admitted to and are working on this as a bug.
TheIgster said:
The white space was never there before and is not there on other devices that I have encountered. Do you have the white space on your device? Also, updates are not appearing to happen properly either. The only reason I saw that one update is because I just installed another app and it updated one app right after that. I normally have numerous updates, daily.
Google has already admitted to and are working on this as a bug.
Click to expand...
Click to collapse
But.. But. 3 people with this issue and they are calling it a bug? Are they blowing some smoke your way? Is there a tracker for this? CSR are notorious for playing the game until you give up. Be wary. I say factory reset and fix it yourself. You have spent way too much time on this I fear. But it's your call at this point. Keep us posted.
Related
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
mac796 said:
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
Click to expand...
Click to collapse
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
mlin said:
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
Click to expand...
Click to collapse
It's very strange happens on both my pixels so must be a bug on googles side maybe.
mac796 said:
It's very strange happens on both my pixels so must be a bug on googles side maybe.
Click to expand...
Click to collapse
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
mlin said:
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
Click to expand...
Click to collapse
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
mac796 said:
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
Click to expand...
Click to collapse
I flashed the factory image on release day and OTA'd to September security patch. No dice.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So it's still not working for you? Maybe I'll just wait till next update then.
mac796 said:
So it's still not working for you? Maybe I'll just wait till next update then.
Click to expand...
Click to collapse
Nope, still not working. I'll let you know if my efforts tomorrow are successful.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
mac796 said:
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
Click to expand...
Click to collapse
Lol, weird. So just reflash before each app purchase and you should be good!
mlin said:
Lol, weird. So just reflash before each app purchase and you should be good!
Click to expand...
Click to collapse
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
mac796 said:
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
Click to expand...
Click to collapse
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
mlin said:
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
Click to expand...
Click to collapse
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
mac796 said:
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
Click to expand...
Click to collapse
Did you wipe data as well?
mlin said:
Did you wipe data as well?
Click to expand...
Click to collapse
Yes I wiped everything except internal storage
mac796 said:
Yes I wiped everything except internal storage
Click to expand...
Click to collapse
I did wipe internal storage, though hard to say if that difference made it work. I'd be curious to hear if you do get it working eventually or if you find a different solution. Best of luck, hope you get it resolved eventually though I get the appeal of being unable to buy apps lol.
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????
Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?
Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:
I can confirm this working again. Pixel 2 XL with 9.0 and November security update.
Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!
michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?
Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.
I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.
My pixel xl started bootlooping. I can get into fastboot but that's it. If I try to boot twrp, bootloop, if I flash stock, bootloop. I've tried Oreo, pie. This came out of nowhere. I tried a gsi, bootloop. I'm very confused. The memory works because its flashing. Something has to be triggering a reboot. Only thing I know of that forces restart is unencrypted internal storage
same here... any updates?
ferydaboss said:
same here... any updates?
Click to expand...
Click to collapse
I just sat down to try again, I will keep you posted. this is a dev device for me so its kind of annoying it would randomly brick for no reason. luckily I always keep the bootloader unlocked
godkingofcanada said:
I just sat down to try again, I will keep you posted. this is a dev device for me so its kind of annoying it would randomly brick for no reason. luckily I always keep the bootloader unlocked
Click to expand...
Click to collapse
This was my personal device, got out of warranty, no google store or any other youbreakwefixit stores near me, and it just bricked by itself. No root,no custom rom, nothing i can barely get into Recovery mode, and when i do, i install the latest OTA, and hope for the best Thanks
ferydaboss said:
This was my personal device, got out of warranty, no google store or any other youbreakwefixit stores near me, and it just bricked by itself. No root,no custom rom, nothing i can barely get into Recovery mode, and when i do, i install the latest OTA, and hope for the best Thanks
Click to expand...
Click to collapse
I bought a one plus literally a week ago. Lucky on my end. Whatever google did it is bad. I opened up the kernel and disabled the securities. Unencrypted the data. Still nothing. I've manually flashed over every partition 1 by 1, switched to the other slot and tried there. This looks like its going to be a battle. I've got a feeling what we flash isn't copying over some things because it keeps the newest version, which is why we can flash but not overwrite the problem
godkingofcanada said:
I bought a one plus literally a week ago. Lucky on my end. Whatever google did it is bad. I opened up the kernel and disabled the securities. Unencrypted the data. Still nothing. I've manually flashed over every partition 1 by 1, switched to the other slot and tried there. This looks like its going to be a battle. I've got a feeling what we flash isn't copying over some things because it keeps the newest version, which is why we can flash but not overwrite the problem
Click to expand...
Click to collapse
So... there may be a solution in the near future? seeing that google themselves did this? because it is a coincidence, that i see literally 5 pots about the same problem under 4 days..
ferydaboss said:
So... there may be a solution in the near future? seeing that google themselves did this? because it is a coincidence, that i see literally 5 pots about the same problem under 4 days..
Click to expand...
Click to collapse
Google's update hurt some pixel devices, but they expect us to RMA repair the device... I went the other direction and opened it up to tinker with instead
mi wifes pixel is having the exact same issue.
google says im out of warranty so some of the patches ****ed us up....
Hi Everyone, thanks for helping me,
I have XT1789-05, Some apps can't access internet and some apps can access internet, with WiFi or Mobile Data, nothing change, in another device the apps not working in My Moto Z2 Force, will work fine, even I have Moto X 1st, all apps work fine in the Moto X, but in the Moto Z2, some apps when opened error can't access the internet, I searched and googled everywhere, I can't find a solution, can you help me please?
I already did a clear cache, clear data, uninstall and install again, only some apps has this issue, it's a completely strange problem, for example, this app not work as well: Ziraat Mobile (This app for Ziraat Bank in Turkey) here is the Google Play download link: play.google.com/store/apps/details?id=com.ziraat.ziraatmobil
I can't add URL, adding by yourself, please
another app: Radio Javan
play.google.com/store/apps/details?id=com.radiojavan.androidradio
please help me to solve this issue
one time I uninstalled Antivirus (Eset Mobile Security) as well, or any apps I thought to cause the problem, still I have the problem, I'm completely confused, please help me, I have one XT1789-02 and it's working fine with same apps, but my Phone XT1789-05 has problems!!!!!!!!
The Best Paul and Joseph Galvin (I Will Love Motorola Ever...)
Hi,
Did it work well before?
Did you do a full fw flashing before?
Have you tried to change the radio in *#*#4636#*#* yet?
mr_5kool said:
Hi,
Did it work well before?
Did you do a full fw flashing before?
Have you tried to change the radio in *#*#4636#*#* yet?
Click to expand...
Click to collapse
It's a new Phone
No Full Flashing before or even now
I tried to change Radio, thanks for your trick, but it does not work!!!!
I still need your help
It's a weird problem. I think you should do a full fw flashing if you bought a 2nd phone. If it's a brand new one, I have no idea about this situation :"|
mr_5kool said:
It's a weird problem. I think you should do a full fw flashing if you bought a 2nd phone. If it's a brand new one, I have no idea about this situation :"|
Click to expand...
Click to collapse
I have no Idea too, I'm going to crazy,
Have you tried a factory reset and use a different Google account? It could be restoring a setting or app causing it
Uzephi said:
Have you tried a factory reset and use a different Google account? It could be restoring a setting or app causing it
Click to expand...
Click to collapse
I used new account no restore anything, I don't want to reset factory because, I have Internet Bank with a digital sign, and I'm abroad, can't go to the bank, so reset factory not a good option
thanks a lot, give me another solution please
AHMN48 said:
I used new account no restore anything, I don't want to reset factory because, I have Internet Bank with a digital sign, and I'm abroad, can't go to the bank, so reset factory not a good option
thanks a lot, give me another solution please
Click to expand...
Click to collapse
I can't help further unless you cooperate to troubleshoot. When you are able to factory reset to nuke any stuck bits and start fresh on a new Google account, (not a secondary one you already have, a brand new one) then we can try pulling a log from a fresh install to see what is blocking it.
Edit: the factory reset would need to be followed up with a fastboot -w command to ensure everything is wiped. If you don't want to do this, then you cannot be helped.
Uzephi said:
I can't help further unless you cooperate to troubleshoot. When you are able to factory reset to nuke any stuck bits and start fresh on a new Google account, (not a secondary one you already have, a brand new one) then we can try pulling a log from a fresh install to see what is blocking it.
Edit: the factory reset would need to be followed up with a fastboot -w command to ensure everything is wiped. If you don't want to do this, then you cannot be helped.
Click to expand...
Click to collapse
so what next?
I did several times reset factory
one time from Setting
and two times from Recovery Mode
Still has the problem on some apps, ohhhh my god, I'm driving crazy!!!!!
I don't know what's the problem, some apps force close, some apps can't access the internet and most apps work fine
help me, please
is it grey import?
AHMN48 said:
so what next?
I did several times reset factory
one time from Setting
and two times from Recovery Mode
Still has the problem on some apps, ohhhh my god, I'm driving crazy!!!!!
I don't know what's the problem, some apps force close, some apps can't access the internet and most apps work fine
help me, please
Click to expand...
Click to collapse
Did you buy it online?
Besides the model, what is your software channel and build number for your phone?
i had similar problem and factory reset still resulted with the same issue. I had to do a full retail rom reinstallation and that fixed the problem.
harkoliar said:
Did you buy it online?
Besides the model, what is your software channel and build number for your phone?
i had similar problem and factory reset still resulted with the same issue. I had to do a full retail rom reinstallation and that fixed the problem.
Click to expand...
Click to collapse
Yes, I bought it online from coolicool.com, this is first time ever I bought one Moto from outside of USA,
Software Channel: retcn
Build Number: OPXS27.109-52-10
Thanks for helping me
The model and build is exactly like mine when I first got it.
First off, I think it's how they flashed the rom that's causing the instability. Your phone would most likely have it's bootloader unlocked like mine but they did something to hide the warning message.
Please read my thread.
https://forum.xda-developers.com/z2-force/help/request-advice-experts-tourbleshooting-t3928349
You will see that I flashed a retail rom using instructions from this thread. It would be step E of the thread. Worked like a charm for me in fixing all the unstable apps
https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
You will have to flash your phone so you really have to follow the step by
step instructions.
I did it for the first time in my thread, it's not hard to do step E if you follow it step by step.
Hah, mine was from coolicool with random issues too. Emailed them, no response. Paypal claim, no respond. Full refund!
Will follow the guide above.
Just check first if bootloader is unlocked. (That's step a). Before you proceed to step E.
I'm assuming it's already unlocked because we have the same issues, build and model number. Mine was unlocked when I received mine. Also from China/hk
harkoliar said:
Just check first if bootloader is unlocked. (That's step a). Before you proceed to step E.
I'm assuming it's already unlocked because we have the same issues, build and model number. Mine was unlocked when I received mine. Also from China/hk
Click to expand...
Click to collapse
why it's unlocked?
it's not Original and it's not from Motorola?
I saw in bootloader it's flashing_unlocked and I was surprised why unlocked????
are you sure if I do these steps problem will solve and also are you sure after installing new stock ROM dual sim work well?
AHMN48 said:
why it's unlocked?
it's not Original and it's not from Motorola?
I saw in bootloader it's flashing_unlocked and I was surprised why unlocked????
are you sure if I do these steps problem will solve and also are you sure after installing new stock ROM dual sim work well?
Click to expand...
Click to collapse
This is my pure speculation. the reason why its unlocked is because it was originally a chinese phone with chinese roms that doesnt have playstore. That must have been the original setting. Since they want to sell it to the international market, they had to unlock the phone and voiding the warranty, flash it with the new international rom before selling it.
Since its unlocked, essentially the warranty on your phone is void. The issue i found is that they must have flashed the wrong rom so its causing all these apps to crash.
Again thats all speculation and theory.
Now the only reason why I'm suggesting this method with you is because I had the same issue, I researched and tried the solution I posted. It worked for me. If you are going to flash a stock rom for the first time, you just do your research and do it one step at a time. Instructions have been provided in the second link (step E) including all the files you require to install the retail rom. It worked for me. I can only suggest, but it's up for you to give it a go.
I loaded the latest RETAIL (-05) factory image and all apps are functioning fine now. Issue was supplier had flashed -06 ROM, assuming because it said APAC in the description.
happy it worked
ben0551 said:
I loaded the latest RETAIL (-05) factory image and all apps are functioning fine now. Issue was supplier had flashed -06 ROM, assuming because it said APAC in the description.
Click to expand...
Click to collapse
glad it worked!
harkoliar said:
glad it worked!
Click to expand...
Click to collapse
I was so confused during the last month. The random apps that were impacted by the issue didn't make sense...
Banking app
ABC Kids Listen App
Kids Daycare App
FuelCheck
Images on CyberFlix
Only one of the devs managed to get their app working for me in the odd state it was in. DayCare app of all things!
Thanks for posting, I wouldn't have thought to reflash or even look at the region code of the flashed rom compared to the compatible one.
ben0551 said:
I was so confused during the last month. The random apps that were impacted by the issue didn't make sense...
Banking app
ABC Kids Listen App
Kids Daycare App
FuelCheck
Images on CyberFlix
Only one of the devs managed to get their app working for me in the odd state it was in. DayCare app of all things!
Thanks for posting, I wouldn't have thought to reflash or even look at the region code of the flashed rom compared to the compatible one.
Click to expand...
Click to collapse
Yeah it was so random, i really thought i got a faulty phone. Mine was all GPS/ internet related (Uber, Spotify, maps)
Nothing made sense but I took the research and decided to flash to stock rom, discovering they installed the wrong ROM and HIDING the fact the bootloader was unlocked. Definitely not your average issue and hopefully this would help other people who are in similar situation buying from any china/hk store.
I even bought the moto mods, and they are working perfectly after reflashing. Pretty happy with overall result.
Not much to say.
When I open camera app I get a pop up saying camera failed.
I have force stopped app clear data and cache and restarted. Didn't work. I have factory reset. I got the phone back in June under Verizon.
Any tips on getting this fixed would be great.
Thanks
thayl0 said:
Not much to say.
When I open camera app I get a pop up saying camera failed.
I have force stopped app clear data and cache and restarted. Didn't work. I have factory reset. I got the phone back in June under Verizon.
Any tips on getting this fixed would be great.
Thanks
Click to expand...
Click to collapse
try to wype partition cache
UNIK97122 said:
try to wype partition cache
Click to expand...
Click to collapse
I have done that as well through bootloader. Forgot to mention. It may be a software issue. I flash a older firmware and the camera worked. I let it update and it worked but after a few hours it stopped working. I've yet to let it stay on the software version that works for more then few minutes.
thayl0 said:
I have done that as well through bootloader. Forgot to mention. It may be a software issue. I flash a older firmware and the camera worked. I let it update and it worked but after a few hours it stopped working. I've yet to let it stay on the software version that works for more then few minutes.
Click to expand...
Click to collapse
do you have the same with another camera app ?
Updates are overated... if I have a stable load that's running well I leave it alone.
I've run outdated OS's on Android for years with no major issues or forced reloads because of it.
Old firmware/software doesn't break Androids but new ones sure as hell can...
Still running on Pie on my 10+ with no plans to go to Q.
blackhawk said:
Updates are overated... if I have a stable load that's running well I leave it alone.
I've run outdated OS's on Android for years with no major issues or forced reloads because of it.
Old firmware/software doesn't break Androids but new ones sure as hell can...
Still running on Pie on my 10+ with no plans to go to Q.
Click to expand...
Click to collapse
Sadly I don't think I can go back to pie I believe there's a different bootloader version
thayl0 said:
Sadly I don't think I can go back to pie I believe there's a different bootloader version
Click to expand...
Click to collapse
Try the new Beta,it might fix it
TheViciousGames said:
Try the new Beta,it might fix it
Click to expand...
Click to collapse
Trying to find the first beta so it can update to latest. No luck so far
thayl0 said:
Sadly I don't think I can go back to pie I believe there's a different bootloader version
Click to expand...
Click to collapse
Yeah they like to lock the doors behind you... just remember the lesson.
I learned the hard way with Kitkat; the last update did nothing except make easy root impossible.
With lollipop AT&T/Samsung purposely screwed up the graphics on just that old model for contacts and the music play list making the S4+ next to unusable.
They'll say it will run better, be more secure.
BS.
Never had a OS "upgrade" that wasn't bigger, hoggier and slower then the original on Android.
Never in 6 years of running outdated OS's on Androids had to do a reload from a virus or worm.
Sure it can happen but rarely does if you don't do stupid things.
Play with it, eventually you'll sort it out
Androids wuv being played with...