Database Develop

SOLUTION :Superuser not remembering requests

Ok so we all are annoyed about superuser app not remembering requested permissions. So i was just experimenting around and that part worked out for me Here is the solution:
First:Check If the superuser remembers granted and denied permissions to an app by launching a root app giving it root access. And relaunching it again if it shows a popup to show requests. If no then move to further step
Second Step: Download super su app(by the great chainfire) and check if it gives installation sucess. If no then move ahead
Third : Download Su update fixer from the Playstore
Fourth:Run the su update fixer app.If it asks for permission then grant it.Mostly it will force close. (Dont worry it should force close).Now if u observe on the device u might not see the super user app.Dont worry its natural.
Fifth:Now download superuser app from the market (mine is v3.1.3(46) ) try to get that one.After the download is completed run the app.
Sixth:Mostly it will force close.Reboot your device
Seventh: once the device is started. Run the superuser app.
Voila It will now remember all your permissions without fails
Incase it does not remember Use the super su app and when it prompts for the installation of binaries allow the superuser request
Supersu works flawlessly
NOTE:I am not responsible if any damage occurs to your device. I just shared it with you because it worked for me on CM9 CM10 and PAC roms

Adi1995 said:
Ok so we all are annoyed about superuser app not remembering requested permissions.
Click to expand...
Click to collapse
It solved for me, my set is Samsung Galaxy Nexus, Android 4.1.1, just root it recently via "Galaxy Nexus ToolKit".
However, the superuser will not remember, and keep asking.
Note: the superuser by ChainsDD, not install via play market, but install from "Galaxy Nexus ToolKit" (last update 21 Oct 2012) during root process.
SuperSU work great for me~

Uninstall as system app

The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?

DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
Sorry as I don't have a solution for your problem....
But still as far as I know Super user 2.46 is not fully compatible with android 5 & above.
On other hand I would suggest you to give a try to super user 2.49 beta which is the latest but still under development.
Hope you find this useful.
ayushbpl10

DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If you want to make SuperSU a user app:
If SuperSU was "updated" by the Play Store (ie there's an eu.chainfire.supersu-*.apk in /data/app), then delete /system/app/SuperSU.apk and reboot. If it's flashed *and* the afore mentioned apk is *not* in /data/app, then move /system/app/SuperSU.apk to /data/app and reboot.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

Sent from my Aqua i5 mini using xda-developers.com, powered by appyet.com

DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app

mmonaghan34 said:
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
Click to expand...
Click to collapse
That doesn't work (v2.46 on LG G3 running v5.0.1). It loops trying to uninstall. After a couple minutes, I forced a reboot. SuperSU was still there, and as a system app.
Edit: The same thing happens when I tell SuperSU to completely unroot the LG G3. Since I needed to unroot in order to apply an LG/Verizon OTA update, I used LG's Flash Tool to replace the system partition (THAT removed SuperSU!), and then the OTA update was successful.
Since LG now supplies an on-phone backup/restore tool for the G3 as part of the Settings menu, I no longer need to run Titanium Backup, which means I no longer need root. Given the nuisance issues with rooting/unrooting/system updating/etc, I've decided to remain unrooted on the LG G3 for the time being. Quite a change for me, since this is the first Android device in well over a dozen for which I've made this decision.

Caterpillar s40 + Xposed?

I have cat s40 met 5.1 Lollipop. This Smartphone is success rooted by rootking.
I want have Xposed on that phone, but when i fail mod that phone how i recover back it?
Caterpillar don't released PC suite like "Samsung Smart Switch" or "Odin". Is any alternative for flash cat s40?
I don't saw any Stock ROM in internet for that phone and i don't found source code for that phone.
I don't found TWRP for that phone is released for it?
Caterpillar s40 is compatible to Xposed? someone have Xposed on that phone?
I search too good program for backup NAND and recovery before try install custom recovery.

Could you find or possibly post your stock Cat S40 rom?

Fudgehog said:
Could you find or possibly post your stock Cat S40 rom?
Click to expand...
Click to collapse
Can't no tools for do that and i don't search more because i my cat s40 send on warrianty.
Now i have formatted clean and no more root that... :/
I had bricked this phone after change root ap KingRoot to SuperSU.
This phone don't have recovery or anyother program like SmartSwitch. No TWRP.
Now i don't try mod this phone like my Samsung because i don't want again brick this phone.

OK I see. Thanks anyway.

Fudgehog said:
OK I see. Thanks anyway.
Click to expand...
Click to collapse
I think I am able to get hold of a rom!!

That would be great but..
I have the S50 and there are still no custom recoveries for either that I'm aware of.

someone has problems with the touch?

cangrejon said:
someone has problems with the touch?
Click to expand...
Click to collapse
Double posting, duh!
Click here.

Source Code S40 + Recovery Mode
Source code cat s40
http://www.catphones.com/en-gb/legal/general-terms-and-conditions
but we don't have access to file for now lol
Cat S40 Source Code
but Cat B15Q can download normally.
Cat B15Q Source Code
i found too how enter Recovery Mode maybe isn't it CWM or TWRP but better that than nothing
1. PowerOff phone
2. Connect USB cable to phone
3. Press and hold the Vol +
4. Connect USB cable to PC or Power Supply
5. Recovery Mode!
I hope after we can download source code someone can make TWRP of custom ROM for us ;]

