Jolla Tablet Announced: The Second Sailfish OS Device

A little over a year ago, Jolla released its first smartphone with the brand new Jolla … more

Android One Devices Get Unofficial CM12 Port

Android One was initially announced right before Android Lollipop. By releasing these cheap, yet … more

WhatsApp Decides to Protect Your Data

When Facebook bought WhatsApp for the absurdly large sum of $19bn back in February, they took the tech … more

Bring Back LTE on the Google Nexus 4 Running Lollipop

One of the predecessors of the latest, largest, and greatest Gooogle Nexus 6(theGoogle … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] What is the Best App or Way to Keep Root after Flashing Zip?

OP xnickfx

20th January 2014, 09:48 PM   |  #1  
xnickfx's Avatar
OP Member
Thanks Meter: 99
 
64 posts
Join Date:Joined: May 2013
More
I love Custom ROMs and Kernels and I'm sure you all do too. It seems that every time I flash my favorite CM ROM which has a built in CM SuperUser found within Settings and then after flashing my favorite kernel, I simply lose root for the ROM and the SuperUser stops working. I want to know how to get the CM SuperUser working again after flashing the zip in recovery.

Here is where my problem seems to be different than others. I can get root back by installing SuperSU and then going to settings and telling it to "Ignore CM Root Settings" and then rebooting, then root access works with SuperSU and the system thinks its doing its job too...but then when I uninstall SuperSU the entire problem comes back.

So my question is, is there a solid method to keeping the built in CM SuperUser found in Settings working as it did before flashing that zip that broke the ROMs root in the first place?

Any help is greatly appreciated! Thanks so much in advance!
Last edited by xnickfx; 20th January 2014 at 10:06 PM.
20th January 2014, 11:02 PM   |  #2  
Cloonix's Avatar
Member
Flag Munich
Thanks Meter: 10
 
