Related
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
This isnt working for me on my OPO running CM12 unofficial... Running the commands gives me a blank adb devices window, any advice?
Hi,
I guess you get the empty device list after the "start adbd" command, right?
Just to be sure, before running the adb devices commad do "adb kill-server"
If adb devices still gives you an empty list of devices try with:
> adb connect localhost:5555
And check again. Usually, what should happen, the adb server detects a adbd listening in the port 5555 and it considers it is an android emulator and it connects to it automatically. Maybe in your case it is not connecting, so the connect command might help. Once you hace at least your phone showing you can run the other commands to access the watch.
Let me know if this helps
gusano38 said:
Hi,
I guess you get the empty device list after the "start adbd" command, right?
Just to be sure, before running the adb devices commad do "adb kill-server"
If adb devices still gives you an empty list of devices try with:
> adb connect localhost:5555
And check again. Usually, what should happen, the adb server detects a adbd listening in the port 5555 and it considers it is an android emulator and it connects to it automatically. Maybe in your case it is not connecting, so the connect command might help. Once you hace at least your phone showing you can run the other commands to access the watch.
Let me know if this helps
Click to expand...
Click to collapse
Works like a charm thanks for the help
Where is the adb binary? Adb isn't a recognized command
My binary is in /system/bin/adb
Sideloading...
Really great, all works... until I try to sideload an APK. I keep getting invalid apk file. I'm doing it by:
adb -s _____ install ____.apk
but it's not working. Any suggestions?
gusano38 said:
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
Click to expand...
Click to collapse
AJWizkid said:
Really great, all works... until I try to sideload an APK. I keep getting invalid apk file. I'm doing it by:
adb -s _____ install ____.apk
but it's not working. Any suggestions?
Click to expand...
Click to collapse
Adb -s localhost:4444 install my.apk
Where can I download the script?
¯\_(ツ)_/¯
thegrim11 said:
Where can I download the script?
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Here's the script.
Using Root Explorer:
Create a folder under /system and copy adbgwrbt.sh there
Set permissions to 100 (execute for owner)
Tap script and hit execute
Profit
No credit. Just copied and pasted from OP. Thank you so much for this gusano!! Always find myself needing this . Now if you could just figure out fastboot [emoji57]
Oh my, thank you very much, I've been trying to do this ever since I got my watch but just didn't have the skills (still managed to fins an other way to send files from the phone to the watch and even install apk's), you're great man!
hatefuel19 said:
Now if you could just figure out fastboot [emoji57]
Click to expand...
Click to collapse
I'm pretty sure that in fastboot mode (bootloader) the bluetooth driver is not loaded, so I guess having fastboot with bluetooth is not possible. Furthermore, I would not trust a bluetooth connection to do things that could brick your watch... of course, the pogo pins is not what I call a super trustable connection either
The sarcasm was lost apparently ?
Grr. Got a replacement phone from insurance and the binary isn't there. Can someone please pm me the adb from system/bin?
Sent from my XT1060 using Tapatalk
gusano38 said:
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
Click to expand...
Click to collapse
Loved your post!
Thing is I get an error each time I try the script.
I own a rooted LG G3 ChupaChups 4.2 ROM and a LG G Watch R
Thanx in advance to your help.
setprop service.adb.tcp.port 5555
Sent from my HTC One_M8 using Tapatalk
Unauthorized
ADB tells me that my device has not authorized itself as an adb connection. The problem is since it's not actually a standard USB debugging connection I don't get a popup to mark my device as trusted. Is there anyway to work around this?
I always get the error from the pictures
N4 Android 6.0 Frank rooted xposed
LG g watch wear 5.1.1 rooted (no idea what adventages)
Gesendet von meinem Nexus 4 mit Tapatalk
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
J0SH1X said:
I always get the error from the pictures
N4 Android 6.0 Frank rooted xposed
LG g watch wear 5.1.1 rooted (no idea what adventages)
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
And yes I did enable all debugging setting in companion app on phone on wear
Gesendet von meinem Nexus 4 mit Tapatalk
i have this problem not connect to localhost 4444. i have cm13
adb commands won't work for me.
I am wondering around the internet to learn any method to disable MTP/PTP/all usb stuff except charging.
So, why i want this?
Because i want my device to be secure.
I don't anyone to sneak around and try to go into bootloader or recovery/connection to a pc etc to set my device to make a fresh start/copying data and end my privacy up.
So is there a way to disable those functions?
And if it is possible then what? Will it be secured?
And the big question is that can i enable it through recovery (from adb or moving mobile files) as you know if one has a messed up rom then he/she should have those functions workable.
I have Galaxy S3 Neo GT-I9301I
With stock rom (rooted)
I found this on a web:
.
The most device-compatible way to disable everything is to run this command at startup or set this in your build.prop:
Code:
setprop persist.sys.usb.config none
which is equivalent to charge-only on all Android devices.
That also disables adb. If you use adb regularly, then:
Code:
setprop persist.sys.usb.config adb
will allow adb when developer options are turned on/checked. If you don't use ADB often, I would not recommend it, because setting adb causes my S5 to still recognize in device manager, even when it is locked.
To restore original functionality,
Code:
setprop persist.sys.usb.config mtp,ptp,adb
allows all USB protocols.
Hello,
I have Oneplus One 64 gb variant, yesterday my nephew somehow changed my phone's lock pattern and now my phone is locked. USB debugging was disabled at that time. I am not able to get into my phone through any means. I have lot of important data in my phone and don't want to hard reset my device. I found a solution online to get usb debugging on through adb , but I am a ultra noob and don't understand how that has to be done. please dumb it down so that I can save my precious data and unlock my phone when debugging gets enabled. Also I don't have any custom recovery installed on my phone.
This is what is mentioned in the solution.
"Instructions
1. You should try your pattern-cracking software (or whatsoever the genre it has) from inside the Stock Recovery to see whether it works with the former's environment (ADB shell available there or not).
2.Since I would never try step 1., I would do the following:
-For Jellybean 4.2.1:
1. Boot into Recovery and mount Data partition.
2. Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace ~/ with home directory of your OS.
3. Open that file in a text editor and you would possibly see mtp written there. Change it to mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using adb pull but doing:
adb shell
echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the echo command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
4. Unmount Data and reboot into Android OS. USB Debugging would probably be enabled.
-For Lollipop 5.0:
JB 4.2.1 users can also follow this method if the previous one didn't work for them.
1. Boot into Recovery and mount Data partition.
2. Repeat step 2 and 3 used in JB 4.2.1 method.
3. We need to tweak some parameters in settings.db. Type:
adb pull /data/data/com.android.providers.settings/databases/settings.db ~/
4. Back it up at some other location too, and open the file in an SQLITE editor. I'm running Linux and DB Browser for SQLite works well. It's also available for Windows OS/OSX.
5. In the global table, change the value for:
adb_enabled to 1
development_settings_enabled to 1
6. Check that verifier_verify_adb_installs is set to 1 in the global table.
7. Check that as default, in the secure table:
adb_notify is 1
adb_port is -1
These checks in step 6 and 7 are not necessary but should be done so that troubleshooting becomes rather easy if the solution doesn't work for you.
8. Save the changes in settings.db and copy it back into Android by typing:
adb shell
rm /data/data/com.android.providers.settings/databases/settings.db
exit
adb push ~/settings.db /data/data/com.android.providers.settings/databases/
That delete (rm) command is not necessary since adb push should overwrite the file, but I executed it for my peace of mind.
8. Unmount Data and reboot into Android OS. ADB probably would be enabled.
source:- https://android.stackexchange.com/questions/112040/how-to-enable-usb-debugging-in-android-if-forgotten-pattern-for-screen-unlock"
Please help me understand this code and be a life saver.
Thanks in advance..
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
jisoo said:
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
Click to expand...
Click to collapse
Is there any way I can create backup of the data in these conditions?
Dush123 said:
Is there any way I can create backup of the data in these conditions?
Click to expand...
Click to collapse
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
jisoo said:
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
Click to expand...
Click to collapse
Ohk. Then it seems I don't have any option but to hard reset my device.
Thanks anyways
HI! Is there anything I can do for my pattern locked Moto E4 Plus? Details I've posted in this thread.
https://forum.xda-developers.com/showthread.php?t=2620456&page=13
Hi folks, I have just got my Find X2 Pro today and so far I am loving it, however one feature is missing for me. On my old Mate 20 Pro, I had the google discover feed if I did swipe right....is there anyway to enable this on the Oppo phone. All I currently have is the smart assistant which does work but its not ideal.
Blackwatch said:
Hi folks, I have just got my Find X2 Pro today and so far I am loving it, however one feature is missing for me. On my old Mate 20 Pro, I had the google discover feed if I did swipe right....is there anyway to enable this on the Oppo phone. All I currently have is the smart assistant which does work but its not ideal.
Click to expand...
Click to collapse
Only on some oppo find x2 pros others don't have it, there's allot of things missing , the theme store to doesn't work for most people
Sent from my AC2003 using Tapatalk
kevinireland11 said:
Only on some oppo find x2 pros others don't have it, there's allot of things missing , the theme store to doesn't work for most people
Sent from my AC2003 using Tapatalk
Click to expand...
Click to collapse
Err i dont think i have the theme store on my device..
Blackwatch said:
Err i dont think i have the theme store on my device..
Click to expand...
Click to collapse
It's all questions with oppo and no answers , never had so much trouble with a phone in my life
Sent from my AC2003 using Tapatalk
Not sure if you figured this out, I was going to do a guide but decided just to post here:
All you need to do to get the discover feed (only tested on ColorOS 11), is to remove the Oppo smart assistant app (what you currently get when swiping left on the home screen).
You need to force the app off with ADB, reboot your phone and as long as you have the Google app installed, you'll have the discover feed!
The ADB command to run is:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
If for some reason you want to reinstall, you can do so with this command:
adb shell cmd package install-existing com.coloros.assistantscreen
If you don't know how to get and use ADB, here's a quick guide.....
You can download Platform Tools directly from the Android developer here: https://developer.android.com/studio/releases/platform-tools
There are loads of more detailed guides on how to use ADB, but basic steps are:
Download the platform tools from the link above and extract to somewhere on your PC, e.g. C:/platform-tools
Open a command prompt on your PC (type cmd in the Windows search bar) and right click on it then run as Administrator
Change the directory to where your 'platform-tools' folder (so something like 'cd C:/platform-tools')
On your phone, USB debugging needs to be enabled, so:
Enable developer options by going to settings > About Phone > Version and clicking on Build number several times
Under Additional Settings > Developer Options, enable 'USB Debugging'
Plug your phone into a USB port on the PC
Make sure your phone is on 'Transfer Files / Android Auto' mode (the default is 'Charge only' mode)
Once set, you should get a popup on your phone to ask to Allow USB debugging, click 'Allow'.
Back in the command prompt, type 'adb devices' and hit return (you should see the serial number of your phone if connected)
Now you can get deleting - run the command mentioned above to remove the smart assistant app.
Note that it doesn't actually delete the app from the phone, it just removes it for the main user, i.e. you.
Done, enjoy!
klanbo78 said:
Not sure if you figured this out, I was going to do a guide but decided just to post here:
All you need to do to get the discover feed (only tested on ColorOS 11), is to remove the Oppo smart assistant app (what you currently get when swiping left on the home screen).
You need to force the app off with ADB, reboot your phone and as long as you have the Google app installed, you'll have the discover feed!
The ADB command to run is:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
If for some reason you want to reinstall, you can do so with this command:
adb shell cmd package install-existing com.coloros.assistantscreen
If you don't know how to get and use ADB, here's a quick guide.....
You can download Platform Tools directly from the Android developer here: https://developer.android.com/studio/releases/platform-tools
There are loads of more detailed guides on how to use ADB, but basic steps are:
Download the platform tools from the link above and extract to somewhere on your PC, e.g. C:/platform-tools
Open a command prompt on your PC (type cmd in the Windows search bar) and right click on it then run as Administrator
Change the directory to where your 'platform-tools' folder (so something like 'cd C:/platform-tools')
On your phone, USB debugging needs to be enabled, so:
Enable developer options by going to settings > About Phone > Version and clicking on Build number several times
Under Additional Settings > Developer Options, enable 'USB Debugging'
Plug your phone into a USB port on the PC
Make sure your phone is on 'Transfer Files / Android Auto' mode (the default is 'Charge only' mode)
Once set, you should get a popup on your phone to ask to Allow USB debugging, click 'Allow'.
Back in the command prompt, type 'adb devices' and hit return (you should see the serial number of your phone if connected)
Now you can get deleting - run the command mentioned above to remove the smart assistant app.
Note that it doesn't actually delete the app from the phone, it just removes it for the main user, i.e. you.
Done, enjoy!
Click to expand...
Click to collapse
Perfect! Thank you for this guide.
klanbo78 said:
Not sure if you figured this out, I was going to do a guide but decided just to post here:
All you need to do to get the discover feed (only tested on ColorOS 11), is to remove the Oppo smart assistant app (what you currently get when swiping left on the home screen).
You need to force the app off with ADB, reboot your phone and as long as you have the Google app installed, you'll have the discover feed!
The ADB command to run is:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
If for some reason you want to reinstall, you can do so with this command:
adb shell cmd package install-existing com.coloros.assistantscreen
If you don't know how to get and use ADB, here's a quick guide.....
You can download Platform Tools directly from the Android developer here: https://developer.android.com/studio/releases/platform-tools
There are loads of more detailed guides on how to use ADB, but basic steps are:
Download the platform tools from the link above and extract to somewhere on your PC, e.g. C:/platform-tools
Open a command prompt on your PC (type cmd in the Windows search bar) and right click on it then run as Administrator
Change the directory to where your 'platform-tools' folder (so something like 'cd C:/platform-tools')
On your phone, USB debugging needs to be enabled, so:
Enable developer options by going to settings > About Phone > Version and clicking on Build number several times
Under Additional Settings > Developer Options, enable 'USB Debugging'
Plug your phone into a USB port on the PC
Make sure your phone is on 'Transfer Files / Android Auto' mode (the default is 'Charge only' mode)
Once set, you should get a popup on your phone to ask to Allow USB debugging, click 'Allow'.
Back in the command prompt, type 'adb devices' and hit return (you should see the serial number of your phone if connected)
Now you can get deleting - run the command mentioned above to remove the smart assistant app.
Note that it doesn't actually delete the app from the phone, it just removes it for the main user, i.e. you.
Done, enjoy!
Click to expand...
Click to collapse
Works perfectly on my Find X2 Lite (ColorOS 11 too). Thank you so much for the wonderful guide! I just received the April 2021 update (by using a VPN to France). and without adding back Oppo Smart Assistant, it appears to work just fine. Also worth noting that the annoying Smart Assistant did not come back from this update.
So it seems (to me at least) that you don't need to bring back Smart Assistant before every update. But still, I would recommend doing so just anyways, especially when the Android 12 update comes around.
klanbo78 said:
Not sure if you figured this out, I was going to do a guide but decided just to post here:
All you need to do to get the discover feed (only tested on ColorOS 11), is to remove the Oppo smart assistant app (what you currently get when swiping left on the home screen).
You need to force the app off with ADB, reboot your phone and as long as you have the Google app installed, you'll have the discover feed!
The ADB command to run is:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
If for some reason you want to reinstall, you can do so with this command:
adb shell cmd package install-existing com.coloros.assistantscreen
If you don't know how to get and use ADB, here's a quick guide.....
You can download Platform Tools directly from the Android developer here: https://developer.android.com/studio/releases/platform-tools
There are loads of more detailed guides on how to use ADB, but basic steps are:
Download the platform tools from the link above and extract to somewhere on your PC, e.g. C:/platform-tools
Open a command prompt on your PC (type cmd in the Windows search bar) and right click on it then run as Administrator
Change the directory to where your 'platform-tools' folder (so something like 'cd C:/platform-tools')
On your phone, USB debugging needs to be enabled, so:
Enable developer options by going to settings > About Phone > Version and clicking on Build number several times
Under Additional Settings > Developer Options, enable 'USB Debugging'
Plug your phone into a USB port on the PC
Make sure your phone is on 'Transfer Files / Android Auto' mode (the default is 'Charge only' mode)
Once set, you should get a popup on your phone to ask to Allow USB debugging, click 'Allow'.
Back in the command prompt, type 'adb devices' and hit return (you should see the serial number of your phone if connected)
Now you can get deleting - run the command mentioned above to remove the smart assistant app.
Note that it doesn't actually delete the app from the phone, it just removes it for the main user, i.e. you.
Done, enjoy!
Click to expand...
Click to collapse
Worked perfectly on Find X2 Pro, first time ever using ADB! Thank you so much!
klanbo78 said:
Not sure if you figured this out, I was going to do a guide but decided just to post here:
All you need to do to get the discover feed (only tested on ColorOS 11), is to remove the Oppo smart assistant app (what you currently get when swiping left on the home screen).
You need to force the app off with ADB, reboot your phone and as long as you have the Google app installed, you'll have the discover feed!
The ADB command to run is:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
If for some reason you want to reinstall, you can do so with this command:
adb shell cmd package install-existing com.coloros.assistantscreen
If you don't know how to get and use ADB, here's a quick guide.....
You can download Platform Tools directly from the Android developer here: https://developer.android.com/studio/releases/platform-tools
There are loads of more detailed guides on how to use ADB, but basic steps are:
Download the platform tools from the link above and extract to somewhere on your PC, e.g. C:/platform-tools
Open a command prompt on your PC (type cmd in the Windows search bar) and right click on it then run as Administrator
Change the directory to where your 'platform-tools' folder (so something like 'cd C:/platform-tools')
On your phone, USB debugging needs to be enabled, so:
Enable developer options by going to settings > About Phone > Version and clicking on Build number several times
Under Additional Settings > Developer Options, enable 'USB Debugging'
Plug your phone into a USB port on the PC
Make sure your phone is on 'Transfer Files / Android Auto' mode (the default is 'Charge only' mode)
Once set, you should get a popup on your phone to ask to Allow USB debugging, click 'Allow'.
Back in the command prompt, type 'adb devices' and hit return (you should see the serial number of your phone if connected)
Now you can get deleting - run the command mentioned above to remove the smart assistant app.
Note that it doesn't actually delete the app from the phone, it just removes it for the main user, i.e. you.
Done, enjoy!
Click to expand...
Click to collapse
Hi
Working fine on my Oppo Find X2 Pro ColorOS 11
klanbo78 said:
Not sure if you figured this out, I was going to do a guide but decided just to post here:
All you need to do to get the discover feed (only tested on ColorOS 11), is to remove the Oppo smart assistant app (what you currently get when swiping left on the home screen).
You need to force the app off with ADB, reboot your phone and as long as you have the Google app installed, you'll have the discover feed!
The ADB command to run is:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
If for some reason you want to reinstall, you can do so with this command:
adb shell cmd package install-existing com.coloros.assistantscreen
If you don't know how to get and use ADB, here's a quick guide.....
You can download Platform Tools directly from the Android developer here: https://developer.android.com/studio/releases/platform-tools
There are loads of more detailed guides on how to use ADB, but basic steps are:
Download the platform tools from the link above and extract to somewhere on your PC, e.g. C:/platform-tools
Open a command prompt on your PC (type cmd in the Windows search bar) and right click on it then run as Administrator
Change the directory to where your 'platform-tools' folder (so something like 'cd C:/platform-tools')
On your phone, USB debugging needs to be enabled, so:
Enable developer options by going to settings > About Phone > Version and clicking on Build number several times
Under Additional Settings > Developer Options, enable 'USB Debugging'
Plug your phone into a USB port on the PC
Make sure your phone is on 'Transfer Files / Android Auto' mode (the default is 'Charge only' mode)
Once set, you should get a popup on your phone to ask to Allow USB debugging, click 'Allow'.
Back in the command prompt, type 'adb devices' and hit return (you should see the serial number of your phone if connected)
Now you can get deleting - run the command mentioned above to remove the smart assistant app.
Note that it doesn't actually delete the app from the phone, it just removes it for the main user, i.e. you.
Done, enjoy!
Click to expand...
Click to collapse
it Woked Perfect ...Thanks buddy
Nomsam86 said:
it Woked Perfect ...Thanks buddy
Click to expand...
Click to collapse
Have you tried it on Android 12? Thanks
klanbo78 said:
Not sure if you figured this out, I was going to do a guide but decided just to post here:
All you need to do to get the discover feed (only tested on ColorOS 11), is to remove the Oppo smart assistant app (what you currently get when swiping left on the home screen).
You need to force the app off with ADB, reboot your phone and as long as you have the Google app installed, you'll have the discover feed!
The ADB command to run is:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
If for some reason you want to reinstall, you can do so with this command:
adb shell cmd package install-existing com.coloros.assistantscreen
If you don't know how to get and use ADB, here's a quick guide.....
You can download Platform Tools directly from the Android developer here: https://developer.android.com/studio/releases/platform-tools
There are loads of more detailed guides on how to use ADB, but basic steps are:
Download the platform tools from the link above and extract to somewhere on your PC, e.g. C:/platform-tools
Open a command prompt on your PC (type cmd in the Windows search bar) and right click on it then run as Administrator
Change the directory to where your 'platform-tools' folder (so something like 'cd C:/platform-tools')
On your phone, USB debugging needs to be enabled, so:
Enable developer options by going to settings > About Phone > Version and clicking on Build number several times
Under Additional Settings > Developer Options, enable 'USB Debugging'
Plug your phone into a USB port on the PC
Make sure your phone is on 'Transfer Files / Android Auto' mode (the default is 'Charge only' mode)
Once set, you should get a popup on your phone to ask to Allow USB debugging, click 'Allow'.
Back in the command prompt, type 'adb devices' and hit return (you should see the serial number of your phone if connected)
Now you can get deleting - run the command mentioned above to remove the smart assistant app.
Note that it doesn't actually delete the app from the phone, it just removes it for the main user, i.e. you.
Done, enjoy!
Click to expand...
Click to collapse
Can someone advise if this process works on the Oppo Find X2 Pro running Color0S 12.1?
Cura96 said:
Can someone advise if this process works on the Oppo Find X2 Pro running Color0S 12.1?
Click to expand...
Click to collapse
I just tried it and, at least in my case, worked only the first swipe and then it disappeared.
I'm on a Find X2 Pro (ColorOS 12 - CPH2025_11_F.13)
However I found out that it worked by updating the stock laucher. I don't know if I can share here the apk, but you can find it online: com.android.launcher_12.0.50-12050_minAPI30(arm64-v8a,armeabi,armeabi-v7a)(nodpi).apk
With this, after the uninstall od the OPPO Assistant via ABD, you'll have Google feed discover working on ColorOS 12
Anyone got this working for ColorOS 13?
When I run:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
I get a message saying the package can't be found???
klanbo78 said:
Not sure if you figured this out, I was going to do a guide but decided just to post here:
All you need to do to get the discover feed (only tested on ColorOS 11), is to remove the Oppo smart assistant app (what you currently get when swiping left on the home screen).
You need to force the app off with ADB, reboot your phone and as long as you have the Google app installed, you'll have the discover feed!
The ADB command to run is:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
If for some reason you want to reinstall, you can do so with this command:
adb shell cmd package install-existing com.coloros.assistantscreen
If you don't know how to get and use ADB, here's a quick guide.....
You can download Platform Tools directly from the Android developer here: https://developer.android.com/studio/releases/platform-tools
There are loads of more detailed guides on how to use ADB, but basic steps are:
Download the platform tools from the link above and extract to somewhere on your PC, e.g. C:/platform-tools
Open a command prompt on your PC (type cmd in the Windows search bar) and right click on it then run as Administrator
Change the directory to where your 'platform-tools' folder (so something like 'cd C:/platform-tools')
On your phone, USB debugging needs to be enabled, so:
Enable developer options by going to settings > About Phone > Version and clicking on Build number several times
Under Additional Settings > Developer Options, enable 'USB Debugging'
Plug your phone into a USB port on the PC
Make sure your phone is on 'Transfer Files / Android Auto' mode (the default is 'Charge only' mode)
Once set, you should get a popup on your phone to ask to Allow USB debugging, click 'Allow'.
Back in the command prompt, type 'adb devices' and hit return (you should see the serial number of your phone if connected)
Now you can get deleting - run the command mentioned above to remove the smart assistant app.
Note that it doesn't actually delete the app from the phone, it just removes it for the main user, i.e. you.
Done, enjoy!
Click to expand...
Click to collapse
I purposely registered an account to thank you.
Thank you for your detailed explanation
I'm trying to disable the guest user on my phone, running android 10 and non rooted, using adb. I have been attempting this by using the command: adb shell settings put global guest_user_enabled 0. However when I type it in nothing happens. Adb does pick up my device and once entering the command, I get no message or any sort of output.