Related
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.
NON ROOTED PHONE
I am trying to create to backup of all application in android but I don't want the users to connect to USB even for the first time.
okay let me first explain what happens when we connect our phone with USB to ADB client
0. USB Debugging mode is enabled in the phone.
1. The phone is connected to PC using a USB cord.
2. We run
Code:
adb tcpip 9999
command from cmd with ADB already installed.
The above command helps now switched the abd demon (adbd) inside the android phone to listen through TCP-IP protocol
3. now we can disconnect the phone from the PC
4. using a terminal emulator application we can now fire the commands
a)
Code:
adb connect localhost:999
b)
Code:
backup -all -f /sdcard/dev/bck.ab
now a backup pop-up will open up, you can simply click backup button.
Now we can anytime execute the command in 4.a and 4.b util the user restarts the phone or
but the problem is I wish to execute
Code:
adb tcpip 9999
without PC. Can someone suggest me how to approach this problem. From where should I start reading or there is some existing application that can do this on a non-root phone.
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
To make this a short as possible I successfully unlocked my Motorola G7 power using an Android device rather than a PC I need help rooting my G7 power with magisk using my designated Android device rather than a PC
ADB⚡OTG - Android Debug Bridge - Apps on Google Play
⚡ Run ADB commands without a computer [No Need ROOT] ⚡
play.google.com
Thank you I appreciate your reply but I use another application for this purpose bugjaeger premium
@Sativa33
Either in magisk manager from device or you can also get the magisk module from Osm0sis' Odds and Ends- (multiple devices scripts) XDA thread. If you go there https://forum.xda-developers.com/t/...-and-ends-multiple-devices-platforms.2239421/
Scroll down halfway oe maybe 2/3 of fge way and click his "adb and fastboot " magisk module and install via magisk manager. Then use termux terminal and type "su" (enter) for root and place files you wish to install in ter
Termux's directory which it will show you after you tape sy and push enter on the screen in terminal just after you grant it root. Then you use an otg cable and connect two Android devices together throw files in Termux's directory and send fastboot and adb commands whenever. I've used this method on two phones so unlock my bootloader ad well. The only prerequisite being you need another (2nd) Android device that is bporloader unlocked and rooted so you can send commands to other device and an OTG cable which are $3-5 USD online. Sure does come in handy when you need it through. Like years ago when my laptop was stollen!! Life saver FR!!!
After reading it that sounds like a reasonable option. But wouldn't it be easier just to download the bugjaeger premium app on a second Android device. And that's basically all you need and a double ended USB c cord. No need for all this other programs or downloades . It's basically running fast boot commands it's purest form one Android device talking to the other using the same language no need to download packets drivers nothing because you're already in the Android shell talking to another Android