Related
Figured I would start here in my device thread before trying the SuperSU thread.
Anybody have issues with SuperSU since the last few updates ago?
SuperSU does not even open. Root-dependent apps do not open. Titanium sits there at the initial screen "asking for root rights" until I kill the app. AdAway does not open... just goes right to a black screen until I kill the app. AdAway seems to work though, as my web surfing does not have ads.
I've also tried manually going in and applying the latest update via (philz) recovery.
Would I be safe to roll back to an older version of SuperSU?
Mods... if you're going to gun the thread, please at least point me in the right direction as I did search, but did not find anything related to recent issues on the Note 2 for SuperSU.
TIA for help and suggestions.
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
ceabbott2 said:
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
Click to expand...
Click to collapse
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
lennykravitz2004 said:
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
Click to expand...
Click to collapse
For me, I just reflashed the ROM I was running at the time and that resolved it. Of course seeing that the update was " fixed" I attempted it and lost root again. I then did the same as before, wiped and relashed. I didn't do clean installs either time. Just wiped caches and reflashed. That sucks if you have to re-root. I mean, it's easy and all but it shouldn't have to be done.
D
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
DJ_Barcode said:
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
Click to expand...
Click to collapse
Thanks for the try. Did not work though.
Looks like I just need to re-flash the ROM.
My problem was odd. Before I discovered the aforementioned trick, I'd re-root with Chainfire or Kingo. I'd reboot, and my device would be rooted. But those two methods have an additional payload - they flash the stock recovery. So I'd ODIN the Philz Touch recovery back to the device, reboot, and root would be gone. Never figured out what was going on.
Yup. Issues with new version. Only last 2 or three updates.
They seemed to be perfectly fine with cm12 though.
Sent from my SPH-L900 using XDA Free mobile app
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
lennykravitz2004 said:
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
Click to expand...
Click to collapse
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
As always, thanks for your response. Your recommendation is what I've been doing, just wanted to follow-up on this and see if there was anything else I needed to consider or change as well.
My main concern was to make sure I was not going to run into any "big" issues (especially security) by staying on current version. Thanks for explaining where the issue really lies on this too. I'm obviously not a dev, however I do want to understand what is exactly going on and responses like yours always provide that type of info. :good: Thank you.
And, FWIW, using "fool proof" to describe a process only makes me more curious (and no, not in that way) about your suggestion. :laugh:
Now I HAVE to find out more about that option... (only after some of the best BBQ in all of the land - Sugarfire BBQ in STL )
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
How do you disable auto update of binary on SuperSU? I keep seeing it in the notification bar, very annoying.
see #5 for problem
Hi guys,
so after quite some time with custom Roms I decided to go stock again as somehow I don't need root at all. Well, that's not true. I miss AdAway.
As there is no possibility to root the stock rom, is there ANY AdBlocker that works on Lollipop? AdBlock Plus doesn't (yet).
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
ckpv5 said:
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
Click to expand...
Click to collapse
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
fBx said:
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
Click to expand...
Click to collapse
Flash twrp recovery and root through the recovery. It'll ask you when you reboot the system if you want to root it
Sent from my HTC One_M8 using XDA Free mobile app
Huh. Didn't know it was THAT straightforward and I've been flashing my phones for years.
Well. I flashed TWRP and SuperSU 2.46, succeeded. But Adaway and Adfree don't work correctly. They block the ads but only until you reboot, then it's reverted, kinda like with a tethered jailbreak on iPhones.
What am I doing wrong here? Also the block is not like on KitKat - there it was really blocked, really removed, here only the images of the ads are removed but you still see the space they were supposed to be.
I also used a system app removal tool that also didn't work although it shows success. It just removes the installed data like updates.
When I delete apps manually via ES Explorer, they just reappear at the next reboot.
Root Checker says root is fine but it isn't supposed to behave like that and undo my changes.
What's wrong? Do I need another kernel maybe? As I said I went back to stock completely and updatet through to L.
I believe I got whats causing the issue.
After deleting a system app and rebooting, I got a message saying that the phone was restored from an "unnormal behaviour". Does Lollipop bring some kind of system restore point that just automatically restores itself when "weird" things like host file alteration happens? If yes, how do I get rid of that?
This phone has always had system files protected since KitKat. You need a kernel mod to delete system apps.
Don't know why the ad blockers aren't working. Adaway is working fine for me on stock US Dev Edition rooted. You said you are using Adaway and AdFree? Are you actually using both at the same time? maybe they are interfering with each other?
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Maybe I should try installing xposed and see if it's gone after a reboot.
fBx said:
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?t=2701816
But unfortunately, flar2 hasn't had the time to update for LP. A user posted the kernel module in Post #210, but a subsequent user said it doesn't work. Custom ROMs have write protection disabled, as does Dev Edition stock ROM.
fBx said:
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Click to expand...
Click to collapse
Odd, as mentioned, I've used AdAway for quite some time now, and don't have these issues.
Yes, very odd indeed. Well, if I don't get it sorted out somehow I might as well switch to Viper or some other close to stock custom Rom again, or make it Dev like you.
Things are getting worse, in 1 of 2 cases AdAway spits an error at me when trying to apply the fixes and the phone just reboots and undos everything. It's like some protection from rooting or changing anything although I am rooted. I don't understand it. I can't possibly be the only one having problems with root on Stock Lollipop
This is really annoying me. I think I'm better of just installing a custom rom and setting the phone up again, will cost me an hour but at least I'm done with the bugs.
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
fBx said:
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
Click to expand...
Click to collapse
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
redpoint73 said:
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
Click to expand...
Click to collapse
I also assume that's the reason. I've never been on a stock rom since I don't know when, but figured that actually I only wanted AdAway which would normally not require a custom rom per se... but as it didn't really work in the end (and also other root-requiring stuff), I went back to custom again. Well, it's not that it's that difficult to wipe the phone occasionally and set up a clean custom rom to get it back to perfect performance. Gonna go with it.
Hi, I have tried a Cyanogenmod 13 on my M8 dual sim and it installed and run fine.
Well, until I tried to install my gps offline navigation apps.
Without full access to the sd card they will not install.
Is there any way enable write access?
Titanium Backup worked with a setting change and ES explorer also has access. But how?
Formatting to internal is not an option.
I am back to Lollipop for now.
Thanks.
Some navigation apps makes Problem with write access
Er? Isn't that what I said? So what's the solution then?
gazzacbr said:
Er? Isn't that what I said? So what's the solution then?
Click to expand...
Click to collapse
Write privileges need to be granted on a per-app bases now. Try going into Settings>Apps, finding the app in question, and go to Permissions, and see if you can toggle "on" the Storage toggle.
redpoint73 said:
Write privileges need to be granted on a per-app bases now. Try going into Settings>Apps, finding the app in question, and go to Permissions, and see if you can toggle "on" the Storage toggle.
Click to expand...
Click to collapse
Hi, I would give that a try if I could get the app installed. Problem is that the app will not install as it say it cant find the sd card.
I may try installing via Titanium Backup then fixing after.
What I was really hoping for is a fix like "just let me give access to everything because its my phone"
gazzacbr said:
Problem is that the app will not install as it say it cant find the sd card.
Click to expand...
Click to collapse
This sounds like a problem with the app and its developer, more than anything. The app apparently hasn't been properly updated for the requirements of Marshmallow, a version that has been around for over 5 months; so the app developer has had ample time to do so.
gazzacbr said:
What I was really hoping for is a fix like "just let me give access to everything because its my phone"
Click to expand...
Click to collapse
Such a hack would be a bad from a security standpoint. The very point of app-by-app granting of permissions is to prevent rogue apps from accessing permissions and data that they aren't supposed to. Compartmentalization is a good thing.
redpoint73 said:
...Such a hack would be a bad from a security standpoint
Click to expand...
Click to collapse
I can see that for 'average Joe' but for me that should be my decision, thats why I would never use a locked non rooted phone.
Still looking for a fix. I am sure it will come soon.
Otherwise happy to stay on (unrestricted) lollipop for now.
Hi,
so the greatness of XDA does it again.
on Cyanogenmod 13 Marshmallow on my M8 dual sim
loaded ExtSD_Fix from twrp http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
and also XInternalSD from Tasker from here
http://forum.xda-developers.com/xposed/modules/xposed-disablesignaturecheck-t2789267/
and full access and control of MY SDcard.
Not sure if I needed both of these but, hey, its all working fine now.
Hi,
I'm using LineageOS on my LG G3,
After upgrading from XenonHD-170504-Official-d855.zip to XenonHD-170522-Official-d855.zip my Root Access setting (in developer options) has gone and I don't have root access in any app any more. SuperSu generates this error:
Code:
"SU binary occupied"
Also downgrading to the previous Rom didn't solve the problem.
This method (called how-to-enable-root-in-lineage-os-using) doesn't work, and almost all other methods in XDA such as "KingoRoot", "LG One Click Root " and ... didn't work either..
Any solution would be appreciated.
Thanks
Wrong thread
@light-blue: if you flashed with wipe system, you always must flash su.zip to get su-access (since ROMs come unrooted). Use su2.79 for now, because 2.8x are buggy.
rp158 said:
@light-blue: if you flashed with wipe system, you always must flash su.zip to get su-access (since ROMs come unrooted). Use su2.79 for now, because 2.8x are buggy.
Click to expand...
Click to collapse
Thanks @rp158
When I do it nothing happens .
It says that the zip successfully installed (or something like that), and when I boot into the system again I don't see any root access.
Try this...
STEP 1:
Go to Settings. Click on About phone and then Tap Seven times on the Build number.
STEP 2:
Now to enable ROOT access, open Developer options and then scroll a little bit down on the Developer Options settings and look for the Root access setting, which must be showing Disabled.
Just click on the Root access and set it to Apps and ADB or Apps only or ADB only, as per your need.
Chrisenglish90 said:
Try this...
STEP 1:
Go to Settings. Click on About phone and then Tap Seven times on the Build number.
STEP 2:
Now to enable ROOT access, open Developer options and then scroll a little bit down on the Developer Options settings and look for the Root access setting, which must be showing Disabled.
Just click on the Root access and set it to Apps and ADB or Apps only or ADB only, as per your need.
Click to expand...
Click to collapse
The problem is exactly here, The Root Access setting has gone from the developer option
Quite. I had the same issue as you though but a different phone but the above solved it for me. I also ran the su installer that was mentioned on the page you read.
Same issue on OnePlus 2 since last LOS update. I suspect is has to do with "su-hide" (see https://lineageos.org/Changelog-9/) but I have no idea how to fix it.
EDIT: The Developer option solution worked for me. I could have sworn I looked for it before posting. Sorry for the noise.
Try Magisk
light-blue said:
The problem is exactly here, The Root Access setting has gone from the developer option
Click to expand...
Click to collapse
So I have a P3100 but in my case the issue was solved by using Magisk. Download the latest zip and try flashing that. The thing is once you are all set up with the apk, go to the menu button within the app and then settings and then scroll down to 'Superuser Access' and simply click and choose the Apps and ADB option. Hope it solves your issue (Atleast it did in my case ).
I tried plenty of things but I can not regain root after flashing LineageOS.
I have tried every root flash on here and nothing worked. I don't understand the thread on here claiming to give you root on LineageOS as it's a load of crap. Really pissed off as I wanted to sell my D855 but now have to wait until someone can root...or just downgrade to LP or something with another ROM that doesn't wipe root on install...
Really unacceptable IMO for any ROM to remove root and not have a guaranteed way to regain it.
Anyone running Android Q beta 2 ? Can you make a comparison to Pie in terms of speed or apps that crash or hang? TIA
I have no apps crashing and no apps unable to start. Performance and battery are identical to Pie.
The Android Q is definitely a daily driver for me.
EDIT: The only single issue I have is that double-tap or lift to wake are not working.
Guys how to root? Android Q?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Will this work on beta 2 ??
spleenandcigars said:
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Click to expand...
Click to collapse
not work on Beta 2, bro
How best to backout of the AndroidQ beta2?
Installed but Android Auto is playing up so want to go back to v8
Can't mount system partition R/W on Marlin using TWRP 3.2.3-1 once updated to AQB2 (although I did a dirty update by removing the -w erase flag from the bat file before executing.) Guess I'll try nuking everything and rebuilding from scratch to see if the partitions will mount R/W to install Magisk...
Is anyone able to set his own mp3 ringtone on this?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
George_Bushels said:
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
Click to expand...
Click to collapse
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Homeboy76 said:
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Click to expand...
Click to collapse
Yes.
sonpro10x said:
not work on Beta 2, bro
Click to expand...
Click to collapse
As you can see in this screenshot, it's working just fine. You have to install the latest Magisk canary build. TWRP won't work to do some backups, but you can flash it fine.
Been running Q2 for a few days and is a great daily driver. As soon as Nova paid was installed I have no complaints
and battery life has been excellent. Coming from the Essential phone rooted this has been a pleasant surprise. For 180.00 new
unlocked on Sprint this is a good deal. I also prefer the 16x9 screen and camera.
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
tufyuma said:
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
Click to expand...
Click to collapse
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
bonfire62 said:
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
Click to expand...
Click to collapse
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
tufyuma said:
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
Click to expand...
Click to collapse
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
bonfire62 said:
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
Click to expand...
Click to collapse
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
tufyuma said:
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
Click to expand...
Click to collapse
After clean flash, still having the same issue with the downloads. Going to Solidexplorer shows that the sdcard partition never created a Download folder. Chrome also is completely not working now, so definitely rolling back until it's resolved.