Having a hell of a time getting my S7 updated. It's a LTE (Verizon) version yet it does not have a SIM card or data plan active. Whenever I go to check for updates, I'm being told it is up to date. Current Android version is 10. I'd like to get this to Android 13 if possible.
So I tried to manual path. I downloaded Smart Switch per one recommendation, and that does not pop up any "updates available" messaging. I downloaded the Verizon/Samsung upgrade utility and it does not see the device. So my next idea is to use ODIN. Herein lies my problem: I cannot find Verizon firmware (Android 13) for this device. Verizon has a huge guide on the new version but no download links to the firmware to be found. Sammobile does not have it, and the other Samsung firmware sites only seem to have 12.
Any recommendations would be extremely helpful.
Related
My parents just got a new Unlocked US Edition Moto G 2014, and it is on Kit Kat out of the box. I was assuming it would just update to Lollipop during the first boot. But nothing, and checking for System Updates is not working.
We do not yet have a SIM in this new phone for several more days.
Since I am not there in town, I do not want to try and drag my parents thru the awesomeness that is sideloading an OTA.
So basically - Can Android OS Updates like Lollipop be downloaded strictly via a wifi connection (using the System Updates feature) on a SIM enabled device like a phone. Obviously it is possible on wifi only devices like tablets.
Does anyone have any official proof/documentation of how this is handled? Or even users posts showing it not working until a SIM is installed? I don't want to waste any more time trying to get the update if a SIM is required on a phone. Which is odd because my phone is Unlocked - so there is no "Official Carrier", so who provides my OTA? The carrier I choose to use? Motorola? Or Google?
Thanks in advance!
I'm using a VS985 with stock Android 35b on it. I'm using this phone on the Tracfone service, which uses Verizon towers in my area. I've been hoping to upgrade to Marshmallow, but from what I've read, the Verizon Upgrade Assistant no longer works for phones that it does not detect an active Verizon sim card in.
I uninstalled the Assistant program and when I reinstalled it, I right-clicked on it and chose "check for upgrade." When the upgrade was found, it gave me the option to "Upgrade device now" and then proceeded to download a large file. I tracked down that file and it appears to be the latest kdz file, called "VS98548A_03_0628.kdz" and is 1.50 gigs in size. However, when I connect my phone to my computer, the Assistant switches from a status of "Upgrade Available" to "Up to Date" after running a "Checking the device information" task. This appears to check online for an active Verizon sim card, as it doesn't work at all if I'm not connected to the internet. I get the same behavior with my Tracfone sim card or the Verizon sim card that came with the phone.
My question is if there is anyway to get this utility to work or if there is an alternative way to install the kdz file it downloaded without rooting my phone. I wonder if there is a way to get the Assistant to work without checking for a active Verizon sim card.
I can't address regarding the official tool - its flaky and I've had that trouble sometimes.
However, you can get the 48A KDZ from my link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, also in my signature below, and flash it with LG Flash Tool 2014 which that thread is a guide for.
Be sure to read the second post too, I believe it is, if you have any trouble with LG Flash Tool 2014.
Hey Guys,
I've come across my limit of knowledge during the past days.
I purchased this new phone, "Samsung Galaxy S 7".
When I look up the "About phone" option in "Settings", it says, that it's a SM-G930F with android verison 6.0.1.
I couldnt find ANYTHING according to my Build number, which says: MMB29M.G930FXXU1BPIA or that my Smart Switch says, that the software version would be PIA(VZW).
But when I go into Download/Odin-Mode there are the following text lines:
ODIN MODE (HIGH-SPEED)
PRODUCT NAME: SM-G930V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
FAP LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B4(2,1,1,1,1) K1 S3
SECURE DOWNLOAD: ENABLE
So, both informations are dividing from each other, because the first says it's a SM-G930F and the second says it's a SM-G930V, except that both have in common, that they say system status is official.
But, my problem is, as you can see, it's still marshmallow that is installed on my Galaxy S 7 and in my settings there is absolutely no possibility to update my phone to nougat.
I've tried several things via Odin like installing: Stock firmware for ADB, Nougat firmware for ADB, Stock firmware for VZW, Nougat firmware for VZW
But just nothing worked out.
Most common issues I had with Odin were: "sboot.bin FAIL!, recovery.img FAIL!, Complete(Write) operation failed.", depending on what kind of files I tried to apply, like pit file, AP-File, Home_CSC-File, etc...
Even if i tried to solve it with the most common troubleshoting methods i could find on google, there would be another issue, like a never ending story.
I also tried applying a firmware with recovery mode but there it says: E: "footer is wrong” ,followed by “E: signature verification failed", even if my SD-Card has never been encrypted.
I dont have any idea what to do anymore,
so i would extremely appreciate some help of a pro, who can tell me, what to do exactly.
Thank you!
*EDIT*
I managed to unroot the phone with the verzon nougat firmware but now it won't let me use the phone with a diferent SIM-card than a Verizon's and I'm going to return the phone.
Hi,
I'm facing the exact same problem.
Which Verizon firmware did you use to unroot your phone?
Thanks!
b0rgsen said:
Hi,
I'm facing the exact same problem.
Which Verizon firmware did you use to unroot your phone?
Thanks!
Click to expand...
Click to collapse
I managed to flash the latest Verizon ROM (SM-G930V_1_20170330100826_87cd9631jd_fac). Now it is obviously branded and I always get a message (after reboot/after ending airplane mode, so everytime the phone connects to a cellular network) that I'm using a non-verizon sim card. Nevertheless, after manually adding the APN, everything works fine, no SIM lock.
Edit: it works even better with this stock ROM w/o branding: updato.com/firmware-archive-select-model?record=EF06A1ED34EB11E7963AFA163EE8F90B
Same Problem
Its showing 930f in my phone information
but when i go into download mode it shows 930v
cant update my phone it's still stuck in ****ty marshmallow
i would highly appreciate any sort of help.. TIA
b0rgsen said:
I managed to flash the latest Verizon ROM (SM-G930V_1_20170330100826_87cd9631jd_fac). Now it is obviously branded and I always get a message (after reboot/after ending airplane mode, so everytime the phone connects to a cellular network) that I'm using a non-verizon sim card. Nevertheless, after manually adding the APN, everything works fine, no SIM lock.
Edit: it works even better with this stock ROM w/o branding: updato.com/firmware-archive-select-model?record=EF06A1ED34EB11E7963AFA163EE8F90B
Click to expand...
Click to collapse
yes I get that error too, and I added the APN. it started to work but sooner or later the network drops.
---------- Post added at 09:12 PM ---------- Previous post was at 09:10 PM ----------
androidarif said:
Its showing 930f in my phone information
but when i go into download mode it shows 930v
cant update my phone it's still stuck in ****ty marshmallow
i would highly appreciate any sort of help.. TIA
Click to expand...
Click to collapse
you have the exact same issue as me. I suggest you review this thread, it would be helpful.
In summation, you have a converted phone. you can flash Verizon's rom if you want nougat. But that didn't help with my network issues.
Same problem
is this phone is not official what's the matter please explain
I'm also having the OP's exact same problem? I thought the phone I had just bought off gumtree was fake. I'm in Australia and noted that the model one the sticker on the back on my device is SM-G930F, the "about" page lists it as SM-G930F running 6.0.1, odin lists the as model SM-G930V, smart switch as PIA(VZW), CPU-Z as having it having a Snapdragon processor and finally the paper instruction manual is for a SM-9300 (China) - WTH!?
I cant seem to figure out which device it was or is ha! I believe it may be a chinese device that has been flashed to american standard. Is the the core point here, are these perhaps all flashed/refurbed chinese models?
Long story short, i'm not having any problems but i want a newer OS like oreo or nougat - if I flash to say SM-G930U standard with XAA (generic, samsung branding), will i begin having network issues in Australia?
Hi all.
This is my first post and will try and make it really quick.
I recently got a Galaxy Note 5 (because their just amazing) It came with Android 6.0.1 installed and the "Software Update" section of the settings menu does nothing. I mean literally nothing. I tap "About Device" then "Software Update" and nothing happens no new screen loads or anything.
so I was looking for the OEM ROM's and this is where I ran into so much confusion. The current details the phone gives me is.
Galaxy Note 5 SM-N920F (There are no F rom's)
Build Number MMB29K.N920FTMB4DPH2
Bootloader N920TUVS6ERH1
Which lead me to believe even though their is no "F" variant, That its a T-Mobile model (No Rom's really give 100% functionality to these except the standard 7.1 from T-Mobile)
So I went to Sammobile.com to download the latest official firmware released, But the the CSC numbers don't match my device. they are all starting N920TT***** and mine starts N920FT*****. However the PDA numbers match my bootloader. So will any Note 5 T-Mobile ROM work even if the CSC numbers are different? as long as the PDA numbers are the same?
I get more confusing info from Samsung as well. The "Samsung Members" app shows my Model number as : SM-N920TZKATMB (Which again has no "F" in it, The sticker on the back of the device with the IMEI even states it as SM-N920F)
Am I making this weirdly complicated for myself? Will the US T-Mobile ROM's for android 7.1 work find I flash them with this device? (I live in the UK and the device has 100% compatibility with my network)
Also will flashing the stock 7.1 US ROM from T-Mobile re-lock the SIM ? I'm pretty sure it doesn't/Cant relock SIM to T-Mobile only, But nothings better than a professional confirming.
There is also another issue. according to "Root Checker" I have a Rooted device. But their is no Super User apps on it at all (Cant seem to even find Binaries for SuperSU when using Root File Manager), Pokémon GO fails to load which I have read could be because of the "Root Check" throwing up a positive. But no other apps fail to work at all. their all perfect even banking never even so much as an error. it is just Pokémon GO. Or has someone previously messed up rooting so it looks like it is but the files are missing and isn't really? I tried using Magisk Manager but it did nothing and I don't get any prompts for Root access when installing apps.
So Please Help Me! Thank You.
I bought a s9+ from swappa around February. I bought my mom one from the same supplier a week ago. At first I was concerned that her's had ATT logo until I realized it would change once a tmobile sim was put in. Her's is now SW ver Tmb/Tmb/Tmb. Then I noticed she is at Android 10.0 UI ver 2.0. I am stuck at Android 9 UI ver 1.0
So It seems I was worried about the wrong phone. It is MY phone that can't get updates. My baseband is:
G965USQU7CSK6 which I believe is an ATT baseband. my SW ver is Tmb/Tmb/Att
I tried connecting to smart switch and it says I am up to date. I tried putting in an at&t sim card (that no longer is in service) and smart switch doesn't complain about anything but it still says it is up to date. Doing OTA while using At&t sim card also says I am up to date. I am CLEARLY not up to date. My last update says Nov.1, 2019.
I have used Odin before...mostly for rooting phone. I haven't rooted since the s5 ( where I could take the battery out ). Little paranoid to use Odin considering I can't take the battery out, but with good instructions I will proceed.
Any help on how to update and especially update on tmobile network would be extremely appreciated.
btw I'm in the US and my model is SM-G965U
-Craig
--UPDATE
I have researched a bit and found that it IS possible to change the firmware over to Tmobile using a patched version of Odin.
I downloaded from
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
the 3.13.3_3B_PatcheD.zip
I downloaded G965USQS7CSK3_G965UOYN7CSK3_TMB.zip
from sammobile, which is for Android 9
I would love to be able to use HOME_CSC but that may not work. I could really use some hand holding going through this process.
Is this the correct firmware? Should I be using Android 10 firmware if that is ultimately what I want? HOME_CSC or no? I notice they have the 10 version:
PDA G965USQS7DTB1
CSC G965UOYN7DTB1
as well, which is Android 10 for Tmobile. Also, knox ? will this trip the knox counter thing-a-ma-jig?
Thanks
SOLVED
cw9002 said:
I bought a s9+ from swappa around February. I bought my mom one from the same supplier a week ago. At first I was concerned that her's had ATT logo until I realized it would change once a tmobile sim was put in. Her's is now SW ver Tmb/Tmb/Tmb. Then I noticed she is at Android 10.0 UI ver 2.0. I am stuck at Android 9 UI ver 1.0
So It seems I was worried about the wrong phone. It is MY phone that can't get updates. My baseband is:
G965USQU7CSK6 which I believe is an ATT baseband. my SW ver is Tmb/Tmb/Att
I tried connecting to smart switch and it says I am up to date. I tried putting in an at&t sim card (that no longer is in service) and smart switch doesn't complain about anything but it still says it is up to date. Doing OTA while using At&t sim card also says I am up to date. I am CLEARLY not up to date. My last update says Nov.1, 2019.
I have used Odin before...mostly for rooting phone. I haven't rooted since the s5 ( where I could take the battery out ). Little paranoid to use Odin considering I can't take the battery out, but with good instructions I will proceed.
Any help on how to update and especially update on tmobile network would be extremely appreciated.
btw I'm in the US and my model is SM-G965U
-Craig
--UPDATE
I have researched a bit and found that it IS possible to change the firmware over to Tmobile using a patched version of Odin.
I downloaded from
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
the 3.13.3_3B_PatcheD.zip
I downloaded G965USQS7CSK3_G965UOYN7CSK3_TMB.zip
from sammobile, which is for Android 9
I would love to be able to use HOME_CSC but that may not work. I could really use some hand holding going through this process.
Is this the correct firmware? Should I be using Android 10 firmware if that is ultimately what I want? HOME_CSC or no? I notice they have the 10 version:
PDA G965USQS7DTB1
CSC G965UOYN7DTB1
as well, which is Android 10 for Tmobile. Also, knox ? will this trip the knox counter thing-a-ma-jig?
Thanks
Click to expand...
Click to collapse
ok, so I bit the bullet and decided to go ahead. I used
odin 3.14.1_3B_PatcheD.zip just to be sure
I made sure my phone was unlocked: yes it changes carriers if I put in different sim. When in Tmobile sim Settings->Connections->Mobile Networks->Network operators , yes it has a search networks button and it eventually comes up with other carriers so....safe to say I had unlocked phone ( but not samsung unlocked ie. SM-G965U not SM-G965U1)
I used the latest android 9 firmware. and I used HOME_CSC ( even though I did a backup with smart switch b4) Everything went smoothly, and I still have my apps and now I can get an ota security patch for it. Will write back once I am up to Android 10. oh, btw I am still at SW ver Tmb/Tmb/Att , but I've got ota updates so I don't care
cw9002 said:
ok, so I bit the bullet and decided to go ahead. I used
odin 3.14.1_3B_PatcheD.zip just to be sure
I made sure my phone was unlocked: yes it changes carriers if I put in different sim. When in Tmobile sim Settings->Connections->Mobile Networks->Network operators , yes it has a search networks button and it eventually comes up with other carriers so....safe to say I had unlocked phone ( but not samsung unlocked ie. SM-G965U not SM-G965U1)
I used the latest android 9 firmware. and I used HOME_CSC ( even though I did a backup with smart switch b4) Everything went smoothly, and I still have my apps and now I can get an ota security patch for it. Will write back once I am up to Android 10. oh, btw I am still at SW ver Tmb/Tmb/Att , but I've got ota updates so I don't care
Click to expand...
Click to collapse
I am now at the same baseband version as my mom. Everything worked perfectly. I suggest you go with the least change possible to get to the point that you are able to do OTA updates. For me this was going to the latest Android 9 that they had at sammobile since I was on Android 9 and going with the Tmobile version. I hear the carrier doesn't even matter these days, but I decided I wanted to make sure it was Tmobile compatible so I chose the Tmobile version from sammobile. Happy trails to you in your endeavors. Hopefully you can learn something from mine.
Hey, I really want to thank you for this! I had the same issue and was exploring similar solutions. After several days of researching alternate plans, I was about to give it up as too risky until I found your post - by googling for hints: "SW ver. TMB/TMB/ATT"! You helped me take the dive, and I'm now happily past having a second-hand S9 (sm-g960u) that wouldn't do an OTA update. After a flawless flash, my first OTA request got me to Android 10, (UI 2). now I have a follow-up update scheduled for the wee hours. (And, yes, I'm still at "TMB/TMB/ATT".)
Perhaps like you, I started by investigating the possibility of flashing the UNLOCKED ("U1") firmware. After learning it was possible with the _patchedD Odin, it still scared me enough that I decided on a more conservative approach and followed your exact advice. I especially appreciated your plan to flash NOT the latest update, but the last Android 9 TMB update. That turned out to correspond to the ATT version on my phone, making TMobile either unable or unwilling to offer an OTA update.
History: This is my third used S9. While all were sold as UNLOCKED, only the first had the "U1" model suffix (SM-g960u1). When the second one booted up as a TMobile phone, I felt tricked - but also lucky that I got the right carrier. That's when I learned about the difference in model numbers. As you noted the U1 firmware is factory unlocked - attached to no carrier. When my third phone booted up with a Verizon greeting I figured I could be facing trouble - even though it accepted my TMB sim card.
The seller explained to me that my phone was part of a batch of ATT phones, all "SIM unlocked" using a Verizon sim card. I think sellers of phones with claims to be unlocked should be required to specify whether FACTORY or SIM unlocked.
Hope this great contribution of yours will continue to help others.