Develop Bugs

[Q] I have superuser installed on android 4.0.4 but I still can't get root access?

I rooted my phone at 4.0.2, then applied the update up to 4.0.4 and am still able to flash new versions of clockwork mod through rom manager... However, all my other apps won't be granted root access. In the superuser application, I'm running superuser v3.0.7(41) and my Su binary is at v3.0.3, for which there is an update available. However, when I try to apply the update, it tries to ask for root privileges and gets denied access... I tried reflashing su.zip through clockwork mod touch but I guess I may be flashing an outdated su.zip? Any insight into the matter would be greatly appreciated!

Same here
Same exact scenario, I went from 4.0.2 to 4.0.4, and even after a factory restore I cant seem to get root access for any app. I checked the bootloader, and I still am rooted.
Help appreciated for us both!

try this zip...flash in recovery
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
this worked for me....
if it doesn't clear superuser data first then try it again.

ezcats said:
try this zip...flash in recovery
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
this worked for me....
if it doesn't clear superuser data first then try it again.
Click to expand...
Click to collapse
CWM Recovery is not working for me, and I cant flash it due to no permission for elevated commands although its rooted.

Clockwork recovery does not require root if it is already installed. If not, fastboot clockwork recovery.

I had the same issue and all you have to do is reroot the phone and all will be well then download and install ota rootkeeper for the future. The update breaks root but doesn't block it

evanextreme said:
CWM Recovery is not working for me, and I cant flash it due to no permission for elevated commands although its rooted.
Click to expand...
Click to collapse
Flash from recovery, not an app.....
Sent from my Galaxy Nexus using xda premium

jerseyh22accord said:
I had the same issue and all you have to do is reroot the phone and all will be well then download and install ota rootkeeper for the future. The update breaks root but doesn't block it
Click to expand...
Click to collapse
This did the trick!
Had this same problem earlier

I need help
I am having the same problem. I am a noob and it sucks cause I can't figure it out. I can't even go into recovery since I installed 4.0.4 someone please dumb it down so i can understand

Install busybox free, then install titanium backup free. Open busybox and click inatall. Then run
Titanium backup, it will ask you do you want it to configure root, accept this. please note After completing busybox steps reboot. Then after titanium backup steps reboot again
Did this help?
If not pm me and il see if i can help

I can't use any of my root apps. My SU isn't working. I'm pretty sure that's causing the problem. I tried updating the binary (I read that somewhere) but the process fails. Is there a way I can do it manually?
Sent from my Galaxy Nexus using XDA

brightsideme said:
I can't use any of my root apps. My SU isn't working. I'm pretty sure that's causing the problem. I tried updating the binary (I read that somewhere) but the process fails. Is there a way I can do it manually?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Try flashing this:
http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip

Can you please explain how to flash? I don't want to mess it up lol
Sent from my Galaxy Nexus using XDA

brightsideme said:
Can you please explain how to flash? I don't want to mess it up lol
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Do you have CWM installed yet?
If not...
I'd recommend simply starting from the top and using my guide.
But if you have CWM:
Just navigate to "Install Zip From SD Card"
"Choose Zip"
And find it.
Yes to install.

I tried going to clockworkmod recovery but I just get that error. Last night I went into recovery using the cmd on my computer. I tried flashing that same file but it just failed.
Sent from my Galaxy Nexus using XDA

brightsideme said:
I tried going to clockworkmod recovery but I just get that error. Last night I went into recovery using the cmd on my computer. I tried flashing that same file but it just failed.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
boot to clockworkmod manually, than flash the superuser zip from here http://www.box.com/s/jvcf196j7x8f8vrc9cyt (this does not require busybox, that why the other su zip was failing)

I can't go to recovery from my phone. When I try I just get the Droid with a red exclamation point. I'll have to do it from a computer. Only problem is that I'm at work. I'll see if I can get to one ASAP
Sent from my Galaxy Nexus using XDA

brightsideme said:
I can't go to recovery from my phone. When I try I just get the Droid with a red exclamation point. I'll have to do it from a computer. Only problem is that I'm at work. I'll see if I can get to one ASAP
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
That is the stock recovery that you're getting to.
Use my guide.
And navigate to the part about flashing a custom (CWM) recovery and flashing SU.
The SU in my post is updated to work for all users...the one you're using won't work on 4.0.4.

