Database Info

Successful flash of SM-G920F - Anyone

OK, no matter what method I try I am unable to achieve a successful flash of my phone. I have tried it via odin with many different firmware versions but all seem to fail almost immediately. The only way to resolve this is to use samsung switch and reset phone to stock. The problem is stock firmware is german vodafone full of vodafone bloatware, I want to get rid of it and flash a UK unbranded firmware but no matter what I do I am unable to achieve this. I can see from the forum that there are many people out there with the same flashing problem but with no real responses on how to achieve the goal. There must be people out there that have achieved this task but don't seem to be offering up much help?

ok
sinbrad said:
OK, no matter what method I try I am unable to achieve a successful flash of my phone. I have tried it via odin with many different firmware versions but all seem to fail almost immediately. The only way to resolve this is to use samsung switch and reset phone to stock. The problem is stock firmware is german vodafone full of vodafone bloatware, I want to get rid of it and flash a UK unbranded firmware but no matter what I do I am unable to achieve this. I can see from the forum that there are many people out there with the same flashing problem but with no real responses on how to achieve the goal. There must be people out there that have achieved this task but don't seem to be offering up much help?
Click to expand...
Click to collapse
Is your phone international unlocked out of the box? I dont believe it was, because as far as I've read international unlocked phones come with "unbranded" firmware. The unlocked ones I know can be pretty much flashed with "any" international firmware, which is what you are trying to do.
If you dont know for sure. Odin the stock German Vodaphone. Let the phone boot. Boot back to stock recovery, then factory reset and clear cache.
Then let the phone boot...Download phone info app by vndnguyen (free version is fine)...Open the app, go to CSC Code tab. Then that will tell you the active CSC code and your firmware CSC code...you are looking for the line that says Available CSC Codes. If it only lists German Vodaphone (VD2), then I believe you are stuck til the phone is unlocked.
Anyone, jump in here if I'm mistaken. I am using this as reference as, I've checked my G920F. Mine is unlocked tho and I can flash any firmware from any region with no problem. Hopefully I've answered your question.

I had no luck with the firmwares on the firmware page either.
If you are on OI9 check http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533
And try flashing the first stock firmware https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list (not the android M one!) via ODIN.
Basic process is:
Download the above file, extract, there should be 4 files inside (AP,BL,CP,CSC), simply select each one to go in the relevant box on ODIN, then go into download mode on your phone and click start...
N.B. Be aware that the above firmware contains a PIT file which will reformat and resize the partitions on your phone, so make sure you have a copy of the stock firmware that works before trying the flash (i.e. the one which Smart Switch downloads). You can grab it from your windows %TEMP% directory during the smart switch download (it first downloads a file to TMPxxx, then extracts it into a directory of the same name, its these files you want. They should be the four files beginning with the type of ODIN file you are flashing (AP,BL,CP,CSC). The files get deleted after the firmware has flashed so make sure you watch the process. If things go wrong you can re-flash these files via ODIN

As far as I was led to believe and when I purchased the phone it did state factory unlocked. I was able to put in any sim when I received it and didn't have to go through any aftermarket unlock process?

I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile

abdussamad said:
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
Click to expand...
Click to collapse
So, seems this is not uncommon?

ok the way to do it is download this file
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
its BTU firmware of 5.1.1
and flash this firmware you'll have 4 files AP,BL,CP,CSC,put it in the respective boxes in odin.I have tested this right now and it works
Press "thanks" if i have helped

Well downloaded the app for CSC info and it states available CSC codes are...
ATL, AVF, CNX, CYV, MOB, MTL, OMN, SIM, SWC, TCL, VD2, VDC, VDF, VDH, VDI, VGR, VIP & VOD
Any ideas?

Ok, tried to get stock firmware when samsung smart switch was downloading and installing but couldn't see where the firmware was being downloaded to? Tried windows temp etc but nothing appeared during download and install?

sinbrad said:
Ok, tried to get stock firmware when samsung smart switch was downloading and installing but couldn't see where the firmware was being downloaded to? Tried windows temp etc but nothing appeared during download and install?
Click to expand...
Click to collapse
Just type in %TEMP% into you windows explorer address bar and it will take you there. arrange by date modified and you will see the size ticking up during the download, before the flash starts it will extract into a folder with the same name, the md5 files can be grabbed from there

No probs here
abdussamad said:
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
Click to expand...
Click to collapse
I flashed BTU firmware on my 920F international unlocked that came with UAE firmware without any problems. Idk

sd_N said:
I flashed BTU firmware on my 920F international unlocked that came with UAE firmware without any problems. Idk
Click to expand...
Click to collapse
Which file and which method?

aaronjp said:
Just type in %TEMP% into you windows explorer address bar and it will take you there. arrange by date modified and you will see the size ticking up during the download, before the flash starts it will extract into a folder with the same name, the md5 files can be grabbed from there
Click to expand...
Click to collapse
Ok, Got it this time, all four files. Will give the method above a go and if it fails at least I've got the stock firmware to fall back on?

Magic, have had great success. Now on the BTU firmware and everything is up and running. Got the stock as well just in case but if this continues to work won't be reinstalling stock. So a big thanks to those who helped

sinbrad said:
Magic, have had great success. Now on the BTU firmware and everything is up and running. Got the stock as well just in case but if this continues to work won't be reinstalling stock. So a big thanks to those who helped
Click to expand...
Click to collapse
Glad you are sorted

No Multi-CSC after flashing Germany's Oreo firmware

Hello, I first bought my phone from Taiwan and the CSC was pointing to BRI(Taiwan) at first but now after flashing Germany's Oreo firmware by following the xda thread, it no longer shows anything in my avaliable CSC, I'm only getting CHO(Chile) and nothing else. Is there a possible fix? I also tried flashing Taiwans firmware for nougat but still ended up with CHO service provider.
Im trying to get back to stock Taiwan firmware because they now have oreo update and supports Samsung Pay while the Germany's firmware doesn't support at all.
Also I accidentally reset my phone with Canada's Sim card in while factory resetting once.
I've attached an image of my phone's CSC info
Any help is appreciated. Thank you
EDIT: another thing I noticed was my phone model changed from SM-G955FD to SM-G955F, is there any way to get it back to FD somehow? In my settings. About phone, it does say SM-G955FD still though

If you change the 'model' of your phone via a flash, you need to flash/change the CSC with the same 'model' of the OS you used.
If it seems a bit convoluted, I'd flash back to full OEM, and make sure that is all OK, and then flash the proper CSC package.

daffychuy said:
Hello, I first bought my phone from Taiwan and the CSC was pointing to BRI(Taiwan) at first but now after flashing Germany's Oreo firmware by following the xda thread, it no longer shows anything in my avaliable CSC, I'm only getting CHO(Chile) and nothing else. Is there a possible fix? I also tried flashing Taiwans firmware for nougat but still ended up with CHO service provider.
Im trying to get back to stock Taiwan firmware because they now have oreo update and supports Samsung Pay while the Germany's firmware doesn't support at all.
Also I accidentally reset my phone with Canada's Sim card in while factory resetting once.
I've attached an image of my phone's CSC info
Any help is appreciated. Thank you
EDIT: another thing I noticed was my phone model changed from SM-G955FD to SM-G955F, is there any way to get it back to FD somehow? In my settings. About phone, it does say SM-G955FD still though
Click to expand...
Click to collapse
Firmwares for SM-G955F and SM-G955FD are IDENTICAL, your model number has not changed. To change CSC I had to install FW with new CSC, then do factory reset and after first boot I got prompted whether I want to change my CSC (based on inserted SIM card), confirmed, the phone did factory reset again and got new CSC installed. Also, Canada is not included within OXM multi-CSC package as G955F/FD is not sold there (or at least not officially).

kernel.killer said:
Firmwares for SM-G955F and SM-G955FD are IDENTICAL, your model number has not changed. To change CSC I had to install FW with new CSC, then do factory reset and after first boot I got prompted whether I want to change my CSC (based on inserted SIM card), confirmed, the phone did factory reset again and got new CSC installed. Also, Canada is not included within OXM multi-CSC package as G955F/FD is not sold there (or at least not officially).
Click to expand...
Click to collapse
JeffDC said:
If you change the 'model' of your phone via a flash, you need to flash/change the CSC with the same 'model' of the OS you used.
If it seems a bit convoluted, I'd flash back to full OEM, and make sure that is all OK, and then flash the proper CSC package.
Click to expand...
Click to collapse
Thank you both for your help. I'll try and flash just the CSC firmware then reset when samsung decides to push the OTA again and will see if that solves it. The firmware for Taiwan came out only a few days before they took it out so didn't have a chance to download it.

Samsung Galaxy S7 - Germany (DBT) - Custom Binary FRP Lock workaround

Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!

Paachan said:
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Click to expand...
Click to collapse
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.

Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
Well this reply isn't really that helpful...
1st she doesn't care anymore because as mentioned she already has a new phone and said I can just keep it or throw it away.
2nd even if it's bricked there are ways to get it back to working, I soft bricked my old HTC M8 once and restored it.
3rd If you're a noob with this just don't reply, I've never had experience with Samsung phones before thats why I'm seeking for help, if it comes to HTC or LG phones I usually get things done myself. Not in this case tho.

Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock

*Detection* said:
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
Click to expand...
Click to collapse
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?

The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835

audit13 said:
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
Click to expand...
Click to collapse
so in this case with the DBT version it's just the default customization file from Samsung, am I right?
Flashing either Home_CSC or CSC didn't had any effect on the S7 tho, it's still stuck in Boot loop with FRP Lock.
Let's say the phone is soft bricked, is there any way to get it back working, so I can flash the stock firmware afterwards`?

Paachan said:
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
Click to expand...
Click to collapse
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related

*Detection* said:
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
Click to expand...
Click to collapse
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day

I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.

audit13 said:
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
Click to expand...
Click to collapse
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!

Sounds like you have tried all you can on your own. Maybe take it to a cell repair shop and have them try to force flash the phone using hardware such as an octopusbox?

Paachan said:
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
Click to expand...
Click to collapse
Yep G930F is International Exynos so you should be good
Some people have problems downgrading from 7.0 to 6.0, what I meant was flash the latest available firmware for DBT, which is 7.0
2018-04-23
Germany
7.0
G930FXXS2DRDI
As above, the bootloader can be a pain to downgrade, so always try unbricking with the latest firmware available
Same process as I posted above, only using the firmware in this post ^^
Good luck
---------- Post added at 19:59 ---------- Previous post was at 19:50 ----------
Paachan said:
I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an indicator)
Click to expand...
Click to collapse
Yea that doesn't sound good, possibly a faulty motherboard, they seem to be quite a high % of hardware faults of the S7 on XDA, at least that is the outcome of sending them in for repair, but also could be the repair centres way of making the most £

