Database Users

Problems CM based roms

Hi I got problems with my lux on every cm based rom. On every cm rom I get no reception of my carrier. I don't know if it's a device tree issue or just apn trouble. Since there are no aosp roms, I'm a little hung up. Stock rom works fine. I own the xt1562 operating on German carrier o2. Sometimes I get a few seconds of reception on cm roms, but it's leading just to no signal after a few seconds again. I nearly tired everything, flashed a different firmware etc. When I've flashed a rom I get the information that no sim card was found. After I restart the device he's asking for a pin. Also tried another sim card with the same result. Really could need some help.

flash the original fimrware from ur carrier or region
flash twrp
install cm and see if works
if not,flash only the radio modem from original firmware

Already did. Didn't work. Flashed the new cm12.1 from h2o64. This one is working.

I have the exact same problem with my XT1562 I bought from Germany through Moto Maker.
I installed h2o64's CM build from 10-10 after a full wipe (everything except internal data), and never got any proper signal. I tried squid2's CM build 10-12 as well, to no avail. Installing the XT1562 EU stock firmware following the linked explanation in the stock firmwares thread I had good, working signal, but then installing h2o64's CM build 10-14 with a factory reset rather than a full wipe resulted in the same issues described in this thread again.
I've read about these issues in different threads, mostly resolved somehow by installing the stock firmware, sometimes by selecting LTE as the preferred network type. I've tried these suggestions, but haven't had any success, and I don't know how to proceed.
Did I install the right stock firmware? (I would think so as it worked while it was installed.)
Did I forget to do something (like wipe, fix permissions, reboot the phone three times, howl at the moon,...)?
I use OpenGApps rather than tkruzze's since they're available in x64 as well so I can use them on all my devices. But that surely can't be it?
I'm at a complete loss at the moment, which is rather frustrating. Can anyone provide any help?
Gesendet von meinem Nexus 9 mit Hilfe von XDA Forums Pro.

I managed to install h2o64's CM build 10-14 and getting proper signal now.
I flashed the RETASIA firmware from XMoDuLeSx's Official stock firmwares added for xt1562,xt1563 thread following the instructions linked in the first post, and then after a wipe of system, data, cache, dalvik-cache I installed [ROM][lux][5.1.1] Cyanogenmod 12.1 - 2015-10-14 [UNIFIED].
Keep in mind that I have ordered my Moto X Play from Germany, so it shouldn't require a RETASIA firmware. I'm not advising to install this, as it was nothing but a shot in the dark that surprisingly didn't brick my phone. Still, I wanted to share that I got it working after all, simply to follow up my previous post properly. Should the signal break again, I'll update this thread; if I haven't, assume that it's still working.
Either way, though: If you decide to go down this road and install a firmware that isn't right for your phone and brick it, don't come to me. I'm advising against doing this.

Seems i'm having the same issue...
I did all the wipes and clean installs but I can't connect to my carrier.
Although my phone only supports one sim card, settings shows two. The first one is the one i'm using and it is displayed correctly. The quick settings tile though tells me that there is no sim card inserted.
I came from stock, unlocked, flashed TWRP from squid2's kernel page, rooted, flashed CM(squid2), kernel(squid2) and OpenGApps.
Did I do something wrong?
Is there any news on how to fix this problem or do I have to try again and again an hope to hit the spot?

Mafaldine said:
Seems i'm having the same issue...
I did all the wipes and clean installs but I can't connect to my carrier.
Although my phone only supports one sim card, settings shows two. The first one is the one i'm using and it is displayed correctly. The quick settings tile though tells me that there is no sim card inserted.
I came from stock, unlocked, flashed TWRP from squid2's kernel page, rooted, flashed CM(squid2), kernel(squid2) and OpenGApps.
Did I do something wrong?
Is there any news on how to fix this problem or do I have to try again and again an hope to hit the spot?
Click to expand...
Click to collapse
You need two more posts before you can post this in the CM thread from squid2. Squid2 is always fast with bugfixes. So make 2 other post and then explain your problem to him.

Lennyz1988 said:
You need two more posts before you can post this in the CM thread from squid2. Squid2 is always fast with bugfixes. So make 2 other post and then explain your problem to him.
Click to expand...
Click to collapse
Thanks for your reply!
I will do that
Meanwhile I managed to get a connection to my carrier by flashing h2o64's CM build 10-14 and then squid2's on top without wiping anything...

RR Lux 5.5.8 didn't work Wifi, after 2 clean instalation, wifi turn on and off then

CM reboots when making or receiving calls :confused:

Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.

This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.

Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs

Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.

pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.

J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs

Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.

I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.

Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.

It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.

J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.

pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.

J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.

rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.

Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.

Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps

It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.

Experience : successful Resurrection Remix NEM-L51 - Meticulus's ROM v5.8.5-20171214

