I have an A51 samsung phone on the download mode screen i get the b:5 k:5 s:5 which im told are important to choosing firmware, can anyone explain them so i dont use the wrong one and possibly brick my phone also what else should i know about samsung phones in general before installing a firmware
seif113 said:
I have an A51 samsung phone on the download mode screen i get the b:5 k:5 s:5 which im told are important to choosing firmware, can anyone explain them so i dont use the wrong one and possibly brick my phone also what else should i know about samsung phones in general before installing a firmware
Click to expand...
Click to collapse
You can flash a firmware that has a binary of 5 or higher, not lower than 5. To identify which binary a firmware has, look at the firmware build number, the 5th character from the right end of the build number represents the binary value for that firmware. Your current firmware build number should have a 5 in that position in it's build number.
As long as you choose a firmware that is for your specific device's model number, from your specific region/country/carrier with a binary that is equal to or higher(not lower) than your currently installed binary, you should be fine as long as you carefully follow instructions to flash the firmware via Odin.
Note: once you upgrade the binary to a newer binary, you can't go back to the binary that you had before. So, if you upgraded from binary 5 to binary 6, you can't go back to 5, 4, 3, 2 or 1 using official methods. It is technically "possible" to downgrade, but that is conditional, it "can" be done depending on the device and certain aspects of the software state of the device. It can be difficult for the uninitiated and risky for the initiated and uninitiated alike.
https://forum.xda-developers.com/t/s10-g973f-problem-bootloader.4536141/post-87950127
Thanks guys, another question, i read that basband matching is important although you can get away with not matching basebands so can anyone clarify a bit more from experience, also if it happens that someone flashed a u5 phone with a u4 or u3 for example what will go wrong and whats the possible ways to fix it . And thankss
Rooting, ODIN, Firmware, CSC Information And Myths Debunked / Noob's Guide To Samsung Devices
Since a lot of people will have their Galaxy S22 Ultra soon and I myself am thinking about either getting an S21 Ultra or S22 Ultra, I wanted to summarise a lot of information I found out during researching as Samsung devices are quite different...
forum.xda-developers.com
Related
Hello wise people of XDA,
This is my first post.
I currently use an S6 G920F United Kindom unlocked as my phone and i have been using this phone for a long time. Now its past its warranty I decided to root the phone and see what i can do with it and get rid of the bloatware. Normally i either use KingoRoot or KingRoot but both failed so I searched around on the internet and came across CF Auto Root. After seeing it was successful for others i jumped on the bandwagon. I rooted it and everything was golden until i came across a problem, it would randomly turn off. This was random and infrequent. but not it happens like 5 times a day so i decided to flash a stock rom. For some strange reason Sam mobile wont let me download a stock Rom so after poking around the internet i have download a few stock roms however they always fail in Odin. Now my phone wont even boot as it says "error occured while updating use smart switch emergency recovery feature" so i go onto the Smart switch PC app and then it doesnt recognise. After 2 days of trying i haven't had any luck so I don't know what to so. Every time I try flashing something, when it fails i get some red text on the phone which I don't understand.
Someone please help me as I cant just buy a new phone and this is the only phone i have got. Any help would be very grateful and please don't hesitate to ask any questions.
Edit:
It says on the Download Screen:
Odin Mode
Product Name: SM-G920F
Current Binary: Custom
System Status: Custom
Reactivation Lock: Off
Secure Download: Enabled
Knox Warranty Woid : 1 (0x0500)
RP SWREV: B:6 K:2 S:2
(When it fails it says) SW REV. Check Fail. Device:6 . Binary: 5
Hopefully that helped.
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Bryan48765 said:
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Click to expand...
Click to collapse
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
wasim.1.wt said:
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
Click to expand...
Click to collapse
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Bryan48765 said:
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Click to expand...
Click to collapse
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
wasim.1.wt said:
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
Click to expand...
Click to collapse
U6/S6, "Device:6" is in the odin log so it's already 6 and won't return to 5.
Hey All,
Like many unfortunate souls out there I updated my device to Oreo via T-Mobile OTA and instantly my device slowed down with odd behavior. Given I have G930T model which cannot be rooted (be very honest I am confused between the models and why G930T can't be rooted), I am desperate to make this posting hoping someone can help me a bit.
My simple goals:
- Get stock Android on my device and have it running faster, all features working and extend my battery life.
- Keep my phone/app settings
- Not have T-Mobile bloatware.
My concerns:
- Will I lose features such as camera not working in a text message app, WiFi calling, etc.
- Is it better to go back to Nougat or install Oreo? (this is once I figure out all the jargon and many guides)
I refuse to upgrade to a newer device because of stupid software updates and I love this phone too much. This phone is causing me issues professionally such as speaker turning off in the middle of the call, call volume is too low, outgoing text messages failing, sluggish performance, freezing, and horrible battery life. Beside for battery issue, everything else started to happen after software updates.
My Device/Setup:
- Samsung Galaxy S7 - T-Mobile - G903T
- Current stock version R16NW.G930TUVU4CRF1
- macOS with Samsung USB cable
Before there is an outcry on why I didn't search for and find a previous thread that can easily explain, I did and found this amazing write up (it took me a while to even find this):
https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-t3846694
However, there are a few things that I use daily such as visual voicemail and WiFi calling in an office where I had a bad signal. I really hope this post gets me some specific pointers and not get removed from the site for posting this. I am a beginner so please be gentle.
Thanks!
The main difference between models and why some can't be rooted is the SoC, all USA models use Snapdragon and come with an locked bootloader that can't be unlocked. All other models come with Exynos with an unlockable bootloader. The bootloader needs to be unlocked for root.
There are root methods for the G930T, but it involves using engineering bootloaders to get around the lock, which is in that thread you linked (AP_SM_G930_OREO_ENG_BOOT.tar), since it's an engineering bootloader and not 'production' it comes with its issues https://www.reddit.com/r/Android/comments/5xzbo3/qualcomm_s7_engineering_boot_images_leaked_root/
Unfortunately if you want the best performance, keeping app settings isn't likely. The best approach would be a clean flash of stock firmware using Odin with a full wipe. If you use the G930U firmware, which is the carrier unlocked version of your phone, it won't have bloatware. But this may impact WiFi calling since that's part of your carriers firmware.
Because of the locked bootloader, you also can't downgrade, so Nougat is off the table.
Here's a pretty easy to follow flash guide https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
You can use the same site to download the firmware files, or use samfirmtool or sammobile.com. Just put the AP, BL, CSC and CP files in their respective slots and hit start.
Flashing stock firmware with Odin doesn't void warranty or anything like that.
EDIT: The guide also links an older version of Odin, you'll want 3.13.1 for flashing Oreo
Beanvee7 said:
The main difference between models and why some can't be rooted is the SoC, all USA models use Snapdragon and come with an locked bootloader that can't be unlocked. All other models come with Exynos with an unlockable bootloader. The bootloader needs to be unlocked for root.
There are root methods for the G930T, but it involves using engineering bootloaders to get around the lock, which is in that thread you linked (AP_SM_G930_OREO_ENG_BOOT.tar), since it's an engineering bootloader and not 'production' it comes with its issues ...
Unfortunately if you want the best performance, keeping app settings isn't likely. The best approach would be a clean flash of stock firmware using Odin with a full wipe. If you use the G930U firmware, which is the carrier unlocked version of your phone, it won't have bloatware. But this may impact WiFi calling since that's part of your carriers firmware.
Because of the locked bootloader, you also can't downgrade, so Nougat is off the table.
Here's a pretty easy to follow flash guide ...
You can use the same site to download the firmware files, or use samfirmtool or sammobile.com. Just put the AP, BL, CSC and CP files in their respective slots and hit start.
Flashing stock firmware with Odin doesn't void warranty or anything like that.
EDIT: The guide also links an older version of Odin, you'll want 3.13.1 for flashing Oreo
Click to expand...
Click to collapse
Thanks for such a detail accurate answer I was looking for. Sorry for the late reply as work has been crazy. I will go through to install Samsung stock firmware and see if it improves performance and battery life. Will try to get G930U and see if I can go without WiFi calling. First, I am trying to do a backup using SmartSwitch (will dig around for more backup option if this one doesn't work). Will update here once I am finished and any lesson learned to help someone else in the future.
It took me awhile to figure this out but I have finally figured it out. If you have further insight or questions, feel free to comment.
Step 1
Step 1 is to recognize which security updates have a number assigned to them by visiting:
http://doc.samsungmobile.com
An example URL for example for a chinese N9600 Note 9 for TGY [Hong Kong] would be to go here:
http://doc.samsungmobile.com/SM-N9600/TGY/doc.html
To find yours, just put it into your search engine to find the link you need:
site:doc.samsungmobile.com [insert your model here]
Example search:
site:doc.samsungmobile.com SM-N960U
Step 2
Step 2 is to look at the last 4 digits after Build Number.
In this case, I wanted to know the last security update available for Oreo 8.1.0 before it switched to Pie. So, I looked at the build number on there and found the last 4 characters to be ASA5 (for N9600 in region TGY. Your phone will be different).
Step 3
Step 3 is to find your firmware on somewhere like sammobile.
In my case I wanted to see if this firmware was the last and most updated possible firmware for Oreo on this carrier.
https://www.sammobile.com/samsung/galaxy-note9/firmware/SM-N9600/TGY/download/N9600ZHU1ASA5/253349/
By looking at the firmware CSC I am able to see this:
N9600TGY1ASA5
Let's break this down.
N9600 TGY1 ASA5
N9600 = model of the phone
TGY = most likely the region
1 = unknown. When I look at these, I see it's either 1 or 2, but that's unimportant for our purposes.
ASA5 = security update
Step 4
By looking at this and referencing the samsungmobile.com changelog page (from step 1), I can therefore see that this firmware is the correct for my N9600 phone, and it is using the latest ASA5 security update which is the last security update for this carrier that will ever be released for Android Oreo 8.1.0.
Keep in mind that a "security update" is not just a "security" update. It includes all the bugfixes for Android. I guess Google would prefer to make the updates appear to be updates "for your security", rather than updates "because there were bugs with our software that we fixed".
Hope it helps! Fee free to reply with any additional knowledge or questions.
Bootloader
The Fifth last digit after the CSC and before the Security Patch version number is the Version of the Bootloader.
eyeb1 said:
The Fifth last digit after the CSC and before the Security Patch version number is the Version of the Bootloader.
Click to expand...
Click to collapse
No, it isn't the bootloader version, it is the binary version of the bootloader. Two firmware can have the exact same bootloader version but have different binary versions. It is possible to have a firmware that has "this" bootloader version with "that" binary version and then an update can be released that uses the same bootloader as the previous firmware but the update could contain a modem or system update and have a higher binary version than the previous firmware even though it has the same bootloader as the previous version.
Sent from my SM-S767VL using Tapatalk
zxzxzxzxzxzxzxzxzx said:
It took me awhile to figure this out but I have finally figured it out. If you have further insight or questions, feel free to comment.
Step 1
Step 1 is to recognize which security updates have a number assigned to them by visiting:
http://doc.samsungmobile.com
An example URL for example for a chinese N9600 Note 9 for TGY [Hong Kong] would be to go here:
http://doc.samsungmobile.com/SM-N9600/TGY/doc.html
To find yours, just put it into your search engine to find the link you need:
site:doc.samsungmobile.com [insert your model here]
Example search:
site:doc.samsungmobile.com SM-N960U
Step 2
Step 2 is to look at the last 4 digits after Build Number.
In this case, I wanted to know the last security update available for Oreo 8.1.0 before it switched to Pie. So, I looked at the build number on there and found the last 4 characters to be ASA5 (for N9600 in region TGY. Your phone will be different).
Step 3
Step 3 is to find your firmware on somewhere like sammobile.
In my case I wanted to see if this firmware was the last and most updated possible firmware for Oreo on this carrier.
https://www.sammobile.com/samsung/galaxy-note9/firmware/SM-N9600/TGY/download/N9600ZHU1ASA5/253349/
By looking at the firmware CSC I am able to see this:
N9600TGY1ASA5
Let's break this down.
N9600 TGY1 ASA5
N9600 = model of the phone
TGY = most likely the region
1 = unknown. When I look at these, I see it's either 1 or 2, but that's unimportant for our purposes.
ASA5 = security update
Step 4
By looking at this and referencing the samsungmobile.com changelog page (from step 1), I can therefore see that this firmware is the correct for my N9600 phone, and it is using the latest ASA5 security update which is the last security update for this carrier that will ever be released for Android Oreo 8.1.0.
Keep in mind that a "security update" is not just a "security" update. It includes all the bugfixes for Android. I guess Google would prefer to make the updates appear to be updates "for your security", rather than updates "because there were bugs with our software that we fixed".
Hope it helps! Fee free to reply with any additional knowledge or questions.
Click to expand...
Click to collapse
The "1" or "2" in the build number that you mentioned is not "unimportant", it is actually the most important character in the build number because it tells you which binary that the firmware is. The binary is very important because it decides what you can and can not flash on the device.
For example, if your device currently has a binary "2" firmware, you will not be able to flash a binary "1" firmware. Basically, you can not flash a firmware that has a lower binary than the firmware that is currently installed. This is to prevent downgrading to a less secure firmware version. If you want to stay up to date and have the most secure firmware, you need to use a firmware that has the highest binary version available for your device.
My current device has a binary 6 firmware, this means that I can not flash binary 5, 4, 3, 2 or 1 on my device. I can only flash binary 6 or binary 7 if 7 is ever released.
Keep in mind, updating binary can ruin your chances of rooting a device if the updated binary locks the bbootloader. Security updates are more about securing the carrier's network than it is about securing your device itself or about bug fixes, though, there are some things in the updates that make your device itself more secure, part of the security updates are about securing the device so that even you as the user can not crack it, this is to prevent you from rooting the device, modifying the device or flashing any kind of unapproved software on the device.
These security and binary updates are what prevent people like us here at XDA from customizing our devices. They are good for device security but they are a thorn in our sides that we can't stand because they prevent us from doing what we want with our devices.
Sent from my SM-S767VL using Tapatalk
So I have a Samsung j260AZ and it got stuck in firmware binary and will not accept any of the original firmware because of the Bit numbers below
B=5 K=5 S=5 <-- this was not the original numbers
So I Am trying to figure out how I can get the phone to accept the firmware.
I've tried 3 different odins (Comsy, 13.3, patched)
I have tried numerous ways to flash this phone and it just wont get back to normal.
HELL I even tried flashing the wrong firmware just to get firmware binary to leave and any kind of launcher to boot up but it wont accept any kind of firmware ...and I am not trying to go any higher in bit numbers. I tried to flash a unlocked version of bit security but that doesn't work either.
Anyways if anyone has any options I can do please let me know.
TheofficialJonerockit said:
So I have a Samsung j260AZ and it got stuck in firmware binary and will not accept any of the original firmware because of the Bit numbers below
B=5 K=5 S=5 <-- this was not the original numbers
So I Am trying to figure out how I can get the phone to accept the firmware.
I've tried 3 different odins (Comsy, 13.3, patched)
I have tried numerous ways to flash this phone and it just wont get back to normal.
HELL I even tried flashing the wrong firmware just to get firmware binary to leave and any kind of launcher to boot up but it wont accept any kind of firmware ...and I am not trying to go any higher in bit numbers. I tried to flash a unlocked version of bit security but that doesn't work either.
Anyways if anyone has any options I can do please let me know.
Click to expand...
Click to collapse
Let me guess, you updated your device and now you want to go back to what you had?
Or, your device needed to have the stock firmware reflashed to repair the device to normal function and now you are trying to flash the stock firmware to repair the device but the firmware you are flashing is older than the firmware that was already on the device?
If either of these is the case for you, it is failing because you can't downgrade from a higher binary down to a lower binary, you can only keep the binary you have or flash up to the next binary, but once you go up to that next binary, once again, you can't go back to the binary that you had before.
In other words, if the firmware that was already on your device was a binary 6 or higher firmware, you can't flash the binary 5 firmware, you could flash a binary 7 over the binary 6, but once you had binary 7 installed, you could never go back to binary 6 or binary 5.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Let me guess, you updated your device and now you want to go back to what you had?
Or, your device needed to have the stock firmware reflashed to repair the device to normal function and now you are trying to flash the stock firmware to repair the device but the firmware you are flashing is older than the firmware that was already on the device?
If either of these is the case for you, it is failing because you can't downgrade from a higher binary down to a lower binary, you can only keep the binary you have or flash up to the next binary, but once you go up to that next binary, once again, you can't go back to the binary that you had before.
In other words, if the firmware that was already on your device was a binary 6 or higher firmware, you can't flash the binary 5 firmware, you could flash a binary 7 over the binary 6, but once you had binary 7 installed, you could never go back to binary 6 or binary 5.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I read also
but I was just hoping that it wasn't true or that their was some way to intercept or clone its coding but install the real thing.
Well I guess I am gonna make this phone my test phone and see how badly I can screw it up by installing stuff and test software on it. LoL until it wont work anymore.
Has anyone tried Linux/Heimdall vs Windows/ODIN? I am just curious to try it myself as I gave up on Windows years ago. It also seems to me that since Android is a Google-based form of Linux, that a Linux user may have more success.. I will be attempting it myself as I cannot get my phone to update to Android Pie, or anything after the June 2019 version of Oreo and the security updates. Contacting Cricket nor Samsung is of any use as they are both reluctant to help anyone with any issue that doesn't include buying something (i.e. new warranty, new phone, new service upgrade, ect.), even though my phones are always purchased, not leased. Anyway.... I will be either flashing this old and busted thing or destroying it completely. Wish me luck.
Hello, I wanted to ask a few questions
After a firmware flash with XPG CSC code for example is it possible to change the CSC code to THL and vice versa?
Is there really any way to lower firmware to a lower version?
If so, what file / path do I need to do this?
what is the differences between OXA and OXM?
Is there a place where you can read about the new changes that Samsung has made in recent years in terms of security that can not flash firmware to an older version and can not change CSC codes?
I know how to root a phone and use ADB (ADB in a very basic way)
Thanks!
up
This post has some information
Fail to flash with odin to downgrade from android 10
About a year ago, I downloaded firmware for N960F from updato and downgraded from Pie to Oreo using Odin and it went all so well. This time around I'm trying to downgrade from Android 10 to the exact same firmware version I used back then, just...
forum.xda-developers.com
But since about the s8-s9 days Samsung implimented anti rollback , wich are not so clear , some phones cand downgrade to a previous version and some dont due the firmware setting the minimun version bar higher so to speak .
Wich model are you trying to downgrade?