Database Users

Speaker, WiFi and Bluetooth not working

Please I need your help guys.
My OnePlus2 recently started behaving weird. The Bluetooth, WiFi and External speaker just stopped working for no apparent reason. Every other thing is working. 3G works just fine. I am able to make calls through the normal speaker (i.e. by putting the phone to the ear), but if I decide to switch the calls to the loudspeaker, I can't hear anything. Also, if I play music to the external speaker I can't hear anything unless I connect a wired earphone through the jack. When I try to turn ON the Bluetooth and Wifi, they just turn themselves back OFF, so they have become useless.
Please has anyone experienced anything like these before; if yes, please how did you solve it.

isadeiza said:
Please I need your help guys.
My OnePlus2 recently started behaving weird. The Bluetooth, WiFi and External speaker just stopped working for no apparent reason. Every other thing is working. 3G works just fine. I am able to make calls through the normal speaker (i.e. by putting the phone to the ear), but if I decide to switch the calls to the loudspeaker, I can't hear anything. Also, if I play music to the external speaker I can't hear anything unless I connect a wired earphone through the jack. When I try to turn ON the Bluetooth and Wifi, they just turn themselves back OFF, so they have become useless.
Please has anyone experienced anything like these before; if yes, please how did you solve it.
Click to expand...
Click to collapse
Not too sure about the External Speaker issue, but generally whenever I get Bluetooth and WiFi issues exactly like yours in the past - a reset solved the problem.
But I only ever had issues like that if I'm using a Custom ROM.....
Is your 1+2 using OxygenOS by any chance?

LogicalJunkie549 said:
Not too sure about the External Speaker issue, but generally whenever I get Bluetooth and WiFi issues exactly like yours in the past - a reset solved the problem.
But I only ever had issues like that if I'm using a Custom ROM.....
Is your 1+2 using OxygenOS by any chance?
Click to expand...
Click to collapse
Thank you for your help.
What I mean by the External Speaker is the speaker at the bottom of the phone next to the charging port that enable you listen to the audio, either call or music, without putting the phone to your ear.
Yes, I am on the stock Oxygen 2.1.0. I have also restarted and wipe data and cache more than five times but nothing different has happened so far.

Ahh so the loudspeaker is faulty? The loudspeaker and the wireless module are quite separate hardware, so we've got to hope that it's a software fault - rather than both multiple prices of hardware being faulty.
At this stage do a nandroid backup, then Clean Install OxygenOS 2.2.0. If that doesn't solve the issue, just let us know. (If you need specific instructions on how to do the nandroid backup & clean install, just let us know as well).

LogicalJunkie549 said:
Ahh so the loudspeaker is faulty? The loudspeaker and the wireless module are quite separate hardware, so we've got to hope that it's a software fault - rather than both multiple prices of hardware being faulty.
At this stage do a nandroid backup, then Clean Install OxygenOS 2.2.0. If that doesn't solve the issue, just let us know. (If you need specific instructions on how to do the nandroid backup & clean install, just let us know as well).
Click to expand...
Click to collapse
Thanks for your support.
I did a nandroid backup as advised and I downloaded and clean install the Oxygen 2.2.0.
The situation didn't change. Its as if the modules are just not present.
For example, when I try to activate the WiFi or Bluetooth, they are animate as if to turn ON; but after a couple of minutes it simply turn back OFF and grey-out.
I even installed the unofficial CM 13 hoping this might solve the problem, but it remains the same.
Do you think this may in any way be connected with the kernel?

