Related
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire TV so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. It is set to a 'root user' but the user is ONLY root in three tiers explained here. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
Code:
"alexa_enabled"
"assistant"
"voice_interaction_service"
"voice_recognition_service"
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Code:
adb shell settings put secure assistant com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
adb shell settings put secure alexa_enabled 0
If the last command doesn't work, go to the Settings Database Editor app and tap on secure tab. Locate the alexa_enabled setting and tap it. change the 1 to a 0 and save the setting.
6. Open the Google App and go to settings > voice > Configure 'Ok Google" or your Assistant.
The more who confirm this, the better
DragonFire1024 said:
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire TV so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. It is set to a 'root user' but the user is ONLY root in three tiers explained here. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
Code:
"alexa_enabled"
"assistant"
"voice_interaction_service"
"voice_recognition_service"
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Code:
adb shell settings put secure assistant com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
adb shell settings put secure alexa_enabled 0
If the last command doesn't work, go to the Settings Database Editor app and tap on secure tab. Locate the alexa_enabled setting and tap it. change the 1 to a 0 and save the setting.
6. Open the Google App and go to settings > voice > Configure 'Ok Google" or your Assistant.
The more who confirm this, the better
Click to expand...
Click to collapse
Tried it on my 2nd gen fire stick (not rooted), nothing, but I think it'd work if I could disable alexa. The alexa_enabled flag doesn't do anything. Maybe we could work together, seeing as you don't have a fire stick?
Nootboot64 said:
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire TV so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. It is set to a 'root user' but the user is ONLY root in three tiers explained here. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Tried it on my 2nd gen fire stick (not rooted), nothing, but I think it'd work if I could disable alexa. The alexa_enabled flag doesn't do anything. Maybe we could work together, seeing as you don't have a fire stick?
Click to expand...
Click to collapse
What happens when you try to set up the assistant and what version of the Google app are you using
DragonFire1024 said:
What happens when you try to set up the assistant and what version of the Google app are you using
Click to expand...
Click to collapse
I already had my voice set up previously and I'm using the latest. I'll have to find out which one that is when I get home.
EDIT: It is version 10.20.2.21.arm
Nootboot64 said:
I already had my voice set up previously and I'm using the latest. I'll have to find out which one that is when I get home.
EDIT: It is version 10.20.2.21.arm
Click to expand...
Click to collapse
On the HD I have to start with the Google app 8.33.5 beta. Then setup your assistant doing the ADB steps reboot and then you can let it auto update to the latest version that's how I've been doing it.
DragonFire1024 said:
On the HD I have to start with the Google app 8.33.5 beta. Then setup your assistant doing the ADB steps reboot and then you can let it auto update to the latest version that's how I've been doing it.
Click to expand...
Click to collapse
Thank you, I'll try that
Nootboot64 said:
Thank you, I'll try that
Click to expand...
Click to collapse
Also note that I have made the Google app system application because we have root but I don't know if that matters. not sure if you guys are rooted or how that happens with the stick.
Nootboot64 said:
Thank you, I'll try that
Click to expand...
Click to collapse
One more thing it's important to remember that when you have your assistant setup from ADB also set up the voice commands and what not. That's important because the idea is to have your voice commands already set up when the Google app updates. As long as that happens you won't have to go back and setup assistant with your voice all over again. As long as it remembers your settings from the beta version of the old app the new app version will also take on those settings, voice included. I think that was the main problem before is it wasn't doing that and something else internally with the Google app wasn't allowing you to save your voice commands to the device again. would you still can't do so don't try and go and set up the voice again because it won't work you'll have to downgrade back to the 8.33 version and start all over.
you can also uninstall delete or do whatever you want with the two Amazon applications that have to do with the speech user interface and speech interaction manager they have nothing to do with anything that goes on with the Google app or the assistant or anything Android for that matter.
Where can I get the Google app 8.33.5 beta
thx
yenmax said:
Where can I get the Google app 8.33.5 beta
thx
Click to expand...
Click to collapse
Maybe you can just use google search?
https://www.google.com/search?q=Google+app+8.33.5+beta
https://www.apkmirror.com/apk/google-inc/google-search/google-search-8-33-5-release/
Do we need to have Google Play Services on the Firestick for this to work? Or will installing the Google app be enough?
gogorman said:
Do we need to have Google Play Services on the Firestick for this to work? Or will installing the Google app be enough?
Click to expand...
Click to collapse
I'm pretty sure assistant will only work with play services but I could be wrong. I do know there's somewhat of an assistant ability built into Google go. But it is not nearly as sophisticated.
Sent from my Google Nexus 10 using XDA Labs
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
Code:
"alexa_enabled"
"assistant"
"voice_interaction_service"
"voice_recognition_service"
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Code:
adb shell settings put secure assistant com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
adb shell settings put secure alexa_enabled 0
If the last command doesn't work, go to the Settings Database Editor app and tap on secure tab. Locate the alexa_enabled setting and tap it. change the 1 to a 0 and save the setting.
6. Open the Google App and go to settings > voice > Configure 'Ok Google" or your Assistant.
The more who confirm this, the better
How can I disable double tap of home button who activates the "voice input", who is no longer avaible as Amazon decided... THANKS THEM
DragonFire1024 said:
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
The more who confirm this, the better
Click to expand...
Click to collapse
Hi DragonFire1024,
Thanks for this very interesting post I was just wondering by to see if anyone had unlocked the bootloader :laugh:
Problem with the fire phone is probably 98% of users here use one of @ggow custom ROM's LineageOS 11 or the AOSP based SlimKat and Nexus Rom. Those running the Stock ROM are likely not interested in development hence why no reply's.
To be honest I never even gave the Fire OS a chance before rooting and switching to the Nexus ROM. I am not sure our fire OS has Alexa :silly: or at least as we know it today yes you heard correct a Premium Amazon Device and they see fit not push it out to Amazon device owners. In fact they just went one better and removed the voice service altogether. https://forum.xda-developers.com/fire-phone/general/amazon-voice-services-fire-phone-t3681235 Pretty amazoning :laugh
I was kinda hoping it was to make way for Alexa and a Massive OS Update but I guess thats just wishful thinking. :laugh:
Hey Guys,
I am running the Mate 20 x EVR-AL00 and I was able to get the hivoice uninstalled and the google assistant to stay the persistent assistant app.
Still struggling on getting "Okay Google" to work without the assistant app already loaded. Currently, holding the home button will launch the app.
Here are steps based on the methods of @RedCriwx for removing the default launcher:
https://forum.xda-developers.com/mate-20-x/how-to/how-to-install-nova-mate-20x-reverting-t3863446
1) Download and extract ADB (I use platform tools:*http://mirrors.zzu.edu.cn/android/re....1-windows.zip)
2) Go to Settings > System > About Phone and tap on "build number" about 8 times. You should see a message saing: "You are a developer now"
3) Back to the previous menu and you should see now a new item called "Developer options", go there, find and enable "USB debugging" (you may have to use a Huawei ID).
4) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
5) Open a command line and go to the directory you extracted "Platform Tools" to.
6) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
7) Run "adb shell"
8) Run "pm uninstall -k --user 0 com.huawei.vassistant". It should show "success"
At this point you should be able to set your default assist app and it shouldnt change back to hivoice.
One thing I am still having a problem with is enabling "Access with voice match"
https://imgur.com/jhUwTjH
Is anybody else able to enable this option that is running on EVR-AL00 ?
y0zer187 said:
Hey Guys,
I am running the Mate 20 x EVR-AL00 and I was able to get the hivoice uninstalled and the google assistant to stay the persistent assistant app.
Still struggling on getting "Okay Google" to work without the assistant app already loaded. Currently, holding the home button will launch the app.
Here are steps based on the methods of @RedCriwx for removing the default launcher:
https://forum.xda-developers.com/mate-20-x/how-to/how-to-install-nova-mate-20x-reverting-t3863446
1) Download and extract ADB (I use platform tools:*http://mirrors.zzu.edu.cn/android/re....1-windows.zip)
2) Go to Settings > System > About Phone and tap on "build number" about 8 times. You should see a message saing: "You are a developer now"
3) Back to the previous menu and you should see now a new item called "Developer options", go there, find and enable "USB debugging" (you may have to use a Huawei ID).
4) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
5) Open a command line and go to the directory you extracted "Platform Tools" to.
6) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
7) Run "adb shell"
8) Run "pm uninstall -k --user 0 com.huawei.vassistant". It should show "success"
At this point you should be able to set your default assist app and it shouldnt change back to hivoice.
One thing I am still having a problem with is enabling "Access with voice match"
https://imgur.com/jhUwTjH
Is anybody else able to enable this option that is running on EVR-AL00 ?
Click to expand...
Click to collapse
Thanks. Got rid of hivoice. Still have the exact same problems as you. Please keep us posted on any kind of fix. Do like the fact I can touch the home button now for google
y0zer187 said:
Hey Guys,
I am running the Mate 20 x EVR-AL00 and I was able to get the hivoice uninstalled and the google assistant to stay the persistent assistant app.
Still struggling on getting "Okay Google" to work without the assistant app already loaded. Currently, holding the home button will launch the app.
Here are steps based on the methods of @RedCriwx for removing the default launcher:
https://forum.xda-developers.com/mate-20-x/how-to/how-to-install-nova-mate-20x-reverting-t3863446
1) Download and extract ADB (I use platform tools:*http://mirrors.zzu.edu.cn/android/re....1-windows.zip)
2) Go to Settings > System > About Phone and tap on "build number" about 8 times. You should see a message saing: "You are a developer now"
3) Back to the previous menu and you should see now a new item called "Developer options", go there, find and enable "USB debugging" (you may have to use a Huawei ID).
4) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
5) Open a command line and go to the directory you extracted "Platform Tools" to.
6) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
7) Run "adb shell"
8) Run "pm uninstall -k --user 0 com.huawei.vassistant". It should show "success"
At this point you should be able to set your default assist app and it shouldnt change back to hivoice.
One thing I am still having a problem with is enabling "Access with voice match"
https://imgur.com/jhUwTjH
Is anybody else able to enable this option that is running on EVR-AL00 ?
Click to expand...
Click to collapse
Looks like a lot work to get the same functions as the Google search widget. I just turned Hivoice off and put a widget on the screen but if this worked with only voice like saying "Hey Google" I'd be all over this.
y0zer187 said:
Hey Guys,
I am running the Mate 20 x EVR-AL00 and I was able to get the hivoice uninstalled and the google assistant to stay the persistent assistant app.
Still struggling on getting "Okay Google" to work without the assistant app already loaded. Currently, holding the home button will launch the app.
Here are steps based on the methods of @RedCriwx for removing the default launcher:
https://forum.xda-developers.com/mate-20-x/how-to/how-to-install-nova-mate-20x-reverting-t3863446
1) Download and extract ADB (I use platform tools:*http://mirrors.zzu.edu.cn/android/re....1-windows.zip)
2) Go to Settings > System > About Phone and tap on "build number" about 8 times. You should see a message saing: "You are a developer now"
3) Back to the previous menu and you should see now a new item called "Developer options", go there, find and enable "USB debugging" (you may have to use a Huawei ID).
4) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
5) Open a command line and go to the directory you extracted "Platform Tools" to.
6) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
7) Run "adb shell"
8) Run "pm uninstall -k --user 0 com.huawei.vassistant". It should show "success"
At this point you should be able to set your default assist app and it shouldnt change back to hivoice.
One thing I am still having a problem with is enabling "Access with voice match"
https://imgur.com/jhUwTjH
Is anybody else able to enable this option that is running on EVR-AL00 ?
Click to expand...
Click to collapse
Excellent step by step instructions. Thank you.
To remove Hi Voice this command was critical:
8) Run "pm uninstall -k --user 0 com.huawei.vassistant". It should show "success"
Can you point me to a reference with a list of commands (or syntax) to remove other features/programs that I'd like to uninstall?
Many thanks!
onepiece said:
Excellent step by step instructions. Thank you.
To remove Hi Voice this command was critical:
8) Run "pm uninstall -k --user 0 com.huawei.vassistant". It should show "success"
Can you point me to a reference with a list of commands (or syntax) to remove other features/programs that I'd like to uninstall?
Many thanks!
Click to expand...
Click to collapse
Thank you very much, I wanted to play around more tonight but didnt get a chance.
So what you can do to get a list of commands is once your in the adb shell just run the command "pm -h"
It will display the output of all the commands that can be used.
1) enable "USB debugging"
2) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
3) Open a command line and go to the directory you extracted "Platform Tools" to.
4) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
5) Run "adb shell"
6 Run "pm -h"
Let me know if you find anything in regards to allowing the persistent "Okay Google" Command
onepiece said:
Excellent step by step instructions. Thank you.
To remove Hi Voice this command was critical:
8) Run "pm uninstall -k --user 0 com.huawei.vassistant". It should show "success"
Can you point me to a reference with a list of commands (or syntax) to remove other features/programs that I'd like to uninstall?
Many thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/note-10/how-to/guide-to-remove-apps-root-t3828324
Use it ta your own risk. You can cause too much damage though. Factory reset heals everything.
Ok Google will not he able to work on that AL00. As it's not installed as a system app.
The reason it works on the L29 is the Google app is installed to the system. Otherwise functionality will not be present.
Removed hiboard, now I can use google feed on home screen setting.
Removed hiVoice restarted a few times, still see google as a default assistant.
access to voice match doesn't work, it grey out, can't click on it.
the google app, it asks f
SmartPhonesFan said:
Exactly I wanted point this out but it kind of works..
I uninstalled hivoice on mine Note10
I set it up as default
And I can say ok Google and whatever I want
But once app is closed and reopened it says Google assistant isn't your default app but in reality is so Every time I have to manually enable it and then it works..
Should be same in mate 20x
Click to expand...
Click to collapse
hello, same problem for me, everytime i kill the google app and start it again, it asks for a default app for voice assistant, i already deleted hivoice via adb on my huawei mate 20X.
SmartPhonesFan said:
leave google assistant open in background all the time and it should work always
Click to expand...
Click to collapse
cannot keep it opened, also if i lock it in recent apps, it closes after a while..
SmartPhonesFan said:
u need to change it in settings apps run in background .. ignore battery optimiz .. etc.. I just tested it unlocked phone and works still
Click to expand...
Click to collapse
hey! great, it works! Thank you so much.. so i only got one problem left on my mate 20
SmartPhonesFan said:
which one?
Click to expand...
Click to collapse
Youtube Vanced always loses my google user account, everytime i close the app
---------- Post added at 06:25 PM ---------- Previous post was at 06:18 PM ----------
SmartPhonesFan said:
which one?
Click to expand...
Click to collapse
the launcher problem is also still there, but i am already used to the emui launcher, so it´s okay for me
SmartPhonesFan said:
hmm how come? mine youtube doesn't .. but make sure u need to go to play store and disable automatic updates .. and leave notifications that there are new updates tap on update all and quickly tap on cross youtube that won't be updated .. youtube must not be updated by playstore ..
uninstall youtube completely and reinstall vanced again .. make sure it won't be updated...
Click to expand...
Click to collapse
tried everything, not working, but it´s not dramatical, everytime i open youtube vanced, it is not connected to google, when i fill in my email adress, it says user already connected, and than its fine, connected and works, weird thing. in the regular youtube app everything works like it should, but the most important problem is fixed, thank you again
ersguterjunge1911X said:
tried everything, not working, but it´s not dramatical, everytime i open youtube vanced, it is not connected to google, when i fill in my email adress, it says user already connected, and than its fine, connected and works, weird thing. in the regular youtube app everything works like it should, but the most important problem is fixed, thank you again
Click to expand...
Click to collapse
Same issue for me. Every time youtube vanced gets cleared from memory or I restart the phone, the app is not logged in. I have click on sign-in and then just back out of the login process...then it's fine. The regular youtube app does not have this issues.
SmartPhonesFan said:
guys but I don't know you supposed to NOT have two youtubes .. When I installed vanced it just replaced normal youtube and icon changed ..
Your problem is dat youtube.com or google detecting two youtube apps .. So unsign from normal YT and disable it .. And login to vanced only ...
Click to expand...
Click to collapse
I don't have 2 YouTube apps installed. After working some of the quirks out, I did a factory reset and set it up again. Now I only have vanced installed and I still have the issue on the L00 version. If there's a fix, please share. It's not a huge deal but just gets annoying I guess.
does google backup has a problem? mine shows waiting for backup except contacts and photo,video.
hattrickho said:
does google backup has a problem? mine shows waiting for backup except contacts and photo,video.
Click to expand...
Click to collapse
I think there was a thread in this forum about the backup sync issue. My contacts and photos work fine but nothing else. I use a SMS Backup and Restore for texts and call history.
htchd2mtk said:
I think there was a thread in this forum about the backup sync issue. My contacts and photos work fine but nothing else. I use a SMS Backup and Restore for texts and call history.
Click to expand...
Click to collapse
yea! same like mine. App data,call history, device settings and sms text messages are all on "waiting to backup" status.
And the "Back up now" greyed out , can't click on it.
I don't know what's going on, well but at least I can use Huawei backup everythings to pc.
hattrickho said:
yea! same like mine. App data,call history, device settings and sms text messages are all on "waiting to backup" status.
And the "Back up now" greyed out , can't click on it.
I don't know what's going on, well but at least I can use Huawei backup everythings to pc.
Click to expand...
Click to collapse
It was the same on my OnePlus 6. I think the backup feature is just broken.
SmartPhonesFan said:
No I don't have this problem.. sorry .. I installed vanced (root) and it auto replaced orig YT
Click to expand...
Click to collapse
hey, thank you again.. it has to do with the microG App, which has to run in the background to stay connected with google. Thanks for your help
enable magisk hide on those apps in screenshot. Use xmlpak magisk mod if you don't see Samsung in play store after activating it on your watch
Please edit title to state that is requires a rooted phone, a simple "[ROOT]" would be fine. Don't want to have a misleading title.
I'm running a rooted note 9 and latest magisk, yet I don't see any of those apps in magisk hide? Not sure why
I have a Samsung galaxy watch 42mm and Nokia 7 Plus, i live in India, since i got the watch there is no option of Samsung pay in Galaxy wear app. I manually installed latest Samsung pay plugin ( https://www.apkmirror.com/apk/samsu...n/samsung-pay-watch-plug-in-1-7-5906-release/ ) , and changed the region to Australia and after that when i paired the watch again with galaxy wear app Samsung pay is showing in it, and i then followed the instructions in the app to set it up.
I followed the below instructions samsung pay works on my nokia 7 plus.
You do NOT need root.
But this is how you do it.
1. So first, download SDBstarterKidv1 from the following link please:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
WARNING: This will reset your watch, so make sure you back it up so you can restore it later.
2. Next make sure your watch is set up as follows:
- Debugging Mode turned ON
- Connect watch to WiFi and get its IP address (To find the IP address on Galaxy Watch: Settings > Connections > Wifi > Wifi Networks > [your network] > Scroll down to IP address)
3. Next, from SDBstarterKidv1 double click on 'install.bat' (it will not install, it just flashes a window, but this step is required)
4. From the subfolder data\tools double click on 'sdb.exe' (it will not install, it just flashes a window, but this step is required too)
After noting IP address of the Galaxy Watch, Launch ‘Ansicon.exe’ from sdb_2.2.60_windows-64\data\tools (this thing will open a command prompt window, and all the action is done here)
5. Type: sdb connect [IP of Galaxy Watch]
6. Look at Galaxy Watch, it will prompt you to accept a message
7. If you try the sdb connect [IP address] again, it will say "already connected". This means we are connected and good to continue.
8. Type: sdb shell and Enter
9. Copy Paste: launch_app csc-manager.csc-pre-configuration and Enter
So this lets you change the region of the watch. Now for me I changed mine to Austrailia. The code for Austrailia is XSA
Once the watch is reset, pair it back up with your phone.
10. Once pared with your phone you will need to:
- Turn on developer mode again
- Turn on debugging mode
- Turn off the watch and turn it back on again.
- You may need to wait a few minutes.
11. Once you have done this, you can open the Samsung Galaxy Wearable app and go to settings. When you scroll down you should see samsung pay.
If you dont see pay, hold down the back button (Top right button) on the watch till samsung pay opens up and follow the instuctions to set it up. But initially the Samsung pay app is not recognising my compatible Indian Debit and Credit card and not allowing me to add, i thought this might be that i had changed the region to Australia, but i tried again after an hour and then to my surprise i am able to add all my 4 cards to Samsung pay app , and it is working also, i tried a payment at NFC enabled terminal and payment works flawlessly
Enjoy your new watch with Samsung Pay enabled.
Delete
Dbj.Dhaval said:
Delete
Click to expand...
Click to collapse
Sorry, My mistake, instead of APK mirror link, i entered xda link, now edited the original post, please check.
ca_guri01 said:
Sorry, My mistake, instead of APK mirror link, i entered xda link, now edited the original post, please check.
Click to expand...
Click to collapse
I followed your steps, but chose SEK as region (thinking it was Sweden). However, now it's impossible to connect to the watch again with sdb. When trying to connect, I sometimes get responses like ¥¸ºeÇþx or other strange characters
EDIT: After the reset when I changed the region, the watch was also showing cyrillic characters for the instructions. However, as soon as I connected my phone, the watch changed to english.
EDIT2: I installed Tizen Studio to get the most recent version of SDB. And after a reboot of the watch, it looks like I'm getting closer:
Code:
PS C:\tizen-studio\tools> .\sdb connect 192.168.0.199
connecting to 192.168.0.199:26101 ...
device unauthorized. Please approve on your device.
PS C:\tizen-studio\tools> .\sdb connect 192.168.0.199
192.168.0.199:26101 is already connected
PS C:\tizen-studio\tools> ./sdb shell
device unauthorized. Please check the confirmation dialog on your device.
device unauthorized. Please check the confirmation dialog on your device.
device unauthorized. Please check the confirmation dialog on your device.
EDIT 3:
I followed instructions here: https://stackoverflow.com/questions/54120334/sdb-device-unauthorized
To delete the key, and after restarting the watch again and running sdb kill-server, I was able to connect again and get the request to confirm my computer.
Damn Samsung, why is this **** so buggy?
Inrego said:
I followed your steps, but chose SEK as region (thinking it was Sweden). However, now it's impossible to connect to the watch again with sdb. When trying to connect, I sometimes get responses like ¥¸ºeÇþx or other strange characters
EDIT: After the reset when I changed the region, the watch was also showing cyrillic characters for the instructions. However, as soon as I connected my phone, the watch changed to english.
EDIT2: I installed Tizen Studio to get the most recent version of SDB. And after a reboot of the watch, it looks like I'm getting closer:
Code:
PS C:\tizen-studio\tools> .\sdb connect 192.168.0.199
connecting to 192.168.0.199:26101 ...
device unauthorized. Please approve on your device.
PS C:\tizen-studio\tools> .\sdb connect 192.168.0.199
192.168.0.199:26101 is already connected
PS C:\tizen-studio\tools> ./sdb shell
device unauthorized. Please check the confirmation dialog on your device.
device unauthorized. Please check the confirmation dialog on your device.
device unauthorized. Please check the confirmation dialog on your device.
EDIT 3:
I followed instructions here: https://stackoverflow.com/questions/54120334/sdb-device-unauthorized
To delete the key, and after restarting the watch again and running sdb kill-server, I was able to connect again and get the request to confirm my computer.
Damn Samsung, why is this **** so buggy?
Click to expand...
Click to collapse
Yeah deleteing the key is the work around, glad you get the answer [emoji3]
Sent from my Nokia 7 plus using XDA-Developers Legacy app
ca_guri01 said:
Yeah deleteing the key is the work around, glad you get the answer [emoji3]
Sent from my Nokia 7 plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thing is, the .tizen folder didn't exist when just installing the tools from this post. Only after I installed tizen studio
Sent from my VOG-L29 using Tapatalk
Inrego said:
Thing is, the .tizen folder didn't exist when just installing the tools from this post. Only after I installed tizen studio
Sent from my VOG-L29 using Tapatalk
Click to expand...
Click to collapse
Strange, i don't have tizen studio, never installed, and still i have .tizen folder, make sure hidden items are shown in windows option
Sent from my Nokia 7 plus using XDA-Developers Legacy app
ca_guri01 said:
Strange, i don't have tizen studio, never installed, and still i have .tizen folder, make sure hidden items are shown in windows option
Sent from my Nokia 7 plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
It is enabled. And it did show after installing Tizen Studio.
EDIT: I even ran the tools on another pc, and here's the user folder:
Inrego said:
It is enabled. And it did show after installing Tizen Studio.
EDIT: I even ran the tools on another pc, and here's the user folder:
Click to expand...
Click to collapse
Ok, then may be i was lucky [emoji23] [emoji23]
Sent from my Nokia 7 plus using XDA-Developers Legacy app
ca_guri01 said:
I have a Samsung galaxy watch 42mm and Nokia 7 Plus, i live in India, since i got the watch there is no option of Samsung pay in Galaxy wear app. I manually installed latest Samsung pay plugin ( https://www.apkmirror.com/apk/samsu...n/samsung-pay-watch-plug-in-1-7-5906-release/ ) , and changed the region to Australia and after that when i paired the watch again with galaxy wear app Samsung pay is showing in it, and i then followed the instructions in the app to set it up.
I followed the below instructions samsung pay works on my nokia 7 plus.
You do NOT need root.
But this is how you do it.
1. So first, download SDBstarterKidv1 from the following link please:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
WARNING: This will reset your watch, so make sure you back it up so you can restore it later.
2. Next make sure your watch is set up as follows:
- Debugging Mode turned ON
- Connect watch to WiFi and get its IP address (To find the IP address on Galaxy Watch: Settings > Connections > Wifi > Wifi Networks > [your network] > Scroll down to IP address)
3. Next, from SDBstarterKidv1 double click on 'install.bat' (it will not install, it just flashes a window, but this step is required)
4. From the subfolder data\tools double click on 'sdb.exe' (it will not install, it just flashes a window, but this step is required too)
After noting IP address of the Galaxy Watch, Launch ‘Ansicon.exe’ from sdb_2.2.60_windows-64\data\tools (this thing will open a command prompt window, and all the action is done here)
5. Type: sdb connect [IP of Galaxy Watch]
6. Look at Galaxy Watch, it will prompt you to accept a message
7. If you try the sdb connect [IP address] again, it will say "already connected". This means we are connected and good to continue.
8. Type: sdb shell and Enter
9. Copy Paste: launch_app csc-manager.csc-pre-configuration and Enter
So this lets you change the region of the watch. Now for me I changed mine to Austrailia. The code for Austrailia is XSA
Once the watch is reset, pair it back up with your phone.
10. Once pared with your phone you will need to:
- Turn on developer mode again
- Turn on debugging mode
- Turn off the watch and turn it back on again.
- You may need to wait a few minutes.
11. Once you have done this, you can open the Samsung Galaxy Wearable app and go to settings. When you scroll down you should see samsung pay.
If you dont see pay, hold down the back button (Top right button) on the watch till samsung pay opens up and follow the instuctions to set it up. But initially the Samsung pay app is not recognising my compatible Indian Debit and Credit card and not allowing me to add, i thought this might be that i had changed the region to Australia, but i tried again after an hour and then to my surprise i am able to add all my 4 cards to Samsung pay app , and it is working also, i tried a payment at NFC enabled terminal and payment works flawlessly
Enjoy your new watch with Samsung Pay enabled.
Click to expand...
Click to collapse
It is show me a failed to connect
[email protected] said:
It is show me a failed to connect
Click to expand...
Click to collapse
Delete .tizen folder from c:/users/your user name, make sure you have enabled the option of seeing hidden files, .tizen is hidden folder, if u can't see this folder, install tizen studio and remove this folder
Sent from my [device_name] using XDA-Developers Legacy app
I ve added all to magisk hide. But still cant open samsung pay watch plugin. Still getting access denied
Hey,
Is it possible that thanks to your method I will be able to turn on Samsung pay in my country (Poland) if it is not supported? Only Google pay works. Maybe I will need to do it using paypal? Thank you for your help in advance
Miccia said:
I ve added all to magisk hide. But still cant open samsung pay watch plugin. Still getting access denied
Click to expand...
Click to collapse
Fixed by using an older version of the plugin
FYI, I just received my Galaxy Watch today. Installed Samsung Pay (ver. 1.9.1206) on my Pixel 3XL and tried to run it but was denied because of Magisk (ver. 19.3 stable). So I hid the Manager via Hide Magisk Manager from within the app. I then was allowed to go through the setup process and add a credit card.
Failed to connect with remote device.
I have getting error failed to connect with remote device while connecting to galaxy watch . How to fix this.
Hello guys,
I also have error - failed to connect. When I try to ping the watch, the ping responses...
I tried it on fresh Windows 7 and 10 installations, also on Mac. Also tried to add the port to IP address. But always failed to connect... There is no message on the watch.
Any idea guys?
Thanks a lot.
OK guys your watch will still work with many Wear OS apps but apps won't sync up with your phone any more. The problem is that the version of Google Play Services on your watch is way out of date.
The solution is you need to sideload a newer version of google play services and then like magic all your apps that can still work with Wear OS 1.5 will work again.
You need to download and install adb fastboot on your PC, and the USB drivers for your particular model of phone. Then go to apkmirror and download the latest version of "Google Play Services (Wear OS)" as an APK.
Now put your Smartwatch into developer mode by going to settings --> about --> build number (click it 7 times, congrats you are now a developer)
Now go to Settings --> Developer Options --> ADB Debugging (enable) and Bluetooth debugging (enable)
Back on your phone, Wear OS App --> Advanced Settings --> Debugging over bluetooth (enable)
Enable Developer options on your phone as well through settings --> About --> Software info --> Build number seven times. Enable USB debugging.
Plug phone into PC with usb and open a command prompt in the directory where you've installed the adb files
Code:
ADB devices
should show your phone unauthorized. Authorize it on the phone popup prompt. Now the command should show your phone as "device"
Code:
adb forward tcp:6666 localabstract:/adb-hub
adb connect localhost:6666
On your watch, authorize the connection
On your phone, Wear OS app, Advanced settings, you should see Host: connected and Target:connected
If you get into trouble, run
Code:
adb kill-server
and try again.
Now you can install the apk
Code:
adb -e install -r (path to apk)
it will take a long while and may appear to hang. Give it time, at least 15 minutes. Go do something else. Wait for the command prompt to come back.
Now reboot your watch and revel in the magic as your apps suddenly reappear.
You also try sideloading other apps your mileage may vary. On APK mirror you can sometimes find older verions of Wear OS apps, look for ones that require Android 6.0+ Instead of 7.1.+
FYI I've tried sideloading several apps, and while many don't work properly, I was able to get Maps working by sideloading
com.google.android.apps.maps_10.35.2-1035250000_minAPI23(nodpi)_apkmirror.com.apk
Hi,
Thanks for this =)
Is there a reason to push the app through the phone instead of directly to watch?
EDIT: just do the same but directly connect the watch through USB worked well for me, including installing more apps like GMaps and Messages.
EDIT2: Just did this, so people could find this workaround faster =) https://support.google.com/wearos/thread/55427445
stormPremier said:
EDIT2: Just did this, so people could find this workaround faster =) https://support.google.com/wearos/thread/55427445
Click to expand...
Click to collapse
Sorry, this page can't be found. Do you have another link?
i5510 said:
Sorry, this page can't be found. Do you have another link?
Click to expand...
Click to collapse
Weird, I can't access this page using Private Navigation, you may need to be connected to your google account to access it ?
Also, it may not be published yet.
stormPremier said:
Weird, I can't access this page using Private Navigation, you may need to be connected to your google account to access it ?
Also, it may not be published yet.
Click to expand...
Click to collapse
Unfortunately, I don't use an account by Google. Would you mind quoting your solution here?
Hey first of all, thank you to bring me a light to follow,
I can confirm that if you use usb is more quickly, just I have:
1: installed "15 seconnds adb installer v1.4.3" found on this forum
2: Plug my smartwatch 3 on my pc (windows 10)
3: downloaded the most recent google play services (wear os) from apk mirror
4: rename the downloaded apk with a shorter name
5: placed the apk on C: and then open a power shell window in that location (****f+right click)
6: put this command adb install -r -g aplicationname.apk
7: wait 5 minutes
8: enjoy
by: Alexai Medina
i5510 said:
Would you mind quoting your solution here?
Click to expand...
Click to collapse
Hi people,
I own a sony smartwatch 3, got some problems about sync multiple times. I always found simples workarounds but some days ago, Google dropped support for wear 1.5 devices.
I consider this as an official announcement:
https://support.google.com/wearos/thread/5538033?hl=en
Therefore, we have a "workaround" for those that need more time to buy another smartwatch or else.
Inspired from this: https://forum.xda-developers.com/smartwatch/smartwatch-3/fix-app-sync-smartwatch-3-dead-t4121409
# Download the latest GService for Wear OS
Using apkmirror website you can find the latest apk for "Google Play Services (Wear OS)",
This link will give you the page of GService v20.21.17 which is the latest available on 2020-06-25.
You must ensure 2 things:
- Is it the latest version
- Is it compatible with Android 6.0+ (as it's the wear android version, 7.0+ and above will not work)
You can also download other apks to install, see the "More" section at the bottom of this post.
Soon or later, Google will definitely drop android 6.0. When this will happen, the latest version will not be available anymore for android 6.0+, therefore it will be the end.
# Download/Install adb debugging tools on your computer
There are multiple ways to install the adb debugging tool, I recommend following the steps you'll find on XDA website: https://www.xda-developers.com/install-adb-windows-macos-linux/
Available for Windows, Linux, and macOS.
# Enable ADB Debugging options on your watch
Enable developer mode by going to
Settings --> about --> build number (click it 7 times, congrats you are now a developer)
Now go to Settings --> Developer Options --> ADB Debugging (enable)
Then open and keep the command line window (aka "terminal")
# Connect your watch to your computer
Then using the terminal, type "adb devices", after a moment, you should get a prompt asking for debugging permission on your watch: accept.
In the terminal, you should now see something like "14452D11F536B52 device" when typing "adb devices" again.
If you see "unauthorized" or else, you're not ready for the next step, go back and try again.
If you struggle at this step, you may need specific drivers or else for your watch, google will be your best friend at this point.
# Send the app to your watch
In the terminal, type "adb install -r path_to_the_apk_file", replace path_to_the_apk_file by the path to the file you download from apkmirror earlier.
Then wait, the installation can take several minutes. Once it's done, restart your watch and you should see the apps beginning to synchronize themself =)
----
If you're new to the command-line tool (aka "terminal"), I'll assume you're a window user.
So you may need to type something like "adb install -r C:/Users/Robert/Downloads/file_downloaded.apk", again, you'll have to replace Robert by your windows username and file_downloaded.apk by the name of the file you downloaded earlier.
The best way to get this line right: open the file explorer, click "This computer" in the sidebar, then click on your main hard drive, then the folder "Users". Here you should see a folder with your username, click on it, then go through folders & files until you see the downloaded file. Once it's done, you should be able to get the full pathname by click in the explorer address bar (didn't understand ? See https://winaero.com/blog/show-full-path-address-bar-windows-10-file-explorer/ ) then at this point you should know how to execute the last command by reading again the last step "Send the app to your watch"
----
# More
You can follow this step and install any apk you want, but I don't recommend installing apk not made for Wear OS even if it works
More apps installable this way on your watch if you don't want to wait for app sync:
- Google Messages (SMS), latest is v6.1.095 on 2020-06-25
- Google Maps, latest is v10.35.2 (android 6.0+) on 2020-06-25
The GMaps is a good example about obsolete versions: on 2020-06-25, the real latest available is v10.43.2, but it's android 7.0+ only, so don't expect GMaps to work indefinitely for your watch, it will stop working soon or later.
# Say thanks
Please, if you can click upvote or post an answer: it will help people with the same problem find this
Thanks for posting a simplified process.
I only used Bluetooth because I have other Wear OS watches that don't work over cable connect, so it's the way I am familiar with. I like to use different watches depending upon activity and mood. The Smartwatch 3 is a great watch for outdoor activities because it is sleek, waterproof, and very sunlight visible.
stormPremier said:
Hi people,
I own a sony smartwatch 3, got some problems about sync multiple times. I always found simples workarounds but some days ago, Google dropped support for wear 1.5 devices.
I consider this as an official announcement:
https://support.google.com/wearos/thread/5538033?hl=en
Therefore, we have a "workaround" for those that need more time to buy another smartwatch or else.
Inspired from this: https://forum.xda-developers.com/smartwatch/smartwatch-3/fix-app-sync-smartwatch-3-dead-t4121409
# Download the latest GService for Wear OS
Using apkmirror website you can find the latest apk for "Google Play Services (Wear OS)",
This link will give you the page of GService v20.21.17 which is the latest available on 2020-06-25.
You must ensure 2 things:
- Is it the latest version
- Is it compatible with Android 6.0+ (as it's the wear android version, 7.0+ and above will not work)
You can also download other apks to install, see the "More" section at the bottom of this post.
Soon or later, Google will definitely drop android 6.0. When this will happen, the latest version will not be available anymore for android 6.0+, therefore it will be the end.
# Download/Install adb debugging tools on your computer
There are multiple ways to install the adb debugging tool, I recommend following the steps you'll find on XDA website: https://www.xda-developers.com/install-adb-windows-macos-linux/
Available for Windows, Linux, and macOS.
# Enable ADB Debugging options on your watch
Enable developer mode by going to
Settings --> about --> build number (click it 7 times, congrats you are now a developer)
Now go to Settings --> Developer Options --> ADB Debugging (enable)
Then open and keep the command line window (aka "terminal")
# Connect your watch to your computer
Then using the terminal, type "adb devices", after a moment, you should get a prompt asking for debugging permission on your watch: accept.
In the terminal, you should now see something like "14452D11F536B52 device" when typing "adb devices" again.
If you see "unauthorized" or else, you're not ready for the next step, go back and try again.
If you struggle at this step, you may need specific drivers or else for your watch, google will be your best friend at this point.
# Send the app to your watch
In the terminal, type "adb install -r path_to_the_apk_file", replace path_to_the_apk_file by the path to the file you download from apkmirror earlier.
Then wait, the installation can take several minutes. Once it's done, restart your watch and you should see the apps beginning to synchronize themself =)
----
If you're new to the command-line tool (aka "terminal"), I'll assume you're a window user.
So you may need to type something like "adb install -r C:/Users/Robert/Downloads/file_downloaded.apk", again, you'll have to replace Robert by your windows username and file_downloaded.apk by the name of the file you downloaded earlier.
The best way to get this line right: open the file explorer, click "This computer" in the sidebar, then click on your main hard drive, then the folder "Users". Here you should see a folder with your username, click on it, then go through folders & files until you see the downloaded file. Once it's done, you should be able to get the full pathname by click in the explorer address bar (didn't understand ? See https://winaero.com/blog/show-full-path-address-bar-windows-10-file-explorer/ ) then at this point you should know how to execute the last command by reading again the last step "Send the app to your watch"
----
# More
You can follow this step and install any apk you want, but I don't recommend installing apk not made for Wear OS even if it works
More apps installable this way on your watch if you don't want to wait for app sync:
- Google Messages (SMS), latest is v6.1.095 on 2020-06-25
- Google Maps, latest is v10.35.2 (android 6.0+) on 2020-06-25
The GMaps is a good example about obsolete versions: on 2020-06-25, the real latest available is v10.43.2, but it's android 7.0+ only, so don't expect GMaps to work indefinitely for your watch, it will stop working soon or later.
# Say thanks
Please, if you can click upvote or post an answer: it will help people with the same problem find this
Click to expand...
Click to collapse
Thank you very much!!!!
You saved my watch!
Hi. In the link to install the adb debugging tool, I can only get as far step 6 connecting my phone. When i type 'adb devices' in the command prompt it says -
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
Nothing appear on my phone as per the step 7 "On your phone’s screen, you should see a prompt to allow or deny USB Debugging access"
Can anyone help?
@MrFleas
1) go again on EVERY.SINGLE.STEP this may feel dumb to do but it could help
2) if it does not work, try googling for swr50 USB drivers, you may need to download Android SDK and drivers - then reboot - then start again at step one
3) come back here to thanks or asking for more help
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
Hi people, just realized we can also download the sony app to our phones (directly from phone or by using adb like on watch) so we can edit stock watch faces again =)
Here's the app to download to the phone: https://www.apkmirror.com/apk/sony-...ditor-2-0-0-20-android-apk-download/download/
Once installed, to edit watch faces, go to wear app, the edit watch faces =)
Seems like the same issue...
My hardly used smart watch is ALIVE again!
Thanks a lot guys!
I have latest but sync not working :/ i have a question is possibile install app with higher api or change apk API level ?
check the play service on your phone and install exactly the same version of the wear app
then it works
Cheers for doing this! Got my old smartwatch working cause of that. If anyone else reading this has issues at the' ADB device' point, and is using a linux based system, remember to use sudo on the commands -as otherwise i found that it would not enable the prompt to let me 'authorise' the device in order to send the apk to the watch.
Question- given that google have disabled the onboard step counter function on wear 1.5 devices (like this one), can we sideload a fitness apk via adb with this method that will then sync to our phones?
skwal83 said:
check the play service on your phone and install exactly the same version of the wear app
then it works
Click to expand...
Click to collapse
Hi, I've got the same issue. I had to change my phone. I've installed the same version of google play services on the watch with the description in this threat. But the phone is still not syncing the apps to the watch. Is there anything more I can do to trigger the sync (already triggered 'resync all app in Wear OS' without effect).
You might try to go Settings-Permissions on the watch and set the Permissions for your app. Sometimes I have got this to make the app work, when it is already installed on the watch but not working.
It works! I first downloaded this version of Wear OS for my phone:
Wear 2.43, the newest one somehow broke the sync for me.
By using ADB with " ADB install -r "I installed the last working Google Play Services for my Watch and also the last available version of Google Fit for Android 6.
Play Services : Play Services Wear OS - 20.45.16
Google fit : Google Fit - 2.10.36