Ran the Samsung/Verizon updater that pops up when you plug phone into computer.
Got an upgrade that inabled the Samsung Pay app and run time, I installed days ago.
Every thing went through but ended with my cards not accepted yet.
Chase is not on the list.
I am on the T-mobile network but it didn't work in till the update.
The update is labled OG7 that's what I had, I think. It took longer to download than update. Not like a full Rom.
The latest OG7 firmware was just a monthly security patch update. Had nothing to do with Samsung Pay. http://www.verizonwireless.com/dam/support/pdf/system_update/android-generic-security-patch-su.pdf
My card activation is still pending so they must be blocking that part still some how. I did get the email from B of A that the virtual card was added but app still shows pending (been almost 2 days now).
How are you guys even getting the Samsung Pay app on your phone? I am on BOG7 as well, but don't have the app.
Side note: been using Samsung Pay on my Note 5 on T-Mobile for a while now and it's awesome Hope my Verizon phone gets it soon!
-Collin-
http://www.apkmirror.com/apk/samsun...ay/samsung-pay-1-3-2116-android-apk-download/
Google for the run time files.apk if it doesn't install.
Thanks. I just get "Connection Error" when trying to add a card
-Collin-
Add this
https://drive.google.com/file/d/0Bx58j3ZoGWenT3RHVkhLV09zem8/view?usp=docslist_api
Samsung Pay Framework_01.16.0002.apk
Thanks. My card activation is still pending after a day as well. Darn
-Collin-
CollinFX45 said:
Thanks. My card activation is still pending after a day as well. Darn
-Collin-
Click to expand...
Click to collapse
Until you get the official update from Verizon, it is unlikely to work correctly. Let's hope Verizon pushes it soon.
Also for those of you have ever rooted your phone or are thinking of rooting, once you do so Samsung Pay will never work on your phone.
Theodric58 said:
Until you get the official update from Verizon, it is unlikely to work correctly. Let's hope Verizon pushes it soon.
Also for those of you have ever rooted your phone or are thinking of rooting, once you do so Samsung Pay will never work on your phone.
Click to expand...
Click to collapse
That's not true. Just have to Odin stock and take the update. Root does not trip Knox.
MIKEYFTP said:
That's not true. Just have to Odin stock and take the update. Root does not trip Knox.
Click to expand...
Click to collapse
From what I remember PingPongRoot doesn't trip Knox, however, it wasn't the only root around and I believe there was a root method that did trip Knox but on other variants. I might just be thinking about the Note 4 though.
Sent from my Super Computer (1976) with Tap Tap Talkolution
................nobody gonna ask why people on T-Mobile are posting in the Verizon threads about an app that Verizon hasn't released for its customers yet?
Everyone should go on verizon's twitter page and complain about Samsung pay so they would hurry their asses up
matrix0886 said:
................nobody gonna ask why people on T-Mobile are posting in the Verizon threads about an app that Verizon hasn't released for its customers yet?
Click to expand...
Click to collapse
Verizon phone, T-Mobile Sim Card.
Side loaded app.
rbeavers said:
Verizon phone, T-Mobile Sim Card.
Side loaded app.
Click to expand...
Click to collapse
getting an update now
http://www.androidcentral.com/update-bringing-samsung-pay-now-hitting-compatible-verizon-phones
Successfully used Samsung Pay today for my lunch. Did OTA last night, it made me re-add my card to Samsung pay (it was already installed a couple week ago from apk mirror). It activated within minutes. So glad this works now...want to use it other places too
Samsung pay finally good to go for several more banks. Will test this puppy out after work >=D
http://www.androidpolice.com/2015/1...e-eligible-for-a-100-samsung-com-coupon-code/
Related
Thanks for all the help on here guys. I loved my S4 but it was time to upgrade. Even though I have been stuck on Samsung phones for years, I decided to switch to the Nexus 6. With carriers locking everything down I figured I might as well. I'm extremely happy with this device so far.
And thanks Muniz_ri, you made my time with the S4 bearable.
dankhar said:
Thanks for all the help on here guys. I loved my S4 but it was time to upgrade. Even though I have been stuck on Samsung phones for years, I decided to switch to the Nexus 6. With carriers locking everything down I figured I might as well. I'm extremely happy with this device so far.
And thanks Muniz_ri, you made my time with the S4 bearable.
Click to expand...
Click to collapse
AT&T is the one that locks bootloaders on Samsung!!!! NOT Samsung...
Reread what I said. "With CARRIERS locking everything down." Never said Samsung was doing it. I was just saying I've always used a Samsung phone, but since they are all being locked on my current carrier I switched to the Nexus.
tailgunner9 said:
AT&T is the one that locks bootloaders on Samsung!!!! NOT Samsung...
Click to expand...
Click to collapse
AT&T had to get Samsung's approval to modify the bootloaders to lock them, so Samsung was complicit in it, they could have easily said no.
They make the most popular phone on earth, I doubt AT&T or Verizon would have stopped carrying them and have their customers buy them elsewhere if they were threatening to drop the phone from their plans.
Apoplectic1 said:
AT&T had to get Samsung's approval to modify the bootloaders to lock them, so Samsung was complicit in it, they could have easily said no.
They make the most popular phone on earth, I doubt AT&T or Verizon would have stopped carrying them and have their customers buy them elsewhere if they were threatening to drop the phone from their plans.
Click to expand...
Click to collapse
Does AT&T lock them on all their phones??? Think I have read that T-Mobile did not lock their Samsung phones, not sure on others at T-Mobile.
tailgunner9 said:
Does AT&T lock them on all their phones??? Think I have read that T-Mobile did not lock their Samsung phones, not sure on others at T-Mobile.
Click to expand...
Click to collapse
I believe so, yes. AT&T has been on the record as stating that they refuse to support any phone with a non-locked bootloader (though, I have no idea where they stand on the new Nexus 6, which I don't believe has one and they do carry).
tailgunner9 said:
AT&T is the one that locks bootloaders on Samsung!!!! NOT Samsung...
Click to expand...
Click to collapse
That doesn't stop HTC from providing unlockable bootloaders on the M7/M8. They allow you to unlock your bootloader in exchange for your warranty, even on AT&T,but Samsung doesn't. I think LG will start unlocking bootloaders soon as well.
If I could afford it or should I say the wife wouldn't pitch a fit I think the Nexus 6 would be my choice as well. I have been on T-Mobile for over 10 years but got the AT&T S4 for free or I wouldn't be in this locked mess.
Yeah. So far I have been using the Nexus since I made this post. Unlocking and rooting were easy and I love 5.0.1. It was a big change from Samsung's S4 having no real buttons and such. But so far I have no complaints. Not gonna lie it did take a few days yo adjust to it. Still glad I made this switch though. I may use a Samsung device again someday, but if I do I would have to go the Developer route.
You know you could just get a T-Mobile Samsung Galaxy S4 or S5 since it has no locked bootloader and then SIM unlock it to work on AT&T.
I got lucky with my Galaxy S4, as it came with the MDL firmware. As soon as I realized it, I froze all the OTA crap so I can take advantage of the LOKI exploit and install Clockwork mod recovery.
Yep without the loki exploit, I dont think gs4 is worth it... I dont safestrap.
Sent from my SGH-I337 using XDA Free mobile app
StoneyJSG said:
You know you could just get a T-Mobile Samsung Galaxy S4 or S5 since it has no locked bootloader and then SIM unlock it to work on AT&T.
I got lucky with my Galaxy S4, as it came with the MDL firmware. As soon as I realized it, I froze all the OTA crap so I can take advantage of the LOKI exploit and install Clockwork mod recovery.
Click to expand...
Click to collapse
Heard they use different LTE freq. Cannot say for sure.
tailgunner9 said:
Heard they use different LTE freq. Cannot say for sure.
Click to expand...
Click to collapse
They use the exact same LTE bands.
TMobile:
http://www.samsung.com/us/mobile/cell-phones/SGH-M919ZWATMB-specs
AT&T:
http://www.samsung.com/us/mobile/cell-phones/SGH-I337ZWAATT-specs
I have an at&t note edge. Running stock kitkat 4.4.4. I see the at&t note 4 has been getting the lollipop update. But nothing for the note edge. I read that the note edge might not get the update. Ive been waiting for a long time now. If I want to put lollipop on my phone myself what should or could I do? Can I root the phone then maybe flash a rom on to it?
Due to the Bootloader been locked by AT&T I don't see a root coming any time soon for our Note Edge.
I'm still loving the edge as is, but if it was rootable, I'd love it even more.
NitroSS said:
I have an at&t note edge. Running stock kitkat 4.4.4. I see the at&t note 4 has been getting the lollipop update. But nothing for the note edge. I read that the note edge might not get the update. Ive been waiting for a long time now. If I want to put lollipop on my phone myself what should or could I do? Can I root the phone then maybe flash a rom on to it?
Click to expand...
Click to collapse
Just out of curiosity, where did you read that? I find it hard to believe that even AT&T being themselves wouldn't push an almost completed update to such an expensive flagship....
raynan said:
Just out of curiosity, where did you read that? I find it hard to believe that even AT&T being themselves wouldn't push an almost completed update to such an expensive flagship....
Click to expand...
Click to collapse
Right !! I'm on Verizon and my wife just got the update yesterday on her note 4 and I've pushed the system update button every hour or so since then with no update for my Note edge at all hummmm!!
raynan said:
Just out of curiosity, where did you read that? I find it hard to believe that even AT&T being themselves wouldn't push an almost completed update to such an expensive flagship....
Click to expand...
Click to collapse
I read it over on some of at&ts online forums. I have also been checking every day to see if there is an update on my phone. Its a little weird the note 4 is getting updates but nothing for the edge.
NitroSS said:
I read it over on some of at&ts online forums. I have also been checking every day to see if there is an update on my phone. Its a little weird the note 4 is getting updates but nothing for the edge.
Click to expand...
Click to collapse
The reason I find it unlikely, from a development standpoint, is because they are virtually the exact same hardware the only major difference being the edge screen, obviously, which would just require a bit of tweaking of the edge screen apps which is already done by Samsung...
Let's also remember the edge came out a month later give at&t time and they will push out lollipop for the edge.
Guess what? I just checked again today for an update. Says it's ready to download! I'll have to go find a WiFi hot spot.
NitroSS said:
Guess what? I just checked again today for an update. Says it's ready to download! I'll have to go find a WiFi hot spot.
Click to expand...
Click to collapse
Woohooo! Awesome! Mine is downloading now.
Mine is downloading very slow download though.
I was gonna make a new thread but I might as well just reply here. I just bought a new unlocked Note Edge but I'm still stuck on 4.4.4. It keeps saying that my phone is up to date even though that's clearly not true. Shouldn't an unlocked phone get it before all the carrier versions? Not to mention, I am in Australia which from what I read should've been the first place to get the update. Any thoughts?
Being in Australia I'd say you should have. I unlocked my phone a few days ago on kitkat 4.4.4. Then today updated to the new lollipop. The update came out yesterday here from at&t. I'm on AT&T in the usa. I have been testing t mobile with it. But so far not impressed with the service area range of t mobile. Maybe it's your service provider?
NitroSS said:
Maybe it's your service provider?
Click to expand...
Click to collapse
Yeah could be but as I mentioned, I bought an unlocked Note Edge and I'm just using a pre-paid SIM card right now so I'm not tied to any carriers. I was always under the impression that unlocked phones don't need to wait for carriers to release updates?
I have never heard of an unlocked phone getting updated before a locked phone on the same network. From what little I know, it being unlocked just allows you to use your phone on other carriers/networks.
NitroSS said:
I have never heard of an unlocked phone getting updated before a locked phone on the same network. From what little I know, it being unlocked just allows you to use your phone on other carriers/networks.
Click to expand...
Click to collapse
So you mean if I put a SIM card in now from a carrier that has already pushed the update out then I should be able to update it? I guess I always thought that unlocked phones would get the update through the phone manufacturer (so in this case, Samsung) instead of waiting for the carrier's approval.
marcolorenzo said:
So you mean if I put a SIM card in now from a carrier that has already pushed the update out then I should be able to update it? I guess I always thought that unlocked phones would get the update through the phone manufacturer (so in this case, Samsung) instead of waiting for the carrier's approval.
Click to expand...
Click to collapse
If your phone isn't branded just go to sammobile.com and download the lollipop update for your phone version.
cnote74 said:
If your phone isn't branded just go to sammobile.com and download the lollipop update for your phone version.
Click to expand...
Click to collapse
Thanks a lot for the info! Well I just went there and downloaded Kies3 (I'm totally new to Samsung) but it doesn't seem to think that my phone needs to be updated (there's no notifications under Firmware information). My current firmware version is N915GXXU1ANK4. The closest model number I could find was the GALAXY Note Edge (SM-N915G) and the newest firmware for my country/carrier (Australia, no carrier) is the 5.0.1 released on 17.02.2015. Could you please take a look and see if that is in indeed the one I need to download without fear of bricking my phone? Thanks a lot!
marcolorenzo said:
Thanks a lot for the info! Well I just went there and downloaded Kies3 (I'm totally new to Samsung) but it doesn't seem to think that my phone needs to be updated (there's no notifications under Firmware information). My current firmware version is N915GXXU1ANK4. The closest model number I could find was the GALAXY Note Edge (SM-N915G) and the newest firmware for my country/carrier (Australia, no carrier) is the 5.0.1 released on 17.02.2015. Could you please take a look and see if that is in indeed the one I need to download without fear of bricking my phone? Thanks a lot!
Click to expand...
Click to collapse
What is your phone model number mine is n915a?
cnote74 said:
What is your phone model number mine is n915a?
Click to expand...
Click to collapse
Oops, yeah I guess I should've just checked that instead of trying to figure it out from my current firmware :silly: My model number is SM-N915G so I guess I'm on the right track. Is there a way to determine for sure which country my phone belongs to? I bought it at a standard brick and mortar shop here so I'm 99% certain it's an Australian phone, but just in case?
marcolorenzo said:
Oops, yeah I guess I should've just checked that instead of trying to figure it out from my current firmware :silly: My model number is SM-N915G so I guess I'm on the right track. Is there a way to determine for sure which country my phone belongs to? I bought it at a standard brick and mortar shop here so I'm 99% certain it's an Australian phone, but just in case?
Click to expand...
Click to collapse
It should be Australian most firmware on Sam mobile tell you what country the firmware is from. Some have multi csc so it can be used in another country, if it has multi csc just get glue service providers apn and enter it for internet to work properly.
I went to the store and was checking out, getting ready to use Samsung Pay, but when I launched the app it brought me straight to the set up screen to add a card with none saved. There was no update or anything, and I've successfully used the previous tokenized card on the app. What the heck, how am I supposed to rely on this as a payment solution when the card disappears randomly from the app?
I've had this watch less than a week and I don't know how to prevent this moving forward to avoid having a situation where I'm at a store and I can't even use one of the primary features of this watch.
Did you disable lock screen? Samsung Pay won't work without a lock screen pin code etc
highaltitude said:
Did you disable lock screen? Samsung Pay won't work without a lock screen pin code etc
Click to expand...
Click to collapse
I did not remove the lock PIN since I set up Samsung Pay the first time about a week ago. The watch app acted like it was the first time I ever turned it on despite me setting up the app and using my card on it successfully a couple days ago.
Crazy. Do you have S-pay on your phone too? I don't as mine has tripped knox. I had to remove the phone version but leave gear S version for it to work. Hope you get it figured out.
highaltitude said:
Crazy. Do you have S-pay on your phone too? I don't as mine has tripped knox. I had to remove the phone version but leave gear S version for it to work. Hope you get it figured out.
Click to expand...
Click to collapse
Yep. I've got a GS7 edge with Samsung Pay configured. Thankfully that still has kept my card for a couple months now.
I have the same issue all my cards keep deleting after about a day or so - I've opened a ticket with Samsung Pay support haven't heard back from them yet
Make sure your watch S pay is updated. The last version used to do that to me.
I only had that happen when I turned off PIN unlock.
My Gear S3 has been recently been doing what the OP has stated. I have added my cards a second time and it has deleted my cards a second time again. Anyone know if it's the new update for some reason?
Any update to this? Just happened to me. Cards deleted within 24 hours. WTF? Since I use a Credit Union...I can't verify my card 'til Monday. As much as I like this watch...it's the little things that give me Buyer's Remorse.
Since this thread is so small... Guessing that it's not as wide spread...or not too many people care?
SiNJiN76 said:
Any update to this? Just happened to me. Cards deleted within 24 hours. WTF? Since I use a Credit Union...I can't verify my card 'til Monday. As much as I like this watch...it's the little things that give me Buyer's Remorse.
Since this thread is so small... Guessing that it's not as wide spread...or not too many people care?
Click to expand...
Click to collapse
Not sure if it's the same issue but I recently had my Amex card stop working...it was showing on my S3 but when I went to use it, it popped up saying "Contact Customer Service". I think an update did get pushed to my watch which might have caused it? I was able to delete and re-add the card without issues and its working again now.
stwallman said:
Not sure if it's the same issue but I recently had my Amex card stop working...it was showing on my S3 but when I went to use it, it popped up saying "Contact Customer Service". I think an update did get pushed to my watch which might have caused it? I was able to delete and re-add the card without issues and its working again now.
Click to expand...
Click to collapse
I have been getting a different popup with my Amex card where Samsung Pay on the S3 shows the 'stay connected to phone' error with my Amex card. It's happened every few months or so. Maybe it's something about Amex cards all together since that's the only card that I've ever had an issue with on the S3. The Amex card continues to work fine on my Galaxy S6 Samsung Pay app without incident, so it's just the S3 Samsung Pay app that has the problem with this card.
Sent from my SM-T800 using XDA-Developers Legacy app
My card gets s removed from my Gear S3 whenever I wear my Gear S2, then go back to wearing my Gear S3. Samsung says this is normal. It's a pain and very frustrating.
I just had all my cards deleted from Samsung pay for no reason. I only found out about it because of emails from Amex saying your card was removed from Samsung pay...at first I thought it was Amex cancelling an account, but all the cards are done and it invites me to "start using Samsung pay". Grr...
I have a Pixel XL running lates 8.1 Oreo OS, with the T-mobile Gear s3 classic. No issues in the past ten days or so prior to now.
Any insight into what might be wrong, or suggestions on how to get it fixed would be very much appreciated. TIA
I've had the Gear S3 for about a month. Loaded two cards into Samsung pay and used them several times over a couple weeks. This morning they didn't show up on the watch and going to "Samsung Pay" in settings it was like I never set it up. I reloaded and activated both cards and it's all ok again. Both cards come up on the watch again. We'll see how long this lasts.
This has happened to me a couple of times over the past 3 months. It's so annoying. My card never gets removed from Google Pay but has been removed from Samsung Pay on my Gear S3 around 4 or 5 times lately. I've had my Gear S3 for a year and a half, and never experienced this issue before.
I'm in the UK and bank with Nationwide, if this helps anyone. Plus my phone isn't a Samsung, the phone my Gear S3 Frontier is connected to is a Huawei Mate 10 Pro.
Ongoing since purchase
stwallman said:
Not sure if it's the same issue but I recently had my Amex card stop working...it was showing on my S3 but when I went to use it, it popped up saying "Contact Customer Service". I think an update did get pushed to my watch which might have caused it? I was able to delete and re-add the card without issues and its working again now.
Click to expand...
Click to collapse
I've had this issue since I purchased the watch in March. It seems random, possibly related to the watch trying to communicate with my phone and failing? Looking at the posts here the only common factor seems to be the watch itself.
I've been getting the card still being present but getting the contact customer support message. I get it about a week after adding the card back. So I just keep doing it, get frustrating. I called Samsung pay and they went round and round and finally asked what phone I'm using and told them it's a OnePlus 6. They came back and said my phone isn't compatible with Samsung pay. I asked why does it content and setup then if not compatible and works for a week or so at a time and they didn't know.
I'm going to try and freeze the Samsung pay on my phone and just leave the one on the watch running and see if that does the trick.
I'm very confused. Some people say I can root it just like a nexus, some say that Google would just brick my phone, and I also heard I would need a custom ROM first. I'm super confused. Can anyone help me out please? Rooting is very important to me. Also it's the pixel XL if for some reason it could make a slight difference in what I would install/use.
OK. All pixels or pixels XL can be bootloader unlocked and rooted except for Verizon and EE variants running the 7.1.1.
Read in the dev section. It's much like a nexus, only thing is the two partitions need to be accounted for.
I'm running Dec 7.1.1 stock rooted with twrp. No issues at all.
Have you looked in the development forum at all?
If you have a pixel from Google you can unlock the bootloader and root it.
If you have a Verizon pixel you can only root if the bootloader is unlocked. The only way you can u look k the bootloader is if you are on 7.1. if you have updated to 7.1.1 you cannot unlock the bootloader therefore you can't root.
aholeinthewor1d said:
Have you looked in the development forum at all?
If you have a pixel from Google you can unlock the bootloader and root it.
If you have a Verizon pixel you can only root if the bootloader is unlocked. The only way you can u look k the bootloader is if you are on 7.1. if you have updated to 7.1.1 you cannot unlock the bootloader therefore you can't root.
Click to expand...
Click to collapse
Is anyone working on a bootloader unlock for 7.1.1 on VZ? Just got my Pixel today and took the update before I knew better.
Squintz said:
Is anyone working on a bootloader unlock for 7.1.1 on VZ? Just got my Pixel today and took the update before I knew better.
Click to expand...
Click to collapse
To my knowledge there is no one working on an unlock for the VZW devices on 7.1.1. The "method" previously used was stumbled across. Even though I am unsure of how Verizon blocks enabling bootloader unlocking I very highly doubt that a new method will be found. Every device in Verizon's history that could either be exploited or had an unlocked method exposed had a patch issued to block it. Once patched there has never been a second exploit found.
FernBch said:
To my knowledge there is no one working on an unlock for the VZW devices on 7.1.1. The "method" previously used was stumbled across. Even though I am unsure of how Verizon blocks enabling bootloader unlocking I very highly doubt that a new method will be found. Every device in Verizon's history that could either be exploited or had an unlocked method exposed had a patch issued ro block it. Once patched there has never been a second exploit found.
Click to expand...
Click to collapse
Yea Verizon sucks. S3 and s5 both eventually were unlocked and stayed that eay
aholeinthewor1d said:
Yea Verizon sucks. S3 and s5 both eventually were unlocked and stayed that eay
Click to expand...
Click to collapse
I completely agree. The first S4 was released with the MDK bootloader. Loki was the exploit. That device lived to see both an AOSP 7.1 and OptimizedCM 14.1. The first OTA they pushed blocked it and many were quite upset. A new method was never discovered. Not sure if Big Red still uses the same "excuse" as back then but they claimed they were protecting network security. Blow that smoke up someone else's ***. I'm not so easily suckered.
FernBch said:
I completely agree. The first S4 was released with the MDK bootloader. Loki was the exploit. That device lived to see both an AOSP 7.1 and OptimizedCM 14.1. The first OTA they pushed blocked it and many were quite upset. A new method was never discovered. Not sure if Big Red still uses the same "excuse" as back then but they claimed they were protecting network security. Blow that smoke up someone else's ***. I'm not so easily suckered.
Click to expand...
Click to collapse
Yup and now I'm stuck with them unless I wanna give up unlimited data
aholeinthewor1d said:
Yup and now I'm stuck with them unless I wanna give up unlimited data
Click to expand...
Click to collapse
You could always return that and buy a pixel from Google, you could still use it on Verizon and i would think still keep your plan.
Sent from my Pixel XL using Tapatalk
jreink01 said:
You could always return that and buy a pixel from Google, you could still use it on Verizon and i would think still keep your plan.
Click to expand...
Click to collapse
I already unlocked my bootloader so I'm good thankfully. Just in general I am sick of Verizon cause most of the time we can't unlock bootloader. Got lucky with the pixel for a little. Sucks for new people getting it though who can't unlock
aholeinthewor1d said:
I already unlocked my bootloader so I'm good thankfully. Just in general I am sick of Verizon cause most of the time we can't unlock bootloader. Got lucky with the pixel for a little. Sucks for new people getting it though who can't unlock
Click to expand...
Click to collapse
OK, with that being said, your probably out of luck on rooting then. Was just providing another possible option.
Sent from my Pixel XL using Tapatalk
jreink01 said:
OK, with that being said, your probably out of luck on rooting then. Was just providing another possible option.
Click to expand...
Click to collapse
Not sure what you are talking about. I have a Verizon pixel with unlocked bootloader and I am rooted. I was just stating that on general I hate Verizon because they require bootloaders to be locked. We got lucky with the pixel because there was an exploit found to unlock it..Which is how I was able to unlock mine.
Now that the recent update patched the exploit it sucks for other people getting Verizon pixels cause once they ship with the update they will not be able to unlock bootloader
aholeinthewor1d said:
Not sure what you are talking about. I have a Verizon pixel with unlocked bootloader and I am rooted. I was just stating that on general I hate Verizon because they require bootloaders to be locked. We got lucky with the pixel because there was an exploit found to unlock it..Which is how I was able to unlock mine.
Now that the recent update patched the exploit it sucks for other people getting Verizon pixels cause once they ship with the update they will not be able to unlock bootloader
Click to expand...
Click to collapse
That's not the only things that sucks for those still waiting and wanting to unlock. I am hearing of clerks in the store activating them before giving it to the customer. They are buying an unlocked device and being given a locked device.
FernBch said:
That's not the only things that sucks for those still waiting and wanting to unlock. I am hearing of clerks in the store activating them before giving it to the customer. They are buying an unlocked device and being given a locked device.
Click to expand...
Click to collapse
Well that's normal procedure for any carrier. You get a phone they open it and try to activate and test. You just have to say "WAIT" and explain that you have to change a setting before activating. Then take sim out and skip everything and turn off auto updates in developer options. Use your best judgement based on the rep you are dealing with. With best buy before even going there to exchange my pixel.. I thankfully got someone who did the same tinkering I did with phone so I was honest with him and I got him to exchange my phone straight out.. without having to do the whole return thing with verizom and mess up my plan. I also examined why I had to take the SIM out and not active and he was cool with it. I walked in and have him my box and he gave me another and that was it haha.
But dealing with verizon you could simple say you heard the update causes issues so you wanna test without it first.. if they say no then argue. They may be required to activate but they definitely don't have any kind of policy that says you can't skip activation during setup and do it right after.
FernBch said:
That's not the only things that sucks for those still waiting and wanting to unlock. I am hearing of clerks in the store activating them before giving it to the customer. They are buying an unlocked device and being given a locked device.
Click to expand...
Click to collapse
It depends on whether or not you're dealing with a knowledgeable Verizon Corporate Store associate (I don't deal with authorized resellers.) He does not have to open the box to activate the phone. He's required to record the IMEI and the SIM IDs, but those values are printed on the box for the last 2 years. The majority of the time, I walk out with still-shrinkwrapped phones. (Obviously, that doesn't guarantee that that particular phone still has an unlockable firmware.)
---------- Post added at 12:38 PM ---------- Previous post was at 12:35 PM ----------
aholeinthewor1d said:
Well that's normal procedure for any carrier. You get a phone they open it and try to activate and test. You just have to say "WAIT" and explain that you have to change a setting before activating. Then take sim out and skip everything and turn off auto updates in developer options. Use your best judgement based on the rep you are dealing with. With best buy before even going there to exchange my pixel.. I thankfully got someone who did the same tinkering I did with phone so I was honest with him and I got him to exchange my phone straight out.. without having to do the whole return thing with verizom and mess up my plan. I also examined why I had to take the SIM out and not active and he was cool with it. I walked in and have him my box and he gave me another and that was it haha.
But dealing with verizon you could simple say you heard the update causes issues so you wanna test without it first.. if they say no then argue. They may be required to activate but they definitely don't have any kind of policy that says you can't skip activation during setup and do it right after.
Click to expand...
Click to collapse
^^^^
He is dead on. You can simply say "I don't want it unwrapped."
quangtran1 said:
It depends on whether or not you're dealing with a knowledgeable Verizon Corporate Store associate (I don't deal with authorized resellers.) He does not have to open the box to activate the phone. He's required to record the IMEI and the SIM IDs, but those values are printed on the box for the last 2 years. The majority of the time, I walk out with still-shrinkwrapped phones. (Obviously, that doesn't guarantee that that particular phone still has an unlockable firmware.)
---------- Post added at 12:38 PM ---------- Previous post was at 12:35 PM ----------
^^^^
He is dead on. You can simply say "I don't want it unwrapped."
Click to expand...
Click to collapse
True, but that is what they are doing. I've been on VZW for years. When I got mine they opened the package and went to insert the SIM and I told them to stop. They said "We have to make sure it activates before you leave the store". I said "No you don't, If you place a SIM in and activate it the deal and sale is off". Long story short I left with a device that did not get powered on. And this was at the VZW store, not a reseller.
I was told at the Verizon store when I got mine, as long as you go to the big corporate store they don't have to set it up, but If you go to the little retail ones they do. I put my sim card in. Had absolutely no problem. I just didn't click on the 7.1.1 update. it didn't automatically update while I set it up. I got home and unlocked. What worries me the most is me going and breaking this thing and getting another one past 7.11, I really wish I would have gone through Google.
mac796 said:
I was told at the Verizon store when I got mine, as long as you go to the big corporate store they don't have to set it up, but If you go to the little retail ones they do. I put my sim card in. Had absolutely no problem. I just didn't click on the 7.1.1 update. it didn't automatically update while I set it up. I got home and unlocked. What worries me the most is me going and breaking this thing and getting another one past 7.11, I really wish I would have gone through Google.
Click to expand...
Click to collapse
Yup that's my fear to. If I ever have an issue and need a replacement I'm screwed.
mac796 said:
I was told at the Verizon store when I got mine, as long as you go to the big corporate store they don't have to set it up, but If you go to the little retail ones they do. I put my sim card in. Had absolutely no problem. I just didn't click on the 7.1.1 update. it didn't automatically update while I set it up. I got home and unlocked. What worries me the most is me going and breaking this thing and getting another one past 7.11, I really wish I would have gone through Google.
Click to expand...
Click to collapse
aholeinthewor1d said:
Yup that's my fear to. If I ever have an issue and need a replacement I'm screwed.
Click to expand...
Click to collapse
I should have bought from Google, too. Since I didn't the first thing I bought after getting the phone was the Defender case. Third device I've bought that case for and it hasn't let me down yet.
aholeinthewor1d said:
Not sure what you are talking about. I have a Verizon pixel with unlocked bootloader and I am rooted. I was just stating that on general I hate Verizon because they require bootloaders to be locked. We got lucky with the pixel because there was an exploit found to unlock it..Which is how I was able to unlock mine.
Now that the recent update patched the exploit it sucks for other people getting Verizon pixels cause once they ship with the update they will not be able to unlock bootloader
Click to expand...
Click to collapse
It is pretty easy... Just buy your phone from Google. Verizon has nothing to do with it, be an adult and buy what you want.
Sent from my Pixel using Tapatalk
For all us impatient OnePlus fans who just had to have it now and went out to purchase the tmo variant instead of ordering the unlocked variant I was wondering has anyone been able to get it unlocked from TMobile imediatly? I've tried several times with no luck.
I tried contacting TMO via Twitter and the rep said she couldn't do anything. She told me that she would absolutely make an exception but that there was no way to override the 40 day/paid in full restrictions. I'm not sure how credible that is though since others claim to have gotten theirs unlocked regardless, but oh well. I'll try calling support later today.
I'm hoping that someone finds a way to reflash the device soon before the return period ends.
I did via TMobile help on Twitter. With Jump on demand and not paid off
dchurch85 said:
I did via TMobile help on Twitter. With Jump on demand and not paid off
Click to expand...
Click to collapse
???
dchurch85 said:
I did via TMobile help on Twitter. With Jump on demand and not paid off
Click to expand...
Click to collapse
I'm jealous. By any chance, can you post screenies of what you said to the support agent? I wanna see how you were able to get them to unlock it
I called and messaged three different people. They both told me no. I reached out on twitter, he made me pay off the phone to unlock it which I think is legit. I didn't have to wait 40 days.
Spoke to a rep on the phone prior, she said if I paid off the phone I would have to wait 40 days
Do not wait just call 611 from your phone.
Tell them you are a developer and the phone is of no use to you without unlocking it. Then tell them it was just the same as on op6t they put u on hold then tell you to try the unlock app.
It worked for me but T-Mobile help on Twitter was a no go 3 times.
bmg1001 said:
I tried contacting TMO via Twitter and the rep said she couldn't do anything. She told me that she would absolutely make an exception but that there was no way to override the 40 day/paid in full restrictions. I'm not sure how credible that is though since others claim to have gotten theirs unlocked regardless, but oh well. I'll try calling support later today.
I'm hoping that someone finds a way to reflash the device soon before the return period ends.
Click to expand...
Click to collapse
That's exactly how the first one I talked to was. I tried a second rep later on, and they told me that since I was a 10-year customer, they'd override the requirements! I'm now SIM unlocked I also applied for my bootloader unlock .bin through the OnePlus site, so in a week or so, I should be rooted!
nmil1484 said:
I called and messaged three different people. They both told me no. I reached out on twitter, he made me pay off the phone to unlock it which I think is legit. I didn't have to wait 40 days.
Spoke to a rep on the phone prior, she said if I paid off the phone I would have to wait 40 days
Click to expand...
Click to collapse
twinnfamous said:
Tell them you are a developer and the phone is of no use to you without unlocking it. Then tell them it was just the same as on op6t they put u on hold then tell you to try the unlock app.
It worked for me but T-Mobile help on Twitter was a no go 3 times.
Click to expand...
Click to collapse
sabrdawg said:
That's exactly how the first one I talked to was. I tried a second rep later on, and they told me that since I was a 10-year customer, they'd override the requirements! I'm now SIM unlocked I also applied for my bootloader unlock .bin through the OnePlus site, so in a week or so, I should be rooted!
Click to expand...
Click to collapse
Are you guys paid in full, eip or JOD?
I'm financing mine via JUMP.
dchurch85 said:
I did via TMobile help on Twitter. With Jump on demand and not paid off
Click to expand...
Click to collapse
I was able to unlock on JOD and my phone is not paid off. I told them I was traveling for 3 months so they wouldn't try to do the temp unlock because you can only temp unlock for 2 months. I told them I wanted the permanent unlock because I didn't want to have to deal with trying to get permission on a 3rd unlock and now I'm out the country with no phone. Did a bit of flexing my 8 year tenure as well but all this was about a 5 min convo and they did it.
That's awesome! For my 6T, they agreed to SIM unlock if I paid two installments, which totaled at $83, and I thought that was good, but this time around, they really showed their appreciation for their long-time customers! I was elated ?
Tweezydak1d said:
I was able to unlock on JOD and my phone is not paid off. I told them I was traveling for 3 months so they wouldn't try to do the temp unlock because you can only temp unlock for 2 months. I told them I wanted the permanent unlock because I didn't want to have to deal with trying to get permission on a 3rd unlock and now I'm out the country with no phone. Did a bit of flexing my 8 year tenure as well but all this was about a 5 min convo and they did it.
Click to expand...
Click to collapse
Nice. I keep trying but each one says something else. Did you do phone or twitter?
Hey everyone! So I was able to get T-Mobile Twitter to unlock it. The rep is telling me to the use the unlock app, but I keep getting a Server error error code = 1 your device isn't recognized by the carrier. If looked through the 6T forums seems like the app isn't asking for phone permissions and the permissions is greyed in in setting (No perms requested)
Any idea on how to get the app to work?
thecool07 said:
Hey everyone! So I was able to get T-Mobile Twitter to unlock it. The rep is telling me to the use the unlock app, but I keep getting a Server error error code = 1 your device isn't recognized by the carrier. If looked through the 6T forums seems like the app isn't asking for phone permissions and the permissions is greyed in in setting (No perms requested)
Any idea on how to get the app to work?
Click to expand...
Click to collapse
I can't get the app to work either...... (JOD, Called 611 told them I wanted it unlocked so I could install OnePlus version of OS, flexed my 11-year service and she unlocked it. Shows unlocked on tmo website but OEM Unlocking is still grayed out).
Well I just got mine unlocked, mines is paid in full. It took me like 5 tries twice on Twitter 3 times on the phone. My 3rd try on the phone I flat out told them "look, I'm looking for someone to unlock my phone because all the other reps keep giving me the run around. I know you guys can unlock it right away, I own the phone I shouldn't have to wait no freaking 40 days or 7 days. I need it unlocked now because I travel." Sure enough the rep apologised for the other reps and unlocked me right away.
thecool07 said:
Hey everyone! So I was able to get T-Mobile Twitter to unlock it. The rep is telling me to the use the unlock app, but I keep getting a Server error error code = 1 your device isn't recognized by the carrier. If looked through the 6T forums seems like the app isn't asking for phone permissions and the permissions is greyed in in setting (No perms requested)
Any idea on how to get the app to work?
Click to expand...
Click to collapse
Have you updated to latest ota? Also this happened when I was on op6t and I fixed it by factory reset. Then skipped through set up and right to the app. It will only unlock with your sim card in the device.
twinnfamous said:
Have you updated to latest ota? Also this happened when I was on op6t and I fixed it by factory reset. Then skipped through set up and right to the app. It will only unlock with your sim card in the device.
Click to expand...
Click to collapse
Yup I am on the latest. There was in OTA while I setting it up. I guess I will have to try a factory reset and hope that fixes it!
matteosaeed said:
Nice. I keep trying but each one says something else. Did you do phone or twitter?
Click to expand...
Click to collapse
On the phone
twinnfamous said:
Have you updated to latest ota? Also this happened when I was on op6t and I fixed it by factory reset. Then skipped through set up and right to the app. It will only unlock with your sim card in the device.
Click to expand...
Click to collapse
So tried resetting no luck! The rep on twitter assures me its because its locked and won't process on there end. But tried two factory reset and the app just spits out the same error code