isadeiza said:
Thanks for your support.
I did a nandroid backup as advised and I downloaded and clean install the Oxygen 2.2.0.
The situation didn't change. Its as if the modules are just not present.
For example, when I try to activate the WiFi or Bluetooth, they are animate as if to turn ON; but after a couple of minutes it simply turn back OFF and grey-out.
I even installed the unofficial CM 13 hoping this might solve the problem, but it remains the same.
Do you think this may in any way be connected with the kernel?
Click to expand...
Click to collapse
Hmm no it shouldn't since you clean installed OOS (that should have flashed the stock kernel too).
Give it a try anyway, try flashing @Lord Boeffla kernel for OOS http://www.boeffla-kernel.de/
Just make sure you download the .md5 as well (ensure the download isn't corrupted).
If that fails, try the stock kernel as well http://boeffla.df-kunde.de/oneplus2/stock-kernel/.
If the above doesn't happen, can you do this check for me?
Shake the phone, tap the phone on a desk (aim around the sim card area), be gentle though, all we need is to ascertain if the signal flex cable is loose.....
Once you shaked and tapped the phone, check if the wifi/bluetooth is working? (if not, give it a reset and try again).....

LogicalJunkie549 said:
Hmm no it shouldn't since you clean installed OOS (that should have flashed the stock kernel too).
Give it a try anyway, try flashing @Lord Boeffla kernel for OOS http://www.boeffla-kernel.de/
Just make sure you download the .md5 as well (ensure the download isn't corrupted).
If that fails, try the stock kernel as well http://boeffla.df-kunde.de/oneplus2/stock-kernel/.
If the above doesn't happen, can you do this check for me?
Shake the phone, tap the phone on a desk (aim around the sim card area), be gentle though, all we need is to ascertain if the signal flex cable is loose.....
Once you shaked and tapped the phone, check if the wifi/bluetooth is working? (if not, give it a reset and try again).....
Click to expand...
Click to collapse
Thank you very much for your time @LogicalJunkie549.
I will download the kernel as advised and install it.
I will come with the update after the installation.

LogicalJunkie549 said:
Hmm no it shouldn't since you clean installed OOS (that should have flashed the stock kernel too).
Give it a try anyway, try flashing @Lord Boeffla kernel for OOS http://www.boeffla-kernel.de/
Just make sure you download the .md5 as well (ensure the download isn't corrupted).
If that fails, try the stock kernel as well http://boeffla.df-kunde.de/oneplus2/stock-kernel/.
If the above doesn't happen, can you do this check for me?
Shake the phone, tap the phone on a desk (aim around the sim card area), be gentle though, all we need is to ascertain if the signal flex cable is loose.....
Once you shaked and tapped the phone, check if the wifi/bluetooth is working? (if not, give it a reset and try again).....
Click to expand...
Click to collapse
I have done the suggested steps.
The phone remains the same.
Please see attached the screen shots.
It looks as if these modules/chips just went dead

Flash Oxygen OS Zip via Stock Recovery & Wipe Cache & Data

isadeiza said:
I have done the suggested steps.
The phone remains the same.
Please see attached the screen shots.
It looks as if these modules/chips just went dead
Click to expand...
Click to collapse
For your speakerphone issue, I can bet it is related to the modem/ radio.
Please update to the latest modem/ radio (via fastboot) for your device.
Then test calling again and report back.
Note that this issue and solution is not specific to Oneplus. It is applicable to CM 13 on all devices across manufacturers.
Hit the 'Thanks' button if this solution works for you.

Where can I get the OnePlus 2 Modem/Radio File
s_u_n said:
For your speakerphone issue, I can bet it is related to the modem/ radio.
Please update to the latest modem/ radio (via fastboot) for your device.
Then test calling again and report back.
Note that this issue and solution is not specific to Oneplus. It is applicable to CM 13 on all devices across manufacturers.
Hit the 'Thanks' button if this solution works for you.
Click to expand...
Click to collapse
Thank you for your support.
Please any idea where I can get Modem/Radio file to download.
A link will help, because I have been searching for it but no luck so far.

isadeiza said:
Thank you for your support.
Please any idea where I can get Modem/Radio file to download.
A link will help, because I have been searching for it but no luck so far.
Click to expand...
Click to collapse
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....

LogicalJunkie549 said:
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
Click to expand...
Click to collapse
Thank you. I am currently on OxygenOS 2.2.1
I will try your suggestions and revert back asap.

LogicalJunkie549 said:
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
Click to expand...
Click to collapse
Thank you @localjunkie549.
I have tried installing the modem and bluetooth files in the downloaded file in the link.
I am afraid the phone response remains the same.
I even tried installing the new OxygenOS 3.0, still the same.

Speaker working Now. But BT and WiFi still down.
LogicalJunkie549 said:
Hi Isadeiza, try this modem first (its the 'modem' for MM which might solve the issue finally). https://www.androidfilehost.com/?fid=24415232478675280.
Also try dirty flashing it first, if that doesn't work... Take nandroid then Clean flashing it.
What OxygenOS are you in now btw? As of right now we're up to 2.2.1....
Click to expand...
Click to collapse
Hi guys, thank you all for your support.
After a long time, my experience are as below.
After upgrading to OxygenOS 3.0, the behavior of the phone did not change. No sound from loudspeaker, no Bluetooth and no WiFi.
Well I stopped using it until my other phone started heating up so I came back to the OnePlus Two again. One day, I was surprised when the phone started ringing loudly as someone called my line. It worked for about 3 - 4 hours and stopped again. After about 5 days, it came up again for some 4 hours and stopped working again. It does this for over 6 cycles and about 3 days ago it kept working without stopping since.
So I am still observing it for the past three days and it seems to have repented, holding my hopes up high that it will continue to work without hitches again; though I cannot say now what happened, why it stopped working and why it started working now.
The problem of the Bluetooth and WiFi still persist and I still can't use the BT and WiFi. It just behave as if the modules are not present. My fingers crossed expecting them to "miraculously" come back to functional state just as the loudspeaker did on its own.
Thank you all guys for your support.

Earpiece is not working

1. After installing custom ROM (Pixel Experience 8.1), I have noticed my earpiece (receiver) isn't working. Yesterday I tried clean flash older Lineage OS 14.1 but earpiece still not worked after that. Maybe some problem caused this while installing these ROMs, but I did clean flash (wiped dalvik/cache/data) each ROM. So I decided to try installing stock ROM, I did this with TOOL_ZUK_Z1.
I'm now back in stock firmware and stock recovery too but this not solved my earpiece. still no sound from it. I tested it with app called: "Phone Doctor Plus" and in the results only lowest frequency 300mhz (2000/8000/12000Mhz don't work) but there is still no sound I'm able to hear physically. So is there any options to try to make it work? Or maybe is hardware issue this time?
2. I still have 1 year warranty, so my second question is: will be there no problem sending it to warranty center.... when I went back to stock ROM (cm-12.1-YOG4PAS7DF) and stock Cyanogen recovery?
Sorry for my amateur level english.

Mrmagnus said:
1. After installing custom ROM (Pixel Experience 8.1), I have noticed my earpiece (receiver) isn't working. Yesterday I tried clean flash older Lineage OS 14.1 but earpiece still not worked after that. Maybe some problem caused this while installing these ROMs, but I did clean flash (wiped dalvik/cache/data) each ROM. So I decided to try installing stock ROM, I did this with TOOL_ZUK_Z1.
I'm now back in stock firmware and stock recovery too but this not solved my earpiece. still no sound from it. I tested it with app called: "Phone Doctor Plus" and in the results only lowest frequency 300mhz (2000/8000/12000Mhz don't work) but there is still no sound I'm able to hear physically. So is there any options to try to make it work? Or maybe is hardware issue this time?
2. I still have 1 year warranty, so my second question is: will be there no problem sending it to warranty center.... when I went back to stock ROM (cm-12.1-YOG4PAS7DF) and stock Cyanogen recovery?
Sorry for my amateur level english.
Click to expand...
Click to collapse
Would recommend to claim warranty. Flash stock rom, stock recovery and lock bootloader. You can use the tool for that.

Zuk Z1's main speaker is giving a low output sound.Please help me to solve this issue.

problem with the voice transmission circuitry. no voice recognition

so, i will try my luck. first thing is, i have a xt1684 retgb. atm i'm on full stock oreo firmware, a backup that i made where everything should have worked fine. after the issue appeared i restored the backup. but yea, it still persists. what a *****y phone.
now i have the problem, that in any case no voice is recognized neither via the build-in mics nor over a plugged headset.
neither a full stock flash to oreo nor to nougat changed it. everything else seems to be working as it should.
really guys, give me any hint to get rid of this. everything is welcome. :fingers-crossed: i count on you. cheers

okay got a little success in camera. in there i got my voice back after re-enabling mic permission in settings. but it doesn't help on google search e.g. .

i got my mic back working. but i still can't tell what caused it. maybe something equal to the problem that causes no touch issue. don't know. flashed a few stock and rom until it worked again. it was a work or die mission. as mentioned in the stock oreo thread it is really neccessary to let every stock flash finish with the initial setup (even if skip everything) till you are on launcher homescreen.

Need help getting LineageOS to be stable (15.1 UNOFFICIAL, hltevzw, TWRP 3.3.0)

I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.

Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.

terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?

I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/

terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.

I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...

I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...

You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.

terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)

