[ODIN] Official stock firmware / U firmware [SM-G935V]

[junear]

need little HELP!! i am using unlocked version of this phone india ,asia.
Want to flash asian radio(modem-network) on my phone.
any guide will be helpfull.

Are you facing any issue with using this phone in India? There should be a Global mode in the connection setting.

All India S7 Edges are Exynos variant, I think there is only one Snapdragon variant for HK.

Sent from my SM-G935V using Tapatalk

 

[bunnycool]

Are you facing any issue with using this phone in India? There should be a Global mode in the connection setting.

All India S7 Edges are Exynos variant, I think there is only one Snapdragon variant for HK.

Sent from my SM-G935V using Tapatalk

i have a verizon phone,unlocked. it has snapdragon

 

[coldengrey]

Hello-
I'm trying to file a warranty claim, for my Verizon US SM-G935V Galaxy S7Edge.
Simply need to remove/repair 'custom binary' status (Knox/Root is still UNTRIPPED and must not be tripped/flagged)...
To merely flash firmware back to original factory state, is the installation of ADB and Fastboot both absolutely required for Odin to work?
Or are the ADB/Fastboot for more advanced security circumvention/rooting, ect, therefore not required for me????

Thanks

 

[zimgir124]

Hello-
I'm trying to file a warranty claim, for my Verizon US SM-G935V Galaxy S7Edge.
Simply need to remove/repair 'custom binary' status (Knox/Root is still UNTRIPPED and must not be tripped/flagged)...
To merely flash firmware back to original factory state, is the installation of ADB and Fastboot both absolutely required for Odin to work?
Or are the ADB/Fastboot for more advanced security circumvention/rooting, ect, therefore not required for me????

Thanks

They are not required for odin to work.
However you can use Smart Switch to restore your phone if you dont want to use ODIN.

 

[coldengrey]

They are not required for odin to work.
However you can use Smart Switch to restore your phone if you dont want to use ODIN.

First and foremost, Thank You, @zimgir124 for your time and effort!!!
You ma-ma-ma make meee haaapieee (sorry, just watched Happy Jack in Tropic Thunder )

