Related
Hello Guys! Just decided to flash a new rom to my phone. Installation went good (wipped and installed rom and gapps stock) and everything went perfectly good. There is no data connection. There is just an exclamation mark. I installed CM 12.0 to see if it was a bug related issue. I didn't connect to a wifi and noticed my data was working until I turned it off and back on and the same issue appeared. Did the same to 12.1 and it worked until I turned cellular data off and on again (and no matter if I reboot and change the APN the problem persists). Any ideas? Thank you for your time
OdyXen said:
Hello Guys! Just decided to flash a new rom to my phone. Installation went good (wipped and installed rom and gapps stock) and everything went perfectly good. There is no data connection. There is just an exclamation mark. I installed CM 12.0 to see if it was a bug related issue. I didn't connect to a wifi and noticed my data was working until I turned it off and back on and the same issue appeared. Did the same to 12.1 and it worked until I turned cellular data off and on again (and no matter if I reboot and change the APN the problem persists). Any ideas? Thank you for your time
Click to expand...
Click to collapse
Yeah i have a great idea for you to just change your CM12 back to stock firmware or try another custom rom based on stock. There is no solution for this problem as far as i know. Due to this problem i am not able to use CM12 or 12.1. Yeah, i had have the same problem and i asked the DEVs to help me out of this but it didn't happened at all. I don't know what was the reason but they weren't able to help me. I tried every possible method but that ****y exclamation mark didn't leave me alone at all. So, after all of this i went back to stock.
Are you sure you have right APN settings?
Arsal7R said:
Yeah i have a great idea for you to just change your CM12 back to stock firmware or try another custom rom based on stock. There is no solution for this problem as far as i know. Due to this problem i am not able to use CM12 or 12.1. Yeah, i had have the same problem and i asked the DEVs to help me out of this but it didn't happened at all. I don't know what was the reason but they weren't able to help me. I tried every possible method but that ****y exclamation mark didn't leave me alone at all. So, after all of this i went back to stock.
Click to expand...
Click to collapse
Well I now use CM 11 which is pretty good actually. Yes i Have the right APN settings. Never mind I'm happy with CM 11 so not gonna spend any more time...
I have that exclamation mark too, but data works ok, I just ignore it. Sometimes it goes away , but most of the time it just stands there next to an network icon.
On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)
zxsq said:
On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)
Click to expand...
Click to collapse
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.
robertofelce said:
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.
Click to expand...
Click to collapse
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
Remember that rr marshmallow releases don't work for SM N900. I guess that your phone is sm N9005. Right?
If it is, is awkward that you can't flash a rr marshmallow ROM
You should be in the T-Mobile note 3 forum?
Cm12.1 for the hltetmo: https://download.cyanogenmod.org/?device=hltetmo
zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
got exactly the same problem....Tried to flash repair stock rom with pit, with success, but doesn't change anything
can flash 5.0 stock or 5.1 port rom but not CM or AOSP..
if you find what happen....
Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.
rikymatteo97 said:
Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.
Click to expand...
Click to collapse
My note 3 smnN900t is doing that same thing and it sucks because I know I did everything perfectly!! What Kernel were you able to flash for it and where did you download it from? By the way thanks in advance for any help and info you can give!!!
Wrong forum
forum links .
http://forum.xda-developers.com/showthread.php?t=2574886
Please help I am having the same issue. Did anyone find a solution for this ?
Greetings fellows! Today I have flashed CM 13.0 on my Redmi 3S Prime (land). After flashing, the device worked like a charm. However, after 1 or 2 reboots, the Wi-Fi stopped working. I can't turn it on. The button is also grayed out. I reflashed /persist and tried everything. The MAC-address has become 02:00:00... etc. Did anyone have the same issue? Could anyone help me? Thank you in advance! (I also tried reflashing stock Stable global MIUI, same issue. I don't think it would be a hardware issue, since the problem persist since the ROM flashing).
Edit: Solved it somehow. After I flashed MIUI, a few reboots later the wireless worked. No idea why.
coda00 said:
Greetings fellows! Today I have flashed CM 13.0 on my Redmi 3S Prime (land). After flashing, the device worked like a charm. However, after 1 or 2 reboots, the Wi-Fi stopped working. I can't turn it on. The button is also grayed out. I reflashed /persist and tried everything. The MAC-address has become 02:00:00... etc. Did anyone have the same issue? Could anyone help me? Thank you in advance! (I also tried reflashing stock Stable global MIUI, same issue. I don't think it would be a hardware issue, since the problem persist since the ROM flashing).
Edit: Solved it somehow. After I flashed MIUI, a few reboots later the wireless worked. No idea why.
Click to expand...
Click to collapse
I'm also facing the same problem . . Plz help out
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Maybe its realy screen problem... did the touch screen works on twrp
fire_onCA said:
Maybe its realy screen problem... did the touch screen works on twrp
Click to expand...
Click to collapse
Yes It Does. Its not the screen issue because on stock rom everything works properly.
Im guessing somethings interrupting with the OS, causing the apps to crash.
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
mfaisal98 said:
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
Click to expand...
Click to collapse
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
aymanabdulla said:
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
Click to expand...
Click to collapse
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Its not actually an error message but a small notice on the top left corner.
When I restore my official rom back the message is normally gone.
But I will try again with ur advice again because I always wipe system before flashing the rom so it could be causing the issue.
Thanks I'll let u know what happens
kaiserfakinaway said:
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
Click to expand...
Click to collapse
I did do that. I have the official stock rom running now since RR and cyanogenmod isn't responding.
aymanabdulla said:
I did do that. I have the official stock ROM running now since RR and CyanogenMod isn't responding.
Click to expand...
Click to collapse
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
kaiserfakinaway said:
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
Click to expand...
Click to collapse
Yes, thats what i did.
G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md5 this was the file name. it works fine i guess, had some issues with the sim as the phone keeps on asking to reboot but no other issues.
Subhashis said:
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
Click to expand...
Click to collapse
Yes i did. as well as the front cam + patch fix. i flashed both yet still the same issue.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
aymanabdulla said:
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
Click to expand...
Click to collapse
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Why Doesnt any one else have this problem?
oh is it? what about lineage os 13.1 running MM?
Fine i have put cm12.1 for download, will flash it and let u know what happened.
Fingers Crossed
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
kaiserfakinaway said:
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
Click to expand...
Click to collapse
Nope, all of them have camera issues too.
but im sure there will be a fix for this, since its running LOLLIPOP.
I'll let u know.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Might not be a kernel issue because I have also tried with this custom kernel [KERNEL][5.x/TW/6.x]Infected Kernel R4[15-05-2016] and still the same.
HavocOS_3.7 ROM (ported)
This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Ten 3.7 on Q vendor,
How to ::
1. Confirm your device model as above.
Don't worry which rom which build ur device have presently. Just flash this.
2. Flash the file thru twrp
Wipe data cache dalvik.
Best of luck
This ROM is included
Magisk
gapps
Google Phone Dialer
Safetynet Fixed
Bugs::
None.
Tell me. Bluetooth not tested.
Thanks to::
Cosmic kernel developer for removing sms bug.
Link for file...
https://www.androidfilehost.com/?fid=8889791610682946656
Hit thanks button below if u like.
NB Drop a line in comment section mentioning your feedback / bugs / experience
Those who want to share a cup of tea
PM me.
Is there any VOLTE bug ?
Because when I flashed Havoc 3.7 ther is the VOLTE bug I have to flash a VOLTE fix file separately to fix this. Does this fastboot ROM include this fix ?
Techgaming432 said:
Is there any VOLTE bug ?
Because when I flashed Havoc 3.7 ther is the VOLTE bug I have to flash a VOLTE fix file separately to fix this. Does this fastboot ROM include this fix ?
Click to expand...
Click to collapse
May be volte fix not worked... It s included. Anyway thanks for feedback.
Also install imsq.apk seperately if required.
please provide shell script to flash through linux
Give me volte fix zip link its rom have problem on volte pls give me
volte-q and ;linux flash all script attached here.
Bluetooth headsets are working only for calling other music an video anything's are not working..!! Help
[email protected] said:
volte-q and ;linux flash all script attached here.
Click to expand...
Click to collapse
does that script behaves same as windows cmd,,,
I mean,, does it unlock the bootloader ??
ankushlohiya said:
does that script behaves same as windows cmd,,,
I mean,, does it unlock the bootloader ??
Click to expand...
Click to collapse
Yes.. But not tested.... Check it and revert
Abou ROM
I have tried your all fastboot roms and the best is Evo X 2.3 because it has great battery life. In the latest ROM of your which is Havoc 3.7 it has battery drainage issue I think all Android 10 GSI will have the issue on our device because of Asus.
I booted a oxygen os GSI but it has minor bugs so please port a Oxygen OS for our device.
Volte not showing please help
Rohit1506 said:
Bluetooth headsets are working only for calling other music an video anything's are not working..!! Help
Click to expand...
Click to collapse
I'v the same problem. Can someone fix it?
Hi Barinda,
Installed havoc 3.7 over havoc 2.9 without erase data.
3.7 is not working correctly.
1. Only back button is working, the other two are not.
2. I have no notifications when I slide down the bar.
3. I have no settings button either.
4. I can't switch off data connection.
5. I can't access developer settings to enable adb to get me out of this mess.
6. Dark mode reverts to light after every boot.
7. Camera crashes after a few seconds.
I tried flashing back havoc 2.9 without erase data.
After successful flash it starts.
I see first logo, then the two blue dots turning around the white circle and it stays like that forever.
Do you have any suggestion how to get back to havoc 2.9 without erasing data?
For me havoc 3.7 is a downgrade because lawnchair is no longer there, and tweaking options are 10 times less than havoc 2.9.
Please help.
Thanks a lot,
Mike
pinket said:
Hi Barinda,
Installed havoc 3.7 over havoc 2.9 without erase data.
3.7 is not working correctly.
1. Only back button is working, the other two are not.
2. I have no notifications when I slide down the bar.
3. I have no settings button either.
4. I can't switch off data connection.
5. I can't access developer settings to enable adb to get me out of this mess.
6. Dark mode reverts to light after every boot.
7. Camera crashes after a few seconds.
I tried flashing back havoc 2.9 without erase data.
After successful flash it starts.
I see first logo, then the two blue dots turning around the white circle and it stays like that forever.
Do you have any suggestion how to get back to havoc 2.9 without erasing data?
For me havoc 3.7 is a downgrade because lawnchair is no longer there, and tweaking options are 10 times less than havoc 2.9.
Please help.
Thanks a lot,
Mike
Click to expand...
Click to collapse
Go to recovery... Wipe cache... Dalvik.
It should boot.
please port miui rom to asus x01ad
needed help wuth some issues
i am not able to make calls and send messages via jio sim using the rom and bluetooth headset not working and gcam crash oftenly please sir suggest me some fix for these problems i will be greatful for your help
ishanjaiswal said:
i am not able to make calls and send messages via jio sim using the rom and bluetooth headset not working and gcam crash oftenly please sir suggest me some fix for these problems i will be greatful for your help
Click to expand...
Click to collapse
1. Flash volte-q
2. Use gcam 6.2
3. Bluetooth issue yet to b solved
Out going call not working i can't make any calls , and can't send or receive any sms. I already flashed Volte-q and Wipe cache... Dalvik. Also try to install the rom 2-4 times tried flashing rom and volte-q together and separately like install rom first then reboot and flash volte-q. Still not able to make any call and send or receive any sms. Incoming calls are working just fine. And my ISP is JIO.
DEXT3RR0R said:
Out going call not working i can't make any calls , and can't send or receive any sms. I already flashed Volte-q and Wipe cache... Dalvik. Also try to install the rom 2-4 times tried flashing rom and volte-q together and separately like install rom first then reboot and flash volte-q. Still not able to make any call and send or receive any sms. Incoming calls are working just fine. And my ISP is JIO.
Click to expand...
Click to collapse
This is magisk module
So flash it in Magisk
See attachment
After flashing this
Download build prop editor from play store
Then open and grant root access
Click on edit/pencil icon on top right corner
Then go to last line and add the lines mentioned below
# Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
THEN RESTART ur phone.You will see Volte icon.
Feel free to PM me if any issue.
While flashing it gives error of E signature failed eroor 21 how to fix it and what to do and flash other two files