I received by nothing phone 1 via beta membership (I'm in the US) and for some reason it refuses to communicate with Google servers. Whether during initial setup, trying to add a Google account, or trying to access the Play Store I am always faced with the error: There was a problem communicating with Google servers. Please try again later. I also am unable to check for updates. I get the error message: Updates are temporarily unavailable. Try again later.
I've tried two different SIMs/carriers, and three different known working WiFi networks. I did notice my phone is running Spacewar-S1.1-220813-1608EEA which implies is it's running the European firmware. Could this be what is causing the issue? Do I need to cross flash? I checked downdetector and Google doesn't appear to be having server issues at the moment. Any help or suggestions are greatly appreciated. Thanks!
wwwryan said:
I received by nothing phone 1 via beta membership (I'm in the US) and for some reason it refuses to communicate with Google servers. Whether during initial setup, trying to add a Google account, or trying to access the Play Store I am always faced with the error: There was a problem communicating with Google servers. Please try again later. I also am unable to check for updates. I get the error message: Updates are temporarily unavailable. Try again later.
I've tried two different SIMs/carriers, and three different known working WiFi networks. I did notice my phone is running Spacewar-S1.1-220813-1608EEA which implies is it's running the European firmware. Could this be what is causing the issue? Do I need to cross flash? I checked downdetector and Google doesn't appear to be having server issues at the moment. Any help or suggestions are greatly appreciated. Thanks!
Click to expand...
Click to collapse
For some reason when the sim card is inserted, it cannot connect to Google Update servers.
These are the steps I took to get my beta version working:
1. Removed sim card, factory reset, and followed the startup instructions with wi-fi only !important!.
2. After start up is complete check for updates and you should be able to connect to Google Servers/play store and download/update.
3. Then, after updates, you can shut down and insert your sim, and turn on. You can still access the Google Play store as normal, but the OS updates are still buggy.
I still have to figure out how to update with a new release is out.
Who-Lep said:
For some reason when the sim card is inserted, it cannot connect to Google Update servers.
These are the steps I took to get my beta version working:
1. Removed sim card, factory reset, and followed the startup instructions with wi-fi only !important!.
2. After start up is complete check for updates and you should be able to connect to Google Servers/play store and download/update.
3. Then, after updates, you can shut down and insert your sim, and turn on. You can still access the Google Play store as normal, but the OS updates are still buggy.
I still have to figure out how to update with a new release is out.
Click to expand...
Click to collapse
Thank you for your reply. I did just manually update to 1.1.1 via sideload. If on device OTA updates are buggy that is not a big deal. I don't mind manually updating as this phone is mostly just a test/play device and not my daily driver.
I will attempt the steps you mentioned and setup with WiFi only with no SIM card installed and see if that helps. Thanks again!
Random side question: Are you running 1.1.x latest or 1.5.x? If 1.5.x, is it worth upgrading for Android 13 or is it more buggy? Thanks!
@Who-Lep thank you so much, that indeed fixed the issue. Once I factory reset and completed all setup without any SIM card inserted communicating with Google servers worked correctly. Much appreciated!
wwwryan said:
@Who-Lep thank you so much, that indeed fixed the issue. Once I factory reset and completed all setup without any SIM card inserted communicating with Google servers worked correctly. Much appreciated!
Click to expand...
Click to collapse
Awesome, no problem, glad it worked out!
I went straight through all the updates to the latest beta 1.5.1 Beta 2, so I can't really compare but, no major bugs on newest release, only had to reboot once because of UI glitch and hasn't happen again.
Related
The updates are rolling out now for UK and WE tablets..
http://download.lenovo.com/slates/think/tablet1/
Where is the zip file?
I can't see the right one....
Edit: OMFG....i was too excited to see it.
Sry
How to update ?
http://forums.lenovo.com/t5/ThinkPa...y-install-updates-and-fix-stucked/td-p/579867
The us release is expected for 8 June 2012
I've lost my 3G connection after updating. It still shows signal strength etc but has no internet connection. I'm using an O2 Germany SIM card
There are some other people with the same problem at android-hilfe.de, so be careful if you need 3G, there might be some more SIM cards that stop working
Does anybody have a stock nandroid backup of A310_02/0039_0089_WE?
I cannot install the update because the checksum is wrong on a lot of files (20% of them to be precise).
Alternatively, I think a nandroid backup of a working OTA 4.0.3 would also work.
Hi!
I've got the same problem after deleting chinese FelxT9. No OTA possible and so I'm searching also for an nandroid backup WE for 3.1 or 4.0.3
Frank
Liftboy said:
Hi!
I've got the same problem after deleting chinese FelxT9. No OTA possible and so I'm searching also for an nandroid backup WE for 3.1 or 4.0.3
Frank
Click to expand...
Click to collapse
Here you have FlexT9chinese from my 0089_WE
I already made the update but CWM is gone and I cannot reinstall it.
You can also modify the update-script and remove the check for the missing files.
Mine keeps getting this error.
Android assert failed apply_patch_check ("/system/xbin/busybox)
I did factory reset but still the same error
The second problem now it cant connect to the router after the factory reset it keep saying obtaining ip number
Any idea what to do
Please help
ThinkPadTablet_A310_02_0039_0089_WE
moom999 said:
Mine keeps getting this error.
Android assert failed apply_patch_check ("/system/xbin/busybox)
I did factory reset but still the same error
The second problem now it cant connect to the router after the factory reset it keep saying obtaining ip number
Any idea what to do
Please help
ThinkPadTablet_A310_02_0039_0089_WE
Click to expand...
Click to collapse
If you have root and CWM-recovery installed you can remove the check for busybox and install the update via recovery-menu
moom999 said:
Mine keeps getting this error.
Android assert failed apply_patch_check ("/system/xbin/busybox)
I did factory reset but still the same error
The second problem now it cant connect to the router after the factory reset it keep saying obtaining ip number
Any idea what to do
Please help
ThinkPadTablet_A310_02_0039_0089_WE
Click to expand...
Click to collapse
Exactly the same as me and I've tried everything I can think of and come to the conclusion that 1. ICS isn't happening 2. The tablet is now broken.
Exe557 said:
If you have root and CWM-recovery installed you can remove the check for busybox and install the update via recovery-menu
Click to expand...
Click to collapse
It is not rooted and I could not root it now
OT: And the battery performance in 4.0.3 is still terrible.
The same problem to me!
To wifi connecting: you will be connected but you must change IP Settings to Static (not DHCP) and then manual entering IP etc.
dencho8 said:
The same problem to me!
To wifi connecting: you will be connected but you must change IP Settings to Static (not DHCP) and then manual entering IP etc.
Click to expand...
Click to collapse
Thanks it works for now
But it keep disconnecting and connecting from time to time
Any way it somehow works
But still can’t update it to ics
what about ROW?
Is there any info when this OTA update will be available also for rest of the world?
Can we say that this upgrade provided by Lenovo to ICS is not working well, regardless if the TPT's are root or not?
As anyone with non-rooted TPT made the official upgrade without problems?
Thanks
The real problem is Lenovo lacking willingness to supply us with a real factory image, so the tablet can be reflashed to absolute stock and reupdated.
It's like... your laptop breaking down because of software failure and then you can't even do a restore because you don't have the software. Only the patches provided by windows update.
Terrible move from Lenovo's side and I would consider taking it up with our consumer rights movement.
cristimv said:
Is there any info when this OTA update will be available also for rest of the world?
Click to expand...
Click to collapse
US approximately 6/8. ROW "later" per sticky below.
http://forums.lenovo.com/t5/ThinkPad-slate-tablets/Re-OTA3-update-ICS-4-03/m-p/755003#M14456
Hi guys,
So, a few days ago I decided to tryout One UI Beta 2.0. A few days it worked perfectly fine, but today, it said my pattern was wrong. So I read on the forums that more people had this issue, and that it was because of the beta. So I downloaded the original firmware for my device from SamFirm, and flashed it in Odin. Phone booted perfectly and I got through the setup progress. Then I wanted to set up a pattern but it wouldn't work. I need to register my pattern 2 times like always, but after that it ask me that I need to back up my pattern, so when I click continue, something comes up for a second that says please check your network connection. And then it just doesn't add it. I tried to install firmware 2 times now with Odin, but no luck, I keep getting the same message.
The first time when I installed the firmware when I got from the beta, I forgot to disable my google and Samsung account, IDK if that may caused it someway.
Edit: I updated apps in galaxy store, and now it doesn't say check your connection, it says backup completed. But it won't change to pattern for some reason. Stays on swipe to unlock.
I hope anyone can help me with this problem,
Kind regards,
Crewz
Flash your original firmware (not the One UI 2 beta) and after ODIN says done or successfully or whatever, unplug ya phone and boot into recovery and do a data factory reset. This should fix it.
ItsCrewz said:
Hi guys,
So, a few days ago I decided to tryout One UI Beta 2.0. A few days it worked perfectly fine, but today, it said my pattern was wrong. So I read on the forums that more people had this issue, and that it was because of the beta. So I downloaded the original firmware for my device from SamFirm, and flashed it in Odin. Phone booted perfectly and I got through the setup progress. Then I wanted to set up a pattern but it wouldn't work. I need to register my pattern 2 times like always, but after that it ask me that I need to back up my pattern, so when I click continue, something comes up for a second that says please check your network connection. And then it just doesn't add it. I tried to install firmware 2 times now with Odin, but no luck, I keep getting the same message.
The first time when I installed the firmware when I got from the beta, I forgot to disable my google and Samsung account, IDK if that may caused it someway.
Edit: I updated apps in galaxy store, and now it doesn't say check your connection, it says backup completed. But it won't change to pattern for some reason. Stays on swipe to unlock.
I hope anyone can help me with this problem,
Kind regards,
Crewz
Click to expand...
Click to collapse
A lot of people had this issue and it was fixed 3 days ago. After beta 2 I also faced the same issue. Dont do factory reset. Just install the third update which was emergency update to fix this specific issue. Download it from beta thread.
kazim.asghar said:
A lot of people had this issue and it was fixed 3 days ago. After beta 2 I also faced the same issue. Dont do factory reset. Just install the third update which was emergency update to fix this specific issue. Download it from beta thread.
Click to expand...
Click to collapse
Hi,
Okay, so with samfirm I downloaded my firmware and installed it with odin. So i tried the emergency update. I am trying to install beta 1 atm ( I read on the forums that you need to beta 1, 2 and the emergency ). but for some reason whenever I am trying to install it, I get the error "E3005 (LINK) has unexpected contents. Error in package.zip Status 7" I have no idea what to do anymore....
I received a new (to me) 2017 Shield via RMA from nVidia. I plug it in and go to set it up but when I get to entering your google account info, it consistently fails. The option to use androidtv dot com/setup and enter the provided PIN fails with "Something went wrong" (yes I'm on the same wifi, also fails when wired). The option to type in your account credentials also consistently fails saying my user name and password don't match. Now before you say "learn 2 type", immediately after not logging in, I get a security notification saying a new device has logged in to my account. This same result happens with any gmail account I try. I have factory reset the Shield (as instructed by nVidia support) to no avail. I have contacted Google support but they say it's nVidia's problem. I'm not sure what to do next. Any suggestions would be greatly appreciated.
Jesterium said:
I received a new (to me) 2017 Shield via RMA from nVidia. I plug it in and go to set it up but when I get to entering your google account info, it consistently fails. The option to use androidtv dot com/setup and enter the provided PIN fails with "Something went wrong" (yes I'm on the same wifi, also fails when wired). The option to type in your account credentials also consistently fails saying my user name and password don't match. Now before you say "learn 2 type", immediately after not logging in, I get a security notification saying a new device has logged in to my account. This same result happens with any gmail account I try. I have factory reset the Shield (as instructed by nVidia support) to no avail. I have contacted Google support but they say it's nVidia's problem. I'm not sure what to do next. Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I have the same problem. Did you manage to get this fixed by chance?
Yes. I fixed it by flashing a recovery image. 8.0.1 just caused a boot loop but flashing 8.0 worked.
https://developer.nvidia.com/gameworksdownload
Jesterium said:
Yes. I fixed it by flashing a recovery image. 8.0.1 just caused a boot loop but flashing 8.0 worked.
https://developer.nvidia.com/gameworksdownload
Click to expand...
Click to collapse
Thanks for getting back to me. I assume that to flash a recovery image, I'll need to unlock the bootloader? I was trying to avoid flashing, but it doesn't look like another solution will work...
Aripex said:
Thanks for getting back to me. I assume that to flash a recovery image, I'll need to unlock the bootloader? I was trying to avoid flashing, but it doesn't look like another solution will work...
Click to expand...
Click to collapse
I tried quite literally everything I could think of - multiple google accounts, different networks including hot-spotting my cell service, multiple factory resets. It seems my problem may have been a very outdated OS as after I was able to flash, the setup process was in a newer android style. It didn't occur to me that what I was seeing previously was "old" and may explain why it wouldn't connect to google.
Keep in mind, you can lock the bootloader again when you're finished.
Jesterium said:
I tried quite literally everything I could think of - multiple google accounts, different networks including hot-spotting my cell service, multiple factory resets. It seems my problem may have been a very outdated OS as after I was able to flash, the setup process was in a newer android style. It didn't occur to me that what I was seeing previously was "old" and may explain why it wouldn't connect to google.
Keep in mind, you can lock the bootloader again when you're finished.
Click to expand...
Click to collapse
Cool - thanks for the advice. Like you, I tried everything too. I tried 2FA on/off, turned on the "Less secure apps" option in my Google Account > Security. I also tried to factory reset without any success, as well as using a different Wi-Fi network and opened a new dummy Google Account just to make sure my original account wasn't the problem! None of it worked and had me tearing my hair out.
I have a 2015 Shield TV that was sealed and unused until the last week. I have never seen an issue before where even an older Android device cannot be signed into Google. At least it is a lesson learned for the future....!
Anyway, I've successfully flashed a newer version of Android now and it works. Hallelujah!
Right guys I have just got a replacement NVidia pro 500gb from them for a bricked unit and I am having the same problem. As I am a novice I have no clue about flashing an updated image to it. Is there anyone who is will to spell it out for me in easy to follow instructions??
My Verizon Note 8 just received an update (N950USQU8DVB1) but I had thought that the phone was out of support and was not going to get any more updates. I don't see mention of this one on the Verizon update page. Does anyone know what this is about and why we are getting an update after the support window is over?
Hmmm. Just got the Verizon update also..it does show on web page now as available.
No idea why this came in a year after support ended...lots more than just security updates it seems. Glad I kept it
Can anyone confirm if this update made voLTE available?
Does anyone have the files available yet to download and flash?
I don't see them on sammobile.com yet, but I would like to get a copy if anyone can help.
This updated broke my phone. I updated last night and now I have a "No sim card" message. I took my phone to a repair shop and they couldn't fix it. They suggested maybe a flash/roll back, but they wouldn't do it for me. My phone was perfectly fine before I updated. Good times..............
Try booting to recovery mode and wiping the cache partition. My friend had a dual sim version and sim not found message happened to him, wiping cache and double checking network was set to auto fixed it for him.
Another method may be trying to connect to windows and download Verizon software assistant and select repair phone. Takes a while to download everything so be patient until it finishes. I recall it took a half hour. Hope it helps.
Hello everyone. I recently purchased a used Pixel 4. Past owner said WiFi+Data stopped working after updating Android and that the phone is unlocked and carrier-free. I need to unlock bootloader in order to install GrapheneOS but it is greyed out. As you can see in the screenshots, it seems like the phone is not recognizing WiFi and IMEI hardware while booted. IMEI does show up in the barcode menu option in fastboot. System UI crashes if I try to open WiFi config. The only thing I could try was tethering via Bluetooth from my other phone and updating Android OS and apps. Already tried wiping everything and forcing phone to connect to Google while on Bluetooth tethering by pressing (*#*#2432546#*#*) in the dialer as sugested here: https://source.android.com/setup/contribute/flash#preparing-your-device
This doesn't show any success or error message.
One thing that may have happened is this: https://www.phonearena.com/news/google-pixel-android-12-verizon-update-issue_id136367
Apparently Google sent OTA Verizon update to unlocked Pixel 4's by mistake. Maybe the wrong software is what is making it not recognize WiFi+Data?
Current installed build is 12.1.0 (SQ3A.220605.009.A1, Jun 2022). Maybe I should wait for a new SP* instead of SQ* build to come out and try installing it? This is because P is for the main platform branch as explained here: https://source.android.com/setup/start/build-numbers#build-ids-defined
Hopefully it comes out before October since that is the end-of-support date.
OTA builds: https://developers.google.com/android/ota#flame
Other option would be to try out this but it seems the riskiest and last resort option:
Unlock carrier locked bootloader Pixel [BETA]
UPDATE AS OF 16 OF MAY 2023 This project isn't working right now, but I am still working on it. However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get...
forum.xda-developers.com
And yet another option would be to purchase a new board and replace it.
What do you think? I tried submiting the IMEI to T-Mobile's site and it says it is OK to be ported. Verizon's site didn't let me submit the IMEI I don't know why. And for AT&T I didn't find any site for that. IMEI checks say it is not blacklisted.
Did u solve this?