In this guide, we will show you various methods to fix the bootloop after doing the ADB Sideload on your Samsung device. There exists quite a few ways through which you can install a firmware on Samsung- with the third-party Odin Tool and ADB Sideload being the two most prominent ones. In this regard, the latter one is the official one and hence is usually the recommended approach for many.
However, as of late, a bunch of Samsung users have said that they are facing a bootloop when trying to install a firmware via ADB Sideload. According to the impacted users, right after the installation, they had to wait on the splash screen for around 10 minutes, after which they were taken to the stock recovery with the following message: “Your phone couldn’t start normally. Some configuration data may be corrupt.” If you are also in the same boat, then this guide will help you out. Follow along for the fixes.
Table of Contents
Fix Bootloop after ADB Sideload on Samsung
There are two ways of getting this job done- without a data loss and via a factory reset. While it’s quite obvious that all of you would prefer to opt for the former method, however, it only tends to work under special circumstances [explained below], whereas the latter one will work across all devices, without any conditions involved. So with that in mind, let’s get started. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device, and data by performing the below steps.
FIX 1: Without Data Loss
This method will only work if you are able to boot to the OS in between the bootloops [in some cases, it might take up to 20 bootloops before you are able to boot to the OS for a few seconds]. So if you are able to boot to the OS as well, then straightaway head over to Developer Options and disable ANGLE. This should fix your issue.
But how did we find out the culprit? Well, we first went through the crash logs of Chrome (because it was failing to render pages). In its stack trace, we noticed that /system/lib64/libGLESv2_angle.so was mentioned. So we went to the Developer Options, turned off ANGLE, and voila, the bootloop was fixed! So, do give it a try and check out the results.
FIX 2: Via Factory Reset
If your device doesn’t boot to the OS even once, then it’s quite obvious that you wouldn’t be able to disable ANGLE. So in that case, you have no other option but to perform a reset from the stock recovery [where your device is currently stuck]. So use the Volume keys to highlight Erase App Data and press the Power key to confirm. See if this workaround spells out success for you or not.
FIX 3: Flash Firmware
If none of the aforementioned methods worked in your favor, then your last course of action is to flash the entire firmware via Odin. Make sure to use the CSC file instead of the Home_CSC file when you load the files in Odin [this process will wipe off all the data from your device].
That’s it. These were the three different fixes that should help you fix the bootloop issue on your Samsung device when trying out ADB Sideload. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution as soon as possible.
