Evening all,
I've just got a Galaxy S4 Mini LTE (I9151), which I've rooted and installed TWRP using the Samsung Toolkit.
I've also disabled and removed as much of Knox as I can.
However, every time I reboot, I get: "SuperSU has stopped responding".
I'm unable to load the app, and have to reinstall it for it to work. I've also tried the permission fix in Toolkit to no avail.
Any ideas?
Cheers
Gavin
I've got the exact same problem.
Sent from my SGH-T999 using Tapatalk
I tried searching because I encountered the same problem, yet failed to find a solution so I tried to fix it myself.
What I did was:
downloaded the latest superSU apk
installed it
opened the app and went to settings then chose reinstall, continue
waited for a while then re installed the downloaded apk once more
rebooted
hope it helps
I was having the same issue as listed in this thread on my s3 and following the instructions below fixed it beautifully !! I'm able to maintain root after rebooting now !!
MrPiggy27 said:
I tried searching because I encountered the same problem, yet failed to find a solution so I tried to fix it myself.
What I did was:
downloaded the latest superSU apk
installed it
opened the app and went to settings then chose reinstall, continue
waited for a while then re installed the downloaded apk once more
rebooted
hope it helps
Click to expand...
Click to collapse
Hey, today I flashed Lionage 14.1 in my Sm-j510fn with twrp. Now i wanted to installiert Root and flashed Root in my device. In the dev settings i ticked Apps and ADB. But if i now want to open Root checker and check it, it says that my device is not rooted. In Es file Explorer i also can not tick Root mode.
Anyone help PLZ
Thanks
DoppelM said:
Hey, today I flashed Lionage 14.1 in my Sm-j510fn with twrp. Now i wanted to installiert Root and flashed Root in my device. In the dev settings i ticked Apps and ADB. But if i now want to open Root checker and check it, it says that my device is not rooted. In Es file Explorer i also can not tick Root mode.
Anyone help PLZ
Thanks
Click to expand...
Click to collapse
Download a recovery flashable zip from here: and flash in TWRP.
http://www.supersu.com/download
Sent from my N9515 using Tapatalk
bcrichster said:
Download a recovery flashable zip from here: and flash in TWRP.
http://www.supersu.com/download
Click to expand...
Click to collapse
I would not give up so soon. At least try a clean installation of ROM and addonsu in one twrp session.
DoppelM said:
Hey, today I flashed Lionage 14.1 in my Sm-j510fn with twrp. Now i wanted to installiert Root and flashed Root in my device. In the dev settings i ticked Apps and ADB. But if i now want to open Root checker and check it, it says that my device is not rooted. In Es file Explorer i also can not tick Root mode.
Anyone help PLZ
Thanks
Click to expand...
Click to collapse
https://download.lineageos.org/extras you can download it here just choose 14.1 between the 3 arm arm64 x68 depending on your device. flashing lineageOS nightlies doesnt automatically root your device
shadow_blitz said:
you can download it here just choose 14.1 between the 3 arm arm64 x68 depending on your device. flashing lineageOS nightlies doesnt automatically root your device
Click to expand...
Click to collapse
he said he already did that.
why can no one give a real answer to this issue. Installed the correct extras, says root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
It was a lot better when it was part of the rom, why the decision to remove it? all it causes is headache and people reverting away from the rom.
wrecche said:
he said he already did that.
why can no one give a real answer to this issue. Installed the correct extras, says root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
It was a lot better when it was part of the rom, why the decision to remove it? all it causes is headache and people reverting away from the rom.
Click to expand...
Click to collapse
We are talking about an unofficial LineageOS? Maybe you should talk with the person that built it.
any solution ?
Me 2
I am having the same issue.
I installed the su extra package using TWRP 3.2 .
I now have the "root" and "manage root acesses" menus under development options.
I enabled "apps and adb" option.
When I type "su" in any terminal app (including the built in one), I get "permission denied"
With root access set to "disabled", when I type "su" I get "command not found".
With root access set to "apps and adb", if I run a root checker app or try to use any app that requires root, I do not get a prompt to allow root access, and I do not get any notifications from Privacy Guard, either.
The root checker apps all say that I do not have root.
Even after running apps that should request root, when I look in the "manage root accesses" menu, it says that no apps have requested root yet.
What gives? I am really trying to use the built in root access features, I do not want to use SuperSU. Partly because SuperSU did not work either (same behavior as above), and because I don't like SuperSU's bloated code and proprietary implementation.
I really hope we can get this working, If I can provide any other info to anyone who wants to help, let me know.
I am seeing a lot of posts about this in relation to Lineage 14.1 and 15.1 and roms based on those builds. The issue is apparent on multiple different devices, so I suspect it is an issue with the base lineage source somewhere. I havn't looked at the source, though, so I don't really know... All I do know is that this is very frustrating.
m1st3r3 said:
I am having the same issue.
I installed the su extra package using TWRP 3.2 .
I now have the "root" and "manage root acesses" menus under development options.
I enabled "apps and adb" option.
When I type "su" in any terminal app (including the built in one), I get "permission denied"
With root access set to "disabled", when I type "su" I get "command not found".
With root access set to "apps and adb", if I run a root checker app or try to use any app that requires root, I do not get a prompt to allow root access, and I do not get any notifications from Privacy Guard, either.
The root checker apps all say that I do not have root.
Even after running apps that should request root, when I look in the "manage root accesses" menu, it says that no apps have requested root yet.
What gives? I am really trying to use the built in root access features, I do not want to use SuperSU. Partly because SuperSU did not work either (same behavior as above), and because I don't like SuperSU's bloated code and proprietary implementation.
I really hope we can get this working, If I can provide any other info to anyone who wants to help, let me know.
I am seeing a lot of posts about this in relation to Lineage 14.1 and 15.1 and roms based on those builds. The issue is apparent on multiple different devices, so I suspect it is an issue with the base lineage source somewhere. I havn't looked at the source, though, so I don't really know... All I do know is that this is very frustrating.
Click to expand...
Click to collapse
I bet you have installed unofficial lineageOS. On all my officially supported devices root works as expected.
kurtn said:
I bet you have installed unofficial lineageOS. On all my officially supported devices root works as expected.
Click to expand...
Click to collapse
Essentially saying 'it works great for me, you must be doing something wrong' isn't actually a very practical troubleshooting approach. While there is definitely the possibility that I am doing something wrong, troubleshooting will reveal if I have made a mistake and will also benefit the loads of other people posting about similar or same issues. That's why we have forums, right?
You bet wrong, do I win anything?
Like I mentioned, I have experienced this issue with both Lineage 14.1, 15.1, as well as unofficial builds and ROMs based on Lineage.
It is hit or miss, in most cases I just tried flashing different ROMs on my devices until I find one that has working built-in root.
I had a lot of issues installing the official builds on my 'bacon' device, I eventually went with resurrection remix instead. That was the only Oreo build that built-in root packages worked with.
In the case of my 'klte' (g900v variant), I installed 7 different Oreo based ROMs. Since there is no official Lineage build for the 'klte' (which is sad, it's a great device), I was using all unofficial builds in the case of this device. They were all based on Lineage, or just unofficial Lineage builds focused on supporting the klte. I couldn't get the built in root functionally working on any of these builds (Lineage unofficial 14.1 & 15.1, Havoc OS, etc). If anyone thinks it will help, I can elaborate further on which packages and versions I used...
Rooted lineageos not recognized
I have exactly the same issue with my Samsung S3 I9300.
I flashed it with lineageos using CWM and thereafter I flashed with the extra armsu. I cannot see anything I could have done wrong. However, neither Titanium nor a root checker recognizes the rooted state. As far as I can see there are quite many having the same issue. Unfortunately most replies are just best guesses like flash with TRWP or add gapps (the katter didn't solve the oroblem either. I am not an expert but I successfully got rid of extremely persisting boot loops most probably caused by Magix which I avoided therefore with this try to root the lineageos.
warbexda said:
I have exactly the same issue with my Samsung S3 I9300.
I flashed it with lineageos using CWM and thereafter I flashed with the extra armsu. I cannot see anything I could have done wrong. However, neither Titanium nor a root checker recognizes the rooted state. As far as I can see there are quite many having the same issue. Unfortunately most replies are just best guesses like flash with TRWP or add gapps (the katter didn't solve the oroblem either. I am not an expert but I successfully got rid of extremely persisting boot loops most probably caused by Magix which I avoided therefore with this try to root the lineageos.
Click to expand...
Click to collapse
So what's your goal? Just moaning or asking for help? In the 2nd case you should provide more details like filenames and procedures.
And yes. Root works well on my S3.
kurtn said:
So what's your goal? Just moaning or asking for help? In the 2nd case you should provide more details like filenames and procedures.
And yes. Root works well on my S3.
Click to expand...
Click to collapse
Yes you are right. Just moaning is not an option. Here are the details:
1. Flashed with lineage-14.1-20181025-nightly-i9300-signed.zip using CWM
2. Installed Titanium (with "not rooted" as result of course)
3. Installed addonsu-15.1-arm-signed.zip using CWM and changed the setting to "apps and ADB" , an option which I didn't have before - however, with no effect on Titanium
4. Checked root status with "Root Checker" which resulted in "not rooted"
5. Installed open_gapps-arm-7.1-pico-20181120.zip using CWM (because someone suggested it as solution) - with no effect.
Now to the observed "irregularities":
1. The installation of the "addonsu" which I repeated had a "Warning: No file_contexts." but ended successfully
2. The reboot metioned: " Root access possibly lost. Fix?" which I replied with "Yes fix root (/system/xbin/su)"
Possibly worth to be mentioned: Titamium tries with command "system/bin/su". I've checked that su resides in both directories bin and xbin with identical size
In writing this I realized the version mismatch 14.1 lineageos and 15.1 addonsu. I uninstalled addonsu 15.1 and installed addonsu 14.1 instead and THIS SOLVED THE PROBLEM
Many thanks for your help.
warbexda said:
Yes you are right. Just moaning is not an option. Here are the details:
1. Flashed with lineage-14.1-20181025-nightly-i9300-signed.zip using CWM
2. Installed Titanium (with "not rooted" as result of course)
3. Installed addonsu-15.1-arm-signed.zip using CWM and changed the setting to "apps and ADB" , an option which I didn't have before - however, with no effect on Titanium
4. Checked root status with "Root Checker" which resulted in "not rooted"
5. Installed open_gapps-arm-7.1-pico-20181120.zip using CWM (because someone suggested it as solution) - with no effect.
Now to the observed "irregularities":
1. The installation of the "addonsu" which I repeated had a "Warning: No file_contexts." but ended successfully
2. The reboot metioned: " Root access possibly lost. Fix? Which I replied with "Yes fix root (/system/xbin/su)"
I hope this helps.
Click to expand...
Click to collapse
Ha! For a 14.1 Rom you need a 14.1 addonsu
For future readers:
There are two versions of lineage os root images, 32 and 64 bit. Please check that you installed correct one, this way I solved this problem!
Solution
wrecche said:
he said he already did that.
why can no one give a real answer to this issue. Installed the correct extras, says root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
It was a lot better when it was part of the rom, why the decision to remove it? all it causes is headache and people reverting away from the rom.
Click to expand...
Click to collapse
Did you get any solution???????
Atharva C said:
Did you get any solution???????
Click to expand...
Click to collapse
Solution for what? I think lineageOS people found the best way to ship a non-pre-rooted ROM with native root solution.
NO ROOT Access
kurtn said:
Solution for what? I think lineageOS people found the best way to ship a non-pre-rooted ROM with native root solution.
Click to expand...
Click to collapse
Are u able to provide a way to Root?
Atharva C said:
Are u able to provide a way to Root?
Click to expand...
Click to collapse
Flash the su package from download/extras matching your lineageOS version. Enable root in settings/developer
NO ROOT Access yet #failed
kurtn said:
Flash the su package from download/extras matching your lineageOS version. Enable root in settings/developer
Click to expand...
Click to collapse
Root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
StykerB said:
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
Click to expand...
Click to collapse
Are you using Adware?
Edit: @StykerB My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
Are you using Adware?
Click to expand...
Click to collapse
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
TechnoSparks said:
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
Click to expand...
Click to collapse
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Click to expand...
Click to collapse
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
TechnoSparks said:
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
Click to expand...
Click to collapse
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Tulsadiver said:
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Click to expand...
Click to collapse
Already did that too my friend. But never mind. I am done for
Hello guys,
I'm having a huge problem with my Oneplus One running LineageOS (Android 9 Pie): when I log into the app in order to retrieve the token from my Bank APP (IWBank), I got an error ("services unavailable, try again later") so I can't access the administrative section of the APP (and handle my money).
I already tried to uninstall and reinstall the App, flush the app cache and permissions, hide the root using `Magisk hide`, reboot the phone, change SIM...
More test has been done: with another Oneplus One (running an old version of Cyanogen) the login works and the token is displayed; the same happens using another mobile phone running the same Android version;
I also tried to create a new user on my mobile phone: the error is shown again!
Is there someone that has a bank account with IWBank and is running LineageOS too or have any idea of what I can try to fix the problem?
Tnx in advance
-JeKo-
jekofx said:
Hello guys,
I'm having a huge problem with my Oneplus One running LineageOS (Android 9 Pie): when I log into the app in order to retrieve the token from my Bank APP (IWBank), I got an error ("services unavailable, try again later") so I can't access the administrative section of the APP (and handle my money).
I already tried to uninstall and reinstall the App, flush the app cache and permissions, hide the root using `Magisk hide`, reboot the phone, change SIM...
More test has been done: with another Oneplus One (running an old version of Cyanogen) the login works and the token is displayed; the same happens using another mobile phone running the same Android version;
I also tried to create a new user on my mobile phone: the error is shown again!
Is there someone that has a bank account with IWBank and is running LineageOS too or have any idea of what I can try to fix the problem?
Tnx in advance
-JeKo-
Click to expand...
Click to collapse
If i ever have to start mobile banking, i will buy an iPhone.
Hey folks, im having an issue with getting twrp up and running, as well as magisk i guess?
when i go to update twrp through google play it tells me "cant install official TWRP App, Try again, and if it will doesnt work see common ways to fix the problem" When i go to install the app through their website it tries to update that way and the update fails as well just saying "app not installed", i only have the base version at the moment with nothing in it that just tells me to update the app because its a placeholder that fits into a recovery
on the safetynet end of things if i try and pass the safetynet check i just get an api error screen?
this has been a huge headache from start to finish so if anyone can help me out here it would be grealy apprciated
siccoblue said:
Hey folks, im having an issue with getting twrp up and running, as well as magisk i guess?
when i go to update twrp through google play it tells me "cant install official TWRP App, Try again, and if it will doesnt work see common ways to fix the problem" When i go to install the app through their website it tries to update that way and the update fails as well just saying "app not installed", i only have the base version at the moment with nothing in it that just tells me to update the app because its a placeholder that fits into a recovery
on the safetynet end of things if i try and pass the safetynet check i just get an api error screen?
this has been a huge headache from start to finish so if anyone can help me out here it would be grealy apprciated
Click to expand...
Click to collapse
That's because there is no twrp for the pixel 3. There is some development for the 3 XL, but nothing for the 3.
That's because there is no twrp for the pixel 3. There is some development for the XL, but nothing for the 3.