Database Users

Help changing from custom rom to legit update (Samsung S5)

Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?

DarkVamprism said:
Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?
Click to expand...
Click to collapse
just look for stock lollipop rom for your phone ( sammobile)/and flash with odin, just make sure to do a full wipe before flashing the stock rom

Thanks for the quick reply, will this allow me to get future updates? like hotfixes released and stuff? I saw somewhere that once you flash it does something to the kernal which makes updates possibly brick the phone.

Just factory reset the custom, then use ODIN to flash the Stock ROM
Flashing the stock ROM will allow OTA updates so long as you don't root or flash anything else custom like recovery - it needs to stay 100% stock for OTA
But you can still root, and each time an OTA arrives, grab the new ROM from sammobile dot com and use ODIN to flash it, that will update your phone, leaving everything in tact, all your data and images etc will be fine, only thing you'll need to do after updating is root the phone again

Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.

DarkVamprism said:
Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.
Click to expand...
Click to collapse
Try a UK firmware, the latest version BOE5 is in my sig link on MEGA, much faster than Sammobile
There is also samsung-updates dot com you can check out

Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.

DarkVamprism said:
Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.
Click to expand...
Click to collapse
Are you sure you had the phone in Download Mode?
Volume DOWN & HOME & POWER (Then volume up when asked)
And yes, disable Reactivation lock before flashing anything or you'll end up with major problems requiring a massive mess on to fix
Using ODIN 3.10.6 ?

think you need pitfiles with the rom

Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.

ad0dh67 said:
think you need pitfiles with the rom
Click to expand...
Click to collapse
Yea I was wondering the same
Try this OP
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Load it into the PIT section along with the ROM in the AP section together and try again
---------- Post added at 19:14 ---------- Previous post was at 19:12 ----------
DarkVamprism said:
Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.
Click to expand...
Click to collapse
Here's the latest ODIN
https://mega.co.nz/#!Exo3yADS!y7pFS5-9RVhp4vDxTRAQARAwkjyQAB_9mDZWfXkLqko

There is no pit section inside of Odin 3.10?
Edit: Nevermind I found it but it says not to use it unless im an engineer, how badly will this screw me up =\ Im kind of scared to.

DarkVamprism said:
There is no pit section inside of Odin 3.10?
Click to expand...
Click to collapse
There is on the lower left log / options / PIT section, although clicking that says to load it into the CSC section
Try using the PIT file with your 3.09 version of ODIN first as Im not sure where 3.10.6 wants the PIT file loaded into, it's not very clear

Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?

DarkVamprism said:
Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?
Click to expand...
Click to collapse
Put it in the PIT section
I'm just reading up on what 3.10.6 means with that engineer warning
Make sure you load the stock ROM into AP together with the PIT file in the PIT section before flashing

I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09

DarkVamprism said:
I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09
Click to expand...
Click to collapse
Are you running ODIN as Admin? (Right click > Run as Administrator)
Using a native PC running Windows? All Samsung drivers installed?
It almost sounds as if your bootloader is locked, but you managed to flash custom recovery and root right?

Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?

DarkVamprism said:
Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?
Click to expand...
Click to collapse
Looks like you need to grab the G900I ROM and PIT
I'd try with just the ROM first, hopefully ODIN saved you from bricking when it realised it was for the wrong model phone
Get the G900I ROM, stick it into ODIN like you originally tried, see how you go from there
EDIT - Now it makes sense why there was no Australian ROM for your G900F, there is for the G900I

Okay, good news is sam mobile had the correct firmware now that im using the correct model number(doh) and the phone still boots fine, will update when I have downloaded and tried it, thanks for sticking with me.

Can't flash stock ROM through ODIN for my Note 3 N9005

Hi. I'm having some trouble when I tried to flash my Note 3 with CM13 but it seems like can't associate with gapps because it will crash. My note 3 is currently on CM13 but without any gapps. I decided to flash it back to original stock rom but ODIN fail.
it says:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In the download mode, it says:
SECURE CHECK FAIL : aboot
I don't know what to right now. Help me. TQ

