Related
I seem to be locked out of Google Wallet on my Nexus S 4G. I have been GW for 4 months on custom roms with no issues. The other day when flashing a peter Alfonso ICS Rom (full wipe) and launching GW App i got the error message Secure Element Not Responding. Since then i have re wiped and re flashed, Unrooted to stock 2.3.7 and re rooted back to CM9 and i still get the error message on any rom i try whether i am rooted and un rooted.
I even tries a nandroid back up when GW was working and it still wont work.
Can anyone help me out. ?
You will need to make a phone call to Money Network or Google for a "master reset". I called the Money Network number last night (01/29/12) around 11pm and I am waiting for a call back from them.
This seems to be happening a lot to Galaxy Nexus owners. I think mine was a result of restoring wallet data from Titanium backup. I do not think Google Wallet should be included with ICS Gapps.
Luckily, our phone is officially supported, some Galaxy Nexus owners are getting pushback from Money Network/Google when requesting a master reset.
Here are the numbers listed on the Google Wallet "Contact Us" page:
For Google Wallet related questions contact google toll-free at 855-492-5538
For Google Prepaid Card questions contact Money Network at 855-896-0693
I feel like maybe I should have contacted the Google number as opposed to the Money Network number, the CSR said she had to contact Google. Maybe this will save a step. She said it can be 24-48 hours before someone contacts you. I will update this post with the number that calls me.
You mean this type of reset:
http://support.sprint.com/support/t...eset_Samsung_Nexus_S_4G_from_Google/25162-101 ?
Unfortunately no. This has to do with them resetting your Google Wallet account. They need your IMEI (MEID) number. I am waiting for a call back, I will keep you posted.
Nick N said:
Unfortunately no. This has to do with them resetting your Google Wallet account. They need your IMEI (MEID) number. I am waiting for a call back, I will keep you posted.
Click to expand...
Click to collapse
Thanks .. awaiting your response !
Still no contact as of 3:45pm, maybe someone wants to try contacting Google using this method?:
http://support.google.com/wallet/bi...contact_policy&policy=mobile&test=country-US&
I would do it, but I do not want them to get annoyed since I am still in their 24-48 hour contact window.
I spoke to the Google Wallet team and there responce was it was a hardware issue and item needs to either be replaced or repaired by Sprint or Samsung. Not sure how it bacame a hardware issue ?
Anyways i took my phone to sprint repair and gonna pick it up at 5pm to see what they can do to fix.
Here is the response i got:
Re: [#955******] Follow-up to Google Wallet
Google Wallet Support [email protected]
1:37 PM (2 hours ago)
to me
Hi Nathan,
Thank you for calling Google Wallet. To have the secure element looked at
for assistance, I suggest contact a Sprint Service shop for this matter.
With the Secure Element not responding, its a matter with the hardware of
the device.
It was a pleasure assisting you today. Feel free to contact us again if
you have any additional questions regarding Google Wallet or visit our
Help Center at http://www.google.com/support/wallet
Sincerely,
Paul
The Google Wallet Team
Any updates? I am still waiting for my call.
Went back to sprint store this evening and they said they did a master reset and the problem was still there.
They offered me a replacement phone (refurbished) which will come in 3 days. They also told me they don't know what the problem is or how it occurred.
I don't know what caused this but I'm gonna avoid using g wallet on my replacement till there is a fix.
Really a strange issue that google wallet is malfunctioning the hardware !
At least you will get a replacement!
2 questions:
1. Did you use an ICS Rom (I think the answer is yes);
2. Did you use Titanium Backup to backup Google Wallet?
There is absolutely nothing a sprint store could do to fix that.
Sent from my Nexus S 4G using XDA App
I'm real happy I got a replacement since phone was 6 months old and was pretty beat up.
1: I did use several ICS ROM's
2:I usually back up all my apps but I don't think the google apps get backed when doing a batch back up with titanium backup so not sure
Money Network called, gave me a few BS steps (remove battery, turn on and off NFC setting, wait 5 minutes). She said if that doesn't work I need a new phone.
it happens when moving between ics and gb roms since rooting could mess with the money... it happened to me a while ago when i unrooted and updated back to 2.3.7 from 2.3.5 but i have a asurion replacement phone so asurion has no problem sending me a phone when this happens...
Try to disable NFC, start wallet, and re-enable it (possibly wiping the wallet app data from app management between the steps). I did get the "secure element stopped responding"-message too (after using the internal wallet wipe function), but it seems it was just a really nasty kind of driver crash and it started working after I messed around a bit. (It did not work after just a Factory Data Reset if I remember correctly!)
So I used the Samsung PC tool to flash stock 2.3.4 on my phone, activated it and signed in. Here are some of my test results:
2.3.4 - Allowed me to download Wallet but said hardware was not supported.
2.3.5 - When activating the NFC it gave me an error
2.3.7 - Secure Element message.
I was able to get to the Google Wallet setup screen by frantically tapping the lock button in the top right corner when on the main page with the offers, payment cards, and transactions. It allowed me to select my account and sent me an email but kept throwing the Secure Element message, which can be bypassed by pressing the search button.
Tried to add a prepaid card... it acted like it wanted to but ending up showing an error adding card message.
When I tried to use the reset feature within the Wallet app it pretends like it resets but it does not.
Nick N said:
So I used the Samsung PC tool to flash stock 2.3.4 on my phone, activated it and signed in. Here are some of my test results:
2.3.4 - Allowed me to download Wallet but said hardware was not supported.
2.3.5 - When activating the NFC it gave me an error
2.3.7 - Secure Element message.
I was able to get to the Google Wallet setup screen by frantically tapping the lock button in the top right corner when on the main page with the offers, payment cards, and transactions. It allowed me to select my account and sent me an email but kept throwing the Secure Element message, which can be bypassed by pressing the search button.
Tried to add a prepaid card... it acted like it wanted to but ending up showing an error adding card message.
When I tried to use the reset feature within the Wallet app it pretends like it resets but it does not.
Click to expand...
Click to collapse
Alright listen carefully. Sprint support and even money network, from my experience, understand nothing when it comes to rooting. On a completely stock phone the issue would be hardware. In this case I'm not convinced. Have u done the msl reset? Use 786 and if that gets u to triangle use the sctrn number which is 72786, then 786. Know that 786 will wipe it internal storage so backup to comp. The point is to wipe so utterly then go to recovery and flash wipe all zip then flash latest vhgomez lota or whatever from, make sure u flash the radio, then bootuo, run thru setup, let it program/activate your phone, once that's all done try wallet and report here.
Goodluck!
PS going stock does not do this kind of wipe if I recall correctly, nor would the sprint store. Not right anyway.
Sent from my Nexus S 4G using XDA Premium App
janspambox said:
Try to disable NFC, start wallet, and re-enable it (possibly wiping the wallet app data from app management between the steps). I did get the "secure element stopped responding"-message too (after using the internal wallet wipe function), but it seems it was just a really nasty kind of driver crash and it started working after I messed around a bit. (It did not work after just a Factory Data Reset if I remember correctly!)
Click to expand...
Click to collapse
So, it is NOT a hardware issue and somehow fixable. I wish you remembered exactly what you did and started working again.
Not getting a error but it will not let me in google wallet
I was on CM9 and went back to a old NAD back up to stock and pulled the 4.0.4 OTA. Google wallet won't let me in now. I called the google # they asked me same stuff. Asked me my MSID and told me that she would send it up the line and I will get a email about it.
Secure Element Error Message
The NFC transmits information from the secure element. They are both different chips within the phone. If the secure element breaks, NFC will still work, but you will not be able to use Google Wallet on the phone anymore.
The "Secure Element" works closely with the NFC Chip as a security feature. When it is tampered physically or with software (rooting and perhaps changing ROMS), it is set up to destroy itself. When it is destroyed, the only solution is to replace the phone. (Factory Data Reset, unrooted, and revert back to stock will not fix the problem).
Google Tech Support sends a typical email to owners who ends up having this error message:
"We strongly discourage gaining system-level "root" access to your phone if you plan to use Google Wallet. We are unable to support devices with unauthorized operating systems as the security layers of the device may be limited.
If you have other questions, please reply to this email and I'll be happy to help."
I hear it is about 50% hit and miss on rooted phones depending on what owners do with their phones. So, with that said, I would suggest you, as rooted owners stick with the SAME ROM all the way if you want to use Google Wallet. The Secure Element have only 1 life, not "9 lives". You are on your own discretion / risk.
Google will replace the Galaxy Nexus phones for free as long it is stock and not rooted.
Unlocked Galaxy Nexus phones are on sale via Google Play for $399, no contract.
---Sharmy
Last Friday I noticed that I stopped receiving texts on my unlocked DE running stock rooted 4.4.4. Sending texts works fine. This phone has never had any problems with anything since I started using it 18 months or so ago, and out of the blue it stopped receiving texts. I have checked Verizon's side on another phone (moved sim card to old Gnex and texts are received fine) and it is definitely a problem with my phone. I have deleted all texts, wiped caches, tried Safe Mode nothing has fixed it. Seems like some odd radio problem. I have read about the 4.4.4 issues others have had, but as I mentioned, this phone has been fine on 4.4.4 since I set it up.
In any event, I am here looking for some answers or some suggestions of what else to try. I would like to keep the total wipe and restore as a last resort, as this phone is mission critical to me for work, and being too stupid to do regular backups, resetting everything back to the way it is now would be a hardship. I do have a nandroid backup from when I originally set up the phone, and was thinking of trying that. If I wipe everything though, does that wipe the SD card too? I thought a factory reset wipes the SD card, so if so I need to back it up first.
(So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...)
Thanks in advance for anything you guys can offer!
In my case, and others, this problem was solved as indicated in post #25 by qtonic (thanks to you, qtonic!). In my case, VVM was not an issue as I did not use that feature, so I can't vouch for whether or not that problem is solved. No "factory reset" was involved, nor any "upgrade" to Lollipop was necessary, so no worries there. One important note is to backup your texts if you want to restore them after you clear the data. I did that and I am back up and running with all my old texts in place. Hopefully this fix works for everyone experiencing this issue.
Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?
cnoevl21 said:
Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?
Click to expand...
Click to collapse
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?
I am dealing with the same issue. Don't want to upgrade to lolly or do i want to factory reset. I will stay tuned to this thread and hopefully get a fix.
Sent from my XT1060 using XDA Free mobile app
amajamar said:
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?
Click to expand...
Click to collapse
i just wiped cache and dalvik. then went to lollipop. it then dawned on me that i should have tried to wipe kitkat, but when u switch to LP it screws everything up so idk if you can go back to kitkat. i may try to at some point, maybe over the weekend.
right now im just running a debloated stock LP rom and i used xposed to customize.
I just added the following to my OP.
So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...
Can you guys duplicate this?
Any solutions other than factory wipe?
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
I went up several levels of tech support at Verizon and eventually ended up getting the same story. I need a factory reset and then all will be fine. They said it was due to some voicemail interface version not being supported anymore and my phone is trying to use the old one and it's keeping the phone from provisioning and that's why texts stopped working.
I've been putting off applying the Lollipop update because I knew it was going to have undesired consequences, but I went ahead and applied it. Text work again but of course I had to re-root (Developer Edition so no sweat there) and even with root WiFi Tether for Root Users (which had been working great under KitKat) bit the dust and no longer works. Under KitKat I had to use the special version that had some added binaries to make up for pieces that were missing from the kernel and I guess those binaries don't work with the Lollipop kernel.
So I'm using the stock tether app now (with provisioning check disabled) but I hate it. You can't turn on access control lists (to "approve" users), you can't see who's connected, you can't define an inactivity timeout, blah blah blah. It sucks so bad compared to WiFi Tether for Root Users.
Oh yeah, in the process of troubleshooting they removed voicemail from my line and put it back on. So I had to set up my voicemail from scratch and lost a bunch of voicemails I'd been saving for years including one from a friend who's dead now. Not happy.
Eh, at least SMS works again.
ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
Yes, for me it was last Thursday that it was working as well. So, that being said, I take it a factory wipe is required. A couple of questions for you guys: Since I have a Developer Edition (running Xposed) too, do I have anything to worry about about doing a factory wipe? I am currently on 4.4.4, rooted, do I need to prep anything to do the factory wipe so I don't brick? Can I stay on 4.4.4 and just re-root and reinstall my apps from TiBU? I haven't messed around with anything since setting it up over a year ago, and not really thrilled with starting from scratch...
Anyway, great sleuthing MotoCache1, seems that you got to the bottom of things. At least we can be sure it was not some other app or something causing this.
I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app
mlucht said:
I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
If you're rooted edit your /system/build.prop file, add this line to the end, reboot the phone, and then use the factory hotspot tethering:
Code:
net.tethering.noprovisioning=true
More information here if you want it.
I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....
ray4jc said:
I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....
Click to expand...
Click to collapse
That's what they told me as well. They said "take it in to a Verizon store and they will back it up and do a factory reset and then restore your data".
I decided against that and instead opted to use the VZW Software Repair Assistant tool. When you use that there are 2 options - Software Repair Assistant (which is supposed to "repair" your currently installed software) and Software Upgrade Assistant (which is supposed to update your device to the latest available software for it).
I didn't particularly want to go to Lollipop so I chose the "repair" option, chose the phone, and clicked "Repair". And it "repaired" it by upgrading it to Lollipop. Lol. Maybe it's because I had previously told the phone to go ahead and try to apply the Lollipop OTA. The OTA failed to install. Not sure why - possibly due to root and/or other changes to the system partition. I was using stock recovery.
So anyway, I ended up on Lollipop even though that's not really what I wanted to do, and that did fix the problem - though, as previously bemoaned, I can't use WiFi Tether for Root Users anymore and have to use the piece of crap that's built into the OS. I guess I should be grateful that works because I'd be in a pickle if I had to do without tether.
Back to what you posted -- I don't think anybody here has yet posted that the factory reset actually fixed the problem for them. Honestly I don't understand how it would. A factory reset isn't going to suddenly make your phone start using a newer version of anything and what I was told was that the phone was using an old, no longer supported version/protocol to access voicemail and that was the root of the problem.
I suspect that if you take it into a VZW store for a "factory reset" what you're really going to get is an upgrade to Lollipop. Lol.
@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
I chatted with Motorola and did a bunch of troubleshooting with them, they suggested trying a new sim card.
ray4jc said:
@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
Click to expand...
Click to collapse
Wow. Talk about a lame answer. Nothing on the phone changed. Nothing on the phone broke. Obviously Verizon changed something on their side and rather than back out, or fix it, they want to shift the problem to the device owners.
At least you know you can probably fix it by going to Lollipop (so far that seems to have fixed everyone that has posted here) but that comes with some negatives. I'd rather still be on KitKat personally, but I put too much time into it already so I'm just going to be satisfied that it's working and try to forget how much I hate the factory tether piece of crap.
Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?
domenci said:
Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?
Click to expand...
Click to collapse
Were you rooted prior to factory reset? Did you need to re-root? Did the factory reset wipe the SD card? I want to fix this without upgrading to lollipop if possible
Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).
domenci said:
Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).
Click to expand...
Click to collapse
I did try a factory reset and it didn't work. Of course I'm running the eclipse 4.4.4 ROM not sure if that matters.
Looking in TiBU I've only got a few Verizon apps, none of them appear to be for voicemail the only thing that says voicemail is the phone 4.4.4-26 (19) app.
I'd love to stay on 4.4.4 if possible.
Otherwise I need to figure out which ROM to go to next.
My phone was stolen over the weekend and I miraculously was able to get it back after the person left it in an emergency room! I am thrilled to have it back, but it looks like maybe a factory reset was performed since all my contacts/photos/etc... are gone. :crying: I have been researching to see if there is anyway to at least recover the photos. I tried a few of the apps like dr.fone but haven't had any luck. Looks like the phone needs to be rooted, but that isn't possible with my phone? Can anyone confirm this? Any other recommendations on options I can try, or are they gone for good? Definitely learned my lesson and will be backing up more often...
Phone: Samsung Galaxy S6 active (SM-G890A)
Android Version: 7.0
Carrier: AT&T
Thanks in advance!
Update: I take that back, they maybe didn't do a factory reset. After looking further, I do still see some apps on my phone that wouldn't be standard, as well as it looks like I am still logged into email. Hoping this increases my chances of retrieving photos?!
If you had your phone set-up to back-up to your google or samsung account, try there.
Bill
All my photos and contacts are backed up to my google account, try logging in and syncing everything. You could also try to login to photos.google.com to see if they're there. If they are you're GTG, if not... Sorry man...
I was hoping for an easy trade-in with Samsung. I have no flaws on my Galaxy Note 8, I sent it in before the date that they asked.
My screen had no issues, no scratches, perfect condition.
The phone turns on and runs absolutely fine.
The last thing I did before I packed my Note8 up was to take out my SIM card and microSD card and then do a factory re-set.
The final screen I saw was when it rebooted after the reset and was ready to start the process from scratch - which I have done before.
So what happened? Why are they saying my device was NOT reset?? This is absurd, I have seen people get no credit before for other things but never the "not factory reset"!
Can someone help me or offer advice? I have a week to call them before they charge me and I can have them ship the device back, but **I had a perfect condition Note8 and I want my $550 trade in!!**
vonDubenshire said:
I was hoping for an easy trade-in with Samsung. I have no flaws on my Galaxy Note 8, I sent it in before the date that they asked.
My screen had no issues, no scratches, perfect condition.
The phone turns on and runs absolutely fine.
The last thing I did before I packed my Note8 up was to take out my SIM card and microSD card and then do a factory re-set.
The final screen I saw was when it rebooted after the reset and was ready to start the process from scratch - which I have done before.
So what happened? Why are they saying my device was NOT reset?? This is absurd, I have seen people get no credit before for other things but never the "not factory reset"!
Can someone help me or offer advice? I have a week to call them before they charge me and I can have them ship the device back, but **I had a perfect condition Note8 and I want my $550 trade in!!**
Click to expand...
Click to collapse
I guess you didn't remove your accounts before resetting your phone. So, most probably, the setup process will ask for previous account credentials.
Samsung should be able to bypass this protection if they want. Or you can see with them the possibility to send them your account credentials to help them unlock the phone. If they refuse then they have bad intentions...
I can only imagine it is the FRP as this would require the setup to ask for the security details you had on the device prior to reseting the device and then the Google email address attached to the account, however this would only happen after a master reset so not sure if this is the reason, however when I tried to sell a S9 to a recycle site in the UK and I made this mistake they sent it back as I was not able to remotely do this.
vonDubenshire said:
I was hoping for an easy trade-in with Samsung. I have no flaws on my Galaxy Note 8, I sent it in before the date that they asked.
My screen had no issues, no scratches, perfect condition.
The phone turns on and runs absolutely fine.
The last thing I did before I packed my Note8 up was to take out my SIM card and microSD card and then do a factory re-set.
The final screen I saw was when it rebooted after the reset and was ready to start the process from scratch - which I have done before.
So what happened? Why are they saying my device was NOT reset?? This is absurd, I have seen people get no credit before for other things but never the "not factory reset"!
Can someone help me or offer advice? I have a week to call them before they charge me and I can have them ship the device back, but **I had a perfect condition Note8 and I want my $550 trade in!!**
Click to expand...
Click to collapse
Did you do your factory reset through settings menu? I sent in my galaxy s8 back to them for the trade in program Monday and it was running One UI beta 3 so I flashed it through ODIN using the latest Sprint firmware and CSC file to wipe everything back to complete stock. When I did the initial factory reset before flashing in odin I went though Settings > General management > Reset > Factory data reset. It asked me for my google password before it would reset the device. I did the ODIN flash to make sure everything was gone and it was on the correct latest Sprint firmware. I was afraid being on the BETA they may reject it. Now you've got me worried because I didn't try and set the device up again to see if it asked for my google password. I'm 99% sure when doing a factory reset through settings and entering in my credentials FRP is no longer active. Does anyone know if a clean ODIN flash using the CSC (not Home CSC) will remove any and all settings such as FRP?
googy_anas said:
I guess you didn't remove your accounts before resetting your phone. So, most probably, the setup process will ask for previous account credentials.
Samsung should be able to bypass this protection if they want. Or you can see with them the possibility to send them your account credentials to help them unlock the phone. If they refuse then they have bad intentions...
Click to expand...
Click to collapse
I am a little confused as I removed my SIM and SD Card and then did a factory reset and it went back to the first set up screen. So, you are saying if we did not remove our Google account or work email prior to factory reset they could refuse the trade in??
Sent from my SM-G973U1 using Tapatalk
maddie01 said:
I am a little confused as I removed my SIM and SD Card and then did a factory reset and it went back to the first set up screen. So, you are saying if we did not remove our Google account or work email prior to factory reset they could refuse the trade in??
Click to expand...
Click to collapse
Yes. FRP (Factory Reset Protection) is designed to deter theft by requiring any Google account (not sure about Samsung account) that was active on the phone at the time of factory reset be logged into prior to using any other account after the factory reset. You can disable FRP by just going into Settings -> Accounts and removing your Google account prior to a factory reset.
Outbreak444 said:
Yes. FRP (Factory Reset Protection) is designed to deter theft by requiring any Google account (not sure about Samsung account) that was active on the phone at the time of factory reset be logged into prior to using any other account after the factory reset. You can disable FRP by just going into Settings -> Accounts and removing your Google account prior to a factory reset.
Click to expand...
Click to collapse
Maybe so, but I've traded two phones with no problems and all I've ever done is a factory reset from the settings. Both times I did reboot to see if it went to the default setup screen, but that's all I've done.
Same here, did a factory reset only. It was approved even with unlocked bootloader and twrp...
galaxys said:
Same here, did a factory reset only. It was approved even with unlocked bootloader and twrp...
Click to expand...
Click to collapse
Well, I appreciate everyone chiming in...I hope ultimately they approve the trade or get you phone back to you so you can sell it to recoup your money...
I checked to be sure and it seems my trade in was excepted as they only charged my Amex the discounted amount and they received my trade in on the 28th of March and i did not do anything but a Factory Reset... same thing when i traded in my S8 for the S9...
Maybe Sammy saw something questionable on the unit and used this as an excuse to deny the trade? It could be possible that this deleting of the prior accounts is in the fine print somewhere and they use when needed?
Best of luck...
Sent from my iPad using Tapatalk
I think you're at Samsung's mercy in these situations. You can complain to them until you're blue in the face, but in the end it's at their discretion.
Yeah, there was nothing wrong with my phone so I am going to complain pretty hard. I have hit up the Samsung Mobile USA and Samsung Support USA on Twitter before and retweet them enough that I hope to make a fuss that I can get taken care of.
vonDubenshire said:
Yeah, there was nothing wrong with my phone so I am going to complain pretty hard. I have hit up the Samsung Mobile USA and Samsung Support USA on Twitter before and retweet them enough that I hope to make a fuss that I can get taken care of.
Click to expand...
Click to collapse
Good luck. What's so bad is that Samsung isn't even the one's inspecting the phones. They should have some process that makes Samsung themselves look at a phone after Ingram Micro rejects it.
Let me preface this with this issue began with the February security update. I cannot say for certain that they are related, however it’s difficult to believe that they are not. Tuesday after installing the February security update my phone and lost the ability to connect to Tmobile’s data network. It can still call, text, send MMS, and run speed tests. I’ve been working with one of the engineers at Tmobile corporate in Bellevue Washington. They have gone above and beyond looking at the switch, refreshing my account By suspending and reactivating it. They have had my Sim card swapped multiple times. When I put my Sim card into my old phone I have data connectivity like normal. Does anybody hear have any insight or anything to try on a pixel five to possibly undo whatever the February security update did.
Update. Best Buy replaced the phone outside of normal warranty. As soon as it got the February security update the problem is back.
Clear system cache.
Do a network reset.
Double check all related settings.
Now you know why I don't update...
blackhawk said:
Clear system cache.
Do a network reset.
Double check all related settings.
Now you know why I don't update...
Click to expand...
Click to collapse
Done, done, and done. This is phone number 2 now. Problem does not follow my sim. Works fine in iphone 10s and a Samsung Note 20.
b0gman said:
Done, done, and done. This is phone number 2 now. Problem does not follow my sim. Works fine in iphone 10s and a Samsung Note 20.
Click to expand...
Click to collapse
Ouch. That sucks.
Try a factory reset if you haven't.
Most likely it was the update.
If a reload doesn't get it, reflash the firmware.
It may be a hardware failure if a reflash to the last known good rom doesn't get it.
blackhawk said:
Ouch. That sucks.
Try a factory reset if you haven't.
Most likely it was the update.
If a reload doesn't get it, reflash the firmware.
It may be a hardware failure if a reflash to the last known good rom doesn't get it.
Click to expand...
Click to collapse
Don't have time for any of that anymore sadly. Best buy does kick ass they swapped me into a S20 FE. Did get an email from google acknowledging that this is a known bug since January.
Go into settings and check your APN settings. I had to delete one and switch to another to get my data working again.