Paachan said:
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Click to expand...
Click to collapse
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993

Matty1993 said:
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Click to expand...
Click to collapse
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for my late reply!

Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.

Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
I'm not 100% sure about this, but that firmware states S2 not U2
See here, my BL is B:2 but all of the firmware files I can successfully flash are U2

Matty1993 said:
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Click to expand...
Click to collapse
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Also maybe download U2 firmware aswell as S2 firmware

Matty1993 said:
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Click to expand...
Click to collapse
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers

*Detection* said:
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
Click to expand...
Click to collapse
Or that also maybe yeah try U2 firmware instead of S2 as far as im aware S2 is the first of the B:2 binary updates

Confusing galaxy s6 model

I got samsung galaxy s6
The problem is that i dont understand witch rom i should flash
At the back of my phone and the odin mode says that my model is Sm g920p
But the settings and also other apps such as device info and smart switch says that my model is sm g920f
I thought the previous owner of my phone has flashed a custom rom that changed my model but the confusing part is When i boot into odin mode the Binary says SAMSUNG OFFICIAL.
Please help me

When you're booting into Download Mode, there is an option to show you a bar code, pressing the home buttom. If the meid match with the Dec numbers down behind your phone, it's an 920p.

I have a customized ROM that says OFFICIAL, and a kernel that does the same... don't pay much attention to that. If in Download Mode, it says that the model is G920P, that's the model - doesn't matter what it says anywhere else.
You shouldn't have an issue flashing a firmware. Just flash it, make sure autoreboot isn't on, and restart it into recovery mode, clear cache, system reboot and that should be all.

