yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S3] Frankie12226:
Fixed

Gear S3 Classic w S7 Edge phone:

Ultimately, we do not want to have to reset our watch and reinstall apps and whatnot. However, that is the path I took, NOT INTENTIONALLY MIGHT I ADD, and it fixed everything...and it wasn't as bad as I dreaded it would be...

#1 - On phone, I unpaired my gear s3 watch from bluetooth list on my s7 edge.

#2 - On phone, I uninstalled gear s plug in from apps list.

#3 - On phone, I went to apps list and cleared cache and data from gear wearable app (cannot uninstall gear wearable app...see next step).

#4 - On phone, I uninstalled UPDATES for gear wearable app as well.

#5 - After that, I went to play store and updated gear wearable app to current version. When I opened the updated galaxy wearable app, it went through the beginning of the set up process, ultimately, repairing my watch w phone. i THOUGHT i COULD DO THIS WITHOUT RESETTING THE WATCH. But a message popped up saying I needed to reset watch in order for them to pair, and it did it itself w push of a button. So, I bit the bullet and reset watch. I did intentionally try to connect them without resetting watch, but it just wouldn't work. In hindsight, I am thinking that was the issue that was causing text notifications to not work.

I thought I was going to have to go through this long drawn out process of setting watch back up, but I did not. ***I did not select restore watch when setting the watch up with app, I instead selected "skip" and went forward like pairing a new watch.*** I figured if I just reinstated the old settings, I'd get the old problems. I was freakishly worried it would be a pain in the a$$ to do this, but it really wasn't. Partly because after pairing the watch, the gear wearable app had updates listed and ready to download without any hassle. I was also worried about resetting up samsung pay, but that was also a breeze. Not sure if this method of resetting was not a "true" factory reset, because the watch was up to date with software, I did not have to update tizen or anything. Now, text notifications work like a charm! I would highly recommend this. I did not lose any contact information or contact pics either.

#6 - I created a back up at this point in gear wearable app, now that I know text notifications work.

2 side notes:

First - I honestly didn't want to reset watch, but it seems to be working perfectly now. And if I had to do this again, I know it wouldn't take me any time at all to fix. I would definitely do this again if I had to. It was that easy.

Second - before I did all this, I tried using Textra SMS, and that app sent notifications to my phone no problem. But I wanted to fix the issue, not use a workaround.
[LineageOS News & Discussion] jtrvk:
https://download.lineageos.org/extras

Root addon packages are available now :D
[LineageOS News & Discussion] Newmanl:
What's the diference between suaddon from lineage and supersu? do I need to flash both? or do I need to pick one?
[LineageOS News & Discussion] jhedfors:
SuperSU is a closed-source, proprietary superuser solution, and the other is LineageOS provided solution. There are other options as well, such as PHH Superuser. Choose one, they all essentially do the same thing.
[LineageOS News & Discussion] Newmanl:
Thank you I'll stay with superSU (I've allways been on this) LOL
[LineageOS News & Discussion] saggydey:
Can i use phh's superuser? I mean magisk cause root isn't enabled by default in new Lineage os.
[LineageOS News & Discussion] jhedfors:
Magisk w/ PHH Superuser works great.
[LineageOS News & Discussion] saggydey:
Thanks a lot.. Then i won't flash supersu i just have to install magisk and phh's superuser from play store and install it from there? Currently i'm using Samsung Galaxy Grand 2 running lineage os 13.1
[LineageOS News & Discussion] MiroBiala:
addonsu-arm-signed.zip can't flash via recovery

addonsu-arm-signed.zip can't flash via recovery. Gives an error : Updater process ended with signal: 4

Phone : Samsung Galaxy S3 Int (i9300)

OS : lineage-14.1-20170125-nightly-i9300-signed

Recovery : TWRP 3.0.2-2

PS : When I got update-binary (META-INF/com/google/android/update-binary) from addonsu-arm64-signed.zip and replaced in addonsu-arm-signed.zip, I was able to flash it!
[LineageOS News & Discussion] jhedfors:
Yes, should work.
[LineageOS News & Discussion] toll_virus:
I'm a i9300 owner with the same problem. Could you please supply me with the working su-addon-arm. I couldn't manage to exchange the file in the zip-archive.

I appreciate your help!!!

Franz
[LineageOS News & Discussion] saggydey:
I did everything its even showing my phone is rooted properly but safetynet failed CTS profile mismatch error :/
[LineageOS News & Discussion] beatmastr:
Same Phone, same OS, Recovery TWRP 6.0.4.7 Non Touch GT-I9300

