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.
HI, The latest version of stock firmware for galaxy mini is MJKT3, now how do I root it?
http://www.mediafire.com/?p0oh96olw9h2v72
hi
this will root all versions even the latest one? or like released by 1 minute? or new ones that has been released 1-10 seconds ago?
just try it if it worked just thank me and the Dev of the update package
if not do something else
I forgot to tell you that you will need to flash that package in stock recovery (in CWM it will not work)
It doesn't work.
it doesn't work for me too
super one click can't be used too
Flash this zip in stock recovery. http://www.mediafire.com/?dg360wy61szduv3
Sent from my SGM using Official Cyanogenmod 7.2 (STABLE)
i did flash it
---------- Post added at 06:42 AM ---------- Previous post was at 06:14 AM ----------
can
ashu.bigsmoke said:
Flash this zip in stock recovery. http://www.mediafire.com/?dg360wy61szduv3
Sent from my SGM using Official Cyanogenmod 7.2 (STABLE)
Click to expand...
Click to collapse
can someone tell me if this one will work?
17thGwydion said:
can someone tell me if this one will work?
Click to expand...
Click to collapse
no
I did try another .zip but not succeeded, it just installed super user
you can flash cwm then with the help of adb you can remount system and can push su to /system
tut
dheeraj (dhlalit11) said:
you can flash cwm then with the help of adb you can remount system and can push su to /system
Click to expand...
Click to collapse
can u give me a tutorial on how to push SU to system? or remount system? or full tutorial.. thanks
full tut plz
still no good
still no good feedback, someone try it please
flash cwm with odin
boot into it
connect your mobile with pc
configure your adb connection correctly
open cmd cd to the folder where you are having adb.exe file
copy your su file in the folder where you have adb
type adb remount
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb shell
if you will get # you are rooted
Can't set SetUID or SetGID bit.
adb shell chmod 06755 /system/xbin/su
"chmod: operation not permitted"
SuperOneClick doesn't work also.
/system partition is 100% full, you have to delete something to push su binary. (i deleted stock samsung apps, and wallpapers)
dheeraj (dhlalit11) said:
flash cwm with odin
boot into it
connect your mobile with pc
configure your adb connection correctly
open cmd cd to the folder where you are having adb.exe file
copy your su file in the folder where you have adb
type adb remount
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb shell
if you will get # you are rooted
Click to expand...
Click to collapse
you were able to push su which means you have proper access
my be permission change is not needed
try type adb shell su
or use aroma file manager v1.80 and change su permission from that
Unfortunately permission change is a must. You must set setuid and setgid (06755), because upon the su binary execution it will pass the owner's (root) permissions.
Can't use aroma file manager to set permissions because /system/xbin/su owner is root and a plain user can't change permission on files that he doesn't own.
I don't know how to solve this issue.
edit:
I can mount the system partition as rfs:
mount -rw -t rfs /dev/block/stl12 /system
Then, i can set chmod 06755 su.
But after unmount or reboot, permission will be set back to 00755...
dheeraj (dhlalit11) said:
you were able to push su which means you have proper access
my be permission change is not needed
try type adb shell su
or use aroma file manager v1.80 and change su permission from that
Click to expand...
Click to collapse
it is too much weird
can you use linux
you may be able to change the permission of the su file in Linux desktop and then can push it to system with adb
in this way permissions would remain same
Ok, it's solved!
I tried with ubuntu's adb. Unpacked the universal_gb_root_v25.zip. I mounted the system partition in adb. Then pushed all files with correct permissions to /system/xbin (the apks goes to /system/app).
First:
chown all files to root:shell
Second:
chmod 06755 /system/xbin/su
chmod 04755 /system/xbin/busybox
chmod 04755 /system/xbin/sqlite3
chmod 04755 /system/xbin/ssh
now it looks like this:
-rwsr-xr-x 1 root shell 853044 Jun 22 2011 busybox
-rwxr-xr-x 1 root shell 60264 Dec 6 10:28 dexdump
-rwsr-xr-x 1 root shell 125024 Jun 22 2011 sqlite3
-rwsr-xr-x 1 root shell 146720 Jun 22 2011 ssh
-rwsr-sr-x 1 root shell 91980 Jun 22 2011 su
It works after unmount or reboot.
Finally i have root access.
dheeraj (dhlalit11) said:
it is too much weird
can you use linux
you may be able to change the permission of the su file in Linux desktop and then can push it to system with adb
in this way permissions would remain same
Click to expand...
Click to collapse
I recently got a repaired Moto X Pure Edition running Marshmallow. I unlocked the bootloader and used fastboot to start TWRP, then set up the systemless install of SuperSU 2.79. The installation seemed successful. I watched it patch the boot image and upon reboot, the SuperSU app was available. It seems happy when I run it.
However, if I run the terminal emulator and type "su", it stalls indefinitely. Nothing happens. The SuperSU "allow/deny" dialog does not appear and nothing shows up in the SuperSU logs. The same happens when I run su via "adb shell" on my PC. TitaniumBackup also stalls when it starts with "Detecting SU and Busybox".
I originally installed SuperSU 2.79, then found the SR3 update and installed that as well. Both had the same problem. The su binary is not completely broken, as some commands work.
Some commands that work:
Code:
[email protected]:/ $ su -v
2.79:SUPERSU
Code:
[email protected]clark:/ $ su -V
279
Code:
[email protected]:/ $ su --help
SuperSU v2.79 (ndk:arm64-v8a) - Copyright (C) 2012-2017 - Chainfire & CCMT
...
Any idea why SuperSU isn't working?
Okay, here's another data point. I switched the default permission from "Prompt" to "Grant", and I can get root. The problem has something to do with showing the dialog.
I figured it out. In a previous cleanup attempt, I failed to restore the link named /system/bin/app_process that points to /system/bin/app_process64. This fixed it:
From the TWRP terminal:
Code:
mount /system
cd /system/bin
ln -s app_process64 app_process
Hi
I rooted my Nexus 5 with custom rom Paranoid androind 7.3.1(Nougat 7.1.2) using Magisk v18.0
When I run the su from adb shell, it says su: not found
Code:
C:\windows\system32>adb shell
~ # ←[6nsu
su
/sbin/sh: su: not found
I looked in Magisk Manager -> SuperUser, to check if shell needs toggle to enable root, but didnt find the entry for shell. Please help
First make sure that adb shell is working as it should and then take a look at the "Superuser Access" setting in the Magisk Manager. It should be set to "ADB only" or "Apps and ADB".
Didgeridoohan said:
First make sure that adb shell is working as it should and then take a look at the "Superuser Access" setting in the Magisk Manager. It should be set to "ADB only" or "Apps and ADB".
Click to expand...
Click to collapse
"make sure that adb shell" - How do I do this?
Superuser Access is set to "Apps and ADB" in Magisk Manager
Hello,
I am developing an app that requires su permission, whenever I reinstall it I have to grant permissions again on first launch. Is there a way I can grant the app su permissions using adb while the phone is connected to the computer?
Ideally I want a script that has:
Code:
adb install myapp.apk
adb shell su -c 'grant magisk permission'
Thanks,
Z