Volte Not works after restoring RR N - Xiaomi Redmi Note 3 Questions & Answers

Dear All,
I am facing problem of volte (calling) not works after restore RR N Roms. (Latest builds)
I am using RR N since 2 months.
Everything was going fine.(Backup/restore with working volte)
But since last 1 weeks builds whenever i backup RR N Roms (Backed up all partitions except firmware because it gives error while restoring) & restore it back, Volte not works.
I thought that may be icon was gone but calling will work but calling also not works.
Tried everything (Restored EFS, Flashed Latest firmware, Flashed volte patch) but not success.
I have to flash rom again to get volte working.
Please help me if i am wrong in process.

After u restore your data...flash only rr rom on it..volte will work..i also had this problem and now its fixed..

Any other peoples are facing this issue?
If yes then request to devs please fix it.

Yes. I too am facing this issue.

Yes...me to facing same issue ...volte icon doesn't appear. n volte doesn't work in rr nitrogen and viper os also if restoring backup

People facing this problem: Reboot to recovery and flash system again over the rom. You have to flash system only.

Related

Can't go through initial setup screen

Hi,
I've got a RN3, snapdragon version, 3GB of RAM. Unlocked bootloader. TWRP 3.0.2-2
I've been using CM for a while, android 6.0.1 and I've been trying now for a few days to move to Nougat.
I've tried different roms: NitrogenOS, lineage OS, resurrectionRemix.
I've also tried flashing different versions os miui firmware: 7.3.16, 7.3.23, 7.3.30
So, after all that, the result is always the same. The flashing seems successful, the phone boots but then I cannot go through the initial setup screen.
I choose the wifi network but when I try to enter the password, the screen resets every 5 seconds or so. I know it's resetting/reloading because the password I've typed so far goes away and I have to start again. It happens every few seconds and I cannot setup wifi properly.
I tried changing the password to aaaaaaaaaa to make it easy and quick to setup. Once I go through that, it stays for ever in the next screen "checking information" (or something like that). Again, it seems to be reloading this screen every few seconds.
is there something am I missing? Maybe I'm flashing firmware/rom in the wrong order?
I'm back with android 6.0.1 now and the phone works fine.
thanks in advance for your help.
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
VaibhavKumar07 said:
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
thanks @VaibhavKumar07
so, this is exactly what I've tried a few times.
what about wipes and all that stuff?
I don't mind doing a clean install and reinstalling/reconfiguring everything.
I've tried different things, but for example what is mentioned in the thread "CM13/14/14.1/AOSP N firmware for KENZO/KATE [VoLTE][12.1.2017]"
-Reboot to TWRP recovery
-Flash firmware
-Factory reset (data, cache and dalvik-cache)
-Flash your favorite Marshmallow or Nougat ROM
-Reboot your phone
is that still valid for the nightly builds from April 2017?
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
So, I did all that several times, except for flashing the latest twrp version. I'm on 3.0.2-2 because it flashes ok but when rebooting it's back to 3.0.2-2. I'm doing this from fastboot. I'm not only loading, but flushing. It seems to be ok but then it's gone after reboot.
Anyway, I've tried this procedure with 3 different roms:
ResurrectionRemix
LineageOS
Nitrogen OS
flashing latest versions for each rom.
Could the twrp not updating properly have something to do with this issue? does the latest version fix some flashing issues with Nougat?
the thing is that if flashed and boots, but it doesn't run properly as mentioned.
I will try to get latest twrp version working and report back if that makes any difference.
VaibhavKumar07 said:
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
txutxe said:
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
Click to expand...
Click to collapse
Try this once (Clean) :
Flash Nitrogen
Reboot
Flash gapps and firmware.
Hope it may work for you.

volte lost after restore from twrp backup

Currently, I'm on April build resurrection remix (25-04). Took a twrp backup. Later tried to install latest build rr ROM , but due lollipop bootloader, it got stuck on get resurrected animation. Now, from twrp, I wiped everything (except microSD) and restored from backup. Each and every thing is working fine, but volte isn't working. Any solutions?

Redmi Note 2 Mokee by BULE

I decided to try out the Mokee ROM which is based on CM 12.1. Everyone on this thread(https://forum.xda-developers.com/re...m-cm-12-1-mokee-bule-mokee-blue-t3328382/amp/) praised this ROM for being stable enough. I installed TWRP and flashed the ROM. Everything was working fine, only problem was I couldn't change notification light color. I installed some CM themes and flashed a font. However after I flash something through TWRP the ROM acts strange. Sometimes it says "Android System stopped working." Widgets are blanked and I have a soft brick. I wiped dalvik even tried I dirty flash twice. Same problem persists(e.g. flashing something hangs up the system) and I couldn't tell if the ROM was stable or not. I was missing my calls so I reverted back to MIUI 9.
Any solution for this? I cannot provide screenshots now.

Wifi doesn't work after latest vendor, can't activate wifi on any rom

Wifi doesn't work after latest vendor(beryllium-9.6.27-9.0-vendor-firmware.zip), can't activate wifi on any rom. I've since tried many different vendor and roms, same issue can't enable wifi.
Have I bricked my phone? I've tried formating data, fix content, full wipe in twrp, still the same issue.
You may have to use the mi tool to fully reflash the stock ROM then it should work.
timbook2 said:
You may have to use the mi tool to fully reflash the stock ROM then it should work.
Click to expand...
Click to collapse
Thanks for your reply, the thing that made the wifi work again was installing the latest beta vendor+firmware (10.x bransh) with latest lineageos.
I believe orange twrp did a bad backup which I restored that somehow temporarily soft bricked my wifi/phone.
Now I don't dare to trust any backups lol

LineageOS/Pixel Experience don't work properly after returning to stock

Hi all, this is my first question here.
I reverted to the stock ROM (11.2.0 Global), which I got from here, from LineageOS 17.1, but when I reinstall LineageOS, the phone shuts down during the first boot, and in subsequent reboots the phone shuts down after a few seconds, making it impossible to complete the setup process.
I followed all the steps, including formatting data and then doing an advanced wipe of /system and /cache in TWRP before installing LineageOS, and there were no error messages during the installation.
Thankfully, the stock ROM works fine, but I'd like to reinstall LineageOS.
Can anyone please help me with this?
Update: the same issue occurs with Pixel Experience.
The same happened to me too, for me I fixed it by flashing permissiver zip after flashing rom.
This was only needed only once after switching to custom rom from stock, after that you can flash roms normally i.e without permissiver.
Happend to me too ,after many tries got it fixed by flashing LOS 16 then clean flashed LOS 17.1 without cleaning the vendor partition. But for me PE was working fine only LOS 17.1 had issue like constant shutdown after installation when its boot up.
Ghoul2077 said:
The same happened to me too, for me I fixed it by flashing permissiver zip after flashing rom.
This was only needed only once after switching to custom rom from stock, after that you can flash roms normally i.e without permissiver.
Click to expand...
Click to collapse
Could you please provide a link?

Categories

Resources