But no chance to root lineage! Plz help
[LineageOS News & Discussion] Shark5060:
is this something different than the "root" option in the developer settings? Since all apps that require root seem to work with just that setting.

EDIT: Okay, I've just read the reason: https://review.lineageos.org/#/c/154019

since my device isn't officially supported yet the developer who uploaded the nightlies may have just enabled that by default.
[LineageOS News & Discussion] sunng87:
Is flashing this addon one-shot action or I need to flash it every time when updating LAOS?
[LineageOS News & Discussion] MiroBiala:
Here is my modified package, which I succeeded to flash : addonsu-arm-signed.zip.

UPDATE :

I also uploaded it here.
[LineageOS News & Discussion] toll_virus:
Sorry, but my virus scanner doesn't like that link....
[LineageOS News & Discussion] Xilyc:
I'm also not able to root. Seems to be a problem with the S3

Phone : Samsung Galaxy S3 Int (i9300)

OS : lineage-14.1-20170125-nightly-i9300-signed

Recovery : cwm.6.0.4.6
[LineageOS News & Discussion] koubiak83:
Same for me, did you find any solution?
[LineageOS News & Discussion] tonithetorpedo:
Magisk
[LineageOS News & Discussion] koubiak83:
Many, it works perfect!
[LineageOS News & Discussion] nezlek:
It depends

I suspect that if you have a supported build it is a one-time event, as specified. With unofficial builds it is going to be a function of HOW they get updated. If you are clearing and flashing to install an update, probably not. Then again, an UNOFFICIAL build may have built-in root from its developer. I for one will build it into my attempts for unsupported devices.
[LineageOS News & Discussion] ahmadeb:
I've just flashed the latest nightly lineage os , and Super su on my oneplus one. The Super su stayed a part of time working properly, but now it crashes at no time and give me a a message " the super su needs to be updated" and then failed to update. when I reboot the system it is stuck before boot animation.

any help please ?
[LineageOS News & Discussion] nezlek:
A few options, maybe .....

What kind(s) of BACKUPS do you have? Since re-flashing Lineage from scratch will likely de-activate SU, you could then download the newest version it seems to be hoping for and take it from there. OR, you could just install the Lineage add-on and since it is a supported build, be done with it. Haven't run across any root-requiring thing that the add on doesn't let me do.

Could also try re-flashing the BOOT area only, but that's a dicey proposition and I don't know nearly enough about the procedure for flashing YOUR device to offer much more than a generality. HOWEVER, if you have a complete set of rom images and only download select partitions you MIGHT be able to just pop in the boot, system, and recovery areas, hopefully keeping YOUR data intact (my deepest thanks to the vendor's support guy who put on to that approach after I sent his company's device to another reality).

MIGHT get away with repeating the update if you can. That may also disable SU in the process since it is NOT part of the build. Can you re-flash just your recovery?

If all those fail, I sadly go back to the question: What kind(s) of BACKUPS do you have? :fingers-crossed:

Good Luck.
[LineageOS News & Discussion] ahmadeb:
I am using TWRP backup. I think I found the problem; my backup included the super user in each time I restore, but SuperSu is not compatible with lineage OS.

For all of you, don't use SuperSu with lineage OS :). Just use addonsu :

https://download.lineageos.org/extras

Thanks [MENTION=7530175]nezlek[/MENTION] :')
[LineageOS News & Discussion] nezlek:
You are most welcome. Glad I could help. This is all a great "adventure" at the moment, but the good news is that things are moving in the right direction.
[LineageOS News & Discussion] M-in-M:
How to remove the '#' on the status bar after flashing the addonsu and enabling root? Also, when i checked with root checker apps, it is shown as unrooted.
[LineageOS News & Discussion] mymmx:
The latest Magisk v11 is working great on Lineage OS... You can install from below tutorial.

http://www.lineageosdownloads.com/get-magisk-systemless-root-lineage-os/
[LineageOS News & Discussion] ran000:
Please, more detail instruction.
[LineageOS News & Discussion] Boolian:
Many thanks for your solution. Kudos!

Credited Here

My fault if you're now plagued with questions

(Have "mirrored" your modified file)
[LineageOS News & Discussion] king555:
https://xdaforums.com/showpost.php?p=70766912&postcount=8

