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.
Related
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.
Using the stock firmware Android 10 (QQ1A.200205.002) on a P2XL with an unlocked bootloader
Running Magisk 20.3
Running Magisk Manager 7.5.1
Hiding Multiple apps and also Hiding the Magisk Manager app
I am able to pass the SafetyNet Check
ctsProfile = true
basicIntegrity = true
I am reading multiple things over and over about getting Google Pay to work again but some people's replies appear to be more unique depending on the phone and version of the image. Anyone have any advice specifically for Android 10 on P2XL?
It's your lucky day lol I had a Magisk module sitting on my computer its a Google Pay Bypass so pretty much it doesn't check that your phone is rooted with the app and works flawlessly everytime i use it. This module will definitely work along with Android 10, it can be flashed through either recovery mode or magisk.
Btw the file is safe to use as well and save it on your pc in case this link ever disappears or gets removed.
Link to the file:
https://mega.nz/#!7OAXnaaA!5ELX85PuzDKWf7RoXq9NnQgKcPT1e2csCaa7wiNHA30
Knxed_ said:
It's your lucky day lol I had a Magisk module sitting on my computer its a Google Pay Bypass so pretty much it doesn't check that your phone is rooted with the app and works flawlessly everytime i use it. This module will definitely work along with Android 10, it can be flashed through either recovery mode or magisk.
Btw the file is safe to use as well and save it on your pc in case this link ever disappears or gets removed.
Link to the file:
https://mega.nz/#!7OAXnaaA!5ELX85PuzDKWf7RoXq9NnQgKcPT1e2csCaa7wiNHA30
Click to expand...
Click to collapse
I found the new version of this v2.0 the XDA post and used it! thank you so much!
BrokenWall said:
I found the new version of this v2.0 the XDA post and used it! thank you so much!
Click to expand...
Click to collapse
Can you post where you got the new version? Thanks
Prey521 said:
Can you post where you got the new version? Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176
So, I managed to root this beauty 1+9 Pro relatively easily.
I got Magisk installed, and hid all the Apps that needed hiding.
Even Google Pay works.
But I can't for my sanity figure out why Netflix or Android OS 11 is refusing to let me install Netflix.
Everytime I try to install the Netflix App latest APK, extracted from my old working phone ( Razer Phone 2 also rooted), it will just give me the error message " Sorry No Application Available "
Does anyone have a clue what can be done to make Netflix install in a rooted 1+9 Pro ?
Thanks.
BTW i tried several Netflix App version already.
Also I do know the APK works because I used it to install on another Tablet that will not show up Netflix on Google store.
AllGamer said:
So, I managed to root this beauty 1+9 Pro relatively easily.
I got Magisk installed, and hid all the Apps that needed hiding.
Even Google Pay works.
But I can't for my sanity figure out why Netflix or Android OS 11 is refusing to let me install Netflix.
Everytime I try to install the Netflix App latest APK, extracted from my old working phone ( Razer Phone 2 also rooted), it will just give me the error message " Sorry No Application Available "
Does anyone have a clue what can be done to make Netflix install in a rooted 1+9 Pro ?
Thanks.
BTW i tried several Netflix App version already.
Also I do know the APK works because I used it to install on another Tablet that will not show up Netflix on Google store.
Click to expand...
Click to collapse
Is Netflix currently installed as a system app? I wasn't able to uninstall that or get it working, so when I was on 11.2.2.2 I managed to fix it by installing a *newer* version of the Netflix apk that I grabbed from apkpure.com, over top of the system app. Then I had the same issue again on 11.2.4.4, and that method didn't work anymore. However, that time it let me uninstall updates to the app and then update in the play store.
I dont know how exactly, but Netflix still detects the rooted device and denies the install from google play, I think based in the unocked boot loader not sure.
I managed to install from apkmirror and is working fine now.
there is a catch though.
They are moving away from simple apk install and using apk bundles, like some sort of tarball with several apks in it, so you will need this apkm installer app for it to install the newer version. to get this installer working you need to disabled MIUI optimizations from dev options. thats all, I got mine working this passed saturday that way
EDIT: never mind with that MIUI option i thought this was a diffirent model, none the less the apkmirror is still worth a shot
I some how managed to force install it via Titanium Backup, but then it gives me another error when I try to run Netflix App.
" This device is not supported by the app "
it's running the latest version Netflix v7.102.0 build 12 35461
You have to install Magisk Canary, once you do so reboot the phone. Wipe Google play stores data and cache.. magisk hide Netflix and the Google Play Services reboot once more. That's how I got mine to work.
Install: liboemcrypto disabler
from Magisk, reboot ....enjoy
luckylui said:
You have to install Magisk Canary, once you do so reboot the phone. Wipe Google play stores data and cache.. magisk hide Netflix and the Google Play Services reboot once more. That's how I got mine to work.
Click to expand...
Click to collapse
This worked for me too w/ Disney Plus
I used Aurora Store to install it and haven't had an issue even with updating
thats_the_guy said:
I used Aurora Store to install it and haven't had an issue even with updating
Click to expand...
Click to collapse
This sort of worked for me, it game me a failed message, but at least it tried to install, unlike the other Apps that wouldn't even let me try to install.
avid_droid said:
For those of you having issues with Netflix after rooting, install this version over the Netflix you have and it should work fine. It's just a version before the latest...
Netflix 7.102.0 build 12 35461 (nodpi) (Android 5.0+) APK Download by Netflix, Inc. - APKMirror
Netflix 7.102.0 build 12 35461 (nodpi) (Android 5.0+) APK Download by Netflix, Inc. - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Click to expand...
Click to collapse
Just tried, it did not work unfortunately, it's probably related to that SafetyNet error I have in Magisk.
avid_droid said:
Make sure you have magisk canary installed to pass safetynet. Stable magisk doesn't work.
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
I use magisk hide and everything works fine
Click to expand...
Click to collapse
Yeah, I got the SafetyNet thing fixed.
However still unable to install Netflix.
still getting "App Not Installed" error, when I try to install the APK.
I tried installing the "liboemcrypto disabler " as suggested a few messages back, and also doesn't seem to make any difference.
AllGamer said:
Yeah, I got the SafetyNet thing fixed.
However still unable to install Netflix.
still getting "App Not Installed" error, when I try to install the APK.
I tried installing the "liboemcrypto disabler " as suggested a few messages back, and also doesn't seem to make any difference.
Click to expand...
Click to collapse
Have you tried to look for it on the play store after fixing safetynet?
craznazn said:
Have you tried to look for it on the play store after fixing safetynet?
Click to expand...
Click to collapse
I just did after reading this.
It's not showing up in Google Play store.
It's just so weird, everything else works, Google Pay (wallet), Pokemon Go, Banking Apps, everything else that usually will complain and refuse to run when Root is detected, are all working fine, except for Netflix.
avid_droid said:
Try clearing cache and data then try reinstalling app over current Netflix. That's what I do and it works everytime
Click to expand...
Click to collapse
I'm thinking maybe I'll need to un-root my phone, update Netflix, see if it runs without root, if it works, then try to root again and figure how to go from there.
... what a hassle
AllGamer said:
I'm thinking maybe I'll need to un-root my phone, update Netflix, see if it runs without root, if it works, then try to root again and figure how to go from there.
... what a hassle
Click to expand...
Click to collapse
I did this and had the same problem while unrooted, so it turned out to be a waste of time. It seems to have an issue with the unlocked bootloader, not just root. At least with root you can hide unlocked status, which is a step in the right direction. Hide root from Netflix, and also hide magisk app itself in magisk settings.
If you're trying to install Netflix over the system app, make sure to first uninstall updates to the system app so it's the oldest possible version. Then make sure whatever version you're installing on top (whether from play store or APK download) is newer than your installed version. Older versions will not install over newer ones.
terlynn4 said:
I did this and had the same problem while unrooted, so it turned out to be a waste of time. It seems to have an issue with the unlocked bootloader, not just root. At least with root you can hide unlocked status, which is a step in the right direction. Hide root from Netflix, and also hide magisk app itself in magisk settings.
If you're trying to install Netflix over the system app, make sure to first uninstall updates to the system app so it's the oldest possible version. Then make sure whatever version you're installing on top (whether from play store or APK download) is newer than your installed version. Older versions will not install over newer ones.
Click to expand...
Click to collapse
There are sai versions floating around here that work search xda also make sure you magisk hide Netflix before you open it initially. Or hide them clear cache and data on netflix
terlynn4 said:
I did this and had the same problem while unrooted, so it turned out to be a waste of time. It seems to have an issue with the unlocked bootloader, not just root. At least with root you can hide unlocked status, which is a step in the right direction. Hide root from Netflix, and also hide magisk app itself in magisk settings.
If you're trying to install Netflix over the system app, make sure to first uninstall updates to the system app so it's the oldest possible version. Then make sure whatever version you're installing on top (whether from play store or APK download) is newer than your installed version. Older versions will not install over newer ones.
Click to expand...
Click to collapse
Update.
Minor good news.
I wiped the phone from recovery mode.
So, the phone is kind of factory mode, I completed the "new" phone setup thing, and the first thing I went to try was Netflix and it worked.
So... it appears to be something to do with Root and/or Magisk being detected.
Update 2
More good news, I rooted it again, installed Magisk and Netflix is still working.
Not sure why it wasn't working before, also not quite sure what was the actual fix.
I don't really consider a full system wipe a "fix" but well that did it for me.
avid_droid said:
A wipe isn't necessary but glad you got it working
Click to expand...
Click to collapse
So, I just imported Apps and Data from the old phone again via Google "setup my device" transfer, and now Netflix got disabled again.
I'll try again and skip Google transfer to find out if that helps.
I can always use One+ Switch App to see if that is better.
avid_droid said:
OnePlus switch will still result in the same issue. Clear data and cache,install the app link I provided and make sure magiskhide is set to on.
Click to expand...
Click to collapse
Seems like it worked,
I installed a full APK from my old phone and now it's able to run.
However it still doesn't show up in Google Play store when I search for Netflix.
Hi
I was on Android 12 and signed in to the beta program 10 days ago.
I've noticed that APKs that were fine on Android 12 are not working anymore on Android 13 Beta.
APKs are crashing at opening.
I thought that may have been an issue related to the beta version of Android but couple of days ago Android 13 stable rolled out (I've signed out from the beta) but those apps are still not working.
I've found older APKs for a couple of apps and one works and one not.
How can I solve this without a factory reset?
Thank you in advance
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
skymera said:
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
Click to expand...
Click to collapse
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Lughnasadh said:
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Click to expand...
Click to collapse
Wasn't aware of this, thanks!
I don't have any issues with manually installed apks...
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Waiting till the weekend to update, but what APKs are giving the error?
skymera said:
Wasn't aware of this, thanks!
Click to expand...
Click to collapse
Can't find this
Jeff_N said:
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Click to expand...
Click to collapse
Do those apps need Accessibility and/or Notification Access permissions? If not, then I don't think the 3 dot menu needs to be there as it is only for those specific permissions (or whatever other permissions Google might add to the list in the future).
For example, I have Adaway installed but it doesn't have the 3 dot menu because it doesn't need either of those permissions. The same for App Manager.
I am really confused with this new "session-based install" security.
What are "session-based install" and "non-session-based install"
Play store app install --------- surly "session-based install" 100%.
3rd-party store install --------- is said also to be "session-based install".
Firefox download an apk --------- is said to be "non-session-based install",
But how the firefox different from a 3rd-party store????? a system white list something?
safetynet, selinux, forcing many settings, anti-rollback, non-store app restrictions.........
I enjoyed so much that google throws sht tons of troubles to billions of advanced users, to fight an enemy that may not even exist.
(how many people have their phone bootloader secretly unlocked remotely by a hacker and installed root malware, unknowingly?)
Gives a warning is good eg. bootloader locked warning is great IMO. But force the hands and keep finding ways to screw the advanced users as hard as they can, to get the "everything is under my control" status is the wrong path.
I read the news that malware devs have already found a way to bypass this restriction.
In the end, like many others, It achieved nothing, except giving trouble to advanced users and devs.
A global bypass must be also on the way, especially from China. Millions like 90% of APPs are not store-based in China since the google ban, and people are used to download apk from every companies' websites as we do on Windows PC.
somethingsomethingroot said:
Waiting till the weekend to update, but what APKs are giving the error?
Click to expand...
Click to collapse
3 APKs from the company I'm working for (not on PlayStore) 2 sideloaded apps, and a LADB signed sideloaded APK
For example you cut and CC cleaner keeps crashing all the time.
Same here. Almost every app not from Play Store keeps closing right on tap to start them.
Tried to sideload them per USB with full rights. Same.
My company apps that didn't come from the play store are opening without a problem
Thats Vers Strange, indeed.
Every sideloaded App, modded or Not does Not work
Thought it was me...this is bs!
What's the next step...start posting logs I assume?
It's not EVERY sideload for me but about 1 in 3 I'd say.
btw...I got an 'install failed' trying to install/flash the viper4android mod not realizing how old it was...now I'm seeing lotsa audio/sound related crap in logcat reader. If I AM 'currupt' somehow, will just a rom re-flash fix a magisk issue or do I need a full wipe?
Tia for any guidance offered!
Zaxx32 said:
Thought it was me...this is bs!
Click to expand...
Click to collapse
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
salamala893 said:
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
Click to expand...
Click to collapse
12 won't work right on the 13 bootloader, and you can't downgrade the bootloader.
When I initially tested flashing only the 13 bootloader on my Pixel 6 Pro, while still running Android 12, it booted fine, I unlocked the phone, and all looked normal. But I didn't launch apps, especially Chrome, YouTube, and plenty of other things. If I had, I would have noticed problems that others have had since then. It was since found that certain/many kinds of apps will not work right running on Android 12 when you have the 13 bootloader installed.
I know this above is not what this thread is discussing, but since you mentioned it, I just wanted to point out that if you're on any Pixel 6/Pro/a with Android 13's bootloader flashed, you won't be able to use stock Android 12 on it. You'll be able to flash everything but the bootloader, boot it up, and unlock it, but before long you would discover problems that you wouldn't be able to work around and would effectively make your phone unuseable for many things that we take for granted.
By the way, hopefully you have the 13 bootloader flashed to both slots. Having the 13 bootloader on only one slot is a little dangerous.
Code:
adb reboot bootloader
fastboot --slot all flash bootloader bootloader.img
Guys, but are you talking of sideloaded apps, or apps installed as apk?
gpvecchi said:
Guys, but are you talking of sideloaded apps, or apps installed as apk?
Click to expand...
Click to collapse
Apks
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)