Jubakuba said:
That is the stock recovery that you're getting to.
Use my guide.
And navigate to the part about flashing a custom (CWM) recovery and flashing SU.
The SU in my post is updated to work for all users...the one you're using won't work on 4.0.4.
Click to expand...
Click to collapse
but i think the su zip in ur post, only work if there is busybox installed...and the stock rom doesn't have it...
this the updater-script of ur su.zip: run_program("/sbin/busybox"...
that work only on custom roms, that usually have busybox preinstalled
check the different syntax in the other su zip posted above, it doesn't require busybox

andQlimax said:
but i think the su zip in ur post, only work if there is busybox installed...and the stock rom doesn't have it...
this the updater-script of ur su.zip: run_program("/sbin/busybox"...
that work only on custom roms, that usually have busybox preinstalled
check the different syntax in the other su zip posted above, it doesn't require busybox
Click to expand...
Click to collapse
nope, he was getting a permissions error because rom manager didn't have root access, that was the issue there.
edit: re-read the post, yes, you might be right about busybox in stock recovery, although i believe cwm has a set of minimal busybox tools.
if manually booting into recovery by shutting down the phone, pressing power+vol up until Google screen appears, doesn't take him to cwm but to stock recovery, he doesn't even have cwm installed, which could very well be the case, since stock rom default behaviour overrides any existing recovery when flashing.

Accidently flashed wrong SU binary, need help!!

My phone is a Huawei u8160 (AKA Vodafone 858) and I rooted it a long time ago with z4root and have had no problems eversince.... until recently when my mate got hold of my phone and accidently flashed an experimental/beta (possibly a binary for x86 systems) SU binary through CWM recovery. I thought I could fix this quite easily by using z4root to uninstall root and then do a fresh reinstall, but it would force close on me after a few seconds. I tried this method with both temporary and permanent root options but nothing worked. The button that pops up saying ''unroot'' wasn't there even though there is still a SU file in /system/xbin as it showed in Rom toolbox. I soon realised that the version of android i was running on my custom rom was not compatible with z4root, so i searched for how to root android version 2.3.9 pro. I dont know the name for that version and it must have been a bit of a flop because google didnt know it either. I dont know how akiro-E (the developer that cooked up the rom) got his hands on version 2.3.9 pro but i recommend to other devs reading this to not use it as there is not much compatibility.
Anyway, i found this apk made by chainsDD called gingerbreak and decided to give it a go. It said that it needed debugging on and that it might take a while, so i did that and pressed the root button. I left it to do its business, but 15 minutes later it was still trying to run the exploit so I stopped and removed it. When i got home later on i searched up how to root any phone and it came up with the pc program 'superoneclick'. I got it, opened it and clicked unroot. It did its thing but failed to remove su and the superuser app like it was meant to. So then i clicked on root and shell root but it did not reinstall properly and got the same error as in unroot error. I did all the steps multiple times but it still wouldnt remove/replace su from the xbin folder. I then reinstalled superuser 3.1.3 and tried using the binary updater on there. I noticed that the su installed was called 'legacy'. The updater was having a spaz and didnt want to update so i tried manually removing su with the root explorer in rom toolbox butvrealised that you needed root (a working one) to do that. Then i found an app on my sd called root cleaner. I tried quick and full cleaning but to no results except for a force close multiple times. I tried to fi the foce close issue by running the script for this in rom toolbox but you need root (surprise surprise) Then i tried flashing cwm recovery through fastboot as i have done lots of succesful times before. It flashed after putting my phone in download/debug mode (power and volume down) but i cant boot to it as you need proper root rights to do that.
I am going to use total commander to check if the permissions are set to 644 for the su binary, if not ill attempt to change them.
I know this a long desciption and technical question but does anyone know any ways to delete the retarded root from my phone and help me restore root as normal? This is a question for the more experienced users and devs on this forum but any help will be appreciated, cheers.

If you've got recovery, you can install one of these zips in recovery mode.
Google "superuser 3.1.3 arm signed zip" and click the first link that comes up - the androidsu one. Then download the superuser zip package that suits your device to your phones internal storage, reboot into recovery, install the zip and there you go! Your root is fixed.
Sent from my LG-E400 using xda app-developers app

Thanks
@odigITECH thanks for the help. I fixed the problem using your method. . . kind of. I flashed recovery via fastboot and then just flashed another rom from my sd card via cwm after I rebooted. Thanks for the help anyway, much appreciated!

No probs
Sent from my LG-E400 using xda app-developers app

[Q] Problems with ROM flashings (i9195)

Hello everybody,
I have a quite stressful situation with my s4 mini right now and I need your expertise.
It goes like this:
I was perfectly happy with my stock rom but for some reason I got this crazy idea of rooting and installing a custom rom.
So I followed the steps on this post: http://forum.xda-developers.com/showthread.php?t=2364980
After CWM was installed and before the phone was rooted, I made a complete backup via CWM (Backup1) and then installed the rootkit (as mentioned on the above post). After successfully rooting it I made another backup (Backup2), you know, just in case
Then I followed the instructions on the CyanogenMod wiki (http://wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx#Installing_CyanogenMod_from_recovery) and installed it on my phone. It worked perfectly and I had CyanogenMod installed. But after playing around with it a bit, I realized that I didn't like it that much for various reasons. So I decided to go back to my original ROM. So I restarted in recovery mode and restored Backup2. Well this is where the problems start
The phone would start but once it boot up everything kept crushing. I kept getting messages every 10 seconds that gapps is not responding and nova launcher is not responding and the play store is not responding, etc. And in general you couldn't use it. So I tried once again restarting in recovery mode and restored Backup1. But again the same thing. Everything kept crushing.
What I want now is to have my original stock rom rooted. Problem is, I don't know where to find it. All I found was this: http://forum.xda-developers.com/showthread.php?t=2375527&highlight=9195 but the download links don't work. Plus I don't know what my firmware's code is (eg I9195XXUAMF5)
Can anyone help?
PS. I live in Denmark and I bought here. Also the phone is the i9195 model with 8gb.

s4 mini
Go to CWM and wipe it or try to fix permissions

Factory reset from recovery should fix the force close.
Sammobile.com for firmwares
Sent from my GT-I9195 using xda app-developers app

mnezo said:
Factory reset from recovery should fix the force close.
Sammobile.com for firmwares
Sent from my GT-I9195 using xda app-developers app
Click to expand...
Click to collapse
Thanks! That helped a lot.
So now I downloaded and successfully flashed what Sammobile.com suggests is my stock firmware.
I followed again the procedure to root my phone (http://forum.xda-developers.com/showthread.php?t=2364980) but although superSU is installed, I don't think I have root access.
What happens is that first of all superSU says that it needs to update the binary but it when I click "continue" it fails to install. Then I get a security warning that superSU is trying to access protected files and that it was blocked. SuperSU asked me if I want to disable KNOX. I said yes so I don't get those messages anymore. But still superSU can't update.
The other thing is that the apps don't actually have root privilages. For example, when I try to enable root on ES File Explorer, I get the prompt to grant root access, and I select grant. But I still can't open specific folders in the file system. For example the /data folder is shown completely empty.
Also other apps don't behave like rooted.
Any thoughts??

flash GT-I9195_Kernel_v1.zip or Vikinger

mnezo said:
flash GT-I9195_Kernel_v1.zip or Vikinger
Click to expand...
Click to collapse
Thanks!
That worked
I hope that kernel doesn't have any bugs

[Q] Root problems - Titanium Backup is granted root but fails to use it

I installed Philz touch recovery earlier, went to reboot and it told me I wasn't rooted. So i let it root me, and nothing happened (it rebooted but no superuser or anyhing, and no root apps worked). I used Dr Ketan's tool, and let it root, install busybox and remove knox.
I updated superSU (it force closed by default), and then titanium backup asked for root and I granted it. But it says root access - failed."The attempt was made using the "/system/xbin/su" command."
I tried to uninstall gmail through ES file explorer, but it says "unfortunately, ES file explorer has stopped" if you try and do it. Adfree android worked though, and so did rootchecker ("success"), as well as busybox updating and an app that reboots you straight to recovery.
I'm really confused and could do with this root working :S Thanks!

Try flashing this zip
https://www.dropbox.com/s/ylh5ckorv089e4h/UPDATE-SuperSU-v1.93.zip
It solved my similar prob.
Regards.
Sent from my GT-N7100 using XDA Premium 4 mobile app

Tamen said:
I installed Philz touch recovery earlier, went to reboot and it told me I wasn't rooted. So i let it root me, and nothing happened (it rebooted but no superuser or anyhing, and no root apps worked). I used Dr Ketan's tool, and let it root, install busybox and remove knox.
I updated superSU (it force closed by default), and then titanium backup asked for root and I granted it. But it says root access - failed."The attempt was made using the "/system/xbin/su" command."
I tried to uninstall gmail through ES file explorer, but it says "unfortunately, ES file explorer has stopped" if you try and do it. Adfree android worked though, and so did rootchecker ("success"), as well as busybox updating and an app that reboots you straight to recovery.
I'm really confused and could do with this root working :S Thanks!
Click to expand...
Click to collapse
Download ROM manager from Play Store and run Fix Permisison, After RM done reboot your phone and then try.

Maybe you have to update su.
Sent from galaxy n7105

[Q] Towelroot -> Xposed -> Everything Force Closes

Problem with Xposed Installer.
Scenario:
Device Status before problem:
Prior to rooting with Towelroot, installed SuperSU first.
Rooted with Towelroot
Opened SuperSU APK and installed binary via the normal method.
Installed Titanium Backup
Backed up some apps and APKs.
Rebooted device several times and works great.
Android version: 4.3
Baseband: P605XXUBMJ4
Build number: JSS15J.P605XXUBMJ9
Steps to produce problem:
1) Download Xposed Installer from Xposed website, I assume it is the latest.
(de.robv.android.xposed.installer_v32_de4f0d.apk)
2) Installed the said Xposed Installer APK.
3) Tap on Install/Update, prompted that device will restart in a few seconds.
4) Device rebooted.
5) Reached lockscreen:
- Entered gesture 3 x 3 security swipe prompt.
- Touchwiz started to force close.
- Then everything else starts to force close as well.
Steps to recover from problem.
1) Hold capacitive menu button and went to S Finder screen.
2) Search for something random.
- Internet is not working even though I have 3G/Mobile internet enabled.
3) Continue search using Google, select a browser. (I used Firefox)
4) Navigate to Xposed installer APK using Firefox (file:///) which resides in my external SD card.
5) Click on the APK and install as usual, then open the installed APK.
6) Uninstall Xposed framework.
7) Reboot.
8) Everything works fine again.
Dared myself to try Xposed again. Got into the same problem. Trying to reinstall Xposed Installer but it is taking so much time. Still installing as
we speak.
Now I am trying to find out where does Xposed APK reside in, so I can launch the app manually.
UPDATE: Managed to uninstall Xposed framework after a LONNNNGGGGG wait. I am not daring enough to try it again. =_=!
Questions:
1) How to run Xposed without everything force closing?
2) What can I do to fix this?
3) Where does Xposed APK reside in the system folder?