thanks, it worked on Galaxy S2 with LineageOS 14
[LineageOS News & Discussion] timothylow:
update after rooting

do i have to remove my root using the removal tool before every ota update?
[LineageOS News & Discussion] jhedfors:
No. And the root will remain after OTA if you are using the official root add-on.
[LineageOS News & Discussion] Athan:
I've just tried this and it still didn't work. With the current addson-arm-signed.zip I get:

Installing update...
E: Error in /data/media/0/Download/addonsu-arm-signed.zip
(Status 0)
Installation aborted.

After making a new zip with the arm64 META-INF/com/google/android/update-binary I now get:

Installing update...
Installation aborted.

I should probably check exactly what recovery is currently installed though.

---------- Post added at 06:32 PM ---------- Previous post was at 05:47 PM ----------

FWIW I am on ClockWorkMOD Recovery 6.0.4.6, which isn't quite the latest. However I've just successfully rooted using Magisk instead, as per the instructions at http://www.lineageosdownloads.com/get-magisk-systemless-root-lineage-os/ - I didn't use the SuperSU option. You just have to install Magisk Manager and then enable SU for apps: <menu> > Settings > Superuser > Superuser Access = Apps (only or also ADB).
[LineageOS News & Discussion] jhedfors:
I would strongly suggest updating to a recent version of TWRP, if it is available for your device. CWM is terribly outdated.
[LineageOS News & Discussion] Athan:
That would have been the next step if needs be. Today I couldn't be bothered setting things up to change that. Magisk is definitely working, TitaniumBackup is happy, and Terminal -> su -> id does the expected.
[LineageOS News & Discussion] Ibuprophen:
I found that when I installed the LOS14.1 Experimental version then the Nightly over a clean install of the CM13, the root addon from the Cyanogenmod remained in there (there's a whole process for the LineageOS Experimental CyanogenMod Migration install).

Just providing an FYI...

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[LineageOS News & Discussion] mika859:
Same phone. Same issue.

Is there any chance we get a new supersu package anytime soon? :)
[LineageOS News & Discussion] Boolian:
The modified Su-add-on in this thread, removes the error messages.

However, after further tests (on i9100) it was confirmed that the LineageOS "Extra" files for both su-add-on & the SU Disabler both actually work, despite showing '..signal-4' & 'failed' error messages when flashing.

So just Flash the file, make sure zip verification is NOT checked, ignore any errors, boot then check "Root Access" menu in Developer Settings and you should have options to turn on Root for eg: Apps& Adb.

See also this Post for complete details.

I'm not aware that any other SU zips will be made available as they actually do work.
[LineageOS News & Discussion] zirrott:
addonsu-x86-signed.zip - z00d

I have the same probleme with flash addonsu but with the x86 version addonsu-x86-signed.zip.

I cannot put nor arm nor arm64 update-binary :(

So, anyone could help me?
[LineageOS News & Discussion] Boolian:
See the link in my post above.

The x86 is probably just the same it shouldn't require modification.

, uncheck zip verification, flash, ignore all errors, reboot, Go to settings, developer options, Tap on Root access and see if the actual options to turn on appear there.

If the options do not appear & the x86 does not work, that is then a problem certainly.

Let us know. Give details of Phone & Rom etc.

The modification is only required to remove error messages (on Arm at least) not to actually make it work.
[LineageOS News & Discussion] M!tch:
is there any way too hide superuser from apps like starfinanz / dkb push tan?
[LineageOS News & Discussion] zirrott:
I have tried many times... Same error with always no change in the Root access.

I'm on a Zenfone z00d woth the last Lineage built
[LineageOS News & Discussion] Boolian:
Best directed at maintainer and thread for your device.

There appeared to be possibly boot & certainly SU/root issues with LineageOS for your device, requiring it's own custom SU flash.

See Here
[LineageOS News & Discussion] zirrott:
Thank you ;)

I download the addonsu-x86.zip and it works great!
[LineageOS News & Discussion] Alteross:
I wasn't able to flash the LinageOS root "addonsu-arm-signed.zip" until I upgraded my TWRP to the latest version. Then it installed (again with a minor error but at least root could be enabled in the Developer Settings).
[LineageOS News & Discussion] chuchipando:
The su packages in the lineage download website say they are version 14.1. Will these work with lineage 13?
[LineageOS News & Discussion] daitalos:
In CM13

