Hi. I was install LineaseOS 17.1 to xz2c. Then, installed the app that I use.
But, Some apps not work because, Rooting detected from my Phone.
Of course, I didn't rooting. (Wipe and only installed LOS and gapps)
I think I recognize it as a Rooted device due to the settings such as build.prop.
To solve this problem, I've tried Magesk or some other method( LOS Recovery -> pull build.prop and Modify), and there's still a problem.
I want to know which part of build.prop or what elements of something else are recognized as a routing device and how to solve this problem.
How should I fix something?
Previously, I tried to solve this problem with Magisk and Module, but it didn't work perfectly.
I have installed magisk and installed magiskHide Props Config 5.4.0 and universal safety net fix 1.1.1.
But Safetynet ctsProfile failed, and some apps works well, but others didn't.
There are only LOS and Gapps now.( Not Uninstall, Full Wipe and reflashing LOS17.1)
Related
Got my 5x for Christmas. I immediately unlocked and flashed TWRP, and started playing with ROMs. Once I settled on cyanogenmod, I decided to flash xposed. After flashing it, upon boot I got stuck in a loop of "Unfortunately, NFC service has stopped." errors.
Since then, I have been troubleshooting on the factory image. I formatted everything, even the sdcard, and then flashed the factory image. I then booted, then flashed and booted TWRP.
From this point, I have tried, in every order imaginable, flashing SuperSU (systemless and traditional), flashing xposed, and installing the Xposed Installer apk. No matter what I do, I get the NFC error loop. I have also tried both xposed v78, v79, and v79 dirty flashed over v78.
The only thing which has been even mildly successful has been flashing the original 6.0 factory image and then following the above steps. This results in a working xposed installation, but then upgrading to 6.0.1 and reflashing xposed causes the loop again.
From what I can tell by reading here and on /r/nexus5x, plenty of other people are having this issue, and no one seems to have the actual cause or solution. So please, if you have seen this issue, post the circumstances (be as specific as you can with versions, orders, etc), as well as your personal solutions. And if anyone has the true cause and/or solution please post that as well.
Deleted
gpvecchi said:
Deleted
Click to expand...
Click to collapse
v78 doesn't work for me either. I've seen a number of people mention that v79 causes this error, and that reverting to v78 will fix it. However, I cannot get either v78 or v79 to work.
lpreams said:
v78 doesn't work for me either. I've seen a number of people mention that v79 causes this error, and that reverting to v78 will fix it. However, I cannot get either v78 or v79 to work.
Click to expand...
Click to collapse
I just clean flashed mmb29q, tried to install v80, and got the nfc bootloop. Only way to fix was to flash the xposed uninstaller.
Tried this: checking "Enable su during boot" in the SuperSU app, then reflashing Xposed. No luck.
And nfc was not on prior to flashing xposed the first time.
Xposed v79 worked for me fine on mmb29p.
I used supersu 2.66 on mmb29p, and 2.67 on mmb29q.
Busybox installed?
Disabled NFC in settings first before flashing xposed
I got this too on MMB29Q with NFC enabled in settings. I disabled NFC in settings prior to flashing on the next try and flashing xposed v80 worked fine. After installing xposed framework, I was able to turn on NFC in settings again and all is well.
Go it to work. This was my path: Checked every box in SuperSu Settings tab that wasn't checked (e.g., enable multi-user, enable su during boot, etc.), installed the Xposed apk, flashed Xposed zip in TWRP.
Setup: MMB29Q, TWRP 3.0, SuperSU 2.67
I have the same issue trying to use layers manager. Wonder if it's related
I've installed v77 all the way up to v82, all with the same result while also trying everything mentioned before
UPDATE: I've checked literally everything now, including multi-user (didnt think that was necessary before), everything works now on v80
Sent from my Nexus 5X using XDA-Developers mobile app
I have a Oneplus 5T and i'm struggling to install a google camera fix patch for my device but in the same time keep my phone root-free because i use a bank app called "BT pay" which detects magisk even with magisk hide, even with magisk manger hidden/uninstalled, i tried many times, can't get it done with root.
I keep tried to install TWRP (even if it being replaced by stock recovery evey boot) and install my gCam fix zip from there. but it seems like those files are replaced by stock files TOO...
I also tried to prevent TWRP from being replaced by deleting "install-recovery.sh" from /system/bin but this didn't work either.
Note that i have the official rom (oxigenOS beta 15) for my phone (official kernel too) which have Treble support, (the TWRP/gCam fix are also treble versions).
I take it you were using the MagiskHide Props Conifg Module right with Magisk 17.1? That is the only way you will pass Safety Net. Does your banking app still not work like that? (With a certified fingerprint)
I have a OnePlus 5T that passes fully the SafetyNet test, but after a few hours it gives false in ctsProfile and BasicIntegrity, I am with Android 8.1 OxygenOS 5.1.5 (I already tried with 5.1.4 doing a thorough cleanup between rom exchange and also unsuccessful ), I unlocked Bootloader and installed TWRP 3.2.3 Blu spark v9.85, then i flash Root Magisk 17.1 by twrp, Installed from a clean ROM and I've already tried with 17.2 and It's the same thing at the end, I have also tried to install Magisk 16.0 from a clean rom and then upgrade to 17.1 directly via Magisk Manager but it was the same, already activated the Magisk Hide in all necessary applications, I hid the Magisk Manager, I've tried flashing Petnoire's SafetyNet Spoofer and me too changed the device fingerprint by MagiskHide Props Config but nothing solved my initial problem, every time I restart the device it passes on the SafetyNet again but after a few hours it fails again, Now i tried to flash the module Universal SafetyNet Fix v3 beta1(MG v17 fix) by Magisk Manager, but Magisk Manager stopped opening even uninstalling the application and installing other versions, I tried more than once and the installation of this module always presents this problem even flashing by TWRP, and after a few hours too SafetyNet failed, Can inform me the latest version of OxygenOS for OnePlus 5T that passes on SafetyNet without any problem? Even though OxygenOS is perfect for me, I'm willing to change rom in the last case, because the most important thing for me is to go through SafetyNet to use the applications I need.
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
anatoly1983 said:
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Click to expand...
Click to collapse
I tried to do this yesterday but the initial problem persisted, every time I restart the device it passes on the SafetyNet again but after a few hours or minutes it fails again.
yoye_cros said:
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
Click to expand...
Click to collapse
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Mega_Monster_X said:
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Click to expand...
Click to collapse
Honestly, I didn't have found any bug. I tried crDroid but I wasn't really happy, and CNP is for my use very stable without bug. I don't know if Volte or VoWifi is working because I don't use this. Also, it's very easy to install compared to other Pie Roms. I just can advise you to try it.
Try a different play services apk. This was the case with me previously.
Seagorilla2 said:
Try a different play services apk. This was the case with me previously.
Click to expand...
Click to collapse
I've tried this but to no avail
With Magisk 16.0 everything went fine, the problem is the Magisk modules I used that are not compatible, but I'll search here to see if I find the modules I want for Magisk 16.0.
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
floborg said:
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
Click to expand...
Click to collapse
I have not found a solution yet, when I fail on SafetyNet I reboot the device and pass SafetyNet a few times for a short time and sometimes lasts several hours but then fails again , I'm using Magisk 18 in OOS Open Beta 20 Android 9.0
Hi, I've bought a second Z2 on which I'm going to install Pie, TWRP, Magisk, edXposed and a lot of nice things...
On my previous Z2 I was still on Nougat, so A LOT of things are different to do....
Pie installation is done (not with some issues at first... )
TWRP is ok too.
Magisk is ok BUT I've found an issue with it trying to remove forced encryption (which I don't like a lot...).
On Nougat I removed it by SuperSU easy way...
With Magisk I've still not found the way to do the same...
I tried an "universal script" too here on XDA and it worked BUT.... as soon as Magisk reactive itself after formatting /data (Installer says Magisk is installed BUT it needs to download some "configuration files" and reboot...) phone begin to have an "early bootloop"....
To remove this I had to reflash at all... If I deleted /data and/or reflashed boot.img only, it begins to bootloop again after Magisk redownload these "configuration files"...
Anybody ( @erfanoabdi ?) has a solution for me?
My work project could be of great interest for many I think....
I tried rooting my OnePlus 7T to underclock It, but somehow the sound stopped working after I successfully root it. Is there anyone with a solution to this? ( Phone is the global version )
Did you obtain Magisk root?
Did you install any Magisk modules?
Uninstall any installed Magisk modules and see if that corrects the problem.
May be uninstall rootand see if that resolved the problem.
Restore the correct boot image and see if that corrects the problem.
Guess if that doesn't resolve the issue then try flashing the correct full stock ROM of the same version you have now? Should be able to accomplish that without a wipe.
That's just my best guess and the way in would think of trying to solve the issue.
I actually noticed that the phone went hard muted before i could even install any magisk module and also, here's the video instruction that i followed (
)