Develop Bugs

[Q] su permission denied

Hello there,
I just flashed a new ROM (Gingerbread 2.3.7) last night. After signing in the Google account everything is great; the old apps got redownloaded and all. I noticed that there is no apps listed in the superuser. I tried 'su' command in the emulator terminal & I got permission denied.
Luckily all the apps are working in perfect harmony. However, how do I get the superuser permission back? It seems like my device is not rooted. Do I need to root my phone again? Fingers crossed I don't.
Initially, I tried to flash the Ice Cream Sandwich. I tried multiple times but to no avail. I even tried to change the HBOOT (from CM7 > downgrader > Stock HBOOT) but the process failed. I afraid that this might be the cause my root access got lost. Anyone can verify this?
Thanks!

Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2

beachcomber said:
Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.

xuminarc said:
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.
Click to expand...
Click to collapse
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.

Alaa said:
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.
Click to expand...
Click to collapse
Thank you! It works!

[Q] remove su/reroot

Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?

TheAngelus said:
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
Click to expand...
Click to collapse
reroot via recovery mode, have you ever think of that ?
or try to use adb command to delete the old superuser file / replace the old superuser file with the working one

Reboot into recovery (turn on whilst holding Volume - [down])
adb uninstall superuser.apk (or whatever its named on your device)
Download new SuperUser
adb install SuperUserNew.apk (Or whatever the file name of the new one is)
Goodluck

Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk

TheAngelus said:
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
Click to expand...
Click to collapse
what is the name of the superuser that you have downloaded ? (the new one, not the old one at system/app/)
if it's the same name "superuser.apk" then the command is "adb install superuser.apk"
or go to recovery mode and apply flashable zip to replace the superuser files
download this one http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
put in your sdcard
go to recovery
apply this supersu package
more information -> http://forum.xda-developers.com/showthread.php?t=1538053

Yeh thanks its working now after reflashing the cwm superuser.

Rooting Hell Since 4.2.1

So I usually use the toolkit to root, in fact I have been for many versions now.
However with the installation of 4.2.1 I haven't been able to root at all. I use the toolkit in the same way but it simply doesn't root the phone.
So today I tried the manual way. I downloaded and installed SDK tools from google navigated to the adb folder and went through the commands. Everything seemed to go okay apart from when I typed adb shell chmod 06755 /system/bin/su. The command window did nothing.
I carried on and typed adb shell chmod 06755 /system/app/Superuser.apk, when it said "bad command" or something similar.
Rebooted the phone, no root... still.
However the Superuser app is there. So:
1) How do I delete the superuser app, bearing in mind it has system permissions. I'd like to simply start again.
2) I don't have CW recovery installed and would prefer not to bother with it if I can.
3) Just to confirm, when I root the phone, does that allow me to delete files in the /system/app folder?
4) Following this guide on rooting manually. Is that all alright?
5) In a couple of sentences, can someone explain rooting to me? From what I understood, rooting simply opens up the phone to allow access to everywhere, where you can copy and delete files, or apks.
6) If 5 is true, when following the rooting guide (4), which command am I actually telling the system to run as root? Is it simply the "root" command?
7) If 6 is true, how come when I re-boot, the phone won't let me delete things from the system/app folder?
Thanks for any help.

1) stop using a toolkit, and no you didnt root the manual way.
2) download this: http://forum.xda-developers.com/showthread.php?t=1538053 - its supersu, superuser is unreliable on 4.2+
3) fastboot flash a recovery
4) flash the supersu.zip
5) done.

Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Don't these superuser apps just manage app permissions? They don't actually enable the root access do they?
Thanks

anotherxdauser said:
Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Thanks
Click to expand...
Click to collapse
follow this: http://forum.xda-developers.com/showthread.php?t=1529058

Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.

anotherxdauser said:
Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.
Click to expand...
Click to collapse
it replaces anything in /system... basically the OS.

[Q] Root Questions

Was setting up my device for a replacement ended up keeping it, Before I attempt anything, I want to make sure I'm not still rooted.
I currently wiped all storage options (including internal) Will I have to root my device again? Or is there another way to get twrp on the device? Maybe thru adb????

To check if you are rooted you could use app like: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
or you could open up adb, enter adb shell (by writing adb shell) and asking for SU access
by writing: su
into the shell.
If you wiped internal, cache, data, you should still have root as you did not touch your system partition.
To install TWRP you can get it here: http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
extract the downloaded zip, and flash with flashify or manually by entering the commands provided in the thread.

NatusVincere said:
or you could open up adb, enter adb shell (by writing adb shell) and asking for SU access
by writing: su
into the shell.
Click to expand...
Click to collapse
I get the message '/system/bin/sh: su: not found'

tarroyo said:
I get the message '/system/bin/sh: su: not found'
Click to expand...
Click to collapse
Which means that you have no root access. You could confirm it with the app I recommended in post above or one of many apps available on google play for that.
To root your device again you could use: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
You also have other root methods available, I personally used Purple Drake method.

NatusVincere said:
To check if you are rooted you could use app like: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
or you could open up adb, enter adb shell (by writing adb shell) and asking for SU access
by writing: su
into the shell.
If you wiped internal, cache, data, you should still have root as you did not touch your system partition.
To install TWRP you can get it here: http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
extract the downloaded zip, and flash with flashify or manually by entering the commands provided in the thread.
Click to expand...
Click to collapse
NatusVincere said:
Which means that you have no root access. You could confirm it with the app I recommended in post above or one of many apps available on google play for that.
To root your device again you could use: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
You also have other root methods available, I personally used Purple Drake method.
Click to expand...
Click to collapse
Thanks for your help. I rooted successfully using this method way easier then purpledrake http://forum.xda-developers.com/lg-...lg-devices-t3129197/post61208412#post61208412