This will give you an error...you can flashing SuperSU in cm13 via twrp : https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[LineageOS News & Discussion] Martell:
Here again - the same message, the same phone. Clean flash lineage-14.1-20170301-nightly-signed + open_gapps-7.1-mini-20170303 + adonsu-arm-signed. I didn't want to bother myself and rebooted the phone. And what a surprise - in the devs menu there was the root option, I switched it on and everything worked like charm. Or was it because my previous unofficial ROM (cm-14.1-20161122-UNOFFICIAL-i9300) had root built-in? :confused: :good: :p
[LineageOS News & Discussion] IronRoo:
They have fixed the bug in LOS13 SU according to the following, so hopefully it will be available soon

http://lineageos.org/Last-Week-in-LineageOS-4/
[LineageOS News & Discussion] arvinp:
Awesome. This fixed my problem of getting SU on lineageos on my i9300. Thanks very much.
[LineageOS News & Discussion] Zdene:
Cyanogenmod recovery , lineage 13 , no rooted with addons , on GT 2 p5100 . no gapps - cannot instal , cm recovery verified fail . HORROR!!!!!! 200MB system only !?!??? Terminal not in su .adb not work . .
[LineageOS News & Discussion] needmymorningcoffee:
I found that on Lineage roms, to get proper root, download Magisk from the Play store. Open app, download the zip file, flash it through recovery, and restart.

SuperSU failed installing on 2 devices for me. I did some digging, saw someone suggesting Magisk, and tried it out. Properly rooted my old Galaxy Tab 2 7.0 and Galaxy S4.
[LineageOS News & Discussion] FreedomS5:
Tried multiple times/ways to get root with the addon package without success.

Galaxy S III i747m
[LineageOS News & Discussion] gudsng:
i have some problem for my phone zenfone 2 Z00D, can u help me?
[LineageOS News & Discussion] RaskVonTreve:
Fail to change system files

Asus Z00L

I have installed and enabled SU, but it denies any change for sys files; since Android Marshmellow, my GPS stopped working and the only solution I found was to change gps.conf file.

The last updates of Lineage change the File Manager app and the behavior of SU tasks is unstable: some works, some don't.

How can I edit the gps.conf file?

Thanks
[LineageOS News & Discussion] Ibuprophen:
Just an FYI...

Lineage just released the SU Addons for the LOS13.0 for the ARM32 and ARM64 Here:

https://download.lineageos.org/extras

They're still working on the release for the x86 addons.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

**IF I WAS HELPFUL IN ANY WAY THEN**

**PLZ THANK ME WITH A THUMBS UP!**
[LineageOS News & Discussion] hellwhynot:
Didn't work for me, using an official LOS 13.0 nightly. After flashing I got the extra options in the dev options menu, but when I checked 'Apps only' I didn't have root (verified with Root Checker). Supersu does work.

Anybody who got the addonsu for 13.0 to work yet?

Update: It works now. Didn't feel like doing a factory reset earlier, but that's what was needed in my case.
[LineageOS News & Discussion] vampsm:
Yes, this ist a Option and works perfect

Thank You
[LineageOS News & Discussion] nobicycle:
Using addonsu-arm-signed.zip worked for me (nexus4). An app requested root and popups allowed me to grant permission.

But I was wondering if there was a suitable app to keep track of which apps have grants?

Thank you
[LineageOS News & Discussion] Ibuprophen:
SuperSU is a Root Management tool that will manage and also track the permissions. It also allows you to manually change already approved permissions in other ways.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[LineageOS News & Discussion] nobicycle:
Hi,

Before posting I already tried Superuser 45.731 ClockworkMod . I'll try Chainfire SuperSU as you suggest.

Best wishes

Update

SuperSu did not detect 1 app already granted root via LineageOs super su zip.

Perhaps it would do so if it were installed first.

SuperSU asked to update via TWRP (present) so I allowed it.

Nexus4 is now hanging during boot after 5 minutes. I don't believe it will come up.
[LineageOS News & Discussion] Ibuprophen:
That's because you had both of them managing it.

You should disable the LineageOS su so SuperSU can provide the management.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[LineageOS News & Discussion] nobicycle:
Update 2

I had to factory reset and reinstall lineageos.

The answer is: There is a perfectly good root app management facility in the developer options of lineageos. No need for any extra app to be installed.
[LineageOS News & Discussion] Baniita:
Still didn't work for me. Same error, still. Which is strange. I've tried it for 5 hours now without luck; countless wipes and restores and sometimes getting stuck in bootloop... sigh

