Related
[SOLVED, see below].
I've also attached the Su flashable zip to this post, as linked below
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I recently rooted my Desire using unrevoked 3.2.1 Basically, no problems so far.
However, when I have tried to run a few Apps that require ROOT access, the Superuser pop-up screen shows, EVERY TIME.
I have clicked Allow, and made sure to check "Remember", but it comes back every time for the same Apps.
I have double-checked that the Apps requesting Superuser permissions are indeed in the Superuser.apk list for Allow. They are, little green dot and all, but it doesn't seem to matter.
I tried a Batch routine in Titanium Backup, and I had to click that damn Allow button like 150 times!
Does anyone have any idea what's going here? Anyone experienced the same thing?
I wonder if it is related to what mortenmhp mentioned over in this post (post 3, "Cant remove Stock apps? Root Explorer and Unrevoked3"; sorry, I can't link yet)...
the fact that unrevoked3 still does not achieve S-OFF HBOOT and thus doesn't r/w to /system.
Btw. the thread mentioned:
http://forum.xda-developers.com/showthread.php?p=8324672#post8324672
Your problem should not have to do with this though.
The superuser app stores it's list on the data partition, and it should be able to grant su access to anything apart from rw to the protected partitions.
First off:
- Does it happen to all apps requesting su?
- Which version of superuser are you currently using?
- How did you get it? Like was it included in a rom or did you install it by flashing superuser only?
- If included in a rom, which?
And finally. You should start by trying to clear the data associated with the superuser app:
"settings -> applications -> application list* -> Superuser -> clear data button"
*I dont remember the exact name, and the charger for my desire is gone for now
If it does not work, you should also try to do a nandroid backup and a factory reset by wiping the data partition to see, if it doesn't fix it.
Thanks for your response, let me see if I can fill in some of the details:
Yes, it happens AFAIK for ALL Apps requesting Superuser access
Version: Superuser v2.3.6.1 - Added c...
Database version 5
(From the info at the bottom of the Superuser>Settings menu)
IIRC, I may have installed the App myself from the Market...? Is that even possible? Honestly, I may have jumped ahead of my knowledge in this one area. But I'm certain it wasn't from any flashing, unless unrevoked adds the App itself.
ROM, Froyo w/ HTC OTA Sept. update
I rooted with unrevoked3.2.1, but haven't flashed anything
(other than the Clockwork Mod as part of unrevoked, and, the ?re-flash? of Clockwork via ROM Manager)
The most noticeable example of this problem is Titanium Backup; I have to click Allow 14 times each time I open the App. And it is clearly listed in the Superuser List, with a green dot.
UPDATE: It is definitely possible to install this App directly from the Market, as I just re-did it. Then I Rebooted, but it all made no difference, still have 14 Allows in order to launch Titanium Backup
Results
Alright, I tried to "Clear Data", and then I did a reboot for good measure. It did NOT work.
The Superuser list was blank, but as soon as I started Titanium, I had to do the same 14 Allows. The Titanium>Log clearly shows each of them, but it's like the fact that the setting is "Remembered" doesn't have any effect.
I guess I can try the Nandroid back-up/wipe, but that just seems to be in the "format and reinstall Windows" family of solutions (no offense).
Other observation
Here's something else I noticed, may or may not be related.
I have Spare Parts installed, and I was testing the different settings.
First, Reboot/Recovery options ask for Superuser access, but then nothing happens, it just returns to the Spare Parts menu.
I'm interested in "upgrading" my boot animation (I have another thread about that), so I also tried the LeoFroyo Addon of Bootanimation>LeoFroYo BIOS
It Requested Superuser access, delayed while "Working...", and then asked to Reboot. When I clicked Yes, nothing. Just went back to the Spare Parts menu. When I rebooted manually, the stock HTC animation is still what I got.
Relaunching Spare Parts confirmed that the bootanimation setting was still on the upgrade, it apparently just didn't work.
The reason I mention these things is because I wonder if possibly I haven't achieved all the ROOT access that maybe I should have???
Any other thoughts? I'm not sure what else to try, but I can provide any other details that would be useful.
Maybe I'm just fighting a pointless losing battle on this, since I plan to flash to Cyanogen anyway. But it just find it irksome that I can't find a solution to a relatively straightforward issue.
It is because you cannot just install the superuser app from the market, because it needs root in the first place. This might just be your problem. I cant find the update.zip only including superuser right now, so if you want cm anyway, I would just go for it. Otherwise you will have to search for a zip file only including the superuser files or another rom with it included.
edit: and sorry for not replying but i have school as well
edit 2: This should be the zip file to flash to get superuser only hope you can get it to work.
Success
Yessir! That did it.
I think you're right. Don't know what I read to carelessly make me think I could just download Superuser from the Market. Actually, I'm not even too sure why its on there, since it CANNOT work if you install it that way.
I guess when I installed Superuser to grant ROOT permissions, I didn't have ROOT permissions. So, Superuser could grant other Apps ROOT (which did work), but it didn't have ROOT itself to store the Allow list. How ironic.
When I get to a computer, I'll add that linked zip as an attachment to this thread, along with some flashing Instructions in case anyone else is less familiar.
It must be pretty uncommon to do the work to get ROOT and then not flash a custom ROM with Superuser built in.
Thanks for your help. All glory to mortenmhp
okay, i was stupid. this fixed the problem for me too! thanks a lot.
Thank god for this thread
Had same problem
solved for me
And for now, i just want su, no custom rom, they seem to be sometimes unstable
Guide for dummies
just in case(copied),
Transfer this zip file file to your SD card. Remember where you saved it.
Reboot the phone into Recovery
(Boot the phone by holding down either the circle button or Volume Down button, then press the Power button. Select Recovery from the menu. (You can navigate the menus with the volume button, and make selections with the round button thingy).)
Select Install zip from SD card and navigate to where you copied the zip file and install. Watch out: Do NOT select the similar-looking apply sdcard:update.zip menu item. You have to confirm by selecting the correct ZIP file from a list.
reboot phone.
This woked for me too. Thanks a lot it was very annoying.
Oh and thanks for the dummies guide. I have not done anything but a nandbackup do it helped me feel a little more comfortable.
Great . It worked for me as well.
Thanks scott and all
I just updated to 3.0 from Market and get the binary out of date message. If I check for updates I eventually get a message stating that “The application Superuser (proceess com.nosufou.android.su) has stopped unexpectedly.
Downloading Manifest: ok
Parsing Manifest: ok
Checking Latest = 3.0
Checking installed version = force close
This is a Sprint Samsung G2 running 2.3.4. The older version I had installed was working. My issues started when I updated to 3.0 today.
I uninstalled the update – back to 2.3.6.1. The SU binary v Original button on this version reads SU binary vNULL on the 3.0 version. Not sure what that means but it seems like an issue.
I left a message on ChainsDD's web site. Has anyone else run into this problem and do you have a work around? I'm still having issues with the roll back.
Z4Root seems to work - at least it doesn't crash and seems to give me permanent root.
An update. I re-flashed Zedo's kernel and things went back to normal. I think the update I made to install CWM messed something up.
According to Super User 3.0, this kernel is improperly using root. It claims SU is in /sbin/su and shouldn't be there. I'm not an expert but this is apparently going to cause some grief if we need to update the su binary in the future.
From ChainsDD's web site at http://androidsu.com/
Binary updater fails to update binary – This usually happens because for Superuser can’t write to the system partition where the binary is installed. This can happen for a couple reasons. First, and most common, is that your device has S-ON which prevents the system partition from being written to at runtime. Even if a remount succeeds, and the system thinks that the partition is mounted as rw, you can’t write to it. There are different solutions for different devices, but the easiest usually involves simply updating Superuser through ROM Manager. If you were able to flash a custom ROM, you’ll be able to update Superuser through ROM Manager. The other reason that updating the binary fails is that your ROM Dev did something silly like putting the su binary in /sbin. I have not found a reason why this would be done, but I’ve seen it many times. The problem with putting su in /sbin is that even though you may be able to modify it at runtime, the changes will not stick over a reboot. This is because /sbin is part of boot.img, which gets unpacked and loaded at boot. The other problem with having the su binary there is that it’s almost always the first entry in the PATH. If you’re unfamiliar with the PATH, it’s a list of places that the system will look for a program, once it finds one it stops looking. Superuser will not try to update su if it’s found to be in /sbin because the change will not persist. The fix for this is not quite so easy as before and you’ll likely have to change ROM, and let the developer of whatever you were using know that they’re doing it wrong.
Click to expand...
Click to collapse
Do not upgrade to SuperUser 3.0 with this kernel. Any attempt to allow root access and remember will fail. SuperUser will not enable the remember button and until it can update the su binary and that won't happen for the above reason.
Time to roll back my SuperUser updates.
Works good for me but I am on stock kernel. Updated app and binaries with no problem. Get su and remembers apps fine.
Sent from my SPH-D710 using xda premium
The issue is the kernel. Zedo appears to have a v3 out that has the SuperUser 3.0 version so I'm going to move to that. I apparently have the v2 kernel with the older SuperUser.
I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?
dferrey said:
I've lost root access after the 6.3.1. push.
I have superuser installed.
I have File Expert configured as Root Explorer
superuser shows File Expert is allowed
When I go into File Expert I see the brief message that it has been granted superuser permissions
If I change a permission it doesn't "stick".
OTA Rootkeeper shows all boxes checked.
If I un-root in Rootkeeper- I still can't watch prime videos
I also installed root check which says I have root
Items 1-5 happened yesterday and ended up installing a new ROM from here which eventually fixed my problem.
I supposed I could go back and do that again but I'm wondering if there is another way to resolve this odd issue?
Click to expand...
Click to collapse
I have seen this happen before that you can retain some permissions with certain apps but not really remain rooted its a 50/50 shot its odd but not totally uncommon results. Generally it has something to do with apps that had su permissions prior to the update adding new su permissions don't usually occur after
I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.
Sometimes it won't push the files if they already exsist
I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.
dferrey said:
I think I've narrowed down the issue.
After rooting I have full root access including ability to change permissions.
The problem is when trying access Amazon Prime, I unroot with root keeper. It removes su from xbin as expected but when I restore, it fails. From that point on I can't change permissions or (of course) put su back.
Any ideas on why root keeper isn't restoring su?
Oh, and even when unrooting, Prime still doesn't work.
Click to expand...
Click to collapse
No its always worked like a charm for me maybe go to the market and install su from there to see if that doesn't change its strange though that prime is still detecting it. This method only works on rooted stock from what I have seen. Each time delete backup when you restore root. You can also give a shot at fixing permissions. I believe that ota rootkeeper ask for permissions to maybe at some point it was denied and it stuck.uninstall ota and reinstall hope you get er fixed
dferrey said:
I did some more playing around and noticed the su symbolic link wasn't in system/xbin.
I decided to root again.
I got this error:
mv: can't rename '/system/bin/check_rooted": No such file or directory.
I do get a message that root was installed though.
Click to expand...
Click to collapse
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
Note: I have never been a superuser on this kindle before, this is my first attempt at rooting - but the 2nd try at rooting is throwing the above error. I can see the file renamed as check_rooted.bak in the dir but cant rename with ES_FileExplorer utility as I dont have write permissions
TIA
harbinger13 said:
How did you over come this error? I am trying to re-root kindle with version 6.3.1_user_410xxxx using the Kindle utility 0.9.5 and it (sort of) aborts at this point - though it does say it has 'rooted' as a display but I do not see it; would be kind if you can give some pointers.
How does one check if Kindle is really rooted? I am trying to install Vendor.apk (google market tool) by moving it into /system/apps but can't copy it to the dir as I dont have write permission - hence my assumption is that rooting has not worked.
TIA
Click to expand...
Click to collapse
Download root checker from the market its free if you like make sure you gift the developer a buck
---------- Post added at 02:51 AM ---------- Previous post was at 02:48 AM ----------
When I used kfu the last time it took 2 times to stick don't try much until you know its rooted and you have twrp installed and fff boot loader and have made a backup you can restore if something goes gunny.
---------- Post added at 03:02 AM ---------- Previous post was at 02:51 AM ----------
If you have done everything right it should reboot a couple of times the last thing you will see is twrp screen with a big reboot button click reboot and your done you will then see the fff splash screen of the boot loader it should eventually boot into the os
---------- Post added at 03:10 AM ---------- Previous post was at 03:02 AM ----------
The same rules apply for 6.3.1 watch nat3mil do it http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US
Hi all,
on my FP1 (nice phone!) I'm no more abled to have root access. For example, ES file explorer does't go into Root Explorer mode, DiskUsage does't show Root required folders (it shows: java.lang.RuntimeException: Error: no more data message). In Superuser log:
Superuser --> Enable;
Titanium backup --> Deny;
and no more.
FairphoneOS doesn't ask me (as it should) about app su request: no dialog appair.
If I try to issue su command in terminal I get "Permisson denied" message.
Can anyone help me?
Thank you a lot
Piero
Did you by any chance activate the "deceleration needed" (or something like that) setting in the superuser settings. It is the second checkbox from above.
If it is activated and the app does not declare that it needs superuser rights it won't get any.
--Hyst
Sent from my FP1 using xda app-developers app
Root my FairPhone
I also have a FairPhone.
Cannot startup Titanium. Should I, and if so how, root my phone.
Please help.
In your feedback, please keep it simple as I am not a programmer
Thank you in advance
Hyst said:
Did you by any chance activate the "deceleration needed" (or something like that) setting in the superuser settings. It is the second checkbox from above.
If it is activated and the app does not declare that it needs superuser rights it won't get any.
--Hyst
Sent from my FP1 using xda app-developers app
Click to expand...
Click to collapse
Hi Hyst,
I'm currently having similar problems. I tried looking in the superuser settings and trying what you suggested, but no luck unfortunately.
Here is a summary of how I got to this stage:
I have recently being trying to transfer my data from my old Samsung Galaxy S4 to my FP1, using Titanium Backup. FP1 is running stock android, not the FP OS.
Unfortunately this caused issues when I tried to restore my apps and settings using Titanium Backup, resulting in the FP hanging when it got to the lock screen. I suspect this may be because of some Samsung settings that were not compatible. I did get a error message saying one of the settings files had not worked properly, but I couldn't find a way of identifying which one. I then restarted the phone as prompted by Titanium Backup, and it wouldn't get past the lock screen.
Due the phone hanging, I had to do a hard reset of the phone, following the instructions on the FP website. However, when I now run Titanium Backup it reports that it could not acquire root privileges when attempting to use "...the "/system/bin/su" command"
I've tried reinstalling both the original FP OS and stock android from the SD card, but I get an 'installation aborted' error message. Any ideas?
Thanks in advance.
Hi i Have a Fairphone fp2 andriod 7.1.2 How To Root
First of all, I have no idea where should this be posted as I am a total noobie to this forum and there is way too many categories.
I have a big problem. I installed Framaroot, used the first option (Boromir?) and have rooted my phone successfully. I tried to use *#*#supersu#*#* but nothing came up, the digits just disappeared, so I installed SuperSU from the market. I didn't do much on it, just changed the theme and hid it from my apps. I were rooted and happy for about a month, then however I got angered by SuperSU because I had to restart Hex Editor every time to get the root permissions (I were editing Terraria save files). The anger made me want to uninstall SuperSU, hoping it would just grant all the perms to the editor. First of all I disabled SuperSU, and when I realised it actually disabled the whole root, I enabled it again (unsure if it worked), I assumed everything is working, but I still wanted to get rid of the permission thing, so I pressed something like 'clean up to switch to a different superuser', and restarted my phone. I come back, and I have no root, so I went into Framaroot and used all the options, each returning that SuperSU and superuser binaries were installed. I restarted my phone, grabbed SuperSU from the Play store, just to find out that 'SuperSU binaries were not installed and SuperSU cannot install them, this is a problem!'. I then went on Framaroot, uninstalled root with all 3 options, restarted, then installed all, restarded, and the problem is still occuring. I am running Android Jelly Bean on Alcatel 4030X.
I have completely no PC access, so any USB roots or things like that are a no go. Please help!
Hi
since no-one has replied it may be because you have no paragraphs so it shows a disorganised mind....giggles
#########
Since you claim you used framaroot to install we now try to get root again
system settings security enable unknown sources
install framaroot ....if you lost it....to sdcard
install it
run it
choose first root exploit as you say that worked
if success you must reboot
###########
What you need to do if you have chainfire's superuser installed next time
go to app drawer
click on the red and yellow su icon
click on settings
change the default from .....ask each time to grant
reboot phone to test permission for apps is now auto granted. Especially test Hex Editor
###########
Altho you don't ask....there are 2 ways of updating chainfire's app
playstore ....click on update for app
open it
it will give you a dialog box to update
choose normal............it attempts to autoupdate
b) install a custom recovery and choose TWRP or CWM or CTR etc and try to update thru custom recovery
good luck