r/SamsungSupport

There's some files that I really want to transfer from my old phone, I think it's a S7, but I'm not 100% sure. However, the phone is dead, and it doesn't charge, whenever I try and charge it, nothing happens for a while before there's loud buzzing and an yellow exclamation mark. Similarly, when I try and connect with cables between this phone and my new phone nothing happens at all.

Is there a way (preferably free or very cheap) to be able to transfer files from my dead phone in these circumstances?

Query Identification: 01098172 (INCLUDE THIS IN YOUR POST! THIS IS AUTO-GENERATED FOR YOU!)

Title: [Galaxy] Transferring Files from Dead Phone

Description: There's some files that I really want to transfer from my old phone, I think it's a S7, but I'm not 100% sure. However, the phone is dead, and it doesn't charge.

Things I have tried: whenever I try and charge it, nothing happens for a while before there's loud buzzing and an yellow exclamation mark. Similarly, when I try and connect with cables between this phone and my new phone nothing happens at all.

Device Name: Galaxy S7, I think

Device Model Number: Don't see one on the back of my phone.

Best regards,

r/SamsungSupport Query

Query Identification: 01098172

Title: [Galaxy S24 Ultra – Incoming VoLTE calls receive 180 Ringing then CANCEL cause=600 "Busy everywhere"]

Description:

I have an intermittent incoming-call failure on an Australian Galaxy S24 Ultra on Optus. It affects multiple callers and appears strongly location-dependent, but mobile data continues working and the handset remains registered for Optus VoLTE/IMS.

I have captured the failures in multiple Samsung Developer Options bug reports.

The failed calls consistently show this IMS/SIP sequence:

IN: INVITE

Handset enters RINGING

OUT: SIP/2.0 180 Ringing

Approximately 0.8–1.0 seconds later:

IN: CANCEL Reason: SIP;cause=600;text="Busy everywhere"

OUT: 200 OK to CANCEL

OUT: 487 Request Terminated to the original INVITE

Only AFTER receiving the CANCEL does Android/Samsung record:

ImsReasonInfo: CODE_REMOTE_CALL_DECLINE (1404)

Samsung code: 3009 / INCOMING_REJECTED

Therefore the handset appears to successfully receive the incoming VoLTE INVITE and return 180 Ringing before subsequently receiving a remote/network-side CANCEL.

The problem has been reproduced with at least three different originating phone numbers.

Samsung/Android call filtering in the captured failures shows DND false, number NOT BLOCKED, direct-to-voicemail Allow, and no identified local automatic rejection.

I specifically investigated Samsung Call & Text on Other Devices/CMC because CMC activity appeared in the logs.

Calls + Texts ON: failed. Calls OFF / Texts ON: failed. Calls + Texts OFF: failed.

When Call on Other Devices was disabled, the CMC voice-fork attempt disappeared from the logs, but the primary incoming call still failed with the identical:

INVITE → 180 Ringing → inbound CANCEL cause=600 "Busy everywhere" → 487 Request Terminated

Therefore CMC voice forking does not appear to be required for the failure.

During controlled testing I captured successful and failed incoming calls while moving between locations. The fault can transition from working to repeatedly failing within 1 km of home.

I subsequently captured repeated failures while returning home, followed by a successful incoming call without rebooting, toggling airplane mode, or manually resetting the network between the failures and success.

The successful call was confirmed in the Samsung logs as VoLTE, not Wi-Fi Calling/ePDG.

Optus has recorded the SIP sequence above, including three affected originating phone numbers, and has escalated the issue to its back-office team.

Samsung has also been sent a Samsung Members Error Report with system logs.

My main technical question is:

What could cause/trigger the inbound SIP CANCEL with cause=600 "Busy everywhere" approximately one second after the handset has already accepted the terminating INVITE and returned 180 Ringing?

I am particularly interested in whether this could originate from Samsung's IMS/modem behaviour, another forked terminating branch, or the carrier IMS network.

Things I have tried:

