X

Firmware news

Galaxy A3 (2017) Oreo update might be causing random reboots and bootloops for some users

For all the time Samsung has taken to get the Android 8.0 Oreo update for its devices out the door, it’s rather unfortunate that it hasn’t been an entirely smooth ride. The Galaxy S8’s Oreo update was halted because of a random reboot issue encountered by some users, and the same problem was later discovered in the Oreo update for the Galaxy S7. While Samsung has since resumed the updates for both its 2016 and 2017 Galaxy S flagships, it turns out random reboots and bootloops might also be affecting Oreo on the Galaxy A3 (2017).

Public Wi-Fi networks to blame for the random reboots?

GalaxyClub has heard from a few users that their Galaxy A3 (2017) either got stuck in a bootloop right after the update or started restarting on its own. Pretty much what Galaxy S7 and S7 edge users faced after upgrading to Oreo, indicating a serious underlying problem in Samsung’s generic code for the latest version of Android.

That’s apparently just the bootloops, though. Some users on the Samsung Community forums say the reboots happen when connected to some Wi-Fi networks, such as those supplied by the eduroam international roaming service for students in European universities. At least one user says the phone works fine on his or her home Wi-Fi network, so public Wi-Fi networks like eduroam may to be to blame for the reboots.

But while one can avoid connecting to such Wi-Fi networks, those who have their phone stuck on a bootloop after installing Oreo aren’t so lucky. Samsung had suggested Galaxy S7 owners to take their device to a local support center to get it fixed without losing all data, but there’s no guarantee the data will remain intact.

Those who cannot hop down to a support center can attempt to fix the device through recovery, which also requires a data wipe. To make it worse, the company hasn’t acknowledged the issue yet, although one of the forum moderators has asked a user for more details so we should hear something soon.

Refrain from installing the update if you haven’t already

In the meantime, you should refrain from installing the update if you haven’t already, until there’s an official all-clear from Samsung. The fixed update would be different from the one currently going out, but since there is no confirmation yet on whether the rollout has stopped, it’s best to steer clear if you have a Galaxy A3 (2017).

Have you run into issues on Oreo on your A3 (2017)? Let us know in the comments!

10 Comments

Sign in »

10
Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

adamao
adamao

the wifi in my a3 2017 is going crazy random reboots wtf is that

androidcbyn
androidcbyn

My galaxy tab s3 SM 820 TM got stuck in a bootloop where I was not even able to reboot into recovery mode. I had to flash back to stock rom with Odin. I am on a private network so that was not the issue at least in my case. My battery was below 50 but not critically low (can’t remember exactly).

Very disappointed with Samsung.

Raees777
Raees777

WTAF Samsung…Oreo was released in August 2017. Its been 9 months and there are still issues??? I mean I personally have an S6 still but if Samsung keep this up I may no other choice but to switch. I mean come on, this happened to the s8 and s7 and you still haven’t fixed it?!?! surely they thought something is wrong with all our oreo builds right? Idek why I’m ranting on right now :/

madness67
madness67

Hy everyone
Do you have an issue on your Galaxy A 5 2017 With oreo. I’ve one of the bigest
issue. When i play to summonerswar sometimes I’ve a screen refresh wich make the game in pause. Reset the Phone and delete the game not solved the problem. The only solution is stay on nougat With a downgrad With odin.
Do you have This kind of issue ?

Sotirisdim4
Sotirisdim4

A3 2017 here, no bootloops or issues whatsoever on oreo. Although one weird quirk is that the shutdown animation has been changed to the one used back in Marshmallow

kukom6
kukom6

Issue happens when you connect to the wifi which is in 2.4Ghz and 5ghz under the same name (ssid)

sandrokl
sandrokl

Will Samsung ever be able to release an update to Oreo without bootloops issues!?

tizen99
tizen99

They’ve already released Oreo updates for the Note 8, Tab S3, A5 (2017) and A7 (2017) without bootloop issues.

madness67
madness67

Hy do you play to summonerswar ? And do you have any problems to run the game since u have update ur Galaxy A5 from nougat to oreo ?

androidcbyn
androidcbyn

Wrong on S3. See my comment above