Related
I have a stock rooted Galaxy s5. For a while now the fingerprint scanner would stop reading fingerprints (nothing would be detected when swiped, no "no match" or "swipe faster" type errors, just no reading at all). This was always fixed by simply rebooting the device. That was until now. After encountering that error again I rebooted the phone. Now it appears to scan the fingerprint but won't match. I've tried all three of the fingers I have registered with the same results. I also can't access the fingerprint manager. When I try to access the fingerprint manager it won't match the fingerprints and says I have the wrong alternative password (which obviously I don't since I was able to bypass the lock screen with it). It does accept the alternate password when I tried to change the password but when I press the last "OK" to change the password it says " an error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device". I have restarted more than once.
Has anyone experienced anything similar to this? is this a defective sensor? I have unlimited data and had to use a loophole to upgrade to this phone so getting support form verizon might be a bit difficult.
finger print scanner tab s
Hello. You bet i have! Just tonight. I have a rooted samsung tab s, I was receiving the exact error messages that you speak of. Swipe slower, blah blah. Now, my tablet will not offer fingerprint scanner- it just disappeared entirely! And my alternative password says it is incorrect when I know it isnt. It doesnt give me an option to retrieve my password either! So, no fingerprint scanner, and incorrect alt password- im hooped! I cannot get into my 600$ tablet that I am currently using for online courses!
Please, if anyone can help me get into my tablet, I will forever be grateful!
I just installed lollipop, not sure if that would have anything to do with it? Another recent install was inbox gmail.
Please what can I do?
Disappointed
Stuck on my s3 for all of my homework too!
Irritated
I have same problem since 1 week.
SMG900H
XTRESTOLITE 1.4
CWM PHILLZ TOUCH 6.48
You need to flash the aroma add-on package. From there, try to select/install an add-on that states "finger print(or something close to the term)". That's what i've done.
Sent from my SM-G900F using XDA Free mobile app
fatfingers25 said:
You need to flash the aroma add-on package. From there, try to select/install an add-on that states "finger print(or something close to the term)". That's what i've done.
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
he said nothing about a custom rom. He is using stock rooted, so flashing an aroma add-on package will not help.
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
worf65 said:
I have a stock rooted Galaxy s5. For a while now the fingerprint scanner would stop reading fingerprints (nothing would be detected when swiped, no "no match" or "swipe faster" type errors, just no reading at all). This was always fixed by simply rebooting the device. That was until now. After encountering that error again I rebooted the phone. Now it appears to scan the fingerprint but won't match. I've tried all three of the fingers I have registered with the same results. I also can't access the fingerprint manager. When I try to access the fingerprint manager it won't match the fingerprints and says I have the wrong alternative password (which obviously I don't since I was able to bypass the lock screen with it). It does accept the alternate password when I tried to change the password but when I press the last "OK" to change the password it says " an error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device". I have restarted more than once.
Has anyone experienced anything similar to this? is this a defective sensor? I have unlimited data and had to use a loophole to upgrade to this phone so getting support form verizon might be a bit difficult.
Click to expand...
Click to collapse
Try reflashing the stock rom via odin.
my bad
guetzli32 said:
he said nothing about a custom rom. He is using stock rooted, so flashing an aroma add-on package will not help.
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
Try reflashing the stock rom via odin.
Click to expand...
Click to collapse
so sorry it was a mistake. i did not noticed that. Thank you. I expected that he has xtrestolite too because of this thread.
HELP!
guetzli32 said:
he said nothing about a custom rom. He is using stock rooted, so flashing an aroma add-on package will not help.
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
Try reflashing the stock rom via odin.
Click to expand...
Click to collapse
will you please help me how to do this---->"Try reflashing the stock rom via odin"
i have just gotten my s5 two weeks ago, it was working perfectly until i charge it yesterday evening, fingerscanner suddenly stopped working and i only got that error message to restart it.. i have tried restart and shutting it down overnight and in the morning it is still not working! i have cleared the cached in the setting and still no response... gonna try to factory reset it but i dont know yet if it will work, im still backing up my files... help please
Every time I turn off the screen while music is playing , there is a short (<1s) glitch/skip/interruption in playback.
I've had this happen on both stock kernel and Veno's kernels which I am currently using, so I think we can safely assume it's not ralated to the kernel.
I tried all the usual like cache/dalvik wipe, cold booting, setting Google Music as a system app, using it as a user app and adding it the the list of protected app in Huawei's power manager, even a factory reset but nothing fixes this.
One weird thing is that for a while, this behavior stopped by itself for a few days only to come back a few days later.
Running stock b170, Meticulus TWRP, Magisk rooted, systemless Xposed, Viper4Android (via Magisk, as a system app)
Any ideas? It's bugging me like crazy.
It's from the audio drivers.
Johnny TDN said:
It's from the audio drivers.
Click to expand...
Click to collapse
Ok, and is there a fix?
All of the sudden and without me doing anything at all, music playback no longer skips when turning off the screen. What the.
Later edit: the glitch is back.
Just a small shameless bump.
I have the same problem.
try to give permisson to not enter in doze mode in battery settings
---------- Post added at 06:35 PM ---------- Previous post was at 06:34 PM ----------
i never had that problem..
hugor671 said:
try to give permisson to not enter in doze mode in battery settings
---------- Post added at 06:35 PM ---------- Previous post was at 06:34 PM ----------
i never had that problem..
Click to expand...
Click to collapse
Setting my music app to not close in the close battery when locked setting under battery. That I have already tried but it's not working. My music still cuts off when I lock my phone. The widget sometimes disappear from the lock screen too.
my phone is rooted and was wondering if any app out there could prevent this annoying problem from happening...
zgomot said:
Every time I turn off the screen while music is playing , there is a short (<1s) glitch/skip/interruption in playback.
I've had this happen on both stock kernel and Veno's kernels which I am currently using, so I think we can safely assume it's not ralated to the kernel.
I tried all the usual like cache/dalvik wipe, cold booting, setting Google Music as a system app, using it as a user app and adding it the the list of protected app in Huawei's power manager, even a factory reset but nothing fixes this.
One weird thing is that for a while, this behavior stopped by itself for a few days only to come back a few days later.
Running stock b170, Meticulus TWRP, Magisk rooted, systemless Xposed, Viper4Android (via Magisk, as a system app)
Any ideas? It's bugging me like crazy.
Click to expand...
Click to collapse
Have you tried another music player?
I need help, as i'm going mentally crazy :crying: :silly: lol.
I have phone: Nubia Z17 Mini S
Model: NX589J
Android: 7.1.1.
Official chinese rom: Build number: NX589J_CNCommon_V212 (this is the latest version). Downloaded from here: http://ui.nubia.cn/rom/detail/49
I did the following (see detailed discription below) but when i open the google playstore icon on the phone it displays Checking info message for few seconds and then it crashes/shut itself off... Or it just won't open! Even after rebooting several times.
This is what i did, someone please tell me what i did wrong, how to fix this issue, did i do the steps wrong or in wrong order?:
Steps i took-->
1. updating the rom/firmware to latest version.
2. install twrp recovery on phone.
3. root (by selecting root option in twrp recovery on phone)
4. reboot.
5. turning phone off, then on with power and volume button to be back in twrp recovery.
6. selecting install, to install gapps zip file (downloaded from open gaps site)
7. after instalation wiping dalvik/cache and then reboot.
I don't know it anymore :crying::crying::crying::crying: How do i make google playstore work on this phone?
TWRP options?
See attachement, can someone give me the english translation of the various options or how can i make the language change to english? :silly:
Hi sweetautumn,
Can you please help by sharing the link where did you get the script used for rooting, now regarding the picture i think is similar used for Z17 Mini below the translation
BR,
Hi sweetautumn,
I found solution on russian forum, u need switch airplane mode on, wait 1-2 minute, and switch airplane mode off, than playstore will working fine.
sweetautumn said:
I need help, as i'm going mentally crazy :crying: :silly: lol.
I have phone: Nubia Z17 Mini S
Model: NX589J
Android: 7.1.1.
Official chinese rom: Build number: NX589J_CNCommon_V212 (this is the latest version). Downloaded from here: http://ui.nubia.cn/rom/detail/49
I did the following (see detailed discription below) but when i open the google playstore icon on the phone it displays Checking info message for few seconds and then it crashes/shut itself off... Or it just won't open! Even after rebooting several times.
This is what i did, someone please tell me what i did wrong, how to fix this issue, did i do the steps wrong or in wrong order?:
Steps i took-->
1. updating the rom/firmware to latest version.
2. install twrp recovery on phone.
3. root (by selecting root option in twrp recovery on phone)
4. reboot.
5. turning phone off, then on with power and volume button to be back in twrp recovery.
6. selecting install, to install gapps zip file (downloaded from open gaps site)
7. after instalation wiping dalvik/cache and then reboot.
I don't know it anymore :crying::crying::crying::crying: How do i make google playstore work on this phone?
Click to expand...
Click to collapse
How do I install TWRP in NX589J version ?
rsinet said:
How do I install TWRP in NX589J version ?
Click to expand...
Click to collapse
What is your ROM buildnumber?
V2.16 Stable version
rsinet said:
V2.16 Stable version
Click to expand...
Click to collapse
CN or EU or VS version? Mine is CNCommon_V212
CN. Where can I find US ROM and how tô flash it?
sweetautumn said:
CN or EU or VS version? Mine is CNCommon_V212
Click to expand...
Click to collapse
CN. Where can I find US ROM and how to flash it?
sweetautumn said:
I need help, as i'm going mentally crazy :crying: :silly: lol.
I have phone: Nubia Z17 Mini S
Model: NX589J
Android: 7.1.1.
Official chinese rom: Build number: NX589J_CNCommon_V212 (this is the latest version). Downloaded from here:
I did the following (see detailed discription below) but when i open the google playstore icon on the phone it displays Checking info message for few seconds and then it crashes/shut itself off... Or it just won't open! Even after rebooting several times.
Click to expand...
Click to collapse
dear sveetautumn. Tell me, please, did you manage to solve the problem with Google services or not? I have the same problem and flight mode does not help. It is impossible to give all permissions for Google applications, since the list of permissions is empty and written "does not require special permissions"
vio47 said:
dear sveetautumn. Tell me, please, did you manage to solve the problem with Google services or not? I have the same problem and flight mode does not help. It is impossible to give all permissions for Google applications, since the list of permissions is empty and written "does not require special permissions"
Click to expand...
Click to collapse
This is the exact same behaviour I have on my z17 mini S too. Tried all sorts and can't find a way to apply permissions to it. Even 3rd party permission apps...
In the end, we found the solution to run Google services for Nubia Z17 miniS nx589j
In the end, we found the solution to run Google services for Nubia Z17 miniS nx589j
Nubia Z17 miniS, nx589j, ui5 v2.16 official CN
After installing TWRP and root and SuperSu nx589j, open the phone, go to this page and download this open gapps: Open GApps
1.1.2.apk
Once you have installed this gapps, open the installed program, accept all grant in SuperSu, and soften the steps in it, as you find the phone settings, and let it download that gapps yourself. It has about 750mb.
After finishing the download, click on the installation, and the phone automatically enters the TWRP and installs the GAPPS.
After it is finished installing in TWRP, the phone opens itself.
Once opened, rejoin the TWRP and click WIPE cache and dalvik.
That's it, I spent a week to find the solution.
If it is ok and it works, please leave here a comment.
I'm sorry for my english.
thanks demyco79, followed your steps and have finally GAPPs running on my Z17 mini s. Downloads from playstore sometimes hang, and some apps don't seem to authenticate well with google account
demyco79 said:
In the end, we found the solution to run Google services for Nubia Z17 miniS nx589j
Nubia Z17 miniS, nx589j, ui5 v2.16 official CN
After installing TWRP and root and SuperSu nx589j, open the phone, go to this page and download this open gapps: Open GApps
1.1.2.apk
Once you have installed this gapps, open the installed program, accept all grant in SuperSu, and soften the steps in it, as you find the phone settings, and let it download that gapps yourself. It has about 750mb.
After finishing the download, click on the installation, and the phone automatically enters the TWRP and installs the GAPPS.
After it is finished installing in TWRP, the phone opens itself.
Once opened, rejoin the TWRP and click WIPE cache and dalvik.
That's it, I spent a week to find the solution.
If it is ok and it works, please leave here a comment.
I'm sorry for my english.
Click to expand...
Click to collapse
Works for me too. Version V2_16. But what have you done about battery consumption? It drains too fast.
mbrockma said:
thanks demyco79, followed your steps and have finally GAPPs running on my Z17 mini s. Downloads from playstore sometimes hang, and some apps don't seem to authenticate well with google account
Click to expand...
Click to collapse
To me it works well. if you're having trouble, put your phone in airplane mode for a few seconds, then you get back to normal.
---------- Post added at 04:56 PM ---------- Previous post was at 04:49 PM ----------
rsinet said:
Works for me too. Version V2_16. But what have you done about battery consumption? It drains too fast.
Click to expand...
Click to collapse
Open the application Neosafe / Power / Power saving mode, and choose Lower-power mode. After activating the Lower-power mode, the battery icon changes from white to yellow. Everything works well and the battery keeps you well.
Hey!
Where did you get the TWRP installation file for the MiniS?
Struggling over here without any Play Services as well >_<
Risuno said:
Hey!
Where did you get the TWRP installation file for the MiniS?
Struggling over here without any Play Services as well >_<
Click to expand...
Click to collapse
drive dot google dot com/file/d/1__yeGVETgxk4tCcx2gFij5eHDwLWzOAc/view
Thanks, will check asap!
---------- Post added at 07:51 PM ---------- Previous post was at 07:31 PM ----------
I got stuck at unlocking the bootloader. :/
After the "fastboot oem unlock" command I get a "waiting for device" message without any response.
Used this tutorial here: https://www.theandroidsoul.com/unlock-bootloader-via-fastboot-android/
Just realized, that Windows recognizes the phone as mobile device NX589J.
But as soon as I go into fastboot the yellow sign flashes up in the device manager as "Android device".
I installed the drivers with the ADB installation, but that doesn't seem to be the issue.
Are there specific drivers for the NX589J somewhere?
[ROM] [8.1.0] [UNOFFICIAL] Resurrection Remix 6.2.1 Oreo Stable-4.0 Release Victara (Moto X 2014)
Updated on 13th November 2018 with Version 6.2.2 Oreo Stable 4.0
Hey Folks:
Finally RR 6.1.0 Oreo presenting for Victara, with lot of tweeks as per RR standard.
Resurrection Remix 8.1.0 Unofficial (STABLE VERSION) for Victara moto x2 2014 By Chinese developers
Dated: 18th June 2018
Battery life check and confirm please.
What's not working
1: Pattern lock late response first time.
2: HDR (waiting for Fix)
3: NFC (Not working)
Other you can tell
What's Working:
1:Almost everything you need for daily use
2: Video recording working
3: All customization of RR 6.1.0
How can i describe lots of customization you can check by yourself and report if any not working.
Other you can check and report bugs for improvement!!!
What you need:
MOTO X2 2014 Victara device
( Unlocked boot loader having TWRP 3.2.1.0 old versions won't work for 8.1)
[GUIDE] (Please Read from point 5 onward with concentration)
1: Download ROM and Unofficial 8.1 Gapps nano or as your taste from below links
2: Open TWRP and prepare all internal storage backup and your NANDROID backup.
3: Open Wipe, Advance Wipe and Change file system and Format Data, system, Cache with ext4
This will erase all your data (If you are already at ext4 then no need to wipe with ext4)
4: Now in TWRP connect device with PC or have a OTG USB with files and copy files in internal storage i.e. ROM zip and gapps zip
5: Now flash ROM zip and reboot system and setup everything
6: You will see some Chinese apps, You can remove them by Root uninstaller, this ROM is rooted by default.
7: Go to setting, developer options and click advance reboot.
8: Now reboot to Recovery and go to gapps and flash then reboot. (You must have latest gapps from opengapps.org or you will need to update play services manually)
Here you done.
If any issue please ask me at G+ anytime
DOWNLOAD LINKS:
Version RR-O-v6.2.1-Stable 4.0_Release
https://mega.nz/#!J35jCCbQ!fDYhmcbOkESLtVLyTTd6lJUrPhxI-9DA8ipFarE39NE
version 1.0
RR-O-v6.1.0-Stable1.0-victara_Release 18062018
GAPPS Official 8.1.0: LINK
Link available at same link above.
ALL DONE HERE
i have already tested this ROM Very good battery and smooth ROM... as far as will get next Update then share according...
SEE YA...
Reserved and Screenshots:
Edit: Recommended full partition format with EXT4,
Results: each and every customization is working.
Simply perfect, everithing that i use and all the tweaks are there. Only this message on start: (using stock gapps)
jeferson1979 said:
Simply perfect, everithing that i use and all the tweaks are there. Only this message on start: (using stock gapps)
Click to expand...
Click to collapse
I asked to resolve the issue and he's sending me v2.0.
zahidm said:
Reserved ans Screenshots:
Click to expand...
Click to collapse
stuck at boot logo, moto x2
---------- Post added at 12:01 PM ---------- Previous post was at 11:57 AM ----------
to install separate gapps?
wladoom said:
stuck at boot logo, moto x2
---------- Post added at 12:01 PM ---------- Previous post was at 11:57 AM ----------
to install separate gapps?
Click to expand...
Click to collapse
Yes install gapps after booting up and changing language.
Edit: One thing i forget to mention that if your play services are outdated than pleass update manually or you will be unable to sign in google account, it will freez at checking Info...
zahidm said:
Yes install gapps after booting up and changing language.
Edit: One thing i forget to mention that if your play services are outdated than pleass update manually or you will be unable to sign in google account, it will freez at checking Info...
Click to expand...
Click to collapse
With gapps stock flashed at the same time works at the first try, without problems
---------- Post added at 06:04 PM ---------- Previous post was at 05:28 PM ----------
Just one question, why in Oreo ROMs selinux are set permissive? Is there some conflict? And If i set manualy to enforcing?
Thanks in advance
Still does not work..
wladoom said:
Still does not work..
Click to expand...
Click to collapse
What is not working?
If you encounter any problem it is recommended to format data partition with EXT4 you will have no issues, i encounters some problems than i asked developer and he recommended this..
the link is broken
Leonardoliveira said:
the link is broken
Click to expand...
Click to collapse
https://mega.nz/#!2dsFkaLJ!Jvj5w0iFvCYqdqungCOimljUM6PsBBwAxtT4VJZOWt4
Leonardoliveira said:
the link is broken
Click to expand...
Click to collapse
No, it's not i just checked, anyhow updated again...
Anybody checked PIN/PATTERN lock? Please share your experience! Thanks
What's your experience with this RR 6.1.0? mine is very good,
zahidm said:
What's your experience with this RR 6.1.0? mine is very good,
Click to expand...
Click to collapse
Here is the best as possible
Hey, I've got one issue here. No input methods. Are all. Just the "Google Voice" from the nano open gapps package appears. But gboard doesn't show up. Whats going on?
warutzu said:
Hey, I've got one issue here. No input methods. Are all. Just the "Google Voice" from the nano open gapps package appears. But gboard doesn't show up. Whats going on?
Click to expand...
Click to collapse
Use stock gapps
warutzu said:
Hey, I've got one issue here. No input methods. Are all. Just the "Google Voice" from the nano open gapps package appears. But gboard doesn't show up. Whats going on?
Click to expand...
Click to collapse
There is a Keyboard in ROM named Ifly, just go to keyboard setting and activate Ifly, it's Chinese keyboard, than yoi can download from anywhere...
Data network not working
I changed from Mokee to this ROM and below are the issues
1. No data connectivity. Only WiFi is working. I changed all the modes - LTE, WCDMA, GSM etc. - but nothing worked. And now no matter which ROM I flash, this issue persists
2. I used stock gapps 8.1 as mentioned but still it is not giving any google input keyboard
3. Google play services issue keeps popping up, even though I flashed latest gapps
4. Music app keeps stopping and giving error
Any inputs on how to fix the data connectivity issue?
Andyvn said:
I changed from Mokee to this ROM and below are the issues
1. No data connectivity. Only WiFi is working. I changed all the modes - LTE, WCDMA, GSM etc. - but nothing worked. And now no matter which ROM I flash, this issue persists
2. I used stock gapps 8.1 as mentioned but still it is not giving any google input keyboard
3. Google play services issue keeps popping up, even though I flashed latest gapps
4. Music app keeps stopping and giving error
Any inputs on how to fix the data connectivity issue?
Click to expand...
Click to collapse
About music, give the permissions about storage, Data conect: can you make Phone calls? If not, flash stock rom
Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10
Device:
Rooted OP 6t, OxygenOS 10.3, stock recovery, Magisk 20.2, Magisk Manager 7.5.0
What did I do:
I updated from the last OxygenOS 9 Version to OxygenOS 10.3 by uninstalling magisk, restoring images and doing the manual update through the downloaded full image. Reinstall magisk. It all went well. First boot took a while but went through.
SIM was not recognised at all.
I've reset all network settings and cleared cache and data of com.android.phone.PhoneApp.
Found out here that its due to a call record magisk module which I uninstalled. Mobile data is working just fine since then.
I tried to uninstall magisk and reinstall it before rebooting in order to keep the possibility to keep root as I do not have twrp installed. (suggested here). I guess this is unrelated.
Issue:
I cannot access the SIM & Network Settings. When I try, the app com.android.phone crashes instantly.
Logs throw these warnings:
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.telephony.action.CARRIER_CONFIG_CHANGED flg=0x15000010 (has extras) }: process is bad
Is there a way to check the carrier config or renew it?
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x5000010 (has extras) }: process is bad
Hows the SIM state changing?
and this Error:
Code:
Sending non-protected broadcast com.android.internal.telephony.ACTION_IMS_CAPABILITY_STATUS_CHANGE from system 1102:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:15963)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:16666)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15980)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:16808)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1422)
at com.android.server.TelephonyRegistry.broadcastImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2644)
at com.android.server.TelephonyRegistry.notifyImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2636)
at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:964)
at android.os.Binder.execTransactInternal(Binder.java:1032)
at android.os.Binder.execTransact(Binder.java:1005)
I am not sure what to do. But I do want to avoid a full factory reset.
Thanks for your hints.
Alternatively is it possible to access the settings of this submenu through a different app or way?
hey_malik said:
Alternatively is it possible to access the settings of this submenu through a different app or way?
Click to expand...
Click to collapse
Sounds like a bad flash, or you didn't factory reset. If you update from 9 to 10 without wiping data, **** can happen
True, I did not because I don't want to set up the whole phone afterwards.
Could it be a solution to flash the ROM again through the integrated update system? Or would I then need to install twrp? I haven't done this in ages
Have you got any magisk module active?
estapagu said:
Have you got any magisk module active?
Click to expand...
Click to collapse
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
hey_malik said:
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
Click to expand...
Click to collapse
I had some SIM problems at the beginning related to a magisk module but I can't remember which. And another problem with WiFi after OTA update using magisk OTA udapte method, so finaly I deleted Magisk completely and updated from TWRP
Just to get this straight:
I may in a first step boot a twrp image (just boot) dirty flash the latest stock image, flash magisk (or not and lose root for the moment which is no issue because I have an unlocked boot loader) and see if the issue is still present. If yes a clean wipe and install is in order?!
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Dadditz said:
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Click to expand...
Click to collapse
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
hey_malik said:
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
Click to expand...
Click to collapse
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Dadditz said:
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Click to expand...
Click to collapse
I suggest you boot to Twrp, then flash the Twrp. Get inside twrp and flash these > OOS, Twrp, Magisk Then reboot again to twrp repeat > OOS, Twrp, Magisk. And for the last time reboot again to twrp and flash the Magisk.
You will be good to go. :good:
Is there any risk involved concerning the encryption?
hey_malik said:
Is there any risk involved concerning the encryption?
Click to expand...
Click to collapse
As you already mentioned, you are in Android 10, and if you are using the correct Twrp. There won't be any.
Still it's always better to take a back up just in case if something goes wrong.
Stuck with the same issue. Did you manage to get it fixed somehow?
Actually the latest available oo update to 10.3.1 fixed it.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Lucky you. I got this issue when switching to 10.3.1 from 9. I tried flashing 10.3.1 once again. Didn't work.
You need to uninstall Magisk then factory reset, it will get rid of all Magisk modules ghost residues. Then flash Magisk again with fastboot twrp method. I had this and going back to factory state was the only fix. No need to flash again and again the rom it doesn't touch Magisk data in /data partition.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Just an update, this worked for me too. Thanks for posting that tip else I would have went ahead and reset the phone. You saved me a hell lot of trouble.
Additionally, I figured out a solution which might work for people still having this issue. I haven't tested this myself since I found this after my issue was solved.
The reason why the issue happened to us is because the system app "Phone Services" was missing, or not installed properly while dirty flashing. There is an alternative hidden activity for sim settings called "com.android.settings.network.telephony.MobileNetworkActivity", which is not a part of Phone Services app, but a part of the Settings app itself. This could be invoked using any activity launcher apps available in the Play Store.
Also, this activity gives more advanced sim settings too. So, probably worth a look if interested.
Same problem here, but fixed!!
Sim not working anymore after update to Magisk 21.2. nothing would change it.
After installing previous version (21.1) the problem persisted. After almost giving up, I found this thread. Simply uninstalled the OOS Native Call Enabbler module and everything workes like a charm again!!!
So it was an easy fix (once you know) and I am very thankful, because I would never have thougt of it! Unfortunately I cannot record Calls anymore, nor find the module now that I am successfully running on 21.2 again with working SIM. Though the choice between being able to use my SIM or record calls was easy
Hope someone finds use of this info.
As mentioned before Encryption is not a problem if the right TWRP version is used.
Put in you password (or pin) and all is nicely decrypted and reachable in TWRP Recovery.
Good luck to all!
PS: still hoping for a new (compatible) call recorder module though