• Restarted phone multiple times.
• Confirmed phone/software fully updated.
• Deleted and reprovisioned Optus eSIM twice.
• Checked/reset mobile network and call settings.
• Tested 5G/4G Auto and 4G preferred – no change.
• Tested Wi-Fi Calling on and off – no change.
• Checked call forwarding – none configured.
• Checked call barring – none enabled.
• Checked FDN – disabled.
• Checked DND, blocked numbers, direct-to-voicemail and Samsung call filtering – no local rejection identified.
• Tested with car Bluetooth connected and disconnected – failures with both.
• Tested Call & Text on Other Devices with Calls + Texts ON, Calls OFF/Text ON, and both OFF – failures in all configurations.
• Troubleshot separately with Samsung support.
• Completed troubleshooting with Optus technical support.
• Tested incoming calls from at least three different phone numbers.
• Conducted controlled mobility testing with repeated incoming test calls.
• Generated 7 Samsung Developer Options bug reports around successful and failed calls.
• Confirmed handset remains Optus VoLTE/IMS registered during captured failures.
• Confirmed successful comparison call was VoLTE rather than Wi-Fi Calling/ePDG.
• Submitted Samsung Members Error Report with system logs and relevant SIP findings.
• Optus has escalated the fault to back office.

Have not yet tried sacrificing a goat while leaving it on charge for an hour.

Device Name: [Samsung Galaxy S24 Ultra]

Device Model Number: [SM-S928B]

Best regards, u/Hellrazed

Título: S23 Ultra

Consulta: 01098172

Descripción: Buenas, ayer la pantalla de mi móvil dejó de encender. Esta mañana la alarma ha sonado, por lo que parece que el problema es específicamente de la pantalla. Ahora mi drama es rescatar todas las fotos 🥲, ya que no tengo ninguna copia hecha. ¿Conocéis alguna forma de hacerlo?

Cosas que ya intenté:

- cargar batería

- intentar apagar y encender

- reinicio forzoso con los botones de bloqueo y volumen

- acceder desde el ordenador con un cable y un hdmi. Me deja ver la información pero me pide autorización para descargarlo y no la puedo ofrecer al no tener acceso al teléfono.

- EN Find My Mobile aparece como apagado, aunque si consigue ubicarlo donde está.

Nombre del dispositivo: Samsung S23 Ultra

Número de modelo del dispositivo: SM-S918WZKFXAA

Gracias, /Hirondelle20.

r/SamsungSupport Query Query Identification: 01098172

Title: Galaxy XCover6 Pro

Description: Bluetooth forces Quick Share visibility back on with no way to keep it off. When Bluetooth is off, Quick Share "Who can share with you" correctly shows "No one." But turning Bluetooth on for anything unrelated (headphones, car, etc.) silently restores my last sharing setting without asking — forcing me to manually reset "No one" every time. This is a real privacy/UX issue since the phone becomes discoverable again whenever Bluetooth is used for anything else.

Things I have tried: Raised this directly with Samsung Support — their reply confirmed the behavior but offered no fix, only generic troubleshooting (update software, review settings, restart device).

Device Name: Galaxy XCover6 Pro

Device Model Number: SM-G736W

Best regards, u/Ok-Monk-327

I have a Sony Google TV connected via ethernet to my home network.

I have a Samsung S24 Plus using Wi-Fi. I use the smart view mirror screen in the notifications panel and I can cast my screen to the TV

I have a Samsung A8 tablet using Wi-Fi. it is using the same WI fi as the phone. When I use smart view mirror screen it cannot find the TV but it finds some neighbor TV's

because they are both using WI fi and the TV is connected via ethernet and does not have WI fi turned on, I don't think it is the TV's problem?

Query Identification: 01098172 (INCLUDE THIS IN YOUR POST! THIS IS AUTO-GENERATED FOR YOU!)

Title: Samsung

Description: as above

Things I have tried: reboot, pressing it again and again and again, there are no updates, the battery is completely full

Device Name: Samsung A8

Device Model Number: sm x205