Achieving root on Xperia Z1 - 14.6.A.1.216

After dabbling around in some murky waters trying to achieve root, and going trough some 2010 stuff I did, I did discover a method I devised back then works to some extent, strangely.
Using fastboot (boot) to a TWRP recovery image (TWRP_v2.8.6.0_honami-f2fs_from_cm12.1_150423.img), mounting /system, and pushing a version of busybox, bash and using the supersu su binary already in the TWRP recovery image.
boot-new.img.bz2.zip (rename to boot-new.img.bz2 before extracting -.Just TWRP_v2.8.6.0_honami, with a different kernel and dt image included to boot from fastboot)
bash and busybox i compiled from git and debian sources yesterday/today
Basically this; (use only for reference.)
Code:
# Magically push all files in place here.
# Optionally, move /system/bin/sh out of the way and link /system/bin/sh to bash
./"$ADB" shell "chmod 755 /system/bin/bash && chown 0.0 /system/bin/bash"
./"$ADB" shell "chmod 4755 /system/bin/busybox && chown 0.0 /system/bin/busybox"
# TWRP
#./"$ADB" shell "cp /supersu/su /system/bin/_su"
./"$ADB" shell "cp /supersu/su /system/bin/su"
./"$ADB" shell "cp /supersu/supolicy /supersu/su /system/xbin"
./"$ADB" shell "cp /supersu/libsupol.so /system/lib/"
./"$ADB" shell "chmod 0644 /system/lib/libsupol.so && chown 0.0 /system/lib/libsupol.so"
./"$ADB" shell "cp -r /supersu /system/app/SuperSU"
./"$ADB" shell "chmod 0755 /system/app/SuperSU && chown 0.0 /system/app/SuperSU && chmod 0644 /system/app/SuperSU/SuperSU.apk"
#
#./"$ADB" shell "chmod 4755 /system/bin/_su && chown 0.0 /system/bin/_su"
#./"$ADB" shell "echo "busybox su -c "_su"" > /system/bin/su" # or busybox su -c "_su -c /system/bin/sh-org"
./"$ADB" shell "chmod 4755 /system/bin/su /system/xbin/su* && chown 0.0 /system/bin/su system/xbin/su*"
# Quite dangerous - Suggest moving passwd when in normal use
./"$ADB" shell "echo "root::0:0:0:/root:/system/bin/sh" > /system/etc/passwd"
./"$ADB" shell "chmod 0644 /system/etc/passwd"
Next step, to remount /system with write permissions from a normal boot, I think, would be to modify boot.img/default.prop and set "ro.secure=0"
Thought I had done this prior, I run with touch disabled as I cracked my screen (impressively massive drop of at least 30 cm! - onto object.. ) ... I could not remount system when I first tried.
Notes:
If i adb in early i can use supersu/su to gain root, when system is loaded busybox su -c ""supersu/"su" works. - NO AUTH

Hm, updated SuperSU via google play and suddenly it realized it was rooted . = ) Still keeping the supersu/su intact in /system/*bin

Thankfully I've been unsuccessful in grabbing root from /data/local/tmp this way as of now. Seems the permissions are reset. Though getting root without any auth is a serious matter no matter how you flip the coin. At least it's not as easy as pushing an archive to /data/local/tmp and running busybox su -c su. Also with a modified busybox you could easily skip the part where I write a /etc/passwd with no password.. Incredibly handy if you need root without Android running, say with setprop ctl.stop zygote, media and bootanim. But incredibly dangerous!

Fastboot to attached TWRP and install [STABLE][2016.02.02] SuperSU v2.65 - http://forum.xda-developers.com/showthread.php?t=1538053 - drop the zip to somewhere on the device and use the install function, i installed supersu via google play first. Attached is the kernel image i'm using. On a side-note, the script above failed .
Apart from this, the attached gnu-tools i will have to update... Got a neon flags optimized for out cpu and all, but that's for a different day.
Cheers, have a good one mates

Noob question: what is the difference between using this method for root and kingroot method? Which is better to use?

I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image

threader said:
I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image
Click to expand...
Click to collapse
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric

Noticed my boot img was rebooting sometimes, went off and updated my compiler toolchain and had a look at the kernel and recent developments.
Had a look at X-Honami v6 and ported some parts of that effort to the latter Sony kernel used in 14.6.a.1.216.
* Messed around with memutils and implemented ARM_PLD_64BYTE and USE_LDRDSTRD_OVER_LDMSTM atop memutils from the Xperia-dev unified kernel. - this needs some testing but appears to be stable at least with the options turned on.
* Slight overclock of GPU to 533 mhz, and underclock to 27 mhz on idle.
* Has kexec hardboot
I cannot busybox su -c su with this kernel. Which is only useful for developers anyway. You'd be wise in running some benchmarks before and after the flash.
Kernel needs to be flashed via fastboot.
Source:
https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/

DectonX said:
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric
Click to expand...
Click to collapse
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)

VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
Ok i have done step #1 by manually updating supersu and it deleted the kingroot by itself. Now i need answer for #2 only, Which recovery should i install in stock based rom ?

VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped

DectonX said:
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped
Click to expand...
Click to collapse
Thanks a lot..

I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
VikasG09 said:
Thanks a lot..
Click to expand...
Click to collapse

threader said:
I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
Click to expand...
Click to collapse
I just used kingroot, unlocked bootloader, flashed dual recovery, flashed prerooted Rom. That's it. Easy as pie.
Sent from my D5503 using Tapatalk