[Q] Headset jack issues - Samsung Galaxy S7 Questions and Answers

I've had an issue with the headset jack on my G930F that I've been trying to diagnose with no luck.
The symptoms:
* Using regular headphones I get no sound from the headset jeck. Doesn't matter what set I use, and I've checked all sets in other devices.
* Using the Samsung headphones with a mic that come with the phone, I get sound as long as the volume is set below about 1/3 of the total volume range.
* Above 1/3 volume, the sound immediately goes to static, and often the phone thinks I've pressed the button on the microphone for voice input.
The history:
* I just purchased this phone off eBay a few weeks ago. It was in near perfect stock condition. No scratches, rub marks, or anything else.
* I immediately started trying root and different ROMs on it. Ended up with SuperStock Kernel and SuperStock ROM with a US AT&T CSC before discovering the headset issue.
* Does not appear to be any physical issues with headphone jack. I get a very solid click as any headphone jack is put in. No lint or anything inside the jack. Plugs appear to be fully inserted into the jack.
* The fact I can get some sound at low volumes would indicate to me that's it's a software issue of some sort, though that doesn't explain why a standard headset without a microphone doesn't work.
* None of the equalizer settings seem to change anything.
* I've tried backing up the phone and completely resetting it to stock firmware, even going back to the earliest version of Nougat that I could find. Behavior is exactly the same. Tried to go back to Mashmallow ROM's, but no luck downgrading further.
Has anyone else had a similar issues with headphone audio? Are there any other settings or software that I could try? I've returned to SuperStock ROM and Kernel, so root isn't an issue.
I know the headset jack is relatively easy to repair, but I'm hesitant to open the otherwise mint condition phone for that if I don't know if will fix the issue.
Thanks,
Jason

How were you resetting the firmware? All 4 firmware files (BP, CSC, AP, CP) via Odin?
I know that having a bootloader firmware version that doesn't match your Android version can cause various sound issues.

Beanvee7 said:
How were you resetting the firmware? All 4 firmware files (BP, CSC, AP, CP) via Odin?
I know that having a bootloader firmware version that doesn't match your Android version can cause various sound issues.
Click to expand...
Click to collapse
Yeah, grabbed the official versions with the original BTU CSC and updated all the firmware files with Odin. No luck on the headphone sound. Is there a block on going back to Marshmallow once a phone has been updated to Nougat?
When I change back to the Superstock Kernel and ROM, I install TWRP and then use the Aroma installer to put in the newest BP and CP with the ROM, then use the CSC Select tool to change the CSC to US AT&T, and finally restore a backup of the original EFS partition.

Nah no limits, I've gone between MM and N and back a few times. Updato.com as all the versions with all firmware files if you want to roll back.

Beanvee7 said:
Nah no limits, I've gone between MM and N and back a few times. Updato.com as all the versions with all firmware files if you want to roll back.
Click to expand...
Click to collapse
Hmmm....odd. I kept getting errors in Odin when I tried the version of MM that I grabbed from sammobile.com. I'll have to try again just to see, though I still don't know why I would have an issue with stock N ROM.
I didn't even think to try the headset jack right when I got it. Obviously I tripped Knox when I did TWRP and root, but that shouldn't any effect on the audio.

Yea shouldn't do, I've got TWRP, root and used SuperMan N without issue, but am currently on SuperMan MM.

Related

No sound or microphone outside of a phone call