Best regards, u/Seppu477

Query Identification: 01098172

Description:

My Galaxy Tab S10 FE Wi-Fi has a strange touchscreen issue. After a reboot, finger touch works perfectly and the touchscreen passes the Samsung Members diagnostic with no dead areas or missed inputs.

However, after the tablet has been locked/asleep for a while, touch still works normally on the lock screen — I can swipe to unlock and interact with lock-screen widgets — but immediately after unlocking, finger touch stops responding completely. The S Pen continues to work.

The tablet was originally purchased in China with CHN firmware (X520ZCS8CZF2). On the original Chinese firmware, the issue was slightly different: finger touch would sometimes stop working after using the S Pen, but locking/unlocking the tablet usually restored it.

I later clean-flashed official Samsung international OXM firmware. I am currently on Android 16 / One UI 8.5, build X520XXS9CZG3. The device is stock, with a locked bootloader and Knox 0x0.

The problem can now occur even without using the S Pen.

Things I have tried:

Clean installation of official Samsung OXM firmware

Updated to X520XXS9CZG3

Tested touchscreen with Samsung Members immediately after reboot — passes completely

Tested without case, keyboard cover, or other magnetic accessories

Tested without using or attaching the S Pen

Restarting temporarily restores normal finger touch

Confirmed that touch still works on the lock screen when the issue occurs

Device Name: Galaxy Tab S10 FE Wi-Fi

Device Model Number: SM-X520

Best regards,

u/augustaklug

Query Identification: 01098172

Title: Samsung Galaxy S21 FE

Description: As of recently I've had charging problems on my S21FE. I get the message: "Check your charger connection." Recently it also began beeping loudly saying something about moisture and the charger, but it has not been exposed to moisture.

Things I have tried:

• It's not dirt or lint, I checked and cleaned the port, there was nothing in it. It is never carried out of the house.
• Other Samsung phones from visiting friends and family charge fine with the block.
• It happens with different chargers too. I tried different cables/chargers, that makes no difference.

Device Name: Galaxy S21 FE

Device Model Number: SM-G990B/DS

Best regards, Saratje

Query Identification: 01098172

Hey all!

Looking to get some help.

I placed a large order with Samsung for their Z fold 8 and Ultra2 watch promotion, and the next day the same combo dropped by nearly $400 in price.

The chat won't let me talk to a supervisor, nor will the phone operators and they keep saying I won't qualify and I should just cancel and re-order my stuff even though the way their system works, once you place an order it saves your account as having taken advantage of a promotion already.

How do I get ahold of an actual supervisor? It's kind of insane that I don't even have my order yet, the price has dropped by $400, and customer support is telling me "tough luck" or "just cancel your order".

r/SamsungSupport Query

Query Identification: 01098172

Description: [i found the phone, i plug it in and it starts to boot into the samsung screen without any input, then it changes to a no command screen for under a second then repeats. ]

Things I have tried: [tried odin and that failed, tried to get into recovery page but no response to button presses.]

Device Name: [Galaxy note 8]

Device Model Number: [SM-N950U]

Best regards, [u/hi_this_is_my_name]

Query Identification: 01098172

Title: Samsung Z flip 7

Description: I've had a Z flip 7 for about a month now and I'm having issues with my phone calls. People I call say that my voice is constantly dopping out of the call. I have tested this by calling my partner's phone and if I talk quietly, my voice doesn't come through the call at all, and if I talk loudly, my voice does come through the call but is constantly dropping out. I've seen that people maybe have this issue with other samsung phones too so I'm hoping someone might know a fix!

Things I have tried: So far I have tried

- restarting my phone

- running the phone in safe mode

- enabling and disabling wifi calling

- calling through whatsapp and directly through my phone

- 2 different sim cards

None of these fixed my issue.

I have also tested my microphone on the voice recorder app (no issues in the playback). I have had people say that my audio sounds a little better when I'm using my headphones.

Device Name: Z flip 7

Device Model Number: SM-F766B

Best regards, Pilpie94