Download another copy .

JJEgan said:
Download another copy .
Click to expand...
Click to collapse
Another copy of STOCK ROM?

Yes and odin
Sent from my GT-N8013 using XDA-Developers mobile app

Odin is failing when trying to flash the bootloader (aboot.mbn) so either the rom isn't for the phone or the bootloader is too old.

audit13 said:
Odin is failing when trying to flash the bootloader (aboot.mbn) so either the rom isn't for the phone or the bootloader is too old.
Click to expand...
Click to collapse
Already try another copy of Stock ROM. But it keeps failing. So how to solve the out of dated bootloader?

Arobase40 said:
This happened to me after using CM ROMs on my old GN1 : hard to recover to stock...
This also happened with my GN3 with stock dutch firmware. Don't know the reasons... ^^
Try to flash a N9005XXUGN1 or N9005XXUEND3 kk firmwares (not dutch) to downgrade first to KK, then you could try upgrading to any other Lollipop firmwares...
Seems to me it's impossible to change or upgrading from Lollipop to another Lollipop. I always had to downgrade first to KK before upgrading to Lollipop so if you used CM13 it should be a bigger problem...
PS : BTW watch at your CM13 settings if a OEM unlock option is activated or de-activated...
Click to expand...
Click to collapse
Will try to download the KK ROM since the file is too big. But then where to find the OEM unlock option?

Isn't the oem unlock option available on the nexus 5x and 6p?

Try take out your battery 1st, then use 3 button combination to go to download mode.
Also try another usb cable as well..

I have never seen the oem unlock option on a cm rom. Doesn't the oem unlock relate to the bootloader? The n9005 has never had a locked bootloader.

With a locked bootloader, cwm, twrp, and ROMs not based on a Samsung kernel could never be flashed to the phone.
The inability to cross flash firmware is due to security checks built into the bootloader to ensure that the ROMs being flashed via Odin is made for the particular phone and not because it is locked. Think of it more as a safety feature.
In some of the Samsung phones, older firmware can't be flashed as the bootloader on the phone cannot be downgraded.

Arobase40 said:
This happened to me after using CM ROMs on my old GN1 : hard to recover to stock...
This also happened with my GN3 with stock dutch firmware. Don't know the reasons... ^^
Try to flash a N9005XXUGN1 or N9005XXUEND3 kk firmwares (not dutch) to downgrade first to KK, then you could try upgrading to any other Lollipop firmwares...
Seems to me it's impossible to change or upgrading from Lollipop to another Lollipop. I always had to downgrade first to KK before upgrading to Lollipop so if you used CM13 it should be a bigger problem...
PS : BTW watch at your CM13 settings if a OEM unlock option is activated or de-activated...
Click to expand...
Click to collapse
Finally managed to restore to its original stock rom after downloading Sprint Lollipop version. I dont know why it must be a Sprint. Anybody know how to unlock the carrier ? I live in Malaysia tho

aruruuuu said:
Finally managed to restore to its original stock rom after downloading Sprint Lollipop version. I dont know why it must be a Sprint. Anybody know how to unlock the carrier ? I live in Malaysia tho
Click to expand...
Click to collapse
Try the Sprint forum .

What is the exact model # of the phone shown in download mode? Was the phone new or used when you got it?

Arobase40 said:
Did you buy your GN3 to Sprint ? lol
Click to expand...
Click to collapse
It is an import version. It is unlocked when I first buy it. And now it relocked after I flash back to Stock ROM

Re-partition operation failed Samsung Galaxy J5 (SM-J500FN)

HI, when I try to install new firmware on my galaxy j5 with odin with pda and file pit for repartition, I got this errors:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010>
<ID:0/010>Re-Partition operazioni failed.
<OSM>All threads completed. (succeed 0 / fail 1)
Please, help me.

Seconded. Does anyone have a solution for this issue?