No audio comes across speaker while playing music, etc.. Microphone also only works in a call. Google Now, etc. can't hear me talk.
I've tried different firmwares(via odin), kernels, and roms. No luck. Tried on both Lollipop and Marsh mellow. Anyone seen anything like this or have any ideas on solution? I figure its got to be software related since the speaker/mic work in the phone app once a call is initiated.
TeamHackura said:
No audio comes across speaker while playing music, etc.. Microphone also only works in a call. Google Now, etc. can't hear me talk.
I've tried different firmwares(via odin), kernels, and roms. No luck. Tried on both Lollipop and Marsh mellow. Anyone seen anything like this or have any ideas on solution? I figure its got to be software related since the speaker/mic work in the phone app once a call is initiated.
Click to expand...
Click to collapse
Well, you can start by telling us the model of your device (some people post in the wrong place)
We also need to know the firmware versions you've tried and what you wiped, if you wiped, kernels, mods, roms....etc.
Odin to stock. Factory reset.
N920T. I tried latest official Odin and T-Mobile leak from November i think. Updated bootloader and all. Which exact firmware do you think I should try? Forgot what I bought it with.
Sent from my SM-N920T using Tapatalk
Aoge
flashes in odin failing. keeps returning with SW REV CHECK FAIL DEVICE:2 BINARY:1
tried smartswitch, odin, and klies, flashing firmwares the whole time. tried all tmo ones. i think error is due to me updating bootloader to MM. Is it possible to downgrade BL?
TeamHackura said:
tried smartswitch, odin, and klies, flashing firmwares the whole time. tried all tmo ones. i think error is due to me updating bootloader to MM. Is it possible to downgrade BL?
Click to expand...
Click to collapse
Yes it is.. and you can get the bootloader only in a thread somewhere around here ..just Google cokc boooader
TeamHackura said:
tried smartswitch, odin, and klies, flashing firmwares the whole time. tried all tmo ones. i think error is due to me updating bootloader to MM. Is it possible to downgrade BL?
Click to expand...
Click to collapse
You still haven't said if it's rooted or has a custom rom, custom recovery or anything. We can't help you unless you give us the information we need.
Do you have a custom recovery installed?
Sent from my SM-N920T using Tapatalk
So i have pretty ,muc h flashed every single TAR, ZIP, ROM, Kernel, etc. that can be flashed. I just bought a Nexus 6P and now i figured out the issue. After flashing Roever loco rom i forgot to install a small app used to control one of those headphone plug button things. without app it makes it think it has headphones plugged in without actually stating such. pulled out the headphone button thing and all is well. thanks guys.

[Completed] Calling issue on Note 2

I have googled, dug deep through XDA, went round in circles flashing modems, roms, kernels, everything i can (including stock rom), but I cannot seem to fix my note II. It is a T889 T-Mobile version, rooted, and flashed with TWRP 3.0.2.x I am running Revolution Remix 6.0.1 Marshmallow, and for the life of me I cannot figure out why I can't make calls. I attempt to make a call and i get no dial tone, however the call does connect and go through, but nor I or the person on the other end can hear anything at all. I have ran multiple system information checks and I have a valid IMEI, which is the original IMEI, i do not have a CSC code if that means anything, I have no access to any USSD codes, however I do have full SMS/MMS/Data (even hotspot) services. This phone was updated to the COH4 4.3 OTA before root, and TWRP flash. I have had zero issues flashing any rom for this device, GAPPS flashes fine, SuperSU and so on. I would very much like to be able to regain the ability to make calls so if anyone could help me that would be fabulous. Thanks!
Xenocide21 said:
I have googled, dug deep through XDA, went round in circles flashing modems, roms, kernels, everything i can (including stock rom), but I cannot seem to fix my note II. It is a T889 T-Mobile version, rooted, and flashed with TWRP 3.0.2.x I am running Revolution Remix 6.0.1 Marshmallow, and for the life of me I cannot figure out why I can't make calls. I attempt to make a call and i get no dial tone, however the call does connect and go through, but nor I or the person on the other end can hear anything at all. I have ran multiple system information checks and I have a valid IMEI, which is the original IMEI, i do not have a CSC code if that means anything, I have no access to any USSD codes, however I do have full SMS/MMS/Data (even hotspot) services. This phone was updated to the COH4 4.3 OTA before root, and TWRP flash. I have had zero issues flashing any rom for this device, GAPPS flashes fine, SuperSU and so on. I would very much like to be able to regain the ability to make calls so if anyone could help me that would be fabulous. Thanks!
Click to expand...
Click to collapse
as a side note, my USB port has taken a ****, so the only fix that i can do currently has to be done on the phone itself.
Hi !
This kind of problems can be basically solved in the rom thread you are using it , the developer can help when you post logs as well
Have you tried to flash to stock in order to exclude a hardware issue ?
Cheers !

Stock Nougat Firmware "BLUETOOTH WON'T TURN ON" (HELP)