Do I need to unlock my bootloader for this? And if so, how?

I'm NOT supposed to flash it after flashing chainfire's auto root, right?

arm7 is this one, right...?

I flashed it with and without chainfire's auto root, and neither worked--it only worked the first time and that was after flashing chainfire's auto root, and it won't happen again and I have no idea why. The only time it flashed was when I flashed 64x (but my sytem's not 64x...), but then it never worked again after that first time.

In the root options, it still only gives me "disabled" or "adb", no other options. I don't know how I did it before.

ugh, let me try Magisk...
[LineageOS News & Discussion] Boolian:
If I knew your setup I could perhaps advise. But I've no idea what your device specifications are, or how you are proceeding.

It's fairly simple. You should have an unlocked bootloader and know if you have.

You should have successfully installed LineageOS

Root is not required for this.

http://wiki.lineageos.org/install_guides.html

You check if you need to partition your device.

Ideally you flash an Isorec Recovery (eg TWRP)

You Flash the correct LineageOS for your device.

Boot & configure.

You boot to recovery & flash the Official Su-Add-on specifically for your device :

and also the correct version - Arm64 or Arm

(The "modified" file posted here and elsewhere is not required. The "modified" file is only modded to remove error messages during flashing)

Ignore any error messages when flashing the official SU-add-on

Boot to LineageOS & enable Developer Options and go to "Root Access" & specifically set the root access you require.

The SU-add-on you flashed will not set this automatically.

It will not show until you go in and manually select the options you want there.

Of course you could throw absolutely everything including Gapps into a single flashing session, but I'd recommend one thing at a time. Good luck.
[LineageOS News & Discussion] Baniita:
I already have Lineage installed. I just don't know how to get it with the Lineage root add on.

Also all my questions were in my original message:

> Do I need to unlock my bootloader for [flashing addonsu]? And if so, how?

> I'm NOT supposed to flash it after flashing chainfire's auto root, right?

> arm7 is the file for the first one without 64x or 84, right?

None of them have been answered.

The error message persists.
[LineageOS News & Discussion] Boolian:
Your bootloader is probably unlocked if you have LineageOS already installed.

Cf-auto root is not required and not used.

CF-auto root is not part of the LineageOS or SU add on install procedure.

I don't know your device, so I don't know which Su-add-on (Arm) file you need.

I don't know which error message you mean, but if it is the "..signal-4" error, then ignore it.

It is a 'junk' error and not important and does not affect the installation.

If the Developer Settings Root Access Menu does not give you four different options to select, after you have flashed the add-on from TWRP recovery, then it is the wrong file, a bad download ( check md5) or you are running a conflicting system (CF-auto-root) which is not part of the procedure.

If in doubt about anything, go back to the beginning and follow the LineageOS install instructions, for your device, from the link I posted.

I can't say any more to help than that.
[LineageOS News & Discussion] Baniita:
Thanks.

In that case... o ~o None of the files worked for me. I checked which one my phone was, and all it told me was "arm7", and googling told me it /wasn't/ x64. The other two didn't work, neither did the custom package. All gave the same error. I tried it without CF-auto-root... I /think/? I... I'm not sure, actually. I'm assuming root leaves if you reformat/wipe your entire phone.
[LineageOS News & Discussion] Boolian:
What's the model of your phone?

Which version of LineageOS?

What error message?
[LineageOS News & Discussion] bnolsen:
I'm in the same boat wrt only having ADB as a root option. I have a surnia (moto e 2015) and currently the 20170407 lineageos version. I switched from cm14.1 to lineageos probably in jan. At the time i had an older version of twrp, since updated to 3.0.0-r2. Neither lineageos su addon nor chainfire will install. I would like to eradicate all the cyanogenmod directories on the internal storage...

looks like magisk installs, i'll test out the functionality but really would prefer root thrugh lineageos itself...i remeber something like that working before but it might have been through cm.

okay root checker fails with magisk installed...
[LineageOS News & Discussion] winchendonsprings:
After flashing the su add on is there a spot on the menu to control which apps have access?
[LineageOS News & Discussion] jhedfors:
You have to enable it in settings. I think in developer options (I use a different root).
[LineageOS News & Discussion] tltan86:
personally, i think this visible '#' sign is good to stay, in case any unintended malware is accessing your system using root capability (assuming the malware does not disable the '#' sign that is. ha.).
[LineageOS News & Discussion] Mort015:
Thx works great on my Klte S5