When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.

terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.

I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.

Redmi k20 gets stuck while trying to play sound

Since Friday my device is restarting automatically with error DEVICE CLOSED UNEXPECTEDLY
I tried hard reset went to service centre they did an software upgrade and then a downgrade to 12.0.3 from 12.0.5 but nothing worked
And now when i try to play any sound whether through YouTube , Music etc it is just crashing
Even the Sound settings are not opening and i couldn't connect to calls either and volume keys are also not working

Seems like hardware problem

But other things are working

Are you sure they did upgrade and downgrade?
Was it full wipe?
It recommend to flash custom ROM and see if sth cbange

Yes they did downgrade from 12.0.5 to 12.0.3
And I had full wiped from recovery 2-3 times
And yesterday I noticed one more thing my front pop-up camera was working fine but when I enabled sound effect for it
It just freezes

Ok, so that's officially India MIUI issue
try this
This is ultra battery saving option related and they're working on an update

i have already tried all these but nothing works and how my device is stuck in fastboot mode while trying to flash stock rom through mi flash tool

You mentioned earlier that phone is boiting, but it restarts often.
What error in miflash?

Yes it was booting then only when I tried to flash miui11 through mi flash tool it got stuck in fastboot mode
Mi flash was giving crclist error everytime
Anyways I have successfully flashed miui 11 through twrp but the above problems are still there

