On the newest version of CMOS12 (12.0-YNG1TAS213)
Kernel - AK.265
Tried to use terminal with the command:
SU (to gain SU access)
vdc cryptfs enablecrypto inplace (password)
but it doesnt do anything it just skips down one line and basically restarts the command line.
Usually when i do this it reboots into the encryption protocol as soon as i enter that command line? anybody had this issue? Thanks
Related
My Xoom is rooted and running tiamat 1.41.
I'm trying to push a file onto the xoom and having trouble with it.
I have the Android SDK installed.
When I type ADB DEVICES, it shows my xoom listed as a long string of letters and numbers.
I figured out I could get into the shell by using ADB -s ###### shell (where #### is the numbers/letters shown as the device).
If I type remount, i get permission denied.
If I try to push a file onto the Xoom, I get permission denied.
What am I missing here and how do I mount the Xoom so that I can push files onto the it?
Anyone know where the libflashplayer.so goes? I have the official flash installed and don't see it in /system/lib
you have to cd into the directory where adb is. most people put it right on the root of there C drive so in terminal type "cd c:\android-sdk-windows\platform-tools" without quotes then type "adb remount" and you should be mounted
if you need more help with adb check out this guide http://androidsamurai.com/forum/viewtopic.php?f=12&t=4&sid=b8c229b771793d03bb84efbcf562e55b
I have tools and platform-tools directories in my PATH so I can run them from any directory. Even running it from the directory containing the executable fails with 'remount failed - operation not permitted'
you could try uninstalling and reinstalling android sdk
shobirama said:
If I type remount, i get permission denied.
If I try to push a file onto the Xoom, I get permission denied.
Click to expand...
Click to collapse
What does running "getprop ro.secure" say? (in adb shell/terminal on the tablet)
ydaraishy said:
What does running "getprop ro.secure" say? (in adb shell/terminal on the tablet)
Click to expand...
Click to collapse
Running getprop ro.secure in both adb shell and in terminal emulator on the tablet returns 1
shobirama said:
Running getprop ro.secure in both adb shell and in terminal emulator on the tablet returns 1
Click to expand...
Click to collapse
You're not in insecure mode. I thought flashing that kernel would put you into insecure mode? Maybe you need to reflash?
If you still actually have a working su binary, copy the file somewhere writeable, then su to root, then copy it from there again to the location.
im trying to just run a simple su request on my macbook. i tried "su" and it asks for a password. my usual password doesnt work. i ran a sudo su and entered my password at the request. i got back "sh-3.2#"
im am lost to say the least. sh-3.2# isnt a root shell apparently.
+1 Having this problem also, but on Ubuntu 12.04
On ubuntu, you used to have to set up a root password manually before su worked. I dont know if thats still the case.
instead of running 'su' you should be able to run 'sudo <command>'. That executes the command as root.
I'm trying to reboot from terminal emulator. What I type is:
Code:
su
reboot
or
Code:
su
reboot -p
but it always returns
Code:
Not permited
.
Note that I get the same "Not permited" both with gaining and not gaining su access before executing the reboot command.
This is a known problem (see here for example) but I haven't been able to find a solution.
Of course, root is working fine on my rom so that's not the problem.
Anyone using reboot from terminal emulator?
Thanks
nor-ric said:
I'm trying to reboot from terminal emulator. What I type is:
Code:
su
reboot
or
Code:
su
reboot -p
but it always returns
Code:
Not permited
.
Note that I get the same "Not permited" both with gaining and not gaining su access before executing the reboot command.
This is a known problem (see here for example) but I haven't been able to find a solution.
Of course, root is working fine on my rom so that's not the problem.
Anyone using reboot from terminal emulator?
Thanks
Click to expand...
Click to collapse
Entering commands
Code:
su
reboot
reboot the phone for me. I'm on latest Carbon rom.
You could try
Code:
su
shutdown -r now
but that will probably have the same result...
Is there a specific reason you want to be able to reboot from terminal? If you are looking for quicker access to recovery or bootloader and are using an AOSP rom you could enable the advanced reboot menu in developer options to get those options from the power menu. Hope this helps.
zaak00 said:
You could try
Code:
su
shutdown -r now
but that will probably have the same result...
Click to expand...
Click to collapse
It instantly reboots, without the proper shutdown routine.
UnspecialEffects said:
Is there a specific reason you want to be able to reboot from terminal? If you are looking for quicker access to recovery or bootloader and are using an AOSP rom you could enable the advanced reboot menu in developer options to get those options from the power menu. Hope this helps.
Click to expand...
Click to collapse
I'm on stock rom and I suspect that's the source of the problem: infact in the thread I linked above the user is on a stock HTC One.
I'd like to do it from terminal so that I can create a reboot event on Tasker/Llama.
Starting with Android L/Lollipop/5.0, full device encryption will be enabled by default, and for good reason. However, we slightly more security-conscious/paranoid SGS3 users have had problems for a while with using custom ROMs and keeping our encryption, as the main custom recovery with support for encryption --- TWRP --- has some incorrect build flags and other problems that aren't considered a priority. However, thanks to the very same bug report and discussion on the issue on TWRP's pages, someone found a solution which I can confirm works for me as well: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/247#issuecomment-52651670
One option would be to check whether CWM Recovery supports your device. Then you'll have access to MiniVold in recovery mode and you can mount encrypted partitions through adb. I prefer the TWR method of just typing in my password, but as long as that does not work on my Galaxy S3, this does:
adb shell
setprop ro.crypto.state encrypted
vdc cryptfs checkpw 'your passphrase here'
mount /dev/block/dm-0 /data
and when you're done backing up/installing a zip
umount /data
Click to expand...
Click to collapse
For Windows users, here's a batch file you can use to automate this process:
Code:
adb shell setprop ro.crypto.state encrypted
adb shell vdc cryptfs checkpw "%~1"
adb shell mount /dev/block/dm-0 /data
Save it under whateveryouwant.bat and then give it the password as a parameter (if the password contains spaces, enclose it in quotes).
Caveat: I've found some operations will unmount /data, which for some reason cannot then be re-mounted by any combination of these commands. Workaround is to just reboot Philz Touch Recovery / CWM Advanced Recovery, re-mount, and continue.
Hi
TWRP doesn't mount the misc partition and sometimes I have to run this code to sort out my bootloader problems.
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Is there a way I can run a file/script within TWRP to save me typing it out manually every time?
Many thanks
Will