Hello XDA!
Im sorry for this thread, but Im little out of loop, wanted to know few things. Because my phone now is 2years old and there is no more warranty, I wanna add custom rom and root. Regarding this, I got question.
After installing new rom, I still want to use my corporate e-mail. As far as Im informed, that e-mail app will not start, if it detects, that a phone is rooted. Is there a way to hide root status, so that app can start? (I think endomondo or spotify also had that ****ty "protection" against root).
There's an xposed module that can do that
The name of the module is RootCloak
You can add apps to a list and root will be completely hidden for these apps
Does xposed work on android 6.xxx ? If I remember correctly, there were problems with android 5 at begginging of it.
I have a samsung Galaxy s5 neo with android 6.0.1 and it works for me. Not all modules are supported but a lot of modules work
So not seeing much on Google when I tried which is to be expected really... I'm calling for a little bit of help so I can make a modification to a particular line in the build.prop for the Z5c.
Since I flashed LineageOS during the night, I'm mostly back up and running save for one thing: Google Pay. Because of that pesky SafetyNet API (curse you Google...), I can't use it right now because the CTS check fails in Magisk. I've tried a couple things already to no avail, since that error is related to the certification for device compatibility for Play Store and other things.
Code:
resetprop ro.build.fingerprint OnePlus/OnePlus3/OnePlus3T:8.0.0/OPR6.170623.013/12041042:user/release-keys
I took this from another thread in the Magisk forum, but I need the stock Z5c fingerprint for whichever release, preferably the latest 7.1.1 Nougat firmware if anyone has it available. If I'd known I would need this, I would of gotten it myself. Hopefully someone can help out with this since that blasted CTS check is what's preventing me from using Google Pay at the moment.
TwinShadow said:
So not seeing much on Google when I tried which is to be expected really... I'm calling for a little bit of help so I can make a modification to a particular line in the build.prop for the Z5c.
Since I flashed LineageOS during the night, I'm mostly back up and running save for one thing: Google Pay. Because of that pesky SafetyNet API (curse you Google...), I can't use it right now because the CTS check fails in Magisk. I've tried a couple things already to no avail, since that error is related to the certification for device compatibility for Play Store and other things.
Code:
resetprop ro.build.fingerprint OnePlus/OnePlus3/OnePlus3T:8.0.0/OPR6.170623.013/12041042:user/release-keys
I took this from another thread in the Magisk forum, but I need the stock Z5c fingerprint for whichever release, preferably the latest 7.1.1 Nougat firmware if anyone has it available. If I'd known I would need this, I would of gotten it myself. Hopefully someone can help out with this since that blasted CTS check is what's preventing me from using Google Pay at the moment.
Click to expand...
Click to collapse
1. You can install Universal SafetyNet fix and CTS will pass.
2. Google Pay won't work anyway because NFC issues on Lineage.
I went through like 40 of those pages and I've seen many conflicting reports about that particular module either working or not. Plus, it hasn't been updated since v14 of Magisk making it fairly old.
TwinShadow said:
I went through like 40 of those pages and I've seen many conflicting reports about that particular module either working or not. Plus, it hasn't been updated since v14 of Magisk making it fairly old.
Click to expand...
Click to collapse
It works, I'm using it ATM.
So it is apparently. Too bad NFC is utterly broke for me in LineageOS.. oh well.
Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)
Could it be related to tripping knox through rooting (i.e. then some of the Samsung apps will not work e.g. Samsung Health)? I am unable to register S.Health and Wearable (on my rooted S7 edge) will not work.
However, working fine on non-rooted S10+.
Does this help?
https://forum.xda-developers.com/galaxy-s10/how-to/guide-samsung-health-knox-0x1non-root-t4075853
Boot into TWRP and flash @ianmacd's multidisabler
I have the same issue with not rooted s10+ and gear s3
Xenenon said:
Hello,
Exactly Same problem!!!!!
Stuck badly!!!
Any solution!!!!
Ahmed
Click to expand...
Click to collapse
xBrownieCodez said:
Boot into TWRP and flash @ianmacd's multidisabler
Click to expand...
Click to collapse
I did but the problem remains the same!!!
My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1
lladwein said:
My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1
Click to expand...
Click to collapse
oops! It did not work on mine S10+
Getting frustrated day by day!
I think the era of Rooted Devices is over!!!!!
Xenenon said:
Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)
Click to expand...
Click to collapse
Anything you figure out!
Please do share with me!!!!
I flashed Beyonde Rom 6.7 it comes based on the latest April Patch.
This fixed all my problems
No Bugs yet with this rom
https://forum.xda-developers.com/ga...pment-exynos/rom-beyondrom-v6-0-t4017921/amp/
Flash with TWRP
Health works
Bcs of magisk all my banking works fine (Sparkasse germany)
I LOVE IT
GeekSiddiqi said:
Anything you figure out!
Please do share with me!!!!
Click to expand...
Click to collapse
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead
any update on this issue ?
Xenenon said:
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead
Click to expand...
Click to collapse
But do you lose the Samsung stock camera with this Rom? I have the same exact problem as you. When I was running the Evolution X custom Rom I could connect. But I wasn't happy with the camera that Rom provided. The stock camera on this phone is so amazing and one of the main reasons I bought the phone. I feel cheated when I have to give that up
nasheednashy said:
any update on this issue ?
Click to expand...
Click to collapse
I was having the exact same issue. I just activated magisk hide. And also installed the magisk module, Bluetooth library patcher. Now mine paired up first try. Not sure which helped or if it was a combination of both. But I'm paired up now.
Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected
synite said:
Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected
Click to expand...
Click to collapse
Did you found a way to connect them?
Inviato dal mio Pixel 3 utilizzando Tapatalk
Hi! Given a Samsung Galaxy Watch Active 2 (LTE) watch and a rooted Galaxy S10 (Android Q). Bluetooth pairing starts but does not end. Two Magisk modules id have been installed but I can't pair them. Is there anything you can bring together? So much for all the stupidity to read, but no answer or stupidity throughout. I can't install Viper4android on the same phone under Android 10. Magisk 21.4, but the 2.7 Viper doesn’t go up. It is installed by plugin, but not among applications. Can these be solved somehow? There was no problem under Android 9. Unfortunately, for the latest Android Q version, XEH version November 27, 2020, TWRP is not trable either. I download the right version, with Magisk, I boot into the AP with Odin, then start button, and odin closes immediately. Nothing goes on this ****ty Android Q. I am waiting for help together or separately! Thanks!
Any update on this issue?
I have problem pairing my Galaxy S21 Ultra and Galaxy Watch Active 2.
No pairing issues before rooting (stock firmware). After rooting using both stable Magisk V22 and Canary 22005, it stuck on Finalizing Pairing screen. I also noticed that the Bluetooth and Samsung accessory icons briefly shown on the notification bar (appear part of the screen) and then disappear.
I hope someone has solution to this.
Der Folks,
I upgraded my SM928F with German Telekom Branding- specification attached, from SDK24 Nougat to Havoc's custom ROM, because my diabetic App LibreFreestyle2 needed it who regarded a higher SDK version as 24 like e.g. SDK 26. This App uses NFC to read the data and Bluetooth to send back alarm notifications to the phone. As in instructions discribed I did a rooting with TWRP-3.1.1-0-zenlte and first with Nougat_Root_SuperSU_No_kernel_included.zip and later on with Magisk-v22.0.zi before installing the custom ROM Havoc 3.12-20210125-zenlte. The Installation worked in both cases fine after deleting in updater-script file the assert line. The ROOT Checker App confirmed the rooting success. But unluckily I couldn't use NFC afterwards no matter what I did. The ui symbol of NFC showed it's on but there was no reacting on any NFC Card or my diabetic sensor. With Nougat NFC worked NFC well e.g with credit cards and their App's so on . Only because of NFC using diabetic App LibreFreestyle2 from sensor manufacture Abott I need a higher SDK as 24 (Nougat). A minor issue is the freezing camera App in video mode with custom ROM. Is there any chance to fix NFC or do I have to buy another modern phone. Any advice is highly appreciated. Regards Droidbud
Droidbud said:
Der Folks,
I upgraded my SM928F with German Telekom Branding- specification attached, from SDK24 Nougat to Havoc's custom ROM, because my diabetic App LibreFreestyle2 needed it who regarded a higher SDK version as 24 like e.g. SDK 26. This App uses NFC to read the data and Bluetooth to send back alarm notifications to the phone. As in instructions discribed I did a rooting with TWRP-3.1.1-0-zenlte and first with Nougat_Root_SuperSU_No_kernel_included.zip and later on with Magisk-v22.0.zi before installing the custom ROM Havoc 3.12-20210125-zenlte. The Installation worked in both cases fine after deleting in updater-script file the assert line. The ROOT Checker App confirmed the rooting success. But unluckily I couldn't use NFC afterwards no matter what I did. The ui symbol of NFC showed it's on but there was no reacting on any NFC Card or my diabetic sensor. With Nougat NFC worked NFC well e.g with credit cards and their App's so on . Only because of NFC using diabetic App LibreFreestyle2 from sensor manufacture Abott I need a higher SDK as 24 (Nougat). A minor issue is the freezing camera App in video mode with custom ROM. Is there any chance to fix NFC or do I have to buy another modern phone. Any advice is highly appreciated. Regards Droidbud
Click to expand...
Click to collapse
Sorry to say ... I recommend to look for a new (more recent) device which fulfills all your needs right from the start.
S6 edge development seems to be (nearly) dead
Hello fellow noob lineageOS user here.
I have a Samsung Note 4 N910G and needing help in regards to fixing the fingerprint scanner as its not being detected at all/ not scanning properly but does work (semi) when trying to add a fingerprint into the phone itself after the first scan out of 8 and doesnt respond after that and its running LineageOS 18.1 and was working prior to the OS upgrade from Android v6.0.1 if anyone can provide me a possible fix it would be much appreciated