King-V said:
I have a customized ROM that says OFFICIAL, and a kernel that does the same... don't pay much attention to that. If in Download Mode, it says that the model is G920P, that's the model - doesn't matter what it says anywhere else.
You shouldn't have an issue flashing a firmware. Just flash it, make sure autoreboot isn't on, and restart it into recovery mode, clear cache, system reboot and that should be all.
Click to expand...
Click to collapse
Okey thank you sir.I have one more quistion.I live in asia so my phone is and should be unlocked.If i flash us sprint version on my phone, will it work just fine? Without any service problem

Tuvshuu31 said:
Okey thank you sir.I have one more quistion.I live in asia so my phone is and should be unlocked.If i flash us sprint version on my phone, will it work just fine? Without any service problem
Click to expand...
Click to collapse
Probably, yeah, but it's best to go for unlocked firmwares.

King-V said:
Probably, yeah, but it's best to go for unlocked firmwares.
Click to expand...
Click to collapse
I successfully flashed my phone to a us sprint version as i said.Unfortunately a problem has occurred.I lost my service.It says searching for service by the way My phone detects my sim card and the sim toolkit appeared.But at alst No service.
Can you help with that sir.If the problem occurred because of my new rom can you suggest me an another unlocked rom? please

Flashing Stock Firmware Failed

I have the SM-G955F.
I flashed TWRP using the instructions on here and everything worked perfectly fine. I even booted back into the stock OS - however, the Magisk app was not there.
I was going to boot back into TWRP when I got the message "Only official released binaries are allowed to be flashed" and went into a bootloop.
Then I followed the instructions to flash the stock firmware back on to my S8+, but it failed. Can someone point me in the right direction please?
I used Odin3_v3.13.1. I have attached 2 pictures to show the error.

negative_silent said:
I have the SM-G955F.
I flashed TWRP using the instructions on here and everything worked perfectly fine. I even booted back into the stock OS - however, the Magisk app was not there.
I was going to boot back into TWRP when I got the message "Only official released binaries are allowed to be flashed" and went into a bootloop.
Then I followed the instructions to flash the stock firmware back on to my S8+, but it failed. Can someone point me in the right direction please?
I used Odin3_v3.13.1. I have attached 2 pictures to show the error.
Click to expand...
Click to collapse
Sounds like you are trying flash older firmware than what is on your phone. Odin saying you are flashing firmware with bootloader ver 3. Download mode saying you have ver 4 bootloader. You will need latest version of firmware with ver 4 bootloader or higher and flash with Odin.
Bootloader version number is 5th number from right of firmware name.

spawnlives said:
Sounds like you are trying flash older firmware than what is on your phone. Odin saying you are flashing firmware with bootloader ver 3. Download mode saying you have ver 4 bootloader. You will need latest version of firmware with ver 4 bootloader or higher and flash with Odin.
Bootloader version number is 5th number from right of firmware name.
Click to expand...
Click to collapse
Thanks so much for responding. So from my reading and researching, I figured that was the case. However, I could only find the the official firmwares from here:
https://forum.xda-developers.com/galaxy-s8+/development/rom-galaxy-s8-t3749444
Which happens to be v3 bootloaders. Is there any specific v4 bootloader that I should be flashing? I am at my wits end here. I followed all the instructions perfectly...
I read that everything works fine until reboot then you get the "Only official released binaries are allowed to be flashed"
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009
Any help would be greatly appreciated.

