Hello guys
I have my galaxy s7 from germany. A while ago I flashed the btu software which had newer changelist. Now I don't know what csc my phone uses because I'm not getting the original DBT neither the BTU updates via OTA. You can see my phone info screenshots. How can I change my csc to get the ota updates?
Flash 4 files either BTU or DBT with the original CSC file instead of home CSC. It will wipe the phone but that's required so you get the OTA's.
I did that a few days ago for BTU and got a new OTA update today.
Sent from my SM-G930F using Tapatalk
Fig Bucker said:
Flash 4 files either BTU or DBT with the original CSC file instead of home CSC. It will wipe the phone but that's required so you get the OTA's.
I did that a few days ago for BTU and got a new OTA update today.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Okay thanks. Can you send me a link with all the files needed? Or some kind of guide?
Sure.
I downloaded BTU firmware from here. It's faster to download than sammobile and it's one OTA update behind so you can test the OTA works right away.
http://updato.com/firmware-archive-select-model?record=AF9CED1074D111E69B2DFA163EE8F90B
1. Download firmware above (or DBT). Extract/unzip to your computer.
2. Download latest Odin (3.1.1)
3. Set up a security pin on your phone, apparently it asks for this but it didn't for me, possibly because I didn't use home CSC but better to be safer than sorry.
4. In Odin allocate your extracted files to each check box(AP, CSC etc.). You don't need to change any settings on any other tabs etc. Make sure to use regular CSC not the home one.
5. Plug in phone, wait a while until detected and then you can start the process.
When complete search for OTA update before reinstalling all your apps. Should be a little quicker this way.
Video below may help too
https://youtu.be/7SK3IMprKVQ
Sent from my SM-G930F using Tapatalk
Fig Bucker said:
Sure.
I downloaded BTU firmware from here. It's faster to download than sammobile and it's one OTA update behind so you can test the OTA works right away.
http://updato.com/firmware-archive-select-model?record=AF9CED1074D111E69B2DFA163EE8F90B
1. Download firmware above (or DBT). Extract/unzip to your computer.
2. Download latest Odin (3.1.1)
3. Set up a security pin on your phone, apparently it asks for this but it didn't for me, possibly because I didn't use home CSC but better to be safer than sorry.
4. In Odin allocate your extracted files to each check box(AP, CSC etc.). You don't need to change any settings on any other tabs etc. Make sure to use regular CSC not the home one.
5. Plug in phone, wait a while until detected and then you can start the process.
When complete search for OTA update before reinstalling all your apps. Should be a little quicker this way.
Video below may help too
https://youtu.be/7SK3IMprKVQ
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Thank you very much
Fig Bucker said:
Sure.
I downloaded BTU firmware from here. It's faster to download than sammobile and it's one OTA update behind so you can test the OTA works right away.
http://updato.com/firmware-archive-select-model?record=AF9CED1074D111E69B2DFA163EE8F90B
1. Download firmware above (or DBT). Extract/unzip to your computer.
2. Download latest Odin (3.1.1)
3. Set up a security pin on your phone, apparently it asks for this but it didn't for me, possibly because I didn't use home CSC but better to be safer than sorry.
4. In Odin allocate your extracted files to each check box(AP, CSC etc.). You don't need to change any settings on any other tabs etc. Make sure to use regular CSC not the home one.
5. Plug in phone, wait a while until detected and then you can start the process.
When complete search for OTA update before reinstalling all your apps. Should be a little quicker this way.
Video below may help too
https://youtu.be/7SK3IMprKVQ
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I might do something wrong but no change in csc. I set pin code. I set it as start up protection(without it as well), but no luck. Flashed the original csc my phone was wiped but still no ota and still the same screens in phone info as I posted earlier. I also tried BTU HOME csc but no luck with that.
kataik95 said:
I might do something wrong but no change in csc. I set pin code. I set it as start up protection(without it as well), but no luck. Flashed the original csc my phone was wiped but still no ota and still the same screens in phone info as I posted earlier. I also tried BTU HOME csc but no luck with that.
Click to expand...
Click to collapse
Samsung is kinda late with the OTA updates so it might take some time before they push it to your device but you better of by making a backup of your apps and setting trough the sammy cloud and then flash the newer firmware in Odin.
Hi guys,
it's been a few weeks that I'm struggling to understand why I'm not getting software updates.
My phone is stock, never rooted nor flashed. It's been with this software since when I bought it.
My CSC is VDI and I was noticing that potentially the modem version on my phone (CP) is wrong.
Here's my details:
AP: G930FXXU1DQEI
CSC: G930FVFG1DQE3
CP: G930FXXU1BPJJ
Model: SM-G930F
I was trying to figure out why I'm not getting updates and from what I can see here: http://fota-cloud-dn.ospserver.net/firmware/VDI/SM-G930F/version.xml I should have a different CP version in order to get the update (G930FXXU1DQD7) which also seems in line with what this firmware page has: https://samsung-firmware.org/download/Galaxy__S7__/n494/VDI/G930FXXU1DQEI/G930FVFG1DQE3/
Now, a couple of questions.
- Any idea of the why? Could it be just a mistake in the production of the device?
- Is my hypothesis correct that I'm not receiving updates because of this?
- Would it be safe to only flash the CP part with ODIN and let the device receive the OTA normally?
Looking forward to hearing your thoughts!
I've not heard of a modem stopping updates, but it's not an area I'm fully familiar with.
Flashing modems with Odin is probably the most harmless flash you can do as long as it's for the same android version (e.g. don't flash a nougat modem on a marshmallow device)
You could also try flashing the latest home_csc, and bootloader (BL) if you really wanted to. Both of those are pretty trivial to flash too. If you do flash csc just make sure it's home_csc, and regular csc wipes your data.
Beanvee7 said:
I've not heard of a modem stopping updates, but it's not an area I'm fully familiar with.
Flashing modems with Odin is probably the most harmless flash you can do as long as it's for the same android version (e.g. don't flash a nougat modem on a marshmallow device)
You could also try flashing the latest home_csc, and bootloader (BL) if you really wanted to. Both of those are pretty trivial to flash too. If you do flash csc just make sure it's home_csc, and regular csc wipes your data.
Click to expand...
Click to collapse
Hi, thanks for your reply.
I ended up flashing CP only for the firmware I was at and I straight away got the update notification and the subsequent security patches up to December 2017 ( was stuck at may ). I'm at the latest firmware for my CSC now.
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
Please help me and excuse my poor english I'm a French guy. Thanks in advance :
I just bought an official new sm-g930f with a Knox set to 0x000 and I want to keep it that way.
The problem is that my phone came with a lot of swisscom bloatwares and apps, since booting up the phone the swisscom logo starts, and I find that very annoying and maybe battery draining with all of the swisscom apps. I want to remove all of that without rooting my phone.
I read different threads about downloading firmware and flash with Odin. Csc changing BTU ZEF. I didn't really understand and I'm afraid of rooting my phone.
My oreo o.s is g930fxxu2ere8.
Please help me. Thank you all
Flashing with Odin won't root your phone or trigger knox, you'd have to specifically flash a custom package to do that, which is hard to accidentally do.
Here's a guide for flashing with Odin: https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Using the same site you can download the unbranded firmware and flash it, flashing home_csc will keep your data but may not get rid of all the bloat, flashing CSC triggers a factory wipe but should clean your bloat.
Thank you for replying I'm currently downloading a firmware that belongs to another country using SamFirm, my question now is :
How to flash the CSC (not home_csc) to get rid of bloatwares ? Does it come with the firmware from Sam mobile ? Thank you
Update
Update of what I did ; for the ones who may face the same problem : Please excuse my English ^_^
I used SamFirm to download a UK country of the Oreo O.S (Named: G930FXXU2ERD6) I installed Odin 3.13.1 on my i5 laptop and select every file of the downloaded firmware in the dedicated cases (I used Home_Csc file, instead of Csc file *this one marked failed in Odin for me anywa*), then hit start
Once Odin finishes the process you will be asked to enter your phone secured pin code. Enter it then you will be asked to Reset the phone. Then it will boot it normally. For me I did hard reset and wipe cache it after the reset.
Things are working the way I want right now and OTA updates are also working. No bloatware or swisscom animation during boot.
Thank you all have a great day.