Welcome to the Android Central Forums Create Your Account or Ask a Question Answers in 5 minutes - no registration required!
Page 1 of 2 12 LastLast
Results 1 to 25 of 29
Like Tree4Likes
  1. Thread Author  Thread Author    #1  
    Montclair's Avatar

    Posts
    52 Posts
    ROM
    Rooted/Stock

    Default SU not working for newly added "root" apps

    Phone: Galaxy Nexus on Verizon, unlocked and rooted
    Version: ICS Stock 4.0.4 OTA

    I was unlocked and rooted running stock 4.0.1 and ran the OTA and used Voodoo OTA RootKeeper to restore root. It worked and was confirmed with Root Check Basic.

    Last night Voodoo OTA RootKeeper upgraded, but it did not show that I had root.

    I then ran Root Check Basic and it said I was not rooted. I can still run ROM Manager and make nandroid backups, run Wi-Fi Tether, Titanium Backup, and other root only apps, so I must be rooted.

    I uninstalled and reinstalled Voodoo OTA RootKeeper (there are check marks for superuser app installed, Device rooted, but not for superuser permission granted)

    Superuser does not ask for my permission to grant root privilege. I tried the Got Root app ... it located superuser, but failed to obtain superuser privileges. The SU Checker app said Status: su declined | not found.

    Has anyone seen this before with Superuser?

    Please advise what I should do to get superuser to start recognizing root apps asking for permission.
  2. #2  
    2defmouze's Avatar

    Posts
    5,825 Posts
    Global Posts
    5,846 Global Posts
    ROM
    AOKP

    Default Re: SU not working for newly added "root" apps

    Flash this in recovery: https://dl.dropbox.com/u/47300967/su404.zip

    Power down, boot to bootloader (hold both volumes and power), volume scroll to recovery, hit power, in recovery flash it.
    Thanked by 3:
    Montclair and zero neck like this.
  3. Thread Author  Thread Author    #3  
    Montclair's Avatar

    Posts
    52 Posts
    ROM
    Rooted/Stock

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by 2defmouze View Post
    Flash this in recovery: https://dl.dropbox.com/u/47300967/su404.zip

    Power down, boot to bootloader (hold both volumes and power), volume scroll to recovery, hit power, in recovery flash it.
    Sounds easy enough, but I've never flashed anything before (NOOB), just have done backups in CWM. I have not renamed the file to permanently install CWM, so every time I reboot, it goes back to stock recovery. I flash CWM with ROM Manager when I want to do a nandriod backup.

    Can I just boot to CWM recovery through ROM Manager?

    Once in recovery, do I just browse to the Download folder for the zip file? (never done it before)
  4. #4  
    2defmouze's Avatar

    Posts
    5,825 Posts
    Global Posts
    5,846 Global Posts
    ROM
    AOKP

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by Montclair View Post
    Sounds easy enough, but I've never flashed anything before (NOOB), just have done backups in CWM. I have not renamed the file to permanently install CWM, so every time I reboot, it goes back to stock recovery. I flash CWM with ROM Manager when I want to do a nandriod backup.

    Can I just boot to CWM recovery through ROM Manager?

    Once in recovery, do I just browse to the Download folder for the zip file? (never done it before)
    Yes you can do it all that way. You may need to make sure the zip is on the root of your sd (meaning not in the download or any other folder, just on the sd).. move it there with whatever your file explorer of choice is (i.e. root explorer).
    Thanked by:
  5. Thread Author  Thread Author    #5  
    Montclair's Avatar

    Posts
    52 Posts
    ROM
    Rooted/Stock

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by 2defmouze View Post
    Yes you can do it all that way. You may need to make sure the zip is on the root of your sd (meaning not in the download or any other folder, just on the sd).. move it there with whatever your file explorer of choice is (i.e. root explorer).
    Sounds good. Moved it to sd root. I'll post back when done.

    Thank you!
  6. Thread Author  Thread Author    #6  
    Montclair's Avatar

    Posts
    52 Posts
    ROM
    Rooted/Stock

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by Montclair View Post
    Sounds good. Moved it to sd root. I'll post back when done.

    Thank you!
    It worked! T H A N K Y O U !

    Now, my question is ... did Voodoo OTA RootKeeper never really restore root after the OTA to 4.0.4 or did something happen to superuser after that?
  7. #7  
    2defmouze's Avatar

    Posts
    5,825 Posts
    Global Posts
    5,846 Global Posts
    ROM
    AOKP

    Default

    Quote Originally Posted by Montclair View Post
    It worked! T H A N K Y O U !

    Now, my question is ... did Voodoo OTA RootKeeper never really restore root after the OTA to 4.0.4 or did something happen to superuser after that?
    No idea, lol. But that's why we have nexii, so they can be rooted again just that easily

    Sent from my Galaxy Nexus using Tapatalk 2
    Montclair and oxymoron like this.
  8. Thread Author  Thread Author    #8  
    Montclair's Avatar

    Posts
    52 Posts
    ROM
    Rooted/Stock

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by 2defmouze View Post
    No idea, lol. But that's why we have nexii, so they can be rooted again just that easily

    Sent from my Galaxy Nexus using Tapatalk 2
    Ain't it the truth!
  9. #9  

    Default Re: SU not working for newly added "root" apps

    Fascinating! I discovered I had a root problem, just as Montclair did, a couple of days ago.

    When I tried to install CWM on my GN, it failed repeatedly. I then discovered that I haven't really had complete root since I updated to 4.0.4 back on 5/2/12 and restored root with OTA Rootkeeper. Superuser didn't have any log entries since that date, but apparently apps that had root granted prior to the update, were able to run and access root successfully, but any new ones wouldn't, and there were no messages from Superuser to show the problem.

    Long story short, the SU404 flash resolved the problem for me, for which I'm eternally grateful. I had considered several other possible solutions to try that were a bit intimidating, but this was painless, using CWM via PC, rather than flashed on my GN.

    I wish I had a better understanding of what I did to fix it, but I can be happy with the results.
  10. #10  
    2defmouze's Avatar

    Posts
    5,825 Posts
    Global Posts
    5,846 Global Posts
    ROM
    AOKP

    Default

    Quote Originally Posted by vicw926a4 View Post
    Fascinating! I discovered I had a root problem, just as Montclair did, a couple of days ago.

    When I tried to install CWM on my GN, it failed repeatedly. I then discovered that I haven't really had complete root since I updated to 4.0.4 back on 5/2/12 and restored root with OTA Rootkeeper. Superuser didn't have any log entries since that date, but apparently apps that had root granted prior to the update, were able to run and access root successfully, but any new ones wouldn't, and there were no messages from Superuser to show the problem.

    Long story short, the SU404 flash resolved the problem for me, for which I'm eternally grateful. I had considered several other possible solutions to try that were a bit intimidating, but this was painless, using CWM via PC, rather than flashed on my GN.

    I wish I had a better understanding of what I did to fix it, but I can be happy with the results.
    Lol you simply flashed an su package updated to work with 4.0.4

    Sent from my Galaxy Nexus using Tapatalk 2
  11. Thread Author  Thread Author    #11  
    Montclair's Avatar

    Posts
    52 Posts
    ROM
    Rooted/Stock

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by 2defmouze View Post
    Lol you simply flashed an su package updated to work with 4.0.4
    When the Jelly Bean OTA hits, will su need to be updated again?
  12. #12  

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by 2defmouze View Post
    Lol you simply flashed an su package updated to work with 4.0.4

    Sent from my Galaxy Nexus using Tapatalk 2
    Yup, I get that. I'm just confused by the fact that I had the latest version of Superuser (& Elite) on the GN already. I'm suspecting that there was a carryover of an earlier version of SU from the backup copy that I had established earlier with OTA Rootkeeper, prior to the 4.0.4 update.

    I just went back in to OTA Rootkeep and removed the SU backup and recreated it, hopefully with the current version.
  13. #13  
    2defmouze's Avatar

    Posts
    5,825 Posts
    Global Posts
    5,846 Global Posts
    ROM
    AOKP

    Default

    Quote Originally Posted by Montclair View Post
    When the Jelly Bean OTA hits, will su need to be updated again?
    Probably.. Those of us on JB ROMs have been using an updated SU or the new SuperSU app+binary (its a different SU regulating app but functions very similarly)

    In any case getting root on JB is just as easy as before, and when you need it we will have the files here for you to flash easily.. In fact I believe Dmmarck's JB Now thread has them in one of the first few posts anyways

    Sent from my Galaxy Nexus using Tapatalk 2
  14. #14  

    Default Re: SU not working for newly added "root" apps

    sorry to say, did this after the update (my rooted icecream nexus worked well with voodoo sound) to the new JB (with JB my voodo doesn`t get superuser rights. but I need my better sound back again.. .)
    Powered down, boot to bootloader (hold both volumes and power), volume scroll to recovery, hit power, >>>>>" in recovery flash it."
    after choosing recovery, hitting power it gets blue - then I see the green android avatar lying back with the red warning sign on it..
    ok, i`m blond ... any hints / help? Thank You
  15. #15  
    2defmouze's Avatar

    Posts
    5,825 Posts
    Global Posts
    5,846 Global Posts
    ROM
    AOKP

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by rusty101 View Post
    sorry to say, did this after the update (my rooted icecream nexus worked well with voodoo sound) to the new JB (with JB my voodo doesn`t get superuser rights. but I need my better sound back again.. .)
    Powered down, boot to bootloader (hold both volumes and power), volume scroll to recovery, hit power, >>>>>" in recovery flash it."
    after choosing recovery, hitting power it gets blue - then I see the green android avatar lying back with the red warning sign on it..
    ok, i`m blond ... any hints / help? Thank You
    That is stock recovery you are seeing, you need to flash a custom one. Download GooManager and select the option to install openrecovery. Then boot to recovery, and once there flash the superuser zip. If you don't go right to a custom ROM where this is already done, you'll want to delete or rename the file recovery-from-boot.p in your /system folder (use root explorer or something similar) so that the custom recovery will stick moving forward.
  16. #16  

    Default Re: SU not working for newly added "root" apps

    Hey, thank you very much. I installed Goo Manager, did Install open recovery, but it only shows: "no recovieries were found for your device"
    (nexus s , android 4.1.1. kernel: 3.0.31-g3b0c5d2 )
  17. #17  

    Default Re: SU not working for newly added "root" apps

    delete or rename the file recovery-from-boot.p in your /system folder (use root explorer or something similar):
    tried to delete it with astro -
    i see the folder, select it, but it could not be deleted...
  18. #18  

    Default Re: SU not working for newly added "root" apps

    ok, to delete or rename files I need reed / write permission.
    I can use su superuser, but have problems to get write permission...
    seems to use superuser rights... whats wrong?

    adb shell
    su
    mount -o remount, rw /system, mv /system/bin/aba /system/bin/aba_bad


    then I get:

    v /system/bin/aba /system/bin/aba_bad
    Usage: mount [-r] [-w] [-o options] [-t type] device directory

    what should I type in now? thank you
  19. #19  
    2defmouze's Avatar

    Posts
    5,825 Posts
    Global Posts
    5,846 Global Posts
    ROM
    AOKP

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by rusty101 View Post
    ok, to delete or rename files I need reed / write permission.
    I can use su superuser, but have problems to get write permission...
    seems to use superuser rights... whats wrong?

    adb shell
    su
    mount -o remount, rw /system, mv /system/bin/aba /system/bin/aba_bad


    then I get:

    v /system/bin/aba /system/bin/aba_bad
    Usage: mount [-r] [-w] [-o options] [-t type] device directory

    what should I type in now? thank you
    Whoa.... what are you trying to do here? lol
  20. #20  

    Default Re: SU not working for newly added "root" apps

    i want to delete or rename the file recovery-from-boot.p in the /system folder...
    there are only read- permissions...

    and therefore it needs to be writeable again...

    found that last command in an other forum to set the system writable... or is that not working...?
  21. #21  
    2defmouze's Avatar

    Posts
    5,825 Posts
    Global Posts
    5,846 Global Posts
    ROM
    AOKP

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by rusty101 View Post
    i want to delete or rename the file recovery-from-boot.p in the /system folder...
    there are only read- permissions...

    and therefore it needs to be writeable again...

    found that last command in an other forum to set the system writable... or is that not working...?
    To set the system writable via adb is simply:
    Code:
    adb remount
    But for dealing with that recovery-from-boot.p file, you can just boot up and use root explorer or something like that to get rid of it.
  22. #22  

    Default Re: SU not working for newly added "root" apps

    thank you!!
    adb remount sorry to say it shows: error: device not found.

    mount -o remount rw /system shows: mount: operation not permitted

    after su shows S but no # ...

    I think something killed my superuser rights with the automatically update to jelly bean.

    root explorer does nothing if I hit "mount r/w" button on the top... if I try to delete:
    recovery-from-boot.p cannot be deleted, because the filesystem is write-protected.

    superuser update fixer says no problems detected - checking signatures...ok.

    gomanager installs openrecovery without problems, but does nothing if I hit reboot recovery

    ota rootkeeper v 2.0.3 does "restore root" shows: root su restored...

    but status of ota rootkeeper only shows:
    superuser app installed... ok
    device rooted .... nothing
    root permission granted .... nothing
    /system supports root protection .... ok
    protected su copy available .... ok

    vodoo sound kernel shows:
    module need to be loaded:
    green:
    device Nexus S
    crespo
    kernel version 3.0.31 - g3b0c5d2
    red: superuser permissions not granted;
    you need to give root access....

    if I start with boot mode android says:
    red: Fastboot mode
    product name: herring
    HW version REV11
    Bootloader Version -
    Basebadn Version
    Carrier Info
    Serial
    red: Lock State: UNLOCKED

    if I select "recovery" with volume+button I get the lying android avatar with red exclamation mark...

    If I start normally, my voodoo sound shows: "had to be stopped.."

    The system info says: Nexus S, Android Version 4.1.1.


    Ive got no ideas, especially I would like to keep my data, numbers and apps on this phone.. Everything did run good before that automatic update from ice cream sandwich to jelly bean. But how could I get my superuser working again... I like the Voodoo Sound very much, because it allows to record videos without sound problems... the best feature of this phone but it needs the rights from the superuser....
  23. #23  
    2defmouze's Avatar

    Posts
    5,825 Posts
    Global Posts
    5,846 Global Posts
    ROM
    AOKP

    Default

    Well seems you lost root. You'll need to temporarily flash a recovery, and flashing this in recovery should give you root on JB: http://db.tt/wTBGIPFk

    After booting you'll want to open that app and be sure to update it.

    Sent from my Galaxy Nexus using Tapatalk 2
  24. #24  

    Default Re: SU not working for newly added "root" apps

    Quote Originally Posted by 2defmouze View Post
    Well seems you lost root. You'll need to temporarily flash a recovery, and flashing this in recovery should give you root on JB: http://db.tt/wTBGIPFk

    After booting you'll want to open that app and be sure to update it.

    Sent from my Galaxy Nexus using Tapatalk 2
    Thanks a lot, i broke my root after installing to JB in my Nexus S international version.
    I had root in my cell but i was denied SU permission.
    I flashed your SU for JB and everything is fine
    Thanks once again
  25. #25  

    Default Re: SU not working for newly added "root" apps

    i rooted my elonex etouch 765et with this method: Howto: Full root access on TAB274 [Archive] - Yarvik Support Forum (it was the only one that worked). and im having the same problem as Montclair. only a few apps work like titanium backup and superuser, but i dont get prompts for apps like samba file share or wifidentifier. im trying the su404 right know, i dont know if it will work
Page 1 of 2 12 LastLast

Posting Permissions