@Vincenzolt98 @Dionisis89
It's a custom PIT or stock one? From where you downloaded stock ROM?
When I flashed stock ROM I only had to put it at PDA ( AP for newer Odin versions). I think the repartition should be done automatically when is flashed stock ROM.
Try latest Odin version and also make sure that the PIT file is the correct one (can be for 8gb, 16gb for example).
I recommend you to use SamFirm program for downloading stock ROMs faster.
SamFirm: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 . Even if it's deprecated, it still works fine. The program is attached at attachments in that thread.

#Henkate said:
@Vincenzolt98 @Dionisis89
It's a custom PIT or stock one? From where you downloaded stock ROM?
When I flashed stock ROM I only had to put it at PDA ( AP for newer Odin versions). I think the repartition should be done automatically when is flashed stock ROM.
Try latest Odin version and also make sure that the PIT file is the correct one (can be for 8gb, 16gb for example).
I recommend you to use SamFirm program for downloading stock ROMs faster.
SamFirm: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 . Even if it's deprecated, it still works fine. The program is attached at attachments in that thread.
Click to expand...
Click to collapse
It should be the stock PIT. I don't remember where I downloaded it from but it appears to be the correct one. I don't know where the problem is.
The firmware corresponding to my J500FN's CSC is Austrian (ATO), so I downloaded it from that updato site.
The reason I went to find the PIT file in the first place is because flashing stock ROM via Odin failed. It showed this code (last 2 lines):
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
It had failed at this point, and I've tried flashing the 6.0.1 and 5.1.1 stock image, to no avail. Perhaps you have a solution for that instead?

Dionisis89 said:
It should be the stock PIT. I don't remember where I downloaded it from but it appears to be the correct one. I don't know where the problem is.
The firmware corresponding to my J500FN's CSC is Austrian (ATO), so I downloaded it from that updato site.
The reason I went to find the PIT file in the first place is because flashing stock ROM via Odin failed. It showed this code (last 2 lines):
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
It had failed at this point, and I've tried flashing the 6.0.1 and 5.1.1 stock image, to no avail. Perhaps you have a solution for that instead?
Click to expand...
Click to collapse
Regsrding hidden.img.ext4 error, try this: https://www.youtube.com/watch?v=2uTHilnRsWw. Credits to @pacower for sharing that video. Also try to use newer Odin version (I used 3.09 or so all the time though).
People confirmed that this video works, but here is a post/tip regarding that video: http://forum.xda-developers.com/showpost.php?p=69673728&postcount=10 .

#Henkate said:
Regsrding hidden.img.ext4 error, try this: https://www.youtube.com/watch?v=2uTHilnRsWw. Credits to @pacower for sharing that video. Also try to use newer Odin version (I used 3.09 or so all the time though).
People confirmed that this video works, but here is a post/tip regarding that video: http://forum.xda-developers.com/showpost.php?p=69673728&postcount=10 .
Click to expand...
Click to collapse
I've tried this method, but Odin shows me another error: MD5 error! binary is invalid .
And yes, I've tried removing the .md5 from the file name, but then Odin is stuck on file analysis forever. That happens on Odin v3.12. At version 3.11, it simply hangs after choosing that file. At version 3.09 (which also has the option of flashing a PIT file) it shows this:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea of what I could do? Maybe the PIT file I used isn't correct, after all? Where should I download it from?
---------- Post added at 01:43 PM ---------- Previous post was at 01:28 PM ----------
Hey bro, found the issue. Apparently the firmware I downloaded wasn't right and that's why it never went through with booting the hidden.img.ext4. The link you provided, however, made it happen! You saved my phone. Thanks a million!

