bu başlıkta ingilizce konuşacağız

Now most advanced users have had been asking if we can then be able to downgrade our owned Galaxy S6 or Galaxy S6 Edge running on Android 5.1.1 update and return it back to the old Android 5.0.2 firmware. The direct answer is No! Why is that and how come Samsung implemented that policy which some folks from Android community might disagree?

There are some good reason why some folks prepared an Android smartphones instead of something else. One of these main reason is that they liked on tinkering and tweaking their devices. People that used to loved into rooting installing custom OS, so they can install any 3rd party apps that requires a rooted device before it can be actually installed. Whilst using a customized OS rectified the device the way how it look and feel according to the owners liking.

Why we are not allowed to downgrade the Galaxy S6 from Android 5.1.1 to 5.0.2?
The answer resides how the Android 5.1.1 update being built. It has now added with a secured “bootloader” which is only a part of the whole Android ecosystem. There are also some several factors like the updated security patches against its vulnerability to thieves and other apps exploitation. All of it is for the sake to improved the device security, no matter if the owners might disagree or not.

What will happen if we downgrade our Galaxy S6 from Android 5.1.1 back to 5.0.2?
If one had to forcefully downgrade his/her Galaxy S6 from Android 5.1.1 to 5.0.2 it cause into a serious problem. Doing so well just ended-up the device into a sudden soft-brick status. The device will just stays in boot loop and just stuck in Samsung logo. It couldn’t boot normally to the home screen and will just stay in the welcome screen no matter how many times you turn it off and on. And even doing a factory reset will not tend to work and cannot fix the problem.

Basically, we may say that there is something on the Android 5.1.1 update that prevents from installing back the previous Android 5.0.2 version. Instead, it will only causes a mismatch error to the new Android 5.1.1 firmware and that is how the device basically experiencing a soft-brick status. But in technical aspects, the soft-brick problem occurs because the new Android 5.1.1 has an updated “boot loader” version. Adding to that it is the new “Kernel” version it uses. Flashing back the old Android 5.0.2 that still holds the old “bootloader” and “Kernel” version will not work.