suddenly i bought this phone second hand. then when I tested Turning on my bluetooth it won't turn on.
Is there anyone experiencing the same problem?
I already did troubleshoot and performed this steps:
1. Wipe cache of Bluetooth Applications on System apps in settings
2. Force stop Bluetooth Applications on System apps in settings
3. Restart my phone
4. Wipe Cache on stock Recovery & restart my phone
5. Restore Factory Settings on Recovery
but suddenly bluetooth still won't open when touching it on notification panel nothing happens even directly on the settings toggling the bluetooth won't work. :crying:
my phone is untouch on rooting world.
So my questions is;
1. Will rooting and flashing rom can solve my bluetooth problem?
2. Is this a hardware problem?
3. Is there a separate chip or module for bluetooth on the motherboard of S7 edge?
to all XDA members I'm asking if you have an idea on this matter please feel free to reply to this post.
thanks you so much!
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Beanvee7 said:
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Click to expand...
Click to collapse
if it is a hardware problem? is there a separate module or chip on the s7 edge motherboard? or it is integrated on the processor ?
I don't know the answer to that
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
dhawal4u said:
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
Click to expand...
Click to collapse
what custom rom have you tested?
i already tried Batman-Rom
lervzz said:
what custom rom have you tested?
i already tried Batman-Rom
Click to expand...
Click to collapse
batman / superman / tgp and many others
none working
dhawal4u said:
batman / superman / tgp and many others
none working
Click to expand...
Click to collapse
I tried flashing newest stock nougat firnware XTC csc.
Tried it using ODIN
But still bluetooth won't turn on.
Can you say that our problem is hardware failure? But I think if it's a hardware issue then wifi should not work too. Because wifi and bluetooth is on the same chip module. ???
Update: I've talk to numerous technician and they think its not a hardware issue since my wifi is working. They said that wifi and bluetooth is on the same micro chip module. So if it is hardware issue on the bluetooth wifi should not work too. ???????? @dhawal4u
Same Problem here. Since 2 months after trying Badman Rom my Bluetooth doenst work. Now I load Stock Rom, Bootloader, Modem but no solve for the Problem

SM-G955U - [Odin Issues] Attempting to Return to Factory Firmware (Phone works)

Hello everyone, looking for advice in how to return to factory firmware. First, a few bullets to condense the information, then an expanded explanation below. Any assistance would be appreciated.
TL : DR
-Xfinity Mobile GS8+, SM-G955U
-Phone boots and works fine
-When device was still on Nougat, the Oreo beta firmware update.zips were floating around
-Downloaded and installed via factory recovery said update.zips in succession
-Stuck on pre-release build, want to get back to official Verizon Firmware and receiving OTAs
-Current Build: R16NW.G955USQU2CRAD
-Desired Build: G955USQS5CRI4 (Verizon, 09.11.18)
-Tried flashing CRI4 package manually via Odin, Odin said no
-A few hours of Googling and reading through forums as etiquette demands I try first has led me to post this, never not been able to find a fix in the forums
-Plz help, will PayPal/GooglePay/whatever you a 12-pack of beer or whatever to whoever gets me back to factory
Things I've Tried:
-Factory reset
-Odin
-Smart Switch
-OTA
So I have a Galaxy S8+ purchased through Xfinity Mobile. I wasn't able to get into the Oreo beta officially offered through the Samsung Program, but there were update.zips floating around that allowed you to migrate to the pre-release builds. The samsung.firmware.science link above was relatively straightforward - pick your model, it had the latest official build, download an update.zip, and profit.
As the beta program progressed and various more final builds were released, these builds provided additional successive update.zips, until ultimately resting on what was the final version, build number R16NW.G955USQU2CRAD, which I am on currently. I use various forms of Package Disabler and had until recently kept a lot of Samsung's bloat disabled, including the OTA services. Note this only disables them and keeps them from running, not actually remove them from the phone.
Anyway, being an old ROM crackhead from back in the day when aftermarket ROMs actually provided significant software improvements over the garbage that OEMs ship on their phones, I don't like OTA updates that often because I prefer to factory reset after each update - the updates usually make the phone feel sluggish, which may be placebo, but here we are. In light of all the recent Android security vulnerabilities, despite not doing dumb stuff on my phone I figured it was time to go ahead and OTA to get the newest security patch. The issue is that my phone does not recognize any new OTAs despite being on a firmware build from January 2018.
I'm familiar with Odin, figure no big deal, grab the newest build for Verizon (Xfinity Mobile runs on Verizon towers, there's currently a Verizon sim in the device, and Xfinity Mobile builds seem to be entirely absent) and try to flash G955USQS5CRI4 dated 09.11.18. Verified through redundant sources this is, in fact, the latest Verizon build for the S8+.
Lo and behold, it doesn't work. Contacted Samsung regarding possible solutions, their chat agent wasn't very helpful, directed me to a local authorized repair store, who said they may or may not be able to flash it back with Samsung's software, and it requires what may be a two hour diagnostic that checks every possible thing it can on the device, and if it's not an official build, they will tell me to **** off, not withstanding the fact that the guy mentioned that the software from time to time glitches and crashes. My experience with flashing firmware makes me wary of what would happen during a system flash if the software crashes.
Anyway, for those of you who bothered to read past the TLR and embrace my dissertation, I've been out of the flashing game for a while, and because flashing factory firmware via Odin was my go to in the past, I'm not up to date on fixes for obscure issues. A few hours of Googling and reading through forums and I'm not anywhere closer than where I started, and I'd rather fix this myself rather than go to a store and potentially pay them for something that is "out of warranty."
Any ideas would be much appreciated, would gladly PayPal/Google Pay/Whatever someone a 12-pack of beer/$ to someone who can help me get this thing back to factory firmware.
Thanks in advance for any help.
From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.
bmxmike said:
From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.
Click to expand...
Click to collapse
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?
zerofighter1 said:
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?
Click to expand...
Click to collapse
I'm saying I have never flashed USERDATA as I've never seen it packed in most the roms I download, only other thing they have included is MAYBE a pit file for repartitioning. As for CSC:
Home_CSC: Flash the firmware without wiping the data (if you just want to update the ROM)
CSC: Flash the firmware along with a complete wipe including data (mostly used in cases like bricked phones or Go-Back-To-Stock situations)
I would try reflashing in download mode doing what I suggested and make sure that only reboot, nand erase, and f. reset are the only things checked.
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.
bmxmike said:
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?
zerofighter1 said:
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?
Click to expand...
Click to collapse
Should have mentioned, the reason I'm asking is there is a discrepancy between the file size from Updato and this file - Updato file is 3.6~ GB and the one in this thread is 3.12~ GB.
No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)
bmxmike said:
No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)
Click to expand...
Click to collapse
Hey sorry, I've been busy working and haven't had the time to get back to this. I'm going to try this today and I'll get back to this post with an update.