Dionisis89 said:
I've tried this method, but Odin shows me another error: MD5 error! binary is invalid .
And yes, I've tried removing the .md5 from the file name, but then Odin is stuck on file analysis forever. That happens on Odin v3.12. At version 3.11, it simply hangs after choosing that file. At version 3.09 (which also has the option of flashing a PIT file) it shows this:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea of what I could do? Maybe the PIT file I used isn't correct, after all? Where should I download it from?
---------- Post added at 01:43 PM ---------- Previous post was at 01:28 PM ----------
Hey bro, found the issue. Apparently the firmware I downloaded wasn't right and that's why it never went through with booting the hidden.img.ext4. The link you provided, however, made it happen! You saved my phone. Thanks a million!
Click to expand...
Click to collapse
Did you try to flash it without PIT file?
Also, if you flashed TWRP before, then try to flash TWRP, then boot in TWRP recovery and wipe /system, /data, /cache and dalvik-cache. Then power off the phone, boot in download mode and try to flash again through Odin.
If you didn't flash TWRP before and you don't wanna lose warranty, then boot in stock recovery and wipe, but your internal memory will be wiped too.
I never used a PIT file when I flashed stock ROM.
EDIT:
Dionisis89 said:
Hey bro, found the issue. Apparently the firmware I downloaded wasn't right and that's why it never went through with booting the hidden.img.ext4. The link you provided, however, made it happen! You saved my phone. Thanks a million!
Click to expand...
Click to collapse
Oh. Nice
I'm glad I helped you.

#Henkate said:
Did you try to flash it without PIT file?
Also, if you flashed TWRP before, then try to flash TWRP, then boot in TWRP recovery and wipe /system, /data, /cache and dalvik-cache. Then power off the phone, boot in download mode and try to flash again through Odin.
If you didn't flash TWRP before and you don't wanna lose warranty, then boot in stock recovery and wipe, but your internal memory will be wiped too.
I never used a PIT file when I flashed stock ROM.
EDIT:
Oh. Nice
I'm glad I helped you.
Click to expand...
Click to collapse
I'm sorry I didn't try flashing the firmware you provided me with in the first place, thereby "making you" type more on an answer that has been answered (by my flashing the correct firmware). There is something else you might help me with, if you have the time. Why did you provide me with a link to the German firmware? I told you it had Austrian CSC. And yet the German firmware was the one that actually worked. How so? And something else. Which is the website that you sent that firmware from? You edited your post soon after you had posted the link.

Dionisis89 said:
I'm sorry I didn't try flashing the firmware you provided me with in the first place, thereby "making you" type more on an answer that has been answered (by my flashing the correct firmware). There is something else you might help me with, if you have the time. Why did you provide me with a link to the German firmware? I told you it had Austrian CSC. And yet the German firmware was the one that actually worked. How so? And something else. Which is the website that you sent that firmware from? You edited your post soon after you had posted the link.
Click to expand...
Click to collapse
Huh? I only gave you links with the YouTube video and SamFirm.
Oh wait, I think that maybe SamFirm downloaded latest available update. In SamFirm you can switch to manual mode and type there the region, PDA and CSC and you can download the firmware which you want.

#Henkate said:
Huh? I only gave you links with the YouTube video and SamFirm.
Oh wait, I think that maybe SamFirm downloaded latest available update. In SamFirm you can switch to manual mode and type there the region, PDA and CSC and you can download the firmware which you want.
Click to expand...
Click to collapse
I didn't use SamFirm to download the firmware file, of that I'm sure. Mostly because upon attempting, I failed. I had put SM-J500FN in model name and ATO in CSC, but SamFirm found nothing.
I think you had a link from Mediafire in your response to me and that's how I downloaded the firmware. Hell, I might be mistaken, since I searched through a ton of threads, including some at XDA, in order to find a solution. It's possible I saw the link at another user's post.
In any case, thank you very much, once again. You saved my phone from becoming a paperweight.

