[GUIDE] Install Lineage OS 14.1 on Redmi Note 3 (No in call audio issue fixed) - Xiaomi Redmi Note 3 Guides, News, & Discussion

Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience.. ?

xzy99 said:
Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience..
Click to expand...
Click to collapse
it this a joke? this looks like a chinese copy of a guide posted 1 week ago and is only 2 posts under this:
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
what is your intention?

@massan1 I hope you have eyes through which you can read properly. No offence brother. Well, I didn't copy it. Plus that guide is made for those who have locked bootloader. Second, I am posting this for those who want to clean install Lineage OS with the call audio fix. So, if you believe I have copied it , just keep believing it.
Keep burning.. I'll get ice packs for you. Thanks.

I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107

r28 said:
I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107
Click to expand...
Click to collapse
just flash upgraded firmware or change build.prop:
https://forum.xda-developers.com/re...stall-lineage-os-locked-t3546154/post70826457
Raaj52 said:
This is not a build.prop issue!! In order to work with the old firmware (patched one) you have to make fluence to none, this is done when you use patched VoLTE. If you make fluence to none the latest MM firmwares won't give sound in call, many are getting no sound because they are using the old patched firmware. Since the native VoLTE is fixed no need of the old firmware and you don't need to change fluence to none. Just flash the latest firmware and you are good to go.
Still doubt? OK then I need to tell you one more thing, The first patch for VoLTE for MIUI MM was made by me (you can check that in MIUI Global forum) and sudeep made a firmware.zip with my NON-HLOS.bin and I can see that the same is copied in the firmware.zip, in order to get fluence working in the patched firmware it should have used with the correct adspso.bin.
Many are thinking that changing firmware is useless but in reality it comes with lot of stability fixes, so I recommend everyone to update your firmware to the latest one instead of all this build.prop editing craps.
What is the problem if I edit build.prop? --> You have to edit your build.prop whenever you flash a ROM, you can't avoid it unless you flash the latest firmware.
Why I am so confident? --> Because I know what is firmware and How does it work!
If you have "no sound in calls" issue even after you change the firmware I recommend a clean mi flash tool flashing with the latest MIUI ROM (because it will fix all your partition related stuffs, instability issues)
@abhishek987 @akhilnarang could you please add the "solution for no sound in calls is to flash the latest firmware" in your first post?
Click to expand...
Click to collapse

Related

[GUIDE] How to get CM 14.1 working.

Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989
-Reserved-
Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings
If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!
kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.
Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...
Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917

Easiest Method To Install Any Custom Rom - Universal 7.XX/8.XX

Hey guys,
So recently I tried a few custom roms and noticed that the steps for all roms are slightly diffferent and that confused. Hence decided to try everything available and come to a easiest step by step conclusion:
Steps :
At the time of writing this guide I was on codeworkx universal TWRP running stock OOS 4.7.6 with Magisk 15.2. But the steps would work from any rom to any rom.
1) Flash codeworx universal TWRp from here : https://goo.gl/yXx2sK
2) Boot into twrp and using your pattern/pin decrypt data, yes thats the good part no matter if you are on stable or custom be it android 7.1.1/8.0/8.1 this recovery is able to decrypt all roms.
3) Make a nandroid backup and copy all contents of your internal storage to a pc/ choose the backup method of your choice.
4) Make sure you have at least 50% battery charged.
5) In twrp go to wipe . format data type yes and tick
6) Reboot to recovery
7) Perform a factory reset also wipe internal storage.
8) While in twrp copy the rom and firmware and gapps to your phone
9) Flash first the firmware if needed by the rom, then flash the rom and then gapps and then dm verity zip if needed by the rom. Wipe cache and dalvik. (note if you are flashing a stock rom please flash magisk and then make the first boot otherwise TWRP will be erased)
10) Boot into rom and set it up
11) Flash magisk or supersu if needed.
Heres a step by step video :
Credits :
@Funk Wizard
 @codeworkx
xda developers
lineage os
team twrp
oneplus
Please note : Do this at your own risk. I would not be responsible for any damage.
If I have missed any names please PM me I will ensure i add it.​
Why all this codeworx TWRP hype all of the sudden? Bluspark has never let me down yet. What is the difference between the two?
It's good if you add DM verity to the list as "if needed" because certain custom ROMs require it.
I'll be looking at this thread at some point in the future. Thanks.
Anyone followed the above and have comments to make ?
after flash any rom black screen and blue LED
any help

How to update AOSP extended ROM

