Well, I am having issues w/Android Pay and am on the stock B20 update (no unlocked bootloader, no root, etc). Won't work. Keeps indicating I have to unlock the phone (which it is) and keeps indicating for me to use fingerprint or code (which I did). Kept blocking me. I would feel the phone "bump" but then kept immediately getting the "unlock" error screen. MCD's said it wasn't on her end as customers were paying.
Tried Android pay this morning and it worked for me. Had to use the pin though, for some reason the finger print didn't work. Kept telling me to unlock the device.
Related
I purchased a S5 G 900V (Verizon) on the 15th (of May) after my last phone died (Razr)... 2 months after the insurance expired of course. The S5 seemed to work fine for the first 3 days and like most I was setting it all up (w/exception of a few root only apps since the verzion phone is locked up).
This last Tuesday late afternoon the phone wouldn't turn on so I did a battery pull and when it booted up it had an unlocked icon (lock that was unlocked) display on the device and the word "custom" displayed under the open lock. The phone would go to sleep and not wake up without a battery pull each time. Device status under the settings area was also the word "custom". I had purchased the device from Best Buy along with insurance at our local mall... and at 7 pm after trying to get the phone to work correctly took it back to the store. The person that had sold me the phone was there along with one of the managers/assistant managers and they both keep telling me it was my own fault for attempting to root the phone (which I didn't do). They fought with the phone for and hour or so and couldn't get anything to work correctly... still getting the unlocked icon and custom word. I was told that if I could get it unrooted they would exchange the device for me, but they couldn't do anything with the phone until I could get it back into ua unrooted status. The assist manager did point me out to another website that explained the use of ODIN and where to get the stock Verizon rom.. which took a good few hours to d/l due to their slow server (not complaining, I'm glad they had it for me to begin with).
I set up and attempted to unroot the device with no avail. Did a factory wipe clean out cache etc etc the ODIN program kept saying it worked and I would be presented with all the normal new phone settings and hoops to jump thru as if it was just being activated... but on a restart the open lock and custom was still there.
Yesterday while looking over forums I noticed the phone was downloading an app I had already downloaded. I looked at the phone and it seemed as if it was re-installing some of the basic play store apps I had! I rebooted the phone and no lock appeared and under the Device status custom was gone and "original" was in it's place. I packed all my boxes and cables up and after work today took the phone in and had them exchange it for a new one. The same assistant manager was there when I had first taken the phone in when I had experienced the strange behavior.
She (the assistant manager), had no problem exchanging it since it didn't have that error showing up.
My major concern is if somehow if/when I connected the phone to my desktop did it (either the phone or computer) try and transfer files that made the phone act up in the first place? I have a rooted Nexus 7 and the Razr I had had ... had also been rooted. I don't think I have anything besides Samsungs device manager and Wugs Nexus Root toolkit, but those shouldn't mess the S5 up I have Eclipse installed but it doesn't launch without manual opening. I would both hate it if I had the same thing happen to this new phone but also dislike the idea of not plugging the phone in to transfer media if I wanted to.
Any ideas... or think it was a bad first phone?
Hello all,
I've read and searched through a few posts before posting this, and it seems there has not been one consistent solution offered that is a guaranteed fix. And no problems that have been solved like this in the past 6 months or more that I saw.
About 10 days ago my Note 3 started doing all kinds of crazy crap. It would:
Boot up with a yellow exclamation point and says Verizon Wireless had detected unauthorized software on my device. In the top corner it would say secure fail: modem. This almost always went away with just another reboot of the phone.
Boot up with a splash screen that normally just says Samsung Galaxy Note 3, but now also has an unlocked padlock and "Custom" on the screen.
Extremely intermittently recognize that I had a sim in my phone and provision my phone on the 4g network.
Not allowi a significant amount of internet activity even when connected to wifi.
Pop up an error box upon entering the OS saying that there was a process system error and ask me to wait or kill the process.
Random unrequested reboots of my phone without even touching it. (this has happened 7 times now through the course of typing this post)
Also a problem, though not a recent development, is a common complaint that there has been significant difficulty in placing clear phone calls even though signal strength looks good, sometimes resulting in attempts to dial timing out without making a connection.
As a bit of background: I've never rooted this phone. Years ago I sold smartphones for a living and I knew how much of bastards Verizon et. al. were when it came to providing hardware warranty coverage to people who had rooted their devices. Having said that, I have no idea why I just randomly started seeing an unlocked padlock and a callout for a custom OS on the boot up splash screen. Also, I've already gone to verizon and replaced the sim just in case it was a defective chip causing these problems. There have been no significant changes, though it does seem that the intermittent rate at which the phone actually finds the network happens a little more often with a new sim. Maybe that's just my wishful thinking that my situation has improved.
Other things I've tried for troubleshooting already:
Booted into recovery mode, wiped cache, rebooted.
Booted into recovery mode, wiped and factory reset the phone from the on board restore software.
Downloaded Kies and booted into download mode on the device and pushed the current OS image to my phone.
Tried some silly battery trick that some guy made a youtube video about where he suggests pulling the battery, pressing the power button for a few seconds, then putting the battery back in will fix the problem.
This phone is out of warranty now, so I'm not opposed to trying a rooting solution to fix it -- if that is even plausible. I also downloaded a 1.6GB zip that is supposed to contain an image of the LP OS (N900VVRUEOF1_N900VVZWEOF1_VZW.zip), but have not done anything with it yet. My only concern with trying to wipe out the stock OS is that I've never attempted it before and don't want to F it up, although at this point could it get much worse??
Cosmetically this phone is in perfect condition. I'm not a phone dropper, and it has been in an otterbox defender case since the day I got it. I bought this phone outright in 2013 so that I could preserve my unlimited data plan, so I'm really hoping there is a potential solution here that does not involve buying a new phone.
Any suggestions you can offer would be great. Like I said, I did some keyword searching on this form and read a few threads before posting, but it seemed like there were a bunch of different theories on how to fix this problem and no consistent solution.
Thanks!
The forum for your phone is here .
http://forum.xda-developers.com/verizon-galaxy-note-3
For starters, I originally had a Pixel from Verizon. Could not unlock that device, obviously. So once my charge port messed up, I started an RMA with Google. Today I received my *new in the box* Pixel from Google, and unlocking is still disabled.
I removed the SIM from the phone before powering it on. Once powered on, I never connected to the internet or signed into my Google account. OEM unlocking was disabled. After doing some quick research, I found out you had to sign into your google account in order to unlock, so I did that. That didn't work.
Then after some more research, some people said once they updated to the newest firmware, unlocking was enabled. So I did that too, and it still didn't work.
I also tried inserting an AT&T SIM in the the phone. It's an active SIM and calling/texting works fine with this SIM in the phone. OEM unlocking still grayed out.
The build number for Android in settings is NJH47D. This is a Google build number (NHG47O is the Verizon one).
What's going on here? As far as this phone is concerned, it was was purchased on the Google store and it has never even had a SIM in it.
Google usually sends a 'Verizon' replacement to Verizon customers. That wasnt the case early on, most all were 'Google' versions. Now it is a crapshoot.
TonikJDK said:
Google usually sends a 'Verizon' replacement to Verizon customers. That wasnt the case early on, most all were 'Google' versions. Now it is a crapshoot.
Click to expand...
Click to collapse
So then this thread: https://forum.xda-developers.com/pixel/how-to/read-regret-buying-verizon-edition-t3581406 is basically obsolete now? If this is the case, then phones are now being locked by Google at the factory, so you have absolutely no hope of being able to unlock...? ****ing hell man.
The SIM has nothing to do with it. It's been tested and proven wrong. You bought a Verizon Pixel and Verizon locks there bootloaders. Why would you assume your replacement wouldn't be locked. Yes some people have gotten lucky but it's nothing more than that.
My friend said I could buy the ATT unlocked V20 so I can use it on Cricket which they've the same network. After setting up my Google account I come to this screen and it's trying to force me to sign in but I don't have an account with ATT. Does this mean it's not unlocked?
I assume that 3rd screen is what shows up when you hit skip?
Also, were you planning on rooting your phone? If so, you don't need to set it up, you can just root it and then you won't have any issues with their setup screen.
-- Brian
I figured it out. I removed the SIM card and turned off WiFi which the app requires to continue. Then it finally gave me the option to exit to the home screen. After that i was able to insert the SIM card again with no problem.
I'll see about rooting. I play Ingress and PoGo and its a hassle to trick SafetyNet. I think Android Pay didn't work the last time I tried Magisk. And ROMs screw up my GPS all the time.
Hi
I owned an S8 on Verizon for a year or so and switched to Sprint's Bring Your Own Device Plan. One a Sprint SIM was inserted, the phone was rebranded and all Verizon apps were wiped off and replaced with Sprint. Fast forward a few months after, early June, I get a firmware update notification which I prompted to accept (as I have many times before for Verizon and Sprint updates). After the update, the phone worked for a few days and then all of the sudden gets stuck on the word Samsung S8 logo and restarts on its own. It keeps looping!
Resetting didn't work and I sent it to a store nearby (You Break, We Fix) and nothing could get this thing to go back to normal. I think the fact that the phone was on Verizon and was rebranded to Sprint is what caused the problem.
I downloaded Odin but can't figure out which version of the firmware I should use to flash the phone and get it to work. The original box that came with it says SM-G950UZKV and the SW-VER is G950USQU1AQC8. I don't care about the phone's photos/other data, I just want it to work again.
What firmware should I download to get the phone to work?