62 posts
Join Date:Joined: Sep 2010
More
I think you are experiencing a similar problem like I did ( http://forum.xda-developers.com/show....php?t=2602670 ). Am I right?

My root in CM11 is not working properly. So every time I flash CM11 with TWRP, I have to flash SuperSU right after CM11 and my kernel.

My personal explanation is, that SELinux (enforcing) doesn't work well with CM11 yet.
20th January 2014, 11:18 PM   |  #3  
xnickfx's Avatar
OP Member
Thanks Meter: 99
 
64 posts
Join Date:Joined: May 2013
More
Quote:
Originally Posted by Cloonix

I think you are experiencing a similar problem like I did ( http://forum.xda-developers.com/show....php?t=2602670 ). Am I right?

My root in CM11 is not working properly. So every time I flash CM11 with TWRP, I have to flash SuperSU right after CM11 and my kernel.

My personal explanation is, that SELinux (enforcing) doesn't work well with CM11 yet.

Yeah, I'm pretty sure we are having the exact same problem seeing that it's CM and you flashed a kernel which broke your built-in root.

Isn't there an update for the built-in SuperUser or something? CM is really popular so I know some people have liked it enough to want to keep the built in SuperUser and not use a halfa$$ workaround. Don't get me wrong, SuperSU is LEGIT, but I want the built-in SuperUser this time because I don't want it sitting in the Settings for no purpose.

Anyone? Thank you in advance!
20th January 2014, 11:19 PM   |  #4  
mistahseller's Avatar
Senior Member
Flag Saint Louis
Thanks Meter: 199
 
814 posts
Join Date:Joined: Mar 2013
More
superuser updated today and fixed the CM breaking root deal.


What's New
- New -cn/--context parameter for su binary (devs: see How-To SU update)
- Handle mksh being switched out for sh
- Daemon forces new session immediately at launch (moved up)
- Fixed reading dynamic properties on 4.4 (update ASAP if 4.4 user)
- Fixed issue where root wasn't granted on CM
- Add support for Samsung 4.4
- Update copyright notices to 2014
- Updated language files
Additional information
Updated
January 20, 2014
Last edited by mistahseller; 21st January 2014 at 12:06 AM.
20th January 2014, 11:35 PM   |  #5  
BirchBarlow's Avatar
Senior Member
Flag Philadelphia
Thanks Meter: 126
 
364 posts
Join Date:Joined: Oct 2013
More
I think the latest version of SuperSU (1.91) is supposed to fix that.
21st January 2014, 12:54 AM   |  #6  
Cloonix's Avatar
Member
Flag Munich
Thanks Meter: 10
 
62 posts
Join Date:Joined: Sep 2010
More
Quote:
Originally Posted by mistahseller

superuser updated today and fixed the CM breaking root deal.


What's New
- New -cn/--context parameter for su binary (devs: see How-To SU update)
- Handle mksh being switched out for sh
- Daemon forces new session immediately at launch (moved up)
- Fixed reading dynamic properties on 4.4 (update ASAP if 4.4 user)
- Fixed issue where root wasn't granted on CM
- Add support for Samsung 4.4
- Update copyright notices to 2014
- Updated language files
Additional information
Updated
January 20, 2014

The problem is imho the built-in superuser by CM (https://play.google.com/store/apps/d...droid.su&hl=en or https://play.google.com/store/apps/d...uperuser&hl=en) not SuperSU. Actually I'm not really sure which one is used in CM.
21st January 2014, 01:37 AM   |  #7  
simms22's Avatar
Recognized Contributor
BROOKLYN!
Thanks Meter: 22,370
 
26,696 posts
Join Date:Joined: Jun 2009
Quote:
Originally Posted by Cloonix

The problem is imho the built-in superuser by CM (https://play.google.com/store/apps/d...droid.su&hl=en or https://play.google.com/store/apps/d...uperuser&hl=en) not SuperSU. Actually I'm not really sure which one is used in CM.

cm uses superuser. flashing supersu fixes the issue and rids cm of everything superuser related.
21st January 2014, 09:54 AM   |  #8  
xnickfx's Avatar
OP Member
Thanks Meter: 99
 
64 posts
Join Date:Joined: May 2013
More
It looks like, at least from all the research I did today, that there actually might be a fix for all this by possibly updating the actual ROMs built-in version of SuperUser.

If you look at this version of the SuperUser app by ClockworkMod on Google Play, you can see in one of the screenshots it shows an app requesting permission from what looks like the exact UI as the built-in SuperUser we see in our CM-based ROMs.

CM Built-In SuperUser App on Google Play:
https://play.google.com/store/apps/d...utta.superuser

Screenshot of SuperUser found on Google Play:


I will report back if I can find a solution or fix!
Last edited by xnickfx; 21st January 2014 at 09:57 AM.
21st January 2014, 10:07 AM   |  #9  
Cloonix's Avatar
Member
Flag Munich
Thanks Meter: 10
 
62 posts
Join Date:Joined: Sep 2010
More
Quote:
Originally Posted by xnickfx

It looks like, at least from all the research I did today, that there actually might be a fix for all this by possibly updating the actual ROMs built-in version of SuperUser.

If you look at this version of the SuperUser app by ClockworkMod on Google Play, you can see in one of the screenshots it shows an app requesting permission from what looks like the exact UI as the built-in SuperUser we see in our CM-based ROMs.

CM Built-In SuperUser App on Google Play:
https://play.google.com/store/apps/d...utta.superuser

Screenshot of SuperUser found on Google Play:


I will report back if I can find a solution or fix!

You could try to get the .apk of SuperSU or CM's superuser and put it in the "app" or "priv-app" folder of your CM-ROM .zip-file.

I tried to simply replace the su-binary in the xbin folder... Stupid idea though. Didn't work out
21st January 2014, 02:21 PM   |  #10  
xnickfx's Avatar
OP Member
Thanks Meter: 99
 
64 posts
Join Date:Joined: May 2013
More
Info 2
Bummer, so I didn't find a solution / fix, but I did find some possibly helpful links.

These are options that I researched very deeply in any and every way possible. Notes for found possibilities are noted below the option, if any.

Opt-1 .) Locate where the files or code for the built-in SuperUser are located within ROM and update / replace them with newest version of SuperUser, and also gain root when re-root is needed.

Opt-2 .) Replace SuperUser found in CM-based ROM's Settings with newest version of SuperSU by either deleting from ROM's Settings somehow or keep it and have SuperSU built in ROM's Settings same as current SuperUser.

I do believe that somewhat of Option #2 might be possible. I don't really know for sure yet, but I found these other 2 links that look pretty interesting.
http://forum.xda-developers.com/show....php?t=2033590
http://forum.xda-developers.com/show....php?t=1539711

I know you can install SuperSU and pretty much ditch SuperUser for good, but then you still have it sitting in the ROMs settings for no reason at all.

You can remove and hide SuperUser from the ROMs settings but in order to do that you have to completely disable root. You can remove it by going to Developer Options or SuperUser settings and choosing "disable" for SuperUser Access. Unfortunately when doing this SuperSU immediately stops working even when open and closes the first chance it gets.

If anyone else can shed any light at all on the subject, it would be VERY MUCH appreciated! Thank you!
Last edited by xnickfx; 21st January 2014 at 02:25 PM.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes