Develop Bugs

[SOLVED] Superuser Request doesn't "remember"

[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

[Q] Superuser/root permissions ICS LH2

Caution! N00b alert!
I rooted my LH2 ICS update that I downloaded through Kies before Samsung pulled it. I used the method described in this thread.
http://forum.xda-developers.com/showthread.php?t=1833579
The problem is when I shut down the phone it takes a long time (a few minutes) and eventually says something like "system has been denied superuser permission." I also never see the popup to allow or deny system root access and the superuser log says system was denied. For other apps, like Titanium Backup, I do get the allow/deny popup.
How do I give system superuser permission without seeing the allow/deny popup?
EDIT: Nevermind, the allow/deny popup came up eventually when I was doing something else. Not sure what it was.

[Q] CM file manager

I'm running CM10 and when launching CM file manager I get the message Unable to run in root Access mode. Right after I loaded CM10 it was working, i'm not sure at what point it quit working. Any suggestions?

Go to the super user app and see if it's in the exception list. If not make sure that the prompt check mark is checked them open the app and see if you get a prompt for root access. If it pops up click grant access, if not you might need to go in the super user app and clear it.
Sent from my pimped out phone

Would the exception list be under the apps tab in super user(Sorry for my noobyness)? At any rate I don't see any mention of File Manager. Super User was hanging for a few seconds on launch I think because of the log so I cleared and disabled that. Notifications are on. I don't have the elite lic, i have no qualms spending $3 for it if it is necessary. I cleared File Manager cache and when it launches i get the welcome screen followed by "Unable to run in root access mode. Change to safe mode?" At this point it crashes whether I choose yes or no.
Thanks for the response.

Yea it would be under the apps tab, try going into apps and clearing cache for the super user app it should work after that.

N-Forced said:
Yea it would be under the apps tab, try going into apps and clearing cache for the super user app it should work after that.
Click to expand...
Click to collapse
Ugh, still didn't work. Maybe I broke it cleaning out a CM10.1 install. Thanks anyways.

In the cm file manager go to settings/access mode and set it to root and it should pop up asking for root access.

Also, check your root access setting in system settings -> development. Select one of the options that allows apps to get root access

SuperSU & Framaroot - Need help!

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

Help needed! Cannot access 'SD card' files on Pixel 3XL

I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!

groston said:
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
Click to expand...
Click to collapse
Just my 2 cents worth, but I've never been a fan of toolkits. They work great sometimes, but then again they don't at times. I think it's better to learn adb/fastboot on your own. I would recommend fastbooting the factory image again, without the -w, and see if that resolves your problem. Then leave well enough alone. And uninstall the toolkit app as well if that's what it is :good:

groston said:
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
Click to expand...
Click to collapse
What were you trying/wanting to do when "checking out" the toolkit? I agree with Badger about installing the factory image, but I would go one step further and leave the -w in place just running the flash-all as is. At some point when you have done some normal work on the phone, you can run it again without the -w so you can start to understand what is not deleted as well as how to re-root since you will need to do it every month. From your description, it sounds like you have deleted some stuff on the user side that would not be restored without the -w.

Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).

groston said:
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
Click to expand...
Click to collapse
Running the flash all with the -w in place will completely wipe your device. If you don't want that then remove the -w. But, without wiping the device there may be something left over that'll continue to cause you your current problem.
Sent from my [device_name] using XDA-Developers Legacy app

groston said:
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
Click to expand...
Click to collapse
jd1639 said:
Running the flash all with the -w in place will completely wipe your device. If you don't want that then remove the -w. But, without wiping the device there may be something left over that'll continue to cause you your current problem.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly what jd said. Running flash-all with no modifications will essentially do a factory restore of that build. Removing the -w (for wipe) from the batch file leaves the non-system files/settings, etc in place and you will then need to fastboot boot TWRP.img and install Magisk. As both of us mentioned, it may be best to get over the pain of a full image instead of seeing what issues remain without the -w in place in the batch. I think the real lesson here is that the folks who make these toolkits do a lot of hard work but it is still better/safer (especially on this device) to understand doing things manually.

I reflashed without the -w and everything seems to be fine. Thanks for the help!