Related
hi, i really want to downgrade my S6 to lollipop but i have one of the latest bootloader (DPFX).
Downgrade was perfectly possible when i was on first build of marshmallow, but now, since i upgraded to DPFX bootloader, i have only fails with odin, and bootloops with custom roms...
is there any solution? if only i could flash an older bootloader, then i will be saved.
but if i flash an old bootloader with odin, i have a fail, so i don't know what to do
Some people suggested to me to use an old TWRP backup and i found it on my pc (with all partitions files: bootloader,system,radio and data, but i didn't use data) but using it, it's the same of flashing a custom rom: bootloop, and i suspect that the old bootloader never was flashed.
help
cescof said:
hi, i really want to downgrade my S6 to lollipop but i have one of the latest bootloader (DPFX).
Downgrade was perfectly possible when i was on first build of marshmallow, but now, since i upgraded to DPFX bootloader, i have only fails with odin, and bootloops with custom roms...
is there any solution? if only i could flash an older bootloader, then i will be saved.
but if i flash an old bootloader with odin, i have a fail, so i don't know what to do
Some people suggested to me to use an old TWRP backup and i found it on my pc (with all partitions files: bootloader,system,radio and data, but i didn't use data) but using it, it's the same of flashing a custom rom: bootloop, and i suspect that the old bootloader never was flashed.
help
Click to expand...
Click to collapse
If you are on a newer mm bootloader then downgrading to lollipop is not possible
sofir786 said:
If you are on a newer mm bootloader then downgrading to lollipop is not possible
Click to expand...
Click to collapse
I knew this, but i want to know if there is a way, a not official way, like reinstalling bootloader in a forced way that doesn't care about security problems... this thing has no sense.... why totally prevent to downgrade? However, i thing it's NORMALLY impossible, but not
TOTALLY impossible
cescof said:
I knew this, but i want to know if there is a way, a not official way, like reinstalling bootloader in a forced way that doesn't care about security problems... this thing has no sense.... why totally prevent to downgrade? However, i thing it's NORMALLY impossible, but not
TOTALLY impossible
Click to expand...
Click to collapse
As far as I know if you're on a newer bootloader official or not there is no current method to downgrade. Maybe a phone shop has specialist equipment to do this but that's me taking a shot in the air
I was able to downgrade but not because i wanted, i flashed a corrupt firmware with ODIN and i have to do an emergency recovery with Smart Switch, my carrier doesn't have Marshmallow on the S6 so my phone restored in Lollipop
Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?
OEM unlock toggle in Developer's Options
Hi ยก...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers
Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME
Skulper said:
Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot
brokboi said:
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot
Click to expand...
Click to collapse
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.
Droidriven said:
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.
Click to expand...
Click to collapse
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex
brokboi said:
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex
Click to expand...
Click to collapse
Have you used TWRP to create a android backup of your stock ROM after you got it fixed? If not, do so, then store a copy of the backup on a PC or USB flashdrive, external sdcard, etc.. That backup can be used to restore your device, if needed.
Hello,
I have a Samsung Galaxy S10e, and recently I've decided to flash a custom ROM on it.
I upgraded from Android 10 Stock Samsung to Android 11 LineageOS 18.1 following this and this guide.
All successful.
However, after some minutes, I wanted to try out a different ROM, so I installed Pixel Experience (which was based on Android 10 -- big mistake). This ended up resulting in a soft brick, throwing me an 'REV Check Fail Device 9 Binary 8' error everytime I turned on the device. I couldn't get into recovery mode - only download mode.
I managed to fix this by waiting for the Samsung's Stock Firmware (based on Android 11) to come out (did after some hours, I was so lucky I didn't have to wait that long) so I could flash it and go back to stock using Odin. All good, the phone boots, everything works as expected -- no problems what so ever.
I should've made a backup in TWRP, in case something went wrong before flashing Pixel Experience (?), but I didn't. I also should've known that I couldn't downgrade. Anyway...
When I enter download mode, the following important info is displayed:
PRODUCT NAME: SM-G970F
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF (U)
Secure Download: Enabled
WARRANTY VOID: 1 (0x0e03)
I believe my bootloader is unlocked, since it's enabled and grayed out in developer otions. I also believe that I have no custom recovery (since I flashed Samsung's Stock Firmware), because when I press the recovery button combination, it doesn't boot into TWRP.
My questions:
1. Should I repeat the process in here when flashing TWRP again since I literally flashed the samsung stock firmware? I'm guess I'm comming from "stock" even though I already have some steps complete? Should I flash the " multidisabler-samsung-2.* " too? I already did once, do I need to do it again since I flashed the Stock Samsung firmware?
2. Is there anything you'd recommend me doing to prevent stupid actions like I had above?
3. As long as I have the Stock Samsung Firmware and the phone boots into download mode, I'm good right?
4. Is TWRP 3.5.0 compatible with the S10e Android 11? Or does android versions not matter with recoveries?
5. Which ROM would you recommend to have a good Pixel-Like Stock Android experience? I'm debating wether I should use the PixelExperience again (I used it on my nexus 5x and was happy with it) or if I should try out something else. I also believe it's not yet available unofficially, so I'd have to wait.
6. Would you recommend me installing a GSI?
Thanks!
Questions updated
bump!
Too bad you didn't get an answer... Did you find anysolution ?
Having issues installing TWRP with odin on a s10e..
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.