Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
Could be. I had tried with Pico and super. Did not work for me
Sent from my Zuk Z1 using XDA Labs
None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...
Fahad305 said:
None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...
Click to expand...
Click to collapse
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs
SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I tried to flash Gapps Stock but it didn't work, Sim selection was still grayed out.
Flashed zui 2.5 Nougat and then clean flashed other Los Nougat ROMs and now Sim selection is working fine.
Thanks for the solution.
SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I've a same problem haunting me in LOS 14.1, I'll try your solution first...will let you know...
Sent from my ZUK Z1 using Tapatalk
Narasimha12 said:
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs
Click to expand...
Click to collapse
my file was corrupt i downloaded it again and bingo. working fine.
thanks
Narasimha12 said:
Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?
Click to expand...
Click to collapse
COS 12.1 sim selection was working out of the box.
CM 13 selection was working
LOS 14.1 selection stopped working
Flashed ZUI selection is back
& then clean flashed LOS again selection keeps working
Thanks a lot.
It must be radio baseband issue.
Sent from my ZUK Z1 using Tapatalk
Suggestion
Simply I tried this at my own,
And it worked!
Steps :
1. Install Lineage OS ROM from TWRP. (don't install Gapps)
2. Restart your android.
3. Skip all the startup steps after booting-up.
4. Now go to SIM settings and you see, you are able to select SIM for calls.
5. Select any SIM of your choice.
6. Reboot again into TWRP & install Gapps.
7. Reboot into system.
Now you see, you are able to select any SIM of your choice. :good:
Well...try updating kernel...it worked for me...try radioactive kernel(Radioactive reborn acuicultor) for nougat....here is the process
1)Go to twrp/cwm recovery
2)Perform factory reset and wipe dalvik,data,cache,system
3)first install any nougat rom then install any gapp package for nougat and finally the radioactive reborn kernel for nougat
4)reboot
Bam you are there...should work fine
https://forum.xda-developers.com/zuk-z1/help/network-solution-grayed-solved-t3545218
Can anyone help me in camera issue on nougat....after the clean flash when i open default camera app it works fine in auto mode but when switched to hdr mode then it crashes and says unknown error or cannot connect to camera this error occured in all the nougat rom excpet for los 14.1...Now for los 14.1 camera app works fine for few hours then it lags lije hell touch focus doesnt respond....plzz help
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
To access the Recovery you have to press the three buttons at the same time (vol+ / vol- / power).
Enviado desde mi ZUK Z1 mediante Tapatalk
happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
Just use "adb reboot recovery" in CMD with USB debugging enabled. Won't have to bother with key combinations. ZUI is installed on system, boot partition, and updates modem partition. Doesn't touch the recovery partition.
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
alot of people have this problem with 12.0 flash the 11.0 and dont update
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
jinkerz9430 said:
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
Click to expand...
Click to collapse
Did what you said and everything seems to be running smoothly, thanks very much for your help! Hoping a more updated kernel that doesn't force SuperSU and works with magisk comes out soon!
Hey all,
I have been stressing out about this the past week or two trying to get myself to a new rom.
AICP, Slimrom 7 and ViperOS seem to break my WiFi and cause my MAC address to default to 02:00:00:00:00:00.
Using my cellular data to set up my phone doesn't work either.
When I choose "don't use any network for set up," there seems to be no data connection (and obv no Wifi) to set up anything from the Playstore later on.
This happens every time flashing a rom that is not of OOS.
What are some ideas to get these roms a working?
I have to format through TWRP and reinstall OOS to get WiFi back rockin.
I am bored of OxygenOS. Help me out?
Maybe I'm overlooking another thread so link me if you can.
Thanks!
Are you clean flashing the ROMs? I haven't tried the ROMs you listed but I have had no luck with any AOSP ROMs on the OP5 because I get a poor phone signal on all of them--but I never had a problem with the WiFi. Maybe clean flash Pure Fusion which is popular and see if the WiFi issue still happens.
You might also be using ROMs that are incompatible with the firmware from whatever build of OOS you are running. Usually the ROM thread will tell you which firmware version you need and sometimes includes links to download the compatible firmware in zip form so you can flash it with the ROM.
Clean flash every time. I'll try Pure Fusion. When I was trying ViperOS there was a firmware and modem zip that went along with the flashing process. Even with that separate zip, I resulted with the same WiFi situation.
Just went from
format data > freedomOS (working wifi) > format data > wipe & formats> Pure Fusion > Gapps nano > magisk 14.3
boot to setup and errors say
com.android.phone has stopped
From the boot up errors I decided to go new rom. Did the wipes necessary to flash Ressurection Remix and this seems to be running ok. I am confident that flashing a new rom will break WiFi, so I'm gonna ride Resurrection Remix out for now.
ckrummi said:
Just went from
format data > freedomOS (working wifi) > format data > wipe & formats> Pure Fusion > Gapps nano > magisk 14.3
boot to setup and errors say
com.android.phone has stopped
Click to expand...
Click to collapse
You just need to reboot once you get to the setup screen and those errors go away
I was a flashaholic with my Nexus 6P, so when I received my OP5 3 weeks ago, I went flashing within minutes
I was having the same issue...but I was able to connect to WIFI...but certain 5GHz wifi SSIDs were giving me issues and it would not let me connect.
Happened with decrypted & encrypted ROMS
right now I'm stuck on OOS 4.5.13 (which isn't a bad stock ROM at all) until I find a thread with a solution.
hi there,
I got a new AGM phone model A1Q some weeks ago, and I am manage to install LOS (unofficial) found on a China website, because the phone go wrong after trying to install Gapps, making none apps work.
After several trials, LOS install to the phone with working Gapps, however I got 2 issues right now.
1. the screen never come back after screen is off, I have to reboot the phone to get it back.
2. notification bar is not updating, I am using Nova Launcher right now, I tried disabled the notification bar and reboot, nothing happen.
For the moment, I am not able to get back TWRP recovery after installing LOS, I have to figure out other way to redo the LOS installation.
Please someone throw me some suggestions.
Sorry for my bad English.
algebrathebard said:
hi there,
I got a new AGM phone model A1Q some weeks ago, and I am manage to install LOS (unofficial) found on a China website, because the phone go wrong after trying to install Gapps, making none apps work.
After several trials, LOS install to the phone with working Gapps, however I got 2 issues right now.
1. the screen never come back after screen is off, I have to reboot the phone to get it back.
2. notification bar is not updating, I am using Nova Launcher right now, I tried disabled the notification bar and reboot, nothing happen.
For the moment, I am not able to get back TWRP recovery after installing LOS, I have to figure out other way to redo the LOS installation.
Please someone throw me some suggestions.
Sorry for my bad English.
Click to expand...
Click to collapse
Update:
Notification bar issue fixed after several reboot, but screen issue still exist.
I am running LineageOS 17.1 (ver. 0.2.11.202414 ) with microg on my oneplus 6T.
I am totally happy with it except that sometimes my nfc is not working on my yubikey but with this i can life.
My main problem i have with updates to newer builds. They are released every week and under settings->system->advanced->updater I can see the builds that i could download and install. Also the OS is reminding me that i should update to newer versions.
I did it once and I softbricked my phone and i dont understand why...
On the LOS guide the steps mentioned are these:
Open Settings, navigate to “System”, then “Updater”.
Click the Refresh Icon in the top right corner.
Choose which update you’d like and press “Download”.
When the download completes, click “Install”. Once the update process has finished, the device will display a “Reboot” button, you may need to go into the Updater menu in Settings, “System” to see it. This will reboot you into the updated system
This is for shore not working with my version and microg variant.
How should i proper update my OS to a newer build version?
Does nobody have a hint for me?
marsxxl said:
Does nobody have a hint for me?
Click to expand...
Click to collapse
Maybe try asking in the Lineage thread.
marsxxl said:
I am running LineageOS 17.1 (ver. 0.2.11.202414 ) with microg on my oneplus 6T.
Click to expand...
Click to collapse
The updater had issues originally. Although since you are using microg, you might have issues anyways. Now it would probably work if you were using a stock version of Lineage. Personally I still just use TWRP to update.
I have a guide here: Installing Lineage, it covers updating.
The only time I ran MicroG for any length of time was Omni, but it was still updated the same way.
You should be able to just flash the new build in recovery, flash the TWRP installer, reboot to recovery, flash Magisk if you use it, reboot to system. Since at this point, most modules will cause problems if flashed in TWRP.
I don't know how old your phone's firmware is, but there was a point in there LOS started checking for the updated firmware, so you maybe forced to update too. It should check before it flashes anyways. So just know if it errors out, you'll be updating everything. Be prepared to backup and clean install if you have to.
Thank you a lot @OhioYJ !
I was able to do the Update
If someone is interested in the NFC problem that I have, i will post it here:
https://forum.xda-developers.com/t/nfc-not-working.3945659/#post-84280433