I had magisk working for quite a while on B25 with no issues (besides it saying it needs to close but still worked) but now Android Pay stopped working. Does anyone have a fix for this?
does no one know how to get this to work?
Related
Hello:
After some tinkering with my new x522 (LeEco Le S3), I managed to install Resurrection Remix (RR-N-v5.8.3-20170728-s2-Official.zip) on it. I did a clean flash of it first thing after I rooted it, but I did not have working SIM/4G data. After restoring to the factory image S2_X520-CN-FN-IEXCNFN5902605131S-5.9.026S.zip (because my stock backup did not fix the SIM issue) and getting SIM and VoLTE functionality back, I did a dirty flash of RR, which kept the cellular capabilities (although I think I lost VoLTE).
However, when I install the SuperSU zip, I lose the cellular capabilities. I can get it back by doing a dirty flash of RR again. Anyone know of a way to keep cellular functionality without running into this issue? Thanks in advance!
EDIT: Solution: I noticed the issue with Lineage OS as well, and figured it was SuperSU causing problems. I am using Magisk and RR without issues so far. Even got VoLTE working.
screamingoutlet said:
Hello:
After some tinkering with my new x522 (LeEco Le S3), I managed to install Resurrection Remix (RR-N-v5.8.3-20170728-s2-Official.zip) on it. I did a clean flash of it first thing after I rooted it, but I did not have working SIM/4G data. After restoring to the factory image S2_X520-CN-FN-IEXCNFN5902605131S-5.9.026S.zip (because my stock backup did not fix the SIM issue) and getting SIM and VoLTE functionality back, I did a dirty flash of RR, which kept the cellular capabilities (although I think I lost VoLTE).
However, when I install the SuperSU zip, I lose the cellular capabilities. I can get it back by doing a dirty flash of RR again. Anyone know of a way to keep cellular functionality without running into this issue? Thanks in advance!
EDIT: Solution: I noticed the issue with Lineage OS as well, and figured it was SuperSU causing problems. I am using Magisk and RR without issues so far. Even got VoLTE working.
Click to expand...
Click to collapse
An older version of SuperSu had these issues, current version should work like magisk does.
screamingoutlet said:
Hello:
After some tinkering with my new x522 (LeEco Le S3), I managed to install Resurrection Remix (RR-N-v5.8.3-20170728-s2-Official.zip) on it. I did a clean flash of it first thing after I rooted it, but I did not have working SIM/4G data. After restoring to the factory image S2_X520-CN-FN-IEXCNFN5902605131S-5.9.026S.zip (because my stock backup did not fix the SIM issue) and getting SIM and VoLTE functionality back, I did a dirty flash of RR, which kept the cellular capabilities (although I think I lost VoLTE).
However, when I install the SuperSU zip, I lose the cellular capabilities. I can get it back by doing a dirty flash of RR again. Anyone know of a way to keep cellular functionality without running into this issue? Thanks in advance!
EDIT: Solution: I noticed the issue with Lineage OS as well, and figured it was SuperSU causing problems. I am using Magisk and RR without issues so far. Even got VoLTE working.
Click to expand...
Click to collapse
Can you please upload the "S2_X520-CN-FN-IEXCNFN5902605131S-5.9.026S.zip" file? I want to update my EUI on my Le 2 x520. It's currently 5.28
Hey!
today I noticed something very weird on my OnePlus 5 (64GB)
somehow unlocking the phone with the fingerprint scanner isn't working anymore!
it always says that I have to use my code, like when you unlock it the first time after powering on!
the hardware is working, fingerprint scan works for example fine with my banking app and the option is still available in the settings menu!
Android 7.1.1
security patch 1st september 2017
francokernel 4.4.21
xxx nolimits rom 4.2 based on oos 4.5.14
rooted with magisk
xposed framework v88.2 installed
I did not make any changes to the phone, it simply stopped working!
I have already removed the security unlock and added new fingerprint scans, it did not work...
can anybody help me?
Are you using Greenify? If so, make sure "Alternative Screen Off mode" is enabled in Settings.
Sent from my ONEPLUS A5000 using Tapatalk
Just restart your phone and all works fine again...
If your fingerprint unlock still doesn't work I would try stock OOS instead of xXx No Limits and see if you still have the issue. I found that ROM extremely buggy both times I tried to run it and the other stock based ROM I tried (Freedom) really wasn't much better.
okey I fixed it by wiping cache and dalvik
thanks for your answers
So on every GSI rom I've tried (currently on phh-treble pie and it's working great btw), I can never get the device google play certified with opengapps. It works fine for a while, but after a few days I get the notification, and some apps become entirely unusable. Reading up about this, apparently it requires the device fingerprint from the build.prop from a stock rom in order to obtain certification (from this thread) - however I didn't back up this before wiping.
If I had to, I could reflash stock, get the fingerprint, and reflash again - but that takes a lot of time and effort. So I'm just wondering if someone could upload a stock build.prop for the P10 lite (hopefully WAS-LX1A) with the fingerprint (if the information it contains isn't too sensitive). Either that, or someone could let me know of an alternate method to get certification (or at least rid of the damn popups and app blocks).
Any help would be appreciated, thanks so much
jekblub said:
So on every GSI rom I've tried (currently on phh-treble pie and it's working great btw), I can never get the device google play certified with opengapps. It works fine for a while, but after a few days I get the notification, and some apps become entirely unusable. Reading up about this, apparently it requires the device fingerprint from the build.prop from a stock rom in order to obtain certification (from this thread) - however I didn't back up this before wiping.
If I had to, I could reflash stock, get the fingerprint, and reflash again - but that takes a lot of time and effort. So I'm just wondering if someone could upload a stock build.prop for the P10 lite (hopefully WAS-LX1A) with the fingerprint (if the information it contains isn't too sensitive). Either that, or someone could let me know of an alternate method to get certification (or at least rid of the damn popups and app blocks).
Any help would be appreciated, thanks so much
Click to expand...
Click to collapse
Here is a fingerprint that I took from my device a few months ago. It's for Was-LX1C432B368. I have never tested it though except for CypherOS which I only got to pass safety net after installing the universal safety net patch.
DeathBell said:
Here is a fingerprint that I took from my device a few months ago. It's for Was-LX1C432B368. I have never tested it though except for CypherOS which I only got to pass safety net after installing the universal safety net patch.
Click to expand...
Click to collapse
Thank you! Set it as fingerprint, but didn't immediately pass safetynet. Once I installed the universal fix it seemed to work, but also seems to break magisk! Well at least my device says it's certified now lol
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
GTF696 said:
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
Click to expand...
Click to collapse
Try magisk as root method insted of su...
Other than that, cant think any other solution
GTF696 said:
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
Click to expand...
Click to collapse
I got error when installed lineageos15.0 on twrp 3.2.3 , suddenly automatic restart. Can you help me dude ?
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 !