I had exactly the same issue with this device.
Then tried 5/6 custom roms of android 11.
Nothing worked, every os had it's own issue.
Then lastly I've installed PIXEL EXPERIENCE 10 PLUS rom and the phone started to work fluid.

I have a same problem. Whenever accessing sound, if freezes and restarts! Went to Mi center. They said they have to replace the motherboard . Actually it's one of the IC that's malfunctioning... Here's a video -

Let e know If there's any ROM that gets around this issue

nilanjan.joy said:
I had exactly the same issue with this device.
Then tried 5/6 custom roms of android 11.
Nothing worked, every os had it's own issue.
Then lastly I've installed PIXEL EXPERIENCE 10 PLUS rom and the phone started to work fluid.
Click to expand...
Click to collapse
Didn't work for me

shrae said:
Let e know If there's any ROM that gets around this issue
Click to expand...
Click to collapse
Pixel Experience 11 plus worked fine, except the Audio problem still remains :-(

Gopalakrishnan V said:
Pixel Experience 11 plus worked fine, except the Audio problem still remains :-(
Click to expand...
Click to collapse
Did you manage to solve your problem? I have the same issue and dont know what to do

levarete said:
Did you manage to solve your problem? I have the same issue and dont know what to do
Click to expand...
Click to collapse
Nope the audio issues cannot be fixed with any software. I think it's caused due to some IC failure.
You would have to change the motherboard to fix the issue or you have to be a professional electronics engineer who knows and have the equipment for micro soldering.

The same issue was encountered with me also. I am in great distress right now. Tried more than 30+ ROMs (including recover, fast boot, custom, and stock), but nothing helps.
IF you find anything please update here.. THat’ll be a great help indeed!!
Here’s my thread: https://forum.xda-developers.com/t/...dphone-and-many-features-not-working.4309769/