Hi, i have ICS for HTC Desire (Bravo), Android 4.0.4 and my problem when i start Terminal Emulator, i type "su" and i get # (superuser permissions) and when i type "adb uninstall package" i get message from terminal "waiting for device" and i dont know what to do
I need to uninstal com.android.vending
Thx for help
t0msk said:
Hi, i have ICS for HTC Desire (Bravo), Android 4.0.4 and my problem when i start Terminal Emulator, i type "su" and i get # (superuser permissions) and when i type "adb uninstall package" i get message from terminal "waiting for device" and i dont know what to do
I need to uninstal com.android.vending
Thx for help
Click to expand...
Click to collapse
This has nothing to do with Terminal Emulator, it's working fine ->
adb stands for android debug bridge, it's meant to be a way to do stuff with your android device from your computer over the "bridge" that is USB. It says "waiting for device" because it needs a USB android device to be connected. As far as I know, even with OTG you can't use adb actually on an android device itself with Terminal Emulator. If all you want to do is uninstall an app, you shouldn't need adb anyway.
Read here.
HTCDreamOn said:
This has nothing to do with Terminal Emulator, it's working fine ->
adb stands for android debug bridge, it's meant to be a way to do stuff with your android device from your computer over the "bridge" that is USB. It says "waiting for device" because it needs a USB android device to be connected. As far as I know, even with OTG you can't use adb actually on an android device itself with Terminal Emulator. If all you want to do is uninstall an app, you shouldn't need adb anyway.
Read here.
Click to expand...
Click to collapse
I tried use adb through cmd in windows but its waiting too (adb through cmd is working only in recovery)
So how can i uninstall system app?
Screenshot is in attachments, i can disable it, but i need to uninstall it, because here is thread: http://forum.xda-developers.com/showthread.php?t=1355660&page=1662
Originally Posted by rfandango View Post
Download: Vending-3.8.15.noupdate.norestrictions.apk - google it - rename to Vending.apk, with root explorer move it to system app and set perm to rw r r...reboot...work like a charm
Unfortunately, this isn't working for me - still no play store, but there's an entry for com.android.vending in Manage Apps with a grey icon (generic app icon with a little SD card in the bottom right corner) and a size of 0.00b. Anyone know what I missed?
Click to expand...
Click to collapse
Edit: Fixed it! Needed to do "adb uninstall com.android.vending" and then reboot. The store is back now.
Click to expand...
Click to collapse
Any idea?
Because i dont have Play Store so i cant do anything
t0msk said:
Any idea?
Because i dont have Play Store so i cant do anything
Click to expand...
Click to collapse
Try run the following in Terminal Emulator:
Code:
pm uninstall com.android.vending
* You must find out the vending apk and delete it first (If the apk exists and is a system app).
codelover said:
Try run the following in Terminal Emulator:
Code:
pm uninstall com.android.vending
* You must find out the vending apk and delete it first (If the apk exists and is a system app).
Click to expand...
Click to collapse
i got "Failure"
I made new screenshot and i found that when i type "adb devices" in Terminal Emulator i get blank page, you can see it in the screenshot
t0msk said:
I made new screenshot and i found that when i type "adb devices" in Terminal Emulator i get blank page, you can see it in the screenshot
Click to expand...
Click to collapse
As mentioned by @HTCDreamOn, adb is for you to run commands from Windows and since you are working with Terminal Emulator you do not need to deal with adb related command.
Also mentioned earlier that you MUST manually delete the apk first before you can uninstall the app if it is a system app.
To do that first find out where the vending apk located. assumed that you have busybox/grep installed, run the following in Terminal Emulator:
pm list packages -f | grep vending
You should get something like this:
package:/system/app/vending.apk=com.android.vending
Click to expand...
Click to collapse
* Actual filename & path may vary depending on device
Now that you know where the apk is, eg: /system, mount the /system rw and delete the vending.apk manually.
Then you can proceed to uninstall using the following command:
pm uninstall com.android.vending
Success :laugh:
Thx!
I dont want to make new thread so my another question is why i cant go to ini.d folder when its exists?
Look at my screenshot
//EDIT: SOLVED
I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!
s1dest3pnate said:
I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!
Click to expand...
Click to collapse
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk
Acid0057 said:
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!
s1dest3pnate said:
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!
Click to expand...
Click to collapse
Awesome!
Sent from my Pixel XL using Tapatalk
I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery
GBpfan95 said:
I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery
Click to expand...
Click to collapse
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.
s1dest3pnate said:
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.
Click to expand...
Click to collapse
Does that work even if I am locked and not rooted?
GBpfan95 said:
Does that work even if I am locked and not rooted?
Click to expand...
Click to collapse
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.
I just ended up factory resetting. Most of everything is backed up anyway. Definitely learned my lesson
Could you please post the SubstratumRescue.zip? I cannot get to the directory on my phone via ADB and want to try running the script commands manually.
EDIT: Nevermind, I tracked it down on the dev's AFH page.
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks
pR0wl3r said:
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks
Click to expand...
Click to collapse
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...
jeremywh7 said:
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...
Click to expand...
Click to collapse
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?
bobby janow said:
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?
Click to expand...
Click to collapse
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.
jeremywh7 said:
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.
Click to expand...
Click to collapse
Yeah still shows an x.
Sent from my Pixel using XDA-Developers Legacy app
Thanks!
AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Thanks so much mate this worked for me perfectly!
This can be done in a less manual fashion. It looks like many of you are on Windows, but I'm sure theres a way to accomplish something similar. I'm on Linux and this is how I did it.
Code:
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 echo cmd overlay disable
cmd overlay disable com.samsung.android.app.aodservice.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.smartmirroring.StatusBarIconsforSamsungextras
cmd overlay disable android.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.app.smartcapture.StatusBarIconsforSamsungextras
cmd overlay disable com.android.settings.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.lool.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.navbars.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.tiles.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.statusbars.StatusBarIconsforSamsungextras
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 adb shell cmd overlay disable
For reference, ag is very similar to grep. So the explanation is adb shell allows you to pass a command to it so it can run that command immediately. So adb shell cmd overlay list is the same as typing adb shell followed by cmd overlay list except it prints the output and immediately exits. So I take that output, grep (using ag in this case) for the enabled overlays and then programmatically disable them. xargs -n 1 says take at most one of the arguments passed to this command and append it to the rest of the line. So this calls adb shell cmd overlay disable __insert-overlay-here__ repeatedly.
I messed up good....
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first one was apparently not removing my overlays. So anyway...
My device rebooted after Chainfire, and was on the G/progress bar for like 5 mins so I knew something was up.
I decided to flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread, so I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
EDIT: Resolved. I was able to delete all overlaid apk's from /data/app.
Hi there,
Question, I got a non-rooted S8, Stock in like everything, and it runs everything fine, including Substratum!
I am wondering about one thing though after reading this thread, imagine something went wrong, what would be my options? I found the Rescue ZIP on my phone, can I apply this if needed with the original recovery from the S8? Or do I need TWRP for that?
---------- Post added at 08:44 PM ---------- Previous post was at 08:39 PM ----------
s1dest3pnate said:
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.
Click to expand...
Click to collapse
Hi mate, do I read correctly, that its possible to only boot TWRP temporaly without flashing it?
I have to put the folder/files in the same folder as platform tools?
So you got your new shiny realme device but you hate bloatware or want to disable system apps so you can use 3rd party apps instead?
Follow the steps below:
THIS DOES NOT REQUIRE ROOT HOWEVER MAKE SURE NOT TO DISABLE IMPORTANT SYSTEM APPS. WIPE DATA/FORMATTING RE-ENABLES ALL SYSTEM APPS. THIS DOES NOT MESS WITH OTAs.
WHAT YOU NEED:-
ADB/Fastboot Drivers
Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip,
Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
DEBLOAT:-
1. Enable developer options by tapping on the build number 7 times and enable USB Debugging.
2. Plug in your phone.
3. Goto the folder where ADB is installed, hold shift and right click, and click on open command window here(windows).
4. Type
in CMD
Code:
adb devices
in Powershell
Code:
./adb devices
.
5. This should return the ID of your device and show if its authorised. Enable debugging Promt on your Phone if it shows unauthorised (allow this computer).
6. Type
in cmd
Code:
adb shell
in Powershell
Code:
./adb shell
.
7. This should display a prompt, something like RMXxxxx:/ $
8. To uninstall type
Code:
pm uninstall -k --user 0 <name of the package>
To disable type
Code:
pm disable-user --user 0 <name of the package>
eg: pm uninstall -k --user 0 com.heytap.browser / pm disable-user --user 0 com.heytap.browser
9. Done!
To reinstall uninstalled apps type
Code:
pm install-existing <name of the package>
To enable disabled apps type
Code:
pm enable <name of the package>
Some apps do not uninstall such as market and gamecenter, disabling is the only option.
Hi, I made a small shell script to remove bloat in my device. Anyone who are interested can check it.
Place it in root of Internal Storage, then
Code:
adb shell
sh /sdcard/bloat.sh.txt
Ref
⋆ [2022-09-28] Remove system apps on Realme UI 2.0 using ADB ⋆
Remove system apps on Realme UI 2.0 using ADB Updated : 2022-09-28 Tested On: Model: RMX2001 Hardware Version: RMX_2001_11 RealmeUI Version: V2.0 ColorOS Version: V11 Android Version: 11 Android Security Update: 2022-03-05 Build Number...
forum.xda-developers.com
Debloat Colour os For smooth Performance
Color OS preloaded with certain apps. Such apps can't simply uninstall. Its hard coded, , for e.g. App Market. Use these command to disable those apps.. No root required... Os updates will still work.. No problems there... Users need to apply...
forum.xda-developers.com
[GUIDE][EU/IN ROM] REALME UI Debloat List
I got this phone a few days ago, am positively surprised with it. As soon as I got it I installed the REALME UI update from the official website and spent the next hour trying to find out what apps should be removed for maximum privacy and...
forum.xda-developers.com
[GUIDE] Debloat your Realme X2 to get more free RAM
Install ADB Drivers properly .This is really important Video Tutorial : Debloat any Realme/Oppo phone Then open command windows in adb directory and type adb devices,then authorize it from your phone . After you have done it ,type adb shell...
forum.xda-developers.com
Debloat COS / RUI
For those who want to debloat the stock system without root, here my list with apps uninstalled for me. How-To: activate ADB in developer settings download ADB tools from Google...
forum.xda-developers.com
[GUIDE] [SCRIPT] Debloater for Bootloader locked & Unlocked devices
For Bootloader Locked: Download debloat_bootloaderLocked.zip extract & execute debloat-main.bat file For Bootloader Unlocked: Assuming you already have custom recovery, just download & flash debloat_flashable.zip Unhide to show up the list of...
forum.xda-developers.com
Nice thank you for sharing this wonderful trick thanks
Hi guys. Thanks for the nice debloat tutorial and script! These are always welcome.
debdeep98 said:
Some apps do not uninstall such as market and gamecenter, disabling is the only option.
Click to expand...
Click to collapse
Are you sure about that? Have you tried it yet with my brand new
universal make system read write flashable script
I am running lineageos 17.1 and installed SAI, split apks installer. When I click on an apk file, I would normally get a prompt to choose between the system package installer (com.google.android.packageinstaller) and SAI (com.aefyr.sai) to open "Just Once" or "Always".
One time I accidently hit "Always" to use the system package installer to install an app and now I no longer get the prompt to pick one or the other. Is there a way to clear the default package installer? The system default installer is not listed in the app drawer or under Settings>Apps and only accessible in adb shell so there is no icon to long press to get app info and change "Open by default" setting. I tried "adb shell pm clear com.google.android.packageinstaller" as root to no avail.
Thank you for help in advance.
May be doing it the other way does help
Code:
adb devices
adb shell "pm clear com.aefyr.sai"
adb uninstall com.aefyr.sai
adb reboot
adb install com.aefyr.sai
Thank you for the suggestion but "adb pm clear com.aefyr.sai" and "adb pm uninstall com.aefyr.sai"and reinstalling didn't help.
Hello. Please forgive my bad English. My Asus ZE500KL phone with Android 6, almost died. I have collected various things in it, phones, notes, passwords... and I had the stupidity of not having any backup. Sometimes it starts, but it throws up countless signs like "Unfortunately com.android.XXX Has Stopped". To do anything with the phone I have to be able to close them and I have very little time, it can be used and restarted in seconds. It behaves similarly in safe mode. Otherwise, it enters fastboot mode and adb, but I don't know how it got stuck there. Any ideas what I can do? A week ago I installed "SWAP no root", could it be from that?
Do a LOGCAT to get the very reason why you get this notification.
logcat is first thing you should do. you can redirect > into file and upload here
Code:
adb logcat '*:W' -b all > logcat.txt
try to uninstall some recent apps from adb maybe it stabilizes. the -k flag preserves app data
Code:
adb shell 'pm list packages -e'
adb shell 'pm uninstall --user 0 -k <pkgname>'
if you don't close any of that pop-up is phone rebooting anyway? if stable enough you can do backup and pull files (confirm blank no password)
Code:
adb pull -a /sdcard
adb backup -apk -shared -all
jwoegerbauer said:
Do a LOGCAT to get the very reason why you get this notification.
Click to expand...
Click to collapse
E:\platform-tools>adb devices
List of devices attached
G6AZCY00W177EUE recovery
E:\platform-tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
E:\platform-tools>adb logcat
adb server version (32) doesn't match this client (41); killing...
* daemon started successfully
- waiting for device -
* daemon still not running
error: cannot connect to daemon at tcp:5037: cannot connect to 127.0.0.1:5037: N
o connection could be made because the target machine actively refused it. (1006
1)
aIecxs said:
logcat is first thing you should do. you can redirect > into file and upload here
Code:
adb logcat '*:W' -b all > logcat.txt
try to uninstall some recent apps from adb maybe it stabilizes. the -k flag preserves app data
Code:
adb shell 'pm list packages -e'
adb shell 'pm uninstall --user 0 -k <pkgname>'
if you don't close any of that pop-up is phone rebooting anyway? if stable enough you can do backup and pull files (confirm blank no password)
Code:
adb pull -a /sdcard
adb backup -apk -shared -all
Click to expand...
Click to collapse
logcat.txt is empty
do this in android, not recovery
aIecxs said:
do this in android, not recovery
Click to expand...
Click to collapse
If I to load Android, the phone works for 20-30 seconds maximum and when I plug in the USB cable, it restarts immediately.
let usb plugged and adb logcat waiting while phone boots