Related
So I called up Google about the problem I started recently having with Google wallet. I get the error message that the secure element stopped responding. Upon searching online the issue seems to still not to be resolved even with other officially supported devices. Google transferred me to Samsung rep who seemed to have never heard of the issue or received any guidance from her employer on steps to take towards a resolution. Her only idea seems to be for me to mail them my phone on the off chance that they might be able to fix it.
Has anyone else had this issue come up and either get it fixed or any other result?
I really wanted to try out Google wallet, but after this happened I am going to stay away unless they figure out how to fix it without replacement of my perfectly working brand new phone. The thought of being sent a refurbished phone as a replacement sickens me.
Sent from my Galaxy Nexus using Tapatalk 2
I'm really curious about this too. Used Google Wallet today and it's pretty cool. Then I lost my dialer while trying to add inverted gapps to Apex. I'd normally just flash another rom but I don't want to mess up that secure element. :-/
I'm guessing you did a factory reset.
Read this. http://www.droid-life.com/2012/05/2...let-forever-learn-how-to-safeguard-your-info/
Sent from my Galaxy Nexus using Tapatalk 2
You killed it! You murderer!
Seriously, it's dead Jim.
It self destructs if it thinks you are trying to tamper with it; a countermeasure to keep somebody from stealing your account info. Only solution is to RMA the phone under warranty.
Rma?
Through Samsung, Verizon or an insurance claim? I had a 1 chat session with Samsung (Complete waste of time)
It's dead, only way to fix it is to get a different replacement phone.
Glad I still have a backup of stock rooted thank you qbking tutorials.
Sent from my Galaxy Nexus using xda premium
Although I never saw a secure element error, my wallet was stuck at "initializing" forever. It happened after I wiped data to go to a newer build of AOKP. I hadn't heard about doing the reset from within the wallet app to prevent it. I've updated ROM's and flashed many times, as well as many factory resets since, and it still occurs.
Today I updated to the latest market release of wallet. It now walks me thru activation, but hangs at "Activating account" forever now instead. I'm sure they're all the same issue.
Now, I have some thoughts on this. Recently Titanium Backup added a new feature. After doing a "wipe data / factory reset" in CWM, you now get prompted when you open TiBackup, that the device ID has changed, and it asks if you want to restore back to a backed up one. If you choose yes, it immediately applies it and reboots. Now, since they just added this feature, I only have a recent one backed up. But I wonder if this isn't the whole problem? TiBackup says it's how apps recognize that they're installed on your specific device and it can break licenses etc.
I wonder if I had the device ID from when I first installed Wallet, if that's all i would need to fix this?
Thoughts?
I called Google and Samsung the result is that I have to send in my phone for repair, not a replacement.
Sent from my HTC One X using Tapatalk 2
aturyan said:
I called Google and Samsung the result is that I have to send in my phone for repair, not a replacement.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
And it hardly seems worth it for something silly like Google wallet. I'll just not even bother with it. The nfc still works and that's the important part.
Sent from my Galaxy Nexus using Tapatalk 2
Literally every time i check for software updates i get
"Communication failed"
The server is currently unavailable.
Your device will automatically check for an update within the next 48 hours.
Then if i check again it says device is up to date, you can check for updates again in XXhours. If i go into application manager -> AT&T Software Update and clear data, i can check for updates again but i get the same communication failed. I also tried clearing data and rebooting phone, and it still wont check.
And i can't get Samsung Kies running on my windows 7 pc for some reason, so i can't get updates from there either.
Is anyone else on AT&T experiencing these problems? Any fix for this? I really want that update that adds brightness control to the notification menu.
jefferson9 said:
I really want that update that adds brightness control to the notification menu.
Click to expand...
Click to collapse
I did not update, but hearing that update would disable local search, add new modem. Nothing about Brightness control
There is no brightness control on ATT update. I was having the same problem you were and exchanged the phone. There is no fix as far as I know for the error you are getting. It is a common issue. Search the annoyances (bugs) thread.
I don't know if the OTA update resolves your issue because they day after I exchanged mine the update came out.
Sent from my SAMSUNG-SGH-I717 using xda premium
I also haven't been able to get the OTA update. I assumed it was because I rooted and the device is listed as 'modified'. Is the update worth it?
It is in my opinion, and my usage habbits, for the WiFi stability increase that is gained.
Universal search is stripped (searches conducted on phone do not include on device results, ie contacts).
In other words, if you use the Google search by long pressing your menu button the results from your search will only be pulled from the internet.
I rarely use the search built in, so it hardly mattered to me.
Check out the developer forum for ways around the universal strip if you are rooted and want to update.
Sent from my SAMSUNG-SGH-I747 using xda premium
Well i reseated the SIM card, and removed the little blue tape from the sd slot and the SIM slot, rebooted and still not working.
I wanted to avoid rooting, since the stock software runs so smoothly and i liked being on the latest at&t software. I guess since i can't get OTA updates now theres no reason not to root.
Will this issue be fixed eventually? Or would i be better off exchanging phones while i can?
I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
the1stSecond said:
I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Well speaking as a software engineer, i'm almost certain its a software issue, most likely with at&t's software update app, or on their servers. Mabey reinstalling the at&t software update application will help?
It sounds reasonable to me. Maybe try the method for No trip flash counter in devoplment? You would be upgrading to the newest firmware and have root and not trip the flash counter. You would still be able to check for ota updates (although should just return the status of your software is up to date since it is a totally stock ROM just with root injected). I imagine that would reinstall the software update service. Although with your knowledge you are way over my head. And whether or not when updating ROMs if that application is reinstalled is something I can't answer.
Maybe just try this first:
Settings> Application Manager> All> AT&T Software Update> Clear Data> Confirm
Power off Phone
Remove battery for at least thirty seconds.
Reinstall battery and power on device.
Try again after device boots up.
Sent from my SAMSUNG-SGH-I747 using xda premium
I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.
k3y0n4 said:
I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.
Click to expand...
Click to collapse
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So, if it's a software issue why is it two identical devices running the same software from the factory yield different results? I.e. my first device would do exactly as your original post outlines, then my replacement device had no issue checking for updates (same stock software, same device form factor).
If you search there are a lot of examples of complaints of this exact issue.
I am also very interested in this because even though there are many complaints out there, the only answers seem to be;
1) who cares this is xda and we update through Odin/cwm etc...
2) replace it.
Good luck, I hope you guys find an answer.
Sent from my SAMSUNG-SGH-I747 using xda premium
jefferson9 said:
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)
k3y0n4 said:
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)
Click to expand...
Click to collapse
You can bypass the wait time between checks by going into application managment -> at&t software update and clearing data. Then you can try to update again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I've had similar issues checking for updates. i gave up and pulled the first update with the USALG1 rom posted in the development forum sticky. I too have several apps disabled (actually moved out of the system/app dir) and was wondering if that possibly caused issues. I never did try updating through kies though.
My kies wont even run on my windows 7 64 bit. There seems to be alot of people having problems with kies on win7 64 bit, nothing from samsung either. So theres really no way for me to get updates
This is How I Got My Phone to Update
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.
AndroidLonghorn said:
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.
Click to expand...
Click to collapse
When you got it to work, exactly what apps did you force close and clear data? Just AT&T software update? Any others?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I force closed the At&T Software Update app and I think the Samsung Push Service. It is really the AT&T software update app that finally started downloading immediately after trying it again.
So I finally attempted the Keis connection and it worked immediately. I don't know what other problems people are having, but when I installed it on my Win7 x64 machine I had the S3 connected. After I ran the software for the first time it mentioned an update and proceeded to update it. Keep fighting the good fight jefferson9.
Hey guys, I'm new here, so this thread is probably on here somewhere, but oh well. I can't update my S3 OTA or through Kies. I know there is an update, as my friend got it fine on his yesterday (it's the one with the brightness slider in notification center). On OTA, it says communication failed every single time, then says up to date. I have tried clearing data and all that as well. And in Kies, it also says I have the latest firmware, even though I know I don't. Any ideas? I really don't want this happening when Jelly Bean comes out. Oh yeah, I'm not rooted or anything by the way, I'm still on stock for now.
I have the same exact issue. I think it has something to do with ATT and the phone not being set up right in their system. Did you by chance have an iPhone before your S3 and use the same Sim card?
Mine wouldn't find the ota on the phone. I searched around here and found a thread someone had started that has instructions on how to download the flashable zip and install it via CWM. Worked like a champ. If you are rooted this is the way you'll want to go
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Yes I did come from an iPhone. And I am planning to root soon so I might have to try that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey do you mind giving me instructions on how to do that? And is there a safe way to root my phone on a Mac? And last of all, can I still get updates such as Jelly Bean on a rooted GS3 without losing root without messing anything up? Sorry I'm coming from iPhones and jailbreaking so I'm not familiar with all this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Vanillamarble said:
Hey do you mind giving me instructions on how to do that? And is there a safe way to root my phone on a Mac? And last of all, can I still get updates such as Jelly Bean on a rooted GS3 without losing root without messing anything up? Sorry I'm coming from iPhones and jailbreaking so I'm not familiar with all this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I've always recommended returning whatever device you have back to 100% stock (as it was out of the box) before taking any official updates. I've heard ppl say they can take them just fine while still rooted - but they lose root. Sometimes you can simply re-root, sometimes you have to wait for a new exploit to be discovered before you can root again. In light of this, I always wait a week (sometimes less) after a new OTA (Over The Air) update is released, just to be sure I can regain root immediately. Welcome to the wonderful world of Android OS!!!
[edit] to answer your post about not being able to take the last OTA update. Have you tried a factory reset? Through Android Recovery? You will lose personal settings and contacts if you dont back them up. But, it may solve your update issue. Another thing I know, that a lot of ppl do is - as soon as you buy a new device, such as the awesome Galaxy S III, is to immediately do the factory reset. (Who knows how many employees have goofed around with the new toys they just got in stock)
I had the same problem with not being able to get the OTA update on my S3. Turns out it was a bad sim. As soon as I got a new sim from AT&T everything worked fine. Wish I would have done that first cause I spent hours on the phone with AT&T and Samsung trying to fix the problem. Good luck. Hope that works for you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Same issue here. Just spent a couple hours this Saturday at an AT&T store - end result is that they are swapping it out under the manufacture 1 year warranty.
Sim replacement did not fix it for me.
Tech support over the the stores land line says that the option to push OTA to phone is greyed out and not selectable with my account.
They are sending me a new phone so we'll see.
G-Man. said:
I've always recommended returning whatever device you have back to 100% stock (as it was out of the box) before taking any official updates. I've heard ppl say they can take them just fine while still rooted - but they lose root. Sometimes you can simply re-root, sometimes you have to wait for a new exploit to be discovered before you can root again. In light of this, I always wait a week (sometimes less) after a new OTA (Over The Air) update is released, just to be sure I can regain root immediately. Welcome to the wonderful world of Android OS!!!
[edit] to answer your post about not being able to take the last OTA update. Have you tried a factory reset? Through Android Recovery? You will lose personal settings and contacts if you dont back them up. But, it may solve your update issue. Another thing I know, that a lot of ppl do is - as soon as you buy a new device, such as the awesome Galaxy S III, is to immediately do the factory reset. (Who knows how many employees have goofed around with the new toys they just got in stock)
Click to expand...
Click to collapse
Read through the thread guys - there are other answers given besides just swapping the sim card...
Ok I'm going to try a factory reset. Wish me luck guys.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Just did a factory reset, and it didn't help at all. Now I've got to get everything back on my phone. Coming from iPhone, I will say that Apple has a heck of a lot better backup system. I do 0refer my GS3 though. Ok so any suggestions now?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
you've tried to update over cell network AND WiFi... correct? same error each time?
I'm not sure what else to suggest except trying a new sim card like someone else suggested... beyond that, a replacement device. Sorry man, wish I could be more useful...
[edit] The only other thing I can think to try would be to completely remove all your current USB Drivers for Samsung from your PC and reboot the PC, then re-install the USB Drivers, and try Kies again. If it still doesn't work, try a different PC.
Well I'm going to try a different computer, and if that doesn't work, I'm going to an AT&T store. Thanks for all the help guys.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I lost my phone last night (yes I'm an idiot). Tried installing Plan B this morning but it doesn't appear to work on Jelly Bean
I'm running 4.1.1 rooted. Phone has password lock on it.
Are there any alternatives I could explore before my battery completely dies and I'm completely screwed?
Also, for future reference, what are the best apps for locating devices? I miss "Find my iPhone"
Thanks y'all
Install Lookout Plan B from Google Play via a computer...
Sent from my Galaxy Nexus using xda app-developers app
Can a thief just go ahead and do a complete wipe and you're not completely helpless?
Jimmyco2008 said:
Install Lookout Plan B from Google Play via a computer.
Click to expand...
Click to collapse
I did that, does not work. Reviews say it doesn't work with JB
Dattack said:
Can a thief just go ahead and do a complete wipe and you're not completely helpless?
Click to expand...
Click to collapse
At the end of the day, my job can remote wipe the phone, plus I have a password that's not 1234, so I'm not concerned about my data being compromised, I just want the damn phone back. I love/need wi-fi hotspot (it's amazing for work)
I'm reluctant to root and install a custom ROM. When does the official Lollipop update push over the air for our Nexus 7 (2013) WiFi?
It's being pushed right now, but gradually.
Sent from my Nexus 7 using XDA Free mobile app
im still waiting.. damn slow
Nam Huy Linux http://www.namhuy.net
What does gradually mean? :silly: Just kidding.
The availability was supposed to be November 12th. By now, all Nexus 7 owners were supposed to receive the update.
Jhall8 said:
It's being pushed right now, but gradually.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
arjun90 said:
What does gradually mean? :silly: Just kidding.
The availability was supposed to be November 12th. By now, all Nexus 7 owners were supposed to receive the update.
Click to expand...
Click to collapse
Good one! Gradually=ssssllloooowww aaaasss heeeeellllll afaik
Sent from my XT1080 using XDA Free mobile app
Darn it. That's Google's way of wishing us Merry Christmas. :good:
Jhall8 said:
Good one! Gradually=ssssllloooowww aaaasss heeeeellllll afaik
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
No OTA for me yet....
No OTA for me too
I'm waiting, too.
Sent from my Nexus 7 using XDA Free mobile app
Waiting here as well for my nexus 7 2013...... (but my brother received two days ago on his nexus 7 2012).
I have two Nexus 7 2013's each on different Google accounts and to date '0 for 2' on this update. Phantomware to me so far. Tick-tock...
Same here... No Lollipop yet.
Still no update here yet in UK... Yet my missus got her update on her nexus 7 2012 few days ago
Yep. My old 2012 Nexus 7 got it a couple of days ago, my Nexus 5 got it a few hours after that, but still waiting on my new Nexus 7.
You can backup your existing data on your Nexus 7, then flash the Stock Factory Image that Google provided and install and enjoy... The first boot though takes 5-7 mins.. Restore your personal Data, NOT the data partition.. Lollipop handles the file structure a tad differently..
https://developers.google.com/android/nexus/images
Edit: when installing a factory image, it completely wipes your device, verses an OTA..
If you look hard enough you can find someone who has posted the OTA here on XDA..
But if you are rooted, using Xposed, Custom Kernel, or a Custom recovery you will not be able to update..
Zaphodspeaks said:
You can backup your existing data on your Nexus 7, then flash the Stock Factory Image that Google provided and install and enjoy... The first boot though takes 5-7 mins.. Restore your personal Data, NOT the data partition.. Lollipop handles the file structure a tad differently..
https://developers.google.com/android/nexus/images
Edit: when installing a factory image, it completely wipes your device, verses an OTA..
If you look hard enough you can find someone who has posted the OTA here on XDA..
But if you are rooted, using Xposed, Custom Kernel, or a Custom recovery you will not be able to update..
Click to expand...
Click to collapse
This misses the point of having a Nexus. This is XDA I am sure people know they can flash it. The point of a Nexus is to get the updates right away from google. I have other devices which I flash roms on but bought a Nexus for the pure google experience.
krispy1 said:
This misses the point of having a Nexus. This is XDA I am sure people know they can flash it. The point of a Nexus is to get the updates right away from google. I have other devices which I flash roms on but bought a Nexus for the pure google experience.
Click to expand...
Click to collapse
There is trick, I forgot how or what.. But it resets the Google cache, and you hammer on update and sometimes rather than not.. the update would pop up.. Someone please remind me of how that is done, I just find the OTA here and sideload it, or install the Factory image..
They are rolling the updates in certain areas in a controlled manor so if something really bad pops up that can stop it from hitting every device at once
If you've never seen this , give it a read, explains why the OTA may have not reached your device yet.
http://www.reddit.com/r/Android/comments/1r1dz4/44_kitkat_has_started_rolling_out_on_the_n4/cdiwt6f
Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure nothing looks wrong before sending it to more. Then typically it goes to 25%, 50%, 100% over the course of a week or two.
What the percentages mean is that when your device checks in, it has a 1% chance (for example) of being offered the OTA. If it doesn't (randomly) get an offer, it will never get an offer until the next batch.
IOW, once your device checks in and gets turned down, that's it until the next batch. Mashing on the "check for updates" button just causes your device to check in again, and get automatically turned down again.
Click to expand...
Click to collapse
Neomagus, That's good info. I'm wondering at 8 days out whether we have days to wait vs another week or two to wait.
Sent from my XT1080 using XDA Free mobile app
Zaphodspeaks said:
There is trick, I forgot how or what.. But it resets the Google cache, and you hammer on update and sometimes rather than not.. the update would pop up.. Someone please remind me of how that is done, I just find the OTA here and sideload it, or install the Factory image..
They are rolling the updates in certain areas in a controlled manor so if something really bad pops up that can stop it from hitting every device at once
Click to expand...
Click to collapse
A google engineer replied to this on reddit
"Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)
How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.
Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.
All of this can be avoided by just doing an 'adb sideload' if you are impatient."
http://www.reddit.com/r/Android/comments/1r1dz4/44_kitkat_has_started_rolling_out_on_the_n4/cdiwt6f