Here's the scenario;
C:\tmp>adb connect tptab
connected to tptab:5555
C:\tmp>adb shell
$ toolbox date +%Z
toolbox date +%Z
EDT
$ busybox date +%Z
busybox date +%Z
UTC
$ toolbox date
toolbox date
Wed Apr 4 20:48:53 EDT 2012
$ busybox date
busybox date
Thu Apr 5 00:49:01 UTC 2012
$ ls -ld system
toolbox ls -ld system
drwxr-xr-x root root 2012-03-30 18:09 system
$ busybox ls -ld system
busybox ls -ld system
drwxr-xr-x 12 root root 4096 Mar 30 22:09 system
Any time related busybox command is reporting UTC instead of local time. Is there some way to get busybox to report local time (EDT in this case) as well?
So this thread is marked as solved but I can't see the solution?
Does anyone know how to output local time in terminal?
Related
Ah... just having fun with root...!
So, if you want to get rid of the camera sounds, follow these steps on your rooted X10:
Prerequisite:
Rooted X10 using the root tutorial (http://forum.xda-developers.com/showthread.php?t=711907).
Busybox installed (download from market)
Fire up your favorite terminal emulator on the phone or launch a shell using "adb shell" (requires android sdk) and run along:
First make the /system partition writable:
Code:
# mount -o remount,rw -t yaffs2 /dev/mtdblock2 /system
Checkout these files:
Code:
# cd /system/media/audio/camera
# ls -l sound0
-rw-r--r-- 1 0 0 9164 Feb 21 02:48 no_sound.ogg
# ls -l sound1
-rw-r--r-- 1 0 0 4384 Jun 29 04:33 af_success.ogg
-rw-r--r-- 1 0 0 6515 Jun 29 04:33 self_timer.ogg
-rw-r--r-- 1 0 0 10806 Jun 29 04:33 shutter.ogg
-rw-r--r-- 1 0 0 5987 Jun 29 04:33 start_rec.ogg
-rw-r--r-- 1 0 0 6279 Jun 29 04:33 stop_rec.ogg
And there are more directories like sound2 and sound3. OK so basically, just replace each of the sounds under soundX folder with no_sound.ogg
Code:
# cp sound0/no_sound.ogg sound1/af_success.ogg
# cp sound0/no_sound.ogg sound1/self_timer.ogg
# cp sound0/no_sound.ogg sound1/shutter.ogg
# cp sound0/no_sound.ogg sound1/start_rec.ogg
# cp sound0/no_sound.ogg sound1/stop_rec.ogg
So when you've got sound1 folder fully patched, simply copy it over sound2 and sound3:
Code:
# cp sound1/* sound2/
# cp sound1/* sound3/
Et Voila!
(You may have to restart the Camera app by killing it via Task killer application or simply restart your phone)
Further development:
Want the phone to say "Say Cheese..."?
You can basically record your own sounds in "ogg" format and replace them in the respective folder either sound1, 2 or 3... but just make sure that you record sounds which are under 5 seconds or so... longer sounds really doesnt make much sense and I really don't know how the Camera app is designed to handle it... YMMV.
You pervy, upskirt-shooting /b/-tard.
Actually, I can set there to be no camera-sound through the settings. Can't you guys do that?
pally777 said:
Actually, I can set there to be no camera-sound through the settings. Can't you guys do that?
Click to expand...
Click to collapse
yea i think I had that option before I rooted my phone... but the japanese firmware that the root relies upon doesnt !
j4mm3r said:
yea i think I had that option before I rooted my phone... but the japanese firmware that the root relies upon doesnt !
Click to expand...
Click to collapse
Slightly off-topic: Didn't Japan recently made it a law that cameras had to make a sound to avoid the secret upskirt-shots the japanese guys are so fond of?
ddewbofh said:
Slightly off-topic: Didn't Japan recently made it a law that cameras had to make a sound to avoid the secret upskirt-shots the japanese guys are so fond of?
Click to expand...
Click to collapse
thats it... this is why i wanted to help our japanese fan boys!!
or.. you know.. /system/default.prop
ro.camera.sound.forced=0
...
[Thread edited and changed, because partially solved]
Device: asus Nexus 7
Android Version: 4.2.2
Build: JDQ39
rooted
I have installed SSHDroidPro (v1.9.6) - https://play.google.com/store/apps/details?id=berserker.android.apps.sshdroidpro and Terminal IDE (v2.02) - https://play.google.com/store/apps/details?id=com.spartacusrex.spartacuside
Code:
/storage/emulated/legacy # which rsync
/storage/emulated/legacy # which mkdir
/data/data/berserker.android.apps.sshdroidpro/home/bin/mkdir
Code:
-rwx------ 1 u0_a86 u0_a86 1012309 Dec 5 2011 /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync
What do I have to do, that _this_ rsync is used by SSHDroidPro? I would like to use all shell.commands from Terminal IDE with SSHDroidPro.
It helped to copy rsync set the permissions to 755 and link it:
Code:
cp /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync /data/data/berserker.android.apps.sshdroidpro/dropbear
ls -l /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
-rwxr-xr-x 1 root root 1012309 Mar 10 01:37 /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
ls -l /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
lrwxrwxrwx 1 root root 60 Mar 10 01:38 /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync -> /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
And then:
Code:
/storage/emulated/legacy # which rsync
/data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
The rest of the posting was deleted, because it was a bug in my script. But what can I do, so the ssh-server can use the commands ot the IDE-Terminal?
I have a problem with root, but I am rooted running carbon ROM. I think is superuser in my case.I still have, or think I have at least half of my root access as I can install and use most root apps, but when removing system Apps it always says uninstall unsuccessfu, but most the time it will actually uninstall...I've tried installingg supersu, but have gotten same message on Joey krims root checker:
Congratulations! You have root access!
Super User Application Status:
SuperSU application - version 2.00 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: ls: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x 1 0 0 125420 Jun 27 09:28 /system/xbin/su
Analysis: Setuid attribute is NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: ls: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: ls: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
Root not properly returning its user id
Root group id:
Root not properly returning its group id
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Results provided on your SGH-I337M device by Root Checker Pro version 1.3.6 from joeykrim in the Android Market - http://goo.gl/NcnHn
-carbon nightly _ KT Kernal... 4.4.4 kitkat...sgh i337m.
If someone v knows the reason or a solution plz lemme know .
Thanks
Spence
Hi, I just upgraded to OxygenOS 3, I did a full wipe (including Internal Storage), and then moved back, via adb push, some folders from my apps to the /sdcard. Now there are some folders that I just can't write to them at all, not even as root. see below:
Code:
[email protected]:/storage/self/primary/tmpFolder # pwd
/storage/self/primary/tmpFolder
[email protected]:/storage/self/primary/tmpFolder # ls -l
drwxrwx--x root sdcard_rw 2016-04-09 22:24 MyFolder
[email protected]:/storage/self/primary/tmpFolder # ls -l MyFolder/ |grep 201615
drwxrwx--x root sdcard_rw 2016-04-08 21:11 201615
[email protected]:/storage/self/primary/tmpFolder # touch test
[email protected]:/storage/self/primary/tmpFolder # touch MyFolder/test
[email protected]:/storage/self/primary/tmpFolder # touch MyFolder/201615/test
touch: 'MyFolder/201615/test': Permission denied
1|[email protected]:/storage/self/primary/tmpFolder #
Notice that I have tmpFolder and then MyFolder, to which I can write without any problems, but I have a tmpFolder/MyFolder/201615/ tthat I cannot write at all. Also notice the permissions, I have the same permissions for all folders, `drwxrwx--x root sdcard_rw`.
Bump! Anyone?
Hi,
A little while back, my Z00T stopped booting (would bootloop shortly after the splash screen). Even with stock.
Looks like logcat line 187 is kicking my butt.
I can get in TWRP with no issue, so I have been tracking down the problem from there, and now suspect a corrupt /firmware partition (or a few files within).
Can a Z00T owner with the MM bootloader (preferably June 2nd 2016 update, can verify with first command below), go into TWRP, mount the firmware partition (under Mounts) and run the following two commands?:
Code:
~ # ls -l /firmware/image/keymaste.*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
-rwxrwxrwx 1 root root 180 Jun 2 2016 /firmware/image/keymaste.b00
-rwxrwxrwx 1 root root 6568 Jun 2 2016 /firmware/image/keymaste.b01
-rwxrwxrwx 1 root root 126672 Jun 2 2016 /firmware/image/keymaste.b02
-rwxrwxrwx 1 root root 8132 Jun 2 2016 /firmware/image/keymaste.b03
-rwxrwxrwx 1 root root 6748 Jun 2 2016 /firmware/image/keymaste.mdt
~ # md5sum /firmware/image/keymaste.*
ccaf75b641f15b9b8b33cefc836f29e0 /firmware/image/keymaste.b00
0a446b039708f600cebf1cba89865cd8 /firmware/image/keymaste.b01
8749be39e11338cf5a7998b57da4549c /firmware/image/keymaste.b02
f10be3e59e81f92243166b5e92fb4e47 /firmware/image/keymaste.b03
af9f26f61a4f12b82e99f028867174ea /firmware/image/keymaste.mdt
~ #
Please paste your results in a reply with the CODE tags for comparison (feel free to give me a mention or have a partial QUOTE in your reply).
Bonus points for (if you have the right date but a different hash)...
I will probably need a new firmware partition, and hope my internal SD is not dying.
If noone knows where I can find an official one, you can make one by first verifying the partition number (should be 41):
Code:
adb shell cat /proc/mounts | grep firmware
Then make an image copy to file with dd* to the external sd (using partition 41), download to PC:
Code:
adb shell dd if=/dev/block/mmcblk0p41 of=/sdcard1/firmware.img
adb pull /sdcard1/firmware.img
* Issue the command verbatim, or don't issue at all if not familiar with dd. If used incorrectly, dd can do some serious damage. Been there, done that, always check your work.
This will help me out in continuing to use this device for development purposes.
ZD551KL Selfi / Z00T. ROM CM13 for Z00T
Code:
C:\adb>adb shell ls -l /firmware/image/keymaste.*
-r--r--r-- root root 180 2016-08-05 04:59 keymaste
-r--r--r-- root root 6568 2016-08-05 04:59 keymaste
-r--r--r-- root root 126672 2016-08-05 04:59 keymaste
-r--r--r-- root root 8132 2016-08-05 04:59 keymaste
-r--r--r-- root root 6748 2016-08-05 04:59 keymaste
C:\adb>adb shell md5sum /firmware/image/keymaste.*
ccaf75b641f15b9b8b33cefc836f29e0 /firmware/image/keymaste.b00
0a446b039708f600cebf1cba89865cd8 /firmware/image/keymaste.b01
8749be39e11338cf5a7998b57da4549c /firmware/image/keymaste.b02
f10be3e59e81f92243166b5e92fb4e47 /firmware/image/keymaste.b03
af9f26f61a4f12b82e99f028867174ea /firmware/image/keymaste.mdt
Well then...that blows that out of the water - the hashes match even with a different model num and OTA date.
Unless the partition is only readable under certain circumstances (system boot not being one of them but TWRP seems more forgiving), then I will need a replacement ZE551KL firmware.img. If it is still something else, I will then be unsure how to proceed since this is a problem across multiple boot.img's so it's not a kernel or ramdisk issue yet still prevents /vendor from getting set up before /vendor symlinks to /system/vendor.
Here is md5sum of my z00t ze601kl
Code:
ccaf75b641f15b9b8b33cefc836f29e0 /firmware/image/keymaste.b00
0a446b039708f600cebf1cba89865cd8 /firmware/image/keymaste.b01
8749be39e11338cf5a7998b57da4549c /firmware/image/keymaste.b02
f10be3e59e81f92243166b5e92fb4e47 /firmware/image/keymaste.b03
af9f26f61a4f12b82e99f028867174ea /firmware/image/keymaste.mdt
Code:
-r--r--r-- system system 180 2016-08-03 00:38 keymaste.b00
-r--r--r-- system system 6568 2016-08-03 00:38 keymaste.b01
-r--r--r-- system system 126672 2016-08-03 00:38 keymaste.b02
-r--r--r-- system system 8132 2016-08-03 00:38 keymaste.b03
-r--r--r-- system system 6748 2016-08-03 00:38 keymaste.mdt