Dionisis89 said:
I didn't use SamFirm to download the firmware file, of that I'm sure. Mostly because upon attempting, I failed. I had put SM-J500FN in model name and ATO in CSC, but SamFirm found nothing.
I think you had a link from Mediafire in your response to me and that's how I downloaded the firmware. Hell, I might be mistaken, since I searched through a ton of threads, including some at XDA, in order to find a solution. It's possible I saw the link at another user's post.
In any case, thank you very much, once again. You saved my phone from becoming a paperweight.
Click to expand...
Click to collapse
Is this the link you talk about? http://www.mediafire.com/download/skldahurz12dick/DBT-J500FNXXU1AOI1-20151006173751.zip . If yes, it's the German stock ROM I've uploaded andmentioned it in my ROM thread at installation instructions I posted it only there. It's kinda old firmware, but always worked fine for me, didn't have any issues (it's the firmware which my phone came with).
You welcome! I'm glad I helped you!
Maybe the OP (first post) has same problem like you. He'll have to read

#Henkate said:
Is this the link you talk about? http://www.mediafire.com/download/skldahurz12dick/DBT-J500FNXXU1AOI1-20151006173751.zip . If yes, it's the German stock ROM I've uploaded andmentioned it in my ROM thread at installation instructions I posted it only there. It's kinda old firmware, but always worked fine for me, didn't have any issues (it's the firmware which my phone came with).
You welcome! I'm glad I helped you!
Maybe the OP (first post) has same problem like you. He'll have to read
Click to expand...
Click to collapse
Yes, yes, that's the one!
I doubt he still has the problem though, since the thread was created at the end of August. Nonetheless, other people who might face the same issue will be able to read this thread and extract useful information.

Nand erase all + pit + g935f fw on G935W8

Hello guys I would like to flash the g935f modem over my g935w8 canadian phone. But in order to do things right, I'm thinking about using g935f pit file and use nand erase all in odin in order to clean the whole phone, hoping that the EFS will regenerate correctly and it can transform into an international version with bootloader and modem from G935f.
Ps: I don't live in canada, that's my reason.
Do you think it's possible ?
Somebody knows some technicalities I am not aware of ?
Please help me not blow my new phone !

you will need to reflash the bootloader and modem for G935W8, otherwise some features will not work properly with fingerprints and calling features.

Cosmic Blue said:
you will need to reflash the bootloader and modem for G935W8, otherwise some features will not work properly with fingerprints and calling features.
Click to expand...
Click to collapse
How come ? Care to explain more about the calling feature. ?
Cauz the whole thing is to replace the modem with 935f one

if you are using the phone outside of Canada, you can basically use any modem but you need to experiement to find the one that that works best for your country.
If you are inside of Canada, the 935W8 bootloader and modem are optimized for use by the big 3 in Canada. Which means that you should get the best signal of their servers.

I think that G935F roms work on G935W8 models, see here: http://forum.xda-developers.com/s7-edge/help/samsung-sm-g935f-sm-g935w8-rom-t3414612
I will maybe try on my G935W8

chucky91 said:
I think that G935F roms work on G935W8 models, see here: http://forum.xda-developers.com/s7-edge/help/samsung-sm-g935f-sm-g935w8-rom-t3414612
I will maybe try on my G935W8
Click to expand...
Click to collapse
G935f roms work fine. I am actually using one right now. It's the modem and bootloader the are uncertain. I am afraid my EFS gets corrupted

You lost your imei??

I finally tried, but Secure Download in download mode didn't let me flash anything from g935f. so no possibility to flash g935f stuff via odin beceause of knox !!!

Never touch Nand Erease All. That's the last thing I would ever touch. (The worst case: dead phone or lost IMEI)
You can use any G935F rom since those two models are identical and other users have verified that everything works well.
And now.. why do You want to somehow reprogram Your phone from G935w8 to G935F? It's just the name + when You flash G935F rom, Your build.prop will be changed to G935F. And if You have poor signal (never happened to me while using weird/random modems) then flash a modem from the country that You live in.
Pit file I think doesn't really change the name either, it should just fix partitions.
You could eventually try flashing G935F stock rom from sammobile with a G935F pit file and see if that changes anything, but avoid touching nand erease all.
---------- Post added at 02:54 PM ---------- Previous post was at 02:49 PM ----------
Richard_10 said:
I finally tried, but Secure Download in download mode didn't let me flash anything from g935f. so no possibility to flash g935f stuff via odin beceause of knox !!!
Click to expand...
Click to collapse
Can You post the odin log?

