I have root, but it says I don't have root - Nexus 4 Q&A, Help & Troubleshooting

ok so I had a rooted phone running AOKP and franco kernel, it was all fine. but then being the irritatingly impatient person that i am, i wanted android 4.3 so flashed the stock rom, and so everything is now stock, which is what i wanted. BUT, I can't use root! I have supersu installed but whenever an application request root...nothing. literally nothing happens, it's meant to pop up with a little box asking me if i want the app have root access, but now it doesn't come up. It may be linked to the fact that whenever I open supersu it says "The SU binary needs to be updated. Continue?" so obviously i tap continue, but then it says installing for a about half a second, then it just says "Installation failed!". I've looked around and some people say they can't update their supersu binary if they don't have busybox. When i rooted with Nexus 4 Toolkit (thanks so much mskip. also because of what i say after this it may make this thanks look sarcastic. it's not, nexus 4 toolkit has been amazingly useful to me) it told me busybox had been installed, so i just assumed that it had been. when i saw people saying that i may need busybox i download a busybox installer from Play and it told me i didn't have busybox. so i told it to install busybox and it said "Installing BusyBox v1.20.2 failed. Please try installing a different version. Please note that BusyBox installer attempts to install BusyBox to your system. Some versions of busybox may not work with some devices. If problems persist please email us and we will be glad to offer our assistance". as it suggested i tried other versions of busybox. in fact i tried every version the app would let me try, and none of them worked.
I have Android 4.3 and stock kernel

rafspeik said:
ok so I had a rooted phone running AOKP and franco kernel, it was all fine. but then being the irritatingly impatient person that i am, i wanted android 4.3 so flashed the stock rom, and so everything is now stock, which is what i wanted. BUT, I can't use root! I have supersu installed but whenever an application request root...nothing. literally nothing happens, it's meant to pop up with a little box asking me if i want the app have root access, but now it doesn't come up. It may be linked to the fact that whenever I open supersu it says "The SU binary needs to be updated. Continue?" so obviously i tap continue, but then it says installing for a about half a second, then it just says "Installation failed!". I've looked around and some people say they can't update their supersu binary if they don't have busybox. When i rooted with Nexus 4 Toolkit (thanks so much mskip. also because of what i say after this it may make this thanks look sarcastic. it's not, nexus 4 toolkit has been amazingly useful to me) it told me busybox had been installed, so i just assumed that it had been. when i saw people saying that i may need busybox i download a busybox installer from Play and it told me i didn't have busybox. so i told it to install busybox and it said "Installing BusyBox v1.20.2 failed. Please try installing a different version. Please note that BusyBox installer attempts to install BusyBox to your system. Some versions of busybox may not work with some devices. If problems persist please email us and we will be glad to offer our assistance". as it suggested i tried other versions of busybox. in fact i tried every version the app would let me try, and none of them worked.
I have Android 4.3 and stock kernel
Click to expand...
Click to collapse
Try this link: http://forum.xda-developers.com/showthread.php?t=2378413

nikhilodeons said:
Try this link: http://forum.xda-developers.com/showthread.php?t=2378413
Click to expand...
Click to collapse
it worked, thank you so much!

Related

[Q] SuperSU hidden/half enabled

I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?
DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats
WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..

CWM Installation Fails - Ouya (!) Screen

I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload ModCollection4Ouya 3.6
Open Xposed Framework and check ModCollection4Ouya 3.6 as a module
Open ModCollection4Ouya 3.6 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open ModCollection4Ouya 3.6 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Thanks for posting this, I will have time to try it to tomorrow, hopefully it fixes this issue for me as well!!
boo13oo said:
I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload Mod Collection 4.0
Open Xposed Framework and check Mod Collection 4.0 as a module
Open Mod Collection 4.0 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open Mod Collection 4.0 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Click to expand...
Click to collapse
Where can I download Mod Collection 4.0 or did you mean Mod_Collection4Ouya.3.6.apk?
Thanks I will try this.
Sent from my GT-I9100 using xda app-developers app
@Toxic_Dragon - you are correct. I meant ModCollection4Ouya version 3.6. I've updated the original post. Thanks!
boo13oo said:
I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload ModCollection4Ouya 3.6
Open Xposed Framework and check ModCollection4Ouya 3.6 as a module
Open ModCollection4Ouya 3.6 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open ModCollection4Ouya 3.6 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Click to expand...
Click to collapse
It didn't work for me.
Sent from my GT-I9100 using xda app-developers app
I had issues with ADB and fastboot until i changed the drivers for the ouya manually for every step in the device manager.
THANK YOU!!! You are the freaking man!!!! I have wasted hours trying to figure out how to fix CWM and I couldn't get anything. Finally stumbled upon this post, and I am kicking myself for not finding it sooner. Thanks a ton! :laugh:
CheeseMcGee said:
THANK YOU!!! You are the freaking man!!!! I have wasted hours trying to figure out how to fix CWM and I couldn't get anything. Finally stumbled upon this post, and I am kicking myself for not finding it sooner. Thanks a ton! :laugh:
Click to expand...
Click to collapse
What exactly did you do as I can't get this to work.
Sent from my GT-I9100 using xda app-developers app
robinscp said:
What exactly did you do as I can't get this to work.
Click to expand...
Click to collapse
I had used a different method to root and install CWM, but in order to fix the problem, I literally followed every step in order starting with sideload One Click Root. It was redundant and un-necessary, but it produced the results in the end by following step by step.

Can't Update SU Binary on Note 3???

So I just got done rooting my Note 3 with towelroot and everything went fine. I checked to make sure it worked with "Root Checker" and it said I successfully had root access. So next step I took was to download a SuperUser app from the PlayStore, and no matter WHAT SuperUser app I use, NONE of them can update the SU Binary????? so I went and downloaded "Busybox Installer" and downloaded the latest Busybox version to my Note. Then went back to retry to update the Binary but still no progess!! I'm stuck and I really don't know what else to do! I'm not trying to install any ROM or Safestrap. Just want my phone rooted to mess around with some permissions and hacked apks. So can someone please tell me what I'm doing wrong???? I've rebooted my Note COUNTLESS number of times and still SuperSU still says it fails to update the Binary! It successfully disable KNOX tho. So what can I do so that I can use my root to my full potential and update the SU Binary???
RECKLESS PAIN said:
So I just got done rooting my Note 3 with towelroot and everything went fine. I checked to make sure it worked with "Root Checker" and it said I successfully had root access. So next step I took was to download a SuperUser app from the PlayStore, and no matter WHAT SuperUser app I use, NONE of them can update the SU Binary????? so I went and downloaded "Busybox Installer" and downloaded the latest Busybox verizon to my Note. Then went back to retry to update the Binary but still no progess!! I'm stuck and I really don't know what else to do! I'm not trying to install any ROM or Safestrap. Just want my phone rooted to mess around with some permissions and no hacked apks. So can someone please tell me what I'm doing wrong???? I've rebooted my Note COUNTLESS number of times and still SuperSU still says it fails to update the Binary! It successfully disable KNOX tho. So what can I do so that I can use my root to my full potential and update the SU Binary???
Click to expand...
Click to collapse
I'm pretty sure I've read somewhere that its just a problem with towelroot.. And that same thing happened to me on my note 3. I'm pretty sure what I did was download safestrap (you can I install it after) http://forum.xda-developers.com/showthread.php?t=2517610 and flash this (chainfires supersu +binary) http://forum.xda-developers.com/showthread.php?t=2517610
If that doesn't work just either pm me or comment that it didn't and I'll see if I can find another way! And you can always uninstall safestrap once you flashed the package (don't forget to clear cache and dalvic)
Sent from my GalaxyAwesome
recovery locked ----boooo!
RECKLESS PAIN said:
So I just got done rooting my Note 3 with towelroot and everything went fine. I checked to make sure it worked with "Root Checker" and it said I successfully had root access. So next step I took was to download a SuperUser app from the PlayStore, and no matter WHAT SuperUser app I use, NONE of them can update the SU Binary????? so I went and downloaded "Busybox Installer" and downloaded the latest Busybox verizon to my Note. Then went back to retry to update the Binary but still no progess!! I'm stuck and I really don't know what else to do! I'm not trying to install any ROM or Safestrap. Just want my phone rooted to mess around with some permissions and no hacked apks. So can someone please tell me what I'm doing wrong???? I've rebooted my Note COUNTLESS number of times and still SuperSU still says it fails to update the Binary! It successfully disable KNOX tho. So what can I do so that I can use my root to my full potential and update the SU Binary???
Click to expand...
Click to collapse
clarify your Super user app from google play is 1.99r4 ....you should check THIS thread for latest SuperSu app (2.00)
http://forum.xda-developers.com/showthread.php?t=1538053
keep in mind Vzw recovery is locked, you cannot flash files on stock rom.
SS will relieve big headaches....so install it.
check upload... you get one free today
:good:
Once rooted with towelroot, I uninstalled the towelroot app. After the next reboot, SuperSU was not complaining anymore for me.
Thanks for all the help! Got it up and running in no time!
RECKLESS PAIN said:
Thanks for all the help! Got it up and running in no time!
Click to expand...
Click to collapse
What fixed your issue?
drewcam888 said:
What fixed your issue?
Click to expand...
Click to collapse
I put Safe strap on and installed it, then updated the SU Binary through custom recovery via SafeStrap.
RECKLESS PAIN said:
I put Safe strap on and installed it, then updated the SU Binary through custom recovery via SafeStrap.
Click to expand...
Click to collapse
I did the above but after opening supersu it still asks to update bibary and then fails
drewcam888 said:
I did the above but after opening supersu it still asks to update bibary and then fails
Click to expand...
Click to collapse
Did you try flashing the files he put for the Superuser + binary in Safestrap? Also do you got the latest busy box installed????
RECKLESS PAIN said:
Did you try flashing the files he put for the Superuser + binary in Safestrap? Also do you got the latest busy box installed????
Click to expand...
Click to collapse
Yes to both. Tried flashing multiple times
Any further suggestions from anyone?
drewcam888 said:
Any further suggestions from anyone?
Click to expand...
Click to collapse
Download the flashable zip of supersu. Then instead of flashing, go to the Commons folder inside it and extract the apk. Install it and then run it from app drawer.
K03WL3R said:
Download the flashable zip of supersu. Then instead of flashing, go to the Commons folder inside it and extract the apk. Install it and then run it from app drawer.
Click to expand...
Click to collapse
This just prompts SU binary update and fails.
I managed to download safestrap and have the su zip in my downloads, but dont knwo where to go from here.
I also don't use anything but stock ROM, won't I trip KNOX by flashing my stock?
First time rooting so I probably shouldn't play around with things alone. Thanks
jinh0o said:
This just prompts SU binary update and fails.
I managed to download safestrap and have the su zip in my downloads, but dont knwo where to go from here.
I also don't use anything but stock ROM, won't I trip KNOX by flashing my stock?
First time rooting so I probably shouldn't play around with things alone. Thanks
Click to expand...
Click to collapse
No you won't trip knox flashing is safe in safestrap!
K03WL3R said:
No you won't trip knox flashing is safe in safestrap!
Click to expand...
Click to collapse
Still not downloading the binary. Now I can't even uninstall it through drawer, did the flash make it a system app?
I think I should've uninstalled it before the flash.
jinh0o said:
Still not downloading the binary. Now I can't even uninstall it through drawer, did the flash make it a system app?
I think I should've uninstalled it before the flash.
Click to expand...
Click to collapse
It might've, sorry but I'm not clear on what I did..(I think I just flashed a rom) Just go to system/app and see if it's there. Delete it and reflash.
---------- Post added at 08:58 PM ---------- Previous post was at 08:35 PM ----------
And here is the version of superSU from when towel root first came out. http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
Helpppppppp
I rooted my phone with ODIN - chainfire CF-Root
After 5 minutes my root is broken !
Now ! i can't update supersu ! installtion failed !
i can't uninstall supersu or full unroot to ROOT my device again !!!
* update it from recovery ,not worked !
** delet it from recovery and root browser ! NOT WORKED
*** re-install not worked too.
Build Number : XXUGBOJ1 - Android 5
can anyone help me !?
Note 3 N9005 3G & LTE
alishirazy said:
I rooted my phone with ODIN - chainfire CF-Root
After 5 minutes my root is broken !
Now ! i can't update supersu ! installtion failed !
i can't uninstall supersu or full unroot to ROOT my device again !!!
* update it from recovery ,not worked !
** delet it from recovery and root browser ! NOT WORKED
*** re-install not worked too.
Build Number : XXUGBOJ1 - Android 5
can anyone help me !?
Note 3 N9005 3G & LTE
Click to expand...
Click to collapse
The N9005 is not a Verizon phone, this forum is about the Verizon Note 3, SM-900V
Sent from my Note 3 via Tapatalk

[Q] SuperSU binaries are not updating...

I tried everything for note 3 to get the SuperSU binaries update to date and I tried all version from the su website or play store. All I get is Installation failed. I am clean stock rooted.
Questions and Help issues belong in Q&A and Help section, thanks!
Thread moved
FNSM
What version of supersu do you have? 2.01?
yup I have the latest SU installed, the problem is that whenever the su app is updated the binaries fail to install, but if I do a factory reset and install the most current version then there are updated... Does the SU app require internet to update/download the binaries?
I was having a similar issue with SuperSU and any all other super user apps. They install, and attempt to update binaries. At this point it never completes the update or the phone crashes and reboots. Haven't quite figured out what the snag is myself.
My issue comes and goes. right now it also asks to update binaries but always fails
I had this issue when I first rooted on stock 4.4.2. So I'm guessing you're on stock? Here download this http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip and instead of installing it. I zip it and go to the common folder. Extract supersu apk and install it. Then run it from the app drawer. Tell me if that works!
That is the not the solution, I have formatted my phone multiple times. I have never been able to update binaries. There has to be a solution to this problem..
jrdnsingh89 said:
That is the not the solution, I have formatted my phone multiple times. I have never been able to update binaries. There has to be a solution to this problem..
Click to expand...
Click to collapse
Why would you format your phone?
I having this weird error when I uninstall an/any app, the android.acore app/service force closes. I tried to wipe clean many times. I just received it again. So whenever I reformat the phone, I can't update the binaries for some reason

Problem Installing Safestrap, Rooted but No SU. in FA44 Developer, 4.4.2

I just got this S5, baseband G900VVRU2AOI1. In the same developer rom I think @FancyPantsu posted about but I don't know if it's from the same source or the exact same phone model. It was flashed on odin, COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5.
It has CID 11 so I know the bootloader is locked but I'm trying to get around it as it seems from tutorials I'm reading that it's possible. I installed kingroot and it's rooted successfully according to rootcheck, busybox is also installed without problems. But the point where my phone won't follow the tutorials is that I can't seem to make a supersu user. When I open it and try to update the binary, and press normal recovery, it goes for like 30 seconds before saying it failed and I need to reboot. Which I've done over and over and can't get it to work. I've tried flashing a SuperSu zip, still no changes. I'm trying to install safestrap eventually, but when I do it goes to 100% quickly, says install successfull but never activates. I also installed selinuxmodechanger and made sure it's set to passive. There was another solution I saw, that involved Kingo Superuser and removing root in the settings, but it didn't have the permissions.
As I understand it so far, I'm stuck in this circle. Like safestrap requires su binary to install, su binary requires safestrap to install, and any way to get one of those two requires the other first. Is there anything I'm missing or should try? It'd be much appreciated!
anyone there?

Resources