On an Asus Zenpad 3s 10 Z500KL tablet, RU Unistaller Pro has been wrongly used to freeze an app named "ZenUI Launcher". After restart, only notification bar and Settings work. I need to run RU Unistaller Pro to defrost "ZenUI Launcher".
How can I run RU Unistaller Pro in this situation (via ADB, or any other solution)?
Or if you have any other solution, please guide me.
Sincere thanks in advance
Dr.Ghobar
Dr.Ghobar said:
On an Asus Zenpad 3s 10 Z500KL tablet, RU Unistaller Pro has been wrongly used to freeze an app named "ZenUI Launcher". After restart, only notification bar and Settings work. I need to run RU Unistaller Pro to defrost "ZenUI Launcher".
How can I run RU Unistaller Pro in this situation (via ADB, or any other solution)?
Or if you have any other solution, please guide me.
Sincere thanks in advance
Dr.Ghobar
Click to expand...
Click to collapse
This is not so complicated.
1. Enter Settings.
2. Go to Google.
3. Choose the three dots from the top right corner.
4. Select “Help and Feedback”.
5. Choose the three dots from the top right corner.
6. Choose “View in Google Play Store”.
7. Search for RU Uninstaller Pro.
8. Just start RU Uninstaller Pro from there.
HippoInWindow said:
This is not so complicated.
1. Enter Settings.
2. Go to Google.
3. Choose the three dots from the top right corner.
4. Select “Help and Feedback”.
5. Choose the three dots from the top right corner.
6. Choose “View in Google Play Store”.
7. Search for RU Uninstaller Pro.
8. Just start RU Uninstaller Pro from there.
Click to expand...
Click to collapse
Thank you very much.
I will try it and report back.
HippoInWindow said:
This is not so complicated.
1. Enter Settings.
2. Go to Google.
3. Choose the three dots from the top right corner.
4. Select “Help and Feedback”.
5. Choose the three dots from the top right corner.
6. Choose “View in Google Play Store”.
7. Search for RU Uninstaller Pro.
8. Just start RU Uninstaller Pro from there.
Click to expand...
Click to collapse
In the tablet, when I click on “View in Google Play Store”, Google Play page opens but in a normal web page not in mobile mode. I searched for RU Uninstaller. It was found. How should I "start" it from there?
HippoInWindow said:
This is not so complicated.
1. Enter Settings.
2. Go to Google.
3. Choose the three dots from the top right corner.
4. Select “Help and Feedback”.
5. Choose the three dots from the top right corner.
6. Choose “View in Google Play Store”.
7. Search for RU Uninstaller Pro.
8. Just start RU Uninstaller Pro from there.
Click to expand...
Click to collapse
In the tablet, when I click on “View in Google Play Store”, Google Play page opens but in a normal web page not in mobile mode. I searched for RU Uninstaller. It was found. There is an "OPEN IN PLAY STORE APP" at the bottom of the page. When I click on it, another page opens (https://goo.gl/app...) and says: "404. That's an error. The requested URL was not found on this server. That's all we know."
So, how should I "start" it from there?
Dr.Ghobar said:
In the tablet, when I click on “View in Google Play Store”, Google Play page opens but in a normal web page not in mobile mode. I searched for RU Uninstaller. It was found. There is an "OPEN IN PLAY STORE APP" at the bottom of the page. When I click on it, another page opens (https://goo.gl/app...) and says: "404. That's an error. The requested URL was not found on this server. That's all we know."
So, how should I "start" it from there?
Click to expand...
Click to collapse
Maybe try googling like the google app on your browser, then it might open Google Play store without issues.
Dr.Ghobar said:
Thank you very much.
I will try it and report back.
Click to expand...
Click to collapse
Try this.
https://stackoverflow.com/questions/4567904/how-to-start-an-application-using-android-adb-tools
You can also use a terminal emulator app or the terminal emulator that is built into TWRP to run adb shell commands(adb shell, not regular adb). Terminal emulator and adb shell are virtually the same thing, they both use the same commands, just remove the "adb" or "adb shell" part from the commands.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try this.
https://stackoverflow.com/questions/4567904/how-to-start-an-application-using-android-adb-tools
You can also use a terminal emulator app or the terminal emulator that is built into TWRP to run adb shell commands(adb shell, not regular adb). Terminal emulator and adb shell are virtually the same thing, they both use the same commands, just remove the "adb" or "adb shell" part from the commands.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
1. Before posting this thread, I had seen the link you mentioned. I could not figure out how to use it to solve my problem.
2. can you explain how to use your own suggestion about "terminal emulator app"? (as far as I know, there is no TWRP for this tablet.)
Dr.Ghobar said:
1. Before posting this thread, I had seen the link you mentioned. I could not figure out how to use it to solve my problem.
2. can you explain how to use your own suggestion about "terminal emulator app"? (as far as I know, there is no TWRP for this tablet.)
Click to expand...
Click to collapse
You don't have TWRP but do you have root? If your device isn't rooted, terminal emulator won't work.
If you are rooted, install the Terminal Emulator app, open terminal emulator(grant superuser permission when promoted), then type:
su (then press enter)
Then type the am command as described in the link, just change the command to input the name of the actual apk file associated to the app that you want to start, you have to know the actual name of the app package instead of the name of the app as it appears in app drawer or homescreen. I don't know the actual package name of the app(s) you want to start so you will have to figure out the exact command for yourself.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You don't have TWRP but do you have root? If your device isn't rooted, terminal emulator won't work.
If you are rooted, install the Terminal Emulator app, open terminal emulator(grant superuser permission when promoted), then type:
su (then press enter)
Then type the am command as described in the link, just change the command to input the name of the actual apk file associated to the app that you want to start, you have to know the actual name of the app package instead of the name of the app as it appears in app drawer or homescreen. I don't know the actual package name of the app(s) you want to start so if you will have to figure out the exact command for yourself.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I do not have root. as far as I know, zenpad z500kl has not been rooted by now.
Dr.Ghobar said:
I do not have root. as far as I know, zenpad z500kl has not been rooted by now.
Click to expand...
Click to collapse
Ok without root, you need to add --user 0 to the am command and you wouldn't have to type the "su" command first before typing the am command, you just type the am command.
So you would add it to the command as follows:
am start --user 0 (then the rest of the command including the proper package name for the app you desire to start)
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ok without root, you need to add --user 0 to the am command and you wouldn't have to type the "su" command first before typing the am command, you just type the am command.
So you would add it to the command as follows:
am start --user 0 (then the rest of the command including the proper package name for the app you desire to start)
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I shall try it.
Dr.Ghobar said:
I shall try it.
Click to expand...
Click to collapse
If terminal emulator doesn't work, install "adb/fastboot 15 second installer" on your PC, then open a terminal on PC, connect your device to PC while the phone is booted into system as you would normally use the device, then type:
adb devices (press enter, if it returns a serial number you're connected)
Then type:
adb shell (press enter)
This will put you in adb shell to run shell commands
Then type:
adb shell (along with the rest of your am command with --user 0 and your app package name)
Hopefully, that works for you.
Sent from my LGL84VL using Tapatalk
Dr.Ghobar said:
I shall try it.
Click to expand...
Click to collapse
If Terminal Emulator works for you without root, you can create a script as a batch file (.bat file, select "file" in note editor, then "save as", then "all files", name the file "whateveryouwant.bat) using a note editor on PC with the commands contained in order in the file. Move the created file to your device and store it in the root of your internal sdcard, then run the script by opening Terminal Emulator and typing the command to run your batch file script whenever you want, this can automate the process somewhat.
Sent from my LGL84VL using Tapatalk
Related
Hello iam using windows vista and xp and I had the same.problems on both. I downloaded the ADB program which gave me 5 seperate files. and downloaded thedrivers for my moto Atrix. But I was told not to run the adb.exe but to look for a run command line prompt. Where and how do I find this. And where do I go to run the commands?
Sent from my MB860 using XDA App
RPK925 said:
Hello iam using windows vista and xp and I had the same.problems on both. I downloaded the ADB program which gave me 5 seperate files. and downloaded thedrivers for my moto Atrix. But I was told not to run the adb.exe but to look for a run command line prompt. Where and how do I find this. And where do I go to run the commands?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hey
press the start button (bottom left), on start menu you should see "run" with a small icon looks like a dialogue box (might be below search), press this. in the dialogue pop up type CMD.
Tho you will prob need to set up Environment Variables before you can use ADB.
kam333 said:
Hey
press the start button (bottom left), on start menu you should see "run" with a small icon looks like a dialogue box (might be below search), press this. in the dialogue pop up type CMD.
Tho you will prob need to set up Environment Variables before you can use ADB.
Click to expand...
Click to collapse
Then you have to go to folder where "adb.exe" is...
For example if you have it in "c:\adb_folder" you have to type "cd adb_folder".......
Then your command line will be like this → C:\adb_folder>
Then, if you want to test if your device is connected properly you have to type "adb devices" and you will see your device listed....
If not, there is a problem.....
(don't forget to enable "USB debugging" at your phone through Applications→Development)
I
pigeonaras said:
Then you have to where "adb.exe" is...
For example if you have it in "c:\adb_folder" you have to type "cd adb_folder".......
Then your command line line will be like this → C:\adb_folder>
Then, if you want to test if your device is connected properly you have to type "adb devices" and you will see your device listed....
If not, there is a problem.....
(don't forget to enable "USB debugging" at your phone through Applications→Development)
Click to expand...
Click to collapse
I was.able.to open up the command.prompt, but when I run adb devices it just says "adb is not a recgonized as an internal or external....." . It is.like its not connecting for somereason ? Iam a complete noon so any help would be great. Thanks
Sent from my MB860 using XDA App
pigeonaras said:
(don't forget to enable "USB debugging" at your phone through Applications→Development)
Click to expand...
Click to collapse
Have you done this .....??????
RPK925 said:
I
I was.able.to open up the command.prompt, but when I run adb devices it just says "adb is not a recgonized as an internal or external....." . It is.like its not connecting for somereason ? Iam a complete noon so any help would be great. Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Before you can use adb command, you have to direct the terminal to the location of the folder where adb is located.
If the location of the file adb is at C:\\windows\androidsdktools\tools\adb
In your terminal type
cd \
Press enter, then type,
cd windows\androidsdktools\tools
Now the terminal should be in the folder where adb is located.
adb devices
A better way in my opinion to use adb is to set the path so it is usable from anywhere, simple easy and no need to always cd the path
directly quoted from dreamsforgotten's tutorial on theming for the epic
http://forum.xda-developers.com/showthread.php?t=821638
"On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path."
Click to expand...
Click to collapse
tmspyder said:
A better way in my opinion to use adb is to set the path so it is usable from anywhere, simple easy and no need to always cd the path
directly quoted from dreamsforgotten's tutorial on theming for the epic
http://forum.xda-developers.com/showthread.php?t=821638
Click to expand...
Click to collapse
This Works!
install adb driver first£¬turn your phone in ¡°charge only mode¡±£¬then find the adb floder£¬hold ¡°shift¡±and right click the floder.choose ¡°run in cmd line mode¡±£¬yeah£¬you done it
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
Description
After always having to search for the latest versions of Android's ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.
You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.
This installer is 32-bit and 64-bit compatible.
Usage
The default installation path is C:\ADB so you can easily add your flashable files in there.
After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don't need to change paths. Keep in mind that you need admin privileges, though.
To open a command prompt with administrator rights on Windows 8, just right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Command Prompt (Admin).
Click to expand...
Click to collapse
If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.
Click to expand...
Click to collapse
Requisites
You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.
You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.
Click to expand...
Click to collapse
Download
I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.
The download link and screenshots are on my website.
http://rubenalamina.mx/custom-installers/android-adb-fastboot/
Latest version of the installer: 1.5 (ADB 1.0.36) updated on 2016.09.21
Thanks mate, it really help people with lacks internet connection like mine
Sent from my WT19i using xda app-developers app
Installer updated to version 1.2 with the new ADB and Fastboot included in Android SDK 23.0.2.
Installer updated to version 1.3 based on the Android SDK 24.0.2.
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Nightmare-Rex420 said:
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Click to expand...
Click to collapse
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
ajua said:
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
Click to expand...
Click to collapse
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Nightmare-Rex420 said:
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Click to expand...
Click to collapse
Try using PowerShell. Also, see if you are able to run the ADB that comes with the SDK but run it from the folder where it is located.
===============================================================================
TUTORIAL REVISED AND WRITTEN BY @parcek
===============================================================================
FURTHER UPDATED FOR ROOTING NOOBS: 10 Steps
Two Methods: Windows and Linux
Originally posted by @brad2192: https://forum.xda-developers.com/android/development/lg-aristo-2-root-t3746425
Credit to @tecknight for updated files: https://forum.xda-developers.com/showpost.php?p=76837384&postcount=2
@brad2192: Updated Tutorial due to people using TWRP (the original tutorial was released before TWRP was released for this device)
1) Backup all apps and data using LG Backup phone apps
2) Enable USB debugging and Unlock OEM. There are two methods in which you will to accomplish this:
First Method: Smartphone GUI
A) On your Lg Aristo 2 Smartphone go into General Tab (If in Tab View), If in list view, scroll down towards System section
"System Settings > About Phone > Software Information > Click on "Build Number" 10 times.
Now go to "System Settings > About Phone > Developer Options > Enable OEM unlock."
and also "System Settings > About Phone > Developer Options > Enable USB debugging."
Second Method: Windows Command Prompt or Linux Terminal:
Windows:
B) Click and drag "adb" file into command prompt and type "reboot bootloader" after it. Press enter.
Click and drag "fastboot" file into command prompt and type "flashing unlock" after it. Press enter.
Linux:
C)Type in your terminal "adb reboot bootloader" and press enter.
Type in your terminal "fastboot flashing unlock."
NOTE: Below has the information which will teach you how to download ADB and FASTBOOT.
3) Download the following:
Updated - TWRP
Updated - Magisk
(Add this file into your phone's SD Card.)
Updated - boot image
Update: Windows:
B)This is how you download ADB and FASTBOOT for Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
4) Open Command Prompt. Then click and drag the adb file (from the latter download link a.k.a platform-tools) into command prompt then press space and type "reboot bootloader" after and then press enter OR power down phone and hold volume down while plugging in USB)
5) Open Command Prompt. Then click and drag the fastboot file (from the latter download link a.k.a platform-tools) into command prompt and then type "flash recovery" after it and then click and drag "newtwrp.img" into command prompt and press enter.)
6) Open Command Prompt. Then click and drag fastboot (from the latter download link a.k.a platform-tools) into command prompt and then type "flash boot" after it and then click and drag "bootimglistedabove.img" into the command prompt after and then press enter) then follow step 7).
Update: Linux:
C) Depending on kernel, for this sake we will use a debian based kernal.
This is how you download ADB and FASTBOOT for Linux: Open terminal and type: "Sudo apt-get install adb && sudo apt-get install fastboot"
4) Open terminal and type: adb reboot bootloader
5) Open terminal and type: fastboot flash recovery (and then click and drag newtwrp.img onto the terminal) and hit enter
6) Open terminal and type: fastboot flash boot (and then click and drag bootfilelistedabove.img onto the terminal) and hit enter
This applies towards both Windows and Linux: continuation after their last listed step written above.
Step 7) Remove battery from phone, in order to force a shut down.
8) Boot into Recovery-TWRP Mode.
How to boot into LG Aristo 2 TWRP Recovery:
a) The phone is off.
b) Hold the volume key and power key at the same time.
c) When the LG logo appears, let go of the power key (while still holding the volume down key) and then click and hold the power key once again.
d)You will be prompted to LG Aristo 2's stock recovery mode asking you if you are sure you would like to delete ur phone.
e) Go to the option "yes" and enter.
f) It will then warn you that can remove all data from your phone.
g) Go to the option "yes" and enter.
You will be in TWRP after this.
TWRP Mode:
9) In TWRP go to "Wipe > Format Data" and then type "yes" and confirm it. (Do not hit reboot, click back a few time and hit reboot > recovery)
10) In TWRP go to "Install > Select Storage" and select your SD Card. Then look for where you placed the "magisk" zip file. Install it.
Your phone is now rooted.
On TWRP menu: Reboot.
Restore your phone if you created an LG backup of your important files (like lets say contacts or applications).
-----------------------------------------------
If any mistakes were made and you phone becomes locked, here is how to go into download mode to repair your LG Aristo 2 into its default stock rom. Credit to @tecknight: https://forum.xda-developers.com/showpost.php?p=76837800&postcount=4
1) Power off phone.
2) connect usb to Lg Aristo 2 phone (without connecting the usb into the PC or laptop)
3) Hold volume up key and then connect USB into computer
4) download LG Bridge
5) detect phone
6) click on "Update Error Recovery"
Your LG Aristo 2 will be repaired and factory resetted.
-------------------------------------------------------------
What root means: In terms of PC language, Root means the superuser that has privileges to Add, Modify, and or Delete any kind of system files without prevention. Pretty much, it's like the actual Administrator account on a PC. Natively, whenever we buy a phone, it is as if to say, we are only using a guest account. Since the android OS is basically a Linux based computer (correct me if i am wrong) we can do anything we like... You want iOS emoji's on an android? A custom boot animation? Having root privileges allows you to go beyond your guest user restrictions because you then become the Admin.
Explaining the function of the provided Magisk app: It allows root privileges for programs intended for rooted phones.
There are other popular programs alternative of Magisk app, such as the SuperSU app: http://www.mediafire.com/file/2dljobq6yw93w76/UPDATE-SuperSU-v2.82-20170528234214.zip
--------------------------------
After being officially done setting up your rooted phone, make sure you disable OEM Unlock to avoid seeing the caution message before every boot.
--------------------------
How to backup your phone.
Also, using ADB, backup your phone.
Windows: Click and drag ADB file onto command prompt and paste " backup -apk -shared -all -f "C:\Users\UserName\Desktop\backupfilename.ab" "
Linux: Open terminal and type " adb backup -apk -shared -all -f "C:\Users\UserName\Desktop\backupfilename.ab" "
Update: For those who are encountering "Now unlock your phone and confirm operation" when typing the latter code, there is an alternative and much more easier and safer way to backup your phone.
Boot into TWRP and click on "backup" and then select what you would like to back up and then swipe to confirm the operation.
-----------------------------------------------------------------
Confirmed Successful rooting for LG Aristo 2 - June 2018
Thank You Brad and Tec!
Salam Aleykom.
You are a lifesaver my friend
Senorhamburgler said:
You are a lifesaver my friend
Click to expand...
Click to collapse
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
tribal1209 said:
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
Click to expand...
Click to collapse
Until there is a custom recovery built, we won't have custom roms. Dont wipe out every metro app. Anything you arent sure about, look up, or just freeze the app and test results. My phone is fine except SuperSU wont work properly due to the binary being occupied, but this is the best we have so far. I debloated no problem.
tribal1209 said:
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
Click to expand...
Click to collapse
Senorhamburgler said:
Until there is a custom recovery built, we won't have custom roms. Dont wipe out every metro app. Anything you arent sure about, look up, or just freeze the app and test results. My phone is fine except SuperSU wont work properly due to the binary being occupied, but this is the best we have so far. I debloated no problem.
Click to expand...
Click to collapse
Root is the only thing needed, not a custom recovery. Apps like Magisk Manager can flash custom images. The reason there is no ROMs built for this device, I can tell you in my opinion there is no need for a Custom ROM. Magisk Manager has plenty of customizations available as well as many other root apps. Basically, custom recoveries are obsolete, it is not needed for gaining root access nor flashing files. Magisk can do it as well as Flashfire.
I need help.... Abd is not functioning it states "the term abd is not recognised as the nane of a cmdlet, function, scrip file of operable program."
Does not exist in current location.... Windows PowerShell does not load conmands by default...
MinaSaotome said:
I need help.... Abd is not functioning it states "the term abd is not recognised as the nane of a cmdlet, function, scrip file of operable program."
Does not exist in current location.... Windows PowerShell does not load conmands by default...
Click to expand...
Click to collapse
Hey man, I would press the Windows Key+R and type" "cmd"
Then, as long as your adb is located at C:\adb type: "cd C:\adb"
Then use adb, I hate how Windows 10 forces it on users!
Hey, I am so sorry to bother you but when I enter in the fourth step of your tutorial, it tells me "flash boot" command doesn't exist. Is there something I'm doing wrong?
---------- Post added at 01:15 AM ---------- Previous post was at 01:01 AM ----------
4btn said:
Hey, I am so sorry to bother you but when I enter in the fourth step of your tutorial, it tells me "flash boot" command doesn't exist. Is there something I'm doing wrong?
Click to expand...
Click to collapse
Okay, after messing around with it a few, I found that once it goes off into fastboot... my computer can't recognize it anymore?
brad2192 said:
Hey guys, spent a few hours figuring out how to root. Pretty Simple!
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
For those skeptical, proof of root here.
X-210 Stock .KDZ Backup HERE (Should not be needed.)
Click to expand...
Click to collapse
Do I need to unlock the bootloader first? I have it rebooted into fastboot and it's giving me instructions to do that, but won't let me push the boot image. If I do need to unlock it, does it wipe my device?
tge101 said:
Do I need to unlock the bootloader first? I have it rebooted into fastboot and it's giving me instructions to do that, but won't let me push the boot image. If I do need to unlock it, does it wipe my device?
Click to expand...
Click to collapse
Yes, that is what OEM unlock means. In doing so you do need to unlock the bootloader.
brad2192 said:
Yes, that is what OEM unlock means. In doing so you do need to unlock the bootloader.
Click to expand...
Click to collapse
Just wanted to make sure but does it wipe it?
tge101 said:
Just wanted to make sure but does it wipe it?
Click to expand...
Click to collapse
Yes, when you use "fastboot oem unlock" it unfortunately erases all data. One of our forum members is working on a TWRP at the moment that might be available today. You could wait to do this so you can create a backup.
brad2192 said:
Yes, when you use "fastboot oem unlock" it unfortunately erases all data. One of our forum members is working on a TWRP at the moment that might be available today. You could wait to do this so you can create a backup.
Click to expand...
Click to collapse
That'd be cool. But, wouldn't the bootloader still need to be unlocked for me to flash TWRP?
tge101 said:
That'd be cool. But, wouldn't the bootloader still need to be unlocked for me to flash TWRP?
Click to expand...
Click to collapse
I'm an idiot, yes LOL. Sorry, just got to work and I am tired you are correct. So, if you would like I suggest just using my tutorial. I believe there is ways of using LG backup to save most of your user data.
brad2192 said:
I'm an idiot, yes LOL. Sorry, just got to work and I am tired you are correct. So, if you would like I suggest just using my tutorial. I believe there is ways of using LG backup to save most of your user data.
Click to expand...
Click to collapse
All good, if I lose it I lose it. Is there a thread for the TWRP development?
I posted a test twrp on my blog for aristo 2
cannot open root_boot.img
hey maybe someone can help me out
previously already unlocked the bootloader on the phone so i skipped that step but i keep getting the error that it can not open root_boot.img
downloaded the file and moved into users/appdata/local/android/sdk/platform-tools
thats where adb.exe so i figured that is the adb folder maybe yes or no
could anyone help me out
greatly appreciate it
tge101 said:
All good, if I lose it I lose it. Is there a thread for the TWRP development?
Click to expand...
Click to collapse
Update: TWRP HERE
TJ-yesthelegend said:
hey maybe someone can help me out
previously already unlocked the bootloader on the phone so i skipped that step but i keep getting the error that it can not open root_boot.img
downloaded the file and moved into users/appdata/local/android/sdk/platform-tools
thats where adb.exe so i figured that is the adb folder maybe yes or no
could anyone help me out
greatly appreciate it
Click to expand...
Click to collapse
What are you typing into ADB to get that error?
Do you have to de-encrypt the phone for root? I am thinking of getting an Aristo2, currently using the MotoE4 (which I hate!), and rooting that requires de-encryption (I love encryption!). This is the MetroPCS version your talking about? Thank you...
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