So I was having an issue with upload speeds in another thread and one of the fine people of this forum informed me to check my build number because it might be fixed with the newest build. I checked and I was on the build that was shipped with the phone. I've had the phone since launch day and never received the update.
Well here's the kicker, I input a T-Mobile SIM in the Verizon phone from initial boot. I have not received an update since I turned on the phone 4 days ago and everyone has stated the newest update should come down within a few minutes on being turned on. I put a Verizon SIM in the phone and what do you know, the update came right down.
So I pose this question to the more informed than I am... Is the Verizon bootloader technically blocking updates to other carriers? Maybe you need to get the newest update and activate it on Verizon first then it will flow and act as unlocked?
I thought this would be important to the many who purchased from Verizon because of availability.
Others have reported getting updates with tmo and at&t sims already in other threads. ymmv
Related
Okay this is kind of weird because I know T-Mobile has not rolled out the update. In fact I believe they are completely refusing to do it to force people to resort to upgrading phones. But I got this system update on my phone this morning and I am wondering if anybody has gotten it as well or has any explanation. I haven't downloaded it yet.
T-Mobile SGH-M919. Weird because it says the GPE
it has been said before if you would have searched, but it is a patch for the stagefright vulnerability and that is about it.
ogkillergreen said:
Okay this is kind of weird because I know T-Mobile has not rolled out the update. In fact I believe they are completely refusing to do it to force people to resort to upgrading phones. But I got this system update on my phone this morning and I am wondering if anybody has gotten it as well or has any explanation. I haven't downloaded it yet.
T-Mobile SGH-M919. Weird because it says the GPE
Click to expand...
Click to collapse
GPe? That's odd, unless you're running a custom ROM
Sent from my SGH-M919 using XDA Free mobile app
ogkillergreen said:
Okay this is kind of weird because I know T-Mobile has not rolled out the update. In fact I believe they are completely refusing to do it to force people to resort to upgrading phones. But I got this system update on my phone this morning and I am wondering if anybody has gotten it as well or has any explanation. I haven't downloaded it yet.
T-Mobile SGH-M919. Weird because it says the GPE
Click to expand...
Click to collapse
Which rom where you using when you get this message?
GPE has already been updated to 5.1, so even if that is LP it's still older than current.
I have been calling TMOBILE (US) every week since May to find out where the LOLLIPOP UPGRADE is for my SGH-M919 ((Galaxy S4) and finally about 3 weeks ago I got them to confess that SAMSUNG HAD GIVEN THEM TO UPDATE FOR THIS PHONE - BUT, THEY WERE NOT GOING TO RELEASE IT.
When I asked why, I was given the B***S*** answer that there were known bugs and all other providers had problems with it - I said they were corrected in the 5.01, and 5.1 versions - he then basically (without saying it) stated they want people to buy newer devices.
I told him I OWN MY DEVICE, THERE IS NOTHING WRONG WITH IT, and I WILL ROOT IT AND PUT A CUSTOM ROM ON IT.
I was told, you will void your warranty.....I rolled with laughter and said...it is over 2 years old - THERE IS NO F***ING WARRANTY anymore...and I hung up.
*BH*
Yet another great example of why I jumped ship for Cricket. Tmo does all this uncarrier crap because they say they care about the consumer, but when it's all on the table they're just like Verizon or Sprint or AT&T. If you're on older hardware, then they don't care about you. You're a number that they added years ago, and all that matters are the numbers they'll add today and tomorrow.
I'm still rockin' my S4 after all this time. When I'm ready to upgrade, I'll be buying my phone unlocked and ready to go with Cricket. Now that the new Nexus devices are on their way, I'm just going to save up and splurge on the Nexus 6P and not have to worry about bull**** carriers screwing me on updates and security fixes.
I buy T-Mo phones because they traditionally have unlocked bootloaders, so I can flash whatever ROM I like. ATT, and I believe Cricket, tends to use phones where the bootloader is locked down tightly. I like the open Nexus platform and am also considering one in the future...
I have a G4 that I thought was SIM free, bought from CEX - I'm in the UK and it has no carrier splash screen, no carrier apps or random antivirus trials. To all intents and purposes it is stock. However today I received an update to software version v10G-234-20. This is not Marshmallow and it ran in at 343.19MB. I've seen no mention of it being released anywhere, which leads me to assume that it is an update from at least a month ago. The model number is LG-H815. I check for updates very regularly so this update certainly hadn't been available for my device a couple of days ago.
So my question is, why is this update only being pushed through now? And does it mean my device will get Marshmallow incredibly slowly too?
Thanks in advance, and apologies if this has already been asked/answered before, but I couldn't see it anywhere.
I'm looking to get a Note 10+ phone that can be bootloader unlocked & rooted, but I'm tied to Verizon.
Anyone using either the N976F or N975F on VZW? Any issues or tricks in order to get them to accept something other than the "V" variant that is locked down and may never have root?
Trying to figure out which of these 3 Note 10+ phone variants to go with:
N975F
N976F
N9750/DS
TIA.
UPDATE: Not officially, but it seems possible. Keep reading below for my experience...
I'm on the n9750 on Verizon and it seems to be working well. I just got it so I haven't got to fully test quite yet.
Just for reference, I wanted to post this for others since I wasn't able to find true compatibility details other than VZW's ironfisted "certified" devices (ie the locked SM-N975U):
I recently purchased a Samsung Note 10+ (SM-N975F/DS) international variant online, and was able to get successfully attached to my VZW account. I have a grandfathered unlimited data plan, and was replacing an existing phone on my account.
Here's how it went down:
Initially when I tried to activate and attach the N10+ to my account via VZW website, it told me the phone couldn't be registered on their network.
Took my phone to a local VZW store.
Told the rep I bought a new phone and needed it attached to my account.
He validated my account details (he never asked for the IMEI of my new phone) & grabbed a new sim card, did his thing on the VZW tablet terminal and then popped the sim into my new phone.
At this point, the LTE data worked almost immediately, however the voice calling didn't work. Test calls just failed and quickly exited the phone app saying call failed/ended.
He said wait a couple minutes, sometimes it takes a bit, so we did. I think we also rebooted too. He was checking various things on my phone and the account.
He noticed that the VZW system said my phone couldn't be used on their network, but said there was something he could try...
He took the sim out of my phone and popped it into his already activated VZW phone. After a maybe 30 seconds, he made a test voice call, and it worked (my sim, his phone)
Then we swapped my newly activated sim back into my new phone and after about 30 seconds, I had both LTE data (as before) and now also had voice calling. A quick test call from my phone confirmed and I was good to go!
Obviously, YMMV, but it can be done, you just might need to find a VZW rep that is helpful and willing to go the extra mile to get the international version (SM-N975F/DS) activated onto the Verizon network.
Please move it to correct forum if this is not the right one.
I bought Samsung Galaxy Note Plus 10 5G in Oct 2019 from Verizon (all paid). I ported my number from Verizon to AT&T 5 days ago (after 9 months of using it with Verizon). My account is disconnected from Verizon and I have received the port is completed e-mail from them. AT&T has confirmed that the sim is fully activated.
But Guess what, When I put the sim in mobile it says another carrier is not allowed to be used on this phone ! For last 4 days I have wasted more than 10 hours staying in Verizon store and on call with customer care and they have no idea what is going on ! Customer care says the phone is fully unlocked. After 3 days of constant trying one of the representative said you have to reactivate the old account again and then try unlock again from the backend (which I have no control of !) . And, guess what, none of those good people are reactivating the account.
Verizon store guy doesn't help, just says talk to customer care and customer care says its unlocked so they can't do anything.
What should I do ?
About the only things I can suggest are:
If you have flashed firmware that is not the Verizon carrier firmware then flash it back to Verizon carrier firmware.
If you have disabled any carrier applications on the phone please re-enable them.
Make sure they are attempting to unlock the phone while you are within native Verizon coverage
I am not sure if a non-carrier branded firmware exists for the Note 10+ 5G, but non-carrier firmware has caused network unlocking issues before. The second idea is just in case you may have used a package disabler and disabled something necessary for network unlocking the phone. Last one is from past experiences where I wasn't able to complete phone activation because I wasn't within Verizon's native coverage area. The coverage I was in, while not roaming (or extended area) was not actually native Verizon coverage... I would tend to believe this would possibly be the same for network unlocking the phone.
Otherwise get a hold of Verizon and hound them to get it unlocked. Not much else can be done really... If the phone qualifies for being unlocked they should unlock it.
Filed fcc complaint
I have filed FCC complaint. I never changed anything in the mobile (didn't even know firmware flash was a thing until now when I started looking for solutions), used it for general purpose. I am in the same area where I bought it. Verizon store guy tried everything from simple reset to factory reset wiping everything out but nothing worked.
I have also ordered a prepaid Verizon sim. I will put that in and will try to get the phone unlocked.
I will post my results after 2-3 days.
Thanks for the quick reply !
scottusa2008 said:
About the only things I can suggest are:
If you have flashed firmware that is not the Verizon carrier firmware then flash it back to Verizon carrier firmware.
If you have disabled any carrier applications on the phone please re-enable them.
Make sure they are attempting to unlock the phone while you are within native Verizon coverage
I am not sure if a non-carrier branded firmware exists for the Note 10+ 5G, but non-carrier firmware has caused network unlocking issues before. The second idea is just in case you may have used a package disabler and disabled something necessary for network unlocking the phone. Last one is from past experiences where I wasn't able to complete phone activation because I wasn't within Verizon's native coverage area. The coverage I was in, while not roaming (or extended area) was not actually native Verizon coverage... I would tend to believe this would possibly be the same for network unlocking the phone.
Otherwise get a hold of Verizon and hound them to get it unlocked. Not much else can be done really... If the phone qualifies for being unlocked they should unlock it.
Click to expand...
Click to collapse
Got it resolved.
Final Update:
Since I had filed FCC complaint online, Verizon Executive Relations department contacted me and She was able to unlock from her side with the help of 'Technical Management' employee on call.
dagarwal82 said:
I have filed FCC complaint. I never changed anything in the mobile (didn't even know firmware flash was a thing until now when I started looking for solutions), used it for general purpose. I am in the same area where I bought it. Verizon store guy tried everything from simple reset to factory reset wiping everything out but nothing worked.
I have also ordered a prepaid Verizon sim. I will put that in and will try to get the phone unlocked.
I will post my results after 2-3 days.
Thanks for the quick reply !
Click to expand...
Click to collapse
My son had a T-Mobile branded S20 5G and I moved our service to Verizon. I paid his phone off and got it unlocked. Everything was working fine up until a couple of weeks ago. He did an update (didnt pay attention to what kind of update) and now he cant make or recieved calls or text (keepin mind the phone was working fine before this update). Attempts to call result in a message from Verizon saying that they cant authenticate his phone.
I *****ed at Samsung for a bit since his phone isnt rooted and even though its over a year old if a software update bricked it, I felt like they should have some ownership of the issue. It was a waste of time so now I'm back on the phone waiting for VZW tech support.
I think the issue is that its a TMO branded phone on VZW's network and everyone is pointing the finger at everyone else. My question is 2 fold.
1) has anyone ever experienced this before, and if so what did you do to resolve it and
2) I will attempt to root it and flash a ROm on it before I entertain buuying another phone.....hes got enough other **** hes dealign with financially he doesnt need to add a new phone purchase to his plate.
Any help would be much appreciated because I'm pissed the eff off at this point.
Yes we tried different APN settings...he walked into a VWZ store and they were able to get his data working but not voice or text....seems like something is out of whack with his radios). We also did a full factory reset.....same issue persists
I am not an expert on ROMs but I will give you my two cents. When I was playing with my unlocked phone, I realized that mine updated some CSC binaries as soon as I inserted the SIM. I saw some message for it updating the CSC code from XAA to TMB when I inserted TMO SIM on stock firmware. So my suggestion would be to try downloading VZW stock firmware from samfw.com and installing that.