Related
Hi.
I don't know what happened, but I cant access my phone via adb anymore. I've used adb for months with no problem so far.
The Device is shown in windows xp as "Android Composite ADB Device". I uninstalled an reinstalled the drivers. But ADB and other apps like ddms don't recognize the device anymore.
I'm not sure, but perhaps the problem exists since I installed the modem-driver to use USB-tethering.
USB-Debugging is enabled too...
Does anyone have an idea?
I'm using cyan 4.3.2.1.
Try unplugging your phone, turning it off, on, let it load up, connect it to your comp, wait a good minute or two for it too load up, double check USB debugging, etc. etc.
If it still doesn't work, boot into recovery, connect it, and try adb shell there. ( assuming you have cyan's recovery, or that other custom one, Idr the name xD )
If none of that works, try to re-root using this;
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_Versions
Make sure to backup and stuff, etc. etc.
Hope I helped!
Exodeity said:
Try unplugging your phone, turning it off, on, let it load up, connect it to your comp, wait a good minute or two for it too load up, double check USB debugging, etc. etc.
If it still doesn't work, boot into recovery, connect it, and try adb shell there. ( assuming you have cyan's recovery, or that other custom one, Idr the name xD )
Click to expand...
Click to collapse
thx a lot for the quick answer, but I tried all of this. In the Recovery (Amon Ras' I recognized the first time, that adb doesn't work)
I can't believe, that I have to re-root... Recovery and SU are still working.
Any other experience with the problem?
p.s.: I unchecked the USB-Tethering and already uninstalled the modem-driver without success...
That's weird, you sure your in the right area on your cmd prompt?
x:\xx\android\tools adb shell
You could also try adb remount and see what that gives you.
I'm just learning the real ADB commands, forgive me, I'm no master
Edit: Make sure to unplug your phone before you uninstall the USB/ADB drivers, and make sure you uninstall *everything* that has android or HTC on it from the device manager.
Exodeity said:
That's weird, you sure your in the right area on your cmd prompt? ( Assuming your on windows, the Terminal in linux, I'm sure you know xP )
x:\xx\android\tools adb shell
You could also try adb remount and see what that gives you.
I'm just learning the real ADB commands, forgive me, I'm no master
Edit: Make sure to unplug your phone before you uninstall the USB/ADB drivers, and make sure you uninstall *everything* that has android or HTC on it from the device manager.
Click to expand...
Click to collapse
you gave the right advice...
it's weird. I set adb as variable in windows environment and it worked till today.
Now I started a command prompt in another folder with adb in it and started adb... and it works. weird. I already uninstalled the drivers with usbdeview, restarted etc. a several times and it didn't work. Just use another adb-command finally worked...
thx
Code:
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT852KV04159 device
Yeah, that happens to me sometimes, where it says the device didn't ACK, or something, but I just unplug it, plug it back it in, and wait a good minute it works flawlessly.
I guess our G1's just get moody sometimes, I know I would if someone changed my innerds and outterds on a regular basis xD
I hope I'm not just being an idiot here, but I am having a lot of trouble with adb shell right now.
When starting the shell, instead of starting in $ it defaults to #.
However, whenever I attempt to use 'su', I receive an access denied error. I am not receiving any prompt on the device as I normally would.
At first I thought this was just related to CM7, but even flashed back to rooted 1.0.1 I am getting this issue.
Can anyone offer some insight?
Thanks
Edit: Damn, forgot to add [Q] to the title. Sorry!
Problem: I have an Aishon A19 tablet, which it is very hard to find information about. It is an RK3288 tablet running Android 5.1.1.
It is not really rooted in the normal sense. However, "adb root" works; I can get a root shell and mount /system as writeable, I can push any app I want to the device, etc.
Things that will not work:
-- I tried to put on a /system/xbin/su (from SuperSU 2.76), with mode 6755 (rwsr-sr-x) and it didn't work. I also made symbolic links to /system/bin/su and /system/xbin/daemonsu. Running it from a non-root shell in adb prints a 1 and doesn't give me root. Running it from a non-root shell on the tablet does the same thing. Running it from a root shell gives me no error, but that obviously isn't much use.
-- Running SuperSU as an app gives me the error message about "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5....." I have no idea if it actually can't see the ./system/xbin/su or if the error message just isn't that good.
-- Trying to use "adb reboot bootloader" or getting into the bootloader using buttons doesn't work. It reboots the tablet into a blank screen, with the same vendor ID and a new product ID; however, "fastboot devices" shows nothing. This happens both under Windows and Linux, and even when run as root under Linux (thus not having to worry about udev rules). This means that I cannot install TWRP unless someone can explain to me how to install TWRP without using the bootloader.
I *can* use "adb reboot recovery" and get into the recovery menu. And as I mentioned, I can get root access to the tablet and a root shell using "adb root", and push any file I want to it.
Is it possible to use this root shell and/or recovery to install SuperSU somehow, even if I have to just copy files one at a time?
Edit: Moderators., you can lock this. Someone had the same problem in http://forum.xda-developers.com/apps/supersu/how-to-manually-update-su-supersu-file-t3238991 and I was able to folloow that, manually running the commands in update-binary.
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
rldev said:
Remove Sprint from LG G8
We are removing the following files. See bottom for some notes. If you are using the floating bar, disable it or adb may not work.
Caller Id
Carrier device manager
Carrier Hub
MCM Client
Mobile Installer
Sprint Mobile Framework Support
Sprint Service
Software Update
pm uninstall -k --user 0 com.lookout
pm uninstall -k --user 0 com.coremobility.app.vnotes
pm uninstall -k --user 0 com.sprint.w.installer
pm uninstall -k --user 0 com.sprint.ms.cdm
pm uninstall -k --user 0 com.sprint.zone
pm uninstall -k --user 0 com.sprint.ecid
pm uninstall -k --user 0 com.sprint.extension
pm uninstall -k --user 0 com.sprint.care
pm uninstall -k --user 0 com.sprint.ce.updater
pm uninstall -k --user 0 com.lge.sprintnativewfc.smf
pm uninstall -k --user 0 com.sprint.ms.smf.services
pm uninstall -k --user 0 com.lge.sprintserver
pm uninstall -k --user 0 com.lge.lgdmsclientspr
NOTE: The last line will remove the Sprint Activation at boot. There are 3 of these that come up when you search in the app.
I don't know how to get rid of the Sprint bootup. The last one I purchased had it removed, so it is possible. Someone let me know.
Click to expand...
Click to collapse
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
brandontw said:
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
Click to expand...
Click to collapse
Will the device be able to receive software updates after this?
kimush said:
Will the device be able to receive software updates after this?
Click to expand...
Click to collapse
Yep. Just got one today actually.
Hi. thanks for the info and the procedure. all went fine on my LG V50 thinq from Sprint (LM-V450PM). some interesting data is that I could get rid of the Sprint bootup performing a hard reset with the key convination before turning the phone on. I could not say if the device will be able to receive software updates after all these procedures because I already had it updated before to android 10. now the phone seems to be running a clean official rom. hope to hear about some root news for this device.
i am stumped at #9. was the next step" CD<path address>?" because that did not work.
then i tried to skip it to enter abd devices in cmd and that didn't work either.
could someone please answer if it's not too much trouble?
brandontw said:
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
Click to expand...
Click to collapse
Hi, mate!
The Sprint boot up animation is still present after following the procedure. by the way, 2 commands (somewhere in the middle of the list) read "failure (not installed for 0). what does this mean?
i truly appreciate your work, mate.
brandontw said:
Yep. Just got one today actually.
Click to expand...
Click to collapse
Hi mate. So my LG G8X can still receive update, right? Although the LG software update is already gone from the update center section?
biscuitcrust said:
i am stumped at #9. was the next step" CD<path address>?" because that did not work.
then i tried to skip it to enter abd devices in cmd and that didn't work either.
could someone please answer if it's not too much trouble?
Click to expand...
Click to collapse
replace <path address> with (if you simply downloaded it and unzipped it) example: Downloads\platform-tools_r30.0.5-windows\platform-tools so it'll be "cd Downloads\platform-tools_r30.0.5-windows\platform-tools"
Do you think this process will allow WiFi calling to work on T-Mobile?
It worked perfectly but i would like to install stock rom for this device without bloatware and that one that does not have to do these steps every time I reset the phone. Can somebody help me to find that rom 'cause i found a lot of regions and i don't know wich one is the one i need.
when doing this process is there a risk of brick? It is the first time that I will try
Lennylegendary said:
when doing this process is there a risk of brick? It is the first time that I will try
Click to expand...
Click to collapse
modding anything theres always a risk but if it bootloops you might just have to go to recovery and do a hard rest
brandontw said:
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
Click to expand...
Click to collapse
Hello can you assist me
Disabling Sprint Activation for non-Sprint Networks (on Mac)
1) Enable Developer options on G8X ThinQ.
Go to Settings > About Phone > Software info and then tap Build number a few times to enable Developer Mode. Accept warning. In the now available "Developer Options" settings, enable USB debugging.
2) Connect the phone to Mac through USB. No additional drivers need to be installed.
2) Following these instructions to install adb and issue commands on Mac
Install and Use ADB and Fastboot on Mac [How to]
If you want to use ADB commands in Mac terminal, you'll have to download and install ADB and Fastboot on Mac or you'll get 'not found' error.
technastic.com
I placed the unzipped platform tools in the Application folder.
3) list potentially unneeded Sprint packages to uninstall.
./adb shell pm list packages | grep sprint
For all packages:
./adb shell pm list packages
3) Check for the existence of com.lge.lgdmsclientspr, the service which initiates the Sprint activation at boot.
./adb shell pm list packages -f com.lge.lgdmsclientspr
or without -f
./adb shell pm list packages com.lge.lgdmsclientspr
4) Uninstall/Disable com.lge.lgdmsclientspr package
Uninstall
./adb shell pm uninstall -k --user 0 com.lge.lgdmsclientspr
Reinstall later
./adb shell pm install-existing com.lge.lgdmsclientspr
Alternatively,
Disable
./adb shell pm disable-user --user 0 com.lge.lgdmsclientspr
Enable
./adb shell pm enable com.lge.lgdmsclientspr
5) Confirm packages enabled or disabled
List all enabled apps filtered by "sprint":
./adb shell pm list packages -e | grep sprint
List all disabled apps
./adb shell pm list packages -d
6) Reboot the device by ADB command
./adb reboot
In Windows, the adb shell command is started as follows:
Windows Command Prompt: adb shell pm list packages -d
Windows PowerShell: .\adb
question 1: is it recommended to remove the (active european) sim card before injecting those commands or does it not affect the system change anyway?
question 2: although my refurbed G8 from California works with a german sim card, it seems the phone itself still has a country lock, due to not accepting european LG Smartworld login. It only offers login possibility via US, Canadian and Mexican LG accounts. Will this restriction be overridden after the here mentioned debrand codes initiation?
In this guide we will see step by step how to debloat the Galaxy Tab S8
First of all we have to enable: Developer Options
Settings->About tablet->Software information->(tap 7 times)Build number
After that we will enable: OEM Unlocking & USB Debbuging
Settings->Developer Options->OEM Unlocking(ON) & USB Debbuging(ON)
On the next step we need to download & install : ADB & Fastboot tools
Once you install the tools, connect your {Tablet} - {PC}
Select: USB Debbuging & Open your: Terminal
We are almost there
Now i will make a short explanation in order to understand what are we doing exactly & how we will do it.
What is ADB?
ADB provides us with commands that can be used to debug Android devices,
installing or uninstalling apps and getting information about a connected device.
adb shell
This command activates the remote shell command console on the connected Android smartphone or tablet.
adb shell pm uninstall -k --user 0
Using this, you can easily uninstall the unwanted system apps. To be able to execute it, you must issue 'adb shell' command first.
You can then use 'pm uninstall -k --user 0' followed by the Android app package name as shown below.
pm uninstall -k --user 0 com.whatsapp_2.20.apk
This command can help you if you want to remove all the bloatware from your phone.
Please note that most system apps don't have the 'Uninstall' option on the device but this command works magically.
If you don't know the app package name for the apps you want to remove, you can use adb shell pm list packages to find it out.
adb shell pm list packages
Using the above ADB Shell command, you can print the list of the app package names for all apps installed on your Android device.
You can use this command with different parameters to get a more specific list of app packages.
For instance, if you want to list the system apps only, use
adb shell pm list packages -s
In order to list all third-party apps installed on your Android phone or tablet, you issue the following command.
adb shell pm list packages -3
Do you want ADB Shell to show the list of all enabled or disabled apps on your device,
try the command with '-d' (disabled apps) and '-e' (for enabled apps) parameter.
adb shell pm list packages -d
adb shell pm list packages -e
Now, if pm list command troubles you or you are unsure that you are making the right choice you should stop right there
(uninstalling the wrong app might harm your tablet's operating system) and use another method for identifying which app you want to uninstall.
(GUI method - Graphical User Interface) For example: APK Inspector will provide you with a detailed list of installed packages (plus their icon) on your device, once you select an app, extra details will be shown to you & that's how you will get the correct name.of.the.app
Thanks for your time ❤
Reserved
I really appreciate this write-up it has been a big help..
I use my OnePlus 9 pro with ADB and fastboot for Android NDK to debloat..
and that application inspector is a God send so again. thank you
I don't know if it was just a fluke or what but when I rebooted after successfully deleting digital well-being my tablet booted up super fast...
either way I'm good.
Awesome thanks for the tip. Is using "install" put the app back if I screw up something?
So it really doesn't uninstall just uninstalls from your app draw?
striker59 said:
So it really doesn't uninstall just uninstalls from your app draw?
Click to expand...
Click to collapse
For the os, it is like it has been uninstalled. But you don't free disk space, as the data of the app are still there. They just been hidden from os. That's why you can have back the app again just with an adb command again.
Man I used this to shut down numerous apps on all of my Android devices. Samsung and Verizon apps. Thanks!
Went back in to uninstall more apps. Device is recognized but adb shell won't load. The last time I used adb it was for my phone.
Figured it out, had to revoke USB debugging on my tablet. Delete on the computer c:user.android and restart (actual path on the computer could be different than what I stated).
Hi there.
Can anyone confirm, if it is save to remove the phone app from the device since it is connected to this samsung feature "calls/ messages on other Galaxy devices"? Actually i fully wanne get rid of this feature and app since i don´t use a galaxy phone.
Can someone share experiences/ideas according this topic?
Stogie87 said:
Hi there.
Can anyone confirm, if it is save to remove the phone app from the device since it is connected to this samsung feature "calls/ messages on other Galaxy devices"? Actually i fully wanne get rid of this feature and app since i don´t use a galaxy phone.
Can someone share experiences/ideas according this topic?
Click to expand...
Click to collapse
I have Debloated it (adb frozen) months ago. Didn't have any problem. You can always enable it again.
Am I right? If i debloat I don't clean up the system space used from the os ?
nofear5888 said:
Am I right? If i debloat I don't clean up the system space used from the os ?
Click to expand...
Click to collapse
You won't earn more free space. Apps are still there after Debloating.
sosimple said:
For the os, it is like it has been uninstalled. But you don't free disk space, as the data of the app are still there. They just been hidden from os. That's why you can have back the app again just with an adb command again.
Click to expand...
Click to collapse
@striker59
You remove the app for the current user but its still inside system's root directory.
You don't gain storage.
What you can achieve tho if you remove/disable the unnecessary services without causing softbrik or error spamming 'service has stop working' is a lightweight $user who uses less ram, your phone's overall performance is better and the battery reduction is slower.