Related
Linux users please go HERE (thanks to bloodychaos)Similar guides can be found on other devices subforums around but I can see that a lot of new users in our forum are not familiar with the setup and use of this commands.
All the instructions and installation files can be found on the Android Developers webpage, but for basic commands it is not necessary to download the whole SDK (which requires the JDK as well) to follow installation and the resources download process.
*Important: to use the adb/fastboot commands you have to enable USB Debugging in your phone Settings -> Applications -> Development menu*
To have working adb and fastboot system wide for basic commands just follow the steps below:
UPDATE: Not necessary for Windows 7 is installng adb drivers automatically after plugging the device and fastboot ones after rebooting the connected device to bootloader. To get the HTC USB Drivers on different Windows version download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system).
*According to post #5 in this thread in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync. Thanks @mimirom*
Download the zip archive or the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
Adding to the System Path globally to use the command without browsing to the containing folder
Method 1 (via GUI):
Go to My Computer icon -> right click and select Properties.
On the left side of the opened screen select Advanced system settings.
(Or Start -> Search -> type sysdm.cpl -> Enter, browse to the Advanced tab)
Look down on the opened menu and select Environment Variables.
In the lower half are listed the System Variables.
Scroll to find "Path" variable, select it and click Edit...
On the Edit window in the Variable value field go to the end of the line (do not delete it!) and add without any intervals (spaces):
Code:
;C:\android-tools
do not forget the semicolon symbol (;)!
Click Ok 3 times.
Method 2 (via Command prompt):
Go to Start and in the Search box type cmd, right click and Run as Administrator
Type
Code:
setx path /m "%PATH%;C:\android-tools"
and hit Enter. Close the cmd window
fonpacific said:
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Click to expand...
Click to collapse
Method 3:
bonesy said:
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
Click to expand...
Click to collapse
To check is it working properly open Command Prompt (Start -> Search -> type cmd -> Enter) and type adb
If everything is configured properly this should list you the Android Debug Bridge version and the available commands.
*HINT*: To use adb or fastboot with files in the Command prompt you have to navigate to the folder containing the file first (using the cd command) e.g. "D:\Downloads\Android" and then to execute the command.
Example:
Start -> type cmd in the Search box, then Enter. You will see
C:\Users\with blinking cursor
If your file is on another drive like the example type "d:" (without the quotes), or other drive letter to go to the relevant drive. Skip this if the file is on C: drive. Then type:
cd D:\Downloads\Android to go to the "D:\Downloads\Android" folder. If your path contains spaces (intervals) type it in quotes.
The command "cd.." brings you one folder back
Good Idea!
Have put a link to this within the GUIDES section of [INDEX][22 SEP 11] ROMS/RECOVERY/ROOT/HBOOT/RADIOS/TWEAKS/GUIDES/etc
I believe that the guide would be more useful if you put in a link to a URL for the HTC Drivers and moved the advice about enabling USB Debugging to the top!
I can now point people at this guide rather than manually instruct them, Thank's you probably just saved me loads of time and aggravation!
Nice Work, Great Help
Excellent! Exactly what I needed. Thanks for showing us this.
Hi an thank you. Good guide.
I believe one important information is missing in the guide:
Before installing the HTC drivers (or HTC sync) it is necessary to temporarily disable AntiVirus software on Windows machines. If you don't do that, Windows won't recognise your phone. After the installation is finished, enable AntiVirus again.
I got this advice somewhere and it was true for me personally. I'm using Windows 7.
Sent from my HTC Desire S using XDA App
One more comment:
This is a minor detail but I think it's worth mentioning.
If you are using the HTC Sync installation in order to get the HTC drivers only, you actually don't need to install and immediately uninstall HTC Sync itself.
The Sync installer will first install the Desired (pun fully intended ;-) drivers and the it will stop. Next it's going to ask you if you want to proceed with the installation of HTC Sync. At that point you hit cancel and you're done. No Sync, just the drivers.
mimirom said:
One more comment:
This is a minor detail but I think it's worth mentioning.
If you are using the HTC Sync installation in order to get the HTC drivers only, you actually don't need to install and immediately uninstall HTC Sync itself.
The Sync installer will first install the Desired (pun fully intended ;-) drivers and the it will stop. Next it's going to ask you if you want to proceed with the installation of HTC Sync. At that point you hit cancel and you're done. No Sync, just the drivers.
Click to expand...
Click to collapse
It's very useful, Thanks!!
Doing all this the phone has to be turned off, on, or power button and volume down?
Desire S said:
Doing all this the phone has to be turned off, on, or power button and volume down?
Click to expand...
Click to collapse
You do not need a phone for this guide It is setup for PC
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
bonesy said:
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
Click to expand...
Click to collapse
This is exactly the purpose of point 4 of the guide (global path setup)
Just trying to give another idea mate, I used to set up all the SDK and make a global path but now just drop them in those folders when i reinstal indows
bonesy said:
Just trying to give another idea mate, I used to set up all the SDK and make a global path but now just drop them in those folders when i reinstal indows
Click to expand...
Click to collapse
Agree, added to the first post.
Sent from my Desire S using Tapatalk
Instructions for Linux users???
jamsh said:
Instructions for Linux users???
Click to expand...
Click to collapse
On my Linux system I have installed Java and the whole Android SDK and the set the path of course. If you are a Linux user you should know how to do this. Also there are guides for other devices that are basically the same
amidabuddha said:
Similar guides can be found on other devices subforums around but I can see that a lot of new users in our forum are not familiar with the setup and use of this commands.
All the instructions and installation files can be found on the Android Developers webpage, but for basic commands it is not necessary to download the whole SDK (which requires the JDK as well) to follow installation and the resources download process.
*Important: to use the adb/fastboot commands you have to enable USB Debugging in your phone Settings -> Applications -> Development menu*
To have working adb and fastboot system wide for basic commands just follow the steps below:
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system).
*According to post #5 in this thread in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync. Thanks @mimirom*
Download the zip archive (Mirror @MediaFire) or the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
Adding to the System Path globally to use the command without browsing to the containing folder
Method 1 (via GUI):
Go to My Computer icon -> right click and select Properties.
On the left side of the opened screen select Advanced system settings.
(Or Start -> Search -> type sysdm.cpl -> Enter, browse to the Advanced tab)
Look down on the opened menu and select Environment Variables.
In the lower half are listed the System Variables.
Scroll to find "Path" variable, select it and click Edit...
On the Edit window in the Variable value field go to the end of the line (do not delete it!) and add without any intervals (spaces):
Code:
;C:\android-tools
do not forget the semicolon symbol (;)!
Click Ok 3 times.
Method 2 (via Command prompt):
Go to Start and in the Search box type cmd, right click and Run as Administrator
Type
Code:
setx path /m "%PATH%;C:\android-tools"
and hit Enter. Close the cmd window
Method 3:
To check is it working properly open Command Prompt (Start -> Search -> type cmd -> Enter) and type adb
If everything is configured properly this should list you the Android Debug Bridge version and the available commands.
*HINT*: To use adb or fastboot with files in the Command prompt you have to navigate to the folder containing the file first (using the cd command) e.g. "D:\Downloads\Android" and then to execute the command.
Example:
Start -> type cmd in the Search box, then Enter. You will see
C:\Users\with blinking cursor
If your file is on another drive like the example type "d:" (without the quotes), or other drive letter to go to the relevant drive. Skip this if the file is on C: drive. Then type:
cd D:\Downloads\Android to go to the "D:\Downloads\Android" folder. If your path contains spaces (intervals) type it in quotes.
The command "cd.." brings you one folder back
Click to expand...
Click to collapse
Nice work mate
Thanks a lot for the guide, dude!
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Hope it helps!
jamsh said:
Instructions for Linux users???
Click to expand...
Click to collapse
OP edited - there is a link to a guide for Linux users
fonpacific said:
Thanks a lot for the guide, dude!
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Hope it helps!
Click to expand...
Click to collapse
Thank you for the remark, I hope it will help the users with the same problem
Hey Guys, I need help!
after an installation of adb all I get is error:device not found
i entered a code adb shell and hit enter, than i entered
dmesg | grep mmc0, since you cannot put two lines of code at once (I'm a rookie)..
where did I put it wrong?
I can get to recovery of my device, but I get error like:
/I]E:Can't open /cache/recovery/command
I made revolutionary S-OFF..
Thanx for a help!
Rocks
You have to enable USB debugging in the settings.
And while in recovery it should work too
Sent from my HTC Desire S
I have a LG Thrill 4G. I rooted the phone using superonelick, root checker says it is rooted. Downloaded ROM Manger and flashed clockworkmod. I cannot click boot into recovery, it just restarts the phone. I have tried to reboot into recovery by pressing 3d button, down volume, and power and it boots me into the android recovery but not clockworkmod, so I can not find anyway in to download the new rom from the zip file. Has had any other people had trouble with this? I have spent over 2 days searching the internet but I cannot find any similar problems, is there anyway to get into the recovery mode to install the new ROM without it just restarting the phone?
LG Thrill 4G ClockworkMod Installation (correct method)
1) You need to have ROOT access at the least (see link below)
It will also be good to have ADB (and hence LG Thrill drivers) installed properly
http://forum.pandaapp.com/thread/2/11/20110919/4e77f603d22632913-1.html
2) Get the recovery image from here and keep it on your PC in a folder accessible by ADB.
OR (if no ADB then) directly put it on your LG Thrill SDCard root
http://forum.xda-developers.com/showthread.php?t=1257588
4) If you have ADB then follow the instructions in the first link above to push the recovery image to your phone.
OR
if no ADB then open Terminal Emulator (install it from Market) and type su and click allow if the prompt comes up
5) Now you can follow instructions in the first link (far above) again, starting from the 'dd if=...' step. But instead of rebooting you could just power off
6) Clockwork recovery should now be flashed. To enter recovery, keep the 3D button, Vol-down and Power button pressed until you see the LG logo
Thank you for getting back with me. I tried to follow these steps and when I am in the Terminal Emulator and type adb push recovery.img /data it comes back with adb: not found. I have redownloaded the recovery file that you have attached to the SD card, same error, and then I tried to copy to the phone itself and same error. I can do any of the other prompts for the emulator but nothing that has to do with the recovery file it will not work. I am guessing maybe this is the problem because if it cannot find the recovery file, I cant do much of anything else. Do you have any suggestions of why the file still cannot be found on my phone?
connect adb through tcp
Try this:
1. If you are using terminal emulator to access adb then try downloading the app called remote adb. This tool will allow you to connect your device via tcp. Take note of the ip adress and port number. Usually the default port is fine.
2. Now open sshdroid, connectbot, terminal emulator and start an ssh session with the adb shell. You must have the correct public ip and port entered in to access the adb via tcp.
3. Once you have made the ssh connection between what ever emulator you are using and remote adb, start a shell as su.
4. Type the commands mentioned earlier.
This should let you run the whole thing from within your phone.
Alternatively...
1. start remote adb on your device.
2. start a terminal or cmd prompt on your cpu.
3. cd to androidSDK\platform-tools
4. type ---> adb start-server
The server then sets up connections to all running emulator/device instances. It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. Where the server finds an adb daemon, it sets up a connection to that port.
Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections. For example:
Emulator 1, console: 5554
Emulator 1, adb: 5555
Emulator 2, console: 5556
Emulator 2, adb: 5557 ...
As shown, the emulator instance connected to adb on port 5555 is the same as the instance whose console listens on port 5554.
Once the server has set up connections to all emulator instances, you can use adb commands to control and access those instances. Because the server manages connections to emulator/device instances and handles commands from multiple adb clients, you can control any emulator/device instance from any client (or from a script).
5. type --> adb forward tcp:5554 tcp:5555
5. type ---> adb devices. In response, adb prints this status information for your device. If there is no emulator/device running, adb returns no device, and you have not made a tcp connection.
6. Take note of the serial number listed. You will use it later to direct commands to device.
7. Type --> adb shell
8. Type --> su
9. Use commands from other post to achieve whatever you need.
10. once finished with shell, type --> exit twice to leave the shell
11. Finally, type --> adb server-kill
Hope that helps. Seems like you were having issues making the connection from device to adb, so that is what I focused on. If I can help anymore, just ask. We are all continually learning and the only stupid question is the one never asked.
B^)
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.
There are servel cmds which we can use
But I post only top 10 cmds to help that ones who need
###############
If I make a mistake so please reply with your suggestions
And if you want a cmd in the list .submit your reply with cmd and features ( full detail as you know.).
########cmds###########
For a lot of us, the fact that we can plug our Android phone or tablet into our computer and interact with it is a big plus. Besides the times when we've broken something and need to fix it, there are plenty of reasons why an advanced Android user would want to talk to his or her device. To do that, you need to have a few tools and know a few commands. That's what we're going to talk about today. Granted, this won't be the end-all be-all discussion of adb commands, but there are 10 basic commands everyone should know if they plan to get down and dirty with the command line.
The tools are easy. If you're a Mac or Linux user, you'll want to install the SDK as explained at the Android developers site. It's not hard, and you don't have the whole driver mess that Windows users do. Follow the directions and get things set up while I talk to the Windows using folks for a minute.
If you're using Windows, things are easier and harder at the same time. The tools themselves are the easy part. Download this file. Open the zip file and you'll see a folder named android-tools. Drag that folder somewhere easy to get to. Next, visit the manufacturers page for your device and install the adb and fastboot drivers for Windows. You'll need this so that your computer can talk to your Android device. If you hit a snag, visit the forums and somebody is bound to be able to help you through it.
Now that we're all on the same page, enable USB debugging on your device (see your devices manual if you need help finding it, and remember it was hidden in Android 4.2), and plug it in to your computer. Now skip past the break and let's begin!
1. The adb devices command
The adb devices command is the most important one of the bunch, as it's what is used to make sure your computer and Android device are communicating. That's why we're covering it first.
If you're a pro at the operating system on your computer, you'll want to add the directory with the Android tools to your path. If you're not, no worries. Just start up your terminal or command console and point it at the folder with the tools in it. This will be the file you downloaded earlier if you use Windows, or the platform-tools folder in the fully installed Android SDK. Windows users have another easy shortcut here, and can simply Shift + right click on the folder itself to open a console in the right spot. Mac and Linux users need to navigate there once the terminal is open, or install an extension for your file manager to do the same right click magic that's in Windows by default.
Once you're sure that you are in the right folder, type "adb devices" (without the quotes) at the command prompt. If you get a serial number, you're good to go! If you don't, make sure you're in the right folder and that you have the device driver installed correctly if you're using Windows. And be sure you have USB debugging turned on!
Now that we have everything set up, let's look at a few more commands.
2. The adb push command
If you want to move a file onto your Android device programmatically, you want to use the adb push command. You'll need to know a few parameters, namely the full path of the file you're pushing, and the full path to where you want to put it. Let's practice by placing a short video (in my case it's a poorly done cover of the Rick James tune Superfreak) into the Movies folder on your device storage.
I copied the superfreak.mp4 file into the android-tools folder so I didn't need to type out a long path to my desktop. I suggest you do the same. I jumped back to the command line and typed "adb push superfreak.mp4 /sdcard/Movies/" and the file copied itself to my Nexus 4, right in the Movies folder. If I hadn't dropped the file into my tools folder, I would have had to specify the full path to it -- something like C:\Users\Jerry\Desktop\superfreak.mp4. Either way works, but it's always easier to just drop the file into your tools folder and save the typing.
3. The adb pull command
If adb push sends files to your Android device, it stands to reason the adb pull command gets them out. That's exactly what it does, and it works the same way as the adb push command did. You need to know both the path of the file you want to pull off, as well as the path you want it placed into. You can leave the destination path blank and it will drop the file into your tools folder to make things easy.
In this example, I did it the hard way so you can see what it looks like. The path of the file on the device is "/sdcard/Movies/superfreak.mp4" and I put it on my Windows 8 desktop at "C:\Users\Jerry\Desktop". Again, the easy way it to just let it drop into your tools folder by not giving a destination, which would have been "adb pull /sdcard/Movies/superfreak.mp4". Remember your forwards slash for the Android side, and you'll have no problems here.
5. The adb reboot-bootloader and adb reboot recovery commands
Not only can you reboot your device, you can specify that it reboots to the bootloader. This is awfully handy, as sometimes those button combos are touchy, and if you have a lot of devices you can never remember them all. Some devices (the LG Optimus Black comes to mind) don't even a way to boot to the bootloader without this command. And once again, being able to use this command in a script is priceless. Doing it is easy, just type "adb reboot-bootloader" and hit the enter key.
Most devices can also boot to the recovery directly with the "adb reboot recovery" (note there is no hyphen in this one) and some can't. It won't hurt anything to try, and if yours can't nothing will happen.
6. The fastboot devices command
When you're working in the bootloader, adb no longer works. You're not yet booted into Android, and the debugging tools aren't active to communicate with. We use the fastboot command in it's place.
Fastboot is probably the most powerful tool available, and many devices don't have it enabled. If you're does, you need to be sure things are communicating. That's where the fastboot devices command comes into play. At the prompt, just type in "fastboot devices" and you should see a serial number, just like the adb devices command we looked at earlier.
If things aren't working and you are using Windows, you likely have a driver issue. Hit those forums for the answer.
7. The fastboot oem unlock command
The holy grail of Android commands, fastboot oem unlock does one thing, and one thing only -- unlocks your Nexus device (or an HTC device using their official tool). If you're using a phone from a different manufacturer, you have a different method of unlocking things -- maybe with ODIN or .sbf files -- and this won't apply to you. We're including it because even if you don't need it, it's an important part of Android's openness. Google doesn't care what we do with phones or tablets that we've bought, and include this easy way to crack them open. That's something you usually don't see from any tech company, and a big part of the reason why many of us choose Android.
Using it is easy enough. Once you've used fastboot devices to make sure everything is communicating, just type "fastboot oem unlock" at the prompt and hit enter. Look at your device, read carefully, and choose wisely.
Protip: Using "fastboot oem unlock" will erase everything on your device
8. The adb shell command
The adb shell command confuses a lot of folks. There are two ways to use it, one where you send a command to the device to run in its own command line shell, and one where you actually enter the device's command shell from your terminal. In the image above, I'm inside the device shell, listing the flies and folders on the device. Getting there is easy enough, just type "adb shell" and enter. Once inside, you can escalate yourself to root if you need to. I'll warn you, unless you're familiar with an ash or bash shell, you need to be careful here -- especially if you're root. Things can turn south quickly if you're not careful. If you're not familiar, ash and bash are command shells that a lot of folks use on their Linux or Mac computers. It's nothing like DOS.
The other method of using the adb shell command is in conjunction with one of those Ash commands your Android device can run. You'll often use it for more advanced tasks like changing permissions of files or folders, or running a script. Using it is easy -- "adb shell <command>". An example would be changing permissions on a file like so: "adb shell chmod 666 /data/somefile". As mentioned, be very careful running direct commands using these methods.
9. The adb install command
While adb push can copy files to our Android devices, adb install can actually install .apk files. Using it is similar to use the push command, because we need to provide the path to the file we're installing. That means it's always easier to just drop the app you're installing into your tools folder. Once you've got that path, you tell your device to sideload it like this: "adb install TheAppName.apk".
If you're updating an app, you use the -r switch: "adb install -r TheAppName.apk". There is also a -s switch which tries to install on the SD card if your ROM supports it, and the -l switch will forward lock the app (install it to /data/app-private). there are also some very advanced encryption switches, but those are best left for another article.
And finally, you can uninstall apps by their package name with "adb uninstall TheAppName.apk". Uninstall has a switch, too. The -k switch will uninstall the app but leave all the app data and cache in place.
10. The adb logcat command
The adb logcat command is one of the most useful commands for some folks, but just prints a bunch of gibberish unless you understand what you're seeing. It returns the events written to the various logs in the running Android system, providing invaluable information for app developers and system debuggers. Most of us will only run this one when asked by one of those developers, but it's very important that we know how to use it correctly.
To see the log output on your computer screen, just type "adb logcat" and hit enter. Things can scroll by pretty fast, and chances are you won't find what you're looking for. There are two ways to handle this one -- filters, or text output.
You also have to specify the cmds properly.
Hope it help you .
Like my work hit thanks button.
$$$$$$$$$$$$$$$$$$$$$$$$
Any suggestions most welcome.
$$$$$$$$$$$$$$$$$$$$$$$$$
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