Stuck in a boot-loop after the Oreo update? Here’s how you can stop bootloop in Samsung Galaxy S8. Samsung started rolling out Android 8.0 Oreo update for Galaxy S8 and S8+ earlier this month. However, the update was stopped after number of users reported the bootloop issues. Even though an update to fix the solution are in process, here is how you can deal with the annoying issue.
Bootloops are where your device repeatedly attempt to reboot until the power is disconnected or the damage is repaired where a device can successfully boot up. If your device restarts over and over, here are few tips and tricks you can try to stop your device from rebooting.
#1. Enter Recovery Mode To Stop Bootloop
Since, bootloops don’t allow your device to boot up, you will need to enter recovery mode (safe mode). To enter recovery mode:
- Power off the device.
- Hold Bixby button+ Volume up button and Power button until “Samsung Galaxy S8” or “Samsung Galaxy S8+” appears
Now, all you have to do is wait. The screen will say “Installing system update” for a few seconds. Just ignore them and wait about 30-90 seconds until it will says “No command” and enters Android Recovery Mode.
Also Read: How To Hard Reset Samsung Galaxy S8 And Galaxy S8 PlusAndroid 8.0 Oreo™ – Bluetooth IssuesHow to use Swipe Function in Outlook
#3. Restore Factory Settings
If the bootloops still continue, get prepared to let go of all the data in your device. Usually, we recommend to back up your data before restoring factory settings. However, since your smartphone restarts over and over, you can possibly not back up the data. To restore factory settings:
#2. Clear the cache partition
Recovery Mode allows you to perform a select few basic functions. Here, to stop bootloop, clear the cache partition. Here’s how you can do it.
- Using the Volume Up and Down keys, navigate to “Wipe cache partition“
- Press Power button to confirm the selection, then your smartphone will reboot
Your device should now stop boot-looping. If this doesn’t work, you can always try the next method.
- Enter the Recovery Mode
- Using the Volume Up and Down keys, navigate to “Wipe Data / Factory Reset“
- Press Power button to confirm
- Select “Yes” using Volume keys and confirm with Power Button
- Select “Reboot System Now”
After the phone restarts, your phone will get out from the bootloop. However, you need to set up your Galaxy device from the start.
Did you successfully stop bootloop in your Samsung Galaxy S8 and S8+? Let us know in the comment section below if you have any issues recovering your device.
- TAGSAndroidAndroid FixAndroid How toandroid oreoGalaxy S8Galaxy S8 PlusHow toSAMSUNGSamsung GalaxySamsung Galaxy S8Samsung Galaxy S8 PlusSystem Update
How to Fix Samsung Galaxy S22 Overheating?
How to Fix Mobile Data Not Working on Samsung Galaxy S22?
Instagram Tips and Tricks
How to See Liked Posts on Instagram?
How to Make Android Faster?
What To Do When Android Buttons Stop Working?
- Daniel Martine
- July 6, 2018 At 7:14 am
- Samsung Galaxy s8 will be the most powerful way to get the entire process fro the Firefox Support that they can tell you the best.
- Reply
- Lekeisha Lyle
- April 15, 2019 At 11:19 pm
- i have tried all these methods. nothing has worked, i updated to the new update, phone restarted came back on, and then said finishing update, from there it kept restarting, and never finished the download. so i did all of the following steps above, and now it will not come on pass the Samsung galaxy 8 display screen. please help. i would have never installed this update if i knew this would have happened.
- Reply
2 COMMENTS
Samsung Galaxy s8 will be the most powerful way to get the entire process fro the Firefox Support that they can tell you the best.
i have tried all these methods. nothing has worked, i updated to the new update, phone restarted came back on, and then said finishing update, from there it kept restarting, and never finished the download. so i did all of the following steps above, and now it will not come on pass the Samsung galaxy 8 display screen. please help. i would have never installed this update if i knew this would have happened.