Richard_10 said:
I finally tried, but Secure Download in download mode didn't let me flash anything from g935f. so no possibility to flash g935f stuff via odin beceause of knox !!!
Click to expand...
Click to collapse
Did you enable "unclock OEM" on developper options?
Sent from my Samsung Galaxy S7 Edge using XDA Labs

chucky91 said:
Did you enable "unclock OEM" on developper options?
Click to expand...
Click to collapse
Yes

ProtoDeVNan0 said:
Never touch Nand Erease All. That's the last thing I would ever touch. (The worst case: dead phone or lost IMEI)
You can use any G935F rom since those two models are identical and other users have verified that everything works well.
And now.. why do You want to somehow reprogram Your phone from G935w8 to G935F? It's just the name + when You flash G935F rom, Your build.prop will be changed to G935F. And if You have poor signal (never happened to me while using weird/random modems) then flash a modem from the country that You live in.
Pit file I think doesn't really change the name either, it should just fix partitions.
You could eventually try flashing G935F stock rom from sammobile with a G935F pit file and see if that changes anything, but avoid touching nand erease all.
---------- Post added at 02:54 PM ---------- Previous post was at 02:49 PM ----------
Can You post the odin log?
Click to expand...
Click to collapse
I am only interested in the modem my friend nothing else.
I tried again no way. Beceause modems from other countries are from g935f. Knox detects that and stop the process in odin. And gives me a warning in download mode.
Literraly nothing from g935f can be flashed through odin.
So I am stuck with the canadian modem. No luck. The difference in reception power is big between the 2. My wife has an international s7, so I compare all the time. It's really problematic

It's really weird that You can't flash it. I used to flash many different files through odin(from totally different phones) and it never gave me any error. Can You extract modem.img from the tar file and repack it into a new tar? Secure download error is even weirder. Have You tried flashing a whole G935F stock rom from sammobile? Those include modems too and maybe it would help. For any compatibility issues I would repack the tar file. It helped me many times.
If nothing above works then I have no idea. Sorry.

Richard_10 said:
Yes
Click to expand...
Click to collapse
I will try to flash G935F rom to verify. Do a Factory reset before flashing rom.
Sent from my Samsung Galaxy S7 Edge using XDA Labs

ProtoDeVNan0 said:
It's really weird that You can't flash it. I used to flash many different files through odin(from totally different phones) and it never gave me any error. Can You extract modem.img from the tar file and repack it into a new tar? Secure download error is even weirder. Have You tried flashing a whole G935F stock rom from sammobile? Those include modems too and maybe it would help. For any compatibility issues I would repack the tar file. It helped me many times.
If nothing above works then I have no idea. Sorry.
Click to expand...
Click to collapse
I did try to flash the whole g935f stock rom, same issue.
And I don't know how to extract and repack .tar files. If you would help I will do it, Hopefully with success.

chucky91 said:
I will try to flash G935F rom to verify. Do a Factory reset before flashing rom.
Click to expand...
Click to collapse
Yes I did. I even did Nand erase all. Beceause despite people think it's prohibited. It is not beceause EFS partition regenerate it self. As long as you have the right pit file.
I restored my system everything fine.
Please try and see if you can fined a solution to that issue. Thank you

I did try and it doesn't flash.
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I flashed the french rom (XEF) (1 file). I also flashed the rom with 4 files but it need pit file and secure download must be disabled.

chucky91 said:
I did try and it doesn't flash.
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I flashed the french rom (XEF) (1 file). I also flashed the rom with 4 files but it need pit file and secure download must be disabled.
Click to expand...
Click to collapse
I used pit file from both phones. It doesn't need a pit. It needs secure download disabled

