my atrix 2 was rooted and everything was good. a few days ago I copied a new su file using "Absolute System root toolbox" from sdcard to /system/bin, now i am still struggling to find a way to change the permission of the su file. looks like it's locked as a read-only file, now I can not use root explorer to change permissions of files or folders, and on my laptop using adb it gives me a $ rather than a #, it reads "operation not permitted".
any clues? thanks in advance!
**One quick note** If you got the 2.3.6 update, zerg doesn't work. In that case you will need to wait for a new root method to be made available.
This comes from the rooting thread in the dev forum. None of it is my work... You need a root shell to reset the permissions on su. Here are some instructions that should allow you to do that.
Download exploit ---> Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> chmod 4755 /system/bin/su
Hope this helps / works...
Yeah you basically need to re-root your device.
Hello Everyone!
I have spent the last 4 full days trying to fix device and every road I go down leads to a dead end. At this point my frustration and exhaustion has got to the point where I am afraid to proceed for fear I will destroy my phone making the whole ordeal pointless. I will spare you all the details as they are comical at this point and try to provide only the basic information. I used the nexus 5 root kit to gain root access in order to repair an issue with my phone and this is what root checker pro said...
Congratulations! You have root access!
Super User Application Status:
SuperSU application - version 2.02 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /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 root root 125424 1970-01-05 10:08 su
Analysis: Setuid attribute is not present BUT root user ownership is present. Root access IS correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /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:
uid=0(root)
Root group id:
gid=0(root)
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: shell (non root) user - ro.secure=1
Results provided on your Nexus 5 - Android 4.4.4 device by Root Checker Pro version 1.3.7 from joeykrim in the Android Market
If someone could provide me with instructions on how to proceed I would be eternally grateful, I have become a wash in all the information out there as well as paralyzed by it. Even better if anyone has a spare few moments having a skype buddy there while I execute the instructions would be so very comforting although I realize people have better things to do with their time.
The one good thing to come of this is I now have a keen interest in Android development and look forward to finding and taking classes so in future I am not such a lost fool.
Very grateful for any help offered,
Garrett
[email protected]
Skype ID: thisguyto
1. using fastboot, unlock your bootloader. if its unlocked, ignore this step.
2. flash a custom recovery via fastboot.
3. flash SuperSU via your custom recovery.
4. boot up with root.
no root toolkit needed.
or, read the stickie threads here on xda to get detailed instructions http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
hey guys,
get this files then, you will find MRW folder inside the zip file , put that mrw in internal memory card
• Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files
• Open Terminal emulator and type :
Su
• Allow root permission
• Type :
sh /sdcard/mrw/root.sh
(put space after sh , then /sdcard/mrw/root.sh)
• It might display some error ignore these errors, at the end it will launch supersu or open supersu manually.
• Update SU binary normal, then reboot
ALSO DELETE THE KINGUSER.APK ( superuser.apk) from /system/app manually, before reboot
and its done , i checked nicely , its working awesome
link for replacer files :- https://drive.google.com/file/d/0B7I...ew?usp=sharing
dont flash these files , (method working on lollipop 5.0, work on kitkat , jellybean also )
CREDIT : 1) Chainfire for awesome SUPERSU ( PLS DONATE HIM AND SUPPORT HIM> http://www.chainfire.eu/),
2) edwuard
3)ME
4) MY PARENTS and WIFE CLAIRE
File Missing
It's show to check the URL. Have you deleted the file ?
nope , the link is working , still i attach files here ,
vasansrine said:
It's show to check the URL. Have you deleted the file ?
Click to expand...
Click to collapse
check the attachment
is it safe
I am runing on android lollipop xolo prime please tell me is it safe
---------- Post added at 08:02 AM ---------- Previous post was at 07:20 AM ----------
So so so thanks I am trying to this this for year but now I have done with your amaging post I can't believe I so fear to doing this but successing I am so happy now thank thank you very much
Interesting. What do the am and pm commands do?
Seems to have worked on my Amazon Fire (KFFOWI/Ford), but I may have left Kingroot installed before rebooting
com.kingroot.kinguser:services
This method works. I tried it myself. The downside is that Kingroot will leave residual files and services even after you have enforced SUPERSU and updated it's binaries. Anyone know where I could locate KSysService and com.kingroot.kinguser:service?
Success on KFFOWI 5.1.2 via adb on Linux
I just tried this on KFFOWI with 5.1.2. It worked, but there were errors output by the script and I don't know if that's ok. It appears to be ok though. Here's what I did (on Linux):
Code:
$ unzip mrw.zip
$ cd mrw
$ adb shell
[email protected] $ cd /storage/emulated/legacy
[email protected] $ mkdir mrw
[email protected] $ exit
$ adb push busybox /storage/emulated/legacy/mrw/busybox
$ adb push root.sh /storage/emulated/legacy/mrw/root.sh
$ adb push su /storage/emulated/legacy/mrw/su
$ adb push Superuser.apk /storage/emulated/legacy/mrw/Superuser.apk
$ adb shell
[email protected] $ su
[email protected] # sh /storage/emulated/legacy/mrw/root.sh
The output looks like this (aparently errors are ok?)
Code:
---------------------------------------
---------- Made By : BEINGTEJAS -------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
Failure [DELETE_FAILED_INTERNAL_ERROR]
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
rm: /system/app/Kinguser.apk: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/bin/install-recovery.sh-ku.bak: No such file or directory
rm: /system/bin/install-recovery.sh-ku.bak: No such file or directory
pkg: /sdcard/mrw/superuser.apk
Success
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
chattr: stat /system/etc/install_recovery.sh: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
Then I followed through the install of SuperSU on the device, using the "normal" option and allowing it to remove the other SU that it detected. Finally, I rebooted the device and performed a quick test:
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # exit
[email protected]:/ $ exit
The SuperSU icon is on available, the KingUser one is gone. Accessing root goes through SuperSU so it looks ok. If any of those errors pose a problem though, let me know!
when i type su and enter, I get a message "Daemon is stop" and i cant get root access, i have tried to reinstall emulator, re-allow kinguser root, but nothing works, busybox is installed
Edit: NVM, got it working with the SuperTool
The script managed to remove Kingroot, but SuperSU normal binary installation still fails. Plus, the Rootchecker now says that the root is not properly installed.
Should I install Kingroot again in order to gain root and try SuperSU again?
I am using Android 6.0. I have an application that copies executable file (compiled for arm) to the app data folder. In the app I have set the executable permissions to:
Code:
chmod 777 /data/data/pckname/files/executable
when I try to run the file using adb shell I get this message
Code:
/system/bin/sh: /data/data/pckname/files/executable: can't
execute: Permission denied
I tried
Code:
ls -l
and this is the result
Code:
-rwxrwxrwx u0_a54 u0_a54 1620988 2016-12-14 13:59 execFile
Is the problem in the user and I must be a root to do it?
DohaE said:
I am using Android 6.0. I have an application that copies executable file (compiled for arm) to the app data folder. In the app I have set the executable permissions to:
Code:
chmod 777 /data/data/pckname/files/executable
when I try to run the file using adb shell I get this message
Code:
/system/bin/sh: /data/data/pckname/files/executable: can't
execute: Permission denied
I tried
Code:
ls -l
and this is the result
Code:
-rwxrwxrwx u0_a54 u0_a54 1620988 2016-12-14 13:59 execFile
Is the problem in the user and I must be a root to do it?
Click to expand...
Click to collapse
Greetings and welcome to assist. Yes I think you need to be root to change the permisisons
Regards
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. Yes I think you need to be root to change the permisisons
Regards
Sawdoctor
Click to expand...
Click to collapse
But the permissions already changed and the file is in the data folder. It just wont execute. but I still think you are correct it wont execute until I run using user root
I'm trying to modify the cacerts file on the system partition of a non-Google Play emulator to avoid annoying messages during development / Pen Testing on Nougat, related to an app I'm working with and I'm running into some issues. Even though I successfully copy the file to the /etc/security/cacerts/ directory and have confirmed the certificate is in the same format, its not showing as a Trusted Credential and gives a permission denied error when utilizing ls -al as a regular user (but displays fine as root). Permissions and file ownership are the same on all certificates, including mine; but my certificate shows up as "unlabeled" when I do an ls -aZl, verses all the working certificates show a label of "system_file". As a result, I'm assuming this is due to SELinux on the emulator, but I'm new to SELinux and I can't figure out what is setting that label. I utilized the following tool to convert file_contexts.bin, but nothing in there appears to reference cacerts. I'm not quite sure where to poke next.
In case it matters, and from a techniques standpoint in case anyone wants to get as far as I have in this:
I utilized Arsenal Image Mounter to mount the system.img file as writeable that was found in the following location:
%USERPROFILE%\AppData\Local\Android\Sdk\system-images\android-25\default\x86_64
Utilizing that I copied my certificate to /etc/security/cacerts/9a5ba575.0 (A copy of this cert is attached as 9a5ba575.0.txt ) . (I did this both as a copy & paste of the local file in Windows, and by duplicating an existing working certificate file utilizing a cygwin bash, and replacing the file contents. Neither method made a difference)
I then built an Android Virtual Device (AVD) and booted it up.
The command ' adb shell "ls -aZl 9a*" as non-root yields (First result is my cert, 2nd is another cert):
Code:
ls: /etc/security/cacerts/9a5ba575.0: Permission denied
-rw-r--r-- 1 root root u:object_r:system_file:s0 7537 2018-08-03 14:57 /etc/security/cacerts/9ab62355.0
The same command run as root yields:
Code:
-rw-r--r-- 1 root root u:object_r:unlabeled:s0 4246 2022-07-06 10:50 /etc/security/cacerts/9a5ba575.0
-rw-r--r-- 1 root root u:object_r:system_file:s0 7537 2018-08-03 14:57 /etc/security/cacerts/9ab62355.0
This shows my certificate is being loaded properly, but has "permission" issues. As you can tell from the ls -aZL output though, the only difference is the security label.
Thanks for your help!