Hi all!
I'm facing some problems when I try to create a zip or tar compressed file from any single file or directory (what I'm actually looking for now) with shell code. How is done it on Android?
Note: I have latest version of Busybox Pro installed.
{
"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"
}
I know these commands, also I can't see zip ones on mine (are not installed)
I have this error while trying to compress by tar command:
Well done!
I have fixed the error by changing the syntaxis shell code: cd /dir && tar -cvf file.xxx FileOrFolder ; gzip -x file.xxx
-v = as the code is executed in tasker it would not need this argument, but have added it because I'll give an export function data to a variable.
.x = because I want to compress the file.
.xxx = I have not put directly the obvious: .tar, because I would like to later use 3 container types (.zip, .rar, .tar).
Thanks for your help!
Related
Im not responsible for any bricked or damaged device, remember to make backups
here are some of my analog clock widget faces with accompanying wallpapers from the screen shots they are compatible with all the Cyan builds and most hero as far as i know.
#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
for installation first extract the zip choose the one you like and rename it to AlarmClock.apk
here are 2 different ways
first from recovery terminal :
mount sdcard
mount system
cp sdcard/AlarmClock.apk /system/app/AlarmClock.apk
reboot
or you can use adb to push the file
heres the download links
clocks http://www.4shared.com/file/149881187/e1ac242f/mmclocks.html
wallpapers http://www.4shared.com/file/149881486/9060d652/wallpapers.html
heres the wallpapers
Those look pretty badass!! Nice job..
cp sdcard/AlarmClock.apk /system/app/AlarmClock.apk
cp: cannot stat 'sdcard/AlarmClock.apk': no such file or directory
I changed the name of the alarmclock and put it in the root directory of sdcard. Anything I did wrong?
nevermind, it worked. Guess a typo there.
Thanks
I'm having a problem installing CWM on my unit
XPERIA SP C5302 running on stock .205 rooted with towelroot ( this is my first time rooting )
i have my phone connected to my PC with USB Debugging checked
and followed the steps on this thread
but whenever i run the install.bat file and choose the 1st option
i always end up with "The system cannot find the path specified
{
"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"
}
Help please~
help
someone help! im facing the same problem
Hi, go DOS mode in the directory where you extracted the archive .. there is an ADB directory. Steps in this directory the command: adb devices .. if you have an answer with number, then your phone is connected...
Problem is not with the device. It is with the recovery. Retry the download. Some file might be deleted by antivirus or something? Check it out. It can't find a file it is looking for.
PS: Press thanks if I helped you!
Check if you have the ADB directory .. Option 1 uses. Look Attachment
-------------------------
-------------------------
axl409 said:
Hello, I have recently installed the twrp recovery, but when I tried to do a backup it give me an error about a path that can't be read. That path refer to the Facebook folder in /data/data/facebook-katana.
There is one file ( 6-lxk7_g5koNUrLwO82eQTzq6_w.cnt ) that can't be deleted. I tried with several file manager, like solid explorer, es file manager and the file manager from rom toolbox. Same result from the picture that I will post in this thread.
Also tried to go in recovery and use the recovery built in file manager to delete that file, but same results. How can I solve?
Here's the pic.
{
"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"
}
Click to expand...
Click to collapse
Thinking off the top of my head, this may not work:
Download a terminal emulator from play store.
Enter the following commands, one after each other:
"su"
"cd data/data/facebook-katana"
"rm 6-lxk7_g5koNUrLwO82eQTzq6_w.cnt"
It may not work, but try it anyway!
Do post your results.
Sent from my XT1068 using XDA Free mobile app
-------------------------
An experiment with boot animation, first try on the Xperia line.
{
"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"
}
Non-flashable file:
1) boot twrp
2) mount oem(using touchscreen)
3) adb shell
4) cd /oem/media
5) mv bootanimation.zip baBAK.zip
6) exit shell then adb push bootanimation.zip /oem/media
7) back on the phone, unmount oem(using touchscreen)
8) reboot.
File is below:
View attachment bootanimation.zip
----------------------------------------------------------------------
Flashable file:
1) boot twrp
2) mount oem(using touchscreen)
3) adb shell
4) cd /oem/media
5) mv bootanimation.zip baBAK.zip
6) flash zip file
7) unmount oem(using touchscreen)
8) reboot.
File is below:
View attachment Target_Dark1080p.zip
******************
modified on 11/13/18 to allow system to interrupt the animation, faster OS load times.
******************
Hello
I am going to write a script that will run another script When the USB device is connected.
I used a rule called 99-my-usb-rule.rules in /etc/udev/rules.d
All the work I did and the error log are all in the attached image file
Can anyone help me?
{
"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"
}
debug your commands/scripts in shell first , to see if they run and do what you want them to.
bash -x ./script.sh ( for detailed debugging )
then running from udev script just like running from crontab
is a very sterile environment unlike a login shell.
do "/usr/bin/env > /tmp/udev-env.txt" from udev script to see what it set and what is not.
vs "env > /tmp/login-env.txt" from a login shell , which would have all sorts of things set besides paths that might be missing etc...
and you are also not specifying any devices ( do you want script to run on all usb device connections? )
lookup udev rules if you want something a bit more specific.
also you do not need /bin/bash if you have shebang #!/bin/bash as first line of your script
just execute your /path/to/script.sh ( make sure it is an executable )