su not permitted error - Xposed General

After installing the xpose framework(v82) on Android 5.0 not able to execute su command in terminal emulator app(kernel version is 3.10). But able to execute su command before installing xpose framework.
And in both cases from adb I am able to execute the su command without any problem.
Any suggestion will be of great help. Thanks in Advance.

Related

Having trouble flashing a new recovery image....

Hi everyone,
I'm using a mac, trying to flash a new recovery image, more specifically the darchstar/godspeed recovery image: http://forum.xda-developers.com/showthread.php?t=672324
I've got the recovery image on the SD Card (not in any folders...right on the top level)
When I issue the flash_image recovery /sdcard/Darchstar-OC-recovery-r2.img command, it's not doing anything.
I've tried issuing it from Terminal on my mac, and using a the android terminal application.
Thanks in advance for any help!
do it with terminal emulator on the actual phone. That's what I usually do
su
flash_image recovery /sdcard/XXXXX.img
adb shell
#flash-blah blah blah.
I am trying to do this as well and when i type su into the command line it tells me permission denied. What am I doing wrong?
silentpanda said:
I am trying to do this as well and when i type su into the command line it tells me permission denied. What am I doing wrong?
Click to expand...
Click to collapse
On terminal emulator your forgetting to type su doing so will give terminal emulator root access. SuperUser Permissions will pop up and ask if its ok click allow.
Try..
Adb remount
adb shell
cd /sdcard
flash_image recovery Darchstar-OC-recovery-r2.img

[Q] Rooting problems regarding permission

Hi, I'm a newbie to android rooting and have spent the whole day trying to root my Kindle Fire HD v7.2.3.
I've used the bin4ry RunMe.bat and RootQemu.bat. I have no problems with the Qemu part but as for the RunMe.bat part I get permission problems (see picture below)
http://www.freeimagehosting.net/ikz64
The device gets rooted but the super user is no where to be seen. Therefore I can access root files but I can't write as it is read only.
I've already tried this: http://forum.xda-developers.com/showthread.php?t=2086210 (fixing a bug)
I've also tried the basics of rebooting after rooting, run as admin, locate through cmd but nothing has worked for me so far.
Anyone know what the problem is?
I was having a similar permission denied error when rooting 7.2.3. Try this and see if it helps. These commands are pulled from the Qemu script.
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
Wait for the device to reboot then run these.
Code:
adb shell rm /data/local.prop
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
reboot
Now wait for the device to reboot then check if the Qemu root hack worked correctly by connecting to your device with adb shell. You should see a root prompt.
Code:
$ adb shell
[email protected]:/ #
If you see a root prompt then re-run the RunMe.bat script and it should complete without error. The reason for your permission denied error is the script is not running as root.

adb shell

hi
i want to calibirate the accelometer sensor and it said to write:
adb shell
su
/system/bin/sensorcalibutil_yamaha
where do i need to run this commands? in the cmd of windows? or another program?
is this commands will work with 4.2.2 slim Rom?
thanks alot

[Q] Stock su binary present, uid not allowed to su

Hello,
On my Teclast P90HD running Kitkat 4.4.2, I found a /system/xbin/su binary while connected through adb. However, the su command in Terminal emulator gives :
uid 10107 not allowed to su
I guess it has to do with SELinux. After setenforce = 0 and reboot, getenforce returns 'Disabled', yet no change in Terminal Emulator.
Installing SuperSU apk from Play Store obviously fails, and I can't get it to boot in recovery to try flashing UPDATE-SuperSU-v2.46.zip.
Is there anything I can do to get that su file helpful ?
Thanks.
Hi, did you find any solution here ?
I'm in the same situation, what looks to be a solution is to recompile su.c removing the AID_ROOT / AID_SHELL related part.

Unable to use ADB Push on 3t

I'm unable to use the adb push command on my rooted OnePlus 3t running OOS 4.0.2. My device shows up after typing adb shell and im also able to execute 'su' command but after that if i try adb push <source> <destination> it returns the following
OnePlus3T:/ $ su
OnePlus3T:/ # adb push 1Carbon /sdcard/
sush: adb: not found
127|OnePlus3T:/ #
I've already downloaded the latest platform-tools and drivers.
is there any solution for this? Thanks in advance!
UTK18 said:
I'm unable to use the adb push command on my rooted OnePlus 3t running OOS 4.0.2. My device shows up after typing adb shell and im also able to execute 'su' command but after that if i try adb push <source> <destination> it returns the following
OnePlus3T:/ $ su
OnePlus3T:/ # adb push 1Carbon /sdcard/
sush: adb: not found
127|OnePlus3T:/ #
I've already downloaded the latest platform-tools and drivers.
is there any solution for this? Thanks in advance!
Click to expand...
Click to collapse
You don't do adb shell,that means your running this command from your phone's terminal which isn't what your trying to do.sp instead of adb shell just do the ADB push command
HeXDeMoN said:
You don't do adb shell,that means your running this command from your phone's terminal which isn't what your trying to do.sp instead of adb shell just do the ADB push command
Click to expand...
Click to collapse
Ohh such a beginners mistake there xD Also, im trying to push some pics via adb so that their timestamp is preserved and it requires me to run adb as root. i now tried adb root and then the push command which worked but timestamps were still altered. what am i doing wrong now?
Anyone?
Bump.

Categories

Resources