Hi
Suggest you unroot your device and reinstall stock firmware via odin. Clear cache/dalvik and factory reset device. Then root again with towel root, install latest chainfire su to disable knox and install Xposed. This should clear your issues. I don't have similar problems on my p605 with Xposed.
Sent from my SM-N9005 using xda app-developers app

tonycfc said:
Problem with Xposed Installer.
Click to expand...
Click to collapse
Sure it is not the rooting method? No problems here with Xposed Installer...Rooted with chainfire's auto root (I don't give a sh**t about crappy Knox), 4.4.2, MagazineUX Rom

sphuyal said:
Sure it is not the rooting method? No problems here with Xposed Installer...Rooted with chainfire's auto root (I don't give a sh**t about crappy Knox), 4.4.2, MagazineUX Rom
Click to expand...
Click to collapse
No, it's not the rooting method. I used towelroot for my P605 + Xposed. I have no problem.
Sent from my SM-N9005 using xda app-developers app

Hi all. I did not manage to solve this problem but I took the plunge and flashed P605XXUCNE2 4.4.2 and rooted it with towel root, installed SuperSU and everything went well. No wipe as well.
I also flashed TWRP and did a nandroid backup. I don't really care about Knox anymore. ^_^

shayind4 said:
Hi
Suggest you unroot your device and reinstall stock firmware via odin. Clear cache/dalvik and factory reset device. Then root again with towel root, install latest chainfire su to disable knox and install Xposed. This should clear your issues. I don't have similar problems on my p605 with Xposed.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
This helped now phone Is fixed on stock firmware