Hello,
I am attempting to downgrade from Android 8 to 7 on Galaxy S7. When I attempt to flash the old firmware I get the error 'Device 3 - Binary 2'. Does anyone know if there is a workaround for this yet?
DannySB1 said:
Hello,
I am attempting to downgrade from Android 8 to 7 on Galaxy S7. When I attempt to flash the old firmware I get the error 'Device 3 - Binary 2'. Does anyone know if there is a workaround for this yet?
Click to expand...
Click to collapse
Odin will not let you flashback to a previous boot loader version, you have to do it through TWRP. So either flash the nougat firmware with TWRP first or any nougat based rom, then flash nougat via odin which will remove root and TWRP.
cooltt said:
Odin will not let you flashback to a previous boot loader version, you have to do it through TWRP. So either flash the nougat firmware with TWRP first or any nougat based rom, then flash nougat via odin which will remove root and TWRP.
Click to expand...
Click to collapse
Are there any instructions for this?
Will secure apps (Banking etc) work again after removing root?
I was under the impression you could via Odin if OEM unlock was enabled, without needing TWRP or root. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-downgrade-android-oreo-8-0-t3821495
edit: As for banking, if you go root then flash back to stock you should have no issues. Even if you stay root, things like Magisk will hide root status from apps and pass safetynet. Your biggest issue would be the loss of Knox, which voids warranty and breaks some Samsung apps.
Beanvee7 said:
I was under the impression you could via Odin if OEM unlock was enabled, without needing TWRP or root. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-downgrade-android-oreo-8-0-t3821495
Click to expand...
Click to collapse
It is not possible as per some of the replies to that thread. I spent a few hours playing TWRP yesterday and it was not possible either.
DannySB1 said:
It is not possible as per some of the replies to that thread. I spent a few hours playing TWRP yesterday and it was not possible either.
Click to expand...
Click to collapse
Ok so listen, it can be done as i said but it's not easy. The choice you have of course before attempting this is to just install a android 7 custom ROM? many nougat ROMs are just stock with the bloatware removed and the boot-loader version isn't checked during flash.
Here's another way to go back, i can't guarantee it will work though i haven't tried it on an S7.
Downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's how's it done?
Download the firmware file (.tar) which you want to downgrade to and open it with an archiver application (7zip). Extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends in .bin (e.g. sboot.bin etc.). This .tar file can now be flashed like any other firmware file via Odin and it should run through it without any problems.
Hope this helps.
plz tell me how to downgrade i upgraded my phone to oreo now there's no network i need to downgrade back to marshmellow i also installed marshmellow but it stuck on samsung bootloop plz help me
Bipnbarsha said:
plz tell me how to downgrade i upgraded my phone to oreo now there's no network i need to downgrade back to marshmellow i also installed marshmellow but it stuck on samsung bootloop plz help me
Click to expand...
Click to collapse
What device? What firmware? What Rom?
S7 edge on oreo and stock rom my network was working fine on marshmellow but after oreo update my mobile network not working unfortunatly my binary has been updated before update i back up everything with twrp but now when i restore using twrp my phone stuck on samsung logo plz help mee
downgrand note 9 N9600 ZTO
i need to downgrand my note 9 i pay for the service of someone who can help me. i'm on the last firmawre bdo android 9 and i want to downgrand to the latest firmware of android 8.1. My note 9 is the N9600 ZTO.
email
[email protected]
whatsapp and telegram
+5582994311001
cooltt said:
Ok so listen, it can be done as i said but it's not easy. The choice you have of course before attempting this is to just install a android 7 custom ROM? many nougat ROMs are just stock with the bloatware removed and the boot-loader version isn't checked during flash.
Here's another way to go back, i can't guarantee it will work though i haven't tried it on an S7.
Downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's how's it done?
Download the firmware file (.tar) which you want to downgrade to and open it with an archiver application (7zip). Extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends in .bin (e.g. sboot.bin etc.). This .tar file can now be flashed like any other firmware file via Odin and it should run through it without any problems.
Hope this helps.
Click to expand...
Click to collapse
Hey man, can you please explain this better ? Im using a galaxy s7 edge, but my firmware doesnt have a TAR file. there are 4 .md5 files (AP,BL,CP,CSC) that are flashable through odin. I want to downgrade bootloader
laurentiudll said:
Hey man, can you please explain this better ? Im using a galaxy s7 edge, but my firmware doesnt have a TAR file. there are 4 .md5 files (AP,BL,CP,CSC) that are flashable through odin. I want to downgrade bootloader
Click to expand...
Click to collapse
Hello that method no longer works, you can't downgrade anymore
cooltt said:
Hello that method no longer works, you can't downgrade anymore
Click to expand...
Click to collapse
I can downgrade to 14.1 Lineage OS.
Edit: There is no way do downgrade the official firmware
My phone is boot-looping after i did android 9.0 update using odin.I had PrometheusOneUI V2.0 as a custom rom before but i had no imei and baseband so i needed that back so i downloaded the newest filmware of sammobile and i flashed the filmware using Odin.I got a pass but the phone is now bootlooping.When i go to download mode now FRP Lock and OEM lock are off.and when i try to flash root it now shows me <Only official released binaries are allowed to be flashed (Recovery)>.It wont let me flash anything other than the stock rom that results in bootlooping.Did anyone else have this problem,Can someone please help me with my bricked SM-J530F
kevin50206 said:
My phone is boot-looping after i did android 9.0 update using odin.I had PrometheusOneUI V2.0 as a custom rom before but i had no imei and baseband so i needed that back so i downloaded the newest filmware of sammobile and i flashed the filmware using Odin.I got a pass but the phone is now bootlooping.When i go to download mode now FRP Lock and OEM lock are off.and when i try to flash root it now shows me <Only official released binaries are allowed to be flashed (Recovery)>.It wont let me flash anything other than the stock rom that results in bootlooping.Did anyone else have this problem,Can someone please help me with my bricked SM-J530F
Click to expand...
Click to collapse
Flash the device via Odin, when it bootloop, turn the device off, then boot your device into stock recovery and then choose the factory reset option.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Flash the device via Odin, when it bootloop, turn the device off, then boot your device into stock recovery and then choose the factory reset option.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I already tried that and i wiped catch,i also tried another filmware form the uk still its bootlooping
kevin50206 said:
I already tried that and i wiped catch,i also tried another filmware form the uk still its bootlooping
Click to expand...
Click to collapse
Ok, you've got something else going on.
Have you previously modified the device or flashed anything on the device that wasn't stock? If so, did the modifications or whatever you flashed cause an issue and that is now the reason you are flashing the firmware?
Are you certain that your firmware is for your specific device and is it the most up to date version for your device?
Droidriven said:
Ok, you've got something else going on.
Have you previously modified the device or flashed anything on the device that wasn't stock? If so, did the modifications or whatever you flashed cause an issue and that is now the reason you are flashing the firmware?
Are you certain that your firmware is for your specific device and is it the most up to date version for your device?
Click to expand...
Click to collapse
Yes i matched the model number and no i was not running anything that isn't for it
kevin50206 said:
Yes i matched the model number and no i was not running anything that isn't for it
Click to expand...
Click to collapse
But are you using the most up to date firmware? Older/downgraded firmware won't work, it has to be exactly the same binary as what is already on the device or a firmware with a newer binary, it can not be a firmware that has an older binary than the firmware that is already on the device.
Sent from my SM-S767VL using Tapatalk
Does anyone know how to downgrade bootloader in Samsung (M51)? I'm trying to rollback to OneUI 2.5 from 3.1 but it keeps giving me sw error
Wondering what sense it would make to downgrade phone's bootloader:
A bootloader helps to load the operating system or runtime environment to add programs to memory and provide access for components. It is needed to run the startup process, initialize the hardware, and pass control to the kernel, which initializes the operating system.
AlanDias17 said:
Does anyone know how to downgrade bootloader in Samsung (M51)? I'm trying to rollback to OneUI 2.5 from 3.1 but it keeps giving me sw error
Click to expand...
Click to collapse
No, you can't downgrade bootloader on Samsung unless the downgraded bootloader has a binary version equal to the binary version of your currently installed bootloader. For example, if the binary version of your currently installed bootloader is binary 4, you can flash the downgraded bootloader if it is also binary 4 but you cannot flash a bootloader that is binary 3, 2 or 1.
xXx yYy said:
Wondering what sense it would make to downgrade phone's bootloader:
A bootloader helps to load the operating system or runtime environment to add programs to memory and provide access for components. It is needed to run the startup process, initialize the hardware, and pass control to the kernel, which initializes the operating system.
Click to expand...
Click to collapse
Downgrading bootloader in order to flash custom recovery or root the device is a common practice if the currently installed bootloader can't be unlocked or does not allow flashing TWRP or rooting.
xXx yYy said:
Wondering what sense it would make to downgrade phone's bootloader:
A bootloader helps to load the operating system or runtime environment to add programs to memory and provide access for components. It is needed to run the startup process, initialize the hardware, and pass control to the kernel, which initializes the operating system.
Click to expand...
Click to collapse
Rationally speaking I'd rather stay on stable version of Android 10 OneUI 2.5 than on Android 11 OneUI 3.1. For me, it's buggy and camera quality got worsen. Updated bootloader isn't the issue but it's the reason I can't downgrade my OS.
Droidriven said:
No, you can't downgrade bootloader on Samsung unless the downgraded bootloader has a binary version equal to the binary version of your currently installed bootloader.
Click to expand...
Click to collapse
So now it's impossible in my situation since bootloader versions don't match since September security patch. Now that sucks.
AlanDias17 said:
So now it's impossible in my situation since bootloader versions don't match since September security patch. Now that sucks.
Click to expand...
Click to collapse
That is usually the case for Samsung owners. In the past, downgrading was possible but not on today's device's. It is rare and few and far between that a Samsung can be downgraded these days. Virtually impossible across the board. This is something to consider when buying Samsung devices and when a stock update is possible.
Me personally, I never update a device with stock updates unless things start having issues or stop working due to not updating to keep up with changing technology. I don't update unless absolutely necessary, I put the update off as long as possible.
My current device has been notifying me for months that an update is available but I have it paused so that it doesn't download. Maybe I'll update at some point in the future, maybe not.
AlanDias17 said:
So now it's impossible in my situation since bootloader versions don't match since September security patch. Now that sucks.
Click to expand...
Click to collapse
There is one potential workaround to downgrade, you can try extracting the system.img from the downgraded firmware then convert it to an Odin flashable .tar using 7zip to compress the file .tar format, select the highest level of compression. After extracting the system.img but before converting to .tar, try extracting the system.img itself then find where the kernel is packaged in the system.img then try finding what the binary version of the kernel is, if the kernel's binary version is lower than the binary version of the currently installed kernel, you will not be able to flash the extracted system.img with the kernel packaged inside it, you will have to try removing it then convert to .tar as I described. Once you verified binary versions, convert the file to .tar then flash the system.img.tar.md5 via Odin, place the system.img.tar.md5 in the AP slot.
Basically, it works like this, if you boot into download mode and look at the revision values, you should see something like this:
swREV B: x K: x S: x
B is for bootloader binary version, K is for kernel binary version and S is for system binary version. If B is lower than your currently installed B version, you can't flash it, if K is lower than your currently installed K version, you can't flash it, if S is lower than your currently installed S version, you can't flash it. See if you can find out what the binary version of your currently installed bootloader, kernel and system are, then compare them to the binary version of the downgraded firmwares bootloader, kernel and system. B, K and S can be independent different values, for example, a firmware could have a B value of 4, a K value of 6 and a S value of 5, they do not always all 3 have the same value in a single firmware. Some updates may come with an updated B binary and an updated K binary but not an S binary, or any combination. In my example above, if a device has values of B: 4 K:6 S:5 and that device receives an update that has B:5 and S7 but no updated K value, after flashing, the device would have B:5 K:6 and S:7.
If any of the parts of the downgraded firmware have a binary version that is equal to its corresponding currently installed component, it can be flashed, but if any of them are lower than their corresponding currently installed components, they can't be flashed.
Sorry to be so long winded, just trying to explain how binary version works and can possibly be manipulated to downgrade each individual element, if the binary versions correspond correctl.
Droidriven said:
There is one potential workaround to downgrade, you can try extracting the system.img from the downgraded firmware then convert it to an Odin flashable .tar using 7zip to compress the file .tar format, select the highest level of compression. After extracting the system.img but before converting to .tar, try extracting the system.img itself then find where the kernel is packaged in the system.img then try finding what the binary version of the kernel is, if the kernel's binary version is lower than the binary version of the currently installed kernel, you will not be able to flash the extracted system.img with the kernel packaged inside it, you will have to try removing it then convert to .tar as I described. Once you verified binary versions, convert the file to .tar then flash the system.img.tar.md5 via Odin, place the system.img.tar.md5 in the AP slot.
Basically, it works like this, if you boot into download mode and look at the revision values, you should see something like this:
swREV B: x K: x S: x
B is for bootloader binary version, K is for kernel binary version and S is for system binary version. If B is lower than your currently installed B version, you can't flash it, if K is lower than your currently installed K version, you can't flash it, if S is lower than your currently installed S version, you can't flash it. See if you can find out what the binary version of your currently installed bootloader, kernel and system are, then compare them to the binary version of the downgraded firmwares bootloader, kernel and system. B, K and S can be independent different values, for example, a firmware could have a B value of 4, a K value of 6 and a S value of 5, they do not always all 3 have the same value in a single firmware. Some updates may come with an updated B binary and an updated K binary but not an S binary, or any combination. In my example above, if a device has values of B: 4 K:6 S:5 and that device receives an update that has B:5 and S7 but no updated K value, after flashing, the device would have B:5 K:6 and S:7.
If any of the parts of the downgraded firmware have a binary version that is equal to its corresponding currently installed component, it can be flashed, but if any of them are lower than their corresponding currently installed components, they can't be flashed.
Sorry to be so long winded, just trying to explain how binary version works and can possibly be manipulated to downgrade each individual element, if the binary versions correspond correctl.
Click to expand...
Click to collapse
can you try If it is possible to downgrade like this, I would like to downgrade the s10e and s7 versions. It would be great if you could make a guide for it.
kullanici32 said:
can you try If it is possible to downgrade like this, I would like to downgrade the s10e and s7 versions. It would be great if you could make a guide for it.
Click to expand...
Click to collapse
I don't think you get the bigger picture.
I was not saying "you absolutely CAN downgrade if you do it like this".
I was saying "IF it is even possible, you can TRY doing it like this".
I don't know if it would work or not on your specific model number, there are too many variables involved in whether it will be successful or not.
I don't own this specific model number so I cant test anything to see if it will work, not to mention that I'm not doing all that research or putting that kind of time, work and energy into making anything for a device that I don't own or use.
I've just given the idea and "possibility" of downgrading based on how some other Samsung devices have been able to successfully downgrade the OS(system) by extracting the system.img from the downgraded firmware and flashing the system.img by itself without flashing the rest of the firmware. This is not the same as downgrading the whole firmware, you're only replacing the upgraded system with the previous version of system but only "IF" the binary versions for system and kernel do not conflict.
If you want to know how to do this or if it will even work on your specific model number, you will have to do your own research, your own thinking and your own hard work to figure it out based on how other Samsung owners have done it.
There are threads here that describe doing this on various other Samsung models. They don't all go about it exactly the same, there are differences in the details and methods based on various device specific software requirements and restrictions. You might or might not be successful, you could even brick your device if you get something wrong. Find other threads that describe how others did it and then try the methods that they used but use your firmware files to make the changes that they made.
Droidriven said:
I don't think you get the bigger picture.
I was not saying "you absolutely CAN downgrade if you do it like this".
I was saying "IF it is even possible, you can TRY doing it like this".
I don't know if it would work or not on your specific model number, there are too many variables involved in whether it will be successful or not.
I don't own this specific model number so I cant test anything to see if it will work, not to mention that I'm not doing all that research or putting that kind of time, work and energy into making anything for a device that I don't own or use.
I've just given the idea and "possibility" of downgrading based on how some other Samsung devices have been able to successfully downgrade the OS(system) by extracting the system.img from the downgraded firmware and flashing the system.img by itself without flashing the rest of the firmware. This is not the same as downgrading the whole firmware, you're only replacing the upgraded system with the previous version of system but only "IF" the binary versions for system and kernel do not conflict.
If you want to know how to do this or if it will even work on your specific model number, you will have to do your own research, your own thinking and your own hard work to figure it out based on how other Samsung owners have done it.
There are threads here that describe doing this on various other Samsung models. They don't all go about it exactly the same, there are differences in the details and methods based on various device specific software requirements and restrictions. You might or might not be successful, you could even brick your device if you get something wrong. Find other threads that describe how others did it and then try the methods that they used but use your firmware files to make the changes that they made.
Click to expand...
Click to collapse
Can you put or give us a link to such a thread or post, we will follow the steps for our own device firmware.
What would be a way to use a TWRP backup with a v3 on a device that has say a v5 boot
Packtlike said:
What would be a way to use a TWRP backup with a v3 on a device that has say a v5 boot
Click to expand...
Click to collapse
If using TWRP, you should, "in theory", be able to flash whatever you want, including an older backup.
Droidriven said:
After extracting the system.img but before converting to .tar, try extracting the system.img itself then find where the kernel is packaged in the system.img
Click to expand...
Click to collapse
Could you please explain how do I go about "extracting the system.img iself"?
Droidriven said:
No, you can't downgrade bootloader on Samsung unless the downgraded bootloader has a binary version equal to the binary version of your currently installed bootloader. For example, if the binary version of your currently installed bootloader is binary 4, you can flash the downgraded bootloader if it is also binary 4 but you cannot flash a bootloader that is binary 3, 2 or 1.
Click to expand...
Click to collapse
What does "unless" mean in the first sentence above? I mean, if the only possibility for replacing an installed bootloader is using another bootloader with equal or higher binary version, then we are not downgrading anything, or are we? I am a bit confused.
zogoibi said:
Could you please explain how do I go about "extracting the system.img iself"?
Click to expand...
Click to collapse
Extract the contents from the firmware file to get to the various .img/bin files in the firmware, find the system.img file, extract it's contents to get to the various files/folders in the system img. Then you find whatever parts of the system.img that you want/need then do whatever it is that you need to do with them.
zogoibi said:
What does "unless" mean in the first sentence above? I mean, if the only possibility for replacing an installed bootloader is using another bootloader with equal or higher binary version, then we are not downgrading anything, or are we? I am a bit confused.
Click to expand...
Click to collapse
It means that it is possible to have a firmware that has a lower "bootloader" version than the firmware currently installed on a device but an equal "binary"version as the firmware currently installed. For example, if a device has firmware installed on it that has bootloader "y" with binary 4, they could flash a firmware that has bootloader "x"(x being lower than y) and the same binary 4, equivalent binary but lower actual bootloader version, which downgrades the bootloader version but not the binary version. If it had bootloader "x" but had binary 3 or lower, then, yes, what you say would apply.
Droidriven said:
Extract the contents from the firmware file to get to the various .img/bin files in the firmware, find the system.img file, extract it's contents to get to the various files/folders in the system img. Then you find whatever parts of the system.img that you want/need then do whatever it is that you need to do with them.
Click to expand...
Click to collapse
Thank you. I already got that I have to gut apart system.img. But my question was: how do I do that? Anyway, I already found the answer: using simg2img command to transform system.img to raw format, then loopmounting it. But now, how do I find the kernel file as per your comment above: "find where the kernel is packaged in the system.img" ? There are one thousand files inside, and none of them seem to qualify as the kernel. Besides, on a developer forum I've read that the kernel is not inside system.img, but inside boot.img. And how to gut apart boot.img?
After a good deal of search, it seems I got the answer to that question too: getting a copy of android_booting_tools, which has the command unpackbootimg (since abootimg couldn't do the job and exited with error "not a valid Android Boot image") Once unpacked boot.img, voilá, the kernel is there (and definitely not inside system.img): the file named boot.img-zimage.
BUT!! Now, what do I want the kernel file for, if what I need is to downgrade the bootloader? Your instructions are a bit unclear in that point.
Droidriven said:
It means that it is possible to have a firmware that has a lower "bootloader" version than the firmware currently installed on a device but an equal "binary"version as the firmware currently installed. For example, if a device has firmware installed on it that has bootloader "y" with binary 4, they could flash a firmware that has bootloader "x"(x being lower than y) and the same binary 4, equivalent binary but lower actual bootloader version, which downgrades the bootloader version but not the binary version. If it had bootloader "x" but had binary 3 or lower, then, yes, what you say would apply.
Click to expand...
Click to collapse
OK. I think I understood this part. Thanks.
zogoibi said:
Thank you. I understood what you meant: gut apart system.img. But my question was: how do I do that? Anyway, I already found the answer: using simg2img command to transform system.img to raw format, then loopmounting it. But now, how do I find the kernel as per your comment above: "find where the kernel is packaged in the system.img" ? There are one thousand files inside, and none of them seem to qualify as the kernel. Besides, as I've searched out there, in a developer forum I've read that the kernel is not in system.img, but in boot.img. And how to gut apart boot.img?
It seems I got the answer to that question either: downloading android_booting_tools, which has the command unpackbootimg (since abootimg couldn't do the job and exited with error "not a valid Android Boot image") Once unpacked boot.img, voilá, the kernel is there (and definitely not in system.img): the file named boot.img-zimage.
BUT!! Now, what the heck do I do with the kernel file, if what I need is to downgrade the bootloader? Your instructions are a bit unclear in that point.
OK. I think I understood this part. Thanks.
Click to expand...
Click to collapse
I use 7zip.
You asked how to extract the system.img, not the kernel.
The boot.img is not the bootloader. If you're trying to downgrade the bootloader then you should be trying to use the bootloader, but you may or may not need other parts of the downgraded firmware also in order for the bootloader to not cause the device to hard rock or block the flash. What you would or wouldn't need, I don't know, it usually requires tinkering to find the right recipe. Trial and error, experimenting with mixing different parts of each firmware to see what will or won't work together.
Also, it may require unlocking the bootloader and/or using a modified version of Odin to flash a modified firmware or modified .img files.
That is all "IF" it is even possible or safe to attempt Your milage may vary.
Droidriven said:
You asked how to extract the system.img, not the kernel.
Click to expand...
Click to collapse
I begun by quoting a post where you supposedly explained a 'potential' workaround for downgrading the bootloader (I qhote: "there is one potential workaround to downgrade"). As per your instructions, one should first extract 'system.img itself' in order to get hold of the kernel. And that's why I asked how to do it. Obviously the end point was to find the kernel, as per your instructions. But it turned out the kernel is not in system.img. I wonder what Is, then, the point in that part of your instructions.
Droidriven said:
The boot.img is not the bootloader.
Click to expand...
Click to collapse
Obviously not. I haven't said that. I just said that I found out that kernel is inside boot.img, not inside system.img.
Droidriven said:
If you're trying to downgrade the bootloader then you should be trying to use the bootloader
Click to expand...
Click to collapse
Well, I can also say: "if you're trying to help people downgrading the bootloader (which is the title of this thread), then you should be trying to help people downgrading the bootloader."
Droidriven said:
There is one potential workaround to downgrade, you can try extracting the system.img from the downgraded firmware then convert it to an Odin flashable .tar using 7zip to compress the file .tar format, select the highest level of compression. After extracting the system.img but before converting to .tar, try extracting the system.img itself then find where the kernel is packaged in the system.img then try finding what the binary version of the kernel is, if the kernel's binary version is lower than the binary version of the currently installed kernel, you will not be able to flash the extracted system.img with the kernel packaged inside it, you will have to try removing it then convert to .tar as I described. Once you verified binary versions, convert the file to .tar then flash the system.img.tar.md5 via Odin, place the system.img.tar.md5 in the AP slot.
Basically, it works like this, if you boot into download mode and look at the revision values, you should see something like this:
swREV B: x K: x S: x
B is for bootloader binary version, K is for kernel binary version and S is for system binary version. If B is lower than your currently installed B version, you can't flash it, if K is lower than your currently installed K version, you can't flash it, if S is lower than your currently installed S version, you can't flash it. See if you can find out what the binary version of your currently installed bootloader, kernel and system are, then compare them to the binary version of the downgraded firmwares bootloader, kernel and system. B, K and S can be independent different values, for example, a firmware could have a B value of 4, a K value of 6 and a S value of 5, they do not always all 3 have the same value in a single firmware. Some updates may come with an updated B binary and an updated K binary but not an S binary, or any combination. In my example above, if a device has values of B: 4 K:6 S:5 and that device receives an update that has B:5 and S7 but no updated K value, after flashing, the device would have B:5 K:6 and S:7.
If any of the parts of the downgraded firmware have a binary version that is equal to its corresponding currently installed component, it can be flashed, but if any of them are lower than their corresponding currently installed components, they can't be flashed.
Sorry to be so long winded, just trying to explain how binary version works and can possibly be manipulated to downgrade each individual element, if the binary versions correspond correctl.
Click to expand...
Click to collapse
Hi, I know this thread is quite old. But i have a Rooted Galaxy M23 (SM-M236B) and in odin it says B:2 K:2 S:2. I was waiting for an software update and sawed that there was one update in that it says that is bit is 3, Questions: 1. If I install the bit 3 software i would not be able to install again a 2 bit software? 2. My bootloader is unlocked, does applying the update locks the bootloader? And 3. How do I know if the update makes my bootloader locked permanently?
Mr. Electrinix said:
Hi, I know this thread is quite old. But i have a Rooted Galaxy M23 (SM-M236B) and in odin it says B:2 K:2 S:2. I was waiting for an software update and sawed that there was one update in that it says that is bit is 3, Questions: 1. If I install the bit 3 software i would not be able to install again a 2 bit software? 2. My bootloader is unlocked, does applying the update locks the bootloader? And 3. How do I know if the update makes my bootloader locked permanently?
Click to expand...
Click to collapse
1) yes, if you flash the binary 3 update, you will not be able to downgrade to a 2 binary, UNLESS the bootloader is unlocked and you use "patched Odin" or Cosmy's Odin to flash the downgraded firmware.
2) I don't know if flashing the update will lock the bootloader or not, you would have to research that yourself to see what results other users of your exact same model got after flashing the exact same update build number that your update has.
3) You would have to find other users that have the exact same model number device that you have and find a user that has flashed the exact update that you are asking about.
***Note***
If the update that you are asking about is a atock OTA update via the system update option in system settings, you will have to unroot the device then boot into recovery and wipe the cache partition (but not factory reset) then reboot the device, then do the update via settings. Stock OTA updates cannot safely be applied on devices that have been rooted, modified system partition or have custom recovery installed. You have to have clean, unrooted, unmodified stock firmware with stock recovery.
If you are manually flashing the update via Odin, you do not need to unroot before flashing the update, flashing via Odin "should" take care of that for you, depending on whether the update is a full update with a new system partition or a partial, incremental update.
Droidriven said:
1) yes, if you flash the binary 3 update, you will not be able to downgrade to a 2 binary, UNLESS the bootloader is unlocked and you use "patched Odin" or Cosmy's Odin to flash the downgraded firmware.
Click to expand...
Click to collapse
You can NEVER downgrade the bootloader/binary/bit level, even if you've bootloader unlocked it. OEM Unlock does NOT magically enable you to downgrade the binary
Hi all,
i have updated to latest date android 9 with binary 5. previously i was on binary 2. Now i want to go back to that version of my firmware which had binary version 2 of bootloader. I don't care about my bootloader as i know it can't be downgraded back. I just want to use my previous build firmware with current bootloader. Is that possible ? if yes how can i do that ? What if i extract my old system.img.lz4 file from AP and make it odin flashable and flash it through odin while in download mode ? will i brick my device or not ? pleas advice how can i go back to my previous build of firmware. My phone is Samsung galaxy A6 (SM-A600T).
khalidhotaky said:
Hi all,
i have updated to latest date android 9 with binary 5. previously i was on binary 2. Now i want to go back to that version of my firmware which had binary version 2 of bootloader. I don't care about my bootloader as i know it can't be downgraded back. I just want to use my previous build firmware with current bootloader. Is that possible ? if yes how can i do that ? What if i extract my old system.img.lz4 file from AP and make it odin flashable and flash it through odin while in download mode ? will i brick my device or not ? pleas advice how can i go back to my previous build of firmware. My phone is Samsung galaxy A6 (SM-A600T).
Click to expand...
Click to collapse
Bootloader binary version is not the only binary version that you need to be concerned with. If the binary version of your currently installed system is higher than the binary version of the system binary in the binary 2 firmware, you will not be able to downgrade the system partition.
Your question can be resolved with these simple questions:
1) What is the System binary version of your currently installed system? Boot into download mode and look at your S binary version.
2) What is the System binary version of the firmware that you want to downgrade to?
3) Is the System binary version of the firmware that you want to grade to lower than or equal to your currently installed System binary? If it is lower than your currently installed firmware you can't downgrade, if it is equal to your currently installed firmware then you can downgrade.
Droidriven said:
Bootloader binary version is not the only binary version that you need to be concerned with. If the binary version of your currently installed system is higher than the binary version of the system binary in the binary 2 firmware, you will not be able to downgrade the system partition.
Your question can be resolved with these simple questions:
1) What is the System binary version of your currently installed system? Boot into download mode and look at your S binary version.
2) What is the System binary version of the firmware that you want to downgrade to?
3) Is the System binary version of the firmware that you want to grade to lower than or equal to your currently installed System binary? If it is lower than your currently installed firmware you can't downgrade, if it is equal to your currently installed firmware then you can downgrade.
Click to expand...
Click to collapse
Thank you for your great reply, to answer your question and solve my query i really need your help. the below answers regarding your questions may help you answer me with right solutions.
1. Currently Booted to download mode and found that RP SWREV: B:5 K:5 S:5
2. I EXACTLY DON'T KNOW, but you can find i think from my old firmware's name as it is A600TUVS2BSG1_A600TTMB2BSG1_TMB
3. I think after seeing the above two answers, you may be able to solve your third question by yourself as i am not able to answer you about this one.
let me know if you need any addiontal information, i really want to solve my query and downgrade back to my old firmware, I was able to to downgrade to android 8 with same version of bootloader v5 binary and was hoping that i could be able to upgrade back to my earler PIE, but later i knew that i wasn't able to do so, and that android 8 was a combination firmware which made me happy just for a small period of time.
Regards.
khalidhotaky said:
Thank you for your great reply, to answer your question and solve my query i really need your help. the below answers regarding your questions may help you answer me with right solutions.
1. Currently Booted to download mode and found that RP SWREV: B:5 K:5 S:5
2. I EXACTLY DON'T KNOW, but you can find i think from my old firmware's name as it is A600TUVS2BSG1_A600TTMB2BSG1_TMB
3. I think after seeing the above two answers, you may be able to solve your third question by yourself as i am not able to answer you about this one.
let me know if you need any addiontal information, i really want to solve my query and downgrade back to my old firmware, I was able to to downgrade to android 8 with same version of bootloader v5 binary and was hoping that i could be able to upgrade back to my earler PIE, but later i knew that i wasn't able to do so, and that android 8 was a combination firmware which made me happy just for a small period of time.
Regards.
Click to expand...
Click to collapse
No, you can't flash a binary 2 firmware, your currently installed binary shows that you can only flash a binary 5 or higher firmware. You will not be able to downgrade to the previous version, there is no way to bypass the binary block and there are no tricks to force it to downgrade. You are stuck with what you have, whether you like it or not.
Droidriven said:
No, you can't flash a binary 2 firmware, your currently installed binary shows that you can only flash a binary 5 or higher firmware. You will not be able to downgrade to the previous version, there is no way to bypass the binary block and there are no tricks to force it to downgrade. You are stuck with what you have, whether you like it or not.
Click to expand...
Click to collapse
Thanks from your help, it was so sad to hear that. By the way I am thinking why the system should be the same binary version ? This rule was just added for bootloader I think, and now you are adding also this rule for firmware binary. What's the exact story here. We must be able to downgrade to our old firmwares except bootloader.
Also can you please give your advise if the info on below link is valid or not, Is him lying?
Downgrade from Pie to Oreo
Hi guy's so i was able to downgrade from Pie ( One Ui ) to Oreo ( save your media on your sd card or your PC then you check if they are there ) 1 - Go to TWRP or Recovery to wipe data 2- Download and unzip...
forum.xda-developers.com
khalidhotaky said:
Thanks from your help, it was so sad to hear that. By the way I am thinking why the system should be the same binary version ? This rule was just added for bootloader I think, and now you are adding also this rule for firmware binary. What's the exact story here. We must be able to downgrade to our old firmwares except bootloader.
Click to expand...
Click to collapse
No, bootloader is not the only binary that matters. There is bootloader binary, kernel binary and system binary. Your currently installed firmware has a bootloader binary 5, kernel binary 5 and system binary 5. This means that you can only flash a firmware that has a bootloader binary 5 or higher but not 4, 3, 2 or 1, or a kernel binary 5 or higher but not 4, 3, 2 or 1 and a system binary 5 other higher but not 4, 3, 2 or 1.
In the cases where users have successfully "downgraded" their firmware were not truly downgrading their firmware, they were flashing a firmware that has a lower android version but not a lower binary. For example, they could have an android 10 firmware with 4 binary installed and "downgrade" to an android 9 firmware that also has a 4 binary. In this case they are not "downgrading" the binary version, they are only downgrading the android version. If their currently installed firmware were android 10 with binary 5, they would not be able to downgrade to android 9 with binary 4.
Also, the link you posted is using TWRP to flash a Pie ROM. They are not using Odin to flash a downgraded firmware. They are flashing a custom file that was created to be flashed via TWRP, similar to flashing a custom ROM, this is not the same as flashing a stock firmware via Odin. This would only be useful to you if your bootloader is unlocked and if there is a TWRP for your device and if there is a downgraded firmware for your device that has been modified to be flashed via TWRP. Odin prevents flashing files with a lower binary, TWRP does not, TWRP will let you flash anything that is made specifically for your device and some things that were not made specifically for your device.
There are specific details involved in this that you just aren't understanding. I'm done trying to explain.
Droidriven said:
No, bootloader is not the only binary that matters. There is bootloader binary, kernel binary and system binary. Your currently installed firmware has a bootloader binary 5, kernel binary 5 and system binary 5. This means that you can only flash a firmware that has a bootloader binary 5 or higher but not 4, 3, 2 or 1, or a kernel binary 5 or higher but not 4, 3, 2 or 1 and a system binary 5 other higher but not 4, 3, 2 or 1.
In the cases where users have successfully "downgraded" their firmware were not truly downgrading their firmware, they were flashing a firmware that has a lower android version but not a lower binary. For example, they could have an android 10 firmware with 4 binary installed and "downgrade" to an android 9 firmware that also has a 4 binary. In this case they are not "downgrading" the binary version, they are only downgrading the android version. If their currently installed firmware were android 10 with binary 5, they would not be able to downgrade to android 9 with binary 4.
Also, the link you posted is using TWRP to flash a Pie ROM. They are not using Odin to flash a downgraded firmware. They are flashing a custom file that was created to be flashed via TWRP, similar to flashing a custom ROM, this is not the same as flashing a stock firmware via Odin. This would only be useful to you if your bootloader is unlocked and if there is a TWRP for your device and if there is a downgraded firmware for your device that has been modified to be flashed via TWRP. Odin prevents flashing files with a lower binary, TWRP does not, TWRP will let you flash anything that is made specifically for your device and some things that were not made specifically for your device.
There are specific details involved in this that you just aren't understanding. I'm done trying to explain.
Click to expand...
Click to collapse
Your replies has already made me understand every truth that I was not getting from reading too many articles and on internet forums, you are a really great personality, thanks from your great help and replies. You explained everything very well and after your explanations I am also done with problem. So sad from knowing these rules now. Hope I understood these things before my upgrade. Some people won't get clever like me until first they make a mistake and then know what have they done, anyways it's just not my fault. 50% is Samsung rules blamed for stuff like this. Shame on them for applying these rules on their users. If my phone kept the battery drain issue like this, I will sold it and will switch to iPhone after 17 years of android use. Thanks again mate for your great help.
Regards.
Samsung's downgrade lock is a humiliation to users. Destroying the device's battery consumption is a mockery of the user's intelligence or an abandonment of Samsung's reputation.
ioeg41 said:
Samsung's downgrade lock is a humiliation to users. Destroying the device's battery consumption is a mockery of the user's intelligence or an abandonment of Samsung's reputation.
Click to expand...
Click to collapse
Your statement will not change anything. Accept that the economy is structured to increase sales and profits.