Would a custom kernel (looking at superkernel) work on a stock but rooted firmware?

I took a break but Ive been playing around with trying to downgrade my s7 to marshmallow, despite the bootloader not letting you. I can get everything to work, except for vibration... it does a quiet beep instead. but haptic feedback is a must for me, as well as ringtone and vibrate mode
But i just wondered, if anyone has tried using this, or another recommended custom kernel, to enable full function of marshmallow samsung stock rom? did you experience any negative side effects from doing so?
Im not new to rooting but fairly new to understanding how firmware and samsungs new bootloader lockdown works... (unlocked should mean you can install whichever firmware youd like as long as its for your specific device, but thats a whole other rant...)
I enjoy the look of touchwiz and really enjoy the samsung themes, so I dont want to go pure stock at all... but if this is possible/works it may be the perfect middle ground.
Thanks
Ive tried playing with editing the stock nougat kernel into the stock marshmallow rom, but none of my PCs support virtualization, which is required to run linux in an emulator in order to finally truly see whats inside of those .img files... this is a dead end approach for me short of buying a new PC which isnt going to happen anytime soon.
Pawprints1986 said:
I took a break but Ive been playing around with trying to downgrade my s7 to marshmallow, despite the bootloader not letting you. I can get everything to work, except for vibration... it does a quiet beep instead. but haptic feedback is a must for me, as well as ringtone and vibrate mode
But i just wondered, if anyone has tried using this, or another recommended custom kernel, to enable full function of marshmallow samsung stock rom? did you experience any negative side effects from doing so?
Im not new to rooting but fairly new to understanding how firmware and samsungs new bootloader lockdown works... (unlocked should mean you can install whichever firmware youd like as long as its for your specific device, but thats a whole other rant...)
I enjoy the look of touchwiz and really enjoy the samsung themes, so I dont want to go pure stock at all... but if this is possible/works it may be the perfect middle ground.
Thanks
Ive tried playing with editing the stock nougat kernel into the stock marshmallow rom, but none of my PCs support virtualization, which is required to run linux in an emulator in order to finally truly see whats inside of those .img files... this is a dead end approach for me short of buying a new PC which isnt going to happen anytime soon.
Click to expand...
Click to collapse
You can flash any kernal to a rooted device as long as that kernal is for the exact same device and firmware. Flash via Odin, make a complete back up before, if it all goes wrong, flash the back up.

Categories

Resources