Warning: I will not be responsible for any wrong doings that might occur with following this guide, this is my first Guide here, expect some errors. Any damage to any device that might happen by following then steps is responsiblility of particular user not mine. I recommend that you don't do anything you don't understand.
Disclaimer: I do not personally own a RedMi Note 5A device, I helped a friend to clean up some space on their device, as a part of which, I uninstalled some of the OEM apps that were not used by them.
If you use any of the apps, you should not uninstall them.
Difficultly level: Easy to medium.
Experience required: You should be familiar with ADB, Windows BatchScript (optional), Android file system.
As superuser access is not used in this process, root is not required, you can try this on Non-Rooted devices
Tested on : Redmi Note 5A, Android-8.x, MiUi v10.x
Should work on all device prior to Android 9.
Requirements: ADB installed on PC, supposedly windows. A proper USB cable, an Android Phone.
I'll assume you have already setup ADB via Android-SDK or minimalistic ADB tools, and not go into that.
1. Enable developer mode, USB debugging on phone,
2. Connect device to PC (in a USB 2.0 port, preferably).
3. start adb, "adb start-server"
4. Make sure device is available.
Now there is batch file in attachment for uninstalling and a text file with the list of apps I uninstalled. You can either replace the package name with those you want to remove or you can copy the command, make it a single line command and replace the package name directly into the prompt as I did
{
"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"
}
Additional details are given in the attachment zip files, see below. You replace the package name with the app you want to uninstall and run the script/command in command line.
Same thing can in theory be achieved if "pm" command is readable by a third party terminal emulator apps like Termux, note that, on new devices, "/" is not readable, "/system/bin/pm" might be readable depending on ROM, thus ADB way should always work, but calling "pm" from on device apps is also possible.
Expected results: single word "success" on a new line.
If it says "device offline", restart adb with "adb kill-server" followed by "adb start-server" , if that doesn't work restart the smartphone, if that doesn't work check that USB port is v2.0( search on Google how to determine ), if that doesn't work, your cable would be faulty or some connection error.
Reserved.
Related
So for the first time I've set up my ADB since I will getting a MT3G tomorrow. Environment variables (PATH) set correctly, etc.
When I type adb shell in recovery model, it says *daemon not running. starting it now, daemon started successfully, error: device not found*
"Android Compsite ADB Interface" shows up in my USB devices. So what's the problem.
Then when I load up "emulator -data c:\", it starts up and gives me this error. msvcrt.dll? I've dealt with that .dll file before for other apps and it is in my system32 folder.
So what's going on here.
{
"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"
}
try reinstalling the usb driver.
mine identifies as HTC Dream Composite ADB Interface.
did you install the usb driver that comes in the SDK?
what if you navigate to the location you have the sdk installed? does it work then? maybe the path is not set up as correct as you think? (i had this problem when trying to do fastboot. everything else worked fine except for fastboot. to get that working i had to navigate to the sdk directory.)
I sure did, and it reads exactly that.
Even adb devices doesn't bring a device up. Or adb remount.
Other thing is under Hard Drives Tree, the HTC Android USB Phone Device has a Microsoft driver. I tried to install drivers from the android/usb_driver/ and nothing. Do I have to do this in the Home Screen for the first time so it brings up the permission screen where I click on "Allow Always" for root? Cause I'm not getting that there, so I rebooted into recovery....nothing there as well.
i did have an issue recently where i couldn't get the usb driver to change over.
what i had to do to get it to change was disable and then re-enable usb debugging while the phone was connected to the computer.
it triggers a hardware change in windows and this allowed me to reinstall the correct driver.
uninstalling the current drivers might also help.
I've tried both things.
Same issue.
What Windows Services need to be enabled in order to get ADB to work? I did some tweaking of the services.msc for XP. I think that might be the reason adb shell isn't working.
Same problem I have:
I have TWO rooted G1s, Cyanogen 4.0.4 modified devices with identical Software releases.
The one (rooted by the Golcard Method) is recognized by ADB - the other one (rooted by the One Click Method) is not.
Troubled !
Oh Sorry -this is a Sapphire forum ... I apologize
Hi Folks,
I am running Mac OS X 10.8.2 and I have ran into the following issues. I am trying to root a friend's Nexus 4 that's on 4.2.2, unlocked bootloader and USB debugging enabled/on.
I can easily root this on my Windows desktop but I thought I'd try out the Mac. Do note that I am not getting the "Allow USB Debugging" message that pops up on the phone when you connect it to a computer normally and you select Allow for the respective RSA key. The one that shows up after 4.2.2 is updated from 4.2.1.
I am not getting the above prompt when hooking up the phone to my Mac. *PS I removed the name of my MBP pro and the user name.
Okay so here are the two issues/scenarios:
1) I downloaded the latest ADB and Fastboot Mac OS X 64 bit files from the ADB dev tools website, etc. The files are "adb" and "fastboot"
When I type "./adb devices" since the "./" command is for Mac on the terminal, I get the following message and it does not show up any device listed.
{
"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"
}
Then when I type "./adb reboot-bootloader", I get the following:
__________________________________________________________________________________________________________
2) When I use an older adb and fastboot files from last year: "./adb_Mac" , "./fastboot_Mac" and "ADB-Install-Mac.sh", I get the following:
When I type in the adb devices command and the adb reboot-bootloader command:
The serial # shows up this time (Again I have crossed out half of it lol)
When typing in the reboot-bootloader command:
Now to my knowledge, I know that I am getting the device offline mode based on using the old ADB and Fastboot files. So the way to fix it, is to download the updated files but it doesn't result in anything at all.
With the updated ADB and fastboot files, and by booting into fastboot mode manually and then typing in ".fastboot devices", I get the Error Could Not Get Pipe Properties error in a loop.
Would appreciate the help folks!
T.I.A
Try this command
adb kill server
adb start server
scream4cheese said:
Try this command
adb kill server
adb start server
Click to expand...
Click to collapse
Beauty! I didn't know that it has to be done for the same in OS X. Query, does this have to be done every time or?
Tutorial: How to transfer files to/from our Moto G while in TWRP recovery
This tutorial have been tested in 7, 8, 8.1 and 10 Windows versions. It can work with other devices beside Moto G.
{
"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"
}
Sometimes we need to transfer files to our device while we are in recovery mode. When we forget to copy the zip we were going to flash, when we are installing a
GPE based ROM (we must format /data and erase all files), to transfer a backup... ect. In many cases we need this function.
The purpose of this tutorial is to make our PC succesfully recognize our Moto G as a storage device being in TWRP recovery.
Many users have reported that their devices are not being recognized.
Requirements:
-Have installe the last TWRP recovery version.
-Have installed ADB drivers in PC. You can try this ones Universal ADB Drivers or Motorola Mobile Drivers 64 bits
-USB data cable.
-PC runnig Windows 7, 8, 8.1 or 10 (can work with older versions).Steps: Sorry for spanish images, if you can provide me english captures would be great.
1) Boot into recovery mode and connect to PC with USB data cable.
2) Being completely sure your device is not being recognized, otherwise this tutorial will be totally useless to you.
3) Open Control Panel and click on Hardware and Sound
4) Go to Device Manager.
5) Look for 'Android Device' or 'Android Phone' or any related name, open the list, rigth-click on the device and click on 'Update driver software'.
6) Now click on the second option.
7) Now click on the option below:
8) Make sure 'ADB composite device' is there and click next.
9) Once this is donde, reboot your PC and it will be in capacity to recognize your device as a storage device while you are in TWRP recovery. We can freely transfer files.---------------------------------------------------
Last Update: 17-07-2015
Reserved
Thanks
{
"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"
}
Install apps over ADB
Install apks on any Android device running any Android version over ADB!
Hi all,
From a long time i was fiddling around with a problem of installing/downloading apps after installing a new ROM.
Thus i came up with an idea of a Batch File to install all of your apks from your system
to your phone in a few tips and taps. Hah! Found my solution .
How does it look?
To see some screenshots, please click below.
Tested on
The script had been tested on Nexus 5x, Nexus 5, Moto G4 but should work on any android device.
Downloads
Google Drive - Here is the link to Drive.
Link Below - You can also find the file below.
Installation instructions
Prerequisites
1. Platform Tools for Windows (ADB),
2. APK files,
3. Target phone connected to PC and
4. A cup of COFFEE or TEA as you like it.
Process
1. Download it from the attachments below or from the drive link above or here.
2. Copy the file to the ADB folder.
3. Execute the file.
4. You can either place your apps in "D:\Apps" folder. (Sllloooowwwww.....)
ORChange the folder location in batch file itself. (Requires some Coding Skills)
ORBatch file will ask you to change the location, if required. (Easy Installation, Pick Me!)
Troubleshooting
I don't think it's needed. But even then if you get any problem do write. I'll be happy to resolve it.
Enjoy, and also don't forget to write anything (Good, Bad or Thanks etc.)!
thank you so much if works like a charm!
Been locking for something similar.
Is it possible to take that script to next level, and make it as, a list of apps, and for them to be downloaded on the phone. I mean give order through ADB for each apps step by step, instead of folder, to be downloaded.
how to add online option like google drive folder in to the script
I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
/https://imgur.com/a/NBfrIcZ
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does so it disappears from the ADB Diver Installer / APK Installer
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything. I don't understand what I am doing wrong and am very stuck sadly
{
"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"
}
Would really appreciate some help!
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
George425 said:
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
Click to expand...
Click to collapse
Ask your question here in moto g4 forum you will gets answers correctly ,because that's where you should have asked, buts it OK here is the link https://forum.xda-developers.com/mo...hread-question-noob-friendly-t3526598/page175
And upload the photos in Google drive and turn on the link sharing feature and post the link there there are many people there to help you out. Don't worry, everything will be fine.
Thank you Dhanush-raj I will do that now.