Hi all XDA's members and Meticulus's RR ROM contributors,
I would like to share my experience with Meticulus's RR ROM for Honor 5C.
First I tried Elite V6 with no success : bootloop, F2FS or EXT4 nothing to do ; the Elite V7 is available from Christmas but I see that there are bugs to fix for Hassan, so I gave up and restored a backup of my STOCK system.
The restore was not good as my camera and audio no longer worked...
Before I get back to the STOCK update NEM-L51C432B357, I decided to try Meticulus's RR. It was a very good idea as I now have a renamed Honor 5c to hi6250 (...) working with no bug up to now.
LTE OK, SMS OK, GPS OK, SDCARD OK, AUDIO OK, VIDEO OK, GAPPS OK, MTP OK, etc
Adaway OK, Afwall+ OK, Magisk v14 OK
+ Bonus : Evie Launcher working as it was not using with STOCK ROM (icon size issue) !
Many thanks to Meticulus and contributors for sharing this very good work.
---
To be more precise for Honor 5C owners :
DEVICE : HONOR 5C
ROM STOCK BUILD : NEM-L51C432B350
MODDED RECOVERY .. : TWRP-3.1.1-0-hi6250-v5.2.zip
ROM INSTALLED .... : RR-N-v5.8.5-20171214-hi6250-Meticulus.zip
GAPPS INSTALLED .. : open_gapps-arm64-7.1-pico-20171225.zip
---
Steps of my successful installation with SDCARD and no SIM CARD :
1- FASTBOOT the TWRP then reboot to the TWRP RECOVERY
2- Wipe all except external SDCARD
3- Install the ROM
4- Reboot to TWRP RECOVERY
5- Install the GAPPS
6- Reboot to system (RR)
7- During RR Android setup, when asked insert the SIM CARD.
It would perhaps also have been successful with the SIM CARD inserted from the beginning...
---
Questions/feature requests :
- On Resurrection Remix site, I have not found your great ROM why ?
- On XDA Dev, there is no thread "Resurrection Remix For The Honor 5C [METICULUS]" but a "[ROM][7.1.2] Resurrection Remix For The Honor 6x [METICULUS]" one, this is why I put my comments here and in the Elite thread for those like me unable to get Elite V6 or V7 working with their Honor 5C.
- One thing is really missing to me (not found in settings) : the scheduled start/stop that worked very well with the STOCK ROM.
Do you think that this useful feature could be added on a future version ?
- The double TAP for screen wake up, would be a great bonus feature (was not provided in the STOCK ROM).
- Not tested the OTG, I will tell it in this thread.
Thanks again.
---
Meticulus's replies :
1. It is unlikely that any device with a kirin processor will get "official support" for LineagOS and therefore Resurrection Remix. There just isn't enough source.
2. Just because there is no "Honor 5c" thread doesn't mean you should come here and confuse information. It makes the water muddy. There is nothing stopping you from creating a thread in the "Honor 5c General" and post your experienced there.
3. Scheduled device start and sleep is not something I will work on.
4. DoubleTap 2 Wake only works on some P9 Lite's. Other devices with different touchscreens simply do not have the hardware capability.
5. I'm glad you like the ROM but please re-post your experiences in the Honor 5c section. I intend to delete these posts...

Is working dual sim and volte
Is works dual sim and volte

Sim working fine??

What do you think solved the audio issue?
Reverting to Stock Rom backup could have helped somehow.
Renaming it maybe ? And how did you rename it? After installing this rom mine became hi6250.
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Now installed this ResurrectionRemix twrp and rom after seeing this thread.Audio still refuses to work .

thatwasmyfakeacc said:
What do you think solved the audio issue?
Click to expand...
Click to collapse
I had the same problem on my NEM-L51. The problem is (or at least i think it is), that the vendor partition is somehow corrupted.
Short explaination, the vendor partition holds some drivers which are not open source (therefore not in the android kernel) and also aren't shipped in the custom roms (because of copyright stuff). So you always need to have them, if the custom rom depends on them (and most/all of the honor 5c custom roms do so). That's also the reason why you always have to flash the custom rom over your emui5.x and if you screwed your whole system, you first need to flash a backup or get back to emui on a different way before you can flash a working custom rom again.
So that's the explaination part. I installed twrp on my device, took a complete backup, flashed aosp from meticulus, everything worked except of Audio/Videos. Flashed LineageOS from Hassan, everything worked except of audio/video playback. Flashed backup, everything worked except audio/video. WTF. I don't know why, but i believe that the backups made with TWRP were somehow not complete, because flashing all partitions (the backup was over all partitions, triple checked, made new backups from stock) didn't solve audio issues, not even on the stock backup. What I now did was getting back to stock with the dload method, and flashed again directly the lineageos from hassan, which then worked. I had a try before where i first accidentially flashed aosp again, and same problems occured again. Also the now stock backup again didn't work. That's why i think that the TWRP backups for Honor 5c NEM-L51 are somehow not right.
Tl;dr if you have audio/video playback issues, try to get back to stock (make sure those features work on your stock rom) and flash again. If it still doesn't work, custom rom is maybe not compatible with nem-l51 (only experienced that with meticulus roms, hassans work great).
thatwasmyfakeacc said:
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Click to expand...
Click to collapse
Try again with the dload method, maybe use another UPDATE.zip. I had to try it several times, device booted sometimes for ever, and suddenly it worked. No idea why, but maybe try it again.

Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones

stevedat said:
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
Click to expand...
Click to collapse
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.

thelous said:
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
Click to expand...
Click to collapse
Rite, it's just for fun.

shankarjdhv125 said:
Is works dual sim and volte
Click to expand...
Click to collapse
Hi,
Dual SIM not tested, Volte I don't know if it works using my ISP (free.fr) and don't know how to check this.
An advice, don't update Magisk, I have done it on several rr (honor 5c, idol3 5.5), the result was bootloop.

Screen problem

Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.

Up :good:

When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.

Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.

Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.

Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !

HavocOS_3.7 (Android Q) ROM for Asus Max M2(ported)

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