Database Info

[Solution]Windows 8 - ADB/fastboot driver problem solved!!

Hello!!​
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that as well, it is, after all, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed. Again (-_-") ) (Note: These are the Sammy OEM drivers.)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check out Beatsleigher & M4gkman's Universal Android Toolkit, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
So, apparently, if you're using Windows 8 and/or USB 3.0 ports, Windows installs its crappy drivers, so you should check out this link, posted by the awesome @tommy_riley and try it out for yourselves! Don't forget to drop him a 'Thanks'!
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers <- Courtesy of @tommy_riley!
Wow. Over 40.000 clicks and downloads. I'm amazed at you guys!
It doesn't cost anything or hurt to hit that 'Thanks' button... Please be sure to hit it, it helps me out and also shows me what sort of content you want to see from me.
Do you like the effort I put into this? Then consider donating, by adding towards a new PC: http://www.gofundme.com/NewPC
With a new PC, I can create more one-click solutions and stuff and things!

Updates & other info!! (Reserved)
If you have a problem, I'll do it over TeamViewer, if you wish
Ok, here is some news, for you!
Well, according to some people, who have used this tutorial, Microsoft has done something new to their device driver signing.
I did not have note of this, as I was using Ubuntu most of the time and the laptop I was using broke, several weeks ago (It's gonna take me ages to get a new one, with which I can finally finish my ROM cooking..)
And Senior Member "purpler" has posted a link, which teaches you to turn device driver signing off, in the new bootloader, which Windows 8 is using/will be using, so; let's give him loads of thanks, for this!
here is his answer:
purpler said:
confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options
Click to expand...
Click to collapse
Many thanks to you, purpler!
Please, if you notice anymore changes, which interferes with this method, please let me know, how to solve the problem!
Every helpfull answer, with new solutions will be posted in this thread and thanked many times!
EDIT: If you don't want to donate, but still want to thank me, then use these links, instead of the links, in the tutorial.
Mod edit: No adfly links allowed.
4lex96 said:
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards
Click to expand...
Click to collapse
Senior member 4alex96 has experienced some problems, while using USB® 3.0 ports.
If you are also experiencing these problems, or you have found a solution to this, be sure to post in this thread or write to me via PM and I'll be sure to quote and write this, so others also get to know and are able to get the most out of there Androids!
Creating a new tool!
Hey guys, I'm going to be creating a new tool or two, which will allow you to install ADB and Fastboot directly to the system root and which will install the Google drivers to your C:\ drive.
These tools will be available for a small donation, and they will save you a lot of work, i.e. you will never have to type in "path=<Whereever the ADB files are>" but you can just debug on
If you want to have the program, hit the "Donate to Me" button on the left of this post and donate a small amount. Then in the donation, write me a message, saying what it's for and give me your XDA username and I'll PM you the download link.
(Minimum of 5€)
tommy_riley said:
For Windows 8, I was having an issue getting my phone to be recognized in bootloader mode on an ASUS laptop that only had USB 3.0 drivers, I followed the procedures at the below URL (luckily I had an INTEL chipset) and once I replaced my native Windows USB 3.0 drivers with the Intel USB 3.0 drivers, I was able to work around a lot of issues:
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
(I cant post HTTP links yet, but you should be able to plug the above into a browser to find the instructions...)
hope this helps!
Click to expand...
Click to collapse
You get that, guys? Go check out that website, and try it out for yourselves!

Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing

thisiswar951 said:
Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing
Click to expand...
Click to collapse
Ok, cool. I haven't been on my laptop, for a few days, so I wouldn't know, if MS has released any updates, yet...
I was thinking: WTF is he talking about? It's worked by so many people :O...
xD
LG familyguy59

confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options

Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!

hshen45 said:
Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!
Click to expand...
Click to collapse
You'll have to wait a moment, the system has to look for all the needed files, in the exe, and then needs to try to execute. If it then doesn't work, I'll upload an updated version, but as this seems to be working pretty much fine, I'll hesitate, not that the updated verison causes problems.
Anyways, I was running Win8 64x and it worked fine, just let the computer do it's work and it will work sooner or later, if nothing happens, even after waiting for 5-10 minutes, then try running it with administrative rights (Run as administrator).. Let me know if it works!

Doesn't work for me because I cant even see my S3 in the device manager.

leeznon said:
Doesn't work for me because I cant even see my S3 in the device manager.
Click to expand...
Click to collapse
Then try a different computer Doesn't mean that your S III is kaputt, does it?
If it then doesn't work, you've probably got dirt in the socket, or something else, like that.
And if you don't have dirt in the socket, then I don't know, whats wrong, but it'll definitely go over warranty

I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:

dalien26 said:
I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:
Click to expand...
Click to collapse
That's what the link in the first post is for. And you still need to follow the steps in the tutorial, otherwise it won't work properly.
I know the tutorial looks complex, but it isn't. You just need to read properly
LG familyguy59/Beatsleigher
EDIT: It's spelled "click"

help me to connect android in win 8
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.

netbook said:
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.
Click to expand...
Click to collapse
OK, I will be back, tomorrow. I'm currently at a friend's, so I will be back tomorrow. Send me an e-mail, when you're back, and I'll help you, right away!
LG familyguy59/Beatsleigher

familyguy59 said:
Hello!!​
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that aswell, it is, afterall, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed) (Thanks so much for 5k+ downloads!!)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
Thanks a ton for 6k+ views/downloads!! The thanks are also very much appreciated!!
9K+ views!!
15K+ views!!!
Click to expand...
Click to collapse
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!

llsiddhantll said:
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!
Click to expand...
Click to collapse
I'm always glad to help, dude
LG familyguy59/Beatsleigher

heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.

shaolinx said:
heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.
Click to expand...
Click to collapse
We're already aware of that (see post #2) but still thanks for briefing everyone again.
LG familyguy59/Beatsleigher
Cyanogenmodded very skankily via XDA app. Skanky, indeed

Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!

4lex96 said:
Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!
Click to expand...
Click to collapse
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher

familyguy59 said:
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards

[Guide] How to Root LG v10 - Easy [1 Jan 2016]

Root Guide for the T-Mobile LG V10
Read Post #2 - Great Info​
Before we start, I like to mention that I did not create any of these files and I do not take credit for the work done. All I am doing is putting everything in one place and some helpful things that I had to google. This effort is mainly to make the process easier and more efficient as opposed to having to have several tabs or windows open to do it. I will make sure the proper thanks are given at the bottom
Click to expand...
Click to collapse
Instructions Start Here:
Warning - This will erase user data so you will have to set everything back up again! Always BACK UP YOUR DEVICE!!
1. Download the following tools for this process: adb-setup-1.4.3.exe, & twrp-2.8.7.1-h901.img, & UPDATE-SuperSU-v2.46.zip
Alternative ADB and Fastboot Option - (I Prefer) [GUIDE] Install Android SDK Standalone [ADB][30 Dec 2015] for Android SDK Standalone if you are interested
2. Install adb-set-up-1.4.3.exe to install the universal adb driver (Creates adb folder in C:\ if you don't already have adb setup)
3. Go to settings, about phone, software info and tap build number 5x to enable Developer Options
4. Check the Enable OEM unlock box to enable OEM Unlock
5. Enable USB debugging
6. Plug phone into the computer
7. Click on USB options on the phone and change it to PTP (USB Debugging will connect - Authorize Your Computer when prompted from phone)
Screenshots of Enabling USB Debugging and OEM Unlock
1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.
3.
4.
5.
6.
7. Open a Command Window and change directory to
Code:
[B]C:\adb[/B]
or if you have Android SDK type this below
Code:
[B]C:\Android\platform-tools[/B]
and type
Code:
[B][SIZE="3"]adb devices[/SIZE][/B]
8. You will Get Prompted after adb runs - Allow USB Debugging
8. From the Command Prompt, verify adb sees the device connected -
Open Command Prompt
Code:
cd C:\adb
Code:
adb devices
9. Reboot into the bootloader in command prompt by typing: adb reboot bootloader
10. You will now unlock the bootloader, verify, and Install TWRP
Note* - Make sure you copied twrp-2.8.7.1-h901.img into the C:\adb Folder already
Code:
[SIZE="3"]fastboot oem unlock
fastboot getvar unlocked
fastboot reboot-bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img[/SIZE]
11. You should be in TWRP Currently.
12. Reboot the device, it will delete user settings, so you need to repeat steps 3-8 to get adb set-up again
13. Now place UPDATE-SuperSU-v2.46.zip om your phone
14. Reboot into recovery
15. Back up YOUR EFS PARTITION
16. Wipe Cache and Dalvick Cache 3x
17. Flash UPDATE-SuperSU-v2.46.zip
18. You have successfully Unlocked the bootloader and Rooted your Device!!
19. SuperSU will prompt you to give tmobile.pr.adapt root privlidges, DENY
20. Navigate with Root Explorer to /system/priv-app/AdaptClient and rename AdaptClient.apk to AdaptClient.apk.bak and reboot
21. Finally, All done
Click to expand...
Click to collapse
USEFUL ROOTING LG V10 - by: Glenn Silvasy
Give Thanks To:
@KAsp3rd - http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740
@Chainfire - For Super User
@mikeyinid - Flashable Stock Image
@TheJesus - Providing img files for stock ROM, and OEM unlock Guide
@Snoop05 - ADB Drivers and Fastboot
And Anyone else that was missed!

Updated [31 Dec 2015]
References, Guides and Great Information - Please Read​
LG-H901 Stock .img Files (Boot, System, and Recovery)
Go Here
LG-H901 Stock Flashable ZIP in TWRP
Go Herehttp://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170
TWRP
Go Here
ADB and Fastboot
Go Here #1
Go Here #2 - This can be reached from Go Here #1, but I posted it for a direct link to the tool just in case you miss it!
Android SDK Standalone Tools for ADB and Fastboot Devlopment Setup Guide
Go Here
Can't Get Into the Bootloader - Enter Fastboot Mode
Go Here
These links will have all the files you need in case you encounter any issues and I will also try to answer any questions within the scope of my knowledge. I been doing this for a while and there are tons of smart people on XDA. Please search for the question you want to ask to avoid issues, however, I do not believe in biting someones head off either. Researching is how you learn!! :good:

16. Wipe Cache and Dalvick Cache 3x
Click to expand...
Click to collapse
You seriously do not need to do that, this isn't 2010. In fact, if you ever do that when Xposed is installed, you'll cause a bootloop.

siraltus said:
You seriously do not need to do that, this isn't 2010. In fact, if you ever do that when Xposed is installed, you'll cause a bootloop.
Click to expand...
Click to collapse
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I'm opening my prompt within the folder adb installed to (C:\adb), adb devices command isn't finding anything. I have the necessary things ticked in developer options. Driver issue maybe? thanks

I never did numbers 15, 16 & 20. Not even sure what number 20 is for. Care to explain?

baySF said:
I never did numbers 15, 16 & 20. Not even sure what number 20 is for. Care to explain?
Click to expand...
Click to collapse
Your EFS partition contains your IMEI number and modem partition that allows you to connect to LTE and data services. This happens on Samsung devices, although rare, it does happen. It is good to just back it up just in case you flash and something happens to that partition, your phone essentially becomes a paper weight. I have always wiped cache and dalvick before flashing anything, feel free to do it if you like, not required.. Lastly, when you have root, that app is a T-Mobile app trying to request root permissions, do not allow it. It is an uneeded app. The only useful T-Mobile apps are the Visual Voicemail, Mobile Hot Spot and T-Mobile My Account.

sleekgreek said:
I'm opening my prompt within the folder adb installed to (C:\adb), adb devices command isn't finding anything. I have the necessary things ticked in developer options. Driver issue maybe? thanks
Click to expand...
Click to collapse
After you unlocked developer settings and checked USB Debugging, did you remember to change your connection from MTP to PTP, once you do that it should prompt you on the phone to allow the connection

bdorr1105 said:
After you unlocked developer settings and checked USB Debugging, did you remember to change your connection from MTP to PTP, once you do that it should prompt you on the phone to allow the connection
Click to expand...
Click to collapse
Yes all checked, I never get the prompt though. Also in the device manager I'm seeing The yellow exclamation for "abd interface". This is such a simple process And I've been jacking with it for awhile. I've run the 15 sec ADB several times already. On windows 10 btw
edit: changing to PTP also

sleekgreek said:
Yes all checked, I never get the prompt though. Also in the device manager I'm seeing The yellow exclamation for "abd interface". This is such a simple process And I've been jacking with it for awhile. I've run the 15 sec ADB several times already. On windows 10 btw
edit: changing to PTP also
Click to expand...
Click to collapse
I am on windows 10, so the adb driver is not installed. Did you run the universal adb driver I have posted in the OP. Run that, then ensure your phone is on PTP. If you still have that yellow exclamation point, right click, uninstall driver, then scan for hardware changes and once the driver is installed correctly, you will be good to go

bdorr1105 said:
I am on windows 10, so the adb driver is not installed. Did you run the universal adb driver I have posted in the OP. Run that, then ensure your phone is on PTP. If you still have that yellow exclamation point, right click, uninstall driver, then scan for hardware changes and once the driver is installed correctly, you will be good to go
Click to expand...
Click to collapse
adb-set-up-1.4.3.exe , yes I've installed that several times. I go to that installed folder (C:abd) and open my command prompt from within it. Maybe I'll just get the sdk again, seems like a real simple issue I can't get sorted. Freaking aggravating

sleekgreek said:
adb-set-up-1.4.3.exe , yes I've installed that several times. I go to that installed folder (C:abd) and open my command prompt from within it. Maybe I'll just get the sdk again, seems like a real simple issue I can't get sorted. Freaking aggravating
Click to expand...
Click to collapse
Well adb wont work unless the driver is working, in device manager, if you have the yellow exclamation point, it wont work. You should have seen the Google ADB driver installer come up like a normal windows program installation. Your driver is giving you problems
Try the attached drivers, just extract the zip and point the computer to look in the location of the extracted folder. See if it makes the exclamation go away

bdorr1105 said:
Well adb wont work unless the driver is working, in device manager, if you have the yellow exclamation point, it wont work. You should have seen the Google ADB driver installer come up like a normal windows program installation. Your driver is giving you problems
Try the attached drivers, just extract the zip and point the computer to look in the location of the extracted folder. See if it makes the exclamation go away
Click to expand...
Click to collapse
Thats a no go also, it's saying windows was unable to install. Thanks for the help, I have to crash though, down to 4 hours sleep before work because of this phone lol. I've never had this issue before, maybe tomorrow I can get it sorted out. thanks again

Running fastboot oem unlock will always wipe your user data

KAsp3rd said:
Running fastboot oem unlock will always wipe your user data
Click to expand...
Click to collapse
Thanks for that info, I am surprised it wipes your data or even touches the user partition. Never would have guessed it was from oem unlock
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Your EFS partition contains your IMEI number and modem partition that allows you to connect to LTE and data services. This happens on Samsung devices, although rare, it does happen. It is good to just back it up just in case you flash and something happens to that partition, your phone essentially becomes a paper weight. I have always wiped cache and dalvick before flashing anything, feel free to do it if you like, not required.. Lastly, when you have root, that app is a T-Mobile app trying to request root permissions, do not allow it. It is an uneeded app. The only useful T-Mobile apps are the Visual Voicemail, Mobile Hot Spot and T-Mobile My Account.
Click to expand...
Click to collapse
Is there a way to check if your IMEI was wiped? I still have data and can still send messages and makes calls but whenever I'm at work, I'll always get "voice access restricted" and I never got that on my nexus 5. I also lose connection to my Wi-Fi at work and at home randomly because it says "avoided poor connection". Granted all I have to do is turn Wi-Fi off then back on but it's very annoying. Again, never happened on my nexus 5.

baySF said:
Is there a way to check if your IMEI was wiped? I still have data and can still send messages and makes calls but whenever I'm at work, I'll always get "voice access restricted" and I never got that on my nexus 5. I also lose connection to my Wi-Fi at work and at home randomly because it says "avoided poor connection". Granted all I have to do is turn Wi-Fi off then back on but it's very annoying. Again, never happened on my nexus 5.
Click to expand...
Click to collapse
If you can access LTE than you are solid.. Trust me you will know, you will get rejected from the network.. It is in settings>about>status it will say 0 or be blank if it missing... Rather be safe than sorry
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Click to expand...
Click to collapse
Clearing Dalvik bootlooped both my G4 and my V10 as well as others with Xposed installed, so I'm passing the warning, no need to be butthurt. Thanks for calling me ignorant, stay classy!

siraltus said:
Clearing Dalvik bootlooped both my G4 and my V10 as well as others with Xposed installed, so I'm passing the warning, no need to be butthurt. Thanks for calling me ignorant, stay classy!
Click to expand...
Click to collapse
I cleared cache and dalvick 3 times after installing xposed, but xposed was updated... Look at how you decided to tell me, in a condescending manner so maybe when I explained my side in the aggressive manner you did which was unnecessary, but anyway, learn to be classy before you ask someone else to be classy. Have a great week and merry Christmas bud
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
I cleared cache and dalvick 3 times after installing xposed, but xposed was updated... Look at how you decided to tell me, in a condescending manner so maybe when I explained my side in the aggressive manner you did which was unnecessary, but anyway, learn to be classy before you ask someone else to be classy. Have a great week and merry Christmas bud
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Aggressive? Condescending? Wow. You need to check your ego at the door, buddy, it gets bruised way too easily.

how to run an app on a tablet which only opens Settings?

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

[How-To] Get Oreo recents on Pie (No-Root)

[WARNING]:I accept no responsibility, do this at your own risk!
If you don't like the Pie recents like I do and hate Google widget always listening to "OK Google" command even when it's actually off in the settings, here are a few steps to get Oreo recents back on Android Pie:
-[IMPORTANT] First off install a launcher to your liking and set it as default (Nova is my favorite)
-Go to About Phone in settings and tap on your Build Number until you get Developer options available,
-Go to System settings and then developer options, enable "USB debugging",
-Connect your phone to your PC via USB cable and open an ADB command prompt then type this code and hit enter:
Code:
adb shell pm disable-user com.android.launcher3
This will disable the stock launcher (Quickstep - Launcher 3) for the current user, nothing more and you voila you have Oreo styled recents.
You will NOT be able to use Navigation Gestures when you disable the stock launcher, if you want to use split screen mode, hold the app you want to use as split screen in recents screen and drag it above the screen then choose the other app (holding square button doesn't work on Pie).
To revert back simply connect your phone to PC and type this code:
Code:
adb shell pm enable com.android.launcher3
Don't use pm uninstall, otherwise you can't go back without factory resetting the phone!

The solution
https://forum.xda-developers.com/apps/magisk/module-quickswitch-universal-quickstep-t3884797/
Requires root

Mark7Aymn said:
The solution
https://forum.xda-developers.com/apps/magisk/module-quickswitch-universal-quickstep-t3884797/
Requires root
Click to expand...
Click to collapse
EDIT: Found the solution, tested and works fine!

Google discover feed, how can I enable it?

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