Hey everyone I recently installed aosp extended and saw in their website that a newer version was available when I checked a youtube video it said that I needed to flash gapps along with the update can someone help me on how to update the ROM is it same like pixelexperience where we just flash the file and clear cache alone?
#updateaex
1. Boot into TWRP
2. Flash AEX zip
3. Flash TWRP installer
4. Reboot to TWRP
5. Flash gapps
6. Flash magisk (optional)
7. Wipe dalvik cache
8. Reboot to system and enjoy
from telegram channel
But, what's your actual version of AEX ?
Sorry to but in...
I have a Mi9 with AOSP...
(please go easy..I'm a tad clueless)
If there is an update do I follow the instructions 21vm gave? And will I lose my apps and settings?

[QUESTION] Not able to boot Custom ROM P8 Lite Alice (ALE-L21)

Hello together,
after 3 Days of reading and searching and testing solutions, I have to ask you if you can solve my problem.
I can't find the reason by myself, because I'm new with this topic. I want to install a Custom ROM on my Huawei P 8 Lite Alice from 2015, but everytime I flash any Custom ROM which should match, it ends in a bootloop (huawei logo, then logo custom rom, then huawei logo etc....).
My device:
Huawei P8 Lite ALE L21 from 2015 - Alice
Built number before start this "project": ALE-L21C432B634
Android 6
Emui 4.0.3
Bootloader unlocked with code generated by dc-unlocker
No Root
My prefered Custom ROM is Lineage OS 14.1 and I tried to flash it following the steps in this thread:
[url]https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-p8-lite-t3824247[/URL]
1. step - Flash TWRP
First Problem was to install the TWRP 3.1.1 linked in this thread:
[url]https://forum.xda-developers.com/p8lite/orig-development/twrp-t3583180[/url][/URL]
To flash the TWRP image with adb caused no problem. When I boot into recovery, TWRP starts, but when I touch anything on the screen (like swipe to unlock) the System boots (With OS installed it boots the OS and without it stucks at huawei logo). Booting again into TWRP is no Problem.
I solved this problem with a TWRP image 3.1.0-1 from this forum:
[url]https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8-lite.2476/huawei-p8lite-neues-inoffizielles-twrp-3-1-0-1-von-surdu_petru-xda.826139.html[/URL]
The thread references on the same XDA thread mentioned above, but it is linked to another version of TWRP image. This Version 3.1.0-1 is working good.
2. step - flash EMUI 4.1
I flashed the EMUI Update B896 with TWRP. In the thread to the Lineage OS 14.1 mentioned above, it is described that you need this update. I used the linked .zip.
Steps:
1. Wipe Data, internal storage, system, Dalvik Cache, Cache (all except micro sd card).
2. Format Data
3. Reboot into TWRP
4. flash .zip from SD card
5. Wipe Davlik Cache and Cache
5. Reboot System
After that :
Android 6
Build number: ALE B896
EMUI: 4.1
The updated ROM works good.
3. Step - Flash Lineage OS 14.1
Steps:
1. Wipe Data, internal storage, system, Dalvik Cache, Cache (all except micro sd card).
2. Format Data
3. Reboot into TWRP
4. flash .zip from SD card
5. Wipe Davlik Cache and Cache
5. Reboot System
Result Boot Loop :victory:
Trouble shooting:
I tried to install different TWRP versions, but only the TWRP 3.1.0-1 works.
I useb adb sideload to flash the Lineage
I flashed the EMUI 4.03. I had before and than Lineage 14.1 (EMUI works, but Lineage doesn't)
I wiped dalvik cache and data, cache after flashing Lineage, to fix the bootloop
I flashed versions of Lineage OS 14.1 from different dates and different download websites
I flashed different Custom ROMS - all the same Problem except Lineage 13.0. Lineage 13.0 boots till it is ready to "preparing" apps and than boots again.
Now I don't know what do do and would be very thankful to get some new ideas to try or perhaps a solution
Thank you! :highfive:
The ROM needs Emui 4.1 B895/B896 update to be installed first
Then unlock bootloader, flash twrp then flash ROM
Thank you for your help. I'll try this. So I have to lock bootloader again first?
No. You flash the update with twrp
Go to step 6 in the first post on this thread
https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Keran_3066 said:
No. You flash the update with twrp
Go to step 6 in the first post on this thread
https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Click to expand...
Click to collapse
Maybe I described it not so good in my first post but I think I did it already exactly like that.
1. Unlock bootloader
2. Flash TWRP
3. Flash Emui 4.1 update B896 ( its working on my phone now)
4. Flash TWRP again
5. Flash Custom Rom ( evertime the result is a bootloop)
Or did I overlook anything?
Sorry I didn't read that part where you flashed emui 4.1
Lineage os 14.1 works for me.
Did you try Resurrection Remix OS
https://forum.xda-developers.com/p8lite/development/rom-t3606568
Keran_3066 said:
Sorry I didn't read that part where you flashed emui 4.1
Lineage os 14.1 works for me.
Did you try Resurrection Remix OS
https://forum.xda-developers.com/p8lite/development/rom-t3606568
Click to expand...
Click to collapse
Thank you very much, that you tried to help me Im happy about all suggestions.
Yes I tried RR and Paranoid, but its the same Problem. I'm wondering that the EMUI Roms which are not officially from Huawei work and any custom rom does not. Maybe there is a Problem with the structure of my system but I dont know anything about this stuff and how to find out the reason for my Problem:laugh:
Maybe you know a command for adb or android terminal app to check if everything is ok?
Jaba Wup said:
Maybe you know a command for adb or android terminal app to check if everything is ok?
Click to expand...
Click to collapse
I'm kinda out of ideas
Keran_3066 said:
I'm kinda out of ideas
Click to expand...
Click to collapse
I feel like you:laugh: thanks and have a nice evening:good:

calls have no speaker or mic

Everytime no matter what I do after flashing a ROM it eventually stops my calling ability. It calls out but no one. Can hear me and I can't hear them.
What OOS are you using? How are you exactly installing roms, step by step..? What rom installing?? Must have more details to help...
After i see that info ill know more. Possible its a hardware issue but i lean more towards software.. Let me know those things and i can help more.
How I install on OnePlus 6t global (or converted)
Boot twrp v3.5.0
Flash OOS 10.3.7 from repo or updater app
Flash rom (with gapps)
Flash twrp installer zip
Flash finalize
Format data (wipes it ALL)
Reboot recovery
Flash magisk
Reboot system
*Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
Without gapps rom install:
Boot twrp
Flash OOS 10.3.7
Flash rom (without gapps included)
Flash twrp installer
Flash finalize
Format data (wipes everything)
Reboot recovery
Flash gapps package
Flash magisk
Reboot system
*Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
Use NanoDroid Micro G and Fdroid instead of Gapps on a rom that has sig spoofing and NO Gapps included:
1st part of micro G install:
Boot twrp
Flash OOS 10.3.7
Flash rom
Flash twrp installer zip
Flash finalize
Format data
Reboot recovery
Flash magisk 21.4
Reboot system
Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
2nd part of Micro G rom install:
Boot twrp
Install micro g (stable) zip from Nanolx xda thread
Install Fdroid from Nanolx xda
Reboot system
Can also use twrp mauronofrio's 3.4.0-9-11. Those are newest twrp. I've flashed everything made for 6t and never an issue like this. Link to micro g and fdroid installer and more in my signiture.
(Edit)
Hey thanks for the responce, so here we go....
How I flash my roms
Flash OOS 10.3.7/twrp
Reboot recovery
Flash other side of a/b with OOS/twrp
Reboot recovery
Flash rom/twrp installer
Reboot recovery
Flash additional as in my migrate/magisk
Format data
Boot
The Roms I've tried are resurrection remix latest build & msm extended & one other I can't remember which tho. & with stock kernel. I've tried flashing other kernels it doesn't do anything or I'm trying the wrong ones.
Im not new to flashing been doing this for a while now, there's always bugs but there's also ways to fix the bugs. Something interesting is just one time calling it worked fine then the next call... back to no audio feedback. There are 2 other Roms that did the same thing. It happens completely random, like I'll be done modding my phone to my likings go a month or a week & all the sudden no audio. I doubt it's hardware cuz if I format data calls work again but yay all my customizing is gone. I've tried all the suggestions from other forums asking similar question like editing build.prop & a few other things I can't remember nothing's worked. I love this phone to death but it's not easy to keep it stable unless I wanted to go with linegen ROM but ever since they left cyanogen their customizations are lame. Anyways I hope this is enough details I imagine not just let me know thanks I appreciate your help.
I'm no noob but definitely not a master, i use micro g. It's something in the data partition so technically it should be fixable im just sick of re flashing every time it decides it's not a phone anymore just a mini computer that can't compute phone call audio
jessejamesd2i said:
I'm no noob but definitely not a master, i use micro g. It's something in the data partition so technically it should be fixable im just sick of re flashing every time it decides it's not a phone anymore just a mini computer that can't compute phone call audio
Click to expand...
Click to collapse
The only time i experienced similar on my 6t is when i used a sound mod, the zen 5 sound mod from asus phone ported.. It caused me to have this no sound issue but when i disable it via magisk it was fine and i had sound again.
Have you tried going back to OOS 10.3.7 only and see if sound is an issue?
If this is present on OOS i would think its a hardware issue.

Categories

Resources