How can I disable secure download? It fail with the lastest version of Odin

chucky91 said:
How can I disable secure download? It fail with the lastest version of Odin
Click to expand...
Click to collapse
That's the million dollars question my friend.

Stuck on AT&T Unreleased beta nougat update from earlier this year

Hi, so i'd like to upgrade my AT&T GS7 G930A to the latest available version of android that's released, as i'm still on the nougat beta update from earlier this year that wasn't officially released(meaning i'm still only at security update's from january 2017), however, none of the odin files i've tried have worked (links will be below) it keeps getting stuck at "Initializing" and on my phone it keeps saying "Odin Protocol version error", so i was hoping you guys would be able to help me
https://forum.xda-developers.com/att-galaxy-s7/how-to/pk1-odin-files-t3522168 (was going to OTA update after downgrading)
https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930aucu4bqd4-5-18-2017-t3608909
and https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-android-n-offical-odin-package-t3567801
the version currently installed on my phone is G930AUCU4BQA4

You need to go completely back to stock in order to get back on nougat latest I suggest that you flash back to the pk1 marshmallow 6.0 and use the odin provided by Sam mobile

logoster said:
Hi, so i'd like to upgrade my AT&T GS7 G930A to the latest available version of android that's released, as i'm still on the nougat beta update from earlier this year that wasn't officially released(meaning i'm still only at security update's from january 2017), however, none of the odin files i've tried have worked (links will be below) it keeps getting stuck at "Initializing" and on my phone it keeps saying "Odin Protocol version error", so i was hoping you guys would be able to help me
https://forum.xda-developers.com/att-galaxy-s7/how-to/pk1-odin-files-t3522168 (was going to OTA update after downgrading)
https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930aucu4bqd4-5-18-2017-t3608909
and https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-android-n-offical-odin-package-t3567801
the version currently installed on my phone is G930AUCU4BQA4
Click to expand...
Click to collapse
Just flash this firmware using Odin3_v3.12_PrinceComsy

muniz_ri said:
Just flash this firmware using Odin3_v3.12_PrinceComsy
Click to expand...
Click to collapse
Nope, now i get
Code:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
tlopez1973 said:
You need to go completely back to stock in order to get back on nougat latest I suggest that you flash back to the pk1 marshmallow 6.0 and use the odin provided by Sam mobile
Click to expand...
Click to collapse
how would i go about finding these files? as you can see by one of the links in my post, i already tried the PK1 firmware from here

From what I learned it always ends up being an Odin problem not going back just try different versions of Odin make sure your restart your phone when putting it in download mode

logoster said:
Nope, now i get
Code:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try just flashing the CSC file with that Odin version. It contains the .pit file to format your partitions. If that works you should then be able to flash all 4 files.

muniz_ri said:
Try just flashing the CSC file with that Odin version. It contains the .pit file to format your partitions. If that works you should then be able to flash all 4 files.
Click to expand...
Click to collapse
nope, same error, <ID:0/004> FAIL! Model dismatch fail

logoster said:
nope, same error, <ID:0/004> FAIL! Model dismatch fail
Click to expand...
Click to collapse
Try the reverse for kicks and giggles meaning try all other files except CSC.

muniz_ri said:
Try the reverse for kicks and giggles meaning try all other files except CSC.
Click to expand...
Click to collapse
<ID:0/004> FAIL! Model dismatch fail

tlopez1973 said:
From what I learned it always ends up being an Odin problem not going back just try different versions of Odin make sure your restart your phone when putting it in download mode
Click to expand...
Click to collapse
so do you have any links to both the PK1 files and odin that you know work? because i still have this problem, and everything i've tried just keeps giving me the same errors, either that odin protocol mismatch, or the model dismatch failure (and you also said try sammobile odin? i can't find it, and their website seems to insist that the G930A doesn't exist)

Sorry for bumping, but I'd really like to fix this