This post explains how you can extract the logs of an app using the adb command line tool. Earlier, we could access the Android->data folder for each app but that is not possible now. But we can do it using the adb command line tool.
1. Step 1
a. Install and setup the adb command line tool for your computer. This article shows you how to do so.
2. Step 2
a. Now since your phone is connected to your computer via adb, open a command prompt and type in "adb shell". Now you can access your phone via the command line.
b. To access the data folder for a particular app, type in the following command "cd /sdcard/Android/data". Here you'll find the data folders for all the apps in your phone.
c. List all the apps using the "ls" command as shown below.
{
"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"
}
3.Step 3
a. Now get the complete name of your app and type in "cd <COMPLETE_APP_NAME>". Here you can access the logs/cache of your app.
b. Now to download this file to your pc, open another command prompt and type in command "adb pull /sdcard/Android/data/<APP_NAME>/<YOUR_PATH>"
c. This will fetch and download the files you need at the location where your command prompt is pointing to (D drive in this case)
Related
{
"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"
}
Here is a SystemUI.apk that changes the Quick Panel icons to blue!
Prerequisites
Root
ADB
Something to mount /system/ as writable (I use ES File Explorer)
[NOTE: This is based on the STOCK Juggernaut 5.0 SystemUI.apk]
Instructions
1. Place the attached "SystemUI.apk" in the folder where you have ADB setup (usually either "tools" or "platform-tools" in your SDK folder)
2. Type "cmd" in Run Dialog
3. Type cd and then type the path to the folder where you have ADB setup
Example
Code:
cd c:/android/android-sdk/platform-tools/
4. On your phone, mount system as writable (IMPORTANT : Your system must be writable or you will get a read-only error in the command prompt)
5. Push the modified "SystemUI.apk" to the /system/app/ folder
Code:
adb push SystemUI.apk /system/app/
You may or may not get some Force Closes after doing this - IT'S OKAY!
6. Reboot your phone - the fastest way is just type "adb reboot" since you already have the command prompt up and are in the correct directory.
Congratulations! You changed your Quick Panel icons are blue!
Wanna control your Samsung Galaxy Young remotely using mouse and keyboard or record a video on your computor ?Recently i found a way its working fine and support all the android devices .
Required
android sdk
latest java runtime environnement ( doesnt have ? click here )
Installation
Install the android sdk
Connect your device through USB cable and ensure it’s detected with “adb devices”
Make sure you have Java Runtime Environnement 5 or later installed
Click HERE. You can launch it by typing “javaws <jnlp file>” from a command line.
If mouse/keyboard control doesn’t work, open a command line and type :
adb shell
su
chmod 777 /data/dalvik-cache
cd /data/dalvik-cache
chmod 777 ./
Features
Mouse and keyboard control FOR ROOTED DEVICES ONLY
Landscape mode (right click)
Video recording
Basic file browser
This method working on rooted and non rooted devices ,but if your devices has been rooted you can control your phone with mouse and keyboard !
{
"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"
}
Screen Recorder Test Video :http://www.youtube.com/watch?v=CaJ_EZMIUAY
original thread : https://code.google.com/p/androidscreencast/
great
Fastboot doesn't "find" Kindle Fire 2 in Fastboot mode (Drivers installed OK)
Hi, I restarted my Kindle Fire 2 in fast boot mode and installed the drivers on Windows successfully under the Device Manager however when I run "fastboot devices" nothing is displayed, what could be the problem?
Thanks
A screenshot:
{
"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"
}
theplagueisback said:
A screenshot:
Click to expand...
Click to collapse
its because the vendor id is non standard, try
Code:
fastboot -i 0x1949 devices
as long as it has the "-i 0x1949" preceding the next bits it should work.
stunts513 said:
its because the vendor id is non standard, try
Code:
fastboot -i 0x1949 devices
as long as it has the "-i 0x1949" preceding the next bits it should work.
Click to expand...
Click to collapse
Thanks man, I was told that I need to follow the instructions from the thread bellow to update my TWRP:
http://forum.xda-developers.com/showthread.php?p=36751828
fastboot driver
Where did you get a fastboot driver, i have tried so many but all i get is [Otter2-Prod-04] in dev mngr
Hello!
I've trying to get root on nook. It gives just neverending 'registering' screen
It coonected with adb drivers and when i've launch root application I've got such screen:
{
"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"
}
How can I root this nook?
Thank you
Starting at the bottom screen:
I don't know which script (batch file) this "rootnook" is.
Apparently it is too picky about the version of adbd on your Glow2.
You can try to delete the line that causes it to stop.
The "find" and "findstr" appear to say "is not recognized as an internal or external command, operable program or batch file."
I don't know if your Windows doesn't have them or if they are named something else.
You can check by just typing:
Code:
C:\>find /?
C:\>findstr /?
The top screen we don't even know what command/script you tried.
It looks like you tried something and used the word "files" instead of an actual path.
The error looks like something out of the Glow2 shell
Code:
# busybox stat files
stat: can't stat 'files': No such file or directory
If instead of taking a graphic screen shot you should copy and paste the text and put it inside [code] & [/code]
so that those of us who don't speak Russian can more easily translate it.
How did I get that to work?
Code:
[b][code[b]][/b][/b] & [b][/code[b]][/b][/b]
Hi all many thanks to all especially j4nn to its Temp root now lets be quick:
You should have 20m kdz ( if you are not already on this version) and 20z download from lg-firmwares
1- you have to be in 20m version ( roll back using LGUP)
2- get the temp root ( usining adb CMD) when everything is ok
You should see something like this: root_by_cve-2020-0041:/data/local/tmp
3- Download the attached patched boot_a and boot_b ( these are the V20z version)
4- put them to the location Download of you phone " /storage/emulated/0/Download/ "
5 - go back to adb and input commands in shell to flash it:
adb shell
su
dd if=/storage/emulated/0/Download/boot_a_magisk_patched.img of=/dev/block/bootdevice/by-name/boot_a
dd if=/storage/emulated/0/Download/boot_b_magisk_patched.img of=/dev/block/bootdevice/by-name/boot_b
6- Now Use LGUP's PARTITION DL and untick boot_a,boot_b
{
"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"
}
after reboot connect to internet and Magisk Manager will ask to update
check your root using any root checker app
Thanks
Will this also work for lg v50 LM-V450PM Verizon version?
you should first path your model boot_a/b using magisk