I was recently able to root my Oneplus 9 Pro, after getting all my data back on getting my device at least usable I decided to try and set back up my watch. I keep being unable to connect. I've blocked galaxy manager/wear from magisk and I've hit a brick wall any advice?
drybonesification said:
I was recently able to root my Oneplus 9 Pro, after getting all my data back on getting my device at least usable I decided to try and set back up my watch. I keep being unable to connect. I've blocked galaxy manager/wear from magisk and I've hit a brick wall any advice?
Click to expand...
Click to collapse
you most likely need to hide magisk from more (or all) google related apps and services on your device. had the same issue with me. i'm pretty google based sign in would also not be working for you in this situation. the solution for me was to re rehide magisk from everything.
That's what I originally thought and was racking my head against it. This is the only this I can't get working post root. I saw Samsung devices have a Bluetooth patch when searching but no universal patch, at least I can't find one
drybonesification said:
That's what I originally thought and was racking my head against it. This is the only this I can't get working post root. I saw Samsung devices have a Bluetooth patch when searching but no universal patch, at least I can't find one
Click to expand...
Click to collapse
is safetynet passing for you?
Seems to be so, everything other then my gear manager is working as intended
For me on a13 the galaxy wear app just crashes while trying to connect (non root)
Related
Pixel 2 XL on 9.0
Bootloader Unlocked
TWRP Recovery
Rooted via Magisk 17.1
The Uconnect app for my Jeep no longer functions because the new version for Android 9.0 checks for an unlocked bootloader or root. When trying to login to the Uconnect app, I receive a popup that states I'm using an unapproved device. When contacting the developer, they claim that it's because my device is a security threat. I've tried Magisk Hide to no avail.
Any suggestions?
Same thing here too. I have an older S6 Edge + running a rooted Android 7.0 with Magisk 17.1. Magisk Hide doesnt fix it as well.
having this issue as well with the latest uConnect app. Pixel 2XL is rooted and unlocked. I loaded the latest stock firmware 9.0 and tried the uConnect app prior to rooting and it works on my end, but still a no-go once Magisk is installed. I even tried the magisk hide and the module that can alter prop to further hide magisk and no go. I think it may be that it is looking for root and is awfully good at finding it. If anyone can get this to work, would be great! I dont get why FCA is so worried about root. One would think that since we have to go through a VERY specific sequence to get root and unlock the bootloader, that we would have quite a grip on what goes on with our phones. Anyways, if someone comes up with something......
Uconnect is detecting Magisk Manager. You have to uninstall it in order for Uconnect to work.
Well that sucks
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
TechnovationLLC said:
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
Click to expand...
Click to collapse
And you are rooted?
CyberpodS2 said:
And you are rooted?
Click to expand...
Click to collapse
I tested root and non rooted. Both seemed to function fine for me. I initially thought rooted might be the issue for me, but it ended up being the old app.
Fresh install from play store gets me this.
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
Sadly, if I install an older version it prompts to update with no way around it... If anyone knows a version that works please post here.
Wondering if a logcat would help to pinpoint the issue and assist the magisk developer with a fix.
MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
The old (black) version of the app doesn't work with 9.0
Very discouraging
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Viol8ter said:
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Click to expand...
Click to collapse
Which version of Android are you on and which app version? Thanks!
lu270bro said:
Which version of Android are you on and which app version? Thanks!
Click to expand...
Click to collapse
I am on 8.0. Though I read somewhere someone said to hide the magisc manger with random name and it worked after clearing app cache. I'm happy and thankyou.
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Machine318 said:
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Click to expand...
Click to collapse
I have never been able to get it working on this phone since the blue icon change. Sucks...
why does a car/radio company care what a joke glad i dont have a car with unconnect
OK boys and girls. I think I found a fix. might not work for all of you, but I got the App to load and let me in.
I'm running the latest Pie version, Magisk 18.1 (Riru - Core v16, Riru - Ed Xposed) and XPrivacyLua (xposed module)
in XPrivacyLua for the Uconnect App, I restricted, Get Applications. Uconnect Logs in.
5T would rooting gain access to Samsung gear and control Gear 2 (R280) & Gear 360?
I've looked all over for a tutorial.
TIA.
Yes it should. I assume your problem is these apps don't show up for you in the app store or they say they aren't compatible with your device? I had that issue with my 6T and my Gear S3. If that is indeed the case you just need to root with Magisk and use:
Magisk Hide Props Module
That module will let you change your device fingerprint to a certified one or something else if necessary. I can test this theory tonight on a rooted 5T with this module if you know what apps you are looking for. (I know what apps are needed for my Gear S3)
Both Magisk and that Module are installed in TWRP. However that module is activated and run from a terminal emulator on the phone. Personally I use this one:
Terminal Emulator
Once running that type:
su <--Hit enter, hit ok when Magisk asks, this will give terminal emulator root.
Now type:
props <--This runs the module you will now get menus choose pick certified fingerprint. It should be pretty self explanatory from here. Any questions ask.
Normal Magsik stuff I recommend hiding Google stuff from Magisk and renaming it with a random name.
Yea, Tried using Wear but doesn't find the R-280 or Gear 360. I remember a modded Gear apk a while back but it didn't work non-root.
So I should root. Is there a good tutorial link that incorporates this props list in the process? Or what rom would be good for this?
I've fairly familiar with the rooting process but it's been a bit.
Thanks for your help.
I've found on several devices now, that sometimes, my cars, headsets, watches, may not pair if the device has been on for some time. A restart and all the sudden everything connects no issue. My Gear S3 is no exception. Restart the phone and my watch and all the sudden it finds it. Your location can be off (my is always off except when using navigation), but those apps do need location permission.
Your best bet is to use FunkWizard's Guide. It doesn't have the props module stuff in it, however once TWRP is installed and you flash magisk, it's just reboot once so magisk will be installed, fully, and then go back to recovery. Then flash the module, then flash busy box. You'll be good to go. (I did realize I left out an important piece of information, that module needs BusyBox to work. You can get that here at the bottom of this post. <-- That BusyBox installer is also installed in TWRP. )
As for ROMs I use Lineage on everything. The privacy guard is the big seller for LOS for me. However that props module works in OOS, on the 5T I used it until LOS came out, back when it was first released. Also used it on my 6T until LOS was fully working with my watch. So all this stuff should work fine in OOS if you want to stay "stock".
Hmm. Got a Havoc installed and Magisk 19. "props not found" when typed in terminal after giving SU permissions. Any ideas?
Also, Anyone know where to download the older Samsung Gear apks or what apps to use for pairing the devices I mentioned?
Thanks again!
djphooka said:
Hmm. Got a Havoc installed and Magisk 19. "props not found" when typed in terminal after giving SU permissions. Any ideas?
Also, Anyone know where to download the older Samsung Gear apks or what apps to use for pairing the devices I mentioned?
Thanks again!
Click to expand...
Click to collapse
When you go into Magisk go to Modules in the menu, does the MagiskHide PropsConfig and BusyBox appear under Modules? I would guess they do not if "props" does not work.
Have you ever used APK Mirror ? It is a very handy site sometimes. It's from Android Police, so at least it's not a completely unknown source. That's not to say you shouldn't use direct sources whenever possible.
OhioYJ said:
Yes it should. I assume your problem is these apps don't show up for you in the app store or they say they aren't compatible with your device?
Click to expand...
Click to collapse
What do I do now? I have Magisk running busybox and props.
Galaxy Wear doesn't find my watch. Isn't there an older version available that might?
djphooka said:
What do I do now? I have Magisk running busybox and props.
Galaxy Wear doesn't find my watch. Isn't there an older version available that might?
Click to expand...
Click to collapse
I don't know that version would help, but you can try other versions on ApkMirror if you want. I know even in stock form connecting my watch sometimes takes some persistence. Sometimes it takes rebooting both devices to get it recognized, sometimes it just a matter of going back and forth and scanning multiple times. It basically never finds it the first time. Been through it many of times, as you can't just reconnect a the watch after a clean install, it's always completely reset the watch and reconnect as a new device.
After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?
Magisk Hide is useless for Google Pay it'll still detect your phone if its still rooted. There's a magisk module called GPay SQlite it pretty much patches the part where google tries to detect if the device is rooted. I've been using this module for a long time and hasn't failed once on me, its definitely worth your time installing this one.
Here's the link to the forum which has the download on there.
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176
xSpartacusx said:
After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?
Click to expand...
Click to collapse
I have a Gear S3 and it seems to work well ONLY if you hide Magisk Manager and then use Magisk hide Samsung Pay. This is as of a couple weeks ago when all the bootloader unlock detection was happening. I haven't tried since then. You can fail CTS/Safetynet, but still get Samsung Pay to work.
Knxed_ said:
Magisk Hide is useless for Google Pay it'll still detect your phone if its still rooted. There's a magisk module called GPay SQlite it pretty much patches the part where google tries to detect if the device is rooted. I've been using this module for a long time and hasn't failed once on me, its definitely worth your time installing this one.
Here's the link to the forum which has the download on there.
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176
Click to expand...
Click to collapse
There's like 50 links. There which do I download?
xSpartacusx said:
After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?
Click to expand...
Click to collapse
Only reason why I have yet to root my Pixel 2 XL.
Ya im not sure how to fix GPay on this device!
xSpartacusx said:
There's like 50 links. There which do I download?
Click to expand...
Click to collapse
This link here is the most up to date version of the GPay patch, this will link you the download. You gotta flash it through recovery to get it working.
https://github.com/stylemessiah/GPay-SQLite-Fix/releases/download/v2.0/GPay.SQLite.Fix.v2.0.zip
I have some issues with certain apps on an unrooted Galaxy S8+ Exynos running LineageOS 17.1 (Android 10.0) with TWRP recovery installed.
I own a Galaxy Watch Active, and I attempted to install the Galaxy Wear app from the Play Store and opened it, and got a 'Operating System on your phone has been modified in an unauthorised way' error. I also own Galaxy Buds+ which I need to pair as well (using standard bluetooth with them for now). How do I fix this issue? (bear in mind I'm not rooted)
The HSBC UK app is also messing around a bit, every time I open it and click the checkbox next to 'I accept the terms and conditions', it reboots my phone and crashes the app. Is this a general Android 10 issue with support for the HSBC app, or an anti-custom ROM move from HSBC? And if this is the case, how would I fix this too?
A more general issue is that Google Pay isn't working. It says my phone isn't supported to make payments in-store via NFC because it has been rooted (it hasn't been rooted, just installed a custom ROM). I didn't pass the SafetyNet test. It was installed with gapps by the way.
The least important issue is the Transport for London app, which says that my phone has been tampered with and is no longer supported by TfL and the app closes. Any way to trick the app into thinking I am not running a custom ROM?
Thank you so much for reading and I'd really appreciate your help! Thanks!
Did you manage to find a fix for the HSBC UK app reboot/crashing problem? I am having the same issue, but on Havoc OS running Android 11 rooted with Magisk.
Hi I rooted my tab s7+ sm-t970 but when I use magisk it give me a SafetyNetApi error it never passes can someone help me fix this. Thank you
I have the same exact issue.
Maybe could be our root?
homogamez said:
Maybe could be our root?
Click to expand...
Click to collapse
I guess its possible. It's been a long time since I've rooted something. When I open the Magisk app it says install next to magisk and the same for app. I hit install and it goes through the processes but nothing happens. There's no other area to add modules or anything. Can we go start over and do it again without breaking something? I'm lost. lol
It also happens on One Ace and N10
Hopefully next version will fix it
I can use banking app but not netflix. I get the red warning at boot up so I figure I gotta be rooted. Maybe I'll try adding TWRP
EDIT:
Went to backup using TWRP and said my device isn't rooted. I give up. lol
There's a discussion about this issue. There's an error on API key.
You can get Safety net check from play store and see the actual results
Let me look for this thread because I don’t see a way to fix
Safetynet api error
Hello looking for help as I can't figure out what's wrong. I've tried downloading the code on only wifi and only mobile data and I still get the api error. I'm not running any add blockers. Using magisk canary.
forum.xda-developers.com
I'm about to become your favorite person ever, everyone! I am currently passing SafetyNet after flashing the kdrag0n safetynet-fix to my Samsung Galaxy Tab S7+ SM-T970 and enabling the MagiskHide Props Config module in Magisk.
HOWEVER, as was the case with literally all of the stock-based ROMs for the Galaxy S8, it appears that there will still be issues with a select few apps. For example, you will get soft-banned from Snapchat every few days. Also, certain healthcare apps will still be able to detect root (likely all related to Knox, since a Pixel 5 rooted via the same methods will launch the same apps without issue).
All the best from your fellow tinkerer - Godless1
(P.S. I'm going to copy and paste this into its own thread for better visibility.)