Hey all. I am in the US but bought international S7Edge when it came out. I dont know what firmware it had I think it was some italian one maybe. Then i rooted and started using custom roms. Then when nougat officially came out for S7Edge i un-rooted and went back to 100% stock using i think Vodafone 7.0 firmware. I think because i rooted i have a negative test response from Knox which i think stops me from getting OTA updates. It shows in software info that my OS version has security patch only from January 2017 so I am clearly not on latest firmware even though OTA says I am on latest.
Is there a site with a database of all firmwares out for the S7Edge international variant So i can find the latest and flash it to my phone since OTA wont get the latest.
samsmobile has the latest.
Yoiu still have an issue with your kernal as phone still thinks you have custom rom. Tripped knox on stock firmware will not stop OTA from downloading.
Anyway ? I get errors.
probably not, you will need to wait until Samsung updates the U firmware bootloader to version 5 as currently the sprint s7 is the only one with a version 5 bootloader.
hello,
so i've been doing some readings and i know the hardware isn't the same so i know technically its impossible
but!
but what i also know is that i bought this second hand galaxy s7 that had android 6.0 using g930f rom, i tried to upgrade it to 7.0 automatically but it didn't detect and update. so i decided to flash a 7.0 rom manually. to my surprise in the download mode it said it was a 930p model and now i am stuck with a sprint version with no hotspot or lte.
so as i don't know if it was a custom rom or something but it used to have a g930f rom in it
What firmware did you flash? You may be able to put the u firmware on that may solve your problem
tried going to the U version but the binary thing is still behind the P version so i need to wait for the U to be updated (or thats what i read)
but that is not my concern here, i want to know how i had an F version while its technically impossible,
mm.salem said:
tried going to the U version but the binary thing is still behind the P version so i need to wait for the U to be updated (or thats what i read)
but that is not my concern here, i want to know how i had an F version while its technically impossible,
Click to expand...
Click to collapse
it can be flashed with flashfire method
So I have what was originally a VZW 955U, flashed soon after I got it, to the unlocked 955U1 firmware using Prince's Odin and have been happy so far. Now with all the Oreo updates released except for the unlocked one, I'm wondering if I can just use prince's odin again to load the latest TMB Oreo firmware or need to do the whole engboot thing first? My current software is latest Nougat build for 955U1 and shows up as TMB//VZW.
Any thoughts?
No one? I remember reading on some of the earlier threads that if you flashed U1 first, you could then flash to the other carriers versions without the other steps but want to confirm. Don't want to deal with bootloops or softbricks.
I think you need the eng file ..but there is not oreo eng file..
Tried a lot of things, flashing tmobile oreo directly using modified and unmodified odin, trying to flash the latest Nougat builds from Tmobile using Prince Odin (the Dec one almost took and showed up as TMB/TMB/VZW but ultimately would not get updates) and then flashing back to the unlocked version but nothing worked, will likely have to do a full erase and reload the unlocked version. The eng boot file no longer works far as I can tell. Will just have to wait for the unlocked version to get updated. Sucks as this is a corporate phone and my firm has been pushing to get Oreo on all devices.
If someone has a recent guide on carrier switching the S8 , would appreciate it. Most guides here are from May of 2017 and I'm betting those files are too old to be compatible if you're on the latest Dec build for 950U1/955U1. At least doing a full reset and reflash of the 955U1 brought Wifi Calling which wasn't quite working right since I had just flashed over the 955U1 software over the stock verizon last year.
I think I'll just wait a few more weeks for the 955U1 Oreo to drop. Has to happen eventually right? Lol.
I'm trying to wrap my head around all this, but my head is spinning. In December I was looking to get my S7 flat to 7.0 rooted. I discovered that root can only be achieved with eng kernel and that has its drawbacks. I decided I don't need/want root at that cost of stability, performance and battery life. Somehow I settled on installing a "U" variant that seemed to work well with less Verizon bloat. I couldn't get the S Health app and monitors on the back of the phone working, but I figured I could live with that. Recently I tried casting my phone to a Amazon Fire Stick and discovered the "Smart View" button is missing and I couldn't figure out how to get it back, so I might've lost that too. I also discovered in the past nine months Oreo is out with additional features and I figure if I'm going to go through the hassle of reinstalling, I might as well upgrade.
So, I hear root with Oreo is better than it's been, but not perfect, so I'l like to upgrade to unrooted oreo, either stock or debloated (if such a version exists without tradeoffs). Is there a certain version I'm supposed to go to so there's some flexibility in reinstalling the OS? Like I know sometimes versions of software are released that upgrade little, but patch exploits.
Also, if I do get whatever version of Oreo installed, do I then ignore OTA updates going forward? Is there any advantage to that?
And I can use the mobile hotspot feature. I don't think I have any special plan to accommodate that, nor do I have an unlimited plan (with Verizon). Is that intended, or is that from the "U" variant. Would I lose that?
My phone's info is below, if anyone can decipher what I did:
Model #: SM-G930U
Android Version: 7.0
Baseband Version: G930UUEU4BQE2
Kernel Version: 3.18.31
Build #: NRD90M.G930UUEU4BQE2
I apologize, I know my nomenclature isn't up to snuff. I realize that this stuff isn't for the casual user, at least on this phone. It's very hard to figure out what's current if you're not in the loop.
Thank you for any help you can offer.
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
djh816 said:
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
Click to expand...
Click to collapse
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Umbra. said:
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Click to expand...
Click to collapse
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
djh816 said:
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
Click to expand...
Click to collapse
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Umbra. said:
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Click to expand...
Click to collapse
Woo, welcome back to the walled garden lol.. BTW I found in the themes/lockscreen app (can't recall where) they had the old lockscreen font I preferred as a clock option