Related
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.
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)
Follow this guide to flash SuperSU on the latest version of android wear for your watch, it should have the same OS compatibility as normal SuperSU and should work all the way upto android 7.1.1
(from PC)
1.Unlock the bootloader if not already unlocked
(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)
Code:
adb reboot bootloader
fastboot oem unlock
2.flash TWRP for your device (REQUIRES read only access to system!, will post working builds in post below)
Code:
fastboot flash recovery recoveryname.img
3.Download SuperSU with busybox YDS included HERE and move it to watch with adb push to /sdcard while TWRP is booted and then install as normal zip
Code:
adb push nameofzip.zip /sdcard/
4.IGNORE SYSTEM NOT INSTALLED Boot watch to system and Now your root apps from 5.1 should work perfect. THERE WILL BE NO SUPER SU APP, IT HAS NOT BEEN PORTED TO ANDROID WEAR
REMEMBER squashfs is read only even with root so don't bother trying to modify system files like the build.prop.
If you would like to modify system use any Linux distro and unsquash the system then resquash it (will make guide if enough interest)
If you would like to change pixel density perform this command in either adb shell or a terminal emulator:
Code:
wm density <dpi>
Please leave thanks if it helped!
Feel free to submit links to twrp for squashfs watch with model name, codename and original developer's name
Will add them to this post
THESE ARE THE ONLY BUILDS THAT WILL WORK UNTIL TWRP IS UPDATED!
I DID NOT CREATE ANY OF THESE BUILDS!
LG G Watch dory (courtesy of @rbox)
LG G watch R lenok
In regards to Busybox on Rails, I compared the link provided and Google Play (which I assume is latest), they are the same versions. Is there a trustworthy place to find the old version suggested?
Not sure if I will need it, just covering my bases. Upgrading to 6.0.1 tonight.
Thanks.
First post and Thanks to you!!!
This is my first post in the community, i thank you all for all you do! I have successfully rooted lg g watch with android 6.0.1 build mec23d using your method. busy box pro installed after uninstalling superuser.
OfficerJimLahey said:
In regards to Busybox on Rails, I compared the link provided and Google Play (which I assume is latest), they are the same versions. Is there a trustworthy place to find the old version suggested?
Not sure if I will need it, just covering my bases. Upgrading to 6.0.1 tonight.
Thanks.
Click to expand...
Click to collapse
Oh I thought it was an older version will edit that as the latest did not work On 5.1.1 wear but I guess it those on 6.0.1
itsthamessenger said:
This is my first post in the community, i thank you all for all you do! I have successfully rooted lg g watch with android 6.0.1 build mec23d using your method. busy box pro installed after uninstalling superuser.
Click to expand...
Click to collapse
Glad I could help! I was not aware the busybox pro worked on wear is it the one by stericson?
Xmaster24 said:
Glad I could help! I was not aware the busybox pro worked on wear is it the one by stericson?
Click to expand...
Click to collapse
Yes it is!
itsthamessenger said:
Yes it is!
Click to expand...
Click to collapse
Thanks for the info will add to post
Unless I am missing something, system access is needed for the LG G Watch.
Tried with TWRP 3.0.0 and 2.8.7, SuperSU 2.65 flash was successful in spite of /system not mounting (notice was given in red letters), rebooted, with same result across both versions:
Code:
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb uninstall eu.chainfire.supersu
Failure [DELETE_FAILED_INTERNAL_ERROR]
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb install Downloads/BusyBox%20On%20Rails_5.1.74_apk-dl.com.apk
1087 KB/s (2287614 bytes in 2.053s)
pkg: /data/local/tmp/BusyBox%20On%20Rails_5.1.74_apk-dl.com.apk
Success
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb shell
[email protected]:/ $ su
/system/bin/sh: su: not found
127|[email protected]:/ $
Looks like SuperSU is not even bothering with system-less mode:
http://pastebin.com/T7k0cWHv
OfficerJimLahey said:
Unless I am missing something, system access is needed for the LG G Watch.
Tried with TWRP 3.0.0 and 2.8.7, SuperSU 2.65 flash was successful in spite of /system not mounting (notice was given in red letters), rebooted, with same result across both versions:
Click to expand...
Click to collapse
Huh I used a modified version of the latest TWRP from a member that allowed the system to be mounted read only as squashfs is a read only file system ie. The system image has to be rebuilt to make changes. I assumed that since supersu is now system less it those not require system access but maybe it those but I really didn't see the use of mounting it read only as it cannot make any changes to system. Will edit thread thanks for info. Link to squashfs twrp above
It is strange though the other poster managed to root without system access.
Xmaster24 said:
Huh I used a modified version of the latest TWRP from a member that allowed the system to be mounted read only as squashfs is a read only file system ie. The system image has to be rebuilt to make changes. I assumed that since supersu is now system less it those not require system access but maybe it those but I really didn't see the use of mounting it read only as it cannot make any changes to system. Will edit thread thanks for info.
Click to expand...
Click to collapse
The third time I flashed to get the log, I attempted to mount /system as read only, since it didn't mount properly otherwise. The onscreen messages looked the same anyway...successful flash, but could not mount /system. And upon leaving TWRP, it warned that no OS was installed. Nothing different for all intents and purposes.
Thanks, I will try your TWRP and report back.
UPDATE:
Your TWRP made all the difference:
Code:
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb uninstall eu.chainfire.supersu
Success
[email protected]:~$ Build/android-sdk-linux/platform-tools/adb shell
[email protected]:/ $ su
[email protected]:/ #
Thank you!
OfficerJimLahey said:
The third time I flashed to get the log, I attempted to mount /system as read only, since it didn't mount properly otherwise. The onscreen messages looked the same anyway...successful flash, but could not mount /system. And upon leaving TWRP, it warned that no OS was installed. Nothing different for all intents and purposes.
Thanks, I will try your TWRP and report back.
UPDATE:
Your TWRP made all the difference:
Thank you!
Click to expand...
Click to collapse
No problem guess SuperSU those require system access to work it seems to be for SE Linux patching and also the build.prop
Xmaster24 said:
<snip>
4.Boot to system and open Busybox on rails app and install busybox
<snip>
Click to expand...
Click to collapse
Thanks for this guide! Rooted AOK :good:
This Step 4 is to install Busybox on Rails onto the phone? or Watch?
drewski_1 said:
Thanks for this guide! Rooted AOK :good:
This Step 4 is to install Busybox on Rails onto the phone? or Watch?
Click to expand...
Click to collapse
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch
Xmaster24 said:
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch
Click to expand...
Click to collapse
got it. thanks again!!
Highly recommend everyone to get invisiblek's kernel its top notch gets rid of the horrible lag of 6.0.1's kernel And is fully supported by my root method so even better!
Sent from my GT-S5830i using XDA Free mobile app
Where do supersu and busybox get installed
Xmaster24 said:
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch
Click to expand...
Click to collapse
Since the new wear has a read only system, where do the supersu and busybox get installed?
ganovim said:
Since the new wear has a read only system, where do the supersu and busybox get installed?
Click to expand...
Click to collapse
SuperSU is now system less if you haven't been following it recently so system access is not required also bits of supersu are stored in the kernel disk and others just at /data. Busybox is stored with the SU mounted image to /su/xbin once installed via the app
/moved to specific lg g watch thread
Hi, I need your help
I have a MK903V Android TV HDMI Stick (Android 4.4.2, API Level 19). I need it to run apps requiring root without prompting for root access - which SuperSU allows.
The stick has a root shell via adb and comes with a su binary ("su --help" says "SuperSU v1.99 - Copyright (C) 2012-2014 - Chainfire"). I cannot boot a recovery like TWRP (I guess).
I've tried:
- install and run superuser.apk v1.99, says it must update su binary, fails updating su binary (normal mode)
- install and run superuser.apk v2.79, says it must update su binary, fails updating su binary (normal mode)
- install and run towelroot, says it got root, install superuser.apk (v2.79), says it must update su binary, fails updating su binary (normal mode)
- rooting via Kingo Root (PC), works including its su prompt on root apps (like the bloatware it installs), running superuser.apk, says it must update su binary, fails updating su binary (normal mode) (never prompted for root)
I found articles saying you could run the installer script from the update.zip, which is used to install SuperSU from recovery, in an adb root shell if you adapt it... I'm not so much into unix stuff / shell, so I'm pretty sure I won't do that on my own. Moving two or three files to the devices and setting chmod/chown is not a problem, but the script looks way more complicated...
Is there actually a version of the script that can run from a adb root shell?
Is there any other way I can get SuperSU on a device I already have root access to?!? Didn't think that could be so complicated...
Thx
P.S. I'd also take a su binary that just grants all access and doesn't even come with a gui
upgrade mk903v to android 5 or higher
How do i upgrade my mk903v stick to a higher version of Android. It comes with 4.4.2 kit kat. Any help would be appreciated...
Thanks
EDIT: SKIP THIS - READ NEXT
Okay, I finally rooted the device...
- Installed KingRoot APK (v5.0.4) from https://kingroot.net/
- Ran KingRoot which did its suspicious magic on the device for more than 15min
- Installed SuperSU and granted it root
- Ran the root.sh script attached which basically kills and removes KingRoot and lets SuperSu replace su binary
- Ran SuperSU again and successfully updated su binary
It is the only solution I found so far...
Sometimes the web just confuses me...
Found this:
http://freaktab.com/forum/tv-player-support/rk3288-devices/17987-new-3288-ez-root-tool
Simple and clean "update.zip" [MD5:7a2755fd5ebe8a2928fc01a4ab0cbabb]
Copy to internal or external sdcard and just reboot or wait for the system popup that says that a new firmware update was found. Update will be applied and device got proper (but old) SuperSU installed.
After that, you may just install the latest SuperSU. (is there a reason why the latest APK is not available on http://www.supersu.com/download#apk ??)
[email protected] said:
How do i upgrade my mk903v stick to a higher version of Android. It comes with 4.4.2 kit kat. Any help would be appreciated...
Thanks
Click to expand...
Click to collapse
Hello,
Did you solution for this?
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.