Cat s40 SuperSU + Xposed
I have SUCCESS ROOT + SuperSU + Xposed on my Cat s40 :]
1. Kingroot root
2. install "SuperSU_v2.65.apk" ( i installed it by Lucky Patcher as System app)
3. Reboot
4. use script "switch_armv7.sh" i added script i found that on XDA forum but i don't remember where.
If script don't work you can try again gain root by kingroot and in SuperSU update supersu binary ( SuperSU can detect Kingroot so you must uninstall it) This script worked for my Cat s40 fine.
5. After script install new binary in SuperSU app
6. SuperSU succes!
7. FlashFire flash Xposed Binary ( i added too Xposed binary)
7. Reboot ( boot is longer than normal)
8. You have SuperSU root and Xposed Framawork on your Cat s40
You can too by FlashFire make backup your system partition and use it in TWRP if someone do it for us... or flash it after gain SuperSU root ( FlashFire on Kingroot don't working)
You do it at your own risk!
First i tried that method on myPhone Infinity LTE ( i can that flash by computer when it bricked )
I think it can work on all Android 5.1 lollipop.

Wirusx, thanks for the feedback.
Can i get more detail and confirmation :
First use kingroot 4.9.3 found here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
After that it's rooted, and then you install the script in supersubinary.rar . But can you explain in detail to put what file where on the S40, or do we only need to install the superuser.apk file?
Is xposed framework nessesary found here: http://forum.xda-developers.com/showthread.php?t=3034811
How about use uptodate kingroot and after that supersumepro ?

Rooted Cat S40 running 5.1 Lollipop
After several attempts and reboots all ok. Caterpillar Cat S40 running Lollipop 5.1 working fine.
1st thanks to all devs. (VickyB, MrW0lf, Chainfire etc). :good:
Then. My attempt consisted from pointers or several threads. Started with Wirusx and got something else from somewhere else. I try getting a whole picture here.
(I did not look for fresh look, but better battery consuption, better security and such. So no new roms etc needed. Cat is quite plain and sleek anyway.)
Basically it was of Wirusx instructions, but with some tweaks as apparently at this stage some update has tightened Cat OS that fewer exploits work.
Several files has be in phone (internal storage worked for me, sdcard not). One app from Gplay (Terminal Emulator) and ->
see this thread: http://forum.xda-developers.com/android/apps-games/replace-kingroot-supersu-t3339950
1. Kingoroot - 2. Reboot - 3. Run Script (which will give you also SuperUser app). - 4. Reeboot - 5. Updated Superuser and another reboot.
- Done.
There were some moments when not all ok. After 3, verified through Emulator who is "in charge". "su -v" in same directory as you ran the original script. Showed SuperUser 2.65, so all ok. But apps listed listed KingoRoot/Purify. But not SuperUser, although the root was through it. I had to download it again via Play. After 5 all ok "in Wonderland".
Some pointers from unknown threads (which I failed to find again). Apparently the situation was like the following exerpt shows.
"It seems that the script doesn't work the same way on every device. For me, it just deleted Kingroot,
and left me with just a temporary root terminal, . SuperSU was never launched nor installed,
and when I installed it I got a "There are no su binaries installed".
I did the following to install SuperSU:
1. Run the script for your proper architecture.
2. If it doesn't launch SuperSU at the end or even worse, if you install it but get the
" no su binaries", DON'T close the last root terminal.
3. Run
su -v
If it returns something like SUPERSU-2.65 you're good to go. If it doesn't,
re-run the script again in order to push the proper su binary again.
4. Go to the terminal and type:
mount -o rw,remount /system
chmod 7777 /system/xbin/su
chmod 7777 /system/xbin/daemonsu
Note: at this point SuperSU will start to work, even if you didn't update its binaries.
4. Open SuperSU. It'll ask you to update its binaries, press yes.
5. Since it's highly advised to have SuperSU in /system in order to preserve root access
through updates, you just gotta move the SuperSU.apk included in the zip to /system /app and
chmod it with 0755 permissions.
I downloaded SuperSu from Play and it worked.

Rooted Cat S40 firmware update
Hi!
Is it possible (ad if yes, how) to update the firmware of a rooted Cat S40. My rooting process was the previously mentioned Kingroot -> SU, but after this the OTA update does't finish, even with FlashFire.

jeroensky said:
Wirusx, thanks for the feedback.
Can i get more detail and confirmation :
First use kingroot 4.9.3 found here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
After that it's rooted, and then you install the script in supersubinary.rar . But can you explain in detail to put what file where on the S40, or do we only need to install the superuser.apk file?
Is xposed framework nessesary found here: http://forum.xda-developers.com/showthread.php?t=3034811
How about use uptodate kingroot and after that supersumepro ?
Click to expand...
Click to collapse
supersumepro = android frezze on boot = send phone for warrianty ;/

pliz share

anyone else succeeded in rooting?

After contacting CAT and bullet-group they managed to fix their "Open Source Codes" section and add links. Sadly, no actual response
(*sigh* can't add links)

SuperSU in CM13 and CM13 based ROMs

Is there any way to use SuperSU in CM13 or CM13 based roms such as Resurrection Remix? In particular on a Nexus 6P?
I ask because I have been using RR for quite some time now but until recently never really noticed the limitations of CM's privacy guard. SuperSU pro has always seemed like a better implementation of a Root management app to me when I've used it in the past on previous devices.
I had considered just disabling root access from the setting in developer options and then updating the binary from the SuperSU app via TWRP and hoping that SuperSU would take over root management after that but I have read that a few people have bricked/bootlooped their devices after doing that and I don't want to have to deal with fixing that.
Many thanks in advance for any help you can provide.

Squall88uk said:
Is there any way to use SuperSU in CM13 or CM13 based roms such as Resurrection Remix? In particular on a Nexus 6P?
I ask because I have been using RR for quite some time now but until recently never really noticed the limitations of CM's privacy guard. SuperSU pro has always seemed like a better implementation of a Root management app to me when I've used it in the past on previous devices.
I had considered just disabling root access from the setting in developer options and then updating the binary from the SuperSU app via TWRP and hoping that SuperSU would take over root management after that but I have read that a few people have bricked/bootlooped their devices after doing that and I don't want to have to deal with fixing that.
Many thanks in advance for any help you can provide.
Click to expand...
Click to collapse
After disabling the root option within the Developer Options, when you open SuperSU and go to the Settings, do you leave the option for "Respect CM root settings" unchecked?
With CM/LOS, when you disable the root option, in SuperSU, you need to keep the "Respect CM root settings" unchecked or SuperSU will default the root to Disabled.
Many individuals don't know that.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

Ibuprophen said:
After disabling the root option within the Developer Options, when you open SuperSU and go to the Settings, do you leave the option for "Respect CM root settings" unchecked?
With CM/LOS, when you disable the root option, in SuperSU, you need to keep the "Respect CM root settings" unchecked or SuperSU will default the root to Disabled.
Many individuals don't know that.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
Click to expand...
Click to collapse
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs

Squall88uk said:
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I am in the same boat. I am using the the latest RR FROM which is awesome, but I'm not wanting to use magical. Have always used super SU and stick Mount for my next SD. Would like to know the process for disabling manual and cm/Los root mgmt. To use Super SU. I can't use stick Mount with root explorer without super SU. WHEN I try to update binary it fails and if I try to flash in recovery, I get stuck in boot loop and have to restore backup.

Having a similiar problem on Galaxy S2 with RR 5.8.2 - installed SeperSu and it fails to update its binary when I choose 'normal'. Tried Cwm/Twrp option on a stock rom once and the phone got softbricked. Converting SuperSu to system app doesn't help.
---------- Post added at 05:05 AM ---------- Previous post was at 04:48 AM ----------
Squall88uk said:
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
No such option appears in SuperSu after disabling root access in dev options here also.

There was a time a while ago that I had asked something similar to to one of the CyanogenMod Team Developers.
I was told that when the Superuser option (in the Developer Options) is set to disabled, that means that the CyanogenMod systems Superuser access is left open. When one of the other options are set, that means that the CyanogenMod system is set to manage Superuser access that is seen by the new access to the Manage Root Access option below it.
So in short, disabled means root access is left open and CyanogenMod doesn't manage it.
If you use another root management app, like SuperSU, and leave the Root Access on disabled, then SuperSU takes on managing Root Access.
I've never had a problem with SuperSU and always left the Root Access disabled.
I hope i had explained it okay...
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***

Ibuprophen said:
There was a time a while ago that I had asked something similar to to one of the CyanogenMod Team Developers.
I was told that when the Superuser option (in the Developer Options) is set to disabled, that means that the CyanogenMod systems Superuser access is left open. When one of the other options are set, that means that the CyanogenMod system is set to manage Superuser access that is seen by the new access to the Manage Root Access option below it.
So in short, disabled means root access is left open and CyanogenMod doesn't manage it.
If you use another root management app, like SuperSU, and leave the Root Access on disabled, then SuperSU takes on managing Root Access.
I've never had a problem with SuperSU and always left the Root Access disabled.
I hope i had explained it okay...
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***
Click to expand...
Click to collapse
Disabled Root access in developer options, rebooted phone and started Supersu, it tries ro update its binaries and fsils again. Then I look for the "respect CM root settings" option but don't see it.
Some people are having success flashing the Supersu.zip through TWRP but isn't there a risk of replacing the RR bundled recovery and ending in bootloop? Is it possible to flash TWRP zip from RR recovery without causing more issues?

kikot said:
Disabled Root access in developer options, rebooted phone and started Supersu, it tries ro update its binaries and fsils again. Then I look for the "respect CM root settings" option but don't see it.
Some people are having success flashing the Supersu.zip through TWRP but isn't there a risk of replacing the RR bundled recovery and ending in bootloop? Is it possible to flash TWRP zip from RR recovery without causing more issues?
Click to expand...
Click to collapse
I attached an image of where in SuperSU the setting is but, I leave it unchecked...
Try flashing the SuperSU zip since flashing it also installs the binaries too.

BETA-SuperSU-v2.72-20160510112018 flashed facing issues?

Hi,
I have flashed beta SuperSU 2.72 variant on my phone which is a Le Max 2. Now I had done this when I had installed AOKP marshmallow based custom rom on the device.
Now I have installed Resseruction Remix official nougat based Rom on the device. Now the issue is that the device is showing as rooted via root checker.
Super su installed via Google play store shows Su binary occupied.
Device is not showing any SU tools in settings.
I wanted to know that is how to remove/ unroot the su 2.72?
Is it possible to flash it to a higher version via twrp recovery i.e my installed recovery app? If so I will do so.
I kind of new to Android system so I will appreciate any help.

Richdad said:
Hi,
I have flashed beta SuperSU 2.72 variant on my phone which is a Le Max 2. Now I had done this when I had installed AOKP marshmallow based custom rom on the device.
Now I have installed Resseruction Remix official nougat based Rom on the device. Now the issue is that the device is showing as rooted via root checker.
Super su installed via Google play store shows Su binary occupied.
Device is not showing any SU tools in settings.
I wanted to know that is how to remove/ unroot the su 2.72?
Is it possible to flash it to a higher version via twrp recovery i.e my installed recovery app? If so I will do so.
I kind of new to Android system so I will appreciate any help.
Click to expand...
Click to collapse
The "Su binary occupied" issue is currently being discussed on the following Official SuperSU thread:
[STABLE][2017.05.27] SuperSU v2.82 by Chainfire
I wish you the best of luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise

Ibuprophen said:
The "Su binary occupied" issue is currently being discussed on the following Official SuperSU thread:
[STABLE][2017.05.27] SuperSU v2.82 by Chainfire
I wish you the best of luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
Click to expand...
Click to collapse
I have sorted this thing out. I found Su binary occupied means something went wrong during super su installation in twrp.
Just flashed the super su again with latest variant i.e 2.82 and then the SuperSU app began showing up on booting.
Unrooted the Rom from there and rebooted the device. Root removed and everything was back to normal.

Richdad said:
I have sorted this thing out. I found Su binary occupied means something went wrong during super su installation in twrp. Just flashed the super su again with latest variant i.e 2.82 and then the SuperSU app began showing up on booting. Unrooted the Rom from there and rebooted the device. Root removed and everything was back to normal.
Click to expand...
Click to collapse
Chainfire had stated that when there's an "SU Binary Occupied" message, it means that there's already a Non-SuperSU SU binary file present in the device.
This usually reflects that the SU Binary file was previously installed by another Superuser installation. The SU Binary is more than likely located in the "/su/bin" but, that all depends on where the previous Superuser installation had placed it.
For LineageOS users, this is typical of the users having the LineageOS SU installed from the LineageOS Extras.
Seeing that you've got it all under control then I wish you the best of luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise

Ejdndklfmmnxnxmxkk:good::victory:........