I tried using SmartSwitch and once in the ?recovery section, it requested Model# - I entered my SM-G935V (Verizon US) hit search (so far so good....);
then prompted for serial # - upon entering my serial number, it said something to the effect of SmartSwitch isn't compatible with my specific model, I was surprised, to say the least....
Now, I used the PC smartswitch software on my Windows 10 machine.... for recovering and reflashing stock firmware, I shouldn't be doing with the preinstalled, on Galaxy smartswitch android app, right? Correct when I tried using PC software and connecting via usb, in download mode, right???
Maybe something to do with the Verizon US variant having a locked bootloader (other than than, have zero clue why it said my specific device couldnt be used)???? Anyone offer any insight or suggestions as to why Samsung SmartSwitch reported incompatible with my SM-G935V (full model #SM-G935VZSAVZW) after entering serial#?

Thanks again....

 

[zimgir124]

First and foremost, Thank You, @zimgir124 for your time and effort!!!
You ma-ma-ma make meee haaapieee (sorry, just watched Happy Jack in Tropic Thunder )

I tried using SmartSwitch and once in the ?recovery section, it requested Model# - I entered my SM-G935V (Verizon US) hit search (so far so good....);
then prompted for serial # - upon entering my serial number, it said something to the effect of SmartSwitch isn't compatible with my specific model, I was surprised, to say the least....
Now, I used the PC smartswitch software on my Windows 10 machine.... for recovering and reflashing stock firmware, I shouldn't be doing with the preinstalled, on Galaxy smartswitch android app, right? Correct when I tried using PC software and connecting via usb, in download mode, right???
Maybe something to do with the Verizon US variant having a locked bootloader (other than than, have zero clue why it said my specific device couldnt be used)???? Anyone offer any insight or suggestions as to why Samsung SmartSwitch reported incompatible with my SM-G935V (full model #SM-G935VZSAVZW) after entering serial#?

Thanks again....

Try not booting into download or recovery.
On smartswitch click more in the top right then click Emergency software recovery and initialization then Software Update and initialization and follow on screen instructions.

Edited because I forgot to type everything out

 

[coldengrey]

Try not booting into download or recovery.
On smartswitch click more in the top right then click Emergency software recovery and initialization then Software Update and

Don't even have device connected and upon entering device model (SM-G935V) and then serial#,
dialog box appears saying "SM-G935V does not support initialization. Please contact support".....

Can anyone confirm that they, have in fact, successfully used smart switch for SM-G935V Emergency Initialization?

 

[zimgir124]

Don't even have device connected and upon entering device model (SM-G935V) and then serial#,
dialog box appears saying "SM-G935V does not support initialization. Please contact support".....

Can anyone confirm that they, have in fact, successfully used smart switch for SM-G935V Emergency Initialization?

You need to use ODIN then

 

[coldengrey]

You need to use ODIN then

Yeah, I'd kinda been prepared from the start to use Odin. I cannot risk tripping Knox cause my deivice is literally a bomb waiting to explode, about once every few days, it will lock up while charging, gets so hot literally must use a glove or towel to pick up.... Take off charger (official OEM) and temps continue to climb until battery dissipates 100%... Completely impervious to ANY user inputs (not even power/home/volume)- cannot even power off!
So, obviously I must get mfr warranty claim going. They denied first time due to 'custom binary' - which Verizon Level 3 tech spent 4 hours investigating, finally confirmed that, just as I'd swore to God I never Rooted or attempted any mods which would be in line with the intended nature of warranty stipulation that any security circumvention or unofficial mods will void warranty.... Verizon agreed that, being that knox/root status untripped, with the Verizon locked bootloader - I, did NOT root/mod (or even accidentally) device at all. Likely 'custom binary' status due to failed sudden interrupted update and, later, factory restore process, simply corrupted Operating System. My particular unit has overheated since I got it, launch week 2016 - has been a nightmare ever since.

So, Thanks, again, @zimgir124 .... Hopefully I will get device back to 'official status' and send it (and its melted image sensor and soldier traces) back for a warranty replacement.

 

[zimgir124]

Yeah, I'd kinda been prepared from the start to use Odin. I cannot risk tripping Knox cause my deivice is literally a bomb waiting to explode, about once every few days, it will lock up while charging, gets so hot literally must use a glove or towel to pick up.... Take off charger (official OEM) and temps continue to climb until battery dissipates 100%... Completely impervious to ANY user inputs (not even power/home/volume)- cannot even power off!
So, obviously I must get mfr warranty claim going. They denied first time due to 'custom binary' - which Verizon Level 3 tech spent 4 hours investigating, finally confirmed that, just as I'd swore to God I never Rooted or attempted any mods which would be in line with the intended nature of warranty stipulation that any security circumvention or unofficial mods will void warranty.... Verizon agreed that, being that knox/root status untripped, with the Verizon locked bootloader - I, did NOT root/mod (or even accidentally) device at all. Likely 'custom binary' status due to failed sudden interrupted update and, later, factory restore process, simply corrupted Operating System. My particular unit has overheated since I got it, launch week 2016 - has been a nightmare ever since.

So, Thanks, again, @zimgir124 .... Hopefully I will get device back to 'official status' and send it (and its melted image sensor and soldier traces) back for a warranty replacement.

ODIN will not trip KNOX as it installs official firmware so rest assured that you'll be fine.
I've gotta ask though, why did you wait so long to send your phone in if it's been having those issues?

 

[DMon04]

This is wrong,the LATEST 7.0 FW is QA4 from Verizon,NOT QA2. I took the OTA update today (Saturday 3/25/17) from Verizon to Android 7.0 QA4. QA2 i believe was a beta or testing FW. Ive been having problems since rooting QA4 and flashed back to QA2 in Odin. I had root installed and everythig running good. Then flashed the fix and debloat.zip in flashfire and my phone went batty. Ill try to include my screenshots from earlier today.

Sent from my SM-G935V using Tapatalk

 

[rene130313]

Good morning, some one can share the new update from Verizon I live in Mexico and not receiving the OTA, thanks in advance.... (I am referring to the update receive in 03/25/17)

 

[DMon04]

Good morning, some one can share the new update from Verizon I live in Mexico and not receiving the OTA, thanks in advance.... (I am referring to the update receive in 03/25/17)

Ive been looking for the QA4 files online again but havent found anything yet. The XDA app is not letting me upload my screenshot to show proof i was on QA4

 

[ChadH42]

I just took the OTA from QA2 to QA4 but there is no documentation as to what has changed since QA2.

 

[maliibu31]

Yeah, I'd kinda been prepared from the start to use Odin. I cannot risk tripping Knox cause my deivice is literally a bomb waiting to explode, about once every few days, it will lock up while charging, gets so hot literally must use a glove or towel to pick up.... Take off charger (official OEM) and temps continue to climb until battery dissipates 100%... Completely impervious to ANY user inputs (not even power/home/volume)- cannot even power off!
So, obviously I must get mfr warranty claim going. They denied first time due to 'custom binary' - which Verizon Level 3 tech spent 4 hours investigating, finally confirmed that, just as I'd swore to God I never Rooted or attempted any mods which would be in line with the intended nature of warranty stipulation that any security circumvention or unofficial mods will void warranty.... Verizon agreed that, being that knox/root status untripped, with the Verizon locked bootloader - I, did NOT root/mod (or even accidentally) device at all. Likely 'custom binary' status due to failed sudden interrupted update and, later, factory restore process, simply corrupted Operating System. My particular unit has overheated since I got it, launch week 2016 - has been a nightmare ever since.

So, Thanks, again, @zimgir124 .... Hopefully I will get device back to 'official status' and send it (and its melted image sensor and soldier traces) back for a warranty replacement.

Verizon has a Samsung Recovery utility for the computer, give that a shot. It got me out of root and restored stock FW.

Sent from my SM-G935V using Tapatalk

 

[zimgir124]

This is wrong,the LATEST 7.0 FW is QA4 from Verizon,NOT QA2. I took the OTA update today (Saturday 3/25/17) from Verizon to Android 7.0 QA4. QA2 i believe was a beta or testing FW. Ive been having problems since rooting QA4 and flashed back to QA2 in Odin. I had root installed and everythig running good. Then flashed the fix and debloat.zip in flashfire and my phone went batty. Ill try to include my screenshots from earlier today.

QA2 was the first official nougat release by Verizon, not a beta.

As for QA4 I know that's the current newest version but as of typing this the files have not been posted online for use.

 

[zimgir124]

I just took the OTA from QA2 to QA4 but there is no documentation as to what has changed since QA2.

As far as I know it was only WiFi fixes.

 

[zimgir124]

QA4 files have not been posted so I am currently unable to update the thread as of now.
When they become available I will update the thread.

 

[DMon04]

QA4 files have not been posted so I am currently unable to update the thread as of now.
When they become available I will update the thread.

Yeah i get that. I just odin'd back to QA2 and now my phone wont take the ota update to QA4. Any ideas? Im stock unrooted right now and it wont uodate the phone. Coukd there be root stuff left over? Ive removed all the root apps. Is anybody able to extract the QA4 update files from their phone?

 

[zimgir124]

Yeah i get that. I just odin'd back to QA2 and now my phone wont take the ota update to QA4. Any ideas? Im stock unrooted right now and it wont uodate the phone. Coukd there be root stuff left over? Ive removed all the root apps. Is anybody able to extract the QA4 update files from their phone?

Did you use the Home CSC or the regular CSC file?