negative_silent said:
Thanks so much for responding. So from my reading and researching, I figured that was the case. However, I could only find the the official firmwares from here:
https://forum.xda-developers.com/galaxy-s8+/development/rom-galaxy-s8-t3749444
Which happens to be v3 bootloaders. Is there any specific v4 bootloader that I should be flashing? I am at my wits end here. I followed all the instructions perfectly...
I read that everything works fine until reboot then you get the "Only official released binaries are allowed to be flashed"
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Firmware can be download from sammobil or updato and flashed with odin
https://www.sammobile.com/firmwares/
https://updato.com/firmware-archive-select-model
Select phone model then search for firmware for your region ( and carrier ).
Only official binary error is probably due to your rmm state being in prernormal state which means if you unlock your bootloader ( oem ) and reboot it will relock bootloader causing this message.
Reflash firmware to get phone running again.
Have a read through this guide for more info about rmm state
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535

spawnlives said:
Firmware can be download from sammobil or updato and flashed with odin
https://www.sammobile.com/firmwares/
https://updato.com/firmware-archive-select-model
Select phone model then search for firmware for your region ( and carrier ).
Only official binary error is probably due to your rmm state being in prernormal state which means if you unlock your bootloader ( oem ) and reboot it will relock bootloader causing this message.
Reflash firmware to get phone running again.
Have a read through this guide for more info about rmm state
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Thank you for the links. I can't tell you how much I appreciate you helping me out.
I bought the phone from eBay, it's a SM-G955F - as for the region and carrier, I live in United States using AT&T. My primary reason getting the international version is to install a custom ROM on it. Is there a specific firmware for my region (U.S.) and carrier (AT&T) that I should flash? I don't see it US listed.
Also, using the guide I mentioned above, I did flash the RMM bypass, however, it was not the version 2, found in the guide you posted. Is that where I messed up?

negative_silent said:
Thank you for the links. I can't tell you how much I appreciate you helping me out.
I bought the phone from eBay, it's a SM-G955F - as for the region and carrier, I live in United States using AT&T. My primary reason getting the international version is to install a custom ROM on it. Is there a specific firmware for my region (U.S.) and carrier (AT&T) that I should flash? I don't see it US listed.
Also, using the guide I mentioned above, I did flash the RMM bypass, however, it was not the version 2, found in the guide you posted. Is that where I messed up?
Click to expand...
Click to collapse
I don't live in the US but there should be filters on the websites to filter by region. I normally use updato and firmware for your region shows up under U.S.A it will show you all your carrier's like at&t, Sprint, t-mobile and non carrier firmware.
As for the rmm zip version 2 may have been better it is more up to date and is smaller in size. Both should do the same job though.

spawnlives said:
I don't live in the US but there should be filters on the websites to filter by region. I normally use updato and firmware for your region shows up under U.S.A it will show you all your carrier's like at&t, Sprint, t-mobile and non carrier firmware.
As for the rmm zip version 2 may have been better it is more up to date and is smaller in size. Both should do the same job though.
Click to expand...
Click to collapse
I looked on updato and sammobile, both do not have USA region. Can I flash firmware from another region and still get it to work on my carrier?
For example, can I flash U.K. (Vodafone) since its on ver 4 firmware and uses GSM - regardless of region and carrier?

negative_silent said:
I looked on updato and sammobile, both do not have USA region. Can I flash firmware from another region and still get it to work on my carrier?
For example, can I flash U.K. (Vodafone) since its on ver 4 firmware and uses GSM - regardless of region and carrier?
Click to expand...
Click to collapse
Just doubled checked saw you have the f series while updato has u1 version firmware that I can see.
You can flash firmware from the UK if you want but can't say for certain you will have full network capabilities due to the difference in region and carriers ( network capabilities ). I would try and find an unbranded version ( non carrier branded) firmware first if not then something like Vodafone .

There is a simple reason for this. If you came from TWRP as "reboot to download", this creates the problem. Turn off the phone. Go to download mode with Vol_Down+Bixby+Power and then press Vol_Up button. When I enter download mode like this, it flashes without any problems.