A question to SAMSUNG users!

  • Thread starter Thread starter JuanMena
  • Start date Start date
  • Views Views 423
  • Replies Replies 4

JuanMena

90s Kid, Old Skull Gamer & Artist.
Member
Joined
Dec 17, 2019
Messages
6,191
Solutions
5
Reaction score
26,041
Trophies
4
Age
32
Location
the 90s
XP
19,186
Country
Mexico
Okis... I'll try to be brief:
- Got a SAMSUNG Galaxy A03, 32GB for cheap.
- The next day got a SAMSUNG Galaxy A03, 64GB for cheap.

- 32GB works fine. Got it second hand and "unlocked".
- 64GB works "fine". Got it second hand and "unlocked".

- 64GB has a weird issue in which if you plug Headphones/Earbuds, sound does come through them, but when I unplug them the phone won't route audio back to the speaker. It's in "earbuds mode" until I press the square icon to "close/open" the app in use THEN audio works through speaker again.

- Thought damaged 3.5mm Jack... opened the phone, resoldered the 3.5mm Jack, didn't fixed it.
- Thought that maybe the "unlocked" process was glitching the phone, so with the aid of ChatGPT I downloaded the required tools to reflash a legit Firmware Image for the phone (Frija + Odin) and EVEN THIS DIDN'T SOLVED THE ISSUE.

- Sister brought up something interesting... what if it's a SAMSUNG bug/glitch that can only get fixed by a new Firmware Update?

So I'm asking! DOES ANYONE HERE HAS HAD THE SAME ISSUE WITH SAMSUNG BEFORE? Specially this particular model!

If yes, then I can literally rest in peace and I'll wait for SAMSUNG to actually address this after I ruled out Hardware/Software/Firmware issues.

The phone is using One UI 5.1 and Android 13.
Oddly enough the 32GB one doesn't has this issue 🤔

Fixed Audio not coming from 3.5mm Jack in "my" SMASNUG Galaxy A03:

View attachment 519837

Connecting earbuds didnt routed sound through them, issue was cold solder points.
 
inb4 EDIT:

1- Yes, Factory Restart did nothing.
2- NO, THE AUDIO JACK ISN'T DAMAGED.
3- Yes, I literally opened the phone, I have the required skills to fix most hardware related problems.
4- NO, LITERALLY REFASHING THE OFFICIAL SAMSUNG FIRNWARE DIDN'T EVEN SOLVED THIS.
5- Just want to know if I'm not the only one with the "issue", THEN I'll stop trying dumb shit... I literally almost bricked the phone entirely after the first Odin reflash failed.
6- Yes, recording videos does record sound. Yes, recording voice works fine. It's just with media reproduction when this issue appears.

Just asking because all my searches leads to:
- Huur factory reset.
- Huur use this app to reroute.
 
Does it also happen with USB-C or BT?

Unfortunately I don't have a recent Samsung phone with a headphone jack, but I haven't had this issue with my BT earphones/headphones.
 
Does it also happen with USB-C or BT?

Unfortunately I don't have a recent Samsung phone with a headphone jack, but I haven't had this issue with my BT earphones/headphones.
Haven't checked because I'm not a fan of Bluetooth nor Wireless stuff, but now that you mentioned it, yeah, I have yet to check that.

Will tell my sis, she's an avid Bluetooth user.
 
3- Yes, I literally opened the phone, I have the required skills to fix most hardware related problems.
Your self-confidence isn't an issue at least. :)
Two phones from the same hardware series running the same version should almost rule out a software/firmware issue (regardless of the eMMC size). There might be something else broken on the lanes than the headphone jack or the solder joints.
My guess: hardware issue.
1- Yes, Factory Restart did nothing.
Religious sacrifices of user data rarely solve problems. Okay, it can on Android phones (after playing around with ADB) opposed to Nintendo consoles, but in this case it sounds unlikely.

I literally almost bricked the phone entirely after the first Odin reflash failed.
It is hard to brick Odin mode itself. If you're using the correct flash file you might end up with a bad flash (error, disconnected early) but unlikely to destroy Odin.
On the other side:
[…] so with the aid of ChatGPT […]
It wouldn't be too surprising if a glorified LLM finds a way of giving so extremely bad instructions that something like this happens.

If yes, then I can literally rest in peace and I'll wait for SAMSUNG to actually address this after I ruled out Hardware/Software/Firmware issues.
You are actually expecting Samsung doing anything more than the minimum which is required according to Android Security Bulletins? For a device from the A series? And one considered to be almost obsolete? You'll be lucky if you receive a final patch. It is overdue (last update I could find has February 2025 patchlevel).
https://security.samsungmobile.com/workScope.smsb

Careful with updating Samsung devices if you like tinkering. With One Ui 8 they killed all bootloader unlock possibilities and nothing stops them from doing the same with seemingly end of life devices for no reason.
 

Site & Scene News

Popular threads in this forum